Vitxi 4.6.0-9: VitalPBX WebRTC Softphone Updates

If your agents work from Vitxi, two things matter more than anything else: the call history has to be accurate, and a callback has to reach the person who actually called. When a callback goes to a routed number instead of the customer, you lose time, credibility and sometimes the deal.

The last three releases of Vitxi, the VitalPBX WebRTC softphone, focus exactly on that — plus a set of fixes that make life easier for anyone managing multiple tenants from one server.

Here’s everything that shipped between October 1 and October 12, 2026 (versions 4.6.0-7, 4.6.0-8 and 4.6.0-9), what each change means in practice, and who benefits most.


The Problem: Call History You Can’t Fully Trust

In real deployments, calls rarely travel a straight line. They pass through trunks, carriers, IVRs and ring groups, and the number a softphone “sees” can end up being a routed number rather than the destination the caller originally dialed.

For agents, that creates two everyday headaches:

  • Callbacks go to the wrong place — the agent clicks “call back” and reaches a routing number, not the customer.
  • Call History shows a number that doesn’t match what the carrier reports, which makes troubleshooting and reporting harder for admins.

Multi-tenant operators had their own friction too: tags that didn’t reflect what was really selected, tag catalogs from the wrong tenant, and long tenant lists that were slow to navigate.


What’s New in the VitalPBX WebRTC Softphone (Vitxi 4.6.0-7 to 4.6.0-9)

Vitxi 4.6.0-9 — October 12, 2026

🆕 Added: choose P-Asserted-Identity or Remote-Party-ID per agent profile Agent profiles can now define whether Call History displays the destination reported through P-Asserted-Identity or Remote-Party-ID. Different carriers and SIP trunks report identity differently — now you can match Vitxi to the way your provider actually works, profile by profile.

✅ Improved: callbacks stay tied to the original dialed destination Callbacks remain linked to the number that was originally dialed, and administrator Call Logs keep the full routing diagnostics. Agents get the right number; admins still see the whole path the call took.

Vitxi 4.6.0-8 — October 9, 2026

🔧 Fixed: realtime Call History callbacks Realtime Call History callbacks were using a routed number instead of the original dialed destination. That’s fixed — and 4.6.0-9 builds on this fix with the improvements above.

Vitxi 4.6.0-7 — October 1, 2026

A connectivity improvement and a round of multi-tenant and tagging polish:

  • Custom HTTPS ports respected for the SIP WebSocket when connecting through a reverse proxy — useful if your deployment doesn’t run on the standard port.
  • Tag checkboxes in agent Call History now display the actual selection state.
  • Stale tenant tag responses can no longer overwrite the active tag catalog.
  • Administrator Call Log tags load from the currently selected tenant.
  • Tenant search is available when the tenant switcher has more than ten entries.

Who Benefits Most

If you are…What these releases give you
A call center managerAgents call back the right customer the first time, and call tags reflect what was actually selected.
An MSP or ITSP running Multi-TenantFaster tenant switching with search, and tags that always belong to the tenant you’re looking at.
An integrator or IT adminPer-profile control over which SIP identity header drives Call History, full routing diagnostics in Call Logs, and support for custom HTTPS ports behind a reverse proxy.

All of this sits on top of VitalPBX’s core model: no per-user or per-extension fees. Whether Vitxi runs for 10 agents or 1,000, your license cost is based on your plan — not your headcount.

VitalPBX Plans & Pricing — https://vitalpbx.com/pbx-plans-and-pricing-vitalpbx-system/


Frequently Asked Questions

What is Vitxi?

Vitxi is the WebRTC softphone client for VitalPBX. It runs in the browser, so agents and users can make and receive calls on their VitalPBX extension without installing a desk phone or a separate desktop application. It complements the VitalPBX Connect mobile app for teams that work from anywhere.

What is the latest version of Vitxi?

As of October 12, 2026, the latest Vitxi release is version 4.6.0-9. It adds a per-agent-profile option to choose whether Call History uses P-Asserted-Identity or Remote-Party-ID, and keeps callbacks tied to the original dialed destination. The full release history is on the official Vitxi changelog at vitalpbx.com.

What is the difference between P-Asserted-Identity and Remote-Party-ID?

Both are SIP headers used to carry caller or destination identity between systems. P-Asserted-Identity (PAI) is the standardized header, while Remote-Party-ID (RPID) is an older header that some carriers and devices still use. Vitxi 4.6.0-9 lets you select which one Call History relies on for each agent profile, so the displayed destination matches what your provider sends.

Why were Vitxi callbacks dialing the wrong number?

In some call flows, realtime Call History callbacks used a routed number instead of the destination the caller originally dialed. Vitxi 4.6.0-8 fixed this, and 4.6.0-9 improved it further by keeping callbacks tied to the original dialed destination while preserving full routing diagnostics in administrator Call Logs.

Does Vitxi work with VitalPBX Multi-Tenant?

Yes. Vitxi 4.6.0-7 includes several multi-tenant improvements: administrator Call Log tags load from the currently selected tenant, stale tag responses can no longer replace the active catalog, and tenant search appears when the switcher contains more than ten tenants. Keep in mind the practical limit for VitalPBX Multi-Tenant is about 100 tenants per server, due to the underlying Asterisk engine.

Can Vitxi run behind a reverse proxy on a custom HTTPS port?

Yes. Starting with Vitxi 4.6.0-7, the SIP WebSocket connection respects custom HTTPS ports when connecting through a reverse proxy. This helps deployments that don’t use the standard HTTPS port.


Try the Latest Vitxi on VitalPBX

Accurate call history, callbacks that reach the right person, and smoother multi-tenant management — all inside a browser softphone, with no per-user fees on top.

👉 Running multiple clients? Start your 30-day Multi-Tenant trial 👉 Want to see it live? Book a demo (US Eastern) · Book a demo (Central European)

Full release notes: Vitxi changelog

Our Latest Post