You're right to enable both domain/URL whitelisting and IP-subnet access—they serve different purposes and both are required for full Webex Calling functionality. Here's a clearer breakdown:
1. Domains/URLs vs. IP Subnets
Domain & URL whitelisting: Needed for accessing services like authentication, cloud APIs, firmware upgrades, etc. (e.g., webex.com, wbx2.com)
IP Subnets + Ports: Required for the actual media and signaling data flow (e.g., SIP, RTP, NTP). These are the static IP ranges used by the Webex Calling cloud infrastructure
Bottom line: You need both—domain whitelists for control-plane traffic, and IP/port rules for data-plane traffic.
2. NTP Rule Clarified
From the port reference:
Purpose Applies To Source Port Protocol Destination Destination Port Notes
| Device time synchronization | Webex Calling devices | 51494 | UDP | Webex IP subnets | 123 | |
That "Refer to IP Subnets..." directive means the destination addresses for NTP requests are those listed in the "IP Subnets for Webex Calling Services" section
So yes, this is part of the IP Subnets for Webex Calling Services category—it’s about phones syncing time to Webex's NTP servers.
What You Should Do
Whitelist domains/URLs under the "Domains and URLs for Webex Calling Services" section.
Allow specific IP ranges and ports from the "IP Subnets for Webex Calling Services" section.
Include NTP rules:
DNS (port 53) and NTP (port 123) for internal infrastructure should also be allowed outbound if your network uses local DNS/NTP.