For the complete documentation index, see llms.txt. This page is also available as Markdown.

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:

Network Traffic Type
Server Addresses
Port / Type

WebRTC flow

*.millicast.com

443 / TCP - API calls

49152-65535 / UDP - Millicast WebRTC Media Server

STUN/TURN

*.dolby.io *.twilio.com

PacPost Live uses Twilio, which currently employs the following ports: 80, 443, 3478, 5349 / TCP and UDP

Standard RTMP Ingest

*.milicast.com, rtmp-auto.millicast.com

1935 / TCP

Secure RTMPS Ingest

*.millicast.com, rtmp-auto.millicast.com

443 / TCP

PacPost Live Dashboard

*.pacpost.live

80, 443 / TCP

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.

Last updated