Disconnect cause code = 58

wilson_1234_2 · ‎10-25-2012

I have a number that when dialed, rings once, then returns a fast busy.

"debug voip ccapi inout" shows the the call disconnects with:

Call Entry(Disconnect Cause=58

According to what I have found, cause 58 = Bearer Capability Not Presently Available

Which would indicate perhaps a codec issue?

I see in the debug that this call does not seem to be negotiating a codec whereas the other calls do.

There are other numbers that are getting mached with the same dial peers and are going out with no problem.

Anyone have any thoughts on this?

Chris Deren · ‎10-25-2012

What circuit is it? If this is PRI or BRI do you have this:

voice-port 0/0/0

bearer-cap Speech

Chris

wilson_1234_2 · ‎10-25-2012

Sorry Chris, I should have mentioned this is a SIP trunk and we are set up to round robin outbound calls to two different CUBE routers.

I see the same results on both CUBE routers.

Another thing I see on the bad call is this:

031922: Oct 25 09:58:22.514 EDT: //2192369/80D87308A214/CCAPI/cc_api_call_proceeding:
Interface=0xC063F02C, Progress Indication=NULL(0)

Not sure what the Progress Indication = NULL means, but the call that makes it out does not do this.

At the same point in the good call I see this:

031240: Oct 23 13:22:49.893 EDT: //2161217/000054434F0C/CCAPI/cc_api_call_proceeding:

031257: Oct 23 13:22:51.493 EDT: //2161217/000054434F0C/CCAPI/cc_api_event_indication:
   Event=156, Call Id=2161217
031258: Oct 23 13:22:51.493 EDT: //2161217/000054434F0C/CCAPI/cc_api_event_indication:
   Event Is Sent To Conferenced SPI(s) Directly
031259: Oct 23 13:22:51.493 EDT: //2161217/000054434F0C/CCAPI/cc_api_event_indication:
   Event=90, Call Id=2161217
031260: Oct 23 13:22:51.493 EDT: //2161217/000054434F0C/CCAPI/cc_api_event_indication:
   Event Is Sent To Conferenced SPI(s) Directly
031261: Oct 23 13:22:51.493 EDT: //2161217/000054434F0C/CCAPI/cc_api_caps_ind:
   Destination Interface=0x0, Destination Call Id=-1, Source Call Id=2161217,
   Caps(Codec=0x0, Fax Rate=0x2, Vad=0x2,
   Modem=0x0, Codec Bytes=20, Signal Type=2)

Chris Deren · ‎10-25-2012

Please post "debug ccsip messages" for the call.

Chris

wilson_1234_2 · ‎10-25-2012

I should have looked there as well.

I do see this:

SIP/2.0 606 Not acceptable

033323: Oct 25 11:28:05.403 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:6441188@1.2.3.4:5107 SIP/2.0
Via: SIP/2.0/UDP 10.2.7.1:5060;branch=z9hG4bK24652F8
Remote-Party-ID: <8631234567>;party=calling;screen=yes;privacy=off
From: <8631234567>;tag=C16D1D08-1155
To: <6441188>
Date: Thu, 25 Oct 2012 15:28:05 GMT
Call-ID: 68043040-1DEF11E2-BF928016-32B5BF29@10.2.7.1
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0007796880-2237305096-2568351492-0184252666
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1351178885
Contact: <8631234567>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 297

v=0
o=CiscoSystemsSIP-GW-UserAgent 9376 4265 IN IP4 10.2.7.1
s=SIP Call
c=IN IP4 10.2.7.1
t=0 0
m=audio 18840 RTP/AVP 18 101 19
c=IN IP4 10.2.7.1
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20

033324: Oct 25 11:28:05.439 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.2.7.1:5060;branch=z9hG4bK24652F8
From: <8631234567>;tag=C16D1D08-1155
To: <6441188>
Call-ID: 68043040-1DEF11E2-BF928016-32B5BF29@10.2.7.1
CSeq: 101 INVITE
Timestamp: 1351178885

033329: Oct 25 11:28:06.219 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.2.7.1:5060;branch=z9hG4bK24652F8
From: <8631234567>;tag=C16D1D08-1155
To: <6441188>;tag=92293714-1351178885793
Call-ID: 68043040-1DEF11E2-BF928016-32B5BF29@10.2.7.1
CSeq: 101 INVITE
Timestamp: 1351178885
Supported:
Contact: <6441188>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Content-Length: 0

033330: Oct 25 11:28:07.403 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 606 Not acceptable
Via: SIP/2.0/UDP 10.2.7.1:5060;branch=z9hG4bK24652F8
From: <8631234567>;tag=C16D1D08-1155
To: <6441188>;tag=92293714-1351178885793
Call-ID: 68043040-1DEF11E2-BF928016-32B5BF29@10.2.7.1
CSeq: 101 INVITE
Timestamp: 1351178885
Content-Length: 0

033331: Oct 25 11:28:07.407 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:6441188@1.2.3.4:5107 SIP/2.0
Via: SIP/2.0/UDP 10.2.7.1:5060;branch=z9hG4bK24652F8
From: <8631234567>;tag=C16D1D08-1155
To: <6441188>;tag=92293714-1351178885793
Date: Thu, 25 Oct 2012 15:28:05 GMT
Call-ID: 68043040-1DEF11E2-BF928016-32B5BF29@10.2.7.1
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

Chris Deren · ‎10-25-2012

Is 6441188 the number you should be dialing? Do other 7 digit numbers work? Assuming this is US can you try dialing it as 11 digits with 1+area code+number?

SIP/2.0 606 Not acceptable basically means the provider cannot route it with these digits.

Chris

wilson_1234_2 · ‎10-25-2012

Yes,

That number is correct and other seven digit numbers work with no problem. Other 644-xxxx numbers work with no problems.

I will check with the carrier and see what they are getting, unless you have any other suggestions Chris.

Chris Deren · ‎10-25-2012

I would definitely check with the provider at this point.

Chris

wilson_1234_2 · ‎10-25-2012

Thanks again Chris for the great information.