P2P offline

Confirm if the P2P shows online

Enter SETTING>NETWORK > P2P and check the status

Testing the ability to log into devices via P2P on DMSS and SmartPSS

Device Shows Offline:

1. Reboot and upgrade to the latest version of the program (except customized programs).

If the device is still abnormal, please proceed to the next step.

2. Test for connection to the external network

On the local side click on MAINTAIN > NETWORK > TEST

Enter the Internet extranet address, test whether the network is connected, to ensure that the device can be connected to the Internet. If you cannot connect please follow step 3 to check DNS, if not please go to step 4 and follow the steps.

3. Check the DNS of the device

Preferred DNS is set to 8.8.8.8, or the network operator has restricted the DNS, replace it with the DNS provided by the operator, whether the network operator has restricted ports, P2P needs to open UDP ports, you can change to a different network operator to try.

If the DNS is correct but you still can't get through to the external network.

Please check your network.

4. Confirm that the device time is accurate

Confirm that the device time is accurate, and the deviation from UTC time is similar as the device time is consistent with the local time.

5. Make sure the port is open ( not in the device )

The on-site network has restrictions on the device ports, and the firewall needs to open the following ports.

UDP 0~65535(These ports are required for P2P connections to the server. UDP ports are used randomly, so all UDP ports need to be opened), TCP 9116、9118 、12367、12366、12337

Device Shows Online (but cannot be added to SmartPSS):

The problem may be caused by a domestic registered address or an error in the upgrade procedure, please follow the Device Shows Offline troubleshooting for details.

Device Shows Online (but cannot be added to DMSS):

1. Reboot and upgrade to the latest version of the program.

If the device is still abnormal, please proceed to the next step.

2. If the sub stream is not on, try switching to the main stream in the app stream settings to see the preview effect.

3. Change the device password in account mode, the shared account will fail to pull the stream

4. RTSP over TLS is enabled on the device side resulting in a failed pull

Check the path of the device as follows,

Setting > Security > A/V Encryption > RTSP over TLS

(In account mode, pulling streams like this is not supported at the moment. This feature will be supported after DMSS V1.99.400)

5. Upgrade DMSS to the latest version (after V1.99.200) and test the local network environment as shown below.

Type ping (Public Network Address) –l 1500 –f

If it shows Packet needs to be fragmented but DF set, so it indicates that the data packet is too large and needs to be reduced. Then reduce the packet data and test it again until it shows Reply from.

If it is confirmed that the MTU value of the network environment where the device is located is less than 1500, you need to manually modify the MTU value of the device to adapt to the network environment to avoid failure in sending streams.

(The optimal MTU value is the test number plus 28, for example, 1472+28=1500, so we set the MTU value to 1500 on the DMSS)

Modify the path as follows,

Device Details > Remote Configuration > Modify MTU

6. If the device still shows online, but cannot be added to Smartpss or DMSS, then you need to provide the SN for L2 to check the device backend.

Ps: If all of the above tips cannot solve the problem, please collect the printing info and capture package, and then send it to our R&D for analysis.