VIC2 2BRI NTTE BRI ISDN status

Unanswered Question
Sep 3rd, 2007

Hi,

The L2 for the ISDN line keeps going UP and down and it is State = MULTIPLE_FRAME_ESTABLISHED.

I have attached a file showing my BRI Config, and the errors I am getting. Is this a telco issue?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
p.holley Mon, 09/03/2007 - 12:12

The IOS verion is flash:c2800nm-spservicesk9-mz.124-11.XW2.bin

Debug isdn q921:

*Sep 3 20:11:14.219: ISDN BR0/0/1 Q921: User TX -> IDVER ri=0 ai=0

*Sep 3 20:11:16.215: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/1, TEI 0 changed to down

*Sep 3 20:11:16.215: ISDN BR0/0/1 Q921: L2_EstablishDataLink: sending SABME

*Sep 3 20:11:16.215: ISDN BR0/0/1 Q921: User TX -> SABMEp sapi=0 tei=0

*Sep 3 20:11:16.247: ISDN BR0/0/0 Q921: User RX <- UAf sapi=0 tei=0

*Sep 3 20:11:16.247: ISDN BR0/0/1 Q921: User RX <- UAf sapi=0 tei=0

*Sep 3 20:11:16.247: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/1, TEI 0 changed to up

*Sep 3 20:11:16.251: ISDN BR0/0/0 Q921: User TX -> IDVER ri=0 ai=0

*Sep 3 20:11:18.251: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 0 changed to down

*Sep 3 20:11:18.251: ISDN BR0/0/0 Q921: L2_EstablishDataLink: sending SABME

*Sep 3 20:11:18.251: ISDN BR0/0/0 Q921: User TX -> SABMEp sapi=0 tei=0

*Sep 3 20:11:18.283: ISDN BR0/0/0 Q921: User RX <- UAf sapi=0 tei=0

*Sep 3 20:11:18.283: ISDN BR0/0/1 Q921: User RX <- UAf sapi=0 tei=0

*Sep 3 20:11:18.283: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/0, TEI 0 changed to up

*Sep 3 20:11:18.287: ISDN BR0/0/1 Q921: User TX -> IDVER ri=0 ai=0

*Sep 3 20:11:20.287: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/1, TEI 0 changed to down

*Sep 3 20:11:20.287: ISDN BR0/0/1 Q921: L2_EstablishDataLink: sending SABME

*Sep 3 20:11:20.287: ISDN BR0/0/1 Q921: User TX -> SABMEp sapi=0 tei=0

*Sep 3 20:11:20.319: ISDN BR0/0/0 Q921: User RX <- UAf sapi=0 tei=0

*Sep 3 20:11:20.319: ISDN BR0/0/1 Q921: User RX <- UAf sapi=0 tei=0

*Sep 3 20:11:20.319: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/1, TEI 0 changed to up

Paolo Bevilacqua Mon, 09/03/2007 - 12:54

Hi,

to what are you connecting to ? There is no answer to IDVER packet. Try configuring 'isdn skipsend-idverify'.

hope this helps, please rate post if it does!

p.holley Mon, 09/03/2007 - 15:07

i have no eyes on the site, working remotely. But I think the BRI cards are connected to a TA. The engineer says a cable from the telco terminates on a box, and from that box two cat 5 cables are termintated on the cards on the router.

the isdn skipsend-idverify command, is this a global or int bri command? and what does it do exactly

Paolo Bevilacqua Mon, 09/03/2007 - 15:21

Hi,

1st of all, Ethernet Cat 5 cables are wrong for BRI. The twisting of pairs is different. This may cause problem on lengthy wires, however it does not appear to be your case. Anyway a possibility is that the TA does not receive any data from router. Actually, if you are conecting to a telco circuit, the box is called an NT and not a TA.

Please rewire per standard BRI S/T pinout as specified in the interface manual.

The skipsend command, hidden in interface config mode prevents the router to use ID verify sequence that actually is standard in bringing layer 2 up.

p.holley Tue, 09/04/2007 - 04:02

Thanks.

i tried the isdn skipsend-idverify command, and it stopped flapping. I am now able to make outbound calls on one of the ports.

However the other port L2 is TEI_Asigned. It is not the BRI Cards, as I swapped the cabling around and the working port went down.

what I have noticed is that both ports will not stay in multiple-frame established state. Whichever port I shut and no shut on, stays in established state and the other port is TEI_Assigned.

If i take out the isdn skipsend-idverify, both ports begin to go up and down again.

what is the link for the correct pin outs for BRI Voice Card?

Any more ideas. Thanks

davieshuw Wed, 09/05/2007 - 08:54

I've got a standard Cat 5 cable plugged into our BRI and that works fine. (UK, BRI connected to and ISDN2)

Paolo Bevilacqua Wed, 09/05/2007 - 12:38

I didn't say it won't work, in fact it does, but because the pair twisting is different, you can have problem on longer distances.

alfbrt2133 Mon, 11/19/2007 - 12:03

Hi.

Now i have the same problem of yuo

Are you repair this problem?

can you help me??

thanks

Alfonso

Actions

This Discussion