Collecting Debug Recording Messages; Debug Capturing On Physical Voip Interfaces - AudioCodes E-SBC User Manual

CHAPTER 58 Syslog and Debug Recording

Collecting Debug Recording Messages

To collect debug recording packets, use the open source packet capturing program, Wireshark. To
analyze AudioCodes debug recording protocol, proprietary Wireshark plug-in files are required.
●
●
➢
To use Wireshark to view debug recording messages:
1. Install Wireshark on your computer (which can be downloaded from
https://www.wireshark.org).
2. Download AudioCodes proprietary Wireshark plug-in files according to the type of installation
(32-bit or 64-bit) from https://www.audiocodes.com/library/firmware.
3. Copy the downloaded plug-in files to the "plugin" directory of the Wireshark installation.
4. Start Wireshark.
5. In the filter field, type "acdr" to view the debug recording messages.
The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording
message, as shown below:
The source IP address of the messages is always the OAMP IP address of the device.

Debug Capturing on Physical VoIP Interfaces

You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN
tagged packets). The captured traffic can be saved in a PCAP-format file (suitable for Wireshark) to
a TFTP (default) or an FTP server. The generated PCAP file is in the Extensible Record Format
(ERF). The maximum file size of debug captures that can be saved to the device is 20 MB100 MB.
To capture traffic on physical VoIP interfaces, use the following CLI commands:
■ Starts physical VoIP debug capture:
# debug capture voip physical eth-lan
# debug capture voip physical start
The default debug recording port is 925. You can change the port in Wireshark (Edit
menu > Preferences > Protocols > AC DR).
The plug-in files are per major software release of Wireshark. For more information,
contact the sales representative of your purchased device.
Mediant 1000 Gateway & E-SBC | User's Manual
- 1054 -