> 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/voice-and-media/target-recording.md).

# Target Recording

[Tmedia](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmedia) units, running Toolpack software and the [Gateway](/telecom-references/sip-and-voip/h248-mgcp/tb-media-gateway.md) application, permit the recording of calls.

Calls are recorded as ".wav" files on the Tmedia unit's drive.

**WARNING: For this reason, target recording is recommend for troubleshooting only and should be disabled when it is not needed. In addition, recording a large amount of calls simultaneously will have an impact on the system's performance.**

### Use cases

Target recording is useful in a variety of applications:

* Voice/line quality control
* FAX quality analysis
* Lawful interception
* Debugging
* Test calls

### Software requirements

* Toolpack software version 2.6 or higher
* [tbstreamserver](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/tb-streamserver) application configured to be running (it's not running by default)
* [Gateway](/telecom-references/sip-and-voip/h248-mgcp/tb-media-gateway.md) application (standard with Toolpack unless explicitly replaced by custom call handling application)

### Hardware requirements

* [Tmedia](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmedia) unit with IVR DSP resources
* Starting with version 2.8.101, [Tmedia](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmedia) unit with IVR DSP resources or VoIP DSP resources with playing/recording licenses

### Recording modes

Recording calls can be achieved using 1 of 2 methods:

#### Web Portal

**This mode should be used for troubleshooting only.**

It is easy to use but not flexible.

This mode is limited to record based on the following parameters:

* Recorded files options:
  * Record each leg of a call into it's own file
  * Record an audio mix of both legs of a call to a single file (only available with Toolpack 2.7 and up only)
* Available filtering parameters:
  * By calling number
  * By called number
  * By incoming NAP
  * By outgoing NAP

#### Routing script

This mode can insert recording into any existing routing script.

It is extremely flexible but requires users to modify their routing scripts.

* Recorded files options:
  * Record each leg of a call into it's own file
  * Record an audio mix of both legs of a call to a single file (only available with Toolpack 2.7 and up only)
* Available filtering parameters:
  * Any call parameters
  * Any route parameters
  * Any routing scripts parameters

#### Configuration (and Accessing the recorded calls)

* [Target Recording for 3.0](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/troubleshooting/tmedia-tdev-and-tsig-web-portal-3-0-troubleshooting#target-recording)

<details>

<summary>Click here for other versions</summary>

* [Target Recording for 2.10](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-troubleshooting#target-recording)
* [Target Recording for 2.9](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-troubleshooting#target-recording)
* Target Recording for 2.8 and earlier: documentation is no longer published. Contact [technical support](https://prosbcdocs.telcobridges.com/tmedia-documentation/operations-and-support/support/contacting-telcobridges-technical-support) if you need it.

</details>

#### Routing Scripts mode

* [routing script mini tutorial guide](/telecom-references/developer-reference/routing-scripts.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/telecom-references/voice-and-media/target-recording.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.
