* Fix the registration failed after provision Flyingvoice phone.
* Fix the parameter configuration of Flyingvoice not displayed in the Default Settings
* Fix: after configuring SIP line 1 of Flyingvoice phone, other SIP lines are disable and the configuration parameters of Flyingvoice are not displayed by default settings.
* Fix after configuring SIP line 1 of Flyingvoice phone, other SIP lines are disable.
* Fix the configuration parameters of Flyingvoice are not displayed by default settings.
* Fix: when only one sip line's shared line is enable, the shared lines of all SIP lines will be enable.
* Fix: unable to generate configuration file of Flyingvoice due to syntax error.
* Add the P1X, P2X, P3X, P5X, i86Box, iMetalBox, audioKit Series for Flyingvoice in Devices.
- When this is disable it will use the domain of the tenant.
- If the domain of the tenant is not resolvable then yealink_provision_url is needed.
- One reason to disable it is the domain_name has to be manually updated to the correct domain.
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.
hershyheilpern
Vincent
FusionPBX
chansizzle
Marvin Skeete
emak
zrd740
agree
Dan