> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/connect-telephony/direct-routing/direct-routing-network-and-firewall.md).

# Network and firewall

Plan the regional endpoint, ports, and firewall rules required between the customer SBC and the Dialogue Cloud SBC.

Use this page to plan the network path between the customer Session Border Controller (SBC) and the Dialogue Cloud SBC for a Connect model deployment.

For the Direct Routing overview and OnePortal configuration workflow, see [Telephone Connection for Dialogue Cloud Neo (Connect)](/connect-telephony/direct-routing.md).

## Identify the deployment region

Before you open firewall rules or configure the SIP trunk destination, confirm which Dialogue Cloud region your service uses.

Use the current region-specific Dialogue Cloud SBC hostname reference when you plan the SIP trunk destination and firewall scope:

| Region                                 | Current hostname reference                                                                                                                                                  |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Europe, Middle East, and Africa (EMEA) | `emea-weu-p-sbc01.emea-weu.anywhere365.cloud` (older deployments), `emea-gwc-p00-sbc01.emea-gwc.prd.anywhere365.cloud`, `emea-szn-p00-sbc01.emea-szn.prd.anywhere365.cloud` |
| Asia Pacific                           | `apac-sea-p-sbc01.apac-sea.anywhere365.cloud`                                                                                                                               |
| Australia                              | `apac-aue-p00-sbc01.apac-aue.prd.anywhere365.cloud`                                                                                                                         |
| North America                          | `nora-cus-p-sbc01.nora-cus.anywhere365.cloud`                                                                                                                               |

{% hint style="warning" %}
Do not assume one default hostname for every deployment. The assigned SBC endpoint can differ per service, especially in EMEA. Confirm the exact hostname for your service with your AnywhereNow representative before you configure the customer SBC or firewall.
{% endhint %}

## Plan for regional redundancy

Plan the connection on the assumption that each regional Dialogue Cloud SBC deployment runs as a highly available cluster across two Azure availability zones and that traffic can be routed to the active nodes within that regional cluster.

## Open the required signalling ports

Allow outbound signalling traffic from the customer SBC to the assigned Dialogue Cloud SBC endpoint on the required protocol and port combination.

| Protocol            | Destination port |
| ------------------- | ---------------- |
| SIP over TLS        | `5061`           |
| SIP over TCP or UDP | `5060`           |

{% hint style="info" %}
Use Transport Layer Security (TLS) as the preferred signalling path.
{% endhint %}

## Open the required media ports

Allow outbound media traffic from the customer SBC to the Dialogue Cloud media components.

| Protocol                | Destination ports |
| ----------------------- | ----------------- |
| SRTP and SRTCP over UDP | `6000-65535`      |
| RTP and RTCP over UDP   | `6000-65535`      |

{% hint style="info" %}
Use Secure Real-time Transport Protocol (SRTP) as the preferred media path.
{% endhint %}

## Use current deployment evidence for firewall allowlists

Use the current IP addresses assigned to your service and region in firewall requests, not example or placeholder addresses.

Obtain the current Direct Routing technical setup material through your Certified Partner. Registered users can access [KB0010642](https://support.anywhere.now/kb/en?id=kb_article_view\&sysparm_article=KB0010642). Access requires the appropriate support-portal account; do not substitute a placeholder address if you cannot open it.

During delivery, request the current values from the Professional Service Engineer. For an operational platform, raise a Support ticket. Include the service and region, and ask for the assigned SBC hostname, applicable signalling/media allowlist, and its applicability date. Add only the IP addresses for the assigned region.

{% hint style="warning" %}
Regional media capacity can scale with load. If you are unsure which firewall IP set applies to your service, confirm the current allowlist values for your assigned region with your AnywhereNow representative before go-live.
{% endhint %}

## Verification

1. Confirm the assigned Dialogue Cloud region and SBC hostname for the target service.
2. Confirm the firewall rules allow the required signalling and media ports from the customer SBC to the assigned Dialogue Cloud endpoint.
3. Confirm the firewall allowlist includes the current IP addresses for the assigned region only.
4. Confirm the customer SBC can resolve the assigned fully qualified domain name (FQDN) and present the required certificate chain for the chosen transport.
5. Continue to SBC configuration and routing-scenario testing only after the network path is open and validated.

## Related topics

Go to **Telephone Connection for Dialogue Cloud Neo (Connect)** for the OnePortal SBC configuration workflow and Enhanced Direct Routing (EDR) enablement steps.

{% content-ref url="/pages/P2EMkmV52Ncf5FcJC6rT" %}
[Connect model: Direct Routing](/connect-telephony/direct-routing.md)
{% endcontent-ref %}


---

# 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://atlas.anywhere.now/connect-telephony/direct-routing/direct-routing-network-and-firewall.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.