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

ISDN problem

Hello

Ihave one 2801 connect with one VIC2-2BRI-NT/TE conected to a ISDN basic line.

This line was working well for 8 months, and konw it doesn?t work.

the router hasi 12.3(14)T5 IOS with a CCME.

if I call to the external number it give error tone (error in line)

And (that's very strange) between 15:30pm and 18:30pm it works well but the rest of the day it doesn?t work.

?any ideas?

here is the bri conf:

interface BRI0/1/0

no ip address

isdn switch-type basic-net3

isdn point-to-point-setup

isdn incoming-voice voice

isdn static-tei 0

here is the isdn status

Global ISDN Switchtype = basic-net3

ISDN BRI0/1/0 interface

dsl 2, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 7, State = TEI_ASSIGNED

TEI = 55, Ces = 1, SAPI = 27, State = TEI_ASSIGNED

TEI = 0, Ces = 1, SAPI = 3, State = TEI_ASSIGNED

TEI = 0, Ces = 1, SAPI = 6, State = TEI_ASSIGNED

TEI = 0, Ces = 1, SAPI = 13, State = TEI_ASSIGNED

TEI = 2, Ces = 1, SAPI = 7, State = TEI_ASSIGNED

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

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

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 2 CCBs = 0

The Free Channel Mask: 0x80000003

thanks in advance

13 REPLIES

Re: ISDN problem

You might want to try to do a show controller and see if you have any errors on the line. It looks like layer 2 is down from the isdn stat.

New Member

Re: ISDN problem

thanks for tour reply

show controller:

BRI unit 2:

layer 1 operating in LT-T mode.

Layer 1 is ACTIVATED. (ISDN L1 State F7)

D Channel Information:

idb at 0x64405928, driver data structure at 0x6441FBF0

Infineon Chip Version 0x1

Infineon Registers:

Int. Status Register [ISTA]=0x00, Aux. Int. [AUXI]=0x00

D-channel: Int. Status Reg: [ISTAD]=0x00, Status. Reg: [STARD]=0x48

Mode Reg: [TR_MODE]=0x01

Transceiver Reg: [TR_CONF0]=0x00

Test mode Reg: [TMD]=0x00

IOM Control Reg: [IOM_CR]=0x08

Status Register [STAR]=0x48, Mode Register [MODED]=0xCA

Serial Data Strobe Control Reg: [SDS1_CR]=0x00, [SDS2_CR]=0x00

RX Buffer Descriptor is at 0x64403E34, Buffer size 1524

pak=0x644206C4 data_ptr=0xEEA12474 partial_size=0x0

TX Buffer Descriptor is at 0x64403D94

pak=0x0 data_ptr=0x0 partial_size=0x0

0 missed datagrams, 324864 overruns

0 bad datagram encapsulations, 0 memory errors

0 transmitter underruns 0 d channel collisions

B1 Channel Information:

0 missed datagrams, 0 overruns

0 bad datagram encapsulations, 0 memory errors

0 transmitter underruns 0 d channel collisions

B2 Channel Information:

0 missed datagrams, 0 overruns

0 bad datagram encapsulations, 0 memory errors

0 transmitter underruns 0 d channel collisions

but if I saw that the interface has a lot of CRC errors as you can see in a sh interface bri

BRI0/1/0 is up, line protocol is up (spoofing)

Hardware is Voice NT or TE BRI

MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation VOICE, loopback not set

Last input 21:08:30, output never, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/2689316/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: weighted fair

Output queue: 0/1000/64/0 (size/max total/threshold/drops)

Conversations 0/1/16 (active/max active/max total)

Reserved Conversations 0/0 (allocated/max allocated)

Available Bandwidth 48 kilobits/sec

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

41311 packets input, 164836 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

2689316 input errors, 2689198 CRC, 0 frame, 327521 overrun, 0 ignored, 1688747 abort

112368 packets output, 446761 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 output buffer failures, 0 output buffers swapped out

3 carrier transitions

any ideas??

New Member

Re: ISDN problem

Also try 'debug isdn standard/q921/q931/error' then do a 'clear int bri0/1/0' to see what particular errors come up while the layer 2 is on its way up.

If it's consistently happening at particular times of the day it could be a line fault being exacerbated by something environmental.

New Member

Re: ISDN problem

here is yhe q921 debug

15 08:50:11.142: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:50:12.142: ISDN BR0/1/0 Q921: User TX -> IDVER ri=0 ai=0

Jan 15 08:50:14.146: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 15 08:50:14.146: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

Jan 15 08:50:15.146: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

Jan 15 08:50:16.146: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:50:17.146: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:50:18.146: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

Jan 15 08:50:20.146: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 15 08:50:20.146: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:50:21.146: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:50:22.146: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

Jan 15 08:50:23.146: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

here is the isdn error debug

Jan 15 08:53:42.201: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?

Jan 15 08:53:42.241: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?

Jan 15 08:53:42.261: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

L2: sapi 63 tei 127 ces 0 ev 0x650

Jan 15 08:53:42.261: ISDN BR0/1/0 Q921: User TX -> IDVER ri=0 ai=0

Jan 15 08:53:42.269: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?

Jan 15 08:53:42.277: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?

Jan 15 08:53:42.293: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?

Jan 15 08:53:42.309: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?

thanks in advance

New Member

Re: ISDN problem

when I do the clear int command,this is the result

#

Jan 15 08:55:30.827: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Jan 15 08:55:30.827: ISDN BR0/1/0 Q921: User TX -> IDVER ri=0 ai=0

Jan 15 08:55:31.483: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

Jan 15 08:55:31.495: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 15 08:55:31.495: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

pencabciscme001#

Jan 15 08:55:32.495: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:55:33.495: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:55:34.495: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:55:34.507: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=0

Jan 15 08:55:34.507: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up

Jan 15 08:55:44.507: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:55:44.519: ISDN BR0/1/0 Q921: User RX <- RRf sapi=0 tei=0 nr=0

Jan 15 08:55:49.504: ISDN BR0/1/0 Q921: User RX <- SABMEp sapi=0 tei=0

Jan 15 08:55:49.504: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=0

Jan 15 08:55:59.504: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:55:59.516: ISDN BR0/1/0 Q921: User RX <- RRp sapi=0 tei=0 nr=0

Jan 15 08:55:59.516: ISDN BR0/1/0 Q921: User TX -> RRf sapi=0 tei=0 nr=0

Jan 15 08:56:00.504: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:01.504: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:02.504: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:03.504: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 15 08:56:03.504: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:04.504: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:05.504: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

Jan 15 08:56:06.504: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:07.504: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 0 changed to down

Jan 15 08:56:07.504: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Jan 15 08:56:07.504: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive

Jan 15 08:56:09.504: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 15 08:56:09.504: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:09.516: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=0

Jan 15 08:56:09.516: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up

Jan 15 08:56:19.520: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:20.520: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:21.520: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:22.520: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 15 08:56:23.520: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 15 08:56:23.520: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:24.520: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:25.512: ISDN BR0/1/0 Q921: User RX <- SABMEp sapi=0 tei=0

Jan 15 08:56:25.516: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=0

Jan 15 08:56:25.520: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 15 08:56:26.512: ISDN BR0/1/0 Q921: User RX <- SABMEp sapi=0 tei=0

Jan 15 08:56:26.516: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=0

Jan 15 08:56:26.520: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Silver

Re: ISDN problem

There are several isues (bugs) with 12.3T train related to VIC2-2BRI-NT/TE. I had strange problems with 12.3(8), after upgrading to 12.4.11T all my problem where gone.

Also, check to see if there is any time based access-list that might block traffic (because you mention that it works in a very specific timeframe only). If so, disable them and see if the problem still exists, if not then I would recommend the upgrade.

HTH,

Leo

New Member

Re: ISDN problem

I have another router with same IOS working perfectly in other line like this.

I don?t have any time based access-list

thanks

Hall of Fame Super Gold

Re: ISDN problem

Hi carlos,

looks like the problem is in the ISDN line or at least the cabling. See above, the router and the switch can't come to good term to pretty much anything. I woulr reccommend, have the line checked by the telco, and the cabling, remember it not like and ethernet cable, altought for short distances it will work.

New Member

Re: ISDN problem

The first Thing I supposed was that the line was bad, becouse this configuration was working properly for 7 months, but the telco tecnician after do test on the line says that the line is correct (I call for 5 times and all the test in the line are correct, they only checks at layer 1)and I dont know waht can I tell them to check.

thanks.

Hall of Fame Super Gold

Re: ISDN problem

can you change port on the router ?

Bronze

Re: ISDN problem

> and the cabling, remember it not like and ethernet cable, altought for short distances it will work.

Is there a special cable that should be used to terminate an ISDN BRI or PRI? We've mostly been using standard U568B CAT5E cables, but are having problems with one of our ISDN PRI's and it's looking like a cabling problem.

Hall of Fame Super Gold

Re: ISDN problem

Yes, the difference is in the pair twisting. 568B is twisted for ethernet, 1-2 and 3-6. T1 and E1 need to twist 1-2 and 4-5. See:

http://www.cisco.com/en/US/products/hw/routers/ps259/prod_technical_reference09186a00800a8585.html#wp38057

So if you are going from 568B cabling to T1, you will need to make the cable accordingly.

Hope this helps, if so please rate post!

New Member

Re: ISDN problem

Talk to the TELCO... almost sure that the circuit is inactive on their side.

Regards,

1888
Views
14
Helpful
13
Replies
CreatePlease to create content