The background,

In the security monitoring industry, GB28181 protocol can achieve the acquisition of live streaming, video, alarm information, channel status and other information, basically meet all the needs of the monitoring industry. LiveGBS is an open GB28181 streaming media service platform. It provides private deployment of users, standard RESTFul HTTP interface for secondary development, and converts video streams into RTMP, RTSP, HTTP-FLV, and HLS formats to support playing on WEB and mobile terminals without plug-ins. In addition, it also supports capturing snapshots, cloud video, cascading, alarm information, rights management and other details. It is a very excellent GB28181 streaming media service platform.

Ii. Common problems of LiveGBS

1. The page cannot be opened

When both LiveCMS and LiveSMS are deployed, the browser does not open the LiveCMS page by typing IP: port 10000. This is usually the case when port 10000 of LiveCMS is occupied by another program. You can uninstall LiveCMS, open the LiveCMS. Ini file, change the HTTP port from 10000 to 100002 or some other port, and then reinstall LiveCMS.

2. The device cannot be registered

After the web page is opened, the device cannot be registered, and you need to check whether UDP port 5060 is enabled.

3. Change the service IP address

When changing the service IP address, you need to change the IP address in LiveCMS and LiveSMS configuration pages at the same time. Do not change only LiveCMS. Otherwise, the device may be online but cannot play.

4. Play splintered screen and stenton

When a video is played, screen splintering or lag occurs, usually because the network fails to catch up when the video is transferred from the device to the server. You can lower the video bit rate on the configuration page of the device. Generally, it is recommended that the bit rate be set to 256-1024 KBPS for public network broadcasting. If the bit rate is too high, the upstream bandwidth of the device may not keep up.

5. “SMS not found”

Check whether the LiveSMS service is running properly

6. “invite sms wait response error”

The possible problem is the configured public IP address, but native LiveCMS cannot access its own LiveSMS directly from this public IP address. Ini file. Change the host in [SIP] to 127.0.0.1, set wan_IP to the previous public IP address, and use_wan_IP_recv_stream =1. Reinstall LiveSMS.

7. “Ack SMS wait response error”

LiveSMS could not receive the inferior push flow. First, it needed to check whether the TCP 30,000-40000 UDP 50,000-60000 port on the server side was open. Second, check whether livesms.ini > [SIP] > host is configured as an IP address accessible to lower-level users

8. Start the output RTSP stream

Edit livesms.ini > [RTSP] below LiveSMS zip

[rtsp]
port=554
Copy the code

Warning Starting port 554 under Linux usually requires root permission, and you need to run the livesms service as sudo

Pull a live stream and view the stream information through the interface/API /v1/stream/list, which contains the RTSP stream address of this live stream, as shown in the figure

This RTSP address can be played with ffplay

9. Enable the HTTPS service

Tip prompts LiveCMS and LiveSMS to enable HTTPS services at the same time

  • Configure LiveCMS to enable HTTPS

    Livecms. Ini > [HTTPS] > Configure the certificate path and THE CMS HTTPS port

  • LiveSMS enable HTTPS

    Livesms.ini > [HTTPS] > Configure the certificate path and SMS HTTPS port, if CMS and SMS are deployed on the same machine, change the port to a different one

    Livesms. ini > [SIP] > wan_ip is configured to the domain name corresponding to the certificate

After the configuration is complete, restart LiveCMS and LiveSMS. Access https:// Certificate domain name :CMS HTTPS port to verify whether HTTPS is enabled successfully

10. WEB player

Player download: www.liveqing.com/docs/downlo…

Details: www.liveqing.com/docs/manual…

11. Play authentication

When connecting to your service system for authentication, the configuration file location is LiveCMS > LiveCMS. Ini > [SIP] > Stream_auth_URL

Enter the authentication address provided by your service system

Fill in the sample: stream_auth_url = http://yourhost:port/playauth

Process description:

  • The user requested a play address

    Example: http://localhost:10001/flv/hls/t.flv? param1=111&param2=222

    Param1 and param2 are additional parameters with any name

  • The LiveGBS system will GET a callback to the stream_AUTH_URL address above and pass through the additional parameters

    Example: http://yourhost:port/playauth? param1=111&param2=222

    Waiting for the return of your authentication interface:

    • Success: 200 (Status Code)
    • Failure: 401

    The authentication result returned by LiveGBS judgment:

    • Success: Start playing
    • Failed: Block playback