> For the complete documentation index, see [llms.txt](https://docs.itgrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itgrix.com/faq/asterisk-integration-policy.md).

# Asterisk Integration Policy

When developing the product, we adhered to the principle of not interfering with the client’s Asterisk configuration.

This means that when implementing our product:

* The dialplan doesn't change: all call routes remain the same;
* The settings for Extensions or Trunks remain unchanged;
* There are no requirements regarding the stream encoding scheme;
* The structure of the tables in your database does not change; the module does not generate any new data.

This policy allows us to ensure that your PBX continues to operate according to your settings, following the same rules and maintaining the same level of quality as before our solution was installed.

The module works with Asterisk:

1. Using simple read queries on your database (you can restrict access as needed);
2. Using ORIGINATE requests via AMI by the user you created in manager.conf with the parameters specified in the application configuration file;
3. A number of other read requests to Asterisk that do not affect calls;
4. If you need automatic call routing, you can modify your dialplan yourself; Asterisk will then send requests to our application to determine which agent should handle the call (no actions can take place without your approval).


---

# 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://docs.itgrix.com/faq/asterisk-integration-policy.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.