Why the Zoiper WebPhone no longer works in modern browsers

If you have found old references to the Zoiper WebPhone and wondered why it will not load, the short answer is that the browsers it depended on changed underneath it. The Zoiper WebPhone is a browser-embedded Webphone, a phone that runs inside the agent's browser page, and it relied on a plugin technology that modern browsers removed years ago. This post explains exactly what broke, which browsers held on the longest, and what to reach for now so you do not waste time trying to revive something the browser itself no longer permits.

The NPAPI dependency that got removed

The Zoiper WebPhone was built on NPAPI, an old browser plugin interface. As of 2016, the WebPhone stopped working with newer versions of Google Chrome and Microsoft Edge because both browsers discontinued support for the NPAPI featureset. Without NPAPI the plugin cannot load, so the embedded phone simply never appears on the page. This is not a configuration you can fix on the VICIdial side or work around with a setting; the capability was taken out of the browser itself, and no amount of server tuning brings it back.

Which browsers held on, and for how long

For a while the WebPhone still ran on Firefox and Microsoft Internet Explorer, the two browsers that kept the older plugin model alive after Chrome and Edge dropped it. Firefox only supported it through mid-2018, after which that door closed too. The phone was always Windows-only and tied to older Internet Explorer and pre-2017 Firefox, so even at its peak the supported matrix was narrow and getting narrower. Today there is no current, maintained browser that runs it, which makes it a dead end for any new build.

• Chrome and Edge: broken since 2016 when NPAPI support ended.
• Internet Explorer: ran it, but Internet Explorer itself is now retired.
• Firefox: supported it only through mid-2018.

Why the plugin model failed and WebRTC won

Plugins like NPAPI carried real audio and signalling but were a security and maintenance burden, so browser makers replaced the whole model with WebRTC, a built-in standard for browser voice and video. A WebRTC phone registers as a SIP endpoint and carries audio over RTP without any plugin at all. Because the support is native to the browser, it does not break the next time the browser updates, which is exactly the failure mode that killed the Zoiper approach over and over.

flowchart LR
  A[Zoiper web phone] --> B[Needs NPAPI plugin]
  B --> C{Browser supports NPAPI}
  C -- No --> D[Phone fails to load]
  C -- Yes --> E[Only old IE and Firefox]
  D --> F[Move to WebRTC softphone]

The supported replacement is ViciPhone, a free WebRTC phone built natively for VICIdial. It works in current browsers and uses SIP (Session Initiation Protocol) over a secure WebSocket with audio over RTP, so there is no plugin to break and nothing that depends on a deprecated browser feature. Switching to it is the right move for any setup still clinging to the old Zoiper phone.

For the full context on how agents connect from outside the office, read the pillar on VICIdial remote agents. To understand what the Zoiper integration offered while it lasted, see what the Zoiper WebPhone integration is. If you would rather start on a phone that already works in every modern browser, our managed plans ship a branded WebRTC phone on every plan.