IP Whitelisting Reference Guide — SIP Trunking
Written By Maruf Ansari
Last updated 3 months ago
If you're connecting your phone system to your Kickcall agent over SIP Trunking, your phone system, firewall, or carrier needs to trust the outbound traffic coming from Kickcall. Wherever a SIP Trunking setup guide asks you to whitelist our IPs, this is the page it's pointing to.
This document is the single source of truth for every IP range associated with Kickcall's SIP Trunking connectivity. If our ranges ever change, this page is what we'll update — so it's worth bookmarking or linking to internally rather than copying the ranges elsewhere.
This page is specific to SIP Trunking. You'll typically be sent here from the Outbound Configuration step of the SIP Trunking Setup Guide. IP whitelisting does not apply to SIP Registration, which authenticates by login credentials instead — see the FAQ below for details.
SIP signaling IP ranges
Add all three of the ranges below to your phone system's, firewall's, or carrier's allow-list. These are the IP ranges Kickcall uses to send outbound SIP signaling traffic — the calls your Kickcall agent places out through your phone system.
All three ranges are required. Outbound calls may fail to connect until all three CIDR ranges are whitelisted on your side. Partial whitelisting can cause intermittent call failures that are hard to diagnose later, so add all three at once.
How to add these to your allow-list
Locate the allow-list setting. Look for a firewall rule set, SBC (session border controller) trust list, or your carrier's SIP allow-list — the exact name varies by system.
Add each range as a separate entry. Enter all three CIDR ranges from the table above — most systems accept CIDR notation directly.
Save and allow time to propagate. Some firewalls and carrier platforms take a few minutes to apply new allow-list entries.
Place a test call. Confirm outbound calls connect cleanly once whitelisting is in place.
Keeping this list current
These ranges are current as of the publication of this guide. If you ever notice outbound calls failing after whitelisting, or you're unsure whether your allow-list matches the current ranges, contact Kickcall Support and we'll confirm what's active — then re-check this page, since it's the version we keep up to date.
Frequently Asked Questions
Do I need to whitelist these IPs for SIP Registration too?
Do I need to whitelist these IPs for SIP Registration too?
No. This list applies only to SIP Trunking. SIP Registration authenticates using a login (username, password, and domain) rather than IP-based trust, so it doesn't depend on your phone system whitelisting Kickcall's IPs. If you're setting up SIP Registration, you can skip this page.
Do I need to whitelist any IPs for inbound calls?
Do I need to whitelist any IPs for inbound calls?
No — for inbound calls it's the reverse: you add your own phone system's IP addresses to Kickcall's Allowed Addresses field, as covered in the SIP Trunking Setup Guide. The ranges on this page are for outbound traffic only, so your phone system can trust calls coming from Kickcall.
What if my firewall only accepts single IP addresses, not CIDR ranges?
What if my firewall only accepts single IP addresses, not CIDR ranges?
Contact Kickcall Support — we can help you work out an equivalent set of individual addresses, or find another authentication method such as credential-based trunking that fits your system.
Where else will I see these IPs referenced?
Where else will I see these IPs referenced?
The SIP Trunking Setup Guide links here from its Outbound Configuration section. Any other Kickcall documentation that mentions whitelisting our signaling IPs will also point back to this page, so you only need to check one place for the current list.
More in SIP Connectivity
Was this helpful?
Still need help? Ask the team