IP Addresses and Ports :: Dynalite Technical Documentation

IP Address Considerations

Multiroom System Manager is a suite of applications and services hosted by an on-premises server on a VLAN alongside our floor and room control devices. System Manager requires a range of static or dynamic IP addresses, allocated as follows:

Allocation Examples

250 rooms across 14 floors would require around 300 IP addresses.
1,200 rooms across two 35-floor towers would require around 1,350 addresses

Guestrooms and Suites

1 x IP address per unique room number or connected space
Recommended: +5% contingency for future reconfiguration or expansion

Notes

Only one IP address is required per room number, regardless of type
(Standard room, presidential suite, villa, etc.)

Floor Network Gateways

1 x IP address per whichever is greater:
- Each unique floor of the building
  OR
- Each group of 25 rooms
1 x IP address for each alternate/redundancy gateway

Notes

A unique floor is any floor containing guestrooms.
In projects with multiple wings or towers, each floor in each wing/tower is considered unique.
Each floor gateway supports a maximum of 25 guestrooms or suites.
Although called floor gateways, the devices are located centrally.

Central & Servers

IP addresses are required for our application and data servers, as well as any backup and redundancy provisions.

Notes

Depending on the size of the hotel and complexity of the system, we may run the system across multiple servers.
The IT architecture example in System Architecture approximates a standard (1-500 room) property.
We recommend that redundancy and backup services are included for each server.

Network Segmentation

Our system comprises of two networks types, connected via each room’s RCU:

RS-485 room/suite network, connecting up to 255 devices.
IP trunk network joining all connected rooms, meeting spaces, and public areas to the server for monitoring, control, and integration.

This structure provides several key benefits:

Network resilience - with every room independently operated by its local RCU, network outages do not affect guests.
In the event of power loss - the RCU restores the room to its previous state thanks to local, continuous storage of room state in non-volatile memory.
Incredible scalability - our nested design architecture supports thousands of rooms concurrently connected to our server, each with their own local room network of controller(s), panels, sensors, and inputs.

Firewall Rule Summary

Core System (Between RCU Devices)

Rooms & Suites <> RCU Gateways
Direction	Client > Host	Port	Connection	Encryption
Bidirectional	RCU > Gateway	50443	TCP/IP	TLS

RCU Gateways <> Interact Server (real-time)
Direction	Client > Host	Port	Connection	Encryption
Bidirectional	Interact Server > Gateway	51443	TCP/IP	TLS

Port 8734 is required for System Manager connection to the Data Access service and must not be used by any other service. Data Access usually resides on the same server, in which case a firewall rule is not required.

User Authentication and Notifications

Hotel Staff PCs <> Interact Server (Data Services)
Purpose	Direction	Client > Host	Port	Connection	Encryption
Staff accessing dashboards & reporting	Bidirectional	Hotel PC > Interact Server	443	TCP/IP	HTTPS

Interact Server (Data Services) <> Hotel LDAPS Service
Purpose	Direction	Client > Host	Port	Connection	Encryption
Dashboard user authentication	Outbound	Interact Server > LDAPS Server	636^[1]	LDAPS over TCP/IP	SSL

Interact Server (Data Services) <> Hotel SMTP Service
Purpose	Direction	Client > Host	Port	Connection	Encryption
Sending system notifications	Outbound	Interact Server > SMTP service	25, 465, 587^[1]	SMTP over TCP/IP	StartTLS Implicit SSL

API clients with token-based access are restricted to approved data.
The administrator can monitor and stop access as required.

System Integrations

Interact Server (real-time) <> Oracle Opera
Purpose	Direction	Client > Host	Port	Connection	Encryption
Synchronize Check-In/Out Events	Bidirectional	Interact Server > Oracle	By Oracle	FIAS over TCP/IP	HTTPS

Interact Server (real-time) <> Infor HMS
Purpose	Direction	Client > Host	Port	Connection	Encryption
Synchronize Check-In/Out Events	Bidirectional	Interact Server > Infor	By Infor	FIAS over TCP/IP

Interact Server (real-time) <> dormakaba Saflok Messenger LENS
Purpose	Direction	Client > Host	Port	Connection	Encryption
Understand staff or guest occupancy	From Saflok	Saflok > Interact	3270	TCP/IP

Interact Server (real-time) <> VingCard Visionline
Purpose	Direction	Client > Host	Port	Connection	Encryption
Understand staff or guest occupancy	To VingCard	Interact > VingCard	443^[2]	TCP/IP	HTTPS