# Network Requirements

If you have an environment that is behind a restrictive network, use the following information to create the proper firewall whitelist configuration to enable the PacPost Live services to pass:

<table><thead><tr><th width="224">Network Traffic Type</th><th width="197.199951171875">Server Addresses</th><th>	Port / Type</th><th data-hidden></th></tr></thead><tbody><tr><td>WebRTC flow</td><td>*.millicast.com</td><td><p>443 / TCP - API calls</p><p></p><p>49152-65535 / UDP - Millicast WebRTC Media Server</p></td><td></td></tr><tr><td>STUN/TURN</td><td>*.dolby.io<br>*.twilio.com</td><td>PacPost Live uses <a href="https://www.twilio.com/docs/stun-turn/regions">Twilio</a>, which currently employs the following ports:<br><br>80, 443, 3478, 5349 / TCP and UDP</td><td></td></tr><tr><td>RTMP Publishing</td><td>*.miillicast.com</td><td><p>1935 / TCP - for unsecure</p><p></p><p>443 / TCP - for secure</p></td><td></td></tr><tr><td>PacPost Live Dashboard</td><td>*.pacpost.live</td><td>80, 443 / TCP</td><td></td></tr></tbody></table>

We also recommend whitelisting the following domains:

* \*.dolby.io
* \*.millicast.com
* \*.twilio.com
* \*.pacpost.live

**DNS Servers**

Due to the nature of the Millicast and Twilio services, it is critical that host computers located on highly restrictive networks (eg. relying on explicit outbound firewall whitelisting) are configured to use their firewall as their DNS provider / proxy.

The firewall and host computer using using independently configured DNS providers, even to the same DNS service (e.g. 8.8.8.8) may yield mismatched domain name / IP resolutions between the devices, and lead to unintended/unexpected blocking behavior by the firewall.


---

# Agent Instructions: 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:

```
GET https://wiki.pacpost.com/public-wiki/network-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.