Vocera Edge IP Ports

Vocera Edge Servers

The Vocera Edge System servers do not require any outbound access to the Internet and all management, monitoring, and support access is managed over an IP specific site-to-site VPN tunnel.

If the organization wants users to be able to access the Vocera Edge System from outside the hospital network for cases such as BYOD mobile device users and/or Web Messenger, then outbound access can be configured just for those two application use cases. In these cases, Vocera Edge Solutions recommends the use of Multi-Factor Authentication (MFA). Device Authorization is available solely in the Vocera Edge system; however, integration with an MFA provider such as SecureAuth, ADFS, or Microsoft Azure AD using SAML 2.0 is recommended.

Vocera Edge Mobile Devices Running the Vocera Edge Mobile Application

While not required, Vocera Edge Solutions does recommend that several ports be allowed for outbound access to the internet in order to provide the most robust application experience. The ports that should be opened for outbound internet access allow Vocera Edge Solutions to provide functionality required by Apple Push Notification Services (APNS). The Vocera Edge mobile application uses APNS to provide notifications to devices that may be in a sleep state and to ensure that the mobile application automatically relaunches if the application crashes. The following ports should be open to the Internet to take full advantage of APNS functionality:

• TCP port 5223 to communicate with APNS
• TCP port 443 or 2197 to send notifications to APNS
• TCP port 443 is required during Apple device activation, and afterwards for fallback (on Wi-Fi only) if devices cannot reach APNS on port 5223

In addition, if your facility is using Mobile Device Management (MDM), additional ports may be required to allow the mobile devices access to check into cloud-hosted MDM services. Ports are specific to your MDM vendor.

Ports

Each managed server is configured with an active firewall. Certain ports are required to be open through the VPN tunnel, while others need to be accessible to the client or internal users.

• Interface Ports
• SQL Database Server Ports
• Customer/Edge Access Ports
• Edge Management Ports (Customer to Edge)
• Edge Management Ports (Edge to Customer)
• Cluster Ports
• Client Ports (iOS and Android)

Interface Ports

SQL Database Server Ports

Access to SQL Database Server VIP from the Edge servers and across VPN.

Customer/Edge Access Ports

Load Balancer should be configured to either send pass through traffic to port 8443 or proxy protocol traffic to port 4443.

* For application and messaging access outside of the hospital network, these ports must be accessible.

Edge Management Ports (Customer to Edge)

Accessible from customer servers to Edge across Support VPN.

Edge Management Ports (Edge to Customer)

Accessible to customer servers from Edge across Support VPN.

Cluster Ports

Accessible between servers in a cluster.

* For application and messaging access outside of the hospital network, these ports must be accessible.

Client Ports (iOS and Android)

* For application and messaging access outside of the hospital network, these ports must be accessible.