<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Kaan,<br>
<br>
I'm glad the first part is properly working now.<br>
<br>
Your ACK (as it is for a 200 OK) should be routed based on Route
headers (record route and loose route mechanism). TO better
understand this, please take a look to this webinar:<br>
<a class="moz-txt-link-freetext" href="http://www.opensips.org/Documentation/Webinars#toc12">http://www.opensips.org/Documentation/Webinars#toc12</a> (
chapter 5.5 )<br>
<br>
At INVITE time you should do record_route() and the ACK should
carry the Route headers in order to follow the same path as the
INVITE.<br>
<br>
Regards,<br>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
On 15.10.2014 07:27, Kaan Dandin wrote:<br>
</div>
<blockquote
cite="mid:1413347240.77902.YahooMailNeo@web121502.mail.ne1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial,
Lucida Grande, sans-serif;font-size:16px">
<div><span>Hi Bogdan,</span></div>
<div style="color: rgb(0, 0, 0); font-family: HelveticaNeue,
Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;
font-size: 16px; font-style: normal; background-color:
transparent;"><span></span> </div>
<div style="color: rgb(0, 0, 0); font-family: HelveticaNeue,
Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;
font-size: 16px; font-style: normal; background-color:
transparent;"><span>Thanks a lot for your response. My aim is
to register to both IMS nodes(.3 and .5) in the same time
,then able to make load balancing to any of them.</span></div>
<div> </div>
<div>With your support ,now I better understand how t_relay and
paralel forking is working.</div>
<div> </div>
<div>I have managed the problem by sending to different IMS
registration scenario (.3 and .5) from IMS bench (.11) instead
of parallel forking in OpenSIPS.</div>
<div> </div>
<div>Now the registrations are successuly completed.</div>
<div> </div>
<div>But I have another problem in the IMS call scenario.</div>
<div> </div>
<div>ACK messages are always going to .5 IMS node in t_relay
instead of the related node. In the logs it seems that related
transaction not found and address is found with DNS lookup and
always sent to .5 node.</div>
<div> </div>
<div>For that reason only half of the calls are successful.</div>
<div> </div>
<div>Below I am sharing related part of the script , call flow
and trace.</div>
<div> </div>
<div>Kind regards,</div>
<div>Kaan</div>
<div> </div>
<div>} else {<br>
if ( is_method("ACK") ) {<br>
xlog("xlog_ack_method");<br>
if ( t_check_trans() ) {<br>
<br>
# non loose-route, but
stateful ACK; must be an ACK after <br>
# a 487 or e.g. 404
from upstream server<br>
xlog("xlog_nonlooseroutestatefulack");<br>
t_relay();<br>
exit;<br>
} else {<br>
# ACK without matching
transaction -><br>
# ignore and discard<br>
t_relay();<br>
xlog("xlog_nonlooseroutenonstatefulack");<br>
exit;<br>
}<br>
}<br>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>