Cisco finally released Jabber for Windows, It’s intended to replace both WebEx Connect and CUPC.
Some new features are introduced such as file transfer, desktop sharing, screen capture tool and the ability to use the Callmanager instead of LDAP for user lookup.
Cisco has moved some of the client configuration from the Presence server to a jabber-config xml file.
Basic presence stuff, visual voice mail, CCMCIP, CTI Gateway profile, Audio profile etc is still done in the Presence admin GUI.
Directory Integration, deskphone/softphone credential source, client policy such as file transfer, video, screen capture etc is configured in a jabber-config xml file.
When it comes to Directory Integration for user lookup there are two options, EDI and UDS.
EDI – Enhanced Directory Integration requires no configuration by default. If you install Cisco Jabber for Windows on a workstation that is registered to an Active Directory domain, Cisco Jabber for Windows automatically discovers the directory service and connects to a Global Catalog in the domain. However, you can configure EDI to specify custom attribute mappings or custom connection settings.
UDS – User Data Service is an interface in Cisco Unified Communications Manager that makes contact information available to Cisco Jabber for Windows.
No server configuration is required for UDS. You create your directory source in Cisco Unified Communications Manager and then synchronize the contact data to Cisco Unified Communications Manager. After the synchronization occurs, your contact data resides in Cisco Unified Communications Manager. Cisco Jabber for Windows then automatically connects to UDS and performs all contact resolution.
UDS contact photo retrieval is done from a web server.
- Microsoft Active Directory 2003
- Microsoft Active Directory 2010
- Cisco Unified Communications Manager User Data ServiceUDS is supported on Cisco Unified Communications Manager 8.6.2 or later.
In this post I will go through how to configure Jabber for Windows in an on-premise Presence environment.
1. Download the Jabber for Windows install file and the admin files from Cisco.
2. Install the cmterm-bfcp-e.8-6-2.cop.sgn file on the publisher. Restart the server when it’s done.
This COP file enables BFCP support for CSF devices which is required for desktop sharing.
Note: this step is not required for 8.6.1.
3. Create a new SIP Profile, Device-> Device Settings-> SIP Profile. Copy the Standard SIP Profile, name it CUPS SIP Profile and check the Allow Presentation Sharing using BFCP.
4. Create a Client Service Framework Device. This is the softphone/desktop sharing used in Jabber for Windows.
I usually name it CSFuserid. Add your standard CSS, Loc, DP as you would on any other phone.
If the user has a deskphone select it under primary phone. This way adjunct licensing is used to save DLUs.
Check Allow Control of Device from CTI.
Select the SIP Profile created in the previous step.
Check the Allow Presentation Sharing using BFCP.
Note: Device name has no correlation with username but for convenience you might choose to include a username in the device name.
Add a DN to the line, be sure to associate the end user to the line to enable on/off hook presence status.
5. Assign CUP and CUPC license capabilities to your end user under System-> Licensing-> Capability Assignment
This is to enable so that you can login with the client and to see/publish presence status.
6. Goto the end user page. Add the CSF device and any deskphones to the end users device associations.
This is so you can use these devices in the Jabber for Windows client.
Add the Standard CTI Enable group.
If the user has a Cisco Unified IP Phone 9900 or 8900 series model phone, also select the following group: Standard CTI Allow Control of Phones supporting Connected Xfer and conf user group.
If the user has a Cisco Unified IP Phone 6900 series model phone, also select the following group: Standard CTI Allow Control of Phones supporting Rollover Mode.
7. Create the jabber-config.xml global configuration file.
The following config file enables screen capture, file transfer and video. Potentially malicious files are blocked for file transfer such as exe, msi etc.
UDS is specified to use the Callmanager as user search database. A web server is defined to fetch contact photos. %%uid%%.jpg is substituted with the userid in the Callmanager. eg http://server_name.domain/rwiklund.jpg
Phone service credentials is set to use the same username and password used in Jabber for Windows.
Note: this file must be saved in UTF-8 format.
<?xml version="1.0" encoding="utf-8"?>
7. Upload the file to all TFTP servers, be sure to restart the tftp service on Pub/Subs.
1. Class of Service -> Voice Mail User COS -> Check the following
– Allow Users to Access Voice Mail Using an IMAP Client and/or Single Inbox
Optional: Select what types of messages you want to be secure from the “Require Secure Messaging” drop down menu.
2. Add your VM account and be sure to set the web password, this is used for Visual Voice Mail in Jabber.
Note: The user ID in Cisco Unity Connection does not need to match the user ID in Cisco Unified Presence or in the client application. The client application has an independent voicemail ID, which is set in the application Options dialog box. However, you might find it useful to have the same user IDs across your Cisco Unified Communications system.
I recommend using LDAP SYNC+AUTH on both CUCM and CUC to keep end user credentials consistent.
1. Application -> Jabber -> Voice Mail server -> Add New
Add your Unity Connection server here.
2. Application -> Jabber -> Mailstore -> Add New
Enter name and IP address of Unity Connection server. Use port 7993 and TLS protocol.
3. Application -> Jabber -> Voice Mail profile -> Add New
Add your Voice Mail profile here. Enter your Voice Mail pilot number, Voice Mail server and Mailstore.
4. Application -> Jabber -> CCMCIP Profile -> Add New:
Add name, description, primary and backup CCMCIP server (I.E Publisher and Subscriber).
Note: This is used to pull information about associated devices for end users.
5. Application -> Jabber -> Settings
Here you can select Credential source for Voice Mail service. If you select CUP, username and password for VM will be pulled from the CUCM.
If you select “Not Set” you will have to manually specify Voice Mail username and password in the Jabber client option page. If your Vocie Mail credentials differ from the CUCM end user credentials chose this option.
6. Application -> Jabber -> User Settings
Select the end user and add your profiles for Voice Mail, CCMCIP, CTI Gateway, etc.
Note: Selecting an LDAP profile here has no effect on Jabber for Windows.
Start the Jabber client, you will be prompted to use WebEx Connect or Presence. Chose Presence and enter the IP address to the server, you must also enter the domain that’s configured on the Presence server.
Because we have phone credentials set to presence in the xml config file you don’t need to enter the username and password to control the softphone/desktphone. The same goes for voice mail because we set the voice mail credentials to CUPS in the Presence admin GUI.
That’s it, you’re good to go.
Note: Desktop sharing can only be turned on when there’s a call in place and only when using softphone mode.
Exchange Outlook Calendar integration.
Outlook calendar integration works the exact same way as before and I already covered that in a previous post. However I cannot find a way to enable/disable calendar integration from the client itself. It seems that the user has to do it from the Presence end user page.
It seems that click to dial is missing from this release. Click to email from the client is not available either.
If you create a customer away message, AFAIK there is no way to delete it, only change it.
Clear chat history seems to be missing, and there is no way to clear the call history all at once, you have to clear each post individually.
I have not tested the Office integration yet.