06-08-2015 08:25 AM - edited 03-17-2019 03:15 AM
Hello All,
I have an issue with a SIP trunk, The call manager is sending 404 not found message after it sent trying message, below is the setup. Kindly help me to understand why CUCM is not able to decode and send the call to the DN 5112. 5112 is the number our SIP provider is delivering.
SIP Server 10.0.0.4 ----------> 10.0.0.153 (IP address in the router where NAT enabled)------------->172.25.225.11 (CUCM).
INVITE From SIP Server to CUCM
14584742.001 |17:14:46.429 |AppInfo |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 1160 from 10.0.0.4:[5060]:
[14372617,NET]
INVITE sip:5112@10.0.0.153:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.0.0.4:5060;branch=z9hG4bKs3uc2t20dgj04lkn51s1.1
From: <sip:914467491300@97.56.30.7:51088;user=phone>;tag=127.0.0.1+1+a5380157+652ceee3
To: <sip:5112@97.208.31.204:5060;user=phone>
CSeq: 818076443 INVITE
Expires: 180
Min-SE: 3600
Session-Expires: 3600
Supported: replaces, timer
Content-Length: 313
Request-Disposition: fork, sequential
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, PRACK, INFO, REFER, UPDATE
Call-ID: 9AB0E358-1FFEC2pzsxRAnf9OsjW3of1wRXuUYiBxisHiIwiB6zBTeY79UsAJ92FonzIYhJx1BEJKAr
P-Asserted-Identity: <sip:914467491300@97.56.30.7;user=phone>
Privacy: none
Max-Forwards: 66
Contact: <sip:914467491300@10.0.0.4:5060;transport=udp>
Content-Type: application/sdp
User-Agent: Alcatel-Lucent 5020 MGC-8 8.1.0.11.SP1.1
v=0
o=root 2085757204 2085757204 IN IP4 10.0.0.4
s=session
c=IN IP4 10.0.0.4
t=0 0
m=audio 34732 RTP/AVP 0 8 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
TRYING CUCM to SIP server
14584746.001 |17:14:46.431 |AppInfo |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 10.0.0.4:[5060]:
[14372618,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.0.0.4:5060;branch=z9hG4bKs3uc2t20dgj04lkn51s1.1
From: <sip:914467491300@97.56.30.7:51088;user=phone>;tag=127.0.0.1+1+a5380157+652ceee3
To: <sip:5112@97.208.31.204:5060;user=phone>
Date: Mon, 08 Jun 2015 11:44:46 GMT
Call-ID: 9AB0E358-1FFEC2pzsxRAnf9OsjW3of1wRXuUYiBxisHiIwiB6zBTeY79UsAJ92FonzIYhJx1BEJKAr
CSeq: 818076443 INVITE
Allow-Events: presence
Content-Length: 0
NOT FOUND CUCM to SIP server
14584775.001 |17:14:46.436 |AppInfo |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 10.0.0.4:[5060]:
[14372619,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 10.0.0.4:5060;branch=z9hG4bKs3uc2t20dgj04lkn51s1.1
From: <sip:914467491300@97.56.30.7:51088;user=phone>;tag=127.0.0.1+1+a5380157+652ceee3
To: <sip:5112@97.208.31.204:5060;user=phone>;tag=4013311~b8eb621a-bc9d-4a8c-9274-855b9682f601-72288869
Date: Mon, 08 Jun 2015 11:44:46 GMT
Call-ID: 9AB0E358-1FFEC2pzsxRAnf9OsjW3of1wRXuUYiBxisHiIwiB6zBTeY79UsAJ92FonzIYhJx1BEJKAr
CSeq: 818076443 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
06-08-2015 12:35 PM
Hi
the Cause code 1 states either the number is unallocated/unassigned or number does not exist.
Please check the significant digits field on the sip trunk it should be set to >=4, or try changing it to All.
Also make sure the "Calling Search Space" in SIP trunk matches the 5112 device CSS.
-Venkatesh
06-08-2015 11:21 PM
Hi Venakatesh,
I set the significant digits to 4 and made sure that the CSS of the SIP trunk have the partition of 5112. Also tried assigning 5112 device CSS but its not working.
Thanks!
Jinto.
05-08-2016 04:33 AM
Hi folks,
Am facing similar issue. In my case, I have 10 digits and FAC enabled.
Did you guys manage to solve the issue?
regards,
Ritesh Desai
05-10-2016 02:23 AM
Hi Ritesh,
Can you please share more details? Original issue reported is about call rejection during inbound call, what you're mentioning with respect to FAC shouldn't have any interaction as FAC is only applicable for outbound calls.
- Vivek
05-10-2016 02:40 AM
Dear Vivek,
Thanks for revert. My problem got resolved.
regards,
Ritesh Desai.
05-10-2016 03:57 AM
Thanks Ritesh for updating us.
- Vivek
05-10-2016 07:55 PM
Here is the link to Ritesh's issue:
https://supportforums.cisco.com/discussion/13017311/force-authorization-outgoing-calls
05-10-2016 10:40 PM
Thanks for sharing.
- Vivek
01-09-2017 02:45 AM
Ritesh, can you please share how did the problem get resolved? I am facing a similar issue.
01-09-2017 04:55 AM
Can you please explain more in detail. SIP 404 means system did not find what it's looking for. OR else you can raise new thread/discussion.
regards,
Ritesh Desai.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide