fusionpbx/resources/install/scripts
emaktech f44ed4370c Fix Ring Group Delay Timing (#4003)
This is going to sound really stupid but I have tested this extensively, submitted a Jira on it months ago (was told FS 1.6.20 was no longer supported) and it's still an issue. Please do not take my word for this and create a ring group to test the delay settings with a stopwatch and you should see the real vs set delay discrepancy.

In FreeSWITCH (both on 1.6.20 and 1.8.5) when sending leg_delay_start values, for whatever reason the actual time is double the value sent. The result of this is that if you send 1000ms as leg_delay_start the actual time the call will be delayed is 2000ms.

Because of this bad behavior, ring group delay settings end up being exactly double what is set. e.g. if you set 10s, you will have to wait 20s for the call to be initiated on leg b.

The easiest way to fix this behavior is to simply multiply leg_delay_start by half as much to get the right "real" delay time. Ugly, I know... I'm not sure if leg_delay_start value is passed elsewhere, I'm thinking this behavior may also be present in find me/follow me. If this gets accepted I will look for other locations where this behavior occurs and submit separate PRs if I find any other instances of this.
2019-06-21 22:04:14 -06:00
..
app Fix Ring Group Delay Timing (#4003) 2019-06-21 22:04:14 -06:00
resources
app.lua
blf_subscribe.lua
call_flow.lua
call_flow_monitor.lua
call_flow_subscribe.lua
call_forward.lua
cidlookup.lua
confirm.lua
destination_caller_id.lua
dial_string.lua
directory.lua
disa.callback.loopback.lua
disa.callback.lua
disa.lua
disa.plus.lua
do_not_disturb.lua
eavesdrop.lua
email.lua
extension_queue.lua
fax_retry.lua
fifo_member.lua
follow_me.lua
ha_monitor.lua
intercept.lua
intercept_group.lua
ivr_menu.lua
mkdir.lua
monitor.lua
page.lua
park.lua
park_monitor.lua
pin_number.lua
recordings.lua
roku.lua
service
streamfile.lua
transfer2.lua
wakeup.lua