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 videoconferences by dragging and dropping
contacts from the list or by searching for participants in the
embedded search bar.
Release and General Information
Clients must meet the following minimum requirements to use Cisco UC Integration for IBM Sametime.
Microsoft Windows XP SP3 32 bit
Microsoft Windows 7 (Pro, Enterprise, or Ultimate) 32 bit or 64 bit
Mobile AMD Sempron
Processor 3600+ at 2 GHz
Intel Core 2 CPU T7400 at 2.16
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.
IBM Lotus Sametime 8.5.1 or later (Standalone)
IBM Lotus Notes 8.5.2 or later with IBM Lotus Sametime 8.5.1 or later (Integrated)
Cisco Unified IP Phones
Cisco Unified IP Phones 9900 Series
Cisco Unified IP Phones 8900 Series
Cisco Unified IP Phones 7900 Series
Cisco Unified IP Phones 6900 Series
Cisco UC Integration(TM) with IBM Sametime is compatible with the following server applications.
Cisco Unified Communications Manager
8.0(3) or later
7.1(3) or later
Cisco Unified Communications Manager with IM and Presence
9.0(1) or later
Cisco Unified Presence
8.6(4) or later
Cisco Unity and Cisco Unity Connection
Protocol Signaling Ports
Persistent TCP connection to CUCM SIP server port (for example, 5060) when using computer for calls
Persistent TCP connection to CUCM CTI server port (for example, 2748) when using desk phone for calls
Persistent TCP connection to Unity Connection 443, 7080
One temporary 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:
Audio call using computer: 2 local UDP ports
Audio-video call using computer: 2 local UDP ports
The following limitations and considerations apply to the 9.1 release:
The phone status feature algorithm is time-staggered algorithm, which results in a trickle-down effect of phone status display for first few runs of the client.
In the case when a user does not has a voicemail profile configured, the incoming call alert toast on computer of that user will not have Decline button, since the call cannot be diverted to voicemail. The user has no option but to either answer the call or manually mute the ringer. Future release(s) will implement muting of incoming call ring-out.
The conference participant list is not updated in CUCI GUI when the conference call is in locally HELD state
Desk phone video operation requires that the Cisco Medianet service is installed and running before the Sametime client is started.
If a desk phone video call is escalated to a video conference or merged with another video call, the resulting local call is sometimes in audio-only mode. However, the call can be escalated back to video after a hold-and-resume operation.
De-escalating a desk phone video call on CUCI IBM 9.1 results in the cessation of both video transmission and reception (unlike the Use my computer for calls mode, where the remote video can still be received).
In normal Use my phone for calls mode (audio/video), when there is a mode switch for the first time from Use my computer for calls to Use my phone for calls, CUCI will be able to show the configured device names to the user. However, CUCI will not be able to show the line numbers associated with them. The impact is that the user, if using the computer for calls and switching to the phone mode, will not be able to select the line number to change to. However, once this first transition to Use my phone for calls is complete, the line numbers will be visible and user can switch between them.
For desk phone video functionality to work, it is important that the phone itself supports certain protocols which make it compatible for supporting desk phone video at 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 fine in desk phone video mode.
Desk Phone Video Limitations
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.
7900 series phones must use SCCP for desk phone video capabilities. 7900 series phones cannot use SIP for desk phone video capabilities.
The following general limitations and considerations apply to the 9.0(1a) release:
CUCI client 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.
The system administrator must supply non-blank values for all server configuration information even if that information is not required for a particular phone mode.
Phone status, phone, and voicemail functionality is aligned with the user logging into the default community. The use of other communities does not affect this functionality but the user must be logged into the default community. Logging out of the default community will disrupt phone status, phone, and voicemail functionality.
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.
It takes 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.
Directory Lookup Rules do not work with Cisco Unified Communications Manager prior to Release 8.6(2). This may cause Cisco UC Integration(TM) with IBM Sametime to be unable to map incoming phone calls and voice messages to your Sametime contacts.
Run the 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 voicemail feature.