Merge pull request #268483 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 3/8

Author: ttorble

articles/ai-services/speech-service/includes/language-support/multilingual-voices.md

@@ -17,4 +17,4 @@ ms.author: v-baolianzou
 
 <sup>2</sup> The neural voice is a multilingual voice in Azure AI Speech. All multilingual voices (except `en-US-JennyMultilingualNeural`) can speak in the language in default locale of the input text without [using SSML](../../speech-synthesis-markup-voice.md#adjust-speaking-languages). However, you can still use the `<lang xml:lang>` element to adjust the speaking accent of each language to set preferred accent such as British accent (`en-GB`) for English. Check the [full list](https://speech.microsoft.com/portal/voicegallery) of supported locales through SSML.
 
-<sup>3</sup> The OpenAI text to speech voices in Azure AI Speech are in public preview and only available in North Central US (`northcentralus`) and Sweden Central (`swedencentral`).
+<sup>3</sup> The OpenAI text to speech voices in Azure AI Speech are in public preview and only available in North Central US (`northcentralus`) and Sweden Central (`swedencentral`). Locales not listed for OpenAI voices aren't supported by design.

articles/app-service/configure-language-java.md

@@ -1086,6 +1086,85 @@ You don't need to incrementally add instances (scaling out), you can add multipl
 
 JBoss EAP is only available on the Premium v3 and Isolated v2 App Service Plan types. Customers that created a JBoss EAP site on a different tier during the public preview should scale up to Premium or Isolated hardware tier to avoid unexpected behavior.
 
+## Tomcat Baseline Configuration On App Services
+
+Java developers can customize the server settings, troubleshoot issues, and deploy applications to Tomcat with confidence if they know about the server.xml file and configuration details of Tomcat. Some of these may be:
+* Customizing Tomcat configuration: By understanding the server.xml file and Tomcat's configuration details, developers can fine-tune the server settings to match the needs of their applications.
+* Debugging: When an application is deployed on a Tomcat server, developers need to know the server configuration to debug any issues that may arise. This includes checking the server logs, examining the configuration files, and identifying any errors that might be occurring.
+* Troubleshooting Tomcat issues: Inevitably, Java developers will encounter issues with their Tomcat server, such as performance problems or configuration errors. By understanding the server.xml file and Tomcat's configuration details, developers can quickly diagnose and troubleshoot these issues, which can save time and effort.
+* Deploying applications to Tomcat: To deploy a Java web application to Tomcat, developers need to know how to configure the server.xml file and other Tomcat settings. Understanding these details is essential for deploying applications successfully and ensuring that they run smoothly on the server.
+
+As you provision an App Service with Tomcat to host your Java workload (a WAR file or a JAR file), there are certain settings that you get out of the box for Tomcat configuration. You can refer to the [Official Apache Tomcat Documentation](https://tomcat.apache.org/) for detailed information, including the default configuration for Tomcat Web Server.
+
+Additionally, there are certain transformations that are further applied on top of the server.xml for Tomcat distribution upon start. These are transformations to the Connector, Host, and Valve settings.
+
+Please note that the latest versions of Tomcat will have these server.xml. (8.5.58 and 9.0.38 onward). Older versions of Tomcat do not use transforms and may have different behavior as a result.
+
+### Connector
+
+```xml 
+<Connector port="${port.http}" address="127.0.0.1" maxHttpHeaderSize="16384" compression="on" URIEncoding="UTF-8" connectionTimeout="${site.connectionTimeout}" maxThreads="${catalina.maxThreads}" maxConnections="${catalina.maxConnections}" protocol="HTTP/1.1" redirectPort="8443"/>
+ ```
+* `maxHttpHeaderSize` is set to `16384`
+* `URIEncoding` is set to `UTF-8`
+* `conectionTimeout` is set to `WEBSITE_TOMCAT_CONNECTION_TIMEOUT`, which defaults to `240000`
+* `maxThreads` is set to `WEBSITE_CATALINA_MAXTHREADS`, which defaults to `200`
+* `maxConnections` is set to `WEBSITE_CATALINA_MAXCONNECTIONS`, which defaults to `10000`
+ 
+> [!NOTE]
+> The connectionTimeout, maxThreads and maxConnections settings can be tuned with app settings
+
+Following are example CLI commands that you may use to alter the values of conectionTimeout, maxThreads, or maxConnections:
+
+```azurecli-interactive
+az webapp config appsettings set --resource-group myResourceGroup --name myApp --settings WEBSITE_TOMCAT_CONNECTION_TIMEOUT=120000
+```
+```azurecli-interactive
+az webapp config appsettings set --resource-group myResourceGroup --name myApp --settings WEBSITE_CATALINA_MAXTHREADS=100
+```
+```azurecli-interactive
+az webapp config appsettings set --resource-group myResourceGroup --name myApp --settings WEBSITE_CATALINA_MAXCONNECTIONS=5000
+```
+* Connector uses the address of the container instead of 127.0.0.1
+ 
+### Host
+
+```xml
+<Host appBase="${site.appbase}" xmlBase="${site.xmlbase}" unpackWARs="${site.unpackwars}" workDir="${site.tempdir}" errorReportValveClass="com.microsoft.azure.appservice.AppServiceErrorReportValve" name="localhost" autoDeploy="true">
+```
+
+* `appBase` is set to `AZURE_SITE_APP_BASE`, which defaults to local `WebappsLocalPath`
+* `xmlBase` is set to `AZURE_SITE_HOME`, which defaults to `/site/wwwroot`
+* `unpackWARs` is set to `AZURE_UNPACK_WARS`, which defaults to `true`
+* `workDir` is set to `JAVA_TMP_DIR`, which defaults `TMP`
+* errorReportValveClass uses our custom error report valve
+ 
+### Valve
+
+```xml
+<Valve prefix="site_access_log.${catalina.instance.name}" pattern="%h %l %u %t &quot;%r&quot; %s %b %D %{x-arr-log-id}i" directory="${site.logdir}/http/RawLogs" maxDays="${site.logRetentionDays}" className="org.apache.catalina.valves.AccessLogValve" suffix=".txt"/>
+ ```
+* `directory` is set to `AZURE_LOGGING_DIR`, which defaults to `home\logFiles`
+* `maxDays` is to `WEBSITE_HTTPLOGGING_RETENTION_DAYS`, which defaults to `0` [forever]
+ 
+On Linux, it has all of the same customization, plus:
+ 
+* Adds some error and reporting pages to the valve:
+ ```xml
+                <xsl:attribute name="appServiceErrorPage">
+                    <xsl:value-of select="'${appService.valves.appServiceErrorPage}'"/>
+                </xsl:attribute>
+ 
+                <xsl:attribute name="showReport">
+                    <xsl:value-of select="'${catalina.valves.showReport}'"/>
+                </xsl:attribute>
+                
+                <xsl:attribute name="showServerInfo">
+                    <xsl:value-of select="'${catalina.valves.showServerInfo}'"/>
+                </xsl:attribute>
+ ```
+
+
 ::: zone-end
 
 ## Next steps

articles/communication-services/concepts/numbers/number-types.md

@@ -14,7 +14,7 @@ ms.service: azure-communication-services
 
 # Number types
 
-Azure Communication Services allows you to use phone numbers to make voice calls and send SMS messages with the public-switched telephone network (PSTN). In this document, we'll review the phone number types, region availability, and use cases for planning your telephony and SMS solution using Communication Services.
+Azure Communication Services allows you to use phone numbers to make voice calls and send SMS messages with the public-switched telephone network (PSTN). In this document, we review the phone number types, region availability, and use cases for planning your telephony and SMS solution using Communication Services.
 
 ## Available options
 
@@ -25,7 +25,7 @@ Azure Communication Services offers three types of Numbers: Toll-Free, Local, an
 - **To send or receive an SMS**, choose a Toll-Free Number or a Short Code
 - **To make or receive phone calls**, choose a Toll-Free Number or a Local Number
 
-The table below summarizes these number types with supported capabilities:
+This table summarizes the number types and supported capabilities:
 
 | Type                                                                  | Example           | Send SMS | Receive SMS | Make Calls | Receive Calls | Typical Use Case                             | Restrictions   |
 | :-------------------------------------------------------------------- | :---------------- | :------: | :---------: | :--------: | :-----------: | :------------------------------------------- | :------------- |
@@ -35,7 +35,8 @@ The table below summarizes these number types with supported capabilities:
 
 ## Next steps
 
-For additional information about getting or managing phone numbers please see the following pages:
+For more information about getting or managing phone numbers, see the following topics:
 
 - Get a [Toll-Free or Local Phone Number](../../quickstarts/telephony/get-phone-number.md)
 - Get a [Short-Code](../../quickstarts/sms/apply-for-short-code.md)
+- [Quickstart: Look up operator information for a phone number](../../quickstarts/telephony/number-lookup.md)

articles/communication-services/concepts/sms/concepts.md

@@ -36,9 +36,9 @@ Key features of Azure Communication Services SMS SDKs include:
 
 ## Sender types supported
 
-Sending SMS to any recipient requires getting a phone number. Choosing the right number type is critical to the success of your messaging campaign. Few of the factors to consider when choosing a number type include destination(s) of the message, throughput requirement of your messaging campaign, and the timeline when you want to start sending messages. Azure Communication Services enables you to send SMS using a variety of sender types - toll-free number (1-8XX), short codes (12345), and alphanumeric sender ID (CONTOSO). The following table walks you through the features of each number type:
+Sending SMS to any recipient requires getting a phone number. Choosing the right number type is critical to the success of your messaging campaign. Some factors to consider when choosing a number type include destination(s) of the message, throughput requirement of your messaging campaign, and the timeline when you want to start sending messages. Azure Communication Services enables you to send SMS using a variety of sender types - toll-free number (1-8XX), short codes (12345), and alphanumeric sender ID (CONTOSO). The following table walks you through the features of each number type:
 
-|Factors              | Toll-Free| Short Code | Dynamic Alphanumeric Sender ID| Pre-registered Alphanumeric Sender ID|
+|Factors              | Toll-Free| Short Code | Dynamic Alphanumeric Sender ID| Preregistered Alphanumeric Sender ID|
 |---------------------|----------|------------|-----------------------|-----------------------|
 |**Description**|Toll free numbers are telephone numbers with distinct three-digit codes that can be used for business to consumer communication without any charge to the consumer| Short codes are 5-6 digit numbers used for business to consumer messaging such as alerts, notifications, and marketing |  Alphanumeric Sender IDs are displayed as a custom alphanumeric phrase like the company’s name (CONTOSO, MyCompany) on the recipient handset. Alphanumeric sender IDs can be used for a variety of use cases like one-time passcodes, marketing alerts, and flight status notifications. Dynamic alphanumeric sender ID is supported in countries that do not require registration for use.| Alphanumeric Sender IDs are displayed as a custom alphanumeric phrase like the company’s name (CONTOSO, MyCompany) on the recipient handset. Alphanumeric sender IDs can be used for a variety of use cases like one-time passcodes, marketing alerts, and flight status notifications. Pre-registered alphanumeric sender ID is supported in countries that require registration for use. |
 |**Format**|+1 (8XX) XYZ PQRS| 12345  | CONTOSO*       |CONTOSO*       |
@@ -56,11 +56,12 @@ Sending SMS to any recipient requires getting a phone number. Choosing the right
 > [!div class="nextstepaction"]
 > [Get started with sending sms](../../quickstarts/sms/send.md)
 
-The following documents might be interesting to you:
+See the following articles for more information:
 
+- [Number lookup overview](../../concepts/numbers/number-lookup-concept.md)
 - Check SMS FAQ for questions regarding [SMS](../sms/sms-faq.md)
 - Familiarize yourself with the [SMS SDK](../sms/sdk-features.md)
 - Get an SMS capable [phone number](../../quickstarts/telephony/get-phone-number.md)
 - Get a [short code](../../quickstarts/sms/apply-for-short-code.md)
-- [Phone number types in Azure Communication Services](../telephony/plan-solution.md)
+- Learn about [Phone number types in Azure Communication Services](../telephony/plan-solution.md)
 - Apply for [Toll-free verification](./sms-faq.md#toll-free-verification)

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

@@ -16,28 +16,28 @@ ms.subservice: pstn
 
 [!INCLUDE [Regional Availability Notice](../../includes/regional-availability-include.md)]
 
-Azure Communication Services Calling SDKs can be used to add telephony and Public Switched Telephone Network access to your applications. This page summarizes key telephony concepts and capabilities. See the [calling library](../../quickstarts/voice-video-calling/getting-started-with-calling.md) to learn more about specific SDK languages and capabilities.
+Azure Communication Services Calling SDKs enable you to add telephony and Public Switched Telephone Network (PSTN) access to your applications. This page summarizes key telephony concepts and capabilities. See the [calling library](../../quickstarts/voice-video-calling/getting-started-with-calling.md) to learn more about specific SDK languages and capabilities.
 
 [!INCLUDE [Survey Request](../../includes/survey-request.md)]
 
-## Overview of telephony
-Whenever your users interact with a traditional telephone number, calls are facilitated by PSTN (Public Switched Telephone Network) voice calling. To make and receive PSTN calls, you need to add telephony capabilities to your Azure Communication Services resource. In this case, signaling and media use a combination of IP-based and PSTN-based technologies to connect your users. Communication Services provides two discrete ways to reach the PSTN network: Voice Calling (PSTN) and Azure direct routing.
+## Telephony overview
+Whenever your users interact with a traditional telephone number, the Public Switched Telephone Network (PSTN) voice calling handles the call. To make and receive PSTN calls, you need to add telephony capabilities to your Azure Communication Services resource. In this case, signaling and media use a combination of IP-based and PSTN-based technologies to connect your users. Communication Services provides two discrete ways to reach the PSTN network: Voice Calling (PSTN) and Azure direct routing.
 
 ### Voice Calling (PSTN)
 
 An easy way of adding PSTN connectivity to your app or service, in such case, Microsoft is your telco provider. You can buy numbers directly from Microsoft. Azure Cloud Calling is an all-in-the-cloud telephony solution for Communication Services. It is the simplest option that connects Communication Services to the Public Switched Telephone Network (PSTN) to enable calls to landlines and mobile phones worldwide. Microsoft acts as your PSTN carrier, as shown in the following diagram:
 
 ![Voice Calling (PSTN) diagram.](../media/telephony-concept/azure-calling-diagram.png)
 
-If you answer ‘yes’ to the following, then Voice Calling (PSTN) is the right solution for you:
+If you answer **yes** to the following questions, then Voice Calling (PSTN) is the right solution for you:
 - Voice Calling (PSTN) is available in your region.
-- You do not need to retain your current PSTN carrier.
+- You don't need to retain your current PSTN carrier.
 - You want to use Microsoft-managed access to the PSTN.
 
 With this option:
 - You get numbers directly from Microsoft and can call phones around the world.
-- You do not require deployment or maintenance of an on-premises deployment—because Voice Calling (PSTN) operates out of Azure Communication Services.
-- Note: If necessary, you can choose to connect a supported Session Border Controller (SBC) through Azure direct routing for interoperability with third-party PBXs, analog devices, and other third-party telephony equipment supported by the SBC.
+- You don't need to deploy or maintain any on-premises system because Voice Calling (PSTN) operates through Azure Communication Services.
+- Note: If necessary, you can choose to connect a supported Session Border Controller (SBC) through Azure Communication Services direct routing for interoperability with third-party Pprivate branch exchanges (PBXs), analog devices, and other third-party telephony equipment supported by the SBC.
 
 This option requires an uninterrupted connection to Azure Communication Services.  
 
@@ -49,19 +49,19 @@ With this option, you can connect legacy on-premises telephony and your carrier
 
 ![Azure direct routing diagram.](../media/telephony-concept/sip-interface-diagram.png)
 
-If you answer ‘yes’ to any of the following questions, then Azure direct routing is the right solution for you:
+If you answer **yes** to any of the following questions, then Azure direct routing is the right solution for you:
 
-- You want to use Communication Services with PSTN calling capabilities.
+- You want to use Azure Communication Services with PSTN calling capabilities.
 - You need to retain your current PSTN carrier.
-- You want to mix routing, with some calls going through Voice Calling (PSTN), some through your carrier.
+- You want to mix routing, with some calls going through Voice Calling (PSTN) and some through your carrier.
 - You need to interoperate with third-party PBXs and/or equipment such as overhead pagers, analog devices, and so on.
 
 With this option:
 
 - You connect your own supported SBC to Azure Communication Services without the need for extra on-premises software.
 - You can use literally any telephony carrier with Communication Services.
 - You can choose to configure and manage this option, or it can be configured and managed by your carrier or partner (ask if your carrier or partner provides this option).
-- You can configure interoperability between your telephony equipment, such as a third-party PBX and analog devices, and Communication Services.
+- You can configure interoperability between your telephony equipment, such as a third-party PBX and analog devices, and Azure Communication Services.
 
 This option requires:
 
@@ -78,9 +78,11 @@ This option requires:
 - [Session Border Controllers certified for Azure Communication Services direct routing](./certified-session-border-controllers.md)
 - [Pricing](../pricing.md)
 - Learn about [call automation API](../call-automation/call-automation.md) that enables you to build server-based calling workflows to control and manage calls for phone numbers and direct routing
+- [Number lookup overview](../../concepts/numbers/number-lookup-concept.md)
 
 ### Quickstarts
 
 - [Get a phone number](../../quickstarts/telephony/get-phone-number.md)
 - [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)
-- [Use call automation to build calling workflow that can place calls to phone numbers, play voice prompts and more](../../quickstarts/call-automation/quickstart-make-an-outbound-call.md)
+- [Use call automation to build calling workflow that can place calls to phone numbers, play voice prompts and more](../../quickstarts/call-automation/quickstart-make-an-outbound-call.md)
+- [Look up operator information for a phone number](../../quickstarts/telephony/number-lookup.md)