Free 90-day token and 30 days free for business users. Learn more →
Embed a Web Phone in your website or CRM
Web Phone is truly the “Swiss Army knife” of embedded Web Phones. Whether you are using your own Web Phone SDK, SIP.js, JsSIP or our free Browser Phone SDK, we have a solution for you.
Web Phone is based on the Siperb Proxy service for provisioning and WebRTC-to-SIP proxy.
Simple to implement, quick to get started, and great-looking. Web Phone is all you need for VoIP, SIP-based browser calling.
Built for Engineers. Designed for Integration.
Everything you need
A composable WebRTC web phone platform designed for embedding into existing web applications, including CRMs, while integrating with your architecture.
Bring your own SDK
Use any WebRTC or SIP SDK — SIP.js, JsSIP, or custom. Web Phone stays SDK-neutral, or use our fully featured Browser Phone.
No Passwords
Authentication uses tokens and identity context, not stored credentials. No shared secrets, no SIP passwords, no password leaks.
Team Management
Provision users, devices, and permissions centrally. Manage teams, roles, and access without exposing SIP or infrastructure details.
Full Provisioning
Attach your own configuration graph to every instance. Web Phone loads and persists arbitrary JSON without enforcing schema constraints.
Proxy Provided
Web Phone proxies signaling and media, simplifying NAT traversal, security, and network topology without locking you into a stack.
Transcoding Available
Bridge modern WebRTC codecs with legacy systems. Automatic transcoding ensures interoperability without sacrificing quality.
The Web Phone Browser SDK provides a complete, production-ready softphone for the browser, implementing full SIP call flows over WebRTC. It supports audio and video calling, call transfers, holds, multiple concurrent sessions, device management, and real-time media statistics. Designed to run embedded inside existing web applications such as CRMs, the Browser Phone integrates with token-based identity, proxy signaling, and media handling without exposing credentials or requiring changes to your backend architecture.
Security
Keeping PBX Credentials Out of the Browser
The Web Phone never stores or exposes real SIP credentials in the client. Instead, all sensitive SIP registration details live inside the Siperb Proxy, where they are protected and managed server-side. The browser authenticates using short-lived, scoped JWTs that represent identity and permissions, not passwords. This design eliminates credential leakage, prevents SIP reuse outside the intended context, and allows phones to be safely embedded into third-party systems such as CRMs without expanding the attack surface.
The Phone Frame
Keep It Simple, Separate.
The Web Phone runs inside an isolated iframe, following a “keep it simple, separate” approach to embedding complex real-time communication logic. This isolation prevents CSS, JavaScript, or dependency conflicts with host applications — a common problem in tightly controlled environments like CRMs or third-party platforms. The iframe loads its configuration and code from the provisioning tree, ensuring the phone always runs the latest compatible version without manual updates or redeployments in your application.
Modular Code Design
Build Together, Extend Freely
The Browser Phone SDK is built using a modular architecture, allowing functionality to be composed and extended through well-defined modules. Core calling, media handling, and UI components are separated from optional providers, making it straightforward to integrate additional systems such as SMS, messaging platforms, email, or custom event sources. This design enables teams to extend the phone’s capabilities incrementally, without forking or tightly coupling to the core codebase.
Window API
Make the Phone Your Own
A fully featured Window API allows developers to extend and customize the Browser Phone’s interface in a controlled way. The API includes primitives such as Window, Alert, Prompt, Confirm, and Toast components, enabling extensions to surface their own UI without breaking consistency. This makes it possible to add custom workflows, notifications, and integrations directly into the phone interface, while keeping the core UI stable and predictable.
Pricing
The Browser Phone SDK is free!
Free Forever! Find out how to use Browser Phone SDK for free, forever. Otherwise Web Phone requires Siperb account – this is the pricing details from Siperb, or see more pricing details here.
If you are using a Siperb account (for provisioning and (or) proxy, you will need a PAT – Siperb offers a free PAT for up to 90 days, so that you can develop without cost. You also get 30 days free on activating your account.
Free – Browser Phone SDK
$0
/month
Free Access Token for up to 90 days
- Hosted WebRTC-to-SIP Proxy
- Business Calling Functionality
- Provisioning
- WebSocket or Proxy Registration
- Buddy Sync across devices
Business
Most Popular
￡2
/user/month
Suitable for most business, with a plan that scales with your business.
- Everything in Personal
- Message Stream Storage & Sync
- Call Recording Storage & Sync
- Domain Users
- Bulk pricing available
Business Pro
￡5
/user/month
Everything we have to offer, with huge storage and the latest awesome tools!
- Everything in Business
- Call Transcoding (SRTP/DTLS to RTP)
- Message Stream Storage for 12+ Months
- Call Recording Storage for 12+ Months
- Bulk pricing available
-
·
WebRTC IP Address Leak
WebRTC is exceptionally good at discovering how devices can reach each other across complex networks — and that strength is…
-
·
WebRTC Password Security in the real world
WebRTC is often described as “secure by default,” thanks to strong browser enforcement, encrypted signaling, and protected media streams. Yet…
-
·
WebRTC: Media, Signaling, ICE, and Why WebRTC is so powerful
WebRTC is often treated as a black box. In this deep dive, we open it up — examining how signaling,…
FAQs
Frequently Asked Questions
What is Web Phone?
Web Phone is a composable WebRTC web phone platform designed to embed real-time calling into existing web applications such as CRMs, dashboards, and portals.
Does Web Phone require a specific PBX or SIP server?
No. Web Phone is PBX-agnostic and works with any SIP-compatible system that supports SIP over WebSocket (WSS).
Can Web Phone be embedded into third-party systems like CRMs?
Yes. Web Phone is designed for embedding and supports iframe-based isolation to prevent CSS, JavaScript, or dependency conflicts with host applications.
Can I extend the Browser Phone with custom features?
Yes. The Browser Phone uses a modular architecture and exposes APIs that allow you to add custom UI elements, workflows, notifications, and providers.
What browsers are supported?
Web Phone supports modern, WebRTC-capable browsers such as Chrome, Edge, Firefox, and Safari. HTTPS is required for media access.
Do I have to use the built-in Browser Phone UI?
No. You can use the Web Phone provisioning APIs with your own SIP client, such as SIP.js, JsSIP, or a custom WebRTC implementation.
Are SIP credentials stored in the browser?
No. When using provisioning and proxying, real SIP credentials are stored server-side. The browser authenticates using short-lived tokens instead of passwords.
Does Web Phone support audio and video calls?
Yes. Web Phone supports WebRTC-based audio and video calling, subject to codec and capability support of the connected SIP infrastructure.
Is Web Phone suitable for production use?
Yes. Web Phone is designed for production environments and includes provisioning, identity handling, media proxying, and isolation patterns required for real-world deployments.
Do I need to use the Siperb Proxy to use Web Phone?
No. You can connect directly to your own SIP infrastructure if you choose. The proxy is optional and provides additional security and operational benefits.
Question not answered above? See more Frequently Asked Questions →