Issues with your connection and environment cause performance problems when you use web-based software such as Zendesk Voice (formerly Talk). System or network issues might not appear when you manage tickets but become obvious with a telephony connection. This article provides steps to fix these issues.
Before you begin, ask these questions to rule out common issues:
- Did Voice (formerly Talk) work before? Check if your IT team changed your network or computer, or added new software or add-ons.
- Is the issue affecting other agents or just you? If the issue affects only you, check your local settings and network. If you and other agents have issues, check with your IT and network teams first, especially if you use a company‑managed laptop.
- Can agents who use unified agent status take calls? If you use unified agent status, make sure agents have appropriate Voice (formerly Talk) permissions and check the live dashboard to confirm agents appear online for Voice (formerly Talk) calls.
Voice (formerly Talk) does not work
Voice (formerly Talk) problems relate to your network. In office setups, network teams block some ports or IP addresses. Ask your network team to confirm that you meet all Voice (formerly Talk) network requirements. For more information, see Voice (formerly Talk) network requirements.
Perform these checks:
- Check the Zendesk and Twilio status pages for outages
- Check the Agent leg quality issues report in Explore to identify call quality issues on your team and with specific agents
Fix voice quality issues
Use these checks to fix call quality:
-
Ask your IT team whether your Voice (formerly Talk) traffic goes through a virtual private network (VPN). If it does, make sure Voice (formerly Talk) traffic does not go through your company network. Your IT department can split-tunnel this traffic or remove the Zendesk IP addresses from the VPN.
Voice (formerly Talk) does not work with multiprotocol label switching (MPLS) or VPN due to Twilio's edge network architecture requirements.
- Run the Twilio network test to confirm ports are open, speed is adequate, and you connect to the right endpoint. To use these results, see How to use the Twilio network test to troubleshoot Voice (formerly Talk) agent calls?
- Connect your computer to your router with an Ethernet cable. Wi‑Fi works, but Ethernet is stable because other wireless devices can interfere with the signal.
- Try a different web browser to rule out a browser issue
- Connect your headset to the computer with a 3.5 mm cable instead of Bluetooth. A USB connection is better than Bluetooth. Other wireless devices and signals degrade audio. To rule out the headset as the cause, use your computer speakers and make a test call.
- If you use a gaming headset, deactivate its audio driver software. It's not supported and causes issues with Voice (formerly Talk). Sometimes browsers, such as Chrome, don't synchronize fast enough in this situation.
- Make sure your internet connection is stable. If your web browser passes the Twilio test and you still have issues, your connection might be unstable. You might drop network packets or have a connection that slows down at times. Your IT or network team can run software over time to measure stability. Do this yourself only if you feel comfortable and your company's IT department allows it.
To see how stable your internet connection is:
- If you're at home, reboot your router
- Run a ping test for 10 to 15 minutes, especially when you have problems. Check for stability and packet loss. See the image below for a short example of the test results.
- In addition to www.zendesk.com, test the Twilio client endpoints with a ping test
Make sure the ping time in ms is adequate and stays consistent. In most cases, you want zero packet loss. If you see as much as 1% packet loss in 15 minutes, this might affect your connection. Voice (formerly Talk) with your IT department or contact your internet service provider for help.
Network connectivity test endpoints
Endpoint URLs may be updated by Twilio. Verify against current Twilio documentation every time before you configure firewalls or network policies.
Make sure the ping time in ms is adequate and stays consistent. In most cases, you want zero packet loss. If you see as much as 1% packet loss in 15 minutes, this might affect your connection. Voice (formerly Talk) with your IT department or contact your internet service provider for help.
Dropped calls
If calls drop after two minutes, check with your admin. You might use a trial account. Voice (formerly Talk) trial accounts limit calls to two minutes. If calls drop every time you call one of your numbers and you use an IVR setup, create a custom greeting. Without a greeting in the right interactive voice response (IVR) menu locations, the system hangs up. If you already have a greeting, a corrupt audio file can cause the same behavior. Re-record the audio file and upload it again to rule this out.
EC# error
See an <EC#> error example:
EC# errors often come from your network or router configuration. They indicate that Voice (formerly Talk) doesn't have an adequate network connection. This can occur anywhere on the network, but it often results from local network limits or from a computer that doesn't meet the minimum requirements to make the connection. Review the Voice (formerly Talk) network requirements. Ensure all ports are open. Also review the steps above. If you still experience EC# errors, contact Zendesk Customer Support for further help. Provide a screenshot of your firewall and router settings that shows these open ports.
For more information on what to include in a ticket about Voice (formerly Talk), see How can I share example calls for troubleshooting a Voice (formerly Talk) issue?
Call status issues
If you refresh your page, your agent status might change to unavailable in Voice (formerly Talk). An agent needs to manually reset their Voice (formerly Talk) agent state to become available. Don't refresh your browser page when you want to receive calls.
If you can't determine the cause of your quality issues and your issue is specific to call routing, see Why are phone calls not routing to agents?