<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>Hi Anca<br><br>The problem is indeed now fixed, calls are working perfectly <img src="http://mail.yimg.com/a/i/mesg/tsmileys2/04.gif">. Please let me know if you would like me to paste a new trace and debug for interests sake...<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br>Also, I was wondering whether you have any benchmark figures on concurrent B2B calls, any figure at all that I can get a rough idea from.<br><br>Thank you so much for all your great work and help so far, Im sure I speak for the entire community when I say how much I appreciate the work that has been done by all involved in Openser/sips project.<br><br>Regards,<br>Bruce<br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2"
face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Anca Vamanu <anca@opensips.org><br><b><span style="font-weight: bold;">To:</span></b> users@lists.opensips.org<br><b><span style="font-weight: bold;">Sent:</span></b> Wed, 16 June, 2010 12:51:16<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [OpenSIPS-Users] B2B Ack issue<br></font><br><meta http-equiv="x-dns-prefetch-control" content="off">
Hi Bruce,<br>
<br>
Thank you for the report. It was indeed a bug - the transaction from tm
module was deleted before the ACK was received. Now we fixed this.
Please update your code.<br>
<br>
Thanks and regards,<br>
<pre class="moz-signature">-- <br>Anca Vamanu<br><a rel="nofollow" class="moz-txt-link-abbreviated" target="_blank" href="http://www.voice-system.ro">www.voice-system.ro</a></pre>
<br>
On 06/15/2010 11:17 AM, Bruce Borrett wrote:
<blockquote type="cite">
<div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div>Hi All<br>
<br>
Sorry if I have confused the list with all my paste links :)<br>
<br>
Anca, if the ACK from 196.x.x.208 is not being matched to a transaction
correctly, then how does B2B module know to route the ACK to 41.x.x.33,
and it is even using the correct call id and from and to tags?<br>
<br>
Regards,<br>
Bruce<br>
</div>
</div>
</blockquote>
<meta http-equiv="x-dns-prefetch-control" content="on"></div></div>
</div><br>
</body></html>