Avaya Solution & Interoperability Test Lab Application Notes for Oak Telecom ProVoice Enterprise Trunk Side Call Recorder with Avaya Communication Manager Issue 1.0 Abstract These Application Notes describe the configuration steps required for Oak Telecom ProVoice Enterprise trunk side call recorder to successfully interoperate with Avaya Communication Manager using Integrated Services Digital Network (ISDN) Q.931 signaling. Information in these Application Notes has been obtained through DeveloperConnection compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab. 1 of 15
MG MT FAN PSU-i PSU-E 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 R R 26 Extreme Networks Summit 200-24 25 FIBER 26 FIBER PORTS 1-24 GREEN = NON-POWERED AMBER = POWERED OK = LINK OK FLASHING = ACTIVITY OFF = NO LINK OR DISABLED ALT AMBER/GREEN = PWR FLT 25 FIBER GREEN = FIBER LINK SELECT ED OFF = 1000BASE-T LINK SELECTED STACK NO CONSOLE 1. Introduction These Application Notes describe the configuration steps required for the Oak Telecom ProVoice Enterprise trunk side call recorder to successfully interoperate with Avaya Communication Manager using ISDN Q.931 signaling. Simulated PSTN High Impedance E1 Tap Oak Telecom ProVoice Enterprise on Dell Optiplex GX280.30 Avaya C363T-PWR Converged Stackable Switch Hostname: Training-Admin Ethernet (10.1.10.x) Avaya IP Telephones C-LAN.12.61.62.63 Avaya S8500B Media Server with G650 Media Gateway.10 Extreme Summit 400 Switch 10001 10002 10003 ProVoice Enterprise records telephone calls by monitoring ISDN trunk groups. ProVoice Enterprise uses OptiLogix PCI cards to capture and process voice data. For the compliance testing, the OptiLogix PCI card was connected to an E1 trunk group by use of a high impedance tap. Integration is achieved using ISDN Q.931 messaging over the D-Channel. Q.931 events are used by ProVoice Enterprise as triggers to control recordings on the B-Channels. ProVoice Enterprise has a web interface, through which the system may be configured and maintained and through which users can search for and review recordings. 2 of 15
2. Equipment and Software Validated The following equipment and software were used for the sample configuration. Equipment Avaya S8500 Server Avaya G650 Media Gateway IPSI Board TN2312BP C-LAN Board TN799DP Medpro Board TN2302AP DS1 Interface TN2464BP Avaya 4610 IP Telephones (H.323) Avaya 4602 IP Telephones (H.323) Avaya 9620 IP Telephones (H.323) Software Avaya Communication Manager 4.0 (4.0.00.730.5) HW7 FW39 HW1 FW24 HW20 FW116 HW5 FW19 2.8 2.3 1.5 Avaya C363T-PWR Converged Stackable Switch Firmware 4.3.12 Extreme Networks Summit 400 Switch Extremeware version 7.5e.2.8 Oak Telecom ProVoice Enterprise running on Dell Optiplex GX280 PC 4.0.1 Windows XP Professional OptiLogix DX30 PCI card SW v283, FW v39 3 of 15
3. Configure Avaya Communication Manager This section provides the procedures for configuring Avaya Communication Manager. The procedures include the following areas. Verify Avaya Communication Manager license. Administer DS-1 boards and trunk groups. Save Avaya Communication Manager translations. For the compliance testing, agents with physical station extensions of 10001, 10002, 10003 were used. 3.1. Verify Avaya Communication Manager License Use the display system-parameters customer-options command to verify that the ISDN-PRI customer option is set to y on Page 4. change system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Internet Protocol (IP) PNC? n Enhanced Conferencing? y ISDN Feature Plus? n Enhanced EC500? y ISDN Network Call Redirection? n Enterprise Survivable Server? n ISDN-BRI Trunks? n Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? n Local Survivable Processor? n Extended Cvg/Fwd Admin? y Malicious Call Trace? y External Device Alarm Admin? n Media Encryption Over IP? y Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? n Multifrequency Signaling? y Global Call Classification? y Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? n Hospitality (G3V3 Enhancements)? n Multimedia Call Handling (Enhanced)? n IP Trunks? y IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.) 4 of 15
3.2. Administer DS-1 Boards and Trunk Groups Use the add ds1 x command, where x is the slot number where the DS-1 board is inserted. Configure the fields as follows. Name: Enter a descriptive name. Bit Rate: 2.048 Line Coding: hdb3 Signaling Mode: isdn-pri Connect: network Country Protocol: etsi Protocol Version: b Interface Companding: alaw add ds1 01a12 Page 1 of 1 DS1 CIRCUIT PACK Location: 01A12 Bit Rate: 2.048 Name: External Line Coding: hdb3 Signaling Mode: isdn-pri Connect: network TN-C7 Long Timers? n Country Protocol: etsi Interworking Message: PROGress Protocol Version: b Interface Companding: alaw CRC? y Idle Code: 01010100 DCP/Analog Bearer Capability: 3.1kHz T303 Timer(sec): 4 Slip Detection? n Near-end CSU Type: other Use the add trunk-group x command, where x is an available trunk group number. Configure the fields on Page 1 as follows. Group Type: isdn Group Name: Enter a descriptive name. TAC: Enter a valid trunk access code. Carrier Medium: PRI/BRI Service Type: public-ntwrk add trunk-group 19 Page 1 of 21 TRUNK GROUP Group Number: 19 Group Type: isdn CDR Reports: y Group Name: PRI to BT COR: 1 TN: 1 TAC: 719 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: public-ntwrk Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 5 of 15
Use the add signaling-group x command, where x is an available signaling group number. Configure the fields on Page 1 as follows. Group Type: isdn-pri Primary D-Channel: Enter x16, where x is the slot number of the DS-1 board. Trunk Group for Channel Selection: Enter one of the trunk groups that will be configured on the DS-1 this signaling group serves. add signaling-group 19 Page 1 of 5 SIGNALING GROUP Group Number: 19 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 01A1216 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 19 X-Mobility/Wireless Type: NONE TSC Supplementary Service Protocol: a The final step is to assign the DS-1 ports to the trunk group. Use the change trunk-group x command, where x is the number of the trunk group to be configured. On Page 5, assign ports 1-31, omitting port 16. The value in the Sig Grp column should match the signaling group added in the previous step. change trunk-group 19 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/30 GROUP MEMBER ASSIGNMENTS Total Administered Members: 30 Port Code Sfx Name Night Sig Grp 1: 01A1201 TN2464 C 19 2: 01A1202 TN2464 C 19 3: 01A1203 TN2464 C 19 4: 01A1204 TN2464 C 19 5: 01A1205 TN2464 C 19 3.3. Save Avaya Communication Manager Translations Use the command save translation to make the changes permanent. Verify that Command Completion Status shows Success and Error Code shows 0. save translation SAVE TRANSLATION Command Completion Status Error Code Success 0 6 of 15
4. Configure ProVoice Enterprise After installation, ProVoice Enterprise automatically discovers the OptiLogix voice processing card and is ready to begin recording with no extra configuration necessary. This section shows how to verify that the discovery of the OptiLogix card has been successful. Installation instructions can be found in the ProVoice Enterprise Administrator Guide, see Section 9. Open a browser window and enter the address http://x.x.x.x:20080/, where x.x.x.x is the IP address of the ProVoice Enterprise system. Enter the user name and password in the Connect to dialog box and select OK. 7 of 15
At the SmartApplications menu, select Configuration. From the Configuration pane, expand Equipment > ProVoice [hostname] (PV), where hostname is the host name of the ProVoice Enterprise system. 8 of 15
From the PV pane, select the Hardware tab. Verify the information in the following fields. Board: Primary rate trunk (PCI) No. of channels: 32 9 of 15
5. Interoperability Compliance Testing The interoperability compliance test included feature, performance and serviceability testing. The feature testing focused on the ability of ProVoice Enterprise to record calls to and from internal and external telephones and replay the voice recordings correctly. The performance testing involved generating traffic over an E1 trunk to 30 simulated IP stations over a four hour period, achieving a Busy Hour Call Completion (BHCC) rate of approximately 3000. After the test period the ProVoice Enterprise was checked to ensure that all calls were completely recorded, and with sufficient quality. The serviceability testing focused on verifying ProVoice Enterprise s ability to recover from an outage condition, such as disconnecting the E1 trunk group and disconnecting the Ethernet cable for the IP phones. 5.1. General Test Approach All feature and serviceability test cases were performed manually. For feature testing, basic telephony operations such as answer, hold/retrieve, transfer, and conference were exercised on inbound and outbound calls as well between internal calls. For serviceability testing, calls were placed before, during and after the outages and the recordings checked for accuracy. For performance testing, a call generator placed inbound calls over an E1 trunk to 30 simulated IP stations over a four hour period. 5.2. Test Results All tests passed successfully. 10 of 15
6. Verification Steps This section provides the tests that can be performed to verify proper configuration of Avaya Communication Manager and ProVoice Enterprise. 6.1. Verify Avaya Communication Manager Verify the status of the trunk group by using the status trunk x command, where x is the trunk group created in Section 3. The Service State should show in-service/idle. status trunk 19 Page 1 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0019/001 01A1201 in-service/idle no 0019/002 01A1202 in-service/idle no 0019/003 01A1203 in-service/idle no 0019/004 01A1204 in-service/idle no 0019/005 01A1205 in-service/idle no 0019/006 01A1206 in-service/idle no 11 of 15
6.2. Verify ProVoice Enterprise The following steps can be used to verify that the ProVoice Enterprise system has been configured correctly and that calls can be recorded. First, place an inbound call over a trunk that is being recorded. Then place an outbound call over a trunk that is being recorded. For both calls, speak into both telephones involved in the call and then hang up. From the SmartApplications menu, shown in Section 4, select Search for calls. On the Search for calls screen, select Search. 12 of 15
On the Search results screen, the two test calls should be displayed. Verify the number dialed in the Called column. The direction of the call is shown in the Direction column. To play the calls click on the loudspeaker icon. 13 of 15
7. Support Technical support on ProVoice Enterprise can be obtained through the following: +44 (0)870 20 20 247 support@oak.co.uk 8. Conclusion These Application Notes describe the configuration steps required for the interoperability of Oak Telecom ProVoice Enterprise trunk side call recorder with Avaya Communication Manager using ISDN Q.931 signaling. All feature, performance and serviceability test cases were completed and passed. 9. Additional References This section references the product documentation relevant to these Application Notes. Documentation for Avaya Communication Manager (4.0), Media Gateways and Servers, Document ID 03-300151, Issue 6, February 2007, available at: http://support.avaya.com. ProVoice Enterprise User Guide and ProVoice Enterprise Administrator Guide, both available at: http://help.oak.co.uk/provoice%20enterprise/online%20help/index.html 14 of 15
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 e-mail 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 DeveloperConnection Program at devconnect@avaya.com. 15 of 15