Shulou(Shulou.com)06/01 Report--

This article introduces you to the RTSP video platform EasyNVR cloud terminal for CDN push failure example analysis, the content is very detailed, interested friends can refer to, I hope it can be helpful to you.

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 at the project site, you can choose to set up hardware devices under the network for transcoding and distribution of streaming video. Both functions are the same.

We have problems with using EasyNVR cloud terminals to push streams to third-party platforms. Take EasyDSS LVB push as an example, you can push streams normally with other push software, but not with EasyNVR cloud terminals.

EasyNVR cloud terminal cannot push streams normally.

First of all, EasyDSS rooms can push streams normally using other push devices, so we can rule out the problem of EasyDSS push space, so the problem is likely to occur on our EasyNVR cloud terminals.

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

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

It can be found that it is because the corresponding domain name cannot be properly ping, but the IP is accessed normally.

Therefore, the high probability is due to the DNS setting problem on this side of the device. 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 makes it more convenient for people to access the Internet.

EasyNVR's hardware box is prefabricated with a Ubuntu804 system, so we can set up DNS for the hardware box.

DNS setting method

1. View network-related configuration files / etc/systemd/resolved.conf

Contents of the file:

[Resolve]

DNS=1.1.1.1 1.0.0.1

# FallbackDNS=

# Domains=

LLMNR=no

# MulticastDNS=no

# DNSSEC=no

# Cache=yes

# DNSStubListener=yes

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

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

After doing the above, restart the EasyNVR cloud terminal to push the stream successfully.

Note: this article takes EasyDSS push platform as an example. If users have their own push platform, EasyNVR cloud terminals can also push streams into it. About EasyNVR Cloud Terminal

EasyNVR cloud terminal integrates software and hardware, cloud OPS, compact size, convenient placement and deployment, 7x24 non-stop operation, low power consumption, high cost of self-built video server, exclusive video service to avoid interaction with other hardware, successful operation and simple deployment.

This is the end of the example analysis of the reasons for the failure of CDN push on EasyNVR cloud terminals on RTSP video platform. I hope the above content can be of some help and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.