@tencent-rtc/mcp 1.6.4 → 1.6.6

package/resource/knowledge/callkit/core-sdk/android/answer-call.md

@@ -78,7 +78,7 @@ class MainActivity : ComponentActivity() {
 Create a call page that launches when an incoming call is received.
 1. **Create the call page:** Implement a new Activity to serve as the call interface, triggered upon incoming call.
 
-2. **Bind the call page to **[CallCoreView](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-call-core-view/index.html)**:** The CallCoreView component automatically observes [CallStore](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/index.html) data and renders video, supporting UI customization like layout switching, avatar, and icon configuration.
+2. **Bind the call page to** [CallCoreView](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-call-core-view/index.html)**:** The CallCoreView component automatically observes [CallStore](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/index.html) data and renders video, supporting UI customization like layout switching, avatar, and icon configuration.
 
    ``` java
    import io.trtc.tuikit.atomicxcore.api.view.CallCoreView
@@ -581,7 +581,6 @@ Get call duration in real time from the `duration` field in [activeCall](https:/
 
    > **Note：**
    >
-
    > For more info on reactive call state data, see [CallState](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-state/index.html).
    >
 
@@ -656,7 +655,7 @@ Implementing Picture-in-Picture (PiP) mode requires Android 8.0 (API level 26) o
        }
     }
    ```
-- **Handling the PiP Transition : **When the system successfully enters PiP mode, the `onPictureInPictureModeChanged` callback is triggered. You must update the **CallCoreView** layout to `CallLayoutTemplate.Pip` at this stage.
+- **Handling the PiP Transition :** When the system successfully enters PiP mode, the `onPictureInPictureModeChanged` callback is triggered. You must update the **CallCoreView** layout to `CallLayoutTemplate.Pip` at this stage.
 
    ``` java
    val callCoreView = CallCoreView(context)
@@ -668,9 +667,9 @@ Implementing Picture-in-Picture (PiP) mode requires Android 8.0 (API level 26) o
       }
    }
    ```
-- **Restoring Full-Screen Layout : **When the user returns to the app from PiP (restoring full screen), the onResume callback will be triggered. You should reset the layout based on the current number of participants:
+- **Restoring Full-Screen Layout :** When the user returns to the app from PiP (restoring full screen), the onResume callback will be triggered. You should reset the layout based on the current number of participants:
 
-  - **1 v 1 Calls: **Use `CallLayoutTemplate.Float`.
+  - **1 v 1 Calls:** Use `CallLayoutTemplate.Float`.
 
   - **Group Calls:** Use `CallLayoutTemplate.Grid`.
 
@@ -712,7 +711,7 @@ class CallActivity : AppCompatActivity() {
 ### Enable Background Audio/Video Capture
 
 To maintain audio and video capture when the app is in the background, you must implement a Foreground Service. Starting from Android 9.0 (API 28), foreground service permissions are required, and Android 14 (API 34) mandates declaring specific service types for the camera and microphone.
-1. **Configure Permissions and Service ( AndroidManifest.xml ) : **Declare the necessary foreground service permissions and specify the service types within the <application> tag.
+1. **Configure Permissions and Service ( AndroidManifest.xml ) :** Declare the necessary foreground service permissions and specify the service types within the <application> tag.
 
    ``` java
    <manifest xmlns:android="http://schemas.android.com/apk/res/android">
@@ -730,7 +729,7 @@ To maintain audio and video capture when the app is in the background, you must
        </application>
    </manifest>
    ```
-2. **Create the Foreground Service Class ( CallForegroundService ) : **The service ensures the system does not kill the app's process while it is in the background by displaying a persistent notification.
+2. **Create the Foreground Service Class ( CallForegroundService ) :** The service ensures the system does not kill the app's process while it is in the background by displaying a persistent notification.
 
    ``` java
    import android.app.Notification
@@ -810,7 +809,7 @@ Congratulations! You have implemented the answer call feature. Next, see Make Yo
 ### Why does the UI appear distorted or show the wrong screen after navigating to another page while in PiP mode?
 - **Cause :** Android's Picture-in-Picture (PiP) mode operates based on the Task Stack. By default, all Activities in an app share the same task stack. If you launch a new Activity while the app is in PiP mode, that new page is pushed onto the current stack. Consequently, the new screen incorrectly attempts to render within the tiny PiP window, leading to UI anomalies.
 
-- **Solution : **Declare the Call Activity as a separate task with its own affinity in the AndroidManifest.xml. This ensures the call remains isolated in its own window regardless of other app navigation.
+- **Solution :** Declare the Call Activity as a separate task with its own affinity in the AndroidManifest.xml. This ensures the call remains isolated in its own window regardless of other app navigation.
 
    ``` java
     <activity

package/resource/knowledge/callkit/core-sdk/android/make-call.md

@@ -71,7 +71,6 @@ class MainActivity : ComponentActivity() {
 
 > **Note：**
 >
-
 > You must log in before making a call. The following steps show how to make a call.
 >
 
@@ -80,7 +79,7 @@ class MainActivity : ComponentActivity() {
 Set up a dedicated call screen that appears when a call is initiated:
 1. **Create the call screen:** Implement a new Activity to host the call UI and handle navigation when a call is received.
 
-2. **Attach **[CallCoreView](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-call-core-view/index.html)**:** This core view component observes **CallStore** data and renders the call UI. It supports layout switching, avatar, and icon customization.
+2. **Attach** [CallCoreView](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-call-core-view/index.html)**:** This core view component observes **CallStore** data and renders the call UI. It supports layout switching, avatar, and icon customization.
 
    ``` java
    class CallActivity : AppCompatActivity() {
@@ -117,7 +116,7 @@ Use the APIs from [DeviceStore](https://liteav.sdk.cloudcachetci.com/doc/product
    |**Icons**|||||||||
    |---------|---------|---------|---------|---------|---------|---------|---------|---------|
 
-- **Example: Adding****hang up, microphone, and camera buttons**
+- **Example: Adding** **hang up, microphone, and camera buttons**
 
   1. **Create Bottom Bar Container:** Add a container at the bottom of the call screen to hold the hang up, microphone, and camera buttons.
 
@@ -418,8 +417,8 @@ After the [calls](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic
 | <strong>Parameter</strong> | <strong>Type</strong> | <strong>Required</strong> | <strong>Description</strong> |
 | --- | --- | --- | --- |
 | userIdList | List | Yes | List of target user <code>userId</code>s. |
-| mediaType | <a href="https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-media-type/index.html">CallMediaType</a> | Yes | Call media type: audio or video.<br>- <code>CallMediaType.Video</code>: Video call.<br>- <code>CallMediaType.Audio</code>: Audio call. |
-| params | <a href="https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-params/index.html">CallParams</a> | No | Optional call parameters, such as room ID, call invitation timeout, etc.<br>- <code>roomId</code> (String): Room ID, optional. If not specified, the server assigns one.<br>- <code>timeout</code> (Int): Call timeout (seconds).<br>- <code>userData</code> (String): Custom user data.<br>- <code>chatGroupId</code> (String): Chat group ID for group calls.<br>- <code>isEphemeralCall</code> (Boolean): If true, the call is encrypted and not logged. |
+| mediaType | <a href="https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-media-type/index.html">CallMediaType</a> | Yes | Call media type: audio or video.<br>-  <code>CallMediaType.Video</code>: Video call.<br>-  <code>CallMediaType.Audio</code>: Audio call. |
+| params | <a href="https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-params/index.html">CallParams</a> | No | Optional call parameters, such as room ID, call invitation timeout, etc.<br>-  <code>roomId</code> (String): Room ID, optional. If not specified, the server assigns one.<br>- <code>timeout</code> (Int): Call timeout (seconds).<br>- <code>userData</code> (String): Custom user data.<br>- <code>chatGroupId</code> (String): Chat group ID for group calls.<br>- <code>isEphemeralCall</code> (Boolean): If true, the call is encrypted and not logged. |
 
 ### Step 5: End the Call
 
@@ -578,7 +577,7 @@ Use [setWaitingAnimation](https://liteav.sdk.cloudcachetci.com/doc/product/tuiki
 
 ### Add Call Duration Display
 
-You can display call duration in real time using the [activeCall](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-state/active-call.html)`duration` field.
+You can display call duration in real time using the [activeCall](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-state/active-call.html) `duration` field.
 1. **Subscribe to the data layer:** Observe `CallStore.observerState.activeCall` for updates to the current call.
 
 2. **Bind duration data:** Bind `activeCall.duration` to a UI control. The UI updates automatically—no need to manage a timer manually.
@@ -627,7 +626,6 @@ You can display call duration in real time using the [activeCall](https://liteav
 
    > **Note：**
    >
-
    > For more reactive call status data, see [CallState](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-state/index.html).
    >
 

package/resource/knowledge/callkit/core-sdk/android/offline-push.md

@@ -4,7 +4,6 @@ To solve this, you need to integrate offline push notifications using FCM Data M
 
 > **Note:**
 >
-
 > Offline push is not required if users are only calling always-online web agents.
 >
 
@@ -16,7 +15,6 @@ Go to the [Chat Console > App Push > Access settings](https://console.trtc.io/ch
 
 > **Note:**
 >
-
 > When your push plugin trial or subscription expires, all push services (including offline push for regular messages, broadcast/tag push, etc.) will be automatically suspended. To ensure uninterrupted service, please [purchase](https://buy.intl.cloud.tencent.com/avc) or [renew](https://console.tencentcloud.com/expense/renewal) your subscription in advance.
 >
 
@@ -56,8 +54,8 @@ Over 90% of missed call notifications are due to users manually disabling app no
 
    > **Note：**
    >
->   - TIMPush requires IM SDK version **7.9.5666** or above.
->   - You can update the Chat SDK version in the `tuicallkit-kt/build.gradle` file.
+   > - TIMPush requires IM SDK version **7.9.5666** or above.
+   > - You can update the Chat SDK version in the `tuicallkit-kt/build.gradle` file.
 
 ### Step 3: Project Configuration
 1. Add the following to the `buildscript > dependencies` section of your project-level `build.gradle` file:
@@ -315,7 +313,7 @@ Listen for incoming call events. After a successful login (Step 1), if there are
        }
    }
    ```
-- **onCallReceived: **Triggered when an incoming call event is received.
+- **onCallReceived:** Triggered when an incoming call event is received.
 
 | <strong>Parameter</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |

package/resource/knowledge/callkit/core-sdk/flutter/answer-call.md

@@ -548,7 +548,7 @@ Use the [loadingAnimation](https://liteav.sdk.qcloud.com/doc/product/tuikit/atom
 
 ### Add Call Duration Indicator
 
-Call duration updates in real time via [activeCall](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallState/activeCall.html)`duration`. To display call duration:
+Call duration updates in real time via [activeCall](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallState/activeCall.html) `duration`. To display call duration:
 1. **Subscribe to Data:** Listen to `CallStore.shared.state.activeCall` for the current active call.
 
 2. **Bind Call Duration:** Bind the `activeCall.duration` field to a UI widget. This is reactive and auto-updates the UI—no manual timer needed.
@@ -612,7 +612,6 @@ Call duration updates in real time via [activeCall](https://liteav.sdk.qcloud.co
 
    > **Note:**
    >
-
    > For more reactive call state data, see [CallState](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallState-class.html).
    >
 
@@ -666,7 +665,7 @@ Use [setLayoutTemplate](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-
 
 ### Set Default Call Timeout
 
-When making a call via [calls](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallStore/calls.html), specify the timeout using [CallParams](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallParams-class.html)`timeout`.
+When making a call via [calls](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallStore/calls.html), specify the timeout using [CallParams](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallParams-class.html) `timeout`.
 ``` java
 void startCall(List<String> userIdList, CallMediaType mediaType) {
   CallParams params = CallParams(
@@ -870,10 +869,8 @@ iOS supports system PiP with the underlying TRTC engine. When the app goes to ba
 
 > **Note:**
 >
-
 > Add `Background Modes` in Xcode's `Signing & Capabilities` and check `Audio, AirPlay, and Picture in Picture`.
 >
-
 > Requires iOS 15.0 or later.
 >
 
@@ -1089,7 +1086,6 @@ To ensure your app can capture audio/video while in the background (e.g., screen
 
    > **Note:**
    >
-
    > Call `start()` via MethodChannel at the appropriate time in your app to enable background keep-alive.
    >
 

package/resource/knowledge/callkit/core-sdk/flutter/make-call.md

@@ -340,7 +340,7 @@ Customize your control buttons using [DeviceStore](https://liteav.sdk.qcloud.com
 ### Step 3: Request Microphone/Camera Permissions
 
 Check for audio/video permissions before starting a call. If permissions are missing, prompt users to grant them.
-1. **Declare permissions for Android in **`AndroidManifest.xml`**:**
+1. **Declare permissions for Android in** `AndroidManifest.xml`**:**
 
    ``` xml
    <manifest xmlns:android="http://schemas.android.com/apk/res/android">
@@ -350,7 +350,7 @@ Check for audio/video permissions before starting a call. If permissions are mis
        <uses-permission android:name="android.permission.CAMERA" />
    </manifest>
    ```
-2. **Declare permissions for iOS in **`Info.plist`**:**
+2. **Declare permissions for iOS in** `Info.plist`**:**
 
    ``` xml
    <key>NSCameraUsageDescription</key>
@@ -619,7 +619,6 @@ You can display call duration in real time using [activeCall](https://liteav.sdk
 
    > **Note :**
    >
-
    > For more reactive call state data, see [CallState](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_call_call_store/CallState-class.html).
    >
 
@@ -865,10 +864,8 @@ iOS supports Picture-in-Picture outside the app using the underlying TRTC engine
 
 > **Note：**
 >
-
 > In Xcode, add `Background Modes` under `Signing & Capabilities` and check `Audio, AirPlay, and Picture in Picture`.
 >
-
 > Requires iOS 15.0 or above.
 >
 
@@ -1101,7 +1098,6 @@ Open your project in Xcode and:
 
       > **Note：**
       >
-
       > Call `start()` via `MethodChannel` at the appropriate time to enable background keep-alive.
       >
 

package/resource/knowledge/callkit/core-sdk/flutter/offline-push.md

@@ -12,7 +12,6 @@ Navigate to [Chat Console > App Push > Integration Settings](https://console.trt
 
 > **Note:**
 >
-
 > After the push plugin trial or purchase expires, push services (including offline push for standard messages, broadcast/tag push, etc.) will be automatically disabled. To avoid business interruption, please [purchase](https://buy.intl.cloud.tencent.com/avc) or [renew](https://console.tencentcloud.com/expense/renewal) the service in advance.
 >
 
@@ -98,7 +97,6 @@ public class MyApplication extends TencentCloudChatPushApplication {
 
 > **Note:**
 >
-
 > If you have an existing Application class, simply extend `TencentCloudChatPushApplication` and ensure `onCreate()` calls `super.onCreate();`.
 >
 
@@ -142,7 +140,6 @@ Open `android/app/src/main/AndroidManifest.xml` and add the `android:name` attri
 
    > **Note:**
    >
-
    > Your app's `Bundle ID` cannot use a wildcard `*`; otherwise, remote push will not work.
    >
 
@@ -175,7 +172,6 @@ Open `android/app/src/main/AndroidManifest.xml` and add the `android:name` attri
 
    > **Note:**
    >
-
    > The Production certificate is actually a combined certificate for both Sandbox (Development) and Production environments and can be used for both.
    >
 
@@ -185,7 +181,6 @@ Open `android/app/src/main/AndroidManifest.xml` and add the `android:name` attri
 
    > **Note:**
    >
-
    > Set a password when exporting the `.p12` file.
    >
 
@@ -198,10 +193,10 @@ Open `android/app/src/main/AndroidManifest.xml` and add the `android:name` attri
 
    > **Note:**
    >
->   - Use only English characters for certificate names (avoid brackets or special characters).
->   - You must set a password when uploading the certificate; otherwise, push notifications will not be received.
->   - Certificates for App Store release must be set to Production environment; otherwise, push notifications will not be received.
->   - The uploaded `.p12` certificate must be a valid certificate you applied for.
+   > - Use only English characters for certificate names (avoid brackets or special characters).
+   > - You must set a password when uploading the certificate; otherwise, push notifications will not be received.
+   > - Certificates for App Store release must be set to Production environment; otherwise, push notifications will not be received.
+   > - The uploaded `.p12` certificate must be a valid certificate you applied for.
 
 ### Step 2: Push Parameter Configuration
 

package/resource/knowledge/callkit/core-sdk/ios/answer-call.md

@@ -27,7 +27,6 @@ Visit [Activate the Service](https://trtc.io/document/59832) to obtain either a
 
    > **Tips：**
    >
-
    > **If your project does not have a Podfile:** In your terminal, navigate to your `.xcodeproj` directory and run `pod init` to generate a Podfile.
    >
 
@@ -39,7 +38,6 @@ Visit [Activate the Service](https://trtc.io/document/59832) to obtain either a
 
    > **Tips：**
    >
-
    > After installation, open your project using the `YourProjectName.xcworkspace` file.
    >
 
@@ -111,7 +109,7 @@ class ViewController: UIViewController {
 You need a call screen that appears when a call is received.
 1. **Create the call screen:** Implement a new UIViewController to serve as the call screen. This screen will be presented when an incoming call arrives.
 
-2. **Attach **[CallCoreView](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/)** to the call screen:** This core component observes **CallStore** data, renders video, and supports UI customization for layout, avatars, and icons.
+2. **Attach** [CallCoreView](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/) **to the call screen:** This core component observes **CallStore** data, renders video, and supports UI customization for layout, avatars, and icons.
 
    ``` swift
    import UIKit
@@ -631,7 +629,6 @@ You can display the call duration in real time by subscribing to the [activeCall
 
    > **Note：**
    >
-
    > For more reactive call status data, see [CallState](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstate).
    >
 

package/resource/knowledge/callkit/core-sdk/ios/make-call.md

@@ -27,7 +27,6 @@ Follow the Activate the service guide to obtain either a trial or paid version o
 
    > **Tips：**
    >
-
    > If your project doesn’t have a Podfile, navigate to your `.xcodeproj` directory in the terminal and run `pod init` to create one.
    >
 
@@ -39,7 +38,6 @@ Follow the Activate the service guide to obtain either a trial or paid version o
 
    > **Tips：**
    >
-
    > After installation, open your project using the `YourProjectName.xcworkspace` file.
    >
 
@@ -111,7 +109,7 @@ class ViewController: UIViewController {
 You need to create a call screen that is displayed when a call is initiated.
 1. **Create the call screen:** Implement a new UIViewController to serve as the call interface. This will be used for both outgoing and incoming calls.
 
-2. **Attach **[CallCoreView](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/)**:** Add the core call view component to your call screen. CallCoreView automatically observes **CallStore** data and renders video streams, with options for customizing layout, avatars, and icons.
+2. **Attach** [CallCoreView](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/)**:** Add the core call view component to your call screen. CallCoreView automatically observes **CallStore** data and renders video streams, with options for customizing layout, avatars, and icons.
 
    ``` swift
    import UIKit
@@ -559,7 +557,7 @@ After completing these five steps, the "Make a Call" feature will look like this
 
 ### Customizing Volume Indicator Icons
 
-Use the **CallCoreView**[setVolumeLevelIcons](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setvolumelevelicons(icons:)) method to assign different icons for each volume level.
+Use the **CallCoreView** [setVolumeLevelIcons](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setvolumelevelicons(icons:)) method to assign different icons for each volume level.
 
 ``` swift
 // Set volume indicator icons
@@ -583,7 +581,7 @@ callCoreView.setVolumeLevelIcons(icons: volumeLevelIcons)
 
 ### Customizing Network Indicator Icons
 
-Use the **CallCoreView**[setNetworkQualityIcons](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setnetworkqualityicons(icons:)) method to assign icons for different network states.
+Use the **CallCoreView** [setNetworkQualityIcons](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setnetworkqualityicons(icons:)) method to assign icons for different network states.
 
 ``` swift
 // Set network quality icons
@@ -598,7 +596,7 @@ callCoreView.setNetworkQualityIcons(icons: networkQualityIcons)
 | --- | --- | --- | --- |
 | icons | [NetworkQuality: String] | Yes | Network Quality Icon Mapping Table. The dictionary structure is defined as follows:<br>Key ( NetworkQuality ) : NetworkQuality<br><code>NetworkQuality.unknown</code> ：Network status is undetermined.<br><code>NetworkQuality.excellent</code>：Outstanding network connection.<br><code>NetworkQuality.good</code> : Stable and good network connection.<br><code>NetworkQuality.poor</code> : Weak network signal.<br><code>NetworkQuality.bad</code> : Very weak or unstable network.<br><code>NetworkQuality.veryBad</code> ：Extremely poor network, near disconnection.<br><code>NetworkQuality.down</code> ：Network is disconnected.<br>Value ( String ) : The absolute path or resource name of the icon corresponding to the network status. |
 
-- **Network Warning Icon: **
+- **Network Warning Icon:**
 
 | <strong>Icons</strong> | <strong>Description</strong> |
 | --- | --- |
@@ -606,7 +604,7 @@ callCoreView.setNetworkQualityIcons(icons: networkQualityIcons)
 
 ### Customizing Default Avatars
 
-Use the **CallCoreView**[setParticipantAvatars](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setparticipantavatars(avatars:)) API to set user avatars. Listen to the [allParticipants](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstate/allparticipants) reactive data: when you have a user's avatar, set and display it; if not, show the default avatar.
+Use the **CallCoreView** [setParticipantAvatars](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setparticipantavatars(avatars:)) API to set user avatars. Listen to the [allParticipants](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstate/allparticipants) reactive data: when you have a user's avatar, set and display it; if not, show the default avatar.
 ``` swift
 // Set user avatars
 var avatars: [String: String] = [:]
@@ -630,7 +628,7 @@ callCoreView.setParticipantAvatars(avatars: avatars)
 
 ### Customizing Waiting Animations
 
-Use the **CallCoreView**[setWaitingAnimation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setwaitinganimation(path:)) API to set a waiting animation for users who are waiting to answer.
+Use the **CallCoreView** [setWaitingAnimation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setwaitinganimation(path:)) API to set a waiting animation for users who are waiting to answer.
 
 ``` swift
 // Set waiting animation
@@ -651,7 +649,7 @@ callCoreView.setWaitingAnimation(path: waitingAnimationPath)
 
 ### Adding a Call Duration Indicator
 
-To display the call duration in real time, subscribe to the [activeCall](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstate/activecall)`duration` field.
+To display the call duration in real time, subscribe to the [activeCall](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstate/activecall) `duration` field.
 1. **Subscribe to the data layer:** Observe `CallStore.observerState.activeCall` for changes.
 
 2. **Bind the duration to your UI:** The `activeCall.duration` field is reactive and will automatically update your UI.
@@ -714,7 +712,6 @@ To display the call duration in real time, subscribe to the [activeCall](https:/
 
    > **Note：**
    >
-
    > For more reactive call status data, see [CallState](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstate).
    >
 
@@ -1064,7 +1061,7 @@ AtomicXCore SDK supports system-level PiP via the underlying TRTC engine. When y
        let params: PictureInPictureParams // Parameter payload
    }
    ```
-2. **Enable Picture-in-Picture: **You can enable or disable the PiP feature using the`configPictureInPicture` method.
+2. **Enable Picture-in-Picture:** You can enable or disable the PiP feature using the `configPictureInPicture` method.
 
    ``` swift
    let params = PictureInPictureParams(

package/resource/knowledge/callkit/core-sdk/ios/offline-push.md

@@ -15,11 +15,10 @@ After following this guide to integrate Apple LiveCommunicationKit, your app wil
 
 ## Activate the Service
 
-Go to the [Chat Console > Plugin Marketplace](https://console.trtc.io/) and click ** Purchase Now** or **Free Trial** (each app is eligible for a one-time, 7-day free trial).
+Go to the [Chat Console > Plugin Marketplace](https://console.trtc.io/) and click  **Purchase Now** or **Free Trial** (each app is eligible for a one-time, 7-day free trial).
 
 > **Note：**
 >
-
 > The push plugin will stop providing push services (including offline message push and broadcast/tag push) when your trial or subscription expires. To prevent service interruption, please purchase or renew your subscription in advance.
 >
 
@@ -30,7 +29,7 @@ Go to the [Chat Console > Plugin Marketplace](https://console.trtc.io/) and clic
 Before applying for a VoIP Push certificate, log in to the [Apple Developer Center](https://developer.apple.com/account/) and enable remote push notifications for your app. Once your AppID has Push Notification capability, follow these steps to apply for and configure your VoIP Push certificate:
 1. Log in to the [Apple Developer Center](https://developer.apple.com/account/), click **Certificates, IDs & Profiles** to enter the Certificates, Identifiers & Profiles page.
 
-2. Click the **+ **button next to Certificates.
+2. Click the **+** button next to Certificates.
 
 3. On the **Create a New Certificate** page, select **VoIP Services Certificate** and click **Continue**.
 
@@ -52,7 +51,6 @@ Before applying for a VoIP Push certificate, log in to the [Apple Developer Cent
 
    > **Note：**
    >
-
    > Be sure to set a password when saving the `P12` file.
    >
 
@@ -63,20 +61,19 @@ Before applying for a VoIP Push certificate, log in to the [Apple Developer Cent
 
 2. In **Manufacturer configuration**, switch to **iOS**, click the **Add Certificate** button, then select the certificate type in the floating page, upload the iOS certificate (p12), set the certificate password, and click **Confirm**.
 
-   > **Description****：**
+   > **Description：**
    >
->   - When adding certificates, the push type defaults to APNs, which does not affect the upload and use of VoIP certificates.
->   - VoIP Push certificates themselves do not distinguish between production and testing environments. Production and development environments use the same VoIP Push certificate, please upload separately.
->   - Certificate names uploaded should preferably use all English (especially avoid special characters like parentheses).
->   - Uploaded certificates need to set a password, otherwise push notifications cannot be received.
->   - Certificates for App Store release need to be set to production environment, otherwise push notifications cannot be received.
->   - The uploaded p12 certificate must be a real and valid certificate you applied for yourself.
+   > - When adding certificates, the push type defaults to APNs, which does not affect the upload and use of VoIP certificates.
+   > - VoIP Push certificates themselves do not distinguish between production and testing environments. Production and development environments use the same VoIP Push certificate, please upload separately.
+   > - Certificate names uploaded should preferably use all English (especially avoid special characters like parentheses).
+   > - Uploaded certificates need to set a password, otherwise push notifications cannot be received.
+   > - Certificates for App Store release need to be set to production environment, otherwise push notifications cannot be received.
+   > - The uploaded p12 certificate must be a real and valid certificate you applied for yourself.
 
 3. After upload is complete, record the certificate IDs for different environments.
 
-   > **Description****：**
+   > **Description：**
    >
-
    > Certificate IDs for development and production environments must be strictly distinguished, please fill in according to the actual environment.
    >
 
@@ -88,12 +85,12 @@ Before applying for a VoIP Push certificate, log in to the [Apple Developer Cent
 2. Under Background Modes, enable the **Voice over IP** option.
 
 ### Step 2: Add Dependencies
-1. **Add Pod Dependency: **Add `pod 'TUICore'` to your `Podfile`.
+1. **Add Pod Dependency:** Add `pod 'TUICore'` to your `Podfile`.
 
    ``` ruby
    pod 'TUICore'
    ```
-2. **Install Component: **In your terminal, navigate to your project directory and run:
+2. **Install Component:** In your terminal, navigate to your project directory and run:
 
    ``` bash
    pod install --repo-update
@@ -208,8 +205,8 @@ Before applying for a VoIP Push certificate, log in to the [Apple Developer Cent
 
    > **Note：**
    >
->   - certificateID is the ID you received after uploading your certificate in the Chat Console.
->   - Always use the correct certificate ID for your development or production environment.
+   > - certificateID is the ID you received after uploading your certificate in the Chat Console.
+   > - Always use the correct certificate ID for your development or production environment.
 
 ### Step 4: Obtain and Save VoIP Token
 
@@ -248,7 +245,6 @@ extension VoIPPushManager: PKPushRegistryDelegate {
 
 > **Note：**
 >
-
 > Only report the VoIP Token after the Chat SDK login is successful. Do not report immediately when the token is obtained.
 >
 
@@ -438,14 +434,12 @@ CallStore.shared.calls(
 
    > **Note：**
    >
-
    > **VoIP Push Downgrade Strategy**
    >
-
    > When using VoIP Push, the backend will intelligently select the certificate type to ensure users receive push notifications:
    >
->   - If a VoIP certificate is uploaded: VoIP Push will be sent.
->   - If only an APNs certificate is uploaded: the system will automatically downgrade to APNs Push.
+   > - If a VoIP certificate is uploaded: VoIP Push will be sent.
+   > - If only an APNs certificate is uploaded: the system will automatically downgrade to APNs Push.
 
 ## Answer a Call
 
@@ -514,7 +508,7 @@ class YourViewController: UIViewController {
 
 5. **Restart the test device to clear system cache and memory (this is important).**
 
-6. **Use the **Chat** Console's Push Troubleshooting tool for diagnostics. For details, see: **[**Push Troubleshooting Tool**](https://www.tencentcloud.com/document/product/1047/60541)**. (highly recommended)**
+6. **Use the** Chat **Console's Push Troubleshooting tool for diagnostics. For details, see:** [**Push Troubleshooting Tool**](https://www.tencentcloud.com/document/product/1047/60541)**. (highly recommended)**
 
 ## Why does the app crash after receiving a VoIP Push?
 

package/resource/knowledge/callkit/core-sdk/web/call-engine.md

@@ -0,0 +1,33 @@
+## TUICallEngine APIs
+
+TUICallEngine API is the **No UI Interface** of the Audio and Video Call Components.
+
+## API Overview
+
+|API|Description|
+|---------|---------|
+|[createInstance](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#.createInstance)|Creating a TUICallEngine Instance (Singleton Pattern)|
+|[destroyInstance](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#destroyInstance)|Terminating a TUICallEngine Instance (Singleton Pattern)|
+|[on](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#on)|Listening on events|
+|[off](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#off)|Canceling Event Listening|
+|[login](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#login)|Sign in Interface|
+|[logout](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#logout)|Logout Interface|
+|[setSelfInfo](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setSelfInfo)|Configure the user's nickname and profile photo|
+|[calls](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#calls)|Initiate a one-on-one call|
+|[accept](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#accept)|Answer Calls|
+|[reject](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#reject)|Decline Call|
+|[hangup](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#hangup)|End Calls|
+|[startRemoteView](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#startRemoteView)|Initiate Remote Screen Rendering|
+|[stopRemoteView](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#stopRemoteView)|Stop Remote Screen Rendering|
+|[openCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#openCamera)|Enable the camera|
+|[closeCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#closeCamera)|Turn Off Camera|
+|[switchCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#switchCamera)|Switch between front and rear cameras, note: only supported on mobile devices|
+|[openMicrophone](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#openMicrophone)|Enable Microphone|
+|[closeMicrophone](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#closeMicrophone)|Turn off the microphone|
+|[setVideoQuality](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setVideoQuality)|Set video quality|
+|[getDeviceList](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#getDeviceList)|Access device list|
+|[switchDevice](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#switchDevice)|Switch camera or microphone devices|
+|[enableAIVoice](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#enableAIVoice)|Enable/disable AI noise reduction|
+|[enableMultiDeviceAbility](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#enableMultiDeviceAbility)|Turn on/off the multi-device login mode of TUICallEngine|
+|[setBlurBackground](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setBlurBackground)|Switch/set background blur|
+|[setVirtualBackground](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setVirtualBackground)|Switch/set image background blur|