When creating an inbound route to an extension using Destinations in Fusion, it used to create 4 lines of XML below the basic info(as viewed in Inbound Routes) similar to this:
I have noticed that in more recent updates to Fusion (not exactly sure when), that only 2 lines are created, similar to this:
Does anyone know why the change? And/or why to use/not use the hangup_after_bridge and continue_on_fail? I find references to these in the forums/docs, but nothing clear for regular usage.
Also, if an Inbound route is created under Dialplan-Inbound Routes it usually does not show up under Dialplan-Destinations. But if an inbound route is created under Dialplan-Destinations, it then shows up both under Destinations and Inbound Routes. Anyone know why and if it matters?
condition | destination_number | ^\+(12223334444)$ | 20 | true | ||||
action | set | hangup_after_bridge=true | true | 30 | true | |||
action | set | continue_on_fail=true | true | 40 | true | |||
action | transfer | 123 XML mydomain.com | 50 | true |
I have noticed that in more recent updates to Fusion (not exactly sure when), that only 2 lines are created, similar to this:
condition | destination_number | ^\+(12223334444)$ | 20 | true | ||||
action | transfer | 123 XML mydomain.com | 40 | true |
Does anyone know why the change? And/or why to use/not use the hangup_after_bridge and continue_on_fail? I find references to these in the forums/docs, but nothing clear for regular usage.
Also, if an Inbound route is created under Dialplan-Inbound Routes it usually does not show up under Dialplan-Destinations. But if an inbound route is created under Dialplan-Destinations, it then shows up both under Destinations and Inbound Routes. Anyone know why and if it matters?