<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I have an upstream provider that utilizes a load balancer that spits back 302 redirects with contact headers <div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><span class="Apple-style-span" style="font-style: italic; ">SIP/2.0 302 Moved Temporarily</span><br><span class="Apple-style-span" style="font-style: italic; ">Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5080;rport=5080;branch=z9hG4bKB6peFDvXZ5S2F;received=xxx.xxx.xxx.xxx</span><br><span class="Apple-style-span" style="font-style: italic; ">From: "test" <<a href="sip:xxxxxxxxxx@xxx.xxx.xxx.xxx">sip:xxxxxxxxxx@xxx.xxx.xxx.xxx</a>>;tag=ByFF2244HHvmj</span><br><span class="Apple-style-span" style="font-style: italic; ">To: <<a href="sip:61xxxxxx920@yyy.yyy.yyy.yy1">sip:61xxxxxx920@yyy.yyy.yyy.yy1</a>>;tag=1288540-274799759-385876096-3219999652</span><br><span class="Apple-style-span" style="font-style: italic; ">Call-ID: f6dc8d30-edd7-122c-c98e-000e7f301839</span><br><span class="Apple-style-span" style="font-style: italic; ">CSeq: 117820807 INVITE</span><br><span class="Apple-style-span" style="font-style: italic; ">Contact: <<a href="sip:61xxxxxx920@yyy.yyy.yyy.yy1:5062">sip:61xxxxxx920@yyy.yyy.yyy.yy1:5062</a>></span><br><span class="Apple-style-span" style="font-style: italic; ">Server: MERA MVTS3G v.3.10.2-49-Release</span><br><span class="Apple-style-span" style="font-style: italic; ">Content-Length: 0</span></blockquote><div><div><br></div><div>in my dialplan I have multiple upstream suppliers in a failover setup so I setup some vars and sip headers then attempt the bridge.</div><div>if it fails I then go on to do the same thing for a few other suppliers ( setup headers, attempt bridge ) so because of this I use continue_on_fail=true</div><div><br></div><div>it appears Freeswitch sees the 302 as a temp failure and does not follow the redirect, and instead moves on to the next upstream and bridges there.</div><div><br></div><div>ive read that I can selectively exclude temporary failures from continue_on_fail but im not sure thats exact enough for this situation.</div><div>I do wish for continue_on_fail to ignore 302 moved temporarily but not ALL temporary failures ( for which there are probably many more causes )</div><div><br></div><div>any help would be greatly appreciated as Im not sure the best way to resolve this.</div><div><br></div><div>Jay</div></div></body></html>