Merge pull request #213029 from boris-bazilevskiy/docs-update-0922

Docs update 0922

Author: BCS2022

articles/communication-services/concepts/telephony/emergency-calling-concept.md

@@ -62,6 +62,11 @@ Emergency dialing is automatically enabled for all users of the Azure Communicat
 
 The Emergency service is temporarily free to use for Azure Communication Services customers within reasonable use, however, billing for the service will be enabled in 2022. Calls to 911 are capped at 10 concurrent calls per Azure resource.
 
+## Emergency calling with Azure Communication Services direct routing
+
+Emergency call is a regular call from a direct routing perspective. If you want to implement emergency calling with Azure Communication Services direct routing, you need to make sure that there is a routing rule for your emergency number (911, 112, etc.). You also need to make sure that your carrier processes emergency calls properly.
+There is also an option to use purchased number as a caller ID for direct routing calls, in such case if there is no voice routing rule for emergency number, the call will fall back to Microsoft network, and we will treat it as a regular emergency call. Learn more about [voice routing fall back](./direct-routing-provisioning.md#voice-routing-considerations).
+
 ## Next steps
 
 ### Quickstarts

articles/communication-services/concepts/telephony/inbound-calling-capabilities.md

@@ -18,15 +18,15 @@ Inbound PSTN calling is currently supported in GA for Dynamics Omnichannel. You
 
 **Inbound calling with Dynamics 365 Omnichannel (OC)**
 
- Supported in General Availability, to set up inbound calling for Dynamics 365 OC with direct routing or Voice Calling (PSTN) follow [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling)
+Supported in General Availability, to set up inbound calling for Dynamics 365 OC with direct routing or Voice Calling (PSTN) follow [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling)
 
- **Inbound calling with Power Virtual Agents**
+**Inbound calling with Power Virtual Agents**
 
- *Coming soon*
+*Coming soon*
 
-**Inbound calling with ACS Client Calling SDK**
+**Inbound calling with ACS Call Automation SDK**
 
-*Coming soon*
+[Available in private preview](../voice-video-calling/call-automation.md)
 
 **Inbound calling with Azure Bot Framework**
 

articles/communication-services/concepts/telephony/known-limitations-acs-telephony.md

@@ -0,0 +1,49 @@
+---
+title: Azure direct routing known limitations  - Azure Communication Services
+description: Known limitations of direct routing in Azure Communication Services.
+author: boris-bazilevskiy
+manager: rcole
+services: azure-communication-services
+
+ms.author: bobazile
+ms.date: 09/29/2022
+ms.topic: conceptual
+ms.service: azure-communication-services
+ms.subservice: pstn
+---
+
+# Known limitations in Azure telephony
+
+This article provides information about limitations and known issues related to telephony in Azure Communication Services.
+
+## Azure Communication Services direct routing known limitations
+
+- Anonymous calling isn't supported
+    - will be fixed in GA release
+- Different set of Media Processors (MP) is used with different IP addresses. Currently [any Azure IP address](./direct-routing-infrastructure.md#media-traffic-ip-and-port-ranges) can be used for media connection between Azure MP and Session Border Controller (SBC).
+    - will be fixed in GA release
+- Azure Communication Services SBC Fully Qualified Domain Name (FQDN) must be different from Teams Direct Routing SBC FQDN
+- Wildcard SBC certificates require extra workaround. Contact Azure support for details.
+    - will be fixed in GA release
+- Media bypass/optimization isn't supported
+- No indication of SBC connection status/details in Azure portal
+    - will be fixed in GA release
+- Azure Communication Services direct routing isn't available in Government Clouds
+- Multi-tenant trunks aren't supported
+- Location-based routing isn't supported
+- No quality dashboard is available for customers
+- Enhanced 911 isn't supported 
+- PSTN numbers missing from Call Summary logs 
+
+## Next steps
+
+### Conceptual documentation
+
+- [Phone number types in Azure Communication Services](./plan-solution.md)
+- [Plan for Azure direct routing](./direct-routing-infrastructure.md)
+- [Pair the Session Border Controller and configure voice routing](./direct-routing-provisioning.md)
+- [Pricing](../pricing.md)
+
+### Quickstarts
+
+- [Call to Phone](../../quickstarts/telephony/pstn-call.md)

articles/communication-services/toc.yml

@@ -185,6 +185,8 @@ items:
         href: concepts/telephony/certified-session-border-controllers.md
       - name: Inbound telephony calling capabilities
         href: concepts/telephony/inbound-calling-capabilities.md
+      - name: Known limitations
+        href: concepts/telephony/known-limitations-acs-telephony.md
   - name: SMS
     items:
       - name: SMS SDK overview