Multiple users experiencing call quality problems

Created by Etienne Marais, Modified on Fri, 25 Oct, 2024 at 2:15 PM by Etienne Marais

Call quality problems can be caused by any of the following:

  • Client's cellular reception - This can be a problem with the client's cellular provider, a problem with the tower due to load shedding or just poor signal
  • Laminin's VoIP network - This can be a problem with our VoIP provider and can affect a single cellular provider (i.e. Vodacom) or more
  • User's workstation or internet - This can be a problem with the user's workstation in terms of resources available (i.e. hard disk running high) or the user's connection to the internet (i.e. a bad connection via Wi-Fi)


When multiple users experiences call quality problems, it is an indication that there is a problem with the Laminin VoIP network or the user's company internet connection.  Please perform the following steps before logging a ticket with Laminin Support.


  • Check your internet connection - To confirm you have a good connection to the internet, go to www.speedtest.net and run a bandwidth speed test.  Speak to your IT Support if this is low so that they can investigate the problem.  Here is an example of an acceptable speed test result.



If your internet connection is good, please log a ticket with Laminin Support and also include a screenshot of your speed test result.  If your internet connection is poor, please log a ticket with your IT Support to investigate the problem.




For any questions or additional support, please mail our team at support@lamin.in

When logging a ticket with the Laminin support team, please provide as much information as possible. This can include references to specific leads or recordings as well as descriptions and screenshots of your own troubleshooting.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article