> 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/use-cases/use-cases-ip-network-configuration.md).

# Use Cases: IP Network Configuration

> **Applies to:** Tmedia 3.0, 3.2, 3.3

The following uses cases provide guideance for the most common IP network configurations using the Web Portal.

**Select a use case to learn about its configuration.**

| IP Network Configuration One subnet, Two IP Addresses, Untagged                                                 | IP Network Configuration Two subnets, One IP per subnet, untagged                                                         | IP Network Configuration Two VLAN, Three IP Addresses, tagged                                                                                                   |
| --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![UseCase OneSubTwoIpUntagged 0](https://docs.telcobridges.com/w/images/d/d8/UseCase_OneSubTwoIpUntagged_0.png) | ![UseCase TwoSubnetsTwoIpsUntagged 0](https://docs.telcobridges.com/w/images/e/ee/UseCase_TwoSubnetsTwoIpsUntagged_0.png) | ![UseCase TwoVlandsThreeIpsVoipAndManagementPortsUsed 0](https://docs.telcobridges.com/w/images/f/f9/UseCase_TwoVlandsThreeIpsVoipAndManagementPortsUsed_0.png) |

| IP Network Configuration Two VLAN, Three IP Addresses, all through VoIP ports, tagged                                                   | IP Network Configuration Two tagged VLAN, Four IP Addresses, all through VoIP ports, SIP/RTP on separate IP                                                                   | IP Network Configuration Two VLAN: tagged VLAN for management, radius and H.248, Untagged VLAN for SIP/RTP/Sigtran on separate IP, all through VoIP ports                                                                   |
| --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![UseCase TwoVlansThreeIpsVoipPortsTagged 0](https://docs.telcobridges.com/w/images/b/be/UseCase_TwoVlansThreeIpsVoipPortsTagged_0.png) | ![TwoTagged VLAN Four IP all throughVoIP SIPRTPonseparate IP 0](https://docs.telcobridges.com/w/images/8/8b/TwoTagged_VLAN_Four_IP_all_throughVoIP_SIPRTPonseparate_IP_0.PNG) | ![UseCase ManagentRadiusH248onTaggedVlan ViaVoipport SIPRTPSigtranSepaateIPUntagged 0](https://docs.telcobridges.com/w/images/1/1a/UseCase_ManagentRadiusH248onTaggedVlan_ViaVoipport_SIPRTPSigtranSepaateIPUntagged_0.PNG) |

| IP Network Configuration Two VLAN: tagged VLAN for management, sigtran, radius and H.248, Untagged subnet for SIP/RTP/ on separate IP, all through VoIP ports                                                               | IP Network Configuration Two VLAN: tagged VLAN for Sigtran, radius and H.248, Untagged VLAN for SIP/RTP on separate IP, all through VoIP ports, Management local only                                                                                               | IP Network Configuration Four VLAN: tagged VLAN 100 for management, VLAN 200 for SIP/RTP, VLAN 300 for Sigtran, VLAN 400 for Radius, all through VoIP ports                 |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![UseCase ManagentSigtranRadiusH248onTaggedVlan ViaVoipport SIPRTPSepaateIPUntagged 0](https://docs.telcobridges.com/w/images/1/14/UseCase_ManagentSigtranRadiusH248onTaggedVlan_ViaVoipport_SIPRTPSepaateIPUntagged_0.png) | ![UseCase SigtranRadiusH248onTaggedvLanallthroughVoIPportsUntaggedSIPRTPonseparateIPManagementLocalonly 0](https://docs.telcobridges.com/w/images/b/b7/UseCase_SigtranRadiusH248onTaggedvLanallthroughVoIPportsUntaggedSIPRTPonseparateIPManagementLocalonly_0.PNG) | ![UseCase SeparatedTrafficNoH248FourVLanallthroughVoipports 0](https://docs.telcobridges.com/w/images/9/94/UseCase_SeparatedTrafficNoH248FourVLanallthroughVoipports_0.PNG) |

| IP Network Configuration Four VLAN: tagged VLAN 100 for management, VLAN 200 for Sigtran, VLAN 300 RTP, VLAN 400 for H.248, all through VoIP ports                                          | IP Network Configuration One VLAN, One IP Addresses, all tagged traffic one IP (TMG800 only)                                                | IP Network Configuration One IP Addresses except for management, all tagged traffic, local only (TMG800 only)                                                                       |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![UseCase SeparatedTrafficH248SigtranRTPFourIPsallthroughVoip ports 0](https://docs.telcobridges.com/w/images/f/f8/UseCase_SeparatedTrafficH248SigtranRTPFourIPsallthroughVoip_ports_0.PNG) | ![UseCase OneVLanallTaggedOne IP TMG800only 0](https://docs.telcobridges.com/w/images/3/3a/UseCase_OneVLanallTaggedOne_IP_TMG800only_0.PNG) | ![UseCase OneIPexceptforManagementallTaggedLocalonlyTMG800 only 0](https://docs.telcobridges.com/w/images/d/d6/UseCase_OneIPexceptforManagementallTaggedLocalonlyTMG800_only_0.PNG) |

| IP Network Configuration Three VLAN: VLAN 100 for management through ETH ports, VLAN 200 for Sigtran and H.248, VLAN 300 for RTP through VoIP ports |
| --------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![UseCase maneth h248 sig RTP](https://docs.telcobridges.com/w/images/a/a5/UseCase_maneth_h248_sig_RTP.png)                                         |


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/use-cases/use-cases-ip-network-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.