Nice one, I remember a heated discussion about that, I'm glad that now everyone can consider OpenSER more RFC-compliant and foolproof when needed :-)
Any idea about the cost of using tight-matching though ? Just being curious there ... (I'll probably evaluate this myself, but I'd like to have your POV). On Mon, 2007-04-30 at 13:29 -0700, Bogdan-Andrei Iancu wrote: > Revision: 2108 > http://openser.svn.sourceforge.net/openser/?rev=2108&view=rev > Author: bogdan_iancu > Date: 2007-04-30 13:29:36 -0700 (Mon, 30 Apr 2007) > > Log Message: > ----------- > - dialog matching can be done also via SIP elements (in addition to > dialog ID via RR cokie) - based on a patch from > Michel Bensoussan <[EMAIL PROTECTED]> > Closes patch submision 1692747. > > - new module parameter - dlg_match_mode for controlling how the matching > of sequential requests is done: > 1) only based on DID > 2) based on DID with fallback to SIP elements > 3) no DID, only SIP elements > > - "use_tight_match" (for DID-based matching) includes FROM and TO tag > checking along callid. > > Modified Paths: > -------------- > trunk/modules/dialog/README > trunk/modules/dialog/dialog.c > trunk/modules/dialog/dlg_handlers.c > trunk/modules/dialog/dlg_handlers.h > trunk/modules/dialog/dlg_hash.c > trunk/modules/dialog/dlg_hash.h > trunk/modules/dialog/doc/dialog_user.sgml > > > This was sent by the SourceForge.net collaborative development platform, the > world's largest Open Source development site. > > _______________________________________________ > Devel mailing list > [email protected] > http://openser.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/devel
