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

ISDN Calls - Bearer capability not implemented

Hi.

Many of the calls are established but only some of them are disconnected.
I have this log in the Cisco 2900
Jan 20 13:26:52.615: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x0166

        Cause i = 0x8090 - Normal call clearing

Jan 20 13:26:52.647: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x8166

Jan 20 13:26:52.647: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x0166

Jan 20 13:26:57.026: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Calling num 528181530100

Jan 20 13:26:57.026: ISDN Se0/0/0:15 Q931: Sending SETUP  callref = 0x0167 callID = 0x80E8 switch = primary-qsig interface = User

Jan 20 13:26:57.026: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0167

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98381

                Exclusive, Channel 1

        Calling Party Number i = 0x0080, '528181530100'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '233000'

                Plan:Unknown, Type:Unknown

Jan 20 13:26:57.046: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8167

        Channel ID i = 0xA98381

                Exclusive, Channel 1

Jan 20 13:26:57.050: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x8167

Jan 20 13:26:57.058: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8  callref = 0x8167

        Facility i = 0x9FAA068001008201008B0100A118020287DE020102800F44465F4154435F434F4E545F505041

        Progress Ind i = 0x8182 - Destination address is non-ISDN

Jan 20 13:26:57.058: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x0167

Jan 20 13:26:57.262: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x0167 Cause i = 0x80C1 - Bearer capability not implemented

Jan 20 13:26:57.290: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x8167

Jan 20 13:26:57.294: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x0167

Do you have any aidea ?

Thanks..

Everyone's tags (3)
6 REPLIES
Hall of Fame Super Silver

ISDN Calls - Bearer capability not implemented

Apply the following to your D-channel:

voice-port 0/0/0:23

bearer-cap Speech

!

Chris

New Member

ISDN Calls - Bearer capability not implemented

Hi Cris, thanks for your feedback.

I tried with this command but the problem continue.

Regards.

Hall of Fame Super Silver

ISDN Calls - Bearer capability not implemented

I've seen this caused by codec mismatch as well, could that be the issue here?

Chris

New Member

ISDN Calls - Bearer capability not implemented

Hi Chirs.

We´ve tried change the codecs but we don´t have results.

Do you know a debug command in order to detect the codec mismatch ?

Thanks.

Hall of Fame Super Silver

ISDN Calls - Bearer capability not implemented

To detect codec mismatch you would need to look at the voip protocol debugs, depending on protocol user it would be different commands, for SIP use "debug ccsip messages"

H323 - "debug h225" or "debug h245 asn1"

MGCP you would look at CCM SDI traces.

HTH,

Chris

New Member

Got to the bottom of this

Got to the bottom of this

For MGCP Gateways anyway .. 

On Call Manager - goto the gateway in question and drill into the Cisco MGCP T1 port config..

Scroll down and change the Channel IE Type from the default ..

USE Number when 1B OR Slotmap

TO the correct setting

Timeslot Number

PCM Type = u-law

thats for US T1 PRI

Hope that helps ..

7806
Views
5
Helpful
6
Replies
CreatePlease to create content