WebRTC Archives - Page 11 of 13

WebRTC Changes Your IT Org Chart

March 23, 2015 / in Markets & People / Add Comment

Before VoIP came along, enterprises had network people and telephony people. These were different groups, nothing to do one with the other. Deploying VoIP forced […]

What to look for at Enterprise Connect 2015

March 15, 2015 / in Markets & People / Add Comment

I will soon arrive at Orlando for Enterprise Connect. What should we expect from this event?
The conference tracks are a good indication for what to expect and more importantly a good reflection of market trends.

WebRTC Standards Update #2

March 4, 2015 / in WebRTC Standards / 4 Comments

This is the second WebRTC Standards Update coming to you from Dan Burnett and Amir Zmora.
Topics covered in this update are: Is there a security vulnerability in WebRTC with regards to detecting your IP address? The New Public Working Drafts of Media Capture and WebRTC. Enhancing media functionality of WebRTC

Being Specific About Your WebRTC Signaling Choices

March 3, 2015 / in VoIP / 1 Comment

In WebRTC things are different. WebRTC doesn’t define any signaling protocol or transport for signaling; this is left for the application. This gives more flexibility but also more things to decide on and therefore debate about.
Case study A – I’m building my new awesome service
Case study B – I’m connecting my telephony network with WebRTC

WebRTC Usage Numbers are Hard to Quantify

February 23, 2015 / in Markets & People / 1 Comment

A similar but more complex question arises for WebRTC. WebRTC is a lower level technology than WordPress. WordPress is more of a complete solution than WebRTC. WebRTC has a more permissive license (BSD for both the Google and Ericsson implementations) and there are good reasons to reuse sub-components of it for different purposes.

AT&T Takes Your Identity to the Web

February 16, 2015 / in VoIP / Add Comment

WebRTC API platforms are not new around here. From a high level perspective, most of these API platforms seem to be more of the same. Having said that, some have an unfair advantage. AT&T could have taken the me too approach but they didn’t. They took a different and interesting stab at WebRTC and made use of their unfair advantage, their users and their AT&T identity.