Publishing RTMP in an Autoscale Environment
With Red5 Pro autoscaling in place, WebRTC, via a browser, can be proxied directly through the Stream Manager through web socket connections. Since Flash was deprecated from browsers, there are a few more steps required to publish a stream from an RTMP source.
- Make the broadcast API call
- Use the origin IP returned from that call as the target for your RMTP broadcaster.
If you want to use Red5 Pro to transcode that stream, then the process is more complicated. See this doc for the full process. The high-level steps are:
- 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 to publish the high-level stream name from your provision.
If you are publishing from an RTMP encoder that can deliver multiple stream levels, and prefer to use those instead of the Red5 Pro transcoder, then:
- Submit a stream provision request; the ABR level names need to match your encoder's stream names.
- Make a broadcast API call using the GUID of the stream provisioned.
- Publish all streams to the origin IP address returned in the above call.
Publishing a single RTMP stream to an autoscale cluster: