
Appendix A SIP Compliance
RFC 2543 and RFC 3261
Table A-3  SIP Responses (continued)
SIP Response
Meaning
Supported?
Cisco SPS Action
4xx   | 
  | 
  | ||
  | 
  | 
  | 
  | 
  | 
400  | Bad Request  | Request can not be understood because  | Yes  | Generates and forwards this  | 
  | 
  | of an illegal format.  | 
  | response.  | 
  | 
  | 
  | 
  | 
  | 
401  | Unauthorized  | Request requires user authentication.  | Yes  | Forwards this response. If it is  | 
  | 
  | 
  | 
  | configured as a registrar and  | 
  | 
  | 
  | 
  | authentication is enabled,  | 
  | 
  | 
  | 
  | generates this response.  | 
  | 
  | 
  | 
  | 
  | 
402  | Payment required  | Payment is required for server to  | See Cisco SPS  | In registrar mode and if proxied  | 
  | 
  | complete the call.  | action  | by the proxy server, generates  | 
  | 
  | 
  | 
  | this response.  | 
403  | Forbidden  | Server has received and understood the  | 
  | |
  | 
  | |||
  | 
  | request but will not provide the service.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
404  | Not found  | Server has definite information that the  | Yes  | Generates and forwards this  | 
  | 
  | user does not exist in the specified  | 
  | response.  | 
  | 
  | domain.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
405  | Method not allowed  | Method specified in the request is not  | See Cisco SPS  | Forwards this response.  | 
  | 
  | allowed. The response contains a list of  | action  | 
  | 
  | 
  | allowed methods.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
406  | Not acceptable  | Requested resource can generate only  | 
  | 
  | 
  | 
  | responses that have unacceptable  | 
  | 
  | 
  | 
  | content as specified in the accept header  | 
  | 
  | 
  | 
  | of the request.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
407  | Proxy authentication  | Similar to the 401 Unauthorized  | Yes  | Forwards this response. If  | 
  | required  | response, but client must first  | 
  | authentication is enabled,  | 
  | 
  | authenticate itself with the proxy.  | 
  | generates this response.  | 
  | 
  | 
  | 
  | 
  | 
408  | Request timeout  | Server could not produce a response  | See Cisco SPS  | Generates and forwards this  | 
  | 
  | before the expiration timeout.  | action  | response.  | 
  | 
  | 
  | 
  | 
  | 
409  | Conflict  | Request cannot be processed because of  | 
  | 
  | 
  | 
  | a conflict with the current state of the  | 
  | 
  | 
  | 
  | resource.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
410  | Gone  | A resource is no longer available at the  | See Cisco SPS  | Forwards this response.  | 
  | 
  | server and no forwarding address is  | action  | 
  | 
  | 
  | known.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
411  | Length required  | User refuses to accept the request  | Yes  | 
  | 
  | 
  | without a defined content length.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
413  | Request entity too large  | Server refuses to process the request  | See Cisco SPS  | 
  | 
  | 
  | because it is larger than the server is  | action  | 
  | 
  | 
  | willing or able to process. If a retry after  | 
  | 
  | 
  | 
  | header field is contained in this  | 
  | 
  | 
  | 
  | response, the user can attempt the call  | 
  | 
  | 
  | 
  | once again in the retry time provided.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
414  | Server refuses to process the request  | Yes  | Generates and forwards this  | |
  | 
  | because the   | 
  | response.  | 
  | 
  | the server to interpret.  | 
  | 
  | 
  | 
  | 
  | 
  | 
  | 
Cisco SIP Proxy Server Administrator Guide