Global meeting, collaboration and enterprise telephony platforms. Choose a platform and validate the RHITOR connection for your workstation.
View model compatibilityThe guidance below describes connection conditions, not certification of every RHITOR model and platform combination. Core audio is available when the operating system recognizes the microphone and speakers and the application allows users to select them.
Meetings, calling and collaboration across the Microsoft ecosystem.
Select the RHITOR headset as the microphone and speaker in device settings. Validate call controls separately for your client version.
Video meetings and remote collaboration for distributed teams.
Select the headset in Audio settings and run a test call. For Bluetooth, confirm the voice profile and microphone quality.
Browser-based and app-based video meetings in the Google ecosystem.
Select the headset microphone and speakers in meeting settings and allow browser microphone access.
Enterprise video communications and online meetings.
Choose the headset as the input and output device in Audio settings and use computer audio when joining a meeting.
RHITOR evaluates integration scenarios with widely used enterprise infrastructure. A brand listed here identifies a validation path and does not by itself imply a commercial partnership or certification.
CONTACT headsets can connect to supported desk phones through a validated QD bottom cable. USB and Bluetooth options depend on the exact phone model.
Phone model, headset port, pinout, microphone level and call control.
Cisco phones may offer analog headset ports, USB or Bluetooth depending on the series. Select the RHITOR connection for the exact device.
Phone port, USB audio support, QD bottom cable and hardware controls.
OpenScape Desk Phone models can provide wired headset ports, USB or Bluetooth. CONTACT, OFFICE and AIR models are validated on the available interface.
CP model, selected headset type, USB or Bluetooth support and audio-device priority.
Core audio works through the operating system input and output devices. Microphone selection, playback, mute and call controls are validated separately.
RHITOR does not claim Microsoft Teams certification; certification and core audio compatibility are different levels.
The headset operates as a computer audio device in desktop or web clients. USB, Bluetooth and QD-to-USB configurations are validated in the working application.
Audio-device selection, browser permissions, HID controls, mute and reconnection.
The microphone and speakers are available to the system or desk phone.
Mute, volume, call controls, indicators and reconnection are tested.
A separate official platform program, claimed only after successful completion.
OFFICE models use USB, CONTACT models use a validated QD-to-USB adapter, and AIR models use Bluetooth or a DECT base audio connection.
On Windows, macOS and Linux, validate client version, device detection, permissions and hardware controls.
PBX compatibility and headset-to-phone compatibility are separate checks. QD requires the exact phone model, a matching bottom cable and the correct pinout.
DECT remote answering may require a supported base and EHS cable. A charging station does not replace an audio adapter.
Compatibility depends on the headset model, operating-system version, audio stack, Bluetooth adapter and corporate application.
Validate USB audio detection, Bluetooth voice profiles, microphone permissions and call controls.
Validate at the workstationSelect the headset for input and output, then test mute, volume and reconnection in the application.
Validate at the workstationValidate USB Audio support, microphone permissions, the Bluetooth adapter and the selected voice profile.
Validate at the workstationAllow microphone access and select the same headset for input and output before the meeting.
Validate at the workstationThe configuration must operate as an audio device in your environment. Results depend on the client, version and workstation.
| Model | Connection | Conditions |
|---|---|---|
| OFFICE START 4220USB | USB to desktop or laptop | The operating system must recognize the headset as an input and output device. Then select it in the UC application. |
| OFFICE PRO 5220USB | USB to desktop or laptop | The operating system must recognize the headset as an input and output device. Then select it in the UC application. |
| AIR BT30Bluetooth | Bluetooth to computer or smartphone | The device and operating system must support a Bluetooth voice profile. Validate simultaneous microphone and playback operation in a call. |
| AIR BT35Bluetooth | Bluetooth to computer or smartphone | The device and operating system must support a Bluetooth voice profile. Validate simultaneous microphone and playback operation in a call. |
| AIR BT40Bluetooth | Bluetooth to computer or smartphone | The device and operating system must support a Bluetooth voice profile. Validate simultaneous microphone and playback operation in a call. |
| AIR BT60 PROBluetooth | Bluetooth to computer or smartphone | The device and operating system must support a Bluetooth voice profile. Validate simultaneous microphone and playback operation in a call. |
| CONTACT 410QD | QD → USB adapter → computer, or QD → dedicated cable → desk phone | Use CONTACT CAB4 USB or CAB7 USB for computers. Desk phones require a bottom cable with the correct connector, pinout and electrical characteristics. |
| CONTACT 510QD | QD → USB adapter → computer, or QD → dedicated cable → desk phone | Use CONTACT CAB4 USB or CAB7 USB for computers. Desk phones require a bottom cable with the correct connector, pinout and electrical characteristics. |
| CONTACT 520QD | QD → USB adapter → computer, or QD → dedicated cable → desk phone | Use CONTACT CAB4 USB or CAB7 USB for computers. Desk phones require a bottom cable with the correct connector, pinout and electrical characteristics. |
| AIR DECT 71DECT | DECT headset through an audio-connected base | Confirm the base configuration and its USB or telephone audio interface. A DECT radio link alone does not connect the headset to a computer application. |
| AIR DECT 72DECT | DECT headset through an audio-connected base | Confirm the base configuration and its USB or telephone audio interface. A DECT radio link alone does not connect the headset to a computer application. |
CONTACT 410, 510 and 520 connect to compatible desk phones through dedicated QD bottom cables. Connectors may look identical while pinouts and electrical characteristics differ. CONTACT CAB4 USB and CAB7 USB are used for computer configurations.
Logos and names belong to their respective owners. Their use identifies platforms and does not imply partnership, endorsement or certification by RHITOR.
Choose a product