Release Notes
Known Issues/Limitations
12
“Unable to establish a secure session. Your contact’s company prohibits sessions that are not
secure, so this session is being disallowed.”
When this message appears, one of the users must close the IM session and start a new one.
• If the Cisco Unified Communications integration is turned on, dialing a non-existing phone number
(111111111) results in the following additional message being logged:
[<Time stamp>] 111111111:
NOTE: Communications with loggeduser@mycompany.com are logged.
• In an IM session between two logged users, the notification (a statement stating that the session is
being logged) is displayed again if one of the users experiences a network disconnect or
reconnect.
• In an IM session between two logged users, the notification is not displayed when one of the
logged users signs out, signs back in, and then starts an IM session with the same user.
• In an IM session between a logged user and a non-logged user, the notification is not displayed
when the non-logged users signs out, signs back in, and either party then starts an IM session with
the other.
• In situations where a user logs in simultaneously from more than one IM client, the notification may
appear more than once.
• If the notification text is customized (for example, if the administrator overrides the default
notification text), the notification will appear without any special formatting in older versions of the
Cisco WebEx Connect application (version 7.2.6 and older) and in third-party applications.
AV with policy restricted
incompatibility between
version 7.0 and earlier
versions
If a user of Cisco WebEx Connect version 7.0 or later who is not VoIP-policy restricted starts a chat with a
user of an earlier version of Cisco WebEx Connect who is VoIP-policy restricted, and then the first user
starts Conference Computer in the conversation window, the user of the earlier version sees no prompt,
while the first user is incorrectly notified that the second user is joining the conference. [419723]
Unable to search the
Microsoft Outlook Global
Address List for contacts
The Add Contact dialog box has been simplified so that users searching for contacts to add to their contact
lists can search only the Cisco WebEx Connect user database. Users are no longer able to search the
Microsoft Outlook Global Address List (GAL) for contacts.
Unable to send a
message in Discussions
within an open Space
If a user has a particular Space open for an extended period of time, the user may be unable to send a
message in the Discussions tab. The workaround is to close the Space and reopen it to continue to
participate in sending messages in the Discussions tab for this particular Space
Desktop sharing
•
The ToolTip indicating who has control of the desktop sharing session incorrectly shows the
contact username instead of the contact display name (for example, the First Name and Last
Name).
• When a user of Cisco WebEx Connect version 7.0 ends a desktop sharing session with a user of a
third-party application, the third-party application user receives an incorrect notification that the
Cisco WebEx Connect user has canceled the invitation. [416579]
• Desktop sharing is not supported with a federated user on a third-party instant messaging
network, such as Google GTalk, Microsoft Lync, and so on. [CSCui66715]
• Participants are able to view the host’s desktop sharing control panel. [CSCzu51375]
Unable to receive
message when signed in
from both Cisco WebEx
Connect and Psi
If you have signed in to Cisco WebEx Connect and to the Psi instant message application (http://psi-
im.org/) at the same time and have set your status to “Custom Away” in Cisco WebEx Connect and to
“Away” in Psi, you may not receive messages correctly on Cisco WebEx Connect.
Unable to view the
business card of some
You may not be able to view the business card of some of your contacts who are not part of your company
or organization. This issue may occur if any of your contacts who are not in your organization have set their