Others questions.
- What is SnapCall?
- How does SnapCall work?
- What is a call button?
- Where can customers launch calls from?
- Where can I receive calls from customers?
- Receiving calls via website or app with WebRTC
- Is SnapCall GDPR compliant?
- Best practices of SnapCall Client's deployment
- All About SnapCall IP Addresses
- How to troubleshoot issues with SnapCall
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.
REST API
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 allowing all outbound HTTPS traffic to any *.snapcall.io subdomain.
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:
| IPServer-side port used | Protocol | |
| 63.34.87.151 | 443/80 | TCP |
| 63.34.87.151 | 80 | UDP |
| 52.211.244.22 | 443/80 | TCP |
| 52.211.244.22 | 80 | UDP |
Bandwidth Requirements
| Product | Platform | PlatformCodec | Bandwidth required* dynamically adjustable |
| SnapCall web client | desktop/responsive | OPUS | 10-40 kBits/sec |
| SnapCall SDKs | mobile | OPUS | 10-40 kBits/sec |
* The Bandwidth value shown is required for both directions
How do I start with SnapCall?
SnapCall provides you an opportunity to try our technology entirely free for 14 days. Create an account and start your free trial. In case you need any assistance, reach out to our team via support@snapcall.io.