ShoreTel 6, 7 and 9 CDR formats

Advanced PBX Data Logger includes 3 parsers for ShoreTel 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 41 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.

Systems on this page

• Shoretel 6 · Serial or TCP, 14 fields
• Shoretel 7 · Serial or TCP, 14 fields
• Shoretel 9 · Serial or TCP, 13 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.

Shoretel 6

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

Settings from the manufacturer's documentation

Taken from ShoreTel - 7 9 CDR. Values are those stated in the documentation; confirm them against your firmware release.

Record format notes

• Legacy CDR record layout and CDR-MMDDYY.log naming (see shoretel-7 finding) is described as applying to releases prior to Shoreline3 3.1k (folder 'Call Records 1') as well as 3.1k and later ('Call Records 2'), so the same field layout likely spans the 6/7/9 parser variants.

Data items: Shoretel 6

Sample record

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

IDN   ,CallID     ,StartTime            ,StartTimeMS,EndTime              ,EndTimeMS,CallNote,BillingCode,FriendlyBillingCode,Locked,Extension,Duration               ,CallType,WorkgroupCall,LongDistance,DialedNumber,CallerID    ,Archived,
188961,209xxxxxxx ,7/25/2007 3:23:07 AM ,122        ,7/25/2007 3:23:28 AM ,184      ,        ,           ,                   ,True  ,4180     ,12/30/1899 12:00:21 AM,1        ,False        ,False       ,4203        ,4180        ,True,
188962,200xxxxxxx ,7/25/2007 3:23:41 AM ,28         ,7/25/2007 3:24:02 AM ,106      ,        ,           ,                   ,True  ,4180     ,12/30/1899 12:00:21 AM,1        ,False        ,False       ,4203        ,4180        ,True,
188963,192xxxxxxx ,7/25/2007 5:09:21 AM ,997        ,7/25/2007 5:09:45 AM ,637      ,        ,           ,                   ,True  ,5200     ,12/30/1899 12:00:23 AM,2        ,False        ,False       ,7500        ,O           ,True,

Shoretel 7

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

Settings from the manufacturer's documentation

Taken from ShoreTel - 7 9 CDR. Values are those stated in the documentation; confirm them against your firmware release.

Switching SMDR output on, as documented

1. Set the CDR retention period from Director: Reporting -> Options.

Record format notes

• Legacy CDR record is column-based, space-separated and ends with CR/LF: Call ID (col 1, len 10), Date (col 12, len 8, mm/dd/yyyy), Time (col 23, right-justified, hh:mm:ss), Extension (col 32, len 10), Duration (col 49, len 16, hh:mm:ss), Call Direction (col 58, 0=incoming/1=outgoing/2=tandem-in/3=tandem-out), Dialed Number (col 60, left-justified), Caller ID (col 77), Trunk Member/Group (col 94/99), Account Code (col 103).
• It is the third-party reporting application's own responsibility to delete the daily CDR log files after processing; the server does not purge them.
• If the WAN is down, a distributed server buffers CDR data up to two hours before discarding it and logging an NT event-log error.

Data items: Shoretel 7

Sample record

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

7     ,428xxxxxx  ,003xxxxxxxxxxxxxa8e001xxxxxadce,5/22/2007 3:37:38 PM ,497        ,5/22/2007 3:37:40 PM ,404      ,         ,          ,                   ,1     ,1257     ,12/30/1899 12:00:01 AM,1       ,0            ,0           ,1256        ,1257        ,0       ,0       ,           ,              ,           ,1       ,7  , 
8     ,199xxxxxxx ,002xxxxxxxxxxxxxa8b001xxxxxadc6,5/22/2007 3:37:58 PM ,935        ,5/22/2007 3:37:59 PM ,607      ,         ,          ,                   ,1     ,1256     ,12/30/1899            ,1       ,0            ,0           ,1257        ,1256        ,0       ,0       ,           ,              ,           ,1       ,8  ,
9     ,190xxxxxxx ,002xxxxxxxxxxxxxa8b001xxxxxadc6,5/22/2007 3:38:06 PM ,810        ,5/22/2007 3:38:08 PM ,106      ,         ,          ,                   ,1     ,1256     ,12/30/1899 12:00:01 AM,1       ,0            ,0           ,1257        ,1256        ,0       ,0       ,           ,              ,           ,1       ,9  ,

Shoretel 9

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

Settings from the manufacturer's documentation

Taken from ShoreTel - 7 9 CDR. Values are those stated in the documentation; confirm them against your firmware release.

Record format notes

• Same legacy CDR-MMDDYY.log format and field layout as documented for ShoreTel 7 is the basis for this file title ('ShoreTel - 7_9 CDR'), implying it also covers release 9.

Data items: Shoretel 9

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.

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.