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
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/telephony/domain-validation.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,17 +14,17 @@ ms.author: nikuklic
14
14
15
15
# Validate a domain for direct routing
16
16
17
-
This article describes the process of validating domain name ownership. A fully qualified domain name (FQDN) consists of two parts: host name and domain name. For example, if your session border controller (SBC) name is `sbc1.contoso.com`, then `sbc1` would be a host name and `contoso.com` would be a domain name. If there's an SBC with FQDN of `acs.sbc1.testing.contoso.com`, `acs` is a host name and `sbc1.testing.contoso.com` is a domain name. To use direct routing, you need to validate that you own the domain part of your FQDN.
17
+
This article describes the process of validating domain name ownership by using the Azure portal.
18
18
19
-
To configure direct routing configuration in Azure Communication Services, you first verify domain ownership for your SBC FQDN. You then configure the SBC FQDN and port number and create voice routing rules.
19
+
A fully qualified domain name (FQDN) consists of two parts: host name and domain name. For example, if your session border controller (SBC) name is `sbc1.contoso.com`, then `sbc1` is the host name and `contoso.com` is the domain name. If an SBC has an FQDN of `acs.sbc1.testing.contoso.com`, then `acs` is the host name and `sbc1.testing.contoso.com` is the domain name.
20
20
21
-
## Validate domain ownership by using the Azure portal
21
+
To use direct routing in Azure Communication Services, you need to validate that you own the domain part of your SBC FQDN. After that, you can configure the SBC FQDN and port number and then create voice routing rules.
22
22
23
-
When you're verifying the domain name portion of the FQDN, keep in mind that the `*.onmicrosoft.com` and `*.azure.com` domain names aren't supported for the SBC FQDN domain name. For example, if you have two domain names, `contoso.com` and `contoso.onmicrosoft.com`, use `sbc.contoso.com` as the SBC name.
23
+
When you're verifying the domain name portion of the SBC FQDN, keep in mind that the `*.onmicrosoft.com` and `*.azure.com` domain names aren't supported. For example, if you have two domain names, `contoso.com` and `contoso.onmicrosoft.com`, use `sbc.contoso.com` as the SBC name.
24
24
25
25
If you're using a subdomain, make sure that this subdomain is also added and verified. For example, if you want to use `sbc.acs.contoso.com`, you need to register `acs.contoso.com`.
26
26
27
-
###Add a new domain name
27
+
## Add a new domain name
28
28
29
29
1. Open the Azure portal and go to your [Communication Services resource](../../quickstarts/create-communication-resource.md).
30
30
1. On the left pane, under **Voice Calling - PSTN**, select **Direct routing**.
@@ -35,23 +35,23 @@ If you're using a subdomain, make sure that this subdomain is also added and ver
35
35
36
36
[](./media/direct-routing-add-domain.png#lightbox)
37
37
38
-
###Verify domain ownership
38
+
## Verify domain ownership
39
39
40
-
1.Select Verify next to new domain that is now visible in Domain’s list.
41
-
1. Azure portal generates a value for a TXT record, you need to add that record to
40
+
1.On the **Domains** tab, select **Verify** next to the new domain that you created.
41
+
1.The Azure portal generates a value for a TXT record. Add that record to
42
42
43
43
[](./media/direct-routing-verify-domain-2.png#lightbox)
44
44
45
-
>[!NOTE]
46
-
>It might take up to 30 minutes for new DNS record to propagate on the Internet
45
+
>[!NOTE]
46
+
>It might take up to 30 minutes for a new DNS record to propagate on the internet.
47
47
48
-
1. Select Next. If everything is set up correctly, you should see Domain status changed to *Verified* next to the added domain.
48
+
1. Select **Next**. If you set up everything correctly, **Domain status** should change to **Verified** next to the added domain.
49
49
50
50
[](./media/direct-routing-domain-verified.png#lightbox)
51
51
52
-
###Remove a domain from Azure Communication Services
52
+
## Remove a domain from Azure Communication Services
53
53
54
-
If you want to remove a domain from your Azure Communication Services direct routing configuration, select the checkbox fir a corresponding domain name, and select *Remove*.
54
+
If you want to remove a domain from your Azure Communication Services direct routing configuration, select the checkbox for a corresponding domain name, and then select **Remove**.
55
55
56
56
[](./media/direct-routing-remove-domain.png#lightbox)
0 commit comments