SIP over WebSocket for Browser AI Voice in 2026: When sipws Beats WebRTC
By Sagar Shankaran, Founder of CallSphere
WebRTC dominates browser AI voice for a reason - UDP under the hood. But SIP over WebSocket still wins for click-to-call inside a SaaS app where you control both ends. Here is the 2026 picture.
Key takeaways
WebRTC won browser voice. But SIP over WebSocket (sipws) is still the right answer for embedding a phone inside a SaaS app where you do not need NAT traversal and you do need a familiar SIP trunk. The choice in 2026 is not WebRTC vs sipws but WebRTC vs WebRTC + sipws-control plane.
Background
flowchart TD
Out[Outbound campaign] --> Twilio[Twilio Voice API]
Twilio --> STIR[STIR/SHAKEN attestation]
STIR --> Carrier[Originating carrier]
Carrier --> Term[Terminating carrier]
Term --> Recipient[Recipient phone]
Recipient --> Webhook[/voice webhook/]
Webhook --> Agent[AI sales agent]SIP over WebSocket (RFC 7118) was specified in 2014 to let SIP user agents run inside browsers. The browser opens a WSS connection to a SIP-over-WebSocket-aware SIP server (Kamailio, OpenSIPS, Asterisk PJSIP), and SIP messages flow over that WebSocket as plain SIP text. Media still uses WebRTC (DTLS-SRTP over UDP) - sipws is a signaling transport only.
For AI voice in 2026 the canonical browser flow is WebRTC + Realtime API direct: the browser establishes a peer connection to OpenAI's edge, audio flows over DTLS-SRTP, no SIP involved. But for products that need PSTN dial-out, transfer to a human, or an existing SIP-trunk billing relationship, sipws is still useful. JsSIP, SIP.js, and Twilio Voice SDK all use sipws (or its WebRTC-bridge equivalent) for signaling.
Technical deep-dive
A sipws REGISTER from a browser:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for IT support in your browser — 60 seconds, no signup.
REGISTER sip:callsphere.ai SIP/2.0
Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK-5
From: <sip:alice@callsphere.ai>;tag=abc123
To: <sip:alice@callsphere.ai>
Call-ID: 1234@browser
CSeq: 1 REGISTER
Contact: <sip:alice@df7jal23ls0d.invalid;transport=ws>
Expires: 600The "df7jal23ls0d.invalid" hostname is a placeholder; sipws clients use the WebSocket-Sec-Key as a stand-in for the network address since browsers do not expose their own IP/port to JavaScript. The server tracks the WebSocket connection internally for routing.
For AI voice agent dial-out from the browser:
INVITE sip:+18001234567@callsphere.ai SIP/2.0
Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK-7
From: <sip:alice@callsphere.ai>;tag=abc123
To: <sip:+18001234567@callsphere.ai>
Contact: <sip:alice@df7jal23ls0d.invalid;transport=ws>
Content-Type: application/sdp
v=0
m=audio 9 UDP/TLS/RTP/SAVPF 111
a=rtcp:9 IN IP4 0.0.0.0
a=fingerprint:sha-256 D2:9A:...:38
a=setup:actpass
a=ice-ufrag:F7gINote the SDP advertises DTLS-SRTP for media even though the SIP signaling is over WSS. The SBC on the server side bridges sipws-to-SIP and WebRTC-to-SRTP-on-trunk.
CallSphere implementation
Explore a live demo and compare current plans to find the right fit for your business.
Implementation steps
- Decide if you actually need SIP-trunk-style billing or interop. If yes, sipws helps; if no, use Twilio Voice SDK or direct WebRTC.
- Choose a sipws-aware server: Kamailio with WS module, OpenSIPS, Asterisk with res_pjsip and PJSIP transport
ws, or FreeSWITCH with mod_sofia ws transport. - Use a vetted client library: JsSIP, SIP.js, or Twilio Voice SDK.
- Run sipws over WSS only - never WS - and front it with a TLS-terminating reverse proxy (nginx, HAProxy).
- Authenticate the browser before issuing SIP credentials; do not embed REGISTER passwords in JavaScript bundles.
- Use short-lived REGISTER tokens (10-60 minutes) tied to the user's logged-in session.
- Bridge the call to your AI agent server-side via REFER or a B2BUA pattern - keep the AI prompt and tools out of the browser.
- Test with sngrep on the server side; verify sipws traffic looks normal SIP after the WebSocket frame strip.
FAQ
Is sipws faster than WebRTC for AI voice? No. The signaling transport is irrelevant to media latency. WebRTC media is the same regardless.
Still reading? Stop comparing — try CallSphere live.
See the IT support AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
Why not use sipws + WebRTC media? That is exactly what JsSIP/SIP.js do. The choice is whether you build the JsSIP-style stack yourself or use an SDK like Twilio Voice SDK that abstracts it.
Does sipws support SIP REFER for transfer? Yes. Transfer behavior is identical to wired SIP; the WebSocket is just a transport.
What about WebTransport? Experimental in 2026. Sipws over WebTransport is on draft work in the IETF SIPCORE working group but no production deployments yet.
Are there NAT traversal issues with sipws? Less than wired SIP because the browser opens an outbound WSS to your server, traversing most NATs cleanly. Media still needs ICE.
Sources
- Symbl.ai: WebSocket or SIP - Which is Better for Your App?
- Forasoft: OpenAI Realtime API with WebRTC, SIP, and WebSockets
- RTC League: When to Use WebRTC vs SIP for AI Voice Agents 2026
Explore a live demo and compare current plans to find the right fit for your business.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
Try CallSphere AI Voice Agents
See how AI voice agents work for your industry. Live demo available -- no signup required.
