reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [reSIProcate] How to selectTransactionUser?

Resip is not designed to work this way.  There should be one stack instance per DUM instance. 

 

Although if I remember correctly I think someone out there has successfully modified the TU selector so that requests/responses for a particular dialog set end up on the right instance of dum – try a google search through the resip-devel mailing list.

 

Scott

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of shf
Sent: Monday, July 16, 2007 9:48 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] How to selectTransactionUser?

 

Hi,all

  i'm using resip stack and DUM to develop a UA program. I create 2 DialogUsageManager instances and they share a SipStack object. And each Dum instance register,invite is ok. The question is that:

   when UA program is connected to Callee UA, when Callee UA hang up, my UA program received bye command from Callee, and

the Stack object process the bye command, the TransactionState's process() function call

   tu = controller.mTuSelector.selectTransactionUser(*sip);

And TuSelector's selectTransactionUser() call

   if (it->tu->isForMe(msg))

   {

       return it->tu;

   }

here , the TuSelector object always return the 1st DUM object. So the dum will result in a 481 response code. This is Wrong.

How to resolve it ??

 

Thank you.