...

1. The browser connects to the server via the Websocket WebSocket protocol and sends the publish command.
2. The browser captures the microphone and the camera and sends the WebRTC stream to the server.
3. The REST client sends the /push/startup query from the browser.
4. The WCS server publishes the RTMP stream on the RTMP server at the URL specified in the query.
5. The WCS server sends the RTMP stream.

...

To send the REST query to the WCS server, use a REST-client.

JavaScript API

Using WebSDK Web SDK you can republish a stream to an RTMP server upon creation, similar to the SIP as stream function. Usage example for this method is available in the WebRTC as RTMP web application.

...

If the server the stream is republished to has certain requirements to the name (Facebook, YoutubeYouTube), this line must be commented out.

...

In this case, RTMP will be republished to localhost only.

Parameters passing in server URL

...

In some cases, a stream publishing name shoukd should be passed in the server URL. To do this, the following option must be set in flashphoner.properties file

...

When RTMP stream is published to another RTMP server, connection to this server may be interrupted and channel may be closed for some reasons (destination server restart, network problems etc). In this case automatic reconnection and RTMP stream republishsing republishing can be enabled with the following parameter in flashphoner.properties file:

...

rtmp_transponder_send_metadata=true

2. Republishing may fail if RTMP destination server requires specific Flash version.

Symptoms: RTMP handshake fails, the channel is closed with RTMP error in server log.

Solution: specify RTMP subscriber Flash version, either using rtmp_flash_ver_subscriber setting in flashphoner.properties, or rtmpFlashVersion parameter in republishing REST request.

For example, for republishing to Periscope:

rtmp_flash_ver_subscriber = LNX 76.219.189.0

3. RTMP destination server may require specific stream parameters: bitrate, keyframe interval, or framerate.

Symptoms: e.g., Periscope displays warnings about not corresponding to the recommended settings.

Solution: set specific constraints to the source stream (e.g., for audio bitrate) and specify required parameters in republishing REST request (keyFrameInterval and fps).