06-20-2013, 03:17 AM
While working on our auto provisioning configuration for the T46G we've noticed a couple of inconsistencies in the configuration parameters:
In your Common.cfg template for the T46G, the possible values for the auto_provision.mode parameter are given like this:
#0-Disabled (default), 1-Power on, 4-Repeatedly, 5-Weekly, 6-Power on + Repeatedly, 7-Power on + Weekly;
We would normally use value 7, but it seems like this value is invalid for the T46G as it will not toggle the corresponding radio buttons in the web configuration.
We currently use these values as a workaround:
auto_provision.mode = 1
auto_provision.weekly.enable = 1
But it would be nice if the configuration parameters in the m7 templates could be made consistent across all phones.
Another observation we did was that the linekey.X.line parameter now starts from 1. It used to start from 0 on the T22P for example, where there's an "auto" value at position 0.
Small changes like these makes it quite difficult to implement reusable template code that can be applied to different yealink products.
Something to consider for the next firmware version perhaps
In your Common.cfg template for the T46G, the possible values for the auto_provision.mode parameter are given like this:
#0-Disabled (default), 1-Power on, 4-Repeatedly, 5-Weekly, 6-Power on + Repeatedly, 7-Power on + Weekly;
We would normally use value 7, but it seems like this value is invalid for the T46G as it will not toggle the corresponding radio buttons in the web configuration.
We currently use these values as a workaround:
auto_provision.mode = 1
auto_provision.weekly.enable = 1
But it would be nice if the configuration parameters in the m7 templates could be made consistent across all phones.
Another observation we did was that the linekey.X.line parameter now starts from 1. It used to start from 0 on the T22P for example, where there's an "auto" value at position 0.
Small changes like these makes it quite difficult to implement reusable template code that can be applied to different yealink products.
Something to consider for the next firmware version perhaps