> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/configuration/web-portal-3-3/troubleshooting/voip-ethernet-capture/voip-ethernet-capture-tmg7800.md).

# VoIP Ethernet Capture TMG7800

|                          |               |             |
| ------------------------ | ------------- | ----------- |
| This article applies to: | **Product**   | **Version** |
| Tmedia                   | 3.0, 3.2, 3.3 |             |

#### Physical Setup

To do a VoIP capture with a [TMG7800](/products/tmedia/tmg7800.md), it is required to:

* Connect one of the VoIP Ethernet port (VOIP0 or VOIP1) to a laptop with a straight ethernet connection. The laptop must support a gigababit connection
* Use [Wireshark](http://www.wireshark.org/) on the laptop.

Once the physical setup is ready. It is possible to start capturing the RTP.

#### Preparing Tmedia for Capture

* Access the telecom unit ([TMG7800-TE](/products/tmedia/tmg7800.md), [TMG7800-DS3](/products/tmedia/tmg7800.md) or [TMG7800-STM1](/products/tmedia/tmg7800.md)) you want to capture using telnet.

`telnet [eth0 IP address of the telecom unit]`

For example

`telnet 172.16.123.45`

The prompt will now be:

`0/tbgw>`

* Start [Wireshark](http://www.wireshark.org/) to capture the Ethernet packets with the connected laptop.

#### Start the Capture

* Do one of the following command to capture packets according to your setup:

For capturing all Ethernet packets that go through VoIP0 and copy them to VoIP1

`mv88eMonitor 0x4 0x4 3 600`

For capturing all Ethernet packets that go through VoIP1 and copy them to VoIP0

`mv88eMonitor 0x8 0x8 2 600`

* Stop [Wireshark](http://www.wireshark.org/) and save the captured data to a file

#### To stop the Capture

`mv88eMonitor 0 0 3`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/configuration/web-portal-3-3/troubleshooting/voip-ethernet-capture/voip-ethernet-capture-tmg7800.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.