ISDN problem "Received a call with a bad bearer cap" Layer 2 is not active

Unanswered Question
Sep 11th, 2007
User Badges:

Hello,


I'm having a ISDN problem that the L2 is not activated, but the link is able to dial-out and recieving the call by phone. I did some debug, but the router seems to only recieve something from ISDN switch, but never send out any.


Please see some result below.


We did some trouble shooting from below page, but it does not seeks to help.

http://www.cisco.com/en/US/customer/tech/tk801/tk379/technologies_tech_note09186a0080094b77.shtml


Your help is highly appliciated.. .. . :(



Regards,

Cats


=========================================


Router#sh isdn status

Global ISDN Switchtype = basic-net3

ISDN BRI0/3/0 interface

dsl 6, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

Layer 2 NOT Activated

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 6 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

Sep 11 09:09:15.023: ISDN BR0/3/0 Q921: User RX <- UI sapi=0 tei=127

Sep 11 09:09:15.027: ISDN BR0/3/0 **ERROR**: host_incoming_call: Received a call with a bad bearer cap from 818803459 on B1

Sep 11 09:09:19.302: ISDN BR0/3/0 Q921: User RX <- UI sapi=0 tei=127

Sep 11 09:09:19.306: ISDN BR0/3/0 **ERROR**: host_incoming_call: Received a call with a bad bearer cap from 818803459 on B1

Sep 11 09:27:06.814: ISDN BR0/3/0 Q921: User RX <- IDASSN ri=40852 ai=65

Sep 11 09:27:06.866: ISDN BR0/3/0 Q921: User RX <- UAf sapi=0 tei=65

Sep 11 09:27:12.714: ISDN BR0/3/0 Q921: User RX <- RR sapi=0 tei=65 nr=1

Sep 11 09:27:12.910: ISDN BR0/3/0 Q921: User RX <- INFO sapi=0 tei=65, ns=0 nr=1

Sep 11 09:27:17.565: ISDN BR0/3/0 Q921: User RX <- INFO sapi=0 tei=65, ns=1 nr=1

Sep 11 09:27:18.569: ISDN BR0/3/0 Q921: User RX <- RRp sapi=0 tei=65 nr=1

Sep 11 09:27:19.569: ISDN BR0/3/0 Q921: User RX <- RRp sapi=0 tei=65 nr=1

Sep 11 09:27:20.569: ISDN BR0/3/0 Q921: User RX <- RRp sapi=0 tei=65 nr=1

Sep 11 09:27:21.569: ISDN BR0/3/0 Q921: User RX <- SABMEp sapi=0 tei=65

Sep 11 09:27:22.569: ISDN BR0/3/0 Q921: User RX <- SABMEp sapi=0 tei=65

Sep 11 09:27:23.569: ISDN BR0/3/0 Q921: User RX <- SABMEp sapi=0 tei=65

Sep 11 09:27:24.568: ISDN BR0/3/0 Q921: User RX <- SABMEp sapi=0 tei=65

Sep 11 09:27:25.572: ISDN BR0/3/0 Q921: User RX <- SABMEp sapi=0 tei=65

Sep 11 09:27:25.576: ISDN BR0/3/0 Q921: User RX <- IDCKRQ ri=0 ai=65

Sep 11 09:27:26.556: ISDN BR0/3/0 Q921: User RX <- IDCKRQ ri=0 ai=65

Sep 11 09:27:26.568: ISDN BR0/3/0 Q921: User RX <- SABMEp sapi=0 tei=65

Sep 11 09:27:27.556: ISDN BR0/3/0 Q921: User RX <- IDREM ri=0 ai=65

Sep 11 09:27:27.560: ISDN BR0/3/0 Q921: User RX <- IDREM ri=0 ai=65

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
jsivulka Mon, 09/17/2007 - 06:33
User Badges:
  • Bronze, 100 points or more

In Europe the switch will bring the line down when the call is over and

no activity for a period of time to save power. Both the router and the

switch can bring the line up whenever there is an outgoing call.

Indeed the router didn't acknowledge the PROGRESS message. There are

quite a few changes in ISDN layer 2 code between 12.3 and 12.4. I

believe this problem is fixed in latest 12.4 image.

when the interface is down, you can check the status of layer 2 by issuing "show isdn status" can

you enable the debuging of the following


show isdn status


debug isdn q921

debug isdn q931

debug dialer

debug bri


then issue the follwoing command"


isdn call interface bri 0019003507243652803


what we should see is the router try to bring up the d channel to activate the call. ie we should

send out an "TEI REQUEST" followed by a "TEI allocate". then q931 should come up.


paolo bevilacqua Mon, 09/17/2007 - 11:42
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

in addition to the good advice above, suggest you configure "isdn tei-negotition preserve". So TEI is taken once for all and no more debating with the switch about it.

Actions

This Discussion