El Thursday 15 May 2008 14:42:09 Brett Tate escribió: > > Also in-dialog OPTIONS is used to verify the state of an > > existing dialog since the UAS is supposed to answer "200 OK" > > in case a dialog with that "To" tag exists. > > OPTIONS within a dialog is not a typical request within dialog. It cannot > be used to check dialog state. RFC 5057 section 5.3 discusses the topic > and quotes RFC 3261.
Are you sure? (to see correclty the following table use a fixed width font) 5.1. A Survey of the Effect of Failure Responses on Usages and Dialogs Table 1 and Table 2 display how the various codes affect transaction, usage, or dialog state. Response code specific comments or exceptions follow the table. +----------------------+----------------+-----------------+ | Transaction Only | Destroys Usage | Destroys Dialog | +----------------------+----------------+-----------------+ | 400 (or unknown 4xx) | 405, 480 | 404, 410, 416 | | 401, 402, 403, 406 | 481, 489 | 482, 483 | | 407, 408, 412-415 | 501 | 484, 485 | | 417, 420, 421, 422 | | 502, 604 | | 423, 428, 429 | | | | 436-438, 486, 487 | | | | 488, 491, 493, 494 | | | | 500 (or unknown 5xx) | | | | 503, 504, 505 | | | | 513, 580 | | | | 600 (or unknown 6xx) | | | | 603, 606 | | | +----------------------+----------------+-----------------+ (2) 404 Not Found: 410 Gone: 416 Unsupported URI Scheme: 484 Address Incomplete: 485 Ambiguous: 604 Does Not Exist Anywhere: The Request-URI that is being rejected is the remote target set by the Contact provided by the peer. Getting this response means that something has gone fundamentally wrong with the dialog state. (8) 481 Call/Transaction Does Not Exist: This response indicates that the peer has lost its copy of the dialog usage state. The dialog itself should not be destroyed unless this was the last usage. The above doesn't explain if a UAS should reply a 404 or 481 or 200 if it receives an in-dialog OPTIONS for a non existing dialog, so I'm not sure at all about it... Regards. -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors