Fedora Talk Facilitator Cases

This page is intended to be a comprehensive list of all the things a Facilitator might want to do with FedoraTalk. A separate page holds things a regular User or Adminstrator might need to do. These use cases are developed as part of the FAD Fedora Talk 2009 game plan.

• If it is works today, there should be a link to a page explaining how to do it
• If it doesn't exist to day, there should be a link to an Ticket with a keyword of ftalk.

Host A Conference

A Fedora community member would like to host a conference where three or more people can participate in the same call.

1. Obtain a conference code and conferencing priveldges
   1. How/Where?
2. Start conference
   1. How/Where?

LINK: FIXME

Host A Recorded Conference

A Fedora community member would like to host a conference where three or more people can participate in the same call and have that call recorded for personal playback and download.

1. Obtain a conference code and conferencing priveldges
   1. How/Where?
2. Start conference
   1. How/Where?
3. Start recording of the conference
4. Stop recording of conference
5. Retrieve recorded conference

LINKS:

• https://fedorahosted.org/fedora-infrastructure/ticket/395
• Documentation--FIXME

Host a Private Conference

Important
This option should be somewhat restricted in usage. The Fedora Project promotes openness and transparency, so use of this capability should be minimized and possible constrained to a few users such as the FPL and/or Infrastructure lead.

A group of people would like to have a conference which requires a level of privacy--the access code is not public knowledge.

1. Go to ____ ?
2. Do _____ ?

LINKS:

• https://fedorahosted.org/fedora-infrastructure/ticket/1160
• Documentation--FIXME

Remote talk at Events

Delivering remote talks at conferences and events removing the need for travel where possible. susmit 17:37, 14 October 2009 (UTC)

1. May require special dial-in room that supports video over SIP
2. Web app allows setup of limited-time account for conference/event dial-in (using at queued jobs perhaps)
   • First job sets up account at startup time
   • Second job removes account at end time
3. User dials in at appointed time using normal account
4. Conference/event on-site dials in using limited-time account

LINK: FIXME

Open Questions

1. In cases of public conferences, can/should we further restrict codec use to promote the lowest possible bandwidth per caller? Or is this a dynamic feature that the Asterisk server and clients manage automatically as call numbers grow? --pfrields 11:21, 16 October 2009 (UTC)
   • My (Bruno) memory is that it is better for everyone in a conference to be using the same codecs. But one of the real Asterisk guys might understand this better.
   • Some of the better/best codecs are patented and we may not be able to use them.
2. Add yours today :-)