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.

Configuring your 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 TIM Enterprise.
• 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 TIM Enterprise.
• 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 an example of system-parameters cdr configuration, Page 1:

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

Configuring Trunk-Groups

If you are using firmware R13+ you will need to set the SMDR output to 'Flexible CIL' and configure the options as below:

Configuring Intra-Switch-CDR

If you are using firmware R13+ you will need to set the SMDR output to 'Flexible CIL' and configure the options as below:

Configuring multiple Avaya Communications Managers

If you are using firmware R13+ you will need to set the SMDR output to 'Flexible CIL' and configure the options as below:

Avaya Communications Manager - LSPs (Local Survivable Processors)

If you are using firmware R13+ you will need to set the SMDR output to 'Flexible CIL' and configure the options as below:

Avaya Communications Manager - Not linked

If you are using firmware R13+ you will need to set the SMDR output to 'Flexible CIL' and configure the options as below:

Configuring TIM Enterprise

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

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 'Avaya Communications Manager'.
4. Left-click on it and select Properties.
5. From the General settings tab select Avaya Communications Manager from the PBX model list.

6. In the Connection tab select No connection required from the Connection method list.
7. Finally, click on the Save button.