Alcatel OmniPCX Enterprise (OXE) CDR: FTP or real-time setup
This page covers the Alcatel Alcatel OmniPCX Enterprise (OXE) and Alcatel OmniPCX Enterprise (Ethernet Real Time) variants in Advanced PBX Data Logger. Each section gives the connection settings, the parser to select and the fields the logger extracts for reports or a database; where the setup steps are the same for every variant they are given once. The settings apply to our logger; other call accounting software may expect a different configuration.
Quick facts
| Item | Alcatel OmniPCX Enterprise (OXE) CDR: FTP or real-time setup |
|---|---|
| Variants on this page | Alcatel OmniPCX Enterprise (OXE), Alcatel OmniPCX Enterprise (Ethernet Real Time) |
| Interface | Differs by variant; see each section. |
| Port | 21, 2533 |
| Parsers | Alcatel OmniPCX Enterprise (OXE), Alcatel OmniPCX Enterprise (Ethernet Real Time) |
| Fields extracted | 11 to 34 |
| Other Alcatel systems | Other PBX SMDR formats, Alcatel to London |
Variants on this page
- Alcatel OmniPCX Enterprise (OXE) · CDR files downloaded by FTP from the PBX or its server and parsed on arrival, port 21, 11 fields
- Alcatel OmniPCX Enterprise (Ethernet Real Time) · LAN, port 2533, 34 fields
Alcatel OmniPCX Enterprise (OXE)
Parser: Alcatel OmniPCX Enterprise (OXE)
Connection: CDR files downloaded by FTP from the PBX or its server and parsed on arrival. Port 21.
Fields extracted: 11
If you want to know what software release do you have on Alcatel OmniPCX Enterprise [OXE] please login using telnet, user mtcl, password mtcl an run the command siteid.
Alcatel OmniPcx Enterprise and 4400 (OXE)
The default address of the pbx system is 192.168.0.254 and the port for ftp is 21. You need to add the "FTP" data source and setup in the remote server address:port the following string: 192.168.0.254:21. Also you must use user mtcl and password mtcl.
Data items: Alcatel OmniPCX Enterprise (OXE)
| Description | Data type | Column name |
|---|---|---|
| Subscriber | string | EXT |
| Subscriber name | string | FLAG4 |
| CCN | string | FLAG5 |
| Call time | datetime | CALL_TIME |
| Call duration | datetime | CALL_DURATION |
| Call duration (s) | integer | CALL_DURATION_S |
| Phone | string | DIALED_PHONE |
| Flag 1 | string | FLAG1 |
| Trunk | string | TRUNK |
| Flag 2 | string | FLAG2 |
| Flag 3 | string | FLAG3 |
Sample record
As delivered by the system; phone numbers, names and public addresses are masked.
|101xxxx |test | |051xxxxxxx|000:00:00| 0| SC |0| | |805xxxxxxxx |N| | 0|000001|000001| 9| 0|B|A| |101xxxx |test | |051xxxxxxx|000:00:00| 0| SC |0|
Alcatel OmniPCX Enterprise (Ethernet Real Time)
Parser: Alcatel OmniPCX Enterprise (Ethernet Real Time)
Connection: LAN. The PBX accepts a connection on TCP port 2533; the logger connects to the PBX IP address. Port 2533.
Fields extracted: 34
Overviewe
The real time accounting (or on the fly) over Ethernet has been designed to emit tickets towards an
external accounting application. These tickets can be masked on the level of the number emitted according to the type of
communication (normal, business and personal). The type of tickets (public, private, outgoing, incoming and so on) can be filtered.
The format of the tickets is identical to that of the tickets stored in compressed form (/usr4/account/*.DAT).
IMPORTANT: The use of the real time accounting is exclusive: the selection of the tickets via Ethernet prohibits the
use of the output of the tickets on V24 interface and vice-versa.
Requirements
The following software locks (license) must be available:
- V24MeteringOnFly (Number 51)
- AccountingEthernet (Number 83)
PCX settings
Configure the Accounting objects as follows:
Applications -> Accounting
Attributes:
Internal Accounting = Yes
Real Time Tickets Output = Ethernet
WARNING: Accounting filters can be set so that only the required tickets are emitted. Select among the list below only the type of tickets exploited by the external application:
ApplicationS -> Accounting
Attributes: Real-Time Tick. Outp. Parameters
Filters:
Public Outgoing PCX calls (The major outgoing ticket when PCX is stand alone)
Public Outgoing Network Calls
PCX Network Calls (2)
Private Outgoing PCX Calls
Private Outgoing Network Calls
Public Incoming PCX Calls
Public Incoming Network Calls
Private Incoming PCX Calls
Private Incoming Network Calls
Priority Incoming Calls
Data Outgoing/Incoming Calls
Public Outgoing 0 Unit Calls (1)
Non Ticketed User
PCX PCX Calls (2)
PCX Transit Calls (2)
PCX/Netw Count. Tick. Duration 0
CDR (Tickets) Management (2)
Settings from the manufacturer's documentation
Taken from Alcatel OmniPCX Enterprise - REAL TIME ACCOUNTING OVER ETHERNET, Alcatel OmniPCX Enterprise - REAL TIME ACCOUNTING OVER ETHERNET. Values are those stated in the documentation; confirm them against your firmware release.
| Setting | Documented value |
|---|---|
| SMDR TCP port | The OmniPCX Enterprise listens for the external accounting application on TCP port 2533 (the client's source port is allocated automatically). |
Switching SMDR output on, as documented
- Confirm the software locks V24MeteringOnFly (51), AccountingEthernet (83) and, if tickets must be sent back to the subscriber's node, TicketsABCNetCalls (99) are present before enabling real-time Ethernet accounting.
Record format notes
- Each accounting ticket (edition ED5.1, in effect since Release 3.2) has 46 defined attributes at fixed byte ranges, e.g. CalledNumber at bytes 006-035, StartDateTime at 442-458, Duration at 202-211.
- The CallType attribute is one of 16 coded values obtainable via the PBX 'accview -l' command, e.g. PublicNetworkOutgoingCall=0, PrivateNetworkCall=2, PublicNetworkIncomingCall=4.
- If the external application disconnects or the link breaks, the PBX buffers up to 500 tickets before it starts discarding them.
Data items: Alcatel OmniPCX Enterprise (Ethernet Real Time)
| Description | Data type | Column name |
|---|---|---|
| Called number | string | DIALED_PHONE |
| Charged number | string | EXT |
| Charged user name | string | CHARGED_USER_NAME |
| Charged cost center | string | CHARGED_COST_CENTER |
| Charged company | string | CHARGED_COMPANY |
| Charged party node | string | CHARGED_PARTY_NODE |
| Subaddress | string | SUBADDRESS |
| Caller phone | string | CALLER_PHONE |
| Call type | string | CALL_TYPE |
| Call type name | string | FLAG3 |
| Direction | string | DIRECTION |
| Cost type | string | COST_TYPE |
| End time | datetime | END_TIME |
| Charge units | string | CHARGE_UNITS |
| Cost info | string | COST_INFO |
| Call duration (s) | integer | CALL_DURATION_S |
| Call duration | datetime | CALL_DURATION |
| Trunk identity | string | TRUNK_IDENTITY |
| Trunk group identity | string | TRUNK_GROUP_IDENTITY |
| Trunk | string | TRUNK |
| Access code | string | AUTH |
| External facilities | string | EXTERNAL_FACILITIES |
| Internal facilities | string | INTERNAL_FACILITIES |
| Initial dialed number | string | INITIAL_DIALED_PHONE |
| Ring duration (s) | integer | RING_S |
| Ring duration | datetime | RING |
| Effective call duration (s) | integer | DURATION_EFFECTIVE_S |
| Redirected call indicator | string | FLAG2 |
| Call time | datetime | CALL_TIME |
| Acting extension | string | ACTING_EXT |
| Called extension node | string | CALLED_EXT_NODE |
| Calling extension node | string | CALLIG_EXT_NODE |
| Initial extension node | string | INITIAL_EXT_NODE |
| Acting extension node | string | ACTING_EXT_NODE |
Connecting the logger
Add a data source in PBX Data Logger that matches the interface named in the section for your variant (RS232, TCP client, TCP server or FTP), then open Modules → Query Parse Filter → Data query, click Setup and select the parser named there.
Alcatel-Lucent programming software
OmniPCX Enterprise is administered through Alcatel-Lucent's OmniVista management platform or the mgr console on the call server. Both come with the system from Alcatel-Lucent Enterprise or your dealer, not from AGG Software. PBX Data Logger only receives the accounting tickets those tools let you switch on.
Reports and a database
Once records arrive, the logger writes them to a text file or to any ODBC database in real time, or hands them to the PBX Reports utility for manual, scheduled and e-mailed reports with a built-in web server. See exporting call log data to a database for the database setup.
Related Alcatel systems
Alcatel 4400 PAlcatel OmniPCX Office (OHL Driver XML)
Alcatel OmniPCX Office
Other PBX SMDR formats, Alcatel to London
Alcatel 4400 (FTP)
All supported PBX systems
Note: Products and companies mentioned here are used only for definition and identification purposes and can be trademarks and/or registered trademarks of the respective companies.
Related topics: Advanced PBX Data Logger
hereCall logging Call accounting SMDR to SQL SMDR Listener Cables and signals