Jabber login error

[anthonykaune]

I am trying to figure out a Jabber login issue for a lab we just spun up.  

Jabber looks to be getting the error failed_ucm90_connection.  

Jabber fails with cannot communicate with server and never even prompts for certificate acceptance (standard self signed certs from install are on the UCM and IMP).

SRV records for both _cuplogin._tcp and _cisco-uds._tcp resolve to the A records for the IMP and UCM servers.  The A records resolve to the IP's.  They can be pinged from the PC.

https://<CUCM IP/FQDN> :8443/cucm-uds/version is reachable from a web browser on the PC.

Services are all running.  Hard phones registered no problem.  Also when using a manual config for jabber it works to point jabber at the UCM.  

UC Service profile is setup and applied to the user.  

Any ideas what else to check?

[Maren Mahoney]

First, you want to have _cisco-uds._tcp records pointing to the CUCM servers (only) and get rid of the _cuplogin records unless you are still running the old CUPC clients or are running really old Jabber clients.

Second, can you use nslookup on the host PC to verify that it is able to resolve the _cisco-uds records for the domain the user is logging in with?

Third, if you've made changes in DNS have you reloaded the zone(s) and even maybe restarted the DNS service (in the DNS snapin)?

If those three things are true, you should at least get the prompt for the server acceptance (unless it has done so already). If not, use the Jabber client to produce a PRT and post it here and we'll take a look.

Maren

[anthonykaune]

the NSlookup does resolve.  I did reload the DNS and the problem remains.  

It looks to me like UCM just isn't responding.  Which doesn't make sense because it is reachable.  

I'll see if I can transfer the logs out.  

[Roger Kallberg]

Can you please post the output from you nslookup for us to be able to verify that it's correct?

[anthonykaune]

Thanks All!  I believe it has something to do with the DNS or the way DNS is configured on the UCM.  

After trying a few more things I deleted and rebuilt the UCM and IMP servers with a different domain and now everything seems to be working just fine.  

[mdrangell22]

I had a simular problem and It was caused for an Incoming Rule in a Firewall after this was eliminated My jabber never show me that error code again.