Avaya 1230 - Page 231

4xx Response Send Receive Comments
404 Not found Yes Yes
The IP Deskphone generates this
response for requests to unknown users.
Receiving this response falls through to
the default handling.
405 Method not allowed Yes Yes
The IP Deskphone ends this response to
a known method if it is received at a time
when the IP Deskphone is not prepared
to handle or the request is missing
necessary information. Receiving this
response falls through to the default
handling.
406 Not acceptable Yes Yes
The IP Deskphone can send this
response when receiving a REFER
request which has an unsupported URI.
Receiving this response falls through to
the default handling.
407 Proxy authentication
required
No Yes See 401.
408 Request timeout No Yes See default handling.
410 Gone No Yes See Default error handling on page 233.
413 Request entity too
large
No Yes
See Default error handling on page 233.
The IP Deskphone does not
automatically retry if a retry-after header
is present.
414 Request---URL too
long
No Yes See Default error handling on page 233.
415 Unsupported Media Yes Yes
The IP Deskphone can send this
response when an incorrect content-type
is detected for a request. Receiving this
response falls through to the default
handling. See Default error handling on
page 233.
420 Bad Extension Yes Yes
The IP Deskphone can respond with a
420 when checking required extensions
of incoming requests. When receiving a
420, see default handling. The
IP Deskphone does not retry the request.
480 Temporarily
unavailable
No Yes See Default error handling on page 233.
481 Call leg/ transaction
does not exist
Yes Yes
Incoming requests are matched against
existing dialogs. If a request appears to
be in-dialog, but does not have an
existing dialog, the IP Deskphone
responds with a 481. For incoming 481
Table continues…
4xx Response—Request failure responses
March 2015 SIP Software for Avaya 1200 Series IP Deskphones-Administration 231
Comments? infodev@avaya.com