Dean Willis wrote:
Anders Kristensen wrote:
So let's take the ubiquitous DTMF example. Someone defines a DTMF info
event package and they want the recipient of DTMF events to be able to
indicate to the sender that a particular event could not be decoded. If
I understand you correctly, the error indication would have to be
carried in an INFO going in the opposite direction of the DTMF itself.
don't we have a SIP error code for "body not understood"?
Unfortunately we don't quite have that, though we have something close:
488 / 606 apply to the body, and have the names Not Acceptable Here /
Not Acceptable which sound about right. But the description says:
some aspects of the session description such as the requested media,
bandwidth, or addressing style were not acceptable.
which really only applies to SDP (-: or SDPng :-).
415 works when the Content-Type itself is not supported, but not for the
other cases.
I'm inclined to stretch the definition of 488/606 to cover arbitrary
bodies. Or we could define a new code that has the more generic meaning.
I'd really like to NOT design every possible application's state into
SIP. Otherwise, we'll end up with error codes for "no, I want a blue one!"
That is the problem with 488 as it stands.
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
