Cisco Jabber for Windows and Mac Features
Call Pickup
Applies to: Cisco Jabber for Windows, Cisco Jabber for Mac
The Call Pickup feature allows users to answer calls that come in on a directory number other than their own. Directory numbers are assigned to call pickup groups and Cisco Unified Communications Manager automatically dials the appropriate call pickup group number. Users select Pickup to answer the call.
Group call pickup allows users to pick up incoming calls in another group. Users enter the group pickup number, select Pickup and Cisco Unified Communications Manager automatically dials the appropriate call pickup group number.
Other group pickup allows users to pick up incoming calls in a group that is associated with their group. When the user selects Other Pickup Cisco Unified Communications Manager automatically searches for the incoming call in the associated groups.
Directed call pickup allows users to pick up an incoming call on a directory number. Users enter the directory number, select Pickup and Cisco Unified Communications Manager connects the incoming call.
For more information about configuring call pickup, see the Feature Configuration Guide for Cisco Unified Communications Manager.
Call pickup notifications
For multiple incoming calls, the notification displayed is Call(s) available for pickup. When the user answers a call, the user gets connected to the incoming call that has been ringing the longest.
Deskphone mode
The Cisco Unified Communications Manager notification settings are not supported for the pickup group. The call pickup notification displayed is CallerA->CallerB.
The Cisco Unified Communications Manager settings for audio and visual settings are not supported. The visual alerts are always displayed.
Shared line behavior
User not a member of an associated group
Expected behavior using group call pickup and directed call pickup
Enter an invalid number Enter a valid number and no current call available to pick up Enter directory number of a phone in an associated group and no current call available to pick up Enter a directory number of a phone on the same Cisco Unified Communications Manager node and not in an associated group Enter first digits of a valid group
Call pickup using a deskphone that is not in a call pickup group
If a user attempts a call pickup from a deskphone that is not in a call pickup group, the conversation window appears for a moment. The user should not be configured to use the call pickup feature if they are not members of a call pickup group.
Original recipient information not available
When the Cisco Unified Communications Manager Auto Call Pickup Enabled setting is true, the recipient information is not available in the client when the call is picked up in softphone mode. If the setting is false, the recipient information is available.
- Configure Call Pickup Group
- Assign Directory Number
- Configure Other Call Pickup
- Configure Directed Call Pickup
- Auto Call Pickup
Configure Call Pickup Group
Call pickup groups allow users to pick up incoming calls in their own group.
What to Do Next
Assign a call pickup group to directory numbers.
Assign Directory Number
Assign a call pickup group to a directory number. Only directory numbers that are assigned to a call pickup group can use call pickup, group call pickup, other group pickup, and directed call pickup.
Before you assign a call pickup group to a directory number, you must create the call pickup group.
Configure Other Call Pickup
Other Group Pickup allows users to pick up incoming calls in an associated group. Cisco Unified Communications Manager automatically searches for the incoming call in the associated groups to make the call connection when the user selects Other Pickup.
Before you begin, configure call pickup groups.
Configure Directed Call Pickup
Directed call pickup allows you to pick up a incoming call directly. The user enters the directory number in the client and selects Pickup. Cisco Unified Communications Manager uses the associated group mechanism to control if the user can pick up an incoming call using Directed Call Pickup.
To enable directed call pickup, the associated groups of the user must contain the pickup group to which the directory number belongs.
When the user invokes the feature and enters a directory number to pick up an incoming call, the user connects to the call that is incoming to the specified phone whether or not the call is the longest incoming call in the call pickup group to which the directory number belongs.
Auto Call Pickup
You can automate call pickup, group pickup, other group pickup, and directed call pickup by enabling the Auto Call Pickup Enabled service parameter. When this parameter is enabled, Cisco Unified Communications Manager automatically connects users to the incoming call in their own pickup group, in another pickup group, or a pickup group that is associated with their own group after users select the appropriate pickup on the phone. This action requires only one keystroke.
Auto call pickup connects the user to an incoming call in the group of the user. When the user selects Pickup on the client, Cisco Unified Communications Manager locates the incoming call in the group and completes the call connection. If automation is not enabled, the user must select Pickup and answer the call, to make the call connection.
Auto group call pickup connects the user to an incoming call in another pickup group. The user enters the group number of another pickup group and selects Pickup on the client. Upon receiving the pickup group number, Cisco Unified Communications Manager completes the call connection. If auto group call pickup is not enabled, dial the group number of another pickup group, select Pickup on the client, and answer the call to make the connection.
Auto other group pickup connects the user to an incoming call in a group that is associated with the group of the user. The user selects Other Pickup on the client. Cisco Unified Communications Manager automatically searches for the incoming call in the associated groups in the sequence that the administrator enters in the Call Pickup Group Configuration window and completes the call connection after the call is found. If automation is not enabled, the user must select Other Pickup, and answer the call to make the call connection.
Auto directed call pickup connects the user to an incoming call in a group that is associated with the group of the user. The user enters the directory number of the ringing phone and selects Pickup on the client. Upon receiving the directory number, Cisco Unified Communications Manager completes the call connection. If auto directed call pickup is not enabled, the user must dial the directory number of the ringing phone, select Pickup, and answer the call that will now ring on the user phone to make the connection.
For more information about Call Pickup, see the Feature Configuration Guide for Cisco Unified Communications Manager.
Configure Auto Call Pickup
Persistent Chat Rooms
Applies to: Cisco Jabber for Windows, Cisco Jabber for Mac
- Configure Persistent Chat
- Administer and Moderate Persistent Chat Rooms
- Enable Persistent Chat Room Passwords
Configure Persistent Chat
Persistent chat must be enabled and configured on Cisco Unified Communications Manager IM and Presence Service before it can be used by the client.
Persistent chat is only available on Cisco Unified Communications Manager IM and Presence Service 10.0 and later.
Refer to Database Setup for IM and Presence Service on Cisco Unified Communications Manager for your release for information on the database configuration necessary to support the persistent chat feature. Database configuration must be performed before continuing with this task.
Local chat message archiving must be enabled for persistent chat. Local chat message archiving is enabled on Cisco Unified Communications Manager IM and Presence Service using the Allow clients to log instant message history setting, for more information, see the Enable Message Settings topic.
What to Do Next
Ensure you configure any client-specific parameters for persistent chat. For more information, see the Client parameters section of the latest Parameters Reference Guide for Cisco Jabber.
Enable file transfer in chat rooms. For more information, see Enable File Transfer and Screen Captures for Group Chats and Chat Rooms.
Administer and Moderate Persistent Chat Rooms
 Note |
|
You administer persistent chat rooms from the Jabber client by creating rooms, delegating their moderators, and specifying members. The node on which the room is created is created automatically, although you can override it and specify a specific node. Administrators and moderators are privileged users in Persistent Chat rooms. You can administer Persistent Chat rooms on any service node that you are an administrator for on Cisco Unified Communications Manager IM and Presence servers.
Administrator Capabilities
-
Create rooms. When you create a room, you automatically become the room administrator.
-
Define and change up to 30 moderators for a chat room (who become room owners).
-
Specify and change the room name.
-
Define the maximum number of participants in a room. This number cannot be less than the number of participants already in a room.
-
Add and remove room members.
-
Block, remove, and revoke participants.
-
Destroy rooms (which removes it from the server, but the history is not deleted).
Moderator Capabilities
Room Creation
-
Room name (required, maximum 200 characters)
-
Description
-
Room type (public or restricted)
After the room type has been defined, it cannot be changed by anyone.
-
Specify whether to add the room to your My Rooms tab (off by default)
-
Add up to 30 moderators (who must have a valid Jabber ID to moderate a room).
-
Room password
After you create the room, you have the option to add members to the room immediately or at a later time. Refresh the All Rooms list in order to see your new room in the list of available rooms.
Enable Persistent Chat Room Passwords
Persistent chat rooms that are password protected means that when users enter a room within a Jabber session, they must enter the password. Password protected rooms comply with the XEP-0045 specification from the XMPP Standards Foundation.
Custom Embedded Tabs
Note | The Jabber embedded browser does not support cookie sharing with pop-ups from SSO enabled webpages. The content on the pop-up window may fail to load. |
- Custom Embedded Tab Definitions
- User Custom Tabs
- Custom Icons
- Chats and Calls from Custom Tabs
- UserID Tokens
- JavaScript Notifications
- Show Call Events in Custom Tabs
- Custom Embedded Tab Example
Custom Embedded Tab Definitions
<jabber-plugin-config> <browser-plugin> <page refresh="" preload=""> <tooltip></tooltip> <icon></icon> <url></url> </page> </browser-plugin> </jabber-plugin-config>
Cisco Jabber for Windows supports Internet Explorer version 9 or earlier. The client uses Internet Explorer in version 9 mode if a later version is on the workstation.
| Parameter | Description |
|---|---|
|
browser-plugin |
Contains all definitions for custom embedded tabs. The value includes all custom tab definitions. |
|
page |
|
|
refresh |
This parameter is optional and is an attribute of the page element. |
|
preload |
This parameter is optional and is an attribute of the page element. |
|
tooltip |
Defines hover text for the custom embedded tab. This parameter is optional. If you do not specify the hover text, the client will use Custom tab. The value is string of unicode characters. |
|
icon |
Specifies an icon for the tab. You can specify a local or hosted icon as follows:
You can use any icon that the client browser can render can render, including .JPG, .PNG, and .GIF formats. This parameter is optional. If you do not specify an icon, the client loads the favicon from the HTML page. If no favicon is available, the client loads the default icon. |
|
url |
Specifies the URL where the content for the embedded tab resides. The client uses the browser rendering engine to display the content of the embedded tab. For this reason, you can specify any content that the browser supports. |
User Custom Tabs
Users can create their own custom embedded tabs through the client user interface.
<Options> <AllowUserCustomTabs>true</AllowUserCustomTabs> </Options>
Note | User custom embedded tabs are set to true by default. |
Custom Icons
Chats and Calls from Custom Tabs
- Use the XMPP: or IM: protocol handler to start chats.
- Use the TEL: protocol handler to start audio and video calls.
UserID Tokens
You can specify the ${UserID} token as part of the value for the url parameter. When users sign in, the client replaces the ${UserID} token with the username of the logged in user.
 Tip | You can also specify the ${UserID} token in query strings; for example, www.cisco.com/mywebapp.op?url=${UserID}. |
JavaScript Notifications
You can implement JavaScript notifications in custom embedded tabs. This topic describes the methods the client provides for JavaScript notifications. This topic also gives you an example JavaScript form that you can use to test notifications. It is beyond the scope of this documentation to describe how to implement JavaScript notifications for asynchronous server calls and other custom implementations. You should refer to the appropriate JavaScript documentation for more information.
Notification Methods
-
SetNotificationBadge — You call this method from the client in your JavaScript. This method takes a string value that can have any of the following values: -
onPageSelected() — The client invokes this method when users select the custom embedded tab.
-
onPageDeselected() — The client invokes this method when users select another tab.
Note | Not applicable for Jabber for iPhone and iPad |
Subscribe to Presence in Custom Tabs
Note |
|
Get Locale Information in Custom Tabs
Note | Jabber for iPad and iPhone only supports OnLocaleInfoAvailable. |
Example JavaScript
<html>
<head>
<script type="text/javascript">
function OnPresenceStateChanged(jid, basicPresence, localizedPresence)
{
var cell = document.getElementById(jid);
cell.innerText = basicPresence.concat(", ",localizedPresence);
}
function GetUserLocale()
{
window.external.GetUserLocale();
}
function SubscribePresence()
{
window.external.SubscribePresence('johndoe@example.com');
}
function OnLocaleInfoAvailable(currentLocale)
{
var cell = document.getElementById("JabberLocale");
cell.innerText = currentLocale;
}
function onHubActivated()
{
var cell = document.getElementById("hubActive");
cell.innerText = "TRUE";
}
function onHubDeActivated()
{
var cell = document.getElementById("hubActive");
cell.innerText = "FALSE";
}
function onHubResized()
{
alert("Hub Resized or Moved");
}
function OnLoadMethods()
{
SubscribePresence();
GetUserLocale();
}
</script>
</head>
<body onload="OnLoadMethods()">
<table>
<tr>
<td>John Doe</td>
<td id="johndoe@example.com">unknown</td>
</tr>
</table>
<table>
<tr>
<td>Jabber Locale: </td>
<td id="JabberLocale">Null</td>
</tr>
<tr>
<td>Hub Activated: </td>
<td id="hubActive">---</td>
</tr>
</table>
</body>
</html>
To test this example JavaScript form, copy the preceding example into an HTML page and then specify that page as a custom embedded tab.
Show Call Events in Custom Tabs
You can use the following JavaScript function to show call events in a custom tab:
OnTelephonyConversationStateChanged — An API in the telephony service enables the client to show call events in a custom embedded tab. Custom tabs can implement the OnTelephonyConversationStateChanged JavaScript function. The client calls this function every time a telephony conversation state changes. The function accepts a JSON string that the client parses to get call events.
The following snippet shows the JSON that holds the call events:
{
"conversationId": string,
"acceptanceState": "Pending" | "Accepted| | "Rejected",
"state": "Started" | "Ending" | "Ended",
"callType": "Missed" | "Placed" | "Received" | "Passive" | "Unknown",
"remoteParticipants": [{participant1}, {participant2}, …, {participantN}],
"localParticipant": {
}
}
Each participant object in the JSON can have the following properties:
{
"voiceMediaDisplayName": "<displayName>",
"voiceMediaNumber": "<phoneNumber>",
"translatedNumber": "<phoneNumber>",
"voiceMediaPhoneType": "Business" | "Home" | "Mobile" | "Other" | "Unknown",
"voiceMediaState": "Active" | "Inactive" | "Pending" | "Passive" | "Unknown",
}
The following is an example implementation of this function in a custom embedded tab. This example gets the values for the state and acceptanceState properties and shows them in the custom tab.
function OnTelephonyConversationStateChanged(json) {
console.log("OnTelephonyConversationStateChanged");
try {
var conversation = JSON.parse(json);
console.log("conversation id=" + conversation.conversationId);
console.log("conversation state=" + conversation.state);
console.log("conversation acceptanceState=" + conversation.acceptanceState);
console.log("conversation callType=" + conversation.callType);
}
catch(e) {
console.log("cannot parse conversation:" + e.message);
}
}
The following is an example implementation of this function with all possible fields:
function OnTelephonyConversationStateChanged(json) {
console.log("OnTelephonyConversationStateChanged");
try {
var conversation = JSON.parse(json);
console.log("conversation state=" + conversation.state);
console.log("conversation acceptanceState=" + conversation.acceptanceState);
console.log("conversation callType=" + conversation.callType);
for (var i=0; i<conversation.remoteParticipants.length; i++) {
console.log("conversation remoteParticipants[" + i + "]=");
console.log("voiceMediaDisplayName=" + conversation.remoteParticipants[i].voiceMediaDisplayName);
console.log("voiceMediaNumber=" + conversation.remoteParticipants[i].voiceMediaNumber);
console.log("translatedNumber=" + conversation.remoteParticipants[i].translatedNumber);
console.log("voiceMediaPhoneType=" + conversation.remoteParticipants[i].voiceMediaPhoneType);
console.log("voiceMediaState=" + conversation.remoteParticipants[i].voiceMediaState);
}
console.log("conversation localParticipant=");
console.log(" voiceMediaDisplayName=" + conversation.localParticipant.voiceMediaDisplayName);
console.log(" voiceMediaNumber=" + conversation.localParticipant.voiceMediaNumber);
console.log(" translatedNumber=" + conversation.localParticipant.translatedNumber);
console.log(" voiceMediaPhoneType=" + conversation.localParticipant.voiceMediaPhoneType);
console.log(" voiceMediaState=" + conversation.localParticipant.voiceMediaState);
}
catch(e) {
console.log("cannot parse conversation:" + e.message);
}
}
Custom Embedded Tab Example
<?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Client> <jabber-plugin-config> <browser-plugin> <page refresh ="true" preload="true"> <tooltip>Cisco</tooltip> <icon>https://www.cisco.com/web/fw/i/logo.gif</icon> <url>https://www.cisco.com</url> </page> </browser-plugin> </jabber-plugin-config> </Client> </config>
Configure Automatic Updates
Applies to: Cisco Jabber for Windows, Cisco Jabber for Mac
Note | If you use the Cisco WebEx Messenger service for instant messaging and presence capabilities, you should use the Cisco WebEx Administration Tool to configure automatic updates. |
- XML File Structure
XML files for automatic updates have the following structure:
<JabberUpdate> <App name=”JabberWin”> <LatestBuildNum>12345</LatestBuildNum> <LatestVersion>10.5.x</LatestVersion> <Mandatory>true</Mandatory> <Message> <![CDATA[<b>This new version of Cisco Jabber lets you do the following:</b><ul><li>Feature 1</li><li>Feature 2</li></ul>For more information click <a target="_blank" href="http://cisco.com/go/jabber">here</a>.]]> </Message> <DownloadURL>http://http_server_name/CiscoJabberSetup.msi</DownloadURL> </App> </JabberUpdate>
- Example XML File 1
The following is example XML file for automatic updates:
<JabberUpdate> <App name="JabberWin"> <LatestBuildNum>12345</LatestBuildNum> <LatestVersion>9.x</LatestVersion> <Message><![CDATA[<b>This new version of Cisco Jabber lets you do the following:</b><ul><li>Feature 1</li><li>Feature 2</li></ul>For more information click <a target="_blank" href="http://cisco.com/go/jabber">here</a>.]]></Message> <DownloadURL>http://http_server_name/CiscoJabberSetup.msi</DownloadURL> </App> </JabberUpdate>
- Example XML File 2
The following is an example XML file for automatic updates for both Cisco Jabber for Windows and Cisco Jabber for Mac:
<JabberUpdate> <App name="JabberMac"> <LatestBuildNum>12345</LatestBuildNum> <LatestVersion>9.6.1</LatestVersion> <Message><![CDATA[<b>This new version of Cisco Jabber lets you do the following:</b><ul><li>Feature 1</li><li>Feature 2</li> </ul>For more information click <a target="_blank" href="http://cisco.com/go/jabber">here</a>.]]> </Message> <DownloadURL>http://http_server_name/Cisco-Jabber-Mac-9.6.1-12345-MrbCdd.zip</DownloadURL> </App> <App name="JabberWin"> <LatestBuildNum>12345</LatestBuildNum> <LatestVersion>9.0</LatestVersion> <Message><![CDATA[<b>This new version of Cisco Jabber lets you do the following:</b><ul><li>Feature 1</li><li>Feature 2 </li></ul>For more information click <a target="_blank" href="http://cisco.com/go/jabber">here</a>.]]> </Message> <DownloadURL>http://http_server_name/CiscoJabberSetup.msi </DownloadURL> </App> </JabberUpdate>
-
Install and configure an HTTP server to host the XML file and installation package.
-
Ensure users have permission to install software updates on their workstations.
Microsoft Windows stops update installations if users do not have administrative rights on their workstations. You must be logged in with administrative rights to complete installation.
| Step 1 | Host the update installation program on your HTTP server. |
| Step 2 | Create an update XML file with any text editor. |
| Step 3 | Specify
values in the XML as follows:
|
| Step 4 | Save and close your update XML file. |
| Step 5 | Host your update XML file on your HTTP server. |
| Step 6 | Specify the URL of your update XML file as the value of the UpdateUrl parameter in your configuration file. |
Restore Chats on Login
Applies to:Cisco Jabber for Windows, Cisco Jabber for Mac.
This feature allows users to specify if open chat sessions are restored on next sign in. This only applies to 1:1 chats.
For desktop clients, this feature is configured using the RestoreChatOnLogin parameter. When the parameter is true the Remember my open conversations check box is selected on the General tab of the clients. The check box is not checked by default when users sign into Cisco Jabber for the first time.
For more information on parameters, see the Parameter Reference Guide for your release.
Feedback