Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Error
Code
Description
INSTANCE_NOT_FOUND_
WITHIN_PATTERN
WITHIN_PATTERN
-2147218252 The client tried to save or get a conference occurrence that is not
part of the recurrence pattern of the series. Error message "No
such occurrence".
such occurrence".
ERR_CLIENT_SESSION_
BLANK
BLANK
-2147218247 The client provided a session ID that was blank or null, which is not
permitted. Cisco TMS will add a new session ID on the thrown
SOAP exception which the client can use in subsequent calls.
SOAP exception which the client can use in subsequent calls.
ERR_CLIENT_SESSION_
EXPIRED
EXPIRED
-2147218253 The provided client session ID has expired. Cisco TMS will add a
new session ID on the thrown SOAP exception which the client can
use in subsequent calls.
use in subsequent calls.
ERR_USER_NOT_FOUND
-2147218255 The provided user information could not be resolved to an existing
user, and Cisco TMS was not able to create a new user. See the
server logs for details.
server logs for details.
If an exception is thrown, the exception message will contain the reason. If you get "Unspecified
Exception"/"Unspecified Error", this usually means that there is a syntax flaw in the conference sent to the
SaveConferenceWithMode function.
Exception"/"Unspecified Error", this usually means that there is a syntax flaw in the conference sent to the
SaveConferenceWithMode function.
In such a case, an error description would be given in the Cisco TMS log files, which you can download from the
Cisco TMS website, or locate in the folder (/tms/data/logs/tmsdebug/log-web.txt) on the Cisco TMS server.
Cisco TMS website, or locate in the folder (/tms/data/logs/tmsdebug/log-web.txt) on the Cisco TMS server.
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.
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.
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.
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.
server.
54
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide