Open RFC 7118 SIP-over-WebSocket

SIP.js demo softphone — your credentials, your control.

Installable browser softphone built on SIP.js. Bring your own SIP credentials — we never see them, they live only in your browser’s local storage. Standards-compliant: works with any RFC 7118 SIP-over-WebSocket server, including a CodeB tenant.

Install it as an app: tap your browser’s “Add to Home Screen” (mobile) or the install icon in the URL bar (desktop). The softphone then launches like a native app, with its own icon, and works offline for the shell.

Your SIP credentials

Stored only in localStorage on this device. Never sent to CodeB. Clear with the “Forget” button below.

or fill in manually

WebSocket server URI

SIP URI

Display name (optional)

Username (auth)

Password (auth)

Idle — fill in your credentials and tap Connect.

Make a call

Tip: keypad sends DTMF tones during a live call (IVR menus, voicemail PIN). Long-press “0” for “+”. Bare digits like 610 become a URI on your registered domain.

Why does this even need its own page?

RFC 7118 — SIP over WebSockets — has been on the books since January 2014. It is the only sensible way to let a modern web browser speak SIP without an extension or a native client. And yet, for more than a decade, several of the most widely deployed soft-PBX platforms have kept it off the roadmap, or stuck it behind premium tiers, or quietly removed it after one release.

We don’t pretend to understand why. Customers have asked for browser-native SIP for years. So we built it — and we’re shipping it as a first-class feature on every tenant. Use the demo above with any RFC 7118-compliant server today; once you have a CodeB tenant, point it at your own subdomain and you’re done. No browser plug-in, no native installer, no per-seat upcharge, no “contact sales” gate.

Open standard. RFC 7118 is public, vendor-neutral, and frozen. Your softphone library of choice (this page demos two) just works.
Your code, your data. Credentials live in your browser’s localStorage — never on our servers. Switch tenants by changing one field.
No lock-in. Walk away whenever you like — the demo will keep working against any compliant SIP-WS server.

Activity log

(no events yet)

How to use this with a CodeB tenant

Get a tenant. Free during preview. Request one on the Get-your-tenant page — takes about a day.

Create a SIP user. In your tenant’s admin, open register.html (SIP credentials page) and add a user with a password. CodeB stores only the HA1 hash — never plaintext.

WebSocket URI. Default URL is wss://<your-tenant>:5443 (the bridge listens on its own port; IIS owns 443). Open port 5443 in your tenant’s firewall, or point this at any RFC 7118 server you already operate.

SIP URI. sip:<username>@<your-tenant> — e.g. sip:alice@acme.codeb.io.

Username + password. The same values you used when creating the SIP user.

Tap Connect. The dot turns green when REGISTER succeeds. Type a number or SIP URI and tap Call. Allow microphone permission when prompted.

Install the PWA. Browser address bar shows an install icon (desktop) or use “Add to Home Screen” (mobile). The softphone then opens with its own icon, no browser chrome.

All credentials live in localStorage on this device only. CodeB’s servers never see them. Use the Forget button to clear everything before passing the device to someone else.

Questions? Talk to us.

No card, no commitment. Pick whichever channel suits you — a human will reply.

✉ Email usinfo@aloaha.com — replies within one business day. ✏ Send a questionOne-page contact form. No tracking, no ticket numbers. ☎ Call us in the browserOne click — rings our office. No install, just a microphone permission.