You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Communication Services capabilities are conceptually organized into discrete areas based on their functional area. Most areas have fully open-source SDKs programmed against published REST APIs that you can use directly over the Internet. The Calling SDK uses proprietary network interfaces and is closed-source.
17
17
18
-
In the tables below we summarize these areas and availability of REST APIs and SDK libraries. We note if APIs and SDKs are intended for end-user clients or trusted service environments. APIs such as SMS shouldn't be directly accessed by end-user devices in low trust environments.
18
+
In the following tables we summarize these areas and availability of REST APIs and SDK libraries. We note whether APIs and SDKs are intended for end-user clients or trusted service environments. You shouldn't directly access APIs such as SMS using end-user devices in low trust environments.
19
19
20
-
Development of Calling and Chat applications can be accelerated by the[Azure Communication Services UI library](./ui-library/ui-library-overview.md). The customizable UI library provides open-source UI components for Web and mobile apps, and a Microsoft Teams theme.
20
+
You can accelerate development of Calling and Chat applications using the [Azure Communication Services UI library](./ui-library/ui-library-overview.md). The customizable UI library provides open-source UI components for Web and mobile apps, and a Microsoft Teams theme.
21
21
22
22
## Creating a practice to use the latest SDK
23
-
Browsers and operating systems are constantly evolving to support the latest enhancements and to fix existing bugs. Using the most recent Azure Communication Services SDK can help you achieve the best overall end user experience for your application when used with updated browsers and operating system updates. The most update Azure Communication Services SDK offers many benefits, such as better performance, security, compatibility, quality, and usability. Updating allows you to access the newest features and updates that are regularly added to the browser and operating system. Azure Communication Services SDKs are updated frequently (approximately every 6 weeks to once a quarter). It's advised that you create a process to ensure that you're always updating to the most recent SDKs.
23
+
24
+
Browsers and operating systems are constantly evolving to support the latest enhancements and to fix existing bugs. Using the most recent Azure Communication Services SDK can help you achieve the best overall end user experience for your application when used with updated browsers and operating system updates. The most update Azure Communication Services SDK offers many benefits, such as better performance, security, compatibility, quality, and usability. Updating allows you to access the newest features and updates that are regularly added to the browser and operating system. Azure Communication Services SDKs are updated frequently (approximately every six weeks to once a quarter). We recommend creating a process to ensure that you're always updating to the most recent SDKs.
| Phone numbers|[REST](/rest/api/communication/phonenumbers)| Service| Acquire and manage phone numbers |
33
-
| SMS |[REST](/rest/api/communication/sms)| Service| Send and receive SMS messages|
34
-
| Email |[REST](/rest/api/communication/Email)| Service|Send and get status on Email messages|
35
-
| Chat |[REST](/rest/api/communication/) with proprietary signaling | Client & Service | Add real-time text chat to your applications |
36
-
| Calling | Proprietary transport | Client | Voice, video, screen-sharing, and other real-time communication |
37
-
| Call Automation |[REST](/rest/api/communication/callautomation/call-connection)| Service | Build customized calling workflows for PSTN and VoIP calls |
38
-
| Job Router |[REST](/rest/api/communication/jobrouter/job-router-operations)| Service | Optimize the management of customer interactions across various applications |
39
-
| Rooms |[REST](/rest/api/communication/rooms/operation-groups)| Service| Create and manage structured communication rooms|
40
-
| UI Library | N/A | Client | Production-ready UI components for chat and calling apps |
41
-
| Advanced Messaging |[REST](/rest/api/communication/advancedmessaging/operation-groups)| Service | Send and receive WhatsApp Business messages |
30
+
| Azure Resource Manager |[REST](/rest/api/communication/resourcemanager/communication-services)| Service| Provision and manage Communication Services resources. |
31
+
| Common | N/A | Client & Service | Provides base types for other SDKs.|
32
+
| Identity |[REST](/rest/api/communication/identity/communication-identity)| Service| Manage users and access tokens. |
33
+
| Phone numbers|[REST](/rest/api/communication/phonenumbers/phone-numbers)| Service| Acquire and manage phone numbers.|
34
+
| SMS |[REST](/rest/api/communication/sms/sms)| Service| Send and receive SMS messages. |
35
+
| Email |[REST](/rest/api/communication/email/email)| Service|Send and get status on Email messages. |
36
+
| Chat |[REST](/rest/api/communication/chat/operation-groups) with proprietary signaling | Client & Service | Add real-time text chat to your applications.|
37
+
| Calling | Proprietary transport | Client | Voice, video, screen-sharing, and other real-time communication.|
38
+
| Call Automation |[REST](/rest/api/communication/callautomation/operation-groups)| Service | Build customized calling workflows for PSTN and VoIP calls.|
39
+
| Job Router |[REST](/rest/api/communication/jobrouter/operation-groups)| Service | Optimize the management of customer interactions across various applications.|
40
+
| Rooms |[REST](/rest/api/communication/rooms/operation-groups)| Service| Create and manage structured communication rooms.|
41
+
| UI Library | N/A | Client | Production-ready UI components for chat and calling apps.|
42
+
| Advanced Messaging |[REST](/rest/api/communication/advancedmessaging/operation-groups)| Service | Send and receive WhatsApp Business messages.|
42
43
43
44
### Languages and publishing locations
44
45
@@ -73,14 +74,14 @@ Publishing locations for individual SDK packages:
73
74
74
75
The Android ecosystem is extensive, encompassing various versions and specialized platforms designed for diverse types of devices. The next table lists the Android platforms currently supported:
| Phones and tablets | Standard devices running [Android Commercial](https://developer.android.com/get-started). | Fully support with [the video resolution](./voice-video-calling/calling-sdk-features.md?#supported-video-resolutions).|
77
+
| Devices | Description | Support |
78
+
| ---| ---|--- |
79
+
| Phones and tablets | Standard devices running [Android Commercial](https://developer.android.com/get-started). | Fully support with [the video resolution](./voice-video-calling/calling-sdk-features.md#supported-video-resolutions). |
79
80
80
81
> [!NOTE]
81
-
> We **only support video calls on phones and tablets**. For use cases involving video on non-standard devices or platforms (such as smart glasses or custom devices), we suggest [contacting us](https://github.com/Azure/communication) early in your development process to help determine the most suitable integration approach.
82
+
> We **only support video calls on phones and tablets**. For use cases involving video on nonstandard devices or platforms (such as smart glasses or custom devices), we suggest [contacting us](https://github.com/Azure/communication) early in your development process to help determine the most suitable integration approach.
82
83
83
-
In case that you found issues during your implementation we encourage you to visit [the troubleshooting guide](./troubleshooting-info.md?#access-support-files-in-the-calling-sdk).
84
+
If you found issues during your implementation, see [the troubleshooting guide](./troubleshooting-info.md#access-support-files-in-the-calling-sdk).
84
85
85
86
#### iOS Calling SDK support
86
87
@@ -119,22 +120,22 @@ All other Communication Services packages target .NET Standard 2.0, which suppor
If you want to improve your app, we suggest read[the Best Practices article](./best-practices.md). It provides recommendations and a checklist to review before releasing your app.
129
+
If you want to improve your app, see[the Best Practices article](./best-practices.md). It provides recommendations and a checklist to review before releasing your app.
129
130
130
131
## REST APIs
131
132
132
-
Communication Services APIs are documented alongside other [Azure REST APIs](/rest/api/azure/). This documentation tells you how to structure your HTTP messages and offers guidance for using [Postman](../tutorials/postman-tutorial.md). REST interface documentation is also published in Swagger format on [GitHub](https://github.com/Azure/azure-rest-api-specs). You can find throttling limits for individual APIs on[service limits page](./service-limits.md).
133
+
Communication Services APIs are documented with other [Azure REST APIs](/rest/api/azure/). This documentation describes how to structure your HTTP messages and offers guidance for using [Postman](../tutorials/postman-tutorial.md). REST interface documentation is also published in OpenAPI format on [GitHub](https://github.com/Azure/azure-rest-api-specs). You can find throttling limits for individual APIs in[service limits](./service-limits.md).
133
134
134
135
## API stability expectations
135
136
136
137
> [!IMPORTANT]
137
-
> This section provides guidance on REST APIs and SDKs marked **stable**. APIs marked pre-release, preview, or beta may be changed or deprecated **without notice**.
138
+
> This section provides guidance on REST APIs and SDKs marked **stable**. APIs marked prerelease, preview, or beta may be changed or deprecated **without notice**.
138
139
139
140
In the future we may retire versions of the Communication Services SDKs, and we may introduce breaking changes to our REST APIs and released SDKs. Azure Communication Services *generally* follows two supportability policies for retiring service versions:
titleSuffix: An Azure Communication Services concept document
5
+
description: Learn about Communication Services CNAM registration process.
6
+
author: henikaraa
7
+
manager: ankura
8
+
services: azure-communication-services
9
+
ms.author: henikaraa
10
+
ms.date: 02/13/2025
11
+
ms.topic: conceptual
12
+
ms.service: azure-communication-services
13
+
---
14
+
15
+
# Define your caller identity
16
+
17
+
A common challenge faced by businesses is the difficulty of getting their calls answered or even noticed by customers. In many cases, potential customers ignore or block calls from unknown or unfamiliar numbers.
18
+
19
+
Using an unidentified number can lead to missed opportunities for sales, customer service, and other important interactions. This problem can be especially challenging for businesses that rely heavily on phone-based communication, such as call centers or sales teams.
20
+
21
+
To address these challenges, Azure Communications Services offers customers the ability to define their caller's name when they place a public switched telephone network (PSTN) call and proposes a new Caller Name Delivery (CNAM) registration process. To avoid their customer calling numbers being flagged as spam, customers should register their PSTN outbound numbers with central registries and to follow best practices described in this article.
22
+
23
+
## What is Caller Name Delivery (CNAM)
24
+
25
+
In the US, Caller Name Delivery (CNAM) provides the caller's name or company name in Caller ID, though it can also show as \"restricted\" or \"not available\" due to blocking or technical issues. The terminating carrier retrieves this information through a database lookup (up to eight
26
+
providers in the US) using the caller\'s phone number. In Canada, you can add the caller's name using either the client\'s equipment (such as PBX) or the originating carrier, as long as it complies with anti-spoofing and fraud regulations.
27
+
28
+
29
+
30
+
## How to register
31
+
32
+
To request a CNAM registration for an Azure Communication Services number, customers need to send an email to `<[email protected]>`, using `"ACS Number Request -- CNAM Registration"` as part of subject line. In the body or the email, provide the following details:
33
+
34
+
- Customer and Azure account details.
35
+
36
+
- List a number and the corresponding caller name to register for each number. The customer must own these numbers under the Azure Resource provided. Customer can register only **US local numbers**.
37
+
38
+
CNAM caller names are limited to 15 characters (including spaces) and support the following special characters:
39
+
40
+
| Special character | Name |
41
+
| --- |:--- |
42
+
|**.**| period |
43
+
|**,**| comma |
44
+
|**&**| ampersand |
45
+
|**-**| dash |
46
+
|**_**| underscore |
47
+
|**'**| single quote (as in Tom's Burgers) |
48
+
49
+
Once the request is approved by the carrier, it takes **48 hours to be published.**
50
+
51
+
## Things to consider
52
+
53
+
- The reliability of CNAM delivery with the call varies depending on the country/region and carriers that handle the call; either as an intermediary or a terminating carrier.
54
+
- Inconsistencies in CNAM can be caused when the intermediate or terminating carriers delay refreshing the CNAM information in authoritative databases, such as in the United States. In countries/regions where there are no authoritative databases for CNAM, individual carrier practices can also cause problems with CNAM information arriving intact with the call.
55
+
- Azure Communication Services currently doesn't support CNAM registration for countries or regions outside the United States.
56
+
- This registration is available only for US local numbers. It doesn't support toll free numbers.
57
+
- This service only applies to *outbound* calls for numbers that customer owns.
58
+
- CNAM databases aren't always up to date and not consistently updated. There's a potential for misspellings.
59
+
- There are multiple CNAM databases across the country and terminating carriers may subscribe to one or more databases.
0 commit comments