RADIUS, TAPI, CSV and hotel interface call record sources

Advanced PBX Data Logger includes 10 parsers for RADIUS, TAPI, CSV and hotel interface 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 105 fields in total that these parsers extract for PBX Reports or a database. The settings apply to our logger; other call accounting software may expect a different configuration.

Hotel and PMS interfaces

In a hotel the phone system usually hands call records to a property management system rather than to a printer or a plain SMDR port, so the record arrives in a PMS interface format instead of a PBX one. Two of those formats are on this page. FIAS, the Micros Fidelio Interface Application, is carried either over a serial port or over TCP; HOBIC is the older hotel billing record. Both are parsers in the logger, selected the same way as a PBX format, so the logger can read the records for billing or reporting alongside the PMS or in its place.

Where the phone system is an IP-PBX rather than a hotel switch, call records more often arrive as RADIUS accounting or through TAPI, and those parsers are here too. If the PBX in the building is a Panasonic, NEC or Samsung system sending ordinary SMDR, its own setup page applies instead — start from the list of supported systems.

Systems on this page

• Australia Mobile (CSV) · Serial or TCP, 8 fields
• DVC (Digital Voice Corp) · Serial or TCP, 9 fields
• FIAS RS232 (Micros Fidelio Interface Application over RS232) · Serial or TCP, 11 fields
• FreeRADIUS (Accounting Log) · Serial or TCP, 12 fields
• HOBIC (I,II,2001) · Serial or TCP, 10 fields
• Komutel Custom Format · Serial or TCP, 12 fields
• RADIUS (Accounting Server) · Serial or TCP, 12 fields
• TAPI data parser · Serial or TCP, 14 fields
• Tapit CSV · Serial or TCP, 9 fields
• Tekelec T6000 (CSV) · Serial or TCP, 8 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.

Australia Mobile (CSV)

Parser: Australia Mobile (CSV)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 8

Data items: Australia Mobile (CSV)

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

039xxxxXXX,040xxxxxxx          ,2006-06-30 09:11:07.000,2006-06-30 09:11:08.000,30/06/2006 09:11:07 AM - 040xxxxxxx - Fixed to mobile,Mobile,Fixed to mobile
039xxxxXXX,041xxxxxxx          ,2006-06-30 09:30:12.000,2006-06-30 09:39:03.000,30/06/2006 09:30:12 AM - 041xxxxxxx - Fixed to mobile,Mobile,Fixed to mobile
039xxxxXXX,039xxxxxxx          ,2006-06-30 09:53:40.000,2006-06-30 09:55:06.000,30/06/2006 09:53:40 AM - 039xxxxxxx - Local Call,Local,Local Call

DVC (Digital Voice Corp)

Parser: DVC (Digital Voice Corp)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 9

Data items: DVC (Digital Voice Corp)

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

   10:34 0:09.5     9   9           896-1783       1408                        
                                                                                                                                 
   10:35 0:00.0 I                       2431       37                          
                                                                                                                                 
   10:36 0:00.7     9 *82     1-507-xxx-xxxx       7478                        
                                                                                                                                 

FIAS RS232 (Micros Fidelio Interface Application over RS232)

Parser: FIAS RS232 (Micros Fidelio Interface Application over RS232)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 11

Settings from the manufacturer's documentation

Taken from FIAS TN WG3PFO, FIAS records. Values are those stated in the documentation; confirm them against your firmware release.

Record format notes

• FIAS messages begin with a two-character message type followed by |-delimited two-character-name/value fields, e.g. LR|RIPS|FLRNPTP#TADATISO|.
• LD (check-in) and LR (check-out) carry room number (RN), and PS posts call charges with date (DA, YYMMDD), time (TI, HHMMSS), duration (DU) and price/meter-pulse (MP) fields.

Data items: FIAS RS232 (Micros Fidelio Interface Application over RS232)

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

LA|DA140401|TI213720|
DR|DA140401|TI213723|
PS|RN403|PTC|P#7|TA49000|DA140330|TI143654|PCI|CTInternational|

FreeRADIUS (Accounting Log)

Parser: FreeRADIUS (Accounting Log)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 12

Data items: FreeRADIUS (Accounting Log)

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

 Tue May 21 00:00:03 2013
            Acct-Session-Id = "1/3/0/3_00FA2701"
            Framed-Protocol = PPP
            Framed-IP-Address = 198.51.100.4
            Cisco-AVPair = "ppp-disconnect-cause=Received LCP TERMREQ from peer"
            User-Name = "user"
            Acct-Authentic = RADIUS
            Cisco-AVPair = "connect-progress=LAN Ses Up"
            Cisco-AVPair = "nas-tx-speed=141xxxxxxx"
            Cisco-AVPair = "nas-rx-speed=141xxxxxxx"
            Acct-Session-Time = 384
            Acct-Input-Octets = 4497
            Acct-Output-Octets = 7951
            Acct-Input-Packets = 64
            Acct-Output-Packets = 64
            Acct-Terminate-Cause = User-Request

HOBIC (I,II,2001)

Parser: HOBIC (I,II,2001)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 10

Settings from the manufacturer's documentation

Taken from hobic, Hobic2. Values are those stated in the documentation; confirm them against your firmware release.

Record format notes

• HOBIC record layout: <STX> sequence(4) space hotel-ID(3) space date(5) space extension(6, left justified) space time(5, 24h) space duration-in-minutes(4) space price(7) space number-dialed(16, left justified) call-type-flag(L/F) <ETX> [BCC].
• HOBIC: sequence number is always '123W' and the dialed number is not hyphenated. HOBIC II: sequence number rolls 000-999 and the number is hyphenated. HOBIC 2001: same as HOBIC II but the L/F call-type flag is fixed at 13 characters past the start of the dialed digits (truncating longer numbers) instead of appearing right after the digits.
• Besides the RS-232 Ack/Nak link, HOBIC records can also be delivered over IP or via file-drop (deleting the file signals successful delivery).

Data items: HOBIC (I,II,2001)

Komutel Custom Format

Parser: Komutel Custom Format
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 12

Data items: Komutel Custom Format

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

   031xxxxxxxxx:01:150xxxx   2229               2236            2229         1
   031xxxxxxxxx:00:010xxxx   2285               2500            2285         1
   031xxxxxxxxx:00:040xxxx   9542               2267           V9542         1

RADIUS (Accounting Server)

Parser: RADIUS (Accounting Server)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 12

RADIUS (Accounting Server)

The logger can implement a basic RADIUS accounting server. This server is capable of gathering and storing accounting billing information from RADIUS compatible PBXs. It records various details, including session duration, calling and called numbers, types of services used, and more. The number of logged values varies depending on the PBX model.

1. Configure your PBX to send CDR records to a computer with our logger. Specify the IP address of the computer with our logger in the PBX settings. The default TCP port for RADIUS accounting data is 1813.

Data items: RADIUS (Accounting Server)

TAPI data parser

Parser: TAPI data parser
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 14

Data items: TAPI data parser

Tapit CSV

Parser: Tapit CSV
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 9

Data items: Tapit CSV

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

UserID,Extension,CallDate,CallTime,CallLength,AreaCode,PhoneNum,UserLastName,UserFirstName
36,228,1/25/2006 0:00,12/30/1899 16:57:22,12/30/1899 0:00:25,845,184xxxxxxxx,Name     ,RJ
1,200,1/25/2006 0:00,12/30/1899 16:58:22,12/30/1899 0:01:27,,,Name ,Name  
19,224,1/25/2006 0:00,12/30/1899 17:01:31,12/30/1899 0:02:40,201,120xxxxxxxx,Name      ,Name 

Tekelec T6000 (CSV)

Parser: Tekelec T6000 (CSV)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 8

Data items: Tekelec T6000 (CSV)

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

CallOID,BillingNum,CallDateTime,Type,Duration,ConnectNum,Location,
000C0.95C9.B5A8.43EB.63DD.0FBD0 ,469xxxxxxx    ,2/9/2006 9:46:37 AM,IN,0.9,(21x) xxx-xxxx      ,GRANDPRARI,TX ,
000C0.95C9.B5A8.43EB.8556.05420 ,469xxxxxxx    ,2/9/2006 12:09:26 PM,IN,9.1,(21x) xxx-xxxx      ,DALLAS,TX     ,
000C0.95C9.B5A8.43EB.92B3.3B2C0 ,469xxxxxxx    ,2/9/2006 1:06:27 PM,DL,13.1,(94x) xxx-xxxx      ,NAME  ,TX     ,

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 RADIUS, TAPI, CSV and hotel interface systems with their own setup pages

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.