03-02-2018 12:37 PM - edited 03-17-2019 12:20 PM
Hi
I have a communication problem because I try to dial from a CUCM to another CUCM using a SIP TRUNK, there is a route pattern in both, however the call is not completed, but from the other CUCM if the call is made.
This is what the log shows me:
SENDER: [SIPTrunkMToCUCMTelepresense] 10.10.50.220
GUID: 9bc5ea00-a991a20d-15602a-421a8c0@192.168.33.2
MSG_LABEL: 503 Service Unavailable
RECEIVER: 192.168.33.2
MAC_ADDRESS: SIPTrunkMToCUCMTelepresense
MSGTAG: 18898445
MSG_TYPE: UCM_CTRACE
CORRELATIONID: 2,100,14,173974.3^10.10.50.220^*
TIMESTAMP: 2018/03/02 13:12:13.549
Detailed Sip Message
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 192.168.33.2:5060;branch=z9hG4bK1a699412078b62
From: " 70078" < sip:70078@192.168.33.2> ;tag=6726498~39f5e661-6c3c-f206-ade4-f81e64c66686-41465062
To: < sip:41001@10.10.50.220> ;tag=1857616815
Date: Fri, 02 Mar 2018 19:14:27 GMT
Call-ID: 9bc5ea00-a991a20d-15602a-421a8c0@192.168.33.2
CSeq: 101 INVITE
Allow-Events: presence
Warning: 399 CUCM9 " Unable to find a device handler for the request received on port 43953 from 192.168.33.2"
Content-Length: 0
Message In Log File
2018/03/02 13:12:13.524|SIPL|0|TCP|IN|192.168.33.2|5060|SEP94D4690D1554|192.168.32.31|53068|2,100,14,173168.247^192.168.32.31^*|18898439|94d4690d-1554014b-19fed024-273cb4d5@192.168.32.31|INVITE
2018/03/02 13:12:13.525|SIPL|0|TCP|OUT|192.168.33.2|5060|SEP94D4690D1554|192.168.32.31|53068|2,100,14,173168.247^192.168.32.31^*|18898440|94d4690d-1554014b-19fed024-273cb4d5@192.168.32.31|100 Trying
2018/03/02 13:12:13.531|CC|SETUP|41465061|41465062|70078|41001|41001
2018/03/02 13:12:13.538|CC|OFFERED|41465061|41465062|70078|41001|41001|SEP94D4690D1554|SIPTrunkMToCUCMTelepresense
2018/03/02 13:12:13.546|SIPT|41465062|TCP|OUT|192.168.33.2|5060|SIPTrunkMToCUCMTelepresense|10.10.50.220|5060|2,100,13,36399.1^*^*|18898443|9bc5ea00-a991a20d-15602a-421a8c0@192.168.33.2|INVITE
2018/03/02 13:12:13.549|SIPT|41465062|TCP|IN|192.168.33.4|5060|SIPTrunkMToCUCMTelepresense|10.10.50.220|5060|2,100,14,173974.2^10.10.50.220^*|18898444|9bc5ea00-a991a20d-15602a-421a8c0@192.168.33.2|100 Trying
2018/03/02 13:12:13.549|SIPT|41465062|TCP|IN|192.168.33.2|5060|SIPTrunkMToCUCMTelepresense|10.10.50.220|5060|2,100,14,173974.3^10.10.50.220^*|18898445|9bc5ea00-a991a20d-15602a-421a8c0@192.168.33.2|503 Service Unavailable
2018/03/02 13:12:13.550|SIPT|41465062|TCP|OUT|192.168.33.2|5060|SIPTrunkMToCUCMTelepresense|10.10.50.220|5060|2,100,14,173974.3^10.10.50.220^*|18898446|9bc5ea00-a991a20d-15602a-421a8c0@192.168.33.2|ACK
2018/03/02 13:12:13.554|SIPL|41465061|TCP|OUT|192.168.33.2|5060|SEP94D4690D1554|192.168.32.31|53068|2,100,14,173974.3^10.10.50.232^*|18898447|94d4690d-1554014b-19fed024-273cb4d5@192.168.32.31|503 Service Unavailable
2018/03/02 13:12:13.558|SIPL|41465061|TCP|IN|192.168.33.2|5060|SEP94D4690D1554|192.168.32.31|53068|2,100,14,173168.248^192.168.32.31^*|18898448|94d4690d-1554014b-19fed024-273cb4d5@192.168.32.31|ACK
2018/03/02 13:12:13.559|CC|REJECT|41465061|41465062|70078|41001|41001|1459617833
Someone with a similar problem
03-02-2018 11:07 PM
Hi There,
When a 503 service unavailable message comes back from CUCM, it is usually due to one of the following reasons:
Can you try resetting the SIP trunks on both sides and checking the IP addresses and ports configured in the SIP trunks as well?
Hope this helps!
- Jon
03-06-2018 10:26 AM
Hello
If you have in both SIP Trunk the IP addresses of the CUCM, and of a CUCM if you can call us, but from another CUCM we can not.
03-03-2018 05:49 AM
this issue was raised before, did you verify:
cheers
03-04-2018 07:12 AM
Is "route on all nodes" checked on both SIP trunks and Route Lists?
05-14-2019 07:10 AM
It is works for me, thanks
02-16-2019 06:14 AM - edited 02-17-2019 03:16 PM
Did you fix this? I have this problem too.
02-17-2019 10:04 AM
1) check the destination of the siptrunk of the destination cluster. the ip from which the invite is coming should be trusted by the remote cluster.
2) check the sip security profile and check for the port it can accept and on which port you receive the invite.
3) is there any inspection enabled between the cluster? if so disable it for SIP traffic.
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