Configuring Avaya IP Office as a Conference Server for an Avaya DEFINITY Server R with an MCC1 Media Gateway - Issue 1.0

Similar documents
Implementing Encrypted Conversations Between Avaya Softphone Endpoints with Avaya IP Office 403 and Avaya S8300 Media Server - Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for H.323 Voice over IP Trunking between Avaya Communication Manager and VoIP Americas Nativevoip VoIP Service - Issue 1.

Application Notes for the Vocera Communications System with an Avaya IP Telephony Infrastructure - Issue 1.0

How to Configure an H.323 IP Trunk between Avaya IP Office and Avaya Communication Manager - Issue 1.0

Application Notes for Configuring the Dialogic Brooktrout SR140 Fax Software with Avaya Communication Manager via H Issue 1.

How to configure an H.323 IP trunk between an Avaya IP600 Internet Protocol Communication Server and Avaya IP Office Server - Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for the T3 Telecom Software T3main Messaging Platform and Avaya Communication Manager using QSIG over a T1 Trunk Issue 1.

Application Notes for Configuring AudioCodes Mediant 1000 VoIP Media Gateway with Avaya Voice Portal Using SIP Trunks Issue 1.0

Configuring Interoperability between Avaya IP Office and Avaya Communication Manager

Abstract. Avaya Solution & Interoperability Test Lab

MCS SIP Integration with Avaya Communication Manager

Application Notes for the Trisys Tapit EX Call Accounting Software with Avaya Communication Manager Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Configuring SIP Trunks among Avaya Aura Session Manager, Avaya Aura Communication Manager, and Cisco Unified Communications Manager Issue 1.

Application Notes for CVT Periscope 3L Call Reporting with Avaya Communication Manager - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for configuring Oak Telecom s reportx with Avaya Aura Communication Manger R Issue 1.0

Configure Avaya Communication Manager and Avaya SIP Enablement Services for SIP Trunks with Cisco Unified CallManager Issue 1.0

Configuring Avaya Communication Manager for Media Encryption Issue 1.0

Application Notes for xmatters enterprise and Avaya Aura Communication Manager and Avaya Aura Session Manager Issue 1.0

Application Notes for Integrating Verint ULTRA9 VoIP Call Recording Service With Avaya Interaction Center - Issue 1.1

NNP Booklet For PBX Configurations Final Phase

Abstract. Avaya Solution & Interoperability Test Lab

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for BT Wholesale/HIPCOM SIP Trunk Service and Avaya IP Office 8.0 Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Abstract. Avaya Solution & Interoperability Test Lab

How to Configure the Juniper NetScreen 5GT to Support Avaya H.323 IP Telephony Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Integrated Research PROGNOSIS IP Telephony Manager with Avaya Communication Manager - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Yealink T-22 SIP Phones to interoperate with Avaya IP Office - Issue 1.0

Application Notes for Configuring Intelepeer SIP Trunking with Avaya IP Office Issue 1.0

Sample Configuration for Microsoft Firewall and McAfee Desktop Firewall 8.5 to Support Avaya IP Softphone Issue 1.0

Configuring an IPSec Tunnel between a Cisco 3825 Router and the Cisco VPN Client to Support Avaya IP Softphone Issue 1.0

Application Notes for Avaya IP Office 7.0 Integration with Skype Connect R2.0 Issue 1.0

Application Notes for Configuring Cablevision Optimum Voice SIP Trunking with Avaya IP Office - Issue 1.1

Application Notes for AudioCodes MP-202 Telephone Adaptor with Avaya SIP Enablement Services and Avaya Communication Manager - Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Cleo Transaction Processor with Avaya Voice Portal Issue 0.2

Application Notes for Configuring Avaya IP Office 8.1 with Colt VoIP Access service Issue 1.0

Configuring Instant Messaging and Presence capability for Avaya IP Agent using Avaya SIP Enablement Services - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Avaya IP Office 9.0 with HIPCOM SIP Trunk Issue 1.0

Application Notes for Configuring Broadvox SIP Trunking with Avaya IP Office - Issue 1.0

Updated Since : 3/17/2010

Application Notes for Biamp AudiaFLEX VoIP-2 with Avaya Aura Communication Manager Using Avaya Aura SIP Enablement Services Issue 1.

Application Notes for DuVoice Emergency Alert System with Avaya IP Office 9.0 Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring QuesCom 400 IP/GSM Gateway with Avaya IP Office using H.323 trunks Issue 1.0

Configuring H.323 over Port Network Address Translation (PNAT) for Avaya IP Endpoints using the Avaya SG200 Security Gateway - Issue 1.

Abstract. These Application Notes provide information for the setup, configuration, and verification of the call flows tested on this solution.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring 911 Enable Emergency Routing Service with Avaya IP Office - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Microsoft Office Communications Server 2007 R2 and Avaya IP Office PSTN Call Routing - Issue 1.0

Application Notes for configuring Avaya IP Office IP500 R7.0 with 2Ring NetFAX R3.0 Issue 1.0

Application Notes for Biamp AudiaFLEX VoIP-2 with Avaya IP Office Issue 1.0

Application Notes for DuVoice with Avaya IP Office 9.0 Issue 1.0

MITEL SX3300 AX Controller w/ NSU or Internal T1 Card

Application Notes for Configuring Broadvox SIPTrunking with Avaya IP Office R9.0 - Issue 1.0

Application Notes for Algo 8180 SIP Audio Alerter with Avaya Aura TM Session Manager and Avaya Aura TM Communication Manager - Issue 1.

Application Notes for Multi-Tech FaxFinder IP with Avaya IP Office Issue 1.0

Application Notes for Configuring a SonicWALL Continuous Data Protection (CDP) backup solution with Avaya Voic Pro - Issue 1.

DEFINITY IP Solutions

Abstract. Avaya Solution & Interoperability Test Lab

IP Office Technical Tip

Application Notes for Configuring Wesley Clover Solutions Trading Platform with Avaya IP Office using SIP Trunks Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring OneStream SIP Trunking with Avaya IP Office Release 8.1 Issue 0.1

Configuring Sample Screen Pop Applications with Avaya IP Agent Passing Caller Number, Prompted Digits or User to User Information - Issue 1.

Application Notes for DuVoice with Avaya IP Office 8.1 Issue 1.1

Application Notes for MultiTech FaxFinder IP with Avaya IP Office Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring SIP Trunking between Metaswitch MetaSphere CFS and Avaya IP Office Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Abstract. Avaya Solution & Interoperability Test Lab

Configuring Check Point VPN-1/FireWall-1 and SecuRemote Client with Avaya IP Softphone via NAT - Issue 1.0

Application Notes for Algo 8028 SIP Door Phone with Avaya IP Office - Issue 1.0

Application Notes for Algo 8180 SIP Audio Alerter with Avaya IP Office - Issue 1.1

Avaya IP Office 8.1 Configuration Guide

MAX T1/E1. Quick Start Guide. VoIP Gateway. Version 1.0

Application Notes for Revolabs FLX UC 1000 with Avaya IP Office - Issue 0.1

Application Notes for Jabra PC Suite and Jabra Evolve 65 Headset with Avaya one-x Agent - Issue 1.0

Application Notes for GN Netcom Jabra GN 9330 USB Headset and Jabra PC Suite with Avaya one-x Communicator and Avaya one-x Agent - Issue 1.

Vocia MS-1 Voice-over-IP Interface. Avaya System Verification. Configuring Avaya Aura Session Manager system with Biamp s Vocia MS-1

Abstract. Avaya Solution & Interoperability Test Lab

Configuring Microsoft Exchange Server 2010 Unified Messaging with Avaya Aura Communication Manager and Avaya Aura Session Manager - Issue 1.

Configuring Interoperability between Avaya IP Office and Avaya Business Communication Manager

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Broadvox SIP Trunking with Avaya IP Office Release 8.0 Issue 1.0

AudioCodes Mediant 1000 Configuration Guide

Application Notes for GN Netcom Jabra LINK 280 USB Adapter and Jabra PC Suite with Avaya one-x Communicator and Avaya one-x Agent - Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring the Ascom i62 VoWiFi handset version with Avaya IP Office Release Issue 1.0

Application Notes for snom 3x0 VoIP Phones with Avaya IP Office Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Transcription:

Configuring Avaya IP Office as a Conference Server for an Avaya DEFINITY Server R with an MCC1 Media Gateway - Issue 1.0 Abstract These Application Notes describe how to configure an Avaya IP Office 412 as a conference server for an Avaya DEFINITY Server R running MultiVantage Software with an MCC1 Media Gateway. A sample configuration is provided showing how to connect various trunks, and an IP H.323 trunk between the DEFINITY Server and IP Office, a sample dial-plan showing how to forward conference digits to IP Office, and an example configuration of the Avaya Voicemail Pro application. 1 of 30

1. Introduction These Application Notes describe how to configure an Avaya IP Office 412 as a conference server for an Avaya DEFINITY Server R with an MCC1 Media Gateway. Included in these Application Notes is a sample configuration showing how to connect a T-1 PRI trunk, an E-1 PRI trunk, and an IP H.323 trunk between the DEFINITY Server and IP Office. This mix of trunks was chosen for illustrative purposes, and the user needs to ensure that there are enough resources in IP Office to support the type and number of trunks configured. Also included is a sample dial-plan showing how to forward conference digits to IP Office. Lastly, these Application Notes offer an example configuration of the Avaya Voicemail Pro application to offer greeting and PIN code acceptance prompts and responses for secure entry into the conferences. Some points to note about this configuration are: The P334T is a Layer 2 switch and is configured to factory defaults. No further configuration information is required. The T-1 and E-1 cables between the DEFINITY Server R with an MCC1 Media Gateway and IP Office are straight-pass-through. A cross-over is not necessary. Although extensions 21810 through 21819 are passed to IP Office, the Voicemail Pro example uses only extension 21812 as the conference extension. Additional extensions can be set up for additional conferences, however this is left as a task for the reader. In Figure 1, an IP Office is connected to a DEFINITY Server R with an MCC1 Media Gateway via a T-1 PRI trunk, E-1 PRI trunk and an IP Trunk. Note that for the IP trunk the Multivantage has two connections. The first connection is the C-LAN board, which is the gatekeeper and it is responsible for H.323 signaling. The second connection is the MEDPRO board, which supplies the talk path. Ten conferences, extensions 21810 thru 21819, are configured on the IP Office as voicmailcollect shortcodes. These extensions do not exist in MultiVantage Software, but are, instead, forwarded to the IP Office. Then extension 21812 is dialed, the user is prompted with a welcome message and a request for a password PIN. The user is joined to the conference after PIN verification. 2 of 30

D EFINITY 034 SD 1 2 3 4 5 6 7 8 9 * 8 # 1 2 3 4 5 6 7 8 9 * 8 # Server running IP Office Manager, and Voicemail Pro software 10.1.1.51 Avaya P333T-PWR IP Office LAN 10.1.1.50/24 Multiple IP TrunkVoice Channels and Gatekeeper C-LAN Gatekeeper 10.1.1.150/24 H.323 Signaling MEDPRO LAN 10.1.1.151/24 Multiple IP TrunkVoice Channels DEFINITY Users DEFINITY Users Avaya IP412 Office T-1 PRI 23 Voice Channels E-1 PRI 30 Voice Channels Avaya DEFINITY Server R and MCC1 Media Gateway Figure 1: IP Office connected to a DEFINITY Server R and MCCI Media Gateway via T- 1, E-1 and IP Trunk 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya DEFINITY Server R with an MCC1 Media R0.11r.02.0.11.0.4 Gateway running Avaya Communication Manager Avaya IP Office 412 with 2 VCM 20 modules, 1 T-1 1.4(20) PRI module and 1 E-1 PRI module Avaya P333T-PWR Stackable Switch 3.12.1 Avaya Voicemail Pro 1.4.3 Table A: Version Table 3. Configure the Avaya MultiVantage Gateway The configuration for the Avaya Definity Server R is described into two parts. The first part describes how to configure the T-1, E-1 and IP Trunks, and the second part describes the configuration of the dialplan. 3 of 30

3.1. Configuring Trunks The circuit packs for the Definity Server R are located in the slots as outlined in Table B. Circuit Type Circuit Pack Cabinet Location T-1 TN464 1C15 E-1 TN464 1C16 C-LAN TN799 1C08 MEDPRO TN2302 1C07 Table B: Circuit Pack Location Table 3.1.1. Configuring T-1 Trunk Step 1: Assign a DS1 circuit pack. Figure 2 describes the framing and linecoding for the T-1 module in Location 1C15. change ds1 01c15 Page 1 of 2 SPE B DS1 CIRCUIT PACK Location: 01C15 Name: IP Office Bit Rate: 1.544 Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: network TN-C7 Long Timers? n Country Protocol: 1 Interworking Message: PROGress Protocol Version: b Interface Companding: mulaw CRC? n Idle Code: 11111111 DCP/Analog Bearer Capability: 3.1kHz Slip Detection? n Near-end CSU Type: other change ds1 01c15 Page 2 of 2 SPE B DS1 CIRCUIT PACK ESF DATA LINK OPTIONS Network Management Protocol: tabs Send ANSI-T1.403 One-Second Performance Reports? n Far-end CSU Address: b Figure 2: Configuring the T-1 parameters Step 2: Configure the signal group. Figure 3 shows the configuration of the associated signaling group parameters for Trunk Group 21. Notice that the field Trunk Group for Channel Selection must be left blank when adding the signaling group, even though this screen shows the value 21. This value will be added in a later step. 4 of 30

change signaling-group 21 Page 1 of 5 SPE B SIGNALING GROUP Group Number: 21 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 01C1524 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 21 X-Mobility/Wireless Type: NONE Supplementary Service Protocol: a Figure 3: Configuring T-1 Signal Group Parameters Step 3: Assign a trunk group. Figure 4 shows T-1 PRI Trunk Group 21 configured. Pages 1 and 2 describe trunk type attributes. Page 6 assigns ports to the trunk group where the first 15 of a total 23 ports were assigned for voice over this trunk. Do not assign port 24 (01C1524) as this is the ISDN PRI signal port and is not used for voice traffic. Now set the Trunk Group for Channel Selection field to 21 in the signaling-group. The first thing to do is to take the link out of service by typing busy signaling-group 21. Type change signaling-group 21, and set the Trunk Group for Channel Selection field to 21. Press Enter to apply the change. Then, type release signal-group 21 to bring it into service. change trunk-group 21 Page 1 of 22 SPE B TRUNK GROUP Group Number: 21 Group Type: isdn CDR Reports: y Group Name: IP Office T1 COR: 1 TN: 1 TAC: 121 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 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: ascend QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 5 of 30

change trunk-group 21 Page 2 of 22 SPE B TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: n Send Calling Number: y Used for DCS? n Suppress # Outpulsing? n Numbering Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n US NI Delayed Calling Name Update? n SBS? n Network (Japan) Needs Connect Before Disconnect? n change trunk-group 21 Page 6 of 22 SPE B TRUNK GROUP Administered Members (min/max): 1/23 GROUP MEMBER ASSIGNMENTS Total Administered Members: 23 Port Code Sfx Name Night Sig Grp 1: 01C1501 TN464 F 21 2: 01C1502 TN464 F 21 3: 01C1503 TN464 F 21 4: 01C1504 TN464 F 21 5: 01C1505 TN464 F 21 6: 01C1506 TN464 F 21 7: 01C1507 TN464 F 21 8: 01C1508 TN464 F 21 9: 01C1509 TN464 F 21 10: 01C1510 TN464 F 21 11: 01C1511 TN464 F 21 12: 01C1512 TN464 F 21 13: 01C1513 TN464 F 21 14: 01C1514 TN464 F 21 15: 01C1515 TN464 F 21 Figure 4: Configuring T-1 Trunk 21 6 of 30

3.1.2. Configuring E-1 Trunk Step 1: Assign an E-1 circuit pack. Figure 5 describes the framing and linecoding for the E-1 module in Location 1C16. change ds1 1c16 Page 1 of 1 SPE B DS1 CIRCUIT PACK Location: 01C16 Bit Rate: 2.048 Name: IP Office Line Coding: hdb3 Signaling Mode: isdn-pri Connect: pbx Interface: peer-master TN-C7 Long Timers? n Peer Protocol: Q-SIG Interworking Message: PROGress Side: a Interface Companding: mulaw CRC? y Idle Code: 11111111 Channel Numbering: timeslot DCP/Analog Bearer Capability: 3.1kHz Slip Detection? y Near-end CSU Type: other Figure 5: Configuring E-1 Parameters Step 2: Configure the signal group. Figure 6 shows the configuration of the associated signaling group parameters for Trunk Group 22. Notice that the field Trunk Group for Channel Selection must be left blank when adding the signaling group, even though this screen shows the value 22. This value will be added in a later step. change signaling-group 22 Page 1 of 1 SPE B SIGNALING GROUP Group Number: 22 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 01C1616 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 22 X-Mobility/Wireless Type: NONE Supplementary Service Protocol: b Figure 6: Configuring E-1 Signal Group Parameters Step 3: Assign a trunk group. Figure 7 shows E-1 PRI Trunk Group 22 configured. Pages 1 and 2 describe trunk type attributes. Page 6 assigns ports to the trunk group where the first 15 of a total 30 channels were assigned for voice over this trunk. Do not assign port 16 (01C1616) as this is the ISDN PRI signal port and is not used for voice traffic. Now set the Trunk Group for Channel Selection field to 22 in the signaling-group. The first thing to do is to take the link out of service by typing busy signaling-group 22. Type change signaling-group 22, and set the Trunk Group for Channel Selection field to 22. Press Enter to apply the change. Then, type release signal-group 22 to bring it into service. 7 of 30

change trunk-group 22 Page 1 of 22 SPE B TRUNK GROUP Group Number: 22 Group Type: isdn CDR Reports: y Group Name: IP Office E1 COR: 1 TN: 1 TAC: 122 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 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 change trunk-group 22 Page 2 of 22 SPE B TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: n Send Calling Number: n Used for DCS? n Hop Dgt? n Suppress # Outpulsing? n Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n Path Replacement with Retention? n Path Replacement Method: better-route SBS? n Network (Japan) Needs Connect Before Disconnect? n 8 of 30

change trunk-group 22 Page 6 of 22 SPE B TRUNK GROUP Administered Members (min/max): 1/30 GROUP MEMBER ASSIGNMENTS Total Administered Members: 30 Port Code Sfx Name Night Sig Grp 1: 01C1601 TN464 F 22 2: 01C1602 TN464 F 22 3: 01C1603 TN464 F 22 4: 01C1604 TN464 F 22 5: 01C1605 TN464 F 22 6: 01C1606 TN464 F 22 7: 01C1607 TN464 F 22 8: 01C1608 TN464 F 22 9: 01C1609 TN464 F 22 10: 01C1610 TN464 F 22 11: 01C1611 TN464 F 22 12: 01C1612 TN464 F 22 13: 01C1613 TN464 F 22 14: 01C1614 TN464 F 22 15: 01C1615 TN464 F 22 Figure 7: Configuring E-1 Trunk 22 3.1.3. Configuring IP Trunk Step 1: Configure IP node names. Assign names and IP addresses for the Multivantage C-LAN and MEDPRO circuit packs. Assign a name to the far-end IP Office gatekeeper and enter its IP address. See Figure 8. change node-names ip Page 1 of 1 SPE B IP NODE NAMES Name IP Address Name IP Address G3R1-CLAN 10.1.1.150... G3R1-MEDPRO 10.1.1.151... IPOffice 10.1.1.50... default 0.0.0.0... Figure 8: Configuring IP Node Names Step 2: Enter the gateway and subnet mask information for the Multivantage C-LAN and MEDPRO circuit packs. See Figure 9. change ip-interfaces Page 1 of 19 SPE B Enable IP INTERFACES Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn y C-LAN 01C08 TN799 D G3R1-CLAN 255.255.255.0 10.1.1.1 1 y MEDPRO 01C07 TN2302 G3R1-MEDPRO 255.255.255.0 10.1.1.1 1 Figure 9: Configuring IP Interfaces Step 3: Assign an extension to the C-LAN circuit pack. The C-LAN circuit pack requires assignment of an internal data-extension assigned to it. This extension must adhere to of the Multivantage dialplan. See Figure 10. Net 9 of 30

change data-module 20000 Page 1 of 1 SPE B DATA MODULE Data Extension: 20000 Type: ethernet Port: 01C0817 Link: 2 Name: CLAN01C08 Network uses 1's for Broadcast Addresses? y Figure 10: Configuring the C-LAN Data Module Step 4: Create the signal group. Figure 11 shows the configuration of the associated signaling group parameters for Trunk Group 2. Notice that the field Trunk Group for Channel Selection must be left blank when adding the signaling group, even though this screen shows the value 2. This value will be added in a later step. change signaling-group 2 Page 1 of 5 SPE B SIGNALING GROUP Group Number: 2 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 2 Supplementary Service Protocol: a Near-end Node Name: G3R1-CLAN Far-end Node Name: IPOffice Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Figure 11: Configuring IP Signal Group Parameters Step 5: Create the trunk group. Figure 12 shows IP trunk group 2 configured. Pages 1 and 2 describe trunk type attributes. Page 6 assigns ports to the trunk group where the first 15 of a total 31 ports were assigned for voice over this trunk. When entering the ports on page 6, simply enter IP and the Multivantage will automatically assign the T00 port ID for the IP trunk. Now set the Trunk Group for Channel Selection field to 2 in the signaling-group. The first thing to do is to take the link out of service by typing busy signaling-group 2. Type change signaling-group 2, and set the Trunk Group for Channel Selection field to 2. Press Enter to apply the change. Then, type release signal-group 2 to bring it into service. 10 of 30

change trunk-group 2 Page 1 of 22 SPE B TRUNK GROUP Group Number: 2 Group Type: isdn CDR Reports: y Group Name: IP Office IP Trunk COR: 1 TN: 1 TAC: 123 Direction: two-way Outgoing Display? n Carrier Medium: IP 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 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 change trunk-group 2 Page 2 of 22 SPE B TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Used for DCS? n Suppress # Outpulsing? n Outgoing Channel ID Encoding: preferred Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Send Name: n Send Calling Number: n UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n SBS? n Network (Japan) Needs Connect Before Disconnect? n 11 of 30

change trunk-group 2 Page 6 of 22 SPE B TRUNK GROUP Administered Members (min/max): 1/31 GROUP MEMBER ASSIGNMENTS Total Administered Members: 31 Port Code Sfx Name Night Sig Grp 1: T00109 2 2: T00110 2 3: T00111 2 4: T00112 2 5: T00113 2 6: T00114 2 7: T00115 2 8: T00116 2 9: T00117 2 10: T00118 2 11: T00119 2 12: T00120 2 13: T00121 2 14: T00122 2 15: T00123 2 Figure 12: Configuring IP Trunk 2 Step 6: Assign an IP network region. Figure 13 shows the configuration the network region QoS parameters for the IP trunk. Point the network region to the appropriate IP Codec set. change ip-network-region 1 Page 1 of 2 SPE B IP Network Region Region: 1 Name: Audio Parameters Codec Set: 1 Location: UDP Port Range Min: 16384 Max: 32767 Direct IP-IP Audio Connections? y IP Audio Hairpinning? y RTCP Enabled? y RTCP Monitor Server Parameters Use Default Server Parameters? y DiffServ/TOS Parameters Call Control PHB Value: 34 VoIP Media PHB Value: 46 BBE PHB Value: 43 802.1p/Q Enabled? n change ip-network-region 1 Page 2 of 2 SPE B Inter Network Region Connection Management Region (Group Of 32) 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 001-032 1 033-064 065-096 097-128 Figure 13: Configuring IP Network Region 12 of 30

Step 7: Choose a codec negotiation list. Assign preferred codecs in descending order. See Figure 14. change ip-codec-set 1 Page 1 of 1 SPE B Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: G.729 n 2 20 3: G.729A n 2 20 4: 5: 6: 7: Figure 14: Configuring IP Codec Set 3.2. Configuring Dial Plans Telephone extensions 21810 thru 21819 are forwarded to IP Office. These extensions are not defined in the MultiVantage system. Instead, they are compared against a Uniform Dialplan Table. If there is a match, digits are analyzed and manipulated in the AAR Analysis Table and are then forwarded to the corresponding trunk group to IP Office, based on the Route Pattern Table. Step 1: Create a Uniform Dialplan for 2181. Create an entry for the first four digits of the fivedigit conference extension. Specify the length of 5 so that the last digit will act as a placeholder for the conference number. Although the last digit is not directly referenced in the ensuing figures, it will be passed along. The first digit is deleted and 212 is added to form the a seven digit number 212181X. This number is then forwarded to the AAR analysis table for further processing. See Figure 15. change uniform-dialplan 2181 Page 1 of 2 SPE B UNIFORM DIAL PLAN TABLE Percent Full: 0 Matching Insert Node Matching Insert Node Pattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num 2181 5 1 212 aar n 31228 5 0 ext n 230 5 1 230 aar n 31229 5 0 ext n 300 5 1 300 aar n 31230 5 0 ext n 301 5 1 300 aar n 31231 5 0 ext n 302 5 1 300 aar n 31232 5 0 ext n 303 5 1 300 aar n 31233 5 0 ext n 304 5 1 300 aar n 31234 5 0 ext n 305 5 1 305 aar n 31235 5 0 ext n 306 5 1 305 aar n 31236 5 0 ext n 307 5 1 305 aar n 31237 5 0 ext n 308 5 1 305 aar n 31238 5 0 ext n 309 5 1 305 aar n 31239 5 0 ext n 310 5 1 310 aar n 313 5 1 310 aar n Figure 15: A Uniform Dial Plan Form 13 of 30

Step 2: Create an AAR Analysis entry. Create the AAR analysis entry for the seven-digit number of 21281X. Specify a maximum and total of 7 digits of the conference. Route pattern 20 is assigned for further processing in the Route Pattern Table. change aar analysis 212181 Page 1 of 2 SPE B AAR DIGIT ANALYSIS TABLE Percent Full: 5 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 212181 7 7 20 aar n 230 7 7 230 aar n 3 7 7 640 aar n 300 7 7 640 aar n 305 7 7 640 aar n 310 7 7 640 aar n 315 7 7 640 aar n 320 7 7 640 aar n 325 7 7 640 aar n 330 7 7 640 aar n 335 7 7 640 aar n 340 7 7 640 aar n 342 7 7 640 aar n 346 7 7 640 aar n 348 7 7 640 aar n Figure 16: AAR Analysis Form Step 3: Create Route Pattern 20. Route Pattern 20 has three entries associated with it. These entries correspond to the trunk groups that were previously created: 21, 22 and 2. The conference digits will be forwarded to the first trunk (T-1) until all 23 channels are filled, then the second trunk (E-1) until all 30 channels are filled, and lastly to the third trunk (IP) until all 31 channels are filled. After that, a reorder tone will sound to anyone who places call using this route pattern. Before the seven digits are forwarded, the first two digits, 21, will be stripped off so that only the original five digits will be sent. See Figure 17. change route-pattern 20 Page 1 of 3 SPE B Pattern Number: 20 Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 21 0 0 2 n user 2: 22 0 0 2 n user 3: 2 0 0 2 n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR 0 1 2 3 4 W Request Dgts Format Subaddress 1: y y y y y n n rest none 2: y y y y y n n rest none 3: y y y y y n n rest none 4: y y y y y n n rest none 5: y y y y y n n rest none 6: y y y y y n n rest none Figure 17: Route Pattern Form 14 of 30

4. Configure the Avaya IP Office There are two parts for configuring the Avaya IP Office. The first part is to configure the Manager application and the second step is to configure the Voicemail Pro application. 4.1. Configure the Avaya IP Office Manager Step 1: Under System, select the IP Office ID. In the form select the Voicemail tab. Enter the IP address of the PC that is running Voicemail Pro. See Figure 18. Figure 18: Configuring Manager to Point to Voicemail Pro s IP Address 15 of 30

Step 2: Enter all valid licenses. In Figure 19, a total of 30 Voicemail Pro ports are allowed. Figure 19: Conference Licenses 16 of 30

Step 3: Enter T-1 line information. Create a line for the T-1 module under Line on the left pane and enter the information in Figure 20 and Figure 21. Figure 20: Configuring T-1 17 of 30

Figure 21: Configuring T-1 (Continued) 18 of 30

Step 4: Enter E-1 line information. Create a line for the E-1 module under Line on the left pane and enter the information as shown in Figure 22. Figure 22: Configuring E-1 19 of 30

Step 5: Enter IP line information. Create a line for the LAN module under Line on the left pane and enter the information in Figure 23. When finished, click on the VoIP tab and enter the information shown in Figure 24. Figure 23: Configuring IP Trunk 20 of 30

Figure 24: Configuring IP Trunk (Continued) 21 of 30

Step 6: Configure the Incoming Call Route. Enter the incoming call route for all 10 conference numbers. Make sure that the Line Group ID matches the same field in the Line forms. See Figure 25. Figure 25: Configuring Incoming Call Route 22 of 30

Step 7: Enter the VoicemailCollect shortcode. This shortcode maps into the Voicemail Pro scripts. See Figure 26. Figure 26: Configuring VoicemailCollect Shortcode 23 of 30

Step 8: Enter the ConferenceMeetMe shortcode. It will be up to the Voicemail Pro script to forward the call to this number once Voicemail Pro validates the caller s PIN number. See Figure 27. Figure 27: Configuring ConferenceMeetMe Shortcode 24 of 30

4.2. Configure the Avaya IP Office Voicemail Pro All Voicemail Pro scripting events contain an Entry Prompt tab where the system manager can record a message to play prior to executing the script. A PC with a microphone and a soundcard is required in order to record and save this wave file. See the Users Manual for more details on how to record and save messages. Step 1: Create a short code entry called conference. A Start Point event has already been created by default. From the Actions Menu choose the following: Under Condition Actions submenu add Check Digits; under Telephony Actions submenu add Assisted Transfer events; under Basic Actions add two Generics and Disconnect. Optionally, rename these actions for clarity purposes. Double click on each action and choose the General tab. Under token name, rename the following: Check Digits to Check Pins Assisted Transfer to Transfer to Conference01 One Generic to Transfer Problem Another Generic to Invalid PIN Connect them as in Figure 28. 25 of 30

Figure 28: Voicemail Pro Main Script Layout 26 of 30

Step 2: Edit the Check PIN event. Double click on the event and select on the Entry Prompts tab and record a greeting and instructions for entering the PIN number. When finished, select the Specific tab. Enter the PIN password that the caller must match. Press OK when complete. See Figure 29. Figure 29: Checking for Correct Pin Number 1234 27 of 30

Step 3: Admit into the conference. Click on the Assisted Transfer event that is connected to the Yes path from the Check Digits event. Fill out the form as in Figure 30. Once again, click on the Entry Prompts tab to record a conference-greeting message. Press OK when complete. Figure 30: If Digits are Correct Then Forward to Internal Extension ConferenceMeetMe Shortcode 28 of 30

Step 4: Select Entry Prompts tab and record appropriate messages for Transfer Problem and InvalidPIN. After the particular message is played, the user is then passed to Disconnect where the call drops. Step 5: Save & Make Live. Under the File drop-down menu on top, click on Save & Make Live option to save and activate the configuration. 5. Verification Steps In Multivantage, type status trunk n where n is either trunk numbers 21, 22, or 2. The trunk status should be in service/idle. If not, recheck the configuration. In addition, all IP interfaces (C-LAN, MEDPRO, and IP Office) should respond to pings. Place calls into the bridge and verify that the calls route properly and voice quality is acceptable. 6. Conclusion After completing the configurations as described above, the Avaya IP Office Conference server will work as a conference server for MultiVantage. 29 of 30

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 Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com 30 of 30