Abstract. Avaya Solution & Interoperability Test Lab

(1)

Avaya Solution & Interoperability Test Lab

How to Configure Avaya Interactive Response (IR) with IP

Station Registration to Multiple Gatekeepers in a Sample

Solution Assurance Configuration – Issue 1.0

Abstract

These Application Notes describe the system configuration parameters required to interconnect via Voice over IP (VoIP), an Avaya Interactive Response (IR) system to multiple gatekeepers in a sample Solution Assurance configuration. Avaya IR Release 2.0 supports IP Station registration to multiple gatekeepers that allows options for VoIP interconnection redundancy and survivability to Avaya Communication Manager.

(2)

1. Introduction

Avaya Interactive Response (IR) is an Interactive Voice Response (IVR) system that supports advanced applications of customer self-service solutions. Avaya IR R2.0 further enhances support by providing VoIP redundancy, survivability, and security to Avaya Communication Manager. Avaya IR supports registration to multiple Avaya Communication Manager CLAN boards or Processor Ethernet resources on simplex (S8300, S8400, and S8500) Media Servers that serve as gatekeepers for IP (H.323) endpoints. An Avaya IR system can have up to ten VoIP cards, and allows the capability to configure each card differently for IP station registration to a particular gatekeeper. Each IP station registration is a virtual VoIP channel or IP port in Avaya IR for calls to and from Avaya Communication Manager. Avaya IR also has the capability to secure the VoIP media streams by setting an encryption algorithm on the VoIP card.

These Application Notes illustrate an example of the administration steps required to configure Avaya Communication Manager and Avaya IR for VoIP interconnection with multiple gatekeeper resources for IP station registration. Various call flow scenarios are described in detail that shows how the solution provides redundancy and survivability options.

1.1. Reference Network Configuration

Parts of the sample Avaya Solutions Assurance Credit Card & Banking Configuration depicted in

Figure 1 are used to verify these Application Notes. Figure 1 represents a typical multi-location

financial customer with a hub and spoke architecture. The parts or locations included in verifying these Application Notes are Main Office, Site 2, and Site 4. The Main Office consists of an Avaya S8710 Media Server pair and two Avaya G650 Media Gateways in an IP Connect High Reliability configuration. The Main Office G650 Media Gateways combine in a single Port Network # 1. The Main Office also contains the Avaya IR. Site 2 has an Enterprise Survivable Server (ESS) S8710 Media Server pair and one Avaya G650 Media Gateway as Port Network # 2. Site 4 contains a G350 Media Gateway and a Local Survivable Processor (LSP) S8500 Media Server. All site Port Networks, Media Gateways, and IP endpoints register to the C-LANs located in the Main Office G650 Media Gateways. Each site has Public Switched Telephone Network (PSTN) access via Time Division Multiplexed (TDM) trunks and private WAN access. Please refer to the Call Flow

Diagrams in Section 1.2 that illustrate the logical VoIP channels (IP station registration) between

Avaya IR, the C-LAN in the G650 in the Main Office, the C-LAN in the G650 in Site 2, and the LSP S8500 Media Server for “Sunny Day” and various fail-over scenarios.

Note: It is important to mention the following:

1. These Application Notes focus on the VoIP interconnection of the Avaya IR and Avaya

Communication Manager using basic network fundamentals. Advanced topics such as VLAN, IP Routing, QoS, etc, are outside the scope of this document, which includes the Cisco networking hardware illustrated in Figure 1.

2. Alternative configurations to one depicted in Figure 1 may provide additional redundancy

and survivability options for VoIP interconnection between the Avaya IR and Avaya Communication Manager.

(3)

3. These Application Notes do not cover the point-to-point Time Division Multiplexing

(TDM) T1s shown in Figure 1 between the Avaya IR and the Main Office, Site 2, and Site 4.

4. It is assumed that CLAN and Media Processor hardware utilized to verify these Application

Notes are previously administered.

(4)

1.2. Call

Flow

The following are call flow depictions for “Sunny Day” and various failover scenarios for the sample configuration covered in these Application Notes.

1.2.1. Sunny Day Scenario

Normal operation may entail percentage allocation routing of Self Service Customer calls from the PSTN to the Main Office and Site 2. These locations have identical sized data centers designed to run at full capacity in a stand-alone mode for maintenance or Disaster Recovery operation. Therefore, these locations have duplicated VoIP channel capacity to the Avaya IR. Site 4 is an alternate location for terminating Self Service Customer calls from the PSTN. However, this option is only available if both the Primary and ESS servers are not available and Avaya IR is reachable.

1.2.2. CLAN Failure Scenarios

Designing an Avaya IR solution that utilizes multiple CLANs for IP Station registration and

signaling provides redundancy and protection from a total loss of IP connectivity. Unlike Avaya IP Telephones, the Avaya IR IP stations do not support CLAN fail-over. At Avaya IR Voice System start-up, the IP stations register to the CLAN board assigned on each VoIP card. If the CLAN board fails or is no longer reachable, the Avaya IR IP stations will not register to an alternate CLAN board. If the CLAN board fails after the initial registration, the Avaya IR IP stations for the effected VoIP card, become out of service. However, other Avaya IR VoIP cards that utilize other CLAN boards continue to provide IP station registration and VoIP connectivity.

Loss of Main Office CLAN - The Avaya IR can no longer register IP stations to the Main Office

CLAN due to a CLAN board failure and looses some VoIP channel capacity. A change to the percentage allocation routing of Self Service Customer calls is not required. Self Service Customer calls that route from the PSTN to the Main Office may continue to terminate on the Avaya IR system only if the Main Office Avaya G650 Media Gateway has available Media Processor

(5)

to Site 2 use the available Media Processor resources in its Avaya G650 Media Gateway for TDM to IP packet conversion before terminating on the Avaya IR.

Loss of Site 2 CLAN - Self Service Customer calls that route from the PSTN to Site 2 may

continue to terminate on the Avaya IR system only if the Site 2 Avaya G650 Media Gateway has available Media Processor resources for TDM to IP packet conversion. Self Service Customer calls that route from the PSTN to the Main Office use the available Media Processor resources in its Avaya G650 Media Gateway for TDM to IP packet conversion before terminating on the Avaya IR.

1.2.3. Loss of Primary Servers Scenario

If the Primary Servers are not available, the Media Gateways and Port Networks may register to the ESS Servers at Site 2 as long as the network has not also suffered an outage and can provide

connectivity between them. Avaya IR may continue to provide VoIP connectivity if CLAN and Media Processor resources are again in service.

(6)

1.2.4. Loss of Primary Servers and Site 2 WAN Scenario

In addition to the loss of the Primary Servers, Site 2 suffers a WAN link outage that isolates it from the other locations. The Main Office Avaya G650 Media Gateway can no longer provide services so the PSTN trunks become out-of-service. At Site 4, the Avaya G350 Media Gateway now registers with the active Avaya S8500 Media Server. The Avaya IR may continue to provide VoIP connectivity as long as the network has not also suffered an outage between them. The Avaya IR IP stations that assigned to utilize the Avaya S8500 Media Server now register to its Processor Ethernet. To allow for Self Service Customer calls to route from the PSTN to Site 4, a routing plan change is required in the PSTN for Self Service Telephone access number.

(7)

FAIL-OVER SCENARIO Main Office Site 2 Site 4

Normal “Sunny Day” 4 4 0

Loss of CLAN (01A02) in Main Office G650

Media Gateway 0 4 0

Loss of CLAN (02A02) in Site 2 G650 Media

Gateway 4 0 0

Loss of Main Office S8710 Media Server

(Site 2 ESS S8710 Media Server active) 4 4 0

Number of VoIP Trunks &

IR Channels

Loss of Main Office S8710 Media Server and connectivity to Site 2

(Site 4 LSP S8500 Media Server Active)

(8)

2. Equipment and Software Validated

The following equipment and software were used for the sample configuration provided:

Equipment – Main Office Software

Avaya S8710 Media Server Avaya Communication Manager

R3.1 (R013x.01.0.628.7) Avaya G650 Media Gateway (2)

• Avaya TN2312BP IPSI Circuit Packs (2) • Avaya TN779DP C-LAN Circuit Packs (2) • Avaya TN2602AP Crossfire Circuit Packs (2) • Avaya TN2501AP VAL Circuit Pack

FW 030 FW 017 FW 031 FW 009 Avaya Converged Stackable Switch C363T-PWR (2) 4.5.14

Avaya Call Management System (CMS) R13.1AUX

Avaya Interactive Response (IR) R2.0

Cisco 6506 Switch Router 12.4(5)

Cisco 2950 Switch (2) 12.4(5)

Cisco 3725 Router 12.4(5)

Table 2: Main Office

Equipment Software

Avaya G650 Media Gateway

• Avaya TN2312BP IPSI Circuit Pack • Avaya TN779DP C-LAN Circuit Pack • Avaya TN2602AP Crossfire Circuit Pack • Avaya TN2501AP VAL Circuit Pack

FW 030 FW 017 FW 031 FW 009 Avaya S8710 Media Server

• Enterprise Survivable Server (ESS) Avaya Communication Manager R3.1 (R013x.01.0.628.7)

Avaya Converged Stackable Switch C363T-PWR 4.5.14

(9)

Avaya G350 Media Gateway • MM712 • MM710 (2) • MM720 • MMANALOG 25.23.0 Vintage 5 Version 7 Vintage 5 Version 14 Vintage 5 Version 6 Version 68

Avaya S8500 Media Server (LSP) Avaya Communication Manager

R3.1 (R013x.01.0.628.7)

Avaya Call Management System (CMS) R13.1AUX

Table 4: Site 4

Avaya Call Center R3.1

Avaya Site Administration (ASA) 3.1.13

Avaya Voice Announcement LAN (VAL) Manager 3.1.12

Avaya Terminals

• Avaya 4600 Series IP Telephones • Avaya DCP 2420 Telephones

• Avaya 6211 Analog Telephones • Avaya IP Agent Client

• Avaya IP Softphone Client

2.3 (2.5 for 4625 )

R6.0 R5.2

Cisco 3845 WAN Router (2) 12.4(5)

Servers: Microsoft Windows Server 2003 Enterprise Edition

PC Workstations: Microsoft Windows XP Professional Version 2002

(10)

3. Configure Avaya Communication Manager

These Application Notes assume all equipment in Table 2 through Table 5 has been previously administered with the exception of the configuration parameters required to interconnect the Avaya IR system to multiple CLAN boards or Processor Ethernet ports. The following pages detail step-by-step instructions on how to verify and administer the required configuration parameters. Please refer to the appropriate User Guides for more information on how to configure the equipment of the sample configuration depicted in Figure 1.

3.1. Verify Avaya Communication Manager Licenses

To set up VoIP connectivity to the Avaya IR system, certain Avaya Communication Manger licenses must be active. The next steps verify these required licenses. If any licenses are missing, contact your Avaya Authorized Sales representative.

The following commands were entered on an Avaya Communication Manager System Access Terminal (SAT):

Step Description

1. Issue the command “display system-parameters customer options” to display the active licensed features. Go to Page 2 and verify that the “Maximum Concurrently Registered IP

Station” field is greater than “0”.

display system-parameters customer-options Page 2 of 11 OPTIONAL FEATURES

IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: 500 15 Maximum Concurrently Registered IP Stations: 2000 28 Maximum Administered Remote Office Trunks: 8000 2 Maximum Concurrently Registered Remote Office Stations: 12000 0 Maximum Concurrently Registered IP eCons: 0 0 Max Concur Registered Unauthenticated H.323 Stations: 600 0 Maximum Video Capable H.323 Stations: 0 0 Maximum Video Capable IP Softphones: 0 0 Maximum Administered SIP Trunks: 20 0 Maximum Number of DS1 Boards with Echo Cancellation: 5 0 Maximum TN2501 VAL Boards: 3 2 Maximum G250/G350/G700 VAL Sources: 10 3 Maximum TN2602 Boards with 80 VoIP Channels: 20 0 Maximum TN2602 Boards with 320 VoIP Channels: 5 2 Maximum Number of Expanded Meet-me Conference Ports: 5 0

(11)

2. Go to Page 4 and verify that the “IP Stations” and “Media Encryption Over IP” fields are set to “y”.

3. Go to Page 5 and verify that the “Processor Ethernet” field is set “y”.

Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Internet Protocol (IP) PNC? y Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? y ISDN Network Call Redirection? y Enterprise Survivable Server? n ISDN-BRI Trunks? y Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? y Local Survivable Processor? n Extended Cvg/Fwd Admin? n 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? n Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? y Hospitality (G3V3 Enhancements)? y Multimedia Call Handling (Enhanced)? y IP Trunks? y

IP Attendant Consoles? y

(NOTE: You must logoff & login to effect the permission changes.)

Multinational Locations? n Station and Trunk MSP? n Multiple Level Precedence & Preemption? n Station as Virtual Extension? n Multiple Locations? y

System Management Data Transfer? n Personal Station Access (PSA)? y Tenant Partitioning? n Posted Messages? y Terminal Trans. Init. (TTI)? y PNC Duplication? n Time of Day Routing? y Port Network Support? y Uniform Dialing Plan? y Usage Allocation Enhancements? y Processor and System MSP? n TN2501 VAL Maximum Capacity? y Private Networking? y

Processor Ethernet? y Wideband Switching? y Wireless? n Remote Office? y

Restrict Call Forward Off Net? y Secondary Data Module? y

(12)

4. Go to Page 10 and verify that the “Maximum IP Registrations By Product ID” limit field for “IP_API_A” is set to a value greater than “0”.

display system-parameters customer-options Page 10 of 11 MAXIMUM IP REGISTRATIONS BY PRODUCT ID

Product ID Rel. Limit Used

IP_API_A : 1000 8 IP_API_B : 1000 0 IP_API_C : 1000 0 IP_Agent : 1000 1 IP_Phone : 12000 18 IP_ROMax : 12000 0 IP_Soft : 500 1 IP_eCons : 0 0 : 0 0 : 0 0 : 0 0 : 0 0 : 0 0

(13)

3.2. Avaya Communication Manager IP Administration

The administration of Avaya Communication Manager IP parameters is specific to each

configuration. Factors such as the placement of Avaya IR on the network determine the required administration, the effect on performance, and how signaling and media paths are established to Avaya IR. On Avaya Communication Manager, administrators may or may not need to administer a different IP Network Region for Avaya IR. It depends on the requirements for the Avaya IR solution. For more information regarding IP Network Region Administration, please refer to the following Application Note: “Avaya Communications Manager Network Region Configuration Guide”, COMPAS ID: 103244.

For the configuration the purposes of these Application Notes, the assignment of a unique IP Network Region for Avaya IR is not recommended. The Avaya IR IP stations inherit the network region of the CLAN board to which it sends the Gatekeeper Discovery (GRQ) message. The Gatekeeper IP Address is static and unique to each Avaya IR VoIP card (Please refer to Section 4.2). Each Avaya IR VoIP card targets a specific CLAN board for IP station registration regardless of network region. For designing redundancy and survivability options, this is significant since the Avaya IR VoIP card may loss connectivity to its gatekeeper, which results in a limited number of IP station registration failures and protects from a total loss of IP connectivity between Avaya IR and Avaya Communication Manager.

The following steps illustrate how to configure Avaya Communication Manager IP parameters for VoIP connectivity to Avaya IR:

1. Issue the command “display ip-network-region 1”. IP network region number 1 (also assigned to the Main Office) is the default for IP endpoints that are not assigned to an IP Network Region using the “change ip-network-map” form (includes Avaya IR). Verify the assigned “Codec Set” number for this IP Network Region.

display ip-network-region 1 Page 1 of 19 IP NETWORK REGION

Region: 1

Location: 1 Authoritative Domain: Name: Main Office

MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? y UDP Port Max: 3029

DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: 26

802.1P/Q PARAMETERS

Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6

Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y

Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5

(14)

2. Go to Page 3 and verify the “Codec Set” number utilized between the source region “src

rgn” (Avaya IR) and destination regions “dst rgn” for Inter Network Region Connection

Management to Site 2 and Site 4.

Note: IP Network Region Number 2 and 4 is for Site 2 and Site 4 respectively.

3. Repeat steps 1 and 2 for IP Network Regions 2 and 4 to verify that Avaya IR will be able to established media paths successfully between these locations.

4. Issue the command “change ip-codec 1”. As verified in steps 1 through 3, IP Codec Set 1 is designated the Intra-Network Region IP Codec Set assigned to every IP Network Region for the reference configuration in Figure 1. Verify or assign an “Audio Codec” of “G.711MU”. Avaya IR only supports the G711MU (mu-law) Codec for VoIP. For the Audio Codec

Number corresponding to G.711MU, set the “Media Encryption” to “aes” (Advanced Encryption Standard). Please refer to Section 4.2 for setting the media encryption algorithm on the Avaya IR VoIP card.

change ip-codec 1 Page 1 of 2 IP Codec Set

Codec Set: 1

Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: 3: 4: 5: 6: 7: Media Encryption 1: aes 2: 3:

display ip-network-region 1 Page 3 of 19 Inter Network Region Connection Management

src dst codec direct Dynamic CAC rgn rgn set WAN WAN-BW-limits Intervening-regions Gateway IGAR 1 1 1 y :NoLimit n 1 2 2 y :NoLimit n 1 3 2 y :NoLimit n 1 4 2 y :NoLimit n 1 5 2 y :NoLimit n

(15)

5. Issue the command “change ip-codec 2”. IP Codec Set 2 is the designated IP Inter-Network Region Codec Set for each IP Network Region for the reference configuration in Figure 1. Verify that the IP Codec 2 has an “Audio Codec” of “G.711MU” assigned or add

“G.711MU” if it is missing in order to support VoIP connectivity between Site 2 and Site 4 to Avaya IR. For the Audio Codec Number corresponding to G.711MU, set the “Media

Encryption” to “aes” (Advanced Encryption Standard). Please refer to Section 4.2 for setting

the media encryption algorithm on the Avaya IR VoIP card.

6. Issue the command “change node-names ip x” where “x” is the name assigned to the Avaya IR. Enter the name “x” and assigned “IP address” (Please refer to Section 4.2).

change ip-codec 2 Page 1 of 2 IP Codec Set

Codec Set: 2

Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.729A n 2 20 2: G.711MU n 2 20 3: 4: 5: 6: 7: Media Encryption 1: 2: aes 3:

change node-names ip sa-ir Page 1 of 1 IP NODE NAMES

Name IP Address Name IP Address val-01a06 10 .1 .2 .31 . . . val-02a06 10 .2 .2 .31 . . . sa-ir 10 .1 .1 .54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 2 of 36 administered node-names were displayed )

Use 'list node-names' command to see all the administered node-names

(16)

3.3. IP Station Configuration for Avaya IR VoIP Channels

An IP station is administered for each Avaya IR VoIP Channel. The extension of the assigned station is equal to the assigned “phone number” in Avaya IR for the VoIP channel. Please refer to Section 4.2 (Avaya IR VoIP Channel Configuration), steps 11 through 17, of these Application Notes.

1. Issue the command “add station xxxxx”, where xxxxx is the extension of Avaya IR VoIP channel. Set the station “Type” field as “7434ND”, the “Port” field as “IP”, and the “IP

Softphone” field to “y”. Assign a password (up to eight digits) in the “Security Code” field

for VoIP Station Authentication. The password assigned to the “Security Code” field of the station form must match the password assigned to the “VoIP H.323 MultiVantage Station

Password” field when assigning the phone number (station extension) to the Avaya IR VoIP

channel.

add station 20780 Page 1 of 4 STATION

Extension: 20780 Lock Messages? n BCC: 0 Type: 7434ND Security Code: 1234 TN: 1 Port: IP Coverage Path 1: COR: 1 Name: IR IP CH96 - Main Office Coverage Path 2: COS: 1 Hunt-to Station:

STATION OPTIONS

Loss Group: 2 Personalized Ringing Pattern: 1 Data Module? n Message Lamp Ext: 20780 Display Module? n

Coverage Module? n Media Complex Ext: IP SoftPhone? y Remote Office Phone? n IP Video Softphone? n

(17)

2. Go to Page 2 and set the “Multimedia Mode” field to “enhanced”. Leave all other fields at the default setting.

3. Repeat these steps 1 and 2 to add an IP station extension for each Avaya IR VoIP channel.

3.4. Administer a Hunt Group Extension for access to the Avaya IR

VoIP Channels

1. Issue the command “add hunt-group x”, where x is the hunt group number. Assign the extension number in the “Group Extension” field. The Avaya IR VoIP Channels will be accessed via this assigned extension number. Set the “Group Type” field to “ucd-mia”.

add station 20780 Page 2 of 4 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? n Restrict Last Appearance? y Active Station Ringing: single Conf/Trans on Primary Appearance? n H.320 Conversion? n Per Station CPN - Send Calling Number? Service Link Mode: as-needed

Multimedia Mode: enhanced Audible Message Waiting? n MWI Served User Type: Display Client Redirection? n AUDIX Name: 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? y Emergency Location Ext: 20780 Always Use? n IP Audio Hairpinning? n

add hunt-group 91 Page 1 of 60 HUNT GROUP

Group Number: 91 ACD? n Group Name: IR (IP) Ports Queue? n Group Extension: 20591 Vector? n Group Type: ucd-mia Coverage Path: TN: 1 Night Service Destination: COR: 1 MM Early Answer? n Security Code: Local Agent Preference? n ISDN/SIP Caller Display: grp-name

(18)

2. Go to Page 3 and enter the assigned IP Station extensions as group members.

add hunt-group 91 Page 3 of 60 HUNT GROUP

Group Number: 91 Group Extension: 20591 Group Type: ucd-mia Member Range Allowed: 1 - 1500 Administered Members (min/max): 1 /12 Total Administered Members: 12 GROUP MEMBER ASSIGNMENTS

Ext Name (24 characters) Ext Name (24 characters) 1: 20780 IR IP CH96 - Main Office 14: 2: 20781 IR IP CH97 - Main Office 15: 3: 20782 IR IP CH98 - Main Office 16: 4: 20783 IR IP CH99 - Main Office 17: 5: 22780 IR IP CH100-Site 2/ESS 18: 6: 22781 IR IP CH101-Site 2/ESS 19: 7: 22782 IR IP CH102-Site 2/ESS 20: 8: 22783 IR IP CH103-Site 2/ESS 21: 9: 24780 IR IP CH104-Site 4/LSP 22: 10: 24781 IR IP CH103-Site 4/LSP 23: 11: 24782 IR IP CH106-Site 4/LSP 24: 12: 24783 IR IP CH107-Site 4/LSP 25: 13: 26: At End of Member List

(19)

4. Configure Avaya Interactive Response

The following steps illustrate how to configure Avaya IR using a Web Graphical User Interface (GUI).

1. Open a Windows Explorer browser and enter the IP address or DNS entry of the Avaya IR system (For Example http://10.1.1.54 or http://sa-ir.solar.com) to display the main Web

Administration page. Click the “Web Administration” button to enter the secure Web Administration pages.

2. Enter a username and password with administrator privileges as shown below. Click the “Logon” button to enter Web Administration.

(20)

4.1. Verify

Avaya

Interactive Response Licenses

Avaya IR R2.0 utilizes Primary and Secondary WebLM servers for implementation of feature licenses. If activation of additional features or ports is required, an updated license file must be obtain and installed on WebLM server. The license life contains details about the features and number of ports purchased. To obtain an updated license file, please contact your Avaya Authorized Sales representative.

The following illustrates how to verify the feature licenses on the Avaya IR.

1. Upon successful login to Web Administration, the following page appears. The windowpane on the left of the web page contains all the Avaya IR Web Administration functions.

To administer additional digital or VoIP (Channel) ports on the Avaya IR system requires the availability of free feature port licenses. To verify the Avaya IR System feature licenses double click on “Feature Licensing” under the “Configuration Management” section.

(21)

2. Verify that the number of free licenses for the feature type “VALUE_IR_PORTS” is a value equal to or greater than the number of ports “VoIP Channels” to be configured on the Avaya IR system.

(22)

4.2. Avaya IR VoIP Channel Configuration

1. To configure the VoIP Channels, click on “Voice over IP” under the “Switch Interfaces” section. Click on the “Assign Card” button to administer the virtual Avaya IR VoIP card.

2. Avaya IR VoIP card numbers range from 6 to 15. Assign number 6 in the “Card” field and click on the “Submit” button to configure the first VoIP card.

(23)

3. Assign the VoIP card parameters for Card 6 to register to the CLAN board located in the Main Office G650 Media Gateway. Click the “Submit” button when complete.

The following describes each VoIP card parameter field shown on the next page:

• Card Name – A unique name for the VoIP card limited to nine characters in length. • Card Enabled – Controls the activation of call processing on the VoIP card.

• Card IP Address – The local IP address assigned to the NIC of the Avaya IR. The IP address entered here should match the one assigned on the IP Node Names form for the Avaya IR (Please refer to Section 3.2, Step 6).

• Gatekeeper IP Address – The IP address of the targeted Gatekeeper (CLAN board or Processor Ethernet card).

• H.323 Gatekeeper Port – UDP port the Gatekeeper uses to accept registration requests (Port 1719 for CLAN board or Processor Ethernet card).

• Low RTP Port – The lowest UDP port the Avaya IR can use for RTP communication. The default value is 8000.

• High RTP Port – The highest UDP port the Avaya IR can use for RTP communication. The default value is 10000.

• RTP Packet Size – The RTP packet payload size in milliseconds (values: 10, 20, 30, 40, 50, or 60) for outgoing calls. The default is 50 milliseconds.

• RTCP Monitor Enabled – Controls sending copies of RTCP packet to a VoIP Monitoring Manager for audio quality monitoring.

• RTCP Monitor IP Address - The IP address of the RTCP monitor to which copies of RTCP packets should be sent.

• RTCP Monitor Port – The UDP port used by VoIP Monitoring Manager to receive copies of RTCP packets. Default UDP port is 5005.

• Station Authentication Enabled – This field controls whether or not the Avaya IR system uses VoIP station authentication when registering with the Gatekeeper.

• Avaya CM Name – A unique name up to twenty characters long. The default naming convention is CM#, where # is the card number currently being configured.

• Number of Ports – The number of ports/channels (IP Stations) that will be assigned to this VoIP card. The default value is 93 channels/ports. The maximum value depends on the number of available port licenses (Refer to Section 4.1)

• Avaya CM Version – Current major version number of Avaya Communication Manager (For Avaya Communication Manager R3.1 use the value 3.0.)

(24)

(25)

5. Repeat step 1 to administer the next virtual Avaya IR VoIP card. Assign number 7 in the “Card” field and click on the “Submit” button.

(26)

6. Assign the VoIP card parameters for Card 7 to use the CLAN board located in the Site 2 - G650 Media Gateway. Click the “Submit” button when complete.

(27)

8. Repeat step 1 to administer the next virtual Avaya IR VoIP card. Assign number 8 in the “Card” field and click on the “Submit” button.

(28)

9. Assign the VoIP card parameters for Card 8 to use the Processor Ethernet card on the S8500 Media Server located in Site 4. IP station registration to the LSP S8500 Media Server may occur only when the server is in active mode. Click the “Submit” button when complete.

(29)

11. To assign Avaya IR VoIP Channels to Avaya Communication Manager IP Stations, click on “Phone Number” under the “Voice Equipment” section. Then click on the “Assign” button.

12. Enter the IP Station range for the Main Office Avaya IR VoIP Channels in the “Phone

Number” fields, the VoIP channel range in the “Channel Number” fields, and the password

in the “VoIP H.323 MultiVantage Station Password” fields. The password must be equivalent to the “Security Code” on Page 1 of the “add station” Avaya Communication Manager command (Please refer to Section 3.3).

Note the following:

• To specify a range of telephone numbers and channels, the number of channels specified must match the number of telephone numbers specified.

• To specify a range of passwords, the number of passwords specified must match the number of telephone numbers and the number of channels specified. If all IP Stations share the same password, enter it in the first field only.

(30)

(31)

14. Refer to Step 12 and enter the parameters for Site 2 Avaya IR VoIP Channels.

(32)

16. Refer to Step 12 and enter the parameters for Site 4 Avaya IR VoIP Channels.

(33)

18. To activate the configuration changes, stop and then restart the voice system. Click on “Stop

Voice System” under the “System Control” section to stop the voice system.

Click on the “Submit” button. Avaya IR confirms the voice system has completely stopped. The beginning and end of the output is shown below.

(34)

19. To restart the voice system, click on “Start Voice System” under the “System Control” section. Click on the “Submit” button.

(35)

5. Verification Steps

5.1. General Verification Steps

Perform the following steps to test and verify the Avaya IR VoIP channels (IP Stations).

1. From the Avaya Communication Manager SAT terminal, issue the command “status station

xxxxx”, where xxxxx is the extension of the Avaya IR VoIP channel to verify that the IP

station is successfully registered. The “Service Start” field should display

“in-service/on-hook” and the “TCP Signal Status” field should display “connected”.

status station 20780 Page 1 of 5 GENERAL STATUS

Administered Type: 7434ND Service State: in-service/on-hook Connected Type: N/A TCP Signal Status: connected

Extension: 20780

Port: S00046 Parameter Download: not-applicable Call Parked? no SAC Activated? no

Ring Cut Off Act? no CF Destination Ext: Active Coverage Option: 1

EC500 Status: N/A Off-PBX Service State: N/A Message Waiting:

Connected Ports:

User Cntrl Restr: none HOSPITALITY STATUS Group Cntrl Restr: none Awaken at:

User DND: not activated Group DND: not activated Room Status: non-guest room

(36)

2. Go to Page 3 and verify the “IP Signaling”, “Node Name”, and “Network Region” information.

3. Repeat Steps 1 and 2 to verify each IP Station assigned to the Avaya IR individually. To view all currently Registered IP Stations, issue the command “list registered-ip-stations” and verify the information for the Avaya IR IP Stations.

Note: Avaya Communication Manager load balances CLAN board resources for IP station

registration and signaling when multiple boards are available within an IP Network Region. Therefore, the “Gatekeeper IP Address” for the particular CLAN board resource may be different from the “IP Card Address” parameter assigned when configuring the VoIP card in the Avaya IR system (Please refer to Section 4.2 - Avaya IR VoIP Channel Configuration).

status station 20780 Page 3 of 5 CALL CONTROL SIGNALING

Port: S00046

Switch IP IP Port Switch-end IP Addr:Port Set-end IP Addr:Port IP Signaling: 01B0217 10. 1. 2. 21 :1720 10. 1. 1. 54:61378 H.245:

Node Name: clan-1b02 sa-ir

Network Region: 1 1

Shared Port:

Switch IP IP Port Switch-end IP Addr:Port Set-end IP Addr:Port IP Signaling:

H.245: Node Name: Network Region:

list registered-ip-stations Page 1 REGISTERED IP STATIONS

Station Set Product Prod Station Net Orig Gatekeeper TCP

Ext Type ID Rel IP Address Rgn Port IP Address Skt 20001 4625 IP_Phone 2.500 10.1.2.102 1 10.1.2.25 y 20002 4625 IP_Phone 2.500 10.1.2.103 1 10.1.2.21 y 20780 7434ND IP_API_A 1.302 10.1.1.54 1 10.1.2.21 y 20781 7434ND IP_API_A 1.302 10.1.1.54 1 10.1.2.21 y 20782 7434ND IP_API_A 1.302 10.1.1.54 1 10.1.2.21 y 20783 7434ND IP_API_A 1.302 10.1.1.54 1 10.1.2.21 y 22001 4625 IP_Phone 2.500 10.2.2.101 2 10.2.2.21 y 22002 4622 IP_Phone 2.150 10.2.2.105 2 10.2.2.21 y 22780 7434ND IP_API_A 1.302 10.1.1.54 2 10.2.2.21 y 22781 7434ND IP_API_A 1.302 10.1.1.54 2 10.2.2.21 y 22782 7434ND IP_API_A 1.302 10.1.1.54 2 10.2.2.21 y 22783 7434ND IP_API_A 1.302 10.1.1.54 2 10.2.2.21 y 24021 4621 IP Phone 2.302 10.14.2.108 4 10.1.2.21 y

(37)

4. Using the Avaya IR Web Administration, click on “Display Equipment” under the “Voice

Equipment” section. View and verify that all assigned VoIP channels for the Main Office

(Channels 96 – 99) and Site 2 (Channels 100 – 103) locations are in the “Inserv” (in-service) state. Under normal “Sunny Day” conditions, the channels for Site 4 (Channels 104 – 107) should be in the “Foos” (facility out-of-service) state because the LSP S8500 Media Server is not active, and therefore not accepting IP station registrations.

(38)

5. To terminate a call to Avaya IR, a “Voice Service” must be assigned to the Avaya IR channels. Click on “Channel Services” under the “Voice Services” section. The resulting Web administration page is shown below.

(39)

6. There are two methods to administer the assignment of “Voice Services” to the Avaya IR channels:

1. Select the “Channel Range” that includes the channels to be administered. The Web page refreshes with to the selected channel range. Under the “Select” column, to administer the desired channel click the square to select it. Then, click on the “Assign

Selected” button. The screen is shown below. This will bring up the “Assign Services to Channels” Web page shown on the next page with the selected channel

range already entered in the “To Chan(s)” field. Select “avftst” for the “Service” and “Startup Service” fields for the test Voice Service. Click on the “Submit” button to complete the administration.

2. An alternative method is to click on the “Assign Selected” button without selecting a “Channel Range”. This will bring up the “Assign Services to Channels” Web page shown on the next page. Select “avftst” for the “Service” and “Startup Service” fields for the test Voice Service, and enter the channel range in the “To Chan(s)” field. Click on the “Submit” button to complete the administration.

Note:

• The “avftst” Voice Service is one of the Transaction Assembler Script (TAS) applications installed by default on the Avaya IR system for testing purposes.

(40)

8. Place a call using the Hunt Group Number (20591) assigned for the Avaya IR VoIP ports (refer to Section 3.4) from the Avaya IP Telephone (20001). Verify that the Avaya IR answers the call successfully.

9. From the Avaya Communication Manager SAT terminal, issue the command “status station

20001” which is the extension of Avaya IP Telephone. Go to Page 4 and verify the Audio

Channel information for the call.

status station 20001 Page 4 of 6 AUDIO CHANNEL

Port: S00007

Switch IP IP Port Other-end IP Addr :Port Set-end IP Addr:Port

G.711MU Audio: 10. 1. 1. 54 :8000 10. 1. 2.102:64262 Node Name: sa-ir

Network Region: 1 1 Audio Connection Type: ip-direct

Port: S00007 Shared Port: Product ID and Release: IP_Phone 2.500

H.245 Tunneled in Q.931? does not apply

Registration Status: registered-authenticated MAC Address: 00:04:0d:9b:5f:20

Native NAT Address: not applicable ALG - NAT WAN IP address: not applicable Authentication Type: DES-56-plus

(41)

10. Go to Page 5 and verify the Source Port to Destination Port Talk Path information for the call. Verify the assigned media encryption.

5.2. Fail-over Verification Tests

Use the verification steps illustrated in Section 5.1 to perform the following test procedures.

5.2.1. Loss of a CLAN

Perform the following procedure to test Avaya IR VoIP channels (IP station registration) and verify correct “Loss of CLAN” operation.

1. Verify that all Avaya IR VoIP channels (IP stations in Avaya Communication Manager) are “in-service” for normal operation.

2. Create a condition such that the CLAN board fails or looses network connectivity.

3. Verify that the Avaya IR VoIP channels (IP stations) assigned to this CLAN change to the “facility out of service” state.

4. Place a call using the Hunt Group Number (20591) assigned for the Avaya IR VoIP ports. The call should route from the PSTN to the Main Office.

5. Verify that the Avaya IR answers the call.

6. Place a call using the same Hunt Group Number (20591) with routing from the PSTN to Site 2.

7. Verify that the Avaya IR answers the call. 8. Restore the CLAN board used step 2.

9. Verify that the Avaya IR VoIP channels (IP stations) change to the “in-service” state can accept new calls.

5.2.2. Loss of Primary Servers

Perform the following procedure to test Avaya IR VoIP channels (IP station registration) and verify correct “Loss of Primary Servers” operation.

status station 20001 Page 5 of 6 SRC PORT TO DEST PORT TALKPATH

src port: S00010

S00010:TX:10.1.2.102:55624/g711u/20ms/aes S00046:RX:10.1.1.54:8000/g711u/20ms/aes

(42)

1. Verify that the Avaya IR VoIP channels (IP stations) are “in-service” for normal operation. The Avaya IR VoIP channels to Site 4 should be in the “facility out of service” state

provided that the Site 4 LSP Media Server in not active.

2. Create a condition such that both S8710 servers at the Main Office fail.

3. Verify that the Media Gateways at each location fail-over to the ESS servers at Site 2. 4. Verify the CLAN boards at the Main Office and Site 2 are “in-service”.

5. Verify Avaya IR VoIP channels (IP Stations) are “in-service” and can accept new calls.

5.2.3. Loss of Primary Servers and Site 2 WAN Link

Perform the following procedure to test Avaya IR VoIP channels (IP station registration) and verify correct “Loss of Primary Servers” operation.

1. Perform steps 1 through 5 from previous test scenario in Section 5.2.2. 2. Create a condition such that Site 2 looses connectivity to the WAN.

3. Verify that the Media Gateway at Site 4 registers to the local S8500 LSP Media Server. 4. Verify the Avaya IR VoIP channels (IP stations) assigned to the CLANs located in the Main

Office and Site 2 change to the “facility out-of-service” state.

5. Verify the Avaya IR VoIP channels (IP stations) assigned to the Processor Ethernet of Site 4 LSP S8500 Media Server are “in-service”.

6. Place a call using the Hunt Group Number (20591) assigned for the Avaya IR VoIP ports. The call should route from the PSTN to Site 4.

7. Verify that the Avaya IR answers the call.

8. Restore the Primary Servers and the WAN connectivity to Site 2.

9. Verify that the Media Gateways at each location register with the Primary Servers as in normal “Sunny Day” operation.

10. Verify that all Avaya IR VoIP channels (IP stations) are “in-service” for normal operation and can accept new calls.

11. Verify the Avaya IR VoIP channels (IP stations) assigned to the Processor Ethernet of Site 4 LSP S8500 Media Server are now in “facility out-of-service” state.

(43)

6. Conclusion

These Application Notes illustrated an example of the configuration steps necessary to interconnect an Avaya Interactive Response (IR) system with multiple virtual VoIP cards to Avaya

Communication Manager utilizing different Gatekeeper resources for IP station registration. Multiple Gatekeeper Support is an Avaya IR VoIP feature that enhances the interconnection capability to Avaya Communication Manager. In addition, these Application Notes covered various call flow scenarios to illustrate redundancy and survivability examples for VoIP interconnection between Avaya IR and Avaya Communication Manager.

7. References

Product documentation for Avaya products may be found at http://support.avaya.com.

1. “Avaya Interactive Response (IR), Release 2.0, Documentation CD-ROM, Issue 1.0, April 2006”, Comcode: 700397003

2. “Avaya Communications Manager Network Region Configuration Guide”, COMPAS ID: 103244

(44)

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 [email protected]