Avaya Communications Manager

These instructions help you configure your Avaya Communications Manager phone system to work with TIM Enterprise. Contact your system maintainer if you are not familiar with the configuration of your PBX.

Connection Type

  TIM Enterprise listens for connections from this PBX.

Support Files

  Avaya Communications Manager.TDT
  Avaya Communications Manager.TDS

Required Tasks

  Configure the SMDR output
  Configure TIM Enterprise

Configuring your SMDR output

Connect to your Avaya Communications Manager using an RS232 or IP terminal client and, after logging in with your administrative credentials, follow the steps below:

Configuring node-names ip

Issue the change node-names command to add a new node. Two fields need to be specified as follows:

• Name: TIMPlus.
• IP Address: (the IP address of the machine running TIM Plus)

Here is an example of a node-names configuration:

Configuring ip-services

Issue the change ip-services command to add or amend IP services. There are three pages to configure:

On Page 1, the following fields are required:

• Service type: CDR1
• Local Node: (set this to the node-name of the CLAN board)
• Local Port: 0 (this cannot be changed)
• Remote Node: TIMPlus (the same node-name as created in the node-names section above)
• Remote Port: (the TCP port that TIM Plus will use to listen for CDR data, e.g. 9000)

Here is an example of an ip-services configuration (page 1):

On Page 2 no configuration changes are needed.

On Page 3 the following fields are required:

• Reliable Protocol: n
• Packets Resp Timer:  30 (default value)
• Sessions Connect Message Cntr: 3 (default value)
• SPDU Cntr: 3 (default value)
• Connectivity Timer: 60 (default value)

Here is an example of an ip-services configuration (page 3):

Configuring system-parameters cdr

Use the change system-parameters cdr command to amend the CDR format. The following screenshots describe how the settings should appear on your system:

Page 1

Configuring trunk-group

To ensure that response times for incoming calls are included in your CDR data, the CDR field for each trunk group must be set to r.  This must be applied to all trunk groups using the following command:

 change trunk-group X  (where X is the trunk group number)

An example trunk-groups configuration screen is shown below:

Configuring intra-switch-cdr

To have internal calls included in your CDRs, ensure that the intra-switch-cdr table is populated with the extension numbers you are interested in.  To modify the table, issue the following command:

 change intra-switch-cdr

Here is an example of an intra-switch-cdr configuration table:

Configuring multiple Avaya Communications Manager systems

If you have more than one Avaya Communications Manager, configuration of your CDR depends on which of the following scenarios you have implemented:

• LSPs (Local Survivable Processors)

  If your Avaya Communications Manager systems are connected and the remote sites are LSPs then you need only configure the Master/Primary Avaya Communications Manager. When TIM Plus receives the CDR information, it will include CDRs from all of the remote LSPs.

• Not linked

  If you have multiple Avaya Communications Manager systems where LSPs aren't in use, you need to configure each Avaya Communications Manager separately. You must ensure that each Avaya Communications Manager has its own unique Remote Port (IP-services) setup.

Configuring TIM Enterprise

Follow the steps below to configure TIM Enterprise to listen for SMDR data from your Avaya Communications Manager:

1. Click on the Directory tab.
2. Choose the PBX object you want to configure and click  Properties.
3. A new window will open. In the General tab, select Avaya Communications Manager from the Data format list and tick the box  Keep a local backup of data.
   
   
4. In the Connection tab, select Listen for connections from PBX from the Connection method list.
5. Leave the Host field blank.
6. In the Port field, enter the Remote Port (ip-services) that you configured above.
7. In the Connection options, enable the Timestamp data field.
8. Click on the Save button to apply the settings.
   
   

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 Avaya Communications Manager

Configuring node-names ip

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:

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 Listen for connection from PBX from the Connection method list.
7. In the Port field enter in 9000.
8. Enable the field Timestamp data.
9. Finally, click on the Save button.