data channel and proxy

Author: vac0224

articles/communication-services/concepts/voice-video-calling/data-channel.md

@@ -1,39 +1,40 @@
 ---
-title: How to pass contextual data between calls
-titleSuffix: An Azure Communication Services how-to guide
+title: Pass user-to-user information (UUI) data in a header
+titleSuffix: An Azure Communication Services article
 description: Use Azure Communication Services SDKs to pass contextual data between calls.
 author: sloanster
 ms.author: micahvivion
 ms.service: azure-communication-services
 ms.subservice: calling
 ms.topic: how-to 
-ms.date: 09/13/2024
+ms.date: 06/27/2025
 ms.custom: template-how-to
 ---
 
-# Using the ACS calling SDK to pass contextual User-to-User Information (UUI) data between calls
+# Pass user-to-user information (UUI) data in a header
 
-In this article, you learn how to pass along custom contextual information when routing calls with Azure Communication Services Calling SDKs. This capability allows users to pass metadata about the call, callee, or any other information that is relevant to their application or business logic.
+This article describes how to pass user-to-user information (UUI) in a header when routing calls with Azure Communication Services Calling SDKs. This capability enables users to pass metadata about the call, callee, or any other information that is relevant to their application or business logic.
 
-The Azure Communication Services (ACS) WebJS SDK provides developers to include custom contextual data (included as a header on the calling object) when directing and routing calls from one person to another.  This information, also known as User-to-User Information (UUI) data or call control UUI data, is a small piece of data inserted by an application initiating the call. The UUI data is opaque to end users making a call.
+The Azure Communication Services WebJS SDK enables developers to include custom contextual data (included as a header on the calling object) when directing and routing calls from one person to another. This information, also known as user-to-user information (UUI) data or call control UUI data, is a small piece of data inserted by an application initiating the call. The UUI data is opaque to end users making a call.
 
-Contextual information supported includes both freeform custom headers and the standard User-to-User Information (UUI) SIP header. Also when you receive an inbound call, the custom headers and UUI are included in the incomingCall payload.
+Contextual information supported includes both freeform custom headers and the standard UUI SIP header. In addition, when you receive an inbound call, the custom headers and UUI are included in the `incomingCall` payload.
 
 All custom context data is opaque to Calling SDK or SIP protocols and its content is unrelated to any basic functions.
 
-Developers can pass this context by using custom headers, which consist of optional key-value pairs. These pairs can be included in the 'AddParticipant' or 'Transfer' actions within the calling SDK. Once added, you can read the data payload as the call moves between endpoints. By efficiently looking up this metadata and associating it with the call, developers can avoid external database lookups and have the content information readily available within the call object.
+Developers can pass this context by using custom headers, which consist of optional key-value pairs. These pairs can be included in the `AddParticipant` or `Transfer` actions within the calling SDK. Once added, you can read the data payload as the call moves between endpoints. By efficiently looking up this metadata and associating it with the call, developers can avoid external database lookups and have the content information readily available within the call object.
 
-The custom call context can be transmitted to SIP endpoints using the SIP protocol. This transmission includes both the custom headers and the standard User-to-User Information (UUI) SIP header. When an inbound call is routed from your telephony network, the data from your Session Border Controller (SBC) in the custom headers and UUI is also included in the IncomingCall event payload.
+The custom call context can be transmitted to SIP endpoints using the SIP protocol. This transmission includes both the custom headers and the standard UUI SIP header. When an inbound call is routed from your telephony network, the data from your Session Border Controller (SBC) in the custom headers and UUI is also included in the IncomingCall event payload.
 
 It’s important to note that all custom context data remains transparent to the calling SDK and isn't related to any of the SDK’s fundamental functions when used in SIP protocols. Here's a tutorial to assist you in adding custom context headers when using the WebJS SDK.
 
 
 > [!IMPORTANT]
-> To use the ability to pass User-to-User Information (UUI) data using the calling SDK you must use the calling WebJS SDK GA or public preview version `1.29.1` or later.
+> To pass UUI data using the calling SDK, you must use the calling WebJS SDK GA or public preview version `1.29.1` or later.
 
 [!INCLUDE [Passing Contextual Data - Client-side JavaScript](./includes/call-context/call-context-web.md)]
 
 ## Next steps
+
 - [Learn how to manage calls](./manage-calls.md)
 - [Learn how to manage video](./manage-video.md)
 - [Learn how to record calls](./record-calls.md)

articles/communication-services/how-tos/calling-sdk/call-context.md

@@ -2,26 +2,26 @@
 author: sloanster
 ms.service: azure-communication-services
 ms.topic: include
-ms.date: 09/13/2024
+ms.date: 06/27/2025
 ms.author: micahvivion
 ---
 
-
 ## Technical parameters
-The calling SDK supports adding up to 5 custom SIP headers and 1000 custom VOIP headers. Additionally, developers can include a dedicated User-To-User header as part of SIP headers list.
 
-The maximum length of a SIP header key is 64 chars, including the X-MS-Custom prefix. Due note that when the SIP header is added the calling SDK will automatically add the ‘X-MS-Custom-’ prefix (which can be seeing if you inspect the SIP header with packet inspector).
+The calling SDK supports adding up to five (5) custom SIP headers and 1000 custom VOIP headers. Additionally, developers can include a dedicated User-To-User header as part of SIP headers list.
+
+The maximum length of a SIP header key is 64 chars, including the X-MS-Custom prefix. When you add the SIP header to the calling SDK, it automatically adds the `X-MS-Custom-` prefix, which you can see by inspecting the SIP header with packet inspector.
 
-The SIP header key may consist of alphanumeric characters and a few selected symbols which include `.`, `!`, `%`, `*`, `_`, `+`, `~`, `-`. The maximum length of SIP header value is 256 chars. The same limitations apply when configuring the SIP headers on your SBC. The SIP header value may consist of alphanumeric characters and a few selected symbols which include `=`, `;`, `.`, `!`, `%`, `*`, `_`, `+`, `~`, `-`.
+The SIP header key might consist of alphanumeric characters and a few selected symbols, which include `.`, `!`, `%`, `*`, `_`, `+`, `~`, `-`. The maximum length of SIP header value is 256 chars. The same limitations apply when configuring the SIP headers on your session border controller (SBC). The SIP header value might consist of alphanumeric characters and a few selected symbols, which include `=`, `;`, `.`, `!`, `%`, `*`, `_`, `+`, `~`, `-`.
 
-The maximum length of a VOIP header key is 64 chars. The maximum length of VOIP header value is 1024 chars.
+The maximum length of a VOIP header key is 64 chars. The maximum length of VOIP header value is 1024 characters.
 
 When adding these custom headers as a developer you can choose to add only SIP headers, only VoIP headers or both can be included.
 
 > [!NOTE]
-> Currently, adding custom User-to-User Information headers is only supported when initiating a 1:1 call. Passing User-to-User Information headers in group calls is not currently supported. To work around this after starting the 1:1 call, you can include additional participants while maintaining the User-to-User Information within the calls. 
+> Currently, adding custom User-to-User Information headers is only supported when initiating a 1:1 call. Passing User-to-User Information headers in group calls isn't currently supported. To work around this constraint after starting the 1:1 call, you can add participants while maintaining the User-to-User Information within the calls. 
 
-For details on the custom context interface API, consult the [custom context API resource](/javascript/api/azure-communication-services/@azure/communication-calling/customcontext?view=azure-communication-services-js&preserve-view=true) page.
+For details about the custom context interface API, see [custom context API resource](/javascript/api/azure-communication-services/@azure/communication-calling/customcontext?view=azure-communication-services-js&preserve-view=true).
 
 ## Place a call with User-to-User Information (UUI) data
 

articles/communication-services/how-tos/calling-sdk/includes/call-context/call-context-web.md

@@ -1,19 +1,19 @@
 ---
-ms.author: enricohuang
-title: Quickstart - Add Data Channel messaging to your calling app
-titleSuffix: An Azure Communication Services quickstart
-description: In this quickstart, you'll learn how to add Data Channel to your existing calling app using Azure Communication Services.
+title: Add data channel messaging to a calling app
+titleSuffix: An Azure Communication Services article
+description: This article describes how to add Data Channel to your existing calling app using Azure Communication Services.
 author: sloanster
+ms.author: enricohuang
 services: azure-communication-services
-ms.date: 05/04/2023
+ms.date: 6/27/2025
 ms.topic: quickstart
 ms.service: azure-communication-services
 ms.subservice: calling
 zone_pivot_groups: acs-plat-web-ios-android-windows
 ms.custom: mode-other, devx-track-js
 ---
 
-# Quickstart: Add Data Channel messaging to your calling app
+# Add data channel messaging to a calling app
 
 ::: zone pivot="platform-web"
 [!INCLUDE [Data Channel feature with JavaScript](./includes/data-channel/data-channel-javascript.md)]
@@ -33,7 +33,7 @@ ms.custom: mode-other, devx-track-js
 
 ## Next steps
 
-For more information, see the following articles:
+For more information, see:
 
-- Learn about [Data Channel feature concept document](../../concepts/voice-video-calling/data-channel.md)
-- Learn more about [Calling SDK capabilities](./getting-started-with-calling.md)
+- [Data Channel feature concept document](../../concepts/voice-video-calling/data-channel.md)
+- [Calling SDK capabilities](./getting-started-with-calling.md)

articles/communication-services/quickstarts/voice-video-calling/get-started-data-channel.md

@@ -1,54 +1,70 @@
 ---
+title: Add data channel messaging to a calling app
+titleSuffix: An Azure Communication Services article
+description: This article describes how to add Data Channel to your existing calling app using Azure Communication Services.
 ms.author: chengyuanlai
-title: Quickstart - Add data channel to your Android calling app
-titleSuffix: An Azure Communication Services document
-description: In this quickstart, you learn how to add data channel messaging to your existing Android calling app using Azure Communication Services.
 author: sloanster
 services: azure-communication-services
-ms.date: 03/01/2024
+ms.date: 06/27/2025
 ms.topic: include
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
 >[!IMPORTANT]
-> Please be aware that the current Data Channel feature API doesn't support direct messaging between a web browser and a native app in a peer-to-peer call scenario.
+> The current Data Channel feature API doesn't support direct messaging between a web browser and a native app in a peer-to-peer call scenario.
 
 ## Overview
+
 The Data Channel feature API enables real-time data messaging during audio and video calls. In this quickstart guide, we illustrate how to integrate Data Channel feature to your call and use the Data Channel APIs to send and receive data messages through a data channel.
+
 ### Prerequisites
+
 Refer to the [Voice Calling Quickstart](../../getting-started-with-calling.md?pivots=platform-android) to set up a sample app with voice calling.
+
 ### Classes
+
 | Name | Description |
-| - | - | 
+| --- | --- | 
 | DataChannelCallFeature | Used to start and manage data channel feature. | 
 | DataChannelSender | Used to manage a data channel as a sender and send data. | 
 | DataChannelReceiver | Used to manage a data channel as a receiver and receive data. |
 | DataChannelSenderOptions | Used for representing options to create a data channel sender. |
+
 ### Enums
+
 | Name | Description |  
-| - | - | 
+| --- | --- | 
 | DataChannelPriority | Describes the priority options of data channel. Values: { `NORMAL`, `HIGH` }. | 
 | DataChannelReliability | Describes the reliability options of data channel. Values: { `LOSSY`, `DURABLE` }. |
+
 ### Error Code
+
 | Name | Description |  
-| - | - | 
-| _DATA_CHANNEL_FAILED_TO_START_ | `getDataChannelSender()` can fail with this error code, indicating underlying Data Channel is not ready to be used. | 
-| _DATA_CHANNEL_RANDOM_ID_NOT_AVAILABLE_ | `getDataChannelSender()` can fail with this error code, indicating all available random channel IDs have already been used. | 
-| _DATA_CHANNEL_SENDER_CLOSED_ | `sendMessage()` can fail with this error code, indicating the sender has already been closed previously. |
+| --- | --- | 
+| _DATA_CHANNEL_FAILED_TO_START_ | `getDataChannelSender()` can fail with this error code, indicating underlying Data Channel isn't ready to be used. | 
+| _DATA_CHANNEL_RANDOM_ID_NOT_AVAILABLE_ | `getDataChannelSender()` can fail with this error code, indicating each available random channel ID is in use. | 
+| _DATA_CHANNEL_SENDER_CLOSED_ | `sendMessage()` can fail with this error code, indicating the sender data channel is already closed. |
 | _DATA_CHANNEL_MESSAGE_SIZE_OVER_LIMIT_ | `sendMessage()` can fail with this error code, indicating the message data size exceeds the limit. You can get the message size limit using `getMaxMessageSizeInBytes()` in `DataChannelSender`. |
 | _DATA_CHANNEL_MESSAGE_FAILURE_FOR_BANDWIDTH_ | `sendMessage()` can fail with this error code, indicating a failure in sending the message due to not enough bandwidth. | 
 | _DATA_CHANNEL_MESSAGE_FAILURE_FOR_TRAFFIC_LIMIT_ | `sendMessage()` can fail with this error code, indicating a failure in sending the message due to the overall usage of Data Channel not in compliance with the traffic limit rules. Refer to [Data Channel Concept Document](../../../../concepts/voice-video-calling/data-channel.md) for details of the traffic limit. |
+
 ### Methods
+
 #### Enable Data Channel feature
 
 1. Get the ongoing call object established during the prerequisite steps.
+
 2. Get the Data Channel Feature object.
+
 ```java
 DataChannelCallFeature dataChannelCallFeature = call.feature(Features.DATA_CHANNEL);
 ```
+
 #### Receiving data message
+
 1. Define the DataChannelReceiverCreatedListener.
+
 ```java
 DataChannelReceiverCreatedListener receiverCreatedListener = new DataChannelReceiverCreatedListener() {
     @Override
@@ -62,11 +78,15 @@ DataChannelReceiverCreatedListener receiverCreatedListener = new DataChannelRece
     }
 };
 ```
+
 2. Register the `receiverCreatedListener`.
+
 ```java
 dataChannelCallFeature.addOnReceiverCreatedListener(receiverCreatedListener);
  ```
+
 3. Define the MessageReceivedListener.
+
 ```java
 MessageReceivedListener messageReceivedListener = new MessageReceivedListener() {
     @Override
@@ -77,7 +97,9 @@ MessageReceivedListener messageReceivedListener = new MessageReceivedListener()
     }
 };
 ```
-4. Define the ReceiverClosedListener.
+
+4. Define the `ReceiverClosedListener`.
+
 ```java
 ReceiverClosedListener receiverClosedListener = new ReceiverClosedListener() {
     @Override
@@ -86,13 +108,18 @@ ReceiverClosedListener receiverClosedListener = new ReceiverClosedListener() {
     }
 };
 ```
+
 5. Register the `messageReceivedListener` and `receiverClosedListener`.
+
 ```java
 receiver.addOnMessageReceivedListener(messageReceivedlistener);
 receiver.addOnClosedListener(receiverClosedListener);
 ```
+
 #### Sending data message
-1. Configure the DataChannelSenderOptions.
+
+1. Configure the `DataChannelSenderOptions`.
+
 ```java
 DataChannelSenderOptions options = new DataChannelSenderOptions();
 options.setChannelId(1000);
@@ -103,7 +130,9 @@ options.setReliability(DataChannelReliability.LOSSY);
 List<CommunicationIdentifier> participants = Arrays.asList( /* identifier1, identifier2, ... */ );
 options.setParticipants(participants);
 ```
-2. Get the DataChannelSender and send data message
+
+2. Get the `DataChannelSender` and send data message.
+
 ```java
 DataChannelSender dataChannelSender = dataChannelCallFeature.getDataChannelSender(options);