Linux-based Analytics Server Integration via Protocol Integration

MIP
, , , ,
1

Hello,

I may have asked this question before, but after some investigations and findings I may need to rephrase.

The Setup:

  • Consider the following 3 machines are on the same network:
    • Machine A: Host OS is Windows and the machine has a single-machine installation of Milestone VMS
    • Machine B: Host OS is Windows and the machine has XProtect Smart Client installed but without the VMS.
    • Machine C: Host OS is Linux and has the Analytics Server installed.

What we did:

  • From Machine B, we used Machine A hostname to login through Milestone XProtect Smart Client. It connected properly and no extra configurations were needed (such as modifying the hosts file on Windows and adding an entry specifying the IP address of Machine A )
  • Somehow Milestone Mobile Server did the trick for Windows, it simply presented Milestone Web Client as a device that appeared in the Network tab of Windows File Explorer. Upon shutting down the Mobile Server, Machine B was no longer able to resolve the hostname of Machine A and connect properly.

On Windows, Everything seems just fine as no extra configuration is required Thanks to the Mobile Server but I am afraid that I can not say the same for Linux.

What could possibly be implemented from our end to enable our Analytics Server to `discover` the Milestone Mobile server and somehow be able to resolve the hostname of Machine A automatically just as the Windows Machine B was able to?

Also, Please direct me if this is not the right place to ask this question.

Thanks in advance

2

Hi Eslam,

In general Smart Client connects through the Management Server, while the Web client and Mobile clients use the Mobile Server.

For your integration to which one do you need to connect?

About the Mobile Server discoverability, we use the UPnP technology, so you can implement UPnP discovery protocol to find it.

Further, I would like to clarify that the Mobile Server implementation of UPnP, respectively stopping the Mobile Server, should not affect in any way the possibility to connect to the system via the Smart Client.

Kind regards,

Svetlana

3

Thanks for pointing to the UPnP technology.

For my integration, I would like to connect to Management Server using its hostname without having any extra configurations or setup.

As for why the XProtect Smart Client (from Machine B) couldn’t connect to The Management Server (on Machine A) when we shut down its Mobile Server, it was because it wasn’t able to resolve the hostname of Machine A. I was able to connect once I entered the Local IP address of Machine A. But once we restarted the Mobile Server, I was able to connect using the hostname as well. I believe it has something to do with UPnP tech giving Machine B the ability to resolve the hostname of Machine A automatically. btw, this doesn’t just apply to XProtect Smart Client as every other entity/component in Windows was able to resolve the hostname of Machine A as long as the Mobile Server is up!

Best Regards,

Eslam