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.

Full control of all Jabber Mobile settings

Current situation / Problem definition:We have full control of Jabber Desktop settings and as Admins can centrally manage them (This is good practice)We have no control of Jabber Mobile settings once a device is handed out to the user (This is a nightmare)How it should be:As Admins we should be able to control the Jabber settings, no matter what platform the Jabber Client is running onWhy the current situation is an ongoing maintenance nightmare:Let me quickly draw our situation. We manage 1'000+ JM devices on site. On each device we have to change a couple of the default settings by hand before we hand the device out to the user (which by itself is ridiculous and a huge source for human errors).[...]... we are somewhere at around 6'000 - 8'000 manual changes of Jabber Mobile settings each year. That is the ongoing maintenance nightmare i was talking about.As much as we love JM but honestly - it's crazy that we are running this kind of setup in a business environment.To get an idea of why this bothers us so much and why it causes all kinds of troubles just have a look at the field report linked below:AppConfig to configure Jabber client for iOSWhat needs to be fixed:Parameters can't be only available for certain platforms.They need to be available for all Jabber Client versions (unless it's some kind of platform specific limitation like a touch screen setting or similar things).An example of the currently existing bad practice:Parameters Reference Guide for Cisco Jabber 11.9 - Options [Cisco Jabber for Windows] - CiscoSet_Status_Inactive_TimeoutApplies to Cisco Jabber desktop clients. Sets the amount of time, in minutes, before the availability status changes to Away if users are inactive.The default value is 15.Example:<Set_Status_Inactive_Timeout>10</Set_Status_Inactive_Timeout>Reason: Currently our users have no way of telling wether somebody really is "Away" or if it just was JM changing the status (once again) without the user even knowing that he was set to "Away".

  • Guest
  • Nov 6 2020
  • Will not implement