Soft Phone QOS on desktop clients - switching to Net2Phone
Hi all,
We are making the switch to Net2Phone this month and will be continuing to use our Polycom phones for the most part. Those phones are already on a Voice VLAN and get high priority. For some users who will wish to use the App instead of their traditional desk phones, they are just on the standard domain vlan.
What sort of tips and tricks have you guys implemented in the dashboard to deal with Phone Apps?
If the MS220's support port-based QoS classification then you should put those rules under switch->switch settings -> QoS. And don't forget to map the correct queue to it also.
The MX side is only relevant if you need to make calls between multiple offices. In the case of DSCP EF marking from the App or the switch setting the EF marking, then you only need to enable the default QoS rules under Security & SD-WAN -> Traffic Shaping. If not, you'll need to reclassify the traffic there and apply the correct behavior there.
For the switching part you need to consider the kind of MS switches you have. The MS120/125 switches cannot classify traffic for QoS purposes and the higher end switches only can use L4 ports.
So the first consideration is the App and how it behaves. What ports it uses.
An alternative is when you use dot1X to get trusted pc's into a certain VLAN you could trust incoming DSCP markings on that VLAN. And then have a group policy that allows DSCP tagging on packets from the voice App.
If the MS220's support port-based QoS classification then you should put those rules under switch->switch settings -> QoS. And don't forget to map the correct queue to it also.
The MX side is only relevant if you need to make calls between multiple offices. In the case of DSCP EF marking from the App or the switch setting the EF marking, then you only need to enable the default QoS rules under Security & SD-WAN -> Traffic Shaping. If not, you'll need to reclassify the traffic there and apply the correct behavior there.
But on the whole, there is so much bandwidth now, and apps have transitioned from being thick to thin (mostly because they are web-based now) it is barely a concern.
You could also take a look at the VoIP design guide.
Thanks to both of you! The phones are on their own vlan and the app is a web app that so far seem to be working just fine with no modification, but I really like Philip's links.
Perhaps I'll configure some of that for Teams.
Get notified when there are additional replies to this discussion.
