New to Claude Skills? Learn how to install them →

Asickn33 on GitHub

Azure Communication CallingServer

Free

Maintain legacy calling applications with deprecated SDK.

Get this skill

Free · Opens the source repo

What Azure Communication CallingServer does

The Azure Communication CallingServer SDK for Java is intended for developers who need to maintain existing applications that rely on this deprecated library. This SDK has been renamed to Call Automation, and while it is still functional for legacy code, it is not recommended for new projects. Developers should transition to the new Call Automation SDK for any new development or features. The documentation provides clear migration paths for developers to update their applications from the old SDK to the new one, ensuring that they can continue to leverage Azure's communication capabilities without disruption.

This skill offers a structured approach to working with the legacy CallingServer SDK, including instructions on how to create clients and manage calls, albeit with the understanding that it is not the preferred method for new implementations. The skill also outlines class name changes and provides code snippets to help developers quickly adapt their existing codebases. This is particularly useful for teams that may have inherited older projects and need to ensure that they can maintain functionality while planning for future upgrades.

While the Azure Communication CallingServer SDK is still available, it is crucial for developers to understand its limitations and the importance of migrating to the Call Automation SDK. This skill serves as a bridge for those who need to keep their legacy systems operational while preparing for a transition to more modern solutions. It is particularly relevant for developers working in environments where legacy code is prevalent and immediate migration may not be feasible.

In summary, this skill is best suited for developers maintaining existing applications that utilize the deprecated CallingServer SDK. It provides essential information and guidance for managing legacy code while emphasizing the need to transition to the updated Call Automation SDK for future development.

When to use it

Use this skill when you need to support or maintain existing applications built with the deprecated CallingServer SDK.

When not to use it

Avoid using this skill for new projects; instead, utilize the Call Automation SDK for any new development.

What you can build with it

Maintaining Legacy Applications

Developers can use this skill to keep existing applications that rely on the deprecated CallingServer SDK operational while planning for migration.

Migrating to Call Automation

This skill provides guidance for developers looking to transition their legacy code to the new Call Automation SDK.

Understanding Class Changes

Use this skill to familiarize yourself with the class name changes and deprecated functionalities when maintaining legacy code.

How to install Azure Communication CallingServer

View source

1. Install with the skills CLI

npx skills add sickn33/agentic-awesome-skills/azure-communication-callingserver-java --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by sickn33

Azure Communication CallingServer (Java) - DEPRECATED

⚠️ DEPRECATED: This SDK has been renamed to Call Automation. For new projects, use azure-communication-callautomation instead. This skill is for maintaining legacy code only.

Migration to Call Automation

<!-- OLD (deprecated) -->
<dependency>
    <groupId>com.azure</groupId>
    <artifactId>azure-communication-callingserver</artifactId>
    <version>1.0.0-beta.5</version>
</dependency>

<!-- NEW (use this instead) -->
<dependency>
    <groupId>com.azure</groupId>
    <artifactId>azure-communication-callautomation</artifactId>
    <version>1.6.0</version>
</dependency>

Class Name Changes

CallingServer (Old)Call Automation (New)
CallingServerClientCallAutomationClient
CallingServerClientBuilderCallAutomationClientBuilder
CallConnectionCallConnection (same)
ServerCallRemoved - use CallConnection

Legacy Client Creation

// OLD WAY (deprecated)
import com.azure.communication.callingserver.CallingServerClient;
import com.azure.communication.callingserver.CallingServerClientBuilder;

CallingServerClient client = new CallingServerClientBuilder()
    .connectionString("<connection-string>")
    .buildClient();

// NEW WAY
import com.azure.communication.callautomation.CallAutomationClient;
import com.azure.communication.callautomation.CallAutomationClientBuilder;

CallAutomationClient client = new CallAutomationClientBuilder()
    .connectionString("<connection-string>")
    .buildClient();

Legacy Recording

// OLD WAY
StartRecordingOptions options = new StartRecordingOptions(serverCallId)
    .setRecordingStateCallbackUri(callbackUri);

StartCallRecordingResult result = client.startRecording(options);
String recordingId = result.getRecordingId();

client.pauseRecording(recordingId);
client.resumeRecording(recordingId);
client.stopRecording(recordingId);

// NEW WAY - see azure-communication-callautomation skill

For New Development

Do not use this SDK for new projects.

See the azure-communication-callautomation-java skill for:

  • Making outbound calls
  • Answering incoming calls
  • Call recording
  • DTMF recognition
  • Text-to-speech / speech-to-text
  • Adding/removing participants
  • Call transfer

Trigger Phrases

  • "callingserver legacy", "deprecated calling SDK"
  • "migrate callingserver to callautomation"

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Frequently asked questions about Azure Communication CallingServer

Similar skills