I am trying to deploy Jabber for Mac and Ipads (version 9), and everithing is ok, the problem is the Software Phone, always in "Disconected" state, if i use Jabber for Mac 8.X, it works.. the client register to my jabber software phone and my deskphone, by the way, only deskphone works in Jabber 9 for Mac and iPad, i revised all the configuration files in cucm and cups.. any help?
Ok I figured out what is going on as far as SSL directory searches of AD, though there are aspects I still don't understand. In one of the docs for Jabber v9.2.1 it says that you can't use the global catalog with a Mac. So why the Mac client defaults to 3268 is beyond me. But I also can't use BDIServerPort1=636 and BDIEnableTLS=1 or 0. But I can use 389 and TLS=1 and I can see using wireshark that it is encrpting the the directory query to AD.
That works. Apparently 389+TLS and LDAPS aren't the same thing. The ipad document here distinguishes between "LDAP TCP 389 LDAP with optional TLS" and "Secure LDAP 636 LDAPS". Sounds similar to SFTP vs FTPS.
Update: I swear it was encrypting the directory search with SSL over port 389 but I can't duplicate that. I'll work with Cisco on ldaps on 636. But the xml file above does work for me without SSL on 389.
Also, the docs say "Cisco Jabber for Mac does not support port 3269 (Active Directory Global Catalog over LDAPS)", not Global Catalog generally. It may not work for me over 3268 because of our AD setup. I'm not an AD guy and another group manages that.
Ok, the problem was that BDIEnableTLS needs to be 'True' and not '1'. So it seems StartTLS (as an extended operation) works over port 389 on the Mac Jabber client and the plain SSL method doesn't. I see the Windows version has a 'UseSSL' parameter but the Mac one doesn't so maybe that is just the way the Mac client works at this point.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...