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

["Micky Kaufmann" <micky@xxxxxxxxxxx>]

DUM is a TransactionUser which means it has ‘setMessageFilterRuleList’ in it.

Wasn’t the stack designed to forward messages to more than one TransactionUser?

If it was designed that way is there still a reason for not overriding ‘setMessageFilterRuleList’ to a few dum threads and still work with one stack?

If both answer are optimistic why not have a HashTable of DumThreads and update MessageFilterRule to filter messages according to transactionId/DialogId hash value?

 

 

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Godin
Sent: Wednesday, November 09, 2005 4:34 PM
To: Meir Elberg; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] dum - sip stack many-to-one relation question

 

You cannot attach many DUM objects to the same stack – it was not designed this way.

 

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Meir Elberg
Sent: Wednesday, November 09, 2005 4: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