Merge pull request #300802 from valindrae/streaming-ga

Streaming ga updates

Author: denrea

articles/communication-services/concepts/call-automation/audio-streaming-concept.md

@@ -12,11 +12,9 @@ ms.custom: public_prview
 
 # Audio streaming overview - audio subscription
 
-[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include-document.md)]
-
 Azure Communication Services provides bidirectional audio streaming capabilities, offering developers powerful tools to capture, analyze, and process audio content during active calls. This development paves the way for new possibilities in real-time communication for developers and businesses alike. 
 
-By integrating bidirectional audio streaming with services like Azure OpenAI and other real-time voice APIs, businesses can achieve seamless, low-latency communication. This significantly enhances the development and deployment of conversational AI solutions, allowing for more engaging and efficient interactions. 
+By integrating bidirectional audio streaming with services like Azure OpenAI and other real-time voice APIs, businesses can achieve seamless, low-latency communication. This additional capability significantly enhances the development and deployment of conversational AI solutions, allowing for more engaging and efficient interactions. 
 
 With bidirectional streaming, businesses can now elevate their voice solutions to low-latency, human-like, interactive conversational AI agents. Our bidirectional streaming APIs enable developers to stream audio from an ongoing call on Azure Communication Services to their web servers in real-time, and stream audio back into the call. While the initial focus of these features is to help businesses create conversational AI agents, other use cases include Natural Language Processing for conversation analysis or providing real-time insights and suggestions to agents while they are in active interaction with end users. 
 
@@ -57,5 +55,15 @@ Developers can use the following information about audio sent from Azure Communi
 ## Billing
 See the [Azure Communication Services pricing page](https://azure.microsoft.com/pricing/details/communication-services/?msockid=3b3359f3828f6cfe30994a9483c76d50) for information on how audio streaming is billed. Prices can be found in the calling category under audio streaming.
 
+## Known Limitations
+- Stopping media streaming using a new operationContext doesn't correctly reflect the updated context.
+	- If you create or answer a call with operationContext set to "ABC" and enable media streaming, you receive the MediaStreamingStarted event with operationContext: "ABC."
+	- If you call the StopStreaming API with a different operationContext, say "XYZ," you would expect to receive the MediaStreamingStopped event with operationContext: "XYZ". However, due to a known issue, the MediaStreamingStopped event still contains operationContext: "ABC."
+- When stopping media streaming using a new callback URI, events continue to be sent to the default callback URI used during call creation or answer.
+	- If you create or answer a call with a default callback URI "https://ABC.com" and enable media streaming, the MediaStreamingStarted event will be sent to "https://ABC.com".
+	- If you then stop streaming using the StopStreaming API and specify a new callback URI "https://XYZ.com," you would expect the MediaStreamingStopped event to be sent to "https://XYZ.com." However, due to a known issue, the event is still sent to the original callback URI "https://ABC.com"
+
+
+
 ## Next Steps
-Check out the [audio streaming quickstart](../../how-tos/call-automation/audio-streaming-quickstart.md) to learn more.
+To learn more check out the [audio streaming quickstart](../../how-tos/call-automation/audio-streaming-quickstart.md).

articles/communication-services/concepts/call-automation/real-time-transcription.md

@@ -12,11 +12,10 @@ services: azure-communication-services
 ---
 
 # Generating real-time transcripts
-[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include-document.md)]
 
 Real-time transcriptions are a crucial component in any major business for driving improved customer service experience. Powered by Azure Communication Services and Azure AI Services integration, developers can now use real-time transcriptions through Call Automation SDKs. 
 
-Using the Azure Communication Services real-time transcription, you can easily integrate your Azure AI Services resource with Azure Communication Services to generate transcripts directly during the call. This eliminates the need for developers to extract audio content and deal with the overhead of converting audio into text on your side. You can store the contents of this transcript to use later on for creating a history of the call, summarizing the call to save an agent's time, and even feeding it into your training/learning modules to help improve your contact center agents' customer interactions.
+Using the Azure Communication Services real-time transcription, you can easily integrate your Azure AI Services resource with Azure Communication Services to generate transcripts directly during the call. This capability eliminates the need for developers to extract audio content and deal with the overhead of converting audio into text on your side. You can store the contents of this transcript to use later on for creating a history of the call, summarizing the call to save an agent's time, and even feeding it into your training/learning modules to help improve your contact center agents' customer interactions.
 
 Out of the box Microsoft utilizes a Universal Language Model as a base model that is trained with Microsoft-owned data and reflects commonly used spoken language. This model is pretrained with dialects and phonetics representing various common domains. For more information about supported languages, see [Languages and voice support for the Speech service](/azure/ai-services/speech-service/language-support).
 
@@ -29,16 +28,21 @@ Assist agents better understand customer needs and respond more quickly and accu
 Help agents focus on the conversation rather than note-taking, allowing them to handle more calls and improve productivity
 
 ### Context for agents
-Provide context to an agent before the agent picks up the call, this way the agent knows the information that the caller has provided avoiding any need for the caller to repeat their issue.
+Provide context to an agent before the agent picks up the call. This way, the agent knows the information the caller already gave and the caller does not need to repeat their issue.
 
 ### Derive insights
-Using the transcript generated throughout the call, you can leverage other AI tools to gain live, real-time insights that will help agents and supervisors improve their interactions with customers.
+Using the transcript generated throughout the call, you can use other AI tools to gain live, real-time insights that help agents and supervisors improve their interactions with customers.
 
 ## Sample flow of real-time transcription using Call Automation
 ![Diagram of real-time transcription flow.](./media/transcription.png)
 
 ## Billing
-See the [Azure Communication Services pricing page](https://azure.microsoft.com/pricing/details/communication-services/?msockid=3b3359f3828f6cfe30994a9483c76d50) for information on how real-time transcription is billed.  Prices can be found in the calling category under audio streaming -> unmixed audio insights streaming.
+See the [Azure Communication Services pricing page](https://azure.microsoft.com/pricing/details/communication-services/?msockid=3b3359f3828f6cfe30994a9483c76d50) for information on how real-time transcription is billed. Prices can be found in the calling category under audio streaming -> unmixed audio insights streaming.
+
+## Known limitations
+- Updating transcription with a new operationContext also fails to reflect the updated context.
+  - When you create or answer a call with operationContext: "ABC" and enable transcription, you receive the TranscriptionStarted event with operationContext: "ABC".
+  - If you call the UpdateTranscription API with a new operationContext: "XYZ," you would expect the TranscriptionUpdated event to include operationContext: "XYZ". However, due to a known issue, the TranscriptionUpdated event still returns operationContext: "ABC".
 
 ## Next Steps
 - Check out our how-to guide to learn [how-to use our Real-time Transcription](../../how-tos/call-automation/real-time-transcription-tutorial.md) to users.

articles/communication-services/concepts/voice-video-calling/network-requirements.md

@@ -61,6 +61,8 @@ Communication Services connections require internet connectivity to specific por
 | :-- | :-- | :-- |
 | Media traffic | Range of Azure public cloud IP addresses 20.202.0.0/16 The range provided above is the range of IP addresses on either Media processor or Azure Communication Services TURN service. | UDP 3478 through 3481, TCP ports 443 |
 | Signaling, telemetry, registration| *.skype.com, *.microsoft.com, *.azure.net, *.azure.com, *.office.com| TCP 443, 80 |
+| Call Automation Media | 52.112.0.0/14, 52.122.0.0/15, 2603:1063::/38|	UDP: 3478, 3479, 3480, 3481|
+| Call Automation callback URLs | *.lync.com, *.teams.cloud.microsoft, *.teams.microsoft.com, teams.cloud.microsoft, teams.microsoft.com, 52.112.0.0/14, 52.122.0.0/15, 2603:1027::/48, 2603:1037::/48, 2603:1047::/48, 2603:1057::/48, 2603:1063::/38, 2620:1ec:6::/48, 2620:1ec:40::/42 | TCP: 443, 80 UDP: 443 |
 
 
 The endpoints below should be reachable for U.S. Government GCC High customers only.

articles/communication-services/how-tos/call-automation/audio-streaming-quickstart.md

@@ -14,8 +14,6 @@ zone_pivot_groups: acs-js-csharp-java-python
 
 # Quickstart: Server-side Audio Streaming
 
-[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include-document.md)]
-
 Get started with using audio streams through Azure Communication Services Audio Streaming API. This quickstart assumes you're already familiar with Call Automation APIs to build an automated call routing solution. 
 
 Functionality described in this quickstart is currently in public preview.

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-csharp.md

@@ -34,14 +34,12 @@ Enable automatic audio streaming when the call is established by setting the fla
 This setting ensures that audio streaming starts automatically as soon as the call is connected.
 
 ``` C#
-var mediaStreamingOptions = new MediaStreamingOptions(
-  new Uri("wss://YOUR_WEBSOCKET_URL"),
-  MediaStreamingContent.Audio,
-  MediaStreamingAudioChannel.Mixed,
-  startMediaStreaming: true) {
-  EnableBidirectional = true,
-    AudioFormat = AudioFormat.Pcm24KMono
-}
+MediaStreamingOptions mediaStreamingOptions = new MediaStreamingOptions(MediaStreamingAudioChannel.Unmixed);
+ mediaStreamingOptions.TransportUri = new Uri(websocketUri);
+ mediaStreamingOptions.EnableBidirectional = true;
+ mediaStreamingOptions.AudioFormat = AudioFormat.Pcm24KMono;
+ mediaStreamingOptions.EnableDtmfTones = true;
+  
 var options = new AnswerCallOptions(incomingCallContext, callbackUri) {
   MediaStreamingOptions = mediaStreamingOptions,
 };
@@ -56,14 +54,12 @@ When Azure Communication Services receives the URL for your WebSocket server, it
 To start media streaming during the call, you can use the API. To do so, set the `startMediaStreaming` parameter to `false` (which is the default), and later in the call, you can use the start API to enable media streaming.
 
 ``` C#
-var mediaStreamingOptions = new MediaStreamingOptions(
-  new Uri("wss://<YOUR_WEBSOCKET_URL"),
-  MediaStreamingContent.Audio,
-  MediaStreamingAudioChannel.Mixed,
-  startMediaStreaming: false) {
-  EnableBidirectional = true,
-    AudioFormat = AudioFormat.Pcm24KMono
-}
+MediaStreamingOptions mediaStreamingOptions = new MediaStreamingOptions(MediaStreamingAudioChannel.Unmixed);
+ mediaStreamingOptions.TransportUri = new Uri(websocketUri);
+ mediaStreamingOptions.EnableBidirectional = true;
+ mediaStreamingOptions.AudioFormat = AudioFormat.Pcm24KMono;
+ mediaStreamingOptions.EnableDtmfTones = true;
+
 var options = new AnswerCallOptions(incomingCallContext, callbackUri) {
   MediaStreamingOptions = mediaStreamingOptions,
 };
@@ -72,10 +68,11 @@ AnswerCallResult answerCallResult = await client.AnswerCallAsync(options);
 
 Start media streaming via API call
 StartMediaStreamingOptions options = new StartMediaStreamingOptions() {
-  OperationContext = "startMediaStreamingContext"
+  OperationContext = "startMediaStreamingContext",
+  OperationCallbackUri = eventCallbackUri
 };
 
-await callMedia.StartMediaStreamingAsync();
+await callMedia.StartMediaStreamingAsync(options);
 ```
 
 
@@ -86,10 +83,11 @@ To stop receiving audio streams during a call, you can use the **Stop streaming
 
 ``` C#
 StopMediaStreamingOptions options = new StopMediaStreamingOptions() {
-  OperationContext = "stopMediaStreamingContext"
+  OperationContext = "stopMediaStreamingContext",
+  OperationCallbackUri = eventCallbackUri
 };
 
-await callMedia.StopMediaStreamingAsync();
+await callMedia.StopMediaStreamingAsync(options);
 ```
 
 ## Handling audio streams in your websocket server
@@ -116,6 +114,9 @@ private async Task StartReceivingFromAcsMediaWebSocket(Websocket websocket) {
 
 The first packet you receive contains metadata about the stream, including audio settings such as encoding, sample rate, and other configuration details.
 
+### Additional Headers
+The Correlation ID and Call Connection ID are now included in the WebSocket headers for improved traceability `x-ms-call-correlation-id` and `x-ms-call-connection-id`. These are sent when Azure Communication Services tries to connect to your endpoint.
+
 ``` json
 {
   "kind": "AudioMetadata",

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-java.md

@@ -46,20 +46,25 @@ When Azure Communication Services receives the URL for your WebSocket server, it
 To start media streaming during the call, you can use the API. To do so, set the `startMediaStreaming` parameter to `false` (which is the default), and later in the call, you can use the start API to enable media streaming.
 
 ``` Java 
-MediaStreamingOptions mediaStreamingOptions = new MediaStreamingOptions(appConfig.getTransportUrl(), MediaStreamingTransport.WEBSOCKET, MediaStreamingContent.AUDIO, MediaStreamingAudioChannel.MIXED, false)
-    .setEnableBidirectional(true)
-    .setAudioFormat(AudioFormat.PCM_24K_MONO);
+MediaStreamingOptions mediaStreamingOptions = new MediaStreamingOptions(MediaStreamingAudioChannel.UNMIXED);
+mediaStreamingOptions.setTransportUrl(appConfig.getTransportUrl());
+mediaStreamingOptions.setStartMediaStreaming(true);
+mediaStreamingOptions.setEnableDtmfTones(true); // Allow receiving DTMF tones
+mediaStreamingOptions.setEnableBidirectional(true);
+mediaStreamingOptions.setAudioFormat(AudioFormat.PCM_24K_MONO);
 
 options = new AnswerCallOptions(data.getString(INCOMING_CALL_CONTEXT), callbackUri)
     .setCallIntelligenceOptions(callIntelligenceOptions)
     .setMediaStreamingOptions(mediaStreamingOptions);
 
 Response answerCallResponse = client.answerCallWithResponse(options, Context.NONE);
 
-StartMediaStreamingOptions startMediaStreamingOptions = new StartMediaStreamingOptions()
-    .setOperationContext("startMediaStreamingContext");
+StartMediaStreamingOptions mediaStreamingOptions = new StartMediaStreamingOptions();
+mediaStreamingOptions.setOperationContext("StartMediaStreamingContext");
 
-callConnection.getCallMedia().startMediaStreamingWithResponse(startMediaStreamingOptions, Context.NONE);     
+client.getCallConnection(callConnectionId)
+      .getCallMedia()
+      .startMediaStreamingWithResponse(mediaStreamingOptions, Context.NONE);    
 ```
 
 ## Stop audio streaming
@@ -68,9 +73,12 @@ To stop receiving audio streams during a call, you can use the **Stop streaming
 - **Automatic stop on call disconnect:** Audio streaming automatically stops when the call is disconnected.
 
 ``` Java
-StopMediaStreamingOptions stopMediaStreamingOptions = new StopMediaStreamingOptions()
-    .setOperationContext("stopMediaStreamingContext");
-callConnection.getCallMedia().stopMediaStreamingWithResponse(stopMediaStreamingOptions, Context.NONE);
+StopMediaStreamingOptions stopOptions = new StopMediaStreamingOptions();
+stopOptions.setOperationContext("StopMediaStreamingContext");
+
+client.getCallConnection(callConnectionId)
+      .getCallMedia()
+      .stopMediaStreamingWithResponse(stopOptions, Context.NONE);
 ```
 
 ## Handling audio streams in your websocket server
@@ -90,6 +98,9 @@ public void onMessage(String message, Session session) {
 
 The first packet you receive contains metadata about the stream, including audio settings such as encoding, sample rate, and other configuration details.
 
+### Additional Headers
+The Correlation ID and Call Connection ID are now included in the WebSocket headers for improved traceability `x-ms-call-correlation-id` and `x-ms-call-connection-id`. These are sent when Azure Communication Services tries to connect to your endpoint.
+
 ``` json
 {
   "kind": "AudioMetadata",

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-js.md

@@ -34,21 +34,26 @@ Enable automatic audio streaming when the call is established by setting the fla
 This setting ensures that audio streaming starts automatically as soon as the call is connected.
 
 ``` JS
-var mediaStreamingOptions = new MediaStreamingOptions(
-	new Uri("wss://YOUR_WEBSOCKET_URL"),
-	MediaStreamingContent.Audio,
-	MediaStreamingAudioChannel.Mixed,
-	startMediaStreaming: true)
-{
-	EnableBidirectional = true,
-		AudioFormat = AudioFormat.Pcm24KMono
-}
-var options = new AnswerCallOptions(incomingCallContext, callbackUri)
-{
-	MediaStreamingOptions = mediaStreamingOptions,
+const mediaStreamingOptions = {
+    transportUrl: "wss://YOUR_WEBSOCKET_URL", 
+    transportType: "websocket",               
+    contentType: "audio",                     
+    audioChannelType: "mixed",                
+    startMediaStreaming: true,
+    enableDtmfTones: true,           
+    enableBidirectional: true,                
+    audioFormat: "Pcm24KMono"                 
+};
+
+const answerCallOptions = {
+    mediaStreamingOptions: mediaStreamingOptions
 };
 
-AnswerCallResult answerCallResult = await client.AnswerCallAsync(options);
+answerCallResult = await acsClient.answerCall(
+    incomingCallContext,
+    callbackUri,
+    answerCallOptions
+);
 ```
 
 When Azure Communication Services receives the URL for your WebSocket server, it establishes a connection to it. Once the connection is successfully made, streaming is initiated.
@@ -58,11 +63,12 @@ To start media streaming during the call, you can use the API. To do so, set the
 
 ``` JS
 const mediaStreamingOptions: MediaStreamingOptions = {
-	transportUrl: transportUrl,
+	transportUrl:  "wss://YOUR_WEBSOCKET_URL",
 	transportType: "websocket",
 	contentType: "audio",
 	audioChannelType: "unmixed",
 	startMediaStreaming: false,
+	enableDtmfTones: true,
 	enableBidirectional: true,
 	audioFormat: "Pcm24KMono"
 }
@@ -134,6 +140,9 @@ async function processWebsocketMessageAsync(receivedBuffer: ArrayBuffer) {
 
 The first packet you receive contains metadata about the stream, including audio settings such as encoding, sample rate, and other configuration details.
 
+### Additional Headers
+The Correlation ID and Call Connection ID are now included in the WebSocket headers for improved traceability `x-ms-call-correlation-id` and `x-ms-call-connection-id`. These are sent when Azure Communication Services tries to connect to your endpoint.
+
 ``` json
 {
   "kind": "AudioMetadata",