Unified Communications in the browser v3.0 v2.2 ABOUT US Founded - - PowerPoint PPT Presentation
Unified Communications in the browser v3.0 v2.2 ABOUT US Founded in 2006 as a VoIP system integrator. No VCs, privately held Addressing the software service provider market. HQ in Spain, worldwide sales through partners. Small size (~25
v2.2
Unified Communications in the browser
v3.0
Founded in 2006 as a VoIP system integrator. No VCs, privately held Addressing the software service provider market. HQ in Spain, worldwide sales through partners. Small size (~25 engineers). Named by Frost & Sullivan as “Emerging company to watch” in 2014.
No installation, plugins or extensions ! Works in any device PCs, smartphones, etc No more costly toll-free numbers or call-backs HD video & audio + chat and file transfer Easy to integrate with the customer assets
What is Sippo Web Collaborator?
1 2 3 4 5
UC suite fully-interoperable with legacy networks RIGHT FROM THE BROWSER!!!
Web browser to web browser
OPTION A:
Enterprise use case
ACD PBX SBC Web browser to legacy phones
OPTION B:
How does it works?
Web browser to web browser
OPTION A:
Enterprise use case
ACD PBX SBC Web browser to legacy phones
OPTION B:
How does it works?
Audio & video
Key features
Live chat File transfer Screen sharing Co-browsing, form sharing, etc. User management by administrator Contact list Meetings and group management Browser detection
Using third-parties Using sippo.js and Sippo WAC modules Sippo Web Collaborator
TIME TO MARKET FLEXIBILITY
Better customer experience and new revenues based on OTT services.
Use case: extending telephony to the browser
Scenario
Residential users are will to access fixed-line audio fees from anywhere (not only from home).
Solution
Using Web Collaborator, users can access audio calls from anywhere. In addition they can add video or IM to call other Web Collaborator
create OTT solutions.
Benefit
+1 555 333 1111
+1 212 666 4444
Use case: enterprise webphone
Better user experience, solve BYOD problem and reduce expenses in licenses and
Scenario
Companies are concerned with proprietary softphones (platform dependant, installation-needed, vendor lock-in. etc).
Solution
Using WebCollaborator, user can access to their existing PBX services, including video and IM, from any device with no need to install or update
with solutions like MS Lync, Cisco, Avaya, etc.
Benefit
Enterprise network
Multi-device Video and IM Meetings Land line mobile ACD PBX SBC
Use case: remote agents
Mobility and flexibility for contact center’s agents. Reduce expenses in devices, licenses and operation.
Scenario
Contact centers are willing to allow remote agents to connect to their platform from home, but the use of different devices is a stopper (VPN, home firewalls, etc…)
Solution
Using Web Collaborator, agents can use their softphone from any device with no need to install or update anything. Video and IM are also available.
Benefit
ACD PBX SBC
Enterprise network
Use case: virtual desktop infrastructure
Better user experience and reduce expenses in devices, licenses and operation.
Scenario
Companies are trying to virtualize their infrastructure to reduce costs. An strategy is need for voice services.
Solution
Using WebCollaborator, user can use their softphone from any device with no need to install or update anything. Only is needed a WebRTC-enable browser.
Benefit
ACD PBX SBC
Enterprise network
Use case: new services for smart TV
Better user experience and
increase revenues.
Scenario
Triple-play telcos are willing to add new services to the TV.
Solution
Using Web Collaborator and an adapted set-top-box or TV, user can make audio and video calls from the TV, while their are watching their favourite TV show.
Benefit
Service video agent Smart TV or Set-top-box
Telcos could take advantage
customers) to leverage their networks and provide new services to end users.
Scenario Solution Benefit
These days some telcos have adopted an OTT strategy as a way to compete with third-parties
real time communication services. WebRTC could help to implement this OTT service thanks to its capacity to work on different platforms and devices. People are not used to identifying an OTT with a browser, but WebRTC could help to extend this new services to the web.
While WebRTC works in any device that can run a browser (tablets, PCs, etc) but not iphones, VoLTE is only supported on modern smartphones (iPhone 6 or 6s, latest Samsung Galaxy mobiles, etc). Despite this, we can say that WebRTC works in more devices than VoLTE as you can install free WebRTC-enabled browsers
In the case of WebRTC, as in any OTT service, it depends on internet/data connectivity. In the case VoLTE the limitation is LTE availability (and service activation by the telco). VoLTE forces telcos to offer QoS for voice (traffic priority to mail, etc.), while WebRTC depends on general QoS and it’s not possible* to give priority to this traffic.
COVERAGE DEVICES
WebRTC makes possible to build lots of user scenarios but VoLTE has two important advantages. First, telcos can control the bandwidth available and offer a better service by comparison by a pure internet service (like WebRTC). Second, the standard codec for VoLTE allows to
transcoding capabilities of the gateway.
QUALITY OF EXPERIENCE INFRASTRUCTURE
WebRTC does not define anything for signalling, standards are
VoLTE implementations are quite closed instead, as they depend on a specific implementation by the telco (protocols defined, few network equipment vendors available, etc.) and a high investment.
While VoLTE works in some of the most modern smartphones, lots of user devices are
etc) that are not natively connecting to the mobile telco networks (i.e. mobile tethering). Telcos are willing to extend the current VoLTE services to other devices, so WebRTC could be the best technology to enable this. Using WebRTC you can emulate really easy and fast the same behaviour as the VoLTE (including video) use case, assuming only the limitations of non-prioritizing the WebRTC traffic.
Multi-device
TELCO
RCS brings new messaging services that were not available on traditional IMS networks, like instant messaging, real presence, live video and file sharing across different devices and telcos. While VoLTE is related to access, RCS is pure application, so can be identified as part of the same segment as WebRTC.
WebRTC allows new use cases and UIs Works in any device PCs, tablets, etc Multimedia interoperability is possible today No need to install anything in WebRTC (browsers are everywhere) WebRTC can replicate the RCS interface
1 2 3 4 5
The WAC manages push notifications to WebRTC-based applications in smartphones (native apps running on Android and iOS devices). Users can opt-in to receive alerts like incoming calls or incoming messages. Today there are different initiatives of standardization bodies and browser developers (including Chrome) to support web push notifications in the browser (based on service workers). The WAC will be responsible again to notify alerts to WebRTC browser users, with no need to have the page open.
The WAC manages everything around the users, depending on the ID, contextual information and predefined user policies, media capacities and roles, helping the browser to download the WebRTC application adapted to it. The following parameters for user management may be configured via the Service API and different Sippo connectors:
NOTE that the WAC can also work as a Network Address Book or can manage the interconnect with a 3rd party NAB to host the user contact list.
The WAC supports different authentication methods, from its own identity manager to federation with existing customer assets and third party entities. The WAC validates a token with the gateway to allow the session.
As a host of WebRTC applications, provides security mechanisms to avoid traditional VoIP attacks and pure web and WebRTC threads:
managements
Malicious webserver websocket http
Malicious Script
Learn more downloading the whitepaper “WEBRTC SECURITY CONCERNS
Malicious Script Malicious Script
?
The WAC stores information about the accesses to the web applications and, via WAPI, all the actions made with the WebRTC applications by the end users (calls and CDRs, Instant messages and file shares, configuration changes and activity detection). In addition any interaction using the Service API and Sippo connectors is stored This is being used for:
As stated before, the WAC get not only information from calls as CDRs as contextual information and feedback from the web access is also available. Type of device, browser, version, usage of the WebRTC apps, default language, URL referrals, etc. can feed big data analytics solutions to get information from the user. As the WAC includes some modules and expose some APIs to deal with user provisioning, user policies and applications and services enablement, this is the element that orchestrates all you need to deploy a WebRTC service.