<div dir="ltr"><div><div>Hi Dave,<br><br></div>I was aware of that service parameter. Sadly, I don't think it can help in this case. What I need would be something like "Continue routing on Q.931 Disconnect Cause Code" and giving it the cause code 27 in order to continue routing.<br><br></div><div>Instead, I change the
<a name="StopRoutingOnUnallocatedNumberFlag">
Stop Routing on Unallocated Number Flag
</a>
to False (default True).<br><br></div><div>I was expecting this could trigger the pstn failover but my tests showed otherwise.<br><br></div><div>Thank you!<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-03-17 1:28 GMT+01:00 Dave Goodwin <span dir="ltr"><<a href="mailto:dave.goodwin@december.net" target="_blank">dave.goodwin@december.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Daniele, have you tried exploring the service parameter "Stop Routing on Q.931 Disconnect Cause Code" at all? I'm not certain it will be useful in your scenario, but if you haven't tried it, that may be an option for you. It's under Service Parameters > select server > select Cisco CallManager > click Advanced button and then search the page for the word cause.<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">For the other issue you mentioned where rerouting fails when the SIP trunk to SME is out of service, are you utilizing OPTIONS ping on the leaf cluster towards the SME? In order for the trunk device to be seen as out of service and another route selected, you need to make sure OPTIONS ping (configurable on a SIP profile) is applied to the SIP trunk.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Mar 16, 2018 at 1:29 PM, daniele visaggio <span dir="ltr"><<a href="mailto:visaggio.daniele@gmail.com" target="_blank">visaggio.daniele@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div><div><div><div><div><div><div>Good evening,<br><br></div>I want to enable rerouting for enterprise pattern learned via ILS.The scenario is a classic sme plus leaves.<br><br></div>Rerouting over pstn does not occur
for the following
cause codes:<br><br>- unallocated number<br>- user busy<br>- normal call clearing<br>- destination out of order<br>- service not available
<br><br></div>I'd like instead to trigger rerouting on
Q.850;cause=27
(destination out of order) and on service not available.<br><br></div>With cucm 11.5 this doesn't seem possible.<br><br></div>Destination out of order is the Q.850 code I get calling a unregistered phone (think srst scenario). In this case rerouting over pstn would be useful.<br><br></div>ILS rerouting over pstn does not trigger even if the outgoing sip trunk to sme is out of service (
503 Service Unavailable or 408 Timeout
). <br><br></div>The only scenario in which I managed to trigger the behavior is cac. Playing with locations is the only way I found to reroute over pstn.<br><br></div>Any thought on this?<br><br></div>thank you<br><div><div><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div></div>
<br></div></div>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailma<wbr>n/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>