Showing results for 
Search instead for 
Did you mean: 

Jabber for iPhone does not keep wifi alive

Level 1
Level 1

I am using a Cisco WLC 5508 on latest software with 1142 WAPs using HREAP mode and WPA2 with PEAP authentication with iPhones. I can connect to wifi without issue once the device is turned on, but when using Jabber for iPhone, when the screen if off, eventually the wifi goes to sleep as well and Jabber loses connection.

This was working before with iPhone 4 and iOS 4 but since upgrading to iOS 5.x I haven't been able to trust Jabber and still have to carry a 7921.  Any tips on getting the wifi to stay alive?

27 Replies 27

Level 1
Level 1

There are a couple considerations when using Cisco Jabber with the iOS 5.

  1. Tap the native iOS device Settings icon
  2. Tap Notifications
  3. Tap Cisco Jabber
  4. Tap Alerts
  5. To see a cont of missed calls or voice messages on the Cisco Jabber icon, slide the toggle beside Badge App Icone to "ON"
  6. To hear Cisco Jabber ring while in the background, slide the toggel beside Sounds to "ON"
  7. To hear Cisco jabber ring or see alerts while the phone is locked, slide the toggle beside View in Lock Screen to "ON"

  • Another possiblility is that you're hitting defect CSCua19385 - cisco jabber for iphone doesn't reregister with cucm when in background.

If you feel that hitting the defect, please contact TAC and provide them the Cisco Jabber Problem report after reproducing the issue.

Bug ID CSCua19385 is fixed in Cisco Jabber for iPhone 9.0.1, according to TAC today.  Unfortunately, they do not have the timeframe for its release.

John Mahon
Level 1
Level 1

I am currently working on the same issue with Cisco TAC

The reason why the iPhone didn't get ring is because it's unregistered with Call Manager and the reason why it's unregistered to Call Manager after some times is that iPhone will switch it's network connection from WiFi to 3G after it sleeps for some time. I have done some research on the net and apparently that is the iPhone behaviour, you can check out the link below:

I also include the analysis below for your reference and hope this help.

Please do not hesitate to let me know if you have any questions on this.

//At 11:03, the Cisco Jabber was NOT in background.

-- 2012-06-08 11:03:38.118 DEBUG [3ee8ad98] - [TCSessionViewManager sessionWasCreated:] - App state: isBackgrounded: NO, isInactive: NO

//At 11:14, the Cisco Jabber went to background and the deskphone integration was disconnected, that is normal in background mode.

-- 2012-06-08 11:14:07.474 DEBUG [3ee8ad98] - TCTConnectionMananger startCTIVerificationWithDeskphoneAccount:] - App state: isBackgrounded:

YES, isInactive: NO

-- 2012-06-08 11:14:07.474 DEBUG [3ee8ad98] - [TCTConnectionManager startCTIVerificationWithDeskphoneAccount:] stop reconnect deskphone when background

-- 2012-06-08 11:19:35.652 DEBUG [3ee8ad98] - [TelephonyAppDelegate refreshLocalNotifications] Canceling the pop-up failure notification.

-- 2012-06-08 11:19:35.680 DEBUG [3ee8ad98] - [TelephonyAppDelegate refreshLocalNotifications] Canceling the pop-up failure notification from archived version.

-- 2012-06-08 11:19:35.682 DEBUG [3ee8ad98] - [AppDelegate refreshLocalNotifications] Creating (or post-poning) pop-up failure notifications

-- 2012-06-08 11:19:35.774 INFO [3ee8ad98] - #### keep alive timer.

accounts: { [Desk Phone Integration, Disconnected], [Internet Calling, Connected], }

//At 12:08, the Cisco Jabber was still in background, Wifi is still active on RFXXXXXX, Cisco Jabber was still showing as registered in Call Manager.

-- 2012-06-08 12:08:08.178 INFO [3ee8ad98] - [CSINetworkAvailability setCurrentLocalAddress] - Local address is 10.61.x.x

-- 2012-06-08 12:08:08.178 INFO [3ee8ad98] - [CSINetworkAvailability updateAvailability] Wifi:RFXXXXXX Carrier:Yes

//At 12:35, the Cisco Jabber was still in background

-- 2012-06-08 12:35:57.495 DEBUG [3ee8ad98] - TCTConnectionMananger startCTIVerificationWithDeskphoneAccount:] - App state: isBackgrounded:

YES, isInactive: NO

//At 12:38, the Wifi is off and that trigger the iPhone to change the network to 3G and iPhone has a new IP Address 10.242.x.x and iPhone can't register to Call Manager via 3G, unregistering the Cisco Jabber.

-- 2012-06-08 12:38:28.842 INFO [3ee8ad98] - [CSINetworkAvailability setCurrentLocalAddress] - Local address is 10.242.x.x

-- 2012-06-08 12:38:28.843 INFO [3ee8ad98] - [CSINetworkAvailability updateAvailability] Wifi:n/a Carrier:Yes

-- 2012-06-08 12:38:28.843 INFO [3ee8ad98] - [TCTConnectionManager resetReconnectionTimer] Deactivating and resetting the reconnection timer.

-- 2012-06-08 12:38:28.843 DEBUG [3ee8ad98] - [TCTConnectionManager IPAddressChangeTimerDidFire:] - Network changed. Attempting to restart the softphone

-- 2012-06-08 12:38:28.843 INFO [3ee8ad98] - [TCTConnectionManager restartTinCanWithError] Restarting the softphone.

-- 2012-06-08 12:38:28.843 DEBUG [3ee8ad98] - -[TCTConnectionManager ctiCallControlDisconnect]

-- 2012-06-08 12:38:28.843 DEBUG [3ee8ad98] - [CSIPhoneManager unregisterClientWithError:] Unregistering client.

Hi John

I am also experiencing this, well defiantly the bug listed where Jabber doesn't reregister when it is running in the background.

When your phones go to 'sleep' how long does it take before the phone unregisters from cucm?

I am going to do some testing on this today to see if I can replicate.

I have a customer that is planning to only have iPhones and not deskphones as their primary device, it needs to be as reliable as a hardphone though.



Hi Andy,

It was variable, it depends as the iPhone could receive an email which re-trigger the WiFi etc, on Apple forum, found that if you turn off the 3G it forces the iPhone's WiFi to stay on. 

General > Network > Cellular Data

Also if the iPhone is plugged into Power the WiFi remains on.

Another alternative is to configure Mobility Identify on CUCM.



John, did you find out anything solid from TAC?  Turning off cellular data isn't a viable option as I'm in and out of wifi as I travel to locations etc.

As Abcronin said, it should be as reliable as a hardphone but we are far from that right now.

dudes, according to a Cisco SE, this is a known issue from 5.1.1 of iOS and they are in discussions with Apples dev's about it, it (wifi) should stay active when the app is running and the phone is having a nap.

They want us to log TAC cases so the BU can put pressure on the internal developers and Apple also to get it resolved.

Any news, about the disconnection of Cisco Jabber, I have the same problem.

Accordiong to Cisco, the Cisco Jabber for iPhone 9.0.1 release that fixes this bug is to be released in August.  I've been told two different dates--8/2 and then 8/16/2012.

I have been using the beta 9.0.1 and can confirm that it resolves the CSCua19385 bug (device doesn't register when running in background)

However I still have had mixed results with the iPhone (and iPad) shutting off the wifi when sleeping. There is an internal bug raised with Apple on this CSCub14854.

I will provide updates on further testing.



Thank you for the update.  Looking forward to this being fixed.


How you have downloaded the version 9.0.1 ?


Hi Matthew, only way to get this is to be on Cisco's internal network to download the app sorry.

FCS is due by the end of this month (Aug)


Hello Everyone,

This bug CSCub14854 affects Cisco Jabber in IOS 6.0.1?


Leonardo Santtana

Leonardo Santana

*** Rate All Helpful Responses***