Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Error handling
If the Cisco TMS server is operational with the proper licenses, errors are caused by sending the wrong
parameters to the API, such as trying to create a booking in the past, or trying to get systems, users, or
conferences from Cisco TMS using the wrong ID. When an exception is caught, it is generally an indication
that the client call must be changed before it is sent again.
parameters to the API, such as trying to create a booking in the past, or trying to get systems, users, or
conferences from Cisco TMS using the wrong ID. When an exception is caught, it is generally an indication
that the client call must be changed before it is sent again.
Exceptions
All errors generated from the API are SoapExceptions, hence each time a save operation is performed
against the API, the code should handle exceptions of type SoapException.
against the API, the code should handle exceptions of type SoapException.
The message field of the exception will contain a string with a description of what went wrong. In many
cases, displaying this information to the user will be helpful.
cases, displaying this information to the user will be helpful.
HTTP error 401
The server will normally return the HTTP error code 500 Internal Server Error for the SoapExceptions.
If the HTTP error code 401 Unauthorized is received, the user credentials supplied were not authorized to
access the server.
access the server.
Cisco TMSBA Programming Reference Guide
Page 56 of 68
Error codes and error handling