Caveats
Download this chapter
CaveatsCaveats
 Feedback

Caveats

This section contains information on the caveats currently associated with Cisco Jabber IM for iPhone.


Note

Some caveats in the following listings reference Cisco Jabber for iPad. Cisco Jabber IM for iPhone and Cisco Jabber for iPad are developed from a common code base and some caveats are applicable to both products.

Bug Toolkit

Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:

  • All severity level 1 or 2 bugs
  • Significant severity level 3 bugs
  • All customer-found bugs except severity level 6 enhancement requests

You can search for problems by using the Cisco Software Bug Toolkit.

Before You Begin

To access Bug Toolkit, you need the following items:

  • Internet connection
  • Web browser
  • Cisco.com user ID and password
Procedure
    Step 1   To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
    Step 2   Log in with your Cisco.com user ID and password.
    Step 3   To look for information about a specific problem, enter the bug ID number in the Search for Bug ID field, then click Go.
    What to Do Next

    For information about how to search for bugs, create saved searches, and create bug groups, click Help on the Bug Toolkit page.

    Open Caveats

    The following caveats are open against Cisco Jabber IM for iPhone.

    Identifier Severity Component Headline
    CSCuc25519 3 general fail to send out msg if swith our app between WIFI and Cellular network
    CSCuc54640 3 general Inconsistent Presence Status Color between CUPC and Jabber IM
    CSCuc84841 3 general Large logs created via 30 times login/out if many contacts in buddy list
    CSCuc34057 4 general Internet call interrupted by GSM call

    Closed Caveats

    The following caveats are closed against Cisco Jabber IM for iPhone.

    Identifier Severity Component Headline
    CSCub10902 3 general WebEx Connect/Jabber Server certificates not signed by a trusted root

    Resolved Caveats

    The following caveats have been resolved in Cisco Jabber IM for iPhone.

    Release 1.0.4

    Identifier Severity Component Headline
    CSCuc67256 3 general Crash if enter website address to sign in
    CSCua25789 4 general cup:cannot manually set current status if CPUC's current status is DND
    CSCub74106 4 general Jabber IM stuck in reconnecting status after users switch network enviro
    CSCub76092 4 general emotion now show on remote side if type emotion after text without blank

    Release 1.0.3

    Identifier Severity Component Headline
    CSCuc27341 3 general Jabber IM crashes when users bring it to foreground
    CSCub76738 3 general It cannot manually change "Automatic Away" to Available in our app
    CSCuc27355 4 general Can't launch email app if click to pure digital email address
    CSCuc27348 6 general No 'tick' show on tag when users add corp contact to assigned group

    Release 1.0.2

    Identifier Severity Component Headline
    CSCub74404 2 general Jabber IM on iPhone crashes when performing contact lookup
    CSCub74485 2 general CUP account login fail for username@domain.com@domain.com in our app
    CSCub74178 3 im IM messages shouldn't be logged into local log file on the phone
    CSCub74231 3 general All characters the settings are NOT displayed and replaced "..."
    CSCub74434 3 general LDAP Session does not restart after a period of inactivity in our app
    CSCub76526 3 general Jabber iPad Google Analytics feed not encrypted
    CSCub76648 3 meetings Wrong meeting invitation sent to the Connect client in CJ iPad
    CSCub76697 3 general WebEx Connect/Jabber Server certificates not signed by a trusted root
    CSCub76773 3 ui Directory contact photo is not displayed if port 389 is not used
    CSCub81393 3 general App crash if click vast unread messages in chats view
    CSCub74500 4 general If a user logs in Jabber, it will kick all their buddies out of CUPC 8.5
    CSCub76433 4 general 'Away' appears if users add and delete a new custom status for 'Busy'