Right-Sizing Your Voice Network
Businesses are always looking to eliminate unnecessary expenditures, but voice circuits are often overlooked because there has been no accurate way to measure them...until now!
CTG's Voice Utilization Assessment can pinpoint the number of call paths required to handle your call volume during peak calling periods. This information will allow you to right-size your voice network.
How It Works
After capturing the call data from your telephone system, we will determine your busy hour for inbound and outbound calls, estimate your average call time, and complete an Erlang study
to calculate the number of call paths needed to handle this amount of traffic.
Whether you intend to use traditional analog, PRI, T-1 circuits, or SIP trunks, CTG will help you use these calculations to design and manage your voice network effectively.
Traditional Voice Utilization Assessment Includes:
1. How many outside lines are currently available for inbound and outbound voice, fax, and modem calls?
2. How many outside lines are actually needed to handle the peak calling period to avoid busy signals?
3. If we were to convert these calls to IP or SIP, how much bandwidth would we need to guarantee good call quality?
Voice over IP Performance Assessment Includes:
1. Is there enough bandwidth available to handle the existing voice traffic and eliminate the need for a separate voice network?
A. If so, how many voice calls can the existing network handle?
B. If not, who is using this bandwidth and what are they using it for?
i. Is there a way to prioritize some applications, (i.e. voice) over other applications in order to get the most out of the available bandwidth?
ii. Is there a way to prioritize power users over other less vital users?
iii. Is there a way for us to keep non-work related traffic from eating up the available bandwidth?
iv. Is there a way to manage the bandwidth based on the time of day and the day of the week or month?
2. Is the existing bandwidth able to support good call quality?
A. How will the inherent packet loss, delay and jitter affect voice quality?
Below is an example of how we use Erlang Calculations to determine required call paths based on a 1% blockage and a .1% blockage. In this example, we determined 61 call paths are needed to handle 858 calls in the busy hour with a likelihood of 1% blockage or 1 busy signal for every 100 calls. By having 70 call paths, the blockage rate drops to .1% or 1 busy signal out of 1,000 calls.