Migration overview

Warning

Following the major release of our new RTC SDK 2.0, we are deprecating the SDK 1.x releases. The SDK 1.x will be out of service on 31/10/2023.

Migration guides are written for the existing customers, currently using SDK 1.x, who must migrate to the newer release before the end of service date.

Before You Start

---

Upgrade to Infobip RTC Android SDK 2.0 version

Before you start with the migration, you need to upgrade the infobip-rtc dependency to version 2.1.0 or newer, which can be pulled from the Maven Central repository, and placed inside Your build.gradle file.

Please keep in mind, as of 31/10/2023, the SDK 1.x will no longer be supported.

SDK 2.0 Changes and Deprecations

---

With the release of SDK 2.0, several elements are changing or are being deprecated. In summary:

• InfobipRTC has been changed from a class with static method modifiers into an interface. You can see how to use it in this tutorial.
• Several call methods, their respective arguments, and call events were slightly renamed. Such changes are described in detail in migration guides:
  • if you previously used the call method, consult the WebRTC-to-WebRTC calls migration guide;
  • if you previously used the callPhoneNumber method, consult the WebRTC-to-Phone calls migration guide;
• The callSIP method is deprecated.
  • Note that you can use our Calls API platform to orchestrate the connection between the webRTC and SIP call legs.
• Error codes have been updated to be more granular.
• The service that handles token changes, FcmTokenRefresher, that should be added to your app's manifest, has had a minor change in its package name. It has been changed from com.infobip.webrtc.sdk.impl.fcm.FcmTokenRefresher to com.infobip.webrtc.sdk.impl.push.FcmTokenRefresher

The deprecated SDK 1.x documentation can still be consulted, until the effective end of support of the SDK 1.x.