[reSIProcate] symmetric signalling

[WAGNER, Jerome (Consultant)]

Hello,

 

I'm looking at the NAT issue.

Do you think it is simple to use the resip socket transport handling to
force "symmetric signalling" ?

(signalling going in and out on the same port)

 

is there an example in the resip examples or in the DUM examples ?

 

thanks

Jérôme

 

-----Message d'origine-----
De : resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] De la part de Scott
Godin
Envoyé : jeudi 5 août 2004 16:31
À : 'Jason Fischl'
Cc : resiprocate-devel at list.sipfoundry.org
Objet : [reSIProcate] Use of StackThread?

 

Hi Jason,

 

I'm curious how would make use of this threaded process call?  

 

My guess is that this is only useful if you can place all of your dum->send
calls within the session callbacks themselves - since calling dum->send
outside of the process thread is not thread safe.

 

Thanks,

 

Scott

 

  _____  

From: svn at sipfoundry.org [mailto:svn at sipfoundry.org] 
Sent: Sunday, August 01, 2004 8:27 PM
To: resiprocate-commit at list.sipfoundry.org
Subject: [reSIProcate-commit] COMMIT: resiprocate 3199 jason

 


Project

resiprocate


New Revision

3199


Committer

jason (Jason Fischl)


Date

2004-08-01 17:27:07 -0700 (Sun, 01 Aug 2004)


Log

 
 
 allow dum to run a separate thread for SipStack using StackThread. provided
a different process call
 
 
 
 
 
 

Modified:


*         main/sip/resiprocate/dum/DialogUsageManager.cxx
<http://scm.sipfoundry.org/viewsvn/resiprocate/main/sip/resiprocate/dum/Dial
ogUsageManager.cxx?r1=3198&r2=3199&diff_format=l>  

*         main/sip/resiprocate/dum/DialogUsageManager.hxx
<http://scm.sipfoundry.org/viewsvn/resiprocate/main/sip/resiprocate/dum/Dial
ogUsageManager.hxx?r1=3198&r2=3199&diff_format=l>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20040805/7b3d055c/attachment.htm>