Configure Jabber for Mac with local CUCM and WebEx Connect

Hi, I was wondering if anyone has been able to configure the Jabber for Mac 8.6.2 client to use the WebEx Connect presence server with a local CUCM and Unity Connection servers. The preferences accounts tab does not show or allow the addition of the voice services. I have added from a working local CUCM preferences plist file what I believe are the correct entries however I still cannot see the accounts on the preferences tab. We currently do not have a local cisco presence server hence the requirement to trial the WebEx Connect server as I can't get past the first configuration step without it.
regards
paul

Hi - I have done this via the admin portal but still cannot get the Jabber client for Mac to register for voice. The Windows version works fine for the same user and CUCM device. Are there any other settings that need to be enabled specific to the Mac client?
Thanks.

Similar Messages

Jabber for Mac 9.2.2 and BFCP Desktop Sharing

I don't see where BFCP is supported using Jabber for Mac 9.2.2/Media Services Interface.
Can Cisco confirm?

Cisco SE confirmed "no BFCP for Jabber for Mac 10.0 using IM&P 10x, this feature is not committed"

Jabber 9.1.2 missing DLL's with Win8 64bit and WebEx Connect

I realize that Windows 8 is not yet listed as supported operating system for Cisco Jabber for Windows, but I would like to make it work anyway I am trying to use Cisco Jabber for Windows 9.1.2 on Windows 8 with WebEx Connect. I am able to log in and IM just fine, but when I attempt to launch an Instant WebEx Meeting the first time, I receive the error
"WebEx Meeting is unavailable. Unable to connect to WebEx meeting server. Please try again later."
However, for any subsequent attempt to launch an Instant WebEx Meeting, I receive three errors in this order:
1) The program can't start because atWbxUI14.DLL is missing from your computer. Try reinstalling the program to fix this problem.
2) The program can't start because ATKBCTL.DLL is missing from your computer. Try reinstalling the program to fix this problem.
3) WebEx Meeting is unavailable. Unable to connect to WebEx meeting server. Please try again later.
In both cases (fresh install and subsequent attempts) I receive an email letting me know that my meeting is in progress. So, I know that it has connected to meeting center and set up the meeting. It just can't seem to launch the WebEx interface. I have no problems launching WebEx by any other method that I have tried (e.g., Productivity Tools, from a browser, or if I uninstall Jabber and install the WebEx Connect client).
Has anyone seen this one?

I had actually tried that already, but just for kicks I did it again. Webex Connect was not installed. I uninstalled anything that had the word webex in it. I uninstalled Cisco Jabber. I went through C:\ProgramData and C:\Users\[username]\AppData\, and I deleted anything that had the words Webex or Jabber. I rebooted the computer, I installed Cisco Jabber. I rebooted the computer again before starting the application. Then I went into meetings and clicked "Instant WebEx Meeting." It gets to the point where it is installing the webex plugin. Once the WebEx plugin installion completes, I get the same error as before.
Since Windows 8 is not listed as a fully supported operating system for Cisco Jabber for Windows, I suppose this kind of thing is to be expected. I was just hoping that maybe someone had found a work around.

Jabber for Windows 9.0.1 on WebEx Connect Admin

When will the Jabber for Windows 9.0.1 client be on the WebEx Connect Admin web site for controlled upgrade of the clients?

Jabber for Windows 9.0(1) will not be posted automatically for all customers.
An internal communication will be issued to all internal CSM's and PSM's in the next couple of days explaining the exact procedure for requesting access to the client and how to raise the ops request to make it available for the customer org in question ... so reach out to the your Partner manager to understand that procedure and to enable access for your customers.
Regards,
John

Cisco Jabber for Mac, possible without a Presence Server?

Hi all,
is it possible to use the cisco jabber client for Mac without a presence server in the uc environment? A customer is looking for Voip Client/Softphone for their Apple Macs. Instant Messaging is no requirement.
Regards
Steffen

WIlliam,
I belive he could use a Webex Connect account, IPSec VPN, and a CSF device in CUCM to achieve what he is looking for. Though it is a shame that he would need to have Webex Connect to do this just to be able to login to Jabber...
FYI:
I just tried out the CUP integration with Jabber for Mac with my customer with CUCM 8.6.2(a), CUCXN 8.6.2(a), and CUP 8.6.1 HA. It seemed to work ok (I was using VPN as well). For some reason the directory service said it failed yet I could search for people in the directory and it worked fine (strange...). I think this may be because the XCP Directory Service on both CUP servers will not start (not sure why because I do not seem to need it).
My only complaint is that I originally had Jabber for Mac installed for Webex Connect integration. There appeared to me, that there was no way to re-run that original wizard (I looked all around in the package contents...) and select Cisco Presence instead of Webex Connect. To get around this I used AppCleaner to remove Jabber, re-download from Cisco, and re-install, this time selecting the Presence option. Once I tested I had to rinse-repeat to get my Webex Connect back because that is what we use internally. Hopefully they fix this because it makes it hard for us engineers to test Presence integration during installs.
Opinion on Jabber with Webex Connect:
I love it for creating Instant Meetings - It sends an email instantly to me that I can forward to attendee's right away (most of time not with contacts otherwise I would do it that way).
I love the new iPhone app that was just released as well. Very cool. (Do not like how you cannot be logged into both though, not a big deal, Archives of chats are my biggest concern). It is a pretty seemless login/logout from iPhone to Mac and Mac to iPhone though, which I appreciate.
I have no desire for Phone Services or Voicemail integration so it is annoying that it always says at the bottom of the buddy list "Server or port unreachable". I assume that you need to be connected to VPN in order to have connection to CUCM to use the CSF device... Jabber 8.6 Release Notes says that Jabber is not supported with NAT without VPN
Also the Chat History is weak on Mac, and none existent on iPhone . Would be cool if history was built in like CUPC or Lync, doesn't require going to Finder to view, and messages would archive on server.
Plus we use Exchange UM for our Voicemail so not sure how that would integrate with Webex Connect. I believe Exchange Voicemail in Jabber would work with Presence integration though (which is puzzling but I guess it is because you can do all of those XCP external integrations in CUP. However, don't get me started with CUP/Exchange calendar integration and CUP not supporting SAN certificates with multiple hostnames on Exchange...
Thanks for the info on X-Lite and Bria, I may try out these options. I have been using CIPC through VMWare Fusion and it worked quite well. I believe I needed to install Virtual Audio Cable for the sound to work correctly. I use it through Fusion's "Unity" function and it looks like it is native!
Just my 2 cents. Let me know what you think.
One more thing (SJ):
Check out this site for Mac Apps for Engineers:
http://ciscovoiceguru.com/2071/mac-app-cisco/comment-page-1/#comment-2760
Ryan

BE 3000 with Jabber (for Mac) and webex connect integration problems

Hi,
This is my first question on the forum so please be gentle!
I have a customer who has a Business Edition 3000 and they have purchased WebEx connect and Jabber integration to go with it.
My problem is I am having difficulty getting the setup to work and I have a number of questions on how to set this up. Most of the docs on Cisco's website seem to be related to either CUCME or full CUCM, but not a lot on BE 3000. My questions are below:
1. I have been reading the documentation for WebEx connect and it states to set the IP address of the BE 3000 server in the Configuration>Additional Services>Unified Communications>Voicemail tab. This is currently on the network with a 192.168.x.x address however. My predecessor put this IP address in the WebEx configuration page but I'm not sure this will work with a private IP as I don't know how this communicates back. The documentation isn't very clear on this. Does this have to be a public IP address / FQDN for it to work?
2. Are there any SRNDs for this type of setup that could help? Again, looking through the website hasn't turned anything up yet.
Note:
we are using the following software:
Jabber for MAC:
uc-client-mac-8.6.7.20127.fcs.zip
MAC OS:
OSX 10.8.3
BE 3000:
MCS7890C1-BE8
8.6.4.10000-15.
Thanks in advance for any help.
Regards,
Jason

Hi - I have done this via the admin portal but still cannot get the Jabber client for Mac to register for voice. The Windows version works fine for the same user and CUCM device. Are there any other settings that need to be enabled specific to the Mac client?
Thanks.

What is BDI or BDS spelled out? Jabber for Mac 9.2(1) Installation and Configuration Guide

I’m spending the day catching up on Jabber/IM&P release notes across the server/clients.
So I’m used to EDI and UDS, but we have a new acronym in the Jabber for Mac 9.2(1) Installation and Configuration Guide called BDI and BDS. However they don’t define what BDI stands for other than BDI is LDAP for non-windows
Clients and suggests it should be used for Jabber for Mac.
What is BDI or BDS spelled out? Something directory integration, but what is the B ?
Then to add to the mix they reference BDS which sounds like the old UDS (is UDS changing to BDS?)
How can Jabber get any more confusing…
I also noted in the Jabber Video for iPad 9.3.4 release notes that Apple is removing the Always Connect option in the near future. Manually launching Cisco AnyConnect Secure Mobility Client before making a call. This is going to upset some customers who like how Lync uses https and just works from anywhere with enhanced directory integration…

Basic Directory Integration. It's not new, we had it in the Windows clients as far back as CUPC. The distinction got introduced when EDI was introduced, relying on Windows ADSI APIs instead of the client making a native LDAP bind.
To my knowledge BDI/BDS are the same thing; I'm guessing S is 'service'. UDS remains unchanged.
I also noted in the Jabber Video for iPad 9.3.4 release notes that Apple is removing the Always Connect option in the near future.
Well, they lost a patent infringement lawsuit and chose to change the functionality instead of pay the troll. That's not Jabber's fault. Collaboration Edge will be the way to avoid this in the near future.
Please remember to rate helpful responses and identify helpful or correct answers.

Cisco Jabber for Mac 9.2.1: slow to register with CUCM

Hi,
We have this specific problem on our Jabber for Mac 9.2.1 client only: the client takes 60 to 70 seconds to connect to CUCM (running 8.6.2) when it starts.
After Jabber registers with CUCM, there is no issue, it's just very slow to register.
Anybody getting the same behaviour? We have no such issue on previous versions of Jabber for Mac version 8 or Jabber for Windows version 9.
Thanks,
Fabrice

For those interested, I have the answer to my own question: if one of your configured DNS servers is not responding, Jabber 9.2.1 will delay registration to the phone services. This behaviour is seen only in this specifc version of Jabber, hopefully it will be fixed in the next release. Watch out if one of your DNS server goes offilne.
Fabrice

Cisco Jabber for Mac - Directory Lookup and Contact Fields

Hello,
After having issues myself with Cisco Jabber for Mac 9.2 specifically with Active Directory lookups not working, or contact information not populating (and therefore not being able to call users from the contact list as no telephone information exists) I am including a sample jabber-config.xml file that works for me.
Please note: there are many different ways to configure this. What I will be showing is the method that works for me and my deployment, which is pretty standard.
As always and as a disclaimer, once again, this is what has worked for my deployment scenario. Always keep backups of your configuration files, and always be mindful of anything you have configured already, especially in the jabber-config.xml file.
Background
My deployment is based on CUCM 9, with 1 publisher and 2 subscribers. I also have a CUCM IM & Presence 9.0 server. This assumes that you have already configured your deployment and Jabber is functioning already, albeit with the aforementioned issues.
As for Active Directory, my deployment will be based on Windows 2008 R2 Domain Controllers running in native 2008 mode. For this example, we will be searching directly against one of the DCs with a Global Catalogue role. Please be aware that in large deployments you will have to plan accordingly with regards to lookup traffic from Jabber clients to the DCs.
Also, as of Cisco Jabber for Mac 9, the client no longer can search via the CUCM internal directory (which may be made of local end users, Active Directory synced users, or a mix of both) and this must be done via a LDAP mechanism.
Scenario
In this deployment scenario, Cisco Jabber for Windows is working properly - you can search and add people from Active Directory, and contacts in your contact list have all the appropriate fields populated from Active Directory. However, when trying the same with Jabber for Mac, Jabber for iPhone or Jabber for iPad you notice that you cannot perform a directory lookup, and if you add people directly (for example, [email protected]) the user only has the IM field populated. No telephone, email or additional information is displayed.
Solution
Whereas Cisco Jabber for Windows uses the EDI mechanism (native Windows), whereby when running from a computer that is on the domain (or in the event that you are search for contacts in another Active Directory domain where a domain trust exists) , Jabber for Mac / iPhone / iPad uses the BDI mechanism.
In this case, you will need to provision a jabber-config.xml file that you will upload to your TFTP server (or Publisher) that will be "downloaded" by your Jabber for Mac client and also used by the iPhone and iPad client. You can configure many options in the jabber-config.xml file, but for this example we will place just the information that we need to order for these clients to request and display Active Directory information.
Please note that the configuration may vary depending on your deployment, but at the very least we will be:
- Configuring a DC where we will perform the lookup.
- Configure credentials that will be used to perform the lookup. This will be an Active Directory account that has read rights on the Active Directory domain. Please note that these credentials are saved in plain text in the file, so ensure that the account that you will be using is not privileged.
- Configure the server port that we will be using to perform the lookup.
- Configure the Search Base. This is basically where we want the directory lookup to happen. You can either choose for this lookup to start at the "base" of the domain (and therefore the search will iterate through all the user accounts and and OUs below the root base) or define a specific OU where you want to search.
Caution!
- There is a current limitation with Cisco Jabber for Mac whereby you can only have 1 search base configured. Please keep this in mind if, like me, you have multiple OUs (like an OU for each company in your organization) and under these OUs you have sub OUs as a user account container.
- If using the top level search base, unless you specify a filter, you will potentially be able to search for all user accounts in the domain. You will need to configure the <BDIBaseFilter> parameter if you want to fine tune your search ability.
Steps
These are the steps I have followed. Other steps or considerations may vary.
- Log in to your TFTP server and download the jabber-config.xml file and keep it as a backup. If you are already using the jabber-config.xml file for other purposes, do not worry - you can add your BDI information parameters inside.
- Remove the jabber-config.xml file
- Edit the jabber-config.xml file and configure thus:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
    <Directory>
        <DirectoryServerType>BDI</DirectoryServerType>
        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>DOMAIN CONTROLLER IP ADDRESS</BDIPrimaryServerName>
        <BDIPresenceDomain>YOUR PRESENCE DOMAIN</BDIPresenceDomain>
        <BDIServerPort1>3268</BDIServerPort1>
        <BDISearchBase1>YOUR SEARCH BASE</BDISearchBase1>
       <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
        <BDIConnectionPassword>PASSWORD</BDIConnectionPassword>
        <BDIEnableTLS>0</BDIEnableTLS>
   </Directory>
</config>
For example, let´s assume the following:
- Domain controller IP address is 10.1.1.2 .
- Your presence domain is test.local .
- Your search base will be test.local using the top level of the domain.
- Your username with which you will be doing your searches is called walt . Usually you can either identify walt as test.local\walt or [email protected] . It is always best, in these sort of scenarios, to use the UPN convention so we will be configuring a [email protected] .
- The password is the Active Directory password for the account walt .
- I have disabled TLS in my case. There are issues with the Jabber for Mac client when using other security methods.
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
    <Directory>
        <DirectoryServerType>BDI</DirectoryServerType>
        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>10.1.1.2</BDIPrimaryServerName>
        <BDIPresenceDomain>test.local</BDIPresenceDomain>
        <BDIServerPort1>3268</BDIServerPort1>
        <BDISearchBase1>DC=test,DC=local</BDISearchBase1>
       <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
        <BDIConnectionPassword>walt01!</BDIConnectionPassword>
        <BDIEnableTLS>0</BDIEnableTLS>
   </Directory>
</config>
One you have configured the jabber-config.xml file, you will now need to upload it to you TFTP server. Once uploaded, you will need to restart the Cisco TFTP service. Again, my TFTP server is on my CUCM publisher, so:
- I go to Cisco Unified OS Administration on my Publisher server, TFTP File Management and I upload jabber-config.xml to / directory
- I then go to Cisco Unified Serviceability on my Publisher server, I locate the Cisco TFTP service and I restart the service
Once this is done, you can figure up your Jabber for Mac client. As a test, on your Mac (using Terminal) go to:
/Users/username/Library/Application Support/Cisco/Unified Communications/Jabber/Config
In here you will see several files, but what we want to see is jabber-config.xml . As soon as you start the Jabber for Mac client and log in, the jabber-config.xml file will download from your TFTP server and get saved here. When you see it appear, just type in your terminal window more jabber-config.xml and make sure that the output is the same as the xml file you created.
From there, try doing directory search. If you have previously added contacts and they still lack attribute information, you will need to remove them (sometimes it will not refresh properly) and add them again from the directory.
I will be updating this guide and ammending anything that is incorrect, but this is meant to be a quick checklist and steps to get this, at least in the most very basic version, up and running for Jabber for Mac.

Hello,
Thanks for this post! It works, I can do lookup and also I can add found contact to contact list and get information about contact from LDAP.
One more question: - I can't get all information about contact. I don't get e.c mobile phone number and more others attributes. I have tried to expand your file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>IP of AD</BDIPrimaryServerName>
<BDIPresenceDomain>Presence Domain</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1> Search Base</BDISearchBase1>
<BDIConnectionUsername>User</BDIConnectionUsername>
<BDIConnectionPassword>Password</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
       <BDISipUri>msRTCSIP-PrimaryUserAddress</BDISipUri>
       <BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
       <BDIBusinessPhone>telephoneNumber</BDIBusinessPhone>
       <BDIMobilePhone>mobile</BDIMobilePhone>
       <BDIHomePhone>homePhone</BDIHomePhone>
       <BDIOtherPhone>otherTelephone</BDIOtherPhone>
       <BDITitle>title</BDITitle>
       <BDICompanyName>company</BDICompanyName>
<BDILocation>co</BDILocation>
<BDIPostalCode>postalCode</BDIPostalCode>
       <BDICity>l</BDICity>
       <BDIState>st</BDIState>
       <BDIStreetAddress>streetAddress</BDIStreetAddress>
</Directory>
</config>
But it didn't help.
When I capture lookup via Wireshark, I can see that Jabbers sends search request with bunch of attributes, but from LDAP answer contains only 8 attributes. (see attached screenshots)

Compatibility between Jabber for iphone 9.0.2 and CUCME 9.1 (IOS 15.2(4))

Hi,
I would like to know if Jabber for IPhone version 9.0.2 is compatible with a CUCME 9.1. The problem is that we are using Jabber for a couple of months running on a CUCME 8.6 and we did not have any problem and since we upgraded to 9.1, we lost some settings directly into Jabber settings.
We cannot configure anymore the voicemail and Directory settings and if we want to delete an account into Jabber, we need to delete the application from the phone and re-download it from the appstore after.
If anyone has some information on that, it will be very appreciated.
Thanks

Hi Steve,
Just checked the release notes of Jabber for iphone 9.0.2 and I see that we only support CME 8.6 and 8.8
HTH,
Christos

Jabber for Mac 9.2.1 Cannot communicate with the server

Hi All,
I'm using Webex and the Jabber for Mac 9.2.1 client that was automatically pushed. I see "Cannot communicate with the server" when I attempt to login.
The same credentials work correctly when using the 8.6.5 client version. I've attached the problem report file.
I would appreciate some guidance on what I need to do to get this to work.
Cheers,
Steve

We've seen this with a few of our users as well. All started noticing having issues Friday morning. As this is a hosted service for us via webex we had our engineers call in to Jabber support. Cisco performed a modification to their account and they were able to connect again. No SRV records were messed with.
***EDIT*** - This appears to have been caused by a certificate issue. The Trusted Root Certificate for QuoVadis expired and was not renewed on some machines.
Go here: https://www.quovadisglobal.com/QVRepository/DownloadRootsAndCRL.aspx
Install the Cert for : QuoVadis Root CA2 (in windows, download as DER>right click file>install)
Jabber should connect now. The issue was in SSL validation with the appropriate hosted servers.

HT4946 i am administrator for Mac. My husband and i both have separate iPhones with separate contacts. Since i0S 6.1 update these contacts are now shared which we do not want. I have set up separate iCloud email and account for my husband. How do i ensure

I am administrator for Mac. My husband and i both have separate iPhones with separate contacts. Since i0S 6.1 update these contacts are now shared which we do not want. I have set up separate iCloud email and account for my husband. How do i ensure that i

You can continue to use the current AppleID for iTunes, but your husband can create a new AppleID to use to create a new iCloud account that will be his own and not overlap with yours. If you do not have another email address to use for an AppleID, just get a free Gmail account and use that.
You can have as many AppleIDs as you want (or at least, as many as you have email addresses for). You can use a separate AppleID for the store, another for iCloud, and even another for iMessage if you wish.
You will want to keep the current one as the shared one for the store as all your previous purchases are permanently tied to it, and thus you need that AppleID to update or redownload your current purchased content.

If I buy a mac with mountain lion and then upgrade to mavericks wil I get iWork for free, If I buy a mac with mountain lion and then upgrade to mavericks wil I get iWork for free

If I buy a mac with mountain lion and then upgrade to mavericks will I get iWork for free.

If you buy a new Mac with Mountain Lion, any included software is free and can be redownloaded from AppStore for that machine only. Some software only gets reinstalled if OS X (only) gets installed over itself to fix issues. See #8 Step here.
..Step by Step to fix your Mac
If you upgrade to Mavericks usually only OS X itself is changed (sometimes the hidden User Library is also), all the software (and user accounts) also carries over (compatible or not), and Apple's software is upgraded.
So if your new Mountain Lion Mac comes with free iWork, then when you upgrade to Mavericks it will still be there.
If your new Mountain Lion does not come with free iWork, then it won't magically appear for free if you upgrade to Mavericks.
If you need a free Office suit, I suggest you look at the donationware LibreOffice.
You will likely need to control key or right click to "Open" LibreOffice to approve through OS X's "Gatekeeper".
You will need to manually update it also, as it's not on AppStore.
https://www.libreoffice.org/
Benefit of LibreOffice is it's completely cross-platform compatible, so you can share working files with Windows and Linux users, which you can't with iWork.
You also should learn Microsoft Office when you have the funds, because it's standardized in the business world.

Using IMOVIE '08 to import from DV camera to 'BUSLINK' external hard drive( formatted for MAC ) but no success and kept getting this message: The import was canceled. You may not have permission to write to /Volumes/BUSLINK/iMovie Events.localized. Thanx

Using IMOVIE '08 to import from DV camera to 'BUSLINK' external hard drive( formatted for MAC ) but no success and kept getting this message: The import was canceled. You may not have permission to write to /Volumes/BUSLINK/iMovie Events.localized. Thanx in advance!

I finally got a representative that was able to help me, she had me go to Get Info, by right clicking iMovie from the finder, and I had to click on Sharing & Permissions>Everyone>Read & Write

I have problems interfacing Outlook 2011 for Mac with my email provider Cable and Wireless Guernsey. Any ideas? Done everything C&W suggest

I have problems interfacing Outlook 2011 for Mac with my email provider Cable and Wireless Guernsey. Any ideas? Don everything C&W suggest

OK I just transitioned to MacMail, iCal, and Mac address book. Goodbye Outlook, It was great for 18 years and painful for the last year. Microsoft is losing share with subpar software development.

Configure Jabber for Mac with local CUCM and WebEx Connect

Similar Messages

Maybe you are looking for