Authenticated Calls
This article explains the requirements needed to enable Authenticated Calls in Mago, allowing meetings to be joined using an authenticated user or room account instead of as a guest.
Last updated
Was this helpful?
This article explains the requirements needed to enable Authenticated Calls in Mago, allowing meetings to be joined using an authenticated user or room account instead of as a guest.
Authenticated Calls allow Mago to join video conferencing meetings using a verified identity instead of joining as a generic guest participant.
Depending on the platform configuration, meetings can be joined using:
• an authenticated user account • an authenticated account associated with the meeting room
This allows the meeting system to appear as a recognized participant within the conferencing platform.
Authentication is supported across multiple conferencing platforms, including Microsoft Teams, Google Meet, Zoom, and Webex. The available authentication methods may vary depending on the platform.
When joining a meeting with authentication, the participant appears with the correct user or room name instead of a generic device name.
Authenticated participants from the same organization can often join meetings directly without waiting for manual approval, depending on the platform’s meeting policies.
Authentication allows the conferencing platform to treat the participant as a trusted identity, improving compatibility with meeting features and organizational policies.
Authenticated calls can be configured using individual user accounts or dedicated accounts associated with meeting rooms, depending on the room setup and conferencing platform capabilities.
In this mode, a user signs in with their conferencing account on their personal device, such as a smartphone or laptop.
Once authenticated, the user connects their device to the meeting room system. This can be done, for example, by scanning a QR code displayed on the room screen.
The authentication is then securely transmitted to the room system, allowing the meeting to be joined using the user’s identity.
This model is commonly used in:
• BYOM environments • shared meeting spaces • scenarios where users temporarily authenticate the room for the duration of a meeting
In this configuration, the meeting participant appears as the authenticated user.
In some deployments, the meeting room itself can authenticate using a dedicated account associated with the room.
In this configuration, the meeting system joins meetings using the identity assigned to the room, allowing scheduled meetings to be joined with a consistent room identity.
This approach is commonly used in permanent meeting spaces where the room regularly joins meetings as a recognized participant.
Note that support for room resource authentication depends on the conferencing platform.
Last updated
Was this helpful?
Was this helpful?