azure-communication-callingserver-java

Migrate Java CallingServer SDK projects to Call Automation with renamed classes and updated dependencies.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/davidrrowley/CortexYouV3 --skill azure-communication-callingserver-java-davidrrowley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-communication-callingserver-java
Source: https://github.com/davidrrowley/CortexYouV3/tree/main/.agents/skills/azure-communication-callingserver-java
Command: npx skills add https://github.com/davidrrowley/CortexYouV3 --skill azure-communication-callingserver-java-davidrrowley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides clear guidance and reference material for maintaining legacy Java projects that depend on the deprecated Azure Communication CallingServer SDK and for migrating those projects to the newer Call Automation SDK.

Core Features & Use Cases

  • Migration Guidance: Shows dependency changes and renamed classes to update Maven coordinates and imports from azure-communication-callingserver to azure-communication-callautomation.
  • Legacy Maintenance: Documents legacy client creation and recording APIs for teams that must retain or debug older code paths.
  • Use Case: A Java service using CallingServer that needs to replace CallingServerClient and CallingServerClientBuilder with CallAutomationClient and CallAutomationClientBuilder and verify recording behavior after migration.

Quick Start

Use this skill to migrate CallingServer usages to Call Automation, update imports and Maven dependencies, and validate deprecated recording APIs in your Java codebase.

Frequently Asked Questions about azure-communication-callingserver-java

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Azure Communication CallingServer Java SDK to Call Automation?

To migrate Azure Communication CallingServer Java SDK to Call Automation, update Maven dependencies from azure-communication-callingserver to azure-communication-callautomation, replace CallingServerClient with CallAutomationClient, and update builder usages accordingly.

What is the replacement for CallingServerClientBuilder in the Azure Java SDK?

The replacement for CallingServerClientBuilder in the Azure Java SDK is CallAutomationClientBuilder, which provides the updated client creation mechanism for the Call Automation service after deprecating CallingServer.

Why was the Azure Communication CallingServer Java SDK deprecated?

The Azure Communication CallingServer Java SDK was deprecated to consolidate calling functionalities, requiring migration to the Call Automation SDK for continued support in managing calls and recording within Java projects.

How do I update Maven dependencies from azure-communication-callingserver to callautomation?

Update Maven dependencies by replacing the azure-communication-callingserver artifact with azure-communication-callautomation, then resolve renamed classes and imports to ensure the Java project builds correctly with the new SDK.

Can I still maintain legacy Java code using the deprecated CallingServer SDK?

Yes, you can maintain legacy Java code using the deprecated CallingServer SDK by referencing its documented client creation and recording APIs, though migrating to Call Automation is recommended for long-term support.

What are the limitations of keeping deprecated recording APIs during CallingServer migration?

Keeping deprecated recording APIs during CallingServer migration limits future compatibility, requiring validation of recording behavior against the Call Automation SDK to ensure functionality remains intact after updating client usages.