home / skills / sickn33 / antigravity-awesome-skills / azure-communication-callingserver-java

azure-communication-callingserver-java skill

safe

/skills/azure-communication-callingserver-java

This skill helps maintain legacy Java apps using Azure Communication CallingServer by guiding migration to Call Automation and preserving functionality.

npx playbooks add skill sickn33/antigravity-awesome-skills --skill azure-communication-callingserver-java

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.7 KB

---
name: azure-communication-callingserver-java
description: Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining legacy code.
package: com.azure:azure-communication-callingserver
---

# 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

```xml
<!-- 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) |
|---------------------|----------------------|
| `CallingServerClient` | `CallAutomationClient` |
| `CallingServerClientBuilder` | `CallAutomationClientBuilder` |
| `CallConnection` | `CallConnection` (same) |
| `ServerCall` | Removed - use `CallConnection` |

## Legacy Client Creation

```java
// 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

```java
// 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"

Overview

This skill documents the Azure Communication Services CallingServer Java SDK (legacy) and helps maintainers work with deprecated APIs. It highlights renamed classes, legacy usage patterns, and direct migration mappings to the newer Call Automation SDK. Use this skill only when supporting or troubleshooting existing projects that cannot be migrated immediately.

How this skill works

The skill inspects legacy CallingServer code patterns and shows equivalent Call Automation client and API usage. It explains old client construction, recording operations, class name replacements, and dependency changes so you can map deprecated calls to their modern counterparts. It focuses on concrete code snippets and migration steps rather than new feature coverage.

When to use it

You are maintaining an existing Java codebase that currently uses azure-communication-callingserver.
You need to understand how legacy recording, client creation, or call operations were implemented.
You must audit or patch a system where immediate migration is not feasible.
You want a clear mapping to azure-communication-callautomation to plan a staged migration.
You encounter runtime issues or build problems tied to deprecated CallingServer types.

Best practices

Treat this SDK as read-only reference: do not introduce new functionality with the deprecated package.
Plan and prioritize migration to azure-communication-callautomation for all active projects.
Replace deprecated dependencies and classes incrementally using provided mappings and tests.
Pin versions when maintaining legacy builds to avoid unexpected breaking changes.
Add integration tests around call recording and participant flows before refactoring.

Example use cases

Quickly identify the CallingServer-to-CallAutomation class mappings when refactoring client creation.
Audit legacy recording flows that use startRecording/pauseRecording/resumeRecording/stopRecording.
Patch a production hotfix while scheduling a migration to Call Automation.
Update build files to replace deprecated Maven coordinates with the new artifact.
Document legacy call handling code for handoff to a migration team.

FAQ

Is this SDK recommended for new projects?

No. The CallingServer SDK is deprecated; use azure-communication-callautomation for all new development.

What are the direct replacement artifacts and classes?

Replace the Maven artifact com.azure:azure-communication-callingserver with com.azure:azure-communication-callautomation and swap CallingServerClient/Builder for CallAutomationClient/Builder; consult the mapping table for other types.