|
|
Table Of Contents
Cisco Systems Equipment needed
PBX Hardware and Software Requirements
Configuring the Alcatel 4400 PBX
Configure Digital Access Options
Calling Name and Number Feature
Catalyst 6000 Switch Configuration
Application Note
Alcatel 4400 PBX with CallManager using 6608-E1 PRI EURO Gateway
This application note illustrates connectivity for Alcatel 4400 Release Cisco CallManager using Cisco 6608-E1 PRI EURO Gateway.
Integration Description
Connectivity is achieved using the ETSI standard PRI protocol. The Alcatel 4400 can be configured as either NETWORK or USER side.
Cisco Systems Equipment needed
Hardware (Gateway): 6608 E1 Port
Software: CallManager Release 3.1
PBX Hardware and Software Requirements
Hardware: PRA2, 3BA23076.
Software: Version R3.2
Features Supported
Key features supported:
Calling/Called Number
Key features not supported:
Calling/Called Name
Network Diagram
Figure 1
Network Test Topology
Configuring the Alcatel 4400 PBX
Configure in the following sequence:
1.
"Configure Board" on page 3
2.
3.
4.
Configure Board
Interface type must be set to PRA2.
\compidea\Shelf::0\Board::3Board Address 3Interface Type PRA2Usage State BusyOperational State EnabledMain/Standby State Main (Master)Number Of Sets Being Connect. 1CRC4 YESCountry Protocol Type USAIncidents Teleservice YESISDN Board Layer 2 ParametersRetransmission Timer 100TEI Identity Check Timer 100Polling Timer 1000Nb_Of_Retransmission 3Max Frame Size (Bytes) 260Window Size In Frames SAPI S T0 1Window Size In Frames SAPI P T0 3Window Size In Frames SAPI S T2 7Window Size In Frames SAPI P T2 7Passive board NOSS7 signalling NOConfigure Digital Access Options
Network mode must be set to Yes for (Master/Network) or No - (Slave/User).
Access Type must be set to T2.
\compidea\Shelf::0\Board::3\Digital Access::0
T0/T2 Access No. 0Access Type T2Synchronisation Priority 255Network Mode YESMax Nb Of Used B Channels 30Max_Nb_Of_Compressed_B_Channels 0TieLine Mode NOWith Alarm NOReserved1 YESReserved2 YESNetwork Date Time Update NOCRC4 YESConfigure Trunk Group
Q931 signal variant is used to set the protocol type to ISDN all countries.
\compidea\Trunk Groups::0Trunk Group Id 0Trunk Group Type T2Trunk Group Name PRA2_EURONode number 1Transcom Trunk Group FalseAuto.reserv.by Attendant FalseOverflow trunk group No. -1Tone on seizure TruePrivate Trunk Group FalseQ931 signal variant ISDN all countriesNumber Compatible With -1Number Of Digits To Send 4Channel selection type QuantumRemote Network 15Shared Trunk Group Falseauto.DTMF dialing on outgoing call NOT2 Specificity NonePublic Network Category 0DDI transcoding FalseSpecial Services NothingCan support UUS in SETUP TrueConfigure Trunk Detail
\compidea\Trunk Groups::0\Trunk Group::1
Instance (reserved) 1Trunk Group Type T2Public Network Ref.Dialling end to end NODTMF end to end signal. NOTrunk group used in DISA NODISA Secret CodeVG for non-existent No. YESRouting To Executive NOTrunk Category Id 19Nb of digits unused (ISDN) 0B Channel Choice YESChannels Reserved By Attend. 0Dissuasion For ACD NODTO joining NOEnquiry Call On B Channel NOAutomated Attendant NOCalling party Rights category 0Entity Number 0TS Overflow YESNumber To Be AddedSupervised by Routing NOVPN Cost Limit for Incom.Calls 0Immediat Trk Listening For VPNCall YESVPN TS % 50Csta Monitored NOMax.% of trunks out CCD 0Charge Calling And ADN Creation NORatio analog.to ISDN taxLogicalChannel 1__15 & 17__31TS Distribution on Accesses YESUse Split Acces NOHeterogeneous Remote Network NOBarring mode Not barredARS class of service 31Quality profile for voice on IP Profile #1IP compression type DefaultUse of volume in system YESConfiguring Cisco CallManager
6608 Gateway Configuration
Route Pattern Configuration
Considerations
Calling Name and Number Feature
Calling Name delivery and presentation features are not supported by the Alcatel 4400 PBX.
When configuring Cisco 6608 Gateway to emulate User side (Alcatel emulate Network side), make sure that the "Display IE Delivery" box is NOT checked, otherwise calls will not be completed. Alcatel PBX complains about the Display information being sent in the "SETUP" message from CallManager by sending STATUS message with cause of "IE non-existent/unimplemented".
When calling from Cisco 7960 IP phone to Alcatel digital phone, Calling/Called Number is displayed on both phones after the call is answered as expected.
When calling from Alcatel digital phone to Cisco 7960 IP phone, IP phone displays Connected Number after the call is answered. Alcatel phone however does NOT get updated when the call is answered. It displays the trunk name. It was verified using ISDN protocol analyzer that the CallManager was not sending "Connected Number" information in the connect message back to PBX.
Appendix A
CallManager Software release:
Alcatel 4400 Software Version
Version Information
\compidea\Node
Node Number (reserved) 1Software Version R3.2Version name c1.712Patch No. 5NotesObject IdentityNode Number (reserved) 1Ethernet NotesNetmaskLocal CPUName x000000_tunIP Address 172.30.253.253Twin CpuNameIP AddressMain CpuName xm000000IP Address 10.253.253.3StandBy CpuNameIP AddressSL NotesIP/X25 Tunnel NotesNetmask 255.255.0.0Local NodeName x000000_tunIP Address 172.30.253.253Catalyst 6000 Switch Configuration
Console> sh versionWS-C6006 Software, Version NmpSW: 5.5(6a)Copyright (c) 1995-2001 by Cisco SystemsNMP S/W compiled on Feb 23 2001, 10:23:18System Bootstrap Version: 5.3(1)Hardware Version: 2.0 Model: WS-C6006 Serial #: TBA04511172Mod Port Model Serial # Versions--- ---- ------------------- ----------- --------------------------------------1 2 WS-X6K-SUP1A-2GE SAD05010NBK Hw : 7.0Fw : 5.3(1)Fw1: 5.4(2)Sw : 5.5(6a)Sw1: 5.5(6a)WS-F6K-PFC SAD05020221 Hw : 1.13 48 WS-X6348-RJ-45 SAD04420N7B Hw : 1.4Fw : 5.4(2)Sw : 5.5(6a)WS-F6K-VPWR Hw : 1.04 24 WS-X6624-FXS SAD050203M8 Hw : 3.0Fw : 5.4(2)Sw : 5.5(6a)HP : A00203010007; DSP : A003C031 (3.3.30)5 8 WS-X6608-T1 SAD04400EM0 Hw : 1.1Fw : 5.4(2)Sw : 5.5(6a)HP1: D00403010013; DSP1: D005C031 (3.3.30)HP2: D00403010013; DSP2: D005C031 (3.3.30)HP3: D00403010013; DSP3: D005C031 (3.3.30)HP4: D00403010013; DSP4: D005C031 (3.3.30)HP5: D00403010013; DSP5: D005C031 (3.3.30)HP6: D00403010013; DSP6: D005C031 (3.3.30)HP7: D00403010013; DSP7: D005C031 (3.3.30)HP8: D00403010013; DSP8: D005C031 (3.3.30)6 8 WS-X6608-E1 SAD04380DW1 Hw : 1.1Fw : 5.4(2)Sw : 5.5(6a)HP1: D00403010013; DSP1: D005C031 (3.3.30)HP2: D00403010013; DSP2: D005C031 (3.3.30)HP3: D00403010013; DSP3: D005C031 (3.3.30)HP4: D00403010013; DSP4: D005C031 (3.3.30)HP5: D00403010013; DSP5: D005C031 (3.3.30)HP6: D00403010013; DSP6: D005C031 (3.3.30)HP7: D00403010013; DSP7: D005C031 (3.3.30)HP8: D00403010013; DSP8: D005C031 (3.3.30)DRAM FLASH NVRAMModule Total Used Free Total Used Free Total Used Free------ ------- ------- ------- ------- ------- ------- ----- ----- -----1 65408K 37541K 27867K 16384K 11546K 4838K 512K 198K 314KUptime is 27 days, 4 hours, 16 minutesConsole>______________________________________________________________________________Console> sh moduleMod Slot Ports Module-Type Model Sub Status--- ---- ----- ------------------------- ------------------- --- --------1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok3 3 48 10/100BaseTX Ethernet WS-X6348-RJ-45 yes ok4 4 24 FXS WS-X6624-FXS no ok5 5 8 T1 WS-X6608-T1 no ok6 6 8 E1 WS-X6608-E1 no okMod Module-Name Serial-Num--- ------------------- -----------1 SAD05010NBK3 SAD04420N7B4 SAD050203M85 SAD04400EM06 SAD04380DW1Mod MAC-Address(es) Hw Fw Sw--- -------------------------------------- ------ ---------- -----------------1 00-04-c0-f8-42-02 to 00-04-c0-f8-42-03 7.0 5.3(1) 5.5(6a)00-04-c0-f8-42-00 to 00-04-c0-f8-42-0100-04-9b-f0-78-00 to 00-04-9b-f0-7b-ff3 00-02-fc-20-5e-50 to 00-02-fc-20-5e-7f 1.4 5.4(2) 5.5(6a)4 00-03-32-ba-2e-35 3.0 5.4(2) 5.5(6a)5 00-01-c9-d9-3a-98 to 00-01-c9-d9-3a-9f 1.1 5.4(2) 5.5(6a)6 00-01-c9-d8-63-3e to 00-01-c9-d8-63-45 1.1 5.4(2) 5.5(6a)Mod Sub-Type Sub-Model Sub-Serial Sub-Hw--- ----------------------- ------------------- ----------- ------1 L3 Switching Engine WS-F6K-PFC SAD05020221 1.13 Inline Power Module WS-F6K-VPWR 1.0Console>______________________________________________________________________________Console> sh port 6Port Name Status Vlan Duplex Speed Type----- ------------------ ---------- ---------- ------ ----- ------------6/1 connected 1 full 2.048 E16/2 notconnect 1 full 2.048 E16/3 notconnect 1 full 2.048 E16/4 notconnect 1 full 2.048 E16/5 notconnect 1 full 2.048 E16/6 notconnect 1 full 2.048 E16/7 notconnect 1 full 2.048 E16/8 notconnect 1 full 2.048 E1Port DHCP MAC-Address IP-Address Subnet-Mask-------- ------- ----------------- --------------- ---------------6/1 enable 00-01-c9-d8-63-3e 10.1.1.104 255.255.255.06/2 enable 00-01-c9-d8-63-3f 10.1.1.118 255.255.255.06/3 enable 00-01-c9-d8-63-40 10.1.1.123 255.255.255.06/4 enable 00-01-c9-d8-63-41 10.1.1.117 255.255.255.06/5 enable 00-01-c9-d8-63-42 10.1.1.120 255.255.255.06/6 enable 00-01-c9-d8-63-43 10.1.1.121 255.255.255.06/7 enable 00-01-c9-d8-63-44 10.1.1.122 255.255.255.06/8 enable 00-01-c9-d8-63-45 10.1.1.124 255.255.255.0Port Call-Manager(s) DHCP-Server TFTP-Server Gateway-------- ----------------- --------------- --------------- ---------------6/1 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/2 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/3 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/4 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/5 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/6 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/7 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.76/8 10.1.1.2 10.1.1.2 10.1.1.2 10.1.1.7Port DNS-Server(s) Domain-------- ----------------- -------------------------------------------------6/1 - -6/2 - -6/3 - -6/4 - -6/5 - -6/6 - -6/7 - -6/8 - -Port CallManagerState DSP-Type-------- ---------------- --------6/1 registered C5496/2 registered C5496/3 registered C5496/4 registered C5496/5 registered C5496/6 registered C5496/7 registered C5496/8 registered C549Port NoiseRegen NonLinearProcessing----- ---------- -------------------6/1 enabled enabled6/2 enabled enabled6/3 enabled enabled6/4 enabled enabled6/5 enabled enabled6/6 enabled enabled6/7 enabled enabled6/8 enabled enabledConsole>Test Configuration
Figure 2
Test Topology
The above diagram is representative of the various configurations used for testing.
As shown in the diagram above, an Alcatel 4400 PBX was connected via an ISDN E1 PRI 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 link between a Cisco 6608-E1 and the PBX.
Layer 1 (Physical Layer)
The Alcatel 4400 PBX configuration screen for the E1 trunk interface is reached using both Alcatel Board and Board\Digital Access menus, setting the E1 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-EURO supports both protocol sides by selecting "Network/User" in the protocol side field when configuring the Gateway via CallManager.
The Alcatel 4400, supports both "USER" (slave) and "NETWORK" (master) protocol sides.
The following options are of particular interest:
•
•
•
•
Test Results
Testing was performed by Test Engineer(s): Samir Batio, August 14, 2001
Test Setup 1
Test configuration:
•
•
Table 1 Test Setup 1 Switch and Gateway Settings
ETSI/Network
PRI EURO/User
Table 2 Basic Calls: (Enbloc Sending)
Phone A to Phone C
Yes
Yes
No
No1
No
Phone C to Phone A
Yes
Yes
No
Yes
No
1 CallManager is not sending "Connected Number" information in the connect message back to PBX.
2 Calling Name delivery and presentation features are not supported by the Alcatel ISDN PRI Link.
Test Setup 2
Test configuration:
•
•
Table 6 Test Setup 2 Switch and Gateway Settings
ETSI / User
PRI EURO/Network
The test results are identical as in Test Setup 1. Refer to the tables in Test Setup 1 for details.
Posted: Thu Sep 6 12:07:39 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
