> For the complete documentation index, see [llms.txt](https://docs.cebodtelecom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cebodtelecom.com/microsoft-teams-integration/direct-routing-user-guide/voice-activation-and-setup/1.-adding-sbc-in-direct-routing.md).
# 1. Adding SBC in Direct Routing
In the left navigation of Microsoft Teams admin centre, go to Voice > Direct Routing, and then click the SBCs tab.
Click Add.
Enter a FQDN for the SBC.
{% hint style="info" %}
Make sure the domain name portion of the FQDN matches a domain that's registered in your tenant, and keep in mind that the \*.onmicrosoft.com domain name isn't supported for the SBC FQDN domain name. For example, if you have two domain names, contoso.com and contoso.onmicrosoft.com, use sbc.contoso.com as the SBC name.
{% endhint %}
When you're done, click **Save**.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cebodtelecom.com/microsoft-teams-integration/direct-routing-user-guide/voice-activation-and-setup/1.-adding-sbc-in-direct-routing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.