VoIP PBX, softswitch and gateway CDR formats

Advanced PBX Data Logger includes 13 parsers for VoIP PBX, softswitch and gateway 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 270 fields in total that these parsers extract for PBX Reports or a database. Of these, 1 over TCP server, 1 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

• 3COM NBX (XML, v6) · Serial or TCP, 11 fields
• AudioCodes Gateway (Extended) · Serial or TCP, 79 fields
• AYC IPcts · Serial or TCP, 9 fields
• NCH AXON · Serial or TCP, 10 fields
• Opticon IP · Serial or TCP, 13 fields
• Quintum Tenor · Serial or TCP, 11 fields
• Snom ONE · TCP server, 10 fields
• Sphere VOIP Softswitch · Serial or TCP, 9 fields
• Splicecom Maximiser · TCP client, 42 fields
• Talkswitch · Serial or TCP, 10 fields
• Telepo 3 · Serial or TCP, 38 fields
• Telnyx CDR (CSV) · Serial or TCP, 17 fields
• VOISpeed · Serial or TCP, 11 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.

3COM NBX (XML, v6)

Parser: 3COM NBX (XML, v6)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 11

Data items: 3COM NBX (XML, v6)

Sample record

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

<CDR>
<B0>2008/01/02</B0>     // date
<B1>2</B1>		// sequence number
<B2>1</B2>		// call type 0 - internal, 1 - outgoing, 2 incoming
<B7>07:53:33</B7>	// start time
<B8>07:54:06</B8>	// stop time
<B9>32</B9> 		// ??
<B11>Local</B11>	// Description
<B13>1</B13>
<B14>204071</B14>
<B3><P1>1703</P1><P2>Name Surname  </P2><P4>Terminal</P4><P11>526xxxx</P11><P5>ORIG</P5><P8>004</P8><P9>Name Surname  </P9><P10>952xxxxx</P10></B3>
<B4><P1>7292</P1><P2>Trunk</P2><P4>PRI Channel</P4><P11>1703</P11><P5>TERM</P5></B4>
</CDR>

AudioCodes Gateway (Extended)

Parser: AudioCodes Gateway (Extended)
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 79

The parser is degisned for the following exact fields order. The configuration process is similar to AudioCodes Mediant 1000.

Call ID
Session ID
Report Type
Leg ID
Endpoint Type
Call Orig
Source IP
Destination IP
Remote IP
Source Port
Dest Port
Remote Port
Call Duration
Termination Side
Termination Raison
Setup Time
Connect Time
Release Time
Redirect Reason
IP Group Name
Transport Type
Termination Reason Category
IP Profile Name
Media Realm Name
SIP Termination Reason
SIP Termination Description
Caller Display ID
Callee Display ID
SIPInterface Name
Termination Side Yes No
ProxySet Name
Call Succes
Coder Type
Local Packet Loss
Local Round Trip Delay
Local Jitter
Remote Packet Loss
Remote Round Trip Delay
Remote Jitter
Local RTP IP
Local RTP Port
Remote RTP IP
Remote RTP Port
RTP IP DiffServ
Local MOS CQ
Latched RTP IP
Latched RTP Port
Coder Transcoding
MC Name
Source URI
Destination URI
Source URI Before Manipulation
Destination URI Before Manipula
Redirect URI
Redirect URI Before Manipulatio
Source Username
Destination Username
Source Username Before Manipula
Destination Username Before Man
Source Host
Destination Host
Source Host Before Manipulation
Destination Host Before Manipul
Remote SIP User Agent

Settings from the manufacturer's documentation

Taken from AudioCodes CDR Field Description. Values are those stated in the documentation; confirm them against your firmware release.

Record format notes

• "Latched RTP IP"/"Latched RTP Port" report the remote address/port the device latched onto via the NAT-traversal RTP latching mechanism, included by default in SBC media CDRs.
• Proxy Set name and SIP Interface name fields are each strings of up to 40 characters.
• The Coder Transcoding field records whether coder transcoding occurred during the SBC call.

Data items: AudioCodes Gateway (Extended)

AYC IPcts

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

Data items: AYC IPcts

Sample record

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

26/11/05 14:10 UNA 01  801    201          012xxxxxxxx 01    550066 00:00:28
27/11/05 12:16 UNA 01  801    201          012xxxxxxxx 01    550066 00:00:27
27/11/05 16:34 UNA 01  801    201          012xxxxxxxx 01    550066 00:00:27

NCH AXON

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

Data items: NCH AXON

Sample record

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

2006-12-11,22:12:39,00:21,00:13,"111","sip:110@192.168.15.100"
2006-12-11,22:12:07,01:21,01:11,"sip:305xxxxxxx@10.0.5.24","701"
2006-12-11,22:15:19,01:04,00:54,"110","sip:930xxxxxxxx@192.168.15.100"

Opticon IP

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

Data items: Opticon IP

Sample record

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

9095 100   007 00:00:11 17/10/07 11:27 I RING 00:02                                           *
9089 110   007 00:00:28 17/10/07 11:22 t                                                      *
9089 102   007 00:01:13 17/10/07 11:23 t                                                       

Quintum Tenor

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

Data items: Quintum Tenor

Sample record

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

5260,228xxxxxxx,50,200xxxxxxxxxxx,200xxxxxxxxxxx,200xxxxxxxxxxx,-, 10.9.1.199, 10.9.1.198,-,1,1,1,2,-,-,-,0,0,0,221xxxx,-,5272,5149,
5261,-,0,200xxxxxxxxxxx,-,200xxxxxxxxxxx,16, 10.9.1.199,-,-,1,0,1,10,-,-,-,0,0,0,-,-,5275,-, 
5262,-,0,200xxxxxxxxxxx,-,200xxxxxxxxxxx,16, 10.9.1.199,-,-,1,0,1,17,-,-,-,0,0,0,-,-,5276,-,

Snom ONE

Parser: Snom ONE
Connection: LAN. The PBX sends records to the logger PC; the logger listens on TCP port 7777.
Fields extracted: 10

Configuring the IP PBX

1. Within the administration console set the settings from the following figure. Replace <ip-addr> and <port> with the real IP address and port of a computer where Data Logger is located. For example: cdr:192.168.1.101:7777

2. In the format template field you must specify the format: $w$2o$5x$5e$15c$5A$5d

The format can be changed using the link http://localhost/reh_status.htm?save=save&cdr_format=$w$2o$5x$5e$15c$5A$5d

SMDR Format String

The following table can help you customize the SMDR record format. Please, note that if you'll customize the format our software will not decode incoming data. The parser is designed foe the default format "$w$2i$5x$5e$15c$5A$5d".

Data items: Snom ONE

Sample record

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

201xxxxxxxxxxx  100xxxxxxxxxx   88
201xxxxxxxxxxx     811xxxxxxx  101
201xxxxxxxxxxx  102       102   37

Sphere VOIP Softswitch

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

Data items: Sphere VOIP Softswitch

Sample record

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

2      ,181xxxxx,outside caller ,pstn           ,303xxxxxxx       ,VM Port             ,svm          ,12@spheremgc1  ,Name Surname          ,ext              ,6994               ,0      ,3     ,118xxxxxxx,1       ,Trunk:1 ,         ,         ,              ,
3      ,181xxxxx,outside caller ,pstn           ,303xxxxxxx       ,VM Port             ,svm          ,12@spheremgc1  ,Name Surname          ,ext              ,6994               ,0      ,3     ,118xxxxxxx,40      ,Trunk:1 ,         ,         ,              ,
2      ,181xxxxx,outside caller ,pstn           ,303xxxxxxx       ,VM Port             ,svm          ,12@spheremgc1  ,Name Surname          ,ext              ,6994               ,0      ,3     ,118xxxxxxx,40      ,Trunk:1 ,         ,         ,              ,

Splicecom Maximiser

Parser: Splicecom Maximiser
Connection: LAN. The PBX accepts a connection on TCP port 4001; the logger connects to the PBX IP address.
Fields extracted: 42

Changing the Call Logging Password

The Call Logging Password configurable in PBX can be used to protect access:

1. From the Management information list select System
2. Beside the Call Logging Password field click on Change
3. In the Script Prompt enter the password required
4. Select OK
5. Re-enter your password to confirm the change
6. Select OK
7. Submit the change

No logging output will occur without the Call Logging password being sent Advanced PBX Data Logger. So, you should activate the data query plugin and specify the password (fig. 2,3)

Settings from the manufacturer's documentation

Taken from Splicecom Maximiser call log format v3.2.2. Values are those stated in the documentation; confirm them against your firmware release.

Switching SMDR output on, as documented

1. Immediately after connecting, send the configured Call Logging Password (newline-terminated, in a single block/packet); no log output occurs until the password is received.
2. Set the Call Logging Password in the PBX's Management information list under System, using the Change link next to the Call Logging Password field.

Record format notes

• The documented record has 36 named comma-separated fields ending with B_OnBehalfOfNumber and B_OnBehalfOfNumber, terminated by a newline.
• A separate log entry is output for each target leg of a call, and only once that leg has been disconnected; ConnectedTime is 0 if the leg never connected.
• ConnectedStat is coded 0=none, 1=connected, 2=sent to voicemail.
• TransferedCall is coded 0=not transferred, 1=primary, 2=secondary, 3=abandoned, 4=park, 5=un-park.

Data items: Splicecom Maximiser

Sample record

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

14/10/2013 12:59,A Person   ,Modules.FXO1.Virtual,A Person   ,214,,,821xxxxx,30260,23340,,,1,,,A Person   ,f5f20300-72dc-5b12-8567-0007d90094c4,0,,0,5410,5410,14/10/2013 11:59:12.516,,1,A Person   ,,821xxxxx,0,,,,0,0,1011,0,,,,821xxxxx
14/10/2013 13:08,Accounting,Modules.FXO2.Virtual,Accounting,212,,,889xxxxx,14860,7890,,,1,,,Accounting,79e00d00-cbde-5b12-8567-0007d90094c4,0,,0,5450,5450,14/10/2013 12:08:58.770,,1,Accounting,,889xxxxx,0,,,,0,0,1011,0,,,,889xxxxx
14/10/2013 13:10,Accounting,Modules.FXO2.Virtual,Accounting,212,,,889xxxxx,78190,71190,,,1,,,Accounting,967xxxxx-e8de-5b12-8567-0007d90094c4,0,,0,5490,5490,14/10/2013 12:10:30.489,,1,Accounting,,889xxxxx,0,,,,0,0,1011,0,,,,889xxxxx

Talkswitch

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

Data items: Talkswitch

Sample record

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

I	16035	01	01/20/2006	08:49	00:00:13	RCO	               	               	11	               	               
I	16036	01	01/20/2006	08:59	00:00:01	RCO	               	               	11	               	               
T	16036	02	01/20/2006	08:59	00:01:44	E111	               	               	11	               	               

Telepo 3

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

Data items: Telepo 3

Sample record

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

2,+463xxxxxxxx,132xxxxxxxxxx,132xxxxxxxxxx,0,0,0,0,0,0,0,0
2,+468xxxxxxxx,132xxxxxxxxxx,132xxxxxxxxxx,0,0,0,0,0,0,0,0
2,300,132xxxxxxxxxx,132xxxxxxxxxx,0,0,0,0,0,0,0,0

Telnyx CDR (CSV)

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

Data items: Telnyx CDR (CSV)

Sample record

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

Originating Number,Originating City,Originating State,Originating Lata,Originating OCN,Originating LRN,Full Terminating number,Terminating number,Call forwarding number,Terminating City,Terminating State,Terminating Lata,Terminating OCN,Terminating LRN,Route,On-net,Start Timestamp(UTC),Answer Timestamp(UTC),End Timestamp(UTC),Call duration,Billable time,Connection Id,Cost,Rate,Direction,Hangup code,Hangup cause,PDD(sec),Tags,Sip call-id,Account id,Unique CDR ID, Call UUID
172xxxxxxxx,DENVER,CO,DENVER CO,078F,720xxxxxxx,720xxxxxxx,172xxxxxxxx,,AURORA,CO,DENVER CO,320A,720xxxxxxx,Intra,FALSE,7/27/2017 14:43,7/27/2017 14:44,7/27/2017 14:44,4,6,5.89117E+17,0.0003,0.0022,outbound,sip:200,NORMAL_CLEARING,0.08,,kaqIJ36DNdC7RM0QpL3R6Q..,2b32052a-3026-4eb8-afdd-1d48aca5e9a0,0200fefa-72da-11e7-a161-02420a0f060e,020100a6-72da-11e7-976e-02420a0f060e
172xxxxxxxx,DENVER,CO,DENVER CO,078F,720xxxxxxx,901xxxxxxx,190xxxxxxxx,,SOMERVILLE,TN,MEMPHIS TENNESSEE,516C,901xxxxxxx,Inter,FALSE,7/27/2017 13:44,7/27/2017 13:45,7/27/2017 13:45,2,6,5.89117E+17,0.0003,0.0021,outbound,sip:200,NORMAL_CLEARING,0.1,,9SyPO2UAeqLhi5tiXefQNg..,2b32052a-3026-4eb8-afdd-1d48aca5e9a0,c663bcfa-72d1-11e7-b10c-02420a0f070e,c663be42-72d1-11e7-ae40-02420a0f070e
172xxxxxxxx,DENVER,CO,DENVER CO,078F,720xxxxxxx,719xxxxxxx,171xxxxxxxx,,NAME  CITY,CO,COLORADO SPRINGS CO,6010,,Intra,FALSE,7/27/2017 15:04,7/27/2017 15:04,7/27/2017 15:05,7,12,5.89117E+17,0.0003,0.0015,outbound,sip:200,NORMAL_CLEARING,0.2,,quM8zhnm0V1ZBRLJXBxizw..,2b32052a-3026-4eb8-afdd-1d48aca5e9a0,e529e8fd-72dc-11e7-9dea-02420a0f060e,e529ea80-72dc-11e7-8f0b-02420a0f060e

VOISpeed

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

Data items: VOISpeed

Sample record

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

ISDN,LAN,missing,250,08/03/2006 15.09.48,00.00.45,missing,489798,489798,17
ISDN,LAN,unknown,250,08/03/2006 15.11.14,00.00.29,missing,489798,489798,18
LAN,ISDN,251,012xxxxxxxx,23/03/2006 10.10.36,00.01.07,251,901xxxxxxxxx,901xxxxxxxxx,1705

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 VoIP PBX, softswitch and gateway 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.