IP Allowlist Configuration

Edited

Product: Prepared

Audience: IT Admins
Last Updated: 03/20/2026


Outcome Statement

After reading this guide, you can configure your firewall to allow all required traffic for Prepared Assist and Prepared Live, ensuring full functionality for real-time media, location, and platform access.


Overview

Prepared Assist and Prepared Live rely on cloud-based services that require specific domains, ports, and protocols to be accessible.

If your dispatch center uses a firewall, proxy, or network security controls, you must allow outbound access to the domains listed below. Failure to do so may disrupt real-time features such as live video, audio, and location sharing.


Prerequisites

  • IT Admin or Network Administrator access

  • Ability to modify firewall, proxy, or network security rules


Firewall Requirements

Your network must allow outbound traffic to the following domains and ports.


Prepared Live Core Services (WebRTC / Media Relay)

These services support real-time media (audio, video, and location) using WebRTC.

*.prepared.live
Port: 443 (TCP)

Includes:

turn.prepared.live
Ports: 443 (TCP), 3478 (UDP)

turn-ephemeral.prepared911.com
Ports: 443 (TCP), 3478 (UDP)

stream.prepared.live
Ports: 443 (TCP), 3478 (UDP)

Prepared Platform Services

Core platform functionality, APIs, and application services:

*.prepared911.com
Port: 443 (HTTPS)

Includes:

portal.prepared911.com  
api.prepared911.com  
cdn.prepared911.com  
onboarding.prepared911.com  
releases.prepared911.com  

logger-media.prepared911.com (443)  
otlp.prepared911.com (443) — gRPC over TLS  

Additional Service:

rp.prepared911.com  
Port: 31092 (TLS)

ANET / ION Services

*.ion.prepared.live  
Port: 443

Includes:

json.ion.prepared.live

Prepared App Services

*.preparedapp.com  
Port: 443

Includes:

911.preparedapp.com  
api.911.preparedapp.com  
onboarding.preparedapp.com

Media, Identity, and Third-Party Services

These services support media storage, authentication, and mapping:

live-production-media.s3-fips.us-east-1.amazonaws.com (443)  
cognito-idp-fips.us-east-1.amazonaws.com (443)  

maps.googleapis.com (443)  
maps.gstatic.com (443)  
fonts.googleapis.com (443)

Protocol Requirements

If your firewall filters by protocol:

  • Prepared uses WebRTC for real-time communication

  • WebRTC relies on:

    • UDP (3478) for media transport

    • DTLS for secure media encryption

    • TCP (443) as a fallback

Blocking UDP may result in degraded or failed media sessions.


Best Practices

  • Regularly test:

    • Live video and audio

    • Location sharing

    • Streaming functionality

  • Document all firewall and network changes

  • Review Prepared release notes for new domains or updates


FAQs

Question

Answer

Does Prepared provide a static IP list?

No. Prepared uses cloud infrastructure with dynamic IP ranges.

What happens if ports are blocked?

Real-time features (video, audio, location) may fail or degrade.

Who should perform these changes?

Your IT Admin or Network Engineer.


Support & Additional Resources

Support@prepared911.com

Quick Allowlist Summary.pdf
65.7KB