One of our client has a Nortel Meridian PBX and they are cutting over to Cisco 2800 gateway as the PBX is unstable and could break anytime. We have a Call manager cluster in the Datacentre with a local gateways.
First we thought it was an ISDN PRI circuit and when we plugged in the E1 cable the alarm LED was on and L1.L2 and L3 were down. After working on the circuit and debugging the router we found the circuit is not ISDN it's an older circuit called DTI (Digital Trunk Interface) or CAS (Channel Associated signalling) which I never came across before but is supported on G.703 VWIC-1MFT card from Cisco. I got a Cisco 2800 router which had G.703 card and plugged the E1 cable and the L1 was up but L2 and L3 were having issue's.
I don’t understand the G.703 protocol as I couldn’t find much document online and how can I configure the router. Please see attachment diagram on how it is configured.
router#sh isdn status
Global ISDN Switchtype = primary-net5
ISDN Serial0/0/0:15 interface
dsl 0, interface ISDN Switchtype = primary-net5
Layer 1 Status:
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0xFFFF7FFF
Number of L2 Discards = 0, L2 Session ID = 39
Total Allocated ISDN CCBs = 0
Dec 8 05:11:09.310: ISDN Se0/0/0:15 Q921: L2_Es
router#sh controller e1
E1 0/0/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20090113, FPGA: 20, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (86 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.