Azure / Azure/azure-rest-api-specs
[Azure Communication Services - Server Calling] API Review
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
**Service Name**: Azure Communication Services - Server Calling
**Review Created By**: Jorge Garcia Hirota
**PR**:
**Description**: Champion scenarios that briefly explain how developers will use your API:
Katie calls Alaska Airlines
Alaska Airlines answers Katie’s call and plays an IVR
Katie selects English from first options and selects booking through a representative as her second option
Katie is put on hold and Alaska Airlines plays music while a suitable representative is found
Katie is transferred to an appropriate representative
**Hero Scenarios Link**: Not Provided
**Core Concepts Doc Link**: [here](https://github.com/richardcho-msft/azure-rest-api-specs/blob/dev-communication-CallingServer-2022-04-07-preview/specification/communication/data-plane/CallingServer/preview/2022-04-07-preview/communicationservicescallingserver.json)
Detailed meeting information and documents provided can be accessed [here](https://web.powerapps.com/apps/e41c69de-ef96-44ba-b287-0e012e7c13ae?view=edit&event=32a98fad-d22e-ed11-9db1-0022480abd5f)
Contributor guide
Research direction
Start with the linked communicationservicescallingserver.json specification and compare its API surface with the listed Alaska Airlines calling scenario. Use the linked meeting information and documents for review context; done means completing the API review for those scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100