The following known issues are present is Cisco Jabber IM for iPhone.
When a user on Cisco Jabber IM for iPhone sends a meeting invitation to a user on Cisco Jabber IM for BlackBerry, the BlackBerry user will not receive the invite.
When making a call on Cisco Jabber, your presence will not change to On a call. The On a call presence state will only show when a user is using their iPhone to place a call.
If a user experiences a network disconnect while the app is running in the background, it may take up to 10 minutes for the app to re-establish a connection. This is an iOS backgrounding limitation.
If a user puts the app in the background, it may take up to 10 minutes for the app to update presence. This is an iOS backgrounding limitation.
If a user puts the app into the background before being fully logged in, the login process will stop.
Long names (such as Jabber IDs or words in German) will be truncated.
If a user changes their proxy settings while logged into the app, the user will need to log out and log back in to have the settings take effect.
In instances of poor network conditions, a user may appear to be available on their own device when the app is actually trying to reconnect the user. During the time the app is trying to reconnect, other users will see them as offline.
If a user receives a cellular phone call on a GSM network while they are engaged in a VoIP call to a corporate contact and they decline the cellular phone call, the VoIP call will resume but with no audio.
Cisco Unified Personal Communicator users only:
When a user is logged into both desktop and mobile and chatting with 3rd party XMPP users (OCS/Sametime/AOL), message routing and presence behavior may vary since it is a client side implementation.
Contact lists will display as the username with fully qualified domain name instead of first name, last name.
If a user sets their status to Offline or Out of Office in Cisco Unified Personal Communicator and the user logs into Cisco Jabber IM for iPhone, any mobile status updates will not appear. The mobile presence changes will not show. Out of Office will remain the presence state.
Cisco WebEx Messenger users only:
If an SSO organization has set their policy to go through the CAS, the user will not be able to login through CAS with their user name and password. The user will need to go through the corporate IDMS page to log in.
Not all buttons have voice over support for accessibility. This will be addressed in a patch release.