> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/voip-ethernet-capture-tsbc5000.md).

# VoIP Ethernet Capture TSBC5000

#### ***Applies to version(s): v2.10***

### Capturing using the internal host of the TSBC5000 internal host

The internal host of the TSBC5000 can be used for capturing packets that are mirrored from the VOIP0 and/or VOIP1 physical ports. This includes RTP traffic.

#### Start Capture

You need **two** SSH sessions to capture the traffic:

**Step 1**

* Access the TSBC5000 management interface using SSH. Then, access the telecom baseboard using telnet 172.31.1.1 Prompt is now: 0/tbgw>
* To capture VoIP0 traffic, enter: mv88eMonitor 0x4 0x4 8 600
* To capture VoIP1 traffic, enter: mv88eMonitor 0x8 0x8 8 600 In the example, the duration is 600 seconds. This will capture traffic for 10 minutes.

Note: We do not recommend to keep capturing for a long time. This is only used for debugging purpose.

**Step 2**

* Access the TSBC5000 management interface using SSH

start tbx\_cli\_tools\_remote \[root\@TB016635 \~]# tbx\_cli\_tools\_remote

* connect to tbrouter (The following is displayed:) Available remote hosts to control (TBX\_GW\_PORT=12358, local IPs 172.16.0.1 / 172.18.0.1). Press corresponding letter to control: a : TB016634.tbrouter b : TB016635.gateway c : TB016635.logtrace d : TB016635.stream\_server e : TB016635.tboam\_app f : TB016635.tbrouter <------------tbrouter g : TB016635.tbsnmpagent h : TB016635.tbsyslog i : TB016635.tbuctwriter j : TB016635.toolpack\_engine k : TB016635.toolpack\_sys\_mgr l : TB016635.web\_server
* Select the tbrouter application. (Letter 'f' in the above example)
* Once you have access to the tbrouter application, press 'p' Capture circular buffer size (nb of packets)? : 50000 <-- set the number of packets to capture Capture mode (1:In 2:Out 4:Monitor) (ex: 3=In+out) : 4 <-- Select 4 VLAN id (list, -1:All) (ex:151, 152, 153, 154) : -1 Convert DSA tags to VLAN tags : Yes Capture only firewall-protected VLANs : Yes

Press Enter to start the capture.

#### Stop Capture

Press 'P' (capital letter) to stop the capture.

* Access the telecom baseboard from the TSBC5000 using telnet. telnet 172.31.1.1
* Stop the capture mv88eMonitor 0 0 0

#### Download Capture

To download the voip\_capture.cap file, use SSH secure copy ("sftp") to the TSBC5000 management port. This can be done on Windows using tools like [Filezilla](https://filezilla-project.org/) or [WinSCP](http://winscp.net/).

The file location of the capture is: /lib/tb/toolpack/tbrouter/pcap

### References

* [VoIP Ethernet Capture](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/voip-ethernet-capture/README.md)
* [FreeSBC VoIP Ethernet Capture](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/voip-ethernet-capture-on-a-prosbc/README.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/voip-ethernet-capture-tsbc5000.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.