Feel free to reach out to us on the Discussion Forum if we have not answered you question here. Find out more about support here.
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.
How does Web Phone handle NAT traversal and firewalls?
Web Phone relies on standard WebRTC ICE mechanisms, using STUN and TURN where required. When proxying is enabled, media routing and NAT traversal are handled consistently across networks, including restrictive corporate environments.
How does identity work without usernames and passwords?
Identity is represented using short-lived, scoped JWTs. These tokens convey user and device context and are validated server-side, eliminating the need to expose reusable credentials in the browser.
Does Web Phone support call transfers, holds, and multiple calls?
Yes. The Browser Phone implements standard SIP call flows including hold, attended and blind transfer, and handling multiple simultaneous call sessions.
Can I integrate messaging or non-voice channels?
Yes. The modular design allows additional providers to be integrated, such as SIMPLE messaging, email, or custom event-driven systems.
Is Web Phone compatible with serverless or API-first backends?
Yes. Web Phone is designed to integrate cleanly with API-driven and serverless architectures, using stateless authentication and externally managed provisioning.
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.
Can I control which codecs are used?
Yes. Codec selection and ordering are controlled through SDP negotiation with your PBX. Web Phone supports modern WebRTC codecs (Opus,G711) and can interoperate with legacy codecs through transcoding when enabled.
Can multiple devices or browser tabs register at the same time?
Yes. Web Phone supports multiple devices per user and can manage concurrent registrations, depending on your PBX and provisioning configuration. Each instance will be uniquely identified.
How are updates delivered to embedded Browser Phones?
The Browser Phone loads its code from a versioned provisioning tree. Updates are applied automatically without requiring changes to the host application or redeployment.
What happens if the provisioning service is temporarily unavailable?
Existing sessions continue to function. New provisioning requests will fail until the service is restored, but cached configuration can be used where enabled.
How does Web Phone scale for large teams or call volumes?
Web Phone scales horizontally by design. Signaling, provisioning, and media proxying can be scaled independently to support large user bases and high concurrency.