Azure Communication Call Automation client library for Python
This package contains a Python SDK for Azure Communication Call Automation. Call Automation provides developers the ability to build server-based, intelligent call workflows, and call recording for voice and PSTN channels.
Overview of Call Automation | Product documentation
Disclaimer
Azure SDK Python packages support for Python 2.7 has ended 01 January 2022. For more information and questions, please refer to https://github.com/Azure/azure-sdk-for-python/issues/20691
Getting started
Prerequisites
- Python 3.8 or later is required to use this package.
- You need an Azure subscription to use this package.
- A deployed Communication Services resource. You can use the Azure Portal or the Azure PowerShell to set it up.
Installing
Install the Azure Communication Service Call Automation SDK.
pip install azure-communication-callautomation
Key concepts
| Name | Description |
|---|---|
| CallAutomationClient | CallAutomationClient is the primary interface for developers using this client library. It can be used to initiate calls by createCall or answerCall. It can also be used to do recording actions such as startRecording |
| CallConnectionClient | CallConnectionClient represents a ongoing call. Once the call is established with createCall or answerCall, further actions can be performed for the call, such as transfer or play_media. |
| Callback Events | Callback events are events sent back during duration of the call. It gives information and state of the call, such as CallConnected. CallbackUrl must be provided during createCall and answerCall, and callback events will be sent to this url. |
| Incoming Call Event | When incoming call happens (that can be answered with answerCall), incoming call eventgrid event will be sent. This is different from Callback events above, and should be setup on Azure portal. See Incoming Call for detail. |
Examples
Initialize CallAutomationClient
from azure.identity import DefaultAzureCredential
from azure.communication.callautomation import (CallAutomationClient)
# Your unique Azure Communication service endpoint
endpoint_url = '<ENDPOINT>'
credential = DefaultAzureCredential()
client = CallAutomationClient(endpoint_url, credential)
Create Call
from azure.communication.callautomation import (
CallAutomationClient,
CommunicationUserIdentifier
)
# target endpoint for ACS User
user = CommunicationUserIdentifier("8:acs:...")
# callback url to receive callback events
callback_url = "https://<MY-EVENT-HANDLER-URL>/events"
# send out the invitation, creating call
result = client.create_call(
target_participant=user,
callback_url=callback_url
)
# this id can be used to do further actions in the call
call_connection_id = result.call_connection_id
Play Media
# using call connection id, get call connection
call_connection = client.get_call_connection(call_connection_id)
# from callconnection of result above, play media to all participants
my_file = FileSource(url="https://<FILE-SOURCE>/<SOME-FILE>.wav")
call_connection.play_to_all(my_file)
Troubleshooting
Next steps
- Call Automation Overview
- Incoming Call Concept
- Build a customer interaction workflow using Call Automation
- Redirect inbound telephony calls with Call Automation
- Quickstart: Play action
- Quickstart: Recognize action
- Read more about Call Recording in Azure Communication Services
- Record and download calls with Event Grid
Provide Feedback
If you encounter any bugs or have suggestions, please file an issue in the Issues section of the project
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the [Microsoft Open Source Code of Conduct][code_of_conduct]. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Metadata
Release files for azure-communication-callautomation 1.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| azure_communication_callautomation-1.6.0.tar.gz | 157.9 kB | Without provenance | Details for azure_communication_callautomation-1.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| azure_communication_callautomation-1.6.0-py3-none-any.whl | Python 3 | none | any | Details for azure_communication_callautomation-1.6.0-py3-none-any.whl |
Total release size: 306.9 kB
Release files / azure_communication_callautomation-1.6.0.tar.gz
| Download URL | azure_communication_callautomation-1.6.0.tar.gz |
|---|---|
| Size | 157.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f35e376931a767aecb0ab64247a1d36e770e3627372fda2762184a9ca2ca0aa3
|
|
BLAKE2b-256 checksum How to use checksums |
eb472a57f7824b890d121f0dbfa686035e68eff1e496f95a78a2c581cfc84fcb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Release files / azure_communication_callautomation-1.6.0-py3-none-any.whl
| Download URL | azure_communication_callautomation-1.6.0-py3-none-any.whl |
|---|---|
| Size | 149.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30be12903438768087032a4a7603278d22fb7d6537a20826a66b1a09c51fee6b
|
|
BLAKE2b-256 checksum How to use checksums |
f828989f609cb8d4f0cfad3737c215b7758b7e0985839584827ec188ac19736f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Security for azure-communication-callautomation 1.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.