- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2025 11:48 PM
Hi
We are currently working on the Webex Calling Services project. Based on our security team, webex calling softphones can only be uses at designated premise and via TMSecureVPN remotely and current softphones is NOT allowed to connect via Public Internet. Seek advise on this query
1) How to restrict user use webex calling sofphone only with VPN
2)Whitelist IP range from TM CITN’s Public IP by the webex cloud calling for all TM’s users softphone connection
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2025 02:50 AM
That’s a really odd request. I’m not aware of a feature that would restrict that from server-side (and it would conceivably be difficult to support that at cloud scale). The only approach I can think of:
- Use SSO to restrict initial login to company-owned/managed devices, usually with certificates-based authentication instead of username/password.
- Run some type of security agent or host firewall on those company-owned assets that only permits traffic to egress toward Webex DNS domains and IP prefixes when on the corporate network or VPN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2025 07:22 AM
Thank you Mr Jonathan, really appreciate for the feedback. Just to reconfirm whitelist IP range from our TM CITN public IP by the webex cloud calling for all TM's users softphone connection not doable right
Whitelist IP range from TM CITN’s Public IP by the webex cloud calling for all TM’s users softphone connection

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2025 02:50 AM
That’s a really odd request. I’m not aware of a feature that would restrict that from server-side (and it would conceivably be difficult to support that at cloud scale). The only approach I can think of:
- Use SSO to restrict initial login to company-owned/managed devices, usually with certificates-based authentication instead of username/password.
- Run some type of security agent or host firewall on those company-owned assets that only permits traffic to egress toward Webex DNS domains and IP prefixes when on the corporate network or VPN.
