Javascript Menu by WebRTC Conference 2012
Carrier Cloud Day Two
Carrier Cloud Day Two Carrier Cloud Day One SDN Workshop Hotel Novotel
Wolfgang Beck, Deutsche Telekom

Wolfgang Beck | Deutsche Telekom

With the participation of:

Download the brochure in pdf

Co-located with

  09.00 Privacy, Security and Regulatory Considerations for RTCWeb
During a transition to WebRTC it will be necessary to address privacy and security challenges and these in turn will raise questions of responsibility and regulation.
Discussing possible security mechanisms and services that can fulfill the requirements for real-time communications on the web and providing some suggestions for further study or implementation trials, based in part on the IIT RTC Lab Voice and Video over Web (VVoW) project.

Authors: Carol Davids, IIT, Wilhelm Wimmreuter, InCharge Systems and
Henry Sinnreich

Wilhelm Wimmreuter | InCharge Systems
  09.30 NAT Traversal and WebRTC’s Real-Time Transmission
Presenting how the WebRTC support the transmission of real-time data. Describing the transmission protocols, explaining how the NAT traversal works, giving an introduction to the support of security such as SRTP, describing the negotiation process and showing performance results.

Authors: Christian Hoene, Michael Haun and Patrick Schreiner, Symonics GmbH Frank Hermann, University of Tübingen
    WebRTC in a mobile context  
  10.00 Extending 4G Communications with WebRTC
Surveying the issues around the support of WebRTC linkages to 4G/LTE communications services and assuming the audience is familiar with WebRTC APIs and design principles and is looking to learn more about the 4G/LTE architecture as a platform for communication services. 

Anne Y. Lee | CTO | Advanced Communications Solutions Innovations |
Bell Labs Fellow
  10.30 WebRTC in Smartphones - Opportunities and Challenges
Introduction of WebRTC capabilities to smartphones opens up great opportunities for new applications and services, but to get there, a number of technical challenges need to be overcome (hardware, connectivity, web application capabilities, WebRTC protocol stack implementation, codecs, power consumption, interface switching, usability).

Markus Isomäki | Nokia
  11.00 COFFEE BREAK  
  OTT versus Carrier VoIP

This panel discusses the scalability, regulatory and security challenges to be faced if all communications processing is done in the endpoint and if the processing performed in the network is reduced to transport and directory services to locate the far end peer. 


Carol Davids | Illinois Institut of Technology
James Body | Truphone
Wolfgang Beck | Deutsche Telekom

Wilhem Wimmreuter | InCharge Systems
Dr. Daniel C. Burnett | Voxeo
  12.30 LUNCH  
    Web APIS  
  14.00 Feedbacks from a Web App Developer
Talking about how to develop a Web App with the JavaScript API. Sharing experience on developing a jQuery plugin. Explaining process and methods, and how to keep up to date regarding the WebRTC project. Showing a demo.

Luc Tribolet | PhD
  14.30 SIP, Javascript and Websockets Use in webRTC
How will WebRTC and SIP-based solutions work together?
Describing a SIP network extension solution, the challenges that need to be solved and the work that Orange and NEXCOM Systems have done together to implement it. Providing insights on the implementation of a SIP stack in JavaScript, as well as the integration of the WebSocket transport protocol in a SIP proxy.

Authors: Didier Neveux, Project Manager, Jean-Pierre Lesgo, Laurent Strullu, France Telecom | Orange Labs and Jean Deruelle, Mobicents

Laurent Strullu | WebRTC Expert | France Telecom | Orange Labs
    15.00 IETF Opus - Official Characterization Results. Does Opus Outperform other Recently Developed Codecs?
Preliminary acoustic listening-only tests show that the Opus codec  performs well when compared to other codecs. Presenting the latest results of the performance of Opus. The test results for Opus are compared to the results of other codecs.

Authors: Christian Hoene, Michael Haun and Patrick Schreiner, Symonics GmbH Frank Hermann, University of Tübingen
Wolfgang Beck, Deutsche Telekom Which Codec for WebRTC?
There is an ongoing debate as to which codecs should WebRTC mandate: VP8 or H.264, G.7xx series or Opus.
Where does this debate come from? What lies behind the different sides in this debate, and why we all should strive for a simple solution?

Tsahi Levent-Levi | Amdocs
    16.00 Tightly Coupled Congestion Control in WebRTC
WebRTC's standard congestion control is currently being defined. One requirement is that it should be possible for users to prioritize different parts of WebRTC transport. This calls for tightly coupling the congestion control of WebRTC streams. Overviewing the design, highlighting the benefits and the many positive side-effects of such tight coupling.

Michael Welzl | University of oslo
    16.30 Bringing WebRTC Video into Corporate Environment
Solutions for remote workforce are vendor specific, cover single modality and don't interoperate in multi-media environment. DEmonstrating how to bring WebRTC video into corporate environment and integrate with existing corporate assets for video communications.

Alex Vishnev | Thrupoint
bistri logos bistri drum bistri bistri
  © 1994-2012 Upperside Conferences. Credit Photos: Ilana Bak | Upperside Conferences. Fotolia. All rights reserved.