Browser phone#
demarc's browser phone uses the Telnyx WebRTC SDK to register a browser client and place operator calls. Supported controls include dialing, DTMF, mute, hold, resume and hangup. Inbound browser ringing is available but ships disabled; see Configuration for the settings it requires.
Before you start#
- A Telnyx credential or connection configured for WebRTC use.
- A production HTTPS dashboard origin.
- Browser permission to use the microphone.
- A headset and a quiet test environment.
Register and place a test call#
- Open the phone area in the authenticated dashboard.
- Confirm that registration reaches the ready state.
- Select the intended outbound identity and enter a test destination.
- Place the call and exercise mute, DTMF and hold/resume.
- Hang up from the dashboard.
The keypad is not offered on conference-backed or inbound-bound legs, so DTMF cannot be sent from those calls.
Do not assume an on-screen control succeeded until the provider and call state agree. Avoid leaving a registered phone open on an unattended workstation.
Verify#
Confirm two-way audio, the final call state in the dashboard, and the matching Telnyx event for an outbound call. If registration fails, check browser permissions, HTTPS, WebRTC credentials and the provider connection before retrying.
If it does not work#
| Symptom | Check | Recovery |
|---|---|---|
| Registration fails | Browser permissions, HTTPS, WebRTC credentials and the provider connection, in that order | The browser phone will not register over plaintext |
| Registered but no audio in one direction | Whether the failure is symmetric | One-way audio is a media path problem, not a registration one |
| The call connects but the dashboard shows no record | The matching Telnyx event | See Dashboard for the disagreement procedure |
| A browser-routed number is answered by the assistant instead | The number's routing | See A browser-routed number answers with the assistant |