Hello again! Ok, after spending several hours trying to debug why incoming calls didn't work, for two separate issues (2nd time I accidentally set "Do not disturb" on my VOIP client. Duh!), I am feeling slightly lazy... Anyone got a set of rules for outgoing calls (Australia) that they are willing to share? Even if I don't use it directly, it may help me understand this new XML based syntax (I am only really familiar with the Asterisk dialplan syntax). As a specific example of something I am unsure of, is it possible to have it try and dial using a sip provider, and if that fails try the zap port? I don't want it to fall back to the zap port though if the person doesn't answer or is engaged, only if there is a problem with the SIP connection (e.g. Internet connection down). Thanks. -- Brian May <brian@microcomaustralia.com.au>
Brian May <brian@microcomaustralia.com.au> wrote:
As a specific example of something I am unsure of, is it possible to have it try and dial using a sip provider, and if that fails try the zap port? I don't want it to fall back to the zap port though if the person doesn't answer or is engaged, only if there is a problem with the SIP connection (e.g. Internet connection down).
http://wiki.freeswitch.org/wiki/Extension_Status_Example is similar to what you want, except that instead of invoking a Javascript application if the call fails (as in the example), you'll need to test the value of originate_disposition to decide how to handle the call if the bridge is unsuccessful and it falls through to the next action in the dial-plan. (I'm assuming based on that page that originate_disposition is the correct variable in this kind of scenario.) Someone (perhaps you after you've implemented and debugged it) should document the result on the wiki, as I'm sure this is a common use case, but there is no documentation currently other than the above-mentioned page.
On 21 February 2010 20:10, Jason White <jason@jasonjgw.net> wrote:
Actually suspect the solution might be even simpler. e.g something like: <action application="set" data="hangup_after_bridge=true"/> <action application="set" data="continue_on_fail=NORMAL_TEMPORARY_FAILURE,TIMEOUT,NO_ROUTE_DESTINATION,NORMAL_CIRCUIT_CONGESTION,NETWORK_OUT_OF_ORDER,etc"/> <action application="bridge" data="sofia/.../$1"/> <action application="bridge" data="openzap/.../$1"/> error tone if all else fails Only I am not in a position to test it just yet, and not sure yet how to generate the error tone if everything fails either. -- Brian May <brian@microcomaustralia.com.au>
Brian May <brian@microcomaustralia.com.au> wrote:
On 21 February 2010 20:10, Jason White <jason@jasonjgw.net> wrote:
Actually suspect the solution might be even simpler. e.g something like:
<action application="set" data="hangup_after_bridge=true"/> <action application="set" data="continue_on_fail=NORMAL_TEMPORARY_FAILURE,TIMEOUT,NO_ROUTE_DESTINATION,NORMAL_CIRCUIT_CONGESTION,NETWORK_OUT_OF_ORDER,etc"/> <action application="bridge" data="sofia/.../$1"/> <action application="bridge" data="openzap/.../$1"/> error tone if all else fails
That looks promising.
participants (2)
-
Brian May
-
Jason White