On Jul 15, 2008, at 2:48 PM, Adam Roach wrote:
On 7/15/08 2:22 PM, Dean Willis wrote:
Let's say that you send a 4XX error response to an in-dialog INFO
(because you don't understand the Info-type of the dialog). What
does that do to the dialog?
Depends on the 4XX.
404, 410, 416, 482, 483, and 485 destroy the dialog. 405, 480, 481,
489 destroy the INVITE usage, which will usually destroy the dialog.
Pretty much any other 4XX only impact the transaction.
See RFC 5057 for the details.
So let's say you return the new 4xx response to an old-fashioned
sender who doesn't understand the 4xx response. It gets treated as a
400. This doesn't destroy the dialog or the dialog usage, but kills
the INFO transaction.
I have no idea what that does to the sender's state, and I'm pretty
sure the sender doesn't either. Can we live with that? I'd think it
would be better if it destroyed the dialog usage, but AFAIK we have no
way of specifying such behavior in a backward-compatible manner
(unless we reuse 405, 480, 481, or 489). What do we know about real-
world implementations treatment of these responses? Is everything RFC
5057 compliant?
--
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
