SignalingTransitionReason Enumeration
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.
Enumerates the possible reasons for signaling state transitions.
Namespace: Microsoft.Rtc.Signaling
Assembly: Microsoft.Rtc.Collaboration (in microsoft.rtc.collaboration.dll)
Syntax
'Declaration
Public Enumeration SignalingTransitionReason
public enum SignalingTransitionReason
Members
Member name | Description |
---|---|
Busy | The called party is not willing or able to take additional sessions. |
Canceled | The operation is canceled (that is, for an Invite). |
Declined | The session or participant declined. |
None | No reason or unknown reason. |
NotAcceptable | The called party can only generate responses with content characteristics that are not acceptable to the Accept header field sent in the request. |
NotAcceptableMedia | There is a problem or the media portion of the session description is incompatible. |
ProvisionResponseReceived | The session received a provisional response in the range 101-199. |
SessionDoesNotExist | The remote does not have the session and sent a 481 Bad Call Leg response. |
SessionTimerExpired | The session timer expired. The remote seems to be unreachable. |
TemporarilyUnavailable | The called party is not available for communication or does not want to be disturbed. |
TerminatedLocally | The local application requested the termination. |
TerminatedRemotely | The (last) remote user requested the termination. |
Timeout | An operation timed out. |
Unreachable | The called party is not reachable. |
Platforms
Development Platforms
Windows XP Professional with Service Pack 2 (SP2), Windows Server 2003, Windows Vista Ultimate Edition, Windows Vista Business Edition, Windows Vista Enterprise Edition