2026 Comparison

Natalia Analytics On-Premise vs Jusan CallXpress GO — 2026 Comparison

Alcatel PBX call record (CDR) analytics, installed at your site in both cases. Deployment, data protection and export comparison based on publicly documented information.

Methodology

  • Independent comparison, not affiliated with Jusan.
  • Sources for Jusan: official site (jusan.es), resellers actaphone.be and eshop-alliance.com, integrator wiki innovaphone.com. Each source is linked below with its archived copy; all were consulted on October 5, 2026. Resellers list the product as "CallXpress".
  • Sources for Natalia: public Natalia Analytics On-Premise documentation (getnatalia.com), updated October 5, 2026.
  • Scope: publicly documented features of both products as of these dates. Natalia Analytics Cloud analyses recorded conversations and does not collect PBX call records: it is outside the scope of this comparison.
  • This comparison avoids unsourced claims. Where information is absent from public sources, it is explicitly marked as "Not publicly documented".

Main comparison table

● Verifiable fact (public source) ● Common market practice ○ Not publicly documented

Criterion Natalia Analytics On-Premise Jusan CallXpress GO
Deployment model ● VM appliance on your hypervisor (VMware vSphere / ESXi, Proxmox VE, Microsoft Hyper-V) ● Local and multi-tenant installations [1]
PBX compatibility ● Alcatel OXE (SSH / SCP) and OXO (FTP) ● All PBX models and brands, per the integrator wiki and a reseller [1][2]
Analysis mode ● Local dashboard + read-only MCP server: natural-language queries from the AI client of your choice ● Reports shown on screen, scheduled by email or exported [2][3]
Pricing model ● Fixed-term license, on request ● In September 2024, a reseller listed both a license purchase and a subscription [4]
Deployment steps ● Import the appliance (database and dashboard included), then an 8-screen first-boot wizard ○ Not publicly documented
Updates ● In-place upgrade, data disk kept; the database is restored if a migration fails ○ Not publicly documented
Network flows ● Inbound HTTPS 443 (admin browsers); outbound to the PBX on 22 (OXE) or 30021 (OXO). No internet flow in Strict disconnected mode ○ Not publicly documented
RGPD / GDPR ● Phone numbers pseudonymized; 3 contractual modes chosen at installation (documented) ○ Not publicly documented
Data export ● CSV, JSONL + JSON Schema ● PDF, XLS, CSV, HTML, TIFF, XPS [1][2]
Support ● "Disconnected + 72h support" mode: one-off remote support access, on your trigger, 72 h at most, per the Support DPA ● Phone installation support sold by a reseller [5]
Sources and notes
  • [1] Innovaphone wiki — Howto: CallXpressGo Call Management (PBX compatibility, local and multi-tenant installations, exports tiff, pdf, excel, CSV, XPS; listed on a customer testimonial, not tested by Innovaphone) — page, archive, consulted on October 5, 2026.
  • [2] Actaphone.be — Jusan Call Xpress product page (compatible with any PBX, reports in pdf, doc, xls, html, csv, periodic reports sent by email) — page, archive, consulted on October 5, 2026.
  • [3] Jusan — official call accounting page (reports shown on screen or sent by email in several formats) — page, archive, consulted on October 5, 2026.
  • [4] Eshop-alliance.com — Jusan brand catalog, archived on September 19, 2024 (CallXPress purchase and subscription items; these items are no longer in the live catalog) — page, archive, consulted on October 5, 2026.
  • [5] Eshop-alliance.com — "Jusan Achat Support à l'installation par téléphone" — page, no archive, consulted on October 5, 2026.
  • Natalia: installation, PBX prerequisites, contractual modes, MCP, exports, in-place upgrade.

3 key differentiators

  • Ready-to-run appliance

    Collection, database and dashboard ship in one VM, configured by an 8-screen wizard.

  • 3 contractual modes

    Strict disconnected, disconnected with a 72 h support channel, or connected: you choose at installation, according to your GDPR requirements.

  • Natural-language queries

    A read-only MCP server lets Claude Desktop, Cursor or Claude Code query your call data. The AI model runs on the client side, never in the appliance. Jusan documents reports shown on screen, scheduled by email or exported [2][3].

Use cases where Natalia fits

  • ✓Alcatel OXE or OXO sites wanting call analytics on a ready-to-run VM appliance.
  • ✓Organizations whose call data must not leave their datacenter (Strict disconnected mode).
  • ✓Teams who want to query their call data in natural language from an MCP AI client.
  • ✓Teams that want their call data exportable in CSV or JSONL, readable without Natalia.

Cases where Jusan can fit

  • •Non-Alcatel PBX environments: Jusan is presented as compatible with all PBX models and brands [1][2], while Natalia is currently limited to Alcatel OXE/OXO.
  • •Organizations preferring a license purchase: a reseller listed one in September 2024 [4]; the Natalia license is fixed-term.
  • •Teams that need ready-made reports in PDF, XLS or HTML [1][2].

See the appliance on your PBX

Demo of Natalia Analytics On-Premise on an Alcatel OXE or OXO.