New CUCM CDR Field Storage and Use in Variphy 11.2

New CUCM CDR Field Storage and Use in Variphy 11.2

Last updated on Mar 9, 2018 by Variphy in category CDR Reporting & Call Analytics

Variphy 11.2 introduces expanded and complete support for all new CUCM CDR fields which were added in CUCM versions 10.x - 12.0.  

These fields include Original and Final Called Party, Redirecting and Hunt Pilot Patterns which identify route and other patterns which were matched for each call:

CUCM CDR FieldField Description/Purpose
Original Called Party Pattern This is the pattern to which the original call was placed before any configured translation rules are applied.
Final Called Party Pattern The pattern of the final called party to which the call is presented until that call is answered or ringing has ended. If no forwarding occurred, this pattern is the same as originalCalledPartyPattern. This field indicates the pattern before any configured translation rules are applied.
Last Redirecting Party Pattern The pattern of the last party which redirected the call to the current called party. If there is no redirection, the field has the same value as the originalCalledPartyPattern.
Hunt Pilot Pattern The huntPilot pattern as configured in the database. This field is populated only when the HuntPilot member answers the call which is placed either directly or as a result of redirection to the huntPilot.

Additional fields are also now supported for Device Mobility info for each call:

CUCM CDR FieldField Description/Purpose
Mobile Calling Party Number If the original calling device is a mobile device, this field specifies the mobile cellular number. If the original calling device is not a mobile device, this field remains empty.
Mobile Final Called Party Number If the final called device is a mobile device, this field specifies the mobile called party. If the final called device is not a mobile device, this field remains empty.
Mobile Originating Device Name For calls from a mobile device, this field specifies the device name of the calling party. If the mobile call uses a remote destination profile the device name is the mobile number and remote destination profile name. For example, mobileNumber: RDP-name.

If the mobile device uses a mobile identity, the device name is the mobile identity name. If the original device is not a mobile device, this field remains empty.
Mobile Terminating Device Name For calls where the destination is a mobile device, this field specifies the name of the destination mobile device. If the mobile device uses a remote destination profile the device name is the mobile number and remote destination profile name. For example, mobileNumber: RDP-name.

If the mobile device uses a mobile identity, the device name is the mobile identity name. If the destination device is not a mobile device, this field remains empty.
Mobile Originating Call Duration (seconds) If the calling party is a mobile device, this field specifies the call duration in the mobile network of the originating device. If the calling party is not a mobile device, this field remains empty.
Mobile Terminating Call Duration (seconds) If the destination device is a mobile device, this field specifies the call duration in the mobile network for the destination device. If the destination device is not a mobile device, this field remains empty.
Mobile Call Type This field specifies the mobility feature that is invoked for this mobile call.
Variphy UC Tools & Analytics is trusted and used by thousands of organizations & Cisco Unified Communications/Collaboration engineers
Providing leading edge UC Management Tools to over 1200 organizations worldwide