Appendixes |
The port numbers that must be opened on the Engage Linux 5.x machine for effective communication are listed in this topic.
Port Number | Protocol | Source | Destination | Interface/Feature | Purpose |
---|---|---|---|---|---|
443 | TCP | Engage Middleware Module |
svc.ext-inc.com 199.180.201.227 |
Provisioning APNS certificate retrieval |
|
22 | TCP | Engage Middleware Module |
svc.ext-inc.com 199.180.201.227 |
Remote Support | |
443 | TCP | Engage Middleware Module |
yum.ext-inc.com 199.180.201.238 |
Repository access for installing Ubuntu and Engage Middleware Module software updates | |
2196 | TCP | Engage Middleware Module |
feedback.push.apple.com 17.0.0.0/8 |
XMPP |
Retrieve list of failed devices from Apple Push Notification Service (APNS) Outbound, to Apple |
5223 | TCP | Engage Mobile App, iOS device |
*.push.apple.com 17.0.0.0/8 |
XXMP |
Receive push notifications on Engage Mobile App, iOS device . According to Apple, the iOS device is using Wi-Fi, port 5223 must be open outbound and inbound to the Wi-Fi. If all devices are using 4G port 5223 is not required. |
443 | TCP | Engage Mobile | Engage Mobile |
Workflow page access for Android and Engage Mobile App, iOS device s using a reverse proxy in a DMZ. Traffic from any address to Engage Middleware Module on port 443 must be open unless a reverse proxy is used. |
|
443 | TCP | Engage Middleware Module (all networks) | Reverse proxy |
Workflow page access for Android and Engage Mobile App, iOS device s using a reverse proxy in a DMZ. Traffic from any address to the proxy on port 443 must be open. Using a reverse proxy also has an internal requirement for the proxy to access Engage Middleware Module. |
|
443 | TCP |
External browser access (all networks) |
Engage Middleware Module |
When workflow page access for browsers outside the network is desired not using a reverse proxy. Traffic from any address to Engage Middleware Module on port 443 must be open unless a reverse proxy is used. |
|
443 | TCP |
External browser access (all networks) |
Reverse proxy |
When workflow page access for browsers outside the network is desired not using a reverse proxy. Traffic from any address to Engage Middleware Module on port 443 must be open unless a reverse proxy is used. |
|
5222 | TCP | Engage Mobile iOS | Engage Middleware Module | XMPP | Client to server XMPP traffic use the well known port 5222. |
5222 | TCP | Engage Mobile iOS | Edge> Engage Middleware Module | XMPP |
External XMPP traffic communicates with Engage Middleware Module through the Edge XMPP proxy on port 5222. |
5269 | TCP | Federated XMPP Server | Engage Middleware Module | XMPP |
Federated server communication uses port 5269. Federation can be initiated in either direction. This does not need to be opened externally if only federating with servers on the internal network. |
5269 | TCP | Engage Middleware Module | Federated XMPP Server | XMPP |
Federated server communication uses port 5269. Federation can be initiated in either direction. This does not need to be opened externally if only federating with servers on the internal network. |
The following tables indicates the internal network requirements
Port | Protocol | Source | Destination | Interface/feature | Purpose |
---|---|---|---|---|---|
443 | TCP | Reverse proxy | Engage Middleware Module |
Reverse proxy access to Engage Middleware Module when a proxy is used in a DMZ for external smart phone or external browsers. |
|
22 | TCP | Any SSH client | Engage Middleware Module | SSH access. | |
80 | TCP | Any HTTP client | Engage Middleware Module | Admin Console and workflow access via HTTP. | |
80 | TCP |
Cisco Phones SpectraLink Phones |
Engage Middleware Module | Workflow access from mobile devices. | |
443 | TCP | Any HTTP client | Engage Middleware Module | Admin Console and workflow access via HTTPS. | |
8888 | TCP | Any HTTP client | Engage Middleware Module | Mirth | HTTP access to Mirth client download and login. |
8443 | TCP | Mirth Client | Engage Middleware Module | Mirth | Mirth administration once client is downloaded. |
389 | TCP | Engage Middleware Module | LDAP Server | LDAP | LDAP default configuration for Active Directory. |
2021 | TCP | Engage Middleware Module | DigiBox | TAP / Serial Devices | Default non-secure DigiBox port. |
1322 | TCP | Engage Middleware Module |
Unite Connectivity Manager (UCM) |
Ascom | Push interactive messages to Ascom devices. |
5000 - 5004 | TCP | UCM | Engage Middleware Module | Ascom | UCM responses to message delivery. |
27015 | TCP | Engage Middleware Module | Vocera Server | Vocera | Communicate with Vocera server. |
25 | TCP | SMTP Client | Engage Middleware Module | Incoming e-mail | Inbound SMTP messages for the incoming e-mail interface. |
25 | TCP | Engage Middleware Module | SMTP | Outgoing e-mail | Outbound SMTP messages from the outgoing e-mail interface. |
6661 | TCP | HL7 (LLP) | Engage Middleware Module | HL7 |
Inbound HL7 messages. This is the default port configured in Mirth. This might be changed or additional connections added. Any additional connections require opening the ports. |
12000 | TCP | Navicare Server | Engage Middleware Module | Navicare | Inbound Hill-Rom Navicare messages |
2000 | UDP | Carescape Network | Engage Middleware Module | Carescape | Time synchronization. |
7000 | UDP | Carescape Network | Engage Middleware Module | Carescape | Device discovery |
7000 | UDP | Carescape Network | Engage Middleware Module | Carescape | Alarm Messages |
161 | UDP | SNMP Client | Engage Middleware Module | SNMP | Query Engage Middleware Module for SNMP parameters. |
161 | UDP | Engage Middleware Module | SNMP Manager | SNMP | Send SNMP traps for audit events. |
The following tables indicates the inbound Engage Middleware Module ports.
Port | Protocol | Purpose |
---|---|---|
22 | TCP | SSH access |
80 | TCP | HTTP access |
443 | TCP | HTTP access |
6661 | TCP | Default HL7 port |
8443 | TCP | Mirth HTTPS administrative access |
8888 | TCP | Mirth HTTP client access |
161 | TCP | SNMP |