User's Manual

4xx Response Send Receive Comments
408 Request timeout No Yes See default handling.
410 Gone No Yes See default handling.
413 Request entity
too large
No Yes
See default handling. The
IP Deskphone does not
automatically retry if a retry-after
header is present.
414 Request---URL
too long
No Yes See default handling.
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.
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 handling.
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
responses, the default handling is
used.
482 Loop detected Yes Yes
Default handling is used when this
response is received.
483 Too Many Hops No Yes See default handling.
484 Address
Incomplete
No Yes See default handling.
485 Ambiguous No Yes
See default handling. The
IP Deskphone does not attempt to
retry the request.
486 Busy Here Yes Yes
The IP Deskphone can respond
with this if the user is on the
IP Deskphone, and the
IP Deskphone has reached its
4xx Response—Request failure responses
SIP Software for Avaya 1100 Series IP Deskphones-Administration November 2012 315