nerdexam
Cisco

300-085 · Question #82

When importing users into Cisco Unity Connection by using AXL, what can cause a user not to be listed in the import view?

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

How the community answered

(52 responses)
  • A
    71% (37)
  • B
    4% (2)
  • C
    17% (9)
  • D
    8% (4)

Why each option

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.

Aif the user primary extension is set to "none" on Cisco Unified Communications ManagerCorrect

Cisco Unity Connection uses the primary extension (directory number) from CUCM to uniquely identify users during AXL-based import; if the extension is set to 'none,' the user has no DN to associate with a voicemail account and is excluded from the import view.

Bif the userdigest credentials are not set

Digest credentials control SIP authentication behavior and do not affect whether a user is listed or visible in the Unity Connection AXL import view.

Cif the userwas imported into Cisco Unified Communications Manager by usingLDAP

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.

Dif the user is not assigned to the Standard CTI Enabled access control group on Cisco Unified

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

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/administration/guide/b_11xcucagx.html

Topics

#AXL import#user import#primary extension#CUCM integration

Community Discussion

No community discussion yet for this question.

Full 300-085 Practice