Fix the ring group timeout action so that is not executed when a call is parked using the approach used by hunt groups.
This commit is contained in:
@@ -124,9 +124,7 @@
|
|||||||
session:execute("bind_meta_app", "3 ab s execute_extension::cf XML features");
|
session:execute("bind_meta_app", "3 ab s execute_extension::cf XML features");
|
||||||
session:execute("bind_meta_app", "4 ab s execute_extension::att_xfer XML features");
|
session:execute("bind_meta_app", "4 ab s execute_extension::att_xfer XML features");
|
||||||
session:execute("bridge", app_data);
|
session:execute("bridge", app_data);
|
||||||
if (session:getVariable("last_bridge_hangup_cause") == "NORMAL_CLEARING") then
|
if (session:getVariable("originate_disposition") ~= "SUCCESS") then
|
||||||
--ring group was answered
|
|
||||||
else
|
|
||||||
session:execute(ring_group_timeout_app, ring_group_timeout_data);
|
session:execute(ring_group_timeout_app, ring_group_timeout_data);
|
||||||
end
|
end
|
||||||
end
|
end
|
||||||
@@ -137,3 +135,4 @@
|
|||||||
--table.insert(ACTIONS, {"set", "continue_on_fail=true"});
|
--table.insert(ACTIONS, {"set", "continue_on_fail=true"});
|
||||||
--table.insert(ACTIONS, {"bridge", app_data});
|
--table.insert(ACTIONS, {"bridge", app_data});
|
||||||
--table.insert(ACTIONS, {ring_group_timeout_app, ring_group_timeout_data});
|
--table.insert(ACTIONS, {ring_group_timeout_app, ring_group_timeout_data});
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user