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.
With set to false the callers original outbound caller ID information is used.
Keep original callers caller ID is now set as the default.
With these enabled to true the caller ID is picked from the extension being called.
- Original kickall had an extra set command and was missing the domain name.
- Shouldn't be needed because conference is set to end when moderator leaves
- For this reason disabled by default.
- Additional kickall with sched_api is a time limit for the call
This setting allows adjusting the variable that is used for match the inbound number. For many years inbound routes have used destination_number as the variable to match inbound calls. When SIP diversion header is used the destination_number is not always dependable. The variable sip_to_user is more dependable but still fails with how some providers have implemented the SIP diversion header. It appears the sip_req_user is the seems to be the most dependable.
* Add new static method to created newly connected database object
* Document database class and clean up and document some of the methods.
This removes the methods that should not be in each instance and places
them in the single instance class as to occupy less resources and be
able to create database objects more efficiently.
* More docs & removed the ability to set any value within the object.
Co-authored-by: Tim Fry <tim@voipstratus.com>
When the caller is a local extension to another location extension the caller ID in the follow-me-destinations dialplan sets the caller ID to the local extension number and then the VoIP provider doesn't accept the call. As long as the local extension has Outbound Caller ID set on their extension then the information is already correct.
