Firewalls, anti virus, and content blockers

To ensure stable call quality and consistent application performance, Aircall requires specific ports, domains, and IP ranges to be allowlisted in your firewall, anti virus software, and any content filtering tools such as web proxies or IDS/IPS systems. Aircall applications initiate all traffic through outbound connections to the destinations listed below, and any related inbound traffic is permitted automatically once a session is established.

General configuration requirements

All Aircall applications rely on the following ports and domains. Make sure these are allowlisted in your environment.

Required ports (allow outbound traffic)

Required domains and URLs (allowlist)

Allowlist the following domains in your firewall, web proxy, and any content filters. The asterisk symbol covers all subdomains.

Server specific IP addresses

Aircall infrastructure is hosted on AWS. While you may restrict traffic to specific IP addresses for tighter security, AWS ranges can change at any time. Relying on domain allowlisting is the most reliable option.

Important: AWS IP ranges change without prior notice. If you must use static IP ranges, consult the official Amazon Public IP Ranges documentation for the most current information.

Public IP addresses for Aircall integrations

Some network environments require IP allowlisting to allow external services to communicate with internal systems. If your organization restricts inbound traffic, you may allowlist the static public IPs used by Aircall integrations in the production environment.

Aircall integration public IPs (Production VPC)

44.239.147.27
54.200.88.37
44.237.249.17
52.40.81.129

Note: Allowlist these IPs only if your organization requires inbound traffic restrictions and uses Aircall integrations that must communicate with internal systems.

Worldwide media (RTP) and WebRTC (STUN) servers

These servers handle media streaming and NAT traversal for real time communication.

Media servers (RTP)

WebRTC servers (STUN)

Regional WebRTC TURN servers (Roaming feature)

These servers relay media when STUN is not possible. They are especially relevant when using the Roaming feature to connect to the closest available server. For more information, refer to Understanding Roaming feature.

Critical call quality and troubleshooting

Adjusting UDP session timeout

VoIP traffic depends heavily on UDP. Since UDP does not use a handshake to close connections, firewalls may terminate an active call session too early. Increasing UDP session timeout helps prevent interruptions.

ACTION:
Increase UDP session timeout on your firewall or router. The recommended value is at least 90 seconds.

Tip: If possible, apply the extended timeout only to Aircall destinations to avoid unnecessary changes to unrelated traffic.

Gateway features that affect VoIP quality

Certain gateway features can disrupt real time media traffic and cause one way audio, choppy calls, or dropped connections. If you experience call quality issues, try disabling or bypassing the following features specifically for Aircall traffic:

• Deep Packet Inspection or Stateful Packet Inspection
• Intrusion Detection or Intrusion Prevention Systems
• Web proxies or web filters
• WAN optimization devices
• Port filtering that exceeds the required ports listed above
• Packet by packet load balancing across multiple ISPs since this can reorder RTP packets

Configuring your network according to these guidelines ensures the best possible performance when using Aircall.