Aastra Intelligate and MX-ONE MDFP15 formats
Advanced PBX Data Logger includes 3 parsers for Aastra Intelligate and MX-ONE systems. This page gathers them in one place. For each system you will find how the call records reach the logger, the parser to select, and the 74 fields in total that these parsers extract for PBX Reports or a database. Of these, 3 over TCP client; the rest are identified by their record layout and can arrive over a serial port or a LAN connection. The settings apply to our logger; other call accounting software may expect a different configuration.
Systems on this page
- Aastra Intelligate IP SMDR · TCP client, 23 fields
- Aastra Intelligate (tab) · TCP client, 39 fields
- Aastra MX-ONE (MDFP15 format) · TCP client, 12 fields
Connecting the logger
Add a data source in PBX Data Logger that matches the interface named in each section: RS232 for a serial SMDR port, TCP client when the PBX accepts connections, TCP server when the PBX pushes records to the logger, or FTP for systems that write CDR files. Then open Modules → Query Parse Filter → Data query, click Setup and select the parser named in the section. The general steps are shown on the SMDR listener page; every other supported system is listed on the supported PBX index.
Aastra Intelligate IP SMDR
Parser: Aastra Intelligate IP SMDR
Connection: LAN. The PBX accepts a connection on TCP port 1080; the logger connects to the PBX IP address.
Fields extracted: 23
OIP server
The call data is stored as a file on the OIP server if so selected during the user-defined installation of the OIP server. In the standard settings a new file is written daily in the directory ...\aastra\oip\tax.
The files are created in .csv format. The file name is taxdata-jjjj-mm-dd.tax, with <jjjj-mm-dd> representing year-month-day. The Call Logging settings can be made in the OIP service Call Logging Driver.
In this case you can create the "File" data source in our software and process "tax" files.
Call logging over IP
The PBX can send the SMDR directly to the Advanced PBX Data Logger. Look at the settings below (Aims, AMS for Aastra 400).

Settings from the manufacturer's documentation
Taken from Aastra Intelligate - syd-0200 en System Functions and Features as of I7.9. Values are those stated in the documentation; confirm them against your firmware release.
Switching SMDR output on, as documented
- Select the OIP output format so the PBX sends call data to the OIP server, which is the basis for the IP SMDR/tax file output.
Record format notes
- The OIP format is an extension of the PC5 output format with additional fields, not a wholly separate design.
- The base PC5 record is fixed-width ASCII, begins with a Horizontal Tab (0x09) and ends with CR LF (0x0D 0x0A) -- fields are not comma- or tab-separated internally.
Data items: Aastra Intelligate IP SMDR
| Description | Data type | Column name |
|---|---|---|
| User number | string | FLAG1 |
| Cost center number | string | FLAG2 |
| Call type | string | CALL_TYPE |
| Direction code | string | DIRECTION_TYPE |
| Direction | string | DIRECTION |
| Extension | string | EXT |
| Type of network access | string | NET_ACCESS_TYPE |
| Type of network access | string | NET_ACCESS |
| Call handling code | string | CALL_HANDLING_TYPE |
| Call handling | string | CALL_HANDLING |
| Call time | datetime | CALL_TIME |
| Call duration | datetime | CALL_DURATION |
| Call duration (s) | integer | CALL_DURATION_S |
| Cost | float | COST |
| Call metering pulses | string | FLAG4 |
| Channel group/Trunk | string | TRUNK |
| Caller phone | string | CALLER_PHONE |
| Caller phone 2 | string | FLAG3 |
| Dialed phone | string | DIALED_PHONE |
| Ring duration (s) | integer | RING_S |
| Ring duration | datetime | RING |
| Sequence number | string | FLAG5 |
| Serial number | string | FLAG6 |
Sample record
As delivered by the system; phone numbers, names and public addresses are masked.
ticketId serialId sequenceId pbxId userId subscriber name account direction destination type handling startDate startTime timeToAnswer duration charge pulses pbx nodeId board port channelGroup callerId1 callerId2 destination1 destination2 publicPbxId publicNodeId publicBoard publicPort publicChannelGroup pbxHops origPBXId origSubscriber origUserId tickets complete ticketDate ticketTime callId terminalId 37 43 41 1 4 6633 Office 5370 IP 1 2 3 2 11.1.2012 11:5:53 4 108 0.0 0 1 0 17 2 0 6631 6633 0 0 0 0 0 1 1 6633 4 1 1 11.1.2012 11:8:3 0 2 38 44 42 1 5 6635 1 2 3 2 11.1.2012 11:6:12 9 88 0.0 0 1 0 17 2 0 6631 6635 0 0 0 0 0 1 1 6635 5 1 1 11.1.2012 11:8:6 0 4 39 45 46 1 5 6635 1 2 3 3 11.1.2012 11:9:0 0 0 0.0 0 1 0 17 2 0 6631 6635 0 0 0 0 0 1 1 6635 5 1 1 11.1.2012 11:9:18 0 0
Aastra Intelligate (tab)
Parser: Aastra Intelligate (tab)
Connection: LAN. The PBX accepts a connection on TCP port 1080; the logger connects to the PBX IP address.
Fields extracted: 39
OIP server
The call data is stored as a file on the OIP server if so selected during the user-defined installation of the OIP server. In the standard settings a new file is written daily in the directory ...\aastra\oip\tax.
The files are created in .csv format. The file name is taxdata-jjjj-mm-dd.tax, with <jjjj-mm-dd> representing year-month-day. The Call Logging settings can be made in the OIP service Call Logging Driver.
In this case you can create the "File" data source in our software and process "tax" files.
Call logging over IP
The PBX can send the SMDR directly to the Advanced PBX Data Logger. Look at the settings below (Aims, AMS for Aastra 400).

Settings from the manufacturer's documentation
Taken from Aastra Intelligate - syd-0200 en System Functions and Features as of I7.9. Values are those stated in the documentation; confirm them against your firmware release.
Record format notes
- Table 95 (PC5 format) lists each field's name, data format, justification/padding, length and byte offset, e.g. the date-of-start field (DATE) is yymmdd, 6 characters, at offset 28.
- The three-digit 'sort character' field encodes call direction/network as digit x, network-access type as digit y, and call handling as digit z.
- Digit y of the sort character distinguishes business vs private vs cost-centre network access and PISN transit calls.
- PC5/OIP fields are fixed length: numeric fields are right-justified and zero-padded, text fields left-justified and space-padded, to the field's defined length.
Data items: Aastra Intelligate (tab)
| Description | Data type | Column name |
|---|---|---|
| Ticked ID | integer | TICKED_ID |
| Serial ID | integer | SERIAL_ID |
| Sequence ID | integer | SEQUNCE_ID |
| PBX ID | integer | PBX_ID |
| User ID | integer | USER_ID |
| Subscriber | string | SUBSCRIBER |
| Name | string | NAME |
| Account | string | ACC |
| Direction | string | DIRECTION |
| Destination | integer | DEST |
| Destination name | string | DEST_NAME |
| Call type | string | CALL_TYPE |
| Call type name | string | CALL_TYPE_NAME |
| Handling | integer | HANDLING |
| Handling name | string | HANDLING_NAME |
| Call date | datetime | CALL_DATE |
| Call time | datetime | CALL_TIME_ONLY |
| Call date and time | datetime | CALL_TIME |
| Ring (sec) | integer | RING_S |
| Ring | datetime | RING |
| Call duration (sec) | integer | CALL_DURATION_S |
| Call duration | datetime | CALL_DURATION |
| Cost | float | COST |
| Pulses | integer | PULSES |
| PBX | string | FLAG1 |
| Node ID | string | FLAG2 |
| Board | string | FLAG3 |
| Port | string | FLAG4 |
| Extension | string | EXT |
| Channel group | integer | FLAG5 |
| Caller phone | string | CALLER_PHONE |
| Caller phone 2 | string | CALLER_PHONE2 |
| Dialed phone 1 | string | DIALED_PHONE1 |
| Dialed phone | string | DIALED_PHONE |
| PBX hops | integer | PBX_HOPS |
| Orig subscriber | string | FLAG6 |
| Orig user ID | integer | ORIG_USER_ID |
| Tickets | integer | TICKETS |
| Complete | integer | COMPLETE |
Aastra MX-ONE (MDFP15 format)
Parser: Aastra MX-ONE (MDFP15 format)
Connection: LAN. The PBX accepts a connection on TCP port 2112; the logger connects to the PBX IP address.
Fields extracted: 12
Call logging for MX-ONE TSE over IP
The PBX can send the SMDR directly to the Advanced PBX Data Logger. You need to configure call info output as:
General format
callinfo_output_set -output 5 -lim 1 -type tcp -subtype general -server 192.168.1.80 -port 2112 - format "FORMAT" -eol NL -record call -localtime
ASB501 format
callinfo_output_set -output 0 -lim all -type tcp -subtype asb501 -server "192.168.1.80" -port 2112 -format -eol CRNL -record call -localtime
MDFP15 format
callinfo_output_set -output 0 -lim all -type tcp -subtype mdfp15 -server "192.168.1.80" -port 2112 -format -eol CRNL -record call -localtime
The following command starting the SMDR stream:
callinfo_status_set -state on -lim all -output OUT_NO
E.g.
callinfo_status_set -state on -lim all -output 0
where FORMAT - the necessary format name (see docs for the PBX);
OUT_NO - the output number from the callinfo_output_set command;
192.168.1.80 - IP address of a remote server, where our software was installed;
2112 - TCP IP port number on the server.
Data items: Aastra MX-ONE (MDFP15 format)
| Description | Data type | Column name |
|---|---|---|
| Call date and time | datetime | CALL_TIME |
| Call duration (s) | integer | CALL_DURATION_S |
| Call duration | datetime | CALL_DURATION |
| Call type | string | CALL_TYPE |
| Direction | string | DIRECTION |
| Access code 1 | integer | FLAG4 |
| Access code 2 | integer | FLAG5 |
| CO | string | TRUNK |
| Ext | string | EXT |
| Dialed phone | string | DIALED_PHONE |
| Caller phone | string | CALLER_PHONE |
| Forwarded from | string | FLAG2 |
Sample record
As delivered by the system; phone numbers, names and public addresses are masked.
1515 00040 M 98699 985xxxxxxx 77709 25 011xxxxxx 1515 00025 FI 2998 915xxxxxxx 25 2976 1515 00023 FI 2998 964xxxxxxx 25 2987
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 Aastra Intelligate and MX-ONE systems with their own setup pages
Aastra 470 (PC5 format)Aastra MX-ONE (ASB501 format)
Aastra MX-ONE
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