N-character Application Identifier (provided by SightCall)
This referrer should be the Application Identifier set into SightCall Allocation database.
Ad-hoc Meeting Point: refers to multi-party calls.
Premium user can also create a fleeting Meeting Point. The associated Conference Room can be reached from the creation of the Meeting Point to the end of the call. This is usually used for unplanned meetings.
Attendee: refers to multi-party calls.
Attendee of a meeting is a user that can only join a multi party call.
Authentication API: RTCC public REST API dedicated to users authentication on to the RTC Cloud
The main input of this API is an UID, that is answered with a token.
To connect to this API, it is mandatory to instanciate an Authentication API Client in the backend of the Application. This connection to the API requires a client.p12, an authCA.crt and an identifier/secret on the client side.
Authentication API Client: API client dedicated to connect to the Authentication API. This client runs in the backend of the Application. This client must reachable fromRTCC clients for them to authenticate to the RTC Cloud. For further explanation, please refer to the Authentication API client github repository.
Conference or multi-party call refers to a call hosted on an advanced RTCC cloud audio/video bridge, with one host user and up to 64 legs for attendees.
Display Name The Display Name is the user displayed name on call window.
Please note that some naming rules apply to the Display Name:
- String – max 127 characters
- Not Null
- UTF-8 Characters except: " ' < > and :
External User: refers to Authentication and User management
External User refers to 'external' users (authenticated users, visitors, guests, ...) to the Application. An
External User is so not directly authenticated on the RTC Cloud, unable to gain a authentication token through the Authentication API. An external user is created in reference to an internal premium user account, with very limited rights where he can only receive calls or start calls to the premium user it belongs to.
Host: refers to multi-party calls.
Hostof a meeting is the owner of the meeting. He manages the Meeting Point as well as the multi party call itself. A mulit-party call cannot start without an Host connected as host.
Internal User: refers to Authentication and User Management
An internal user is an authenticated user in the cloud. It requires a token to be provisionned and has rights associated to his profile.
Meeting Point Id: refers to multi-party calls.
Meeting Point Id is the identifier of a meeting point. This is the piece of data sent by the host to other users to invite them in a multi-party call
Permanent Meeting Point: refers to multi-party calls.
Premium user has the ability to have an everlasting conference room. The
Permanent Meeting Point is the entry point of that Conference Room. This is usually used to have a permanent place where a user can be met.
Profile: refers to Authentication and User Management
Profile defines the class of a user. A standard user has rights limited to 1:1 call, datachanel use and attend multi-party calls. A premium user can in addition to that host multi-party calls and use Dual Call. Profiles only apply to internal users.
RTCC clients: refers to the software clients which the users can use to connect to the RTCC cloud.
Currently available: RTCCdriver, WebRTC, Mobile SDK. A plugin will be available in the 5.4 RTCC.
Scheduled Meeting Point: refers to multi-party calls.
Premium user can also create a Meeting Point valid for a limited time period. The Conference Room is accessible only during the Meeting Point lifetime. This is usually used for appointments or scheduled meetings.
Token: refers to Authentication.
UID: refers to Authentication and Calls
UID stands for User Id. It is unique per provider and identifies a user. It is used during Authentication process to provision a user and retrieve a
token. It is also used in all APIs to call or text another user. Please note that some naming rules apply to the UID:
- Min size = 6 characters;
- Max size = 90 characters;
- Authorized characters: UTF8 - unicode - basic Latin, except: & " # \ % ? [space]
Correct UID examples:
Bad UID examples:
- user a
- JoHn SmitH
- my_user %a