[Devel] session termination

[JF]

Hi Daniel,

The dialog module I mentioned is in SER, not OpenSER. Unfortunately
the SER/OpenSER split is getting confusing. When it happened, I
thought OpenSER would be a more experimental branch of SER, but this
AFAIK has not been the case, since developments from both projects are
not being merged.

We definitely should discuss further about this dialog statefulness or
dialog management module (I called it 'dlgm').
My targeted usage scenario started by being just session termination
(which can be used simply to control ongoing call durations or in IMS
scenarios), but we are seeing bigger interest in other features which
are enabled by dialog awareness in SER, like the session timer support
you mentioned, and even some kind of B2BUA API.
I think we should start by collecting requirements (both from SER and
OpenSER lists), check which functionalities have been implemented and
what needs to be done and expect core developers' feedback.

JF

P.S.: You probably should also check some serdev mails on this, since
not all the thread is being sent on devel at openser.

On 1/16/06, Daniel Hsueh <dhsueh at somanetworks.com> wrote:
> 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:dhsueh at somanetworks.com
> SOMA Networks                           tel:+1-416-348-1631
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>