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

# Monitoring status

***Applies to version(s): v2.9, v2.10, v3.0, v3.2***

There are multiple ways to verify the status of network monitoring. This is done from the Status menu and the Navigation panel.

## Status menu

1- Click **Status** in the navigation panel.

2- Click the **Monitoring** tab.

The monitoring status is displayed, as two sub-tabs.

The first tab contains a summary of ISDN analyzers status, indicating which are available (all line services are up), partially available (some line services are down) or unavailable (all line services are down).

StatusMonitoring\_1\_ISDN.png

The second tab contains a summary of SIP simulators status, indicating which are available (all destinations available), partially available (some destinations unavailable) or unavailable (all destinations unavailable).

StatusMonitoring\_1\_Simulator.png

## ISDN Analyzers Status (Navigation Panel)

1- Click **ISDN Analyzers** from the navigation panel.

2- Click the **Status** tab.

* A summary of per-analyzer status is displayed.
* Select a ISDN analyzer from the list.

The ISDN Analyzer status is displayed.

**Path**

```
/configurations/@[configuration_name]/mon_isdn_analyzers/@[isdn_analyzer]/status
```

## SIP Simulator Status (Navigation Panel)

1- Click **SIP Simulators** from the navigation panel.

2- Click the **Status** tab.

* A summary of per-simulator status is displayed.
* Select a SIP Simulator from the list.

The SIP Simulator status is displayed.

**Path**

```
/configurations/@[configuration_name]/mon_sip_simulators/@[sip_simulator]/status
```


---

# 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/configuration/web-portal-3-3/monitoring/status.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.