Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

PRI back to back connectivity

Hi All,

Is it possible to connect two PRIs back to back on two different 5350s with out going through Telco-SWITCH. Like

5350-1(T1)--------------(T1)5350-2

PRI cross-cable

To my understanding it's not possible with out passing it to telco-switch. Please confirm with this and if its possible by any chance a working config for this part will highly be appreciated.

What i want is to get the calls on 5350-1 and then send it to 5350-2 then anywhere i like. I tried to configure PRIMARY-NET5 switch type, as it supports USER and NETWORK side both but the PRIs Flaps secondly its a T1 link not E1.

Help will highly be appreciated with detail answer.

3 REPLIES
New Member

Re: PRI back to back connectivity

I think it's possible. I'm doing this on 2651xm routers.

Make sure you use a cross over cable pin1 to pin4 and pin2 to pin5.

Then make one router network side and the other one user side.

Don't forget the clocking.

If you can configure it it should work.

You can even do it on one gateway with two E1's :)

network pri

interface Serial0/1:15

no ip address

no logging event link-status

isdn switch-type primary-net5

isdn protocol-emulate network

isdn incoming-voice voice

no isdn outgoing display-ie

no cdp enable

user pri

interface Serial0/0:15

no ip address

no logging event link-status

isdn switch-type primary-net5

isdn overlap-receiving

isdn incoming-voice voice

isdn send-alerting

isdn sending-complete

no cdp enable

New Member

Re: PRI back to back connectivity

Hi Peter,

You have been very helpful. Yes i did the same config and even used the cross cable as my PRI comes up but its going down occasionally. Config and error is:

!

controller T1 3/1

framing esf

linecode b8zs

pri-group timeslots 1-24

!

!

interface Serial3/1:23

no ip address

isdn switch-type primary-net5

isdn not-end-to-end 64

isdn protocol-emulate network

isdn incoming-voice modem 64

isdn map address .* plan isdn type subscriber

isdn T310 10000

no cdp enable

!

Now the config of User-side PRI

!

!

controller T1 3/3

framing esf

linecode b8zs

pri-group timeslots 1-24

!

!

interface Serial3/3:23

no ip address

isdn switch-type primary-net5

isdn overlap-receiving

isdn not-end-to-end 64

isdn incoming-voice modem 64

isdn map address .* plan isdn type subscriber

isdn T310 60000

fair-queue 64 256 0

no cdp enable

!

Global ISDN Switchtype = primary-dms100

ISDN Serial3/1:23 interface

******* Network side configuration *******

dsl 1, interface ISDN Switchtype = primary-net5

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 1 CCBs = 0

The Free Channel Mask: 0x807FFFFF

Number of L2 Discards = 0, L2 Session ID = 41

Total Allocated ISDN CCBs = 0

!

error i got on the same system:

Aug 9 11:48:48: %CONTROLLER-5-UPDOWN: Controller T1 3/1, changed state to down

Aug 9 11:48:48: %CSM-5-PRI: delete PRI at slot 3, unit 3, channel 23 with index 0

Aug 9 11:48:48: ISDN Se3/1:23: Event: received MNL_RESET_REQ

Aug 9 11:48:48: ISDN Se3/1:23: Event: received NL_REL_IND

Aug 9 11:48:48: ISDN Se3/1:23: Event: received MNL_RESET_REQ

Aug 9 11:48:48: ISDN Se3/1:23: Event: received NL_REL_IND

Aug 9 11:48:48: ISDN Se3/1:23: Event: received MNL_RESET_REQ

Aug 9 11:48:48: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se3/1:23, TEI 0 changed to down

Aug 9 11:48:48: ISDN Se3/1:23: Event: received NL_REL_IND

Aug 9 11:48:53: %CONTROLLER-5-UPDOWN: Controller T1 3/1, changed state to up

Aug 9 11:48:53: %CSM-5-PRI: add PRI at slot 3, unit 3, channel 23 with index 0

Aug 9 11:48:53: ISDN Se3/1:23: TX -> SABMEp c/r = 1 sapi = 0 tei = 0

Aug 9 11:48:53: ISDN Se3/1:23: RX <- UAf c/r = 1 sapi = 0 tei = 0

Aug 9 11:48:53: %ISDN-6-LAYER2UP: Layer 2 for Interface Se3/1:23, TEI 0 changed to up

Aug 9 11:49:03: ISDN Se3/1:23: RX <- RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:49:03: ISDN Se3/1:23: TX -> RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:49:13: ISDN Se3/1:23: TX -> RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:49:13: ISDN Se3/1:23: RX <- RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:49:23: ISDN Se3/1:23: RX <- RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:49:23: ISDN Se3/1:23: TX -> RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:49:33: ISDN Se3/1:23: TX -> RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:49:33: ISDN Se3/1:23: RX <- RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:49:43: ISDN Se3/1:23: RX <- RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:49:43: ISDN Se3/1:23: TX -> RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:49:53: ISDN Se3/1:23: TX -> RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:49:53: ISDN Se3/1:23: RX <- RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:50:03: ISDN Se3/1:23: RX <- RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:50:03: ISDN Se3/1:23: TX -> RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:50:13: ISDN Se3/1:23: TX -> RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:50:13: ISDN Se3/1:23: RX <- RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:50:18: %CONTROLLER-5-UPDOWN: Controller T1 3/1, changed state to down

Aug 9 11:50:18: %CSM-5-PRI: delete PRI at slot 3, unit 3, channel 23 with index 0

Aug 9 11:50:18: ISDN Se3/1:23: Event: received MNL_RESET_REQ

Aug 9 11:50:18: ISDN Se3/1:23: Event: received NL_REL_IND

Aug 9 11:50:18: ISDN Se3/1:23: Event: received MNL_RESET_REQ

Aug 9 11:50:18: ISDN Se3/1:23: Event: received NL_REL_IND

Aug 9 11:50:18: ISDN Se3/1:23: Event: received MNL_RESET_REQ

Aug 9 11:50:18: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se3/1:23, TEI 0 changed to down

Aug 9 11:50:18: ISDN Se3/1:23: Event: received NL_REL_IND

Aug 9 11:50:23: %CONTROLLER-5-UPDOWN: Controller T1 3/1, changed state to up

Aug 9 11:50:23: %CSM-5-PRI: add PRI at slot 3, unit 3, channel 23 with index 0

Aug 9 11:50:23: ISDN Se3/1:23: TX -> SABMEp c/r = 1 sapi = 0 tei = 0

Aug 9 11:50:23: ISDN Se3/1:23: RX <- UAf c/r = 1 sapi = 0 tei = 0

Aug 9 11:50:23: %ISDN-6-LAYER2UP: Layer 2 for Interface Se3/1:23, TEI 0 changed to up

Aug 9 11:50:33: ISDN Se3/1:23: RX <- RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:50:33: ISDN Se3/1:23: TX -> RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:50:43: ISDN Se3/1:23: TX -> RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:50:43: ISDN Se3/1:23: RX <- RRf sapi = 0 tei = 0 nr = 0

Aug 9 11:50:53: ISDN Se3/1:23: RX <- RRp sapi = 0 tei = 0 nr = 0

Aug 9 11:50:53: ISDN Se3/1:23: TX -> RRf sapi = 0 tei = 0 nr = 0

Please help me on this ...why is this going down. Secodnly do you think T1 with the Switch-type Primary-5ess will work like this ???

New Member

Re: PRI back to back connectivity

two things

1. is this on the same 5300? the orginal question indicated it was two. if it is the same 5300 it may get confused sense with a pri the router looks at the sapi information that it sends out to determin if the line is in loopback. with having two ports on the same router may confuse the system since it send sapi on one port and receives the same sapi on a diferent port.

2. one of your t1 ports need to be a master clock on one has to be a reciever.

hope this helps

scott

224
Views
0
Helpful
3
Replies