[cisco-voip] What SIP response code does CUCM need to try another trunk?

[Dave Goodwin]

Robert, I believe there is a service parameter for CallManager called
something like "Stop Routing on Unallocated Number Flag" which you could
change to False. While I haven't tried changing that to route past a 404
not found code on a SIP trunk to try the next route in a route list, I
believe it may do what you want. Under normal circumstances, most systems
probably want to keep that flag set to True, because there is no point
trying to extend a call twice to a PSTN number that you were told was
invalid. Once should be enough.

-Dave

On Mon, Jun 8, 2015 at 7:42 PM, Robert Kulagowski <rkulagow at gmail.com>
wrote:

> We're looking to make our trunking more robust. We've had occasions
> where we get a 404 from our provider for a call which _should_ work.
> We're troubleshooting that.
>
> The 404 makes CUCM stop processing, even if there's more than one
> trunk group (I'm thinking SIP as a primary, with PRI as a secondary)
>
> If I rewrite the 404 into something else on the SBC, will that work?
> If yes, what does CUCM look for to try the next entry?
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150608/f6cab755/attachment.html>