> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx/english/faq/outbound-routing/prohibiting-calls-via-a-backup-route.md). # Prohibiting calls via a backup route When describing [outgoing routes](/mikopbx/english/manual/routing/outbound-routing.md), it is allowed to use the same phone number template. If several routes are used with the same template, the PBX will try to make a call on each of the routes until the call is accepted. This functionality is not always necessary and there may be a need to disable it. At the moment, this can only be done through the customization of the PBX. 1. Go to the provider's settings and copy its ID in the browser's address bar:

2. Go to the section "**System file customization**"

3. Go to the editing section of the **extensions.conf** file.

4. Add the following context to the end of the file: ```php [SIP-1687941868-outgoing-after-dial-custom] exten => _X!,1,Hangup() same => n,return ```

Save the changes. Now all calls via routes associated with the provider will occur without taking into account the backup provider. It will work out only the first of the outgoing routes. --- # 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://docs.mikopbx.com/mikopbx/english/faq/outbound-routing/prohibiting-calls-via-a-backup-route.md?ask=&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.