Friday 10 April 2020

Automated CUCM CDR Exception Analyser

So Covid-19 containment has resulted in some spare time that would otherwise have been spent commuting, so I finally got around to creating something I've been meaning to do ever since I left AT&T Global Network Services, which is try to replicate their CDR exception analysis reporting. For customer's managed CUCM deployments AT&T would do an analysis of the CDR/CMR files & pick out repeated instances of non-normal call termination cause codes, as well as instances of poor call quality.
My automated version doesn't do quite the same depth of analysis, but does provide an interesting insight into the surprisingly varied & many things going wrong behind the scenes in a CUCM deployment. A CDR exception being:
  • For a given source device, all instances of a particular source cause code
  • For a given source device, all instances of a particular destination cause code
  • For a given destination device, all instances of a particular source cause code
  • For a given destination device, all instances of a particular destination cause code
  • For a given source device, all instances of poor MoS or CCR
  • For a given destination device, all instances of poor MoS or CCR

 Project hosted on my GitHub

5 comments:

  1. This comment has been removed by the author.

    ReplyDelete
    Replies
    1. This comment has been removed by the author.

      Delete
  2. This comment has been removed by a blog administrator.

    ReplyDelete
  3. This comment has been removed by a blog administrator.

    ReplyDelete
  4. This comment has been removed by a blog administrator.

    ReplyDelete