Set the default value back to destination_number. There are cases where ${sip_to_user} and ${sip_req_user} may work better with the SIP diversion header. However seeing issues for some people when not using destination_number. It maintains original behavior so setting it back to the original default.
In this condition you already have p.dialplay_uuid = s.dialplay_uuid and you have p.dialplay_uuid = CONST, no need tor s.dialplay_uuid=CONST,
In small databases, this could be trivial; but in significant databases, this saves a lot of processing.
This dialplan is meant to not record any calls any feature code calls. This means all calls starting with a * prefix. However if you set the call to record all on the extension wouldn't you expect it to record all calls? Including when picking up a call. Or when intercepting call? or when un-parking a call. Had a someone call that had used a * prefix on an outbound route because they did that this condition prevented the call from being recorded which they didn't expect when the extension was set to record all calls. Tempted to remove it entirely but have instead disabled it by default for now.
* Add extension_effective_caller_id_name and extension_effective_caller_id_number
Adds 2 new variables to the user_exists dialplan:
* extension_caller_id_name
* extension_caller_id_number
This allows us to access these channel variables from the event socket and get the caller id name and number of the dialed extension when an inbound call comes in to that extension.
* Update 010_user_exists.xml
---------
Co-authored-by: FusionPBX <markjcrane@gmail.com>
When logging into call center from phone, index.lua
only supports identity with agent_id. We allow passing
agent_name as well to assist with BLF configuration.
Update local_extension fail_on_single_reject to handle stale registrations and other failures. Previously any failure mode would cause the call to drop to all registrations.
FusionPBX