[Freeswitch-users] Failure Causes in an Originate Statement with |

[Mathieu Rene]

<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 at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20090619/733fe4bd/attachment-0002.html