SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
WebRTC for Telcos
Berlin 28/10/2013, Rich Communications
conference. WebRTC Workshop
q Helping telcos to add value to their current
q Making fix & mobile voice available using a
q Engage the customers & reduced the churn
WebRTC (Web Real-Time Communication) is an
API definition being drafted by the World Wide
Web Consortium (W3C) to enable browser-tobrowser applications for voice calling, video
chat, and P2P file sharing without plugins.
It could be implemented a WebRTC – Telco
Gateway to as a bridge between Web and fix/
mobile operator networks allowing service
providers to extend their communication services
to the Internet. It means creating web-based
IMS Core or SoftSwitches supporting SIP
access DO NOT need any modification
The WebRTC-Telco GW
can be deployed
outside the telco
premise, in a public or
private cloud as the
access to the network
core is UNI based
Hardware. Intel based server architecture running Linux (Dell, HP, IBM), no special
HW needed, also deployable in public clouds as AWS and virtualized environment
for cloud computing as Cisco UCS.
Scalable to the number of concurrent calls and users online needed .
A single platform could serve different cores, multi-tenancy available.
A single platform could serve different UX for different customers profiles.
It could be combined with RCS Thin Client Server to provide an all-in-one Unified
Communications experience: voice, video and enriched messaging.
Supporting current WebRTC capable Web-Browsers: Google Chrome & Mozilla
Firefox for Windows, Mac & Linux and Chrome for Android.
Via WebRTC instanced e-164 identity based phone
Outgoing voice-calls / Incoming voice-calls
NAB (network address book) . Possible easy integration with 3rd party NAB.
Call History (starting time, call duration, missed/answered/rejected icons)
UI/UX customizable with customer logo and colors. Also possible full re-design
UI/UX could include RCS capabilities when combined with RCS Thin Client Server Product
RCS Videoshare and IP Videocall capable
For the of RCS services with separated voice & RCS cores, dual register capable.
Login with credentials not exposing real IMS/Softswitch credentias). Security.
HTTPS available for signalling.
Plug&Play on top of SIP Servers, SoftSwitch with SIP access, IMS. Proven in 3 telcos from 3 countries. Also could
be integrated with legacy PSTN.
q The javascropt SDK allows to use Voice/Videocapabilities in your
q Embeddable modules make even easier to add WebRTC to third
party websites or applications. Just embedding the pre-designed
modules with CSS3 configuration to adapt to whatever UX preexisting style. Modules include now:
…more coming soon…
UI/UX as it is web
based could be fully
Combined with RCS Thin
Client Server product it is
possible to build a RCS
web client with all the
UI/UX as it is web
based could be fully
WebRTC is not a rival service of RCS nor
telco communications, instead it is a great
tool for telcos to extend their end-point
portfolio, and leverage a more ubiquitous
reach of their enablers.
The platform includes the
web-server to serve the
“WebPhone” but it could
be served from other
server as in the case of
future WebRTC cases
using the SDK.
tool to create
access to telco
A market of WebRTC services based
on telco capabilities, causal services
to engage the users and extending
the reach of telco driven comms.
Self-service web based market of
premium services based on WebRTC
Started activities in 2007 trying to open Push to Talk and IMS VideoShare as
REST API. Pivoted to RCS API exposure in 2010, 1st to market solution and
editors of the GSMA spec on RCS API.
Awarded in 2011 as pioneers in the area: GSMA RCS Innovation Winner.
Staff: 15. Growth planned. HQ in Madrid (Spain).
Currently with RCS GW in 3 tier-1 telco groups and several opportunities
opened in 3 continents.
GSMA network RCS API provider for Joyn Innovation Accelerator.
web client accreditation submitted (API based web client).
Pioneering the WebRTC for Telcos vision.
Juan developed his career in several companies as Motorola (Networks and Mobile Devices divisions), DMR
Consulting (now Everis), ICEX (Spanish Foreign Trade Office) and Colortex.
Juan holds an MSc degrees in Telecom Engineering from Polytechnics University of Valencia (Spain), an MSc in
Economics from UNED (Spain) and a Diploma in Politics from the University of London (Lead College, LSE).
Jose has developed his career in Motorola and Ceselsa-Indra
Mr. Recio holds an MSc in Telecom Engineering from Universidad Politécnica de Madrid and an MSc (Distinction) in
Information Security from Royal Holloway College, University of London.
Luis had previous roles at Motorola and Alcatel. developing Switching, GSM coverage planning and IMS software.
Also worked at Textil Bondrap.
Mr. Valencia holds an MSc degree in Telecommunications Engineering from the Polytechnics University of Valencia
David developed his career in Motorola, Altran SDB and Consum SCV.
David holds an MSc degree in Telecom Engineering from Polytechnics University of Valencia (Spain) and an
executive MBA from EOI Business School (Spain).
ü Solaiemes is solving a real problem telcos have. To find a
new role and make their assets a platform in the way that
developers can use them, as API.
ü Solaiemes is recognized by pioneering this field in the next
telco messaging, RCS joyn and the WebRTC for telcos
ü Solaiemes team is experienced, visionary, with international
experience in several continents and able to do more with
less and execute.
Addtional info at: