Cisco 7960G Administration Manual page 95

Appendix A Compliance with RFC 3261
4xx Response
411 Length Required
413 Request Entity Too
Large
414 Request—URL Too
Long
415 Unsupported Media
420 Bad Extension
480 Temporarily
Unavailable
481 Call Leg/Transaction
Does Not Exist
482 Loop Detected
483 Too Many Hops
484 Address Incomplete
485 Ambiguous
486 Busy Here
487 Request Canceled
488 Not Acceptable
491 Request Pending
OL-7890-01
Supported? Comments
Yes This response indicates that the user refuses to accept
the request without a defined content length. If
received, the phone resends the INVITE request if it
can add a valid Content-Length header field.
Yes If a retry-after header field is contained in this
response, the user can attempt the call once again in the
retry time provided.
Yes The user is notified if this response is received.
Yes The user is notified if this response is received.
Yes The user is notified if this response is received.
If the phone does not understand the protocol
extension specified in the Require field, the 420 Bad
Extension response is generated.
Yes The response is received only by the phone. The user
is notified if this response is received.
Yes The user is notified if this response is received.
Yes If a new contact is received, the phone might reinitiate
the call.
Yes The phone generates this response if the called party is
off-hook and the call cannot be presented as a
call-waiting call. Upon receiving this response, the
phone notifies the user and generates a busy tone.
Yes This response indicates that the initial request is
terminated with a BYE or CANCEL request.
Yes When media cannot be negotiated properly, the phone
receives and generates this response.
Yes Indicates a glare condition (when INVITE requests
cross). The phone supports sending and receiving this
response.
Cisco Unified IP Phone 7960G and 7940G Administration Guide for Release 8.0 (SIP)
SIP Responses
A-5