Rich Communication Suite in the Cloud

VoipSwitch has extended its RCS Cloud offering by adding a new private label hosted model. The model combines the VoipSwitch hosted and managed Class 5 softswitch partition with the Rich Communication Suite Cloud platform, giving providers even more flexibility. Up till now a provider could enroll on our white label reseller program or become a 3rd party partner. The main difference between the two is that a reseller can’t bring their own termination while a partner can handle the offnet traffic on their own softswitch and thus decide on the routing and billing. This, however, requires a provider to already have a proper system in its network, and that system must be capable of certain integration with the RCS Cloud.

The newly introduced hosted model bridges this gap and enables a provider to have their own voice termination on our managed softswitch platform. The provider has access to an isolated partition where they can interconnect with termination carriers, use their own payment gateways for online top-ups, and connect to DID suppliers.

On top of that, VoipSwitch is providing RCS mobile dialers for Android and iOS as well as an RCS desktop version for Windows PC and MAC. The softphones are delivered branded according to the provider’s specification. The RCS user to user audio video communication and additional services are realized through the RCS cloud; provisioning of new accounts with SMS verification is also on VoipSwitch’s network. The provider’s partition handles the paid traffic only, that is, calls and SMSes to non RCS users (offnet traffic) and inbound traffic (DIDs).

In this model providers are charged a fixed rate per month, which is the simplest approach, letting a provider estimate the exact future cost of the business. The rates vary depending on the partition’s concurrent call capacity.

What Rich Communication Suite means:

RCS enhances consumer VoIP services by adding a whole suite of new features that go beyond voice and simple text communication. The emphasis is on a contact oriented approach where a user can not only initiate conversation but can also see his contacts’ interest, mood, location and readiness to communicate.

More about VoipSwitch’s RCS Cloud services can be found here:

multidevice support

This functionality enables users to have the Rich Communication Suite client installed on various devices; for example, on smartphones (e.g. iPhone or android) and at the same time on a desktop PC, Mac or tablets (e.g. iPad) using the same account. Incoming calls and messages are forked and ring on all devices; a user can answer from any terminal. The mechanism also works with the PUSH notification framework. PUSH notifications are sent only to those devices which are not online while the softswitch still sends the SIP call directly to the others which are registered to the server.

The implementation is based on the +sip.instance feature tag contained in the Contact header of the SIP Register request and identifies each unique User Agent instance.

When a user logs in on a particular mobile device (smartphone, tablet) for the first time, a unique ID is obtained from the device’s parameters. The ID is then sent to the Web API and stored in the user’s profile/ devices table. The administrator can set a limit on the number of devices per user; in the Vippie client, for example, the limit is set to 4 devices. In addition to mobile terminals a user can log in from a desktop PC, Mac and the Web. In this case, however, the instance ID is the same regardless of the computer being used. This means that a user can be registered from only one desktop at a time; his previous session will be overridden.

Every attempt at registering from a device which does not contain an authorized sip.instance will be rejected on the softswitch. Management of the devices and associated instance IDs stored in a user’s profile are available from the User Portal.

A user can use the same public ID across all his devices or log in using a different ID on a second or other terminal. The private (main) identity remains the same. Public IDs represent how a user is presented to others and how he can be discovered. Allowed IDs include phone numbers (with verification by SMS or phone call), Vippie ID (a service id, username) and social nickname from facebook and google +.

The feature is available in VoipSwitch’s Rich Communication Suite client for iOS (from version 2.6), Android (from 2.17) and also desktop clients for Mac and PC.