Cloud Streaming Services
- Release Notes and Announcements
- Announcements
- Product Introduction
- CSS Products
- Purchase Guide
- Basic Service Fee
- Value-Added Service Fee
- Live Video Broadcasting (LVB)
- Live Event Broadcasting (LEB)
- Live Video Caster
- General Cloud Director
- Console Guide
- Domain Management
- Adding Domain Names
- Push Domain Name Management
- Playback Domain Name Management
- HTTPS Configuration
- Feature Configuration
- Time Shifting
- Live Stream Moderation
- Live Subtitling
- Laboratory
- Monitoring
- Log Service
- Feature Guide
- Push and Playback
- WebRTC Protocol Push Stream
- Features
- Live Recording
- Live Streaming Security
- Global CSS Service
- Callback Notifications
- User Guides for Common Third-Party Tools
- SDK Guide
- 1. Stream Push
- API Documentation
- Making API Requests
- Monitoring Data Query APIs
- Billing Data Query APIs
- Live Transcoding APIs
- Delayed Playback Management APIs
- Domain Name Management APIs
- Watermark Management APIs
- Certificate Management APIs
- Live Stream Mix APIs
- Stream Pulling APIs
- Recording Management APIs
- Time Shifting APIs
- Live Callback APIs
- Screencapturing and Porn Detection APIs
- Authentication Management APIs
- Live Stream Management APIs
- Ops Guide
- Troubleshooting
- About Pushing
- Generating Push URLs
- PC Push
- Playing Method
- Web Player
- Web Player TcPlayer
- Web CSS Player 1.0
- Web VOD Player 1.0
- FAQs
DocumentationCloud Streaming ServicesFeature GuideCallback NotificationsPush Error Event Notifications
Push Error Event Notifications
Last updated: 2025-01-15 17:20:29
Push error callbacks notify you of the details of push errors. You need to configure a callback address in the CSS console, and CSS will send push error callbacks to the server you configured.
This document describes the fields in a callback notification sent by CSS after a push error occurs.
Must-Knows
This guide assumes that you understand how to configure callbacks and receive callback notifications from CSS. For details, see How to Receive Event Notification.
Push Error Callback Parameters
Event type
Event Type | Parameter Value |
Push errors | event_type = 321 |
Common callback parameters
Parameter | Type | Description |
appid | int | The user’s App ID. |
stream_id | string | The stream ID. |
data_time | int | The callback time (ms). |
report_interval | int | The reporting interval (ms) when a push error occurs. |
abnormal_event | json | The push error details. |
abnormal_event parameters
Parameter | Type | Description |
type | int | The error type. |
count | int | The number of times the error occurred between two reports (within the reporting interval). |
detail | json | desc: The error description. occur_time: The time when the error occurred. |
type_desc_cn | string | The error description in Chinese. |
type_desc_en | string | The error description in English. |
Error types
Type | Description |
1 | The video timestamp moved backwards. |
2 | The audio timestamp moved backwards. |
3 | The video timestamp increased notably (by more than 1000 milliseconds). |
4 | The audio timestamp increased notably (by more than 1000 milliseconds). |
5 | Chunk size too big (bigger than 8,192). |
6 | Two consecutive video frames arrived late (by more than 3000 milliseconds). |
7 | Two consecutive audio frames arrived late (by more than 1000 milliseconds). |
8 | The video codec changed. |
9 | The audio codec changed. |
10 | No codec header before a video frame arrived. |
11 | No codec header before an audio frame arrived. |
12 | The interval between audio frame timestamps is too long. |
13 | Audio/Video codec formats are uncommon. |
14 | The video header cannot be parsed. |
15 | The video frame rate is too low. |
16 | The GOP size is too large. Currently, if it exceeds 10s, it is considered too large. |
Note:
Currently, you cannot configure callbacks for a specific type of push error. A push error callback includes the information of all push errors that occurred during the reporting interval. If no push errors occur, no callbacks will be sent.
A push error callback only collects data for push errors in the current reporting cycle. The system will not handle the errors.
Sample callback
{"abnormal_event":[{"count":2,"detail":[{"desc":"video frame arrive interval too long, interval=3046(msec)","occur_time":1670588070569},{"desc":"video frame arrive interval too long, interval=2953(msec)","occur_time":1670588073522}],"type":6,"type_desc_cn":" ","type_desc_en":"video frame arrive interval bigger than 1000(ms)"},{"count":2,"detail":[{"desc":"audio frame arrive interval too long, interval=3009(msec)","occur_time":1670588070532},{"desc":"audio frame arrive interval too long, interval=2917(msec)","occur_time":1670588073486}],"type":7,"type_desc_cn":" ","type_desc_en":"audio frame arrive interval bigger than 1000(ms)"}],"appid":0,"data_time":1670588074971,"domain":"xxxx.xxxxx.xxxx.xxxx","event_type":321,"interface":"general_callback","path":"xxxx","report_interval":5000,"sequence":"000000000000000000","stream_id":"xxxxxx","stream_param":"txSecret=f5828cd4a8a09109304b060172fb3960&txTime=665982e4","timeout":5000}
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No