> 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/tmedia-documentation/other-pages/use-cases/ip-network-configuration-use-case-one-subnet-two-ip-addresses-untagged.md). # IP Network Configuration Use Case:One subnet, Two IP Addresses, Untagged Worked IP network configuration for a Tmedia system on one untagged subnet with two IP addresses - one for management, one for VoIP. Tmedia 2.9 to 3.2. > **Applies to:** Tmedia 2.9, 2.10, 3.0, 3.2 ### One subnet, Two IP Addresses, Untagged ![UseCase OneSubTwoIpUntagged 0](https://docs.telcobridges.com/w/images/d/d8/UseCase_OneSubTwoIpUntagged_0.png) | | Local IPs | Remote IPs | | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | In this example, here are the IPs used: \* Management on mgmt0: 192.168.4.10 \* VoIP on voip0/voip1 (bonded): 192.168.4.20 | \* Radius server: 192.168.4.200 \* H.248 MGC: 192.168.4.210 \* Remote Sigtran endpoint IP: 192.168.4.100 \* Remote SIP endpoint IP: 192.168.4.110 \* Remote RTP endpoint IP: 192.168.4.120 | | | | | Configure IP Network A | Configure IP Network B | | | \*Subnet A is accessed through MGMT0 \*MGMT0 network interface modification requires the use of the tbchangeip shell script \*Use [tbchangeip](/tmedia-documentation/operations-and-support/troubleshooting/software/troubleshooting-toolpack/change-management-ip-address.md) with the following parameters: \*\***IP Address**: 192.168.4.10 \*\***Netmask**: 255.255.255.0 \*\***Default gateway**: 192.168.4.1 | Subnet B is untagged and bonded over VOIP0 and VOIP1 ports. \*Delete voip0 and voip1 virtual port \*Create [VP\_VOIP virtual port](/tmedia-documentation/configuration/web-portal-3-3/hardware/ip-network/configuring-virtual-port.md): \*\***Name**: VP\_VOIP \*\***vLanId**: Untagged \*\***Physical Ports**: voip0, voip1 \*Delete voip0 and voip1 IP Address \*Create [VOIP\_ADDRESS IP Address](/tmedia-documentation/configuration/web-portal-3-3/hardware/ip-network/configuring-voip-interfaces.md): \*\***Name**: VOIP\_ADDRESS \*\***Virtual Ports**: VP\_VOIP \*\***IP Address**: 192.168.4.20 \*\***Netmask**: 255.255.255.0 \*\***Services**: RTP, SIP, SIGTRAN | | | | Configure SIP | Configure SIGTRAN | Configure H.248 | Configure RADIUS | | \*[Configure SIP](/tmedia-documentation/configuration/web-portal-3-3/protocol-stack.md) \*\*IP range parameters: \*\*\***Name**: PORT\_RANGE\_VOIP \*\*\***IP Interface**: VOIP\_ADDRESS \*\*\***Minimum Port**: 20000 \*\*\***Maximum Port**: 30000 \*\*SIP transport server parameters: \*\*\***Port**: 5060 \*\*\***IP Interface**: VOIP\_ADDRESS \*\*SIP NAP parameters: \*\*\***Proxy Address**: 192.168.4.110 \*\*\***Port Range**: PORT\_RANGE\_VOIP | \*[Configure SIGTRAN](/tmedia-documentation/configuration/web-portal-3-3/protocol-stack.md) \*For Local Service Access Point (SAP), use voip0/voip1 bonded (192.168.4.20) \*For the remote service use 192.168.4.100 | \*When you [Configure H.248](/tmedia-documentation/configuration/web-portal-3-3/protocol-stack.md), set the following: \*\***Local IP Address and Public IP Address**: 192.168.4.10 \[Public IP or NAT public IP] | \*When you [Configure RADIUS](/tmedia-documentation/configuration/web-portal-3-3/cdr.md), set the following: \*\***Source IP interface**: Any \*\***Radius -> Radius Server** \*\***Public IP Address**: Empty | --- # 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://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/use-cases/ip-network-configuration-use-case-one-subnet-two-ip-addresses-untagged.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.