06-10-2018 03:15 PM - edited 03-18-2019 12:26 PM
Hi guys,
I have a trunk from my CUCM to an Avaya, the SIP trunk was working fine, but suddenly the following error appeared, remote = 503, If I arrive by ICMP to the IP of the Avaya, I have restarted the SIP Trunk and the behavior is the same.
Thanks for the help.
06-10-2018 04:17 PM
06-10-2018 04:23 PM
06-10-2018 05:29 PM
06-10-2018 07:50 PM
Hi Stobar,
1) Make sure there is no changes made on Firewall in terms of port 5060 (or any other that is being used by CUCM-Avaya trunk.
2) Please send us the output of "utils dbreplication runtimestate" on Publisher of CUCM.
3) Is "Run On All Active Unified CM Nodes" option checked on the trunk configuration page?
Thanks,
Priyam Acharya
06-10-2018 07:58 PM
06-10-2018 08:38 PM
Hi,
Please collect packet captures from CUCM nodes and try resetting the SIP trunk in question.
Make sure before you collect packet captures under Device >> Device Settings >> SIP Profiles >> "Enable OPTIONS Ping to monitor destination status for Trunks with Service Type "None (Default)" is checked.
Thanks,
Priyam Acharya
06-11-2018 05:35 AM
Because this has been working before; are you using TLS across this trunk? If so have you checked for expired certs?
06-11-2018 03:52 PM - edited 06-11-2018 03:53 PM
.
06-11-2018 03:55 PM
Hello everyone,
They have found an inconvenience in Avaya, on that side there was the problem.
The weird thing is that Avaya always appeared UP.
Saludos,
06-11-2018 07:27 PM
awesome! what was it?
06-15-2018 07:58 PM
12-14-2022 05:06 PM
Case 1: SIP trunk between IP office and Call Manager.
When there is an incoming call from CUCM to IP Office, IP Office displays 503 service unavailable, destination incompatible cause 88.
Case 2: Cause code 88 - Incompatible destination.
Case1: Cisco Call Manager is sending the invite to IP Office without SDP and IP Office is rejecting the call with 503 service unavailable.To be fixed from CUCM side.
OR
Case2: Enable the option "Allow Empty INVITE" in SIP Advanced tab, this will allow the call to be established from IP Office without SDP.
12-15-2022 12:36 AM
Why you answering to a post, that's already years old and also seems to solved?
12-15-2022 10:11 AM
Because as mentioned by stobar1101: "The Avaya provider did not tell us what the problem was, but it took 4 days to restore the service."
I had a recent situation that is similar and I wanted to post the solution applied.
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