There are two methods used to forward calls to a different destination: from the IP phone (the user’s method) and from the Cisco IOS CLI (the administrator’s method). This section describes the user’s method as shown in the following demonstration.



To forward calls from the IP phone, simply press the CFwdAll softkey button, as shown in the figure below. The IP phone beeps twice and allows you to enter a number. Enter the number to which all calls on the IP phone will forward, and then press the pound key (#) on the phone so that it knows you are done entering the number. To cancel call forwarding, press the CFwdAll button a second time.


In the following demonstration MOKAYA (1001) is going to configure his phone to forward all calls to MANANI (1002). These are the step by step processes to achieve this.


Step 1: MOKAYA (1001) presses the CFwdALL softkey button as shown below



Step 2: The IP phone beeps twice and allows MOKAYA (1001) to enter a number 1002 (MANANI) to which to forward all calls to as shown below.



Step 3: Now when JOSECK (1000) or anyone tries to call MOKAYA (1001), the calls will be forwarded to 1002 (MANANI) as shown in the figure below. JOSECK (1000) calls MOKAYA (1001) and is forwarded to MANANI (1002).







So far we have laid the foundation of what an ideal Collaboration solution should look like or have. In this article, we are going to show you how to use different features of Cisco Unified Communications Manager. Most of these features are both supported on CUCME or CUCM.


Before we start exploring each and every feature in a Cisco based Collaboration environment, we are going to give you a background of what we are going to state what we are going to use to accomplish this objective.


These are some of the tools that we are going to use in our Collaboration demonstration:


1. Cisco Unified Communication Manager (CUCM) version 8.6.1


2. Cisco Unified Communication Manager Express (CUCME) version 8.6


3. Cisco IP Communicator


4. Cisco 7970 IP Phone.


5. Zoiper Softphone on Android smartphone




1. Cisco Unified Communication Manager (CUCM) version 8.6.1



2. Cisco Unified Communication Manager Express (CUCME) version 8.6



3. Cisco IP Communicator



4. Cisco 7970 IP Phone.



5. Zoiper Softphone on Android smartphone







On the smartphone front, the Jabber client runs on the iPhone and Android platforms. Like the tablet versions, the smartphone versions will support IM, presence, voice, and HD video. Again, the video quality is subject to hardware capabilities. The figure below shows the Jabber for iPhone client.



The figure above shows the control console on the client. The figure below shows the Jabber for Android client on a smartphone. Again, the clients have the same look, feel, and capabilities. The difference in the two figures is merely to show differing views of the Jabber client capabilities.



The figure above shows an IM session in progress on the Jabber client. Notice the escalation icons at the top of the client. These function identically to the escalation functions on the tablet and desktop clients.






Cisco Jabber for iPad and Android enable mobile users to make use of Jabber on a mobile platform somewhat larger than the smartphone and more portable than even the smallest laptop computer.


Tablets have taken over as the perfect balance of application portability and screen real estate. It is only natural that they become an extension of our work desktop.


Using the Jabber client enables the full collaboration experience in a very small footprint. This includes IM, presence, voice, HD video, content sharing, and so on. It will run on iPad, iPad mini, or an Android tablet.


The figure below shows the Cisco Jabber for iPad client.



The figure below shows the Jabber client contacts and IM screen on an Android tablet. The Jabber client on both platforms has the same look, feel, and capabilities. The quality of video will, of course, be subject to the wireless network radio, processor and optics capabilities of the tablet.


For example, the quality of the experience on a new iPad Air with Retina camera and display will be superior to that on an iPad 3 without Retina capabilities.






Cisco Jabber has come a very long way in a relatively short time. It represents the evolutionary result of a number of prior clients including Cisco IP Communicator (CIPC), Cisco Unified Personal Communicator (CUPC), WebEx Messenger, TANDBERG Movi, and numerous other components. It has become the all-in-one client we have so long desired in the Cisco collaboration realm.


Cisco Jabber offers one common user experience across multiple platforms, including desktops, tablets, and smartphones. It has the same look and feel regardless of whether it is used on a Windows platform, Apple OS X / IOS Platform, Android platform, or web platform.


The fact that it is based on a unified Client Services Framework (CSF) allows it to layer multiple services into a single, highly flexible platform.


On the desktop client, multiple custom tabs can be added to provide access to frequently used websites, widgets, and applications.


The Jabber software development kit (SDK) provides the ability to fully customize the client look, feel, and content. Regardless of platform, when launched, the client kicks off a service discovery process.





For desktops, Cisco Jabber supports both Windows and Mac operating systems. The look and feel of each client, while nearly identical, will take on the attributes expected in the OS in which each is used.


Jabber includes cloud-based or premise-based instant messaging (IM), presence, voice, HD video, voice messaging, desktop sharing/remote control, and conferencing capabilities all from a single client.


It also integrates with Microsoft Office applications for presence status, calendar information, and communication from within the Office application.


Being a multiuse client, Jabber makes use of a number of protocols to facilitate communications. For IM, Jabber makes use of standard extensible messaging and presence protocol (XMPP).


Being such, Cisco IM&P services can be easily federated with any other standards-based Extensible Messaging and Presence Protocol (XMPP) implementation. For voice and video calling capabilities, Jabber is a SIP-based endpoint.


It can operate in soft phone mode, providing full calling capabilities from the desktop. This is useful when there is no desk phone present on the desktop or when the end user is on the move.


When a desk phone is available, Jabber can integrate with it through the use of Computer Telephony Integration (CTI). This allows the client to make use of the desk phone for communications launched from the Jabber client itself.


It also allows the ability to enable video communications for any Cisco IP Phone. All that is required on the workstation is a webcam. For video calls, Jabber is capable of resolutions up to 720p30 when expanded to full-screen mode.


It does support SIP URI dialing as well as traditional numeric dialing. For multiparty calls, a video or audio conferencing resource is required as appropriate for the call. The figure below shows the Cisco Jabber for windows client.



For comparison, the figure below shows the Cisco Jabber for Mac client.



Desktop sharing can be initiated from the client as well simply by initiating an IM session. The client can be in either desk phone mode or soft phone mode when the share is initiated.


The share can also be used to control the desktop being shared. In cases where the screen share is initiated from a multiparty IM session, the screen share can include up to five participants.


No call need be active between the two endpoints. If only an IM session is active, the screen share is initiated via XMPP. If a call is active, the share is initiated via Binary Floor Control Protocol (BFCP).


This is a relatively new addition, however, in Jabber 10.5 and later. Note that that IM-only screen share is using Remote Desktop Protocol (RDP) to accomplish the connection. Therefore, it is available only with Jabber for Windows.


Prior to Jabber 10.5, only BFCP was used for desktop share, and no remote control capability was possible. This necessitated the need for the Jabber client to be in soft phone mode and a call to be up between the desktops to initiate the share.  This is no longer the case.





Go to top