-
Notifications
You must be signed in to change notification settings - Fork 0
Authentication
Since Infobip RTC is an SDK, it means you develop your own application, and you only use Infobip RTC as a dependency. We will refer to your application users as subscribers throughout this guide. So, in order to use Infobip RTC, you need to register your subscribers on our platform. The credentials your subscribers use to connect to your application are irrelevant to Infobip. We only need the identity they will use to present themselves on our platform. When we have the subscriber's identity, we can generate a token assigned to that specific subscriber. Using that token, your subscribers are able to connect to our platform (using Infobip RTC SDK).
To generate these tokens for your subscribers, you need to call our
/webrtc/1/token
HTTP API endpoint using
proper parameters. After you successfully authenticated your subscribers against Infobip platform, we can relate their
token to your application. Typically, generating a token occurs after your subscribers are authenticated inside your
application. You will receive the token in the response that you will use to make and receive calls via
InfobipRTC
client in your mobile application.
- Prerequisites
- Events
- InfobipRTC
- Call
- IncomingCall
- OutgoingCall
- CallRequest
- CallConversationsRequest
- CallOptions
- VideoOptions
- VideoTrack
- RecordingOptions
- CameraOrientation
- CallPhoneNumberOptions
- CallStatus
- CallError
- DTMFError
- ErrorCode
- RTCUser
- CallDelegate
- CallRingingEvent
- CallEstablishedEvent
- CallUpdatedEvent
- CallHangupEvent
- CallErrorEvent
- InfobipSimulator
- Conference
- ConferenceDelegate
- ConferenceRequest
- ConferenceStatus
- ConferenceError
- ConferenceUser
- NetworkQuality
- NetworkQualityChangedEvent
- NetworkQualityDelegate