# WebRTC phones on ViciBox 12: the SIP and PJSIP traps

> ViciBox 12 runs chan_sip and PJSIP side by side. Which stack a browser phone lives in, which template to pick, and the checks that show where it went wrong.

URL: https://trustane.com/blog/vicidial-webrtc-phones-vicibox-12
By Trustane. Published 2026-11-05.

> **To the point**
> On ViciBox 12 a browser phone is a chan_sip peer by default, built from the template `vicibox-RTC`, even though the server also runs PJSIP. Most "the phone registers but I cannot see it" problems are a search in the wrong stack.
>
> - Check both: `sip show peers` and `pjsip show contacts`. An agent missing from one may be in the other.
> - Reload both after a change: `sip reload` and `pjsip reload`.
> - Templates on the build we read: `vicibox-RTC`, `VICIphonePJSIP`, `VICIphoneSIP`, `SIP_generic`, `IAX_generic`. There is no template called `WebRTC`.
> - A browser phone also needs a valid certificate name, a reachable WebSocket and microphone permission.

## Two stacks on one server

The box runs `chan_sip` and `res_pjsip`. They are separate drivers with separate config files, CLI commands and registration lists. A phone made in the admin has a protocol field. The default, `SIP`, writes a chan_sip peer. The PJSIP choice with a PJSIP template writes PJSIP objects.

| Question | chan_sip | PJSIP |
|---|---|---|
| Who is registered? | `sip show peers` | `pjsip show contacts` |
| What is configured? | `sip show peers` | `pjsip show endpoints` |
| Do carrier registrations work? | `sip show registry` | `pjsip show registrations` |
| Reload | `sip reload` | `pjsip reload` |

Run them as `asterisk -rx "<command>"`. After a change, `sip reload` does nothing for a PJSIP phone and the reverse. Reloading one stack can make a good fix look bad.

![Diagram: one ViciBox 12 server with a chan_sip column and a PJSIP column, each with its own commands](https://trustane.com/media/16195808b2cd9eb2-1600x595.webp "Two stacks, two sets of commands, one server")

## The templates the server has

The phone template list on the ViciBox 12 server we read held five names. Check by name in the admin templates screen before you trust any name from a blog post, ours included.

- `vicibox-RTC`: a chan_sip entry of type `friend` set up for WebRTC. It is what the standard installation script uses, and the one to pick for a browser phone on a stock ViciBox 12.
- `VICIphoneSIP`: a plain chan_sip desk or soft phone.
- `VICIphonePJSIP`: the PJSIP equivalent. We did not test it with a browser phone on this build.
- `SIP_generic` and `IAX_generic`: hardware phones and other uses.

A phone whose protocol and template disagree (chan_sip with a PJSIP template, or the reverse) shows in the admin but no stack registers it.

## What a browser phone needs

A desk phone needs less. A browser phone has four things that can fail alone. The certificate and listener notes below are general Asterisk and browser knowledge, not our measurements.

**A name on a valid certificate.** Browsers open the microphone only on HTTPS, and WebRTC needs a secure WebSocket (`wss`). A raw IP cannot carry a normal public certificate. A self-signed one makes the browser refuse or warn, and accepting it for the page may not carry over to the WebSocket port. The usual symptom is a phone that never registers while the page loads fine.

Check that the name resolves to the server, the certificate is valid and unexpired for that name, and the WebSocket address in VICIdial uses the same name.

![VICIdial server record with Web Socket URL and External Web Socket URL highlighted](https://trustane.com/media/79c551e46606ea1a-1600x275.webp "Admin, Servers, then your server: the WebSocket address the browser phone connects to")

1. **Web Socket URL**: the `wss` address of this server. Its host name must match the certificate.
2. **External Web Socket URL**: the address used when agents reach the server from outside.

**The Asterisk HTTP listener.** `http show status` shows whether it is listening and on which port. We believe a standard ViciBox build uses 8089. Read it from your server and make sure the firewall lets agents reach it. A port open for the web page and closed for this one gives the same "never registers" symptom.

**Media through the firewall.** WebRTC audio is encrypted RTP. Behind a corporate firewall, calls can connect with no audio one way. We did not measure NAT traversal on the template. If only some agents have one-way audio, suspect their network first. See [lagged agents](https://trustane.com/guides/vicidial-lagged-agents-network).

**The microphone.** The browser asks once per site. An agent who clicked Block cannot talk, and nothing on the server shows it. The setting is in the browser's site settings.

> **Two certificates is a common trap**
> If the certificate was issued for the web server but Asterisk's HTTPS listener loads a different file, only one of the two is right. Check the one Asterisk serves.

## A diagnosis order that saves time

![Flow: find the stack, read the pair, open the WebSocket, check the listener, read the debug, look for a second login](https://trustane.com/media/93461587249b7388-1600x1223.webp "Six checks, in order, when an agent says the phone does not work")

1. Run `sip show peers` and `pjsip show contacts` and search for the extension. Found in one means you know the stack.
2. Read the protocol and template as a pair in the admin.
3. Open the WebSocket address in a browser from the agent's machine. A certificate warning here is the answer.
4. Run `http show status`.
5. Use `sip set debug peer <name>` or `pjsip set logger on`, ask the agent to log in again, then turn logging off. Both are verbose.
6. Look for a second browser tab with the same login, which can take the registration.

Most cases we have seen end at step 1 or 3.

## Carriers follow the same split

A chan_sip carrier and a PJSIP carrier are different objects. In the carrier log's channel column, a PJSIP call shows as `PJSIP/` plus the endpoint name, a more reliable record than a description field. For setup see [a PJSIP carrier on Asterisk 22](https://trustane.com/guides/vicidial-pjsip-carrier-setup-asterisk-22).

## What we did not test

Voice quality of chan_sip against PJSIP browser phones, Opus against G.711 on the browser leg, and builds other than the one ViciBox 12 build we read. If your template list differs, trust your server.

## Questions people ask

### Why can I not see my agent in `sip show peers`?

The phone may be a PJSIP phone. Run `pjsip show contacts` as well. The two stacks keep separate lists.

### Which template should I pick for a browser phone?

On a stock ViciBox 12, `vicibox-RTC`. It is a chan_sip entry made for WebRTC.

## Next steps

Note which stack your agents are in, confirm one host name, one certificate and one WebSocket address that agree, and always reload both stacks. We build the browser phone path on the servers we host, see [VICIdial hosting](https://trustane.com/vicidial-hosting) and [pricing](https://trustane.com/vicidial-pricing). If a phone will not register, [contact us](https://trustane.com/contact).

VICIdial is a trademark of its owner. Trustane is an independent hosting provider.
