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.

Screen Sharing while on a call via UCM Calling


We use UCM Calling Registration. If we're on a call via softphone with WebEx Teams, we're able to share our screen successfully. However, if we're on a call using a desk phone (via CTI Control), in an attempt to share the screen, the Teams client notifies us that we're already on a call and are unable to place another one.
It is very important that this ease of use is improved. More often than not, users will share their screen while already on a call. Forcing a user to either hang up and replace the call via softphone or spin up a webex is disruptive and makes for a very poor user experience.

Please get this feature prioritized as it is a key feature which is available in Jabber but still unavailable in Teams.

  • Joshua Reinmann
  • Nov 7 2020
  • Already exists
  • Parth Patel commented
    6 Apr 08:32pm

    This function is still not supported. If the user has screenshared first and then initiated a call. it gives error to end call before making another call. It won't allow to initiate call on other devices also.
    During the screenshare it doesn't provide use of microphone and speakers.

    this issue is present in all devices, Softphone desktop, iPhone, iPAD, Android from what we know.

    And this is a functionality that all IT or Helpdesk need when their clients are on meeting with someone else and they are experiencing issues during ongoing calls.

    helpdesk cannot request screenshare, and IT client cannot screenshare because they are on an ongoing call with someone else and experiencing issues.

  • Admin
    Jefferson Lu commented
    29 Dec, 2020 02:26am

    This function is supported already, if it doesn't work, please report a problem with logs