> 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-tmg800.md).

# VoIP Ethernet Capture TMG800

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

### Capturing using the [TMG800](/products/tmedia/tmg800.md)'s internal host

The [TMG800](/products/tmedia/tmg800.md)'s internal host can be used for capturing packets that are mirrored from the VOIP0 and/or VOIP1 physical ports. This includes RTP traffic.

#### Preparing the [Tmedia](/products/tmedia/tmedia.md) for capture

* If the traffic to be captured is on a VLAN, then an [IP Interface](/configuration/web-portal-3-3/hardware/ip-network/configuring-voip-interfaces.md) with the services "MANAGEMENT" must be created.\
  \*The IP has to be static and on the same network as the one to capture.\
  \*The virtual port assigned must be the same as the port to capture. See [IP Interface](/configuration/web-portal-3-3/hardware/ip-network/configuring-voip-interfaces.md).

#### Start Capture

You need **two** SSH sessions to capture the traffic:\
**First**, access the [Tmedia](/products/tmedia/tmedia.md) management interface using SSH. Then, access the telecom baseboard using

`telnet 172.31.1.1`

Prompt is now

`tml>`

Do command

`mv88eMonitor`

* If the output is like this (TMG800v4):

`PortDesc : voip0 voip1 sw6352 fpga mgmt0 mgmt1 eth0 eth1 host sw6321 cpu`\
`PortNumber : 0 1 2 3 4 5 6 7 8 9 10 11 12 13`\
`PortMask : 0x1 0x2 0x4 0x8 0x10 0x20 0x40 0x80 0x100 0x200 0x400 0x800 0x1000 0x2000`

Use this command to capture VoIP0 traffic (for 600 seconds or 10 minutes):

`mv88eMonitor 0x8 0x8 11 600`

Use this command to capture VoIP1 traffic:

`mv88eMonitor 0x10 0x10 11 600`

Note: We don't recommend to keep the capturing for a long time. This is only for debugging purpose.

* If the output is like this (TMG800v2):

`PortDesc : voip0 voip1 host mgmt cpu fpga`\
`PortNumber : 0 1 2 3 4 5`\
`PortMask : 0x1 0x2 0x4 0x8 0x10 0x20`

Use this command to capture VoIP0 traffic (for 600 seconds or 10 minutes):

`mv88eMonitor 0x1 0x1 2 600`

Use this command to capture VoIP1 traffic:

`mv88eMonitor 0x2 0x2 2 600`

**Second**, access the [Tmedia](/products/tmedia/tmedia.md) management interface using SSH. Prompt is now

`[root@TBxxxxxx ~]#`

To dump the content of the VOIP traffic in the file voip\_capture.cap\
if the VOIP traffic is untagged:

`tcpdump -i mgmt0 -s 1500 -w voip_capture.cap`

If the traffic is tagged, use the name of the IP interface created previously (for example vlan333)

`tcpdump -i vlan333 -s 1500 -w voip_capture.cap`

You will see something like this:

`tcpdump: listening on mgmt0, link-type EN10MB (Ethernet), capture size 1500 bytes`

#### Stop Capture

When you're ready, stop the capture by pressing **control-C** on the shell that was running tcpdump command\
You will see something like this:

`364 packets captured`\
`590 packets received by filter`\
`0 packets dropped by kernel`

* Access the telecom baseboard from the [Tmedia](/products/tmedia/tmedia.md) 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 Tmedia management port. This can be done on Windows using tools like [Filezilla](https://filezilla-project.org/) or [WinSCP](http://winscp.net/).\
The file will be located in

`/root`

### References

* [VoIP Ethernet Capture](/operations-and-support/troubleshooting/how-to/voip-ethernet-capture.md)
* [FreeSBC VoIP Ethernet Capture](/operations-and-support/troubleshooting/rtp-codecs-tones/voip-ethernet-capture-freesbc.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 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-tmg800.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.