RCS Developer Portal as a Service. Revolutioning how telco API may be offered.

We are pleased to announce a new offering, the concept of RCS Developer Portal as a Service. Telcos will be able to launch RCS API at the same time that RCS/joyn service itself. No painful integrations, experiment what plug&play means ;).

The telcos just need to provide connectivity with the telco SBC and a bunch of RCS users (numbers) to be used as developer created services will be enough.

What about the API Management layer? Well, it is not needed to try to reinvent the wheel, the portal front-end and API Management use 3Scale, one of the leading vendors in the API management field. The developer look&feel and the developer plans are fully customizable.





Time now for telcos to use the cloud for their own enablers exposure. Time is money!!!

New Product: RCS Advertising Platform. Creating a role for telcos in the advertisement market.

We got involved in RCS 3 year ago and pioneered the REST API network exposure. We received many telco feedbacks about considering great the API to create person-to-service cases but were concerned about the monetization capabilities of RCS/joyn in a context of free messaging apps competition. With this new product that is combined with RCS API GW, we provide telcos a white-label platform to engage development and create a new business model, use the contextual advertising in-chat RCS API based services created by developers.

In a sentence, a Google Adwords/Adsense model for telcos, using the instant messaging (not the search or blogs) as the media to insert ads.



We are sure that properly used it could be a very smart marketing model, both, for developers and users, and the API GW only will insert the chat or file transfer (pic, audio, etc). The textual and also location (push/pull) will allow a very accurated targetting, being this new mobile marketing the way to make service providers strong players in the SOLOMO (social, local, mobile).

Also, finally telcos can use their enablers to engage and foster the ecosystem by proposing a fair revenue sharing model while users are enjoying new services for free.

Any feedback welcomed.

#joynhack in Berlin, welcome the RCS API Hackatons

Two "solaiemers" attendend the joyn Hackaton in Berlin past weekend. Organized by Orange and Deutsche Telekom the 2 hackatons, one in Paris last month and one in Berlin the past weekend make clear that RCS/joyn is not only about person to person messaging but a platform. The platform is useful for developers to create amazing use cases for the users.

During the weekend the RCS API was used in 2 ways: embedding RCS communications in apps and creating network based services. The winner of #joyn category (Yeppt) was the "porting" of a web based service to the chateable experience.

We welcome this kind of initiatives to engage developers. RCS can enrich the apps and also can complement the App model by providing an alternative interaction model based in chat & file transfer as we explained our last post.

It would be great to see other telcos organizing this kind of hackatons, engaging developers to use their exposed or "to be exposed soon" enablers and also to get first hand feedback from the real movers of the ecosystem, the developers.

The greatest feature joyn/RCS can have versus OTT's is the openness, the API to go beyond the person to person messaging.

You can see the G+ of the event with pics uploaded by organizers here

Understanding the RCS network REST API potential in just 4 minutes.

We prepared in-house a 4 minutes cartoon-type video explaining the potential of the RCS/joyn network API. It shows examples of its use to make RCS messaging a platform by making the phonebook a hub of chateable services.



If you like it, please share :-)
the Solaiemes team

Solaiemes WebRTC-Telco Gateway. Telco voice (including PSTN) easily ubiquitous.

Solaiemes works hard to help telcos to adapt to the new competitive scenario. We see WebRTC as huge opportunity for telcos as they finally are not depending on 3rd parties and their roadmaps to deliver "physical end-points". Also, we continue relying on UNI (user to network interface) approach to avoid painful integrations with the telco cores. Connecting to the SBC is the perfect way, plug&play, works inmediately and allows cloud deployment when needed.


We can say we tested the platform in several live telco environments, and it worked with no integration at all needed. Just provisionate in the platform the user credentials and voice become ubiquitous. We published videodemos in previous posts: webphone and RCS webphone.

Telco VAS decline, the key role of telco APIs & the coining of a new term W2P

Telco is an industry facing transformation, basic services being cash-cows with high margins as voice and SMS, and lately broadband, are becoming commodities in a fierce competitive market. Most of telco customers are contracting plans with a number of minutes, SMS and data enough for their needs at very low prices.

Value Added Services (VAS) being perceived as the next stream of revenues are not properly implemented by telcos. We could read this week about the VAS revenue declining.

What is happening? Well, too many things at a time:

• Telco enablers as Voice and SMS for VAS being exploded more successfully by companies creating REST API to use the communications enablers as they are costume to work with social networka and internet tools APIs. Companies as Tropo, Twilio, Plivo make easier to use telco enablers than the own telcos.

• New communication enablers beyond voice and SMS as rich messaging are being pioneered and led by amazing "over the top" companies as Whatsapp, Line, WeChat (Tencent) harming telcos in 2 ways: commoditizing the enhanced messaging as being offered for free or just for a small annual fee, and capturing new VAS market share (virtual goods, B2C, etc).

• Service providers (carriers) are not properly adapted to the new times: years to deploy a new technology is not an acceptable period, waiting to the perfect standards with all the features defined is not how now service cycles work. RCS (Rich Communication Services)/joyn had to be deployed years ago and just right now it is taking off slowly.

• Fortunately telcos realize about the potential of APIs and they are giving steps in the right direction launching developer portals as Telekom Developer Garden, AT&T Developer Program, Telefonica Bluevia and others. They are understanding finally that Parlay is not API for developers, developers needs web APIs (REST, SOAP).  Unfortunately the new communication enablers are not usually launched with API to try to generate non person-to-person communication use case from day 1.

• It is difficult for the carriers to work at the start-up pace required if they don't learn to work with start-up's and it would mean to use their investing arms to fund interesting companies creating stuff useful for telco transformation, paying fairly for trials...and avoid screwing up innovators :-(

• Also, incumbent vendors, the so-called NEVs, may also try to cooperate with small vendors with complementary stuff to jointly help telcos to adapt. Obvious? NO, we suffered first hand how NEVs tend to promise to offer "very soon" what small innovative vendors are doing and keep telcos (as they are more customed to work with NEVs) waiting and waiting and wasting time and time is money.

All above is the cocktail that could make telcos irrelevant in the VAS if they can not adapt properly soon, as sooner the better. Which are the keys? Telcos commercialized universal communication enablers, known user experiences that properly combined can be as Lego pieces to create services. APIs are the telco Lego. 

What can be built with that Lego? Whatever thing, communication is not about people only, or between machines only, communications is between people, services as customer care bots, machines, home sensors, etc. Today, the concept of A2P/P2A (application-to-person / person-to-application) coined for VAS using SMS is too small. 

A new term may be coined W2P/P2W (person-to-whatever thing, whatever thing-to-person) and messaging, RCS may be the enabler being the HUB of those type communications, with the benefit of not facing learning curve, chatting is chatting, sending files is sending files.  

Thanks to telco APIs and semantic technologies (a hot topic) telcos may take benefit from the texting trend and become the relevant player making easy to connect the world, not a bit level but at service level: people with customer care bots or agents (B2C communications), people with their home sensors, people with social games & new smart advertisement, people with info services with just the same tool, the same user experience. 
Too, this common user experience thanks to the APIs will be available in all the screens (web, TV), telco should not be only tied to "phone-type" devices.

Long life to the W2P coin!

Solaiemes participated in the TelcoAPI workshop at SDP Summit.

Solaiemes had the opportunity to attend the SDP Global Summit organized by Informa Telecoms  & Media the past 17-20th September in Rome.

It was an interesting event with telcos and vendors explaining their approaches to the "service delivery". Topics as how close API exposure & telco core have to be in the architecture and long tail versos internal/enterprise users to be the target were discussed.

Our opinion is that telco exposure may be done in a way that could be deployed easily, and with no/little integration tasks. We know big vendors sometimes like the complexity as a form of lock-in but we embrace UNI-exposure (user to network interface, API behaving as telco-client/end-point). It is the way we are doing for RCS API exposure and also for WebRTC-Telco exposure.

We are including our slides from the TelcoAPI post-conference Workshop chaired by Alan Quayle where we could share the stage with great companies as Tropo, Telestax & Apidaze. We talked about RCS API as opportunity for telcos in the B2C communications space.


Alan Quayle just published about the SDP Summit review and the TelcoAPI Workshop with his own slides and the slides from participants in the SDP Summit and the workshop.

We particularly recommend the slides 36-64 of the his presentation, priceless as it is described with funny slides why the old-telco mindset could make telcos irrelevant soon. It would make no sense, many vendors, established ones and young blood ones are trying to help them to stay relevant and competitive players in the new communication services field.

Voxeo Pioneers Use Of joyn In Business-To-Consumer Communications Using Solaiemes’ RCS API Gateway

Voxeo CXP is the first Multi-Channel Application Platform to support joyn as a communication channel for more engaging mobile customer self-service 

Cologne, Germany and Madrid, Spain, September 04, 2013 – Voxeo, an Aspect company, is pioneering the use of the joyn messaging service in business-to-consumer communication by adding it to its award-winning Voxeo CXP multi-channel self-service platform, allowing companies to offer much richer, more engaging mobile self-service communications to their customers. Voxeo has integrated joyn into its CXP (formerly VoiceObjects) platform using the Solaiemes’ RCS API Gateway, creating a developer-friendly environment for fast and easy deployment of joyn-powered apps to existing customer communication strategies.

joyn was developed by the GSMA as a joint service initiative between carriers and handset providers. It allows individuals and organisations to share images, documents, music, video and other files during or outside of a regular telephone call. Like SMS, it comes pre-installed and configured on the mobile phones of participating carriers. Voxeo’s award-winning CXP application lifecycle management suite is the first multi-channel self-service platform in the industry to support joyn, helping to advance the Rich Communications Services (RCS) network.

 “joyn has huge potential for business-to-consumer communication, both in agent-assisted and automated self-service solutions,” says Tobias Goebel, Voxeo’s director of mobile strategy. “By introducing joyn to Voxeo CXP via Solaiemes’ RCS API Gateway, it becomes exceptionally easy for organisations to add joyn-powered apps to their customer communication strategies in a fully integrated fashion.”

Voxeo CXP is the first application development and lifecycle management suite that helps customer service departments build, deploy, manage, and analyse automated applications on joyn, in addition to the IVR, mobile Web, and SMS channels that CXP also supports. Voxeo has integrated joyn with its CXP platform using the Solaiemes’ RCS API Gateway. Solaiemes facilitates the integration of non-RCS platforms through a simple but powerful HTTP interface.

Voxeo deployed a pilot program of joyn-enabled Voxeo CXP with one of its European mobile carrier clients. The carrier reported a high degree of success in designing self-service applications that, for example, allow the customer to request account status information or top up their prepaid account.

Voxeo and Solaiemes expect the joyn-enabled CXP platform to be adopted rapidly by its mobile carrier clients, who are eager to derive added value from their investment in the development of this new messaging standard. Ultimately joyn should see adoption in the enterprise as well, as its communications streams can be encrypted, thereby allowing more secure B2C communication than can be provided by third-party vendors. For example, travel companies could use it to allow self-service and ticket distribution, or insurance companies to capture video footage of accident damage.

 “Solaiemes envisioned from the beginning the potential of joyn instant messaging as something beyond the person-to-person casual messaging, and considered it a perfect channel for B2C communication,” comments Juan Mateu, Solaiemes co-founder. “It is exciting to see Voxeo add joyn as a communications channel in its CXP multi-channel self-service platform and make joyn available to companies to communicate with their customers”.

About Solaiemes
Solaiemes creates infrastructure to help carriers, MVNO’s and service providers to enrich the communication experience making it ubiquitous and available to 3rd parties to create value added services on top. Solaiemes pioneered the 3rd party API exposure of RCS/joyn to build application to person and person to application use cases and different types of endpoints, combining telecommunications and internet spaces. Visit http://www.solaiemes.com

About Aspect
Aspect’s fully-integrated solution unifies the three most important facets of modern contact center management: customer interaction management, workforce optimization, and back-office. We help the world’s most demanding contact centers seamlessly align their people, processes and touch points to deliver remarkable customer experiences. For more information, visit www.aspect.com.

About Voxeo
Voxeo, an Aspect company, removes the locks that make voice, SMS, instant messaging, Twitter, web chat, mobile web, unified communications and self-service applications difficult to create, manage, analyze, optimize and afford. Every day we work to unlock the neglected value of these communications solutions with open standards, disruptive innovation and a passion for problem solving–fueled by an obsession with customer success. We do so for more than 250,000 developers, 45,000 companies and half of the Fortune 100. Visit us or join our conversations on the web at www.voxeo.com, blogs.voxeo.com, or twitter.com/voxeo.

PR at Voxeo's site

WebRTC Phone. Fix phone is not anymore something tied to a wire.

Following our previous post where we show a full communicator based on WebRTC including voice, video, and RCS/joyn features we received some questions from customers & prospects about if it could be used only to extent the reach of traditional PSTN or VoIP numbers with a simple UX.

The answer is YES, OF COURSE. We prepared a simpler WebRTC Phone supporting voice call, phonebook (NAB, network address book) and the call register. Have a look please:




(*) Note: it is difficult to record the live audio from demos :-(, but we can say and show the audio-quality is better that it could seem listening the video :-)  You can request a demo.

Google Chrome becomes a real phone with Solaiemes WebRTC.

Solaiemes is using WebRTC to build a compelling solution to help telcos to deliver ubiquitously their communication services. Now, we have created for Google Chrome (the most advanced WebRTC browser) a web-phone that enables a PSTN line (it could be also a mobile line or VoIP) to be accessed everywhere just with a browser.
You can see how you can dial a number and make a simple call, or you can be reached by a mobile joyn capable number and enjoy the features of RCS/joyn as video-share.




Fix carriers are no restricted anymore to offer communications tied to a physical wire, VoIP telcos are now free to offer their services tied to softphones to be installed or VoIP physical phones, mobile numbers will be also available from a web browser. The communications revolution is just starting and telcos must defend its role by delighting their customers.

Solaiemes to offer joyn as a platform for Firefox OS. Personal messaging & chat based use cases in one.

Finally Firefox OS is taking off. The web as a platform in this new concept of smartphones matches completely with the Solaiemes vision of keeping telco stuff at telco side, and build the communication experience witht the telco API exposure.

Solaiemes already has a HTML5 client for Firefox OS to be tested by telcos in the market. It is based on the standard OMA RCS API exposed by RCS Thin Client Server product, compatible with all RCS core solutions (ZTE, Newpace, Ericsson, etc) and even with SIP Servers as Kamailio.

See what can be done with joyn on Firefox OS in this minisite joynfirefoxos.solaiemes.com

We are offering to test it in our RCS-Lab environment and test also the concept of chateable services (info services, casual games, self-service CRM) that you can also create easily with the REST API.

Also, it could be used as client for the GSMA joyn Innovation Accelerator  to test the use cases you are creating.

It's time for telcos comitted with Firefox OS to take an active role in enriching the platform with useful services and also create a framework for open innovation with 3rd parties using joyn API.
Developers can now work in a way to create alternative UX to use their services using enriched messaging: chat, group chat, file transfer, location push, etc. In this new platform joyn and OTT messaging are departing from the same line, and telcos can take the lead if move faster, just try :)

We are offering trial package for telcos including:

- 6 months license for RCS Thin Client Server (powering joyn client comms) & RCS Solution GW powering the 3rd Party exposure API to create A2P & M2P cases.
- Integrating with telco RCS full core (IMS + IM AS), IMS or using a SIP server as core. We can provide with a partner a hosted RCS Core if needed.
- Developer portal with testbed pc client to test easily the use cases based on joyn created.
- Training to internal developers and telco developer partners & Hackaton participation.
- A package of hours to help the telco to create own proof of concepts of joyn based service.
- Upon request support.

joyn casual games, m-learning & sponsoring of interactive services as a new way of mobile marketing.

We are presenting a new demo to demonstrate the use cases of joyn as a platform for services. A casual game based on chat interaction which also can be a learning tool has been creating by combining our RCS network API and a content API, a linguistic API by our friends of Molino de Ideas, see APIcultur.

Also, we unveil how these services can be offered for free to the users and monetized with smart advertisement & couponing, with perfect targetting as you can find the right sponsor to the use case offered. In-joyn-advergaming is born :-)


Quick service development, easy mash-up combining APIs, smart advertisement space, fun for the user...let's think in joyn because the person to person messaging initial case.

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 :-)

joyn location push API. The future enabler for LBS. Demo: city bus information.

We want to unveil a new call of our joyn API, the location push and want to explain how it can be a key enabler for future LBS in the fields of information, couponing, advertisement.
In this demo we are using joyn to create a real time information system of public transportation. We are using OpenData API from EMT, the local city bus company in Madrid.



The future of mobility will be creating a lot of services combining content APIs and channel API as the joyn/RCS. No need to install individual apps to access to each type of info you may require, just the phonebook will be the hub of services. Stay tunned, soon more.