Cisco CUBE SIP trunk call out fail

[Kosi227]

Hi all,

one of our customer facing a issues when trying use the SIP trunk to call out

CUCM10.5 ->SIP Trunk-->CUBE-->SIP-->TELCO

customer can receive the call from the telco via this sip ,and works fine. But when customer trying to make a call out will get the fast busy tone. i try to use debug voip ccapi inout and found the disconnect cause as below:

Disconnect Cause (CC) : 41
Disconnect Cause (SIP) : 500

the full log is attached for reference , please help.

thanks !

[vladpetra]

Hello simontse227

Can you attach your config of the CUBE for a review?

[Kosi227]

ok, please find the running config in attached

more information that:

this cube have E1 and SIP trunk connection from provider , we use cor list to control the extension to use which path to call out. extension 38XXX will use SIP , and extension 35XXX will use the E1. and the E1 is working fine with any issues

and more information from customer , they can use the this SIP trunk to make the international call (eg. 0061XXXXXX) , only the local call will fail with fast busy tone...so strange...

thanks !

[gsikarwar]

Check If "shutdown" command is there under voice service voip ?

[Kosi227]

yes, we check it already, all dial peer and voip service is active now

[Dennis Mink]

can you share the debug csip message output of a failing call.  

[Kosi227]

here you are, i just capture one of fail call message . thanks !

[R0g22]

You are getting a 500 from ITSP -

007227: May 24 10:17:55: //61178/0051DDA94C01/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 500 Server Internal Error

Via: SIP/2.0/UDP 191.1.5.105:5060;branch=z9hG4bK8C9B1F1F

Record-Route: <sip:191.0.16.181:5060;transport=udp;lr>

Call-ID: 80D3BA22-5E2F11E8-AAE5CAAC-C4684751@191.1.5.105

From: "Crystal Zhou"<sip:50298107@191.1.5.105>;tag=3FEABB88-106F

To: <sip:62793502@191.0.16.181>;tag=sbc0406127.0.0.1alUtKGp-02092+1+d89c01a0+74ec8562

CSeq: 101 INVITE

Server: Alcatel-Lucent 5060 MGC-8 9.8.0.2.0.29

Supported: replaces,path,100rel,timer

Contact: <sip:62793502@191.0.16.181:5060>

Expires: 180

Content-Length: 0

You can contact them and see what is going on.

[gmgarrian]

I agree with Nipun, you'll need to contact your service provider.

You may need to change something on your end but they'll have to tell you what they don't like about the INVITE.  It can be incorrect source IP, calling number, or they require EO instead of DO.  Or, it might be something completely on their end.

[Kosi227]

thanks all, will try to contact the service provider to check the issues !