I found it. There was an InitialPhoneSelection keyword set to 'deskphone' in the policies section of the jabber-config.xml. I changed it to 'softphone', but perhaps I could have removed it. ... View more

No we're not using that. Thanks ... View more

Oops. I was going to restart Tomcat on the pub and see if it helped. That did it. Weird, I've never had it run slow like that. Must not have started right after the upgrade. Thanks for the response. ... View more

Jabber for Mac v9.6 fixed the SSL issues from v9.2.1 & 9.2.2.  So now I've removed the keywords BDIConnectionUsername & BDIConnectionPassword, and let it use a given user's jabber credentials for their directory lookups.   <BDIServerPort1>636</BDIServerPort1> <BDIEnableTLS>True</BDIEnableTLS> <BDIUseJabberCredentials>True</BDIUseJabberCredentials>   Not sure if I had to, but I also added this part to the top at some point in time. At the state of Jabber development at the time at least I think, it eliminated the user having to enter any hostnames during Jabber setup. <CUCM>   <PhoneService_UseCredentialsFrom>presence</PhoneService_UseCredentialsFrom> </CUCM>   <Presence>   <PresenceServerType>CUP</PresenceServerType> </Presence>   <Voicemail> <VoiceMailService_UseCredentialsFrom>phone</VoiceMailService_UseCredentialsFrom> </Voicemail> ... View more

Here's the jabber-config.xml file I used to get directory searches for Mac Jabber 9.2.1 working in AD environment.  Note that though I am using TLS, I could not get it working over the standard ldaps (636) port. I assume this is a bug in 9.2.1, but in any case wireshark confirms it is doing ssl.  Also, I have the UCM service profile for Jabber is set to ldap not global catalog mode if that even matters when using a config file. <?xml version="1.0" encoding="UTF-8"?> <config version="1.0">     <Directory>         <DirectoryServerType>BDI</DirectoryServerType>         <BDILDAPServerType>AD</BDILDAPServerType>         <BDIPrimaryServerName>1.1.1.1</BDIPrimaryServerName>         <BDIPresenceDomain>mycompany.com</BDIPresenceDomain>         <BDIServerPort1>389</BDIServerPort1>         <BDISearchBase1>ou=My Users,dc=ad,dc=mycompany,dc=com</BDISearchBase1>         <BDIConnectionUsername> ucm_query@ad.mycompany.com </BDIConnectionUsername>         <BDIConnectionPassword>my_password</BDIConnectionPassword>         <BDIEnableTLS>1</BDIEnableTLS>         <BDIBaseFilter>(&(objectCategory=person)</BDIBaseFilter>     </Directory> </config> NOTE (from v9.2.1 doc): The default value is (&(objectCategory=person). Configuration files can contain only valid XML character entity references. Use &amp; instead of & if you specify a custom base filter. ... View more

My memory may be incorrect, but I think the SSH rule error was a cosmetic bug and not related to the main problem, which I do remember well.  Namely, the mobility connectivity problems.  Those problems began after shifting a number of APs onto a lightly loaded controller.  The mobility issues baffled everyone, and I finally just moved the APs back off the affected controller and the mobility issues went away.  Moved them back again and the mobility problems did not return.  It must have been some bizarre fluke. ... View more

If the switches are 4500s, you can use the 'show int link' command.  Here is an example from a 4500 of mine.  I have not seen documentation on this and I don't understand why, nor why it is only available on 4500 series. Port    Name               Down Time        Down Since Te1/1                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Te1/2                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi1/3                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi1/4                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi1/5                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi1/6                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi2/1                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi2/2                      29 weeks, 5 days, 21 hours, 15 minutes 40 secs      20:24:52  Sat Apr 14 2012 Gi2/3                      5 weeks, 10 hours, 57 minutes 32 secs      06:43:00  Fri Oct 5 2012 ... View more

That isn't my understanding.  My understanding is that compatibility works within major version numbers. http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp89677 ... View more