reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] dum - sip stack many-to-one relation question

How didn’t I think about this question? It can solve many efficiency issues…

Were you able to separate callback processing from DUM thread?

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Meir Elberg
Sent: Wednesday, November 09, 2005 11:09 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] dum - sip stack many-to-one relation question

 

Hi,

I'm checking the option to attach many dum objects to one SIP stack. Therefore, my first question is whether it is possible and if so, is it recommended ?
 
The reason for doing so is that I wish to have one listening point, i.e. by adding one transport to a SIP stack and have many dum stacks (working as UAS) using this sip stack, working in different threads in parallel.
 
Another question is when a SIP request is received to the SIP stack, what is the policy of distribution of this SIP request between the different dum objects attached to the SIP stack ?

Thanks,
Elberg Meir
Ventego Networks