Cisco Jabber Invalid Username/Password

[c.carrion]

Hi ,

upgraded my cisco callmanager to 9.1.2SU1 (Previous version 9.1.1a) and add UDS COP file and now i have problem to login internal (via finding service , Manual is OK)

Any advice

Thanks for your help

[Amit Kumar]

i see that it is trying to do a UDS SRV query;

About to make a dns request against _cisco-uds._tcp.domain.com.pe.
-- 2014-04-15 00:27:54.731 INFO [b2b8000] - [csf.dns][makeQuery] Making an SRV record request. _cisco-uds._tcp.domain.com.pe.

and fails with the following message;

Ucm Locator query has failed with FAILED_TO_FIND_HOME_UDS
-- 2014-04-15 00:27:54.761 WARNING [b0f5000] - [csf.config][fetchXmlFileSet] No information available after doing a fetch.
-- 2014-04-15 00:27:54.761 DEBUG [b0f5000] - [csf.config][fetchXmlFileSet] Returning: FAILED_TO_FIND_HOME_UDS
-- 2014-04-15 00:27:54.761 INFO [b0f5000] - [csf.config][fetchXmlFileSet] Time taken to complete the ucm-config library fetchXmlFileSet(): 0 seconds.
-- 2014-04-15 00:27:54.762 INFO [b0f5000] - [service-discovery][authenticate] Ucm90 Library Returned with Code FAILED_TO_FIND_HOME_UDS

is the UDS SRV record provisioned in the network ; or do you have _cuplogin record configured.

[c.carrion]

Hi,

My srv records.

> set type=srv
> _cisco-uds._tcp.domain.com.pe
Server:        10.251.25.101
Address:    10.251.25.101#53

_cisco-uds._tcp.domain.com.pe    service = 0 0 8443 10.251.1.10.
> _cuplogin._tcp.domain.com.pe
Server:        10.251.25.101
Address:    10.251.25.101#53

_cuplogin._tcp.domain.com.pe    service = 0 0 8443 10.251.1.16.
>

Thanks for your help

[Amit Kumar]

i see the following information mentioned in the document;

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html#CJAB_RF_S2C1A378_00

"You should use the fully qualified domain name (FQDN) as the hostname in the SRV record."

in your case the hostname look to be ip address. If this is a lab setup can you try to ensure you correct this to FQDN( note this will also need A records) once done re test the log in. If this is a production setup kindly ensure you accommodate downtime before trying this.