Skip to main content

PTZ issue with Hikvision dome

Completed

Comments

8 comments

  • Norman
    • Network Optix team

    Hi Juhani Lammi,

    Did you verify PTZ controls in the Onvif Device Manager?

    If it works there, please remove the device from Nx Witness, and add it again.
    Please, before adding it again, start Wireshark with the device IP address as the host filter, and capture the process from adding till the final initialisation (streaming an image).

    If successful, discard the capture, if unsuccessful again, please share the pcapng file.

    0
  • Osku Mattinen

    Hi,

    We tried to add the device again, but still no success. PTZ works with ODM.

    Where do I send the pcapng file?

    0
  • Norman
    • Network Optix team

    Hi Osku Mattinen,

    You can share a download link with the pcapng file from Google Drive, Microsoft OneDrive, uDrop, etc here.

     

    0
  • Osku Mattinen

    OK, here you go.

    <removed_link>

    0
  • Norman
    • Network Optix team

    Hi Osku Mattinen,

    I found the issue. For some reason, the device responds to their own ISAPI (=Hikvision integration API) with an HTTP/1.1 500 Internal Server Error and therefore the VMS assumes that there are no PTZ capabilities.

    See the communication below:

    GET /ISAPI/PTZCtrl/channels HTTP/1.1
    Accept-Encoding: gzip
    Authorization: Digest username="admin", realm="DS-2TD4035D-50", nonce="4d7a6b7a4e7a6731516a51364f5463794f4755344d7a593d", uri="/ISAPI/PTZCtrl/channels", response="7531c60538cc56a6393b325cb78f31f8", cnonce="0a4f113b", nc=00000010, qop=auth
    Connection: keep-alive
    Date: Mon, 09 Jan 2023 13:32:09 GMT
    Host: 192.0.0.15
    User-Agent: Nx Witness/5.0.0.35745 (Network Optix) Mozilla/5.0 (Windows NT 6.1; WOW64)
    X-Nx-User-Name: admin

    HTTP/1.1 500 Internal Server Error
    Date: Mon, 09 Jan 2023 15:32:08 GMT
    Server: App-webs/
    Connection: close
    Content-Length: 298
    Content-Type: application/xml

    <?xml version="1.0" encoding="UTF-8"?>
    <ResponseStatus version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
    <requestURL>/ISAPI/PTZCtrl/channels</requestURL>
    <statusCode>3</statusCode>
    <statusString>Device Error</statusString>
    <subStatusCode>deviceError</subStatusCode>
    </ResponseStatus>

    This should be reported to Hikvision.

    But, no worries, most likely there is a workaround. Can you share a screenshot of the Nx Witness Desktop client, menu Camera Settings, tab General, that shows the Vendor and Model name?

    With this information, we can create a fix, which you can apply to your system and most likely this will force the camera to use Onvif PTZ controls instead, instead of the native PTZ controls.

    0
  • Osku Mattinen

    Sounds great, picture below.

    0
  • Norman
    • Network Optix team

    Hi Osku Mattinen,

    Please follow the steps as described below:

    1. Remove the device from the system.
    2. Stop the mediaserver application and paste the resource_data.json file in THIS LINK at the following location:

      For Windows: C:\Program Files\Network Optix\Nx Witness\MediaServer
      For Linux: /opt/networkoptix/mediaserver/bin/

    3. Now start the mediaserver application again.
    4. Add the device again.

    Now the device should be able to be controlled.

    To stop and start the media server, please do it as follows:

    For Windows: Open the task manager, select tab ‘Services’ find the mediaserver application, right-click and select; Stop or Start

    For Linux: Open the terminal (Ctrl+Alt+T) and enter the following command; sudo service networkoptix-mediaserver stop or sudo service networkoptix-mediaserver start.

    After this, the request should be fulfilled.
    Please confirm, and we will add it to a future patch so it remains working.

     

     

     

    0
  • Osku Mattinen

    This worked, thank you!

    0

Post is closed for comments.