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

T1 PRI

I am trying to bring up a T1 PRI. I have the following config.

isdn switch-type primary-dms100

Controller t1 0/0

linecode b8zs

framing esf

pri-group timeslot 1 - 24

when i do a sh isdn status, layer 2 is showing

TEI - ASSIGNED, then it changes to awaiting-establishment, and then back to TE1 - ASSIGNED. Basically bouncing between these two states.

I am missing something..it should be showing multiple frame-established, right?

Thanks

10 REPLIES

Re: T1 PRI

Can you post the rest of your config or is this all you have? Are you sure the telco has brought the line up on their end?

Community Member

Re: T1 PRI

This is the rest of the config

Controllert t1 0/0

framing esf

linecode b8zs

cablelength short 133

pri-group timeslots 1 - 24

int s0/0:23

no ip add

no logging event link-status

isdn switch-type primary-dms100

isdn incoming-voice voice

This is a 2651xm-v with IOS 2600-ipvoice-mz.123-1a.bin.

Thanks

Re: T1 PRI

Can you comfirm with telco (you may already know though) that the isdn switch-type is in fact a primary-dms100 and not primary-ni?

Silver

Re: T1 PRI

The reason you are getting slips is the clocking is not right. I will bet you have a T1 VWIC and an AIM-VOICE-30 card.,.

You will need to add the following commands :

network-clock-participate wic 0

network-clock-select 1 t1 0/0

this should clear up the slips.

Keep running the Q921 debugs. What you should see is the router TX a SABME , and the switch should respond with a UA, then every 30 seconds or so each dvice will send a RR towards each other.

If you get no response to the SABME and the controller is showing no errors, call up the Telco as they are not responding to your Q921 link establishment.

Community Member

Re: T1 PRI

Yes, if layer 2 is stable you should see the multiple frame-established. Under the pri serial interface I would also put the isdn switch-type command. Have you verified with the telco that this is the correct switch type? Can you post the output of a isdn q921 debug?

http://www.cisco.com/en/US/partner/tech/tk713/tk628/technologies_tech_note09186a00801509d7.shtml

Community Member

Re: T1 PRI

This is the output of the denug isdn q921 and sh controller:

Router(config-controller)#shut

Router(config-controller)#no shut

Router(config-controller)#

*Mar 1 00:12:45.410: %CONTROLLER-5-UPDOWN: Controller T1 0/0, changed state to administratively d

*Mar 1 00:12:50.102: %CONTROLLER-5-UPDOWN: Controller T1 0/0, changed state to up

*Mar 1 00:12:50.106: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:12:51.108: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:12:52.109: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:12:53.111: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:12:59.113: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:00.114: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:01.116: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:02.118: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:08.119: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:09.121: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:10.123: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:11.124: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:17.126: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:18.128: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:19.129: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

*Mar 1 00:13:20.131: ISDN Se0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

Router#un al

*Mar 1 00:13:21.922: %SYS-5-CONFIG_I: Configured from console by vty0 (10.102.1.1)l

All possible debugging has been turned off

Router#

Router#sh controllers t1 0/0

T1 0/0 is up.

Applique type is Channelized T1

Cablelength is long gain36 0db

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20020812, FPGA: 11

Framing is ESF, Line Code is B8ZS, Clock Source is Line.

Data in current interval (124 seconds elapsed):

0 Line Code Violations, 0 Path Code Violations

8 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

8 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Data in Interval 1:

2 Line Code Violations, 6 Path Code Violations

56 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 2 Degraded Mins

60 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Total Data (last 1 15 minute intervals):

2 Line Code Violations, 6 Path Code Violations,

56 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 2 Degraded Mins,

60 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Router#

Blue

Re: T1 PRI

Is this a PBX integration? Are you sure the clock source should be line? Verify that you are supposed to be User side (as opposed to network) isdn protocol-emulate {user | network} . Just throwing out things to try. Have you verified the cable is in good working order?

Re: T1 PRI

You're only transmitting, not receiving anything.

There are a bunch of errors on that controller.

If this is new, chances are it's probably a line/circuit issue between the controller interface and whatever it is connecting to.

Anonymous
N/A

Re: T1 PRI

Hi. Pholley,

MULTIPLE_FRAME_ESTABLISHED indicating that the signaling channel is functioning correctly and is exchanging Layer 2 frames with the Telco switch.

Layer 2 is TEI_ASSIGNED. This indicates that the PRI is not exchanging Layer 2 frames with the switch. Use the show controller e1 x command to troubleshoot.

Check with the telco if they have turn on the service.

http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00800f9e3a.shtml

Community Member

Re: T1 PRI

Thanks for your post guys. It turned out that the telco have not setup the PRI correctly.

I took my router with my configs, and tested it out on a customer PRI during after hours, and my layer 2 signalling was fine.

Paul

821
Views
5
Helpful
10
Replies
CreatePlease to create content