300-820 · Question #61
An administrator is configuring a new Cisco Webex Hybrid Message Service deployment, and the Expressway-C Message Connector is successfully registered in the Control Hub. After the server…
The correct answer is D. Enable a second administrator account for AXL API permissions on the IM and Presence Service. The AXL API on IM and Presence Service does not allow the primary platform administrator account to be used for AXL queries initiated by the Expressway-C Message Connector. Cisco's implementation requires a dedicated, separate administrator account with AXL API permissions to…
Question
An administrator is configuring a new Cisco Webex Hybrid Message Service deployment, and the Expressway-C Message Connector is successfully registered in the Control Hub. After the server information of the IM and Presence server is added to the Expressway-C, an error "Connectivity to IM and Presence AXL Service could not be established" is displayed in the Control Hub. The Cisco AXL Web Service is enabled on the IM and Presence Service publisher, and the main administrator account enabled for AXL API permission is being used. Which configuration change must be made to resolve this error?
Options
- AEnable the Cisco AXL Web Service on the Control Hub
- BEnable the Cisco AXL Web Service on the Expressway-C Message Connector
- CEnable an End User account for AXL.API permissions on the IM and Presence Service publisher
- DEnable a second administrator account for AXL API permissions on the IM and Presence Service
How the community answered
(32 responses)- A3% (1)
- B16% (5)
- C9% (3)
- D72% (23)
Explanation
The AXL API on IM and Presence Service does not allow the primary platform administrator account to be used for AXL queries initiated by the Expressway-C Message Connector. Cisco's implementation requires a dedicated, separate administrator account with AXL API permissions to be created and configured. Even though the main administrator account appears to have the right role, using it directly for external connector AXL access is not supported and causes this connectivity error. Creating and configuring a second administrator account with AXL API permissions resolves the issue.
Topics
Community Discussion
No community discussion yet for this question.