Initializes a new instance of the SIP_ResponseCodes class.

The server received a request with a Request-URI that was incomplete. Additional information SHOULD be provided in the reason phrase.

The Request-URI was ambiguous.

The server did not understand the protocol extension specified in a Proxy-Require or Require header field.

The server, while acting as a gateway or proxy, received an invalid response from the downstream server it accessed in attempting to fulfill the request.

The request could not be understood due to malformed syntax. The Reason-Phrase SHOULD identify the syntax problem in more detail, for example, "Missing Call-ID header field".

The callee's end system was contacted successfully but the callee is busy and does not wish to take the call at this time.

The callee's end system was contacted successfully, but the callee is currently not willing or able to take additional calls at this end system. The response MAY indicate a better time to call in the Retry-After header field.

A server MAY use this status code to indicate that the call is being forwarded to a different set of destinations.

This status indicates that the UAS received a request that does not match any existing dialog or transaction.

The callee's machine was successfully contacted but the user explicitly does not wish to or cannot participate.

The server has authoritative information that the user indicated in the Request-URI does not exist anywhere

Determines whether the specified Object is equal to the current Object.

The UAS needs a particular extension to process the request, but this extension is not listed in a Supported header field in the request. Responses with this status code MUST contain a Require header field listing the required extensions.

Allows an Object to attempt to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection.

The server understood the request, but is refusing to fulfill it. Authorization will not help, and the request SHOULD NOT be repeated.

Serves as a hash function for a particular type. GetHashCode() is suitable for use in hashing algorithms and data structures like a hash table.

Gets the Type of the current instance.

The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent.

The server is rejecting the request because the expiration time of the resource refreshed by the request is too short. This response can be used by a registrar to reject a registration whose Contact header field expiration time was too small.

The server has detected a loop.

Creates a shallow copy of the current Object.

The server was unable to process the request since the message length exceeded its capabilities.

The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI.

The resource identified by the request is only capable of generating response entities that have content characteristics not acceptable according to the Accept header field sent in the request.

The user's agent was contacted successfully but some aspects of the session description such as the requested media, bandwidth, or addressing style were not acceptable.

The response has the same meaning as 606 (Not Acceptable), but only applies to the specific resource addressed by the Request-URI and the request may succeed elsewhere.

The server has definitive information that the user does not exist at the domain specified in the Request-URI.

The server does not support the functionality required to fulfill the request.

The request has succeeded.

This code is similar to 401 (Unauthorized), but indicates that the client MUST first authenticate itself with the proxy.

The called party is temporarily unavailable, but the server has decided to queue the call rather than reject it. When the callee becomes available, it will return the appropriate final status response.

The server is refusing to process a request because the request entity-body is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.

The request was received by a UAS that had a pending request within the same dialog.

The request was terminated by a BYE or CANCEL request. This response is never returned for a CANCEL request itself.

The server could not produce a response within a suitable amount of time, for example, if it could not determine the location of the user in time.

The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.

The UA receiving the INVITE is trying to alert the user.

The server encountered an unexpected condition that prevented it from fulfilling the request.

The server is temporarily unable to process the request due to a temporary overloading or maintenance of the server.

The 183 (Session Progress) response is used to convey information about the progress of the call that is not otherwise classified.

The callee's end system was contacted successfully but the callee is currently unavailable (for example, is not logged in, logged in but in a state that precludes communication with the callee, or has activated the "do not disturb" feature).

The server did not receive a timely response from an external server it accessed in attempting to process the request.

The server received a request that contains a Max-Forwards.

Returns a String that represents the current Object.

This response indicates that the request has been received by the next-hop server and that some unspecified action is being taken on behalf of this call (for example, a database is being consulted).

The request requires user authentication.

The request was received by a UAS that contained an encrypted MIME body for which the recipient does not possess or will not provide an appropriate decryption key.

The server is refusing to service the request because the message body of the request is in a format not supported by the server for the requested method. The server MUST return a list of acceptable formats using the Accept, Accept-Encoding, or Accept-Language header field, depending on the specific problem with the content.

The server cannot process the request because the scheme of the URI in the Request-URI is unknown to the server.

The server does not support, or refuses to support, the SIP protocol version that was used in the request.