cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Soft Phone QOS on desktop clients - switching to Net2Phone

SOLVED
Highlighted
Getting noticed

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?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Head in the Cloud

Re: Soft Phone QOS on desktop clients - switching to Net2Phone

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.

View solution in original post

5 REPLIES 5
Highlighted
Head in the Cloud

Re: Soft Phone QOS on desktop clients - switching to Net2Phone

Hi,

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.

Getting noticed

Re: Soft Phone QOS on desktop clients - switching to Net2Phone

Ah yeah, they are MS220-48FP's.

I will have to get that info about how the app behaves and what port it uses. Do you think it would be safe to post that info here? 

Or rather, where in the dashboard should I head to plug that info in?

 

Thanks!

Highlighted
Head in the Cloud

Re: Soft Phone QOS on desktop clients - switching to Net2Phone

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.

View solution in original post

Highlighted
Kind of a big deal

Re: Soft Phone QOS on desktop clients - switching to Net2Phone

If you are using Windows machines and have Active Directory can you configure the app to have its packets marked as EF.

https://docs.microsoft.com/en-us/windows-server/networking/technologies/qos/qos-policy-manage

 

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.

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/... 

 

Highlighted
Getting noticed

Re: Soft Phone QOS on desktop clients - switching to Net2Phone

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.

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.