Bumping up this thread - curious if anyone had some more input on SetDest?  To 
reiterate- SetDest does work, but SIPp will evenutally Lock up (freeze) and all 
calls will be dropped; it'll eventually un-freeze, but it appears no more calls 
will actually go through.  Clearly there's some issue with SetDest and perhaps 
an optimization/fix could be created?  Or perhaps a way to handle the redirect 
w/out requiring the use of SetDest?




From: John Rodriguez [mailto:[email protected]] 
Sent: 24 June 2009 15:18
To: SIPp Mailing List
Subject: [Sipp-users] Perform redirect without SetDest?


When I send a TCP sip call, I am getting a 302 redirect from the server which 
redirects to the port I should connect to.  I've had no trouble extracting the 
new destination port from the CONTACT header.  However, the only way I've been 
able to get the call to work is if I use the "SetDest" function to point to the 
new redirected port.  Is there anyway to perform a redirect of this nature 
WITHOUT using SetDest?  Simply sending another invite with the new port does 
not work.  
 
The reason I'm asking is b/c I noticed that although the call WILL go through, 
SIPp actually locks up occasionally during load at seemingly random intervals 
and drops all calls.  I'm 100% positive that setdest is causing this b/c if I 
bypass the initial port and redirect to the new port by specifying in the cmd 
line, all works fantastic, no lock ups, etc; I am aware from the doc that the 
setdest may cause locking which may be exactly what I'm experiencing.  The 
problem with this is a) it's not forcing the server to send the redirect and b) 
getting the redirected port is a bit of pain as it tends to change every so 
often.
 
Any ideas?
 
Thanks!

_________________________________________________________________
Windows Liveā„¢: Keep your life in sync. 
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to