This capture would include the packet transmitted via the Ethernet of Yeastar device. The packets are captured before the firewall of Yeastar device takes effect.
The key of logging is to ensure the issue has been included in the log files.
S-Series & Cloud PBX
Go to the menu: Maintenance>Troubleshooting> Ethernet Capture Tool
Then follow the procedure:
- Choose both Interface (if there is only LAN, choose LAN), click 'Start' button.
- Start to make a call or start to replicate the issue.
- If issue is replicated, end the call or stop you action; if issue not replicated, continue till you replicate.
- Click 'Stop' button and download the package
- Post us the package
GSM gateway
Go to the menu: Status> Reports> Troubleshooting> Ethernet Capture Tool
Then follow the same steps as S-Series.
U-Series & N-Series
Go to the menu: Reports> Logs> Capture Tool> Packet Capture Tool
Then follow the procedure:
- Choose correct interface (default is eth0 - LAN, and eth1 presents WAN), click 'Start' button.
- Start to make a call or start to replicate the issue.
- If issue is replicated, end the call or stop you action; if issue not replicated, continue till you replicate.
- Click 'Stop' button and download the package
- Post us the package
Other Gateways (TA, TB, TE, TGv2)
Go to the menu: Status> Reports> Packet Tool or Status> Reports> System logs> Packet Capture Tool
Then follow the procedure:
- Click 'Start' button.
- Start to make a call or start to replicate the issue.
- If issue is replicated, end the call or stop you action; if issue not replicated, continue till you replicate.
- Click 'Stop' button and download the package
- Post us the package
0 Comments