| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Polycom VVX phones have an option in the Menu where the users can Enable/Disable
the Call Waiting feature themselves (that is the global config, not per line/registration)
It's available in: Menu -> Settings -> Basic -> Preferences -> Call Waiting
When this option is changed the phone will push its configuration back to the provisioning
server (MACADDRESS-phone.cfg) including the value call.callWaiting.enable=0
Since this parameter is not being parsed the database information is not updated and it
becomes difficult to troubleshoot when the user reports that Call Waiting is not working
(the provisioning web interface shows the option as enabled)
With this patch we ensure that the value is properly parsed and the database gets updated
showing the correct information
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
If the set_device_params function fails, notify the phone to pull its config and revert the change
|
| |
|
|
|
|
| |
to DB
Signed-off-by: Ted Trask <ttrask01@yahoo.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
of functions table"
This reverts commit fb00ff8f05dae3c110beceb929ea036e4cd14ae1.
Conflicts:
provisioning-model.lua
Conflict was resolved by removing "mymodule." from function calls that are once again made local
|
| |
|
|
|
|
|
|
| |
functions table
Changed the order of the first two parameters passed to validate function in provisioning_params
Replaced all APP references with self, now that self is available
Still need to implement swapvalidateparams script
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
