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)
I believe 483 and 503 are critical errors, and CUCM may not move to the next RG in line
user busy [Q.850]
This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy it is noted that the user equipment is compatible with the call.
no circuit/channel available [Q.850]
This cause indicates that there is no appropriate circuit/channel presently available to handle the call.
Although there's a spirit from the SIP RFC to suggest the implementation to retry the call on other endpoint.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...