ONVIF Integration and Camera Streams
CompletedSo I we use a few select models of Interlogix cameras (OEM HIKVISIONs) and there seems to be an issue in v3.2 that cause a lot of RTSP packet losses on this camera manufacture. Prior to v3.2 we would never get RTSP packet loss. After the update, we seem to get many. In my current issue I have TVW-5305 with built in audio. When we initially set these up they worked great. After the 3.2 update we started getting packet losses. After reviewing it seemed that the packet losses were occurring when the cameras would switch from high-res to low-res. What I found is that because we are recording audio, NX isn't pulling the audio stream on the low-res when NX is controlling the streams. So I turned on manual config under expert settings > went to my cameras to configure streams manually > made sure to turn on audio for sub-stream and everything worked perfect. Fast forward to the past week and the customer called and said that they are still having issues. Logged on and noticed that some how the auto config was turned back on for all cameras but not checked under system admin screen. There are no reporting in the audit to indicate that a user turned on auto config again. So I went back turned off auto config on each camera and the went to each camera to reprogram my streams. Now it seems as if NX will not pull the sub stream, only seems to record high-res motion stream. Prior to the system somehow defaulting back to auto config, I had no errors and the cameras were recording audio and video perfectly until march 4th when somehow auto-config was turned back on.
Do changes made under expert tab not show in audit trail?
How can i get these cameras to work properly using the auto config to pull the audio and video streams on the low-res. Ultimately i would like to leave NX configuring the streams as I can see configuring the streams manually could pose issues down the road.
Is it possible for auto config streams to be turned on somehow? I've asked my customer if they inadvertently clicked any check boxes and he said he didn't even know how to get into the sys admin menu.
-
Official comment
Hi Brandon - what firmware version on the cameras are you using?
-
Hey Tony - Using fw: S3_V3.1_FP6 which looks like the most current.
0 -
Hi Brandon - have created a support ticket for you so our guys can take a look / make suggestions.
0 -
sounds good, ill keep checking here, and thanks for fast responses.
0 -
I see RTSP packet loss across the board with HIK cameras. We don't record audio but concur with the observation that it seems to happen when the cameras switch between high and low res. Have opened a ticket around this before and support said it was likely network performance (this was ruled out) or Camera firmware.
0 -
I can back up Tim's post above. This has been an enduring issue with all Hikision cameras since the earliest versions of Nx (v1.5 IIRC is the first we used).
0 -
Hi Tim and Jon,
To be clear, I assume that RTP package losses are meant and not RTSP package loss.
RTP package loss is not a VMS issue, the VMS just detects the RTP package loss and notifies and logs these logs.
We also wrote a support article about this which can be found HERE.With all modern networks, bandwidth, network or cabling issues are becoming rarer, but still, appear every now and than.
In case that the camera is the root of the cause, it often helps is to reduce the strain on the cameras by reducing the framerate and/or the quality. In this way the camera hardware has more power left to send the packages to the VMS and, in general, fewer packages will be lost.
0 -
Yes I meant to say RTP. I always knew it was a Hikvision issue, not a VMS or network issue. We are able to duplicate the issue only with Hikvision cameras. In fact, every single Hikvision camera to date gives us these errors.
0 -
Hi All
I have continued to experience the issue with all our HIK deployments on NX - however, I updated 1 site a week ago that had 5 DS-2CD2355FWD-I cameras to the latest Australian (CSD) FW: V5.5.82 build 181222
Since this has been deployed the issue has not happened again, hope this helps others fix up this issue.
1
Post is closed for comments.
Comments
9 comments