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/concepts/telephony/direct-routing-provisioning.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added
68
68
69
69
## Managing inbound calls
70
70
For general inbound call management use [Call Automation SDKs](../call-automation/incoming-call-notification.md) to build an application that listens for and manage inbound calls placed to a phone number or received via ACS direct routing.
71
-
Omnichannel for Customer Service customers refer to [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling).
71
+
Omnichannel for Customer Service customers, refer to [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling).
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/telephony/domain-validation.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,9 @@ This page describes the process of domain name ownership validation. Fully Quali
18
18
19
19
Azure Communication Services direct routing configuration consists of the following steps:
20
20
21
-
1. Verify domain ownership for your SBC FQDN
22
-
1. Configure SBC FQDN and port number
23
-
1. Create voice routing rules
21
+
- Verify domain ownership for your SBC FQDN
22
+
- Configure SBC FQDN and port number
23
+
- Create voice routing rules
24
24
25
25
## Domain ownership validation
26
26
@@ -37,27 +37,27 @@ Make sure to add and verify domain name portion of the FQDN and keep in mind tha
37
37
1. Reenter the domain name.
38
38
1. Select Confirm and then select Add.
39
39
40
-
:::image type="content" source="./media/direct-routing-add-domain.png" alt-text="Screenshot of adding a custom domain.":::
40
+
[](./media/direct-routing-add-domain.png#lightbox)
41
41
42
42
#### Verify domain ownership
43
43
44
44
1. Select Verify next to new domain that is now visible in Domain’s list.
45
-
1. Azure portal generates a value for a TXT record, you need to add that record to your registrars or DNS hosting provider website to set up your domain.
45
+
1. Azure portal generates a value for a TXT record, you need to add that record to
46
46
47
-
:::image type="content" source="./media/direct-routing-verify-domain-2.png" alt-text="Screenshot of verifying a custom domain.":::
47
+
[](./media/direct-routing-verify-domain-2.png#lightbox)
48
48
49
49
>[!Note]
50
50
>It might take up to 30 minutes for new DNS record to propagate on the Internet
51
51
52
52
3. Select Next. If everything is set up correctly, you should see Domain status changed to *Verified* next to the added domain.
53
53
54
-
:::image type="content" source="./media/direct-routing-domain-verified.png" alt-text="Screenshot of a verified domain.":::
54
+
[](./media/direct-routing-domain-verified.png#lightbox)
55
55
56
56
#### Remove domain from Azure Communication Services
57
57
58
58
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*.
59
59
60
-
:::image type="content" source="./media/direct-routing-remove-domain.png" alt-text="Screenshot of removing a custom domain.":::
60
+
[](./media/direct-routing-remove-domain.png#lightbox)
0 commit comments