docs: add outbound calling guide

fern/docs.yml

@@ -196,6 +196,12 @@ css:
   - components/sigmond-card/styles.css
 
 redirects:
+  # Browser SDK outbound guide consolidated into the platform outbound calling
+  # guide, which now carries the browser walkthrough and media options.
+  - source: /docs/browser-sdk/guides/outbound-calls
+    destination: /docs/platform/voice/outbound-calling
+  - source: /docs/browser-sdk/v4/guides/outbound-calls
+    destination: /docs/platform/voice/outbound-calling
   # Legacy Agents SDK pages (#526). Use known paths and equivalent existing
   # content only. Exact entries prevent unknown or removed pages (examples,
   # best-practices, patterns, migration, changelog) from redirecting to an
@@ -534,6 +540,12 @@ redirects:
   - source: /docs/platform/ai/prompt-engineering/where-to-apply
     destination: /docs/platform/ai/prompt-engineering
 
+  # The VAPI inbound and outbound guides were merged into one integration guide.
+  - source: /docs/platform/ai/vapi/inbound
+    destination: /docs/platform/ai/vapi
+  - source: /docs/platform/ai/vapi/outbound
+    destination: /docs/platform/ai/vapi
+
   # SWML methods reorganized into calling/ and messaging/ subsections.
   # The old methods overview lived at /docs/swml/reference, which was
   # entirely calling-flavored — point it at the new calling overview.

fern/llms.txt

@@ -76,14 +76,14 @@ Send text and media messages from your application, and choose how to process in
 
 Give users an identity, authorize their access, and connect them to other users or shared resources. Your backend manages subscribers and credentials; the client provides the calling and chat interface.
 
-- Browser SDK: For web clients, [place audio or video calls](/docs/browser-sdk/v4/guides/outbound-calls) and [send and display chat messages](/docs/browser-sdk/v4/guides/messaging-chat).
+- Browser SDK: For web clients, [place audio or video calls](/docs/platform/voice/outbound-calling) and [send and display chat messages](/docs/browser-sdk/v4/guides/messaging-chat).
 - REST APIs: [Create subscribers](/docs/apis/rest/subscribers/create-subscriber) and [issue subscriber access tokens](/docs/apis/rest/subscribers/tokens/create-subscriber-token) from your backend. Follow the [Browser SDK authentication guide](/docs/browser-sdk/v4/guides/authentication) to connect a web client.
 
 ### Video conferences
 
 Build a browser conference interface or use a conference with a prebuilt interface. The [platform video overview](/docs/platform/video) explains rooms, participant permissions, and recordings.
 
-- Browser SDK: [Join a room with audio and video](/docs/browser-sdk/v4/guides/outbound-calls), then add [call controls](/docs/browser-sdk/v4/guides/call-controls), [screen sharing](/docs/browser-sdk/v4/guides/screen-sharing), and [participant layouts](/docs/browser-sdk/v4/guides/layouts).
+- Browser SDK: [Join a room with audio and video](/docs/browser-sdk/v4/guides/build-voice-video), then add [call controls](/docs/browser-sdk/v4/guides/call-controls), [screen sharing](/docs/browser-sdk/v4/guides/screen-sharing), and [participant layouts](/docs/browser-sdk/v4/guides/layouts).
 - REST APIs: [Create a video room](/docs/apis/rest/video/rooms/create-room) and [issue room access tokens](/docs/apis/rest/video/room-tokens/create-room-token), or [create a video conference with a prebuilt interface](/docs/apis/rest/video/video-conferences/create-video-conference).
 
 ### Migrate a Twilio application

fern/products/browser-sdk/pages/v4/guides/build-voice-video/call-controls.mdx

@@ -24,7 +24,7 @@ instance — get one of these going first.
   <Card title="Set up the client" icon="fa-regular fa-rocket" href="/docs/browser-sdk/v4/guides/overview">
     Install the SDK and create a `SignalWire` client with a credential provider.
   </Card>
-  <Card title="Place an outbound call" icon="fa-regular fa-phone-arrow-up-right" href="/docs/browser-sdk/v4/guides/outbound-calls">
+  <Card title="Place an outbound call" icon="fa-regular fa-phone-arrow-up-right" href="/docs/platform/voice/outbound-calling">
     Dial a destination with `client.dial()` to get a `Call` instance.
   </Card>
   <Card title="Answer an inbound call" icon="fa-regular fa-phone-arrow-down-left" href="/docs/browser-sdk/v4/guides/inbound-calls">

fern/products/browser-sdk/pages/v4/guides/build-voice-video/device-management.mdx

@@ -448,7 +448,7 @@ Pick a different mic, camera, or speaker before dialing. The log records each pi
 
 ### Switch a device mid-call
 
-Enter a destination in the **Destination** field (a `/public/<resource>`, `/private/<user>`, PSTN number, or SIP URI the token can reach — see [Outbound Calls](/docs/browser-sdk/v4/guides/outbound-calls#pick-a-destination) for the destination shapes) and click **Dial**. The local and remote tiles populate once the call connects.
+Enter a destination in the **Destination** field (a `/public/<resource>`, `/private/<user>`, PSTN number, or SIP URI the token can reach — see [Outbound calling](/docs/platform/voice/outbound-calling#choose-a-destination) for the destination shapes) and click **Dial**. The local and remote tiles populate once the call connects.
 
 With the call connected, change the **Microphone** or **Camera** dropdown again. The log now records the change as `live: …` — the picker is routing through `activeCall.self.selectAudioInputDevice()` instead of the client-level preference, and the remote side hears or sees the new device immediately without renegotiation. Picking a new **Speaker** triggers `applySelectedAudioOutputDevice()` on the remote `<video>` element so the sink swaps too.