...
As a base rule of thumb given the myriad options for prioritization through DSCP, NocTel recommends that SIP be set to the CS3 class and RTP set to EF. We can generally safely set SIP to CS3 as it isn’t as sensitive to latency as RTP is while maintaining some tolerance for packet loss with re-transmission. EF, or Expedited Forwarding, designates traffic as being high priority and very undesirable for packet loss. In RTP’s case, since the communication is effectively streaming re-transmission of data isn’t feasible, possible as it operates off UDP hence we set it to EF.
In the following sections QoS configuration examples are provided.
...
| Info |
|---|
If you find a syntax error in any of the above examples, let us know! Also feel free to contribute your own examples to grow the knowledgebase! |
Final Considerations
While building solid QoS configurations internally can help optimize VoIP service, it is not a panacea as an ISP could be operating with congested ports, which is unfortunately generally outside of locus of control. Though this article outlines QoS primarily in the vein of VoIP, it can be applied to the rest of your network. However, do this sparingly and do not try to micromanage traffic priority through DSCP as it will likely cause contrasting results from attempting to involve too many service levels. Keep things simple: determine what needs to be delivered consistently and with minimal loss and determine what is not a priority. Everything else will fall into the "best effort" bucket of priority.
Related articles
| Content by Label | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...