> 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/use-cases/transcoding-unit-configuration-use-case-baremetal-and-virtual-machine.md). # Transcoding Unit Configuration Use Case: Baremetal and Virtual Machine > **Applies to:** SBC 3.1, 3.3 ### Transcoding Unit Configuration | | Perequisites | | | | | | | | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ------------------- | ------- | ------------------- | -------------- | | \*ProSBC Host Configuration | | Network device name | Purpose | Network device role | Network Config | | | | | mgmt0 | Management port | mgmt | Untagged | | | | | | | wan0 | SBC port | LAN/WAN | Tagged 1650 (or other) | | | | | | | lan0 | SBC port | LAN/WAN | Tagged 1651 (or other) | | | | | | | ctrl0 | control port | ctrl0 | Tagged 750 | | | | | | | ctrl1 | control port | ctrl1 | Tagged 751 | | | | | | | trans | transcoding port | LAN/WAN | Tagged 752 **NOTES:** \* The 'Network device name' for transcoding must be **trans**. To have redundancy, the **trans** port bonding (using trans0 and trans1 physical ports) needs to be created at initialization time. \* For baremetal, the **trans** port bonding, using trans0 and trans1 physical ports must be bonded at initialization time. You can look here for reference: [Initial Configuration](https://prosbcdocs.telcobridges.com/) (Search for "Bonding") \* For virtual machines, the virtual ports trans0 and trans1 are bonded in the Hypervisor layer of the virtual machine (optional) and the **tran** interface is presented to the guest (the ProSBC). \*Hardware Unit - TB002177 is the TSBC-HW-TRANS unit in the below setup. | | Network device name | Purpose | Network device role | Network Config | | voip0 | transcoding port | trans | Tagged 752 (Bonded with voip1) | | | | | | | voip1 | transcoding port | trans | Tagged 752 (Bonded with voip0) | | | | | | | eth0 | control port | ctrl0 | Untagged PVID 750 \*\* | | | | | | | eth1 | control port | ctrl1 | Untagged PVID 751 \*\* | | | | | | | | Configure IP Network for trans | | | | | | | | | \*Create [vp\_trans virtual port](/configuration/web-portal-3-3/hardware/ip-network/configuring-virtual-port.md): \*\***Name**: vp\_trans \*\***Ethernet Ports**: trans \*\***VLAN name**: vlan\_752 \*\***VLAN id**: 752 \*Create [trans IP Address](/other-pages/ip-network/toolpack-configuring-ip-interfaces.md): \*\***Name**: trans \*\***Service to use**: RTP \*\***Host VLAN**: vp\_trans:vlan\_752 \*\***IP address**: 192.168.152.1 \*\***Netmask**: 255.255.255.0 | | | | | | | | | | Add transcoding unit | | | | | | | | | | \*Show [transcoding unit](/other-pages/ip-network/show-the-hardware-units-menu.md) \*Add [TB002177 transcoding unit](/other-pages/ip-network/adding-transcoding-unit.md) === Transcoding unit network configuration === | | Configure IP Network for voip ports | | | | | | | | \*Modify [voip virtual port](/configuration/web-portal-3-3/hardware/ip-network/configuring-virtual-port.md): \*\***Name**: vp\_voip \*\***Untagged**: unselect \*\***VLAN id**: 752 \*\***Physical Ports**: Use voip0 and voip1 (ctrl-click) \*Modify [voip IP Address](/configuration/web-portal-3-3/hardware/ip-network/configuring-voip-interfaces.md): \*\***Interface Name**: voip \*\***Service to use**: RTP \*\***Virtual port**: TB002177:vp\_voip \*\***IP address**: 192.168.152.10 \*\***Netmask**: 255.255.255.0 | | | | | | | | | --- # 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/use-cases/transcoding-unit-configuration-use-case-baremetal-and-virtual-machine.md?ask=&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.