VMP Architecture

The VMP architecture indicates how the VMP Server is connected to other Vocera servers, to client devices, and to other servers.

The following diagram shows how the VMP Server connects to other servers inside your network firewall. As shown in the diagram, a reverse proxy can be used to communicate with entities outside of your corporate firewall.

For information on the ports that these connnections use, see Port Requirements.

Note: In older versions of VMP, devices running the Vocera Collaboration Suite app communicated with the Vocera Voice Server using a Comet connection. This connection option is still available for backward compatibility, but has been replaced by a TCP-based connection to the Vocera Client Gateway server. See Configuring VCS to Use Vocera Client Gateway for more details.

When the Vocera Collaboration Suite app is being used outside of your corporate firewall, it communicates with the Apple Push Notification Service (APNS) if you are using the Apple iOS operating system, or with the Firebase Cloud Messaging service (FCM) if you are using the Android operating system. The diagram below shows the relationships between the VMP Server, VCS, APNS, and FCM.

Note: For more information on security and the interface to APNS and FCM, see iOS and Android Security.

The VMP Server can also use the Vocera Voice Server to communicate with Vocera badges, or to interact with the Vocera SIP Telephony Gateway when VCS apps are making cellular calls.

VMP also has a SOAP-based API that external systems can use to send messages and receive delivery statuses and responses to the messages. See the Vocera Messaging Platform API Guide for more information on this API, and also see SOAP Connections for information on how to integrate an inbound SOAP connection to the VMP Server.

VMP also supports WCTP as an inbound and outbound protocol to allow third-party systems to initiate and receive messages. See WCTP Connections for more details.