> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/setup/pascom-trunk/templates.md).

# Trunk Templates

The PASCOM cloud phone system includes a SIP provider database including a number of templates for creating SIP trunks. These templates are designed to support admins with the trunk setup and automati

{% embed url="<https://www.youtube.com/watch?v=DQwK3imFHrk>" %}

## Trunk Templates

Add a new trunk under `Gateways` > `Trunks` > `+Add`. This will direct you to the SIP provider database where you can find templates for all supported and certified trunks, plus the manual configuration options.\
Using the filter tool, you can search for your trunk. If your provider is not listed, please use the `Manual SIP` option.

![Ämterauswahl](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-0057e982ea00ad7d767cd498d1b8c273f3f3b6f6%2Ftrunk_templates_EN.png?alt=media)

Enter the required data in the setup template, which you received from your Telephony Provider.\
As different Trunk types require different variables, please refer to the overview below:

| Variable                     | Description                                                                                                                                                                                                                                                                                                                                    |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**                     | Enter a name for the trunk, which is then displayed in the Trunks overview list                                                                                                                                                                                                                                                                |
| **International Prefix**     | The characters or numbers needed to dial international numbers - ordinarily *00*.                                                                                                                                                                                                                                                              |
| **Country Code**             | Enter the country code for the Trunk's originating country. For example, the UK is **44**. SIP trunks allow you to have your phone system server located in one country and register it with a trunk from another country via the internet. Therefore, enter the country code for where the Trunk is located, not the phone system server.     |
| **National Prefix**          | The numbers which need to be dialled in order to make a call to a national landline (with an area code) - ordinarilly *0*.                                                                                                                                                                                                                     |
| **Area Code**                | Enter the area code (excluding the proceeding 0). For example for London you would enter 20 instead of 020.                                                                                                                                                                                                                                    |
| **Line / Subscriber Number** | The base number of your telephony connection.                                                                                                                                                                                                                                                                                                  |
| **Prefix Incoming Number**   | Any pre-set number which is attached to incoming calls via this trunk. If, for example, you enter a **0**, then calls to this number may appear in your IP phone's call history as `00172123123` instead of `0172123123`. This allows users to directly callback numbers in the call history using the same trunk over which the call came in. |
| **DID format**               | Number format for user extensions - how many digits. (Not the total number in a Number (DID) Block!)                                                                                                                                                                                                                                           |
| **Switchboard Extension**    | Enter the internal extension on which calls to the first number in your number block (normally 0) should be routed.                                                                                                                                                                                                                            |


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/setup/pascom-trunk/templates.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 `build a script that syncs our docs to a CMS` 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.
