Board Review: IC3 ACS Calling

[jamchengms]

Attention

For internal teams, our process for scheduling review sessions with the Azure SDK Architecture team has changed. The Azure SDK Architecture team has moved to using a Scheduling Tool for the scheduling of both Introduction and SDK Review meetings.

Thank you for submitting this review request. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.

The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.

Please reference our review process guidelines to understand what is being asked for in the issue template.

To ensure consistency, all Tier-1 languages (C#, TypeScript, Java, Python) will generally be reviewed together. In expansive libraries, we will pair dynamic languages (Python, TypeScript) together, and strongly typed languages (C#, Java) together in separate meetings.

For Tier-2 languages (C, C++, Go, Android, iOS), the review will be on an as-needed basis.

Before submitting, ensure you adjust the title of the issue appropriately.

Note that the required material must be included before a meeting can be scheduled.

Contacts and Timeline

• Responsible service team: IC3 ACS Calling
• Main contacts: James Cheng
• Expected code complete date: Aug 11, 2025
• Expected release date: Aug 18, 2025

About the Service

• Link to documentation introducing/describing the service: https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/voice-video-calling/get-started-with-video-calling?pivots=platform-android
• Link to GitHub issue for previous review sessions, if applicable: Azure SDK Review - [IC3 ACS Calling] #8247

About the client library

• Name of the client library: Azure Communication Services Calling
• Languages for this review: .NET, Android, iOS

Artifacts required (per language)

Please read through “API Review” section here to understand how these artifacts are generated. It is critical that these artifacts are present and are in the right format. If not, the language architects cannot review them with the SDK Team’s API review tool.

.NET

• APIView Link: https://spa.apiview.dev/review/db8d6cbd1678473da111b1967350b837?activeApiRevisionId=231cd58e92c745fdbd5cef8cde347830&diffApiRevisionId=f566b1438793401ab6438bbf0e1e8282&diffStyle=trees

Java

• APIView Link: https://spa.apiview.dev/review/27c8888536054317a5982da831a91f2d?activeApiRevisionId=f498bc25e9b14614976c5986bb985259&diffApiRevisionId=4ffa3703734f47e8a58ca6a3c80406a7&diffStyle=trees

Swift

• APIView Link: https://spa.apiview.dev/review/80768c5191c748a69f83e4e2d42bd97d?activeApiRevisionId=ba9d552867ac427792a9f906976fa965&diffApiRevisionId=d997c8eeea004e5a829d4ca1ab370fca&diffStyle=trees

For all other languages, send a request to the Architecture Board to discuss the best format on individual basis.

Thank you!