ONVIF issue with OEM PTZ camera

Answered

Comments

5 comments

  • Avatar
    Norman - Nx Support

    Hi Dan,

    We noticed that in some situations, devices didn't respond in time to digest authentication requests, and therefore we create a private patch that extends the response time and which should resolve the issue.

    You can use the following credentials to update your Nx Witness system:
    Build Number: 36096
    Password: hqbper

    0
    Comment actions Permalink
  • Avatar
    Dan

    Hi Norman,

    Thanks for the link, it seems to have resolved the issue. How do I keep up to date with the latest test build featuring the extended response time?

    I also have a secondary issue with cameras randomly disconnecting as seen bellow in the log and side bar. Are they related? The patch hasn't seemed to resolve the secondary issue which was present along side the first issue -

     

     

    0
    Comment actions Permalink
  • Avatar
    Norman - Nx Support

    Hi Dan,

    Regarding:

    Thanks for the link, it seems to have resolved the issue. How do I keep up to date with the latest test build featuring the extended response time?

    In this case, you couldn't know, since this was a private patch.

    Typically, we publish a public patch approx. every month. In past months, this hasn't been done for various reasons, but the next public patch should be available later this month.

    Regarding:

    I also have a secondary issue with cameras randomly disconnecting as seen bellow in the log and side bar. 

    First thing that comes to mind is that the devices are connected to another resource (VMS or NVR) causing conflicts. If this is that case, you can enable Keep camera stream and profile settings in the Camera Settings menu, tab Expert. Ideally, the cameras are only connected to the Nx Witness VMS.

    If that isn't the case, please assure the devices have been defaulted, before adding them to Nx, to avoid conflicting profiles.

    Lastly, if the issue persists, after the previous suggestions, the event should be captured with Wireshark to investigate the issue. In general, capturing the event for one camera (use the host filter in Wireshark for that) should be sufficient.

    0
    Comment actions Permalink
  • Avatar
    Dan

    Hello again,

    I have had to re-install again on my Raspberry Pi.

    It is now running version 5.0.0.36634 and I have the same issue as my first post again. Is there a test build with the: "We noticed that in some situations, devices didn't respond in time to digest authentication requests, and therefore we create a private patch that extends the response time and which should resolve the issue." fix?

    Thanks.

    0
    Comment actions Permalink
  • Avatar
    Norman - Nx Support

    Dear Dan,

    Thank you for reaching out. We appreciate your message, and we are sorry to hear that you are experiencing unexpected issues with our latest build.

    We understand the frustration that comes with encountering unexpected problems, but rest assured that we are committed to resolving this matter for you as quickly and efficiently as possible.

    To assist you with this issue, we recommend checking out our support article linked HERE. This article provides helpful suggestions that may address the issue you are experiencing.

    If the issue persists, we suggest defaulting the camera to ensure that all settings from the previous VMS build are removed. This will allow the new VMS to push its profiles correctly.

    In the event that the above steps do not resolve the issue, we would be happy to provide further assistance. If you are able to forward the camera through port forwarding, please let us know. We will then create a support ticket for you, which will provide a private environment for sharing credentials and resolving the issue.

    Thank you for your understanding, and we look forward to hearing back from you soon.

    Best regards

    0
    Comment actions Permalink

Post is closed for comments.