Skip to content

Commit 602232f

Browse files
authored
Update and rename How to Manage Your Calling Identity.md to how-to-manage-your-calling-identity.md
updated file name and doc structure
1 parent f9e7837 commit 602232f

File tree

1 file changed

+9
-15
lines changed

1 file changed

+9
-15
lines changed

articles/communication-services/concepts/telephony/How to Manage Your Calling Identity.md renamed to articles/communication-services/concepts/telephony/how-to-manage-your-calling-identity.md

Lines changed: 9 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ providers in the US) using the caller\'s phone number. In Canada, you can add th
2727

2828
![A call flow diagram showing your call registered with a Caller Name Delivery (CNAM) from Azure Communication Services through an originating service provider and terminating service provider to the called device displaying your CNAM.](../media/cnam-call-flow.png)
2929

30-
### How to register
30+
## How to register
3131

3232
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:
3333

@@ -48,18 +48,12 @@ CNAM caller names are limited to 15 characters (including spaces) and support th
4848

4949
Once the request is approved by the carrier, it takes **48 hours to be published.**
5050

51-
### Things to consider
51+
## Things to consider
5252

53-
1. 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-
55-
2. 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.
56-
57-
3. Azure Communication Services currently doesn't support CNAM registration for countries or regions outside the United States.
58-
59-
4. This registration is available only for US local numbers. It doesn't support toll free numbers.
60-
61-
5. This service only applies to *outbound* calls for numbers that customer owns.
62-
63-
6. CNAM databases aren't always up to date and not consistently updated. There's a potential for misspellings.
64-
65-
7. There are multiple CNAM databases across the country and terminating carriers may subscribe to one or more databases.
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

Comments
 (0)