# WebRTC Client — full site content > WebRTC Client is a browser-based softphone and multi-tenant management portal that connects to your existing PBX (Asterisk, FreePBX, VitalPBX, MirtaPBX, Issabel and more) over a secure websocket. No devices or installs. The new version adds multiple lines, live AI transcription, queues and voicebot monitoring — available in early access, with more to come. Generated: 2026-11-18 --- # WebRTC Client > Call from your browser with multiple lines and live AI transcription. A browser softphone for Asterisk, FreePBX, VitalPBX, MirtaPBX and other PBX systems — no devices or installs. URL: https://webrtcclient.com/ **New: multiple lines & live transcription** # Calling from your browser — *with live transcription.* No desk phones, no installations. Call straight from Chrome, Edge, Firefox or Safari with multiple lines, live AI transcription and simple management — connected to the phone system you already run. [Get early access](https://webrtcclient.com/trial/) [Explore features](https://webrtcclient.com/features/) - Live transcription & translation (optional) - Works anywhere: office & home - No devices or installs needed ![The WebRTC Client webphone in dark mode on a desktop monitor in a modern office](https://webrtcclient.com/img/product/webphone-v3.png) **It doesn't get easier** ## You just want to call — without the hassle With WebRTC Client you work from anywhere as if you were at the office. Switch between calls, transfer, and work together with colleagues — all in one clear screen. And thanks to live transcription you always know what was discussed, without taking notes. - Multiple lines: handle and switch between several calls - Attended and direct transfer, hold, mute and keypad - Transcription, AI assistant and live assist — one toggle per call - Panels you can show, hide and arrange to fit your work [See all call features →](https://webrtcclient.com/features/call-features/) ![WebRTC Client panels: an active call with transcription, assistant and live assist toggles, voicebot calls with a live transcript, and call queues](https://webrtcclient.com/img/product/webphone-panels.jpg) **Up and running quickly, instant overview** ## See what's happening — at a glance You're live in no time: we set everything up and make sure it works the way you expect. In the browser you immediately see who's available, and what your queues and AI assistant are handling. ### Presence & status See instantly whether colleagues are available, on a call or don't want to be disturbed — and set your own status. No more calling at the wrong moment. ### Queues Callers waiting, longest wait, active calls, agents online and free agents per queue. Pause or log out of queues in one click. ### Voicebots & AI assistant Follow live voicebot calls with their transcript, listen in, take over or transfer the caller — or tell the bot what to say. **Live AI transcription** ## Never take call notes again Switch on transcription for a call and the conversation appears as text while you talk — both sides clearly labelled. Afterwards the transcript is right there with the call. - Optional and switchable per call - Live translation (beta): talk to customers in their own language, with the translation next to the transcript - Live assist: AI support during the conversation - Controlled per tenant with policies [About live transcription & translation →](https://webrtcclient.com/features/ai-transcription/) ![A live transcript of a phone call shown in the WebRTC Client on a desktop monitor](https://webrtcclient.com/img/product/live-transcript.png) **A full desk-phone replacement** ## Everything you expect from business telephony — in your browser You don't need a desk phone anymore. ### Call & be called Place and receive calls, hold, mute and use the keypad. ### Transfer Attended (announced) or direct transfer in two clicks. ### Multiple lines Handle call waiting and switch between calls. ### Call history Searchable history with filters and one-click call-back. ### Click to call Click a number — or a `tel:` link on any web page — to dial. ### Presence & status See who's available and change your own status. ### Speed-dial panel BLF buttons and speed dials, just like a desk phone. ### End-to-end encrypted Secure WSS signalling and DTLS-SRTP encrypted audio. **Compatibility** ## Works with the PBX you already run Any phone system with a secure websocket (WSS) and WebRTC-enabled extensions works. Step-by-step guides are available for the most popular platforms. - [![Asterisk logo](https://webrtcclient.com/img/logos/asterisk.png)](https://webrtcclient.com/guides/asterisk/) Asterisk - [![FreePBX logo](https://webrtcclient.com/img/logos/freepbx.png)](https://webrtcclient.com/guides/freepbx/) FreePBX - [![VitalPBX logo](https://webrtcclient.com/img/logos/vitalpbx.png)](https://webrtcclient.com/guides/vitalpbx/) VitalPBX - [![MirtaPBX logo](https://webrtcclient.com/img/logos/mirtapbx.png)](https://webrtcclient.com/guides/mirtapbx/) MirtaPBX Also compatible with Issabel, Kamailio and FreeSWITCH. [See full compatibility →](https://webrtcclient.com/compatibility/) ## Built for everyone in the telephony chain Whether you run a single office or a platform with thousands of seats, WebRTC Client fits the way you already work. ### Businesses Connect your existing phone system and start calling from the browser. Keep your PBX and your telephony provider. ### Partners & resellers Sell a browser-based VoIP solution under your own brand. Add companies and users in minutes. ### Service providers Run the complete multi-tenant, white-label platform in your own cloud. ## Latest articles - [New in WebRTC Client: multiple lines and live AI transcription](https://webrtcclient.com/blog/new-multiple-lines-and-live-transcription/) (2026-11-18): The new WebRTC Client adds multiple lines, live AI transcription, an AI assistant, voicebot monitoring and a queue overview — all in the browser. - [A browser-based alternative to desktop softphones like Bria](https://webrtcclient.com/blog/alternative-to-desktop-softphones/) (2023-05-16): Compare the practical considerations of a browser softphone and a desktop application such as Bria. - [Click to call with tel links in Chrome](https://webrtcclient.com/blog/click-to-call-with-tel-links/) (2023-04-21): Use the Click2Tel Chrome extension to send phone numbers from tel links to your WebRTC Client dialer. [All articles →](https://webrtcclient.com/blog/) ## More to come AI call summaries, searchable conversations and more are on the way. Get in touch to join early access, or to talk about a partner or service-provider licence. [Contact us](https://webrtcclient.com/contact/) --- # Compatible PBX and phone systems > WebRTC Client works with any phone system that offers a secure websocket and WebRTC-enabled extensions, including Asterisk, FreePBX, VitalPBX, MirtaPBX, Issabel, Kamailio and FreeSWITCH. URL: https://webrtcclient.com/compatibility/ WebRTC Client is compatible with almost every phone system. The only requirement is a **secure websocket (WSS) listening on your PBX** and extensions with WebRTC enabled. Connect it in a few steps and start dialing from your favourite browser. - [![Asterisk logo](https://webrtcclient.com/img/logos/asterisk.png)](https://webrtcclient.com/guides/asterisk/) Asterisk - [![FreePBX logo](https://webrtcclient.com/img/logos/freepbx.png)](https://webrtcclient.com/guides/freepbx/) FreePBX - [![VitalPBX logo](https://webrtcclient.com/img/logos/vitalpbx.png)](https://webrtcclient.com/guides/vitalpbx/) VitalPBX - [![MirtaPBX logo](https://webrtcclient.com/img/logos/mirtapbx.png)](https://webrtcclient.com/guides/mirtapbx/) MirtaPBX ## Supported systems | Phone system | Status | Guide | |---|---|---| | [Asterisk](https://www.asterisk.org/) (chan_sip and PJSIP, 11+) | Supported | [Asterisk guide](https://webrtcclient.com/guides/asterisk/) | | [FreePBX](https://www.freepbx.org/) | Supported | [FreePBX guide](https://webrtcclient.com/guides/freepbx/) | | [VitalPBX](https://www.vitalpbx.org/) | Supported | [VitalPBX guide](https://webrtcclient.com/guides/vitalpbx/) | | [MirtaPBX](https://www.mirtapbx.com/) | Supported, incl. API login | [MirtaPBX guide](https://webrtcclient.com/guides/mirtapbx/) | | [Issabel](https://www.issabel.org/) (Issabel Project / Issabel PBX) | Supported | [Issabel guide](https://webrtcclient.com/guides/issabel/) | | [Kamailio](https://www.kamailio.org/) | Supported | — | | [FreeSWITCH](https://freeswitch.org/) | Supported | Guide coming | | Other SIP platforms with WSS | Usually works | [Contact us](https://webrtcclient.com/contact/) | ## Requirements in short - A **valid TLS certificate** for the PBX hostname (not self-signed). - A **websocket over TLS**, usually on TCP port `8089`, reachable from where your users are. - Extensions with **WebRTC enabled**: AVPF, ICE support, rtcp-mux and DTLS-SRTP media encryption. - A **STUN server** when the PBX is behind NAT — see [STUN servers](https://webrtcclient.com/guides/stun-servers/). - For users: a modern browser (Chrome, Edge, Firefox or Safari), a microphone and speakers or a headset. [Go to the integration guides →](https://webrtcclient.com/guides/) --- # Roadmap — more to come > What is new in WebRTC Client — multiple lines, live AI transcription, queues and voicebots — and what comes next, such as AI call summaries and searchable conversations. URL: https://webrtcclient.com/roadmap/ | Status: in-development WebRTC Client has been rebuilt. The proven feature set — browser calling, presence, multi-tenancy and white-label — stays at the core, and the new version adds multiple lines, live AI transcription, queues and voicebots. And there is more to come. This page shows where we are heading. Plans can change; we update this page as we go. ## Now and next ### New version — early access The new WebRTC Client is available in early access and in active development: - [Multiple lines](https://webrtcclient.com/features/multiple-lines/) with per-call controls - [Live AI transcription](https://webrtcclient.com/features/ai-transcription/), switchable per call - [Live call translation](https://webrtcclient.com/features/ai-transcription/#live-call-translation-beta) in both directions (beta) - AI assistant and live assist during calls - [Voicebot monitoring](https://webrtcclient.com/features/voicebots/): live transcript, listen in, transfer, take over - [Queues](https://webrtcclient.com/features/queues/) with live figures, pause and log out - Presence with your own status, configurable panels, call history with filters ### AI call summaries and action items A short summary with action items after every call, stored with the call history entry. ### Searchable conversations Find calls by what was said, not only by number or date. ### Client improvements - Caller ID refresh on attended transfer (RPID / PAI / From) - Custom distinctive ringtones per user - Personal phonebook and phone-number search across phonebooks - Add users as BLF buttons directly - Send a call-back e-mail request from call history - Two-factor authentication (2FA) ### Integrations - FreeSWITCH integration guide - Improved MirtaPBX API integration - Research: WebRTC-to-SIP proxy for PBX systems without native WebRTC support - User manual for the new WebRTC client ## Help shape the roadmap Have a feature request or want to join early access? We build on customer demand. [Contact us](https://webrtcclient.com/contact/) See what has been delivered so far in the [changelog](https://webrtcclient.com/changelog/). --- # Changelog > Release history of WebRTC Client — the new client built since December 2025 (multiple lines, live AI transcription, translation, queues, voicebots, headset control) and the previous generation from 2021–2023. URL: https://webrtcclient.com/changelog/ The release history of WebRTC Client. The new client has been built from the ground up since 7 December 2025; the releases of the previous generation (2021–2023) are listed further down. For what's coming next, see the [roadmap](https://webrtcclient.com/roadmap/). ## New WebRTC Client ### 9.1.4 — 14 October 2026 Live call translation (beta) and more reliable reconnects. - **New:** live call translation (beta) for incoming and outgoing audio. The translation appears next to the transcript of each speaker. - **New:** set a default language for yourself and for the customer, and switch languages during the call. Dutch is available as a beta translation target. - **New:** administrators decide per tenant or user whether translation is available. - **New:** choose between the Stable and Beta channel from the version button in the footer — even before signing in. The choice is remembered on the device and cannot be changed during a call. - Separate language settings for the microphone and the remote-party transcript. - Wider AI tools menu; smoother ringing animation on modest graphics hardware; BLF updates are drawn in batches. - After a connection loss the client restores the websocket, waits for a confirmed registration and re-subscribes all BLF buttons. Reconnects are spread with a random delay to protect the PBX. - Fixed: transcription and translation now stop cleanly on hold, hang-up or when switched off, and remaining translated text is saved with the call transcript. - Fixed: changing the microphone during a translated call keeps the new microphone and its mute state. - Fixed: the voicebot panel refreshes its agent list every minute and reconnects with current details. ### 9.1.3 — 4 June 2026 - **New:** support for realtime voicebots of the latest generation in the voicebot panel: live transcript, transfer, whisper/say-in and remote hang-up. ### 9.1.1 — 22 May 2026 - Fixed: headset call control stays active after a page refresh or reconnect. ### 9.1.0 — 1 May 2026 Voicebots, queues, server-side buttons and tenant feature management. - **New:** [voicebots](https://webrtcclient.com/features/voicebots/) — follow and manage active voicebot calls from the webphone. - **New:** [queues](https://webrtcclient.com/features/queues/) — your queues, waiting callers and agents, a *Take call* action and transfer of queue calls to your own extension. - **New:** settings per tenant and per user, feature toggles, button profiles and a provisioning portal for administrators, including a bulk page to switch features on or off for many users at once. - **New:** permissions that control whether users may change their status, personal buttons, caller ID, DND, the queue panel, queue transfers, voicebot controls and webhooks. - **New:** personal BLF and speed-dial buttons are stored on the server, so they follow you to every device. - **New:** DND and caller-ID controls in the user menu. - **New:** presence everywhere — status of colleagues and queue agents in phonebook search, the transfer dialog and dialer search. - **New:** webhooks that send call transcripts to your CRM or AI tools. - Movable panel layout: drag and resize panels, save named layouts, synchronised per user. - Improved search across phonebook, extensions, queues and agents. - Call history shows a call as soon as it is active; clearer compact history cards. - F5 no longer reloads the page by accident during a call (Ctrl/Cmd+R still works). - A manual headset disconnect is remembered and not reconnected automatically. ### 9.0.4 – 9.0.9 — February–March 2026 - **New:** the realtime AI assistant is integrated in the active call card, with an expandable transcript and assistant panel. - **New:** transcripts can be stored on the server for analysis (with an explicit consent text), synced in the background without affecting calls. Only new transcripts are uploaded. - Call history retention extended from 30 to 365 days, loading 50 items at a time while you scroll. - Pressing Transfer puts the current call on hold first. - Pasted numbers such as `+31 (0) 6 1234 5654` are cleaned up automatically. - Better behaviour when switching audio devices. ### 8.2.0 – 8.3.0 — January–February 2026 Headset call control, phonebook editing and connection monitoring. - **New:** Yealink headset call control — answer, hang up, mute and unmute. - **New:** Jabra headset call control via WebHID. - **New:** Poly (formerly Plantronics) call control, including the BT600 and BT700 dongles. - Headsets reconnect automatically when plugged back in. - **New:** add and delete phonebook contacts from the webphone and from call history; names in history are resolved from the phonebook. - **New:** "Trust this device for 30 days" for two-factor authentication; the last login e-mail is remembered. - **New:** speed dials in the transfer dialog; click an active call to take it off hold; ringback tone during an attended transfer; caller ID refreshes on call pickup. - Pasted numbers are cleaned up (spaces, dashes, brackets, dots) and normalised (`+31 6…` → `06…`, other countries → `00…`). - Connection-quality monitoring with SIP latency measurements and alerts on registration problems. - Improved audio settings and audio testing. ### 8.0.0 – 8.1.3 — January 2026 First AI features and better audio. - **New:** AI analysis of call transcripts, with a default prompt, your own instructions and optional automatic analysis after every call. - **New:** first-login consent dialog; calls can be excluded from AI processing. - **New:** voice isolation, improved echo cancellation, noise reduction and automatic gain control. - **New:** notifications and an explanation dialog when audio devices change; transcription follows the new device. - **New:** mark BLF buttons as favourite to show them first; manual BLF and speed-dial buttons; multiple function-button profiles. - Call history, transcripts and analyses moved to browser storage without the 5 MB limit. - Large phonebooks load without slowing down the browser. - Better handling of expired sessions, network disconnects and BLF after sleep or hibernation. - Click2Tel/click-to-call extension support updated. ### 7.0.0 – 7.4.1 — January 2026 - Reliable hold/unhold with multiple simultaneous calls, also during early media. - Larger dial buttons, improved incoming-call animation and a tinted background for calls on hold. - Redesigned BLF panel and full-screen layout; history and BLF filters as tabs. - Version and changelog link in the footer. ### 6.x — late December 2025 - **New:** two-factor authentication. - **New:** departments, history filters (collapsible) and a list or grid view. - **New:** multiple speech-to-text engines. - **New:** login, session checks and upfront browser permissions with an explanation when microphone access is missing. - Declined calls get their own status in history. ### 1.0.0 – 5.x — 7–23 December 2025 The new client was built from scratch, starting on 7 December 2025: - Dialer, DTMF and a mobile-friendly layout - [Multiple lines](https://webrtcclient.com/features/multiple-lines/) with call waiting, hold and mute - First live transcriber and transcription button - BLF and speed dials, phonebook and history search - Browser notifications, audio indications and early media - Automatic reconnect and per-user storage ## Previous generation (2021–2023) ### V2023-0.05 - Click-to-call Chrome extension released and approved by Google. After installing the extension and restarting your browser, you can click `tel:` links to place the number in the dialer. [Learn more](https://webrtcclient.com/features/click-to-call/). ### V2022-03 - Better breadcrumbs and page titles - Image upload improvements - End-user licence agreement (EULA) and acceptance - Better visibility while transferring - Automatic retry when the WebRTC connection is lost - External links for partners - Incoming call control and call waiting - Fixed transfer after hold; call put back on hold after a failed transfer - Fixed duplication and editing of button profiles - Server-side Do Not Disturb - Two-factor authentication (work started) - Fixed special characters in the WebRTC client - SIP passwords hidden in the management interface ### V2022-02 - Penetration tests performed by an external security company - Duplicate button profiles - Fixed multiple input fields and the forgot-password flow - Improved database scheme and indexing for performance - Fixed an error after standby - Improved responsive layout - New URL structure - Call control for Plantronics / Poly and Jabra headsets ### V2022-01 Beta version of the WebRTC client: - Log in and log out - Place and receive calls - Add BLF and speed-dial keys - Set up the websocket connection in the management portal ### V2021-12 Initial version of the WebRTC client: - Faster page loading and new menu items - Edit function keys - Permissions and tenant-admin features - Reason codes in call history - Retry connections - Security fixes - New layout and buttons in the client --- # Features > Everything WebRTC Client offers — multiple lines, live AI transcription, queues, voicebots, presence, phonebook, click-to-call, multi-tenancy and white-label branding. URL: https://webrtcclient.com/features/ WebRTC Client is an all-in-one WebRTC communication platform. It combines a browser-based softphone with a multi-tenant management portal, so businesses, resellers and service providers can deliver professional telephony to every desk — without installing anything. ### Call features Calling, attended and unattended transfer, hold, mute, dial pad, redial and call rejection — the essentials, done right. ### Multiple lines Call waiting and switching between calls, with hold, transfer and per-call AI toggles. ### Live AI transcription Switch on transcription per call and read the conversation as it happens. Optional, with live assist. ### Live call translation Speak with customers in another language: the translation appears live next to the transcript, in both directions. ### Queues Callers waiting, longest wait, agents online and free agents — live, per queue. ### Voicebots & AI assistant Follow voicebot calls with a live transcript, listen in, take over or transfer. ### Advanced call features Reason codes, distinctive ringtones via Alert-Info, and both server-side and client-side Do Not Disturb. ### Presence buttons & speed dials See whether colleagues are available, busy or on Do Not Disturb, set your own status, and use BLF speed dials. ### Web phonebook Point to a CSV file and every user gets a sorted, searchable contact list inside the client. ### Click-to-call extension A Chrome extension that turns every `tel:` link on the web into a number in your dialer. ### Multi-tenant System administrator, Reseller, Customer and User layers — each with their own scope and permissions. ### White-label branding Your logo, colours, domain name and notification e-mail addresses on every layer of the platform. ### Headset integration Answer, end and mute calls from supported Yealink, Poly (Plantronics) and Jabra headsets. ### End-to-end encrypted Secure WSS signalling and DTLS-SRTP encrypted audio, with two-factor authentication for users. ### Works anywhere Office or home: all you need is a browser and an internet connection. No devices, no installs. ## Platform at a glance | Area | What you get | |---|---| | Client | Browser softphone (Chrome, Edge, Firefox, Safari) with multiple lines and configurable panels — no installation | | Signalling & media | SIP over secure websocket (WSS), DTLS-SRTP encrypted audio, ICE/STUN for NAT traversal | | PBX support | Asterisk, FreePBX, VitalPBX, MirtaPBX (incl. API login), Issabel, Kamailio, FreeSWITCH | | Administration | Multi-tenant management portal with policies, button profiles and phonebooks | | Branding | Full white-label per reseller and customer | | Security | E-mail/password login with SIP passwords hidden, encrypted media, external penetration tests; 2FA in development | | AI | Live transcription per call, live call translation (beta), AI assistant and live assist, voicebot monitoring | | Coming next | AI call summaries, searchable conversations — [see roadmap](https://webrtcclient.com/roadmap/) | --- # Live AI transcription > Switch on live transcription per call and see the conversation as text while you talk — now with live call translation (beta). Optional, controlled per tenant, with live assist and an AI assistant. URL: https://webrtcclient.com/features/ai-transcription/ | Status: new Phone calls hold some of the most valuable information in a business — and most of it is lost the moment you hang up. With live AI transcription in WebRTC Client the conversation appears as text while you talk, so you always know what was discussed, without taking notes. ![A live transcript of a call shown in the WebRTC Client](https://webrtcclient.com/img/product/live-transcript.png "The transcript window: both sides of the conversation, with timestamps.") ## How it works - **One toggle per call** — switch *Transcription* on in the call card of the [calls panel](https://webrtcclient.com/features/multiple-lines/). - **Live** — text appears in real time, with both sides of the call labelled and timestamped. - **Afterwards** — the transcript is available with the call, ready to read back. - **Live assist and AI assistant** — switch on AI support for the same call with the *Live assist* and *Assistant* toggles. - **Voicebot calls too** — conversations handled by an [AI voicebot](https://webrtcclient.com/features/voicebots/) show their transcript live. ## Live call translation (beta) Talking to a customer who speaks another language? Switch on **live translation** and the translated text appears right next to each speaker's transcript — for both what you say and what you hear. - **Both directions** — incoming and outgoing audio are translated live during the call. - **Your language and theirs** — set a default language for yourself and for the customer, and switch languages during the call when needed. - **Separate language settings** for your microphone and for the remote party. - **Saved with the call** — translated text is stored together with the call transcript. - **Controlled by the administrator** — per tenant or user you decide whether translation is shown and can be used. **Beta:** Live translation is in beta. Dutch is available as a beta translation target, and more languages and improvements are on the way. Choose the Beta channel from the version button in the client to try it. ## Optional and under your control Transcription and translation are **optional**. Administrators decide per tenant which users and teams may use it, with [policies](https://webrtcclient.com/guides/quick-start/policies/). We design the AI features to: - make it clear to the user when transcription is active; - keep transcripts within the tenant that owns them; - let administrators set retention periods; - support the GDPR obligations of European businesses. ## Why in the browser? Because WebRTC Client already handles the audio in the browser, transcription needs no extra hardware, recording integrations or PBX changes. It works with Asterisk, FreePBX, VitalPBX, MirtaPBX and every other [compatible system](https://webrtcclient.com/compatibility/). **More to come:** More translation languages, AI call summaries with action items and searchable conversations are next on the [roadmap](https://webrtcclient.com/roadmap/). --- # Call features > The essential call handling in WebRTC Client — calling, attended and unattended transfer, hold, mute, dial pad, redial and call rejection, all in the browser. URL: https://webrtcclient.com/features/call-features/ The foundation of any reliable communication platform is its basic call handling. WebRTC Client gives every user the tools they know from a desk phone, in a clean browser interface that needs no training. ![WebRTC Client panels: an active call with transcription and assistant toggles, live voicebot calls with transcript, and call queues](https://webrtcclient.com/img/product/webphone-panels.jpg "Calls, transcription, voicebots and queues side by side in one screen.") ## Calling Start a call with a single click on a contact, a presence button or a call-history entry — or type the number in the dialer. Incoming calls show a browser notification, so you never miss one while working in another tab. ## Multiple lines Take a second call while you're on the phone and switch between calls. Each call has its own card with its own controls. [More about multiple lines](https://webrtcclient.com/features/multiple-lines/). ## Call transfer Connect a caller to another department or colleague without hassle. WebRTC Client supports both transfer types: ### Attended transfer Speak with the recipient first, then complete the transfer. Use it when you want to be sure the colleague is available and prepared to take the call. ### Unattended (direct) transfer Send the call straight to another extension or phone number without announcing it. Ideal for quickly routing callers to the right person or team. ## Hold Put a caller on hold and pick the call up again whenever you are ready to continue the conversation. ## Mute Silence your microphone with one click — to cut background noise or have a quick word with a colleague. ## Dial pad A built-in keypad for entering numbers, navigating IVR menus and typing access codes during conference calls (DTMF). ## Redial Call back the last dialed number instantly, or redial any entry from the call history. ## Call history All incoming, outgoing and missed calls in one list, with search and filters (all, incoming, missed, outgoing) and one-click call-back. ## Reject a call Not every call can be answered right away. Reject it and the PBX sends it to voicemail or another pre-configured destination. **Looking for more?:** See the [advanced call features](https://webrtcclient.com/features/advanced-call-features/) such as reason codes, distinctive ringtones and Do Not Disturb, or [presence buttons and speed dials](https://webrtcclient.com/features/presence-buttons-blf-speed-dials/). --- # Multiple lines > Handle several calls at once in the browser — call waiting, switching between calls, hold, transfer and per-call controls in the WebRTC Client calls panel. URL: https://webrtcclient.com/features/multiple-lines/ | Status: new WebRTC Client handles multiple lines, just like a professional desk phone. Take a second call while you're on the phone, switch between conversations and transfer the right call to the right colleague — all from the calls panel in your browser. ![The calls panel in WebRTC Client with an active call and buttons for hold, mute, transfer, keypad and hang up, plus transcription, assistant and live assist toggles](https://webrtcclient.com/img/product/webphone-panels.jpg "The calls panel (left): every call gets its own card with controls.") ## How it works - **Every call gets its own card** in the *Calls* panel, showing the name, number, state (for example *Active*), duration and direction. - **Call waiting** — a new incoming call appears while you're on the phone. Answer it and the current call goes on hold. - **Switch between calls** — pick up the call you want; the other one stays on hold. - **Per-call controls** — hold, mute, transfer, keypad and hang up on every call card. - **Per-call AI toggles** — switch *Transcription*, *Assistant* and *Live assist* on or off for each call separately. See [live AI transcription](https://webrtcclient.com/features/ai-transcription/). ## Who decides? Whether a user may receive a second call is set with the *call waiting* option in [policies](https://webrtcclient.com/guides/quick-start/policies/). Call-centre agents can be limited to one call at a time; receptionists can handle several lines. ## Related - [Call features](https://webrtcclient.com/features/call-features/) — transfer, hold, mute, history - [Queues](https://webrtcclient.com/features/queues/) — see what's waiting before it reaches you --- # Queues > See your call queues live in the browser — callers waiting, longest wait, active calls, agents online and free agents — and pause or log out of queues in one click. URL: https://webrtcclient.com/features/queues/ | Status: new The *Queues* panel in WebRTC Client shows what's happening in your call queues in real time. Teams see at a glance how busy it is, and agents manage their own queue membership without asking an administrator. ![The Queues panel in WebRTC Client listing queues with callers waiting, longest wait, active calls, agents online and free agents](https://webrtcclient.com/img/product/webphone-panels.jpg "The Queues panel (bottom): live figures per queue.") ## Live figures per queue | Figure | Meaning | |---|---| | Waiting | Number of callers currently waiting in the queue | | Longest wait | How long the caller who has waited longest has been waiting | | Active calls | Calls from this queue currently being handled | | Agents online | Agents logged in to the queue | | Free agents | Logged-in agents who are available to take a call | ## Agent controls - **Pause** a queue for yourself — for example during a break or while finishing a call note. - **Log out of all queues** in one click at the end of the day. - Switch between the **queue callers** view and the **queues** overview. ## Good to know - Queue figures come from your PBX. Availability of queue information depends on the phone system and its configuration — [contact us](https://webrtcclient.com/contact/) to check your setup. - Combine queues with [multiple lines](https://webrtcclient.com/features/multiple-lines/), [presence](https://webrtcclient.com/features/presence-buttons-blf-speed-dials/) and [voicebots](https://webrtcclient.com/features/voicebots/) for a complete overview in one screen. --- # Voicebots and AI assistant > Follow AI voicebot calls live in the browser with a real-time transcript, listen in, transfer or take over the caller, end the call, or tell the bot what to say. URL: https://webrtcclient.com/features/voicebots/ | Status: new More and more first-line calls are answered by an AI voicebot — a virtual assistant that greets callers, answers questions and routes them. WebRTC Client shows you exactly what the voicebot is doing, live, and lets you step in at any moment. ![The Voicebots panel in WebRTC Client showing a current voicebot call with a live transcript and buttons to listen, transfer, transfer to me and end the call](https://webrtcclient.com/img/product/webphone-panels.jpg "The Voicebots panel (right): a live voicebot call with its transcript.") ## Follow voicebot calls live The *Voicebots* panel lists the voicebot conversations that are going on right now, per voicebot. For each current call you see the caller's name and number, the start time, and a **live transcript** of what the assistant and the caller are saying. ## Step in when needed | Action | What it does | |---|---| | **Listen** | Listen in on the voicebot call without the caller noticing. | | **Transfer** | Transfer the caller to a colleague or another destination. | | **Transfer to me** | Take the caller over yourself. | | **End call** | End the voicebot call. | | **Say** | Type a text and the voicebot speaks it to the caller. | ## AI assistant in your own calls On every call card in the *Calls* panel you can switch on the **Assistant** and **Live assist** for that call, next to [live transcription](https://webrtcclient.com/features/ai-transcription/). The assistant works alongside you during the conversation. **More to come:** AI call summaries, action items and searchable conversations are on the [roadmap](https://webrtcclient.com/roadmap/). --- # Advanced call features > Reason codes, distinctive ringtones based on Alert-Info, and server-side and client-side Do Not Disturb in the WebRTC Client browser softphone. URL: https://webrtcclient.com/features/advanced-call-features/ On top of the [basic call features](https://webrtcclient.com/features/call-features/), WebRTC Client offers advanced functionality for modern businesses and contact centres. These tools give users and administrators more control over how calls are handled. ## Reason codes Users can select predefined reason codes during or after call handling — for example to record the outcome of a call, or why a call was transferred or missed. Reason codes are stored with the call history, giving teams and managers better insight. ## Distinctive ringtones (Alert-Info) Recognise the type of call before you answer. WebRTC Client reads the SIP `Alert-Info` header set by your PBX and plays a matching ringtone. Assign different ringtones to queues, VIP customers, internal calls or specific inbound numbers so users can prioritise at a glance. ## Do Not Disturb WebRTC Client supports two kinds of Do Not Disturb (DND), so it works with the way your PBX is set up: | Type | What happens | Typical use | |---|---|---| | **Server-side DND** | The PBX stops delivering calls to the extension and reroutes them to a predetermined destination, such as voicemail or another extension. | When DND must apply to all of the user's devices. | | **Client-side DND** | The browser client stops ringing and suppresses incoming call notifications. | Focus time in the browser while desk phones keep working. | Whether a user may toggle DND is controlled with [policies](https://webrtcclient.com/guides/quick-start/policies/) in the management portal. ## Call waiting With call waiting enabled, a user can receive a second call while already on the phone. Without it, a second incoming call is rejected with *busy* — useful for call-centre agents who should handle one call at a time. This, too, is set per policy. ## Headset call control Answer, end and mute calls directly from supported Yealink, Poly (Plantronics) and Jabra headsets. --- # Presence buttons (BLF) and speed dials > Busy Lamp Field presence buttons and speed dials in the browser — see who is available, ringing or busy, and manage button profiles centrally for many users. URL: https://webrtcclient.com/features/presence-buttons-blf-speed-dials/ Busy Lamp Field (BLF) buttons and speed dials have long been essential on traditional VoIP desk phones. WebRTC Client brings them to the browser: administrators create button profiles once and assign them to many users, and the client subscribes to every button automatically — just like a desk phone. ## Set your own status Users can change their own status — for example to available or Do Not Disturb — so colleagues can see at a glance whether it's a good moment to call. Whether users may toggle Do Not Disturb is set with [policies](https://webrtcclient.com/guides/quick-start/policies/). ## What the colours mean | Colour | State | |---|---| | Green | Available / ready | | Orange | Ringing | | Red | Busy / on the phone | | Grey | Unavailable (not registered) | | Blue | Speed dial (no presence) | Click a presence button to call the colleague directly. Click a speed dial to dial an internal or external number. ## Key features - **Button profiles** — System administrators and company admins create profiles with BLF buttons and speed dials, tailored to a team or department. - **Assign to many users at once** — one profile can be used by an entire department. Change it once and everyone gets the update. - **User-level customisation** — users with the right [policy](https://webrtcclient.com/guides/quick-start/policies/) can add and edit their own buttons in the client. - **Central management** — add, remove and sort buttons from the management portal. - **Automatic subscription** — the client loads the buttons and subscribes to their state on login. No setup on the user's side. ## Getting started 1. Log in to the management portal. 2. Create a button profile and add BLF buttons and speed dials, just as you would on a SIP desk phone. 3. Assign the profile to one or more users. 4. If permitted, users can fine-tune their buttons in the client. For the detailed walkthrough, see the quick start step [Button profiles](https://webrtcclient.com/guides/quick-start/button-profiles/). --- # Web phonebook > Give every user a sorted, searchable phonebook in the browser client, fed by a simple two-column CSV file that you host and maintain centrally. URL: https://webrtcclient.com/features/web-phonebook/ Managing contacts is easy with the WebRTC Client web phonebook. Point the platform to a simple CSV file and every assigned user gets an alphabetically sorted, searchable contact list right next to the dialer. ## How it works The phonebook is based on a CSV file with two columns: ```csv Name,PhoneNumber Customer Service,+31881014520 Jane Doe,+31612345678 ``` Host the file at a URL that the platform can reach, add it as a phonebook in the management portal and assign it to users. Don't have a place to host the file? We can help. ## Key features - **CSV-based** — just two columns, `Name` and `PhoneNumber`. Export from almost any CRM or spreadsheet. - **Automatic sorting** — contacts are sorted A–Z with a quick-jump index. - **Search by name or number** — find the right contact in seconds. - **One source of truth** — a central file means everyone works with the same, up-to-date contacts. - **Secure** — contact data is only available to authenticated users of the tenant. ## Getting started 1. Prepare a CSV file with the columns `Name` and `PhoneNumber`. 2. Log in to the management portal. 3. Add a new phonebook and point it to the URL of your CSV file. 4. Assign the phonebook to one or more users. 5. Users now see the sorted, searchable list in the *Phonebook* tab of the client. **More to come:** A personal phonebook per user and phone-number search across phonebooks are on the [roadmap](https://webrtcclient.com/roadmap/). --- # Click-to-call Chrome extension > Click any tel link on a web page and the number is placed in the WebRTC Client dialer. A free, white-label Chrome extension that shares no data. URL: https://webrtcclient.com/features/click-to-call/ Stop copying phone numbers from websites. With the WebRTC Client Chrome extension (also known as *Click2Tel* or *Click2Call*), clicking a `tel:` link on any web page places the number directly in your browser dialer. ## Key features - **One click** — click a `tel:` link and the number is pasted into the dialer field. No copy-paste, no typos. - **Works with your account** — the extension hands the number to your open WebRTC Client tab. - **Quick installation** — add it from the Chrome Web Store and you're set. - **Private and secure** — the extension shares no data at all and has been reviewed and approved by Google. - **White-label** — available for branded deployments, too. ## How to use it 1. **Install the extension.** Open the Chrome Web Store, search for the Click2Tel extension and click *Add to Chrome*. 2. **Restart your browser.** Close all browser windows and start Chrome again so the extension is activated. 3. **Open your WebRTC Client dialer** in a tab and sign in. 4. **Click a `tel:` link** on any web page. A small pop-up briefly shows the number. 5. **Call.** The number is copied and pasted into the dialer field — press the call button. **Note:** The extension works in Google Chrome and other Chromium-based browsers that support Chrome Web Store extensions, such as Microsoft Edge. Read more about the background in [Click-to-call with tel: links](https://webrtcclient.com/blog/click-to-call-with-tel-links/). --- # Multi-tenant platform > A multi-tenant, multi-layered platform with System administrator, Reseller, Customer and User levels — each with its own scope, permissions and branding. URL: https://webrtcclient.com/features/multi-tenant/ WebRTC Client is a multi-tenant, multi-layered communication platform. System administrators, resellers, customers and users each work within their own scope in one flexible hierarchy — and every layer can carry its own [white-label branding](https://webrtcclient.com/features/white-label/). ## The four layers ### System administrator Full control over the platform: system configuration, reseller accounts and global settings. Keeps the environment secure and efficient for everyone. ### Reseller Sells and manages customer accounts. Creates customers, connects their PBX, manages licences and provides first-line support. ### Customer A company with its own dedicated environment: users, policies, button profiles and phonebooks — managed by the company admin if you allow it. ### User Signs in to the browser client with e-mail and password and gets their extension, buttons and phonebook automatically. ## Why it matters - **Scale without chaos** — onboard hundreds of customers with thousands of users from one portal. - **Delegated administration** — let resellers or company admins manage their own tenants, within the limits you set. - **Isolation** — every customer sees only their own users, settings and data. - **Licences per customer** — the portal tracks used versus available licences per customer. - **Consistent branding** — logo, colours, domain and e-mail sender per layer. ## How a tenant is set up Setting up a new customer takes five short steps in the management portal — see the [quick start manual](https://webrtcclient.com/guides/quick-start/). --- # White-label branding > Deliver WebRTC Client under your own brand — your logo, colours, domain name and notification e-mail addresses on every layer of the platform. URL: https://webrtcclient.com/features/white-label/ A strong brand is crucial in a competitive market. WebRTC Client is fully white-label: partners and service providers deliver the platform with their own logo, colours, domain name and e-mail addresses, so customers experience *your* product from first login to password reset. ## What you can brand - **Logo and colours** — personalise the client and the management portal with your logo and brand colours. - **Custom domain** — run the platform on your own (sub)domain, e.g. `phone.yourbrand.com`. - **Branded e-mail notifications** — enrolment and password-reset e-mails are sent from your own address. - **Per layer** — resellers and customers can each have their own branding in the [multi-tenant](https://webrtcclient.com/features/multi-tenant/) hierarchy. ## Benefits - **Trust** — users only see your brand, which builds confidence and reduces support questions. - **Consistency** — the same look and feel across web, e-mail and documentation. - **Scalable** — add brands as you add resellers or customer segments. ## Getting started 1. [Contact us](https://webrtcclient.com/contact/) to discuss your white-label requirements. 2. Provide your logo, brand colours, custom domain and the e-mail addresses for user notifications. 3. We configure the platform to match your brand identity. 4. Train your staff and users on the platform. 5. Enjoy a fully branded communication platform. --- # Solutions > WebRTC Client for businesses, partners and resellers, and service providers who want to run the platform themselves. URL: https://webrtcclient.com/solutions/ WebRTC Client is available in three ways, depending on your role in the telephony chain. - [WebRTC Client for business](https://webrtcclient.com/solutions/business/): Connect your existing phone system and start calling from the browser. Keep your PBX, telephony provider and desk phones — no software to install. - [WebRTC Client for partners](https://webrtcclient.com/solutions/partners/): Sell a browser-based VoIP solution under your own brand. Add customers and users in minutes with competitive per-seat pricing and no upfront investment. - [WebRTC Client for service providers](https://webrtcclient.com/solutions/service-providers/): Host the complete WebRTC Client platform in your own cloud. We provide the software; you run the platform, sell it under your brand and keep the recurring revenue. --- # WebRTC Client for business > Connect your existing phone system and start calling from the browser. Keep your PBX, telephony provider and desk phones — no software to install. URL: https://webrtcclient.com/solutions/business/ Easily connect your existing phone system and start dialing. WebRTC Client is designed for placing and receiving calls in your favourite web browser — Chrome, Edge, Firefox or Safari — without installing additional software. In a few steps you connect your Asterisk, FreePBX or other phone system and your team can call from the browser. ![The WebRTC Client webphone in dark mode on a desktop monitor in an office](https://webrtcclient.com/img/product/webphone-v3.png "Calling from the browser — at the office or at home.") ## Why businesses choose WebRTC Client ### Keep what you have Keep your existing PBX, telephony provider, desk phones and integrations. WebRTC Client simply adds a browser extension of your phone system. ### Quick to deploy Connect your PBX websocket, add users with their e-mail address and they are ready to call. No software rollout. ### Low cost, no upfront investment Low licensing cost per user and no hardware to buy. Ideal for remote workers and hybrid teams. ### User-friendly A clean interface with everything users expect from a desk phone — and nothing they need to configure. ## Perfect for - **Remote and hybrid teams** — call from home with the same extension, buttons and phonebook as in the office. - **Hot desks and flex workers** — sign in on any computer; settings follow the user. - **Reception and customer service** — BLF presence, transfers and a central phonebook at a glance. - **Companies leaving desktop softphones** — no installs, updates or local settings to support. [Read why](https://webrtcclient.com/blog/the-nightmare-of-desktop-softphones/). ## How to get started 1. Make sure your PBX has a secure websocket — see the [integration guides](https://webrtcclient.com/guides/). 2. Add your PBX server and users in the management portal — see the [quick start](https://webrtcclient.com/guides/quick-start/). 3. Users sign in with their e-mail address and start calling. ## Interested in WebRTC Client for your business? The new version with multiple lines and live AI transcription is available in early access. Contact us to get started. [Contact us](https://webrtcclient.com/contact/) --- # WebRTC Client for partners > Sell a browser-based VoIP solution under your own brand. Add customers and users in minutes with competitive per-seat pricing and no upfront investment. URL: https://webrtcclient.com/solutions/partners/ Start selling a browser-based VoIP solution under your own brand. Connect your customers' phone systems, add companies and users in minutes, and deliver a professional webphone — with low costs and minimal effort. No hardware or hosting needed: we run the platform, you own the customer relationship. ## What you get as a partner ### Your own brand Your logo, colours, domain and e-mail addresses — customers only see your brand. ### Multi-tenant portal Manage all your customers, their PBX connections and users from one reseller account. ### Pre-configured presence Prepare BLF buttons and speed dials per department before users even log in. ## Partner benefits - **Flexibility** — combine WebRTC Client with your existing hosted PBX, SIP trunking or managed-service offering. - **No upfront investment** — start with one customer and grow at your own pace. - **Competitive price per seat** — attractive margins and predictable recurring revenue. - **Quick and easy to deploy** — onboarding a customer takes minutes. - **Integrates with Asterisk, FreePBX, VitalPBX, MirtaPBX** and other [compatible systems](https://webrtcclient.com/compatibility/). - **Technical support from Europe** — from our team in the Netherlands. ## Become a partner Pricing for the new version is available on request. Contact us to discuss partnership and early access. [Contact us](https://webrtcclient.com/contact/) --- # WebRTC Client for service providers > Host the complete WebRTC Client platform in your own cloud. We provide the software; you run the platform, sell it under your brand and keep the recurring revenue. URL: https://webrtcclient.com/solutions/service-providers/ Start your own WebRTC platform and host it wherever you like. We provide the software; you run the platform at your premises or in your own cloud. Sell it to your partners and customers under your own brand and generate monthly recurring revenue — with low costs and minimal effort. ## Why service providers choose WebRTC Client ### Bring your own cloud Deploy on your own infrastructure or hardware, close to your PBX and SIP platform. You stay in control of data and availability. ### Sell to your partners The multi-tenant model lets your resellers manage their own customers under their own brands. ### Custom branding White-label on every layer: platform, resellers and customers. ### Flexible licensing Different licence types: pay-as-you-go or lifetime licences, per platform. ## At a glance - Sell to your partners and customers - Bring your own cloud or hardware - Quick and easy to deploy - [Multi-tenant](https://webrtcclient.com/features/multi-tenant/) and [white-label](https://webrtcclient.com/features/white-label/) - Technical support from Europe (the Netherlands) - Pay-as-you-go or lifetime licences ## Run WebRTC Client on your own platform Talk to us about platform licences and early access to the new version with live AI transcription, queues and voicebots. [Contact us](https://webrtcclient.com/contact/) --- # Integration and installation guides > Step-by-step guides to enable a secure websocket and WebRTC on Asterisk, FreePBX, VitalPBX, MirtaPBX and Issabel, plus the management portal quick start. URL: https://webrtcclient.com/guides/ Follow these guides to connect your phone system to WebRTC Client. In most cases you'll be up and running within an hour. ## How it fits together 1. **Prepare your PBX** — enable a secure websocket (WSS) and WebRTC on the extensions. Pick your system below. 2. **Set up the management portal** — create a customer, enter the websocket server, and add policies, button profiles and users. Follow the [quick start](https://webrtcclient.com/guides/quick-start/). 3. **Sign in** — users log in to the browser client with their e-mail address and start calling. ## Websocket setup per phone system ### Asterisk-based systems `http.conf`, `sip.conf` / PJSIP and `rtp.conf` for plain Asterisk installations. ### FreePBX Certificate Manager, extension settings and NAT for FreePBX 15 and later. ### VitalPBX Enable WebRTC on VitalPBX extensions and connect the websocket. ### MirtaPBX Extension security settings and optional API login without storing SIP credentials. ### Issabel HTTPS for the Asterisk mini-HTTP server and WebRTC extensions on Issabel PBX. ### Internal PBX with remote clients One hostname for office and home workers with split DNS. Also useful: [List of STUN servers](https://webrtcclient.com/guides/stun-servers/) · FreeSWITCH guide (coming) · Kamailio: see the [Kamailio documentation](https://www.kamailio.org/). ## Management portal - [Quick start manual](https://webrtcclient.com/guides/quick-start/) — onboard your first customer in five steps. ## WebRTC client - [Click-to-call Chrome extension](https://webrtcclient.com/features/click-to-call/) - [Frequently asked questions](https://webrtcclient.com/faq/) - User manual (coming soon) **Need help?:** Don't know where to start? You are not alone. We offer integration and installation services and can do the work for you — [contact us](https://webrtcclient.com/contact/). --- # Integration guide for Asterisk-based systems > Set up a secure websocket (WSS) for WebRTC on Asterisk with chan_sip or PJSIP — http.conf, sip.conf, rtp.conf, NAT, firewall and verification. URL: https://webrtcclient.com/guides/asterisk/ This guide enables a TLS websocket on a plain Asterisk server (chan_sip or PJSIP stack) so that WebRTC Client can register extensions from the browser. Using a distribution with a web interface? See the guides for [FreePBX](https://webrtcclient.com/guides/freepbx/), [VitalPBX](https://webrtcclient.com/guides/vitalpbx/), [MirtaPBX](https://webrtcclient.com/guides/mirtapbx/) or [Issabel](https://webrtcclient.com/guides/issabel/). ## Requirements - Asterisk 11 or later (Asterisk 16+ with PJSIP recommended) - A valid TLS certificate for the server's hostname — **not self-signed**, because browsers refuse websocket connections to untrusted certificates - Inbound TCP port `8089` open and forwarded to the Asterisk server - UDP RTP ports (default `10000–20000`) reachable for media ## Step 1 — Install the certificate Upload a valid certificate and private key to the server, for example to `/etc/ssl/certs/` and `/etc/ssl/private/`. A free Let's Encrypt certificate works fine. ## Step 2 — Enable the TLS web server Edit `/etc/asterisk/http.conf`: ```ini [general] enabled=no ; disable plain HTTP tlsenable=yes tlsbindaddr=0.0.0.0:8089 tlscertfile=/etc/ssl/certs/my.cert.pem tlsprivatekey=/etc/ssl/private/my.key.pem ``` ## Step 3 — Enable the websocket **chan_sip stack** — in `/etc/asterisk/sip.conf`: ```ini [general] websocket_enabled=yes ``` **PJSIP stack** — disable the chan_sip websocket in `/etc/asterisk/sip.conf` so that PJSIP can handle it, and make sure a websocket transport exists in `pjsip.conf`: ```ini ; sip.conf [general] websocket_enabled=no ; pjsip.conf [transport-wss] type=transport protocol=wss bind=0.0.0.0 ``` ## Step 4 — ICE and STUN Add to `/etc/asterisk/rtp.conf`: ```ini [general] icesupport=true stunaddr=stun.l.google.com:19302 ``` If the server is behind NAT, also map its private IP to its public IP: ```ini [ice_host_candidates] 192.168.1.100 => 12.12.12.12 ``` More public STUN servers are listed in [STUN servers](https://webrtcclient.com/guides/stun-servers/). ## Step 5 — Restart and verify Restart Asterisk and check that the websocket is listening: ```bash asterisk -rx 'http show status' ``` You should see the HTTPS server enabled and bound to `0.0.0.0:8089`, and the `/ws` URI listed: ![Output of http show status showing the HTTPS server bound to port 8089 and the /ws websocket URI](https://webrtcclient.com/img/guides/asterisk-http-show-status.png "http show status: HTTPS enabled on 0.0.0.0:8089 with the /ws websocket.") ## Step 6 — Configure WebRTC extensions For every extension that will be used with WebRTC Client, enable WebRTC and SRTP. For PJSIP endpoints, `webrtc=yes` sets the right defaults (AVPF, ICE, rtcp-mux, DTLS-SRTP): ```ini [1001] type=endpoint webrtc=yes transport=transport-wss context=from-internal disallow=all allow=opus,ulaw,alaw auth=1001 aors=1001 ``` For chan_sip peers, set `transport=wss`, `avpf=yes`, `icesupport=yes`, `encryption=yes`, `dtlsenable=yes` and the matching DTLS certificate options. ## Step 7 — Firewall Allow inbound TCP `8089` and your RTP range to the Asterisk machine, and forward them on your router if the server is behind NAT. ## Next steps Enter the websocket server (hostname), port `8089` and path `/ws` in the management portal — see [Configure server settings](https://webrtcclient.com/guides/quick-start/server-settings/). **We can do this for you:** Need help? We offer a websocket installation service for Asterisk. [Contact us](https://webrtcclient.com/contact/). --- # Integration guide for FreePBX > Enable WebRTC on FreePBX 15 and later — install a certificate, verify the websocket, configure extensions for DTLS-SRTP and set up NAT, STUN and ICE host candidates. URL: https://webrtcclient.com/guides/freepbx/ FreePBX supports WebRTC out of the box. This guide walks you through enabling the secure websocket, configuring extensions and handling NAT so that WebRTC Client can register from the browser. ## Requirements | Component | Minimum version | |---|---| | Asterisk | 11.5 | | Certificate Manager | 12.0.0alpha1 | | Core | 12.0.1beta9 | | User Control Panel | 12.0.0beta7 | | FreePBX | 12.0.1beta34 (tested on v15 and later) | ## Step 1 — Install a certificate for your domain Use a certificate for your domain — **not self-signed**. 1. In the top menu, click **Admin**. 2. Choose **Certificate Manager**. 3. No certificate yet? Generate a Certificate Signing Request (CSR) and apply for a certificate, or use the built-in Let's Encrypt option. 4. Already have one? Upload the certificate and click **Generate Certificate**. 5. Optionally set the certificate as the **default**. ![FreePBX Certificate Manager with an uploaded certificate](https://webrtcclient.com/img/guides/freepbx-certificate.png "FreePBX Certificate Manager: upload or generate the certificate for your domain.") ## Step 2 — Restart Asterisk and check the websocket Go to **Admin → Asterisk CLI** and run: ```text core restart now ``` Then check that the websocket is listening: ```text http show status ``` ![FreePBX Asterisk CLI output of http show status with HTTPS bound to port 8089](https://webrtcclient.com/img/guides/freepbx-http-status.png "The HTTPS server should be enabled and bound to port 8089.") ## Step 3 — Enable WebRTC on an extension 1. Click **Admin → Extensions** (in newer versions: **Applications → Extensions**). 2. Create or edit an extension. 3. On the **Advanced** tab, set: - Enable AVPF = **Yes** - Enable ICE Support = **Yes** - Enable rtcp Mux = **Yes** - Media Encryption = **DTLS-SRTP** 4. Save the extension and click **Apply Config**. ## Step 4 — Add the websocket server to the management portal Enter your domain, port `8089` and path `/ws` in the management portal — see [Configure server settings](https://webrtcclient.com/guides/quick-start/server-settings/). ## Step 5 — Firewall and port forwarding behind NAT If the PBX runs behind NAT, set up port forwarding and allow inbound traffic to the internal server. WebRTC media uses UDP ports (the RTP range, by default `10000–20000`). You also need a STUN server to make two-way audio possible. Example: FreePBX behind NAT on public IP `123.123.123.123` and private IP `10.10.10.231`. 1. Forward TCP port `8089` (and the RTP range) to `10.10.10.231` on your router. 2. Adjust the NAT settings under **Settings → Asterisk SIP Settings**: ![FreePBX SIP settings with external address and local networks](https://webrtcclient.com/img/guides/freepbx-nat-settings.png "Set the external address and local networks.") 3. Add a STUN server under **Settings → Asterisk SIP Settings**: ![FreePBX SIP settings with a STUN server configured](https://webrtcclient.com/img/guides/freepbx-stun-server.png "Configure a STUN server, e.g. stun.l.google.com:19302.") 4. Set up the ICE host candidate, mapping the private to the public address: `10.10.10.231 => 123.123.123.123` ![FreePBX ICE host candidates mapping the private IP to the public IP](https://webrtcclient.com/img/guides/freepbx-ice-host-candidates.png "ICE host candidate: private IP => public IP.") ## Internal domain name When users also work on the same network (behind the same WAN IP) as the PBX, create an internal DNS record pointing to the server so the traffic stays local — for example `webrtc.company.xyz A 10.10.10.231`. You can also use a DNS rewrite in Pi-hole or AdGuard. See [internal PBX with remote clients](https://webrtcclient.com/guides/internal-pbx-remote-clients/). --- # Integration guide for VitalPBX > Connect VitalPBX to WebRTC Client — enable WebRTC on extensions, make sure the secure websocket on port 8089 is reachable and add the server to the portal. URL: https://webrtcclient.com/guides/vitalpbx/ VitalPBX has built-in support for WebRTC clients. Follow the official VitalPBX article [Configuring VitalPBX for WebRTC clients](https://www.vitalpbx.org/blog/configuring-vitalpbx-for-webrtc-clients/) for the screens of your version. In short: ## Steps 1. **Install a valid certificate** for the hostname of your VitalPBX server (Let's Encrypt is supported in VitalPBX). 2. **Make sure the secure websocket is enabled** and that TCP port `8089` is allowed in the VitalPBX firewall and forwarded to the server. 3. **Enable WebRTC on the extension's device** — use a WebRTC-capable technology profile so that AVPF, ICE, rtcp-mux and DTLS-SRTP are enabled. 4. **Behind NAT?** Configure the external address, local networks and a [STUN server](https://webrtcclient.com/guides/stun-servers/), and open the RTP port range. 5. **Add the server in the management portal** — hostname, port `8089` and path `/ws`. See [Configure server settings](https://webrtcclient.com/guides/quick-start/server-settings/). **Note:** Menu names differ slightly between VitalPBX versions. If something does not match, the official VitalPBX article is leading — or [contact us](https://webrtcclient.com/contact/) for help. --- # Integration guide for MirtaPBX > Configure MirtaPBX extensions for WebRTC and optionally let WebRTC Client authenticate users via the MirtaPBX API, so SIP credentials are never stored. URL: https://webrtcclient.com/guides/mirtapbx/ ![MirtaPBX logo](https://webrtcclient.com/img/logos/mirtapbx-large.png) Before you start, first follow the [Asterisk guide](https://webrtcclient.com/guides/asterisk/) to set up the websocket on the MirtaPBX server. Then continue below. ## Configure the extensions For each extension, set the following in the **Security** section: - WebRTC Support: **Yes** - RTP Encryption (SRTP): **Yes** ![MirtaPBX extension security settings with WebRTC support and SRTP enabled](https://webrtcclient.com/img/guides/mirtapbx-extension-webrtc.png "MirtaPBX extension: enable WebRTC support and SRTP.") Users can now log in to WebRTC Client. ## Optional: login via the MirtaPBX API WebRTC Client can also talk to the MirtaPBX API. This saves time and removes the need to share or store SIP credentials in the WebRTC Client platform. When a user logs in, the `GETWEBRTCAUTH` API request retrieves the SIP username and password, and WebRTC Client uses them to set up the websocket connection to the PBX. **Important:** With API login, the *forgot password* feature of WebRTC Client does not work, because the password is managed in MirtaPBX. ### In MirtaPBX 1. Create an extension and enable **WebRTC support** and **SRTP** (see above). 2. Enter a **Web User** (an e-mail address) and **password**. These become the user's login credentials for WebRTC Client. ![MirtaPBX web user with e-mail address and password](https://webrtcclient.com/img/guides/mirtapbx-web-user.png "The MirtaPBX Web User (e-mail) and password are used to log in.") ### In the WebRTC Client management portal 1. Open the customer and go to the **PBX server settings**. 2. Select **Authenticate users using the API**. 3. Enter the MirtaPBX API details (API URL and credentials) and save. The newly created user can now log in to WebRTC Client with the MirtaPBX web-user credentials. --- # Integration guide for Issabel > Enable HTTPS and the websocket on Issabel PBX, configure WebRTC extensions and set up ICE and STUN when the server is behind NAT. URL: https://webrtcclient.com/guides/issabel/ Issabel PBX supports websockets and WebRTC. In a few steps you can connect WebRTC Client to Issabel. ## Requirements - Asterisk 11 or later - A valid TLS certificate - TCP port `8089` open and forwarded to your Issabel server ## Step 1 — Enable HTTPS for Issabel Open **Security → Advanced Settings**, set **Enable direct access** to **On** and click **Save**. ![Issabel advanced settings with direct access enabled](https://webrtcclient.com/img/guides/issabel-direct-access.png "Security → Advanced Settings: enable direct access.") Then open **PBX → PBX Configuration → Option → Unembedded IssabelPBX**. ![Issabel menu showing the Unembedded IssabelPBX option](https://webrtcclient.com/img/guides/issabel-unembedded.png) Under **Advanced Settings**, select your certificate and set the HTTPS options as shown below. ![Issabel HTTPS settings with HTTPS enabled, bind address 0.0.0.0:8089 and certificate paths](https://webrtcclient.com/img/guides/issabel-https-settings.png "Enable HTTPS, bind to 0.0.0.0:8089 and select your certificate and private key.") ### HTTPS options missing? If you don't see the HTTPS options, add them to the database manually. Adjust the values where needed — at your own responsibility: ```bash mysql -u root -p asterisk -e "INSERT INTO issabelpbx_settings VALUES \ ('HTTPSBINDADDRESS','0.0.0.0:8089','HTTPS Bind Address/Port',2,'Address and port to bind to for HTTPS. Default is 127.0.0.1:8089','text','','127.0.0.1:8089',0,0,'Asterisk Builtin mini-HTTP server','',0,0), \ ('HTTPSCERTFILE','/etc/asterisk/keys/cert.pem','Certificate file',2,'Full path to certificate file for HTTPS.','text','','/var/lib/asterisk/keys/localhost.crt',0,0,'Asterisk Builtin mini-HTTP server','',0,0), \ ('HTTPSENABLED','1','Enable HTTPS support for the mini-HTTP Server',1,'Whether to enable HTTPS support for the Asterisk HTTP interface. Default is no.','bool','','0',0,0,'Asterisk Builtin mini-HTTP server','',0,0), \ ('HTTPSPRIVATEKEY','/etc/asterisk/keys/priv.pem','Private key file',2,'Full path to private key file for HTTPS. If empty, default is to look into certificate file for private key.','text','','/var/lib/asterisk/keys/localhost.key',0,0,'Asterisk Builtin mini-HTTP server','',1,0);" ``` ## Step 2 — Configure an extension with WebRTC support Use dedicated extensions for WebRTC. Open **PBX → PBX Configuration → Extensions**, select the extension and make sure the WebRTC values (transport, AVPF, ICE support, encryption) are set as shown: ![Issabel extension settings for WebRTC](https://webrtcclient.com/img/guides/issabel-extension-webrtc.png "Issabel extension settings for WebRTC.") ## Step 3 — Behind NAT? If your PBX is behind NAT, enable ICE and set a [STUN server](https://webrtcclient.com/guides/stun-servers/). Edit `/etc/asterisk/rtp_custom.conf`: ```ini icesupport=true stunaddr=stun.stunprotocol.org:3478 ``` ## Step 4 — Map the extensions Log in to the management portal, enter the WebRTC (websocket) settings and map the extensions to users. See the [quick start](https://webrtcclient.com/guides/quick-start/). --- # Internal PBX server with remote clients > Let office users and remote workers connect to an on-premises PBX with the same hostname, using a public DNS record, port forwarding and an internal DNS override. URL: https://webrtcclient.com/guides/internal-pbx-remote-clients/ A common setup: the company runs a PBX in the office, while some employees work from home or on the road. With one hostname and *split DNS*, both groups connect to the same PBX — office users over the LAN, remote users over the internet. ## Setup 1. **Create a public hostname** pointing to the office's public IP address, e.g. `webclient.company.com A 123.123.123.123`. 2. **Get a TLS certificate** for that (sub)domain and install it on the PBX. 3. **Forward the websocket port** on the router to the PBX, e.g. `123.123.123.123:8089 → 192.168.1.100:8089` (plus the RTP range for media). 4. **Add an internal DNS record** for the same name pointing to the private IP, e.g. `webclient.company.com → 192.168.1.100`. ## How it works | Where the user is | DNS answer | Connection | |---|---|---| | Outside the office | `123.123.123.123` (public) | Via the internet and the port forward | | In the office | `192.168.1.100` (private) | Directly over the LAN | Because the hostname is the same, the certificate is valid in both cases and users don't have to change anything. **Important:** Office computers must use the router's (or your internal) DNS servers. If they use a public DNS resolver such as 8.8.8.8, they receive the public IP instead. Tip: you can also create the internal record with a DNS rewrite in Pi-hole or AdGuard. --- # List of STUN servers > Why WebRTC needs a STUN server when the PBX is behind NAT, how to configure one in Asterisk, and a list of public STUN servers. URL: https://webrtcclient.com/guides/stun-servers/ To receive audio when your phone system is behind NAT, you will most likely need a STUN server. The PBX asks the STUN server for its public IP address and port, and uses that information in the media negotiation (ICE) so that the browser can send audio to the right address. ## Configuring STUN in Asterisk In `/etc/asterisk/rtp.conf` (or `rtp_custom.conf` on FreePBX/Issabel): ```ini [general] icesupport=true stunaddr=stun.l.google.com:19302 ``` ## Commonly used public STUN servers | Server | Port | |---|---| | `stun.l.google.com` | 19302 | | `stun1.l.google.com` | 19302 | | `stun.stunprotocol.org` | 3478 | | `stun.cloudflare.com` | 3478 | A longer, community-maintained list of public STUN servers is available [here](https://gist.github.com/mondain/b0ec1cf5f60ae726202e). **Note:** STUN helps in most NAT situations. Behind very strict (symmetric) NAT or firewalls, a TURN server may be required to relay the media. --- # Quick start manual > Onboard your first customer in the WebRTC Client management portal in five steps — customer, server settings, policies, button profiles and users. URL: https://webrtcclient.com/guides/quick-start/ When the secure websocket on your PBX is up and running (see the [integration guides](https://webrtcclient.com/guides/)), you can enrol customers in the management portal. Follow the steps in order: - [Step 1: Creating a customer](https://webrtcclient.com/guides/quick-start/creating-a-customer/): Create a new customer (tenant) in the WebRTC Client management portal. - [Step 2: Configure server settings](https://webrtcclient.com/guides/quick-start/server-settings/): Enter the PBX websocket server, port, path and user-agent name for a customer in the WebRTC Client management portal. - [Step 3: Policies](https://webrtcclient.com/guides/quick-start/policies/): Use policies to allow or restrict WebRTC Client features such as call waiting, Do Not Disturb and button editing per group of users. - [Step 4: Button profiles](https://webrtcclient.com/guides/quick-start/button-profiles/): Create button profiles with BLF presence buttons and speed dials and assign them to users or departments in the WebRTC Client management portal. - [Step 5: Adding users](https://webrtcclient.com/guides/quick-start/adding-users/): Add users in the WebRTC Client management portal and map their PBX extension to an e-mail address so they can log in to the browser client. ## Before you begin - A working WSS websocket on the PBX — check with `http show status` on Asterisk-based systems. - SIP credentials (auth name, username, password) of the extensions you want to use. - The e-mail addresses of the users. - Access to the management portal as a system administrator or reseller. --- # Step 1: Creating a customer > Create a new customer (tenant) in the WebRTC Client management portal. URL: https://webrtcclient.com/guides/quick-start/creating-a-customer/ A customer is a company with its own users, PBX connection, policies, button profiles and phonebooks. 1. Log in to the management portal. 2. Go to **Customer** and click **Add customer**. 3. Fill in the required fields (marked with `*`), such as the customer name, an optional reference and the number of user licences. 4. Click **Submit**. The new customer appears in the customer list, with its status and the number of used versus available licences. **Next:** [Step 2: Configure server settings →](https://webrtcclient.com/guides/quick-start/server-settings/) --- # Step 2: Configure server settings > Enter the PBX websocket server, port, path and user-agent name for a customer in the WebRTC Client management portal. URL: https://webrtcclient.com/guides/quick-start/server-settings/ Tell WebRTC Client where the customer's PBX websocket can be reached. 1. Open the customer. 2. Click **Server settings**. 3. Enter the details of the PBX server (see the table below). 4. Click **Update**. ## Fields | Field | Example | Description | |---|---|---| | Websocket server | `client.yourdomain.com` | Hostname of the PBX. Must match the TLS certificate. | | Websocket port | `8089` | The TLS port of the Asterisk HTTP server. | | Websocket path | `/ws` | The websocket path on the PBX. | | User-agent name | `Your Webphone name` | The SIP user agent shown on the PBX, e.g. in `pjsip show contacts`. | **MirtaPBX:** For MirtaPBX you can choose **Authenticate users using the API** here, so SIP credentials don't need to be stored. See the [MirtaPBX guide](https://webrtcclient.com/guides/mirtapbx/). **Next:** [Step 3: Policies →](https://webrtcclient.com/guides/quick-start/policies/) --- # Step 3: Policies > Use policies to allow or restrict WebRTC Client features such as call waiting, Do Not Disturb and button editing per group of users. URL: https://webrtcclient.com/guides/quick-start/policies/ Policies allow or restrict users from using certain features. You can create multiple policies per company and assign each user to one policy. For example, a manager may edit buttons and use DND, while a call-centre agent may not. ## Available policy options | Option | When enabled | When disabled | |---|---|---| | **Call waiting** | The user can receive a second call while on a call. | Only one call at a time; a second incoming call is declined with *busy*. | | **DND** | The user can switch Do Not Disturb on and off in the client. While DND is on, the user receives no calls. | The DND toggle is not available. | | **EDIT** | The user can add and edit buttons in the client. | Buttons are managed by administrators only. | ## Adding a policy 1. Open the customer. 2. Click **Policy**. 3. Click **Add policy**. 4. Enter a policy name and check the options you want to allow. 5. Click **Submit**. **Next:** [Step 4: Button profiles →](https://webrtcclient.com/guides/quick-start/button-profiles/) --- # Step 4: Button profiles > Create button profiles with BLF presence buttons and speed dials and assign them to users or departments in the WebRTC Client management portal. URL: https://webrtcclient.com/guides/quick-start/button-profiles/ Just like on a traditional VoIP desk phone, you can add buttons to the client: **speed dials** and **BLF** (Busy Lamp Field) buttons. When users log in, they see the state of each extension — unavailable, available, busy or ringing — and can click a speed dial to dial. You can create multiple button profiles per company and assign each user to one. For example, create a profile per department and assign it to the users in that department. ## Adding a button profile 1. Open the customer. 2. Click **Button profile**. 3. Click **Add button profile**. 4. Enter a profile name and add buttons with the **+** icon. 5. For each button, choose the type: - **BLF** — subscribe to an internal extension to show its presence, e.g. label *Michael*, extension `1002`. - **Speed dial** — dial a number with one click, e.g. label *Customer Service*, number `+31881014520`. 6. Click **Submit**. Read more about [presence buttons and speed dials](https://webrtcclient.com/features/presence-buttons-blf-speed-dials/). **Next:** [Step 5: Adding users →](https://webrtcclient.com/guides/quick-start/adding-users/) --- # Step 5: Adding users > Add users in the WebRTC Client management portal and map their PBX extension to an e-mail address so they can log in to the browser client. URL: https://webrtcclient.com/guides/quick-start/adding-users/ A user maps a PBX extension to an e-mail address. Users log in with their e-mail address and password and are registered to their extension automatically — with all features ready to use. 1. Open the customer. 2. Click **Add user**. 3. Enter the user's information: - E-mail address and password - SIP settings: auth name, username and password (use the credentials from your PBX) - Language - Button profile (template) - Policy - Optional: check **This user has permissions to manage all the settings in the tenant** and set a password to give the user access to the management portal as company admin. 4. Click **Submit**. The user receives an e-mail with the login details and a link to log in. That's it — your first customer is live. Users can now sign in to the browser client and start calling. Problems? See the [FAQ](https://webrtcclient.com/faq/) or [contact us](https://webrtcclient.com/contact/). --- # Blog > Articles about WebRTC, browser-based calling, Asterisk softphones, desktop softphone pitfalls and what's coming next for WebRTC Client. URL: https://webrtcclient.com/blog/ Background articles about WebRTC and browser-based telephony, practical guides, and news about WebRTC Client. - [New in WebRTC Client: multiple lines and live AI transcription](https://webrtcclient.com/blog/new-multiple-lines-and-live-transcription/) (2026-11-18): The new WebRTC Client adds multiple lines, live AI transcription, an AI assistant, voicebot monitoring and a queue overview — all in the browser. - [A browser-based alternative to desktop softphones like Bria](https://webrtcclient.com/blog/alternative-to-desktop-softphones/) (2023-05-16): Compare the practical considerations of a browser softphone and a desktop application such as Bria. - [Click to call with tel links in Chrome](https://webrtcclient.com/blog/click-to-call-with-tel-links/) (2023-04-21): Use the Click2Tel Chrome extension to send phone numbers from tel links to your WebRTC Client dialer. - [What is a WebRTC Asterisk client?](https://webrtcclient.com/blog/webrtc-asterisk-client/) (2023-04-21): Learn how a WebRTC client registers with Asterisk and brings business calling to a browser. - [WebRTC Asterisk softphone for browser calling](https://webrtcclient.com/blog/webrtc-asterisk-softphone/) (2023-04-21): Connect a browser-based WebRTC softphone to Asterisk for business calls from a compatible browser. - [How to use WebRTC dialing in the browser](https://webrtcclient.com/blog/webrtc-dialing-in-the-browser/) (2023-04-21): Follow a practical checklist to connect a browser dialer to a PBX and test incoming and outgoing calls. - [What is WebRTC?](https://webrtcclient.com/blog/what-is-webrtc/) (2021-09-08): Learn what WebRTC does and how a browser-based softphone connects it to a PBX for business calling. - [The nightmare of desktop softphones](https://webrtcclient.com/blog/the-nightmare-of-desktop-softphones/) (2021-09-07): Seven common desktop softphone support problems and how central management can help. - [Why use WebRTC for business calling?](https://webrtcclient.com/blog/why-webrtc/) (2021-09-07): Explore why a WebRTC softphone can make browser calling and PBX administration more convenient. --- # The nightmare of desktop softphones > Seven common desktop softphone support problems and how central management can help. URL: https://webrtcclient.com/blog/the-nightmare-of-desktop-softphones/ | Published: 2021-09-07 ![The WebRTC Client webphone in dark mode on a desktop monitor in an office](https://webrtcclient.com/img/product/webphone-v3.png) Desktop softphones can create recurring support work when each user must install, configure and maintain an application. Seven common problems range from incorrect SIP credentials to unexpected changes in licensing. ## 1. First-time configuration A new user may face a screen full of unfamiliar settings. Even when only a SIP username, password and server are needed, identifying the right fields can lead to a support call or remote assistance. ## 2. Incorrect registration details A copied space, line break or mistyped password can prevent registration. Repeated failed attempts may trigger a PBX security tool such as Fail2ban. If an office shares a public IP address, a resulting block can affect other users too. ## 3. User and device administration Supplying credentials and helping users across Windows, macOS and Linux devices takes time. At scale, forgotten passwords, replacement computers and reinstalls can turn small tasks into a steady stream of requests. ## 4. Locally stored settings and data Some desktop applications keep contacts, call history or presence settings on the computer. A crash or reinstall can lead to an uncomfortable conversation: > User: Are all my contacts gone? > Support: Yes. Did you make a backup? > User: I thought the phone system ran in the cloud. > Support: It does, but your softphone and contacts were stored locally. > User: What about my call history? The answer depends on where each application stores its data and whether it was backed up. ## 5. Trial and usage limits A product that appears free may have a trial period, calling limits or terms limited to personal use. Discovering a restriction after deployment can interrupt a team's workflow. ## 6. Updates and licenses Users may need help deciding when to update. An update can also change system requirements or licensing, leaving administrators to assess compatibility and explain the change. ## 7. Recommendations can become support obligations Even when a provider only recommends a free application, customers may return to that provider if its business model changes. A recommendation can create expectations of ongoing help that were never agreed. ## How central management helps WebRTC Client provides a browser dialer and a [multi-tenant management portal](https://webrtcclient.com/features/multi-tenant/). Central administration can reduce individual setup and credential handling for problems 1 and 2, and organize users across customers for problem 3. A [web phonebook](https://webrtcclient.com/features/web-phonebook/) and centrally managed configuration reduce reliance on a single computer for problem 4; administrators should still verify storage and backup arrangements for each kind of data. For problems 5–7, managing a chosen service centrally makes it easier to review its terms, coordinate changes and set support expectations. It cannot prevent every licensing or update change, but it gives the provider a clearer place to manage the service. ## Key takeaways - Initial setup and incorrect credentials can generate support calls and registration blocks. - Local data and distributed devices complicate recovery and administration. - Trial terms, updates and recommendations can create unexpected obligations. - Browser access and central management can reduce several of these burdens. --- # Why use WebRTC for business calling? > Explore why a WebRTC softphone can make browser calling and PBX administration more convenient. URL: https://webrtcclient.com/blog/why-webrtc/ | Published: 2021-09-07 ![WebRTC Client panels: an active call with transcription and assistant toggles, live voicebot calls with transcript, and call queues](https://webrtcclient.com/img/product/webphone-panels.jpg) WebRTC makes real-time communication possible in compatible browsers. With a browser softphone and a properly configured PBX, it gives teams a way to make and receive business calls without installing a separate desktop phone application. ## A familiar place to work A browser-based dialer places calling alongside the web applications people already use. Users need a supported browser, network access and a microphone and speaker or headset. They must also grant microphone permission when prompted. The PBX and client still need to be configured before calling can begin. WebRTC Client connects to an existing compatible phone system using SIP over WebSocket. That means a business can use its PBX for extension registration and call routing while providing a browser interface to its users. See the [compatibility overview](https://webrtcclient.com/compatibility/) for supported systems, including Asterisk, FreePBX and VitalPBX. ## Calling features around WebRTC WebRTC itself supplies communication capabilities; the application adds the tools a team uses. WebRTC Client includes a web phonebook, presence buttons and speed dials, and a Chrome extension for dialing from `tel:` links. These features can reduce the need to switch between tools or retype numbers. Read more about [call features](https://webrtcclient.com/features/call-features/) and [click-to-call](https://webrtcclient.com/features/click-to-call/). ## Administration for multiple customers For providers and resellers, managing users across separate customer organizations can be as important as the dialer. The management portal organizes access through system administrator, reseller, customer and user levels. White-label branding and policies offer further ways to tailor the service to customers. A browser approach does not remove the need to check PBX settings, network connectivity or audio devices. It does provide a common interface for users and a central place to manage the service. The next generation of WebRTC Client is in development, with more to come. ## Key takeaways - WebRTC enables real-time communication in compatible browsers. - A browser softphone connects users to a suitably configured PBX. - Calling tools and central management extend the basic browser connection. - Audio permissions, network access and PBX setup still matter. --- # What is WebRTC? > Learn what WebRTC does and how a browser-based softphone connects it to a PBX for business calling. URL: https://webrtcclient.com/blog/what-is-webrtc/ | Published: 2021-09-08 ![The WebRTC Client webphone in dark mode on a desktop monitor in an office](https://webrtcclient.com/img/product/webphone-v3.png) WebRTC stands for Web Real-Time Communication. It is a collection of open web technologies that lets applications exchange real-time media and data through compatible browsers; a softphone can use it to carry voice calls. ## What WebRTC provides WebRTC gives web applications tools for real-time audio, video and data exchange without requiring a separate browser plugin. It is supported by modern browsers, although the experience and available capabilities depend on the browser and application. Applications built on WebRTC can support uses such as voice conversations, video meetings or collaborative tools. WebRTC is a technology, not a complete phone system. An application still needs a way to arrange a connection, manage users and provide a usable interface. For business telephony, it also needs to connect to a PBX or a VoIP service that can handle extensions and route calls. ## How WebRTC works with a PBX A browser softphone brings WebRTC and VoIP together. WebRTC Client uses WebRTC for browser audio and SIP over WebSocket to communicate with an existing compatible PBX. The PBX handles its configured extensions and call routing, while the browser presents the dialer to the user. An administrator must configure the PBX and connection correctly. Users also need a suitable browser, a network connection and an audio device. The browser will ask for microphone permission; users may also need to select the right microphone and speaker or headset. See the [compatibility overview](https://webrtcclient.com/compatibility/) for supported PBX platforms and the [quick-start guide](https://webrtcclient.com/guides/quick-start/) for a starting point. ## Beyond a browser dialer A business phone needs more than a way to enter a number. WebRTC Client also offers presence buttons and speed dials, a web phonebook, click-to-call and management tools. These features bring everyday calling tasks into the browser while the existing PBX continues to provide the phone system. The management portal supports a hierarchy from system administrator through reseller and customer to user. This can help service providers organize access and administration across customers. Explore the [features](https://webrtcclient.com/features/) to see the broader set of tools. ## Key takeaways - WebRTC enables real-time media and data in compatible browsers. - A softphone combines WebRTC with signaling and a PBX to provide calling. - Users need a working audio device and browser microphone permission. - WebRTC Client adds business calling and management features around the connection. --- # Click to call with tel links in Chrome > Use the Click2Tel Chrome extension to send phone numbers from tel links to your WebRTC Client dialer. URL: https://webrtcclient.com/blog/click-to-call-with-tel-links/ | Published: 2023-04-21 A `tel:` link is a phone-number link on a web page. The Click2Tel Chrome extension can copy its number into the WebRTC Client dialer, saving users from retyping it before placing a call. ## What you need Use Google Chrome with the Click2Tel extension, an open WebRTC Client dialer and an account connected to a working PBX extension. Your browser also needs access to a microphone and a suitable speaker or headset. Your administrator can help if the dialer is not registered or calling is unavailable. A link must actually use the `tel:` scheme for this workflow. A phone number displayed as ordinary text is not necessarily a clickable telephone link. A typical link target looks like `tel:+31123456789`. ## Set up Click2Tel 1. In the Chrome Web Store, search for the Click2Tel extension and select **Add to Chrome**. 2. Close all open browser windows and restart Chrome to activate the extension. 3. Open WebRTC Client and sign in to the dialer. 4. Find a `tel:` link on a web page and click it. A small popup displays the number. 5. The extension copies the number to the clipboard and pastes it into the dialer input field. Check the number and place the call from the dialer. The link transfers a number into the calling workflow; it does not replace the PBX or guarantee that a destination can be reached. Dialing permissions and routing remain subject to your phone system's configuration. ## Why use telephone links? Clicking a link avoids copying or retyping a number and can reduce dialing mistakes. It can also make the workflow easier for someone who has difficulty entering numbers manually. A useful link displays a recognizable number and uses a complete dialing format appropriate for its audience. If the number does not reach the dialer, check that the extension is enabled, Chrome has been restarted, the dialer is open and the link uses `tel:`. Then check your extension's registration and audio settings before trying a test call. See [click-to-call features](https://webrtcclient.com/features/click-to-call/) and the [quick-start guide](https://webrtcclient.com/guides/quick-start/) for related setup information. ## Key takeaways - A `tel:` link identifies a phone number for a calling application. - Click2Tel copies the linked number into the open WebRTC Client dialer. - Check the number and place the call using your configured PBX extension. - The extension requires Chrome and a working browser dialer. --- # How to use WebRTC dialing in the browser > Follow a practical checklist to connect a browser dialer to a PBX and test incoming and outgoing calls. URL: https://webrtcclient.com/blog/webrtc-dialing-in-the-browser/ | Published: 2023-04-21 ![The WebRTC Client webphone in dark mode on a desktop monitor in an office](https://webrtcclient.com/img/product/webphone-v3.png) WebRTC dialing lets you make and receive phone calls in a compatible browser when a browser softphone is connected to a suitably configured PBX. Start with a working extension, configure the connection, allow microphone access and test calls in both directions. ## Gather what you need Before setup, have the following available: - A compatible browser and a reliable network connection. - A PBX or VoIP service configured for WebRTC and SIP over WebSocket. - The extension and connection details supplied by your administrator. - A microphone and speaker, or a headset. - Access to WebRTC Client and permission to use the intended extension. The PBX still controls routing and calling permissions. A browser dialer alone does not provide a phone number or an outside line. ## Configure the PBX and client 1. Ask the PBX administrator to prepare an extension and the WebRTC connection. Confirm the signaling endpoint, credentials and any network requirements. 2. Configure the user and PBX connection in WebRTC Client. Keep credentials protected and use the details supplied for that extension. 3. Open the dialer in a compatible browser and sign in. Allow microphone access when the browser asks. 4. Select the appropriate microphone and speaker or headset in the available audio settings. 5. Confirm that the extension is registered before placing a call. The [quick-start guide](https://webrtcclient.com/guides/quick-start/) is a useful starting point. PBX-specific instructions are available in the [guides](https://webrtcclient.com/guides/), including Asterisk and other supported systems. ## Make and receive a test call Enter a number allowed by your PBX dial plan and start a call. Confirm that the other person can hear you and that you can hear them. Then call your extension from another phone and answer in the browser. Test any transfer or hold workflow your team needs as well. If registration fails, check the server address, credentials and WebSocket configuration. If a call connects without audio, check browser microphone permission, device selection and network settings. Firewalls and network address translation can affect media; the [STUN server guide](https://webrtcclient.com/guides/stun-servers/) offers related guidance. ## Make dialing easier Once calling works, a web phonebook and presence buttons can help users find contacts. The Chrome click-to-call extension can send a `tel:` link's number to the dialer, reducing manual entry. Keep the PBX and browser configuration documented so support staff can repeat the setup for new users. ## Key takeaways - A configured PBX and WebSocket connection are required for browser dialing. - Grant microphone access and select the correct audio devices. - Test incoming and outgoing calls and audio in both directions. - Check registration and media settings separately when troubleshooting. --- # WebRTC Asterisk softphone for browser calling > Connect a browser-based WebRTC softphone to Asterisk for business calls from a compatible browser. URL: https://webrtcclient.com/blog/webrtc-asterisk-softphone/ | Published: 2023-04-21 ![WebRTC Client panels: an active call with transcription and assistant toggles, live voicebot calls with transcript, and call queues](https://webrtcclient.com/img/product/webphone-panels.jpg) 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](https://webrtcclient.com/guides/asterisk/) for configuration guidance and the [compatibility overview](https://webrtcclient.com/compatibility/) 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](https://webrtcclient.com/guides/stun-servers/) 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. --- # What is a WebRTC Asterisk client? > Learn how a WebRTC client registers with Asterisk and brings business calling to a browser. URL: https://webrtcclient.com/blog/webrtc-asterisk-client/ | Published: 2023-04-21 ![The WebRTC Client webphone in dark mode on a desktop monitor in an office](https://webrtcclient.com/img/product/webphone-v3.png) 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](https://webrtcclient.com/guides/asterisk/) 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](https://webrtcclient.com/features/presence-buttons-blf-speed-dials/) and the [web phonebook](https://webrtcclient.com/features/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](https://webrtcclient.com/guides/stun-servers/) 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. --- # A browser-based alternative to desktop softphones like Bria > Compare the practical considerations of a browser softphone and a desktop application such as Bria. URL: https://webrtcclient.com/blog/alternative-to-desktop-softphones/ | Published: 2023-05-16 ![The WebRTC Client webphone in dark mode on a desktop monitor in an office](https://webrtcclient.com/img/product/webphone-v3.png) WebRTC Client is a browser-based softphone for organizations looking for an alternative to desktop applications such as Bria. It connects to a compatible existing PBX and adds a central portal for managing customers and users. ## Browser or desktop application? Bria is a desktop softphone option. A desktop application and a browser softphone can both provide a way to use a phone system from a computer, but their deployment and administration models differ. The right choice depends on the features, operating systems, support arrangements and terms an organization needs. WebRTC Client runs its dialer in a compatible browser, so users do not need a separate desktop softphone application for the calling interface. They do need network access, an audio device, microphone permission and a correctly configured PBX connection. Browser settings and network conditions still affect the experience. ## Keep an existing PBX WebRTC Client uses SIP over WebSocket to connect to compatible PBX systems. The PBX continues to handle its configured extensions and routing; the client provides the browser interface for calling. Supported platforms include Asterisk, FreePBX, VitalPBX, MirtaPBX, Issabel, Kamailio and FreeSWITCH. Review the [compatibility information](https://webrtcclient.com/compatibility/) and confirm the configuration needed for your system. ## Tools for everyday calls A browser dialer can bring common tasks into the same workspace. WebRTC Client offers presence buttons and speed dials, a web phonebook with CSV support, and a Chrome extension that sends `tel:` link numbers to the dialer. Yealink, Poly and Jabra headset call control is also supported. The [call features](https://webrtcclient.com/features/call-features/) page describes more of the calling workflow. ## Administration across customers The portal organizes administration from system administrator to reseller, customer and user. Providers can use policies and white-label branding as part of their service. This can be useful when supporting several customer organizations and their users; see [multi-tenant management](https://webrtcclient.com/features/multi-tenant/) for details. Before choosing any softphone, test a representative extension, audio device and network. Compare the features and support terms that matter to your team, and check how users and settings will be managed over time. The next generation of WebRTC Client is in development, with more to come. ## Key takeaways - WebRTC Client provides a browser-based alternative to a desktop softphone. - A compatible, correctly configured PBX remains responsible for its extensions and routing. - Presence, phonebook and click-to-call tools support everyday work. - Evaluate deployment, features and support against your own requirements. --- # New in WebRTC Client: multiple lines and live AI transcription > The new WebRTC Client adds multiple lines, live AI transcription, an AI assistant, voicebot monitoring and a queue overview — all in the browser. URL: https://webrtcclient.com/blog/new-multiple-lines-and-live-transcription/ | Published: 2026-11-18 ![A live transcript of a phone call shown in the WebRTC Client](https://webrtcclient.com/img/product/live-transcript.png) The new version of WebRTC Client brings multiple lines, live AI transcription and a clear overview of queues and voicebots to the browser. Calling without desk phones or installations was already possible; now you also see — and read — what's happening on every call. ## Multiple lines Take a second call while you're on the phone and switch between conversations. Every call gets its own card in the calls panel with hold, mute, transfer, keypad and hang-up — and its own AI toggles. [More about multiple lines](https://webrtcclient.com/features/multiple-lines/). ## Live AI transcription Switch on *Transcription* for a call and the conversation appears as text while you talk, with both sides labelled and timestamped. You always know what was discussed, without taking notes. Transcription is optional and administrators control it per tenant with policies. [More about live transcription](https://webrtcclient.com/features/ai-transcription/). ## AI assistant and live assist Next to transcription, each call card has toggles for the *Assistant* and *Live assist*, so AI can support you during the conversation. ## Voicebots under control When an AI voicebot answers your callers, the *Voicebots* panel shows each live conversation with its transcript. Listen in, transfer the caller, take the call over yourself, end it — or type a sentence for the bot to say. [More about voicebots](https://webrtcclient.com/features/voicebots/). ## Queues at a glance The *Queues* panel shows callers waiting, the longest wait, active calls, agents online and free agents per queue. Agents pause a queue or log out of all queues in one click. [More about queues](https://webrtcclient.com/features/queues/). ## Everything else you expect Presence and your own status, BLF speed dials, call history with filters, click-to-call, and end-to-end encrypted connections to Asterisk, FreePBX, VitalPBX, MirtaPBX and other [compatible systems](https://webrtcclient.com/compatibility/). ## More to come AI call summaries with action items and searchable conversations are next. Follow the [roadmap](https://webrtcclient.com/roadmap/) or [contact us](https://webrtcclient.com/contact/) for early access. ## Key takeaways - The new WebRTC Client supports multiple lines with per-call controls. - Live AI transcription is optional, switchable per call and controlled per tenant. - Voicebot calls and call queues are visible live in the same browser screen. - AI call summaries and searchable conversations are on the roadmap. --- # Frequently asked questions > Answers to common questions about WebRTC Client — requirements, compatibility, security, NAT, notifications, multiple lines and live AI transcription. URL: https://webrtcclient.com/faq/ ### What is WebRTC Client? WebRTC Client is a browser-based softphone with a multi-tenant management portal. It registers to your existing PBX over a secure websocket, so users can make and receive calls in Chrome, Edge, Firefox or Safari without installing software. ### Is WebRTC Client available today? The new version of WebRTC Client — with multiple lines, live AI transcription, queues and voicebots — is available in early access and still in active development, with more on the [roadmap](https://webrtcclient.com/roadmap/). [Contact us](https://webrtcclient.com/contact/) for early access or to discuss partner and service-provider licences. ### Which phone systems are supported? Asterisk, FreePBX, VitalPBX, MirtaPBX, Issabel, Kamailio, FreeSWITCH and most other SIP platforms with a secure websocket. See [compatibility](https://webrtcclient.com/compatibility/). ### What do I need on my PBX? A valid TLS certificate (not self-signed), a websocket over TLS (usually TCP port 8089) and extensions with WebRTC enabled (AVPF, ICE, rtcp-mux, DTLS-SRTP). The [integration guides](https://webrtcclient.com/guides/) explain each step. ### What do users need? A modern browser, a microphone and speakers or a headset, and an internet connection that can reach the PBX websocket. On first use, the browser asks permission to use the microphone. ### Do users need to know their SIP credentials? No. Administrators map extensions to e-mail addresses in the management portal. Users sign in with e-mail and password; SIP passwords stay hidden. With MirtaPBX, credentials can even be retrieved via the API. ### Is it secure? Signalling runs over a TLS-encrypted websocket (WSS) and media is encrypted with DTLS-SRTP. The platform has been penetration-tested by an external security company. ### My PBX is behind NAT and I have no audio. What should I do? Enable ICE support and configure a STUN server, and add ICE host candidates that map your private IP to your public IP. See [STUN servers](https://webrtcclient.com/guides/stun-servers/) and the NAT sections of the [Asterisk](https://webrtcclient.com/guides/asterisk/) and [FreePBX](https://webrtcclient.com/guides/freepbx/) guides. ### Can office users and remote workers use the same address? Yes. Use a public hostname for remote users and an internal DNS record for office users that points to the PBX's private IP. See [internal PBX with remote clients](https://webrtcclient.com/guides/internal-pbx-remote-clients/). ### Browser notifications or pop-ups are not showing on Windows. How do I fix this? Check Windows **Focus assist** (called *Do not disturb* on Windows 11). When it is on, Windows hides browser notifications. Switch it off or add your browser as an allowed app. ![Windows Focus assist settings switched off](https://webrtcclient.com/img/guides/windows-focus-assist.png "Switch Focus assist off so browser notifications for incoming calls are shown.") ### Can I use my own brand? Yes. WebRTC Client is fully [white-label](https://webrtcclient.com/features/white-label/): logo, colours, domain and notification e-mails. ### Does WebRTC Client transcribe calls? Yes. The new version offers optional [live AI transcription](https://webrtcclient.com/features/ai-transcription/), switchable per call and controlled per tenant with policies. Live call translation is available in beta: the translation appears next to the transcript, for both sides of the call. AI call summaries and searchable conversations are on the [roadmap](https://webrtcclient.com/roadmap/). ### Can I handle more than one call at a time? Yes. WebRTC Client supports [multiple lines](https://webrtcclient.com/features/multiple-lines/): call waiting, switching between calls and per-call controls. ### Is there a free trial? Yes, a free 30-day trial is available through early access. See [free trial](https://webrtcclient.com/trial/). --- # Free trial > Try WebRTC Client free for 30 days through early access. The trial ends automatically, without costs or obligations. URL: https://webrtcclient.com/trial/ We like to convince you with the product itself. That's why WebRTC Client comes with a **100% free 30-day trial**. Need more time? Just let us know. **Early access:** The new version of WebRTC Client — with multiple lines, live AI transcription, queues and voicebots — is available in early access. [Contact us](https://webrtcclient.com/contact/) to request your trial. ## How the trial works - You connect your own Asterisk, FreePBX or other [compatible PBX](https://webrtcclient.com/compatibility/). - You get access to the management portal and the browser client. - The trial **ends automatically**, without any costs. - We will **not** chase you with sales calls. - We will **not** use your information for marketing purposes. ## Prepare your PBX You can already get your phone system ready: follow the [integration guide](https://webrtcclient.com/guides/) for your PBX to set up a secure websocket and WebRTC-enabled extensions. --- # Contact > Contact 10Telecom B.V., the company behind WebRTC Client, in Emmen, the Netherlands. Call +31 88 10 14 520, Monday to Friday 8:30–17:00. URL: https://webrtcclient.com/contact/ Questions about WebRTC Client, early access, partnerships or a platform licence? We'd love to hear from you. ### Give us a ring [+31 88 10 14 520](tel:+31881014520) Monday – Friday, 8:30–17:00 (CET) ### Find us at the office Bislett 10 7825 SB Emmen the Netherlands ### Legal information 10Telecom B.V. VAT ID: NL822745197B01 Chamber of Commerce: 50444719 ## Need help with installation? Not sure where to start? You're not alone. We offer integration and installation services — for example setting up a secure websocket on your Asterisk server — and can do the work for you. Call us to discuss your situation.