Table of Contents
Advertisement
SIP Responses
4xx Response—Request Failure Responses
4xx Response
400 Bad Request
401 Unauthorized
402 Payment
Required
403 Forbidden
404 Not Found
405 Method Not
Allowed
406 Not
Acceptable
407 Proxy
Authentication
Required
Cisco SIP IP Phone Administrator Guide
A-4
Supported?
Yes
Yes
Yes
Yes
Yes
See comments
See comments
See comments
Appendix A
SIP Compliance with RFC 3261 Information
Comments
The phone generates a 400 Bad Request response
for an erroneous request. For an incoming response,
the phone initiates a graceful call disconnect
(during which the caller hears a busy or fast busy
tone) before clearing the call request.
This response is received only in this release.
If a 401 Unauthorized response is received during
registration, 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.
The phone does not generate the 402 Payment
Required response.
This response is received only in this release.
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.
The Cisco SIP IP phone generates this response if it
is unable to locate the callee. Upon receiving this
response, the phone notifies the user.
This response is received only in this release.
If the phone receives a 405 Method Not Allowed
response, it notifies the user of the response.
The SIP 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.
This response is received only in this release.
The 407 Proxy Authentication Required response
indicates that the phone must first authenticate
itself with the proxy server. If received by the
phone, the phone may repeat the INVITE request
with a suitable Proxy-Authorization field. This
field should contain the authentication information
of the user agent for the next outbound proxy or
gateway.
- Quick Links:
- Using the Command-Line Interface
Hide quick links:
Advertisement
Table of Contents
