- Joined
- Jan 1, 2018
- Messages
- 21
- Reaction score
- 6
We noticed with the the 3CX official template, version 2.0003, the <Auto_onhook_Time> is now set to 1 instead of 0.
This causes a short busy signal tone for whichever extension is the last to hang up.
by setting this to 0, the short busy signal is eliminated. (I set it manually in the config web page for the phone, but the next provision overrides it)
It is a little disconcerting for the users.
I have a brand new install and I don't want to start day 1 with an unsupported template.
Is there any way to configure auto_onhook_time through a parameter setting, or do we need to wait for 3CX to correct the setting.
I am not really sure when any value other than 0 makes sense actually, or why they would have changed it from 0 in the first place.
When one or the other parties terminates the call, we want an immediate, quiet, teardown of the connection.
This causes a short busy signal tone for whichever extension is the last to hang up.
by setting this to 0, the short busy signal is eliminated. (I set it manually in the config web page for the phone, but the next provision overrides it)
It is a little disconcerting for the users.
I have a brand new install and I don't want to start day 1 with an unsupported template.
Is there any way to configure auto_onhook_time through a parameter setting, or do we need to wait for 3CX to correct the setting.
I am not really sure when any value other than 0 makes sense actually, or why they would have changed it from 0 in the first place.
When one or the other parties terminates the call, we want an immediate, quiet, teardown of the connection.