Application Notes for Invision Interaction Recording System Version 5.0 with Avaya Aura Communication Manager Release 6.3 Issue 1.

Avaya Solution & Interoperability Test Lab Application Notes for Invision Interaction Recording System Version 5.0 with Avaya Aura Communication Manager Release 6.3 Issue 1.0 Abstract These Application Notes describe the configuration steps required for Invision Interaction Recording System (I-Record) Version 5.0 to interoperate with Avaya Aura Communication Manager Release 6.3. Invision I-Record captures Avaya 9600 series H323 Deskphones and 1600 Series H.323 Deskphones voice conversation and presents the recordings in a report accessible via web. Readers should pay attention to section 2, in particular the scope of testing as outlined in Section 2.1 as well as the observations noted in Section 2.2, to ensure that their own use cases are adequately covered by this scope and results. 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 22

1. Introduction These Application Notes describe the configuration steps required for Invision Interaction Recording System (I-Record) Version 5.0 to interoperate with Avaya Aura Communication Manager Release 6.3. Invision I-Record (hereafter refer to as I-Record) captures Avaya 9600 series H323 Deskphones and 1600 Series H.323 Deskphones voice conversation by receiving network traffic from mirroring the ports of these H.323 IP endpoints in Managed Ethernet Switches. In our compliance test, Avaya Managed Ethernet Switch is used for testing. 2. General Test Approach and Test Results The feature test cases were performed manually. Each call was handled manually at the user with generation of unique audio content for the recordings. Necessary user actions such as hold and reconnect, call park and unpark, transfer and conference were performed from the user telephone to test the various call scenarios. The serviceability test cases were performed manually by disconnecting and reconnecting the Ethernet cable to the server, disabling and enabling the database. 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. 2 of 22

2.1. Interoperability Compliance Testing The interoperability compliance test included feature and serviceability testing. The feature testing focused on verifying the following from I-Record: Handling, reporting, and playback of call recording for various call scenarios including internal, external, inbound, outbound, drop, hold/reconnect, blind/attended transfer, blind/attended conference, hunt group, park/unpark simultaneous users, simultaneous calls and outbound calls which require authorization codes. The serviceability testing focused on verifying the ability of I-Record to recover from adverse conditions, such as disconnecting and reconnecting the Ethernet cable and disabling the database. 2.2. Test Results All test cases were executed and verified. The following were observations on I-Record from the compliance testing. Direct IP to IP Audio Connections need to be turned off for IP stations in order to record internal calls as well. Disconnecting and reconnecting of Ethernet cable to the server requires to restart the services manually for call recording to work again. 2.3. Support Technical support on I-Record can be obtained through the following: Phone: +62-81-1101109 Web: support@invision-ap.com 3 of 22

3. Reference Configuration The configuration used for the compliance testing is shown below. The setup includes a duplex pair of Communication Managers with G430 and G650 Media Gateway; 9600 and 1600 Series H.323 Deskphones and I-Record server is installed with the necessary software with two LAN connections. One of the LAN connections (highlighted) is to receive the monitored network traffic from the Avaya managed switch. Microsoft SQL Server 2008 database is also installed on the same server for testing though it is recommended to be installed on a separate server for traffic purpose. In the compliance testing, I-Record captures call recordings of users from mirroring the switch ports of the H.323 Deskphones. Figure 1: Compliance Testing Configuration 4 of 22

4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment/Software Avaya Aura Communication Manager S8800 Duplex Server Avaya G650 Media Gateway TN2312BP IP Server Interface TN799DP C-LAN Interface TN2302AP IP Media Processor TN2602AP IP Media Processor Avaya G450 Media Gateway 36.7.0 Release/Version R6.3.7 Build R016x.03.0.124.0 HW07, FW058 HW01, FW044 HW20, FW121 HW02, FW066 Avaya Ethernet Routing Switch 5520-48T-PWR Hardware 36 Firmware 6.0.0.6 Software v6.2.4.010 Avaya 96x1 Series IP Deskphones (H.323) 6.4014 Avaya 96x0 Series IP Deskphones (H.323) 3.220A Avaya 16xx Series IP Deskphones (H.323) 1.360A Microsoft SQL Server running on Windows 7 Professional SP1 2008 R2 SP2 IHCUSYS running on Windows 7 Professional SP1 5.0 IMFCUSYS running on Windows 7 Professional SP1 5.0 Web Server running on Windows 7 Professional SP1 5.0 5 of 22

5. Configure Avaya Aura Communication Manager This section covers the station configuration for Avaya one-x Agent. The configuration is performed via the System Access Terminal (SAT) on Communication Manager. Administration of the IP endpoints is assumed to be in place. Enter change station 10001 command and go to page 2. Set the Direct IP-IP Audio Connections field to n. This is to disable shuffling of the IP endpoint so that traffic can be captured for internal calls between stations. change station 10001 Page 2 of 5 STATION FEATURE OPTIONS LWC Reception: spe Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: none CDR Privacy? n Data Restriction? n Redirect Notification? y Idle Appearance Preference? n Per Button Ring Control? n Bridged Idle Line Preference? n Bridged Call Alerting? y Restrict Last Appearance? y Active Station Ringing: single EMU Login Allowed? n H.320 Conversion? n Per Station CPN - Send Calling Number? Service Link Mode: as-needed EC500 State: enabled Multimedia Mode: enhanced MWI Served User Type: sip-adjunct Audible Message Waiting? n Display Client Redirection? n Select Last Used Appearance? n Coverage After Forwarding? s Multimedia Early Answer? n Remote Softphone Emergency Calls: as-on-local Direct IP-IP Audio Connections? n Emergency Location Ext: 10001 Always Use? n IP Audio Hairpinning? n 6 of 22

6. Configure Avaya Ethernet Routing Switch Avaya Managed Switch is use in this Compliance Testing. Managed switches from other brands can be used as long as port mirroring or spanning can be configured. Check the network traffic with trace tool such as Wireshark. Step Description 1. Open a web browser and access the Ethernet switch web interface at http://<ip address>/login.html. Log in with the appropriate credentials. 2. From the Home Menu, on the left panel click Configuration Edit Diagnostics Port Mirrors. Click Insert as below. 7 of 22

Step Description 3. Enter the appropriate parameters below: Instance: Leave the auto-generated instance number as default. PortMode: manytoonerxtx (all received and transmit traffic of many ports). MonitorPort: Selected port connected to the I-Record server where all the mirrored IP Endpoints network traffic is collected. PortListX: Ports list of all the IP Endpoints Allow Traffic: Uncheck this as bi-direction monitor port is not required. 8 of 22

7. Configure I-Record This section provides the procedures for configuring I-Record which include licensing. Installation of the HPXMedia and SmartWORKS software including database will be done by the member technical staff which will not be detailed here. Step Description 1. On the Windows server, navigate to Starts Menu All Programs Ai-Logix SmartWORKS SmartView. 9 of 22

Step Description 2. On the Home Menu, if Resource is in CLOSED state, select System MTSysStartup from the drop down menu and Resource will be OPENED. 3. Now, the resource is OPENED. 10 of 22

Step Description 4. Register the license by navigating to drop down menu Board MTIp(GetLicenseInfo/LoadLicense). 5. Click Browse (not shown) and navigate to where the license file (HPXxxxxxx.lic) is located and click Open. 11 of 22

Step Description 6. Click Load and verify validity of license and then click Get. 7. Copy also the license file of HPXMedia in the name format of HPXMxxxxxxxx.lic as shown below into the folder default location at Program Files\AudioCodes USA\HPXMedia. 12 of 22

Step Description 8. Go to Control Panel in Windows. Double Click to open SmartControl. 13 of 22

Step Description 9. Click on the Board tab, set Monitoring Port 0 to enable and choose the relevant adapter on the server as the port that received the monitoring port network traffic from the managed switch and click OK. 14 of 22

Step Description 10. Run the Services.msc from the Windows Start Menu and check the HPXMedia and SmartWORKS Services are started. Otherwise, start them. 15 of 22

Step Description 11. Go to where the Log folder resides for recordings and locate IMFCUSYS.exe and IHCUSYS.exe. Both executables provides the logging of I-Record. 16 of 22

Step Description 12. Open ihcusys_settings.cfg and verify the setup field with the description of the parameters below. dbserver is Server Name of SQL Server dbname is database which we was restore before dbuser is Username to login to SQL Server dbpass is Password to login to SQL Server loglevel is Level log (1 is debug, 0 is info) logtarget is destination of log file how Application is the show or hide the application (1 is show, 0 is hide) 17 of 22

Step Description 13. Open imfcu_settings.cfg and verify the setup field with the description of the parameters below and then double click the IHCUSYS.exe and IMFCUSYS.exe executable program located as in STEP 11 to start recordings. dbproduct is database we use dbserver is Server Name of SQL Server dblogin is Username to login to SQL Server dbpassword is Password to login to SQL Server dbinstance is Server Name of SQL Server logtarget is destination of log file 18 of 22

8. Verification Steps This section provides the tests to verify proper integration between Communication Manager and I-Record. Prior to verification, place an incoming trunk call to any user. Answer the call at the user, and generate unique audio content for the call prior to hanging up. Access the I-Record Login web-based interface below from the server. The Login screen is displayed as shown below. Log in using the appropriate admin credentials. 19 of 22

The screen below is displayed current records of voice capture in the Home Menu. Click on the rows which display the call. The following display the recorded conversation and can be played back. Verify the conversation, time and length of recordings is correct and accurate. 20 of 22

9. Conclusion These Application Notes describe the configuration steps required for I-Record to successfully interoperate with Avaya Aura Communication Manager. All feature and serviceability test cases were completed with observations noted in Section 2.2. 10. Additional References This section references the product documentation relevant to these Application Notes. The following Avaya product documentation can be found at http://support.avaya.com. [1] Administering Avaya Aura Communication Manager, Release 6.3, Issue 10.0, June 2014, Document Number 03-300509. [2] Configuration System Monitoring Avaya Ethernet Routing Switch 5000 Series, Release 6.2, December 2010, Document Number NN47200-505 06.03. Product documentation can be obtained from Invision. 21 of 22

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 DevConnect Program at devconnect@avaya.com. 22 of 22