Confirming QoS for VOIP on Procurve 2848
-
So I'm checking to ensure our switches are setup for QoS for voip phones as we're really close to pulling the trigger on this. I found this administrative guide for the switches, and everything is unmodified (via a telnet session to the switch).
If I am reading this part correctly:
By default, the IP ToS, VLAN-ID, and (source) port show outputs automatically list No-override for priority options that have not been configured. This means that if you do not configure a priority for a specific option, QoS does not prioritize packets to which that option applies, resulting in the No override state. In this case, IP packets received through a VLAN-tagged port receive whatever 802.1p priority they carry in the 802.1Q tag in the packet’s header. VLAN-Tagged packets received through an untagged port are handled in the switch with “normal” priority. For example, figure 6-8 below shows a qos VLAN priority output in a switch where nondefault priorities exist for VLANs 22 and 33, while VLAN 1 remains in the default configuration.It would seem I don't have to make any configuration changes, as the switch will simply pass the 802.1p priority along, correct?
-
Do the phones set that priority themselves?
-
@Dashrender I haven't gotten to look at the phones yet. I honestly don't know, something I should look into.
-
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848 - Procurve:
@Dashrender I haven't gotten to look at the phones yet. I honestly don't know, something I should look into.
If they aren't, then what would be setting the priority?
-
This is the details on the phone
Network and Security
SIP v1 (RFC2543), v2 (RFC3261)
Call server redundancy supported
NAT transverse: STUN mode
Proxy mode and peer-to-peer SIP link mode
IP assignment: static/DHCP/PPPoE
HTTP/HTTPS web server
Time and date synchronization using SNTP
UDP/TCP/DNS-SRV(RFC 3263)
QoS: 802.1p/Q tagging (VLAN), Layer 3 ToS DSCP
SRTP for voice
Transport Layer Security (TLS)
HTTPS certificate manager
AES encryption for configuration file
Digest authentication using MD5/MD5-sess
OpenVPN, IEEE802.1X
IPv6So it does do 802.1p/Q tagging for VLANs, as well as Layer 3 ToS DSCP
-
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848 - Procurve:
So it does do 802.1p/Q tagging for VLANs, as well as Layer 3 ToS DSCP
You mean it can. Have you checked that it's enabled by default? Perhaps this is part of the settings you have to do when you pick what VLAN to put voice on. Of course ML folks all say, you shouldn't bother with a VLAN, waste of time.
-
@dashrender said in Confirming QoS for VOIP on Procurve 2848:
@dustinb3403 said in Confirming QoS for VOIP on Procurve 2848 - Procurve:
So it does do 802.1p/Q tagging for VLANs, as well as Layer 3 ToS DSCP
You mean it can. Have you checked that it's enabled by default? Perhaps this is part of the settings you have to do when you pick what VLAN to put voice on. Of course ML folks all say, you shouldn't bother with a VLAN, waste of time.
That is the goal, I do not want to configure any additional VLANs, if the phone can pass this information without additional "effort" wonderful.
-
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.
