WebRTC Connection Failed

What Causes This Error

The browser-based WebRTC softphone cannot establish a connection to the Asterisk server. Causes include: WSS (WebSocket Secure) port not open or blocked by firewall, SSL certificate issues with the WebRTC endpoint, STUN/TURN server not configured, browser doesn’t support WebRTC, or Asterisk res_pjsip_transport_websocket module not loaded.

How to Fix It

• 1 Check if WebSocket port (8088/8089) is accessible from agent browser: nc -zv VICIDIAL_SERVER 8089

• 2 Verify SSL certificate is valid for the VICIdial hostname: openssl s_client -connect HOSTNAME:8089

• Check Asterisk has pjsip_transport_websocket: asterisk -rx ‘module show like websocket’

• 4 Verify firewall allows port 8089 from agent IPs: iptables -L | grep 8089

• 5 Check http.conf: cat /etc/asterisk/http.conf — enable=yes, bindport=8088

• Load missing module: asterisk -rx ‘module load res_pjsip_transport_websocket.so’

• 7 Test from agent browser: open browser console and check WebSocket connection errors

How to Prevent It

Monitor WebRTC connection success rate in agent login reports. Use a wildcard SSL certificate to avoid certificate mismatch issues. Document WebRTC browser requirements for agents. Test WebRTC after any firewall changes.

ViciStack’s free 30-day support plan includes unlimited live VICIdial troubleshooting. If you can’t resolve this error with the steps above, our engineers will connect to your system and fix it directly — no support tickets, no hourly billing.