Appendix A SIP Compliance with
SIP Responses
3xx Response—Redirection Responses
3xx Response | Supported | Comments | ||
|
|
| ||
300 Multiple | Yes |
| ||
Choices |
| None | ||
|
|
| ||
301 | Moved | Yes | ||
| ||||
Permanently |
|
| ||
|
|
|
| |
302 | Moved | Yes | The Cisco SIP IP phone does not | |
Temporarily |
| generate this response at this time. Upon | ||
|
|
| receiving this response, the phone sends | |
|
|
| an INVITE containing the contact | |
|
|
| information received in the 302 Moved | |
|
|
| temporarily response. | |
|
|
|
| |
305 | Use Proxy | Yes | The phone does not generate these | |
|
|
| responses. The gateway contacts the new | |
380 | Alternate | Yes | ||
address in the Contact header field. | ||||
Service |
| |||
|
| |||
|
|
|
| |
4xx Response—Request Failure Responses
4xx Response | Supported? | Comments |
|
|
|
400 Bad Request | Yes | The phone generates a 400 Bad Request |
|
| response for a 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. |
|
|
|
|
| Cisco SIP IP Phone 7960 Administrator Guide |
|
|
|
|
| ||
|
|
|
| |
|
|
|
