Page Comparison

...

1. The UMS Console requests the UMS Server to initiate a secure terminal session.
2. The UMS Server requests the device via the Unified Protocol WebSocket to open the secure terminal session.
3. The device opens the WebSocket tunnel for secure terminal data to the UMS Server and starts the secure terminal session.
4. The UMS Server forwards the secure terminal session information to the UMS Console.
5. The UMS Console opens the WebSocket tunnel for secure terminal data to the UMS Server and starts the secure terminal session.
6. The terminal data is sent through the opened WebSockets.

Over ICG

Before the secure terminal flow:

...

1. The UMS Console requests the UMS Server to initiate a secure terminal session.
2. The UMS Server requests the ICG to open a secure terminal session.
3. The ICG requests the device via the Unified Protocol WebSocket to open a secure terminal session and the UMS Server forwards the secure terminal session information to the UMS Console.
4. The device opens the WebSocket tunnel for secure terminal data to the ICG and starts the secure terminal session and the UMS Console opens the WebSocket tunnel for secure terminal data to the ICG and starts the secure terminal session.
5. The terminal data is sent through the opened WebSockets.

IGEL OS 11 or Earlier

Direct Connection

...

The following figure illustrates the communication between the UMS Console, the UMS Server and a device:

Over ICG

Both the UMS Server and the device have established a WebSocket connection to the ICG; this WebSocket is used for commands from the UMS and messages from the device. 

The UMS Console and the device establish a dedicated WebSocket for the secure terminal with the ICG.