Appendix A
Compliance with RFC 3261
1xx Response
181 Call Is Being Forwarded See comments
182 Queued
183 Session Progress
2xx Response—Successful Responses
2xx Response
200 OK
202 Accepted
3xx Response—Redirection Responses
3xx Response
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
305 Use Proxy
380 Alternate Service
4xx Response—Request Failure Responses
4xx Response
400 Bad Request
401 Unauthorized
Supported?
Comments
The phone does not generate these responses; however,
the phone does receive them. The phone processes
these responses in the same way that it processes the
100 Trying response.
The phone does not generate this message. Upon
receiving this response, the phone provides early
media cut-through and then waits for a 200 OK
response.
Supported?
Comments
Yes
—
Yes
—
Supported?
Comments
Yes
—
Yes
Yes
The phone generates this response when local call
forwarding is enabled. Upon receiving this response,
the phone sends an INVITE that contains the contact
information received in the 302 Moved Temporarily
response.
Yes
The phone does not generate these responses. The
gateway contacts the new address in the Contact
Yes
header field.
Supported?
Comments
Yes
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 fast busy tone).
Yes
If a 401 Unauthorized 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.
Cisco SIP IP Phone Administrator Guide, Release 6.x and 7.x
SIP Responses
A-3