2N doorbell

Answered

Matt Baker

August 17, 2026 04:33 Edited

I have recently connected a new 2N doorbell to our NX Witness system, but having some issues with the video side of things.

It is discovering the device just fine, and adds the video and audio.  The issue is then that it constantly drops out both. If I tick the setting Keep Camera Stream and Profile settings it is the stable. However the video quality is low.

I see that it has set the Primary stream to:

rtsp://<removed>/onvif/media?transport=unicast&profile=hdwitnessP

and the Secondary stream to:

rtsp://<removed>/onvif/media?transport=unicast&profile=profile_h264_hq

However this doesn’t seem to correspond with the settings on the 2N device itself.  There is a URL generator on the device which shows a form:

rtsp://<removed>/media?vcodec=h265&vres=1920x1440&fps=30&vbr=256&audio=1&zipstream=medium

Our other Axis cameras are all working fine, its just this 2N variant.

NX Witness server and client are running 6.1.2.42921. The device is a 2N IP One.  Firmware version 3.3.0.82.2

If I configure the camera as a basic RSTP device, and give it the rtsp url suggested by the 2N device then that works fine..  however I lose the ability to set the secondary stream and normal detection so would prefer not to have to resort to this.

I have packet captures, but not sure how to provide these.


Regards,

 

Matt

0

• 

  Matt Baker

  August 17, 2026 05:51

  I have actually managed to resolve this issue myself.
  Posting incase anyone else has the same issue.

   

  I noticed under the 2N settings that the lowest Framerate that can be set in the web UI is 10 fps.  This made me wonder about the NX witness config where it likes to set the secondary channel to 7 fps by default (for motion sensing).
  
  The solution was to set a frame rate of 10 fps for the secondary channel under the Advanced tab for the camera in NX Witness.
  
  Now the image/audio connection is stable.

   

   

  0
• 

  Norman

  • Network Optix team

  August 26, 2026 13:52

  Hi Matt Baker 
  
  Most VMS or NVR systems set their own stream profiles on a device. This is why you sa: 

  rtsp://<removed>/onvif/media?transport=unicast&profile=hdwitnessP 

  instead of the expected:

  rtsp://<removed>/media?vcodec=h265&vres=1920x1440&fps=30&vbr=256&audio=1&zipstream=medium

  This one can be used to add the device directly to the VMS via its RTSP stream. 

  Also, 2N devices are not treated as Axis devices, which is why the original URL included /onvif/.

  Since changing the frame rate from 7 fps to 10 fps resolved the issue, this points to a camera bug. A VMS typically will not set a frame rate value that the device does not support. Usually, 7 fps (or the nearest supported value) is standard for secondary streams, so it appears the device incorrectly reported 7 fps as an available option during discovery.

  I recommend reporting this to the 2N team for further investigation. You can also escalate this through your Nx Reseller so we can confirm the issue on our end. 

  If you do, please include a Wireshark capture of the discovery process so we can review the ONVIF requests sent by the VMS and the device's actual responses.

  Best regards.

  0

Please sign in to leave a comment.