> 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/configuration/web-portal-3-3.md).

# Configuration — Web Portal 3.3 and 4.0

**Introduction** This Web Portal Tutorial provides you with a scenario-based approach to configuring and monitoring the status of [Tmedia](/tmedia-documentation/products/tmedia/tmedia.md) and [Tsig](/tmedia-documentation/products/tsig/tsig.md) systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific application.

**Prerequisites** [Tmedia](/tmedia-documentation/products/tmedia/tmedia.md) or [Tsig](/tmedia-documentation/products/tsig/tsig.md) devices must be installed as described in their respective [installation guides](/tmedia-documentation/products/tmedia/installation/product-installation.md). Tmedia and Tsig devices are shipped with the Tmedia Web Portal pre-installed. Tmedia and Tsig system communication is established with the control network.

**Web Portal Categories** Web Portal configuration and status topics are grouped into the following major categories. It is recommended that you follow this order.

## System

* Host Role
* Access and User Management
* Database Backup
* SNMP
* Configuration
* Services
* Telephony Services
* Package Upgrade
* Upload Software License
* Statistics
* Audit Logs

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/system.md) [(Status)](/tmedia-documentation/configuration/web-portal-3-3/system/status.md)

## Hardware

* New Hardware
* TDM Network
* System Clock
* IP Network
* NAT

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/hardware.md) [(Status)](/tmedia-documentation/configuration/web-portal-3-3/hardware/status.md)

## Protocol Stack

* SCTP
* SS7
  * MTP2
  * MTP3
  * ISUP
  * SCCP
  * TCAP
  * SIGTRAN
  * M2UA
  * M2PA
  * M3UA
* ISDN
* IUA
* CAS
* SIP
* H.248

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/protocol-stack.md) [(Status)](/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/status.md)

## CDR

* Text CDR
* RADIUS [(Status)](/tmedia-documentation/configuration/web-portal-3-3/cdr/status.md)

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/cdr.md)

## Fax

* FAX passthrough (silence suppression)
* FAX T.38
* FAX passthrough (NSE)
* FAX passthrough (VBD)

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/fax.md)

## Call Route

* Static Route
* Routing Script
* Label Routing
* RADIUS Authorization and Authentication [(Status)](/tmedia-documentation/configuration/web-portal-3-3/cdr/status.md)

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/call-route.md)

## Lawful Intercept

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/lawful-intercept.md) [(Status)](/tmedia-documentation/configuration/web-portal-3-3/lawful-intercept/status.md)

## Monitoring

* ISDN Analyzer
* SIP Simulator

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/monitoring.md) [(Status)](/tmedia-documentation/configuration/web-portal-3-3/monitoring/status.md)\
**NOTE:** For Monitoring as a Service solution (MaaS), please refer to this link: [MaaS](/tmedia-documentation/products/tmonitor/monitoring-tools/monitoring-as-a-service-maas.md)

## Troubleshooting

* CallTrace
* Test Call
* Target Recording
* VoIP Ethernet Capture

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/troubleshooting.md)

## Use Cases

* IP Network
* Redirect
* SIGTRAN
* M3UA

[(Configuration)](/tmedia-documentation/configuration/web-portal-3-3/use-cases.md)

## In this section

* [System](/tmedia-documentation/configuration/web-portal-3-3/system.md)
* [Hardware](/tmedia-documentation/configuration/web-portal-3-3/hardware.md)
* [Protocol Stack](/tmedia-documentation/configuration/web-portal-3-3/protocol-stack.md)
* [CDR](/tmedia-documentation/configuration/web-portal-3-3/cdr.md)
* [Fax](/tmedia-documentation/configuration/web-portal-3-3/fax.md)
* [Call Route](/tmedia-documentation/configuration/web-portal-3-3/call-route.md)
* [Lawful Intercept](/tmedia-documentation/configuration/web-portal-3-3/lawful-intercept.md)
* [Monitoring](/tmedia-documentation/configuration/web-portal-3-3/monitoring.md)
* [Troubleshooting](/tmedia-documentation/configuration/web-portal-3-3/troubleshooting.md)
* [Use Cases](/tmedia-documentation/configuration/web-portal-3-3/use-cases.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://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3.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.