> For the complete documentation index, see [llms.txt](https://docs.bird.com/toky-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/toky-en/readme/byoc-requirements.md).

# BYOC Requirements

Learn more about the technical requirements to start the Bring your Own Carrier setup.

\- The carrier must work with SIP Protocol.

\- The carrier must support G711 (ulaw or alaw) or G729.

\- Please provide the SIP credentials of your account to your carrier, we will need this information to register your account.

*SIP Username :*

*SIP Password :*

*SIP proxy :*

\- Please provide the IP Address (or addresses) of your carrier servers that will be receiving our registration and the calls.

\- Ask for the Caller ID for your account to your carrier, we will need this information to send calls.

\- Ask for the dialing rules supported by your carrier, we will need that information to send the calls.

\- If your carrier needs an authorized IP address from Toky, please contact support. ([*support@toky.co*](mailto:support@toky.co))

**Important:** The amount of outbound simultaneous calls is determined by your carrier, ask your carrier about how many channels are permitted.


---

# 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.bird.com/toky-en/readme/byoc-requirements.md?ask=<question>&goal=<endgoal>
```

`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.