06-04-2015, 02:43 AM
Hi there
I want to make my provision data to be V73 compliant. After checking the V73 provision manual I am somewhat confused.
On page 88 there is written about "Configurations never be saved to <MAC>-local.cfg file."
http://www.yealink.com/Upload/UCOne/2014...V73_40.pdf
My current V72 provision mac config includes parameter for several VLAN related values. The reason is that these VLAN values can be different for each phone. According to the V73 provision manual it is now no longer allowed to put these VLAN parameter into the <MAC>-local.cfg file.
Well, how can this be? Thats absolutely illogical. When these VLAN values are put into the <COMMON>-local.cfg file, these values are applied to ALL phones. They have to be individual, - different for each phone. Out of my view this new V73 rule cannot be right.
I want to make my provision data to be V73 compliant. After checking the V73 provision manual I am somewhat confused.

On page 88 there is written about "Configurations never be saved to <MAC>-local.cfg file."
http://www.yealink.com/Upload/UCOne/2014...V73_40.pdf
My current V72 provision mac config includes parameter for several VLAN related values. The reason is that these VLAN values can be different for each phone. According to the V73 provision manual it is now no longer allowed to put these VLAN parameter into the <MAC>-local.cfg file.
Code:
network.vlan.internet_port_enable = {$voice_vlan_enable}
network.vlan.internet_port_vid = {$voice_vlan_id}
network.vlan.internet_port_priority = 0
network.vlan.pc_port_enable = {$data_vlan_enable}
network.vlan.pc_port_vid = {$data_vlan_id}
network.vlan.pc_port_priority = 0
Well, how can this be? Thats absolutely illogical. When these VLAN values are put into the <COMMON>-local.cfg file, these values are applied to ALL phones. They have to be individual, - different for each phone. Out of my view this new V73 rule cannot be right.