Using WebRTC with Calls
Although you can use Infobip webRTC SDKs independently from the Calls API, combining webRTC with Calls API comes with the following advantages:
- Comprehensive and granular control of webRTC calls from your backend application.
- Easily join and remove webRTC calls to and from conferences.
- Mix webRTC calls into the same conferences with any other supported endpoints (phone, SIP).
- Implement routing logic for inbound webRTC calls in your backend applications.
- Play text-to-speech, collect and send DTMF, or play audio files in webRTC calls.
To use webRTC in Calls, you need to:
- Declare a webRTC Application by following our instructions in the webRTC Getting Started section.
- Integrate Infobip webRTC SDK into your application(s), whether web or mobile (Android/iOS).
- Follow specific guidelines related to the Calls API platform as documented in our webRTC's SDK Wikis: Javascript SDK, Android SDK, iOS SDK.
IMPORTANT
WebRTC's Dynamic Destination Resolving is becoming a deprecated feature, superseded by the Calls platform. When using webRTC together with the Calls API platform and if you need to take routing decisions in case of inbound webRTC call.
We strongly recommend that you do not implement the webRTC Dynamic Destination Resolving feature but instead leverage the Calls API platform and associated event traffic.
Was this page helpful?