continue_on_failbleg拨号失败后是否继续执行,不继续就直接挂断aleghangup_after_bridgebleg挂断后是否挂断alegransfer_after_bridgebleg挂断后,alegtransfer目的的 park_after_bridgebleg挂断后,aleg是否park,esl开发接口非常有用exec_after_bridge_appbleg挂断后后,aleg执行一个APPapi_after_bridgebleg挂断后后,a...
1. continue_on_fail 控制无法接通被叫方(忙/离线)时发生的情况。如果true拨号计划继续被处理。如果false拨号计划将停止处理。可以包含将继续失败的返回消息。 <action application="set" data="continue_on_fail=true"/> <action application="set" data="continue_on_fail=NORMAL_TEMPORARY_FAILURE,USER_BUSY,NO...
1. continue_on_fail 控制无法接通被叫方(忙/离线)时发生的情况。如果true拨号计划继续被处理。如果false拨号计划将停止处理。可以包含将继续失败的返回消息。 <actionapplication="set"data="continue_on_fail=true"/><actionapplication="set"data="continue_on_fail=NORMAL_TEMPORARY_FAILURE,USER_BUSY,NO_ANSWER,...
originate_continue_on_timeout The originate_continue_on_timeout is set to true for this: if the bridge’s dial string specifies several destinations separated by the «|» (this is for failover), the bridge will time out on an unanswered destination and will attempt the next specified de...
continue_on_fail continue_on_fail Created by Ryan Harris, last modified on 2018.02.07 continue_on_fail string Controls what happens when the called party can not be reached (busy/offline). Iftruethe dialplan continues to be processed. Iffalsethe dialplan will stop processing. Can contain ...
continue_on_fail=trueA–>freeswitch–>B,A拨打B,如果B没接通直接挂断,那么会继续执行,比如后续可能会自动应答,有ring_back,或者语音信箱。 11)hash哈希表,一般会增删改查一些数据到哈希表 通过查询hash key获取value12)log输出日志,data需要写需要输出的内容,ERR表示log level ...
> 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. ...
<action application="set" data="continue_on_fail=true"/> <action application="set" data="dtmf_type=info"/> <!-- 解决不能二次拨号--> <action application="export" data="nolocal:execute_on_answer=start_dtmf"/> <!-- 解决不能二次拨号--> ...
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"/> ...
<action application="set" data="continue_on_fail=USER_BUSY,NO_ANSWER”/> 其他可能的值有:NORMAL_TEMPORARY_FAILURE(临时故障),TIMEOUT(超时),NO_ROUTE_DESTINATION(呼叫不可达)。 接着往下看: <action application="answer"/> Dialplan执行到这里,Freeswitch会给主叫1000回送应答消息,以建立真正的媒体流,准备...