WebRTC-Telco Monetization Webinar slides and poll analysis.

Thanks to all the attendants to our webinar about WebRTC-Telco Monetization and the feedback provided with the initial polls and a short final survey. You all can access to the slides here:



Also, we would like to share the initial poll results. Some key points:

• Most of the attendants consider that WebRTC is a technology that telcos may use.


• Almost half of responses consider "internal politics" the cause of telcos not using WebRTC.


• The telco applications of WebRTC are broad and not a clear preference about the focus.


• The poll suggests the convenience of starting to use WebRTC by Telcos asap, and in case of waiting for "something", the most relevant issue to be solved is the lack of WebRTC support in mobile/tablet platform, not Internet Explorer. It seems that the lack of support of WebRTC by IE is not a concern.

Feel free to contact us or provide additional feedback, by email, linkedin or just visiting our booth at #MWC14.

Solaiemes to exhibit at MWC 2014.

As previous years Solaiemes is  exhibiting at the Mobile World Congress 2014. Our stand will be located in the Spanish Pavilion in the Congress Square in the corridor communication the Halls 4 & 5. In the Pavilion our Stand is the number 14.

Solaiemes is presenting its new products with the focus on helping telcos to monetize new enablers as RCS (Rich Communication Services) and tools as WebRTC.
Solaiemes has the right portfolio at the proper time to market but needs strong commercial partnerships (you know, in this telco world size matters) and/or get additional funding for the growth stage. We are interested in meeting:

- Telcos: mobile, fixed, triple play or even OTTs eager to integrate RCS/joyn in their offerings with monetizaton platforms and also interested in WebRTC to generate telco revenues.
- Investors: yes, we are looking for some fuel to accelerate our growth. Yes, we know that Spain is no a sexy country for VC's and telco technology is not the preferred area for investors, but we keep trying :(
- Partners: complementary technology providers or integrators wanting to pioneer RCS and WebRTC in their countries integrating our solutions.
- M&A guys from companies interested in expanding portfolio through selected acquisitions.

If you want to schedule a meeting contact us at: mwc (at) solaiemes (dot) com
See you there !!

New Webinar: WebRTC Telco Monetization. WebRTC as Telco opportunity. Tuesday, Feb, 11th.

After the experience of our first webinar about RCS monetization and the positive feedback received we were encouraged to repeat :-)

Several RCS Monetization attendants confirmed that they changed their mind regarding RCS business opportunity or the how the deployment strategy shoud be prepared.

We think it is a good idea to prepare a new one covering the monetization strategy of WebRTC by telcos.

Our aim is to dismantle "mantras" regarding WebRTC as it is only a challenger technology for telcos and not a technology that telcos can use to enhance its communication services portfolio.

YES! WebRTC offers telcos a lot of potential and we want to explain how WebRTC will benefit telcos and how new telco services WebRTC based could get Monetized.

Please, join the WebRTC Telco Monetization. WebRTC as Telco opportunity on Tuesday 11th, February. 

https://attendee.gotowebinar.com/register/1446721263229590018
  

WebRTC is the new telcos gold. See how!

We have been following the debate WebRTC vs Telco and our position is that WebRTC is a very useful tool for telcos. WebRTC makes easy to expose their communication assets reaching the internet browsers as endpoints and also with the proper SDK as a key instrument to innovate creating new services that could be monetized.

We created a demo of WebRTC Telco Service portal, allowing telcos to sell not only voice minutes for outgoing calls but also creating a new business model. A possible new revenue could come from selling incoming minutes while allowing people to call you browser using alphanumeric codes or just being authorized using Facebook Connect. This is a way to protect the privacy of your phone number while allowing others to call you. YES, it means telcos taking advantage from internet companies stuff as well.



Our WebRTC-Telco GW product has now an SDK allowing to develope telco-WebRTC services easily. We have designed 3 services and create a Service Portal that telcos can deploy today as are UNI and can be connected to whatever IMS or VoIP server.

To create a funny and customizable user interface based on widgets we used Gridster.js  a framework from Ducksboard.

Telcos & You Developer. Our presentation at API Days Mediterranea

We were invited to speak at API Days Mediterranea event organized by apicultur (thanks a lot for the invitation).

It was a very interesting event about APIs: types of API and use cases, API management approaches, API business models and also telco APIs.

We would like to share the slides and demos of our talk about the telcos and their new role close to developers by exposing their communication APIs and RCS / joyn as a potential huge enabler for devs.


Looking forward next time event :-)

The way our RCS-e/Joyn REST API exposure works.

Solaiemes approach to the need of exposing carriers communication capabilities to 3rd parties was radically different to the previous ones. In the past, the attempts to expose capabilities to create services were based in OSA, Parlay, etc, more thought to offer professional services the own infrastructure vendors than a proper exposure to the vast ecosystem of developers. Our approach is simple, expose not directly from the core infrastructure but as "clients". We instance virtual clients (telco protocols of the clients being kept at carrier cloud) and in the case of our web-clients strategy. In this case the RCS-e Virtual Client API is not used to create an alternative UI in a device but to create a service based on messaging interaction (as it was done with SMS to create A2P and P2A cases).
The chart.

(click to enlarge)

We were awarded by this approach. As you can see, the 3rd party API is core vendor independent (no lock-in then), as it behaves as "client", we can say we are interoperated with the main vendors of IMS, Instant Messaging Server and the SBC leader. What we provide is that "extra mile" for telcos to create a new frontier, the one we name FTB (Friendly Telco Border). With our approach "plug & play" whatever RCS-e core can have integrated a 3rd party REST and SOAP WS exposure in less than a week and RCS-e automatically becomes a platform to create value added services (application to person and person to application) complementing the person to person messaging (initial use case). You can see in the chart how device clients interact with "service clients" representing services (i.e: CRM). Those "service identities" (additional contacts in the user phonebook) will be a new revenue stream for carriers, and if they are defined as SIP URI, also a new business model appears: the domaining based on the names of the services to be deployed. If we see how amazing companies as Voxeo, Twilio etc are succeeding "selling" communication capabilities, we see that they approach the developers/customers offering the interface they know how to use and needing none/minimum support: internet style APIs (REST & SOAP). Time for telcos to make their try in the way developers can embrace it :-)