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.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4