Vanillasoft IP Whitelisting and Network Requirements
Last updated: October 25, 2026
If users have trouble accessing VanillaSoft, signing into VS Connect, sending or receiving emails, or using our HubSpot integration, your network may be blocking required IP addresses, domains, or ports.
Adding the appropriate destinations to your organization's allow list (whitelist) can help resolve these connectivity issues.
Tip: Share this article with your IT or network administrator. Changes to firewalls, routers, and security tools must be completed by your organization.
Important Network Update — October 2026
Action may be required for customers using IP whitelisting or restrictive firewalls.
Our calling technology provider, CounterPath, is migrating its Stretto data center between October 23 and October 25, 2026.
As part of this migration, the following IP address changes apply:
| IP Address Range | Status |
|---|---|
| 154.6.16.0/24 | New Stretto IP range—allow outbound access |
| 216.93.246.0/24 | Previous Stretto IP range—scheduled for decommissioning by October 31, 2026 |
What you need to do
If your organization restricts outbound connections using IP whitelisting or firewall rules:
- Add
154.6.16.0/24to your approved outbound destinations. - Maintain existing required access during the migration.
- Verify that the appropriate ports and domains are accessible.
- Test your VS Connect calling functionality.
- Review the previous IP range for removal after the migration is confirmed complete.
Customers without restrictive firewall configurations generally do not need to make changes.
Important: Do not remove the previous IP range until the migration is complete and your IT administrator has confirmed connectivity.
General Vanillasoft IP Addresses
Allow the following IP addresses and ranges as applicable to your organization's Vanillasoft services.
23.249.208.0/20 23.251.156.253 23.251.158.66 23.251.224.0/19 34.30.31.128 34.36.86.221 34.54.149.42 34.58.92.217 34.70.219.215 34.85.161.225 34.85.163.100 34.85.195.195 34.85.227.217 34.85.240.119 34.110.243.255 34.132.14.188 34.133.142.170 34.133.222.22 34.150.147.253 34.160.11.251 34.170.24.243 35.186.163.5 35.186.186.0 35.186.188.38 35.192.127.34 35.193.117.228 35.194.71.131 35.194.85.204 35.194.86.78 35.199.8.57 35.199.33.15 35.202.40.161 35.202.238.243 35.223.82.228 35.223.230.185 35.224.124.87 35.224.199.87 35.225.158.213 35.225.238.124 35.227.253.253 35.227.254.120 35.230.175.155 35.230.177.29 35.230.183.196 35.232.107.96 35.239.26.134 35.245.4.117 35.245.213.62 52.82.172.0/22 54.240.0.0/18 54.240.64.0/19 54.240.96.0/19 69.169.224.0/20 74.125.0.0/16 76.223.128.0/19 76.223.176.0/20 173.194.0.0/16 199.127.232.0/22 199.255.192.0/22 209.85.128.0/17 216.58.192.0/19 216.239.32.0/19
These are the previously published Vanillasoft IP requirements. Your IT team should maintain the entries applicable to your services and review them when infrastructure requirements change.
Using Vanillasoft VoIP (VS Connect)? Expand the following section for additional calling-related requirements.
Vanillasoft VoIP (VS Connect)
To support reliable calling with Vanillasoft VoIP (VS Connect), your network must permit the appropriate signaling, media, provisioning, and supporting service connections.
Share these requirements with your IT or network administrator.
Required VS Connect Ports
Allow outbound connections and the associated return traffic using the applicable protocols.
| Purpose | Protocols | Ports | Destination Ports |
|---|---|---|---|
| Provisioning | HTTP/TCP, HTTPS/TCP | 80, 443 | 80, 443 |
| SIP Communications | SIP/UDP/TCP, SIP/TLS/TCP | 5060, 5061 | 5060, 5061 |
| Media | SRTP/UDP, RTP/UDP | 4000–5000, 8000–8200, 10000–60000 | 443, 8801, 10000–64999 |
These are the previously published VS Connect requirements. The specific ports needed depend on your calling configuration.
IP Addresses to Whitelist
Permit outbound traffic to the following service IP addresses and ranges, as applicable.
40.78.10.175 52.183.45.217 52.250.216.127 69.9.45.128/25 168.151.26.0/24 198.38.7.0/24 198.204.63.15 173.244.45.15 207.99.114.0/24 154.6.16.0/24
New October 2026 requirement
154.6.16.0/24 is the new Stretto data center IP range.
Customers using restrictive firewall rules should allow outbound access to this range.
Previous Stretto IP range
216.93.246.0/24
CounterPath has announced that this range will be decommissioned by the end of October 2026.
Retain required access during the transition and remove obsolete firewall rules only after your IT administrator has confirmed the migration is complete.
Additional Stretto Network Requirements
CounterPath identifies the following ports for Stretto services.
These are provider-level requirements. Your IT administrator should enable only the services applicable to your organization's configuration.
| Port | Protocol | Purpose |
|---|---|---|
| 443 | HTTPS | Client provisioning |
| 18082 | HTTPS/WSS | User services, enhanced client traces, and Help Desk Assistant |
| 18889 | HTTPS | Stretto synchronization |
| 1080 | SOCKS5 | XMPP file transfers |
| 5222 | XMPP | Client-to-server messaging connections |
Note: Not all Vanillasoft customers use every Stretto service listed above. Your network administrator should confirm which services apply before opening additional ports.
Domain Names to Allow
Ensure that the following previously published VS Connect domains are accessible as applicable:
*.google.com gsbc.ha10.sbcdax.com gsbc.ha6.sbcdax.com gsbc.udp.ha2.sbcdax.com secure-east.softphone.com secure-west.counterpath.com secure.counterpath.com
Additional CounterPath Service Domains
The following domains are identified in CounterPath's network documentation.
| Domain | Purpose |
|---|---|
| login.softphone.com | Client provisioning |
| sip.softphone.com | Team Voice SIP signaling and media |
| logging.softphone.com | User services |
| hda.softphone.com | Help Desk Assistant |
| sync.bria-x.com | Synchronization |
| uem.bria-x.com | Call statistics |
These are provider service domains and may not all apply to your Vanillasoft calling configuration.
Important: Some CounterPath services operate on cloud infrastructure with changing IP addresses. Where supported by your network security policies, allowing the required fully qualified domain names (FQDNs) is preferable to maintaining static IP addresses for those services.
Recommended Network Configuration
For the best calling experience:
- Use a wired Ethernet connection where possible. Wi-Fi can introduce jitter, packet loss, and inconsistent call quality.
- Separate voice and data traffic. Where supported, use a dedicated voice VLAN and configure Quality of Service (QoS) to prioritize calling traffic.
- Maintain stable bandwidth. Ensure sufficient upstream and downstream capacity with low latency and minimal packet loss.
- Review firewall restrictions. Confirm that required outbound connections and return traffic are permitted.
Unsupported Network Devices
The following configurations are not supported for Vanillasoft VoIP:
- Load balancers routing VoIP traffic concurrently across multiple WAN connections.
- WAN accelerators or WAN acceleration.
Device Configuration Recommendations
Where applicable, disable the following features on routers, firewalls, or switches when they interfere with VoIP traffic:
- SIP ALG (Application Layer Gateway)
- Deep Packet Inspection (DPI) applied to VoIP
- Stateful Packet Inspection (SPI) rules that modify SIP/RTP traffic
- SIP Transformation or SIP Helpers
- Power-saving Green Ethernet features
Your IT administrator should evaluate these settings before making changes.
Alternate Configuration — Dedicated Voice Network
Organizations that prefer not to modify their primary firewall may consider routing Vanillasoft VoIP traffic through a dedicated router or voice network.
A typical configuration includes:
- The primary internet modem/router continues serving the organization's data network.
- A separate router manages the voice network.
- Calling devices or applications connect through the dedicated voice network.
- The voice router permits the required ports, domains, and IP ranges.
This approach can simplify network management and help isolate voice traffic.
Need help?
Your IT or network provider can implement these changes.
If calling issues persist after the network configuration has been reviewed, contact VanillaSoft Support with the date, time, and examples of affected calls.
Google Netblocks (Maintained by Google)
Some Vanillasoft services rely on Google infrastructure, including APIs, email transport, and cloud services.
Because Google updates its IP ranges regularly, we recommend referencing Google's published lists rather than relying exclusively on static entries.
Google IP Range References
goog.json— Google-wide infrastructure and servicescloud.json— Google Cloud infrastructure
How to Use These Lists
- Where supported, configure your firewall to reference the published JSON feeds automatically.
- Avoid duplicate entries where Google ranges are already included in your existing allowlist.
- If your security policy requires static IP entries, periodically review the published ranges.
- Review both IPv4 and IPv6 requirements based on your network configuration.
Note: The JSON files contain both IPv4 and IPv6 prefixes. Only permit the destinations required for your environment.
HubSpot IP Addresses
Customers using the VanillaSoft HubSpot integration may need to permit the following previously published infrastructure ranges.
23.249.208.0/20 23.251.224.0/19 52.82.172.0/22 54.240.0.0/18 54.240.64.0/19 54.240.96.0/19 69.169.224.0/20 76.223.128.0/19 76.223.176.0/20 199.127.232.0/22 199.255.192.0/22
Note: HubSpot's infrastructure and IP requirements may change. Consult your HubSpot account documentation for current requirements.
Frequently Asked Questions
Do all VanillaSoft customers need to update their firewall?
No. The October 2026 Stretto IP change primarily affects customers who use restrictive firewall rules or IP-based allowlisting for the relevant calling services.
What IP address do I need to add?
The new Stretto IP range is:
154.6.16.0/24
Your IT administrator should permit outbound access to this range if your organization restricts the applicable connections.
What happens if we don't update our firewall?
Organizations using restrictive IP allowlists may experience connectivity problems with affected calling services.
Possible symptoms include difficulty connecting, provisioning issues, or interruptions to supporting services.
Should we remove the previous IP range?
Not immediately.
CounterPath has scheduled 216.93.246.0/24 for decommissioning by October 31, 2026.
Your IT administrator should retain required access during the transition and remove obsolete entries only after confirming the migration is complete.
Do we need to open every port listed in this article?
No.
The requirements depend on your organization's calling configuration and the services being used.
Your IT administrator should permit only the necessary traffic.
Does this change affect VanillaSoft account data?
The Stretto migration is a network infrastructure change. It does not, by itself, indicate changes to your VanillaSoft account information or stored data.
What should we do if calling stops working?
- Verify that
154.6.16.0/24is allowed where required. - Confirm the applicable ports and domains are accessible.
- Restart VS Connect and test calling functionality.
- Contact VanillaSoft Support if the issue continues.
Need Additional Assistance?
IP whitelisting and firewall configurations are managed by your organization's IT or network administrator.
VanillaSoft Support cannot directly modify your organization's firewall, antivirus software, routers, or local network settings.
However, our Support team can assist with troubleshooting VanillaSoft connectivity issues after your IT team has reviewed the applicable network requirements.
When contacting Support, please provide:
- A description of the issue.
- Any error messages received.
- The approximate date and time of the issue.
- Examples of affected calls, if applicable.
- Confirmation of whether your organization uses IP whitelisting or restrictive firewall rules.
Last reviewed: October 25, 2026
October 2026 update: Added the new Stretto IP range, documented the previous range's scheduled retirement, and expanded the VS Connect network requirements.
Network requirements may change as service providers update their infrastructure. Customers should periodically review their firewall configurations and consult their IT administrators when connectivity issues occur.
Was this article helpful?
Thanks for the feedback. Glad we could help!
Sorry this article didn't give you the answer you were looking for. If you'd like to let us know what was missing, unclear, or anything else that could help us improve it, please share as much or as little detail as you'd like.
In case we need to clarify anything. All feedback is reviewed, whether or not you leave your email.
We read and investigate all feedback, using it to continuously improve our knowledge base.
Thank you for your feedback. If you need further assistance, please reach out to our support team.