QoS for Voip
QoS is new to me. I'm just trying to get a better understanding of my options before I learn how to implement it.
I have some voice servers located in a data center.
I have several small/medium (5-40 users) remote offices connecting to them with Yealink phones.
For the remote LAN's where the Yealink phones reside, I see Yealink can tag a DSCP value to SIP and a DSCP value to Voice (RTP). The recommendation is value 26 for SIP and 46 for Voice RTP. Yealink can also vlan voice, but I don't think I need to complicate with that at this point.
So I assume the best plan is have the phone tag with the recommendations, use a managed switch for the remote office lan and give priority queuing to the DSCP values. This would make sure any voice packets in queue in the switch would go out to the router before any other type of traffic and then to the internet. Unless I decide to vlan the voice and in the switch and put two uplinks from the vlans to the router, there wouldn't be any QoS config needed in the router as it connects to the switch with one link at this point? If I do vlan, I would have one uplink from each vlan into the router and prioritizing the voice port in the router?
So that's how I understand my options of putting QoS on the remote office lan and egress to the internet.
As far as any QoS on the ingress from the internet, I understand there isn't much to do here as it's dependent on the internet/ISP and which packets from my voice server or internet traffic get there 1st. However, if the router is capable, a bandwidth reservation for incoming voice would not be a bad idea?
Lastly, I can tag all traffic coming out of the Windows voice servers with a DSCP value. If I do this, will those packets travel the internet and arrive to the remote LAN switch with the DSCP value still intact, resulting in incoming voice traffic also getting a priority in the remote lan switch over other lan traffic?
Thanks for your help. I hope I'm on the right track for understanding this without making it too complicated. These remote offices do not have someone onsite to deal with a complicated setup like vlans, but that may be something I have to do with the bigger sites.
Brian
Back to the
I have some voice servers located in a data center.
I have several small/medium (5-40 users) remote offices connecting to them with Yealink phones.
For the remote LAN's where the Yealink phones reside, I see Yealink can tag a DSCP value to SIP and a DSCP value to Voice (RTP). The recommendation is value 26 for SIP and 46 for Voice RTP. Yealink can also vlan voice, but I don't think I need to complicate with that at this point.
So I assume the best plan is have the phone tag with the recommendations, use a managed switch for the remote office lan and give priority queuing to the DSCP values. This would make sure any voice packets in queue in the switch would go out to the router before any other type of traffic and then to the internet. Unless I decide to vlan the voice and in the switch and put two uplinks from the vlans to the router, there wouldn't be any QoS config needed in the router as it connects to the switch with one link at this point? If I do vlan, I would have one uplink from each vlan into the router and prioritizing the voice port in the router?
So that's how I understand my options of putting QoS on the remote office lan and egress to the internet.
As far as any QoS on the ingress from the internet, I understand there isn't much to do here as it's dependent on the internet/ISP and which packets from my voice server or internet traffic get there 1st. However, if the router is capable, a bandwidth reservation for incoming voice would not be a bad idea?
Lastly, I can tag all traffic coming out of the Windows voice servers with a DSCP value. If I do this, will those packets travel the internet and arrive to the remote LAN switch with the DSCP value still intact, resulting in incoming voice traffic also getting a priority in the remote lan switch over other lan traffic?
Thanks for your help. I hope I'm on the right track for understanding this without making it too complicated. These remote offices do not have someone onsite to deal with a complicated setup like vlans, but that may be something I have to do with the bigger sites.
Brian
Back to the
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great. So I'm on the right track. Thank you. Maybe another question I need to post, but do you know of a simple easy to use tool/software I could use to flood the switch and cause voice issues, then implement the QoS to verify it is helping in such situation?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
3cx
Sounds good. Just feel free to create more questions if you need more assistance. And be sure that you handle the security controls properly when building the environment.
ASKER