VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
View previous topic :: View next topic |
Author |
Message |
mattdfong at gmail.com Guest
|
Posted: Fri Jun 19, 2009 1:19 am Post subject: [Freeswitch-users] Failure Causes in an Originate Statement |
|
|
I have two providers and want to first try to originate the call with provider A, and if that fails on certain failure causes attempt to originate the same call with provider B.
Normally I would do this using an | in the dial string like originate sofia/gatewayA/123456|sofia/gatewayB/123456
but I do not want it to fail over on failure codes like USER_BUSY or NO_ANSWER because then I'm simply wasting the second carrier's resources. instead I would like to set a which error codes are considered a failure. The wiki notes a failure_causes channel variable for bridged calls, but this does not seem to work in an originate statement like
originate {failure_causes='RECOVERY_ON_TIMER_EXPIRE',continue_on_fail=false}sofia/gateway/gatewaya.com/1XXXXXX |sofia/gateway/gatewayb.com/1XXXXXX 5000
Can anyone recommend a way to accomplish what I'm trying to do...preferably w/o mod_lcr?
Thanks. |
|
Back to top |
|
|
mrene_lists at avgs.ca Guest
|
Posted: Fri Jun 19, 2009 1:20 am Post subject: [Freeswitch-users] Failure Causes in an Originate Statement |
|
|
<action application="set" data="failure_causes=user_busy,recovery_on_timer_expire" /> and then originate it.
Math
On 19-Jun-09, at 1:16 AM, Matthew Fong wrote:
Quote: | I have two providers and want to first try to originate the call with provider A, and if that fails on certain failure causes attempt to originate the same call with provider B.
Normally I would do this using an | in the dial string like originate sofia/gatewayA/123456|sofia/gatewayB/123456
but I do not want it to fail over on failure codes like USER_BUSY or NO_ANSWER because then I'm simply wasting the second carrier's resources. instead I would like to set a which error codes are considered a failure. The wiki notes a failure_causes channel variable for bridged calls, but this does not seem to work in an originate statement like
originate {failure_causes='RECOVERY_ON_TIMER_EXPIRE',continue_on_fail=false}sofia/gateway/gatewaya.com/1XXXXXX |sofia/gateway/gatewayb.com/1XXXXXX 5000
Can anyone recommend a way to accomplish what I'm trying to do...preferably w/o mod_lcr?
Thanks.
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org (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 |
|
|
mattdfong at gmail.com Guest
|
Posted: Fri Jun 19, 2009 1:41 am Post subject: [Freeswitch-users] Failure Causes in an Originate Statement |
|
|
the script is not part of a session or dial plan.
On Thu, Jun 18, 2009 at 11:31 PM, Jason White <jason@jasonjgw.net (jason@jasonjgw.net)> wrote:
|
|
Back to top |
|
|
brian at freeswitch.org Guest
|
Posted: Fri Jun 19, 2009 8:08 am Post subject: [Freeswitch-users] Failure Causes in an Originate Statement |
|
|
If you're getting RECOVERY_ON_TIMER_EXPIRE then you have maybe a NAT issue.
/b
On Jun 19, 2009, at 1:38 AM, Matthew Fong wrote:
|
|
Back to top |
|
|
mattdfong at gmail.com Guest
|
Posted: Fri Jun 19, 2009 12:37 pm Post subject: [Freeswitch-users] Failure Causes in an Originate Statement |
|
|
recovery_on_timer_expire was just my example..
I actually just want to try carrier B on everything except no_answer or user_busy...
On Fri, Jun 19, 2009 at 6:06 AM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:
|
|
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
|