Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Users might experience few discrepancies in Search results. We are working on this on our side. We apologize for the inconvenience it may have caused.
New Member

Bearer capability not implemented

Hi,

We are currently getting transfer issue on our network. When received incoming call to our attendant console then we attempt transfer from AC to outside mobile via PRI, I get cause=65 from debug voice ccapi inout aswell going out the correct dial peer which is Outgoing Dial-peer=9000

Same result when using Cisco IP Phone, call receive then transfer to outside mobile via PRI.

Also, under the Device -> Gateway, when I check Media Termination Point Required the transfer works but takes down other service such as our Fax.

CUCM 7.1.5

H323 to Voice Gateway

E1 PRI

See attached running config and Q931 debug.

Help please.

Everyone's tags (2)
4 REPLIES
VIP Super Bronze

Bearer capability not implemented

My guess is that the carrier doesn't like the ANI you're sending here. You may be missing an External Phone Number Mask somewhere in CUCM.

002740: Aug  9 2012 01:48:19.591 UTC: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x077E

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98383

                Exclusive, Channel 3

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

SVC-PLV-VG1#

        Calling Party Number i = 0x00A1, '88101'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '0611741176'

                Plan:Unknown, Type:Unknown

Please remember to rate helpful responses and identify helpful or correct answers.

Hall of Fame Super Gold

Re: Bearer capability not implemented

Jonathan Schulenberg wrote:

My guess is that the carrier doesn't like the ANI you're sending here. You may be missing an External Phone Number Mask somewhere in CUCM.

Can't be, because CM is disconnecting, not CO:

002740: Aug  9 2012 01:48:19.591 UTC: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x077E

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98383

                Exclusive, Channel 3

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

SVC-PLV-VG1#

        Calling Party Number i = 0x00A1, '88101'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '0611741176'

                Plan:Unknown, Type:Unknown

002741: Aug  9 2012 01:48:19.615 UTC: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8  callref = 0x877E

        Channel ID i = 0xA98383

                Exclusive, Channel 3

        Progress Ind i = 0x8088 - In-band info or appropriate now available

002742: Aug  9 2012 01:48:19.887 UTC: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x877E

        Channel ID i = 0xA98383

                Exclusive, Channel 3

002743: Aug  9 2012 01:48:20.087 UTC: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x077E

        Cause i = 0x80C1 - Bearer capability not implemented

I don't know much about CM but it may be short of media resources or something.

VIP Super Bronze

Re: Bearer capability not implemented

Nice catch Paolo; clearly it's time for sleep here.

We would need detailed-level SDI traces from CUCM to figure out why it tore this call down. If you collect them be sure to also give us the matching Q931 traces again so we have a shot at matching it up in the SDI logs.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml#calm

Please remember to rate helpful responses and identify helpful or correct answers.

New Member

Bearer capability not implemented

Thanks guys for the reply.

This has been working since we completed upgrade to CUCM 7.1.5 last year. Problem started recently around a couple of weeks ago.

I will get the trace ready according to the link above and get TAC to have a look.

Thanks again guys.

4655
Views
10
Helpful
4
Replies
CreatePlease to create content