DEFINITION • BROWSER • CALLING
What is a webphone?
A webphone is a voice or video calling interface that runs inside a web browser. Instead of installing a desktop softphone, a user opens a webpage, grants permission to the microphone and uses controls such as dial, answer, mute, hold and end call.
Most modern webphones use WebRTC, the browser technology for capturing audio and video, negotiating media capabilities and transporting real-time media securely. WebRTC does not define a complete business telephone system by itself. Registration, telephone numbers, extensions, queues, call routing and connections to external networks are supplied by signaling servers, SIP infrastructure or application services.
A webphone can therefore be a simple click-to-call widget, an agent console inside a CRM, an internal extension, a customer-support entry point or a complete browser-based communications interface.
WEBRTC • SIP • ARCHITECTURE
What components does a webphone require?
Browser interface
The webpage provides the call controls and requests access to the user’s microphone or camera. It also displays call state, errors and device choices. Microphone access normally requires a secure HTTPS page and explicit user permission.
Signaling service
WebRTC leaves signaling to the application. Signaling exchanges call offers, answers, session descriptions, candidates and application events. It may use WebSocket, HTTPS or another application-defined transport.
ICE, STUN and TURN
ICE helps two endpoints determine how media can travel across local networks, firewalls and NAT. STUN helps discover a public-facing network address. TURN relays media when a direct path cannot be established. A production deployment should not assume that peer-to-peer connectivity will always succeed.
SIP server or IP-PBX
Business calling commonly depends on a SIP server or IP-PBX for extensions, registration, routing, queues, trunks and call control. Because browsers do not normally act as conventional UDP, TCP or TLS SIP endpoints, a WebRTC-to-SIP component is often placed between the browser and the SIP network.
Media bridge or gateway
The bridge maps browser signaling to SIP call control and handles differences between WebRTC media and the existing VoIP network. Depending on the deployment, it may terminate secure WebRTC media, negotiate codecs, relay RTP and manage media compatibility.
In a VaxVoIP deployment, the browser WebPhone communicates with VaxServerWebRTC. That server component connects the browser call with an existing SIP server or IP-PBX while the telephony platform retains its routing and account configuration.
CALL • FLOW • MEDIA
How does a browser-based phone call work?
Incoming calls follow the same principles in reverse. The application must remain connected to receive the signaling event, and browser background restrictions can affect how reliably a webpage receives calls when it is suspended or closed.
CAPABILITIES • IMPLEMENTATION
What capabilities can a webphone provide?
The available functions depend on the application, signaling service and telephone platform. WebRTC supplies real-time browser media, but features such as voicemail and recording require additional server or application support.
- Browser audio and video: Capture and exchange real-time media without a legacy browser plugin.
- Call controls: Dial, answer, reject, mute, hold, transfer and end calls when supported by the call-control layer.
- Website calling: Let a visitor start a support or sales call from a page without using a separate telephone.
- Business-system integration: Embed calling within a CRM, helpdesk, customer portal or agent workspace.
- Presence and status: Display availability or call state when the application server supplies that information.
- Recording and conferencing: Add these functions through the SIP platform, media server or application workflow.
WEBPHONE • SOFTPHONE • COMPARISON
How is a webphone different from a softphone?
Both provide software-based calling, but their deployment and operating environments differ.
Webphone
- Runs inside a supported browser and is delivered as part of a website or web application.
- Uses WebRTC for browser media and browser-compatible signaling.
- Can be updated centrally when the web application is deployed.
- Depends on browser permissions, lifecycle rules and background limitations.
- Fits naturally inside browser-based CRM, support and customer portals.
Installed softphone
- Runs as a native desktop or mobile application.
- May communicate directly with SIP servers using native SIP transports.
- Can integrate more deeply with operating-system notifications, devices and background services.
- Requires installation, packaging and platform-specific updates.
The better option depends on the required user experience. A webphone is useful when immediate browser access and web integration matter. An installed softphone is often more suitable when persistent background registration or deeper operating-system integration is required.
SECURITY • PRIVACY • ACCESS
Are webphone calls secure?
WebRTC requires encrypted media, but overall security depends on the complete application. HTTPS, authentication, authorization, SIP security, media relays, server configuration and operational controls all remain important.
- Serve the webphone through HTTPS and restrict microphone access to the expected origin.
- Use short-lived authenticated sessions rather than embedding reusable SIP or API credentials in browser code.
- Protect signaling endpoints against unauthorized registration, enumeration and excessive requests.
- Configure TURN credentials, firewall rules and media port ranges for the intended deployment.
- Define whether calls, transcripts or diagnostic logs are retained and who can access them.
- Apply consent and disclosure requirements when calls are monitored or recorded.
DEPLOYMENT • TESTING • OPERATIONS
What should be tested before deployment?
Testing should reflect the real deployment path from the browser through the WebRTC server to the SIP server, IP-PBX or service provider. A successful call on one local network does not demonstrate production readiness.
WEBPHONE • FAQ
Frequently asked questions
Does a webphone require software installation?
The calling interface normally runs in the browser without a separate softphone installation. The browser, operating system and required audio devices still need to support the application.
Can a browser connect directly to a SIP server?
Not usually in the same way as a native SIP phone. Browsers use WebRTC-compatible media and application-defined signaling, so a server component or gateway commonly connects the browser side with SIP infrastructure.
Do webphones require STUN and TURN?
ICE is used to select a media path. STUN is commonly used for address discovery, and TURN is needed when direct media cannot pass through a firewall or NAT. The precise configuration depends on the network design.
Can a webphone receive incoming calls?
Yes, while the web application maintains the required session and the browser permits it to run. Receiving calls after a tab is closed or suspended generally requires a different application or notification strategy.
Can a webphone call regular telephone numbers?
Yes, when the connected SIP server, IP-PBX or service provider supplies the required routing and PSTN service. WebRTC itself does not provide telephone numbers or carrier connectivity.
Does WebRTC guarantee high call quality?
No. Quality still depends on network latency, jitter, packet loss, codec selection, media routing and endpoint devices. WebRTC provides the media framework but cannot remove all network constraints.
Is a webphone the same as a softphone?
A webphone is a type of software phone that runs inside a browser. The term softphone often refers to an installed desktop or mobile application with deeper operating-system integration.