1. No image is forwarded in real time.
a) Whether the camera is a smart device
After a camera is connected to the platform and goes online, check whether the camera attribute is a smart camera. A common camera does not connect to the IMGU, and the camera pushes images to the platform. Therefore, no image is displayed for all services of the camera.
b) Check whether the camera is connected to the IMGU.
If all services are normal, search for InternalMediaPortForSDC in the IMGU configuration file /home/ivs_imgu/config/ivs_imgu.conf.
Run the Netstat command to check whether the port listening status and the IP address for establishing the connection have the corresponding camera.
If no connection is set up, check the camera status. If the camera status changes, search for the log "Device info set main device status." in normal cases, the value is 0->1->2->3->7.
Common errors are as follows:
(1) The NE in slot 1->0 goes offline or the ASON attribute is normal.
(2) The DCG fails to respond to the 0501 message sent in step 2 to step 1 or does not respond within a specified period. For details about the log, see +++HandleStartStreamRSP.
(3) If the device does not initiate a connection, check whether the IMGU port listening is abnormal. 2. Check whether the IP address changes due to NAT traversal (the IP address returned by the device is different from the actual IP address). 3. Check whether the device fails to identify the connection because the device returns a URL verification failure. If the preceding scenarios are excluded, transfer the fault to the SDC for fault locating.
2. No historical image is downloaded (including white image search on the C/S client).
a) Check whether the camera is on the MPR and has a storage device.
For the platform, the storage function can be enabled only on the MPU. If the storage function is disabled, the IMGU only forwards data. No image is related to the image download service. For example, the metadata subscription data contains no image, and the image ID returned by the IMGU is 0. If a camera has structured data but no image data, check this item first.
3. Some images are missing during real-time and historical forwarding.
You can use the eSDK Demo to pull real-time or historical forwarding and view the detailed data in the TLV or JSON sent by the camera. You can use the TLV parsing tool to view the TLV data. You can directly open the JSON data using a text editor to view the TLV data.
Check whether the corresponding image data exists in the TLV. The description of the corresponding image type is as follows:
PANORAMA_PIC = 0x0A00000A; // Scenario image, large image
FACE_PANORAMA = 0x0A000017 ; // Face scene image, large image
FACE_PIC = 0x0A000012; // Face cutout, small image
HUMAN_PIC = 0x0A000013; // Person cutout, small image
VEHICLE_PIC =0x0A000067 ; // Vehicle (cyclist) cutout, small image
PLATE_PIC = 0x0A000009; // License plate cutout, small image
For details about how to use the TLV parsing tool, see wiki: http://3ms.huawei.com/km/blogs/details/7608161.
In JSON data, SubImageList corresponds to an image array. Each image corresponds to a SubImageInfoObject object. Data indicates the Base64 code of the image data. If this field is left empty, no image data exists, and Type indicates the image type.
4. Fields in structured data forwarded by the IMGU are missing.
Refer to problem 3. The eSDK Demo usage wiki: http://3ms.huawei.com/km/blogs/details/6724297 is attached.
