I have a route group with 2 members, the first is a SIP trunk and the second one is a PRI line. The problem is, when a call is routed through the SIP trunk and for some reason the SIP gateway replies with "486 busy here" or "503 service unavailable", Callmanager (version 7.1) will drop the call instead of trying to route it through the second member of the route group (the PRI line). Is there any way to force CCM to always try the next route group member, when it receives a SIP 483 or 503 response? (setting "Stop Routing on User Busy Flag" to false under service parameters won't do the trick)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
