Tuesday, April 22, 2014

Solaiemes, IMS technology partner of Project Clearwater


Solaiemes joined the Project Clearwater ecosystem as IMS Technology Partner.
Clearwater is IMS in the Cloud, a project sponsored by Metaswitch Networks.

We think Clearwater is a very good way to introduce IMS for telcos, decreasing both, complexity and cost, It worth to add value with VAS platforms from the ecosystem.

For us, it is great to become partners among a list of impressive telco technology companies as Telestax (we are Telestax partners also http://www.telestax.com/solaiemes-joins-telestax-partner-ecosystem), BroadForward, Metaswitch and cloud and virtualization companies as AWS (Amazon) and VMware.

IMS is not about a technology itself, it is about a way for telcos to create easily new IP based services and add value to their enablers. IMS is taking off finally but need options to be adopted by all telcos, not only the incumbent ones, and virtualized environments fill that gap. Application layer and VAS platforms may follow that path, and Solaiemes does.

We have tested our RCS API Gateway and our WebRTC-Telco Gateway and we can say that both are plug&play deployable on top of Clearwater IMS. Never telcos had so easy way to explore their future.

Thursday, April 3, 2014

Stop talking, start playing the game. Solaiemes RCS Monetization Suite trial unbeatable offer.

Messaging is a hot space and, late but finally happened, telcos are realizing about the risk of becoming the feared "just pipe" if they leave the communication services space.

Amazing OTT apps made mandatory to offer person to person multimedia messaging for free and telcos need to offer a compelling messaging and at the same time discover how to monetize fairly the service.

It's OK, Solaiemes was working almost 4 years to prepare this moment, we build not only the pioneer and most innovative RCS network API but also additional monetization elements as the Developer Portal, RCS Store and RCS Ad Server to innovate in mobile advertising using chat based context "non-push". All our infrastructure can be cloud based and connected easily to whatever RCS core solution. As it makes no sense to launch or be testing RCS in a lab without exploring user engagement VAS and monetization capabilities we would like to present our offering to telcos:

6 Months of hosted Solaiemes Monetization Suite infrastructure including:

- RCS Network API Gateway
- RCS Developer Portal using 3Scale as API Manager
- RCS Store
- RCS Ad Server
- RCS Web/FirefoxOS client based on network API.
- 250 engineering hours for support, training, or creating API based B2C proof of concepts at your request.

TOTAL PRICE: 49.000 € 
& the amount will be discounted if you decide to go ahead and deploy commercially our products in the first licensing PO.


  1. Why? Because of it is better to touch the things than just talk about, to build the future you have to touch the pieces as sooner the better.
  2. As a telco I would like the trials for free... We understand and would like to do in that way but we have to eat every day, we are not based in the VC paradises and technology for telcos is not their preferred area either :-(. At the same time we think that is a better offering that paying twice or more just to get 50 pages advice from strategic management firms.
  3. Can be customized the package with requirements as needing onsite stayings? Yes, let's talk.
  4. Is the Solaiemes network API deployed in some telcos? Yes, in 4 tier-1 we can not disclose yet they have our RCS API GW and also the GSMA joyn/RCS innovation accelerator environment for developers is powered with our solutions.
  5. What changes are needed in my network to use this trial? Nothing, we only need the RCS or IMS users/pwd and access to IP address of your SBC, the same than configuing device clients.
  6. Is it useful without RCS launched commercially and without external develepers? Yes, as you can engage the internal telco geeks to create A2P cases to make the launch more exciting and showing that RCS opened with API is beyond alternative messaging apps regarding use feasible use cases to delight the users.
  7. I am not a telco but a complementary technology provider, can we used the trial to create cases to bid jointly in the future to our customer based? Yes, let's talk.
  8. As telco I am starting to select RCS core, but we are interested in defining business model and prepare in advance some B2C cases as our own Customer Care based on RCS, can be used the trial without a core? Yes. We can provide a e2e testbed based on Kamailio (the only features you will be missing are group chat and store&forward).

The successful boat is about to sail, come on board !!!

email us at: info (at) solaiemes.com

Tuesday, March 18, 2014

RCS Monetization Suite

In the past months we have been unveiling additional platforms on top of our pioneering RCS network API GW.

It is time to explain why API itself is not enough in the telco industry today.

We have been talking with many telcos about the possibilities of the API, and they believed in the value, but they think they need huge base of users first. That will not happen if they focus in the person to person messaging where the incumbents today are OTT. We needed to unblock this egg-chicken scenario.

Well, in the last months we have been developing the complementary pieces to the RCS API exposure to move from telco internal trials/PoCs to something they can "sell" to both, enterprise and long-tail developers, engage the final users and the magic world...MONETIZE.

To expose easily the API developers are not keen to call account managers, sign paper contracts, etc...they want a Twilio or Tropo alike portal...and we just used a tier-1 API Management company, 3Scale to offer a RCS Developer Portal cloud based that whatever telco can launch quickly.

As a new way to access to services is born, the rich-chat based interactive cases, it would be needed a way to discover new "chat services" and add to your phonebook, the market of "RCS based cases", and we developed the RCS Store framework to make feasible the "RCS service market" , as standalone app or with API to integrate with RCS clients.

Finally we may talk about money, the well-know sentence "show me the money". Yes, telcos pay a good money to strategy consultants but ask the tech vendors about how to make money :-)

Enabling high rates of API concurrence for B2C is a revenue model with enterprise, but in the other hand, to get adoption telcos need to enrich RCS with casual chat based cases created by developers. How to reward them? Well, in the same way that internet companies are overlapping the telco space and revenue sources, telcos can overlap internet space and their traditional revenue sources as advertisement. Chat based services, person-to-information, person-to-chat-based-game become a new media, providing a context where inserting contextual non-push ads...Yes, the Google model applied to instant messaging. Voilà!, our RCS Advertising Platform fills the gap.

Does it makes sense, doesn't it? Then, bundling all the pieces of the puzzle is what we named as RCS Monetization Suite.

Monday, March 10, 2014

#MWC14 or how RCS is happening without a name.

After the hectic week of #MWC14 and the also hectic post Mobile World Congress week with urgent follow-up's, it's time now to explain our views.

For Solaiemes it was the best MWC ever, more visitors, many meetings with C-level people of telcos and leading vendors, and a lot of unexpected visitors that already knew about our portfolio and interested in include our vision and related portfolio in their future strategy. We can say proudly that had visitors from the 5 continents :-)

This year GSMA did not reserve an specific RCS or joyn area. The RCS acronym is included in the Future Communication space and the commercial brand, joyn, is quietly being removed. Only in a few pods in the Connected City and Future Communication areas RCS use cases were demoed. Does it mean that RCS is being discarded? NO, just the opposite, a lot of telcos are issuing RFP's, and talked openly about plans with us. RCS will happen as messaging evolution, perhaps it does not need new names but providing new experiences and associated use cased based on messaging. Just our vision. Some of the people we talk with expressed our same opinion, we need our own messaging, and SMS is not enough today. It seems that RCS is now in the scope of enlightenment.

http://www.slideshare.net/FrostandSullivan/key-takeaways-from-the-2014-mobile-world-congressAlso, we received many visitors interested in how WebRTC can be used by telcos, not only to expose their legacy enablers as voice but to create a myriad of new services. We returned with the batteries full of charge to walk the extra-mile and help to change the telco industry :-)

And last but not least we just read a couple of mentions.
We were mentioned in the Frost&Sullivan MWC 2014 Key Takeaways slides by Ronald Gruia.

Also we were mentioned by Andre Rios from Barcinno.com talking about Telco APIs and listing Solaiemes as interesting company together big names as Apigee and Aepona.


Now, it's time to work even harder, this year will be our year!

Friday, February 21, 2014

Helping users to control the overwhelming messaging tsunami. RCS Personal Manager to the rescue.

Instant messaging is a hot topic (this week Facebook acquired Whatsapp, a great messaging app) but not everything is invented yet! The popularity and affordability of messaging is creating a "messaging mess" that can not be solved with white/black list strategy but enabling used to define their messaging filters as molding clay.

This enhanced experience can be provided with our RCS Personal Manager AS, that can be combined with whatever RCS Instant Messaging server in the market and let RCS fill a gap that OTT's are not solving yet. The UX can be integrated in the RCS client itself, or offered as standalone mobile App or website using our RCS PM API to access to the IM-BOX and PM Rule Manager.

Also, the PM can be used of opt-out easily from B2C cases. RCS is a Platform but no reason to bother users that can keep only for personal messaging. Flexibility is key :-)

We are eager for innovative telcos wanting to be the first in market with this solution and RCS Core vendors for partnering

See you in Barcelona this MWC 2014 !!!

Wednesday, February 19, 2014

Unified Communications based on RCS using RCS API & WebRTC.

See the new Unified Comms client based on telco assets. Combining RCS and voice you can create full UC experience in you browser combining messaging and media features. For media WebRTC is used, YES!!!! WebRTC is useful for RCS!

The 2 Solaiemes products needed are Solaiemes RCS Web Solution API and the WebRTC-Telco Gateway. The UX/look&feel can be fully customized to your requirements, do not worry :-)

See you at #MWC14 !

Tuesday, February 18, 2014

Facebook Private Call App: telco wedding with WebRTC and social networks.

Hi, we recently talked about our WebRTC-Telco Gateway and its SDK enabling new innovative telco services and mash-ups with internet. We included some services, in a demo service portal, to authorize to be reached at your mobile without disclosing your number, one of them was using Facebook Connect.

Now we just built as Facebook app the service. The idea is that you may prefer not to give your phone number to new friends but have an option allowing them to call you at your number. Yes! It is possible, see how.

With this approach, both telcos and social networks can partner and offer premium services for new communication experiences with an added value, in the example, to be reachen at your mobile normally without disclosing your number.

More services coming soon!

Monday, February 17, 2014

Solaiemes in the WIPjam developer event at #MWC14

Apart from exhibiting at the #MWC14 Solaiemes will be this year actively participating in a new collateral event, WIPjam, an event to engage de mobile developer community. We will be participating in:

  • Telco API Workshop with representatives from very important companies Deutsche Telekom Developer Garden, Apigee, Broadsoft, Intel and the GSMA.

  • Innovation Mashup Hackaton our technology exposing RCS as API will be used with other APIs from companies as Apigee, Dejamobile and Orange Partners.

  • Expert Table where we will explain our strategy for developer engagement and RCS Monetization. Other companies participating in the Expert Table include Mozilla, Orange, Canonical and Dejamobile.
 We are ready for networking...

See you there !!!

Thursday, February 13, 2014

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.

Monday, February 3, 2014

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 !!

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.