Confirming QoS for VOIP on Procurve 2848
-
So I found this, which recommends setting QoS by using DSCP priority (forum post first answer).
But I have no idea to know how the packets are being tagged with this information.
Does this make any sense?
Paging @scottalanmiller and @JaredBusch
-
Yealink is on by default. Other models I do not know.
-
@jaredbusch So if 802.1p / Layer 3 DSCP is enabled, then I shouldn't have to modify these switches, considering the defaults have DSCP 101110 already enabled.
Right?
-
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848:
@jaredbusch So if 802.1p / Layer 3 DSCP is enabled, then I shouldn't have to modify these switches, considering the defaults have DSCP 101110 already enabled.
Right?
Phones only do DSCP, while 802.1 is on the switching and routing.
-
That is the default DSCP settings on one of my switches, assuming that we use Yealink (99.99999% certainty) we should be good, just need to configure our firewall.
-
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848:
That is the default DSCP settings on one of my switches, assuming that we use Yealink (99.99999% certainty) we should be good, just need to configure our firewall.
As long as nothing else is setting itself above that.
-
111 000 is set to priority 7 as well, let me look through the entire list.
-
So there are 3 items with a priority of 7
101110
111000
100110There are 3 items with a priority of 6
100010
100100
110000Should I be looking for any other DSCP codepoints?
-
As long as the switches are honouring priority, you should be fine.
In reality, even if they don't, you should be fine.
-
So I know this is going to get me lambasted.
Should I create a custom application type for specific UDP/TCP ports and set a priority there as well? Or should I not bother and see how things perform from the start?
-
@scottalanmiller said in Confirming QoS for VOIP on Procurve 2848:
As long as the switches are honouring priority, you should be fine.
In reality, even if they don't, you should be fine.
Right, unless the switches are saturated, and then you have other problems.
-
By default Yealink phones use these DSCP tags.
RTP on 46 and SIP on 26.
A lot of online guide for setting up DSCP tagging use RTP on 48. Just be aware of that.
-
@jaredbusch, thanks. So 26 (011 010) is set for a Priority of 4, 46 (101 110) is set to a priority of 7.
48 (110 000) is set to priority 6.
-
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848:
@jaredbusch, thanks. So 26 (011 010) is set for a Priority of 4, 46 (101 110) is set to a priority of 7.
48 (110 000) is set to priority 6.
That should be fine then.
-
Ok cool.
Now looking at another switch 46 and 48 have a priority of 7, and 26 a priority of 4. (without an override).
Should I set everything to be like below?
46-7
48-6
26-4 -
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848:
Ok cool.
Now looking at another switch 46 and 48 have a priority of 7, and 26 a priority of 4. (without an override).
Should I set everything to be like below?
46-7
48-6
26-4Doesn't really matter. If you have no traffic on any other DSCP tags those priorities never apply.
Also does not matter much if you are not saturating the switch port in the first place.
