----- Original Message ----- From: "Krishna Kanth T" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, August 19, 2003 7:51 AM Subject: [Sip-implementors] Doubts in sip-protocol
> Hi, > > I am pretty much confused regarding how to handle some error cases in sip. The error scenarios is as follows :- > > 1. RFC 3265 says that there MUST be only one EVENT header in a SUBSCRIBE message. Suppose if a SUBSCRIBE message somes with more that one EVENT header, then what is the best handling ?? > a:> Should we drop the message ? > b:> Should we have to send an 4xx message back ? If so which is the best status code to use > c:> Should we ignore second EVENT header and process only the first one ? > > 2. RFC 3261 says that there MUST be only one parameter with a given name in any header. Suppose if there is more than one parameter with the same name in a header. then what should the best handling ? > Options are same as the above. >[ABN] yaaa.... rfc says there must be only one parameter with a particular parameter name its upto the implementation to consider valid or not. If u think consider its OK it adds some robustness. > 3. RFC 3261says that a dialog is matched based on from tag, to tag and callid. In this case suppose if a request comes with matching from tag, to tag, callid but with different from and to uri, then what should be done ? > Options are same as the above. > [ABN] probably that check on URI is not required when the tags matches. If the tags matches then it does mean that both caller and callee are 3261 compliant entities. even in this case if URI differs then its a bug from such an entity. Just we are using the tag match for easier dialog match compared one done using URI comparison (which is quite costly). I feel we can consider OK in this case and no need to go for URI comparison once tags matches... > Any responses will be appreciated. > > Rgds > Krishna > ---------------------------------------------------------------------------- ---- > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
