The SightCall's platform is based on SDKs to be embedded in application on client side (i.e. on user side) and on a cloud where most operations take place.
A Token based authentication is needed on the client side. This token is obtained from the cloud. Once authenticated, SDKs can perform any operation directly from the commands it receives. Application front end or back end can also request some services directly from the cloud using a Rest API.
SightCall's platform helps you bring Real Time Communications to your application. In order to ease integration of those features, SightCall provides SDK for all supported devices and a REST Api for server to server features.
SightCall provides client SDKs for:
- Android to embbed real time communicatiosn in your Java Android application.
- iOS to embbed real time communicatiosn in your iOS application. The iOS SDK can be linked with an Objective-C or a swift application.
In addition to that, SightCall provides a Rest API for back-end operation like authentication or conference management, as well as a REST API designed for direct client requests.
As real time communications, SightCall helps you add into your app
- One to One Direct Calls
- Multiparty Conference Calls
- 6 digits Call Routing
- Waiting Room Features
- Chat services
- Inband Data transfer
- Presence and Roster Management
- Annotations features
- Automatic Call Dispatcher features
- Call Recording
One to One Direct Calls
Any authenticated user can call another authenticated user using his uid. The routing and the signalization of the new call is handled by the SightCall's platform. All standard notifications are sent on both side (ringing, proceeding, call active, hangup with reason,...). During a call, both attendees can start or stop video or sound, can start a screenshare or send low-latency messages to the other.
Multiparty Conference Calls
In addition to One to One call, SightCall's platform supports multiparty calls up to 32 participants. A waiting room mechanism helps the management of multiparty calls and control of the attendees. Even if anybody can join a multiparty call, a minimum profile is needed to
6 digits Call Routing
Call routing can also be managed within the Rtcc SDKs. A plus user can create at any moment a 6 digits code that can be given to a non registered user. No need for him to have an account in your website, he can simply authenticate to the Rtcc cloud using this code and will have limited rights: the code authenticated user can only start a call to the user who gave him the code or can join a multiparty call hosted by the user who gave hime the code.
Waiting Room Features
A complete set of feature has been introduced in the concept of waiting room. Based on meeting point where users can meet, the host of a call can accept or deny the right ro to users to enter a call. Users are placed in a waiting room untill the host notifies the system of his answer.
Chat service are also available in the SightCall's platform. Any user can send chat messages to another user authenticated in the same provider. Chat messages can be acknowledge or not, depending on the application needs and integration.
Inband Data transfer
In addition to chat, attendees of the same call can send inband data message to each others. Inband data messages are send within the video stream (inband) and have the same latency than the video. This feature is dedicated to short, low latency messages in a call. It can be used for sending coordinates of a pointer for example, but also for any kind of data the application is integrated with (IOT,...)
Presence and Roster Management
SightCall's platform also provides an advanced presence management. When a user connects to the cloud, he is automatically registered to the presence servers with a presence value equals to 0. The user, or his application, can set this value to any value between 0 and 255, 0 meaning not present. Any user on the cloud can request the presence value of another user (presence feature) and can also subscribe to changes of this value (Roster feature).
During a call, annotation are available, i.e. a user can annotate a paused video or a screen share to highlight some points on what he wants to show.
Automatic Call Dispatcher features
An automatic call dispatcher (ACD) is alos available. Agents can register with several criterias and users can request to start a call with an agent that matches requested criterias. The ACD then dispatches requests to matching agents that can accept or deny the call request. This feature can be linked to presence to add the presence as a criteria for the dispatch.
SightCall's platform can also record multiparty call, either locally and forward the recording on an Amazon storage, or via chunck http post request to a provider server.