Source Connectivity and Network Reachability

Once sources have been identified and validated, the next step is to ensure they are accessible from the visability environment. This means confirming that Display Nodes can successfully reach and retrieve content from each required source.

Even when sources are properly documented, network configuration is one of the most common reasons they fail to appear during commissioning.

(Insert Diagram Here)

In visability, Display Nodes are responsible for retrieving content.

When a source is requested:

• The System Manager coordinates the request
• The Display Node initiates the connection
• The source delivers content directly to the Display Node

This means that network access between Display Nodes and sources is required for every source type.

Source communication relies on standard network protocols. Depending on the source type, Display Nodes may use:

• TCP-based communication (control, web content, APIs)
• RTSP / RTP (UDP or TCP) for video streams
• HTTP / HTTPS for web-based applications and dashboards

Each of these requires that the appropriate ports and protocols are allowed across the network.

If these protocols are blocked — even if the source is reachable by IP — the content will fail to load or display.

Each source must be accessible from the system that will consume it — typically the Display Node.

This includes confirming:

• The source IP or hostname is reachable
• Required TCP/UDP ports are open
• The correct protocol (RTSP, HTTP, etc.) is allowed
• No firewall or segmentation rules are blocking access

NOTE: A successful “ping” does not mean the source is usable — the actual application traffic must be allowed.

In many deployments, sources and Display Nodes exist on different networks.

This may include:

• Separate VLANs
• Different subnets
• Routed network segments
• External or third-party systems

visability supports these environments, but requires that:

• Routing is configured between networks
• Firewall rules allow required TCP/UDP traffic
• Name resolution (DNS or static mapping) is consistent

Most source-related issues during deployment come down to blocked or misconfigured traffic.

Common examples include:

• Required Ports not open between VLANs
• RTSP or streaming traffic being blocked
• Firewall rules allowing ping but blocking application traffic
• Multicast traffic not being routed correctly

Where possible, connectivity should be validated directly from the Display Node.

Examples include:

• Opening a stream URL (RTSP/H.264)
• Accessing a web-based application or dashboard
• Verifying encoder or camera endpoints respond
• Confirming that required ports are reachable

Testing from another system is not sufficient — validation must occur from the system that will consume the source.