atcomsystems.ca/forum Forums VOIP Phones & IP PBX Yealink Telephones & Systems Yealink WAN and PC Port VLAN Tagging

So I have a better understanding, is anyone able to explain the WAN and PC port VLAN tagging on the Yealink phones for me.
I understand the VLAN tagging for the WAN port so that the phone will communicate to on the voice VLAN setup for voice traffic.

But for the PC port VLAN tagging, does the PC not pickup the data VLAN association when it negotiates on the network?
Wouldn't the PC receive this information when it connects to the network? Or does the PC port NEED to be tagged with the data VLAN so that the PC is able to communicate on the data VLAN and receive its DHCP information from the data VLAN?

I am trying to understand this better. My understanding leads me to think that the data traffic sent from the phone to the network is received at the router/switch without VLAN tagging.
But does the phone send all traffic on its WAN port with the VLAN tag set on the WAN port unless you specifically call out data traffic on the PC port to be tagged with a separate VLAN (i.e. the PC port tags traffic with the appropriate VLAN prior to sending traffic out the WAN port of the phone).

If more clarification of my question is needed, please ask and I will try to explain/ask more clearly.
Thanks!

I think of it as this:
You have one VLAN for data (VLAN 1 for example) and one VLAN for voice (VLAN 2 for example).

Many providers/installers like to separate this voice and data traffic, and it is definitely recommended on large deployments. If there are separate drops for voice and data, it is easy to segregate your traffic. However many times, there may only be one data drop available, which is where the VLANS come into play. To pass more than one network down a wire/drop, at least one (or both) must be tagged. So oftentimes, the voice traffic will be tagged and the data traffic left untagged. Then when a user plugs in a phone, the network (usually through the use of the LLDP protocol) will tell the phone as it is booting up, that its voice traffic is on tagged VLAN 2, and to simply pass untagged (data) traffic thru.

This lets you hard code in the LAN port in the event you would need to just as you can do with the WAN port. That way someone couldn't walk up to plug something in and get direclty on to a say Production VLAN or the likes if maybe the phone was in a warehouse or common area.