A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

What are ICE errors?

When a call is connected using the Twilio Voice JavaScript SDK (formerly "Twilio Client"), the client and server exchange periodic messages verifying that the call is alive. If these message exchanges fail, it could indicate a problem with the connection to Twilio. Previously such errors were returned to your server as unspecified errors, they now manifest as the following :

  • ICE liveness checks failed: This error implies that the browser had a media session with Twilio, but had trouble exchanging information to keep the media session active. In this case, the call will continue, although it could imply that network connectivity has degraded.
  • ICE negotiation with Twilio failed: This means that the browser made a TCP connection to Twilio for signaling, but could not establish UDP/RTP media connectivity. This can happen if network connectivity is poor, or if UDP is being blocked, or if a network policy prevents UDP to/from IP addresses in Amazon's public range. When this error occurs please ensure that the Twilio Voice JavaScript and Mobile SDK Network Connectivity and Bandwidth Requirements are taken into consideration. If you have verified connectivity requirements, but these errors persist, please contact our Support team.
Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk