Patches item #1642890, was opened at 2007-01-23 12:41 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=1642890&group_id=139143
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: ver devel Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kobi Eshun (ekobi) Assigned to: Nobody/Anonymous (nobody) Summary: 'bye2bye' UA module prototype Initial Comment: Hi, Attached are two patches implementing a prototype 'bye2bye' UA module that cheaply fakes end-to-end BYE requests -- it's a watchdog that enforces metered call duration. One of the patches augments the existing dialog module so that it caches to/from contact and CSeq values; the other implements the new module. I'm soliciting feedback, in particular: Q1 - is there enough general interest in this functionality to warrant further development? Q2 - is there some additional functionality that makes sense? Q3 - would it be better implemented as an integrated extention to the existing dialog module? Use of the module is very straightforward: - Define the module flag parameter that will enable the watchdog on a per-dialog basis. This is used in conjunction with the dialog module flag defined by 'dlg_flag.' - Optionally define the module parameters 'bye2bye_headers,' 'bye2bye_to_next_hop,' and 'bye2bye_from_next_hop.' - set the value of the dialog 'timeout_avp' as required for each dialog that will be monitored. -- kobi ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-24 02:21 Message: Logged In: NO Hello Kobi, I am myself in the process of writing some code to implement this functionnality myself, so I am very enthusiastic about you submission. If you want to talk about it (help, debugging, ideas, discussion), I can be reached at [EMAIL PROTECTED] My own code is not a module but an external piece of code called by exec(), so I'll probably dump it in favor to your approach which is of course cleaner. As of your questions, here are my answers : Q1 - is there enough general interest in this functionality to warrant further development? Well, given the number of threads I've seen on SER/OPENSER MLs, I would say everybody's looking for a way to cut calls. Currently, I've only seen external perl scripts using FIFO UA features to acheive this (and I'm doing the same thing). Q2 - is there some additional functionality that makes sense? In order to enlarge the module's userbase, an ideal addition would be being able to trigger the end2end BYE messages from an external source in addtion to timed calls. Q3 - would it be better implemented as an integrated extention to the existing dialog module? I would keep both modules separate for now, as I suspect many more functionnalities will arise that use dialog statefullness, and a global policy that makes sense would rather be keeping things clean, small and maintainable. But that's just IMHO. Cheers, Jerome Martin ---------------------------------------------------------------------- Comment By: Kobi Eshun (ekobi) Date: 2007-01-23 12:42 Message: Logged In: YES user_id=1039134 Originator: YES File Added: dialog.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=1642890&group_id=139143 _______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
