Add ACS Call Automation GA6

[antonsamson-msft]

Data Plane API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

• Link to API Spec engagement record issue:

Is this review for (select one):

• a private preview
• a public preview
• GA release

Change Scope

^{This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.}

• Design Document:
• Previous API Spec Doc:
• Updated paths:

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Release planner

A release plan should have been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

• 💬 Teams Channel
• 💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

• Open API validation tools were run on this PR. Go here to see how to fix errors
• Spectral Linting

Guidelines & Specifications

• Azure REST API Guidelines
• OpenAPI Style Guidelines
• Azure Breaking Change Policy

Helpful Links

• Schedule a data plane REST API spec review

Getting help

• First, please carefully read through this PR description, from top to bottom.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language	API Review for Package
Swagger	CallAutomation-CallAutomation

[weidongxu-microsoft]

Overall LGTM. A few minor comments may need your input.

AI summary

Summary of Changes from 2025-05-15 to 2025-06-15
1. Reference Updates
Changed Common schema references from stable 2023-11-15 to preview 2025-03-15-preview
Communication identifiers and models now reference from the newer preview path
For example: CommunicationIdentifierModel, PhoneNumberIdentifierModel, CommunicationUserIdentifierModel, etc.
2. StartCallRecordingRequest Changes
Removed the required property constraint for callLocator
Added support for using callConnectionId as an alternative to callLocator
This provides a more flexible way to identify the call for recording operations
The API now includes a description indicating "Only one of callLocator or callConnectionId to be used"
3. Common Model Updates
Added TeamsExtensionUserIdentifierModel reference from Common schema
Added MicrosoftTeamsAppIdentifierModel reference from Common schema
4. CreateCallRequest Extension
Added a new property teamsAppSource of type MicrosoftTeamsAppIdentifierModel
This allows specifying a Teams app as the source when creating a call with Teams resource account ID
5. WebSocketMediaStreamingOptions Enhancement
Added enableDtmfTones property
This provides a flag to indicate whether to stream DTMF tones in the media stream
6. Common Schema Version Alignment
The API now uses the consistent Common schema version across all model references
This ensures consistent behavior between related Communication Services APIs

[weidongxu-microsoft]

In 2025-05-01, this property is "required"

      "required": [
        "callLocator"
      ],

So this is also a break. Though you probably intend this for adding callConnectionId.

(it is mentioned in CI https://github.com/Azure/azure-rest-api-specs/pull/34830/checks?check_run_id=42662219511)

[antonsamson-msft]

Thank you for pointing this out. The change from required to optional for callLocator was intentional and was previously approved. As you mentioned, the API still supports usage of callLocator, but now also gives clients the option to use callConnectionId instead. This makes the API more flexible while maintaining backward compatibility.

Edit: Either a callLocator or callConnectionId must always be provided

Please let me know if you have further concerns or need additional clarification.

cc: @khannavikas

[mikekistler]

There are a few minor issues that I think need to be resolved.

[mikekistler]

Looks good! 👍