Copyright © 2013-2016 Kurento. Licensed under Apache 2.0 License.
This project is no longer maintained. Please use OpenVidu Project instead, as it is a programable platform aimed to create room-like applications. It has several demos and tutorials updated with last technologies (Angular, React, Ionic, WebComponents, etc).
Kurento Room is composed by several modules to offer group communications by means of WebRTC. These modules are:
kurento-room-sdk- module that provides a management interface for developers of multimedia conferences (rooms) applications in Java.
kurento-room-server- Kurento’s own implementation of server-side room management. It provides a WebSockets API for the communications between room clients and the server.
kurento-room-client- Java library that uses WebSockets and JSON-RPC to interact with the Room Server. Can be used to implement the client-side of a room application based on our server.
kurento-room-test- integration and functionality tests for the room server applications (demo & basic).
kurento-room-basicapp- lighter demonstration project.
There is extensive documentation on each of these components together with a tutorial based on the Room demo. These docs are generated from a separate Kurento project.
What is Kurento
Kurento is an open source software project providing a platform suitable for creating modular applications with advanced real-time communication capabilities. For knowing more about Kurento, please visit the Kurento project website: http://www.kurento.org.
Kurento is part of FIWARE. For further information on the relationship of FIWARE and Kurento check the Kurento FIWARE Catalog Entry
Kurento is part of the NUBOMEDIA research initiative.
The Kurento project provides detailed documentation including tutorials, installation and development guides. A simplified version of the documentation can be found on readthedocs.org. The Open API specification a.k.a. Kurento Protocol is also available on apiary.io.
Code for other Kurento projects can be found in the GitHub Kurento Group.
News and Website
Check the Kurento blog Follow us on Twitter @kurentoms.
Issues and bug reports should be posted to the GitHub Kurento bugtracker
Licensing and distribution
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
You can contribute to the Kurento community through bug-reports, bug-fixes, new code or new documentation. For contributing to the Kurento community, drop a post to the Kurento Public Mailing List providing full information about your contribution and its value. In your contributions, you must comply with the following guidelines
- You must specify the specific contents of your contribution either through a detailed bug description, through a pull-request or through a patch.
- You must specify the licensing restrictions of the code you contribute.
- For newly created code to be incorporated in the Kurento code-base, you must accept Kurento to own the code copyright, so that its open source nature is guaranteed.
- You must justify appropriately the need and value of your contribution. The Kurento project has no obligations in relation to accepting contributions from third parties.
- The Kurento project leaders have the right of asking for further explanations, tests or validations of any code contributed to the community before it being incorporated into the Kurento code-base. You must be ready to addressing all these kind of concerns before having your code approved.
The Kurento project provides community support through the Kurento Public Mailing List and through StackOverflow using the tags kurento and fiware-kurento.
Before asking for support, please read first the Kurento Netiquette Guidelines