The minimum requirements for an Vocera TAP Adapter installation are described here.
System
Vocera Platform
uses and tests on TAP version 1.8.
Warning: Sending systems must use a persistent connection. Non-persistent
serial interface connections are inefficient and may result in issues.
Hardware
The Vocera Platform TAP integration uses DIGI SP ONE serial to IP converters to connect all serial
devices to the Vocera Platform
application. See the Configuring a Serial Device to Work with Vocera Platform
documentation for additional information.
For a standard installation, where the TAP port is a physical device such as a pocket
pager port, or an RS-232 port of a gateway server:
- A single DIGI SP ONE serial to IP converter is used.
- A Null Modem Serial Cable is connected from the pocket pager or RS-232 serial
port to DIGI SP ONE serial to IP converter.
- Vocera Platform is configured to use the DIGI SP ONE serial to IP converter as a virtual
serial port over the network.
- Vocera Platform may be deployed as either a physical or virtual server in this
configuration.
For an installation where the TAP port is virtual, such as a virtualized gateway
server of a nurse call system:
- The Vocera TAP Adapter should be configured to connect directly to the virtualized gateway as a
client or a server, depending on the other end being a server or client
respectively, using the TCP/IP host and port settings in the Vocera TAP Adapter. No DIGI is required.
- Vocera Platform may be deployed as either a physical or virtual server in this
configuration.
Serial Device Port Settings
The serial device, such as Digibox, communicates with Vocera Platform
using port 771/tcp, by default. See the Configuring a Serial Device to Work with Vocera Platform documentation for
additional information.
Warning: Do NOT use the following ports for an adapter configuration: 22,
8888, 8443, 1099, 52517, 3700, 3820, 3920, 4848, 7676, 8080, 8181, 8686, 13579,
36123, 41776, 52071, 5432, 80, 443, 25