Push to Talk: Difference between revisions

From OLPC
Jump to navigation Jump to search
(form)
Line 33: Line 33:
See also http://www.cozybit.com/projects/pa_ptt/ for one that depends on a software layer not yet available on the OS builds.
See also http://www.cozybit.com/projects/pa_ptt/ for one that depends on a software layer not yet available on the OS builds.


===RPMs===
===RPMs===somos de calle


===Resources===
===Resources===

Revision as of 16:41, 15 August 2008

OlpcProject.png Quozl

see more templates or propose new

Description & Goals

Summary

The concept is to create a voice over IP "Push To Talk" radio. This way anyone on the mesh can push a button, and everyone else running the activity can hear them.

Goals

Multicast reception, multiple channels. Easy to use.

Collaboration

Visual Design

Media

Screenshots

Development

Source

There is a proof of concept available in this darcs code repository: http://quozl.linux.org.au/darcs/olpc-radio-testing

See also http://www.cozybit.com/projects/pa_ptt/ for one that depends on a software layer not yet available on the OS builds.

===RPMs===somos de calle

Resources

Links

Activity Summary

Icon: Sugar icon::
Genre: Activity genre::Other
Activity group: ,|x|Activity group::x}}
Short description: Short description::The concept is to create a voice over IP "Push To Talk" radio. This way anyone on the mesh can push a button, and everyone else running the activity can hear them.
Description:
Maintainers: ,|x|Contact person::x}}
Repository URL: Source code::http://quozl.linux.org.au/darcs/olpc-radio-testing
Available languages: ,|x|Available languages::x}}
Available languages (codes): ,|x|Language code::x}}
Pootle URL:
Related projects: Related projects,|x|Related projects::x}}
Contributors: ,|x|Team member::x}}
URL from which to download the latest .xo bundle Activity bundle::
Last tested version number:
The releases with which this version of the activity has been tested. ,|x|Software release::x}}
Development status:
Ready for testing (development has progressed to the point where testers should try it out): ,|x|Ready for testing::x}}
smoke tested :
test plan available :
test plan executed :
developer response to testing :