azure-communication-callingserver-java
CallingServer legacy SDK
Developer Setup
Setup & Installation
npx skills add https://github.com/microsoft/skills --skill azure-communication-callingserver-javanpx skills add https://github.com/microsoft/skills --skill azure-communication-callingserver-javaOverview
What This Skill Does
Legacy Java SDK for Azure Communication Services call management, now deprecated in favor of azure-communication-callautomation. Covers the original CallingServerClient API surface including call recording, participant management, and server call operations. Only relevant when maintaining existing code built on the beta releases.
Application
When to use this Skill
- Configuring integration settings for custom agent workflows.
- Optimizing query execution and response latency in production.
- Developing clean, standard-compliant implementations for enterprise services.
- Troubleshooting connection timeouts and authentication handshakes.
- Monitoring API rate limits and execution pipelines programmatically.
Documentation
Show Skills.md file
Azure Communication CallingServer (Java) - DEPRECATED
⚠️ DEPRECATED: This SDK has been renamed to Call Automation. For new projects, use
azure-communication-callautomationinstead. 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) |
Recommendations
Explore other random skills
autobrowse
Self-improving browser automation via the auto-research loop. Iteratively runs a browsing task, reads the trace, and improves the navigation skill (strategy.md) until it reliably passes. Supports parallel runs across multiple tasks using sub-agents. Use when you want to build or improve browser automation skills for specific website tasks.
browser-to-api
Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover/extract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR/fetch surface for client integration.
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.