SHARE



ABOUT THE AUTHOR


Andrew Prokop
Andrew Prokop has been heavily involved in the world of communications since the early 1980s. He holds five United States...
Read Full Bio >>
SHARE



Andrew Prokop | October 27, 2014 |

 
   

Avaya Makes WebRTC as Simple as Point and Click

Avaya Makes WebRTC as Simple as Point and Click The Avaya WebRTC Snap-in offering is an end-to-end solution that turns WebRTC into a scalable, secure, and practical tool to Web-enable your communications. Or said in a different way, it turns hype into reality.

The Avaya WebRTC Snap-in offering is an end-to-end solution that turns WebRTC into a scalable, secure, and practical tool to Web-enable your communications. Or said in a different way, it turns hype into reality.

I've been in this industry long enough to be wary of hype and irrational exuberance. How many of you are old enough to remember analog mobile phones or when ATM meant asynchronous transfer mode and not the ubiquitous cash-dispensing machine? I am, and I remember how they were slated to revolutionize communications. Well, they didn't.

The same can be said for video. Although I still hold out hope for a much broader penetration, it has yet to become as important as dial tone. Clearly, seemingly good ideas don't always translate into user acceptance and marketplace success.

WebRTC is one of those technologies that will either be wildly successful or take its place in the "nice attempts" graveyard. Personally, I would love for it to achieve the former, but a number of factors are working against it.

Here are the WebRTC challenges as I see them:

  1. The WebRTC standard has yet to be solidified.
  2. Neither Apple nor Microsoft has embraced WebRTC.
  3. The WebRTC operating environment isn't fully defined. For example, there's no standard way to implement signaling.
  4. WebRTC applications are difficult to write.
  5. Different Web browsers support WebRTC functionality in their own ways.
Those are a lot of negatives for something that is supposed to replace communications as we know it today. While the first two items are out of the hands of any one particular organization, the remaining three offer up plenty of opportunities for a clever company.

Enter Avaya and its WebRTC Snap-in. Actually, it would be more accurate to say, "Enter Avaya and its impressive solution for enabling a simplified, easy to use, and more feature-rich approach to WebRTC – which happens to be built around its WebRTC Snap-in."

I need to make it clear that Avaya hasn't redefined WebRTC. If you're familiar with WebRTC, you've probably heard about such things as STUN and TURN servers. You may have even heard of JavaScript Session Establishment Protocol (JSEP). The Avaya approach uses everything that the WebRTC specification says you're supposed to use. The trick is that the Avaya solution hides all the gory details from the application designer. Avaya is 100% compliant with WebRTC, and has taken complete responsibility for all the hard parts.

Before I go too much further, allow me to define a few general terms:

  • WebRTC Client - This is a WebRTC-compliant Web browser such as Chrome, Firefox, or Opera.

  • WebRTC Application - This is a Web page that exposes communications functionality like call-me or click-to-call. A WebRTC application is written in HTML and a programming language called JavaScript. The application's JavaScript uses the embedded WebRTC functionality supplied by HTML5 to make voice, video, and data calls.

  • Web Server - A WebRTC application is stored on a Web server and is downloaded to a client when the user navigates to the appropriate URL.

  • WebRTC Signaling Server - A signaling server is used to allow one WebRTC client to communicate with another WebRTC client. The server relays information between clients (IP addresses, ports, codecs, commands, etc). The WebRTC specification states that such a server must exist, but it does not define what that server is or provide guidelines as to how it should be written.

  • WebRTC Wrapper API - This is a collection of JavaScript objects that surround the standard WebRTC objects and abstracts them into a much simpler form. This item is not part of standard WebRTC.
In essence, the Avaya solution is a collection of libraries and services that implement the functionality of the signaling server as well as the wrapper API. It's completely standard WebRTC, while filling in the many gaps in the WebRTC specification.

Putting a Wrapper on Complexity
When I first wanted to understand how WebRTC worked, I did what any good geek would do: I wrote my own application. Granted, it wasn't incredibly sophisticated, but I could make a video call from one Web browser to another, and that was good enough for me.

Besides having a communications application to demonstrate to my friends and coworkers, I walked away from that experience with something even more valuable than bragging rights. I learned just how complicated it is to write a WebRTC application -- I had to pay too much attention to too many different things, and all the while I kept saying to myself, "There has to be an easier way to do this."

The Avaya wrapper API is the answer to my wish. It takes the somewhat convoluted processes of establishing a signaling connection, working with private IP addresses, and calling from one client to another, and turns them into a few simple lines of JavaScript. At the same time, it deals with all the idiosyncrasies that come from the fact that Chrome doesn't implement WebRTC in the same way that Firefox does. The Avaya wrapper allows me to write my application once and run it unchanged on any WebRTC-compliant browser.

Signaling
When I wrote my application, I built a bare-bones signaling server from open source that I found on the Internet. It did what I wanted it to do, but it wasn't scalable or secure, and it was limited to browser-to-browser communication. While that's fine for a demonstration, the real power in WebRTC lies in calling from a Web browser to an actual telephone. That's how you would implement WebRTC in a contact center, and my simple application was worthless in that realm.

The next big thing that comes from Avaya is the signaling server that it calls the WebRTC Snap-in. This Snap-in is a service that runs on an Avaya Collaboration Environment server. It allows a WebRTC application to call an Avaya endpoint or use the Avaya system to call out to the PSTN.

In addition to being a signaling server, the Snap-in acts like a gateway that converts HTTP from the WebRTC application into SIP. This essentially makes the Snap-in look like a SIP trunk to an Avaya Session Manager, and ultimately, a Communication Manager. This enables a Web browser to call an Avaya endpoint, or in some cases, invoke the services of an outbound trunk. This is where the power and money in WebRTC lies.

Security
The WebRTC specification defines aspects of security in terms of signaling and media, but no authentication mechanism has been provided. By this, I mean that there are no processes to validate who or what a WebRTC application can call.

Avaya rectifies this problem with something it calls a security token. The Web server generates this token in conjunction with the WebRTC Snap-in and uses it to limit what a WebRTC user can do. For example, the token might allow calls to contact center agents, but prohibit trunk calls to outside numbers. Without such a mechanism, an enterprise would open itself up to toll fraud and denial-of-service attacks.

Caller-Attached Data
The Avaya solution fills yet another hole in the WebRTC specification. It uses the Avaya Context Store Snap-in to attach caller data to the WebRTC call. With the Context Store Snap-in, a contact center agent can know who is calling and from what particular page the caller invoked WebRTC. This allows the agent to know the difference between a general information call and one about a specific product – e.g., men's bootcut jeans.

Mischief Managed
I've spared you the architectural details of the Avaya approach, but unless you're tasked with installing the servers and connecting them to one another, those details aren't necessary. The point of this article is to introduce you to the moving parts as seen by the application developer and the end user.

If you walk away with anything from my missive, I want it to be these two thoughts: First, the Avaya WebRTC solution greatly simplifies the process of developing and rolling out a WebRTC application. Instead of dwelling on SDP and WebSocket, the developer stays focused on the business logic of the application.

Second, the Avaya solution creates a business-ready platform by addressing many of the gaps and shortcomings in WebRTC. Using the WebRTC Snap-in, wrapper API, and Context Store Snap-in, developers can create practical applications that deliver quantifiable results today.

If you're serious about WebRTC, you need to be serious about your platform. The Avaya offering is an end-to-end solution that turns WebRTC into a scalable, secure, and practical tool to Web-enable your communications. Or said in a different way, it turns hype into reality.

Andrew Prokop writes about all things unified communications on his popular blog, SIP Adventures.





COMMENTS



Enterprise Connect Orlando 2018
March 12-15 | Orlando, FL

Connect with the Entire Enterprise Communications & Collaboration Ecosystem


Stay Up-to-Date: Hear industry visionaries in Keynotes and General Sessions delivering the latest insight on UC, mobility, collaboration and cloud

Grow Your Network: Connect with the largest gathering of enterprise IT and business leaders and influencers

Learn From Industry Leaders: Attend a full range of Conference Sessions, Free Programs and Special Events

Evaluate All Your Options: Engage with 190+ of the leading equipment, software and service providers

Have Fun! Mingle with sponsors, exhibitors, attendees, guest speakers and industry players during evening receptions

Register now with code NOJITTEREB to save $200 Off Advance Rates or get a FREE Expo Pass!

October 18, 2017

Microsofts recent Ignite event had some critically important announcements for enterprise communications. Namely, Microsofts new Team Collaboration offering, Teams, will be its primary communicatio

September 20, 2017

Customer experience can make or break your business. But how do you achieve outstanding customer service when you're dealing with outdated organizational structure, lagging technology, dated proces

August 16, 2017

Contact centers have long been at the leading edge of innovation in communications technology, given their promise of measurable ROI and the continual need to optimize customer interactions and sta

September 22, 2017
In this podcast, we explore the future of work with Robert Brown, AVP of the Cognizant Center for the Future of Work, who helps us answer the question, "What do we do when machines do everything?"
September 8, 2017
Greg Collins, a technology analyst and strategist with Exact Ventures, delivers a status report on 5G implementation plans and tells enterprises why they shouldn't wait to move ahead on potential use ....
August 25, 2017
Find out what business considerations are driving the SIP trunking market today, and learn a bit about how satisfied enterprises are with their providers. We talk with John Malone, president of The Ea....
August 16, 2017
World Vision U.S. is finding lots of goodness in RingCentral's cloud communications service, but as Randy Boyd, infrastructure architect at the global humanitarian nonprofit, tells us, he and his team....
August 11, 2017
Alicia Gee, director of unified communications at Sutter Physician Services, oversees the technical team supporting a 1,000-agent contact center running on Genesys PureConnect. She catches us up on th....
August 4, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, has lately been working on integrating enterprise communications into Internet of Things ecosystems. He shares examples and off....
July 27, 2017
Industry watcher Elka Popova, a Frost & Sullivan program director, shares her perspective on this acquisition, discussing Mitel's market positioning, why the move makes sense, and more.
July 14, 2017
Lantre Barr, founder and CEO of Blacc Spot Media, urges any enterprise that's been on the fence about integrating real-time communications into business workflows to jump off and get started. Tune and....
June 28, 2017
Communications expert Tsahi Levent-Levi, author of the popular BlogGeek.me blog, keeps a running tally and comprehensive overview of communications platform-as-a-service offerings in his "Choosing a W....
June 9, 2017
If you think telecom expense management applies to nothing more than business phone lines, think again. Hyoun Park, founder and principal investigator with technology advisory Amalgam Insights, tells ....
June 2, 2017
Enterprises strategizing on mobility today, including for internal collaboration, don't have the luxury of learning as they go. Tony Rizzo, enterprise mobility specialist with Blue Hill Research, expl....
May 24, 2017
Mark Winther, head of IDC's global telecom consulting practice, gives us his take on how CPaaS providers evolve beyond the basic building blocks and address maturing enterprise needs.
May 18, 2017
Diane Myers, senior research director at IHS Markit, walks us through her 2017 UC-as-a-service report... and shares what might be to come in 2018.
April 28, 2017
Change isn't easy, but it is necessary. Tune in for advice and perspective from Zeus Kerravala, co-author of a "Digital Transformation for Dummies" special edition.
April 20, 2017
Robin Gareiss, president of Nemertes Research, shares insight gleaned from the firm's 12th annual UCC Total Cost of Operations study.
March 23, 2017
Tim Banting, of Current Analysis, gives us a peek into what the next three years will bring in advance of his Enterprise Connect session exploring the question: Will there be a new model for enterpris....
March 15, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, discusses the evolving role of the all-important session border controller.
March 9, 2017
Organizer Alan Quayle gives us the lowdown on programmable communications and all you need to know about participating in this pre-Enterprise Connect hackathon.
March 3, 2017
From protecting against new vulnerabilities to keeping security assessments up to date, security consultant Mark Collier shares tips on how best to protect your UC systems.
February 24, 2017
UC analyst Blair Pleasant sorts through the myriad cloud architectural models underlying UCaaS and CCaaS offerings, and explains why knowing the differences matter.
February 17, 2017
From the most basics of basics to the hidden gotchas, UC consultant Melissa Swartz helps demystify the complex world of SIP trunking.
February 7, 2017
UC&C consultant Kevin Kieller, a partner at enableUC, shares pointers for making the right architectural choices for your Skype for Business deployment.
February 1, 2017
Elka Popova, a Frost & Sullivan program director, shares a status report on the UCaaS market today and offers her perspective on what large enterprises need before committing to UC in the cloud.
January 26, 2017
Andrew Davis, co-founder of Wainhouse Research and chair of the Video track at Enterprise Connect 2017, sorts through the myriad cloud video service options and shares how to tell if your choice is en....
January 23, 2017
Sheila McGee-Smith, Contact Center/Customer Experience track chair for Enterprise Connect 2017, tells us what we need to know about the role cloud software is playing in contact centers today.