Avaya Communications Manager

These instructions should assist in configuring your Avaya Communications Manager to work with TIM Enterprise. If you are not familiar with PBX configuration, please contact your system maintainer.

Connection information	Description
Connection type	IP: The Avaya Communication Manager requires a few changes on the system to get it to output the CDR via TCP/IP. You will find information on the required changes below.
IP Method	The Avaya Communications Manager sends the CDR data to the IP address of the TIM Enterprise machine on a specific TCP port.

Configuring your Avaya Communications Manager

Configuring node-names

You will need to use the change node-names command to add a new node. You will have two fields which are required to be populated:

Name: In this field please enter in TIMEnterprise.
IP Address: This needs to be set to the IP Address of the machine that TIM Enterprise is installed on.

Below you can find an example of node-names configuration:

Configuring ip-services

You will need to use the change ip-services command to add/ammend ip-services. There are three pages that need to be configured, below you will find, by page the fields that need to be configured.

In Page 1, you will have the following fields which are required to be populated:

Service type: This needs to be set to CDR1.
Local Node: This needs to be set to the node-name of the CLAN board.
Local Port: This cannot be changed, it is always set to 0.
Remote Node: This needs to be set to the node-name which was created in the node-names section which should be TIMEnterprise.
Remote Port: This is the TCP port that TIM Enterprise will be listening on. Generally the 9000 range is normally free so we could recommended you select one from there.

Below you can find an example of ip-services configuration, Page 1:

In Page 2, no configuration changes are needed.

In Page 3, you will have the following fields which are required to be populated:

Reliable Protocol: This needs to be set to n.
Packets Resp Timer: Please leave this as the default, which is 30.
Sessions Connect Message Cntr: Please leave this as the default, which is 3.
SPDU Cntr: Please leave this as the default, which is 3.
Connectivity Timer: Please leave this as the default, which is 60.

Below you can find an example of ip-services configuration, Page 3:

Configuring system-parameters cdr

You will need to use the change system-parameters cdr command to amend the CDR format. As there are quite a few changes, we have supplied screenshots of each page and how it should be configured.

Below you can find Page 1 of system-parameters cdr configuration:

Page 2 of system-parameters cdr configuration is as shown below:

Configuring trunk-group

To receive response times for incoming calls, you need to set the CDR field for each trunk group to r. You will need to use the change trunk-group X, 'X' being the trunk group number.

Below you can find an example of trunk-groups configuration:

Configuring intra-switch-cdr

To receive internal calls CDRs you will need to populate the intra-switch-cdr table with the extension numbers that you want to see the internal calls for. You will need to use the change intra-switch-cdr command.

Below you can find an example of the intra-switch-cdr configuration:

Configuring multiple Avaya Communications Managers

If you have multiple sites where you have more than one Avaya Communications Manager, configuring the CDR output can vary depending on the setup. The two scenarios are explained below:

Avaya Communications Manager - LSPs (Local Survivable Processors)
If all of your Avaya Communications Managers are connected and the remote sites are 'LSPs' then you only need to configure the Master/Primary Avaya Communications Manager. When TIM Enterprise receives the CDR information, it will include all of the CDRs from the remote LSPs.
Avaya Communications Manager - Not linked
If you have multiple Avaya Communications Managers where LSP isn't being used, you will need to configure each Avaya Communications Manager separately. You will need to make sure that each Avaya Communications Manager has its own unique Remote Port (IP-services) setup.

Configuring TIM Enterprise

Below you will find steps on how to configure TIM Enterprise to listen for SMDR data from your Avaya Communications Manager:

Browse to TIM Enterprise as normal and login with your credentials.
Click on the Directory tab.
Go the the point in the Directory where you need to add the PBX Object and add a PBX with the name 'Avaya Communications Manager'.
Left-click on it and select Properties.
From the General settings tab select Avaya Communications Manager from the PBX model list.

In the Connection tab select Listen for connection from PBX from the Connection method list.
In the Port field enter in 9000.
Enable the field Timestamp data.
Finally, click on the Save button.