Skip to end of metadata
Go to start of metadata
Description

The Web-Start application let you select a area of your screen that will be published.
In case you do screensharing it will be transfered as rtmp-stream to the Red5 server using SHA1 codec and then redirected to all users.
In Case you do recording the stream will be additionally stored on the server, also all audio/video signals from every user in the conference will be stored on the server. A post processor will then extract the audio from each stream and merge it with the screen data to a single recording file that contains everything and that you can watch in the section with the recordings of Openmeetings include meta infos.
You can download the recording as AVI/FLV and there is also a SOAP/REST service to load or single sign on just to watch a recording in the OpenMeetings included recording player.

Use-Cases for testing
  • The whole test makes zero sense if you do not produce sound while you are recording. You can for example count numbers and show the numbers in the camera to verify after recording if the audio/video is in sync.
  • verify of recording means to look if the audio and video is in sync at the beginning, in the middle and at the end of the recording.
  • each test has (if not specified different) a minimum duration of 20-30 seconds for the recording part

use case

Description

1 single user

  • user has no audio/video turned on
  • start recording
  • stop recording
  • verify (see top)

2 two users

  • two users in a room, both already audio/video turend on
  • start recording
  • stop recording
  • verify (see top)

3 user enters

  • single user in room
  • starts recording
  • second user comes in room start sharing a/v
  • stop recording
  • verify (see top)

4a user browser close and re-enters

  • single user in room
  • starts recording
  • second user comes in room start sharing a/v
  • second user shut down browser
  • second user re-enters the room and starts a/v
  • stop recording
  • verify (see top)

4b user leaves and re-enters

  • single user in room with a/v on
  • starts recording
  • second user comes in room start sharing a/v
  • second user clicks on "exit rooms" and leaves the room
  • second user re-enters the room and starts a/v
  • stop recording
  • verify (see top)

5 re-publish stream

  • two users in a room, both already audio/video turend on
  • start recording
  • one of the users clicks on device settings and chooses different settings (maybe another micro) and re-publishes
  • wait couple of seconds
  • the same user clicks on his device settings and chooses the previous settings again
  • stop recording
  • verify (see top)

6 long term test

  • one or two users in a room, both already audio/video turend on
  • start recording
  • wait for 45 minutes or more, then produce some sound, wait unother 45 minutes, maybe you turn your micro off
  • stop recording
  • verify (see top)

7a screenshare while recording

  • two users in a room, both already audio/video turend on
  • turn screensharing on one user client
  • watch screensharing on other user client
  • start recording
  • stop recording
  • verify (see top)

7b screenshare while recording

  • two users in a room, both already audio/video turend on
  • start recording
  • turn screensharing on one user client
  • watch screensharing on other user client
  • stop recording
  • verify (see top)

8 RTMPT Screensharing

  • change config.xml rtmpport to point to nonsense port
  • two users in a room, both already audio/video turend on
  • start recording
  • turn screensharing on one user client
  • watch screensharing on other user client
  • stop recording
  • verify (see top)

TODO: RTMPS Screensharing

Flow
Gliffy Zoom Zoom
Labels
  • No labels