LDU

Context

• Currently, only cameras connected to the HWT-IVS1800 through HWSDK support frontend intelligence configuration.

• HWSDK-compliant cameras can be connected in any of the modes illustrated in Table 3-9.
  Table 3-9 Application scenarios

  Mode	Application Scenario	Remarks
  Plug-and-play	The network cables of the device and cameras are connected to the network ports on the same VLAN on the switch.	The camera version must be 10.0.0 or later. Before connecting a camera for the first time, you do not need to log in to the camera web system to configure the camera IP address. The HWT-IVS1800 can directly discover the camera based on the MAC address. After cameras are connected to the HWT-IVS1800, a static IP address is automatically assigned to each camera. If DHCP is deployed on the network where the cameras are located: It is recommended that the static IP addresses of the cameras be not in the DHCP address pool. If the static IP addresses of the cameras need to be in the DHCP address pool, you need to bind a fixed IP address to the MAC address of each camera. For details about how to bind a fixed IP address, see the router product documentation provided by the vendor.
  By search	The network cables of the device and cameras are connected to the network ports on the same VLAN on the switch.	Before connecting a camera for the first time, you do not need to log in to the camera web system to configure the camera IP address. The HWT-IVS1800 can directly discover the camera based on the MAC address. After cameras are connected to the HWT-IVS1800, you need to assign a static IP address to each camera. If DHCP is deployed on the network where the cameras are located: It is recommended that the static IP addresses of the cameras be not in the DHCP address pool. If the static IP addresses of the cameras need to be in the DHCP address pool, you need to bind a fixed IP address to the MAC address of each camera. For details about how to bind a fixed IP address, see the router product documentation provided by the vendor.
  By network segment	If the IP addresses of the device and camera can successfully ping each other, the network cables can be connected to the network ports on the same VLAN or different VLANs.	Before connecting cameras for the first time, you need to log in to the camera web system and configure static IP addresses for these cameras. If DHCP is deployed on the network where the cameras are located: It is recommended that the static IP addresses of the cameras be not in the DHCP address pool. If the static IP addresses of the cameras need to be in the DHCP address pool, you need to bind a fixed IP address to the MAC address of each camera. For details about how to bind a fixed IP address, see the router product documentation provided by the vendor.
  By IP address
  By importing the template file		If IP addresses have been planned for a large number of cameras to be connected to the HWT-IVS1800, you can add the cameras by importing the template file.

• By default, the docker0 process of the device occupies the 172.17.0.0/16 network segment. If the camera and docker0 IP addresses are in the same network segment, the cameras will fail to be discovered or added due to IP address conflict.

  You are advised to plan the camera IP addresses in a network segment other than 172.17.0.0/16.

Prerequisites

The network connection between the HWT-IVS1800 and cameras is normal.

For details about how to check the network connection between the HWT-IVS1800 and cameras, see How Do I Check Whether the HWT-IVS1800 Is Properly Connected to the Target Network Environment?.

Plug-and-Play

Only inactive cameras are supported.

1. Log in to the LDU as the admin user. ( Logging In to the LDU)
2. Right-click on the desktop and choose Camera Management > Camera List.
3. Click . The list of cameras that are not added is displayed. Toggle on Plug and play, as shown in Figure 3-25. The device automatically searches for and adds cameras in the same VLAN as the device at the background.
   Figure 3-25 Plug-and-play
   

By Search Automatically

1. Log in to the LDU as the admin user. ( Logging In to the LDU)
2. Right-click on the desktop and choose Camera Management > Camera List.
3. Click . The list of cameras that are not added is displayed. Click Search Automatically. The device automatically searches for cameras on the same VLAN, as shown in Figure 3-26.
   Figure 3-26 Search Automatically
   

4. Connect cameras.
   1. (Optional) Assign IP addresses in batches, as shown in Figure 3-27. Select cameras, click Batch Configure, select Assign IP, and assign IP addresses in batches.
      

      • The Camera Network Segment parameter is automatically set to the southbound network segment of the current camera by default. You need to manually specify the last field of the camera network segment.
      • During the setting, you need to enter the password for registering a camera through the HWSDK protocol. The user name is fixed to admin. If an IP address in the assigned network segment has been occupied by another device, this IP address will be automatically ignored during the IP address assignment to cameras.
      Figure 3-27 Assign IP
      
   2. (Optional) Change camera passwords in batches as required, as shown in Figure 3-28. Select cameras, click Batch Configure, select Change Passwords, and change passwords for the selected cameras. The default user name is admin.
      Figure 3-28 Batch Change Camera Passwords
      
   3. (Optional) Change port numbers, as shown in the following figure. Select cameras, click Batch Configuration, select Change Port, and change camera port numbers in batches.
      

      If you connect cameras by searching for cameras, the default port number is 6061.

      Figure 3-29 Change Port
      
   4. Select cameras and click Add.
      Figure 3-30 Adding a camera
      
      

      • After you click Add, if the camera status is Adding failed (Need to activate), change the port number (6061 by default) to 6060 and add the camera again.
      • You cannot perform operations on other pages when adding cameras in batches.

5. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click next to the camera for which you want to set the intelligent attribute.
   3. Set basic parameters, as shown in Figure 3-31.
      Figure 3-31 Setting basic parameters
      

      Table 3-10 describes the mandatory parameters.

      Table 3-10 Parameter description

      Parameter	Description
      Direct Connection Preferred	Indicates whether direct connection takes precedence. After this function is enabled, the system directly obtains video streams from a camera and displays the video. The direct connection mode does not occupy the forwarding bandwidth of the server but has high requirements on the network quality. You can enable this function based on the site requirements.
      Channel Name	Video channel status (enabled or disabled). The video channel is enabled by default. NOTE: The disabled video channel is not displayed on the live video viewing and recording playback pages of the LDU, and is not reported to the cloud service or upper-level video and image management platform. You can enable or disable only the sub-channels of multi-channel cameras.
      Device Model	Camera type. You can set this parameter based on the site requirements. Fixed box camera PTZ box camera PTZ dome camera Fixed dome camera Bullet camera The value of this parameter must be the same as the actual camera type. Otherwise, some basic functions of the camera will be unavailable. For example, if you set this parameter to Fixed box camera or Fixed dome camera for a PTZ dome camera, the PTZ function of the camera will be unavailable.
      Intelligent Attribute	Intelligent attribute of a camera. The intelligent attribute of a checkpoint camera must be the same as the actual one. Otherwise, snapshots taken by the checkpoint camera cannot be uploaded to the HWT-IVS1800. This parameter does not need to be set for generic cameras. Common (default value) Target Plate analysis Object classification Person detection Target detection and plate analysis Target and person recognition Target detection and object classification Others NOTE: For details about the image access specifications supported by the HWT-IVS1800, see the software specifications of the corresponding models in the product specifications section.

By Network Segment

1. Log in to the LDU as the admin user. ( Logging In to the LDU)
2. Right-click on the desktop and choose Camera Management > Camera List.
3. Click Add Manually and choose Add by Network Segment. The page shown in Figure 3-32 is displayed.
   Figure 3-32 Add by Network Segment
   

   Table 3-11 describes the parameters.

   Table 3-11 Parameter description

   Parameter	Description
   Protocol	Protocol. Select HWSDK.
   Network Segment	Start and end IP addresses of the cameras (in the same network segment as the cameras). A precise network segment will shorten the search time.

4. (Optional) Change camera passwords in batches as required, as shown in Figure 3-33. Select cameras, click Batch Configure, select Change Passwords, and change passwords for the selected cameras. The default user name is admin.
   Figure 3-33 Batch Change Camera Passwords
   

5. (Optional) Change port numbers, as shown in the following figure. Select cameras, click Batch Configuration, select Change Port, and change camera port numbers in batches.
   

   If you connect cameras by searching for cameras, the default port number is 6061.

   Figure 3-34 Change Port
   

6. Select cameras and click Add.
   Figure 3-35 Adding a camera
   
   

   • After you click Add, if the camera status is Adding failed (Need to activate), change the port number (6061 by default) to 6060 and add the camera again.
   • You cannot perform operations on other pages when adding cameras in batches.

7. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click next to the camera for which you want to set the intelligent attribute.
   3. Set basic parameters, as shown in Figure 3-36.
      Figure 3-36 Setting basic parameters
      

      Table 3-12 describes the mandatory parameters.

      Table 3-12 Parameter description

      Parameter	Description
      Direct Connection Preferred	Indicates whether direct connection takes precedence. After this function is enabled, the system directly obtains video streams from a camera and displays the video. The direct connection mode does not occupy the forwarding bandwidth of the server but has high requirements on the network quality. You can enable this function based on the site requirements.
      Channel Name	Video channel status (enabled or disabled). The video channel is enabled by default. NOTE: The disabled video channel is not displayed on the live video viewing and recording playback pages of the LDU, and is not reported to the cloud service or upper-level video and image management platform. You can enable or disable only the sub-channels of multi-channel cameras.
      Device Model	Camera type. You can set this parameter based on the site requirements. Fixed box camera PTZ box camera PTZ dome camera Fixed dome camera Bullet camera The value of this parameter must be the same as the actual camera type. Otherwise, some basic functions of the camera will be unavailable. For example, if you set this parameter to Fixed box camera or Fixed dome camera for a PTZ dome camera, the PTZ function of the camera will be unavailable.
      Intelligent Attribute	Intelligent attribute of a camera. The intelligent attribute of a checkpoint camera must be the same as the actual one. Otherwise, snapshots taken by the checkpoint camera cannot be uploaded to the HWT-IVS1800. This parameter does not need to be set for generic cameras. Common (default value) Target Plate analysis Object classification Person detection Target detection and plate analysis Target and person recognition Target detection and object classification Others NOTE: For details about the image access specifications supported by the HWT-IVS1800, see the software specifications of the corresponding models in the product specifications section.

By IP Address

1. Log in to the LDU as the admin user. ( Logging In to the LDU)
2. Right-click on the desktop and choose Camera Management > Camera List.
3. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-37 is displayed.
   Figure 3-37 Add by IP Address
   

   Table 3-13 describes the parameters you need to set. Parameters marked with an asterisk (*) in the figure are mandatory.

   Table 3-13 Parameter description

   Parameter	Description
   Protocol	Protocol. Select HWSDK(DeviceToPlatform).
   IP Address	IP address of a camera.
   User Name/Password	User name and password for registering a camera through the HWSDK protocol.
   Management Port	If the cameras use the encrypted transmission protocol TLS, set the port number to 5062. If the camera uses a non-encrypted transmission protocol, set the port number to 5060. Non-encrypted transmission protocols may cause security risks. You are advised to use an encrypted transmission protocol. If a camera fails to be connected, rectify the fault by referring to Failure to Verify a Camera When You Follow the Wizard to Add It.
   Camera Name	User-defined camera name.
   Camera Code	Camera ID. The value must be the same as the device ID in Figure 3-39.
   AccessWay	Transmission protocol. HTTP HTTPS HTTP/HTTPS HTTP is an insecure protocol. Exercise caution on data security when using it. HTTPS is recommended.

4. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click next to the camera for which you want to set the intelligent attribute.
   3. Set basic parameters, as shown in Figure 3-38.
      Figure 3-38 Setting basic parameters
      

      Table 3-14 describes the mandatory parameters.

      Table 3-14 Parameter description

      Parameter	Description
      Direct Connection Preferred	Indicates whether direct connection takes precedence. After this function is enabled, the system directly obtains video streams from a camera and displays the video. The direct connection mode does not occupy the forwarding bandwidth of the server but has high requirements on the network quality. You can enable this function based on the site requirements.
      Channel Name	Video channel status (enabled or disabled). The video channel is enabled by default. NOTE: The disabled video channel is not displayed on the live video viewing and recording playback pages of the LDU, and is not reported to the cloud service or upper-level video and image management platform. You can enable or disable only the sub-channels of multi-channel cameras.
      Device Model	Camera type. You can set this parameter based on the site requirements. Fixed box camera PTZ box camera PTZ dome camera Fixed dome camera Bullet camera The value of this parameter must be the same as the actual camera type. Otherwise, some basic functions of the camera will be unavailable. For example, if you set this parameter to Fixed box camera or Fixed dome camera for a PTZ dome camera, the PTZ function of the camera will be unavailable.
      Intelligent Attribute	Intelligent attribute of a camera. The intelligent attribute of a checkpoint camera must be the same as the actual one. Otherwise, snapshots taken by the checkpoint camera cannot be uploaded to the HWT-IVS1800. This parameter does not need to be set for generic cameras. Common (default value) Target Plate analysis Object classification Person detection Target detection and plate analysis Target and person recognition Target detection and object classification Others NOTE: For details about the image access specifications supported by the HWT-IVS1800, see the software specifications of the corresponding models in the product specifications section.

Proactive Registration

1. Enable the proactive registration function for cameras.
   1. Log in to the camera web system as the admin user. ( Logging in to the Camera Web System)
   2. Choose Settings > Network > Platform Connection > SDK Settings.
   3. Set platform connection parameters, as shown in Figure 3-39.
      Figure 3-39 Setting platform connection parameters
      

      Table 3-15 describes the parameters.

      Table 3-15 Parameter description

      Parameter	Description
      Active SDK registration	Indicates whether to enable proactive registration for the camera. If this check box is selected, the camera will proactively register with the HWT-IVS1800 through HWSDK.
      Two-factor authentication	Indicates whether to enable the authentication mode between the camera and the platform. If this check box is selected, TLS authentication is used. If this check box is not selected, password authentication is used. You are advised to select this check box to improve system security.
      Registration type	Registration type. Select Single-server mode.
      Device ID	Camera ID used to connect to the HWT-IVS1800. Enter a 20-digit decimal number. The value is padded with zeros if there are not enough digits. The ID of each camera must be unique. NOTE: The 20-digit decimal number you entered must be the same as the connection code configured on the HWT-IVS1800. Otherwise, the connection fails.
      Platform IP	IP address of the HWT-IVS1800.
      Port number	If Two-factor authentication is selected, set Port number to 5062. If Two-factor authentication is not selected, set Port number to 5060. If a camera fails to be connected, rectify the fault by referring to Failure to Verify a Camera When You Follow the Wizard to Add It.
      Enable SDK	Indicates whether to enable SDK. Select this check box when the camera is passively registered with the device through the HWSDK protocol. In addition, you do not need to set all the preceding parameters.

2. Connect cameras to the HWT-IVS1800.
   1. Log in to the LDU as the admin user. ( Logging In to the LDU)
   2. Right-click on the desktop and choose Camera Management > Camera List.
   3. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-40 is displayed.
      Figure 3-40 Add by IP Address
      

      Table 3-16 describes the parameters you need to set. Parameters marked with an asterisk (*) in the figure are mandatory.

      Table 3-16 Parameter description

      Parameter	Description
      Protocol	Protocol. Select HWSDK(DeviceToPlatform).
      IP Address	IP address of a camera.
      User Name/Password	User name and password for registering a camera through the HWSDK protocol.
      Management Port	If the cameras use the encrypted transmission protocol TLS, set the port number to 5062. If the camera uses a non-encrypted transmission protocol, set the port number to 5060. Non-encrypted transmission protocols may cause security risks. You are advised to use an encrypted transmission protocol. If a camera fails to be connected, rectify the fault by referring to Failure to Verify a Camera When You Follow the Wizard to Add It.
      Camera Name	User-defined camera name.
      Camera Code	Camera ID. The value must be the same as the device ID in Figure 3-39.
      AccessWay	Transmission protocol. HTTP HTTPS HTTP/HTTPS HTTP is an insecure protocol. Exercise caution on data security when using it. HTTPS is recommended.

   4. Set the type and intelligent attribute of cameras.
      1. Right-click on the desktop and choose Camera Management > Camera List.
      2. Click next to the camera for which you want to set the intelligent attribute.
      3. Set basic parameters, as shown in Figure 3-41.
         Figure 3-41 Setting basic parameters
         

         Table 3-17 describes the mandatory parameters.

         Table 3-17 Parameter description

         Parameter	Description
         Direct Connection Preferred	Indicates whether direct connection takes precedence. After this function is enabled, the system directly obtains video streams from a camera and displays the video. The direct connection mode does not occupy the forwarding bandwidth of the server but has high requirements on the network quality. You can enable this function based on the site requirements.
         Channel Name	Video channel status (enabled or disabled). The video channel is enabled by default. NOTE: The disabled video channel is not displayed on the live video viewing and recording playback pages of the LDU, and is not reported to the cloud service or upper-level video and image management platform. You can enable or disable only the sub-channels of multi-channel cameras.
         Device Model	Camera type. You can set this parameter based on the site requirements. Fixed box camera PTZ box camera PTZ dome camera Fixed dome camera Bullet camera The value of this parameter must be the same as the actual camera type. Otherwise, some basic functions of the camera will be unavailable. For example, if you set this parameter to Fixed box camera or Fixed dome camera for a PTZ dome camera, the PTZ function of the camera will be unavailable.
         Intelligent Attribute	Intelligent attribute of a camera. The intelligent attribute of a checkpoint camera must be the same as the actual one. Otherwise, snapshots taken by the checkpoint camera cannot be uploaded to the HWT-IVS1800. This parameter does not need to be set for generic cameras. Common (default value) Target Plate analysis Object classification Person detection Target detection and plate analysis Target and person recognition Target detection and object classification Others NOTE: For details about the image access specifications supported by the HWT-IVS1800, see the software specifications of the corresponding models in the product specifications section.

Context

• ONVIF-compliant cameras can be connected to the IVS1800 in either of the modes illustrated in Table 3-18.
  Table 3-18 Application scenarios

  Mode	Application Scenario	Remarks
  By network segment	If the IP addresses of the device and camera can successfully ping each other, the network cables can be connected to the network ports on the same VLAN or different VLANs.	Before connecting cameras for the first time, you need to log in to the camera web system and configure static IP addresses for these cameras. If DHCP is deployed on the network where the cameras are located: It is recommended that the static IP addresses of the cameras be not in the DHCP address pool. If the static IP addresses of the cameras need to be in the DHCP address pool, you need to bind a fixed IP address to the MAC address of each camera. For details about how to bind a fixed IP address, see the router product documentation provided by the vendor.
  By IP address
  By importing the template file		If IP addresses have been planned for a large number of cameras to be connected to the HWT-IVS1800, you can add the cameras by importing the template file.

• Cameras with the same IP address and port number cannot be connected.
• Currently, only cameras connected to the HWT-IVS1800 through HWSDK support frontend intelligence configuration.
• By default, the docker0 process of the device occupies the 172.17.0.0/16 network segment. If the camera and docker0 IP addresses are in the same network segment, the cameras will fail to be discovered or added due to IP address conflict.

  You are advised to plan the camera IP addresses in a network segment other than 172.17.0.0/16.

• Only IPv6 cameras connected through ONVIF are supported. You can request streams from such cameras.
• NVR devices cannot be connected through ONVIF. If NVR devices need to be connected, you are advised to connect them through RTSP.

Prerequisites

The network connection between the HWT-IVS1800 and cameras is normal.

For details about how to check the network connection between the HWT-IVS1800 and cameras, see How Do I Check Whether the HWT-IVS1800 Is Properly Connected to the Target Network Environment?.

By Network Segment

1. Enable the ONVIF protocol on the camera side.
   1. Log in to the camera web system as the admin user. ( Logging in to the Camera Web System)
   2. Choose Settings > Network > Platform Connection > Second Protocol Parameters.
   3. Select Enable ONVIF.

2. Confirm with the camera vendor whether only the MD5 algorithm is supported for ONVIF connection.
   • If not, go to the next step.
   • If so, check whether the MD5 algorithm is enabled.
     1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
     2. Choose System > Network Security Configuration.
     3. Select Advanced. In the MD5 Algorithm area, select Enable MD5 when RTSP requests media stream from cameras and Enable MD5 for connection to camera through ONVIF.

        Using the MD5 algorithm may cause cyber security risks. Therefore, perform cyber security controls after enabling this algorithm.

3. (Optional) If NAT networking is used between the HWT-IVS1800 and camera, set advanced parameter ONVIF_NAT to 1.
   1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
   2. Choose System > Advanced Configuration.
   3. Set ONVIF_NAT to 1, as shown in Figure 3-42.
      

      If the HWT-IVS1800 is on the public network and the camera is on the private network, in the port mapping on the firewall, the external RTSP port must be the same as the internal RTSP port. (You need to change the camera's RTSP port to the post-NAT port.)

      Figure 3-42 Setting advanced parameters
      

4. Log in to the LDU as the admin user. ( Logging In to the LDU)
5. Right-click on the desktop and choose Camera Management > Camera List.
6. Click Add Manually and select Add by Network Segment. The page shown in Figure 3-43 is displayed.
   Figure 3-43 Add by Network Segment
   

   Table 3-19 describes the parameters.

   Table 3-19 Parameter description

   Parameter	Description
   Protocol	Protocol. Select ONVIF.
   Network Segment	Start and end IP addresses of the cameras (in the same network segment as the cameras). A precise network segment will shorten the search time.

7. Select cameras and click Add.
   Figure 3-44 Adding a camera
   
   

   • After you click Add, if the camera status is Adding failed (Need to activate), change the port number (6061 by default) to 6060 and add the camera again.
   • You cannot perform operations on other pages when adding cameras in batches.

8. (Optional) Determine whether to import the ONVIF connection certificate based on the site requirements.

   If necessary, import it by referring to Replacing the Certificate for Southbound Connection.

By IP Address

1. Enable the ONVIF protocol on the camera side.
   1. Log in to the camera web system as the admin user. ( Logging in to the Camera Web System)
   2. Choose Settings > Network > Platform Connection > Second Protocol Parameters.
   3. Select Enable ONVIF.

2. Confirm with the camera vendor whether only the MD5 algorithm is supported for ONVIF connection.
   • If not, go to the next step.
   • If so, check whether the MD5 algorithm is enabled.
     1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
     2. Choose System > Network Security Configuration.
     3. Select Advanced. In the MD5 Algorithm area, select Enable MD5 when RTSP requests media stream from cameras and Enable MD5 for connection to camera through ONVIF.

     Using the MD5 algorithm may cause cyber security risks. Therefore, perform cyber security controls after enabling this algorithm.

3. (Optional) If NAT networking is used between the HWT-IVS1800 and camera, set advanced parameter ONVIF_NAT to 1.
   1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
   2. Choose System > Advanced Configuration.
   3. Set ONVIF_NAT to 1, as shown in Figure 3-45.
      

      If the HWT-IVS1800 is on the public network and the camera is on the private network, in the port mapping on the firewall, the external RTSP port must be the same as the internal RTSP port. (You need to change the camera's RTSP port to the post-NAT port.)

      Figure 3-45 Setting advanced parameters
      

4. Log in to the LDU as the admin user. ( Logging In to the LDU)
5. Right-click on the desktop and choose Camera Management > Camera List.
6. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-46 is displayed.
   Figure 3-46 Add by IP Address
   

   Table 3-20 describes the parameters you need to set. Parameters marked with an asterisk (*) in the figure are mandatory.

   Table 3-20 Parameter description

   Parameter	Description
   Protocol	Protocol. Select ONVIF.
   IP Address	Camera IP address. You can set this parameter based on the site requirements.
   Camera Name	User-defined camera name.
   User Name/Password	User name and password for registering a camera.
   Management Port	Default port generated after you select a protocol. You can also customize a port ranging from 1 to 65535.
   AccessWay	Transmission protocol. You can set this parameter as required. HTTP HTTPS HTTP/HTTPS HTTP is an insecure protocol. Exercise caution on data security when using it. HTTPS is recommended. NOTE: If NAT networking is used between the HWT-IVS1800 and cameras, this parameter must be set to HTTP/HTTPS.

7. Set the camera type.
   1. Right-click on the desktop and choose Camera Management.
   2. On the page that is displayed, choose Camera List.
   3. Click next to the camera for which you want to set the intelligent attribute.
   4. Set basic parameters, as shown in Figure 3-47.
      Figure 3-47 Setting basic parameters
      

      Table 3-21 describes the mandatory parameters.

      Table 3-21 Parameter description

      Parameter	Description
      Device Model	Camera type. You can set this parameter based on the site requirements. Fixed box camera PTZ box camera PTZ dome camera Fixed dome camera Bullet camera The value of this parameter must be the same as the actual camera type. Otherwise, some basic functions of the camera will be unavailable. For example, if you set this parameter to Fixed box camera or Fixed dome camera for a PTZ dome camera, the PTZ function of the camera will be unavailable.
      Intelligent Attribute	Intelligent attribute of a camera. The intelligent attribute of a checkpoint camera must be the same as the actual one. Otherwise, snapshots taken by the checkpoint camera cannot be uploaded to the HWT-IVS1800. This parameter does not need to be set for generic cameras. Common (default value) Target Vehicle Object classification Person Target+Vehicle Target+Person Target+Object classification Others

8. (Optional) Determine whether to import the ONVIF connection certificate based on the site requirements.

   If necessary, import it (which must be the same as that used by the camera) by referring to Replacing the Certificate for Southbound Connection.

Context

• GB/T 28181-compliant cameras can be connected to the device in only one mode illustrated in Table 3-18.
  Table 3-22 Application scenarios

  Mode	Application Scenario	Remarks
  By IP address	If the IP addresses of the IVS device and camera can successfully ping each other, the network cables can be connected to the network ports on the same VLAN or different VLANs.	Log in to the camera web system and configure camera IP addresses.
  By importing the template file		If IP addresses have been planned for a large number of cameras to be connected to the HWT-IVS1800, you can add the cameras by importing the template file.

• Currently, only cameras connected to the HWT-IVS1800 through HWSDK support frontend intelligence configuration.
• OSD cannot be configured for third-party cameras connected through GB/T 28181.
• By default, the docker0 process of the device occupies the 172.17.0.0/16 network segment. If the camera and docker0 IP addresses are in the same network segment, the cameras will fail to be discovered or added due to IP address conflict.

  You are advised to plan the camera IP addresses in a network segment other than 172.17.0.0/16.

• When the southbound network port is used for connecting to the IVS1800 through GB/T 28181, single-channel cameras can be connected but multi-channel cameras and NVR devices cannot. If NVR devices need to be connected through the southbound network port, you are advised to use RTSP to add the NVR devices.

Prerequisites

The network connection between the HWT-IVS1800 and cameras is normal.

For details about how to check the network connection between the HWT-IVS1800 and cameras, see How Do I Check Whether the HWT-IVS1800 Is Properly Connected to the Target Network Environment?.

Procedure

1. (Optional) Disable strong password verification on the IVS1800. Perform this step only when a weak password is used for a camera to be connected through GB/T 28181.
   1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
   2. Choose System > Advanced Configuration and set Module to SCU.
   3. Set PURegStrongPwd to 0 to disable strong password verification, as shown in Figure 3-48.
      Figure 3-48 Disabling strong password verification
      

2. Enable the GB/T 28181 protocol on the camera side.
   1. Log in to the camera web system as the admin user. ( Logging in to the Camera Web System)
   2. Choose Configuration > Network > Advanced Settings > Platform Connection > Second Protocol Parameters > T28181.
   3. Set GB/T 28181 parameters, as shown in Figure 3-49.
      Figure 3-49 Setting GB/T 28181 parameters
      

      Table 3-23 describes the key parameters.

      Table 3-23 GB/T 28181 parameters

      Parameter		Description
      GB/T 28181		If this parameter is selected, the GB/T 28181 protocol is enabled.
      Protocol		Protocol. You can select a value from the drop-down list box. NOTE: If TCC-VMS-2020 is selected, the active and standby servers can be configured. When the active (standby) server fails, services are automatically switched to the standby (active) server.
      GB/T 28181 Advanced Parameters	Max recordings can be queried	Maximum number of recordings carried in a packet during recording query when GB/T 28181 is used for platform connection. The value is an integer ranging from 1 to 20. The default value is 10. If the HWT-IVS1800 limits the packet size, you can properly adjust the value of this parameter. Adjusting the value of this parameter affects the recording query speed.
      Compatibility Parameters	H.265	If this parameter is selected, the H.265 and H.264 encoding protocols are supported when the camera is connected to the HWT-IVS1800 through the GB/T 28181 protocol. If this parameter is not selected, only the H.264 encoding protocol is supported when the camera is connected to the HWT-IVS1800 through the GB/T 28181 protocol.
      	Clear media streams triggered by same subject	If this parameter is selected, only one channel of video streams can be obtained if the HWT-IVS1800 requests video streams with the same subject ID. If this parameter is not selected, multiple channels of video streams can be obtained if the HWT-IVS1800 requests video streams with the same subject ID.
      	Shanghai Local Standard	If this parameter is selected, the Shanghai local protocol is supported. NOTE: If the Shanghai local standard is enabled, the image capture function of the HWT-IVS1800 does not take effect.
      	Video stream type	Video stream type. You can select a value from the drop-down list box. Auto: Sends media streams based on the request of the HWT-IVS1800. Video stream: Sends only video streams. Hybrid stream: Sends video and audio streams.
      	Signaling transmission mode	Signaling transmission mode. The options include UDP and TCP. Only UDP can be selected for cameras to be connected to the HWT-IVS1800.
      Service Parameters	Downlink voice stream for voice intercom	Protocol of downlink voice streams for voice intercom. The value can be UDP or TCP. NOTE: If a camera and the HWT-IVS1800 are on different network segments, you are advised to set this parameter to TCP.
      	Max. timeouts	If the number of consecutive heartbeat timeouts reaches the value specified by this parameter, the camera cannot connect to the HWT-IVS1800. The default value 3 is recommended. NOTE: The maximum number of timeouts for the camera and HWT-IVS1800 must be the same.
      	Registration validity period (s)	Validity period of the camera registration with the HWT-IVS1800. The default value is 86400 (one day). NOTE: If the camera fails to be registered within 86400s, the registration fails. You are advised to use the default value. Before the validity period expires, the camera initiates a registration request to the HWT-IVS1800 again.
      	Heartbeat interval (s)	Time interval at which the camera sends heartbeat messages. The default value 60 is recommended. NOTE: The camera and the HWT-IVS1800 must have the same heartbeat interval.
      Server Parameters	Server IP	HWT-IVS1800 IP address.
      	Port number	Port used by the HWT-IVS1800 to listen on cameras connecting to the HWT-IVS1800 through GB/T 28181. The default value is 5060. Before selecting the Port number check box, ensure that the configured port is within the range of 1 to 65535.
      	Server code	GB/T 28181 server code. The value is a string of 1 to 64 characters, including letters and digits. NOTE: If a camera is to be connected to the HWT-IVS1800, the eleventh to thirteenth digits of the server code must be 200. The local domain code does not need to be configured for the HWT-IVS1800.
      	SIP server domain	Domain name, which is a string of up to 127 digits.
      Device Parameters	Device ID	Unique ID of a camera. The value contains 1–64 characters, including letters and digits. The value must be the same as the camera ID configured on the HWT-IVS1800. NOTE: This parameter is mandatory. If this parameter is not set, service alarms cannot be reported to the HWT-IVS1800. If a camera is to be connected to the HWT-IVS1800, the eleventh to thirteenth digits of the device ID must be 132. Besides, the device ID must be different from the lens ID. Otherwise, you cannot view live video from the camera on the HWT-IVS1800.
      	Password	Password used by a camera to register with the HWT-IVS1800. NOTE: The value of this parameter must be the same as the registration password configured on the HWT-IVS1800. If they are different, the camera will fail to connect to the HWT-IVS1800.
      	Name	Login name used for registering a camera with the HWT-IVS1800. The value can contain digits or other characters.
      	Local port	Port number of the camera for connecting to the SIP server. NOTE: The value is an integer ranging from 1024 to 65535.
      	Alarm input ID	Alarm input ID of the camera. The value is a string of 0 to 64 characters, including letters and digits. NOTE: You need to manually enter the value. The eleventh to thirteenth digits must be 134. Otherwise, the HWT-IVS1800 cannot report alarms properly.
      	Audio output ID	Audio output ID of the camera. The value is a string of 0 to 64 characters, including letters and digits. NOTE: You need to manually enter the value. The eleventh to thirteenth digits must be 137. Otherwise, the HWT-IVS1800 cannot transmit uplink or downlink audio streams properly.
      	Authentication mode	SHA256: Only the SHA256 authentication method is supported. MD5/SHA256: Both MD5 and SHA256 authentication methods are supported. NOTE: The MD5 authentication method has security risks. Therefore, you are advised to use the SHA256 authentication method. The value of this parameter must be the same as that configured on the HWT-IVS1800. Otherwise, the registration fails.
      Channel Parameters	Channel	Channel type of the camera.
      	Stream index	Type of streams to be sent to the platform. You can select the primary stream or a secondary stream. The default value Primary stream is recommended.
      	Lens ID	Lens ID. The value is a string of 0 to 64 characters, including letters and digits. For a multi-lens camera, you need to select a channel type from the drop-down list box and set a unique ID for each lens. NOTE: If a camera is to be connected to the HWT-IVS1800, the eleventh to thirteenth digits of the lens ID must be 131 or 132. Besides, the device ID must be different from the lens ID. Otherwise, live video from the camera cannot be viewed on the HWT-IVS1800.

3. Confirm with the camera vendor whether only the MD5 algorithm is supported for GB/T 28181 connection.
   • If not, go to the next step.
   • If so, check whether the MD5 algorithm is enabled.
     1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
     2. Choose System > Network Security Configuration.
     3. Select Advanced.
     4. In the MD5 Algorithm area, select Enable MD5 for connection to camera through GB/T 28181.
     

     To enable the MD5 algorithm for a camera of 8.0.0, 8.1.0, or 8.2.RCx (excluding 8.2.0 and later patch versions), log in to the OMU portal, choose System > Advanced Configuration, and set EnableMD5_SHA256_S_28181 to 2.

     Using the MD5 algorithm may cause cyber security risks. Therefore, perform cyber security controls after enabling this algorithm.

4. Log in to the LDU as the admin user. ( Logging In to the LDU)
5. Right-click on the desktop and choose Camera Management > Camera List.
6. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-50 is displayed.
   Figure 3-50 Add by IP Address
   

   Table 3-24 describes the parameters you need to set. Parameters marked with an asterisk (*) in the figure are mandatory.

   Table 3-24 Parameter description

   Parameter	Description
   Protocol	Protocol. Select T28181.
   Password	Password of the camera to be connected.
   Camera Name	User-defined camera name.
   Camera Code	ID and password of a camera. The camera ID and password must be the same as the device ID and password configured in Figure 3-49.
   AccessWay	Transmission protocol. HTTP HTTPS HTTP/HTTPS HTTP is an insecure protocol. Exercise caution on data security when using it. HTTPS is recommended.

7. Set the camera type.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click next to the camera for which you want to set the intelligent attribute.
   3. Set basic parameters, as shown in Figure 3-51.
      Figure 3-51 Setting basic parameters
      

      Table 3-25 describes the mandatory parameters.

      Table 3-25 Parameter description

      Parameter	Description
      Device Model	Camera type. You can set this parameter based on the site requirements. Fixed box camera PTZ box camera PTZ dome camera Fixed dome camera Bullet camera The value of this parameter must be the same as the actual camera type. Otherwise, some basic functions of the camera will be unavailable. For example, if you set this parameter to Fixed box camera or Fixed dome camera for a PTZ dome camera, the PTZ function of the camera will be unavailable.
      Intelligent Attribute	Intelligent attribute of a camera. The intelligent attribute of a checkpoint camera must be the same as the actual one. Otherwise, snapshots taken by the checkpoint camera cannot be uploaded to the HWT-IVS1800. This parameter does not need to be set for generic cameras. Common (default value) Target Vehicle Object classification Person Target+Vehicle Target+Person Target+Object classification Others

Context

The Real Time Streaming Protocol (RTSP) is an application-layer real-time stream transmission protocol in the TCP/IP protocol suite. It defines how applications transmit multi-media data effectively over network IP networks. RTSP allows operations (such as play, pause, and fast-forward) on streaming media, and defines specific control messages, operation methods, and status codes.

Restrictions

• RTSP-compliant cameras can be connected to the device in only one mode illustrated in Table 3-26.
  Table 3-26 Application scenarios

  Mode	Application Scenario	Remarks
  By IP address	If the IP addresses of the IVS device and camera can successfully ping each other, the network cables can be connected to the network ports on the same VLAN or different VLANs.	Log in to the camera web system and configure camera IP addresses.
  By importing the template file		If IP addresses have been planned for a large number of cameras to be connected to the HWT-IVS1800, you can add the cameras by importing the template file.

• When a camera is connected to the HWT-IVS1800 through RTSP, the video parameters modified on the LDU or iClient S100 do not take effect. You need to modify the video parameters on the camera side.
• Cameras with the same URL cannot be added.
• Currently, only cameras connected to the HWT-IVS1800 through HWSDK support frontend intelligence configuration.
• By default, the docker0 process of the device occupies the 172.17.0.0/16 network segment. If the camera and docker0 IP addresses are in the same network segment, the cameras will fail to be discovered or added due to IP address conflict.

  You are advised to plan the camera IP addresses in a network segment other than 172.17.0.0/16.

Prerequisites

The network connection between the HWT-IVS1800 and cameras is normal.

For details about how to check the network connection between the HWT-IVS1800 and cameras, see How Do I Check Whether the HWT-IVS1800 Is Properly Connected to the Target Network Environment?.

Procedure

1. Enable the MD5 algorithm on the OMU portal.
   1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
   2. Choose System > Network Security Configuration.
   3. Select Advanced. In the MD5 Algorithm area, select Enable MD5 when RTSP requests media streams from cameras.

      Using the MD5 algorithm may cause cyber security risks. Therefore, perform cyber security controls after enabling this algorithm.

2. Add cameras on the HWT-IVS1800.
   1. Log in to the LDU as the admin user. ( Logging In to the LDU).
   2. Right-click on the desktop and choose Camera Management > Camera List.
   3. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-52 is displayed.
      Figure 3-52 Add by IP Address
      

      Table 3-27 describes the parameters. Parameters marked with an asterisk (*) in the figure are mandatory.

      Table 3-27 Parameter description

      Parameter		Description
      Protocol		Protocol. Select RTSP.
      User Name/Password		User name and password of the camera to be connected.
      IP Address		IP address of the camera to be connected.
      Management Port		Management port number, which can be customized but must be the same as the port number of the camera to be connected. The default port number is 554.
      Camera Name		Name of the camera to be connected.
      Primary Stream Resource Path/Secondary Stream Resource Path	-	URL for obtaining streams from the camera to be connected through RTSP. The URL varies depending on the camera vendor.

      

      If the connected camera is always displayed online but the video image shot by the camera appears abnormal, stream pulling fails. In this case, check whether the camera is properly connected. If the camera is disconnected, perform the connection steps in this section to reconnect the camera.

Restrictions

• In the HWSDK-compliant (passive registration), ONVIF-compliant, and Dahua camera access scenarios, cameras with the same IP address and port number cannot be added.
• If NAT networking is used between the HWT-IVS1800 and camera, you need to set advanced parameter ONVIF_NAT to 1 before importing ONVIF-compliant cameras. For details, see Setting Advanced Parameter ONVIF_NAT.
• In the RTSP-compliant access scenario, cameras with the same URL cannot be added.
• OSD cannot be configured for third-party cameras connected through GB/T 28181.

Procedure (on the LDU)

1. Log in to the LDU as the admin user. ( Logging In to the LDU)
2. Right-click on the desktop and choose Camera Management > Camera List.
3. Download the template file for adding cameras. If the template file has been filled in, go to 5.
   Click Import. On the page that is displayed, click Download Template, edit the template name, select the export path, and click OK to download the template file to the local computer, as shown in Figure 3-53.

   Figure 3-53 Downloading the template file
   

4. Fill in the template file. For details about how to set parameters, see Table 3-28. Table 3-29 describes the parameters.
   

   In Table 3-28, M indicates mandatory and O indicates optional.

   Table 3-28 Parameter requirements in the template

   Parameter/Protocol	HWSDK(PlatformToDevice)	HWSDK(DeviceToPlatform)	ONVIF	T28181	HWSDK_Ext1	RTSP
   Device Name	M	M	M	M	M	M
   IP	M	O	M	O	M	M
   Port	M	M	M	M	M	M
   User Name	M	M	M	M	M	M
   Password	M	M	M	M	M	M
   Transport Protocol	O	O	M	O	O	O
   RTSP Port	O	O	O	O	O	M
   Device ID	O	M	O	M	O	O
   RTSP Primary Stream Resource Path	O	O	O	O	O	M
   RTSP Secondary Stream Resource Path	O	O	O	O	O	O
   Main Device Code	O	O	O	O	O	O

   Table 3-29 Parameters in the template

   Parameter	Description
   Device Name	Camera name displayed on the HWT-IVS1800. You are advised to set this parameter to the installation location or area of the camera.
   IP	IP address of a camera. You can enter a single IP address or a network segment.
   Port	Port number for camera access. The value must be the same as that set on the camera side. You are advised to use the default port number. If the port number is changed on the camera, set this parameter based on the site requirements.
   User Name	User name for registering a camera with the HWT-IVS1800. The default user name is admin.
   Password	Password for registering a camera with the HWT-IVS1800.
   Transport Protocol	Transmission protocol for connecting cameras to the HWT-IVS1800. The value must be the same as the transmission protocol configured for the HWT-IVS1800. HTTP: unencrypted transmission. HTTPS: encrypted transmission. You are advised to select HTTPS to ensure data security during transmission. HTTP/HTTPS: If the device supports the HTTPS transmission protocol (the device needs to respond to the HWT-IVS1800 within a specified period), HTTPS is preferentially used for connection.
   RTSP Port	To enable the RTSP stream obtaining function, you must set the same port (default port: 554) for the client and the frontend device.
   Device ID	Camera ID used to connect to the HWT-IVS1800. Enter a 20-digit decimal number. The value is padded with zeros if there are not enough digits. The ID of each camera must be unique. NOTE: The 20-digit decimal number you entered must be the same as the connection code configured on the HWT-IVS1800. Otherwise, the connection fails.
   RTSP Primary Stream Resource Path	URL of the RTSP primary stream.
   RTSP Secondary Stream Resource Path	URL of the RTSP secondary stream.
   Main Device Code	Device code of the camera. The code of each camera must be unique.

5. Import the template file, as shown in Figure 3-54.
   Figure 3-54 Camera information list
   
   1. Click Import. On the page that is displayed, click and import the template file that has been filled in from the local computer.
      

      The template file to be uploaded must be in CSV format, and the file size cannot exceed 10 MB.

   2. Click verification to verify the camera information in the template file.
      • If all camera information passes the verification, the list of cameras imported is displayed. Then, go to c.
      • If any camera information fails to pass the verification, the list of failed cameras is displayed. You can modify the template file according to the verification failure cause and import the template file again.
   3. Click Import to add cameras in batches.

Procedure (on the OMU Portal)

1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
2. Choose Maintenance Management > Camera Management.
3. Click Download Template to download the template file for importing cameras. If the template file has been filled in, go to 5.
4. Fill in the template file for importing cameras. For details about how to set parameters, see Table 3-30. Table 3-31 describes the parameters.
   

   In Table 3-28, M indicates mandatory and O indicates optional.

   Table 3-30 Parameter requirements in the template

   Parameter/Protocol	HWSDK(PlatformToDevice)	HWSDK(DeviceToPlatform)	ONVIF	T28181	HWSDK_Ext1	RTSP
   Device Name	M	M	M	M	M	M
   IP	M	O	M	O	M	M
   Port	M	M	M	M	M	M
   User Name	M	M	M	M	M	M
   Password	M	M	M	M	M	M
   Transport Protocol	O	O	M	O	O	O
   RTSP Port	O	O	O	O	O	M
   Device ID	O	M	O	M	O	O
   RTSP Primary Stream Resource Path	O	O	O	O	O	M
   RTSP Secondary Stream Resource Path	O	O	O	O	O	O
   Main Device Code	O	O	O	O	O	O

   Table 3-31 Parameters in the template

   Parameter	Description
   Device Name	Camera name displayed on the HWT-IVS1800. You are advised to set this parameter to the installation location or area of the camera.
   IP	IP address of a camera. You can enter a single IP address or a network segment.
   Port	Port number for camera access. The value must be the same as that set on the camera side. You are advised to use the default port number. If the port number is changed on the camera, set this parameter based on the site requirements.
   User Name	User name for registering a camera with the HWT-IVS1800. The default user name is admin.
   Password	Password for registering a camera with the HWT-IVS1800.
   Transport Protocol	Transmission protocol for connecting cameras to the HWT-IVS1800. The value must be the same as the transmission protocol configured for the HWT-IVS1800. HTTP: unencrypted transmission. HTTPS: encrypted transmission. You are advised to select HTTPS to ensure data security during transmission. HTTP/HTTPS: If the device supports the HTTPS transmission protocol (the device needs to respond to the HWT-IVS1800 within a specified period), HTTPS is preferentially used for connection.
   RTSP Port	To enable the RTSP stream obtaining function, you must set the same port (default port: 554) for the client and the frontend device.
   Device ID	Camera ID used to connect to the HWT-IVS1800. Enter a 20-digit decimal number. The value is padded with zeros if there are not enough digits. The ID of each camera must be unique. NOTE: The 20-digit decimal number you entered must be the same as the connection code configured on the HWT-IVS1800. Otherwise, the connection fails.
   RTSP Primary Stream Resource Path	URL of the RTSP primary stream.
   RTSP Secondary Stream Resource Path	URL of the RTSP secondary stream.
   Main Device Code	Device code of the camera. The code of each camera must be unique.

5. Import the template file, as shown in Figure 3-55.
   Figure 3-55 Importing the template file
   
   1. Click Import. The Import Camera dialog box is displayed.
   2. Click and select the camera template file stored from the local computer.
      

      The template file to be uploaded must be in CSV format, and the file size cannot exceed 10 MB.

   3. Click Check to verify the information of cameras to be imported. If any camera information already exists, the verification fails.
      • If all camera information passes the verification, the list of cameras to be imported is displayed. Then, go to 4.
      • If any camera information fails to pass the verification, the list of failed cameras is displayed. You can modify the template file according to the verification failure cause and import the template file again.
   4. Click Start Import.

Context

A dual-lens PTZ dome camera consists of a prime lens and a zoom lens. After the camera is connected, each lens occupies one channel.

Procedure

• Add a dual-lens PTZ dome camera on the LDU. For details about the connection modes, see HWSDK-based Access or Template-based Access.

Context

A compound-eye camera consists of a prime lens and one or two zoom lenses. After the camera is connected, each lens occupies one channel.

Procedure

• Add a compound-eye camera on the LDU. For details about the connection modes, see HWSDK-based Access or Template-based Access.

Prerequisites

NAT has been configured.

• If the camera is on an intranet and the HWT-IVS1800 is on an extranet, see Cameras on an Intranet and HWT-IVS1800 on an Extranet.
• If the camera and HWT-IVS1800 are on different intranets, see Cameras and HWT-IVS1800 on Different Intranets.

Procedure

• Add a 5G camera on the LDU. For details about the connection modes, see HWSDK-based Access or Template-based Access.

Context

The high-performance camera (primary camera) performs intelligent analysis on video from generic cameras (secondary cameras) and generates intelligent analysis results.

Prerequisites

The 1 + N cameras have been configured in the camera web system.

Procedure

Connect 1 + N cameras on the LDU. For details about the connection modes, see HWSDK-based Access or Template-based Access.

Model Restrictions

Only DH-TPC-BF5421, U1-4R(4)A-Th, U6-4R(40x)A-Th, and DHI-TPC-SD5441-T thermal cameras are supported.

Context

• A thermal camera consists of a common lens and an infrared lens. After the camera is connected, each lens occupies one channel.
• In the Dahua camera access scenario, cameras with the same IP address and port number cannot be added.
• Cameras connected through HWSDK_EXt1 do not support automatic camera type identification. You need to manually change the camera type.

Prerequisites

You have obtained the SDK files libdhnetsdk.so and libdhconfigsdk.so of the thermal camera.

You can click here to obtain them.

Procedure

1. Enable the temperature reporting and snapshot taking functions of the thermal camera.

   For details about how to enable the functions, see the camera documentation.

2. Load the SDK files.
   1. Log in to the operating system as the root user. ( How Do I Log In to the Operating System Through a Network Port?)
   2. Upload the SDK files libdhnetsdk.so and libdhconfigsdk.so to the /tmp directory.
   3. Move the SDK files to the specified directory.

      mv /tmp/libdhnetsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

      mv /tmp/libdhconfigsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

   4. Change the SDK file owner group and permissions.

      chown ivs_dcg:ivs /home/lib/ivs_dcg/third/lib/Dahua/arm/*

      chmod 440 /home/lib/ivs_dcg/third/lib/Dahua/arm/*

   5. Re-load the library path.

      ldconfig

   6. Restart the DCG process.

      sh /home/ivstool/bin/service.sh restart dcg

3. Enable the Basic authentication and the MD5 algorithm.
   1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
   2. Choose System > Network Security Configuration.
   3. Select Advanced.
   4. In the MD5 Algorithm area, select Enable MD5 when RTSP requests media streams from cameras.

      Using the MD5 algorithm may cause cyber security risks. Therefore, perform cyber security controls after enabling this algorithm.

   5. Enable Basic authentication.

4. Add a camera.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click Add Manually and select Add by IP Address. The page shown in Figure 3-56 is displayed.
      Figure 3-56 Add by IP Address
      
      Table 3-32 Parameter description

      Parameter	Description
      Protocol	Access protocol of the camera. Set this parameter to HWSDK_Ext1.
      IP Address	IP address of a camera.
      User Name	User name and password used to register a camera with the device.
      Password
      Management Port	Camera access port. The port configured on the HWT-IVS1800 must be the same as that on the device. You are advised to use the default port number. If the port number is changed on the camera, set this parameter based on the site requirements.
      Camera Name	Camera name displayed on the HWT-IVS1800. You are advised to enter the installation location or detection area.

5. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management.
   2. On the page that is displayed, choose Camera List.
   3. Click next to the camera for which you want to set the intelligent attribute.
   4. Set Intelligent Attribute to Target and Device Model to Fixed box camera, as shown in Figure 3-57.
      Figure 3-57 Setting basic parameters
      

Verification

1. Right-click on the desktop and choose Camera Management.
2. Check the camera connection status.
   Two video channels are displayed in the device list of the HWT-IVS1800, and the camera is connected successfully.

   • Common video channel: The channel name is Device access name.
   • Thermal video channel: The channel name is in Device access name0102 format.

Model Restrictions

Only the IPC6021-TH06-DU, U1-4R(4)A-Th, U6-4R(40x)A-Th, and DHI-TPC-SD5441-T thermal cameras are supported.

Context

• A thermal camera consists of a common lens and an infrared lens. After the camera is connected, each lens occupies one channel.
• In the Dahua camera access scenario, cameras with the same IP address and port number cannot be added.
• Cameras connected through HWSDK_EXt1 do not support automatic camera type identification. You need to manually change the camera type.

Prerequisites

• U6-4R(40x)A-Th, U1-4R(4)A-Th, IPC6021-TH06-DU, and DHI-TPC-SD5441-T cameras can be connected through HWSDK_EXt1. Before the connection, you have obtained the SDK files libdhnetsdk.so and libdhconfigsdk.so of the camera to connect. You can click here to obtain them.
• U1-4R(4)A-Th cameras can be connected through ONVIF.

HWSDK_EXt1-based Access

1. Enable the temperature reporting function of the thermal imaging camera.
   1. Log in to the thermal camera's web system.
   2. Choose Setting > Heat.
   3. Configure a temperature measurement rule, as shown in Figure 3-58.
      Figure 3-58 Configuring a fire warning rule
      
      

      On the Heat page, you need to set Snapshot to 1. Otherwise, alarms cannot be reported.

2. Load the SDK files.
   1. Log in to the operating system as the root user. ( How Do I Log In to the Operating System Through a Network Port?)
   2. Upload the SDK files libdhnetsdk.so and libdhconfigsdk.so to the /tmp directory.
   3. Move the SDK files to the specified directory.

      mv /tmp/libdhnetsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

      mv /tmp/libdhconfigsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

   4. Change the SDK file owner group and permissions.

      chown ivs_dcg:ivs /home/lib/ivs_dcg/third/lib/Dahua/arm/*

      chmod 440 /home/lib/ivs_dcg/third/lib/Dahua/arm/*

   5. Re-load the library path.

      ldconfig

   6. Restart the DCG process.

      sh /home/ivstool/bin/service.sh restart dcg

3. Enable the Basic authentication and the MD5 algorithm.
   1. Log in to the OMU portal as the admin user. ( Logging In to the OMU portal)
   2. Choose System > Network Security Configuration.
   3. Select Advanced.
   4. In the MD5 Algorithm area, select Enable MD5 when RTSP requests media streams from cameras.

      Using the MD5 algorithm may cause cyber security risks. Therefore, perform cyber security controls after enabling this algorithm.

   5. Enable Basic authentication.

4. Add a camera.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-59 is displayed.
      Figure 3-59 Add by IP Address
      

      Table 3-33 describes the key parameters.

      Table 3-33 Parameter description

      Parameter	Description
      Protocol	Access protocol of the camera. Set this parameter to HWSDK_EXt1.
      IP Address	IP address of a camera.
      User Name	User name and password used to register a camera with the device.
      Password
      Camera Name	Camera name displayed on the HWT-IVS1800. You are advised to enter the installation location or detection area.
      Management Port	Camera access port. The port configured on the HWT-IVS1800 must be the same as that on the device. You are advised to use the default port number. If the port number is changed on the camera, set this parameter based on the site requirements.

5. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management.
   2. On the page that is displayed, choose Camera List.
   3. Click next to the camera for which you want to set the intelligent attribute.
   4. Set Intelligent Attribute and Device Model based on the actual camera model, as shown in Figure 3-60.
      Figure 3-60 Setting basic parameters
      

ONVIF-based Access

TPC cameras can be connected through ONVIF. For details about the connection method, see ONVIF-based Access.

Verification

1. Right-click on the desktop and choose Camera Management.
2. Check the camera connection status.
   Two video channels are displayed in the device list of the HWT-IVS1800, and the camera is connected successfully.

   • Common video channel: The channel name is Device access name.
   • Thermal video channel: The channel name is in Device access name0102 format.

Model Restrictions

• Only IPC6091-P180-Z40, IPC6092-P360-Z40, and P4-4R(1.4)A panoramic cameras are supported.
• IPC6091-P180-Z40 and IPC6092-P360-Z40 do not support the home position.

Context

• P4-4R(1.4)A is a fisheye camera. IPC6091-P180-Z40 or IPC6092-P360-Z40 consists of one PTZ dome camera and one panoramic camera. After such devices are connected, each lens occupies a channel.
• In the Dahua camera access scenario, cameras with the same IP address and port number cannot be added.
• Cameras connected through HWSDK_EXt1 do not support automatic camera type identification. You need to manually change the camera type.

Prerequisites

• P4-4R(1.4)A, IPC6091-P180-Z40, and IPC6092-P360-Z40 cameras can be connected through HWSDK_EXt1. Before the connection, you have obtained the SDK files libdhnetsdk.so and libdhconfigsdk.so of the camera to connect. You can click here to obtain them.
• P4-4R(1.4)A, IPC6091-P180-Z40, and IPC6092-P360-Z40 cameras can be connected through ONVIF.

HWSDK_EXt1-based Access

1. Load the SDK files.
   1. Log in to the operating system as the root user. ( How Do I Log In to the Operating System Through a Network Port?)
   2. Upload the SDK files libdhnetsdk.so and libdhconfigsdk.so to the /tmp directory.
   3. Move the SDK files to the specified directory.

      mv /tmp/libdhnetsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

      mv /tmp/libdhconfigsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

   4. Change the SDK file owner group and permissions.

      chown ivs_dcg:ivs /home/lib/ivs_dcg/third/lib/Dahua/arm/*

      chmod 440 /home/lib/ivs_dcg/third/lib/Dahua/arm/*

   5. Re-load the library path.

      ldconfig

   6. Restart the DCG process.

      sh /home/ivstool/bin/service.sh restart dcg

2. Add a camera.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-61 is displayed.
      Figure 3-61 Add by IP Address
      

      Table 3-34 describes the key parameters.

      Table 3-34 Parameter description

      Parameter	Description
      Protocol	Access protocol of the camera. Set this parameter to HWSDK_EXt1.
      IP Address	IP address of a camera.
      User Name	User name and password used to register a camera with the device.
      Password
      Camera Name	Camera name displayed on the HWT-IVS1800. You are advised to enter the installation location or detection area.
      Management Port	Camera access port. The port configured on the HWT-IVS1800 must be the same as that on the device. You are advised to use the default port number. If the port number is changed on the camera, set this parameter based on the site requirements.

3. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management.
   2. On the page that is displayed, choose Camera List.
   3. Click next to the camera for which you want to set the intelligent attribute.
   4. Set Device Model to PTZ dome camera and Intelligent Attribute to Others, as shown in Figure 3-62.
      Figure 3-62 Setting basic parameters
      

ONVIF-based Access

• For details about the connection method, see ONVIF-based Access.

Verification

Right-click on the desktop and choose Camera Management.

• If the connected camera is of the IPC6091-P180-Z40 or IPC6092-P360-Z40 model, two video channels are displayed in the device list of the HWT-IVS1800, and the camera status is connected.

  Video channel of panoramic camera 1: The channel name is Device access name0102, and IPC is displayed in the lower left corner of the live video image.

  Video channel of the PTZ dome camera: The channel name is Device access name, and IP PTZ Dome is displayed in the lower left corner of the live video image.

  

  By default, a recording plan is configured for the video channel of panoramic camera 1. For details about how to configure recording plans for other channels, see Configuring the Recording Function.

Model Restrictions

Only high-rise dual-spectrum cameras of the FW-500-ET-C10 model are supported.

Context

An FW-500-ET-C10 camera consists of a visible-light optical lens and an infrared lens. After the camera is connected, each lens occupies a channel.

Procedure

Add a China Forestry Star camera on the LDU. For details about the connection method, see GB/T 28181-based Access.

Model Restrictions

• Only P5-4RV(4x)A PTZ dome cameras are supported.
• In the Dahua camera access scenario, cameras with the same IP address and port number cannot be added.
• Cameras connected through HWSDK_EXt1 do not support automatic camera type identification. You need to manually change the camera type.

Prerequisites

P5-4RV(4x)A cameras can be connected only through HWSDK_EXt1. You have obtained the SDK files libdhnetsdk.so and libdhconfigsdk.so of the camera to connect. You can click here to obtain them.

Procedure

1. Load the SDK files.
   1. Log in to the operating system as the root user. ( How Do I Log In to the Operating System Through a Network Port?)
   2. Upload the SDK files libdhnetsdk.so and libdhconfigsdk.so to the /tmp directory.
   3. Move the SDK files to the specified directory.

      mv /tmp/libdhnetsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

      mv /tmp/libdhconfigsdk.so /home/lib/ivs_dcg/third/lib/Dahua/arm/

   4. Change the SDK file owner group and permissions.

      chown ivs_dcg:ivs /home/lib/ivs_dcg/third/lib/Dahua/arm/*

      chmod 440 /home/lib/ivs_dcg/third/lib/Dahua/arm/*

   5. Re-load the library path.

      ldconfig

   6. Restart the DCG process.

      sh /home/ivstool/bin/service.sh restart dcg

2. Add a camera.
   1. Right-click on the desktop and choose Camera Management > Camera List.
   2. Click Add Manually and choose Add by IP Address. The page shown in Figure 3-63 is displayed.
      Figure 3-63 Add by IP Address
      

      Table 3-35 describes the key parameters.

      Table 3-35 Parameter description

      Parameter	Description
      Protocol	Access protocol of the camera. Set this parameter to HWSDK_EXt1.
      IP Address	IP address of a camera.
      User Name	User name and password used to register a camera with the device.
      Password
      Camera Name	Camera name displayed on the HWT-IVS1800. You are advised to enter the installation location or detection area.
      Management Port	Camera access port. The port configured on the HWT-IVS1800 must be the same as that on the device. You are advised to use the default port number. If the port number is changed on the camera, set this parameter based on the site requirements.

3. Set the type and intelligent attribute of cameras.
   1. Right-click on the desktop and choose Camera Management.
   2. On the page that is displayed, choose Camera List.
   3. Click next to the camera for which you want to set the intelligent attribute.
   4. Set Device Model to PTZ dome camera and Intelligent Attribute to Others, as shown in Figure 3-64.
      Figure 3-64 Setting basic parameters
      

Procedure

1. Right-click on the desktop and choose Live from the shortcut menu.
2. Drag a camera from the camera list to a live video pane, as shown in Figure 3-65.
   Figure 3-65 Viewing live video
   

• If the number of live video panes on the LDU is greater than or equal to 9, secondary streams are obtained by default. If the stream type of a camera is set only to primary stream, the camera cannot obtain secondary streams. As a result, live video fails to be enabled.
• You are advised not to play video from the same camera in different video panes at the same time.
• If live video cannot be viewed after you drag a camera to a live video pane, click to manually refresh the camera list and drag the camera to the live video pane again.

Related Operations

Table 3-38 describes the icons in the live video pane.

Restrictions

OSD cannot be configured for third-party cameras connected through GB/T 28181.

Procedure

1. Log in to the LDU as the admin user. ( Logging In to the LDU)
2. Click in the upper left corner to access the main menu.
3. Choose Camera Management > OSD Settings and select the camera to be configured.
4. Set the OSD1 parameters and date format, as shown in Figure 3-70. Table 3-43 describes the parameters.
   Figure 3-70 Setting OSD parameters
   

5. Click Apply to Camera Name to synchronize the configured OSD1 content to the names of multiple cameras in batches, as shown in Figure 3-71.
   Figure 3-71 Synchronizing the configured OSD content to the names of multiple cameras in batches