Merge pull request #229277 from boris-bazilevskiy/doc-update-0223

ACS PSTN Quickstart: Direct Routing config & Domain Ownership Validation

Author: American-Dipper

articles/communication-services/concepts/telephony/direct-routing-provisioning.md

@@ -2,11 +2,11 @@
 title: Use direct routing to connect existing telephony service
 description: Learn how to add a Session Border Controller and configure voice routing for Azure Communication Services direct routing.
 author: boris-bazilevskiy
-manager: nmurav
+manager: rcole
 services: azure-communication-services
 
 ms.author: bobazile
-ms.date: 05/26/2022
+ms.date: 03/11/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: pstn
@@ -23,34 +23,25 @@ For information about whether Azure Communication Services direct routing is the
 
 ## Connect the SBC with Azure Communication Services
 
-### Configure using Azure portal 
-1. In the left navigation, select Direct routing under Voice Calling - PSTN and then select Configure from the Session Border Controller tab.
+### Validate domain ownership
+Follow [these instructions](../../how-tos/telephony/domain-validation.md) to validate a domain ownership of your SBC
 
-2. Enter a fully qualified domain name and signaling port for the SBC.
-    - SBC certificate must match the name; wildcard certificates are supported.
-    - The *.onmicrosoft.com domain can’t be used for the FQDN of the SBC.
-
-    For the full list of requirements, refer to [Azure direct routing infrastructure requirements](./direct-routing-infrastructure.md).
-
-   :::image type="content" source="../media/direct-routing-provisioning/add-session-border-controller.png" alt-text="Screenshot of Adding Session Border Controller.":::
-
-3. When you're done, select Next.
-
-    If everything is set up correctly, you should see an exchange of OPTIONS messages between Microsoft and your Session Border Controller. Use your SBC monitoring/logs to validate the connection.
+## Configure outbound voice routing 
+Refer to [Voice routing quickstart](../../quickstarts/telephony/voice-routing-sdk-config.md) to add an SBC and configure outbound voice routing rules.
 
 ## Outbound voice routing considerations
 
 Azure Communication Services direct routing has a routing mechanism that allows a call to be sent to a specific SBC based on the called number pattern.
 
-When you add a direct routing configuration to a resource, all calls made from this resource’s instances (identities) will try a direct routing trunk first. The routing is based on a dialed number and a match in voice routes configured for the resource. 
+When you add a direct routing configuration to a resource, all calls made from this resource’s instances (identities) try a direct routing trunk first. The routing is based on a dialed number and a match in voice routes configured for the resource. 
 
 - If there's a match, the call goes through the direct routing trunk. 
 - If there's no match, the next step is to process the `alternateCallerId` parameter of the `callAgent.startCall` method. 
 - If the resource is enabled for Voice Calling (PSTN) and has at least one number purchased from Microsoft, the `alternateCallerId` is checked. 
 - If the `alternateCallerId` matches a purchased number for the resource, the call is routed through the Voice Calling (PSTN) using Microsoft infrastructure. 
-- If `alternateCallerId` parameter doesn't match any of the purchased numbers, the call will fail. 
+- If `alternateCallerId` parameter doesn't match any of the purchased numbers, the call fails. 
 
-The diagram below demonstrates the Azure Communication Services voice routing logic.
+The diagram demonstrates the Azure Communication Services voice routing logic.
 
 :::image type="content" source="../media/direct-routing-provisioning/voice-routing-diagram.png" alt-text="Diagram of outgoing voice routing flowchart.":::
 
@@ -64,56 +55,20 @@ The following examples display voice routing in a call flow.
 If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, then when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If neither SBC is available, the call is dropped.
 
 ### Two routes example:
-If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 and sbc2 are unavailable, the route with lower priority will be tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of the second route are available, the call is dropped.
+If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 and sbc2 are unavailable, the route with lower priority is tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of the second route are available, the call is dropped.
 
 ### Three routes example:
-If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`, and created a third route with `^+1(\d[10])$` with `sbc5.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 nor sbc2 are unavailable, the route with lower priority will be tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of a second route are available, the third route will be tried. If sbc5 is also not available, the call is dropped. Also, if a user dials `+1 321 XXX XX XX`, the call goes to `sbc5.contoso.biz`, and it isn't available, the call is dropped.
+If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`, and created a third route with `^+1(\d[10])$` with `sbc5.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 nor sbc2 are unavailable, the route with lower priority is tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of a second route are available, the third route is tried. If sbc5 is also not available, the call is dropped. Also, if a user dials `+1 321 XXX XX XX`, the call goes to `sbc5.contoso.biz`, and it isn't available, the call is dropped.
 
 > [!NOTE]
 > Failover to the next SBC in voice routing works only for response codes 408, 503, and 504.
 
 > [!NOTE]
 > In all the examples, if the dialed number does not match the pattern, the call will be dropped unless there is a purchased number exist for the communication resource, and this number was used as `alternateCallerId` in the application. 
 
-## Configure outbound voice routing 
-
-### Configure using Azure portal
-
-:::image type="content" source="../media/direct-routing-provisioning/voice-routing-configuration.png" alt-text="Screenshot of outgoing voice routing configuration.":::
-
-Give your voice route a name, specify the number pattern using regular expressions, and select SBC for that pattern. 
-Here are some examples of basic regular expressions:
-- `^\+\d+$` - matches a telephone number with one or more digits that start with a plus
-- `^\+1(\d{10})$` - matches a telephone number with a ten digits after a `+1`
-- `^\+1(425|206)(\d{7})$` - matches a telephone number that starts with `+1425` or with `+1206` followed by seven digits
-- `^\+0?1234$` - matches both `+01234` and `+1234` telephone numbers.
-
-For more information about regular expressions, see [.NET regular expressions overview](/dotnet/standard/base-types/regular-expressions).
-
-You can select multiple SBCs for a single pattern. In such a case, the routing algorithm will choose them in random order. You may also specify the exact number pattern more than once. The higher row will have higher priority, and if all SBCs associated with that row aren't available next row will be selected. This way, you create complex routing scenarios.
-
 ## Managing inbound calls
-
-For general inbound call management use [Call Automation SDKs](../call-automation/incoming-call-notification.md) to build an application that listen for and manage inbound calls placed to a phone number or received via ACS direct routing. 
-Omnichannel for Customer Service customers please refer to [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling).
-
-## Delete direct routing configuration
-
-### Delete using Azure portal
-
-#### To delete a voice route:
-1. In the left navigation, go to Direct routing under Voice Calling - PSTN and then select the Voice Routes tab.
-1. Select route or routes you want to delete using a checkbox.
-1. Select Remove.
-
-#### To delete an SBC:
-1. In the left navigation, go to Direct routing under Voice Calling - PSTN.
-1. On a Session Border Controllers tab, select Configure.
-1. Clear the FQDN and port fields for the SBC that you want to remove, select Next.
-1. On a Voice Routes tab, review voice routing configuration, make changes if needed. select Save.
-
-> [!NOTE]
-> When you remove SBC associated with a voice route, you can choose a different SBC for the route on the Voice Routes tab. The voice route without an SBC will be deleted.
+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. 
+Omnichannel for Customer Service customers, refer to [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling).
 
 ## Next steps
 

articles/communication-services/how-tos/telephony/domain-validation.md

@@ -0,0 +1,73 @@
+---
+title: Azure Communication Services direct routing domain validation
+description: A how-to page about domain validation for direct routing.
+services: azure-communication-services
+author: boris-bazilevskiy
+
+ms.service: azure-communication-services
+ms.subservice: pstn
+ms.date: 03/11/2023
+ms.topic: how-to
+ms.custom: include file
+ms.author: nikuklic
+---
+
+# Domain validation
+
+This page describes the process of domain name ownership validation. 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, while `contoso.com` would be a domain name. If there's an SBC with FQDN of `acs.sbc1.testing.contoso.com`, `acs` would be a host name, and `sbc1.testing.contoso.com` would be a domain name. To use direct routing, you need to validate that you own a domain part of your FQDN.
+
+Azure Communication Services direct routing configuration consists of the following steps:
+
+- Verify domain ownership for your SBC FQDN
+- Configure SBC FQDN and port number
+- Create voice routing rules
+
+## Domain ownership validation
+
+Make sure to add and verify domain name portion of the FQDN and 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. If using a subdomain, make sure this subdomain is also added and verified. For example, if you want to use `sbc.acs.contoso.com`, then `acs.contoso.com` needs to be registered.
+
+### Domain verification using Azure portal
+
+#### Add new domain name
+
+1. Open Azure portal and navigate to your [Communication Service resource](../../quickstarts/create-communication-resource.md).
+1. In the left navigation pane, select Direct routing under Voice Calling - PSTN.
+1. Select Connect domain from the Domains tab.
+1. Enter the domain part of SBC’s fully qualified domain name.
+1. Reenter the domain name.
+1. Select Confirm and then select Add.
+
+[ ![Screenshot of adding a custom domain.](./media/direct-routing-add-domain.png)](./media/direct-routing-add-domain.png#lightbox)
+
+#### Verify domain ownership
+
+1. Select Verify next to new domain that is now visible in Domain’s list.
+1. Azure portal generates a value for a TXT record, you need to add that record to
+
+[ ![Screenshot of verifying a custom domain.](./media/direct-routing-verify-domain-2.png)](./media/direct-routing-verify-domain-2.png#lightbox)
+
+>[!Note] 
+>It might take up to 30 minutes for new DNS record to propagate on the Internet
+
+3. Select Next. If everything is set up correctly, you should see Domain status changed to *Verified* next to the added domain.
+
+[ ![Screenshot of a verified domain.](./media/direct-routing-domain-verified.png)](./media/direct-routing-domain-verified.png#lightbox)
+
+#### Remove domain from Azure Communication Services
+
+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*.
+
+[ ![Screenshot of removing a custom domain.](./media/direct-routing-remove-domain.png)](./media/direct-routing-remove-domain.png#lightbox)
+
+## Next steps:
+
+### Conceptual documentation
+
+- [Telephony in Azure Communication Services](../../concepts/telephony/telephony-concept.md)
+- [Direct routing infrastructure requirements](../../concepts/telephony/direct-routing-infrastructure.md)
+- [Pricing](../../concepts/pricing.md)
+
+### Quickstarts
+
+- [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)
+- [Redirect inbound telephony calls with Call Automation](../../quickstarts/call-automation/redirect-inbound-telephony-calls.md)

articles/communication-services/how-tos/telephony/media/direct-routing-add-domain.png

@@ -5,7 +5,8 @@
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - [Java Development Kit (JDK)](/java/azure/jdk/?preserve-view=true&view=azure-java-stable) version 8 or above.
-- [Apache Maven](https://maven.apache.org/download.cgi).- A deployed Communication Services resource and connection string. [Create a Communication Services resource](../../create-communication-resource.md).
+- [Apache Maven](https://maven.apache.org/download.cgi).
+- A deployed Communication Services resource and connection string. [Create a Communication Services resource](../../create-communication-resource.md).
 
 ## Setting Up