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

What is a WebRTC Asterisk client?

Learn how a WebRTC client registers with Asterisk and brings business calling to a browser.

View as Markdown
The WebRTC Client webphone in dark mode on a desktop monitor in an office

A WebRTC Asterisk client is a browser-based phone interface that registers with an appropriately configured Asterisk PBX. It lets users make and receive calls through their existing extension using a compatible browser and audio device.

The roles of the client and PBX

WebRTC Client uses SIP over WebSocket for signaling and WebRTC for browser audio. Asterisk manages the extension and applies its configured dial plan, routing and permissions. Together they provide a browser calling experience backed by the existing phone system.

The client registers as a normal extension. PBX features such as voicemail, conferencing and recording can remain available through that extension when configured on Asterisk; their operation and access depend on the PBX setup. They should not be assumed to be built-in client features. Consult the Asterisk guide for connection guidance.

Calling and everyday tools

Users can place and receive calls from the browser. Depending on the configured service, call controls such as hold and transfer support everyday conversations. WebRTC Client also offers a web phonebook and presence buttons with speed dials, helping users find colleagues and initiate calls. Learn more about presence buttons and the web phonebook.

An administrator can manage users through a portal organized by system administrator, reseller, customer and user. This is useful when the service is provided to multiple customer organizations, each with its own users and settings.

Prepare for a reliable connection

A working deployment needs more than a browser tab. Check these elements with your administrator:

  • An Asterisk extension and WebRTC-compatible PBX configuration.
  • A reachable signaling endpoint and network path for media.
  • A compatible browser with microphone permission.
  • A working microphone and speaker or headset.
  • Suitable PBX routing and permissions for the intended calls.

After configuration, verify registration, an incoming call and an outgoing call. Check audio in both directions and test any PBX features your team relies on. If something fails, distinguish registration problems from audio problems: each can have different causes. The STUN server guide explains a relevant part of network configuration.

Key takeaways

  • The browser client registers with Asterisk as an extension.
  • Asterisk controls its configured routing and PBX features.
  • Voicemail, conferencing and recording depend on PBX configuration and access.
  • Test registration, audio and required call flows before deployment.