<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Try:<br>
append_branch("sip:dst_ip:port;transport=tcp");<br>
<br>
Also take a look at $branch variable & co:<br>
<a class="moz-txt-link-freetext" href="http://www.opensips.org/Documentation/Script-CoreVar-1-11#toc21">http://www.opensips.org/Documentation/Script-CoreVar-1-11#toc21</a><br>
<br>
Regards,<br>
</tt>
<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>
<div class="moz-cite-prefix">On 17.08.2015 14:36, Tito Cumpen wrote:<br>
</div>
<blockquote
cite="mid:CANZPVB4G+O-yHLzmzWPESfPkhRJAnn507oEB86pq3MyYKpdf8g@mail.gmail.com"
type="cite">
<p dir="ltr">Bogdan,<br>
</p>
<p dir="ltr">I will acquire the capture later today and post. Can
you tell me how I can append the port and protocol when creating
the branch ? Or at least what the string needs to look like ?</p>
<p dir="ltr">Thanks,<br>
Tito </p>
<div class="gmail_quote">On Aug 17, 2015 5:38 AM, "Bogdan-Andrei
Iancu" <<a moz-do-not-send="true"
href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi Tito,<br>
<br>
Yes, your SIP URI does not have any protocol or port
indication, so NAPTR lookup is perform.<br>
<br>
Now, of the call flow you describe : DNS based discovery is
to be done for initial request only - the sequential
requests (in dialog) should simply follow the path
discovered by the initial request. So, better post somewhere
the pcap or so.<br>
<br>
Regards,<br>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>On 15.08.2015 00:41, Tito Cumpen wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I enabled debug level 6 and I am noticing
this
<div> <span>: DBG:core:mk_proxy: doing DNS lookup...<br>
Aug 14 20:42:09 cloud-server-06
/sbin/opensips[22814]: DBG:core:sip_resolvehost: no
port, no proto -> do NAPTR lookup!</span><br>
</div>
<div><span><br>
</span></div>
<div>Here it claims that this request is lacking a port
and and a proto on this branch I am appending the
branch like so </div>
<div><br>
</div>
<div>
<p><span>
avp_pushto("$du","sip:sisterproxyIP");</span></p>
<p><span> </span></p>
<p><span> </span></p>
<p><span>
append_branch();</span></p>
<p><br>
</p>
<p>the sister proxy is where the user resides. This is
actually confusing the remote opensips proxy(same
version) because now it sends all in dialog request
via a tcp socket all thought the 200 was sent via
udp leg. 2 requests came into the sister proxy. I'm
not sure why the one gets a 404 and the proceeds the
only difference is the udp request has two rr
headers. It appears that the remote proxy might not
have cancelled the dialog even thought it sent a
negative reply. I have a trace of this if needs to
be supplied.</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Tito</p>
<p><br>
</p>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Aug 14, 2015 at 3:52
PM, Tito Cumpen <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:tito@xsvoce.com" target="_blank">tito@xsvoce.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">Group,
<div><br>
</div>
<div><br>
</div>
<div>I am using :</div>
<div>
<p><span>version: opensips 2.2-dev
(x86_64/linux)</span></p>
<p><span>flags: STATS: On, DISABLE_NAGLE,
USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT</span></p>
<p><span>ADAPTIVE_WAIT_LOOPS=1024,
MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535</span></p>
<p><span>poll method support: poll, epoll_lt,
epoll_et, sigio_rt, select.</span></p>
<p><span>git revision: b7db080</span></p>
<p><span>main.c compiled on 22:43:41 Jun 25 2015
with gcc 4.8.3</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span>I have a strange issue in which dns SRV
lookups and routing is happening although I
have set the RURI domain as an alias in my
config. On some calls this will eventually
screw up the dialog termination once a bye
is sent because it makes an attempt to
transmit the bye to this SRV entry.</span></p>
<p><span>I see this error in the logs.</span></p>
<div style="font-family:'Helvetica
Neue';font-size:14px"><span
style="background-color:rgb(0,0,0)"><span
style="font-size:12px"><span
style="font-family:'Andale Mono'"><span
style="color:rgb(202,251,66)">Aug 14
18:36:25 cloud-server-06
/sbin/opensips[15805]: <a
moz-do-not-send="true">INFO:core:init_sock_keepalive</a>:
TCP keepalive enabled on socket 47<br>
Aug 14 18:36:25 cloud-server-06
/sbin/opensips[15805]:
ERROR:core:tcpconn_async_connect: poll
error: flags 1c<br>
Aug 14 18:36:25 cloud-server-06
/sbin/opensips[15805]:
ERROR:core:tcpconn_async_connect:
failed to retrieve SO_ERROR
[server=192.XX.XX.XX:38798] (111)
Connection refused<br>
Aug 14 18:36:25 cloud-server-06
/sbin/opensips[15805]:
ERROR:core:proto_tcp_send: async TCP
connect failed<br>
Aug 14 18:36:25 cloud-server-06
/sbin/opensips[15805]:
ERROR:tm:msg_send: send() for proto 2
failed</span></span></span></span></div>
<p><span><span>Aug 14 18:36:25 cloud-server-06
/sbin/opensips[15805]:
ERROR:tm:t_forward_nonack: sending request
failed</span> </span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>