This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Unified Communications Managed API 2.0 Core SDK follows the standard .NET Framework exception model for reporting exceptions. Both the standard exception classes in the .NET Framework and custom exception classes specific to UCMA 2.0 Core SDK are used. UCMA 2.0 Core SDK applications should catch exceptions thrown by UCMA 2.0 Core SDK methods. In addition we recommend that applications validate the data they pass to the API to avoid exceptions derived from ArgumentException from being thrown in released products.
The following custom exception classes are implemented in UCMA 2.0 Core SDK.
Except for RealTimeInvalidOperationException, this is the root class for the exceptions that are specific to UCMAV1.0 and UCMA 2.0 Core SDK. It is thrown when the error condition cannot be mapped to any other exception types.
Thrown when an error associated with conference scheduling or management occurred when communicating with the server. Possible reasons for this exception being thrown include the following:
The conference could not be created, scheduled, retrieved, or removed.
The conference could not have its settings modified.
The check failed for whether a passcode is optional for a conference.
The conference passcode could not be verified.
A failure occurred in the attempt to get the available MCU types for a conference.
Failure to communicate with the server components for conferencing could result in FailureResponseException.
Thrown when a network connection could not be made. Applications might consider prompting for a new URI (host and port) or a server name.
Thrown when a 4xx, 5xx, or 6xx response was received for a request. This exception contains the ResponseData property, which contains the complete response including response code, reason text, headers, and message body. In some rare cases, this may also be thrown when an error other than a 4xx, 5xx, or 6xx response occurred. In such cases the ResponseData property is null.
Thrown when a 401 response was received in authentication. It exposes the failed response data (ResponseData) and parsed values of authentication-specific headers.
Thrown when a FailureResponseException occurred for requests of the SERVICE and SUBSCRIBE types. This class inherits from FailureResponseException and adds diagnostic information about the message body and the fault code parsed from the body.
Thrown when an error occurred in a registration-related operation.
Thrown when an operation is rejected due to server policy.
Thrown when an incoming response or message could not be parsed. For example, an invalid custom signaling header was used.
Thorwn when a parsing error occurs during multipart body parsing.
Thrown when one of the following errors occurred in a media provider:
The SDP for the offer could not be created.
The answer received from the remote side could not be accepted.
A collision in the offer/answer interchange occurred because a previous negotiation is still pending.
An answer for a received offer could not be sent.
Thrown when an operation fails. The FailureReason property indicates the cause of failure.
Thrown when an operation could not be completed in a reasonable time. For example, a response from another endpoint or server was not received after a request was sent.
Thrown when an error occurred during a TLS handshake. This error can occur when the remote server certificate is rejected. This can also occur when the MTLS local certificate is rejected by the remote server.
Thrown when the operation is currently invalid, but the application might be able to take further action based on the reason.
The following object model lists the exceptions that are specific to UCMA 2.0 Core SDK.
Was this page helpful?
Your feedback about this content is important. Let us know what you think.
1500 characters remaining
We appreciate your feedback.
Have a suggestion to improve MSDN Library?
Visit our UserVoice Page to submit and vote on ideas!