> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/guides/phone-call-ins-with-vdo-ninja-and-virtual-audio-cables.md).

# Phone call-ins with VDO.Ninja and virtual audio cables

Connect a phone caller and VDO.Ninja guests with mix-minus routing in Voicemeeter, a hardware mixer, or virtual audio cables.

This setup brings a phone caller into a VDO.Ninja show through an external mixer. It works with any phone, softphone, or calling app. To answer calls inside VDO.Ninja instead, see the experimental [call-in panel and provider options](https://docs.vdo.ninja/guides/phone-call-in-provider-options.md).

![Mix-minus routing: the host mic, VDO.Ninja guest and phone caller feed one mixer. The guest receives the host and caller, the caller receives the host and guest, and the program receives everyone.](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-384e09e115f7cfff58ec99a41d574daa7437b585%2Fcallin-mix-minus-routing.svg?alt=media)

## The rule: two separate returns

Everyone needs to hear the other talkers, but never a delayed copy of themselves. That takes two **mix-minus** returns plus your program mix:

| Mix           | Contains               | Leaves out      | Send it to                                   |
| ------------- | ---------------------- | --------------- | -------------------------------------------- |
| Guest return  | Host + phone caller    | VDO.Ninja guest | VDO.Ninja, selected as the host's microphone |
| Caller return | Host + VDO.Ninja guest | Phone caller    | The phone app, softphone, or phone interface |
| Program       | Everyone               | Nobody          | OBS, your stream, or your recorder           |

The most common mistake is sending the program mix back to a guest or caller. That causes echo.

## What you need

* A way to get the call into the computer or mixer: a phone on a mixer input, a softphone or browser calling app, or a USB phone interface.
* The VDO.Ninja guest's audio on the host computer, for example from a view link in Chrome or [Electron Capture](https://docs.vdo.ninja/steves-helper-apps/electron-capture.md).
* A mixer with at least two output buses: Voicemeeter Banana or Potato on Windows, a hardware mixer with custom routing (such as a RØDECaster Pro or Duo), or virtual cables between apps (VB-CABLE, Virtual Audio Cable, Loopback, BlackHole).

## Voicemeeter example

Device names vary by system.

1. Install Voicemeeter Banana or Potato and at least one virtual audio cable.
2. Put the host microphone on a hardware input.
3. Play the VDO.Ninja guest into a virtual cable, then add that cable as a Voicemeeter input. You can set the output in the browser, in Electron Capture, or with [`&audiooutput`](https://docs.vdo.ninja/advanced-settings/setup-parameters/and-audiooutput.md) on the view link.
4. Bring the phone caller in on another input, such as a softphone output, a USB phone channel, or another cable.
5. Make a **guest return** bus with the host mic and caller only. Select it as the microphone on the host's VDO.Ninja page.
6. Make a **caller return** bus with the host mic and guest only. Select it as the microphone in the phone app, or send it to the phone interface.
7. Make a **program** bus with all three and send it to OBS or your recorder.

Because the host's VDO.Ninja microphone is now a finished mix, you can add [`&proaudio`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio.md) to the host link. It turns off the browser's echo cancellation, noise suppression and auto-gain. Use it only with headphones and correct mix-minus routing, because echo cancellation will no longer hide a bad loop.

```
https://vdo.ninja/?room=YourRoomName&label=Host&proaudio
```

## Hardware mixer example

1. Connect the host computer to the mixer over USB.
2. Connect the phone over USB, Bluetooth, or the mixer's phone or TRRS input.
3. Bring the VDO.Ninja guest audio from the computer into its own mixer channel.
4. In the mixer's routing matrix, set the **phone send** to host + guest, the **computer send** (VDO.Ninja) to host + caller, and the **stream send** to everything.

The brand does not matter. What matters is that the phone return and the VDO.Ninja return are different mixes.

## Using OBS for routing

An OBS Browser Source can capture the VDO.Ninja guest for the stream, but OBS has a single audio monitoring device. Two independent returns usually need Voicemeeter, a hardware mixer, or a per-source monitoring plugin. For sending OBS audio into VDO.Ninja through a cable, see [Share audio from OBS](https://docs.vdo.ninja/guides/share-obs-audio-with-vdo-ninja.md).

## Useful VDO.Ninja parameters

| Parameter                                                                                                                                                                                                                                                      | Use                                                                                                                          |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [`&audiooutput`](https://docs.vdo.ninja/advanced-settings/setup-parameters/and-audiooutput.md) (alias `&od`)                                                                                                                                                   | Plays VDO.Ninja audio to a named output device, such as a virtual cable, in browsers that support it.                        |
| [`&proaudio`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio.md)                                                                                                                                                                       | Sends a pre-mixed feed at higher quality without browser processing.                                                         |
| [`&aec=0`](https://docs.vdo.ninja/advanced-settings/audio-parameters/aec.md), [`&denoise=0`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-denoise.md), [`&autogain=0`](https://docs.vdo.ninja/advanced-settings/audio-parameters/autogain.md) | Turn off single processing steps when a mixer already handles them. Keep echo cancellation on if anyone listens on speakers. |
| [`&miconly`](https://docs.vdo.ninja/advanced-settings/setup-parameters/miconly.md)                                                                                                                                                                             | Audio-only host or utility connection.                                                                                       |

## Test before going live

Connect all three parties, then check:

1. When the host speaks, the guest and caller both hear it.
2. When the guest speaks, the host and caller hear it, and the guest hears no delayed copy.
3. When the caller speaks, the host and guest hear it, and the caller hears no delayed copy.
4. The stream or recording contains all three voices.
5. Muting one source removes only that source.

## Troubleshooting

| Symptom                                                         | Likely cause                                                                                                        |
| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| The guest hears the caller, but the caller can't hear the guest | The caller return is missing the guest.                                                                             |
| The caller hears the guest, but the guest can't hear the caller | The host's VDO.Ninja microphone is missing the caller.                                                              |
| Echo                                                            | A return includes the person receiving it, or a microphone picks up a speaker.                                      |
| Crackling or distortion                                         | Virtual cable buffer or sample-rate mismatch. Use 48 kHz where possible and raise the buffer size.                  |
| Audio works in OBS but not in VDO.Ninja                         | The wrong side of the cable is selected. On Windows, apps play to **CABLE Input** and record from **CABLE Output**. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vdo.ninja/guides/phone-call-ins-with-vdo-ninja-and-virtual-audio-cables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
