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
| Item | AudioCodes Mediant 1000 |
|---|---|
| Interface | LAN. The PBX sends records to the logger PC; the logger listens on TCP port 514. |
| Port | 514 |
| Parser to select | AudioCodes Mediant 1000 |
| Fields extracted | 30 |
| Other AudioCodes systems | VoIP 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.
SBC CDR Format
8. Open the SBC CDR Format page.
9. Define fields as showed on fig. 3 (the column order is important).
Gateway CDR Format
10. Open the Gateway CDR Format page.
11. Define fields as showed on fig. 4 (the column order is important).
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).

2. Configure the TCP settings as shown below.

514
514
Selecting the correct parser for AudioCodes Mediant 1000

AudioCodes Mediant 1000
AudioCodes Mediant 1000
Data items
| Description | Data type | Column name |
|---|---|---|
| Call type | string | CALL_TYPE |
| Call time | datetime | CALL_TIME |
| Connect time | datetime | CONNECT_TIME |
| Release time | datetime | RELEASE_TIME |
| Ring | datetime | RING |
| Call Identifier | string | FLAG6 |
| Call Originator | string | FLAG5 |
| Direction | string | DIRECTION |
| Trunk | string | TRUNK |
| Ext | string | EXT |
| Dialed IP | string | DIALED_PHONE |
| Caller phone | string | CALLER_PHONE |
| Source URL | string | FLAG1 |
| Destination URL | string | FLAG2 |
| Call duration (sec) | integer | CALL_DURATION_S |
| Call duration | datetime | CALL_DURATION |
| Termination Reason | string | FLAG7 |
| Caller Display ID | string | FLAG3 |
| Callee Display ID | string | FLAG4 |
| Termination Reason | string | TERM_REASON |
| Termination Reason Categoty | string | TERM_REASON_CAT |
| IP Group Name | string | IP_GROUP |
| SRD ID and Name | string | SRD_ID |
| SIP interface ID | string | SIP_ID |
| Proxy Interface ID | string | PROXY_ID |
| IP Profile ID | string | IP_PROFILE |
| Medial Realm ID | string | MEDIA_REALM |
| Direct Media ID | string | DIRECT_MEDIA |
| SIP Termination Reason | string | SIP_TERM_REASON |
| SIP Termination Description | string | SIP_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.
Related topics: Advanced PBX Data Logger
hereCall logging Call accounting SMDR to SQL SMDR Listener Cables and signals



