300-820 · Question #32
Refer to the exhibit. Mobile Cisco Jabber cannot register with on-premises Cisco Unified Communications Manager using Mobile and Remote Access. Some logs were captured on Expressway Edge. Which action
The correct answer is C. Ensure that the credential has been entered correctly.. When MRA registration fails and Expressway Edge logs show authentication errors, the root cause is typically incorrect credentials entered in the Jabber client. MRA authenticates the user against CUCM's LDAP directory or local user database via Expressway, so a wrong username or
Question
Refer to the exhibit. Mobile Cisco Jabber cannot register with on-premises Cisco Unified Communications Manager using Mobile and Remote Access. Some logs were captured on Expressway Edge. Which action corrects this problem?
Exhibit
Options
- AEnsure that the peer address does not match the Common Name on certificate.
- BEnsure that the _cisco-uds SRV record has been configured.
- CEnsure that the credential has been entered correctly.
- DEnsure that the SIP domains are added on Expressway Core.
How the community answered
(55 responses)- A7% (4)
- B2% (1)
- C87% (48)
- D4% (2)
Explanation
When MRA registration fails and Expressway Edge logs show authentication errors, the root cause is typically incorrect credentials entered in the Jabber client. MRA authenticates the user against CUCM's LDAP directory or local user database via Expressway, so a wrong username or password will produce authentication failure log entries on Expressway-E. Option A (certificate CN mismatch) would produce TLS handshake errors, not authentication failures. Option B (_cisco-uds SRV record) relates to CUCM service discovery and would produce DNS lookup failures. Option D (SIP domains on Expressway Core) would prevent Expressway from routing the registration, showing domain-not-found errors rather than authentication failures.
Topics
Community Discussion
No community discussion yet for this question.