1> Saying "It's on 10GB, it's fine"
2> Using a separate network (port group and VLAN) specifically for voice on a VSS with 1GB uplinks
3> Using a separate network (port group and VLAN) specifically for voice on a VDS with 1GB uplinks pinned to the port group
4> Using a separate network (port group and VLAN) specifically for voice on a VDS with 10GB uplinks
5> Using a separate network (port group and VLAN) specifically for voice on a VDS with 10GB uplinks and traffic prioritization on the TOR switches for the voice VLAN using IP Precedence (differentiated services code point [dscp]) audio priority.
Any thoughts community?
Best answer by bbbburns
Why IP Communicator instead of Cisco Jabber? I understand that the requirements for one or the other aren't always directly in your control, but if you have the option to do Cisco Jabber you can use the VXME Plugin:
This plugin allows the media to be streamed directly between the thin clients, thus you can keep all of your RTP audio traffic out of the data center and directly between endpoints. Your QoS marking and classification is then done at the switches near the endpoints and you avoid hairpinning RTP audio back and forth to the data center. The caveat here is this won't work on a zero client.
If you remove the RTP traffic from the VM then you no longer have to look at giving special QoS to all traffic from this VM. If you have no choice but to use IP Communicator I still don't like the extra complexity that a dedicated network adapter for voice enabled VMs would require. Having two network adapters in the same VM (one dedicated for voice) could lead to problems with one way audio if the IP Communicator doesn't handle it properly.
The ideal scenario removes the RTP from the datacenter, or remarks and reclassifies the voice traffic coming out of the data center where it's feasible to do so.
That's a long way of saying "Option 1 - It's on 10GB, it's fine." With a note to try to avoid the scenario in the first place, or to try marking the traffic where you can.
Jason Burns | CCIE Voice #20707 | Solutions & Performance Engineer | email@example.com | @bbbburns