<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This can all be accomplished with standard bridge lines stacked one on top of the other with continue_on_fail set to the list of codes you wish to fail over with. You would also want to set hangup_after_bridge=true. Loopback should NEVER be used in this case.<div><br></div><div><a href="http://wiki.freeswitch.org/wiki/Channel_Variables#continue_on_fail">http://wiki.freeswitch.org/wiki/Channel_Variables#continue_on_fail</a></div><div><a href="http://wiki.freeswitch.org/wiki/Channel_Variables#hangup_after_bridge">http://wiki.freeswitch.org/wiki/Channel_Variables#hangup_after_bridge</a></div><div><br></div><div>/b</div><div><br><div><div>On Aug 11, 2009, at 9:46 AM, Phillip Jones wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thanks for the reply Brian.<br><br>I went through this fairly carefully with Mike Jerris - please see<br><a href="http://www.nabble.com/Calling-Multiple-Destinations-with-Failover-td24877157.html">http://www.nabble.com/Calling-Multiple-Destinations-with-Failover-td24877157.html</a><br><br>I am very open to any other mechanism that allows the calling multiple<br>destinations with carrier failover support. I would have thought this<br>is a fairly common requirement and is a fundamental requirement in my<br>application.<br><br>As always - your help is appreciated.</blockquote></div><br></div></body></html>