|
Table Of Contents
Calling Name and Number Feature
Configuring the Alcatel 4400 PBX
Configure "ISO Function" System Parameters
Configure Digital Access Options
Configuring CCM—6608-E1 Gateway Configuration
Enbloc Route Pattern Configuration
Overlap Sending Route Pattern Configuration
Cisco Catalyst 6000 Switch Configuration
Application Note
Alcatel 4400 Rel3.2 PBX with Cisco CallManager (CCM) Using 6608-E1 QSIG Protocol as MGCP Gateway
This application note illustrates connectivity for Alcatel 4400 Release 3.2 PBX with Cisco CallManager using Cisco 6608-E1 QSIG as MGCP Gateway.
Introduction
Key attributes of the network environment used for this application note:
•The network topology diagram shows the test set-up for end-to-end interoperability with the Cisco CallManager (CCM) connected to the PBX via 6608-E1 QSIG link as MGCP Gateway.
•Connectivity is achieved by using the PRI ISO QSIG E1 protocol type on the MGCP gateway and ABC-F (ISO version) as protocol type on the Alcatel 4400 PBX.
•Basic Calls worked fine in both directions with Calling/Connected Name and Calling Number features support.
•Alcatel 4400 PBX does not honor Connected Number Identification Presentation feature. Alcatel phone does not display Connected Number even though CCM is sending the information in the connect message.
•Call Forwarding did not work when the IP phone calls an Alcatel phone that is setup to forward to another Alcatel phone.
Network Topology
Figure 1
Network Topology or Test Setup
Limitations
Calling Name and Number Feature
When calling from Alcatel digital phone to Cisco 7960 IP phone, the Cisco IP phone displays Calling Name and Number when the call is answered. Alcatel phone however displays connected Name only, No connected Number when the call is answered. Alcatel does not honor Connected Number Identification Presentation QSIG service even though CCM is sending the Connected Number information in the connect message.
CCM Seaview release does not support sending Alerting Name or Busy Name Identification information.
Call Forwarding
Calls did not complete when the IP phone calls an Alcatel phone that is setup to forward to another Alcatel phone. Alcatel in this case sends Facility IE for 'CallRerouting'. Since CCM3.3 Seaview release does not support CallRerouting, the call is not completed.
System Components
Hardware Requirements
Cisco Hardware:
•Cisco Cat6K switch with 6608-E1 Gateway
•Cisco CM 3.3
Alcatel 4400 PBX Hardware:
•PRA2, 3BA23076- E1 PRI/QSIG
Software Requirements
Alcatel: PBX Software version 3.2
Cisco: Cisco CM 3.3
Features
Key features supported:
•Calling Name Identification Presentation
•Calling Number Identification Presentation
•Calling Number Identification Restriction
•Connected Name Identification Presentation
•Connected Number Identification Presentation
•Honor Calling/Connected Name Identification Restriction
•Honor Calling/Connected Number Identification Restriction
•Key features not supported:
•Sending Alerting Name Identification
•Sending Busy Name Identification
•Sending Calling/Connected Name Identification Restriction
•Sending Connected Number Identification Restriction
•Updating Connected Number on Alcatel phone for Basic Calls
•Updating Connected Name and Number for Call Transfers
•Updating Connected Name and Number for Call Forwarding
Configuring the Alcatel 4400 PBX
Configure in the following sequence:
1. "Configure "ISO Function" System Parameters" on page 4
2. "Configure Board" on page 5
3. "Configure Digital Access Options" on page 10
4. "Configure Trunk Group" on page 12
5. "Configure Trunk Detail" on page 13
6. "Configure T2 Access" on page 15
Configure "ISO Function" System Parameters
Command:
\compidea\System::1\Other System Param::1
Configure Board
Note: Interface type must be set to PRA2
Command:
\compidea\Shelf::0\Board::4
Configure Digital Access Options
Note: Network mode must be set to Yes for (Master/Network) or No- (Slave/User); Access Type must be set to T2.
Command:
\compidea\Shelf::0\Board::4\Digital Access::0
Configure Trunk Group
Note: Q931 signal variant is used to set the protocol type to ABC-F
Command:
\compidea\Trunk Groups::1
Configure Trunk Detail
Command: \compidea\Trunk Groups::1\Trunk Group::1
Configure T2 Access
Command:
\compidea\Trunk Groups::1\T2/T1/T0 Access::0-4-0
Configuring CCM—6608-E1 Gateway Configuration
Enbloc Route Pattern Configuration
Overlap Sending Route Pattern Configuration
References
Alcatel 4400 Rel4.2 PBX with CCM using 6608-E1 QSIG protocol as MGCP Gateway (Application Note)
Appendix A
CCM Software release:
Alcatel 4400 Software Release
Command:
\compidea\node
Cisco Catalyst 6000 Switch Configuration
Console> (enable) sh version
WS-C6506 Software, Version NmpSW: 6.1(4)
Copyright (c) 1995-2001 by Cisco Systems
NMP S/W compiled on May 15 2001, 12:27:20
System Bootstrap Version: 5.3(1)
Hardware Version: 2.0 Model: WS-C6506 Serial #: TBA04110341
Mod Port Model Serial # Versions
--- ---- ------------------- ----------- --------------------------------------
1 2 WS-X6K-SUP1A-2GE SAD041504XL Hw : 3.1
Fw : 5.3(1)
Fw1: 5.1(1)CSX
Sw : 6.1(4)
Sw1: 6.1(4)
WS-F6K-PFC SAD0413097K Hw : 1.1
3 48 WS-X6248-RJ-45 SAD04150CK1 Hw : 1.2
Fw : 5.1(1)CSX
Sw : 6.1(4)
5 8 WS-X6608-E1 SAD043300AJ Hw : 1.1
Fw : 5.4(2)
Sw : 6.1(4)
HP1: D00403030007; DSP1: D005b033 (3.6.
33)
HP2: D00403030007; DSP2: D005b033 (3.6.
33)
HP3: D00403030007; DSP3: D005B033 (3.6.
33)
HP4: D00403030007; DSP4: D005B033 (3.6.
33)
HP5: C00103010007; DSP5: C002E031 (3.3.
2)
HP6: C00103010007; DSP6: C002E031 (3.3.
2)
HP7: C00103010007; DSP7: C002E031 (3.3.
2)
HP8: C00103010007; DSP8: C002E031 (3.3.
2)
DRAM FLASH NVRAM
Module Total Used Free Total Used Free Total Used Free
------ ------- ------- ------- ------- ------- ------- ----- ----- -----
1 65408K 43645K 21763K 16384K 5327K 11057K 512K 245K 267K
Uptime is 199 days, 22 hours, 13 minutes
Console> (enable)
Console> (enable) sh module
Mod Slot Ports Module-Type Model Sub Status
--- ---- ----- ------------------------- ------------------- --- --------
1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok
3 3 48 10/100BaseTX Ethernet WS-X6248-RJ-45 no ok
5 5 8 E1 WS-X6608-E1 no ok
Mod Module-Name Serial-Num
--- ------------------- -----------
1 SAD041504XL
3 SAD04150CK1
5 SAD043300AJ
Mod MAC-Address(es) Hw Fw Sw
--- -------------------------------------- ------ ---------- -----------------
1 00-d0-d3-37-f9-8e to 00-d0-d3-37-f9-8f 3.1 5.3(1) 6.1(4)
00-d0-d3-37-f9-8c to 00-d0-d3-37-f9-8d
00-01-63-af-5c-00 to 00-01-63-af-5f-ff
3 00-01-97-4a-10-30 to 00-01-97-4a-10-5f 1.2 5.1(1)CSX 6.1(4)
5 00-01-64-12-22-80 to 00-01-64-12-22-87 1.1 5.4(2) 6.1(4)
Mod Sub-Type Sub-Model Sub-Serial Sub-Hw
--- ----------------------- ------------------- ----------- ------
1 L3 Switching Engine WS-F6K-PFC SAD0413097K 1.1
Console> (enable)
Console> (enable) sh port 5/1
Port Name Status Vlan Duplex Speed Type
----- ------------------ ---------- ---------- ------ ----- ------------
5/1 connected 1 full 2.048 E1
Port DHCP MAC-Address IP-Address Subnet-Mask
-------- ------- ----------------- --------------- ---------------
5/1 enable 00-01-64-12-22-80 10.10.10.104 255.255.255.0
Port Call-Manager(s) DHCP-Server TFTP-Server Gateway
-------- ----------------- --------------- --------------- ---------------
5/1 10.10.10.1 10.10.10.1 10.10.10.1 10.10.10.1
Port DNS-Server(s) Domain
-------- ----------------- -------------------------------------------------
5/1 - -
Port CallManagerState DSP-Type
-------- ---------------- --------
5/1 registered C549
Port NoiseRegen NonLinearProcessing
----- ---------- -------------------
5/1 enabled enabled
Port Trap IfIndex
----- -------- -------
5/1 disabled 66
Console> (enable)
Test Configuration
Figure 2
Test Configuration Diagram
As shown in Figure 2, an Alcatel 4400 PBX was connected via an ISDN E1 PRI QSIG link to a Cisco 6608-E1 Gateway, which in turn, was connected to an Ethernet switch. The interoperability testing involved Layers 1, 2 and 3 on the ISDN PRI QSIG link between a Cisco 6608-E1 and the PBX.
Layer 1 (Physical Layer)
The Alcatel 4400 PBX configuration screen for the ISDN PRI QSIG trunk interface is reached using both Alcatel Board and Board\Digital Access menus, setting the PRI physical layer parameters.
Layers 2 & 3 (Q.921 and Q.931)
Layer 2 and 3 packet exchanges were monitored using an Acacia Clarinet protocol analyzer, bridged across the PRI link in high impedance mode.
Layer 2 Q.921 packets were monitored to ensure that each PBX/6608-E1 software configuration properly exchanged SABME/UA packets to initialize the ISDN link, and then RR packets were exchanged every 30 seconds.
Layer 3 Q.931 packets were monitored to ensure that the appropriate call setup/teardown packets were exchanged for each configuration, and that the SETUP packets contained the mandatory Information Elements with the necessary details, as well as optional IEs such as Calling Name and Number.
Telephone calls were made end-to-end in both directions through the Cisco 6608-E1 Gateway, and a check was made to ensure that there was an audio path in both directions for each call.
User/Network Settings
The Cisco 6608-E1 Gateway with ISDN protocol type setting of PRI ISO QSIG E1 supports both protocol sides by selecting "Network/User" in the Protocol Side field when configuring the Gateway via CCM.
The Alcatel 4400, supports both "USER" (slave) and "NETWORK" (master) protocol sides. Network/User options are set in the Board/Digital Access Options menu. Network mode must be set to Yes for (Master/Network) or No - (Slave/User).
The following options for Alcatel PBX are of particular interest:
•Trunk interface type must be set to PRA2.
•Access Type must be set to T2.
Q931 signal variant is used to determine Protocol type. This option was set to ABC-F.
Appendix B
Test Results
Testing was performed by Test Engineer(s): Samir Batio, July 24, 2002
Retesting with CCM3.3-256c load was performed by Test Engineer: Samir Batio, October 1, 2002
Test Setup 1
Test setup was as follows:
•PBX1 configured as ISO version ABC-F, emulates Network.
•Cisco 6608-E1 Gateway configured as PRI ISO QSIG E1, emulates User.
Table 8 Switch and Gateway Settings
Alcatel 4400 Switch-type / Protocol-Side Setting Cisco 6608-E1 ISDN protocol-type/Protocol-Side SettingABC-F / Network
PRI ISO QSIG E1/User
Table 9 Basic Calls: (Enbloc Sending
Calls Made Call Comp? "Calling Number" Displayed on Final Destination? "Calling Name" Displayed on Final Destination? "Called Number" Displayed on Orig. Side? "Called Name" Displayed on Orig. Side? Notes Phone A to Phone CYes
Yes
Yes
No 1
Yes
Phone C to Phone AYes
Yes
Yes
Yes
Yes
1 Alcatel ISO version ABC-F QSIG link does not honor Connected Number Identification Presentation.
1 Overlap Receiving on Alcatel PBX works when the Cisco gateway configuration for Called Numbering Plan field is set to `private', `unknown', or `ISDN'.
1 CM3.3 Seaview release does not support Updating Connected Name and Number for Call Transfers QSIG supplementary Services.
1 CM3.3 Seaview release does not honor redirectingName and redirectingNumber IE messages.
1 When Alcatel phone is setup for local Call Forwarding it sends Facility IE for `CallRerouting'. Since CCM3.3 Seaview release does not support `CallRerouting', the call is not completed.
Test Setup 2
Setup was as follows:
•PBX1 configured as ISO version ABC-F, emulates User
•Cisco 6608-E1 Gateway configured as PRI ISO QSIG E1, emulates Network
.
Table 17 Switch and Gateway Settings
Alcatel 4400 Switch-type/Protocol-Side Setting Cisco 6608-E1 ISDN protocol-type/Protocol-Side SettingABC-F / User
PRI ISO QSIG E1 / Network
The test results are the same as in previous section. Refer to Tables 9 through 16 for details.
Posted: Thu Sep 6 13:35:28 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.