Cloud Edition See On-Premise Edition →

Alcatel OXE & OXO prerequisites

What to validate on your Alcatel PBX before connecting the Natalia Analytics agent: license, account, network ports, CDR format.

Pre-deployment checklist

Print this checklist or tick the boxes locally. Twelve items to validate before booting the agent VM, covering PBX, account, network and host.

  1. PBX version identified — OXE R8 → R13 or OXO R10 / R10.2
  2. Taxation over IP license active (OXE only) — spadmin -l | grep -i account
  3. Dedicated SCP/HTTPS account created — NOT the admin account
  4. PBX IP + port known — 22 OXE / 443 or 30443 OXO
  5. CDR path located on OXE — find /usr -name "TAXA*.DAT"
  6. /etc/shells contains /bin/bash (if SCP account created with bash)
  7. Read ACL on /usr4/account/ enabled for the dedicated account
  8. Target hypervisor identified — VMware / Proxmox / Hyper-V / VirtualBox
  9. VM resources available — 1 vCPU, 512 MB RAM, 5 GB disk
  10. Outbound HTTPS 443 to api.getnatalia.com opened
  11. vTPM available (recommended) OR lost-password procedure accepted
  12. Natalia Cloud account created + API key received

Side-by-side prerequisites

Prerequisite Alcatel OXE (OmniPCX Enterprise) Alcatel OXO (OmniPCX Office)
Compatible versions R8, R10, R11, R12, R13 R10, R10.2
Required license Taxation over IP Built-in (no additional license)
Collection protocol SSH + SCP HTTPS WMC + JWT
Network port 22 (SSH/SCP) 443 (HTTPS) or 30443
System account netadmin (V24 mode) WMC profile: CDR operator (or equivalent per firmware)
CDR location /usr4/account/ Pulled via API endpoint /cdr
CDR format ocals/icals : text, semicolon-separated, ISO-8859-1
.DAT : compressed binary (Lempel-Ziv) — rename to .z then gunzip 		JSON / XML
Native retention 31 days (in /usr4/account/) Number of tickets (configurable in WMC, not days)
Recommended cycle 30 min 30 min (must stay < 60 min for JWT TTL)
Go to OXE configuration → Go to OXO configuration →

Natalia vs Alcatel alternatives

  • — Native CDR collection over standard Alcatel protocols (SSH/SCP for OXE, HTTPS for OXO), no proprietary middleware required
  • — Outbound HTTPS only, zero inbound port. Easier network/security validation
  • — Per-month, no-commitment pricing (no perpetual license, no per-extension fee)
  • — Cloud dashboard, MCP-ready for LLM querying, multi-PBX consolidation built-in
  • — Detailed comparison pages: coming soon (/comparisons/)

Last updated :

Suggest an edit