docs: calls sdk improvements

calls/android/recording.mdx

@@ -18,13 +18,13 @@
 <Tabs>
 <Tab title="Kotlin">
 ```kotlin
 val callSession = CallSession.getInstance()
 callSession.startRecording()
 ```
 </Tab>
 <Tab title="Java">
 ```java
 CallSession callSession = CallSession.getInstance();
 callSession.startRecording();
 ```
 </Tab>
@@ -39,13 +39,13 @@
 <Tabs>
 <Tab title="Kotlin">
 ```kotlin
 val callSession = CallSession.getInstance()
 callSession.stopRecording()
 ```
 </Tab>
 <Tab title="Java">
 ```java
 CallSession callSession = CallSession.getInstance();
 callSession.stopRecording();
 ```
 </Tab>
@@ -58,20 +58,27 @@
 <Tabs>
 <Tab title="Kotlin">
 ```kotlin
 val sessionSettings = CometChatCalls.SessionSettingsBuilder()
     .enableAutoStartRecording(true)
     .build()
 ```
 </Tab>
 <Tab title="Java">
 ```java
 SessionSettings sessionSettings = new CometChatCalls.SessionSettingsBuilder()
     .enableAutoStartRecording(true)
     .build();
 ```
 </Tab>
 </Tabs>
 
+<Note>
+**A recording runs until it is stopped.** Whether it was started manually or automatically through `enableAutoStartRecording`, it keeps running until someone stops it. If nobody does, it stops on its own when either:
+
+- Everyone leaves the session — the recording ends about a minute later.
+- Everyone in the session stays muted for 10 minutes.
+</Note>
+
 ## Hide Recording Button
 
 Hide the recording button from the default call UI:
@@ -79,14 +86,14 @@
 <Tabs>
 <Tab title="Kotlin">
 ```kotlin
 val sessionSettings = CometChatCalls.SessionSettingsBuilder()
     .hideRecordingButton(true)
     .build()
 ```
 </Tab>
 <Tab title="Java">
 ```java
 SessionSettings sessionSettings = new CometChatCalls.SessionSettingsBuilder()
     .hideRecordingButton(true)
     .build();
 ```
@@ -100,7 +107,7 @@
 <Tabs>
 <Tab title="Kotlin">
 ```kotlin
 val callSession = CallSession.getInstance()
 
 callSession.addMediaEventsListener(this, object : MediaEventsListener() {
     override fun onRecordingStarted() {

calls/flutter/recording.mdx

@@ -39,6 +39,13 @@ SessionSettings sessionSettings = CometChatCalls.SessionSettingsBuilder()
     .build();
 ```
 
+<Note>
+**A recording runs until it is stopped.** Whether it was started manually or automatically through `enableAutoStartRecording`, it keeps running until someone stops it. If nobody does, it stops on its own when either:
+
+- Everyone leaves the session — the recording ends about a minute later.
+- Everyone in the session stays muted for 10 minutes.
+</Note>
+
 ## Hide Recording Button
 
 Hide the recording button from the default call UI:

calls/ios/recording.mdx

@@ -23,7 +23,7 @@
 </Tab>
 <Tab title="Objective-C">
 ```objectivec
 [[CallSession shared] startRecording];
 ```
 </Tab>
 </Tabs>
@@ -42,7 +42,7 @@
 </Tab>
 <Tab title="Objective-C">
 ```objectivec
 [[CallSession shared] stopRecording];
 ```
 </Tab>
 </Tabs>
@@ -54,7 +54,7 @@
 <Tabs>
 <Tab title="Swift">
 ```swift
 let sessionSettings = CometChatCalls.sessionSettingsBuilder
     .enableAutoStartRecording(true)
     .build()
 ```
@@ -68,6 +68,13 @@
 </Tab>
 </Tabs>
 
+<Note>
+**A recording runs until it is stopped.** Whether it was started manually or automatically through `enableAutoStartRecording`, it keeps running until someone stops it. If nobody does, it stops on its own when either:
+
+- Everyone leaves the session — the recording ends about a minute later.
+- Everyone in the session stays muted for 10 minutes.
+</Note>
+
 ## Hide Recording Button
 
 Hide the recording button from the default call UI:
@@ -75,7 +82,7 @@
 <Tabs>
 <Tab title="Swift">
 ```swift
 let sessionSettings = CometChatCalls.sessionSettingsBuilder
     .hideRecordingButton(true)
     .build()
 ```

calls/javascript/actions.mdx

@@ -17,9 +17,9 @@
 CometChatCalls.muteAudio();
 ```
 
 ### Unmute Audio
 
 Unmutes your local microphone, resuming audio transmission.
 
 ```javascript
 CometChatCalls.unmuteAudio();
@@ -184,6 +184,10 @@
 CometChatCalls.leaveSession();
 ```
 
+<Note>
+`leaveSession()` takes no session ID. `CometChatCalls` is a singleton that tracks one active session at a time, so this leaves whichever session is currently in progress. The same applies to every action on this page. See [Single Active Session](/calls/javascript/overview#single-active-session).
+</Note>
+
 ## UI Controls
 
 ### Show Settings Dialog

calls/javascript/join-session.mdx

@@ -87,7 +87,7 @@
 |-----------|------|-------------|
 | `callToken` | String | Previously generated call token |
 | `callSettings` | Object | Configuration for the session (see [Session Settings](/calls/javascript/session-settings)) |
 | `container` | HTMLElement | Container element for the call UI |
 
 The method returns an object with:
 
@@ -135,6 +135,21 @@
 All participants joining the same call must use the same session ID.
 </Note>
 
+## One Session at a Time
+
+`CometChatCalls` is a singleton that holds a single active session. Joining a second session while one is in progress is not supported - leave the current session first, wait for `onSessionLeft`, then join the next one.
+
+```javascript
+CometChatCalls.addEventListener("onSessionLeft", async () => {
+  const { token } = await CometChatCalls.generateToken(nextSessionId);
+  await CometChatCalls.joinSession(token, callSettings, container);
+});
+
+CometChatCalls.leaveSession();
+```
+
+This is also why `leaveSession()` and the other [actions](/calls/javascript/actions) take no session ID - they always apply to the session that is currently active. See [Single Active Session](/calls/javascript/overview#single-active-session) for the full behavior.
+
 ## Error Handling
 
 Common errors when joining a session:

calls/javascript/migration-guide-v5.mdx

@@ -26,7 +26,7 @@
 - **Granular event listeners** — subscribe to specific events like `onParticipantJoined` or `onSessionLeft` instead of one monolithic `OngoingCallListener`
 - **Dedicated `login()` method** — the Calls SDK now handles its own authentication instead of depending on the Chat SDK's auth token or REST APIs
 - **Simplified initialization** — pass plain objects to `init()` and `joinSession()` instead of using builder classes
 - **Strongly-typed enums** — `LayoutType`, `SessionType` instead of raw strings
 
 ---
 
@@ -79,9 +79,9 @@
 <Tab title="v4">
 ```javascript
 // No dedicated Calls SDK login — relied on Chat SDK for auth token
 const authToken = CometChat.getUserAuthToken();
 
 // Had to pass authToken manually
 CometChatCalls.generateToken(sessionId, authToken).then(
   (token) => { /* use token to start session */ },
   (error) => { }
@@ -118,7 +118,7 @@
 <Tabs>
 <Tab title="v4">
 ```javascript
 const callSettings = new CometChatCalls.CallSettingsBuilder()
   .enableDefaultLayout(true)
   .setIsAudioOnlyCall(true)
   .showEndCallButton(true)
@@ -135,15 +135,15 @@
     onCallEndButtonPressed: () => { },
     onUserJoined: (user) => { },
     onUserLeft: (user) => { },
     onUserListUpdated: (userList) => { },
     onError: (error) => { },
   }))
   .build();
 ```
 </Tab>
 <Tab title="v5">
 ```javascript
 const sessionSettings = {
   sessionType: "VIDEO",       // or "VOICE"
   layout: "TILE",             // or "SPOTLIGHT", "SIDEBAR"
   startAudioMuted: false,
@@ -209,6 +209,20 @@
 
 Static methods remain on `CometChatCalls` but some have been renamed.
 
+<Note>
+**Boolean toggles are now paired methods.** In v4, `muteAudio()` took a boolean: `muteAudio(true)` muted the mic and `muteAudio(false)` unmuted it. In v5 these are two separate, argument-free methods — replace `muteAudio(true)` with `muteAudio()` and `muteAudio(false)` with `unmuteAudio()`. The same split applies to `pauseVideo(true)` / `pauseVideo(false)`, which become `pauseVideo()` and `resumeVideo()`.
+</Note>
+
+```javascript
+// v4
+CometChatCalls.muteAudio(true);   // mute
+CometChatCalls.muteAudio(false);  // unmute
+
+// v5
+CometChatCalls.muteAudio();       // mute
+CometChatCalls.unmuteAudio();     // unmute
+```
+
 | v4 Method | v5 Method |
 |---|---|
 | `CometChatCalls.endSession()` | `CometChatCalls.leaveSession()` |
@@ -289,6 +303,24 @@
 `addEventListener()` returns an unsubscribe function. Call it to remove the listener. You can also pass an `AbortSignal` for cleanup.
 </Note>
 
+### New Events Require `addEventListener()`
+
+The events introduced in v5 are only delivered through `addEventListener()`. None of the v4 registration paths — `setCallListener()` / `setCallEventListener()` on `CallSettingsBuilder` and `CometChatCalls.addCallEventListener(name, listener)` — will ever fire them, because `OngoingCallListener` only carries the legacy v4 event set. Events such as `onSessionJoined`, `onConnectionLost`, `onLeaveSessionButtonClicked`, and `onCallLayoutChanged` are unreachable from a v4 listener no matter how it is registered.
+
+You don't have to migrate everything at once. `addEventListener()` works alongside an existing v4 listener without breaking it — keep your current `OngoingCallListener` for the legacy events and add `addEventListener()` subscriptions for the new ones.
+
+```javascript
+// Existing v4 listener keeps working
+CometChatCalls.addCallEventListener("MY_LISTENER", new CometChatCalls.OngoingCallListener({
+  onCallEnded: () => { },
+  onUserJoined: (user) => { },
+}));
+
+// Add v5-only events alongside it
+CometChatCalls.addEventListener("onConnectionLost", () => { });
+CometChatCalls.addEventListener("onCallLayoutChanged", (layoutType) => { });
+```
+
 ### Event Mapping
 
 | v4 Event | v5 Event |

calls/javascript/overview.mdx

@@ -45,7 +45,7 @@
 | Samsung Internet | ✅ Full support |
 
 <Note>
 For native mobile apps, consider using the [iOS](/calls/ios/overview) or [Android](/calls/android/overview) SDKs for better performance and native features like CallKit/VoIP.
 </Note>
 
 ## Framework Integrations
@@ -59,7 +59,7 @@
 </Card>
 
 <Card title="Vue" icon="vuejs" href="/calls/javascript/vue-integration">
   Composables and reactive state management
 </Card>
 
 <Card title="Angular" icon="angular" href="/calls/javascript/angular-integration">
@@ -142,6 +142,40 @@
 | `CallSettings` | Configuration object for individual call sessions |
 | `addEventListener` | Method to register event listeners for session, participant, media, and UI events |
 
+## Single Active Session
+
+`CometChatCalls` is a singleton, and it tracks one active call session at a time. Every session method acts on that current session, which is why methods like `leaveSession()` take no session ID:
+
+```javascript
+// Joins and becomes the active session
+await CometChatCalls.joinSession(callToken, callSettings, container);
+
+// Acts on whatever session is currently active - no session ID needed
+CometChatCalls.leaveSession();
+```
+
+| Behavior | Detail |
+|----------|--------|
+| One session at a time | The SDK does not support being connected to two sessions simultaneously. Leave the current session before joining another. |
+| Session methods take no session ID | `leaveSession()` and the other [actions](/calls/javascript/actions) apply to the active session only. |
+| Actions apply to the active session | `muteAudio()`, `pauseVideo()`, `startScreenShare()`, and similar methods target the session currently in progress. |
+| Events are not session-scoped | Listeners registered with `addEventListener` fire for the active session. |
+
+To move a user from one call to another, leave the current session, wait for the `onSessionLeft` event, then generate a token for the new session and join:
+
+```javascript
+CometChatCalls.addEventListener("onSessionLeft", async () => {
+  const { token } = await CometChatCalls.generateToken(nextSessionId);
+  await CometChatCalls.joinSession(token, callSettings, container);
+});
+
+CometChatCalls.leaveSession();
+```
+
+<Note>
+The limit applies per SDK instance. Separate browser tabs or windows each load their own instance, so they can hold separate sessions independently.
+</Note>
+
 ## Sample App
 
 <CardGroup cols={3}>

calls/javascript/recording.mdx

@@ -42,6 +42,13 @@ Stop the current recording:
 CometChatCalls.stopRecording();
 ```
 
+<Note>
+**A recording runs until it is stopped.** Whether it was started manually or automatically through `autoStartRecording`, it keeps running until someone stops it. If nobody does, it stops on its own when either:
+
+- Everyone leaves the session — the recording ends about a minute later.
+- Everyone in the session stays muted for 10 minutes.
+</Note>
+
 ## Recording Events
 
 ### Recording Started

calls/react-native/actions.mdx

@@ -17,9 +17,9 @@
 CometChatCalls.muteAudio();
 ```
 
 ### Unmute Audio
 
 Unmute the local user's microphone:
 
 ```tsx
 CometChatCalls.unmuteAudio();
@@ -65,6 +65,10 @@
 The `leaveSession()` method ends the call for the local user. Other participants will remain in the call unless they also leave.
 </Note>
 
+<Note>
+`leaveSession()` takes no session ID. `CometChatCalls` is a singleton that tracks one active session at a time, so this leaves whichever session is currently in progress. The same applies to every action on this page. See [Single Active Session](/calls/react-native/overview#single-active-session).
+</Note>
+
 ## Raise Hand
 
 ### Raise Hand

calls/react-native/join-session.mdx

@@ -282,6 +282,21 @@ const styles = StyleSheet.create({
 export default CallScreen;
 ```
 
+## One Session at a Time
+
+`CometChatCalls` is a singleton that holds a single active session. Render one `CometChatCalls.Component` at a time - joining a second session while one is in progress is not supported. Leave the current session first, wait for `onSessionLeft`, then join the next one.
+
+```tsx
+CometChatCalls.addEventListener('onSessionLeft', async () => {
+  const { token } = await CometChatCalls.generateToken(nextSessionId);
+  setCallToken(token); // Re-renders the component with the new session
+}, { signal });
+
+CometChatCalls.leaveSession();
+```
+
+This is also why `leaveSession()` and the other [actions](/calls/react-native/actions) take no session ID - they always apply to the session that is currently active. See [Single Active Session](/calls/react-native/overview#single-active-session) for the full behavior.
+
 ## Error Handling
 
 Common errors when joining a session:

calls/react-native/migration-guide-v5.mdx

@@ -26,7 +26,7 @@
 - **Granular event listeners** — subscribe to specific events like `onParticipantJoined` or `onSessionLeft` instead of one monolithic `OngoingCallListener`
 - **Dedicated `login()` method** — the Calls SDK now handles its own authentication instead of depending on the Chat SDK's auth token or REST APIs
 - **Simplified initialization** — pass plain objects to `init()` instead of using builder classes
 - **Strongly-typed enums** — `LayoutType`, `SessionType` instead of raw strings
 
 ---
 
@@ -79,9 +79,9 @@
 <Tab title="v4">
 ```javascript
 // No dedicated Calls SDK login — relied on Chat SDK for auth token
 const authToken = CometChat.getUserAuthToken();
 
 // Had to pass authToken manually
 CometChatCalls.generateToken(sessionId, authToken).then(
   (token) => { /* use token to start session */ },
   (error) => { }
@@ -120,7 +120,7 @@
 <Tabs>
 <Tab title="v4">
 ```javascript
 const callSettings = new CometChatCalls.CallSettingsBuilder()
   .enableDefaultLayout(true)
   .setIsAudioOnlyCall(true)
   .showEndCallButton(true)
@@ -135,15 +135,15 @@
     onCallEndButtonPressed: () => { },
     onUserJoined: (user) => { },
     onUserLeft: (user) => { },
     onUserListUpdated: (userList) => { },
     onError: (error) => { },
   }))
   .build();
 ```
 </Tab>
 <Tab title="v5">
 ```javascript
 const sessionSettings = {
   sessionType: "VIDEO",       // or "VOICE"
   layout: "TILE",             // or "SIDEBAR" or "SPOTLIGHT"
   startAudioMuted: false,
@@ -212,6 +212,20 @@
 
 Static methods remain on `CometChatCalls` but some have been renamed.
 
+<Note>
+**Boolean toggles are now paired methods.** In v4, `muteAudio()` took a boolean: `muteAudio(true)` muted the mic and `muteAudio(false)` unmuted it. In v5 these are two separate, argument-free methods — replace `muteAudio(true)` with `muteAudio()` and `muteAudio(false)` with `unmuteAudio()`. The same split applies to `pauseVideo(true)` / `pauseVideo(false)`, which become `pauseVideo()` and `resumeVideo()`.
+</Note>
+
+```javascript
+// v4
+CometChatCalls.muteAudio(true);   // mute
+CometChatCalls.muteAudio(false);  // unmute
+
+// v5
+CometChatCalls.muteAudio();       // mute
+CometChatCalls.unmuteAudio();     // unmute
+```
+
 | v4 Method | v5 Method |
 |---|---|
 | `CometChatCalls.endSession()` | `CometChatCalls.leaveSession()` |
@@ -290,6 +304,24 @@
 `addEventListener()` returns an unsubscribe function. Call it to remove the listener.
 </Note>
 
+### New Events Require `addEventListener()`
+
+The events introduced in v5 are only delivered through `addEventListener()`. Neither of the v4 registration paths — `setCallEventListener()` on `CallSettingsBuilder` and `CometChatCalls.addCallEventListener(name, listener)` — will ever fire them, because `OngoingCallListener` only carries the legacy v4 event set. Events such as `onSessionJoined`, `onConnectionLost`, `onLeaveSessionButtonClicked`, and `onCallLayoutChanged` are unreachable from a v4 listener no matter how it is registered.
+
+You don't have to migrate everything at once. `addEventListener()` works alongside an existing v4 listener without breaking it — keep your current `OngoingCallListener` for the legacy events and add `addEventListener()` subscriptions for the new ones.
+
+```javascript
+// Existing v4 listener keeps working
+CometChatCalls.addCallEventListener("MY_LISTENER", new CometChatCalls.OngoingCallListener({
+  onCallEnded: () => { },
+  onUserJoined: (user) => { },
+}));
+
+// Add v5-only events alongside it
+CometChatCalls.addEventListener("onConnectionLost", () => { });
+CometChatCalls.addEventListener("onCallLayoutChanged", (layoutType) => { });
+```
+
 ### Event Mapping
 
 | v4 Event | v5 Event |

calls/react-native/overview.mdx

@@ -14,9 +14,9 @@
 1. **CometChat Account**: [Sign up](https://app.cometchat.com/signup) and create an app to get your App ID, Region, and API Key
 2. **CometChat Users**: Users must exist in CometChat to use calling features. For testing, create users via the [Dashboard](https://app.cometchat.com) or [REST API](/rest-api/users/create). Authentication is handled by the Calls SDK - see [Authentication](/calls/react-native/authentication)
 3. **React Native Requirements**:
-   - React Native 0.71 or later
+   - React Native 0.71 or later (works with both the old architecture and the [New Architecture](/calls/react-native/setup#react-native-new-architecture), including bridgeless mode)
    - Node.js 18 or later
    - iOS: Minimum iOS 13.0, Xcode 14.0+
    - Android: Minimum SDK API Level 24 (Android 7.0)
 4. **Permissions**: Camera and microphone permissions for video/audio calls
 
@@ -95,6 +95,34 @@
 | `CometChatCalls.Component` | React component that renders the call UI |
 | `CometChatCalls.addEventListener` | Subscribe to call events; returns an unsubscribe function |
 
+## Single Active Session
+
+`CometChatCalls` is a singleton, and it tracks one active call session at a time. Every session method acts on that current session, which is why methods like `leaveSession()` take no session ID:
+
+```tsx
+// Acts on whatever session is currently active - no session ID needed
+CometChatCalls.leaveSession();
+```
+
+| Behavior | Detail |
+|----------|--------|
+| One session at a time | The SDK does not support being connected to two sessions simultaneously. Leave the current session before joining another. |
+| One `Component` at a time | Render a single `CometChatCalls.Component` for the active call. Mounting two at once is not supported. |
+| Session methods take no session ID | `leaveSession()` and the other [actions](/calls/react-native/actions) apply to the active session only. |
+| Actions apply to the active session | `muteAudio()`, `pauseVideo()`, `switchCamera()`, and similar methods target the session currently in progress. |
+| Events are not session-scoped | Listeners registered with `addEventListener` fire for the active session. |
+
+To move a user from one call to another, leave the current session, wait for the `onSessionLeft` event, then generate a token for the new session and render the component with the new token:
+
+```tsx
+CometChatCalls.addEventListener('onSessionLeft', async () => {
+  const { token } = await CometChatCalls.generateToken(nextSessionId);
+  setCallToken(token); // Re-renders CometChatCalls.Component with the new session
+}, { signal });
+
+CometChatCalls.leaveSession();
+```
+
 ## Related Documentation
 
 - [Setup](/calls/react-native/setup) - Install and configure the SDK

calls/react-native/recording.mdx

@@ -46,6 +46,13 @@ Stop an active recording:
 CometChatCalls.stopRecording();
 ```
 
+<Note>
+**A recording runs until it is stopped.** Whether it was started manually or automatically through `autoStartRecording`, it keeps running until someone stops it. If nobody does, it stops on its own when either:
+
+- Everyone leaves the session — the recording ends about a minute later.
+- Everyone in the session stays muted for 10 minutes.
+</Note>
+
 ## Recording Events
 
 Listen for recording state changes:

calls/react-native/setup.mdx

@@ -59,6 +59,14 @@
 yarn add @react-native-async-storage/async-storage@^2.1.2 react-native-background-timer@^2.4.1 react-native-performance@^5.1.2 react-native-svg@^15.12.0 react-native-url-polyfill@2.0.0 react-native-webrtc@124.0.7
 ```
 
+## React Native New Architecture
+
+The Calls SDK works with both the old architecture and the New Architecture, including bridgeless mode. No extra setup is needed — leave `newArchEnabled` set to whatever your app requires and follow the same integration steps either way.
+
+<Note>
+The SDK ships as a legacy native module rather than a TurboModule/Fabric component. On the New Architecture it runs through React Native's built-in interop layer, so the API and behavior are identical on both architectures.
+</Note>
+
 ## iOS Configuration
 
 ### Install CocoaPods Dependencies
@@ -86,7 +94,7 @@
 
 For calls to continue when the app is in the background:
 
 1. Open your project in Xcode
 2. Select your target and go to **Signing & Capabilities**
 3. Click **+ Capability** and add **Background Modes**
 4. Enable:

calls/v4/android/call-logs.mdx

@@ -2,9 +2,17 @@
 title: "Call Logs"
 sidebarTitle: "Call Logs"
 sdk_version: "4.x"
-description: "CometChat Calling SDK v4 - Stable Release - Call Logs for Android"
+description: "CometChat Calling SDK v4 - Legacy Release - Call Logs for Android"
 ---
 
+<Warning>
+**You're reading the legacy documentation for Calling SDK v4 (Android).**
+
+Follow this page only if your app is on **v4.x**. If you're using v5, see the [**Calling SDK v5 documentation**](/calls/android/overview) instead.
+
+Ready to move off v4? Follow the [v4 → v5 migration guide](/calls/android/migration-guide-v5).
+</Warning>
+
 ## Overview
 
 CometChat's Android Call SDK provides a comprehensive way to integrate call logs into your application, enhancing your user experience by allowing users to effortlessly keep track of their communication history. Call logs provide crucial information such as call duration, participants, and more.
@@ -32,12 +40,12 @@
 | `setLimit(int limit)`                                                         | Specifies the number of call logs to fetch.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 | `setCallType(@CometChatCallsConstants.CallType String callType)`              | Sets the type of calls to fetch (audio or video). It accepts `CallType` Enum with following values `CometChatCallsConstants.CallType.CALL_TYPE_VIDEO`, `CometChatCallsConstants.CallType.CALL_TYPE_AUDIO` & `CometChatCallsConstants.CallType.CALL_TYPE_AUDIO_VIDEO`                                                                                                                                                                                                                                                                                                                              |
 | `setCallStatus(@CometChatCallsConstants.CallStatus String callStatus)`        | Sets the status of calls to fetch (initiated, ongoing, etc.). It accepts `CallStatus` Enum with following values `CometChatCallsConstants.CallStatus.CALL_STATUS_ONGOING`, `CometChatCallsConstants.CallStatus.CALL_STATUS_BUSY`, `CometChatCallsConstants.CallStatus.CALL_STATUS_REJECTED`, `CometChatCallsConstants.CallStatus.CALL_STATUS_CANCELLED`, `CometChatCallsConstants.CallStatus.CALL_STATUS_ENDED`, `CometChatCallsConstants.CallStatus.CALL_STATUS_MISSED`, `CometChatCallsConstants.CallStatus.CALL_STATUS_INITIATED`, `CometChatCallsConstants.CallStatus.CALL_STATUS_UNANSWERED` |
 | setHasRecording(boolean hasRecording)                                         | Sets whether to fetch calls that have recordings.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
 | setCallCategory(@CometChatCallsConstants.CallLogCategory String callCategory) | Sets the category of calls to fetch (call or meet). It accepts `CallLogCategory` Enum with following values `CometChatCallsConstants.CallLogCategory.CALL_CATEGORY_CALL` & `CometChatCallsConstants.CallLogCategory.CALL_CATEGORY_MEET`                                                                                                                                                                                                                                                                                                                                                           |
 | setCallDirection(@CometChatCallsConstants.CallDirection String callDirection) | Sets the direction of calls to fetch. It accepts `CallDirection` Enum with following values `CometChatCallsConstants.CallDirection.CALL_DIRECTION_INCOMING` & `CometChatCallsConstants.CallDirection.CALL_DIRECTION_OUTGOING`                                                                                                                                                                                                                                                                                                                                                                     |
 | setUid(String uid)                                                            | Sets the UID of the user whose call logs to fetch.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | setGuid(String guid)                                                          | Sets the GUID of the user whose call logs to fetch.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
 | setAuthToken(String authToken)                                                | Sets the Auth token of the logged-in user.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 
 ### Fetch Next
 

calls/v4/android/call-session.mdx

@@ -2,9 +2,17 @@
 title: "Call Session"
 sidebarTitle: "Call Session"
 sdk_version: "4.x"
-description: "CometChat Calling SDK v4 - Stable Release - Call Session for Android"
+description: "CometChat Calling SDK v4 - Legacy Release - Call Session for Android"
 ---
 
+<Warning>
+**You're reading the legacy documentation for Calling SDK v4 (Android).**
+
+Follow this page only if your app is on **v4.x**. If you're using v5, see the [**Calling SDK v5 documentation**](/calls/android/overview) instead.
+
+Ready to move off v4? Follow the [v4 → v5 migration guide](/calls/android/migration-guide-v5).
+</Warning>
+
 ## Overview
 
 This section demonstrates how to start a call session in an Android application. Previously known as **Direct Calling**.
@@ -28,7 +36,7 @@
 <Tabs>
 <Tab title="Java">
 ```java
 String sessionId = "" //Random or available in call obecjt in case of default calling
 String userAuthToken = CometChat.getUserAuthToken() //Logged in user auth token
 
 CometChatCalls.generateToken(sessionId, userAuthToken, new CometChatCalls.CallbackListener<GenerateToken>() {
@@ -85,21 +93,21 @@
 | ------------------ | ------------------------------------------------------------------------ |
 | `activityContext`  | The activity context where the call UI will be displayed                 |
 | `videoContainer`   | A `RelativeLayout` where the calling UI will be rendered                 |
 | `callToken`        | The `GenerateToken` object received from `generateToken()` onSuccess     |
 
 <Tabs>
 <Tab title="Java">
 ```java
 RelativeLayout videoContainer = findViewById(R.id.video_container);
 Context activityContext = this;
 GenerateToken callToken; // Received from generateToken() onSuccess
 
 CallSettings callSettings = new CometChatCalls.CallSettingsBuilder(activityContext, videoContainer)
     .setDefaultLayoutEnable(true)
     .setIsAudioOnly(false)
     .build();
 
 CometChatCalls.startSession(callToken, callSettings, new CometChatCalls.CallbackListener<String>() {
     @Override
     public void onSuccess(String s) {
         // Call session started successfully
@@ -178,9 +186,9 @@
 <Tabs>
 <Tab title="Java">
 ```java
 private String listenerId = "UNIQUE_LISTENER_ID";
 
 // Register listener (e.g., in onCreate or onResume)
 CometChatCalls.addCallsEventListeners(listenerId, new CometChatCallsEventsListener() {
     @Override
     public void onCallEnded() {
@@ -238,7 +246,7 @@
     }
 });
 
 // Unregister listener (e.g., in onDestroy or onPause)
 CometChatCalls.removeCallsEventListeners(listenerId);
 ```
 
@@ -469,7 +477,7 @@
 Controls the local audio stream transmission. When muted, other participants cannot hear the local user.
 
 - `true` — Mutes the microphone, stops transmitting audio
 - `false` — Unmutes the microphone, resumes audio transmission
 
 <Tabs>
 <Tab title="Java">
@@ -525,7 +533,7 @@
 <Tabs>
 <Tab title="Java">
 ```java
 String audioMode = CometChatCallsConstants.AUDIO_MODE_EARPIECE;
 CometChatCalls.setAudioMode(audioMode);
 ```
 
@@ -533,7 +541,7 @@
 
 <Tab title="Kotlin">
 ```kotlin
 val audioMode = CometChatCallsConstants.AUDIO_MODE_EARPIECE
 CometChatCalls.setAudioMode(audioMode)
 ```
 

calls/v4/android/overview.mdx

@@ -2,12 +2,16 @@
 title: "Calling SDK"
 sidebarTitle: "Overview"
 sdk_version: "4.x"
-description: "CometChat Calling SDK v4 - Stable Release - Overview for Android. This is the stable v4 documentation. Most users should use this version."
+description: "CometChat Calling SDK v4 - Legacy Release - Overview for Android. This is the legacy v4 documentation. Most users should use v5, the current stable version."
 ---
 
-<Note>
-🚀 **v5 Beta Available** — The Calling SDK v5 is now available in beta with significant improvements. [Check out the v5 docs →](/calls/android/overview)
-</Note>
+<Warning>
+**You're reading the legacy documentation for Calling SDK v4 (Android).**
+
+Follow this page only if your app is on **v4.x**. If you're using v5, see the [**Calling SDK v5 documentation**](/calls/android/overview) instead.
+
+Ready to move off v4? Follow the [v4 → v5 migration guide](/calls/android/migration-guide-v5).
+</Warning>
 
 ## Overview