# Packet Trace

Use this diagnostic tool to intercept and log a time-stamped sequence of packets passing over the network or part of the network. You would typically run the "packet trace" to log traffic for a limited period of time, such as during a phone call.

Only one packet trace file is retained on the system. Every time you run the utility, the new file overwrites the existing file.

## Filter Options

When entering filter options, you can use letters, numbers, and spaces, as well as boollean operators such as OR and AND. You cannot use dashes, hyphens, underscores or special characters such as &, |, or !.

Examples:

- udp and port 5060 (to trace all SIP packets)

- host 1.2.3.4 (to trace all packets, including RTP, from a particular host)

- host 1.2.3.4 and port 5060 (to trace SIP packets from a particular host)

To run a packet trace:

1. On the MBG main page, click the Administration tab , and then click Diagnostics.

2. Beside Packet trace, click Run.

3. In the Filter options field, enter options to limit the trace (for example, enter "udp and port 5060" to restrict the capture to SIP traffic).

4. To capture a TCP dump of unencrypted MiNET, SIP and webRTC signaling traffic, select Enable concurrent signalling capture. The file can be downloaded and used for troubleshooting purposes.

5. To start the trace, click Run.

6. To stop the trace, click Stop.

The packet trace files are captured in PCAP format and listed at the bottom of the screen.

7. To download a PCAP file, click it.

8. Click Open to view the file immediately or Save to store it for viewing in a network protocol analyzer such as Wireshark.

Note: The Disk space remaining field displays the amount of free disk space on the server. If you allow a packet trace to continue indefinitely, it will be automatically shut off when disk space is reduced to 500 MB.