Failure Causes in an Originate Statement with |
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.
<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:
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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Mathieu Rene <mrene_lists@avgs.ca> wrote:
<action application="set" data="failure_causes=user_busy,recovery_on_timer_expire" /> and then originate it.
Or if you're originating from a script, set that as a channel variable first.
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> wrote:
Mathieu Rene <mrene_lists@avgs.ca> wrote:
<action application="set" data="failure_causes=user_busy,recovery_on_timer_expire" /> and then originate it.
Or if you're originating from a script, set that as a channel variable first.
_______________________________________________ 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
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:
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> wrote: Mathieu Rene <mrene_lists@avgs.ca> wrote:
<action application="set" data="failure_causes=user_busy,recovery_on_timer_expire" /> and then originate it.
Or if you're originating from a script, set that as a channel variable first.
_______________________________________________ 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
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> wrote:
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:
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> wrote:
Mathieu Rene <mrene_lists@avgs.ca> wrote:
<action application="set" data="failure_causes=user_busy,recovery_on_timer_expire" /> and then originate it.
Or if you're originating from a script, set that as a channel variable first.
_______________________________________________ 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
participants (4)
-
Brian West
-
Jason White
-
Mathieu Rene
-
Matthew Fong