Configuring Cisco AS5400 Universal Gateway with Avaya Voice Portal and Avaya SIP Enablement Services Issue 1.0

Avaya Solution & Interoperability Test Lab Configuring Cisco AS5400 Universal Gateway with Avaya Voice Portal and Avaya SIP Enablement Services – Iss...
14 downloads 2 Views 1MB Size
Avaya Solution & Interoperability Test Lab

Configuring Cisco AS5400 Universal Gateway with Avaya Voice Portal and Avaya SIP Enablement Services – Issue 1.0

Abstract These Application Notes describe the configuration steps required to enable routing of calls between Avaya Voice Portal and the PSTN through a SIP infrastructure consisting of Avaya SIP Enablement Services and the Cisco AS5400 Universal Gateway. This solution allows Avaya Voice Portal to receive calls from the PSTN and transfer calls to the PSTN. The Cisco AS5400 interfaces to the PSTN via a T1/ISDN interface.

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

1 of 26 Cisco-AS5400

1. Introduction These Application Notes describe the configuration steps required to enable calls between Avaya Voice Portal and the PSTN through a SIP infrastructure consisting of Avaya SIP Enablement Services (SES) and the Cisco AS5400 Universal Gateway (also referred to as “Cisco AS5400”). This solution allows Avaya Voice Portal to receive calls from the PSTN and transfer calls to the PSTN. The Cisco AS5400 interfaces to the PSTN via a T1/ISDN interface. Refer to Figure 1 for an illustration of the test configuration. The following features were covered during the interoperability testing of Avaya Voice Portal, Avaya SIP Enablement Services, and Cisco AS5400 in a SIP environment: ƒ ƒ ƒ ƒ ƒ ƒ ƒ

Basic calls from PSTN to Avaya Voice Portal Call transfers from Avaya Voice Portal to PSTN, including blind, supervised, and bridged transfers DTMF tones / RFC 2833 support Sending UUI from Avaya Voice Portal to PSTN G.711 mu-law and G.711 a-law codec support T1/ISDN network interface between Cisco AS5400 and simulated PSTN Failure recovery

Avaya SIP Enablement Services (192.45.122.133) Cisco AS5400 VoIP Gateway (142.16.57.2)

T1

Simulated PSTN

Voice Portal Management System (192.45.122.130)

Media Processing Platform 1 (192.45.122.131)

x32225 x32243

Media Processing Platform 2 (192.45.122.132) Avaya Voice Portal

Application Server (192.45.60.61)

Nuance Speech Server (192.45.122.52)

Figure 1: SIP-to-PSTN Interworking with the Cisco AS5400 Universal Gateway

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

2 of 26 Cisco-AS5400

1.1.

Equipment and Software Validated

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

Software

Avaya Voice Portal ƒ Voice Portal Management System (VPMS) ƒ Media Processing Platform (MPP)

4.0.0.0.2901 4.0.0.1.0005

Avaya SIP Enablement Services

4.0.0.0-033.6

Cisco AS5400 Universal Gateway

12.4(17)

Nuance Speech Server ƒ Nuance OpenSpeech Recognizer ƒ Nuance RealSpeak

3.0 4.0

Application Server – HTTP Server running on Windows 2003 Server

JAO; Reviewed: SPOC 2/12/2008

Service Pack 2

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

3 of 26 Cisco-AS5400

2. Configure Avaya Voice Portal This section covers the administration of Avaya Voice Portal. Avaya Voice Portal configuration required: ƒ ƒ ƒ ƒ ƒ • ƒ

Importing certificates for TLS authentication Configuring a SIP connection Adding MPP servers Configuring the VoIP audio format (mu-law or a-law) Adding a speech server Adding applications Starting the MPP servers

Avaya Voice Portal is configured via the Voice Portal Management System (VPMS) web interface. To access the web interface, enter http:///VoicePortal as the URL in an Internet browser, where is the IP address of the VPMS. Log in using the Administrator user role. The screen shown in Figure 2 is displayed. Note: All of the screens in this section are shown after Avaya Voice Portal had been configured. In addition, the navigation steps to each screen are displayed at the top of each screen.

Figure 2: VPMS Main Screen

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

4 of 26 Cisco-AS5400

Install Certificate. In this configuration, Avaya Voice Portal used TLS authentication over the SIP interface to Avaya SIP Enablement Services. To install the certificate for TLS authentication, navigate to the Certificates page and select the Root Certificate tab. Specify the directory path where the certificate is located and the password, and then click Install. Figure 3 shows a certificate that has already been installed.

Figure 3: Certificates Configure the SIP Connection. To configure a SIP connection, navigate to the VoIP Connections screen and then click on the SIP tab. The SIP tab is displayed as shown in Figure 4. Configure the parameters as described below: ƒ ƒ ƒ ƒ ƒ ƒ ƒ

Select TLS as the Proxy Transport Specify the IP address of Avaya SIP Enablement Services in the Proxy Server Address field Set the Proxy Server Port and Listener Port fields to ‘5061’ for TLS Set the SIP Domain (e.g., avaya.com) Set the Maximum Simultaneous Calls and Number of Outbound Calls Allowed. In this example, a maximum of 40 calls is supported between two MPP servers. Under the SIP Proxy Certificate section, click on the Trust this Certificate checkbox (not shown in the screen below) Accept the default values for the other fields

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

5 of 26 Cisco-AS5400

Figure 4: SIP Connection

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

6 of 26 Cisco-AS5400

Add the MPP Servers. Add the two MPP servers1 by navigating to the MPP Servers screen. In the MPP Server configuration page, specify a descriptive name and the Host Address of each MPP server. Also, specify the Maximum Simultaneous Calls supported by each MPP server. Figure 5 shows the configuration for the first MPP server. Repeat these steps for the second MPP server.

Figure 5: MPP Server

1

Although two MPP servers were used in this configuration, only one MPP is required when deploying an Avaya Voice Portal system. JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

7 of 26 Cisco-AS5400

Configure the VoIP Audio Format. The VoIP Audio Format for the MPP servers is configured in the VoIP Settings screen. The Cisco AS5400 supports both G.711 mu-law and G.711 a-law. The MPP Native Format field in Figure 6 is set to audio/basic for mu-law.

Figure 6: VoIP Settings

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

8 of 26 Cisco-AS5400

Add an ASR Server. To configure the automatic speech recognition (ASR) server, click on Speech Servers in the left pane, select the ASR tab, and then click Add. Figure 7 shows the screen after the ASR server has already been configured. Set the Engine Type to the appropriate value. In this configuration, a Nuance ASR server was used so the engine type was set to Nuance. Set the Network Address field to the IP address of the speech server and select the desired Languages to be supported. The other fields were set to their default values.

Figure 7: ASR Speech Servers

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

9 of 26 Cisco-AS5400

Add a TTS Server. To configure the text-to-speech (TTS) server, click on Speech Servers in the left pane, select the TTS tab, and then click Add. Figure 8 shows the screen after the TTS server has already been configured. Set the Engine Type to the appropriate value. In this configuration, a Nuance TTS server was used so the engine type was set to Nuance. Set the Network Address field to the IP address of the speech server and select the desired Languages to be supported. The other fields were set to their default values.

Figure 8: TTS Server

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

10 of 26 Cisco-AS5400

Add an Application. On the Applications page, add a Voice Portal application. Specify a Name for the application, set the MIME Type field to the appropriate value (e.g., VoiceXML), and set the VoiceXML URL field to point to a VoiceXML application on the application server. Next, specify the type of ASR and TTS servers to be used by the application and the called number that invokes the application. The Applications screen is shown in Figure 9.

Figure 9: Applications

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

11 of 26 Cisco-AS5400

Start the MPP Servers. Start the MPP servers from the MPP Manager page shown in Figure 10. Select each MPP and then click the Start button. The Mode of each MPP should be Online and the State should be Running.

Figure 10: MPP Manager

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

12 of 26 Cisco-AS5400

3. Configure Avaya SIP Enablement Services This section covers the administration of Avaya SIP Enablement Services with a focus on configuring: ƒ ƒ ƒ ƒ

an Adjunct System for Avaya Voice Portal an Application ID for the Avaya Voice Portal application a Host Address Map for routing calls to the PSTN a Trusted Host for the Cisco AS5400

Initial configuration of Avaya SIP Enablement Services, including the Host and Server Configuration screens, are not included in these Application Notes. Refer to [1] for more information. In this configuration, the SIP domain was avaya.com. Avaya SIP Enablement Services is configured via an Internet browser using the Administration web interface. To access the Administration web interface, enter http:///admin as the URL in the Internet browser, where is the IP address of Avaya SES. Log in with the appropriate credentials and select the Launch Administration Web Interface link. Note: All the configuration screens in this section were captured after they were already configured. Configuration data is displayed in edit screens instead of add screens.

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

13 of 26 Cisco-AS5400

Add Adjunct System. Provision an adjunct system for the VPMS. Provide a System Name and select the Avaya SES with which this adjunct system will be integrated. Figure 11 displays the Adjunct System page configured for the VPMS.

Figure 11: Adjunct System

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

14 of 26 Cisco-AS5400

Add Adjunct Servers. Add an adjunct server, associated with the adjunct system configured in Figure 11, for each MPP server. Specify the Server Name, Server ID, Link Type, and the Server IP Address. In this configuration, TLS is enabled between Avaya Voice Portal and Avaya SES. Figure 12 shows the configuration for one MPP server. Repeat this configuration for the other MPP server. Note: To install the certificates for TLS authentication, navigate to the Trusted Certificates page and import the certificate. Refer to [1] for more information on installing SIP certificates.

Figure 12: Adjunct Server

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

15 of 26 Cisco-AS5400

Add Applications IDs. Add Application IDs for the applications configured on Avaya Voice Portal in Figure 9. This Application ID is associated with the adjunct system configured in Figure 11. When the digits of an incoming call matches the Application ID field in this form, Avaya SES will route the call to the adjunct system. Figure 13 displays the Application ID screen.

Figure 13: Application ID

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

16 of 26 Cisco-AS5400

In this configuration, there were two ways to call users on the PSTN, dialing a 5-digit number or an 11-digit number. The configuration of each address map is provided below. Add a Host Address Map. To transfer calls from Avaya Voice Portal to the PSTN, 5-digit numbers beginning with ‘32’ were dialed. To route SIP calls to the PSTN through the Cisco AS5400, a Host Address Map was required. In this example, the host address map entry was configured as shown in Figure 16. The Pattern field in the Host Map Entry was set to ^sip:32[0-9]{3}. The Host Contact shown in Figure 15 specified the IP address of the Cisco AS5400 and the transport protocol and port.

Figure 14: Host Map Entry

Figure 15: Host Contact

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

17 of 26 Cisco-AS5400

The List Host Address Map screen in Figure 16 summarizes the configuration of the Host Map Entry and Host Contact for using 5-digit dialing to the PSTN.

Figure 16: Host Address Map for 5-Digit Dialed Number To transfer calls from Avaya Voice Portal to the PSTN using 11-digit numbers, including prefix mark 1 and the area code, the following host map may be configured. In this example, the host address map entry was configured as shown in Figure 17. The Pattern field in the Host Map Entry was set to ^sip:1732[0-9]{7}. The Host Contact specified the IP address of the Cisco AS5400 and the transport protocol and port.

Figure 17: Host Address Map for 11-Digit Dialed Number

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

18 of 26 Cisco-AS5400

To route calls from the PSTN to Avaya Voice Portal, 7-digit numbers beginning with ‘852’ were received by Avaya SES. These calls were routed directly from Avaya SES to Avaya Voice Portal because Application IDs starting with ‘852’ were associated with Avaya Voice Portal. Avaya SES matched the incoming 7-digit number to an existing application ID. No address maps were required. Application IDs are shown in Figure 13. Add a Trusted Host. Configure the Cisco AS5400 as a trusted host so that Avaya SES does not challenge incoming SIP requests from the Cisco AS5400. Navigate to the Trusted Host page and configure the IP address of the Cisco AS5400 and provide a descriptive comment. The Trusted Host page is shown in Figure 18.

Figure 18: Trusted Host

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

19 of 26 Cisco-AS5400

4. Configure Cisco AS5400 Universal Gateway This section provides the configuration of the Cisco AS5400 Universal Gateway. Refer to [2] for a description of the Cisco AS5400 commands. isdn switch-type primary-ni isdn voice-call-failure 0 voice service voip fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none sip min-se 240 voice class codec 1 codec preference 1 g711ulaw controller T1 7/0 description To_PSTN framing esf linecode b8zs pri-group timeslots 1-24 interface FastEthernet0/0 ip address 142.16.57.2 255.255.255.0 interface Serial7/0:23 no ip address encapsulation hdlc isdn switch-type primary-5ess isdn timer T310 40000 isdn incoming-voice modem isdn T309-enable no fair-queue no cdp enable voice-port 7/0:D dial-peer voice 1732 pots description To_PSTN service session destination-pattern 1732....... direct-inward-dial port 7/0:D forward-digits all prefix 9 dial-peer voice 32 pots description To_PSTN service session destination-pattern 32... port 7/0:D forward-digits all dial-peer voice 852 voip description To Avaya SES - Voice Portal destination-pattern 852.... progress_ind setup enable 1 voice-class codec 1 session protocol sipv2 session target ipv4:192.45.122.133:5060 session transport udp dtmf-relay rtp-nte

Figure 19: Cisco AS5400 Configuration JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

20 of 26 Cisco-AS5400

5. Verification Steps This section provides the verification steps that may be performed to verify that Avaya Voice Portal can establish calls to the PSTN through the Cisco AS5400. 1. From the VPMS web interface, verify that the MPP servers are online and running in the System Monitor page shown in Figure 20.

Figure 20: System Monitor

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

21 of 26 Cisco-AS5400

2. From the VPMS web interface, verify that the ports on the MPP servers are in-service in the Port Distribution page shown in Figure 21.

Figure 21: Port Distribution

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

22 of 26 Cisco-AS5400

3. From the Cisco AS5400, use the show controller command to verify that the controller is up. HCC_AS5400# show controller t1 7/0 T1 7/0 is up. Applique type is Channelized T1 Cablelength is long gain36 0db Description: To_PSTN No alarms detected. alarm-trigger is not set Soaking time: 3, Clearance time: 10 AIS State:Clear LOS State:Clear LOF State:Clear Version info of slot 7: HW: 519, PLD Rev: 1 Framer Version: 0x9

Figure 22: Controller Status 4. From the Cisco AS5400, use the show interface serial command to verify that the serial interface is up. HCC_AS5400# show interface serial 7/0:23 Serial7/0:23 is up, line protocol is up (spoofing) Hardware is DSX1 MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Last input 00:00:01, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 31079 packets input, 130576 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 5 abort 31103 packets output, 130648 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 unknown protocol drops 0 output buffer failures, 0 output buffers swapped out 1 carrier transitions Timeslot(s) Used:24, Transmitter delay is 0 flags

Figure 23: Serial Interface Status

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

23 of 26 Cisco-AS5400

5. From the Cisco AS5400, use the show isdn status command to verify that the ISDN link is established. HCC_AS5400# show isdn status Global ISDN Switchtype = primary-ni ISDN Serial7/0:23 interface dsl 0, interface ISDN Switchtype = primary-5ess Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 0 CCBs = 0 The Free Channel Mask: 0x807FFFFF Number of L2 Discards = 0, L2 Session ID = 11 Total Allocated ISDN CCBs = 0

Figure 24: ISDN Status 6. From a phone on the PSTN, place a call to Avaya Voice Portal. Verify that the call is established successfully and that the proper greeting is provided. Transfer the call to another user on the PSTN. Verify that two-way audio is established between the two PSTN users.

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

24 of 26 Cisco-AS5400

6. Support Cisco technical support is available at http://www.cisco.com. Alternative support options are described at http://www.cisco.com/en/US/support/index.html.

7. Conclusion These Application Notes describe the configuration steps required to allow incoming and outgoing calls between Avaya Voice Portal and the PSTN through a SIP infrastructure consisting of Avaya SIP Enablement Services and the Cisco AS5400 Universal Gateway. The following issues were identified while testing the Cisco AS5400 with an ISDN interface to the simulated PSTN: ƒ ƒ

When calling a busy PSTN user or specifying an invalid number during a blind or supervised transfer, the Cisco AS5400 returns a SIP NOTIFY message with 503: Service Unavailable. Cisco AS5400 does not forward User-to-User Info (UUI) received from Avaya Voice Portal over the ISDN interface to the PSTN.

8. References This section references the product documentation that is relevant to these Application Notes. [1] Installing and Administering SIP Enablement Services, Document 03-600768, Issue 4.0, May 2007, available at http://support.avaya.com. [2] Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide, Document 0L-3418-02 B0, available at http://www.cisco.com.

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

25 of 26 Cisco-AS5400

©2008 Avaya Inc. All Rights Reserved.

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]

JAO; Reviewed: SPOC 2/12/2008

Solution & Interoperability Test Lab Application Notes ©2008 Avaya Inc. All Rights Reserved.

26 of 26 Cisco-AS5400

Suggest Documents