edit-icon download-icon

Callbackformat

Last Updated: Apr 11, 2018

Example of the file generation event callback

It means that the targeted recording file is generated.

  1. {
  2. "domain": "qt01.alivecdn.com",
  3. "app": "mp4flvtest_flv",
  4. "stream": "callback_test",
  5. "uri": "mp4flvtest_flv/callback_test/0_2017-03-08-23:09:46_2017-03-08-23:10:40.flv",
  6. "duration": 69.403,
  7. "start_time": 1488985786,
  8. "stop_time": 1488985840
  9. }

Specifically, the domain, app, and stream are the domain name for recording, application name and stream name respectively. The uri is the route of the targeted recording file under the user’s recording OSS Bucket. The duration, start_time and stop_time represent the duration as well as start time and end time of the target recording file.

Example of recording status callback, generated when NeedStatusNotify=true

  1. Callback of the recording initiating event, which means that the recording begins successfully.

    1. {
    2. "domain": "gs_domain",
    3. "app": "gs_app",
    4. "stream": "gs_stream",
    5. "event": "record_started"
    6. }

    Specifically, the domain, app and stream are the domain name for recording, the application name and stream name respectively. The event is the event name and it can be record_started/record_paused/record_resumed.

  2. Callback of recording pause event, which means that the recording is paused successfully.

    1. {
    2. "domain": "gs_domain",
    3. "app": "gs_app",
    4. "stream": "gs_stream",
    5. "event": "record_paused"
    6. }
  3. Callback of recording resumption event, which means that the recording is resumed successfully.

    1. {
    2. "domain": "gs_domain",
    3. "app": "gs_app",
    4. "stream": "gs_stream",
    5. "event": "record_resumed"
    6. }
Thank you! We've received your feedback.