Hello all,
I'm currently implementing a module to track dialogs to implement call
statefulness for OpenSER, and specifically, to implement SIP Session
Timers (RFC 4028) proxy behavior for OpenSER.
JF, perhaps we should work together on implementing dialog tracking.
I'm not sure what exact usage scenarios you are targeting; shall we
discuss in email? You mentioned a "dialog" module; I don't see any
module like that when browsing the source at
http://cvs.sourceforge.net/viewcvs.py/openser/sip-server/ -- could you
point me to where I can find this code? (Or are you refering to the
"dlg" code that comes with the tm module?)
Thanks!
On 1/16/06, JF <jfkavaka at gmail.com> wrote:
This still needs reviewing, but the next step I guess should be
discussing how best to store the dialog table. This could potencially
waste a lot of resources if kept in memory as the calls in progress
grow in number. So maybe a database storage mode would be appropriate.
I recently tripped on some code in SER HEAD which partially kinda does
just that. It's the 'dialog' module. Maybe it can be used here.
What do people think about all this?
--
Daniel Hsueh mailto:[EMAIL PROTECTED]
SOMA Networks tel:+1-416-348-1631
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
