Document Reference: X-0036-01-07 Cadmus & Ratifi Operating Manual
Drawn: 13/11/2020
Page 62 of 66
Useful Information
3.2
Firewalls
Cadmus communicates with the cloud using the following IP address and port.
UDP Port
49152 (bi-directional)
Server 1
3.8.223.231
Server 2
35.177.84.149
The device will also make a DNS lookup to determine which of the 2 addresses above to use.
National NHS Firewalls
Implementation Date
BT N3
July 2019
HSCN
*1
July 2019
1*: HSCN = Health & Social Care Network.
3.3
Loss of Communication
In the event of loss of communication between the Cadmus device and the cloud, the device will attempt to re-connect in a short period of time after
the connection was broken. This re-try connection will continue to be re-tried until the connection is re-stored, but to extended battery life the device
will increase the time between connections. The system is set to re-attempt connection after 1, 2, 3, 4, 5, 10, 20, 30, 40, 50 and 60 minutes. The re-
attempt will not exceed the upload rate. The system will reset the re-try mechanism to 1minute after a successful connection and receipt of a valid
packet from the cloud. If the upload rate is 30 minutes, the maximum retry period will also be 30 minutes. This process will continue until the re-
attempt period >= upload rate.
3.4
Late Alarms
In the event that a device does not connect to the Cloud for more than 2 hours. The cloud will mark the Cadmus device late. The Cadmus user screens
will give a clear indication of this, and in addition the cloud will email the administrator to inform them of the loss of connection. The email alarm
will be repeated every 12 hours, until such time as the uploaded data is back within 2 hours of the current time. The Cadmus device will continue to
hold logged data in its non-volatile memory and upload the data when the connection is re-made. Late alarms are not triggered by disabled (NAP)
Cadmus devices.
The 2 hour late alarm timeout and the email repetition period are configurable via the administrator screens.
