> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/general/trunks-for-microsoft-teams/troubleshooting-call-routing.md).

# Troubleshooting Call Routing

This is a general guide on how to do some basic troubleshooting for the Microsoft Teams Direct Routing

## General Steps

The below items can be used to troubleshoot majority of issues that you are observing with your Teams Direct Routing configuration.

* Confirm the number works from a known working source (e.g. Mobile phone, soft-phone, landline, etc)
* Confirm if you are able to reach a known working number (your mobile is always a good number to do a test call to)
* Confirm you can resolve the DNS Name of your Microsoft Teams Domain (you can view the domain name under the Domain settings of your tenant)
* Confirm whether the issue is isolated to just that specific user, or if everyone is affected

## I am getting errors when calling outbound

First you need to confirm if the call is leaving the Microsoft Teams system and hitting our system, login to your Trunk management portal and check the call logs. If the calls are leaving Microsoft teams correctly you should see them appear in the call logs.

If you can't see anything login to [admin.teams.microsoft.com](https://admin.teams.microsoft.com/) and navigate to **Analytics & Reports >> Usage**. Once there select the report named **PSTN and SMS (Preview) Usage** , then select **Last 7 Days** and click **Run Report**. Once the report comes back click on **DIRECT ROUTING** at the top of the table, you should then be able to see your call logs. What you want to look at specifically is the columns named **Final SIP Code Phrase**, **Final SIP Code** and **Event Type**. Below is some explanations of what you might see in there.

* Event Type = Success, Final SIP Code = 200 - This means that the call was successfully established
* Final SIP Code Phrase = Fallback to LGW - This means that the call couldn't be routed via the Direct Routing and instead failed over to the Microsoft Teams Gateway
* Final SIP Code = 302 - This means the system attempted the call but failed to route the call correctly

You can find more explanations of the SIP Codes in the articles below:

{% embed url="<https://en.wikipedia.org/wiki/List_of_SIP_response_codes>" %}


---

# 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://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/general/trunks-for-microsoft-teams/troubleshooting-call-routing.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.