Pages Menu
TwitterRssFacebook

Posted by on Jul 1, 2021 in Azure Communication Services, Development | 0 comments

Upgrade your Azure Communication Services Calling SDK to avoid disruption

Upgrade your Azure Communication Services Calling SDK to avoid disruption

There’s a new version of the Azure Communication Services Calling SDK (@azure/communication-calling) and it’s a required upgrade to avoid any disruption.

The new version is 1.1.0 and was released around 2 weeks ago. There shouldn’t be any breaking changes here, but the upgrade is required to address the fact that the Plan B SDP Semantics is being deprecated in at least one of the major browsers: Google Chrome. Support is expected to be dropped in M93, which goes to Canary on July 15th and Stable August 24th.

You can access 1.1.0 of the Calling SDK at NPM, or update your codebase to the latest of both the common and calling SDKs with:

npm install @azure/communication-common --save 
npm install @azure/communication-calling –save 

You should do this before July 31st if you have any published applications that need to keep running, although you can do it sooner than that. Why not do it today and start testing that everything is still working OK? This is especially true if you picked up Azure Communication Services in the early days when it was still in Preview; you might be sitting on an old beta version, meaning there could be some breaking changes moving straight to 1.1.0.

There is also a 1.2.0-beta.1 if you want to really explore the new… 🙂

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Tom is currently writing a book: Building and Developing Apps & Bots for Microsoft Teams. Register your interest today and be the first to know when it's ready to read.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.