**Legacy** Bandwidth-Aware Max Call Control
Posted by Tech Support, Last modified by Taylor Lobo on 21 August 2019 02:07 PM


There are 2 core reasons for limiting a Customers concurrent call limit;


a. For product/billing purposes so that the customer receives the call capacity they have purchased. For example: 5 max calls when a service like "SIP Trunking with 5 Call Paths" has been sold.


b. For audio quality reasons to ensure the customer does not engage in more active calls than their internet service can support resulting in the degradation of audio quality not just for the over limit calls but for all calls on their network.


Up until now Partners had the ability to set Max Call Limitations per Customer, its Branch Offices and even Individual SIP Trunks.

This flexibility meant that Partners could market and sell SIP Trunks with their own call limitations or even Shared SIP Trunk services that allowed Customers to aggregate Active Call Paths across multiple locations leveraging the services value.


With the introduction of Bandwidth Aware Call Limitation, Partners can now specify a Customers', or one if its specific locations, Bandwidth availability for the VoIP service.

3NG's switching and billing platform will then measure the bandwidth used per active call and allow or reject calls once this bandwidth threshold has been reached.

This means that your customer will not be able to engage in more calls than their internet connection can support offering yet another tool in ensuring their service operates within the restriction of their internets capacity and limiting the chances of connection saturation resulting in a bad audio quality experience.



How it Works:

When this feature is active the billing and switching platform will keep track of each active call and the bandwidth that call is consuming based on the codec used.

Each time your customer initiates a new call the system will first determine how much bandwidth is already being used and if there is enough bandwidth left to establish the new call. 

If your customer has already engaged in more calls that the bandwidth setting allows it will block the call request until another call has been hung up.

Should this occur the system will play a recording stating "All Accounts Are Currently In Use".


For Example:

You have input a Max Bandwidth Value of 512 Kbps and you customer has 4 Active Calls using the G711 codec at an estimated 100 Kbps consumed per call (4 Calls x 100Kbps = 400Kbps). 

The customer then initiates a 5th and 6th call using the G729 codec at an estimated 40 Kbps consumed per call (2 Calls x 40Kbps = 80Kbps.

Currently the system monitor is calculating that your customer is consuming 480Kbps for all 6 of their active calls.

Without any calls being hung up the customer tries to initiate a 7th call using the G711 Codec. Because this call requires 100Kbps and 480Kbps are already being used the sum would result in 580Kbps which is 80Kbps over their allowance.

As a result the 7th call would be blocked.

Once more Bandwidth has been freed up by the disconnection of other calls or the use of less bandwidth consuming codecs like G729 are used more call will be allowed again.



How to Use it:

1. Go to the customer record.

2. From the customer record, click on Sites from the action bar.

3. Click Default Site to select the site.

4. Change the Limit Simultaneous Calls to "Yes".

5. Change the Codec Connectivity Profile to "Ethernet".

6. Enter in values for Max Bandwidth, Max Incoming Bandwidth, and Max Outgoing Bandwidth. 


Use Max Bandwidth or Inbound/Outbound. Do not use all 3.

  • Max Bandwidth - Total Bandwidth
  • Inbound Bandwidth - Download 
  • Outbound Bandwidth - Upload

Because many ISPs don't offer symmetrical bandwidth, the Download and Upload bandwidths may differ. It is important to understand those speeds so that an accurate value can be used when using this feature.

(0 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).