SRT and Zixi Restreaming with Red5 Pro Autoscaling
At the time of this document (June 2023), there is no direct restreamer API call via the stream manager. Because of that, you need to run the restreamer calls against the origin (or transcoder) that you will be publishing to.
Configuration Requirements
The restreamer plugin will need to be activated on the node (origin or transcoder) image per the API doc. Since this can add some overhead to the server, it is recommended to create a separate image, for your relay and edge nodes, that does not include the activated restreamer.
If you are using SRT, then make sure to open the TCP port range for your calls to the cloud node security group.
Publishing an SRT or Zixi stream to an Autoscale Environment
The steps for publishing SRT to an autoscale cluster are as follows:
- Make the broadcast API call.
- Using the origin IP address returned from that call, make the SRT stream create or Zixi stream createAPI call.
- Start the SRT or Zixi publisher.
Restreaming an IP Camera to an Autoscale Environment
The steps for broadcasting an IP camera stream to an autoscale environment are as follows:
- Make the broadcast API call.
- Using the origin IP address returned from that call, make the IP camera create API call.
Transcoding from Restreamers
If you wish to use Red5 Pro transcoding with your restreamer, then you’ll need to follow a similar process to the RTMP transcoding flow.
- Submit a stream provision request for the ABR levels (GUID of the stream plus the stream levels)
- Using the GUID, make the broadcast – transcode API call
- Use the transcoder IP returned from that call for the restreamer API calls, and the high-level stream variant name as your incoming stream name (e.g.
stream_1
).