Applies to Models: Wisenet Wave
Summary:
Wisenet Wave allows you to connect to a Wave Server behind a router/network address translation without establishing port forwarding rules.
Explanation of Behavior:
Establishing the ability to maintain a constant connection to a Wave Server without having to open ports and establishing routing rules for remote access.
Resolution:
Wave Server:
- The mediator is an intermediate service that allows the Server and the Desktop client (each behind its own NAT) to find out the address of each other to establish a direct connection, running in Wave and managed by Hanwha Vision America
NOTE: For an explanation of NAT Traversal >Click Here<
- The relay (proxy) This is another cloud service responsible for relaying traffic between the client and the media server if UDP hole punching does not work
NOTE: For an explanation of what UDP Hole punching is >Click Here<
- When the Server application starts, it reports all of its local addresses to the mediator. This is needed if the media server is installed on a machine with a public IP
- The Server connects to the relay and waits for incoming requests
Wave Client:
The Desktop client takes the following steps to connect to the media server:
- If the Server can be found in a LAN using multicast, then the client establishes a direct TCP connection to that server. In this case, the mediator is not used.
Otherwise, the client sends a connection request to the mediator. - The mediator responds with all known addresses of the media server. This includes TCP addresses (forwarded and local) and the UDP address obtained by punching a hole in NAT.
After receiving this information, the client tries to establish a connection to every address simultaneously. - At the same time, the client tries to connect to the media server through a cloud relay service.
Note: To minimize connection time, there is no preference between TCP
and UDP. In some network environments, TCP may be the only option while
in others - UDP. Because of this possibility, giving preference to one
of them will slow down the time it takes to connect.
How to locate the Cloud System ID:
What is the Wave Sync System ID?
- The Wave Sync System ID is a unique identifier for the System on Wave Sync. It is a combination of numbers and letters used to identify resources. It follows a standard format described in RFC 4122.
- The Wave Sync System ID is generated when the Wave Media Server is connected to Wave Sync for the first time.
How can I locate the Cloud System ID?
1. Open your browser
2. Enter sync.wavevms.com
3. Log in to your Wave Sync Account
4. You will see the portal and the system tiles on your screen
5. Click on the System that you want to obtain the Wave System ID of
6. The Wave system ID is found in the URL and appended to /systems/
Example: https://sync.wavevms.com/systems/04fsqsya-3cb8-04b0-bb62-401b420701de/
NOTE: Wave still uses ports, and services. For a complete list
>Click Here< for our Firewall Whitelist