> 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/en/account-management/gruppen-und-user/wie-vergebe-ich-rufnummern-und-durchwahl-fuer-gruppen.md).

# How do I assign phone numbers and extensions to groups?

Instructions for assigning phone numbers and extensions to sipgate groups - including a list of blocked extensions.

{% hint style="info" %}
The function *Groups* is **is available only to customers on sipgate classic** available. On sipgate neo, it is integrated in a different form.
{% endhint %}

If you would like to assign phone numbers or internal extensions within a group, please proceed as follows:

First, go to the [**group management**](https://app.sipgate.com/groups). Then select the group for which you want to assign a phone number or extension. You can now assign a phone number or extension via Visual Routing and assign the desired people to the group.

The following extensions cannot be assigned for technical reasons:

* 110 (police emergency number Germany)
* 111 (emergency number New Zealand)
* 112 (fire and rescue service emergency number Germany)
* 113
* 114
* 115 (government information Germany)
* 116
* 117
* 118
* 119
* 211
* 311
* 411
* 511 (USA hotline number)
* 611
* 711 (USA long-distance operator assistance)
* 811
* 911 (emergency number USA)
* 999 (emergency number UK)
* 9900-9999


---

# 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/en/account-management/gruppen-und-user/wie-vergebe-ich-rufnummern-und-durchwahl-fuer-gruppen.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.