Geetha,
I could not find the phrase that you have qouted in either of the two
sections you have specified nor elsewhere in 3261. The two sections discuss
rejecting an offer for different reasons.
Section 13.3.1.3 discusses rejection of the offer for either of the
following reasons:
1) the UA is busy (eg. already participating in a call) creating a 486 Busy
Here or 600 Busy Everywhere error response or;
2) the offer is understood but unacceptable (eg. a UA only capable of audio
received an offer for only video)creating a 488 Not Acceptable Here error
response, also in the response for the given example should be a Warning
header with 304 'Media type not available'.
Section 21.4.13 discusses rejection of the offer for a different
reason to those above, that the body of the message can not be processed /
understood. This can for a few reasons - type, disposition and encoding
(eg. say my experimental UAC used 'Content-Type: Wayne' - this is not going
to be understood!) creating a 415 Unsupported Media Type response, in the
response for the example given should be a list of supported content types
in the Accept header.
Hope this helps. Regards - Wayne.
Geetha asked:
******************************************
Hi all,
According to 13.3.1.3 and 21.4.13 of RFC 3261 I need a
clarification of what exactly it means that an " INVITE request including a
session description that it can understand but it can not accept"
Can anyone explain it in detail with simple example?
Thanks,
regards,
geetha
**********************************************************************
Any personal or sensitive information contained in this email and
attachments must be handled in accordance with the Victorian Information
Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988
(Commonwealth), as applicable.
This email, including all attachments, is confidential. If you are not the
intended recipient, you must not disclose, distribute, copy or use the
information contained in this email or attachments. Any confidentiality or
privilege is not waived or lost because this email has been sent to you in
error. If you have received it in error, please let us know by reply
email, delete it from your system and destroy any copies.
**********************************************************************
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
