Don't know much about CISCO! 1

[EddieDuece]

So we have a CS1000 (opt 81 upgraded) connected to one of our sites via PRI option 11 4.5. We just recently had fiber installed and moved our network gear to the fiber. It is up and running great. Now we want to eliminate the T1 between the sites and connect the 2 PBX's via fiber. So the PRI comes out of the CS1000, in and out of a CSU and plugs into a CISCO 3845 router. Everything greens up and looks good. Routes over the fiber to the far end to a CISCO 2801....in and out of a CSU, to the Opt 11. Everything greens up and looks good. So I enable the D channel and loop, but the D channel releases and the B channels go into a MSBY state. This is the error I get;

DCH055 DCH: 6 RLS WRONG MODE TIME

Anyone have any clue as to why this is happening? Any help would be greatly appreciated.

 

[whykap]

what do the router configs look like for the T1 controllers? Can you post them?

 

[EddieDuece]

Sure....give me a minute.

 

[EddieDuece]

Here is the 3845 config;
boot system flash:c3845-adventerprisek9-mz.124-25a.bin
boot-end-marker
!
card type t1 0 0
card type t1 0 1
card type t1 1 0
card type t1 1 1
! card type command needed for slot/vwic-slot 2/0
no network-clock-participate slot 1
no network-clock-participate slot 2
network-clock-participate wic 1
no network-clock-participate wic 2
no network-clock-participate wic 3
!
isdn switch-type primary-qsig
voice-card 0
dspfarm
!
!
!
!
controller T1 0/1/1
framing esf
linecode b8zs
cablelength short 110
pri-group timeslots 1-24
description Tilley T1
!
!
translation-rule 2
Rule 0 ^0... 2220
Rule 1 ^1... 2221
Rule 2 ^2... 2222
Rule 3 ^3... 2223
Rule 4 ^4... 2224
Rule 5 ^5... 2225
Rule 6 ^6... 2226
Rule 7 ^7... 2227
Rule 8 ^8... 2228
Rule 9 ^9... 2229
!
!
!
!
!
!
interface GigabitEthernet0/0
description $FW_INSIDE$
ip address 192.168.17.1 255.255.255.0
ip helper-address 192.168.11.1
no ip redirects
no ip unreachables
no ip proxy-arp
ip nbar protocol-discovery
ip route-cache flow
duplex auto
speed auto
media-type rj45
no mop enabled
!
interface Serial0/1/1:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
no cdp enable
!
!
!
!
!
control-plane
!
!
!
voice-port 0/1/1:23
translate called 2
!
!
!
!
!
dial-peer voice 1 voip
description Default route to Tilley 2801
destination-pattern 222....
session target ipv4:192.168.110.253
codec g711ulaw
!
dial-peer voice 2 pots
incoming called-number .
direct-inward-dial
port 0/1/1:23
!
dial-peer voice 3 pots
destination-pattern 111....
port 0/1/1:23
!
!
!
banner login ^C
-----------------------------------------------------------

And here is the 2801 Config;

boot system flash:c2801-adventerprisek9-mz.124-25a.bin
boot-end-marker
!
card type t1 0 1
network-clock-participate wic 1
network-clock-select 1 T1 0/1/0
!
!
!
!
isdn switch-type primary-qsig
!
voice-card 0
codec complexity medium
!
!
controller T1 0/1/0
framing esf
linecode b8zs
cablelength long 0db
pri-group timeslots 1-24
!
controller T1 0/1/1
framing esf
linecode b8zs
cablelength long 0db
!
!
!
!
translation-rule 1
Rule 0 ^0... 1110
Rule 1 ^1... 1111
Rule 2 ^2... 1112
Rule 3 ^3... 1113
Rule 4 ^4... 1114
Rule 5 ^5... 1115
Rule 6 ^6... 1116
Rule 7 ^7... 1117
Rule 8 ^8... 1118
Rule 9 ^9... 1119
!
!
!
!
!
!
interface FastEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0$$ES_LAN$$FW_INSIDE$
ip address 192.168.110.253 255.255.255.0
ip route-cache flow
duplex auto
speed auto

!
interface FastEthernet0/1
no ip address
ip route-cache flow
shutdown
duplex auto
speed auto
!
interface Serial0/1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
no cdp enable
!
!
!
control-plane
!
disable-eadi
!
!
voice-port 0/1/0:23
translate called 1
!
!
!
!
!
dial-peer voice 1 voip
description Default route to Core 3825
destination-pattern 111....
session target ipv4:192.168.17.1
codec g711ulaw
!
dial-peer voice 2 pots
incoming called-number .
direct-inward-dial
port 0/1/0:23
!
dial-peer voice 3 pots
destination-pattern 222....
port 0/1/0:23

Thanks for taking some time to help with this. We have been beating our heads against the wall!

 

[whykap]

Enable the D-channel on the Nortel and then post the results of the following commands from both routers:

show controllers T1

and

Show isdn status

Oh yeah and you are using T1 x-over cables right?

 

[EddieDuece]

The site is pretty busy today so won't be able to test until later in the day or next week. So when we used the x-over cables, the routers don't green up. They do have CSU's on each end and when I bring up the span, the CISCO gear can see that the span is up or down so the T1 seems to be good. It's just that when I bring the span up, the D channel releases and B channels go into MSBY mode. Does that tell you anything?

 

[whykap]

No it does not. I will need to see the above results first.
Also can you post a "show diag" from each router?

Have you tried to do ni instead of qsig just for teting purposes?

 

[EddieDuece]

No, we have not tried ni. We are set to SL1 on the PBX's.

 

[whykap]

you got the router set to qsig. unless you are doing qsig on the nortel you'll never get the d-channel to come up.
What protocol do you want to use?

 

[EddieDuece]

What would your recommendation be? Whats the benefit of one over the other?

 

[whykap]

It all depends what you are trying to achieve here. Since this is a NORTEL to NORTEL PBX integration that is question for your phone system vendor and the requirements you need to meet.
The problem you are having here is that your nortel is set for one protocol and the router for another. D-channel will never come up and work this way.
I suggest NI2 to get it working and if your requirements include MWI's and other advanced features, then you can switch to qsig.
Either way they have to match on both ends.

 

[burtsbees]

Nortel and some Cisco protocols will not jive, like with port-channels, you need LAGP insteat of PAGP, or something like that, as an example...

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[madwok]

ED,

Using the IP trunking (SIP or H323) between them CS1000s make more sense to me.

With this you can don't have to deal with voice card/ protocol mess on the Cisco side . The only thing that you might consider is the QOS, vlan aspect for your voice traffic if shared with data.

 

[EddieDuece]

Hey, got it going. Thanks for all the help. Got us pointed in the right direction.

 

[jamie2]

Working with Eddie on this... Almost have it working but we can not 7-digit dial out of the option 11C.

 

[jamie2]

Here are the cisco translation

translation-rule 1
Rule 0 ^0 ... 1110
Rule 1 ^1 ... 1111
Rule 2 ^2 ... 1112
Rule 3 ^3 ... 1113
Rule 4 ^4 ... 1114
Rule 5 ^5 ... 1115
Rule 6 ^6 ... 1116
Rule 7 ^7 ... 1117
Rule 8 ^8 ... 1118
Rule 9 ^9 ... 1119