Tuesday, January 28, 2014

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. 


Wednesday, January 22, 2014

RCS Monetization Webinar, the slides.

We started yesterday a series of Webinars with a RCS Monetization one. Thanks to all the attendand online and offline to the seminar for their time and providing feedback with previous questions and a short final survey. We decided to make public the slides as we are pioneering this area, we know some competitors will be copying our pitch soon. It would not be the first time but copying slides is easy, make it happen is more difficult :-)

If you want to make it happen and think RCS can be a monetizable service from the beginning, visit as at Mobile World Congress!

Tuesday, January 14, 2014

Solaiemes Webinar. RCS Monetization & API blue ocean. Tuesday Jan, 21st.


Solaiemes pioneered the vision of RCS as a Platform to make feasible for telcos to evolve from SMS but keeping the B2C/A2P capabilities of monetization and customer engagement.

Now, Solaiemes, 1st available RCS network API (UNI, plug&play on top of whatever RCS core solution, IMS and not-IMS based) is expanding the VAS layer with additional platforms to speed-up RCS adoption by marketers and also increase the possibilities of engagement of customers.

In the past months we have been presenting VAS platforms using RCS API to create new revenue streams, now we want to explain in a Webinar our vision and compare with what OTTs are doing, and define an strategy to make the telco IP messaging a strong player & how to do it. Join our Seminar.

Monday, January 13, 2014

Solaiemes RCS API supporting WebSockets. Why it matters.

We are receiving as of lately many questions about WebSockets and Telco APIs.

Solaiemes started implementing WebSockets interfaces accross all our infrastructure in 2013, with working prototypes available since the summer. We are sharing now that experience to help the operators looking at this topic. Most likely WebSocket support will be included in the RCS OMA API spec soon and Solaiemes wants, among other API flavours, offer the standardized for the customers requiring it.

In our experience, WebSockets is first and foremost useful for Telco API developers as an additional notification channel. Existing notifications can be reused without any change, because WebSockets provide a native framing mechanism and it is agnostic about the format. Existing notification processing code can be reused.

This approach makes even more sense as in many cases WebSockets won't be available (for example, behind some corporate firewalls), so it is advisable to keep existing channels (native messaging, long polling, etc.).

From the developer point of view, it is just needed to plug (or activate) javascript plugins that automatically manage the transport used (long polling, web sockets, etc.), such as Atmosphere, Socket.io, etc.

On the infrastructure side, a new notification transport is added, but existing APIs can be kept, as REST or whatever format, because there is no need to move the whole API package to WebSockets.

Solaiemes has also API invocation over WebSockets implemented. It is very easy to transform an HTTP-based invocation model (REST or pseudo-REST) to WebSockets, but in our experience the benefits are not so evident, specially as WebSockets are not as ubiquitous as other HTTP mechanisms and scalability solutions do not play well with WebSockets in some scenarios.

WebSockets may be used where its use has a positive impact but not in the cases that its applicability is a mere "reinventing the wheel" without no straightforward advantage.

Thursday, January 2, 2014

New minisites explaining our RCS API + VAS Platforms & WebRTC portfolios.

RCS as a Platform

We created a couple of months ago a "back to school" style mini-site to explain the concept of RCS as a Platfom and detail our products related.

Past 2 weeks we created 2 additional mini-sites with "boards" to explain additional pieces of our portfolio.


To explain the WebRTC for Telcos approach the new minisite explains our WebRTC portfolio showing the webphones and RCS web clients and also the SDK to create easily services, all of them based in our WebRTC-Telco Gateway product.

Also we included the powerful concept of the "WebRTC Telcos Services portal with a demo of portal with innovative services.


And finally, a third minisite explains our vision of "chats in your apps / in-chat services". How group chat becomes thanks to the RCS API in something cooler and more useful.

We envision the group chat as something dynamic, where "chat based bots" can be included temporarily to provide fun (chat based games) or productivity (recorder, translator, group access to a travel agent, etc).
You can see the web "Apps in your Chats"

We are working to also refurbish our corporate site www.solaiemes.com :-) Hope to be on time for the coming Mobile World Congress, we need to make clear what we have to help telcos to keep a relevant role.