VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
jaybinks at gmail.com
Guest
|
 Posted: Fri Jul 17, 2009 10:58 pm Post subject: [Freeswitch-users] 302 redirects and continue_on_fail=true |
 |
|
I have an upstream provider that utilizes a load balancer that spits back 302 redirects with contact headers
| Quote: | SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5080;rport=5080;branch=z9hG4bKB6peFDvXZ5S2F;received=xxx.xxx.xxx.xxx
From: "test" <[url=sip:xxxxxxxxxx@xxx.xxx.xxx.xxx]sip:xxxxxxxxxx@xxx.xxx.xxx.xxx[/url]>;tag=ByFF2244HHvmj
To: <[url=sip:61xxxxxx920@yyy.yyy.yyy.yy1]sip:61xxxxxx920@yyy.yyy.yyy.yy1[/url]>;tag=1288540-274799759-385876096-3219999652
Call-ID: f6dc8d30-edd7-122c-c98e-000e7f301839
CSeq: 117820807 INVITE
Contact: <[url=sip:61xxxxxx920@yyy.yyy.yyy.yy1:5062]sip:61xxxxxx920@yyy.yyy.yyy.yy1:5062[/url]>
Server: MERA MVTS3G v.3.10.2-49-Release
Content-Length: 0 |
in my dialplan I have multiple upstream suppliers in a failover setup so I setup some vars and sip headers then attempt the bridge.
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
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.
ive read that I can selectively exclude temporary failures from continue_on_fail but im not sure thats exact enough for this situation.
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 )
any help would be greatly appreciated as Im not sure the best way to resolve this.
Jay |
|
| Back to top |
|
 |
raul at etellicom.com
Guest
|
| Posted: Sat Jul 18, 2009 5:41 pm Post subject: [Freeswitch-users] 302 redirects and continue_on_fail=true |
|
|
You can set continue_on_fail to the major (or all) causes that you want
to handle and don't include 302 in those so it will continue to execute
the extension, for example:
continue_on_fail=NORMAL_TEMPORARY_FAILURE,USER_BUSY,NO_ANSWER,TIMEOUT,NO_ROUTE_DESTINATION,CALL_REJECTED,USER_NOT_REGISTERED
You can know more about the hangup causes here:
http://wiki.freeswitch.org/wiki/Hangup_causes
Regards,
Raul
On Sat, 2009-07-18 at 13:49 +1000, Jay Binks wrote:
| Quote: | I have an upstream provider that utilizes a load balancer that spits
back 302 redirects with contact headers
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP
xxx.xxx.xxx.xxx:5080;rport=5080;branch=z9hG4bKB6peFDvXZ5S2F;received=xxx.xxx.xxx.xxx
From: "test"
<sip:xxxxxxxxxx@xxx.xxx.xxx.xxx>;tag=ByFF2244HHvmj
To:
<sip:61xxxxxx920@yyy.yyy.yyy.yy1>;tag=1288540-274799759-385876096-3219999652
Call-ID: f6dc8d30-edd7-122c-c98e-000e7f301839
CSeq: 117820807 INVITE
Contact: <sip:61xxxxxx920@yyy.yyy.yyy.yy1:5062>
Server: MERA MVTS3G v.3.10.2-49-Release
Content-Length: 0
in my dialplan I have multiple upstream suppliers in a failover setup
so I setup some vars and sip headers then attempt the bridge.
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
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.
ive read that I can selectively exclude temporary failures from
continue_on_fail but im not sure thats exact enough for this
situation.
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 )
any help would be greatly appreciated as Im not sure the best way to
resolve this.
Jay
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
|
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org |
|
| Back to top |
|
|
jaybinks at gmail.com
Guest
|
| Posted: Sat Jul 18, 2009 7:03 pm Post subject: [Freeswitch-users] 302 redirects and continue_on_fail=true |
|
|
Sure however my concern is that NORMAL_TEMPORARY_FAILURE is a generic
failure and not only from 302 redirects. I'm not sure I'm game to do
this, unless Im being completly paranoid which is possible.
Can I get advice on this from a few
Other users ?
Jay
On 19/07/2009, at 8:29 AM, Raul Fragoso <raul@etellicom.com> wrote:
| Quote: | You can set continue_on_fail to the major (or all) causes that you
want
to handle and don't include 302 in those so it will continue to
execute
the extension, for example:
continue_on_fail=
NORMAL_TEMPORARY_FAILURE,
USER_BUSY,
NO_ANSWER,
TIMEOUT,NO_ROUTE_DESTINATION,CALL_REJECTED,USER_NOT_REGISTERED
You can know more about the hangup causes here:
http://wiki.freeswitch.org/wiki/Hangup_causes
Regards,
Raul
On Sat, 2009-07-18 at 13:49 +1000, Jay Binks wrote:
| Quote: | I have an upstream provider that utilizes a load balancer that spits
back 302 redirects with contact headers
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP
xxx.xxx.xxx.xxx:
5080;rport=5080;branch=z9hG4bKB6peFDvXZ5S2F;received=xxx.xxx.xxx.xxx
From: "test"
<sip:xxxxxxxxxx@xxx.xxx.xxx.xxx>;tag=ByFF2244HHvmj
To:
<sip:61xxxxxx920@yyy.yyy.yyy.yy1>;tag=1288540-274799759-385876096-3219999652
Call-ID: f6dc8d30-edd7-122c-c98e-000e7f301839
CSeq: 117820807 INVITE
Contact: <sip:61xxxxxx920@yyy.yyy.yyy.yy1:5062>
Server: MERA MVTS3G v.3.10.2-49-Release
Content-Length: 0
in my dialplan I have multiple upstream suppliers in a failover setup
so I setup some vars and sip headers then attempt the bridge.
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
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.
ive read that I can selectively exclude temporary failures from
continue_on_fail but im not sure thats exact enough for this
situation.
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 )
any help would be greatly appreciated as Im not sure the best way to
resolve this.
Jay
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
users
http://www.freeswitch.org
|
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
users
http://www.freeswitch.org
|
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
