/mcpC H A P T E R 6 Cisco Unity Connection Imaging Interface (CUII) API -- Error Handling Links to Other API pages: Cisco_Unity_Connection_APIs • Cisco Unity Connection Imaging Interface (CUII) API -- Error Handling , on page 11 Cisco Unity Connection Imaging Interface (CUII) API -- Error Handling Links to Other API pages: Cisco_Unity_Connection_APIs Possible Errors The HTTP status codes themselves provide information about many typical errors. See the following list for some of the status codes returned by CUII: Troubleshooting Cause Description Possible Errors As the error clearly specifies the user does not have necessary permissions to access the information, so either provide admin credentials or admin should assign the user the necessary role. The cause of this error can be that the user credentials provided in the request are not authorized to view the information requested in the API. This means there has been an error in authentication and the response text will have a "Not Authorized" message. 401 This is actually not a problem. The throttling is implemented to save connection's tomcat server from taking up multiple requests which can cause issues in memory, DB etc. The cause of this error can be that the connection server is processing multiple simultaneous API requests so it is not able to take up that request at that particular time. This means "Server Busy". It signifies that the connection server is busy and cannot handle this request at that time. 503 Cisco Unity Connection Imaging Interface (CUII) API 11
