Adding this fix enables both remote phone book and provisioning to work correctly on the newly released android based Yealink devices.
It appears that during the provisioning process, the T5X series supply a colon formatted mac address in their user agent.
However, when requesting a remote phone book, the presented user agent has no colons. This allows both formats to work as expected.
* Update Grandstream provisioning
* Add Vtech
* Create app_config.php
fix typo
* Update app_config.php
remove newline at end as it can break php
* Update app_config.php
remove newline at end as it can break php
* Create app_config.php
remove newline at end.
* Update app_config.php
remove trailing newline
* Create device_edit.php
Add both http and https
* Create app_config.php
remove newline
* Add gxp16xx and fix typos
* Added functionality to show when a devices was last provisioned
Added functionality to show when a devices was last provisioned
Need addition to database: v_devices table:
device_provisioned_on -> datetime
device_provisioned_by -> char(10)
* Revert "Added functionality to show when a devices was last provisioned"
This reverts commit c3e40d68fa.
* Revert "Revert "Added functionality to show when a devices was last provisioned""
This reverts commit 8c27a46565.
* Changed field names as requested
Changed field names as requested for last provisioned data
* Added database fields for device provisoned functionality
Added provisioned_date, provisioned_method, provisioned_ip
* Added ability to search device provisioned info
* Added ip tracking to device provisoned functionality
Added ip tracking to device provisoned functionality and moved the code
to before rendering to register the contact even on unseccessful render
* Added IP address to status column
* Add. Provision to Escene ES330/ES320
* Add. Look up Escene device by ext+domain.
* Update Escene template.
* Add. `provision` section in config.
Found than ES330 some time hangup when it try get software/core and get error from fusion.
So, please find in this set numerous small changes which eliminate numerous php warning messages.
Also, a small bug fix in an sql statistics routine, naming a count(*) field as count, so displaying correct detail.
If any of the proposed changes are omitted, the relevant page will experience php warnings.
There are no doubt fusionpbx pages I've yet to visit that still generate warnings, this set is nearly certainly not comprehensive.
