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.

Jabber 12.7+ Lines Forwarded Notification / CUCM Administrator Line Lock

We have had a severe problem since Jabber 12.7 where it now shows that other lines are forwarded and “Click to turn off”.

This has become a major issue as people are people and they think that there is a problem and click on this to turn off the forwardings. The problem is that this is the Forward All to voicemail for their general voicemail (GVM) boxes. Once they shut this off, the calls will no longer go to voicemail and start ringing ALL phones that have that GVM on it (this could be many phones spread across the state). We have configured all GVM lines with the minimum amount in the “No Answer Ring Duration (seconds)” to 1 second then forward to voicemail because people keep shutting off the forward all to voicemail. This is also causing issues now because people are thinking that calls are failing or that they are missing calls.

I’m not sure why Cisco enabled this feature in Jabber 12.7 and higher. I would imagine that this is causing issues for organizations other than just mine. I would propose removing this feature from Jabber as well as providing a way to add a checkbox to the lines that Administrators can lock the line so that the users are not allowed to change it? The 8800 series phones show the forwarding as well and people have a bad habit of shutting this off either on accident or on purpose. Locking the line by and Administrator would make it so that these GVM boxes continue to function properly.

  • Jeremy Schweigert
  • Aug 26 2020
  • Will not implement
  • Jeremy Schweigert commented
    21 Jan, 2021 02:17pm

    Jefferson Lu - Is Cisco stopping work on Jabber and merely pushing everyone to Webex or is this going to be fixed?

  • Jeremy Schweigert commented
    15 Dec, 2020 02:49pm

    Jefferson Lu...At this point, because Webex is not FEDRamp compliant nor ready for use in our environment, that is not an option. We would like to move to Webex, but we are waiting on Cisco to get everything finished. That being said, if it is "fixed in Webex", then why can't it be "fixed" in Jabber?

  • Admin
    Jefferson Lu commented
    14 Dec, 2020 08:34am

    Please migrate to Webex , It's fixed in Webex