> For the complete documentation index, see [llms.txt](https://ac.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ac.docs.landis.cloud/appendix/usb-audio-device-call-control-buttons-preview.md).

# USB Audio Device Call Control Buttons (Preview)

USB audio device call control buttons allows the attendant console user to answer, disconnect, mute/unmute, and change volume by using the buttons on the audio device. The button locations may vary by model. Please refer to manufacturer documentation.

Requirements:

* Jabra USB Audio Device (No other brands are supported at this time)

### Enable Device Call Control Buttons:

{% hint style="info" %}
The device buttons cannot be simultaneously enabled for both the Teams desktop client and Attendant Console because the applications will conflict.
{% endhint %}

#### Disable Device Buttons in Teams Desktop Client

1. In the Teams desktop client, open settings | Devices | Disable Sync device buttons

#### Enable Device Buttons in Attendant Console

  1\.  Select the Devices Tab

2. Web browser only: Select Find and pair headsets | Select the headset on the browser notification | Connect

  3\.   Select the Jabra device under Utilize headset buttons

  4\.   Restart or refresh Attendant Console


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ac.docs.landis.cloud/appendix/usb-audio-device-call-control-buttons-preview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.