Cisco 7960G Administrator's Manual page 92

SIP Responses
4xx Response
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication
Required
408 Request Timeout
409 Conflict
410 Gone
411 Length Required
413 Request Entity Too
Large
414 Request—URL Too
Long
415 Unsupported Media
Cisco SIP IP Phone Administrator Guide, Release 6.x and 7.x
A-4
Supported? Comments
Yes The phone does not generate the 402 Payment
Required response.
Yes If the phone receives a 403 Forbidden response, it
notifies the user of the response. This response
indicates that the SIP server has the request but will not
provide service.
Yes The phone generates this response if it is unable to
locate the callee. Upon receiving this response, the
phone notifies the user.
Yes If the phone receives a 405 Method Not Allowed
response, it notifies the user of the response.
Yes The phone does not generate a 406 Not Acceptable
response. For an incoming response, the gateway
initiates a graceful call disconnect (during which the
caller hears a busy or fast busy tone) before clearing
the call request.
Yes If a 407 Proxy Authorization Required response is
received, the phone accepts the response and sends a
new request that contains the user's authentication
information in the format of the HTTP digest as
modified by RFC 3261.
Yes For an incoming response, the phone initiates a
graceful call disconnect (during which a caller hears a
fast busy). The phone generates this response after an
INVITE Expires timeout to avoid leaving the phone in
a continuous ringing state (fail safe mechanism). This
will occur only if the phone does not receive any
messages from the network to tear down the call after
the timer expires.
Yes The 409 Conflict response indicates that the INVITE
request could not be processed because of a conflict
with the current state of the resource. If this response
is received, the user is notified.
Yes The 410 Gone response indicates that a resource is no
longer available at the server and no forwarding
address is known.
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.
Appendix A Compliance with RFC 3261