New: multiple lines, live AI transcription, queues and voicebots — early access now. More to come.See the roadmap →

WebRTC Asterisk softphone for browser calling

Connect a browser-based WebRTC softphone to Asterisk for business calls from a compatible browser.

View as Markdown
WebRTC Client panels: an active call with transcription and assistant toggles, live voicebot calls with transcript, and call queues

A WebRTC Asterisk softphone lets users make and receive calls in a compatible browser using an Asterisk phone system. WebRTC Client provides the browser dialer while Asterisk handles the configured extension and call routing.

How the connection works

Asterisk is an open-source PBX that can manage extensions and route calls. WebRTC Client connects to a suitably configured Asterisk system using SIP over WebSocket and uses WebRTC for browser audio. The browser interface gives users a way to work with their business extension without a separate desktop softphone application.

The connection requires compatible PBX settings and a network path between the client and the server. External calling also depends on the PBX's configured provider and routing. Consult the Asterisk guide for configuration guidance and the compatibility overview for supported systems.

What users need

Users need a compatible browser, a reliable network connection and a microphone and speaker or headset. They must grant microphone permission when prompted and select the correct audio devices. A quiet test call is a useful way to check both directions of audio before relying on the setup for daily work.

Remote users can work through their browser when the PBX and network are configured to allow their connection. Location alone does not guarantee connectivity: firewalls, network address translation and audio device settings can all affect a call.

Set up and test the service

  1. Prepare an Asterisk extension and configure the PBX for the WebRTC connection.
  2. Configure the corresponding customer and user in WebRTC Client using the appropriate connection details.
  3. Sign in from a compatible browser and allow microphone access.
  4. Confirm that the extension registers, then place and receive a test call.
  5. Check audio in both directions and verify the call routes and permissions your users need.

If registration fails, review the credentials, server address and WebSocket configuration with the PBX administrator. If registration works but audio does not, check browser permissions, selected devices and network configuration. The STUN server guide provides related network guidance.

Key takeaways

  • WebRTC Client brings an Asterisk extension into a compatible browser.
  • Asterisk remains responsible for configured extensions and routing.
  • PBX, network and audio settings all need to work together.
  • Test registration and calls in both directions before rollout.