Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
Domain Name Service
VPC Endpoint
Cloud Connect
Enterprise Switch
Security & Compliance
Web Application Firewall
Host Security Service
Data Encryption Workshop
Database Security Service
Advanced Anti-DDoS
Data Security Center
Container Guard Service
Situation Awareness
Managed Threat Detection
Cloud Certificate Manager
Anti-DDoS Service
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GaussDB(for MySQL)
Distributed Database Middleware
GaussDB(for openGauss)
Developer Services
Distributed Cache Service
Simple Message Notification
Application Performance Management
Application Operations Management
API Gateway
Cloud Performance Test Service
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Cloud Communications
Message & SMS
Cloud Ecosystem
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP License Service
Support Plans
Customer Operation Capabilities
Partner Support Plans
Professional Services
Intelligent EdgeFabric
SDK Developer Guide
API Request Signing Guide
Koo Command Line Interface
Help Center> Live> User Guide> Stream Pushing Configuration> Configuring Stream Status Notifications
Updated at: Mar 31, 2022 GMT+08:00

Configuring Stream Status Notifications

You can add a URL on the Live console for receiving messages when stream pushing starts or ends. The messages are sent as POST requests to your server through an HTTP API. Then your server returns the status code 200 to confirm that the messages have been received.


In the AP-Bangkok region, submit a service ticket for review after configuring stream status notifications. The configuration takes effect only after it is approved.

After stream status notifications are enabled, you will receive a message each time when a live stream is pushed or disconnected. However, when a stream is disconnected soon after it was pushed, the server may receive the message on stream disconnection before receiving the message on stream pushing due to network transmission latency. In this case, you need to check the Unix timestamp parameter publish_timestamp in the message to check whether the stream pushing and stream disconnection are in the same stream pushing event. The timestamps generated in the stream pushing and stream disconnection of the same stream pushing event are the same.


  • Domain names have been added.
  • CNMAE records have been added to your domains' DNS records.

Adding a Notification URL

  1. Log in to the Live console.
  2. In the navigation pane, choose Domains.
  3. Click Manage in the row containing the target ingest domain name.
  4. In the navigation pane, choose Template > Stream Status Notifications.
  5. Click Add. On the displayed dialog box, add a notification URL, as shown in Figure 1.

    Only HTTP and HTTPS URLs are supported.

    Figure 1 Adding a notification URL
    Authentication Key: authentication key. You need to configure this parameter only when notification authentication is required.
    • A key contains 32 to 128 characters.
    • A key can also be automatically generated.

  6. Click OK.

    When stream pushing starts or ends, you will receive a notification message. For details about the notification message body, see Callback Example.

Managing Notification URLs

You can also perform the following operations:

  • Editing a notification URL

    Click Edit in the Operation column to edit the URL or authentication key for receiving stream pushing messages.

    Figure 2 Editing a notification URL
  • Deleting a notification URL

    Click Delete in the Operation column to delete the URL or authentication key for receiving stream pushing messages.

    Figure 3 Deleting a notification URL

Callback Example

The following is an example of stream pushing and stream disconnection messages. Table 1 describes the fields in a message body.

Table 1 Message body




Ingest domain name


Application name


Stream name


Stream pushing parameter


IP address of the streaming device


IP address of the receiver


Unix timestamp. One single timestamp is generated for each stream pushing event.


Stream pushing or stream disconnection.

Possible values are:

  • PUBLISH: Stream pushing starts.
  • PUBLISH_DONE: Stream pushing ends.


UNIX timestamp when the event notification signature expires. This parameter is carried when an authentication key is configured.

The value is a decimal UNIX timestamp, that is, the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT).

Example: 1592639100 (June 20, 2020 15:45)


Event notification signature. This parameter is carried when an authentication key is configured.

auth_sign = HmacSHA256 (event + domain + app + stream + auth_timestamp, key)

key indicates the key used for authentication.

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel