Cisco VoIP Call Data Records

The Traverse VoIP module includes analysis of CDR and CMR records from Cisco Call Manager. The Cisco Call Manager must be configured to export the call detail records CDR) and call management records (CMR) to Traverse.

Cisco Call Manager (CUCM) uses FTP or SFTP to transfer these records to one or more "billing servers" - this is configured using the CDR Repository Manager (see the Cisco Unified CallManager Serviceability Administration Guide for more details on how to configure the CDR Repository Manager). When setting up for Traverse, the DGE would be one of the "billing" servers.

You will need to setup an FTP (or SSHD based server for SFTP) server on the DGE where the CUCM device is provisioned. On Linux DGEs, you can use the standard sshd for this purpose. On Windows platforms, you can use the freeSSHD application if you would like to setup a SFTP server.

Configure the Cisco Call Manager to send the CDR records to the TRAVERSE_HOME/utils/spool/cmr/input/NN directory on the DGE where NN is the department serial number. The department serial number may be obtained by logging in as superuser and navigating to Administration > Departments > Update. The Internal Object Id is the department serial number. As soon as the CDR records are placed in this directory, they are processed by Traverse automatically and used to generate CDR reports and metrics.

A DGE can accept CDR/CMR records from multiple Call Managers.When provisioning CMR tests, you need to specify the cluster ID in Traverse. For multiple CUCM instances that are not part of the same cluster, they will need to have different names to send data to the same DGE. Even though the CMR records will be in the same directory, the DGE automatically associates the data against the correct CUCM by comparing the clusterID information.

Configuring Windows freeSSHd

1. Download freeSSHd for Windows: www.freesshd.com.
2. Run freeSSHd.exe as an Administrator
3. Choose to create private keys, and run FreeSSHd as a system service when prompted.
4. Double click the FreeSSHd desktop shortcut, an icon should show up in the system tray.
5. Click the icon, it should open the settings. The SSH server should already be running.
6. Click the Users tab to add a new user. I set up a login for my local Windows administrator account, and used NT authentication, so the Windows password will be used. Authorize the user to login with shell and SFTP, and click OK.
7. If a firewall is active on the server, you also may need to add an exception for TCP port 22.
8. Test the connection with a SFTP program such as WinSCP or Filezilla.