We are using EventTriggerWithMetadata method to start camera feed and it worked well for a while. But, recently we faced below issue;
After a successful request , camera feed starts but 1 minute later it stops. Below I’m sharing request response details. We counldn’t find any log at eventlogs and also there is enough storage on disk.
Do you have any idea?
Request:
<soapenv:Envelope xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:xpr=“http://videoos.net/2/XProtectCSServerCommand”>
soapenv:Header/
soapenv:Body
xpr:EventTriggerWithMetadata
xpr:token</xpr:token>
xpr:eventId3d860c69-98a6-4f72-8872-22ee88977fa1</xpr:eventId>
xpr:metadata
xpr:KeyValue
xpr:KeyTargetDevices</xpr:Key>
xpr:Value<targetDevices><deviceIds><deviceId>9b546b84-eba6-4861-9bd2-a12253a216b5</deviceId><deviceId>49bd5f3f-a0b0-409e-a8c5-2ac70a514462</deviceId></deviceIds></targetDevices></xpr:Value>
</xpr:KeyValue>
</xpr:metadata>
</xpr:EventTriggerWithMetadata>
</soapenv:Body>
</soapenv:Envelope>
Response:
<s:Envelope xmlns:s=“http://schemas.xmlsoap.org/soap/envelope/”>
<s:Body>
</s:Body>
</s:Envelope>
Camera Status after the request:
Only active recording rule:
Wrong explanation! - See below. If you disable the the “Default Start Feed Rule” and doesn’t replace it with something else the cameras will not be asked to stream video. This is not a consequence of the event you send.
There are scenarios where you might not want to have your cameras streaming always, if you want them to stream video always you should keep the “Default Start Feed Rule” as is.
You have a rule, and this rule starts and stops the streaming of video.
The issue is that the feed starts upon the “start_record” event, but stops after a minute, and NOT because you have sent an “end_record” event.
Is my understanding correct?
Does it make a difference if you trigger this rule manually in the Management Client instead of using the SOAP method?
Hello Bo,
Yes your understanding is correct.
But, I cant test this through GUI because as you can see my user defined event is just start / end events.
But, through API, I trigger the rule with this event along with the camera metadata. There is no way (or I dont know) to trigger start event with camera’s metadata ID.
Yes. You are right, we cannot test this way. If you add a second rule where the camera on which to record is a test camera you have chosen (not the device from metadata) but otherwise the same, then you can do a manual test if the recording stops in the same way.
Is it exactly one minute? Always one minute? Or, does it vary how long?
Does the camera stream appear to be fluent or does the camera drop and resume the stream (communication errors or similar)?
What version of XProtect is this?
I have to admit I do not really know what could cause this. Please do the observations and reply, I will try to ask around if there are know issues or similar.
I enabled the default camera feed rule and problem continues. Cameras enables and 1 minute later stops. Looks like not an API but application issue But, couldn’t figured out what could be the reason.
Please report this on Support Community instead where general issues to XProtect not involving the MIP SDK are handled. When you can reproduce the issue without involvement of the MIP SDK the issue must be in the base system and it will perhaps also be easier to troubleshoot without the extra complexity of involving the MIP SDK.
https://supportcommunity.milestonesys.com
