WebRTC explained from browser permission to the far-end call.
Learn how WebRTC browser APIs, signaling, ICE, media, security, TURN relays, gateways, cloud call control, and PSTN provider roles fit together.
A browser call uses an application lane and a negotiated media lane
WebRTC coordinates application signaling and a negotiated real-time media path; telephone service sits beyond an explicit gateway boundary.
The user grants media permission and the application applies identity, call state, and business policy.
Application and session lane
The application exchanges offers, answers, ICE candidates, identity, and call state; WebRTC does not mandate the business signaling service.
- 01Authenticate and authorize
- 02Create offer or answer
- 03Exchange ICE candidates
- 04Apply call and workflow state
ICE-selected protected media lane
Connectivity checks choose a viable candidate pair; media can be direct, relayed through TURN, or processed by an approved media service.
- Capture and encode
- Check direct and relay candidates
- Select and monitor the pair
- Decode, play, and report statistics
The remote side negotiates compatible media and represents the intended user or telephony path.
How WebRTC works and when TalkChief fits
The W3C WebRTC Recommendation defines JavaScript interfaces including RTCPeerConnection and an RTP media API. The IETF WebRTC overview describes the associated protocol suite. The application still needs a service to authenticate users, decide who may call whom, exchange session descriptions and connectivity candidates, apply business policy, and preserve operational evidence.
WebRTC can support browser-to-browser sessions or connect through media and signaling infrastructure to SIP endpoints and the public telephone network. The latter requires explicit gateway, number, carrier, caller-identity, and destination arrangements; browser capability alone proves none of them.
TalkChief fits when the business wants its browser calling inside the TalkChief SaaS workflow. A customer-specific web, CRM, or service embedding can be designed by the TalkChief team after discovery and agreement; the microservices architecture supports adaptable integration, but browser support and each custom interface still require an explicit scope and test plan.
ICE finds a usable path; it does not promise a direct path
Interactive Connectivity Establishment gathers and checks candidate addresses across NAT and firewall boundaries. Depending on the endpoints and network policy, the selected route may be direct or may relay media through TURN. A relay can be necessary for reachability, and it changes capacity, geography, cost, and troubleshooting considerations.
Signaling and media can take different routes. Diagnose the selected candidate pair, RTP statistics, codec, audio device, packet loss, jitter, round-trip time, and relay behavior rather than assuming the web page and audio used the same path.
WebRTC production checklist for business voice
Test permissions, networks, browser versions, relays, gateways, provider routes, and support evidence as one user journey.
Supported browsers and versions, microphone and speaker selection, permission recovery, and accessibility
Authentication, authorization, session signaling, timeout, retry, reconnect, and duplicate-call prevention
ICE servers, TURN capacity and credentials, IPv4 and IPv6, VPN, proxy, firewall, and mobile-network behavior
Encryption, origin security, privacy notices, logs, retention, and least-privilege administration
Codec, DTMF, early media, hold, transfer, recording, two-way audio, and representative network impairment
PSTN gateway, number, destination, caller identity, emergency-service boundary, billing, and escalation where applicable
Further reading
Product information and relevant public resources for readers who want more detail.
Frequently asked questions
Is WebRTC the same as SIP?
No. WebRTC defines browser APIs and a protocol suite for real-time communication. SIP is a signaling protocol often used elsewhere in the voice system; a gateway or service can connect the two.
Does WebRTC always send media directly between browsers?
No. ICE selects a viable candidate pair, and some networks require a TURN relay or application media service.
Does adding WebRTC give a web app a phone number?
No. Telephone-number supply, inbound routing, outbound destinations, caller identity, and PSTN provider service are separate from browser media capability.