* [user_record] move back to session_record
use RECORD_ANSWER_REQ variable to start recording after answer
* Use record_session but leave api_on_answer as an disabled option.
Co-authored-by: FusionPBX <markjcrane@gmail.com>
Some people were used to *72 original behavior then at some point someone added *72 followed by 2 - 20 digits. However to make everyone happy both of these can co-exist.
Using ${sip_authorized} is not effective since the inbound
call often has authorization to call into the PBX, either via
ACL or registration. Instead, use ${from_user_exists} to test
if this user exists on the system.
We also fix a condition that the local user types *1 and the
remote user receives the dial tone.
* [click_to_call] fix Call-Info header set on bleg and move dialplan order before outbound route
* Update and rename 530_click_to_call_auto_answer.xml to 25_click_to_call_auto_answer.xml
- Used api_on_answer so that the recording only starts when the call is answered. Should save diskspace and prevent the need for using action: ringback.
- Added 'both,self' to the end of the bind_digit_action to fix inbound call mask.
This is a dialplan approach to fix the feature key sync loop/race with yealink phones. This aproach may also need to be extended to the Call Forward dialplans as well. It limits the number of simultaneous calls for a particular user to change their DND/Forwarding status to a single call at a time. This prevents the infinite loops that the yealinks can get into if the user presses the DND button too quickly with feature key sync enabled.
I am also reverting the lua fix because it was not reliable and can still easily allow the loop to occur.
This variable should be optional as it can be defined in other places as well. It should not be assumed that this is the only place it could be set for those that need it.
When editing in the CLI with any editor that does syntax highlight, the * breaks it. Adding on the following line /* **/ restores the right highlighting
