Issue with automatic AD sync for Jabber account creation
We are currently running TMS 13.1.2 and VCS X7.2.2 with TMS Agent Legacy mode. The Jabber accounts are synchronized with our Microsoft Active Directory domain. Synchronization works fine when we manually synchronize the different Jabber groups. The issue is with the automatic synchronization which occurs every day at 4am. We get the following error in the log-TMSAgent.txt file:
04:00:46,449 [btpool0-1] WARN com.tandberg.provisioning.external.impl.SecureAdConnection - Initial Login failed: Pre-authentication information was invalid (24) 04:00:46,449 [btpool0-1] WARN com.tandberg.provisioning.external.impl.SecureAdConnection - KrbException->Pre-authentication information was invalid (24) 04:00:46,449 [btpool0-1] WARN com.tandberg.provisioning.external.impl.SecureAdConnection - Asn1Exception->Identifier doesn't match expected value (906)
When these errors occur we can no longer manually sync the Jabber accounts until we restart the TMSAgentService service on the TMS server. Which account is this automatic synchronization task trying to use?
We will be upgrading TMS 13.2 with TMSPE but until this can happen we need to sort out this issue.
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. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...