There's a mobile version of our website.
Is it a relatively simple process to install and active Windows Jabber Clients?
I'm assuming this document isnt related to the BE3k:
I have purchased JAB9-DSK-LIC and adjunct licenses
I've created a new Phone:
For configuration specific to Cisco Jabber clients, make sure to do the following:
• Choose Cisco Unified Services Client as the Phone Type
• Enter a unique name for the Cisco Jabber client in the Identifier field on the Add a Phone window. The Identifier is the name that Cisco Business Edition 3000 assigns to the Cisco Jabber client. The XML device configuration file that the TFTP service sends to the Cisco Jabber client during the registration process is given the name you assign in this field.
I've installed Jabber for Windows: 9.0.4
The client starts up and asks for either a WebEx server or Cisco Unified Presence Server (Both ask for a username and password)
I'm assuming that I select Unified Presence Server and the IP of the BE3000
Where does the username and password come from?
We're about to publish some more detailed guidance on how to use Jabber clients with the BE3000, but in the mean time please note - as Sanjay states - Jabber desktop clients must be activated with a valid WebEx Connect subscription.
Once registered with the Connect service, then you will be able to use the UC Integration features of the client covered by the JAB9-DSK-LIC license. Integration options allow desk phone control from the Jabber client without a BE3000 endpoint license and for the client to be used as a softphone with a license.
Note that Jabber softphone clients for Android and iPhone devices do not require a WebEx Connect account for activation (a separate phone app is available there for IM).
When you fill out the registration form, you should get a link with where to download the client from and server address. This is Step 7 in the GPL Ordering process diagram.
The information is not provided. I have been going back and forth with Webex to obtain the info and have gotten no where.
Get with the WebEx provisioning team and get them to email this info correctly.
Sent from Cisco Technical Support iPhone App
When I ordered the WebEx Connect subscription I received a PAK ID. I then registered it and about 3 days later was able to connect to WebEx Connect for IM only. When trying to follow document to integrate with BE3000, the client does not have the option for Phone Account. I also did not receive a server to connect to either as the instructions outline.
Sent from Cisco Technical Support iPhone App
Have you ordered the call control license, JAB9-DSK-K9 & JAB9-DSK-LIC?
Since call control is separate, you need to order it separately for Call control functionality to be enabled on the client.
When you order the WebEx Connect service, you have to specify that you require the UC Manager integration option, as this is not included by default at this time. If you don't, it won't appear in the cluster configuration options in the Connect Admin Tool (see image below) and subsequently won't be enabled as an option in the client.
More detail on the ordering process can be found The specified document was not found.. Details on configuring the Jabber client for UC integration can be found here.
Raise a case with the WebEx Connect team and ask them to add the UC Manager Integration for Webex Connect option to your accound.
Also, while you are at it, ask them to make the Jabber desktop clients (Windows/Mac) available for user download - with this setting in place, users will get a link to download the client in their welcome email from Connect when their account is set up.
You can submit your request using the WebEx Order Enquiry Tool. You can use the following options.
For WebEx Connect, you can just use the "Default Server" option.
More detail from the Jabber Admin Guide:
Defines whether Cisco Jabber for Windows automatically looks up the presence server. Select one of the following options:
Enables you to provide connection properties for the presence server. Select this option if your presence server does not support domain name system service records (DNS SRV). For example, Cisco Unified Presence 8.5.2 does not support DNS SRV.
I tried Default server option but it says invalid username and password. I believe I need to get username and password form Cisco webex first in order to login to jabber software , and then assoicates with the users on local BE3k. I'm still in the process of tracing up the jabber licenses from webex team.
Thats right, there are basically two sets of credentials - WebEx Connect to sign in to the client and then BE3000 user credentials to configure the UC integration feature.
When you get up and running with Connect, you create a new user which will generate a welcome email for them. This will invite the user to set a password and download the client.
Take a look at the Connect and Windows Desktop guide that I posted yesterday.
I finally got this Jabber client working with WebEx accounts, and also enabled "enable the call manager integration with Cisco Webex Connect" by Webex team. Now I can see the "Phone accounts" option on the Cisco jabber client. But when I typed in username and password, I kept getting Invalid username or password" error message, even though I added a phone with phone type=Cisco Unified Service Client" and Identifier = "CSFX300" ( according to Sanjay's document, identifier = CSF"userid")
My question is what exactly the username and password I should type in ?
if we are validating phone accounts userid and passoword then this will be authenticated based on the phone assoicated user page user id and Password.
Where did you find the
"enable the call manager integration with Cisco Webex Connect" by Webex team.
I can login using the Windows webex client but dont have the option for Phone etc...
Were do I get this server address: (From Sanjays document) - It works using default but the Phone menus are not available in the Jabber application.
Enter the Server address that you receive from Webex Service. Click Save Enter the username and password that you received.
Click on Sign-In
At this time, you should be signed in to the Jabber Client. You can add Contacts using File -> New-> Contact
I noticed I had to do this from the WebEx Connect Admin portal:
We had ordered the correct options as we have the option to enable Cisco UC Manager integration with WebEx Connect
The 'Missing step' I believe is to Create a new cluster with the "Enable Cisco UC Manager Integration with Cisco WebEx Connect" AND THEN select the user and then select add to the new Cluster under the communications tab (under edit user)
Ensure that the Jabber clients has fully 'Exited' via the Windows System task bar and then fully re-load/re-connect to enable the addition menus…
We ordered the correct options too but Cisco doesn't enable for you automatically. I need to contact Webex team to ask them to enable this option then you can select "enable the call manager integration with Cisco Webex Connect" , otherwise you can only have first option which is "enable cisco webex connect click-to-call'
WOW - Finally have it up and running - what a drama!
Now for what seems a really stupid question after all the other hoops I've been through!
How do you add a contact - you type a name and it says not found?
I want to add contacts for the other staff so that I can press to dial them/view their phone status?
You need some sort of directory services which can be integrated with the Jabber client using LDAP for it to search contacts when u are adding them.
Sorry can you explain further?
The Jabber WebEx Client can communicate with other instant chat clients/platforms 'out of the box' and you would also 'assume' that the client can call other extensions on the phone system - again how are they added so you can click on a user to dial their extension. When a user on the system calls their name etc is displayed - this information needs to be added as a contact.
In the presentation there were users coming from gmail.com - how are they added?
Setting up a LDAP server was NEVER part of any presentation nor is part of a phone system install.