jabber as call control only

[kennis1977]

Hi all,

for one of our customers we are trying to get jabber on mobile phones to registrar only to the callmanager as softphone so call control only.

we created some devices in callmanager and this all is working when push the jabber client to manually settings and add the ip address and tftp address.. however when we try automatic it won't work the dns srv records looks fine and is pointing to the callmanager addresses version 11.5

but when trying to login we get username or password not correct (this is the correct userid and password)

what can be the problem?

thanksss

[Chris Deren]

Sounds like your SRVs are not correct, can you verify you have _cisco-uds SRV properly pointing to CUCM nodes?

If so, your next move is to review the jabber logs from the client to see what is happening, these are pretty easy to read.

[kennis1977]

Yes the _cisco-uds srv records are pointing to the callmanager cluster (checked it with nslookup and wireshark) when starting jabber client.

so think we have to check the jabber logfiles right...

[Chris Deren]

Correct.

[kennis1977]

So checked to logfiles of jabber when trying to logon without the precense service..

authentication failed looks like this:

36,136 DEBUG [0x000013cc] [p\lifecycle\PresenceAuthenticator.cpp(0)] [IMPServices] [CSFUnified::PresenceAuthenticator::Authenticate] - Exit
2016-11-14 09:34:36,136 ERROR [0x000013cc] [s\impl\AuthenticationHandlerImpl.cpp(75)] [authentication-handler] [CSFUnified::AuthenticationHandlerImpl::AuthenticateImpl] - Authentication Failed
2016-11-14 09:34:36,136 DEBUG [0x000013cc] [src\framework\ServicesDispatcher.cpp(39)] [services-dispatcher] [CSFUnified::ServicesDispatcher::enqueue] - ServicesDispatcher.enqueue: AuthenticationHandlerCallback::OnAuthenticationFailed
2016-11-14 09:34:36,136 DEBUG [0x000012ec] [rc\framework\ServicesDispatcher.cpp(116)] [services-dispatcher] [CSFUnified::ServicesDispatcher::pumpNext] -  pumpNext.executing (AuthenticationHandlerCallback::OnAuthenticationFailed)
2016-11-14 09:34:36,136 INFO  [0x000012ec] [common\CertificateValidityCache.cpp(172)] [csf.cert] [csf::cert::CertificateValidityCache::clear] - Clearing accepted and rejected certificates from memory
2016-11-14 09:34:36,136 INFO  [0x000012ec] [ervices\impl\StartupHandlerImpl.cpp(327)] [startup-handler] [CSFUnified::StartupHandlerImpl::OnAuthenticationFailed] - Calling startupHandlerCallback.OnSystemLoginFailed
2016-11-14 09:34:36,136 INFO  [0x000012ec] [src\services\impl\LifeCycleImpl.cpp(802)] [Life-Cycle-Logger] [CSFUnified::LifeCycleImpl::Impl::OnSystemLoginFailed] - OnSystemLoginFailed - Callback received
2016-11-14 09:34:36,136 INFO  [0x000012ec] [rc\services\impl\LifeCycleImpl.cpp(1339)] [Life-Cycle-Logger] [CSFUnified::LifeCycleImpl::Impl::updateState] - Changing lifecycle State to: SIGNEDOUT
2016-11-14 09:34:3

rihjt now the end user is pushed by active directory... so windows authentication is the correct password however.. already tried to create a new end user with authentication by the callmanager and push this end user to the client services framework.. same result..