300-810 · Question #290
An engineer is integrating a Cisco UCM cluster with a Cisco Unity Connection cluster and discovers that users are not imported from Cisco UCM to Unity Connection. The port and port groups are…
The correct answer is A. Ensure that the AXL server is configured and operational. Cisco Unity Connection imports users from Cisco UCM using the AXL (Administrative XML) Web Service API. Even though ports, port groups, and voicemail functionality work correctly (which rely on SIP/SCCP), user synchronization is a separate process that depends entirely on AXL…
Question
An engineer is integrating a Cisco UCM cluster with a Cisco Unity Connection cluster and discovers that users are not imported from Cisco UCM to Unity Connection. The port and port groups are configured. Calls can be received, and messages left on the manually configured test accounts are working. Which action resolves the issue?
Options
- AEnsure that the AXL server is configured and operational.
- BEnsure that Cisco UCM and Unity Connection are pointing to the same LDAP group.
- CEnsure that SCCP, not SIP, is configured for this combination.
- DEnsure that LDAP services are running.
How the community answered
(27 responses)- A70% (19)
- B19% (5)
- C7% (2)
- D4% (1)
Explanation
Cisco Unity Connection imports users from Cisco UCM using the AXL (Administrative XML) Web Service API. Even though ports, port groups, and voicemail functionality work correctly (which rely on SIP/SCCP), user synchronization is a separate process that depends entirely on AXL. If AXL is not configured or the AXL service is not running on the UCM publisher, Unity Connection cannot query UCM for user data. LDAP services (D) are separate and would affect UCM's own directory integration, not the UCM-to-Unity Connection user import. SCCP vs SIP (C) affects call signaling, not user import.
Topics
Community Discussion
No community discussion yet for this question.