Re: [reSIProcate-users] Transactions & Dialogs in reSIP

[Andrew Wood <ajwood@xxxxxxx>]

Thanks for the help so far.

Ive been looking through the example programs, am I right in thinking I 
need to create an instance of DialogUsageManager, then register with it 
a handler for each type of SIP message I want to deal with, by subclassing
the classes in /resip/dum


Where are the 'Transaction' objects and 'Dialog' objects or whatever 
you've called them stored because I need to ensure they are written to a 
database rather than just stored in RAM.

Presumably they're in a collection somewhere like a hashmap indexed on 
their ID? Could someone point me in the direction of the right class 
please?

Thanks
Andrew



Max Bowsher wrote:
> Andrew Wood wrote:
>   
> > What is meant by an FdSet and a TU?
> >     
>
> A FdSet is a set of file descriptors. "Set of communication channels
> which need processing by resiprocate this time around the processing
> loop" is an adequate description, but you don't really need to care too
> much if you are driving the stack processing in a conventional way,
> using the example code snippets, or the StackThread class.
>
> A TU is a Transaction User - it's a term defined in the SIP RFC, and
> loosely means "the application logic that builds on the services of a
> SIP stack to actually do something".
>
> Max.
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
>