Use of multicast in "VideoOS.Platform.Client.ImageViewerWpfControl"

MIP
,
1

I am developing a Form application that displays multicast video using Visual Studio C# and the .NET Framework 4.8.

To display the multicast video, I am using VideoOS.Platform.Client.ImageViewerWpfControl.

When I set the XProtect Recording Server’s multicast port number to 32,767, I was able to display the multicast video, but when I set the multicast port number to 32,768, the VideoOS.Platform.Client.ImageViewerWpfControl displayed the port number as -32,768, and I was unable to display the multicast video.

Are there any restrictions on port numbers (such as requiring the port to be 32,767 or lower) when using VideoOS.Platform.Client.ImageViewerWpfControl?

3

Hello,
I have reported this issue to Milestone Development.
We will get back to you when we get updates from them.

Best Regards, Rie

4

Thank you for your reply.
I look forward to hearing from you.

Best regards,NVS Technical Support

5

This matter concerns an inquiry from our partner.
We have received a request from our partner asking for a response.
We would appreciate it if you could respond as soon as possible.

7

Hi @NVSTS

You are right. Software is implemented so that ports up to 32767 are allowed, which corresponds to int16’s max value.

Br,
Nikolay

8

Dear Nikolay-san,

Thank you for your response.

My partner has some additional questions.

Please provide your answers.

Q1: Do you plan to make changes to support “ports above the upper limit of 32,767” in order to accommodate the specified port range? Alternatively, would it be possible to handle this on a case-by-case basis?

Q2: Does “Software” in your response refer to “ImageViewerWpfControl”?

Q3: Is this limitation specific to “ImageViewerWpfControl”?

Or does it stem from common internal reception and playback processing?

Q4: Please specify the scope of this limitation.

・Does it apply only to multicast receive ports?

・Does it apply to UDP ports in general?

・Does it extend to related port processing such as RTP/RTCP?

・Does it apply only to the display control, or to the entire reception process?

Q5: Is this behavior by design, or is it a known issue?

Q6: Please let us know if there are any plans to fix this, or if there is information regarding affected versions or versions where it has already been fixed.

Q7: We have built our application based on “ImageViewerWpfControl” and would like to avoid major rework.
Please let us know if there are any Milestone-recommended workarounds or alternative approaches that can address this without significantly changing our existing configuration.

Best regards,
NVS Technical Support

9

@NVSTS Please find my answers below:

A1. This looks like a bug and you’re the first one to report it.
A2. “Software” in my response refers to any Milestone-owned code. I’m not aware where the actual problem is.
A3. Probably not specific to ImageViewerWpfControl, but I don’t really know.
A4. It’s a newly-reported issue and I’m not aware of the scope.
A5. It’s an unknown issue, still.
A6. No plans to fix this any time soon, unless you file a customer case and it’s prioritized for development/fix.
A7. I recommend that you only configure ports up to 32767 in Recording Server’s settings. And keep using ImageViewerWpfControl as is. Don’t worry, any future change in Milestone’s internal processing of the port will not break currently working scenarios.

Hope the workaround will work well enough for you. If that’s not the case, please open a customer case and assign proper severity to it.

Best regards,
Nikolay

11

Thank you for your response.

I have no further questions.
Thank you for your assistance.