Milestone Client streams properly but NOT SDK based application

MIP
, , ,
1

Hello,

I’m running a C# based application that login into VMS and try to stream video from cameras. Application uses MIP SDK 2018 R3 and VMS is XProtect Corporate 2022.

I’m able to login successfully and retrieve cameras, but when try to stream, no frames received from the frame callback.

Using Milestone Client I see video properly.

The C# application works well with other customer sites that use same VMS, it is qualified and I know it’s able to receive frames from callback. The issue seems to be related a specific configuration (please see attached for architecture used).

Architecture Diagram
Architecture Diagram660×480 60.7 KB

The 2 Management servers are configured with Windows Cluster.

I tried to login with C# application to the virtual IP and also to the single management nodes. The result is the same. Application is able to connect, fetch cameras, but no frames.

The same test with Milestone client succeed.

Which port should I verify to be sure there are no network issues? Why Milestone client works? I expect client and SDK will use same ports to retrieve video stream, no?

Please help me.

2

Just to give an update.

The user used from C# application is a basic user with administrator role. So no restrictions from that side.

Recorders have ports 7563 and 9001 opened. 9000 is closed. Asked customer to open that port as well.

Can be related port 9000 closed?

Thanks

3

MIP SDK 2018 R3 is old and no longer supported. Please use the newest MIP SDK, rebuild and see if the same issue happens.

If the issue happens even after having rebuilt using the newest MIP SDK NuGet package, it would be of interest to us if an unmodified sample fails in the same way. In that case, please test with Video Viewer using the newest version of the MIP SDK. https://doc.developer.milestonesys.com/html/index.html?base=samples/componentsamples/videoviewer/readme.html&tree=tree_2.html

4

Hello Rie,

thank you for your suggestion.

Updating SDK to latest fixed the issue. Great. We did not upgrade initially, because the application was able to work with another 2022 R2 VMS, but it was a single node configuration.

Thank you