Alcatel OXE and OXO prerequisites
What to check on your Alcatel PBX before opening the appliance wizard: collection account, network flows, CDR files.
Pre-deployment checklist
Ten items to tick before booting the appliance. Print the page or tick the boxes locally.
- PBX model identified — OXE (SSH/SCP collection) or OXO (embedded FTP collection)
- OXE: Taxation over IP license active —
spadmin -l | grep -i account - OXE: SSH enabled, read access to
/usr4/account— accountmtclor a dedicated account - OXO: embedded FTP server reachable on port 30021 — account
ftp_nmc - Flow opened from the appliance to the PBX — TCP 22 (OXE) or TCP 30021 plus passive FTP data ports (OXO)
- PBX IP address known and fixed
- Target hypervisor identified — VMware vSphere / ESXi, Proxmox VE, Microsoft Hyper-V
- VM resources reserved — 4 vCPU, 8 GB RAM, 20 GB system disk + 100 GB data disk
- Signed license file received — license lifecycle
- Contractual mode chosen — Strict, +Support 72h or Connected
OXE and OXO side by side
| Prerequisite | Alcatel OXE (OmniPCX Enterprise) | Alcatel OXO (OmniPCX Office) |
|---|---|---|
| Collection protocol | SSH + SCP | Embedded FTP, passive mode |
| Network port | 22 | 30021 |
| Collection account | mtcl (wizard default) or a dedicated account |
ftp_nmc |
| Ticket location | /usr4/account |
/current/nmc (account.gz), optionally /current/metering |
| Collected files | TAXA*, icals*, ocals* (.dat, .csv, .gz) |
account.gz |
| Writes to the PBX | None: listing and file copy only | None: read-only FTP commands |
| Host check | SSH key pinned at first connection | — |
| Collection cycle | 30 min by default, adjustable from 5 min to 24 h | |