Introduction
AudioCodes’ RXV81 Bring Your Own Device (BYOD) is a cost-effective, UC-agnostic collaboration bar designed for small and medium rooms, huddle rooms, focus rooms and executive rooms.
As a peripheral device, RXV81 BYOD with its integrated camera, microphones and speaker is connected in the room via USB to a PC or laptop running the UC application (which may be Teams, Zoom, and so on). If only used as a peripheral, RXV81 BYOD does not require any UC license to be installed on it.
From a pure peripheral, RXV81 BYOD can be upgraded via software license (purchased separately) to a full Android MTR. For details about configuring and using an RXV81 MTRA, refer to the RXV81 MTRA Video Collaboration Bar User's and Administrator's Manual.
RXV81 BYOD is fully managed by the AudioCodes One Voice Operations Center (OVOC) Device Manager (a plugin of OVOC), allowing admins to remotely oversee and easily upgrade all deployed devices from anywhere.
RXV81 BYOD can be operated with a Remote Control Unit (RCU) or RX PAD Meeting Room Controller.
| ● | The RCU is bundled in the RXV81P bundle to control meetings. |
| ● | The RX PAD is bundled in the RXV81P-B10 bundle to control meetings. |
For details, see Bundles.
A/V control functions include camera on / off, camera settings, mute / unmute and volume up / down.
Deployment is straightforward with its robust mounting element and minimal cable connections.
Microsoft Teams Android devices now utilize Intune Android Open Source Project (AOSP) device management. AOSP device management is a mobile device management (MDM) platform specifically designed for Teams devices. This update delivers more reliable user experience, an enhanced deployment process for administrators, and serves as the foundation for future innovations and advanced management capabilities for Microsoft Teams Android devices, including Teams Rooms, Teams panels, Teams phones, and Teams displays.
AOSP Device Management replaces the legacy Android Device Administrator solution previously used to manage Teams devices.
For detailed information on the AOSP migration process, please refer to the relevant Microsoft documentation.