Hi Lenard,
I'm not sure if you have (1) phone/PC pairs sharing a single switchport (as seen behind your first link) or (2) phones and PCs plugged into separate switch ports (as seen behind your second link) or (3) a combination of both.
But no matter what - in any case you end up with two VLANs and hence two IP networks, one for voice and one for data.
Hence, the features of your router play a key role: Usually the router will serve only one IP network at the LAN site and route (and NAT) the IP packets with private source addresses to the Internet. But in your case, your router should have to serve two LAN site private networks (one for voice and one for data) - that is, it should have to provide either two LAN-site Ethernet ports that can be isolated from each other and configured for two different IP networks - or a single LAN-site Ethernet port that can be configured for two vlan-aware subinterfaces, each one serving a different IP network.
If I look at your
router model, unfortunately I can't see, that it provides such a feature.
So, if your router can serve only one IP network, a solution has to be found that combines two VLANs in a way, that they can share a single IP network. The easiest (and perhaps only) solution I can see in the moment is to bridge both VLANs in the following way: Within your switch you configure two access ports, one for the voice VLAN and one for the data VLAN, and then you connect these two ports via a cable. Of course, while technically feasible, the disadvantage of this (workaround) solution is that it consumes two switch ports for the bridge cable and that any prioritization of voice frames inside the switch gets lost as soon as they have passed over to the data VLAN.
Even more simple: If (2) meets your scenario you could even forget anything about a separate voice VLAN and simply plug your phones to the switch in the same way you connect PCs. The workaround solution I suggested is only needed in cases (1) or (3).
To say it the other way round: If prioritization of voice is an absolute demand, you can't help to handle voice within a separate and prioritized voice VLAN (and IP network) throughout the switch and even beyond: For example your router should prioritize voice appropriately, and ideally voice frames should be transmitted to the router via a seperate/dedicated link. This means you would have to purchase another router, that provides the required features (second LAN network for voice, voice prioritization within the router and for the communication to the Internet).
The somewhat annoying thing behind the scenarios your referred to via the two web links is that they only tell half the truth in favor of a restricted view that fits some praised product feature but ignores the following obvious questions (they cannot provide a solution for):
first link: And how can I connect the two VLANs to my router and to the Internet respectively?
second link: And what about the PC at port Gi1/0/3? It's obviously isolated and can't talk to the router/Internet (only the phones can do).
PT
