Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current ·  View Page History

These instructions should assist in configuring your Cisco UCM / Business Edition to work with TIM Enterprise. If you are not familiar with PBX configuration, please contact your system maintainer.

Connection information Description
Connection type FTP or SFTP.
Connection method The Cisco UCM will send the CDR data to TIM Enterprise via FTP or SFTP.

The tasks required to be done are as follows. They are all analysed in details further down this page.

  1. Downloading and configuring interface file UCM.zip.
  2. Creating Cisco Application User for AXL sync.
  3. Configuring TIM Enterprise to receive data from UCME.
  4. Creating AXL object to sync from UCM.
  5. Setting up FTP / SFTP on Cisco UCM to transfer CDRs to TIM Enterprise.

1.  Downloading and configuring interface file UCM.zip

  1. Visit Tri-Line's Portal and download the template file, as shown below:
  2. 3CX
  3. Extract the Cisco UCM.zip file to C:\Program Files\Tri-Line\TIM Enterprise\config folder. Zip file should contain two files, Cisco UCM.TDT and Cisco UCM.TDS.

2.  Creating Cisco Application User for AXL sync

Create an Application User on Cisco UCM, enabling TIM Enterprise to query the Cisco DB. Just follow the steps shown below:

  1. Connect to your UCM node, Select Cisco Unified CM Administration from the Navigation drop down list on the right and click Go.
  2. Login to the system, select User Management from the menu and click Application User.
  3. Click Add New from the menu.
  4. Enter in the following details:
    • User ID: TIM_AXL
    • Password: C1sco
    • Confirm Password: C1sco
  5. Scroll down to the Permissions Information section, click Add to User Group.
  6. In the new window, enter Standard Tab then click Find. Tick on Standard TabSync User and click Add Selected, followed by Save.

3.  Configuring TIM Enterprise to receive data from UCME

Below you will find steps on how to configure TIM Enterprise to listen for SMDR data from your Cisco UCM:

  1. Browse to TIM Enterprise as normal and login with your credentials.
  2. Click on the Directory tab.
  3. Go the the point in the Directory where you need to add the PBX Object and add a PBX with the name 'Cisco UCM'.
  4. Left-click on it and select Properties.
  5. From the General settings tab select Cisco UCM 5+ from the PBX model list and enable the local backup.
  6. Cisco UCM
  7. In the Connection tab select Receive FTP transfers from PBX from the Connection method list.
  8. In the Username/span> field enter in the username of your choice e.g. 'Cisco'.
  9. In the Password field enter in the password of your choice e.g. 'C1sco'.
  10. Finally, click on the Save button.
  11. Cisco UCM

4.  Creating AXL object to sync from UCM

Below you will find steps on how to configure the Directory Sync from Cisco UCM:

  1. Browse to TIM Enterprise as normal and login with your credentials.
  2. Click on the Directory tab.
  3. Go to the point in the Directory where you need to synchronise and add a new Directory Sync object with an appropriate description e.g. 'Cisco AXL'.
  4. Cisco UCM
  5. Left-click on it and select Properties.
  6. In the Directory type drop-down list select Cisco UCM.
  7. In the Host name field enter in the IP address or Hostname of Publisher node.
  8. In the Username field enter in the username configured at phase '2. Creating Cisco Application User for AXL sync', e.g. 'TIM_AXL'.
  9. Cisco UCM
  10. Click Set password and enter the password configured at phase '2. Creating Cisco Application User for AXL sync', e.g. 'C1sco', followed by clicking OK.
  11. Cisco UCM
  12. Finally, click on the Save button.

TIM Enterprise will now connect to the PBX and sync the directory objects.

5.  Setting up FTP / SFTP on Cisco UCM to transfer CDRs to TIM Enterprise

You will need to configure your Cisco UCM to send the CDR data to TIM Enterprise. Note that the UCM can be configured with cluster wide or server specific settings depending on how the system maintainer has installed it. Please note that by default CDR records are turned off.

  1. Login to Cisco UCM Administration and choose System, Service Parameters which is located on the left hand side of the screen.
  2. Select your UCM node from the Server drop down list.
  3. Select Cisco Call Manager from the Service drop down list.
  4. In the System section, change the CDR Enabled Flag to True, enable this parameter on all servers in the cluster that you want to log calls for.
  5. Change the CDR Log Calls with Zero Duration Flag to True(This parameter enables or disables the logging of CDRs for calls which were never connected or which lasted 1 second.
  6. Click on the Save button.
  7. Click on the Navigation drop-down list in the top right hand corner and select Cisco Serviceability.
  8. You may be prompted to login with a user account with Administrative permissions, if so, login with such an account.
  9. Select Tools then click CDR Management.
  10. Click Add New button. You will now see the Billing Application Server Parameters window.
  11. Enter the following parameters:
    • Host Name/IP Address: The IP address or hostname of the machine running TIM Enterprise.
    • User Name: as configured within phase '2. Creating Cisco Application User for AXL sync' e.g. 'Cisco'.
    • Password: as configured withinphase '2. Creating Cisco Application User for AXL sync' e.g. 'C1sco'.
    • Protocol: Select FTP or SFTP as configured above.
    • Directory Path: Enter /.
    • Remove the tick from Resend on Failure.
  12. Now click on the Add button to complete the Billing Server configuration. The UCM node will check that the FTP/SFTP details are correct and will write a test file to the FTP/SFTP directory.
  13. If it fails you should check the FTP or SFTP details, configures above.

You have now completed the configuration.

NOTE: If you have more than one server in your cluster you must repeat Steps 1 to 5 for each node. This will enable the UCM nodes to start creating CDR records, which are stored on the Publisher Node.

Labels: