210-060 · Question #21
An end user is unable to sign into Jabber. Assuming that network connectivity has been verified, which three settings for the end user should be checked? (Choose three.)
The correct answer is A. Jabber Advanced Settings B. Cisco Unified Communications Manager Service Profile C. Cisco Unified Communications Manager User Management. When a user cannot sign into Jabber, the administrator should verify the user's Jabber client settings, the assigned CUCM Service Profile, and the user account configuration in CUCM User Management.
Question
An end user is unable to sign into Jabber. Assuming that network connectivity has been verified, which three settings for the end user should be checked? (Choose three.)
Options
- AJabber Advanced Settings
- BCisco Unified Communications Manager Service Profile
- CCisco Unified Communications Manager User Management
- DCisco Unified Presence Server Advanced Settings
- ECisco Unified Presence Server Application Listener
- FCisco Unified Presence Server System Topology
- GJabber Version
How the community answered
(58 responses)- A78% (45)
- D12% (7)
- E5% (3)
- F3% (2)
- G2% (1)
Why each option
When a user cannot sign into Jabber, the administrator should verify the user's Jabber client settings, the assigned CUCM Service Profile, and the user account configuration in CUCM User Management.
Jabber Advanced Settings control client-level configuration such as server discovery and connection modes, which directly affect whether Jabber can authenticate and connect.
The CUCM Service Profile assigned to the end user defines which UC services (IM and Presence, voicemail, conferencing) Jabber uses; an incorrect or missing profile prevents successful login.
CUCM User Management contains the end user account credentials, associated devices, and enabled services; misconfigured user accounts are a common cause of Jabber sign-in failures.
Cisco Unified Presence Server Advanced Settings are system-wide configuration items not typically checked on a per-user basis for basic sign-in issues.
The Application Listener on CUPS relates to server-side SIP/XMPP port configuration, not to an individual user's inability to sign in.
System Topology in CUPS defines cluster relationships and is not a user-specific troubleshooting point for sign-in failures.
While compatibility matters, verifying the Jabber version alone does not address the configuration settings that govern a specific user's ability to authenticate.
Concept tested: Jabber end-user sign-in troubleshooting in CUCM
Source: https://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-windows/116674-troubleshoot-jabber-windows-00.html
Topics
Community Discussion
No community discussion yet for this question.