> 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/telecom-references/sip-and-voip/toolpack-monitoring-sip-generator.md).

# Toolpack monitoring sip generator

![Monitoring generator overview2](https://docs.telcobridges.com/w/images/6/64/Monitoring_generator_overview2.png) The Toolpack Monitoring "SIP Generator" is a behavior that can be attached to a call flow, and that will create outgoing SIP calls used to "monitor" the call that this behavior is attached to.

The SIP generator will generate 2 outgoing SIP calls, each carrying audio from one direction of the monitored call.

It's expected that these outgoing SIP calls are accepted and answered by remote SIP equipment.

### SIP generator call flow

Once attached to a call flow, the "SIP generator" behavior will identify the "main" legs of the attached call flow (one incoming and one outgoing). Once these "main legs" are detected (they can be TDM, IP or monitored leg), then the outgoing SIP calls are generated to carry a copy of the audio of these "main legs".

![SIP generator call flow](https://docs.telcobridges.com/w/images/d/dd/SIP_generator_call_flow.png)

#### Attaching to a monitoring call flow

The SIP generator behavior can be attached to a standard call flow (CTBCAFBrige for example, which deals with a bridge between one incoming and one outgoing call legs).

It can also be attached to a "monitoring" call flow that receives call state change events from an analyzer (like an [ISDN Analyzer](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/isdn-cas/toolpack-monitoring-isdn-analyzer/README.md)).

In both cases, it will generate a pair of outgoing SIP calls to carry a copy of the audio of each direction of the monitored call.

### SIP generator configuration

The SIP generator has a few options that can be configured (from it's "parameters" class for developers, or from the Web Portal for Toolpack Gateway users).

* The "First side" and "Second side" SIP NAP to generate outgoing SIP calls with
* The "First side" and "Second side" profile to generate outgoing SIP calls with (will use NAP's profile by default if not specified)

Note: Each "Side" represents one direction of the monitored call. (and ISDN and other protocol analyzers have configuration to specify which side correspond to which direction of monitored trunks)

### Configuring SIP Generators in Toolpack Web Portal

Developers can use SIP Generators in their application by attaching behavior CTBCAFCallBehaviorSipGenerator to their call flow (which can be either a "standard" call flow bridging two call legs, or a "monitoring" all flow monitoring the two directions of a call)

Non-developers that use Toolpack system with built-in Gateway application can also use SIP Generators and attach them to ISDN analyzers.

For more information and step-by-step screen shots of the configuration of SIP Generators, please refer to the [Web Portal Tutorial Guide v2.9](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tsig-and-tdev-web-portal-2-9-tutorial-guide/README.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 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/telecom-references/sip-and-voip/toolpack-monitoring-sip-generator.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.
