<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Sergio,<br>
one option (besides modifying ROUTE_MASK_CONTACT in
lb/kamailio.cfg.customtt.tt2) would be to leave kamailio.lb.port
set to 5060, but add another extra_socket in config.yml with port
60666 and if this is a separate network interface or VLAN you are
using to receive client traffic, add also type sip_ext_incoming on
that interface in network.yml.<br>
<br>
The reason is that it is insignificant what is selected in
outbound_socket preference on the user or domain level, because
NGCP simply reuses the interface it has received registration on,
but it is using the outbound_socket preference of the peer both to
send packet there and mask Contact header.<br>
<br>
Edit: actually it is strange that you are getting port 60666, are
you using advertised address by any chance? As in this case it's a
bit inconsistent using the kamailio.lb.port instead of the one
from extra_socket:<br>
ROUTE[ROUTE_MASK_CONTACT]<br>
...<br>
[% IF sip_adv_ips.size -%] <br>
xlog("L_INFO", "Mask local contact using
advertised address - [% logres -%]\n");<br>
[% IF kamailio.lb.strict_routing_safe == "yes" %]<br>
$var(tmpcontact) = "<<a class="moz-txt-link-freetext" href="sip:ngcp-lb@">sip:ngcp-lb@</a>[%
sip_adv_ips.0 %]:[% kamailio.lb.port %];ngcpct=" + $var(b64ct) +
">";<br>
[% ELSE %]<br>
$var(tmpcontact) = "<<a class="moz-txt-link-freetext" href="sip:ngcp-lb@">sip:ngcp-lb@</a>[%
sip_adv_ips.0 %]:[% sems.bindport %];ngcpct=" + $var(b64ct) +
">";<br>
[% END %]<br>
[% ELSE -%]<br>
<br>
BR,<br>
Andrew<br>
<br>
On 18/10/16 16:20, Sergio Serrano wrote:<br>
</div>
<blockquote cite="mid:1476800423.4990.8.camel@avanzada7.com"
type="cite">
<div>Hi all,</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>We
have configured SIPWise with non standar SIP Port(60666) for
customers communication and extra_sockets(5060) to communicate
with Peers. We have setup extra_socket in Peerings-> details
-> peering server preferences -> internal -> outbound
sockets. When we connect with Peer, sipwise always put not
standar port in Contact header</div>
<div><br>
</div>
<div>Contact: <sip:<a moz-do-not-send="true" href="ngcp-lb@X">ngcp-lb@X</a>:X:X:X:60666;ngcpct=7369703a3132372e302e302e313a35303830></div>
<div><br>
</div>
<div>This is generate that INVITE transaction works fine, but when
de BYE is initiated by Peer, send REQUEST to contact header and
the REQUEST is not received by SIPWise.</div>
<div><br>
</div>
<div>Are there any way to fix in sipwise that contact header put
the correct port(in this case 5060 instead of 60666) when
SIPwise communicate with Peer that uses special extra_socket?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Sergio</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>