Cisco Cisco Unified Communications Integration for Cisco WebEx Connect
Known Issues/Limitations
9
•
Under certain scenarios, Cisco WebEx Connect users always see a Contact List Request from an
OCS or Sametime user, even if they had previously denied the request by selecting Deny in the
Contact List Request dialog box.
OCS or Sametime user, even if they had previously denied the request by selecting Deny in the
Contact List Request dialog box.
The workaround for this problem is to block the OCS or Sametime contact by selecting Block in the
Contact List Request dialog box.
•
OCS and Sametime clients may show Cisco WebEx Connect contacts in the OCS or Sametime
software even after the Cisco WebEx Connect user has removed them completely from his
software even after the Cisco WebEx Connect user has removed them completely from his
contact list. This can lead to confusion between the Cisco WebEx Connect user and the OCS or
Sametime user because the OCS and Sametime software will not show a status for the Cisco
WebEx Connect user.
WebEx Connect user.
•
Cisco WebEx Connect custom statuses, such as “On the phone” or “In a WebEx Meeting,” may not
be visible or be reflected correctly in the OCS or Sametime software.
be visible or be reflected correctly in the OCS or Sametime software.
•
A Sametime user may not be able to send an IM to a Cisco WebEx Connect user if the user status
is “Away,” because Sametime interprets the status as “Do not disturb” or “Busy.”
is “Away,” because Sametime interprets the status as “Do not disturb” or “Busy.”
•
An OCS user may see a Cisco WebEx Connect user’s status as “Available” when the user’s status
is actually “Idle.”
is actually “Idle.”
•
Cisco WebEx Connect emoticons may not translate well in the Sametime or OCS software and
vice-versa.
vice-versa.
•
A Sametime user may receive a “blank” message when communicating with a Cisco WebEx
Connect user who is signed in to Cisco WebEx Connect Web IM and that user then signs off.
Connect user who is signed in to Cisco WebEx Connect Web IM and that user then signs off.
•
A Sametime user may receive “blank” messages when a Cisco WebEx Connect user is typing a
message—this is because the Sametime client does not interpret “typing indicators” correctly.
message—this is because the Sametime client does not interpret “typing indicators” correctly.
•
An OCS user cannot federate with a Cisco WebEx Connect user if the Cisco WebEx Connect
username contains a quotation mark ( “ ).
•
OCS rejects hyperlinks that contain extensions on its blocked list.
Issues with third-party
XMPP software
•
Some third-party XMPP software applications such as Pidgin and PSI, do not support the Decline
feature, and when you click the Cancel button in Pidgin, it does not do anything. As a result, a
feature, and when you click the Cancel button in Pidgin, it does not do anything. As a result, a
group chat invitation that is sent from Cisco WebEx Connect to a third-party application may not
receive an “accept” or “reject” response.
•
When a Cisco WebEx Connect user ends a desktop sharing session, third-party applications may
show the internal commands being exchanged to the end user in the IM window.
show the internal commands being exchanged to the end user in the IM window.
•
Some third-party applications do not support HTML rendering in the same way Cisco WebEx
Connect does; for example, if the Cisco WebEx Connect window has a “Here” link, some third-
Connect does; for example, if the Cisco WebEx Connect window has a “Here” link, some third-
party applications cannot produce the URL.
•
Some third-party applications, such as MomentIM, do not support server side blocking (XEP-0016,
privacy lists). As a result, a Cisco WebEx Connect user may still see a user’s presence status after
privacy lists). As a result, a Cisco WebEx Connect user may still see a user’s presence status after
being blocked from the third-party application and the user of the third-party application may still
receive instant messages from the Cisco WebEx Connect user.
receive instant messages from the Cisco WebEx Connect user.
Secure Real-Time
Protocol (SRTP)
Protocol (SRTP)
The Cisco Unified Communication Integration with Cisco WebEx Connect version 7.0 or later does not
support Secure Real-Time Protocol (SRTP), even though the user interface still shows settings for that
support Secure Real-Time Protocol (SRTP), even though the user interface still shows settings for that
protocol.
CUCM Integration and
DTMF signals
Although the Cisco Unified Communication Manager (CUCM) Integration with Cisco WebEx Connect
version 7.0 or later may send dual-tone multi-frequency (DTMF) signals while the call is considered “in
progress,” it does not send tones.