making your enterprise ready for webrtc - tmcnet · 2014-06-19 · video conferencing system...
TRANSCRIPT
Making Your Enterprise Ready for WebRTC
Amir Zmora
Independent Consultant/AudioCodes
Speakers
• Karl Stahl
– Ingate Systems, CEO/CTO
• Shubh Agarwal
– OpenClove, VP Marketing
Using WebRTC Cloud Services, AND Taking Enterprise UC to New Heights
Karl Stahl, CEO/CTO
Ingate Systems [email protected]
Merged Intertex Data AB and Ingate Systems AB
Ingate’s SBCs do more than POTS-like SIP. They were developed for standards-compliant end-to-end multimedia SIP quality connectivity everywhere. Ingate’s WebRTC support is aligned: Q-TURN brings telepresence quality and the WebRTC & SIP PBX Companion brings all the WebRTC features to the enterprise Unified Communications Solution.
WebRTC: Finally High-Quality Multimedia Real-Time Communication Available Everywhere You Can Surf…
6/19/2014 5
Or isn’t that easy?
• A Giant Step: From POTS to Telepresence
• NAT/firewalls are always an obstacle for real-time communication
• New ways of communicating:
• Browsers send media directly between one another
• Click on the Web to connect – No numbers
• Web/Cloud services by themselves and/or Integrating with Enterprise UC or Carrier SIP/IMS
Pre- AM Radio 3.5 kHz voice 20 kHz audio and 3.5 Mbps video
We Have IP-PBX / UC Solution RTC in the Enterprise – But Use SBCs For:
MPLS
• SIP Trunking – Connecting to telephony
• Remote users
• Federating UC with others
SIP System
Data & VoIP LAN
SIParator®
WebRTC doesn’t use SIP and should work everywhere:
• HD Multimedia Telepresence
• No Numbers!?
• Passing links?
• Browsers as Softclients!
Pass a WebRTC link over IM or an email, asking people to click-to-call you or something. http://companion.smartcomp.com/[email protected]
LAN
CompanyWeb Server
SIP
Does WebRTC Traverse the Enterprise Firewall?
• WebRTC may work through the enterprise firewall using ICE/STUN/TURN, but it does not traverse the most restrictive firewalls.
• What about Quality: prioritization, traffic-shaping in the firewall? The firewall is often the congestion point!
• A local turn server paralleling the existing firewall (or inside it) is a secure solution for both traversal and quality.
• A standard for discovering/using network-provided (enterprise or ISP) TURN servers is in progress.
LAN
CompanyWeb Server
TURN SERVER
media
LAN
CompanyWeb Server
media
Q-TURN
Q-TURN - A Novel View on ICE
Knock knock: Give my media a Quality Pipe
• Regard ICE as a request for real-time traffic through the access router/firewall. Interpret the STUN & TURN signals in the firewall.
• With the STUN/TURN server functionality IN the access router/firewall, it sets up the media flows under control.
• Security is back in the right place - The firewall is in charge of what is traversing.
• Firewalls in parallel can still be restrictive.
A TURN server in a firewall can:
• Securely allow WebRTC on the LAN
• Prioritize and traffic-shape for QoS
• Route media to a quality IP pipe
• Diffserv or RVSP QoS over the net
TURN/STUN required for WebRTC (like SBCs for SIP)
Nice - But We Want Calls Into the Contact Center?
Where did our Auto Attendant, Queues, Forwards, Transfers, Conference Bridges, PBX Phones go?!
Is there “a Gateway” into the enterprise PBX / UC-solution?
LAN
CompanyWeb Server media
HD/Video/Telepresence,
from passed links and
click-to-call buttons etc.
Ask your PBX/UC call center vendor!
Internet
WebRTC by itself
bypasses the
enterprise SIP UC
infrastructure.
LAN SIP
media
InternetCompany
Web Server
The WebRTC Browser as a Softphone – So Much Better!
Having the PBX/UC softphone available everywhere, on every device with a browser, without any plug-in and not just for plain voice phone calls, but potentially also for HiFi HD telepresence quality, is of course a dream.
This is the most obvious WebRTC application for the enterprise PBX or UC Solution.
It will especially ease remote PBX users because WebRTC includes a NAT/firewall traversal method (ICE/STUN/TURN) in itself.
A WebRTC-SIP Gateway is required
And the PBX-Integrated WebRTC Browser Can Be a Video Conferencing System
Telepresence video conferencing- Not in a separate room, but
directly in every PBX browser client!
- Invite to a conference by passing links
- Or simply add parties to any call anytime
- For everyone. Everywhere!
And screen sharing is coming
11Meet Ingate at Display Table #101
Ask your PBX, UC or call center vendor for this WebRTC integration!
Communications for Enterprise Apps
Shubh Agarwal
OpenClove
OpenClove and Apps
• Cloud Communications for Internet of Apps
– Video, Voice and Data
– Most advanced features
– iOS, Android, Web and Phone
• Apps experience
– Developed apps for DoCoMo, IBM, Yahoo..
– Multiple apps launched across platforms
Purpose of the App
• Defining the use case – direct monetization, productivity, better customer service, lower costs, new service
• Focus of the app – content vs. communications
• Nature of communications– Social: provides an engaging experience
– Complementary: enhances the user experience or productivity
– Critical: Core functionality relevant for purpose or monetization
How will users access app?
• Who is the audience, what devices and platform
• Web - WebRTC or need IE and Safari
• Mobile and Tablets– iOS, Android
– Native vs. Responsive vs. Web
• Phone support for bandwidth challenged or user preference
What will users do?
• What features are required to fulfill purpose?
• User to user vs. group real time Communications
• Recording - Content generation and management
• Streaming – participants vs. viewers
• Voice Dialing - Global reach including low bandwidth regions
How will I implement?
• Technology – codecs, security, firewall traversal, mobile bandwidth
• Backend - Capacity, Global coverage, Quality of Service
• User Identity – host app, enterprise ID, phone number, email, social ID..
How does it all come together?
• Ensure the User experience meets the intent of app
• Content and Communications mashing
• Button placements, launch options (pop up or embedded), feature enablement
• Audience sophistication – browser support, connection options, verbosity of the app
Summary
• Apps are about a purpose and success depends on user experience – NOT TECHNOLOGY
• Mobile and Web RTC is about a new way of doing things and not about re-inventing UC
• Enterprises need to focus on the purpose and the user experience and the technology (and industry) will have to catch up.
Thank YouPlease remember to complete an evaluation of today’s sessions
Questions (hidden)