> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/anbindungen-und-integrationen/asteriske/wie-konfiguriere-ich-asterisk-zum-setzen-einer-individuellen-absendernummer.md).

# Wie konfiguriere ich Asterisk zum Setzen einer individuellen Absendernummer?

Anleitung zum Setzen individueller Absenderrufnummern in Asterisk per P-Preferred-Identity-Header mit sipgate Trunking.

{% hint style="info" %}
**Hinweis:** Diese Funktion kann ausschließlich in Verbindung mit sipgate trunking genutzt werden.
{% endhint %}

Voraussetzung ist ein bestehender Rufnummernvertrag und die dementsprechende Festlegung einer Fallback Absendernummer im Account unter **Accountverwaltung**, **Trunks** und **Fallback-Absenderrufnummer**.

Die Absenderrufnummer muss als zusätzlicher Header **P-Preferred-Identity** im internationalen Format (**E.164**) gesetzt werden. Modifizieren Sie die Datei **extensions.conf** wie folgt:

{% code title="extensions.conf" %}

```ini
[sipout]
exten => _X.,1,Set(CALLERID(number)=SIPID)
exten => _X.,n,Dial(SIP/${EXTEN}@sipgate-out,30,trgb(sipout-hook^${EXTEN}^1))
exten => _X.,n,Hangup

[sipout-hook]
exten => _X.,1,Set(PJSIP_HEADER(add,P-Preferred-Identity)=<sip:4921158000000@sipconnect.sipgate.de>)
```

{% endcode %}

**Anstelle von 4921158000000** setzen Sie die **gewünschte Absendernummer**. Wichtig ist das korrekte internationale Format, allerdings ohne führende Nullen oder Plus-Zeichen.

Möchten Sie die Rufnummer unterdrücken, tragen Sie folgendes ein:

```ini
SipAddHeader(P-Preferred-Identity: <sip:492111234567@sipconnect.sipgate.de>)

SipAddHeader(Privacy: id)
```


---

# 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://help.sipgate.de/cloud-telefonanlage/anbindungen-und-integrationen/asteriske/wie-konfiguriere-ich-asterisk-zum-setzen-einer-individuellen-absendernummer.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.