<p>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.</p> <table class="confluenceTable"> <tbody> <tr> <th class="confluenceTh" width=158>Connection information</th> <th class="confluenceTh">Description</th> </tr> <tr> <td class="confluenceTd"><b>Connection type</b></td> <td class="confluenceTd"><b>IP: </b> 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. </td> </tr> <tr> <td class="confluenceTd"><b>IP Method</b></td> <td class="confluenceTd">The Avaya Communications Manager sends the CDR data to the IP address of the TIM Enterprise machine on a specific TCP port. </td> </tr> </tbody> </table> <h2>Configuring your Avaya Communications Manager</h2> <h4>Configuring node-names</h4> <p>You will need to use the <span class="reference">change node-names</span> command to add a new <i>node</i>. You will have two fields which are required to be populated:</p> <ul> <li><b>Name:</b> In this field please enter in <span class="keyword">TIMEnterprise</span>.</li> <li><b>IP Address:</b> This needs to be set to the IP Address of the machine that TIM Enterprise is installed on.</li> </ul> <p>Below you can find an example of node-names configuration:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_1.png" alt="Avaya Communications Manager" /> <h4>Configuring ip-services</h4> <p>You will need to use the <span class="reference">change ip-services</span> 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.</p> <p>In <b>Page 1</b>, you will have the following fields which are required to be populated:</p> <ul> <li><b>Service type:</b> This needs to be set to <span class="keyword">CDR1</span>.</li> <li><b>Local Node:</b> This needs to be set to the node-name of the CLAN board.</li> <li><b>Local Port:</b> This cannot be changed, it is always set to <span class="keyword">0</span>.</li> <li><b>Remote Node:</b> This needs to be set to the node-name which was created in the <span class="reference">node-names</span> section which should be <span class="keyword">TIMEnterprise</span>.</li> <li><b>Remote Port:</b> 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.</li> </ul> <p>Below you can find an example of ip-services configuration, <b>Page 1</b>:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_2.png" alt="Avaya Communications Manager" /> <p>In <b>Page 2</b>, no configuration changes are needed.</p> <p>In <b>Page 3</b>, you will have the following fields which are required to be populated:</p> <ul> <li><b>Reliable Protocol:</b> This needs to be set to <span class="keyword">n</span>.</li> <li><b>Packets Resp Timer:</b> Please leave this as the default, which is <span class="keyword">30<span>.</li> <li><b>Sessions Connect Message Cntr:</b> Please leave this as the default, which is <span class="keyword">3<span>.</li> <li><b>SPDU Cntr:</b> Please leave this as the default, which is <span class="keyword">3<span>.</li> <li><b>Connectivity Timer:</b> Please leave this as the default, which is <span class="keyword">60<span>.</li> </ul> <p>Below you can find an example of ip-services configuration, <b>Page 3</b>:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_3.png" alt="Avaya Communications Manager" /> <h4>Configuring system-parameters cdr</h4> <p>You will need to use the <span class="reference">change system-parameters cdr</span> 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.</p> <p>Below you can find <b>Page 1</b> of system-parameters cdr configuration:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_4.png" alt="Avaya Communications Manager" /> <p><b>Page 2</b> of system-parameters cdr configuration is as shown below:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_5.png" alt="Avaya Communications Manager" /> <h4>Configuring trunk-group</h4> <p>To receive response times for incoming calls, you need to set the CDR field for each trunk group to <span class="keyword">r</span>. You will need to use the <span class="reference">change trunk-group X</span>, 'X' being the trunk group number.</p> <p>Below you can find an example of trunk-groups configuration:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_6.png" alt="Avaya Communications Manager" /> <h4>Configuring intra-switch-cdr</h4> <p>To receive internal calls CDRs you will need to populate the <span class="reference">intra-switch-cdr</span> table with the extension numbers that you want to see the internal calls for. You will need to use the <span class="reference">change intra-switch-cdr</span> command.</p> <p>Below you can find an example of the intra-switch-cdr configuration:</p> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_7.png" alt="Avaya Communications Manager" /> <h4>Configuring multiple Avaya Communications Managers</h4> <p>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:</p> <ul> <li><h6>Avaya Communications Manager - LSPs (Local Survivable Processors)</h6> If all of your Avaya Communications Managers are connected and the remote sites are 'LSPs' then you only need to configure the <span class="reference">Master/Primary</span> Avaya Communications Manager. When TIM Enterprise receives the CDR information, it will include all of the CDRs from the remote LSPs. </li> <li><h6>Avaya Communications Manager - Not linked</h6> 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. </li> </ul> <h2>Configuring TIM Enterprise</h2> <p>Below you will find steps on how to configure TIM Enterprise to listen for SMDR data from your Avaya Communications Manager:</p> <ol> <li>Browse to TIM Enterprise as normal and login with your credentials.</li> <li>Click on the <span class="button no_margin">Directory</span> tab.</li> <li>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'.</li> <li>Left-click on it and select <span class="button no_margin">Properties</span>.</li> <li>From the <span class="button no_margin">General</span> settings tab select <span class="keyword">Avaya Communications Manager</span> from the PBX model list.</li> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_8.png" alt="Avaya Communications Manager" /> <li>In the <span class="button no_margin">Connection</span> tab select <span class="keyword">Listen for connection from PBX</span> from the <span class="reference">Connection method</span> list.</li> <li>In the <span class="reference">Port</span> field enter in <span class="keyword">9000</span>.</li> <li>Enable the field <span class="keyword">Timestamp data</span>.</li> <li>Finally, click on the <span class="button no_margin">Save</span> button.</li> <img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_communications_manager_9.png" alt="Avaya Communications Manager" /> </ol> |