Application Notes for configuring Avaya Aura Communication Manager R6.2 with Pridis Florin Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for configuring Avaya Aura Communication Manager R6.2 with Pridis Florin Issue 1.0 Abstract These Application Notes describe the compliance testing done with Avaya Communication Manager and Pridis Florin. Pridis Florin collects Call Detail Records (CDRs) from Avaya Communication Manager and creates telephone usage reports. 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. 1 of 23

2 1. Introduction Pridis Florin is a PC or server-based application, which collects and evaluates Call Detail Records (CDRs) from Avaya Aura Communication Manager via an IP network. Pridis Florin can generate reports containing statistics on the usage resources, such as trunks and individual stations. 2. General Test Approach and Test Results The general test approach was to manually place intra-switch calls, inter-switch IP Trunk calls, inbound and outbound PSTN trunk calls to and from telephones on Avaya Aura Communication Manager Systems, and verify that Florin collects the CDR and reports the correct attributes of the call 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 Interoperability compliance testing consisted of successful and accurate collection of CDR date from Communication Manager as well as recovery from failure in the following scenarios: H.323 and SIP intra and inter-switch calls Calls over simulated PSTN Tandem Calls Use of Account Codes Use of Authorization Codes Routing calls using AAR, ARS and Trunk Access codes Use of bridged appearances Hunt group calls Supervised and un-supervised transfers Trunk to trunk calls Verification of condition codes Recovery from network and power outage 2 of 23

3 2.2. Test Results All test cases passed successfully with the following observations, all of which are a result of the configuration of SIP endpoints based on the OPTIM OPS application: Where an intra-switch call is placed from and H.323 or SIP endpoint to a SIP endpoint the call direction is reported as inbound. Where an outbound inter-switch call is placed from a SIP endpoint over an H.323 trunk using the AAR FAC, 2 call legs are reported of the same duration. One to the H.323 TAC and another to the actual called party. Where an outbound inter-switch call is placed from a SIP endpoint over an H.323 trunk using the TAC, only a call to the TAC is recorded, the called party is not shown. Where an outbound call is placed over PSTN from a SIP endpoint using ARS, 2 call records are created. One as outbound with the correct originating and destination information, and another as an inbound call from the CLI of the SIP endpoint to the TAC of the PSTN trunk. Where account-code is enabled on the system-cdr and a SIP endpoint places an outbound call where no account code is required, an account code of is reported for both the inbound and outbound leg of the SIP call. Where SIP endpoint A is forwarded to SIP endpoint B, and an H.323 endpoint places an intra-switch call to SIP endpoint A, it is reported as an inbound call. Where an inbound inter-switch call is made to SIP endpoint A which then performs a consultative transfer to SIP endpoint B, only the consultation leg between SIP endpoint A and SIP endpoint B is reported. Where an inbound PSTN call is placed to SIP endpoint A, and a consultative inter-switch transfer is made by SIP endpoint A, the leg from PSTN to SIP endpoint A is not reported, the consultative leg is reported as SIP endpoint A to the TAC of the inter-switch trunk, and the transferred leg reported as SIP endpoint A to the inter-switch destination. Where an inbound PSTN call is placed to SIP endpoint A, and a blind inter-switch transfer is made by SIP endpoint A, the transfer leg is not reported. Where an outbound PSTN call is made by SIP endpoint A, and SIP endpoint A then performs a blind inter-switch transfer, the leg from SIP endpoint A to PSTN is not reported, the call from SIP endpoint A to the inter-switch destination is shown as the full call duration. Additionally there are 2 calls to the TAC, one of which is 0 seconds in duration and the other the duration of the call from SIP endpoint A to the PSTN, which is not charged. Note: 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. 3 of 23

4 2.3. Support Support for Florin is available at. info: 3. Reference Configuration An Avaya S8800 Server running Avaya Aura Communication Manager R6.2 serving H.323 endpoints with an Avaya G450 Media Gateway was configured along with Avaya Aura Session Manager R6.2 hosted on an Avaya S8800 Server providing SIP endpoints. A second Avaya Aura Communication Manager PBX was configured to provide H.323 trunks as a networked PBX and a QSIG PRI trunk. Pridis Florin was hosted on a Windows server and was configured to collect the CDR output from Avaya Aura Communication Manager over the IP Network. Avaya Aura Communication Manager, Avaya Aura Session Manager and Avaya Modular Messaging with Pridis Florin Solution 4 of 23

5 4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment/Software Release/Version Avaya Aura Communication Manager R6.2 SP5 build R016x running on Avaya S8800 Server Avaya Aura Session Manager running on R6.2 SP3 Avaya S8800 Server Avaya Aura System Manager running on R6.2 SP4 Avaya S8800 Server Avaya Modular Messaging running on 5.2 Patch 8 S3500 Server pair MAS Avaya G450 Media Gateway MM710 HW5 FW22 Avaya 9630 IP Deskphone H S SIP Avaya 2420 Digital Deskphone 2420 Rel 6.00 HWT=51H HWV=1 FWV=6 Pridis Florin running on generic hardware Version: and Windows Server 2008 R2 OS. 5. Configure Avaya Aura Communication Manager The configuration and verification operations illustrated in this section were all performed using the Communication Manager System Administration Terminal (SAT). It is assumed that the relevant dialplan, hunt groups, stations, trunks and call routing have been configured. The connection from Communication Manager to Session Manager is not specific to the test environment and is therefore not detailed below. The information provided in this section describes the configuration of Communication Manager for this solution. For all other provisioning information such as installation and configuration, please refer to the product documentation in Section 9. 5 of 23

6 5.1. Configure Node-Names The IP address of Florin must be configured on Communication Manager. Enter the command change node-names ip and assign a Name and IP Address for the server hosting Florin as shown below. Also note the procr IP address. change node-names ip Page 1 of 2 IP NODE NAMES Name IP Address default Florin gateway procr procr6 :: 5.2. Configure IP-Services The connection information and port must be configured to establish the output of CDR by Communication Manager. Enter the command change ip-services and configure as follows: Service Type set to CDR1 Local Node set to the procr node name Remote Node set to the node name assigned to the Florin server, in this case Florin Remote Port set to the Port which will be used by Florin to listen for CDR data, in this case 9001 change ip-services Page 1 of 4 IP SERVICES Service Enabled Local Local Remote Remote Type Node Port Node Port CDR1 procr 0 Florin 9001 On Page 3 ensure the Service Type CDR1 has Reliable Protocol set to n. change ip-services Page 3 of 4 SESSION LAYER TIMERS Service Reliable Packet Resp Session Connect SPDU Connectivity Type Protocol Timer Message Cntr Cntr Timer CDR1 n of 23

7 5.3. Configure System-Parameters CDR The CDR information to be sent by Communication Manager and the format in which it will be sent must be configured. Enter the command change system-parameters cdr and configure the following: CDR Date Format set to day/month Primary Output Format set to customized Primary Output Endpoint set to CDR1 Enable CDR Storage on Disk set to y Use Legacy CDR Formats set to n Intra-switch CDR set to y Inc Trk Call Splitting set to 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? y Use Enhanced Formats? n Condition Code 'T' For Redirected Calls? n Use Legacy CDR Formats? n 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: group-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: 5 7 of 23

8 On Page 2 configure the output format as shown below. change system-parameters cdr Page 2 of 2 CDR SYSTEM PARAMETERS Data Item - Length Data Item - Length Data Item - Length 1: date : - 33: - 2: time : - 34: - 3: sec-dur : - 35: - 4: cond-code : - 36: - 5: dialed-num : - 37: - 6: calling-num : - 38: - 7: in-trk-code : - 39: - 8: code-used : - 40: - 9: duration : - 41: - 10: in-crt-id : - 42: - 11: vdn : - 43: - 12: return : - 44: - 13: - 29: - 45: - 14: - 30: - 46: - 15: - 31: - 47: - 16: - 32: - 48: - Record length = Configure Intra-Switch-CDR Calls between internal extensions whose records should be output to CDR must be configured. Enter the command change intra-switch-cdr under the Extension column enter those extensions whose call records must be captured. change intra-switch-cdr Page 1 of 3 INTRA-SWITCH CDR Assigned Members: 5 of 5000 administered Extension Extension Extension Extension of 23

9 5.5. Configure Off-Station-PBX Configuration Set Because the Avaya SIP endpoints are administered as off-pbx-telephone stations, the configuration-set used by the SIP endpoints should be changed. Enter the command change offpbx-telephone configuration set 1 and set the value of CDR for Calls to EC500 Destination to n. where 1 is the default configuration-set assigned to the SIP EC500 stations. change pbx-telephone configuration-set 1 Page 1 of 1 CONFIGURATION SET: 1 Configuration Set Description: Calling Number Style: network CDR for Origination: phone-number CDR for Calls to EC500 Destination? n Fast Connect on Origination? n Post Connect Dialing Options: dtmf Cellular Voice Mail Detection: timed (seconds): 4 Barge-in Tone? n Calling Number Verification? y Call Appearance Selection for Origination: primary-first Confirmed Answer? n Use Shared Voice Connections for Second Call Answered? n Use Shared Voice Connections for Second Call Initiated? n 5.6. Configure Trunk CDR The Application Notes assume that the trunks between Communication Manager and Session Manager, the networked PBX and the PSTN are preconfigured. Enter the command change trunk x where x is the relevant trunk number to Session Manager, the Networked PBX or the PSTN and set the CDR Reports field to r. change trunk-group 1 Page 1 of 21 TRUNK GROUP Group Number: 1 Group Type: sip CDR Reports: r Group Name: TRUNK TO SM62 COR: 1 TN: 1 TAC: 701 Direction: two-way Outgoing Display? y Dial Access? n Night Service: Queue Length: 0 Service Type: public-ntwrk Auth Code? n Member Assignment Method: auto Signaling Group: 1 Number of Members: 30 9 of 23

10 6. Configure Pridis Florin The Application Notes assume that the Florin Application has been installed and licensed. From the Florin server open the System Administration Tool located in the Windows Start Menu. The following screen will appear, enter the appropriate credentials and click Login. 10 of 23

11 6.1. Add PABX Click Windows Infrastructure Manager (not shown) and choose Edit Add PABX 11 of 23

12 Select the newly added PABX and assign an identifying Name 6.2. Add Network Click Networks Edit Add network Select the newly added network and assign an identifying Name. 12 of 23

13 6.3. Add Tariff File A previously configured tariff file is used to define the charging tariff according to the call type. Select Tariffs File Add Tarifftable from XML and select the appropriate tariff file. Select the previously configured Network and configure the AssignedTariff accordingly. 13 of 23

14 6.4. Configure Monitor With the Infrastructure Manager in the System Administration Tool multiple PBXs can be configured where for example a company may be divided into several locations and each location can contain one or more PBX. For all connection types the Monitor Configurator needs to be started and a PABX must have been added in the System Administration Tool. From the Florin server start the Monitor Configurator located in the Windows Start menu. 14 of 23

15 Expand the Monitor Configuration and Location, select the PABX to configure and click on Edit 15 of 23

16 The screen below will appear, configure as follows: PABX Name enter an identifying name PABX Type select Definity from the drop down box Active place a check in this box Timezone set accordingly PABX Directory enter the patch where Florin is installed Link select LAN Max ext. digits configure with the maximum internal extension number length, in this case 5. All extensions with more digits will be considered as external numbers Digits to hide configure accordingly to mask the last x digits of the dialed number. This is a privacy option. This way the dialed number will be stored in the Florin database with the last x digits masked. It is also possible to mask digits in the reports whilst storing the complete number in the database. Click Setup when done. 16 of 23

17 The screen below will appear, configure as follows, click OK when done: Type set to TCP Server Servername enter the procr IP Address Port configure as 9001 as shown in Section of 23

18 6.5. Import Organisation Data In Florin there is an organization tree available. When a call is delivered by CDR, the record will be matched with the extension in the organization tree. To view and edit the Organization Tree click System Administration (not shown) Organization Tree. To add a user to the Organization Tree click Add User. Click New User 18 of 23

19 The following screen will appear, complete accordingly and click Save and Close (not shown). 19 of 23

20 To add an asset (extension) to a user, select the appropriate user and click Add Asset (not shown), the following screen will appear. The Available Assets pane will show those items which have been recorded in the CDR data which are as yet unassigned to any asset. These are also known as unassigned items. Select the appropriate available asset and click Add to List. Click Save and Close when done. Repeat this process for all available assets and corresponding users. 20 of 23

21 7. Verification Steps The following steps may be used to verify the configuration 7.1. Verify Avaya Aura Communication Manager CDR Link Status On the SAT, enter the status cdr-link command to verify that the Primary CDR Link State is up. status cdr-link Primary CDR LINK STATUS Secondary Link State: up CDR not administered Date & Time: 2012/12/01 16:24: /00/00 00:00:00 Forward Seq. No: 0 0 Backward Seq. No: 0 0 CDR Buffer % Full: Reason Code: OK 7.2. Verify Florin is Receiving CDR Place a call and using the Florin web interface run a report to verify that the Florin report shows the call with the correct call related information. Click Personal details Dashboard (not shown). Check if the widget, recent calls shows the call and if the widget CDR status has the proper date. 21 of 23

22 8. Conclusion These Application Notes describe the required configuration steps for Avaya Aura Communication Manager and Pridis Florin to collect Call Detail Records from Avaya Aura Communication Manager. All test cases completed successfully with the observations and exceptions noted in Section Additional References This section references the product documentations that are relevant to these Application Notes. Avaya product documentation can be found at Administering Avaya Aura Communication Manager, Release 6.2, , Issue 7.0 December of 23

23 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 23 of 23