omtdiscoveryserver
OMTDiscoveryServer is a console application that serves as an alternative to DNS-SD Discovery on networks that block multicast traffic.
Run the application with a command line argument specifying the TCP port to run the server on.
This can be any free port on the system that has been configured to be accessible all OMT clients that wish to use the server.
All instances of OMTSend and OMTReceive on a computer can be configured to use the OMTDiscoveryServer by creating a settings.xml file placed in the following location:
Windows
C:\ProgramData\OMT\settings.xml
MacOS
~/.OMT/settings.xml
The syntax of this configuration file is as follows:
<Settings> <DiscoveryServer>omt://x.x.x.x:port</DiscoveryServer> </Settings>
Where x.x.x.x is the IP Address of the server and port is the port
If you only want a specific process to use the discovery server, ensure the settings.xml is removed or the setting left blank.
Then before using any OMT apis, call the following:
OMTSettings.GetInstance().SetString("DiscoveryServer","omt://x.x.x.x:port");
OMTSend
Anytime a new OMTSend instance is created, the name is sent exclusely to the OMTDiscoveryServer when it is configured on the client.
DNS-SD is not used at all in this case.
The server will record the IP address used to connect and send that alongside the name to all OMT clients currently connected.
Any new OMT clients that connect will also receive a complete list from the server.
When an OMTSend instance is disposed or OMTDiscoveryServer detects that the connection to the server is lost, all OMT clients will be informed that the OMTSend is no longer available.
OMTReceive
Any new OMTReceive instances will use both standard DNS-SD discovery and OMTDiscoveryServer to find sources.
This application utilises the OMTDiscoveryServer class from libomtnet.
This class can be used by any applications that wish to integrate the server directly.
Content type
Image
Digest
sha256:94cac1a02…
Size
29.7 MB
Last updated
2 months ago
docker pull makishimuakuma/omtdiscoveryserver