Good call quality is crucial for any business relying on VoIP (Voice over Internet Protocol) technology. Bad call quality can lead to frustration, misunderstandings, and lost business opportunities. This article will explore possible causes of bad call quality and provide steps to improve it.
Interpreting Call Error Codes
On WebApp
If you're having issues with call quality during a call, you'll likely see an error code at the top of your MarketingPlex dashboard. You can view the meaning of each error code here.
The most common errors are:
high-rtt - Round-trip-time (RTT) is the network's latency measure. Higher latency can result in perceptible delays in audio.
high-jitter - Jitter is the measure of variability at which packets arrive at the SDK sensors. High jitter can result in audio quality problems on the call, such as crackling and choppy audio.
high-packet-loss - Packet loss is measured as the percentage of packets sent but not received at the SDK sensors. High packet loss can result in choppy audio or a dropped call.
On Mobile App
The MarketingPlex and LeadConnector has safety built-in to notify your clients when bad call quality is experienced.
high-rtt: We detect high round-trip time on this network. You might experience perceptible delays.
low-mos: The call quality on this network might be affected.
high-jitter: We detect high jitter on this network. You could experience choppy audio or crackling noises.
high-packet-loss: We detect high jitter on this network. You could experience choppy audio or crackling noises.
If you are using LC Phone System
As the LeadConnector Phone System is relatively new, we are continually monitoring the quality of the user experience. We have periodic surveys that ask for feedback on the call’s quality. This is super important and necessary to developing and honing this feature. The surveys will show up every four calls as long as the feedback is submitted. This will become less frequent as time goes on as we collect more data and improve the app. Thank you for helping us work towards a more seamless system.
In our experience, in most cases, the reason for bad call quality is a bad internet connection or a bad router.
Step 1 - Check the quality of your internet connection
VoIP breaks audio data into small chunks called packets to transfer them over the internet. This means a bad internet connection or a router might affect your audio quality.
Please head over to https://speed.cloudflare.com/ and do a test.
It is recommended to have at least a 50MBPS uplink/downlink connection with a jitter of less than 10ms and Ping of less than 40ms. If you have an inferior connection to the mentioned specs, you may need to upgrade your internet or router.
Step 2 - Check VoIP Compatibility
You can check the VoIP compatibility of your internet connection by heading over to - https://test.8x8.vc/
If you see any warnings (like in the example above), you may need to upgrade your internet, router, or computer to improve your call quality.
Step 3 - Check your Computer (or mobile) hardware
VoIP connections require your computer to perform heavy computations; therefore, if you are using an old machine, it is expected to have problems with VoIP call quality.
If you are using your own Twilio Account
If you are using your own Twilio account, you need to open a ticket to determine the cause of bad call quality with Twilio.
Also, be sure to run: https://networktest.twilio.com/
Twilio isn't able to help me. What are my options?
Option 1 - Move to LeadConnector Phone System
Moving to LeadConnector Phone System might save you a lot of trouble that comes with managing Twilio as it is completely managed by MarketingPlex.
Option 2 - Look for Configuration Issues
Log in to your Twilio account -> View Sub-accounts -> Select Sub-account -> Monitor -> Loges -> Errors and check if you have any common errors listed there.
Once you have identified the root cause for the error, your call experience should improve significantly.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article