10-25-2013, 07:29 PM
I have recently installed a new client with a YeaLink system.
This time we used the v72 firmware, 2.71.0.140 on h/w 1.0.0.53 it connects to Cisco Catalyst switches.
Some of the handling with using phone system on VLAN:7 and PC Port on VLAN:1 has changed.
By default the Cisco Switch in 'trunk' mode will tag VLAN:7 but VLAN:1 is native and untagged (even in trunk mode). But the phone now ignores these packets (older firmware did not). The Cisco will accept both tagged and untagged packets as VLAN:1. So effectively the phone could talk to network but the replies were not getting back to the phone, as untagged packets were ignored.
Obviously the solution is to make the Cisco switch tag VLAN:1. This resolved the matter. So the topic here is about how to improve the phone to better support customers.
However this is a change in behavior from before and causes a headache for installation.
We have the configure the switch one way, then configured the phone, then change the configuration of the switch to finalize the installation.
This presents additional extra work to factory reset a phone, ship out a new phone and get it working on the network. Since the phone disappears off the network between the modes in cases where the switch does not support hybrid (tagged and untagged) mode on the port.
I think there should be a new option in the VLAN settings area with 4 possible values.
New Configuration Item) Untagged Packet: ignore, with voice, with PC Port, Not Applicable
This setting will instruct the phone what to do with any untagged packets received on the Network port. The existing options on VLAN ID affect the outgoing packets to the Network port only, as well as setup a reciprocal incoming packets.
If both the Voice and the PC Port are in VLAN mode with a VLAN ID set, then this option would become relevant (to what happens with incoming untagged packets)
* Not Applicable - this whole option would be disabled, instead of not applicable it could be greyed out with the previous setting seen. As stated above the option is not relevant when either port (voice/PC port) has VLAN support disabled.
* with voice - this means treat the inbound data as-if it was with the voice network (so the phone sees it, so data can be tagged and untagged), this option should probably be the default to make installation easier since a hybrid switch mode can be setup and the phone still accesses to change settings in all. This is also good for supporting clients as if a factory reset if performed on a phone it can be setup again without reconfiguring the switch.
* with PC port - this means the phone does not see the data and the PC port does.
* ignore - this means do not do anything with the data, ignore it, the phone can not see it, the PC port can not see it. This seems to be the default now, so the phone becomes lost to the network upon enabling VLAN IDs for both voice/PC-port.
* both - not sure if this is useful, this means the untagged packets can be seen by both the phone and the PC port (like bridging), it will only create setup headaches when used
Previously the older firmware behaved as if the option "with voice" was set (which is better for installation and support IMHO), but I see the new v71 is behaving as if "ignore" is set.
This time we used the v72 firmware, 2.71.0.140 on h/w 1.0.0.53 it connects to Cisco Catalyst switches.
Some of the handling with using phone system on VLAN:7 and PC Port on VLAN:1 has changed.
By default the Cisco Switch in 'trunk' mode will tag VLAN:7 but VLAN:1 is native and untagged (even in trunk mode). But the phone now ignores these packets (older firmware did not). The Cisco will accept both tagged and untagged packets as VLAN:1. So effectively the phone could talk to network but the replies were not getting back to the phone, as untagged packets were ignored.
Obviously the solution is to make the Cisco switch tag VLAN:1. This resolved the matter. So the topic here is about how to improve the phone to better support customers.
However this is a change in behavior from before and causes a headache for installation.
We have the configure the switch one way, then configured the phone, then change the configuration of the switch to finalize the installation.
This presents additional extra work to factory reset a phone, ship out a new phone and get it working on the network. Since the phone disappears off the network between the modes in cases where the switch does not support hybrid (tagged and untagged) mode on the port.
I think there should be a new option in the VLAN settings area with 4 possible values.
New Configuration Item) Untagged Packet: ignore, with voice, with PC Port, Not Applicable
This setting will instruct the phone what to do with any untagged packets received on the Network port. The existing options on VLAN ID affect the outgoing packets to the Network port only, as well as setup a reciprocal incoming packets.
If both the Voice and the PC Port are in VLAN mode with a VLAN ID set, then this option would become relevant (to what happens with incoming untagged packets)
* Not Applicable - this whole option would be disabled, instead of not applicable it could be greyed out with the previous setting seen. As stated above the option is not relevant when either port (voice/PC port) has VLAN support disabled.
* with voice - this means treat the inbound data as-if it was with the voice network (so the phone sees it, so data can be tagged and untagged), this option should probably be the default to make installation easier since a hybrid switch mode can be setup and the phone still accesses to change settings in all. This is also good for supporting clients as if a factory reset if performed on a phone it can be setup again without reconfiguring the switch.
* with PC port - this means the phone does not see the data and the PC port does.
* ignore - this means do not do anything with the data, ignore it, the phone can not see it, the PC port can not see it. This seems to be the default now, so the phone becomes lost to the network upon enabling VLAN IDs for both voice/PC-port.
* both - not sure if this is useful, this means the untagged packets can be seen by both the phone and the PC port (like bridging), it will only create setup headaches when used
Previously the older firmware behaved as if the option "with voice" was set (which is better for installation and support IMHO), but I see the new v71 is behaving as if "ignore" is set.