Cisco UC Integration(TM) for IBM Sametime provides instant access to Cisco Unified Communications capabilities directly from IBM Sametime. The integration enhances productivity by extending native audio and HD video capabilities to Sametime IM and presence users. It also includes Cisco phone control and presence status with integrated voicemail and conversation history. The integration allows access to Cisco call control for both standalone and Notes-embedded clients.
Features and Capabilities
With this tight integration for IBM Sametime, users
get a consistent user experience, enhanced communications
capabilities, and reduced infrastructure complexity. The
integration also provides Sametime users with the following
Native phone mode control for audio and video
Users can choose
to control audio or video calls in IBM Sametime from the user's
computer or from the phone.
Phone presence and control using XMPP
The phone presence icon,
which indicates whether a contact is busy on another call or
available to receive a call, is displayed in addition to the IM
presence icon where available.
Click-to-call capability from IBM Sametime client
from your list of existing contacts by right-clicking a contact and
selecting Phone Call or by choosing a number from the provided
Integrated visual voicemail and conversation history
users can view, play, or review conversation history right from the
main Sametime client window.
Easy creation and
management of audio and video conferences by dragging and dropping
contacts from the list or by searching for participants in the
embedded search bar.
Release and General
What's new in Cisco UC Integration for IBM Sametime
The following improvements were added to Cisco UC Integration for IBM
As of this release Cisco UC Integration for IBM Sametime validates
certificates when connecting to the Cisco servers.
Enhancements to Synchronized Cisco UC Credentials
When user credentials are not synchronized correctly, additional
menu items will direct the user to the Accounts Preference window.
Clients must meet
the following minimum requirements to use Cisco UC Integration for IBM
Microsoft Windows XP SP3 32 bit
Microsoft Windows 7 (Pro, Enterprise, or Ultimate) 32 bit or 64
AMD Sempron Processor 3600+ at 2 GHz
Core 2 CPU T7400 at 2.16 GHz
Free Physical Memory
DirectX 9 (Microsoft Windows XP SP3)
DirectX 11 (Microsoft Windows 7)
USB 2.0 is required for USB
cameras and audio devices.
Lotus Notes 9.0
Lotus Notes 8.5.2 or later with IBM Lotus Sametime 8.5.1 or later (Integrated)
Lotus Sametime 8.5.1 or later (Standalone)
Cisco Unified IP Phones
Unified IP Phones 9900 Series
Unified IP Phones 8900 Series
Unified IP Phones 7900 Series
Unified IP Phones 6900 Series
Integration(TM) with IBM Sametime is compatible with the following server
Cisco Unified Communications
Cisco Unified Communications
Manager with IM and Presence
Cisco Unified Presence
Cisco Unity and Cisco Unity
Click to Call
You can use any of
following desktop applications with the Click to Call feature:
Firefox 3.5 or higher
Internet Explorer 7.0, 8.0, 9.0, and 10.0
Excel 2003, 2007, and 2010
2003, 2007, and 2010
Outlook 2003, 2007, and 2010 Microsoft PowerPoint 2003, 2007, and 2010
SharePoint Server 2003 and 2007
Click to Call
only supports 32-bit versions of Microsoft Office 2010 applications.
TCP connection to CUCM SIP server port (for example, 5060) when using computer
TCP connection to CUCM CTI server port (for example, 2748) when using desk
phone for calls
TCP connection to Unity Connection 443, 7080
TCP connection to CUCM on 8443, at initialization time
Up to two
temporary/need-basis TCP connections to LDAP/Directory server
UDP ports for the
following audio-video streams:
using computer: 2 local UDP ports
call using computer: 2 local UDP ports
audio call: no local UDP ports
IBM Sametime has
one issue in its media player, because of which you might receive an popup
saying "null" error when you try to play any voicemail. IBM provides a HotFix
for Sametime 8.5.1, which you can download at
limitations and considerations apply to all releases:
Users need to
supply non-blank values of all servers, even if they are not required for that
particular phone mode. For example, in soft phone mode, user must enter a
non-null string value in preference page configuration for phone functionality.
Rules to function properly with Cisco UC Integration for IBM Sametime and Cisco
Unified Communications Manager prior to Release 8.6(2), an additional .cop file
must be installed on the version each time dial rules are added or modified.
multiple Sametime community servers:
presence and voicemail functionality in Cisco UC Integration for IBM Sametime
only function when the user logs in to their default community. However, the
simultaneous use of other communities (in other words, if the user logs in and
out of other community servers) does not impact Integration functionality as
long as the default community is connected.
Customers who do not log in to the default community, but instead log in to
another non-default Sametime community server will not be able to use
limitations and considerations apply to the 9.5.2 release:
certificate validation, when connecting to the Cisco Unified Communications
Manager, there is a 10 second limit to accept the certificate and connect
successfully. After that duration, even on accepting the certificate will be
added to the store, however the connection will fail.
limitations and considerations apply to the 9.5 release:
There is an
issue with a call that moves from "Integrated" to "Standalone". This is a case
that involves three parties: A, B, and C. A makes a call to B, and B then
transfers the call to C. Subsequently, C transfers the call back to Party B.
After the transfers complete, A first sees the number of C in the call area of
the chat window (the chat between A and B). The call then pops out to a
standalone window that shows the name and image of B.
When this occurs, the user must click the pop-in (View video in Chat window)
button on the standalone window to return to the integrated call display.
Delay in window
swap operations for video calls: Cisco UC Integration for IBM Sametime allow
you to switch between various window types, such as to full screen from an
integrated conversation window, or to a conference window from a standalone
conversation window. Because video GUI elements are moved on the screen, a
slight, perceptible delay occurs during this operation.
If a user has
not set up a voicemail profile, then an incoming call alert will not include a
Decline button on their computer, because the call cannot be diverted to
voicemail. In this scenario, the only options for the user on an incoming call
are to answer the call or manually mute the ringer. The future release(s) will
implement muting of incoming call ring-out.
conference participant list is not updated in the Cisco UC Integration for IBM
Sametime GUI when the conference call is in the locally HELD state.
addition of an existing call to an existing ad hoc conference fails because of
network race conditions. In this circumstance, Cisco UC Integration for IBM
Sametime does not repeat the "add to conference" operation attempt; instead,
the user can attempt the operation manually as desired.
video operation requires that the Medianet service is installed and running
before the Sametime client is started.
a desk phone video call is escalated to a video conference or merged with
another video call, the resulting local call is in audio-only mode. However,
the user can escalate that call back to video after a hold-and-resume operation
a desk phone video call in Cisco UC Integration for IBM Sametime results in
cessation of both video transmission and reception (this is unlike soft phone
mode, in which the remote video can still be received).
When the user
switches from soft phone mode to desk phone mode (audio and video) for the
first time, the Integration shows the configured device names. However, this
listing does not include the line numbers associated with the devices. Because
of this, a user that changes to desk phone mode will not be able to designate
the specific line number. However after the transition to desk phone mode
completes, the line numbers will be visible and user can switch between them.
phone video to function properly, it is important that the phone supports
certain protocols that make it compatible for desk phone video on a tethered
computer. For example, Cisco IP Phone 7960 with firmware SCCP60.8-1-2SR2 does
not work, while Cisco IP Phone 7961 with firmware sccp 41.9-2-3s works properly
in desk phone video mode.
simultaneous merge of a call at both ends is not supported. If you attempt this
procedure, you could encounter unexpected results. For example, some calls
might remain "unmerged" outside the conference, or more than one conference
window might open. Similar behavior can also occur if you attempt a normal
merge during slow network conditions.
A user who
does not appear in the Contact list might get resolved to a person with name
appended with the search base. This works properly for users in buddy contact
video-enabled desk phone (whose camera is temporarily detached), is being
controlled by Cisco UC Integration for IBM Sametime, any attempt to initiate a
video call will result in a self-view window with a black background.
The Click to
Call feature only supports 32-bit versions of Microsoft Office 2010
of an established Cisco UC Integration for IBM Sametime call is not supported
across a Cisco Unified Communications Manager failover.
that allows you to forward a voice message as an attachment will only function
if the default mail client is Lotus Notes. Also, the Forward feature is not
active until one minute after the user logs in to voicemail.
the conference feature in desk phone mode, the remove participant option has no
Integration for IBM Sametime does not allow more than one simultaneous call to
same end party number. This case holds even when first call is on hold.
If a number
that is not configured in LDAP is added to the conference window using the
search bar, that participant will be added as number only, and will not be
resolved as a name that is configured on Cisco Unified Communications Manager.
that use a SIP-based protocol might experience one-way video during a desk
phone video call. This behavior occurred on Cisco 9XXX series devices in lab
strings on the Call Voicemail button and in the Preference windows are
truncated when Cisco UC Integration is used with some non-English languages.
Desk Phone Video
You cannot use
desk phone video capabilities on devices if video cameras are attached to the
devices, such as a Cisco Unified IP Phone 9971. You can use desk phone video
capabilities if you remove video cameras from the devices.
You cannot use
desk phone video capabilities with devices that do not support CTI.
It is not
possible for endpoints that use SCCP to receive video only. SCCP endpoints must
send and receive video. Instances where SCCP endpoints do not send video result
in audio only calls.
phones must use SCCP for desk phone video capabilities. 7900 series phones
cannot use SIP for desk phone video capabilities.
general limitations and considerations apply to the 9.0(1a) release:
does LDAP queries for the contact user ID and telephone number. If a customer
does not add the telephone number in LDAP, presence will not work.
A call will
separate out to a standalone window when it is transferred to a third party and
then transferred back to the originator. If you open a chat window manually,
you can move the call into the chat window manually.
Users may notice
a delay during video calls when moving between window types. Movement between
window types can include moving from an integrated to standalone window and
moving from a standalone call window to a conference call window.
multiple steps to get the video in an integrated conversation window taller.
First shrink the incoming chat area and then shrink the outgoing chat area.
Then you can stretch you chat window so that the video fits better. You can
also move the call out of the integrated chat window into a standalone window
and resize that window.
configuration tool first to deploy as Lotus Notes widgets. Make a copy of the
update site and ensure that only one feature jar is in each update site feature
directory. Next, make two widgets, one for phone feature and one for the