Cisco 2621 Gateway-PBX Interoperability: Ericsson MD-110 With T1 PRI Signaling
Cisco 2621 Gateway-PBX Interoperability: Ericsson MD-110 With T1 PRI Signaling
This document describes the interoperability and configuration of a Cisco 2621 Gateway with an Ericsson MD-110 PBX using T1 PRI signaling. It includes the following sections: System Components Configuration Tasks Caveats
System Components
PBX Model PBX Release Telephony Signaling Voice Gateway Gateway Release Call Manager Release VoX Protocol Ericsson MD-110 ASB50104-R6-SES-R9-BC90D/CNI80 T1 PRI Cisco 2621 Gateway IOS Version 12.2(3.5)T 3.1.1 H.323
Configuration Tasks
See the following sections for configuration tasks for this feature: Set Up Ericsson PBX Configuration Call Manager Configuration Cisco 2621 Gateway Configuration
Page 1
Set Up
This section includes the following information: Connectivity Diagrams Set Up Notes
Connectivity Diagrams
Figure 1: Test Configuration
VoIP
PBX #1 Phone B x5002 Phone E x N/A Cisco 7960 IP phones Phone C x2001 Phone D x2002
Figure 1 represents the configuration used for testing: an Ericsson MD-110 PBX connected to a Cisco 2621 Gateway via a T1 PRI connection.
Set Up Notes
The Cisco 2621 Gateway with switch type setting of primary-ni supports both protocol sides by using the isdn protocol-emulate network/user command. The Ericsson MD-110 uses a command line interface where many switch features are changed with a single command. The PBX documentation must be consulted to make changes. Using the RODAI command controls physical layer parameters. The Ericsson MD-110 supports both user (peer-slave) and network (peer-master) protocol sides by using the RODAI command. When calling from Cisco 7960 IP phone to an Ericsson digital phone, Calling/Called Number is displayed on both phones after the call is answered. When calling from an Ericsson digital phone to Cisco 7960 IP phone, the IP phone displays connected number after the call is answered. The Ericsson phone however, does not get updated when the call is answered. It displays the word PRIVATE instead. It was verified using ISDN protocol analyzer that the CallManager was not sending connected number information in the connect message back to PBX.
Page 2
ROCAI Route Category Initiate RODAI Route Data Initiate ROEQI Route Equipment Initiate RODDI Route External Destination Data Initiate
< ROCAP:ROU=20; ROUTE CATEGORY DATA ROU SEL 20 TRM SERV 3110000010 NODG DIST DISL TRAF 0 5 20 SIG BCAP
711000000000 7
Page 3
Page 4
Page 5
Page 6
Page 7
MAINTENANCE INTERIM S
ROM: System Bootstrap, Version 12.1(3r)T2, RELEASE SOFTWARE (fc1) 2621_B uptime is 1 week, 4 days, 3 hours, 15 minutes System returned to ROM by power-on System image file is "flash:c2600-js-mz.122-3.5.T" cisco 2621 (MPC860) processor (revision 0x200) with 56320K/9216K bytes of memory . Processor board ID JAD051516TX (503811939) M860 processor: part number 0, mask 49 Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. Primary Rate ISDN software, Version 1.1. 2 FastEthernet/IEEE 802.3 interface(s) 24 Serial network interface(s) 2 Channelized T1/PRI port(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write) Configuration register is 0x2102 2621_B# ______________________________________________________________________________ 2621_B#show diag Slot 0: C2621 2FE Mainboard Port adapter, 2 ports Port adapter is analyzed Port adapter insertion time unknown EEPROM contents at hardware discovery: Hardware Revision : 2.0 PCB Serial Number : JAD051516TX (503811939) Part Number : 73-3200-08 RMA History : 00 RMA Number : 0-0-0-0 Board Revision : A0 Deviation Number : 0-21249 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 00 A2 41 02 00 C1 17 4A 41 44 30 35 31 0x10: 35 31 36 54 58 20 28 35 30 33 38 31 31 39 33 39 0x20: 29 82 49 0C 80 08 04 00 81 00 00 00 00 42 41 30 0x30: 80 00 00 53 01 FF FF FF FF FF FF FF FF FF FF FF 0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Page 8
Slot 1: High Density Voice Port adapter Port adapter is analyzed Port adapter insertion time unknown EEPROM contents at hardware discovery: Hardware Revision : 1.1 Top Assy. Part Number : 800-03567-01 Board Revision : F1 Deviation Number : 0-0 Fab Version : 02 PCB Serial Number : JAB05080LU9 RMA Test History : 00 RMA Number : 0-0-0-0 RMA History : 00 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 00 CC 41 01 01 C0 46 03 0x10: 42 46 31 80 00 00 00 00 02 02 C1 0x20: 35 30 38 30 4C 55 39 03 00 81 00 0x30: FF FF FF FF FF FF FF FF FF FF FF 0x40: FF FF FF FF FF FF FF FF FF FF FF 0x50: FF FF FF FF FF FF FF FF FF FF FF 0x60: FF FF FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF
20 8B 00 FF FF FF FF FF
00 4A 00 FF FF FF FF FF
0D 41 00 FF FF FF FF FF
EF 42 04 FF FF FF FF FF
01 30 00 FF FF FF FF FF
VIC Slot 0: T1 (2 Port) Multi-Flex Trunk (Drop&Insert) WAN Hardware revision 1.0 Board revision Serial number 17759676 Part number Test history 0x0 RMA number Connector type PCI EEPROM format version 1 EEPROM contents (hex): 0x20: 01 24 01 00 01 0E FD BC 50 12 06 01 00 0x30: 58 00 00 00 00 01 15 00 FF FF FF FF FF
00 00 00 FF FF FF
HDV firmware: Compiled Fri 23-Mar-01 00:20 by miriyala HDV memory size 524280 heap free 175065 2621_B# _________________________________________________________________________________________ 2621_B#show controllers t1 1/0 T1 1/0 is up. Applique type is Channelized T1 Cablelength is long gain36 0db No alarms detected. alarm-trigger is not set Version info Firmware: 20010710, FPGA: 15 Framing is ESF, Line Code is B8ZS, Clock Source is Line. Data in current interval (184 seconds elapsed): 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs 2621_B#
Page 9
enable password cisco ! ! ! memory-size iomem 15 voice-card 1 dspfarm ! ip subnet-zero ! ! no ip domain-lookup ! isdn switch-type primary-ni ! ! voice class codec 1 codec preference 1 g729r8 codec preference 2 g711ulaw codec preference 3 g711alaw ! ! ! ! ! ! ! controller T1 1/0 framing esf linecode b8zs pri-group timeslots 1-24 ! controller T1 1/1 shutdown framing esf linecode b8zs ! ! ! ! interface FastEthernet0/0 ip address 192.168.100.2 255.255.255.0 no ip mroute-cache load-interval 30 no keepalive speed auto half-duplex ! interface FastEthernet0/1 ip address 10.1.1.129 255.255.255.0 no ip mroute-cache duplex auto speed auto ! interface Serial1/0:23 no ip address no logging event link-status isdn switch-type primary-ni isdn incoming-voice voice isdn T309-enable isdn T306 30000 isdn T310 40000 no cdp enable ! router rip network 1.0.0.0 network 192.168.100.0 ! ip classless no ip http server ip pim bidir-enable !
Page 10
dialer-list 1 protocol ip permit dialer-list 1 protocol ipx permit ! ! snmp-server packetsize 4096 snmp-server manager tftp-server nvram call rsvp-sync ! voice-port 1/0:23 ! ! mgcp profile default ! dial-peer cor custom ! ! ! dial-peer voice 1 pots destination-pattern 5... direct-inward-dial port 1/0:23 prefix 5 ! dial-peer voice 3 voip destination-pattern 2... progress_ind setup enable 1 voice-class codec 1 session target ipv4:10.1.1.2 dtmf-relay h245-alphanumeric ! ! line con 0 exec-timeout 0 0 line aux 0 exec-timeout 0 0 line vty 0 4 exec-timeout 0 0 password cisco login line vty 5 15 exec-timeout 0 0 login ! scheduler allocate 3996 1000 ! end
Caveats
Calling Name delivery and presentation features are not supported by the Ericsson MD-110 PBX. Warning: The Ericsson MD-110 PBX user interface is very cryptic. All parameters and options are mapped to position-dependent numeric fields within the various commands listed below. The user must have the correct revision of the Ericsson MD-110 PBX Administration manual to be able to decipher each field position to determine its meaning. Therefore it is advised not to make changes to an MD-110 PBX unless you know exactly what you are doing. A single number out of place in a command string can cause unusual behavior on the PBX.
Page 11