mike at jerris.com
Tue Dec 8 08:09:53 PST 2009
You definitely need to use the settings in combination for what you are trying to do. Can you explain a bit more what you want to do in what conditions and maybe we can suggest how to accomplish this. NORMAL_CLEARING is not a failure, so it can continue on after the bridge unless you specify otherwise.
On Dec 7, 2009, at 1:31 PM, Peter P GMX wrote:
> I have a Problem with continue_on_fail.
> I have setup a hunt group
> <action application="set" data="continue_on_fail=NO_ANSWER,USER_BUSY"/>
> <action application="bridge"
> data="sofia/external/219 at 10.11.12.243,sofia/external/223 at 10.11.12.234,sofia/external/236 at 10.11.12.188,sofia/external/101 at 10.11.12.245"/>
> <action application="bridge" data= (dialstring for fallback user )
> I want the fallback user to be called whenever none of the previously
> called 3 gateway numbers picks up or if they are all busy.
> Therefore continue_on_fail=NO_ANSWER,USER_BUSY
> The fallback user is called, however if any of the previously called
> gateways picks up and then hangs up, the fallback user is called afterwards.
> Means: The fallback user is always called.
> I had expected, that continue_on_fail=NO_ANSWER,USER_BUSY would not fire
> the next bridge if it gets a NORMAL_CLEARING.
> Am I thinking wrongly about this?
> I have added
> <action application="set" data="hangup_after_bridge=true"/>
> and this works, but I would like to specify more in detail the
> conditions when to follow the next hunt group entry.
More information about the FreeSWITCH-users