This URL must be tested for all CUCM Servers in the cluster. If the response is unsuccessful, verify that the DNS is configured correctly to resolve them and also if no Network Elements like Firewall/ASA block the port 8443. Test if you are able to open this URL in the browser on the PC :8443/cucm-uds/version Sample Log Snippet 12:04:00,282 INFO - ServiceDiscoveryHandlerResult return code FAILED_UCM90_CONNECTION Jabber is unable to resolve/reach the CUCM FQDN/HOSTNAME that it received during the Service discovery Tip: From the LDAP Server perspective, ensure that the account is not locked, that the passwords are not expired, and that all the users are synchronized with the CUCM server. If this issue is seen for all users, verify if the LDAP synchronisation and LDAP Authentication settings on CUCM Administration > System > LDAP is correct. This image refers to the scenario where the LDAP is unable to authenticate the user either because the user is not a valid user or the password supplied is incorrect. ![]() Verify that credentials are correct and the user is active. Navigate to CUCM Administration > Enduser page. Ensure that the User is configured as an enduser in CUCM. Sample Log Snippet 08:59:10,652 INFO - ServiceDiscoveryHandlerResult return code FAILED_UCM90_AUTHENTICATION This error is seen when the credentials entered is wrong or the user is locked in CUCM/LDAP Restart these services on all the CUCM nodes. Validate that the CUCM nodes configured as TFTP Servers are up and running. HTTP response code 503 for request #29 to This error is seen when the Jabber is unable to retrieve the UDS or TFTP Servers to gather its log in information and configuration settings. If no records are returned, contact your DNS administrator to configure the SRV records This is an example of the Successful _cisco-uds SRV record. This returns the DNS A records which point to the CUCM servers. Start the command prompt (on a Windows Client) and then enter nslookup. 17:55:00,438 WARN - *-* DNS query _cuplogin._tcp.applab has failed: DNS name does not exist. (9003). Sample Log Snippet 017-03-19 17:55:00,422 WARN - *-* DNS query _cisco-uds._tcp.applab has failed : DNS name does not exist. This error is seen when the _cisco-uds or _cuplog in SRV records are not configured in the DNS server Click Advanced settings to set up manually CUCM Service Discovery Error on screenĬannot find your services automatically. LERR - shows the Log in Errors when the Jabber fails to log in to the IM&P Server. shows when the XMPP log in was successful. Keywords to Search in Logs IMPStackCap::Log in::OnLog log in cup succeeds - shows when the SOAP log in was successful. How to collect logs from Expressway (When Jabber is over MRA). ![]() (From the Jabber Help menu, select Report a problem option to launch the problem report tool. %AppData%\Roaming\Cisco\Unified Communications\Jabber\ %AppData%\Local\Cisco\Unified Communications\Jabber\ Sign out and exit the Jabber application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |