All firmware version;
【2】Description of the problem
EVS or NVR configures the front end, prompting that the request has timed out or the configuration is not valid.
【3】Problem Processing (Root Cause)
This kind of problem is generally caused by the timeout when the NVR/EVS side receives the result returned from the front end. There are two cases of timeout, one is the network is not good, and the other is the camera response timeout. Except for timeout, other situations require packet capture confirmation.
There are generally two reasons for this situation:
The network is not good, causing the front-end response or returning configuration timeout;
The performance of the front-end is fully loaded, and it cannot respond to the commands sent by the NVR/EVS to the front-end in time, resulting in a timeout for returning the configuration. (You can log in to the background of the front end to see if its CPU is high to judge whether it is overloaded)
In both cases, you can confirm by capturing packets. Capture packets on both the NVR/EVS side and the front-end at the same time. From the captured packets, determine whether 1. Whether the NVR/EVS side initiates a configuration request command; How long did it take to respond to this command after receiving the configuration request; 3. How long did it take to return from the front end to the NVR/EVS end.
Through the above investigation method, it is basically possible to determine where the problem is.
NVR/EVS has successfully obtained the front-end configuration, but the configuration still fails: configure the device for the front-end device
First use the front-end web to perform the same configuration on it. If it fails, contact a front-end colleague to check.
If the front-end web configuration is normal, you need to provide NVR/EVS printing and packet capture information.
By capturing packets to confirm whether the command interaction is normal, to determine which section the problem is, and printing to confirm where the problem may be.