**ERROR**: host_incoming_call: Received a call with a bad bearer cap

Answered Question
Feb 27th, 2008
User Badges:

Hi,


I have a 1700 running Version 12.2(8)YN, acting as a voice gateway with ISDN BRI lines.


Everything works find, and it has been running for years without a problem.


Now, when I try and divert calls from a Mobile to my ISDN DDI, I get the above error message.



A ISDN debug is as below


Both called and calling part numbers show up correctly ! (I have xxxx them out)


The BRI Config is as below



interface BRI2/0

description BT line

no ip address

no logging event link-status

isdn switch-type basic-net3

isdn incoming-voice voice

isdn map address .* plan unknown type unknown

isdn static-tei 0

!

interface BRI2/1

no ip address

no logging event link-status

isdn switch-type basic-net3

isdn incoming-voice voice

isdn map address .* plan unknown type unknown

isdn static-tei 0





*Mar 15 22:22:35.732: ISDN BR2/1 Q931: RX <- SETUP pd = 8 callref = 0x01

Sending Complete

Bearer Capability i = 0x9090A3

Standard = CCITT

Transer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Facility i = 0x91A1240202400002010F301B0201010A0100A113A011A10F0A0102120A37393434303335313730

- ETSI Supplementary Service, Invoke, Diverting leg 2

Progress Ind i = 0x8483 - Origination address is non-ISDN

Calling Party Number i = '!', 0x83, 'xxxxxxxxxx'

Plan:ISDN, Type:National

Called Party Number i = 0x81, 'xxxxx'

Plan:ISDN, Type:Unknown

*Mar 15 22:22:35.736: ISDN BR2/1 **ERROR**: host_incoming_call: Received a call with a bad bearer cap from <unknown> on B1

*Mar 15 22:22:39.718: ISDN BR2/1 Q931: RX <- SETUP pd = 8 callref = 0x01

Sending Complete

Bearer Capability i = 0x9090A3

Standard = CCITT

Transer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Facility i = 0x91A1240202400002010F301B0201010A0100A113A011A10F0A0102120A37393434303335313730

- ETSI Supplementary Service, Invoke, Diverting leg 2

Progress Ind i = 0x8483 - Origination address is non-ISDN

Calling Party Number i = '!', 0x83, 'xxxxxxxxx'

Plan:ISDN, Type:National

Called Party Number i = 0x81, 'xxxxx'

Plan:ISDN, Type:Unknown

*Mar 15 22:22:39.722: ISDN BR2/1 **ERROR**: host_incoming_call: Received a call with a bad bearer cap from <unknown> on B1

*Mar 15 22:22:43.625: ISDN BR2/1 Q931: RX <- DISCONNECT pd = 8 callref = 0x01

Cause i = 0x82E6 - Recovery on timer expiry

*Mar 15 22:22:43.625: ISDN BR2/1 Q931: L3_Go: L3_GetUser_NLCB returned NULL cid 0x0 cr 0x81 ev 0x45 ces 1 -- Message ignored

*Mar 15 22:22:43.629: ISDN BR2/1 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x81

Cause i = 0x80D1 - Invalid call reference value




For a normal call, the ISDN is as below




*Mar 15 22:43:55.798: ISDN BR2/1 Q931: RX <- SETUP pd = 8 callref = 0x01

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Calling Party Number i = '!', 0x80, 'xxxxxxx'

Plan:ISDN, Type:National

Called Party Number i = 0x81, 'xxxx'

Plan:ISDN, Type:Unknown




Obviously the bearer capability is causing the problem, but I cant seem to figure out how to fix it !!


I tried setting bearer-cap speech and 3100hz on the BRI voice ports, but that does not seem to help !!


Any idea how I can fix this ??


Thanks

Correct Answer by smvoicerite about 9 years 2 months ago

Just wanted to flag this issue as resolved

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
shahedvoicerite Wed, 02/27/2008 - 05:59
User Badges:


After I upgraded the IOS to 12.3, I now get :-


Rejecting call, calltype screening failed


I am translating the calling number on the Voice Port, but I have


translation-rule 90

Rule 0 ^0 900 ANY unknown


and


isdn map address .* plan unknown type unknown


So, I cant understand what the problem may be.


Any ideas ?


Thanks

shahedvoicerite Wed, 02/27/2008 - 06:07
User Badges:

Actually the IOS upgrade solved my problem.


I had made some chages to the config, that rejected 3100hz audio and did not realise it was still there !!



Correct Answer
smvoicerite Wed, 02/27/2008 - 06:11
User Badges:

Just wanted to flag this issue as resolved

Actions

This Discussion