bg

AudioCodes Mediant 1000 SMDR setup and CDR format

This page shows how to get call records out of the AudioCodes Mediant 1000 into Advanced PBX Data Logger: the connection settings, the parser to select and the 30 fields the logger extracts for reports or a database. The settings apply to our logger; other call accounting software may expect a different configuration.

Quick facts

ItemAudioCodes Mediant 1000
InterfaceLAN. The PBX sends records to the logger PC; the logger listens on TCP port 514.
Port514
Parser to selectAudioCodes Mediant 1000
Fields extracted30
Other AudioCodes systemsVoIP PBX, softswitch and gateway CDR formats

Configuring CDR

Note: For CDR reporting, you must also enable the Syslog feature.

1. Open the Syslog Settings page (Troubleshoot menu > Troubleshoot tab > Logging folder > Syslog Settings).
2. From the Enable Syslog drop-down list, select Enable.
3. Specify the Syslog Server IP address 0.0.0.0.
5. Specify the Syslog Server Port number (default: 514).
6. Open the Call Detail Record Settings page.
7. Under the CDR Reports group:
7.1. Specify the IP address of your computer or server with Advanced PBX Data Logger in the CDR Server IP Address field.
7.2. Select End Call in CDR Report Level and Medial CDR Report Level drop-down lists.
7.3. Select Disable in CDR Syslog Sequence Number.

Syslog settings

CDR settings

SBC CDR Format

8. Open the SBC CDR Format page.
9. Define fields as showed on fig. 3 (the column order is important).

SBC CDR settings

Gateway CDR Format

10. Open the Gateway CDR Format page.
11. Define fields as showed on fig. 4 (the column order is important).

Gateway CDR settings

Settings from the manufacturer's documentation

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

Record format notes

  • CDR syslog messages comply with RFC 3164 and are identified by Facility 17 (local1) and Severity 6 (Informational).
  • SBC signaling CDRs are sent at three points in the SIP dialog: on the INVITE (CALL_START), on the 200 OK (CALL_CONNECT), and on the BYE (CALL_END); for billing the CALL_END record is usually sufficient.
  • In addition to Syslog, CDRs can be sent to a RADIUS server; CDR history can also be viewed directly on the device for both Gateway and SBC calls.
  • The device's syslog output is pipe-delimited and tabular: a header line lists the field names, followed by a line of matching values, e.g. for SBC signaling CDRs.
  • "Latched RTP IP"/"Latched RTP Port" report the remote address/port the device latched onto via NAT-traversal RTP latching, and are included by default in SBC media (MEDIA_END) CDRs under the raw titles LatchedRtpIp/LatchedRtpPort.

Configuring Advanced PBX Data Logger as a TCP server

Advanced PBX Data Logger should be configured to the TCP server mode and listen on 0.0.0.0:514 (see below). The IP address 0.0.0.0 allows receiving data from all network connections on your computer. The port number should match the value from the SMDR settings in your AudioCodes Mediant 1000.

1. Add a new configuration with the TCP data source (if you didn't it before).

TCP/IP Data Interface

2. Configure the TCP settings as shown below.

TCP Server Mode for AudioCodes Mediant 1000

514

514

Selecting the correct parser for AudioCodes Mediant 1000

Parser Selection For PBX Data Logger

AudioCodes Mediant 1000

AudioCodes Mediant 1000

Data items

DescriptionData typeColumn name
Call typestringCALL_TYPE
Call timedatetimeCALL_TIME
Connect timedatetimeCONNECT_TIME
Release timedatetimeRELEASE_TIME
RingdatetimeRING
Call IdentifierstringFLAG6
Call OriginatorstringFLAG5
DirectionstringDIRECTION
TrunkstringTRUNK
ExtstringEXT
Dialed IPstringDIALED_PHONE
Caller phonestringCALLER_PHONE
Source URLstringFLAG1
Destination URLstringFLAG2
Call duration (sec)integerCALL_DURATION_S
Call durationdatetimeCALL_DURATION
Termination ReasonstringFLAG7
Caller Display IDstringFLAG3
Callee Display IDstringFLAG4
Termination ReasonstringTERM_REASON
Termination Reason CategotystringTERM_REASON_CAT
IP Group NamestringIP_GROUP
SRD ID and NamestringSRD_ID
SIP interface IDstringSIP_ID
Proxy Interface IDstringPROXY_ID
IP Profile IDstringIP_PROFILE
Medial Realm IDstringMEDIA_REALM
Direct Media IDstringDIRECT_MEDIA
SIP Termination ReasonstringSIP_TERM_REASON
SIP Termination DescriptionstringSIP_TERM_DESC

Sample record

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

<142> |3     |73f65b00-c3f1dfb7-3b6c2a-c102010a@10.1.2.193      |08:51:51.025  UTC Thu Jan 17 2019  |08:52:05.858  UTC Thu Jan 17 2019  |08:52:18.312  UTC Thu Jan 17 2019  |12   |RMT  |021xxxxxxxx@10.1.2.193                   |081xxxxxxxx@10.1.127.19                  |GWAPP_NORMAL_CALL_CLEAR                 |8ebcc2:9:472xxxx        |UDP             |OPERATOR LT 16                                     |
<142> |3     |150xxxxxxxxxxxxxxxxxxx@10.18.11.10                |08:51:51.027  UTC Thu Jan 17 2019  |08:52:05.857  UTC Thu Jan 17 2019  |08:52:18.315  UTC Thu Jan 17 2019  |12   |LCL  |021xxxxxxxx@10.1.2.191                   |081xxxxxxxx@10.18.11.9                   |GWAPP_NORMAL_CALL_CLEAR                 |8ebcc2:9:472xxxx        |UDP             |OPERATOR LT 16                                     |
<142> |3     |106xxxxxxxxxxxxxxxxxxx@10.18.11.10                |08:45:35.766  UTC Thu Jan 17 2019  |08:45:41.963  UTC Thu Jan 17 2019  |08:52:38.228  UTC Thu Jan 17 2019  |416  |LCL  |021xxxxxxxx;ext=user@example.com |082xxxxxxxxx@10.18.11.9                  |GWAPP_NORMAL_CALL_CLEAR                 |8ebcc2:9:472xxxx        |UDP             |Name Surname  ABM                                  |
<142> |3     |f2bf526d-a18b-4f0e-a114-1b6ab215f8f3              |08:45:35.764  UTC Thu Jan 17 2019  |08:45:41.965  UTC Thu Jan 17 2019  |08:52:38.232  UTC Thu Jan 17 2019  |416  |RMT  |+622xxxxxxxxx;ext=user@example.com.i|+082xxxxxxxxx@10.1.127.19                |GWAPP_NORMAL_CALL_CLEAR                 |8ebcc2:9:472xxxx        |TCP             |Name Surname  ABM                                  |
<142> |3     |c27b1e8f-0f11-404f-9132-a7b989e2e788              |08:51:12.986  UTC Thu Jan 17 2019  |08:51:14.915  UTC Thu Jan 17 2019  |08:52:45.556  UTC Thu Jan 17 2019  |90   |RMT  |+622xxxxxxxxx;ext=user@example.com|+021xxxxxxxx@10.1.127.19                 |GWAPP_NORMAL_CALL_CLEAR                 |8ebcc2:9:472xxxx        |TCP             |Receptionist CJ                                    |
<142> |3     |107xxxxxxxxxxxxxxxxxx@10.18.11.10                 |08:51:12.988  UTC Thu Jan 17 2019  |08:51:14.913  UTC Thu Jan 17 2019  |08:52:45.558  UTC Thu Jan 17 2019  |90   |LCL  |021xxxxxxxx;ext=user@example.com  |021xxxxxxxx@10.18.11.9                   |GWAPP_NORMAL_CALL_CLEAR                 |8ebcc2:9:472xxxx        |UDP             |Receptionist CJ                                    |
<142> |3     |893xxxxxxxxxxxxxxxxxx@10.18.11.10                 |08:52:21.963  UTC Thu Jan 17 201
...

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 AudioCodes systems

AudioCodes Gateway (Extended)
Asterisk Fonality (CSV)
AudioCodes SBC
AudioCodes VoIP Gateway
VoIP PBX, softswitch and gateway CDR formats
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.