Publish and Subscribe Examples
Publishing and Subscribing Via Wavelength Zones
Because the Stream Manager can’t communicate to the Wavelength nodes via their Carrier IP addresses, it is necessary to proxy websocket/ssl calls via private IP. From the https://<streammanager>/webrtcexamples/
settings page, scroll down to the STREAM MANAGER SPECIFIC section, and place a check next to Use Private Proxy.
To request a server in the wavelength zone, you will need to include the wavelength zone in your broadcast request. For example: https://<streammanager>/streammanager/api/4.0/event/live/test123?action=broadcast®ion=us-west-2&zone=us-west-2-wl1-lax-wlz-1
Similarly, if you want to force connection to a non-wavelength zone instance you’ll need to specify the zone where your nodes were launched. For example: https://<streammanager>/streammanager/api/4.0/event/live/test123?action=broadcast®ion=us-west-2&zone=us-west-2a
To use this with the webrtcexamples, include the region and zone in the Region field, such as us-west-2&zone=us-west-2-wl1-lax-wlz-1
If you do not set a zone for your connection then the stream manager will round-robin publish/subscribe requests between available origin/edge nodes for the first connection attempts only. After there are connected clients, then the stream manager will target the least-used node for new connections.
Red5 Pro HTML5 SDK Examples:
Note: the streaming-html5
examples testbed is included with the Red5 Pro server distribution, and can be accessed via your stream manager at https://your.server.url/webrtcexamples/
.
Red5 Pro iOS SDK Examples:
Red5 Pro Android SDK Examples: