[Terminal equipment] Analysis of the reason for the failure of CDN streaming on the EasyNVR hardware version of the RTSP protocol video platform

Many people may know that EasyNVR is a software version of the video platform, but in fact, EasyNVR also has a hardware version-EasyNVR cloud terminal. When it is not convenient to deploy software on the project site, you can choose hardware equipment to set up under the network to transcode streaming video Distribution, the functions of both are the same.

EasyNVR Cloud Terminal.png

We use EasyNVR cloud terminal to push the stream to a third-party platform and there is a problem. Take the live push of EasyDSS as an example, the stream can be pushed normally with other push software, and the stream cannot be pushed normally with the EasyNVR cloud terminal.

EasyNVR cloud terminal cannot push stream normally

First of all, EasyDSS live streaming room can use other push streaming equipment to push the stream normally, so we can eliminate the problem of EasyDSS push space, so the problem is likely to appear on our EasyNVR cloud terminal.

The EasyNVR device is actually online and can also be played normally, so there is no problem with the device access; the CDN address in the channel live broadcast is also correct, so you can know that it should not be an EasyNVR network problem.

376.png

377.png

Enter the EasyNVR system running interface and find that the device cannot ping the demo website domain name.

379.png

It can be found that the corresponding domain name cannot be pinged normally, but the IP is normally accessed.

380.png

Therefore, the high probability is due to the DNS settings on the device side. DNS (Domain Name System) is a service of the Internet. As a distributed database that maps domain names and IP addresses to each other, it can make it easier for people to access the Internet.

The hardware box of EasyNVR is prefabricated with Ubuntu804 system, so we can set DNS for the hardware box.

DNS setting method

1. Check the
content of the network-related configuration file /etc/systemd/resolved.conf :
[Resolve]
DNS=1.1.1.1 1.0.0.1
#FallbackDNS=
#Domains=
LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
#DNSStubListener=yes

2. If we want the configuration in the /etc/resolve.conf file to take effect, we need to add the DNS configuration items in the systemd-resolved configuration file (as in the example above, the modification has been completed), and then restart the systemd-resolved service OK.

Another simpler way is to stop the systemd-resolved service directly and modify /etc/resolve.conf to take effect.

After pressing the above operations, restart the EasyNVR cloud terminal, and the stream can be successfully pushed.

381.png

Note: This article takes the EasyDSS streaming platform as an example. If the user has his own streaming platform, the EasyNVR cloud terminal can also push streaming.

About EasyNVR Cloud Terminal

956eed4.png

EasyNVR cloud terminal software and hardware integration, cloud operation and maintenance; small size, easy to place and deploy; 7x24 hours of uninterrupted operation, low power consumption; saves the high cost of self-built video server; exclusive video service, eliminating the interaction with other hardware Impact; it can run successfully after powering on and connecting to the Internet, and the deployment operation is simple. For more information about video platform solutions, please visit TSINGSEE Qingxi Video for details.

Guess you like

Origin blog.csdn.net/EasyNVR/article/details/108603514