User Community Feedback
Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.
NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.
Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.
NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.
Commenting as I have a similar idea, but wanting web.webex.com to check local workstation registered default protocols (Webex App registers <WEBEX:>) and offer to run the local Webex App client.
If no registered local client is found, then initiate the web-only version web.webex.com (doesn't offer UCM calling capability).
This would allow us to offer one link in our SSO user portal: web.webex.com to kick off either a local client run/maximize (if present) or initiate the cloud-only version via browser if not locally present.
I am presuming that the cloud-based app would offer users the ability to download the hard "App" client instead of the current "Meetings" client (post-November rollout of version 42.11)
Also wondering if long term, user initiation of direct site links ([org].webex.com and/or specific meeting links could check for local App client availability as well.
What is Cisco's plan long term as they merge Meetings and "Teams" into App for the user's primary entry point into their Webex features?
Note that when clicking a MS Teams based meeting link, Teams does something similar to check if your workstation has locally based MS Teams app and offers in the browser window the user can jump to the local client (if it exists) instead.
Attachments Open full size