AudioCodes Mediant MSBR Series, Troubleshooting Manual, Page: 15 / 36

Configuration Note 2. Capturing Packets
Version 7.2 15 Troubleshooting the MSBR
2.3 Capturing Voice on Physical Interfaces
Voice-CPU has two interfaces:

LAN switch

VLAN 4001 connected to the Data-CPU: This interface is monitored using the
“debug capture data physical eth-lan vlan4001” command.
Sometimes you may need to debug or analyze traffic coming from the internal LAN switch
directly to the Voice-CPU, by-passing the Data-CPU. For example, an IP Phone that is
located on the same VLAN as the Voice-CPU communicates directly without passing through
the Data-CPU, while the same IP Phone that is located on a different VLAN on the LAN side,
passes through the Data-CPU first (Data-CPU refers to the system Router).
Debug capture voice provides the capability of monitoring the traffic that goes directly to the
Voice-CPU.
Debug capture physical is applied on all wire levels. With multiple logical interfaces (VLANs),
you can monitor them all using this methodology.
2.3.1 Monitoring VoIP Physical Interface Example
The same concept is applied in “debug capture voip physical” as in “debug capture data
physical” command. You need to:

Select the interface to be monitored

Select the target to send the files (TFTP/FTP/USB)

Trigger the Start flag

Wait for relevant traffic to be captured

Trigger the Stop flag, and specify the destination IP address if using the TFTP protocol
debug capture voip physical eth-lan
debug capture voip physical start
…..capture….
debug capture voip physical stop <tftp server ip-adders>