Application Notes for TANDBERG Video Conference Solution with Avaya Meeting Exchange - Issue 1.0

Avaya Solution & Interoperability Test Lab Application Notes for TANDBERG Video Conference Solution with Avaya Meeting Exchange - Issue 1.0 Abstract These Application Notes describe the configuration steps required for interoperability of TANDBERG Video Solution with Avaya Meeting Exchange. The TANDBERG Video Conference Solution consists of the TANDBERG Video Communication Server (VCS) and the TANDBERG Cordian MCU. The objective is bridging audio conference call on Avaya Meeting Exchange with a video conference call on the TANDBERG side to increase the number of overall participants in a mixed audio and video collaboration call. 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

1. Introduction These Application Notes describe the sample configuration required for TANDBERG Video Conference Solution to interoperate with Avaya Meeting Exchange, with the objective of collaboration with the inclusion of Avaya Meeting Exchange audio conference users bridged into a TANDBERG video conference and TANDBERG video callers bridged as audio callers into Avaya Meeting Exchange conference via the link line. In this configuration, TANDBERG Codian MCU, TANDBERG video endpoints 1700 MXP and T150 MXP register to TANDBERG VCS. TANDBERG VCS communicates via H.323 with TANDBERG Codian MCU, and SIP with Avaya Meeting Exchange The interoperability compliance testing included basic feature testing. Feature tests focused on: Avaya Meeting Exchange audio callers dialing into TANDBERG Codian MCU video conference. TANDBERG Codian MCU video callers dialing into Avaya Meeting Exchange conference as audio callers. Multiple callers dialing into TANDBERG and Avaya Meeting Exchange conference. Verification of basic conference DTMF features like mute/unmute in the conference. Longevity test with 12 hours conference. Audio codec G.711 A law. 1.1. Support Technical support on TANDBERG can be obtained through the following: Web: http://www.tandberg.com/contact-tandberg-video-conferencingtelepresence.jsp 2 of 23

2. Reference Configuration The configuration in Figure 1 was used to test TANDBERG Conference Video Solution interoperability with Avaya Meeting Exchange to support Avaya Audio Collaboration Solution. The Avaya Bridge Talk application was used to provision a sample conference on Avaya Meeting Exchange. Figure 1: TANDBERG Video and Avaya Audio Solution 3 of 23

3. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya Meeting Exchange Enterprise Conferencing S6200 Server 5.1 build 5.1.0.0.161 Avaya Bridge Talk (BT) 5.2.0.0.4 Avaya Aura Communication Manager on 5.2, 947.3-17584 Avaya G350 Media Gateway Avaya 9620 phones S3.002 TANDBERG Codian MCU 2.4 build 6.13 (1.20) TANDBERG Video Communication Server (VCS) 4.2.1 TANDBERG 1700 MXP F8.0 Security TANDBERG T150 MXP L5.1 Security 4. Configure Avaya Meeting Exchange This section provides the procedures for configuring Avaya Meeting Exchange SIP link line into TANDBERG Codian conference as audio call via TANDBERG VCS. The VCS takes care of internetworking between SIP and H.323.The following steps describe the administrative procedures for configuring the Avaya Meeting Exchange: Basic configuration Enable link line for dial out Provision DDI/DNIS for dialling into the conferences 4.1.1. Basic Configuration Log in to the Avaya Meeting Exchange console (PuTTY) using ssh to access the Command Line Interface (CLI) with the appropriate credentials. Configure settings that enable SIP connectivity between the Avaya Meeting Exchange and other devices by editing the system.cfg file as follows: Edit /usr/ipcb/config/system.cfg Add Meeting Exchange S6200 IP address o IPAddress=( 10.10.14.35 ) Add a line to populate the From Header Field in SIP INVITE messages for Avaya Meeting Exchange in this sample configuration the values used. o MyListener=<sip:6000@10.10.14.35;5060;transport=tcp> Note: The user field 6000 was set as default digit string, used as the CLI for dials out originating from Avaya Meeting Exchange, this number should be aligned with dial plan. It is selected to match the user field provisioned for the respcontact entry (see below). Add a line to provide SIP Device Contact address to use for acknowledging SIP messages from the Avaya Meeting Exchange: o respcontact=<sip:6000@10.10.14.35:5060;transport=tcp> 4 of 23

Add the following lines to set the Min-SE timer to 900 seconds in SIP INVITE messages from the Avaya Meeting Exchange : o sessionrefreshtimervalue= 900 o minsetimervalue= 900 4.1.2. Enable link line by Dial Out To enable link line by Dial-Out from the Avaya Meeting Exchange to the TANDBERG VCS, edit the telnumtouri.tab file as follows: Edit /usr/ipcb/config/telnumtouri.tab file with a text editor. Add a line to the file to route outbound calls from the Avaya Meeting Exchange to the TANDBERG VCS. $1 substitutes the first wild card. * sip:$1@10.10.14.19:5060;transport=tcp TANDBERG VCS 5 of 23

4.1.3. Provision DDI/DNIS for Dialing into the Conferences The following steps provide examples of how to provision Scan Flow (Scheduled and Demand) conference call functions by utilizing the cbutil utility on the Avaya Meeting Exchange. To map DNIS entries, run the cbutil utility on Avaya Meeting Exchange as follows: If not already logged on, log in to the Avaya Meeting Exchange with a ssh connection using PuTTY with the appropriate credentials. Enable Dial-In access (via passcode) to conferences provisioned on the Avaya Meeting Exchange as follows: Add a DNIS entry for a scan call function corresponding to DID 1001 by entering the following command at the command prompt: cbutil add <dnis> <rg> <msg> <ps> <ucps> <func> [-l <ln> -c <cn>], where the variables for add command is defined as follows: o <dnis> DNIS o <rg> Reservation Group o <msg> Annunciator message number o <ps> Prompt Set number (0-20) o <ucps> Use Conference Prompt Set (y/n) o <func> One of: DIRECT/SCAN/ENTER/HANGUP/AUTOVL/FLEX o -l <"ln"> Optional line name to associate with caller o -c <"cn"> Optional company name to associate with caller In this sample configuration: S6200App->cbutil add 1001 0 247 1 n SCAN l Avaya_Linklineto_TANDBERG cbutil Copyright 2004 Avaya, Inc. All rights reserved. At the command prompt, enter cbutil list to verify the DNIS entries provisioned. [sroot@mx config]# cbutil list cbutil Copyright 2004 Avaya, Inc. All rights reserved. DNIS Grp Msg PS CP Function On Failure Line Name Company Name Room Start Room End ---------------- --- --- --- -- -------- ---------- -------------------- ---- --------------- ----------- ---------- 1001 0 247 1 N SCAN ENTER Avaya_Linklineto_TANDBERG AvayaLinklinetoTANDBERG 3331 0 301 1 N DIRECT ENTER TANDBERG_linklineto_Avaya 6 of 23

4.2. Bridge Talk The following steps utilize the Avaya Bridge Talk application to provision a sample conference on the Avaya Meeting Exchange. This sample conference enables both Dial-In and Dial-Out access to audio conferencing for endpoints on the Public Switched Telephone Network. Logging into Bridge Talk Provision a dial out Provision a Conference with Auto Blast Enabled Note: If any of the features displayed in the Avaya Bridge Talk screen captures are not present, contact an authorized Avaya sales representative to make the appropriate changes. 4.2.1. Logging into Bridge Talk Invoke the Avaya Bridge Talk application as follows: Double-click on the desktop icon from a Personal Computer loaded with the Avaya Bridge Talk application and with network connectivity to the Avaya Meeting Exchange [Not shown]. Enter the appropriate credentials in the Sign-In and Password fields. Enter the IP address of the Avaya Meeting Exchange (10.10.14.35 for this sample configuration) in the Bridge field. 7 of 23

4.2.2. Provision a Dial-Out Provision a dial list that is utilized for Dial-Out (e.g., Blast dial and Fast dial) from the Avaya Meeting Exchange.From the Avaya Bridge Talk Menu Bar, click Fast DialNew. 8 of 23

From the Dial List Editor window that is displayed: Enter a descriptive label in the Name field. Enable conference participants on the dial list to enter the conference without a passcode by checking the Directly to Conf box as displayed. Add entries to the dial list by clicking on the Add button and enter Name, Company and Telephone number for dial out for each participant. [Optional] Moderator privileges may be granted to a conference participant by checking the Moderator box. When finished, click on the Save button on the bottom of the screen. 9 of 23

4.2.3. Provision a Conference with Auto Blast Enabled To provision a conference with Auto Blast enabled go to the Avaya Bridge Talk Menu Bar, click View Conference Scheduler. From the Conference Scheduler window, click File Schedule Conference. 10 of 23

Provision a Scan Flow conference on Avaya Meeting Exchange, let moderator dial into this conference and auto blast will be trick, establishing link line from Avaya Meeting Exchange to TANDBERG. From the Schedule Conference window that is displayed, provision a conference as follows: Enter a unique Conferee Code to allow participants access to this conference. Enter a unique Moderator Code to allow participants access to this conference with moderator privileges. Enable moderator access with a passcode for this conference call by configuring the following: Note: This conference remains open for participants to enter as either moderator or participant by entering the appropriate code when prompted. Enter a descriptive label in the Conference Name field. Administer settings to enable an Auto Blast dial by setting Auto Blast to Auto/Manual depending on this test. Select a dial list by clicking on the Dial List button, select a dial list from the Create, Select or Edit Dial List window that is displayed, and click on the Select button (To verify Dial out and Blast Dial out) [Not Shown]. When finished, click on the Save button on the bottom of the screen. 11 of 23

Provision one more conference that is DIRECT in Avaya Meeting Exchange using Avaya Bridge Talk, this conference is used to create a link line from TANDBERG to Avaya Meeting Exchange.Refer Step 4.2.3 to open Conference Scheduler. From the Schedule Conference window that is displayed, provision a conference as follows: Enter a unique Conferee Code to allow participants access to this conference. Enter a Moderator Code which match s the DIRECT DDI of the Avaya meeting Exchange to establish link line from TANDBERG Codian (Refer Section 4.1.3 for more details). In this sample configuration 3331 is assigned as the link line number to dial out from Tandberg to Avaya Meeting Exchange. Enable moderator access with a passcode for this conference call by configuring the following: 12 of 23

5. Configure TANDBERG Conference Video Solution This section provides the procedures for configuring TANDBERG Codian SIP link line via TANDBERG Video Communication Server into Avaya Meeting Exchange as audio call. The VCS takes care of internetworking This conference when dialed in will create link line from Avaya Meeting Exchange to TANDBERG between H.323 and SIP: Configuring the TANDBERG VCS Configuring TANDBERG Codian MCU 5.1. Configure the TANDBERG VCS This section provides the procedures for configuring TANDBERG VCS. The procedures include the following areas: VCS Configuration Zone Configuration Route Pattern 13 of 23

5.1.1. VCS Configuration Open a web browser, enter http://x.x.x.x for the URL, where x.x.x.x is the IP address of the TANDBERG VCS. Log in with appropriate credentials. Click on the VCS Configuration Protocols H.323 and configure as shown below and click on Save. H.323 mode = On Registration UDP port = 1719 Call signaling TCP port = 1720 14 of 23

Click on the VCS Configuration Protocols SIP, configure as shown below and click on Save. SIP mode = On 15 of 23

5.1.2. Zone Configuration To configure a link from the TANDBERG VCS to Avaya Meeting Exchange perform the following steps. Click on the VCS Configuration tab and then the Zones sub-tab. Then on Add New Zone. Configure as shown below. For Name enter descriptive name, Peer 1 address is the IP address of the Avaya Meeting Exchange and click Save (not shown). 16 of 23

5.1.3. Route Pattern To configure the routing from TANDBERG VCS to Avaya Meeting Exchange click on the VCS Configuration tab and then the Zones sub-tab. Then click and open Avaya MX Zone. Configuring as show below: Mode = PatternMatch (Default Values) Priority = 100 (Default Values) Pattern string = (\d+)@avaya.com (\d+) Specifies the pattern against which the alias is compared and avaya.com is the domain name of the Avaya Meeting Exchange network. (For more details refer TANDBERG VCS 4.1.2 Administrators Guide) Pattern type = Regex (Regular Expression) Pattern behavior = Leave 17 of 23

Click on the VCS Configuration tab and then the TransformsNew. Configuring the following as shown in the sample configuration and click Save. Pattern string = (\d+) (Specifies the pattern against which the alias is compared) Priority = 1 Pattern type = Regex (Regular Expression) Pattern behavior = Replace Replace string = \1@avaya.com(avaya.com is the domain name of the Avaya Meeting Exchange network. (For more details refer TANDBERG VCS 4.1.2 Administrators Guide) 18 of 23

5.2. Configuring TANDBERG Codian MCU This section provides the procedures for configuring TANDBERG Codian MCU with TANDBERG VCS to allow TANDBERG users to dial into Codian MCU. Open a web browser; enter http://x.x.x.x for the URL, where x.x.x.x is the IP address of the TANDBERG Codian MCU. Log in with appropriate credentials. Click on Settings tab and then the Gatekeeper sub-tab. Set H.323 gatekeeper usage to Enabled. Set H.323 gatekeeper address to IP Address of VCS. Set Gatekeeper registration type to MCU (standard). Set Mandatory H.323 ID to register to Codian. (Enter descriptive name of the TANDBERG MCU.) Enter the MCU service prefix as configured. For the sample configuration MCU Service Prefix 6666 is DID or DDI to dial into Codian MCU conference from TANDBERG. Leave rest as default and click on Apply changes. 19 of 23

5.2.1. Dial List on Codian In the screen below, the participant 3331 configured in the dial list is used to create link line from Codian MCU Conference to Avaya Meeting Exchange. Open a web browser; enter http://x.x.x.x for the URL, where x.x.x.x is the IP address of the TANDBERG Codian MCU. Click on End Points followed by Add H.323, enter the following as shown in the sample configuration below and Save. Caller 3331 when dial out will create link line from TANDBERG conference to Avaya Conference (Refer Section 6.2 for more details). Display parameter Name=3331(Name of the endpoint) Call-out parameters Address=3331(IP address/host name or Phone number) Call-in match parameters Name=3331 (Name which sends to the MCU) E.164=3331 (Name with which end point is registered to gatekeeper) 20 of 23

6. General Test Approach and Test Results The general test approach was to bridge audio conference call on Avaya Meeting Exchange Enterprise with a video conference call on the TANDBERG side to increase the number of overall participants in a mixed audio and video collaboration call. It should be noted that, when a user invokes Avaya Meeting Exchange DTMF s features like mute and unmute all TANDERG callers hear the announcement but there is audio between two conferences. These features apply to Avaya Meeting Exchange callers only. 7. Verification Steps This section provides the tests that can be performed to verify configuration between Avaya and TANDBERG solution. Avaya Meeting Exchange Audio Conference establishing a link line with TANDBERG Codian MCU Video Conference. TANDBERG Codian MCU Video Conference establishing a link line with Avaya Meeting Exchange Audio Conference. 7.1. Verify Avaya Meeting Exchange Audio users dial into conference as Moderator. (Refer Section 4.3.2 for conference details). Since the conference is booked with Moderator Auto Blast as soon as the Moderator is in the conference Auto blast takes places which dials the audio link line (6666@10.10.14.19) to TANDBERG Codian conference. Dial a video caller from the TANDBERG 1700 MXP or T150 MXP using DDI 6666 and open Codian Adhoc conference. At this stage both the conference have bridged and verify audio is established between Avaya and TANDBERG and video within TANDBERG end points. 21 of 23

7.2. Verify TANDBERG Conference Audio users dial into Direct Avaya Meeting Exchange conference as Moderator. (Refer Section 4.3.2 for conference details). TANDBERG 1700 MXP or T150 MXP dial into Codian Adhoc Conference as video callers using DDI 6666. Login into TANDBERG Codian MCU webpage as administrator, from Conference Tab, open the active Adhoc conference. Click on Add Participants button and at the bottom of the page select End Point 3331 and dial. This will create a audio link line (3331@10.10.14.25) between Avaya and TANDBERG. At this stage both conferences have bridged and verify audio is established between Avaya and TANDBERG and video within TANDBERG end points. 8. Conclusion These Application Notes demonstrate how to provision TANDBERG VCS 4.2.1 and Avaya Meeting Exchange Enterprise S6200. In this configuration TANDBERG Codian MCU and TANDBERG video endpoints 1700 and T150 MXP register to TANDBERG VCS, and TANDBERG VCS integration is via SIP link line to Avaya Meeting Exchange. 9. Additional References Avaya references, available at http://support.avaya.com [1]Avaya Meeting Exchange S6200 5.1 SP1 Administration and Maintenance S6200/S6800 Doc ID 04-602674 TANDBERG references are available at www.tandberg.com/video-conferencing-support.jsp [1]TANDBERG VCS 4.1.2 Administrators Guide [2]TANDBERG 150 MXP Administrators Guide (L5) [3]TANDBERG 1700 MXP Administrator Guide (F8) [4]TANDBERG Codian MCU Getting Started 22 of 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 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. 23 of 23