> 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/connections-and-integrations/ms-teams/wie-gehe-ich-vor-wenn-die-telefonie-in-ms-teams-eingeschraenkt-ist.md).

# What do I do if telephony is restricted in MS Teams?

Troubleshooting restricted telephony in MS Teams with sipgate - step-by-step guide to resolving the issue.

This article explains the **procedure** for **various error messages** in the **in connection with MS Teams** explained. A uniform procedure is often easier to implement than creating different scenarios with separate case distinctions for each situation. If telephony in MS Teams is restricted, please follow these steps:

{% stepper %}
{% step %}
**Check integration online**

*Affects both incoming and outgoing telephony.* First, you should check the registered endpoints on the affected user's extension.

* To do this, log in to **sipgate** and navigate to **User**
* Click the affected extension and check under **Registered devices**, whether any devices are registered.
* Also check by clicking on the **gear icon** which devices are listed. More information can be found in the video [Check registered devices](https://www.loom.com/share/fb84b43c8a524b1fa5e99bc2ea216205?sid=f226221f-5bc4-4d4e-8f48-b4ea05ecd86d)
* If no devices are registered or among the registered devices **NOT** "**GILAWA DR-SBC GW\\"** is listed:
  * Please write to <support-ms-teams@sipgate.de>, that the MS Teams integration is not online.
  * Please include the affected user, your customer number, and a callback number, preferably a mobile number.
  * Wait for a response.
  * If that worked, continue with the next step.
    {% endstep %}

{% step %}
**Match phone numbers**

*Affects both incoming and outgoing telephony.*

* Match the **Phone numbers** of the user in the **sipgate profile** with the user's phone number in your **Office tenant** against it. You can also check the required license directly in the Office tenant.
* Also check the numbers for **typos,** as a connection can only be established with identical phone numbers.
* More information can be found in the video [Match phone numbers](https://www.loom.com/share/50a7f0ea584d4bcd8e4cf664bf79237b?sid=65ec6f51-746f-4859-b53b-4a64f9e7a784)
  {% endstep %}

{% step %}
**Check routing policy**

*Affects outgoing telephony.*

* Open the **User profile** in the **MS Teams admin center**
* Select **Policies**
* Check which VoIP routing policy is set.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Note: For the integration with sipgate, it should also be named accordingly</p></div>
* More information can be found in the video: [Check routing policy](https://www.loom.com/share/4438bddb09c8449ab8fbf7f178e98055?sid=d3912f4a-6229-4f95-9864-38613c04e71a)
  {% endstep %}

{% step %}
**Exclude call forwarding**

*Affects incoming telephony.*

* Check the **call forwarding settings** of the user in the **sipgate portal** More information can be found in the article [**How do I set up call forwarding?**](https://help.sipgate.de/hc/de/articles/360019990558-Wie-stelle-ich-Weiterleitungen-ein)
* Check the **call forwarding settings** of the user in the **Office tenant** More information can be found in the video [Check forwarding in the MS Teams admin](https://www.loom.com/share/2cba94b146024f308c742d60b1f2a030?sid=90f014ba-1a58-4002-a85b-479299de6e69)
  {% endstep %}
  {% endstepper %}


---

# 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/connections-and-integrations/ms-teams/wie-gehe-ich-vor-wenn-die-telefonie-in-ms-teams-eingeschraenkt-ist.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.