New DIDs unable to make outbound calls

[dspicer]

Hello,

I'm fairly new to CUCM and CUBE configurations. I have an existing system and we just recently purchased additional DIDs from our SIP provider.

I added the translation pattern in CUCM to send the new numbers to the CUBE for external dialing.

Then I added the numbers to the voice class e164-pattern-map "e164 +15716172..." and voice translation rules " rule 11 /^\(15716172...\)$/ /+\1/
rule 12 /^\(5716172...\)$/ /+1\1/" to the CUBE. Inbound calls work fine, but I get a "SIP/2.0 503 Service Unavailable" when dialing out.

System Path
CUCM (172.17.xxx.51-52) > CUBE (Internal 172.17.xxx.1, External 192.168.xxx.1) > SIP Provider Router (AdTran 192.168.xxx.2)

Looking for any assistance or ideas on what to look at.

Thanks,

Failed call log from CUBE.

10980577: Feb 16 10:09:50.164 EST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.17.xxx.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.xxx.52:5060;branch=z9hG4bK6c393413140ef
From: <sip:172.17.xxx.52>;tag=1904170349
To: <sip:172.17.xxx.1>
Date: Fri, 16 Feb 2024 15:09:50 GMT
Call-ID: 6cc1f880-1ef1eae0-62914-340011ac@172.17.xxx.52
User-Agent: Cisco-CUCM12.5
CSeq: 101 OPTIONS
Contact: <sip:172.17.xxx.52:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0

10980578: Feb 16 10:09:50.165 EST: //-1/xxxxxxxxxxxx/SIP/Error/httpish_msg_free:
Freeing NULL pointer!
10980579: Feb 16 10:09:50.165 EST: //3458234/43A938619B79/SIP/Error/sipSPIGetPeerByCalledPartyId:
input arg error
10980580: Feb 16 10:09:50.165 EST: //3458234/43A938619B79/SIP/Error/sipSPIUpdateCallInfo:
input argument error
10980581: Feb 16 10:09:50.166 EST: //3458234/43A938619B79/SIP/Error/sipSPIFlushDeferredQueue:
Invalid deferredQueue
10980582: Feb 16 10:09:50.166 EST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.xxx.52:5060;branch=z9hG4bK6c393413140ef
From: <sip:172.17.xxx.52>;tag=1904170349
To: <sip:172.17.xxx.1>;tag=DFB4508A-68B
Date: Fri, 16 Feb 2024 15:09:50 GMT
Call-ID: 6cc1f880-1ef1eae0-62914-340011ac@172.17.xxx.52
Server: Cisco-SIPGateway/IOS-16.12.4
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Accept: application/sdp

PBX-RT004#Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 366

v=0
o=CiscoSystemsSIP-GW-UserAgent 5062 5309 IN IP4 172.17.xxx.1
s=SIP Call
c=IN IP4 172.17.xxx.1
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 172.17.xxx.1
m=image 0 udptl t38
c=IN IP4 172.17.xxx.1
a=T38FaxVersion:3
a=T38MaxBitRate:33600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

PBX-RT004#
10980583: Feb 16 10:09:55.442 EST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.17.xxx.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.xxx.51:5060;branch=z9hG4bK600c92f41a00a
From: <sip:172.17.xxx.51>;tag=1047623878
To: <sip:172.17.xxx.1>
Date: Fri, 16 Feb 2024 15:09:55 GMT
Call-ID: 6fbce900-1ef1eae0-600c2-330011ac@172.17.xxx.51
User-Agent: Cisco-CUCM12.5
CSeq: 101 OPTIONS
Contact: <sip:172.17.xxx.51:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0

10980584: Feb 16 10:09:55.443 EST: //-1/xxxxxxxxxxxx/SIP/Error/httpish_msg_free:
Freeing NULL pointer!
10980585: Feb 16 10:09:55.443 EST: //3458235/46CE93B09B7A/SIP/Error/sipSPIGetPeerByCalledPartyId:
input arg error
10980586: Feb 16 10:09:55.443 EST: //3458235/46CE93B09B7A/SIP/Error/sipSPIUpdateCallInfo:
input argument error
10980587: Feb 16 10:09:55.444 EST: //3458235/46CE93B09B7A/SIP/Error/sipSPIFlushDeferredQueue:
Invalid deferredQueue
10980588: Feb 16 10:09:55.444 EST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.17.xxx.51:5060;branch=z9hG4bK600c92f41a00a
From: <sip:172.17.xxx.51>;tag=1047623878
To: <sip:172.17.xxx.1>;tag=DFB46527-FA3
Date: Fri, 16 Feb 2024 15:09:55 GMT
Call-ID: 6fbce900-1ef1eae0-600c2-330011ac@172.17.xxx.51
Server: Cisco-SIPGateway/IOS-16.12.4
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: kpml, telephone-event
Accept: application/sdp

PBX-RT004#Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 366

v=0
o=CiscoSystemsSIP-GW-UserAgent 6709 1550 IN IP4 172.17.xxx.1
s=SIP Call
c=IN IP4 172.17.xxx.1
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 172.17.xxx.1
m=image 0 udptl t38
c=IN IP4 172.17.xxx.1
a=T38FaxVersion:3
a=T38MaxBitRate:33600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

PBX-RT004#
10980589: Feb 16 10:10:27.745 EST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:91703728xxxx@172.17.xxx.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.17.xxx.52:5060;branch=z9hG4bK6c3962dca7b4a
From: "PHONE_532" <sip:15716172xxx@pbx.xxxxxxxxxxxx.com>;tag=6601309~0f8c084d-dac3-47b7-9c9f-8dd39ed71f16-49623616
To: <sip:91703728xxxx@172.17.xxx.1>
Date: Fri, 16 Feb 2024 15:10:27 GMT
Call-ID: 82cfb900-1ef1eae0-62916-340011ac@172.17.xxx.52
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM12.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:172.17.xxx.52:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 3afbbe8200105000a0005cb12ee1501f;remote=00000000000000000000000000000000
Cisco-Guid: 2194651392-0000065536-0000001679-0872419756
Session-Expires: 1800
P-Asserted-Identity: "PHONE_532" <sip:15716172xxx@pbx.xxxxxxxxxxxx.com>
Remote-Party-ID: "PHONE_532" <sip:15716172xxx@pbx.xxxxxxxxxxxx.com>;party=calling;screen=yes;privacy=off
Contact: <sip:15716172xxx@172.17.xxx.52:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP5CB12EE1501F"
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 373

v=0
o=CiscoSystemsCCM-SIP 6601309 1 IN IP4 172.17.xxx.52
s=SIP Call
c=IN IP4 172.16.xxx.115
b=TIAS:64000
b=AS:80
t=0 0
m=audio 25864 RTP/AVP 0 8 116 18 101
b=TIAS:64000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:116 iLBC/8000
a=maxptime:20
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

10980590: Feb 16 10:10:27.745 EST: //-1/xxxxxxxxxxxx/SIP/Error/httpish_msg_free:
Freeing NULL pointer!
SIP: (3458236) Attribute mid, level 1 instance 1 not found.
SIP: (3458236) setup attribute, level 1 instance 1 not found.
SIP: (3458236) connection attribute, level 1 instance 1 not found.
SIP: (3458236) Attribute label, level 1 instance 1 not found.
SIP: (3458236) a=framerate attribute, level 1 instance 1 not found.
SIP: (3458236) Attribute ptime, level 1 instance 1 not found.

[Shalid Kurunnan Chalil]

Hi there, 

When I get a new range of DDI or DID from the existing service provider, I may do the following;

My CUBE: Update the configuration to send the call to the call manager when an inbound call is made on any number within this DDI range.

• Update the dial peer to include the new DDI range or create a new dial peer.
• Update the translation rule if I want to translate the called number to a different number.

Call Manager: I will ensure that I have a dial plan entity for answering or number translation for these new DDIs.

1. A translation pattern to convert the DDI to an extension, if required.
2. Final extension / DN to accept the call.

But since your inbound calls are working fine, I believe it's already been updated, and no changes are required.

For outbound calls, generally, you don’t need to perform any actions unless you want to manipulate the calling or called numbers for an existing working setup. [provided your DDI is from the same existing service provider and via the existing SIP trunk from your service provider].

If you still have not resolved your issue, it's better to share the complete output of “debug ccsip messages” from your CUBE after making failed outbound calls. Please attach it as a text file rather than pasting the output in the thread. Also the running configuration of the CUBE after masking all the sensitive details from it. 

Regards, 

Shalid 

Disclaimer:

Responses are based on personal knowledge and experience. Consider them as guidance. Other members may offer different perspectives or better approaches. No responsibility is assumed for outcomes; discretion is advised.

[Maren Mahoney]

If that INVITE is from the CUBE it is clear that the CUCM is successfully sending the call out and that it is the CUBE that is unable to process the call. (Or, possibly, the CUCM is sending something weird to the CUBE.)

Your output does not show the 503 error. Would you please post the entire SIP exchange? It is easier if you put the file into Notepad++ and then post that (rather than pasting into the post window).

Even better, if you can post a debug from a successful call AND one from an unsuccessful call we should be able to determine the source of the problem.

Maren

[dspicer · Accepted solution]

Thank you for your replies. Turns out the SIP provider was at fault, just took them a week to figure it out.