Communication Platform as a Service

This is our flagship product, designed for service providers to offer Unified Communications as a Service. We designed this product to be a money maker instead of a simple PBX. The objective here is to generate revenue with low cost of ownership.

The WeHostVoIP CPaaS has many different components.  You can see our architecture below.

The main difference between our CPaas infra-structure and others is the fact it has been build from scratch with service providers in mind. As this is the third generation of this product we have learned important lessons from previous experiences.

1 – The platform need to be easy to use with only the essential features

If you have too many features, the cost of technical support increases in the same proportion. Different than SIP trunks SPs are used to, communication services have so many features such as transfers, interceptions, ivrs. Many SPs don’t realize the amount of tech support required to keep an operation like this running. By providing only the essential, you can reduce the costs and make the system viable. Keep in mind, some customers are simply too expensive to serve.

2 – The platform needs to be compatible with most phones

I remember once saying to a customer, we support only A, B and C phones. He just said, sorry we have 1000 D phones in our customers, so you are not a fit.  Devices change all the time, we need to have a consistency on features such as transfer and interceptions. If you leave this  to the phone, you will have to test and teach every single model model of phone in the market.

3 – The Session and Media Border Controller

Each SP will have the opportunity to host a SBMC in the cloud or on premises. The objective is to get the lowest latency possible improving voice quality. As the media is processed in this server, there is no shared usage of your calls in relation to other SPs. This will guarantee the best performance possible for you and your customers. You can add as many SMBCs as required for your operations scaling the solution

To make it simple we have created three major interfaces, the SPs interface, the Customer interface and the Subscriber interface. Just to clarify, the SP is the phone company or Internet Telephony Service Provider. The Customer is the company buying services from the SP and subscriber is the customer’s user of a phone extension.

SP Interface

In the Service Provider Interface you can:

Define a carrier to terminate your calls. If you don’t have a carrier we can terminate your calls in our own.

• Define your logo, favicon and brand, see settings ->theming
• Create customers
• Create tenants 1 or more per customer
• Create a number inventory for your users to allocate
• Define how your customers will be billed
• Define how your customers will dial using a customized dial plan

Customer’s Interface (Tenant)

The customer’s interface allow you to manage the cloud communication instance of the system. There you can create subscriber and its extensions.

In the tenant interface you can:

• Define subscribers/extensions
• Define groups of subscribers
• Create a security group limiting international destinations
• Configure business and non business hours
• Upload audios and music on hold
• Configure the inbound handling using a visual dialplan

For the inbound handling you can use our exclusive Visual Dial Plan

Visual Dial Plan

For the subscriber we allow WebRTC Interfaces, SIP Phones and Softphones. For mobile we have a made a partnership with Acrobits SRL to provide a white label unified communications client to the user.

Free and Simple WebRTC client