Job aid, replacing the media server or its hard drive (10 pages)
Summary of Contents for Avaya S8300
Page 1
Avaya and Cisco Telephones - Issue 1.0 Abstract These Application Notes describe a configuration, including, Avaya Communication Manager, a Cisco 2811 Gatekeeper, and Cisco CallManager that was verified for a customer proof of concept request. In this configuration, Avaya Communication Manager and Cisco CallManager are registered with the Cisco 2811 Gatekeeper, which provides call control between Avaya Communication Manager and Cisco CallManager.
Page 2
Figure 1 depicts the network configuration utilized for these Application Notes. In Location A in Figure 1, the Avaya G350 Media Gateway with S8300 Server provides both H.323 Gateway (GW) and Gatekeeper (GK) functionality. In Location B, the Cisco 2811 access router is configured as an H.323 Gatekeeper, and the Cisco CallManager is registered with it.
The following equipment and software were used for the sample configuration provided: Network Component Software Version Avaya Communication Manager 3.1.2 (634) S8300 Server with G350 Media Gateway Avaya G350 Media Gateway 26.31 Avaya 9600 IP Telephone (H.323) 1.2.1 Avaya 4620 IP Telephone (H.323) Cisco 2811 Gatekeeper 12.4(2)T5 (IP Voice)
Communication Manager. It is assumed that appropriate license and authentication files have been installed on the S8300 Server. It is also assumed that the network IP address on the S8300 Server has been configured to 22.1.1.22/24 and the IP address on the G350 GW has been configured to 22.1.1.23/24.
Page 5
Calls above the specified limit will not be permitted, and may be re-routed to a different path. The bandwidth usage is based on the packet size and codec selection. Avaya supports IP Call Admission Control via Bandwidth Limits (CAC-BL). Codec set 2 is used for calls between regions 1 and 2.
Page 6
Calls above the specified limit will not be permitted, and may be re-routed to a different path. The bandwidth usage is based on the packet size and codec selection. Avaya supports IP Call Admission Control via Bandwidth Limits (CAC-BL). Codec set 2 is used for calls between regions 2 and 1.
Page 7
Cisco 2811 GK, a signaling group for outbound traffic must be configured. Note that the IP address of the Avaya S8300 Server (procr) functions as an IP address for both H.323 GW and Use the command add signaling-group <group number> to create a signaling group. The Near- End Node Name and Far-end Node Name are configured to the procr and Cisco-GK respectively.
Note that Codeset to Send Display must be configured to 0 in order for the Cisco GW to accept the Q.931 call setup message from the Avaya Media Gateway. add trunk-group 20 Page 2 of Group Type: isdn TRUNK PARAMETERS...
Page 10
4: T00089 5: T00090 When a call is placed from Avaya Communication Manager, the called number is routed (by appropriate routing, e.g., UDP, AAR/ARS, etc.) to the Cisco 2811 Gatekeeper via trunk group 20. The Cisco 2811 Gatekeeper will send the call setup message to the appropriate gateway, for these Application Notes, Cisco CallManager.
Page 11
To reduce the configuration required, the Far-end Node Name can be left unspecified, or an inbound signaling group can be configured for each GW from which Avaya Communication Manager should accept calls. The following screen shows the configuration for inbound signaling group 21.
3.4. Configuring Dial Plan and Caller ID on Avaya Communication Manager Uniform Dialing Plan (UDP) and Automated Alternate Routing (AAR) are used for the call routing. The configurations in this section are for demonstration only. Use the command display system-parameters customer-options to verify that Uniform Dialing Plan is set to y.
Page 15
The following are the annotated Cisco 2811 Gatekeeper configuration. A Gatekeeper will forward the LRQ from Avaya CM and Cisco CallManager when the LRQ forwarding is enabled on the GK. To enable a gatekeeper to forward LRQ messages, use the lrq forward-queries command in gatekeeper configuration mode.
Page 18
Regions are used for codec selection. In these Application Notes, two regions are used. The default region is used for Location B and a new region, named Avaya, is created for Location A. To save bandwidth on WAN link, codec G.729 is used between these two regions. Intra-region calls will use codec G.711 ulaw.
Page 21
Cisco CallManager will use this default device pool. A new device pool, named avaya, will be created for Avaya S8300 Server with G350 Media Gateway in Location A. The purpose of creating a new device pool is to use different regions defined in previous section to select different codec.
Page 22
• Enter avaya as Device Pool Name. • Use drop-down menu to select avaya as Region. This will put this device pool into region avaya, which will use G.729 codec for calls to other region. • Use drop-down menu to select 1-SampleAudioSource for Network Hold MOH Audio Source.
Page 24
• Enter Trunk-to-Gatekeeper as Device Name • Select avaya for Device Pool • Check the box for Wait for Far End H.245 Terminal Capacity Set • Check the box for Enable Inbound FastStart SZ; Reviewed: Solution & Interoperability Test Lab Application Notes...
Signaling Type: facility associated signaling Group State: in-service • Make a call from extension 61000 (Cisco CallManager phone) to extension 4555 (Avaya IP telephone). Use the command show gatekeeper call from the Cisco 2811 Gatekeeper and verify that this is a gatekeeper controlled call. Note that bandwidth (BW) is shown 16 (Kbps), which is the VoIP call with G.729 codec.
Native NAT Address: not applicable ALG - NAT WAN IP address: not applicable Authentication Type: DES-56-plus • Page 6 shows the same call from S8300 Server VoIP engine (22.1.1.1) to a Cisco phone (60.1.1.100) using codec g729. status station 4555...