Posts

WebRTC 2015 Conference Agenda Updates

Some exciting news around the WebRTC Conference & Expo Paris 2015 Agenda

As we are getting closer to the event the agenda continues to evolve adding more sessions and speakers.

Latest agenda updates include:

WebRTC on mobile devices

Experts will examine mobile WebRTC issues from concept to delivered applications and what steps and decisions need to be made along the way.

Running WebRTC is indeed still a challenge with several options to solving it.

A panel has been added during the Training session.

Chaired by Amir Zmora, our Technology Committee Chairman, it will review what the alternatives developers have for enabling WebRTC services on mobile devices.

Moreover, in the main conference, Scott Graham, from IBM, will discuss what frameworks to use, native vs. hybrid, how to handle security and other critical aspects for mobile WebRTC to become a reality.

IDC Forecasts WebRTC benefits for SPs and enterprises

Another great news for our December Agenda is the addition of IDC, a leading market intelligence firm in the WebRTC area, delivering its expertise on benefits for Service Providers and Enterprises.

Mark Winther, Group VP and Consulting Partner, will apply recent IDC survey data, comparing WebRTC benefits for SPs and Enterprise:

Which business operations benefits? What WebRTC features are most important and what are the barriers to Enterprise adoption?

Closing Panel on status and predictions for 2016

Finally, the Conference will end with the closing panel on WebRTC Current Status and Predictions for 2016.

During the conference the audience will be presented with an on-line survey covering WebRTC industry and technology questions.

In the panel the results of this survey will be presented and discussed by a set of experts.

Read more

Bouygues Telecom WebRTC Prototypes, An interview with Patrice Crutel

Patrice CrutelPatrice Crutel is Senior Arcitect for Core and Service Network Layer at Bouygues telecom. He is deeply involved in WebRTC work at Bouygues and is also a regular contributor to our WebRTC yearly conference. I asked Patrice to give us details of current work taking place at Bouygues with regards to WebRTC.

Who are the industry partners they are working with?

How are they tackling the WebRTC for mobile challenge?

What are the obstacles to deployments they are dealing with?

How far along are you with your WebRTC projects and who are your partners?

Over the past few months, we have launched several in-house prototypes. They are being used by employees at Bouygues Telecom. Quobis and Ericsson helped us in designing these prototypes in our own lab. We are continuing to meet with various players in the webRTC domain (webRTC GW suppliers and also Unified Communication solution providers) as well as in web application development. We are making progress within the company on testing and enriching via applications revolving around webRTC.

Do you have any projects for mobile terminals?

Clearly it is a positive step to deploy WebRTC on all devices, main interest we see is to be able to access our services on tablet-type devises basically because they have greater capacity than mobile phones, mainly due to the larger screen. A mobile terminal is still “handicapped” by its small size and the battery.

As iPhone do not support ViLTE, webRTC could be seen as an alternative to offer video “natively”.

What do you see as the business case for WebRTC? For instance, do you intend to open your future platforms to other clients?

For the time being, we are not considering opening our platforms. Firstly we are concentrating on WebRTC’s contribution to the services proposed by an operator to its clients. The OTT (Over-The-Top) content providers are not out to make a profit on this type of service. But will operators be able to do so? They need to have differentiation, one of which is better QoS/QoE but there needs to be more than that. Therefore, we will look into how to make certain value-added services associated with WebRTC profitable.

What is the largest obstacle for the deployment of WebRTC?

What discourages us the most are the regular changes made by Google on its browser, which can lead to a loss of service for our subscribers. For an operator, this is inacceptable. There are also problems with the battery life of mobile devices. WebRTC applications are extremely energy-greedy. This aspect needs to be improved and we are following such developments closely.

Read more

Things We Talked About at WebRTC 2014

Many things were discussed last week at the WebRTC Conference & Expo. One thing I noticed when doing show of hands was a beginning of expansion of the audience from telecom only to other areas. To my surprise, a non-neglectable number of hands were raised when I asked to know who are not coming from telecom oriented companies but rather from Web companies.

Topics discussed covered a range of areas from general WebRTC standard and technology to Telecom and enterprise specific ones.

TAKE THE CONFERENCE FEEDBACK SURVEY NOW!

I included some of these topics in the audience survey and closing panel. The presentation with the survey results can be fond below. I would like to discuss 2 out of these topics.

 

The panel moderated by myself included: Chad Hart (WebRTC Hacks & Dialogic), Douglas Tait (Oracle), Gilles Duboué (Alcatel-Lucent), Chris Koehncke (&yet), Sebastian Schumann (Slovak Telekom)

Are there still WebRTC roadblocks?

It was interesting to see the audience response compared to the opinion of the panel.

The question was designed to be controversial by intention as I put several of the issues discussed during the conference in one option. The audience played along and almost 80% voted for this option.

The panel on the other hand didn’t fall for this and followed the line of, there will always be issues, this can’t be a reason to hold back. In this case, I agree with the panel. There are always issues; ORTC was one of the topics brought up by many people as a concern. This and the video codec came up in several discussions I had with customers. Having said that, these concerns will be solved as issues will arise, they can’t be an excuse why not to use the technology.

Are there any roadblocks for WebRTC to be ubiquitous

Is WebRTC ready for mobile?

WebRTC for mobile is still a concern of many people. There are several options how to tackle this, options differ based on specific needs and device OS. This is why I decided to give a presentation about this at the conference (details of it will be published on Tuesday on my blog TheNewDialTone).

Most of the audience replied to this question either saying iOS is still an issue or that an SDK is the right option to take.

How do you view the readiness of WebRTC for Android and iOS

I believe it is less important what is the “correct” answer but rather to understand the general perception people have on WebRTC for mobile.

WebRTC support on mobile devices is a topic that needs to be solved in a better way during 2015.

More about the conference can be found in my summary.

Looking forward to hearing your feedback about the conference and what are your expectations for next year.

TAKE THE CONFERENCE FEEDBACK SURVEY NOW!

Read more

WebRTC Survey – Results Are Here

Many views are expressed about WebRTC; What is the killer app? What is it that stops its proliferation? Which should be the mandatory video codec?…

Lately, TheNewDialTone together with Upperside, we came out with a survey to learn more about the WebRTC market status. Now is the time to share the results.

I’ll start off with an apology, the survey was closed last week and this post was going live, then we discovered that someone has played with the results by inserting a large amount of responses in a way that made it clear that these are not authentic responses. Unfortunately Survey Monkey doesn’t have any basic security means like Captcha or identification of strange response behaviors. Maybe it was that Amazon Gift Card that was tempting this person or maybe just a strong desire to play with the survey results. Anyway, all fake results had to be manually removed, something that took a bit of time.

The complete and detailed results can be found in this presentation. In this post I would like to take a closer look at a few of them.

Making it easy to add voice & video communication to applications

If you dumb down WebRTC to the very basic thing that it brings, that is a great media engine. Anyone who had to go through the experience of building a voice & video client or service knows all the headaches it takes, and it is a never-ending story as you need to improve quality continuously. The first question of the survey was looking at what companies have used before WebRTC was available.

WebRTC Survey Results Q1

There were different approaches used to build voice and video communications into an application, self development was less common as it required to license some components, develop others and integrate them into one nicely working client. Hard work.

Putting aside the move to the Web and no download, compiling WebRTC into your application is a savior.

Where will WebRTC have the most significant impact?

The interesting thing is not so much what people voted for but rather what they didn’t vote for and that is service provider. I believe that the webification of communications will impact service providers in 2 ways:

  • It will move communication previously handled by the service provider to other places
  • Those that will jump on the WebRTC wagon will be able to create services and platforms that will enable them to build new asymmetric business models.

WebRTC Survey Results Q3

Microsoft & WebRTC

The survey came out just after Microsoft announced their plans to support WebRTC (ORTC, H.264) so it was interesting to hear people’s thought about this and the video codec.

Since then, Skype for Web was announced and things moved on in the IEFT toward a decision (or a decision not to decide to compromise).

People were really worried about the fragmentation in video codec and preferred both to be supported. Should they still be worried? That really depends on how this decision will be implemented in browsers and mobile devices. My guess, we haven’t seen the end of it yet.

WebRTC Survey Results Q4

WebRTC Survey Results Q5

There are more interesting results so make sure to take a look at this presentation with the complete information.

I do want to touch 2 more questions that will be reviewed by Tsahi and myself in December during the WebRTC conference in Paris.

WebRTC API Platforms

We had a Webinar about this topic and Tsahi will be moderating a panel about the topic during the conference.

The response to the question – In what cases would you choose to use a WebRTC API platform? – was not a big surprise. I was hoping to have more votes for the third option, specific services in the cloud. Now, after Twilio announcing their network traversal service it will be interesting to hear what people have to say about this option on the panel.

WebRTC Survey Results Q7

WebRTC for mobile

In the response to the question about the readiness of WebRTC for mobile devices there was a strong consensus that there is still some way to go until it will be easy to tackle this one, mainly for iOS. During the conference we will review the complexities and give examples of how companies have solved the mobile challenge.

WebRTC Survey Results Q8

For more information about these and other questions take a look at the detailed results presentation.

Last but not least. An email will be sent by Upperside to the 2 winners of the Amazon Gift Card.

Your thoughts about the survey results will be happily received at the comments section below.

Read more