Cisco Virtual office users should use the public Ethernet ports on their CVO router.

There are multiple ways to connect to dCloud sessions. If connecting through a firewall, the ports that must be permitted on that firewall depend on the method you are using to connect to the session. The table lists access methods and port numbers that must be permitted for each method.

Table 1. Ports to Open and Communication Types to Enable to Access dCloud Sessions from Behind a Firewall

For VPN connections (the first three access methods), after you permit a VPN connection to dCloud sessions for the specified port, no other modifications are required on the firewall.

For example, assume that you have an endpoint router kit that you want to connect to a dCloud session via VPN. You must permit port 443 on the firewall for the VPN to be established between the router and dCloud. After the VPN is established, any device connected to that router should be able to connect through the router directly to the active session. This is because after the VPN is established, all traffic to the active session will go over the VPN; however, any Internet browsing traffic is sent over the local connection. This is done by the split-tunneling setup on the router.

Similarly, assume that you want to connect an endpoint device to a dCloud session using AnyConnect. After the VPN connection is permitted across port 443 and established, all traffic between the endpoint device and the session across that VPN will be allowed.

Additional ports may be required for some dCloud content. Those port numbers will be provided in the content documentation or the Help for that architecture.

The ports you use on your router depends on the router model that you have. Please review Supported Routers and Endpoints for details.