Qsig avaya-cisco

Tech Note: Configuring Q.SIG PRI trunk between Cisco Call Manager and Avaya S8700/G650 with Cisco Unity Voice Mail integration

The objective of this document is to provide Cisco’s customers and business partners with exact steps to configure Q.SIG PRI trunks between the Cisco Call Manager and the Avaya S8700/G650. Also, it details steps on how to add Cisco Unity on the Cisco Call Managerplatform to provide voice mail support for both Cisco and Avaya IP phones. This is particularly important for situations where IPPBX interoperability and voice mail integration are required. The Avaya configuration screen captures have been done using the standard Emulation tool. As an alternative, the user can also use the Avaya Site Administration (ASA) tool for configuration tasks on the AvayaS8700/G650. The output display is the same in both cases. This IP-PBX interoperability and voice mail integration document is intended for external use.

The Avaya IP-PBX system used was the Avaya S8700/G650 running Avaya Communication Manager 2.0. The Q.SIG feature set comes standard with this software version. The AVAYA IP Phones used were the 4610SW and 4620 running Phone Firmware Version 2.01. Onthe Cisco side, Cisco Call Manager 4.1.2 was used to control the 3745 MGCP gateway with the NM-HDV module, running IOS version 12.2.15ZJ3. Tests were also repeated with IOS version 12.3.8.T5. Cisco Unity running version 4.0(4) SR1 was used for the voice mail integration testing.

The next sections provide procedures and screen captures of how to configure the Q.SIG trunk between an AvayaS8700/G650 running Avaya Communication Manager 2.0 and a Cisco Call Manager platform running Call Manager version 4.1(2) with the Cisco 3745 MGCP device providing the physical ISDN PRI connection to the Avaya S8700/G650.

! "#$ 1. Login to the S8700 server. Make sure that all the necessary Q.SIG features are enabled on the S8700 server by running the “display system-parameters customer” feature.2. Configure the DS-1 card for Q.SIG PRI

3. The next step is to configure a trunk group. Type “add trunk-group #” where # is the desired trunk group. The next 3 screen captures relate to the trunk configuration. Once the trunk group is created, add the 23 DS0 channels to the group. The following is an example of the port assignment: 01A0901 would mean: Gateway# 1, Cabinet A, Slot# 9, DS0channel# 1.

4. Add signaling group and point to the trunk group created above.

5. Next, add a route pattern and point it to the signaling group. In this example, the route pattern 4 points to signaling group# 1 that was created in the previous step.

6. Finally add an entry into the AAR table to use the route pattern above to route calls. In this example, calls to Cisco IP phone extension4XXX are using the AAR table entry starting with 4, which in turn points to route pattern# 4.

7. Last step is to ensure caller id is enabled on each IP phone to send calling party name.

% 1. Under Service parameters, make sure that the Start Path Replacement Minimum and Maximum time values are set appropriately to prevent any issues (such as hair pinning). The next two screen captures relateto the Q.SIG Service Parameters setting:

2. Add Cisco 3745 as an MGCP gateway and configure the NM-HDV T-1 module for Q.SIG PRI. The next 5 screen captures relate to this configuration.

3. As a final step, create a Call Manager pickup group to provide path proposal extension to the PBX. Make sure that the call pickup number is also entered into the Path PINX Replacement ID Serviceparameter (Look at Step# 1). Also, the Avaya system needs a route pattern to route to the pickup group.

& '$

(

Included below is the show version and show running-configuration on the Cisco 3745 MGCP device. Controller T1 1/0 on the Cisco 3745 is connected to the Avaya S8700/G650 DS1 PRI card. Q.SIG signaling is configured on PRI link between the Cisco 3745 and the Avaya S8700/G650....