"MessageCommunication.ProvideCurrentStateRequest" returns old camera serverId after camera was moved from one recording server to another for a while. Is this a valid behaviour?

MIP
, , , ,
1

I have two recording servers. When I move camera from one to another, “MessageCommunication.ProvideCurrentStateRequest” returns old camera serverId (old server URI too). After some time (e.g. a minute) if I call “MessageCommunication.ProvideCurrentStateRequest” again, serverId is correct.

I use this serverId to get camera current status (see picture below). If I connect old recording server I don’t get any camera status.

ProvideCurrentStatusThis causes wrong camera statuses in our system.

Is there any way how to get correct camera statuses (or correct camera serverId) after camera is moved from one recording server to another?

2

Yes, it is by design and a known behavior. Event Server get configuration every 1 minutes, if the configuration change was immediate it could cause Event Server overload, therefore there is up to one minute delay.