generate a support info file, to include this capture along with the system general configuration.Retrieve the CaptureĪfter selecting “Stop”, the capture file is saved on your local disk. This is to avoid dual or stale background capture processes running in the OS, filling up the hosts’s disk space / memory. ⚠ Important : Do not click anywhere except “Stop”, or change the URL in the browser as the window will be locked until the capture is stopped by the admin. When done click on “Stop” to end the capture. Reproduce the issue as quickly as possible, since traffic capture consumes resources and disk space.Wireshark on Windows and tcpdump on Linux, remotely start capturing on the server machine. Click on “Capture” to start a new network traffic recording.

💡 Tip : Linux allows you to also capture from the localhost (lo), useful while debugging SBC and tunnel connections. If a capture driver is installed, an interface selector is visible for selecting a specific interface to record from, or select all system interfaces (IPv6 tunneling adapters are excluded).Go to “Dashboard” > “Activity Log” in the 3CX Management Console.If Wireshark cannot be detected this message is shown.įor Linux-based setups, tcpdump is automatically installed while installing or updating 3CX. Prerequisitesįor Windows-based installs, it remains the administrator's obligation to install Wireshark on the OS running 3CX. This allows for live packet captures that are saved in PCAP format which can then be attached to a generated SupportInfo file or can be directly downloaded. In the 3CX network, captures can be triggered directly from the Management Console.

Tcpdump wireshark