Landis Attendant Console for Microsoft Teams
  • About
  • Getting Started
  • Daily Usage
    • Layout
    • Notifications
    • Teams Presence
    • Teams Status Message
    • Call Handling
    • Search for Contacts
    • Contacts
    • Contact Groups
    • Call Details
    • Call History
    • Voicemail
    • Contact Card
    • Click to Dial
  • Settings
    • General
    • Search
    • Contacts
    • Caller Info
    • Transfer
    • Devices
    • Layout
    • Keyboard Shortcuts
    • Quick Access Shortcuts
    • Connectors
    • Permissions
    • AI Prompts
    • Advanced
  • Administration
    • Settings Policies
      • Access Settings Policies
      • Configuring Settings Policies
  • Appendix
    • Advanced Settings
    • App Service Information
    • Attendant Pro Comparison
    • Custom Layout
    • Desktop App Antivirus Exclusions
    • Desktop App / Browser Feature Comparison
    • Desktop App Minimum Requirements
    • Enable Chat Consult Transfer
    • External Search
    • Integration Permissions
    • Known Limitations
    • Network Recommendations
    • Restricting Application Access
    • Supported Audio Devices
    • Supported Browsers
    • USB Audio Device Call Control Buttons (Preview)
    • Feature States
    • Release Notes
  • Knowledge Base
  • Service Health
    • Current Incidents
    • Incident Reports
  • What's New in Attendant Console
  • Download the Desktop App
  • What is an Attendant Console for Microsoft Teams
Powered by GitBook
On this page

Was this helpful?

  1. Appendix

Known Limitations

  • Call control functionality using buttons on USB audio devices is compatible exclusively with Jabra Teams Certified headsets (1)

    • Audio on other Teams certified headsets will work, but the answer/hangup and mute/unmute buttons will not function.

  • Call Park (2) (Workaround: Use chat consult)

  • (Coming Soon) Teams Contact Groups/Teams People app Categories do not show in Attendant Console (3)

1 - Requires headset vendor APIs which only Jabra currently provides. 2 - Adding this functionality requires a Microsoft API that is not yet available. 3 - Microsoft API now available and feature is now possible.

Last updated 1 day ago

Was this helpful?