Optimizing Voice over IP (VoIP) using Quality of Service (QoS)

Welcome to Ecessa Support, we have a variety of technical information and tools for a variety of solutions. If you aren't finding a solution, or would like to talk to a technical support team member, please call 800-669-6242.

See Ecessa's full line of products and solutions

This article assumes knowledge of the VoIP Proxy and Quaility of Service features on the Ecessa appliance. To learn more, please visit the Quality of Service (Bandwidth Throttling) and Voice over IP (VoIP) sections of the online Ecessa manual.

 Quality of Service allows traffic prioritization and bandwidth allocation for VoIP traffic or other services on each WAN line. For VoIP, this can reduce or eliminate conversations experiencing poor (“choppy”) voice quality. Quality of Service can also limit the bandwidth other applications can use, allowing the required bandwidth to be available by more time-sensitive data, such as VoIP.

 This article will provide an example for how VoIP and QoS can be configured to optimize performance.

 Typically, a single phone call uses 64 kbps of bandwidth so the following equation can provide a baseline for how much bandwidth should be reserved for VoIP use:

 (64 kbps) * (# of concurrent phone calls) = VoIP bandwidth

 However, if unsure how much VoIP traffic is or will be generated, it is recommended to start with 50% of the bandwidth on a WAN line reserved for VoIP. If bandwidth is available due to lack of VoIP traffic, other services can utilize up to 100% of the bandwidth; however VoIP will be guaranteed 50% if there is an increase in call volume (and thus, VoIP traffic). The bandwidth allocation can be adjusted at any time if it is determined that more or less bandwidth is required.

 When configuring QoS for VoIP, the RTP protocol (Real-Time Protocol) will be used to identify the traffic for prioritization as it contains the voice data. RTP is included as a protocol in the drop-down list when configuring the QoS classifier on the ClariLink platform.



If RTP is not included in the drop down list, the classifier will need to be defined by destination port number(s). In this example, the port range used for RTP is 7000-7999.


QoS includes the default classifier which acts as a catch-all for traffic that is not identified in other classifiers. This traffic will typically have the lowest priority. In this example, classifiers were created for VoIP (called rtp) and ICMP (called EcessaTesting). It is important to reserve a small amount of bandwidth for WAN testing to prevent disrupting the testing the Ecessa appliance performs to determine WAN status.



After creating classifiers to identify the traffic, classes are added to the link to prioritize the traffic and allocate bandwidth. Please note, that there are outbound and inbound classes and each will need to be configured and activated.


QoS is configured for VoIP and is reflected on the Configure VoIP page.



Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


  • 0

    Very helpful!

  • 0

    RTP drop down only works when utilizing the SIP Proxy feature. If you have VOIP appliance providing that function then simply classify that traffic by IP. Seems to work well. 

  • 0
    Jay Walker

    Rate Limit and Priority Limiting

    Our outbound voice has issues. We use a rtp classifier and rate prioritize that as highest. Has not helped. Looking at using High Priority classes which appears to be the same thing except backwards that cisco and adtran use where 0-7 are your priorities. Ecessa has 0 as the highest priority and 7 lowest but where cisco and adtran have the opposite 7 as highest priority and 0 is lowest.

    I am wondering does ecessa actually do it backwords or is this is a bug in their qui where 0 is actually the lowest? Or is ecessa just using a different technology that looks similiar but was done the opposite of everyone else?


    • Priority 0 — Background

    • Priority 1 — Best Effort

    • Priority 2 — Excellent Effort

    • Priority 3 — Critical Applications

    • Priority 4 — Video

    • Priority 5 — Voice

    • Priority 6 — Internetwork Control

    • Priority 7 — Network Control


    SIP Proxy and SIP Configuration

    It should be noted that this documentation is outdated. SIP Proxy is the latest menu link label for Ecessa builds. SIP Proxy should only be used as far as I can tell if you want the Ecessa to act as a SIP Proxy. Meaning phones will register with the Ecessa an not a PBX. And the Ecessa will allow registered phones to place and receive calls using the Ecessa as the Proxy.

    Edited by Jay Walker
Please sign in to leave a comment.