Guest

Preview Tool

Cisco Bug: CSCvu85165 - Jabber for Android keeps Away status when getting IM or call in while in Automatic Away mode

Last Modified

Aug 07, 2020

Products (1)

  • Cisco Unified Mobile Communicator

Known Affected Releases

12.8(1) 12.8(2)

Description (partial)

Symptom:
J4A 12.8.2: does not change status back to Available after Automatic Away when App is foreground

Jabber for Android has Automatic Away (15 mins) feature enabled by default.
When Jabber App starts up user becomes Available. Once Jabber App moves to background in 15 minutes status changes to Away.
When Jabber App is brought to foreground by incoming call, expectations are that Jabber will change status back to Available.
This is not happening. Manual status change from Away to Available is required.
Jabber 'switches' from Automatic Away to Manual away and never gets back to Available if it's getting IM or Incoming call while staying in background in Automatic Away state.

Conditions:
- Automatic Away is enabled (this is by default)
- Jabber App is in the background reaching Automatic Away state
- Jabber App is getting incoming call or IM
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.