When we stop recording server then not responding for cameras under that recording server are not firing ?

MIP
, , ,
1

In older versions of Milestone XProtect VMS, when we stop recording server then not responding for cameras under that recording server are firing but In newer versions its not firing

So we are facing issue in Identifying camera online or offline when recording server stopped or started manually using system tray icon.

Not Responding alarms for camera also not firing

Any fix is there for this scenario ?

  MessageCommunicationManager.Start(serverId);
  messageCommunication = MessageCommunicationManager.Get(serverId);
  messageCommunication.RegisterCommunicationFilter(NewEventMessageHandler, new CommunicationIdFilter(MessageId.Server.NewEventIndication));
2

I was able to reproduce. I think it is a bug. I will report this to Milestone Development as a bug, and I will keep you updated when I have feedback.

3

Thank you for the quick response.

4

A quick question. I have tested with 2025R3, and have assumed that you do the same. If you have tests showing which versions gives a “Not Responding” message when recording server stops and in which versions it doesn’t, please let us know.

5

I’ve tested every version back to 2024R2, and in none of them does the NewEventIndication from the Event Server (ES) include a “Not Responding” message for cameras when the Recording Server (RS) is stopped.

Development’s position is that “Server Not Responding” means the ES cannot communicate with the RS. While this often correlates with the RS being unable to reach cameras—or clients being unable to reach the RS—it’s not guaranteed.

Effectively, when the ES cannot communicate with the RS, camera status becomes unknown. From that perspective, the current design may be correct: receiving “Server Not Responding” indicates the ES cannot reach the RS, and in most cases, clients also cannot reach cameras under that RS.

You can consider to change your integration so that “Server Not Responding” is used to indicate that all cameras are unreachable.

From the start, I believed your observation was correct, and I still suspect that might be the case. Could you confirm the latest version you know of where “Not Responding” was sent for all cameras when the RS was stopped?