Cisco
300-085 · Question #82
300-085 Question #82: Real Exam Question with Answer & Explanation
The correct answer is A: if the user primary extension is set to "none" on Cisco Unified Communications Manager. When importing users into Cisco Unity Connection via AXL, a user will not appear in the import view if their primary extension is set to 'none' on CUCM, because Unity Connection requires a valid directory number to identify and map the user.
Cisco Unity Connection
Question
When importing users into Cisco Unity Connection by using AXL, what can cause a user not to be listed in the import view?
Options
- Aif the user primary extension is set to "none" on Cisco Unified Communications Manager
- Bif the userdigest credentials are not set
- Cif the userwas imported into Cisco Unified Communications Manager by usingLDAP
- Dif the user is not assigned to the Standard CTI Enabled access control group on Cisco Unified
Explanation
When importing users into Cisco Unity Connection via AXL, a user will not appear in the import view if their primary extension is set to 'none' on CUCM, because Unity Connection requires a valid directory number to identify and map the user.
Common mistakes.
- B. Digest credentials control SIP authentication behavior and do not affect whether a user is listed or visible in the Unity Connection AXL import view.
- C. Users imported into CUCM via LDAP synchronization are still visible and importable through AXL into Unity Connection; the import mechanism does not filter based on how the user was originally provisioned in CUCM.
- D. The Standard CTI Enabled access control group is required for CTI and JTAPI applications to control devices, not for AXL-based user import operations in Unity Connection.
Concept tested. AXL user import requirements for Unity Connection
Topics
#AXL import#user import#primary extension#CUCM integration
Community Discussion
No community discussion yet for this question.