<div dir="ltr">Feroze, <div><br></div><div>Are any other lines of logging printed just above it?</div><div><br></div><div>Ben</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 8, 2016 at 3:48 PM, feroze waris <span dir="ltr"><<a href="mailto:feroze.chaudhry@gmail.com" target="_blank">feroze.chaudhry@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Ben<br><br>I have put the address of my interface <br><br></div><div>Regards <br></div><span class="HOEnZb"><font color="#888888"><div>Feroze<br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 8, 2016 at 7:39 PM, Benjamin Cropley <span dir="ltr"><<a href="mailto:benjamin.cropley@gmail.com" target="_blank">benjamin.cropley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Feroze<div><br></div><div>Can I just check.. in the listen variable have you put the address of your interface or 1.2.3.4?</div><div><br></div><div>You need to put your address.. not 1.2.3.4....</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 8, 2016 at 3:30 PM, feroze waris <span dir="ltr"><<a href="mailto:feroze.chaudhry@gmail.com" target="_blank">feroze.chaudhry@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi ben<br><br></div>As you said i have enabled the listen=tls:<a href="http://1.2.3.4:5061" target="_blank">1.2.3.4:5061</a> on receiving proxy as well. Now i am getting the following error in this case <br><br> Apr 8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:msg_send: send() for proto 3 failed<br>Apr 8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:t_forward_nonack: sending request failed<br>Apr 8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:w_t_relay: t_forward_nonack failed<br><br><br></div>regards<span><font color="#888888"><br></font></span></div><span><font color="#888888">Feroze<br></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 8, 2016 at 1:15 PM, Benjamin Cropley <span dir="ltr"><<a href="mailto:benjamin.cropley@gmail.com" target="_blank">benjamin.cropley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Feroze,<div><br></div><div>I think you misunderstood :)</div><div><br></div><div>I was saying, the URI has <span style="font-size:12.8px">;transport=tls, but the receiving server probably doesn't have a port open to listen for it.. Don't remove this if you want to use TLS, as by using rewrite() you're effectively breaking TLS ;)</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">In the documentation it says if you dont specify a listen= variable, then it will listen on 'all interfaces'. It doesn't say whether it will listen to UDP TCP and TLS. But I would guess it's possibly only UDP and TCP.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Therefore, make sure on the servers receiving the packets that you specifically set a tls listening interface with </span><span style="font-size:12.8px">listen = tls:</span><a href="http://1.2.3.4:5061/" style="font-size:12.8px" target="_blank">1.2.3.4:5061</a></div><div><br></div><div>Good luck</div><div>Ben</div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 8, 2016 at 7:29 AM, feroze waris <span dir="ltr"><<a href="mailto:feroze.chaudhry@gmail.com" target="_blank">feroze.chaudhry@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi ben<br><br></div>I have checked the traces and you were right that there was transport = tls in RURI when request forwards from load balancer to 2 opensips instances . I have replaced the RURI using rewrite() function and removed the transport parameter but the issue remains and i am getting the same error <br><br><br></div>regards <br></div><span><font color="#888888">Feroze<br></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <span dir="ltr"><<a href="mailto:benjamin.cropley@gmail.com" target="_blank">benjamin.cropley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Wild guess here, based on what I've read..<div><br></div><div>It might be your request URI is explicitly declaring which protocol to use, and OpenSIPS has no interface configured for that protocol.. eg. ;transport=tls is added to the request URI but there's no listen = tls:<a href="http://1.2.3.4:5061" target="_blank">1.2.3.4:5061</a></div><div><br></div><div>I know it's tricky to look at a trace for TLS. But have a look at <a href="http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark" target="_blank">http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark</a></div><div><br></div>Good luck<div>Ben</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 6, 2016 at 6:24 PM, feroze waris <span dir="ltr"><<a href="mailto:feroze.chaudhry@gmail.com" target="_blank">feroze.chaudhry@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi ben<div><br></div><div>yes i am load balancing the Register and Invite request to two proxy servers using dispatcher module but all three servers (i.e load balncer and two opensips servers) are sharing same opensips database. <br>This issue is not occurring in UDP call but on TLS this error occurs. </div><div><br></div><div>Regards </div><span><font color="#888888"><div>Feroze</div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <span dir="ltr"><<a href="mailto:benjamin.cropley@gmail.com" target="_blank">benjamin.cropley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Feroze,<div><br></div><div>Are you load balancing REGISTER <b>and </b>INVITE requests to different nodes? </div><div><br></div><div>If so, then unless you share location information between the Registrars, then they wont all know where to route INVITEs.</div><div><br></div><div>Ben</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Wed, Apr 6, 2016 at 3:20 PM, feroze waris <span dir="ltr"><<a href="mailto:feroze.chaudhry@gmail.com" target="_blank">feroze.chaudhry@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div><div><div>Hello <br><br></div>I have one load balancer connected to 2 opensips server <br></div>Request is balancing through dispatcher module on load balancer <br></div>the problem is when Register request of B party lands on different server than that server at which A Party sends invite request the call drops and i am getting following error<br>Apr 6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst: failed to fwd to af 2, proto 3 (no corresponding listening socket)<br>Apr 6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:t_forward_nonack: failure to add branches<br>Apr 6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay: t_forward_nonack failed <br><br></div>I am using Openisps version 2.1.1 and using TLS on it <br><br><br></div>Regards<span><font color="#888888"><br></font></span></div><span><font color="#888888">Feroze <br></font></span></div>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>