> 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/other-pages/hardware-and-lines/enabling-voip-bonding.md).

# Enabling VoIP Bonding

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

1- Access the telecom baseboard of the Tmedia unit:

> a. For TMG800 and TMG3200, access the unit using SSH, then connect to the telecom baseboard using telnet. telnet 172.31.1.1 b. For other platforms, such as TMP800, TMP6400 and TMG7800, connect to the telecom baseboard directly using telnet and the eth0 IP address. telnet 10.3.2.21

2- In the baseboard prompt, use the set\_voip0bonding shell command to enable VoIP Bonding. set\_voip0bonding <0|1> \[IP\_To\_Ping] \[Ping\_Timeout] \[Retries]

> Where: `<0|1>` selects if the feature is enabled (1 to enable). When the feature is enabled, the Ethernet PHY states are polled periodically to discover which port is available. `[IP_To_Ping]` is the IP address to send ICMP echo requests to verify if a logical path is available. When no response is received within the requested timeout after the specified number of retries, the port is considered temporarly unusable and the other VoIP port is used instead. `[Ping_Timeout]` is the ICMP echo request timeout in milliseconds `[Retries]` is the number of ICMP echo request retries to send before doing a switchover. Examples: `set_voip0bonding 1` `set_voip0bonding 1 10.3.10.187 1000 1` `set_voip0bonding 1 123.45.67.89 2500 3`

3- Reboot the unit (note: this causes downtime). reboot

4- (optional) After the reboot, access the telecom baseboard again and verify that the VoIP Bonding was successfully enabled: print\_bonding


---

# 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/other-pages/hardware-and-lines/enabling-voip-bonding.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.