1 - All About SnapCall IP Addresses
Whether you are enforcing strict Firewall policies, connecting with API, or securing your voice flow, understanding SnapCall's IP address whitelisting scenarios is essential.
Here is a roundup of the IP address details from across our platform.
The REST API's IP addresses are highly dynamic across a vast range, so it's not practical to whitelist based on IP addresses. Instead, we recommend you allow all outbound HTTPS traffic to any
SnapCall Client & SDKs
The original SnapCall web client and also SDKs allow you to connect directly to SnapCall from a web browser or a custom mobile application.
Here are the network requirements for SnapCall web client and SDK connections:
|IP||Server-side port used||Protocol|
|Product||media||Platform||Codec||Bandwidth required* dynamically adjustable|
|SnapCall web client||audio||desktop/responsive||OPUS||10-40 kbits/sec|
|SnapCall SDKs||audio||mobile||OPUS||10-40 kbits/sec|
|SnapCall web client||video||desktop/responsive||
|SnapCall SDKs||video||mobile||VP8||600-800 kbits/sec|
* The Bandwidth value shown is required for both directions
Do you have any questions? Want to share some feedback? We're more than happy to discuss this with you. Drop us a message via firstname.lastname@example.org and we'll get back to you soon! 💌