Application Notes for Configuring Avaya Aura Communication Manager R6.2 with Tri-Line TIM Plus using TCP - Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Avaya Aura Communication Manager R6.2 with Tri-Line TIM Plus using TCP - Issue 1.0 Abstract These Application Notes describe the configuration steps for provisioning Avaya Aura Communication Manager R6.2 with Tri-Line TIM Plus Tri-Line TIM Plus will collect Call Detailed Records by listening to a TCP port configured on Avaya Aura Communication Manager Information in these Application Notes has been obtained through DevConnect Compliance Testing and additional technical discussions. Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 1 of 15

2 1. Introduction Tri-Line TIM Plus is a call logger which runs as a Windows Service and all of its functions, configuration, and call reports are accessible through any standard web browser. Tri-Line TIM Plus collects Call Detailed Record (CDR) data from Avaya Aura Communication Manager by listening for connections on a specific TCP port and it uses a native SQL database for storing and processing data. Tri-Line TIM Plus provides a web interface which can be used for configuration with Avaya Aura Communication Manager. The web interface also allows the system to be updated for additional Avaya Aura Communication Managers and for general maintenance. Users can use this web interface for reporting purposes and access can be restricted by username and password and directory position. 2. General Test Approach and Test Results The interoperability compliance test included both feature and functionality testing. The feature and functionality testing focused on verifying that Call Detailed Records are collected by TIM Plus and received in the format as generated by Communication Manager. The TIM Plus Call Logger collects CDR data by listening on a TCP port configured on Communication Manager. DevConnect Compliance Testing is conducted jointly by Avaya and DevConnect members. The jointly-defined test plan focuses on exercising APIs and/or standards-based interfaces pertinent to the interoperability of the tested products and their functionalities. DevConnect Compliance Testing is not intended to substitute full product performance or feature testing performed by DevConnect members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member s solution Interoperability Compliance Testing The testing included: Verification of connectivity between TIM Plus and Communication Manager using a TCP connection. Verification that Call Detailed Records (CDR) was collected as output by Communication Manager. Link Failure\Recovery was also tested to ensure successful reconnection on link failure Test Results Tests were performed to insure full interoperability between TIM Plus and Communication Manager. The tests were all functional in nature and performance testing was not included. All test cases passed successfully. There are some differences in Communication Manager in the call records generated by SIP endpoints compared to Analog, Digital, and H.323 endpoints. As a result in certain scenarios involving SIP endpoints (e.g., two-party call, transfer, or conference), a CDR application may see more or less records, or records with condition codes/calling party other than expected. Avaya is investigating the differences and code changes may be made available in a future release pending the outcome of that investigation. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 2 of 15

3 2.3. Support Technical support can be obtained for TRI-Line products as follows: Web Portal Telephone +44 (0) Reference Configuration Figure 1 illustrates the network diagram of the configuration used during compliance testing. Communication Manager is configured to output CDR data using a non- Reliable Session Protocol (RSP) CDR link. CDR data is sent via IP to the Tri-Line TIM Plus server on a designated TCP port. The CDR format is customized. The Tri-Line TIM Plus Call Logger is connected on the same LAN as Communication Manager and will collect CDR records. Figure 1: Avaya Aura Communication Manager R6.2 with Tri-Line TIM Plus Reference Configuration CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 3 of 15

4 4. Equipment and Software Validated The hardware and associated software used in the compliance testing is listed below. Avaya Equipment Software / Firmware Version Avaya S8800 Server Avaya Aura Communication Manager R6.2 Build R016x Avaya S8800 Server Avaya Aura System Manager R6.2 Build Avaya S8800 Server Avaya Aura Session Manager R6.2 Build Avaya G250 Media Gateway Avaya 96xx Deskphones - H S3.186a - H G S3.105s - SIP9611G SIP9621G Avaya One-X communicator Tri-Line Equipment Software Version TIM Plus running on a Dell Latitude Version E5400 with Windows 7 Professional SP1 5. Avaya Aura Communication Manager Configuration Configuration and verification operations on Communication Manager illustrated in this section were all performed using Avaya Site Administrator Emulation Mode. The information provided in this section describes the configuration of Communication Manager for this solution. It is implied a working system is already in place. For all other provisioning information such as initial installation and configuration, please refer to the product documentation in Section 9. The configuration described in this section can be summarized as follows: Create Node Name for TIM Plus Call Logger Define the CDR link Change system-parameters cdr Change Trunk Group Change Intra- Switch-CDR Note: Any settings not in Bold in the following screen shots may be left as Default. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 4 of 15

5 5.1. Create Node Name for Tri-Line TIM Plus Call Logger A Node Name needs to be created to associate the TIM Plus Call Logger with Communication Manager. Use the change node-names ip command to configure the following: Name Enter an informative name i.e. TIMPro IP address Enter the IP address of the TIM Plus Call Logger Press F3 button to save the new settings. change node-names ip Page 1 of 2 IP NODE NAMES Name IP Address TIMPro CLAN procr Define the CDR link A CDR link needs to be defined between Communication Manager and TIM Plus. Use the change ip-services command to configure the following: Service Type Enter CDR1 Local Node Enter CLAN Remote Node Enter TIMPro Remote Port Enter 9000 change ip-services Page 1 of 3 IP SERVICES Service Enabled Local Local Remote Remote Type Node Port Node Port CDR1 CLAN 0 TIMPro 9000 Navigate to Page 3 and set the Reliable Protocol field to n. This will disable Reliable Session Protocol (RSP) for CDR transmission. In this case, the CDR link will use TCP without RSP. Reliable Protocol Enter n Press F3 button to save the new settings. change ip-services Page 3 of 3 SESSION LAYER TIMERS Service Reliable Packet Resp Session Connect SPDU Connectivity Type Protocol Timer Message Cntr Cntr Timer CDR1 n CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 5 of 15

6 5.3. Change system-parameters cdr Certain parameter changes are required for Communication Manager to interoperate with TIM Plus. The screen shots below show the settings used during compliance testing. Use the change system-parameters cdr command to configure the following: CDR Date Format Enter day/month Primary Output Format Enter customized Primary Output Endpoint Enter CDR1 Record Outgoing Calls Only Enter n Intra-Switch CDR Enter y Outg Trk Call Splitting Enter y Inc Trk Call Splitting Enter y change system-parameters cdr Page 1 of 2 CDR SYSTEM PARAMETERS Node Number (Local PBX ID): CDR Date Format: day/month Primary Output Format: customized Primary Output Endpoint: CDR1 Secondary Output Format: Use ISDN Layouts? n Enable CDR Storage on Disk? n Use Enhanced Formats? n Condition Code 'T' For Redirected Calls? n Use Legacy CDR Formats? y Remove # From Called Number? n Modified Circuit ID Display? n Intra-switch CDR? y Record Outgoing Calls Only? n Outg Trk Call Splitting? y Suppress CDR for Ineffective Call Attempts? y Outg Attd Call Record? y Disconnect Information in Place of FRL? n Interworking Feat-flag? n Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n Calls to Hunt Group - Record: member-ext Record Called Vector Directory Number Instead of Group or Member? n Record Agent ID on Incoming? n Record Agent ID on Outgoing? y Inc Trk Call Splitting? y Inc Attd Call Record? n Record Non-Call-Assoc TSC? n Call Record Handling Option: warning Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed Privacy - Digits to Hide: 0 CDR Account Code Length: 4 CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 6 of 15

7 Navigate to Page 2 and enter the following information. Enter Data Item and Length as shown in the screen below Press F3 button to save the new settings. change system-parameters cdr Page 2 of 2 CDR SYSTEM PARAMETERS Data Item Length Data Item Length Data Item - Length 1: date : dialed-num : auth-code : space : space : return - 1 3: time : in-trk-code : line-feed - 1 4: space : space : - 5: sec-dur : in-crt-id : - 6: space : space : - 7: cond-code : calling-numbe : - 8: space : space : - 9: attd-console : vdn : - 10: space : space : - 11: code-used : bcc : - 12: space : space : - 13: out-crt-id : ppm : - 14: space : space : - 15: code-dial : acct-code : - 16: space : space : - Record length = Change Trunk Group To collect call data on Trunks, CDR Reports need to be set. Trunk Group 9 was used for the compliance test. Use the change trunk-group 9 command to configure the following: CDR Reports Enter r Press F3 button to save the new settings. change trunk-group 9 Page 1 of 21 TRUNK GROUP Group Number: 7 Group Type: isdn CDR Reports: r Group Name: ISDN to CS1K COR: 1 TN: 1 TAC: *19 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 7 of 15

8 5.5. Change Intra-Switch-CDR Internal CDR is activated on a per set basis. When the Intra-switch CDR field is set to y in the CDR System Parameters form, the extensions that will be subject to CDR need to be defined. During compliance testing, extensions 2010, 2011, 2012 and 2022 were used. Use the change intra-switch-cdr command to define the extensions that will be subject to call detail records. Configure the following: Extension Press F3 button to save the new settings. Enter the extensions that will be subject to CDR. Note: To simplify the process of adding multiple extensions in the Assigned Members field, the Intra-switch CDR by COS (SA8202) feature may be utilized in the SPECIAL APPLICATIONS form under the system-parameters section. To utilize this feature, contact an authorized Avaya account representative to obtain the license. change intra-switch-cdr Page 1 of 3 INTRA-SWITCH CDR Assigned Members: 4 of 5000 administered Extension Extension Extension Extension Configuring Tri-Line TIM Plus A number of steps are required to configure TIM Plus to interoperate with Communication Manager. The TIM Plus Call Logger uses a TCP port to collect CDR data from Communication Manager. The TIM Plus application requires a template file which matches the PBX type during configuration. Both TIM Plus application and template file can be downloaded from the Tri-Line Web Site once the end customer has a registered account. The configuration of the TIM Plus Call Logger is achieved during the initial installation. An installation wizard is used whereby certain steps require specific information relating to the TIM Plus configuration. The configuration described in this section can be summarized as follows: Downloading the Communication Manager template. Configure Site information Create an administrator account Logging into TIM Plus Call logger Access to TIM Plus 6.1. Downloading Avaya Aura Communication Manager Template As part of configuration an Avaya Communication Manager template is required. This template is provided as standard with the installation package. During compliance testing the template used was called Avaya Communication Manager.tdt. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 8 of 15

9 6.2. Configure Site information Start the installation wizard after the TIM Plus application has been downloaded. Follow the wizard steps until step 5. The PBX model used is a template which was downloaded as described in Section 6.1. The following information is required for the initial site setup: Site name Enter an informative name, i.e. Test Site PBX model Choose Avaya Communication Manager from the dropdown box. Method Choose Listen for connection from PBX from the dropdown box. Port Enter 9000 Note this is the Remote Port as configured in Section 5.2 Click on the Next button to continue CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 9 of 15

10 6.3. Create an administrator account Once the wizard has progressed to step 8, an administrator account must be created. This account allows web users to log into the TIM Plus Call Logger. The following information is required to create the administrator account: Display name Enter an informative name, i.e. Tri-Line Support UserName Enter a User name, i.e. admin Password Enter a password. Click on the Finish button to continue. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 10 of 15

11 6.4. Logging into the Tri-Line TIM Plus Call Logger Once the administrator account is created, the user is prompted to log in. Log into the TIM Plus Call logger by entering the User name and Password as created in Section 6.3. Click the OK button to log in. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 11 of 15

12 6.5. Access to Tri-Line TIM Plus A web browser is required to view the call record. During compliance testing, the web browser and TIM Plus service were installed on the same PC. The loopback address was used. Note: The User name and Password as created in Section 6.3 is required for log in. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 12 of 15

13 7. Verification Steps This section provides a set of tests that can be performed to verify correct configuration of Communication Manager and TIM Plus Verify the Avaya Aura Communication Manager CDR Link Use the status cdr-link command to verify that the Link State is up and the Reason Code is OK. status cdr-link CDR LINK STATUS Primary Secondary Link State: up CDR administered Number of Retries: 999 Date & Time: 2011/12/15 17:32: /00/00 00:00:00 Forward Seq. No: 0 0 Backward Seq. No: 0 0 CDR Buffer % Full: Reason Code: OK 7.2. Verify that Tri-Line TIM Plus Call Logger retrieves CDR data To ensure that TIM Plus Call Logger is retrieving CDR data, make some calls on Communication Manager. Verify that something similar to the following is presented. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 13 of 15

14 8. Conclusion These Application Notes describe the configuration steps required for Avaya Aura Communication Manager R6.2 to successfully interoperate with Tri-Line TIM Plus using a TCP connection. Tri-Line TIM Plus is considered compliant with Avaya Aura Communication Manager R6.2. All test cases have passed and met the objectives outlined in Section Additional References This section references Avaya and Tri-Line documentation that is relevant to these Application Notes. Product documentation for Avaya products is available at [1] Installing and Configuring Avaya Aura System Platform Release 6.2, June [2] Administering Avaya Aura System Platform Release 6.2, June [3] Administering Avaya Aura Communication Manager, Release 6.2, April 2013 [4] Avaya Aura Communication Manager Feature Description and Implementation, April [5] Implementing Avaya Aura System Manager Release 6.2, July [6] Implementing Avaya Aura Session Manager, March Product Documentation for Tri-Line can be obtained at Login required. CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 14 of 15

15 2013 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya DevConnect Program at CMN; Reviewed Solution & Interoperability Test Lab Application Notes Page 15 of 15