Cisco Systems RFC 2543 and RFC 3261 appendix SIP Response Meaning Supported? Cisco SPS Action

Appendix A SIP Compliance

RFC 2543 and RFC 3261

Table A-3		SIP Responses (continued)
SIP Response			Meaning	Supported?	Cisco SPS Action
415	Unsupported media		Server refuses to process the request	Yes	Forwards this response.
			because the format of the body is not
			supported by the destination endpoint.
420	Bad extension		Server cannot understand the protocol	Yes	Generates and forwards this
			extension indicated in the Require		response.
			header.
480	Temporarily		Called party was contacted but is	Yes	Forwards this response. If
	unavailable		temporarily unavailable.		preauthentication is enabled and
					fails, generates this response.
481	Call leg/transaction		Server ignores the request because it is	Yes	Generates and forwards this
	does not exist		either a BYE for which there is no		response.
			matching leg ID or a CANCEL for
			which there is no matching transaction.
482	Loop detected		Server received a request that includes
			itself in the path.
483	Too many hops		Server received a request that requires
			more hops than allowed by the
			Max-Forwards header.
484	Address incomplete		Server received a request that contains	See Cisco SPS	Forwards this response.
			an incomplete address.	action
485	Ambiguous		Server received a request that contains
			an ambiguous called-party address. It
			can provide possible alternative
			addresses.
486	Busy here		Called party was contacted but his or
			her system is unable to take additional
			calls.
487	Busy here; request		Request was terminated by a BYE or	Yes
	cancelled		CANCEL request.
488	Not acceptable media		An error in handling the request	See Cisco SPS
			occurred.	action

Cisco SIP Proxy Server Administrator Guide

A-5