Session Creation — Ruby

You can use the OpenTok Ruby library to generate OpenTok sessions. Each session has a
unique session ID, which you can use in an OpenTok client library to connect to an OpenTok
session. (See "Joining a Session" for Web,
iOS, or
Android.)

Creating a session that uses the OpenTok Media Router

The following code creates a session that uses the OpenTok Media Router:

The OpenTok Media Router can decrease bandwidth usage in multiparty sessions. (In a
relayed session, each client must send a separate audio-video stream to each client
subscribing to it.)

The OpenTok Media Router can improve the quality of the user experience through
audio fallback and video recovery. With these
features, if a client's connectivity degrades to a degree that it does not support video
for a stream it's subscribing to, the video is dropped on that client (without affecting
other clients), and the client receives audio only. If the client's connectivity improves,
the video returns.

In a relayed session, clients will attempt to send streams directly between each other.
However, if clients cannot connect due to firewall restrictions, the session uses the OpenTok
TURN server to relay audio-video streams.

Important: Some features, such as archiving, are only available in
routed (not relayed) sessions. See the previous section for instructions on
creating a routed session.

Creating an automatically archived session

You can create a session that is automatically archived. Here is Ruby sample code that creates
an automatically archived session: