This class holds SIP respnse codes.
Declaration Syntax| C# | Visual Basic | Visual C++ | F# |
public class SIP_ResponseCodes
Public Class SIP_ResponseCodes
public ref class SIP_ResponseCodes
type SIP_ResponseCodes = class end
Members| All Members | Constructors | Methods | Fields | ||
| Icon | Member | Description |
|---|---|---|
 | SIP_ResponseCodes()()()() | Initializes a new instance of the SIP_ResponseCodes class |
| Equals(Object) | (Inherited from Object.) |
 | Finalize()()()() | Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.) |
| GetHashCode()()()() | Serves as a hash function for a particular type. (Inherited from Object.) |
| GetType()()()() | Gets the Type of the current instance. (Inherited from Object.) |
| MemberwiseClone()()()() | Creates a shallow copy of the current Object. (Inherited from Object.) |
| ToString()()()() | Returns a string that represents the current object. (Inherited from Object.) |
  | x100_Trying |
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).
|
| x180_Ringing |
The UA receiving the INVITE is trying to alert the user.
|
| x181_Call_Forwarded |
A server MAY use this status code to indicate that the call is being
forwarded to a different set of destinations.
|
| x182_Queued |
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.
|
| x183_Session_Progress |
The 183 (Session Progress) response is used to convey information
about the progress of the call that is not otherwise classified.
|
| x200_Ok |
The request has succeeded.
|
| x202_Ok |
The request has accepted. Defined in rfc 3265.
|
| x301_Ok |
The user can no longer be found at the address in the Request-URI,
and the requesting client SHOULD retry at the new address given by
the Contact header field (Section 20.10). Defined in rfc 3265.
|
| x302_Ok |
The requesting client SHOULD retry the request at the new address(es)
given by the Contact header field (Section 20.10). Defined in rfc 3265.
|
| x400_Bad_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".
|
| x401_Unauthorized |
The request requires user authentication.
|
| x403_Forbidden |
The server understood the request, but is refusing to fulfill it.
Authorization will not help, and the request SHOULD NOT be repeated.
|
| x404_Not_Found |
The server has definitive information that the user does not exist at
the domain specified in the Request-URI.
|
| x405_Method_Not_Allowed |
The method specified in the Request-Line is understood, but not
allowed for the address identified by the Request-URI.
|
| x406_Not_Acceptable |
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.
|
| x407_Proxy_Authentication_Required |
This code is similar to 401 (Unauthorized), but indicates that the
client MUST first authenticate itself with the proxy.
|
| x408_Request_Timeout |
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.
|
| x410_Gone |
The requested resource is no longer available at the server and no
forwarding address is known. This condition is expected to be
considered permanent.
|
| x412_Conditional_Request_Failed |
Is used to indicate that the precondition given for the request has failed. Defined in rfc 3903.
|
| x413_Request_Entity_Too_Large |
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.
|
| x414_RequestURI_Too_Long |
The server is refusing to service the request because the Request-URI
is longer than the server is willing to interpret.
|
| x415_Unsupported_Media_Type |
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.
|
| x416_Unsupported_URI_Scheme |
The server cannot process the request because the scheme of the URI
in the Request-URI is unknown to the server.
|
| x417_Unknown_Resource_Priority |
TODO: add description. Defined in rfc 4412.
|
| x420_Bad_Extension |
The server did not understand the protocol extension specified in a
Proxy-Require or Require header field.
|
| x421_Extension_Required |
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.
|
| x422_Session_Interval_Too_Small |
It is generated by a UAS or proxy when a request contains a Session-Expires header field
with a duration below the minimum timer for the server. The 422 response MUST contain a Min-SE
header field with the minimum timer for that server.
|
| x423_Interval_Too_Brief |
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.
|
| x428_Use_Identity_Header |
It is used when the verifier receives a message with an Identity signature that does not
correspond to the digest-string calculated by the verifier. Defined in rfc 4474.
|
| x429_Provide_Referrer_Identity |
TODO: add description. Defined in rfc 3892.
|
| x436_Bad_Identity_Info |
It is used when the Identity-Info header contains a URI that cannot be dereferenced by the
verifier (either the URI scheme is unsupported by the verifier, or the resource designated by
the URI is otherwise unavailable). Defined in rfc 4474.
|
| x437_Unsupported_Certificate |
It is used when the verifier cannot validate the certificate referenced by the URI of the
Identity-Info header, because, for example, the certificate is self-signed, or signed by a
root certificate authority for whom the verifier does not possess a root certificate.
Defined in rfc 4474.
|
| x438_Invalid_Identity_Header |
It is used when the verifier receives a message with an Identity signature that does not
correspond to the digest-string calculated by the verifier. Defined in rfc 4474.
|
| x480_Temporarily_Unavailable |
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).
|
| x481_Call_Transaction_Does_Not_Exist |
This status indicates that the UAS received a request that does not
match any existing dialog or transaction.
|
| x482_Loop_Detected |
The server has detected a loop.
|
| x483_Too_Many_Hops |
The server received a request that contains a Max-Forwards.
|
| x484_Address_Incomplete |
The server received a request with a Request-URI that was incomplete.
Additional information SHOULD be provided in the reason phrase.
|
| x485_Ambiguous |
The Request-URI was ambiguous.
|
| x486_Busy_Here |
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.
|
| x487_Request_Terminated |
The request was terminated by a BYE or CANCEL request. This response
is never returned for a CANCEL request itself.
|
| x488_Not_Acceptable_Here |
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.
|
| x489_Bad_Event |
Is used to indicate that the server did not understand the event package specified
in a "Event" header field. Defined in rfc 3265.
|
| x491_Request_Pending |
The request was received by a UAS that had a pending request within
the same dialog.
|
| x493_Undecipherable |
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.
|
| x494_Security_Agreement_Required |
TODO: add description. Defined in rfc 3329.
|
| x500_Server_Internal_Error |
The server encountered an unexpected condition that prevented it from
fulfilling the request.
|
| x501_Not_Implemented |
The server does not support the functionality required to fulfill the request.
|
| x502_Bad_Gateway |
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.
|
| x503_Service_Unavailable |
The server is temporarily unable to process the request due to a
temporary overloading or maintenance of the server.
|
| x504_Timeout |
The server did not receive a timely response from an external server
it accessed in attempting to process the request.
|
| x504_Version_Not_Supported |
The server does not support, or refuses to support, the SIP protocol
version that was used in the request.
|
| x513_Message_Too_Large |
The server was unable to process the request since the message length
exceeded its capabilities.
|
| x580_Precondition_Failure |
When a UAS, acting as an answerer, cannot or is not willing to meet the preconditions
in the offer. Defined in rfc 3312.
|
| x600_Busy_Everywhere |
The callee's end system was contacted successfully but the callee is
busy and does not wish to take the call at this time.
|
| x603_Decline |
The callee's machine was successfully contacted but the user
explicitly does not wish to or cannot participate.
|
| x604_Does_Not_Exist_Anywhere |
The server has authoritative information that the user indicated in
the Request-URI does not exist anywhere
|
| x606_Not_Acceptable |
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.
|
Inheritance Hierarchy| Object | |
 | SIP_ResponseCodes |
Assembly: LumiSoft.Net (Module: LumiSoft.Net.dll) Version: 4.5.5510.19119