<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 6, 2014 at 1:54 PM, Nick Altmann <span dir="ltr"><<a href="mailto:nick.altmann@gmail.com" target="_blank">nick.altmann@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Carrier is just a gateways list. You may also set weight for each gw<br>
and drouting will choose gw's due its weight.<br>
Route_to_carrier() gets carrier parameters (gateways list) into avps<br>
and set $ru to first gw address.<br>
Use_next_gw() extract next gw parameters from avps and set $ru to the<br>
new gateway.<br>
So, you may try to work with these avps to change routing behaviour.<br>
<div class="im HOEnZb"><br></div></blockquote><div><br></div><div style>Hello Nick, </div><div style><br></div><div style>Thank you for your response. After looking into it further I realized that this approach is not very scalable. The reason why</div>
<div style>is because we have over 30 interconnects (30 gateways), and would have to maintain all of them to the carrier table.</div><div style><br></div><div style>Is there not way to pass a gwlist list to a function dynamically (at run time) that will route to that call with failover? do_routing</div>
<div style>would be perfect! If it adheres to the order of the gateway list.</div><div style><br></div><div style>PS I really don't want to change the ruri in perl either if this functionality can be made available in the script.</div>
<div style><br></div><div style>Kind Regards,</div><div style><br></div><div style>Nick.</div></div></div></div>