Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Users might experience few discrepancies in Search results. We are working on this on our side. We apologize for the inconvenience it may have caused.
New Member

Jabber 9.2.4 Build 4528 on Win7

Hello everyone,

Jabber 9.2.4 on Win7

AD 2008R2 64bit

vCUCM 8.6.2 (pub/2 subs)

vCUPS 8.6.5 (pub/sub)

vCUC 8.6.2 (pub/sub)

I've got more than 1 Domain Controller getting pegged CPU because of Jabber client - because of transfers of data like placed calls & missed calls - the Domain Controller CPU utilization sorted list of processes had the Jabber client processes with phone numbers in view.

I changed the referenced DC port from 389 to 3268 in hopes of reducing the load on the DC for LDAP queries, but the CPU spikes continue.  I haven't reset anything after making that change - we will be recycling the clients after hours, and I'm assuming that is all that needs to be done for the port change to be fully updated?

If changing to port 3268 isn't where I can control whether call data like that is not sent from client to AD, where can I disable that behavior?  Sending call information records to Active Directory doesn't seem like a default behavior.



CreatePlease to create content