<div dir="ltr">Hi Andrew, <div><br></div><div>this is my reg_agent.conf.customtt.tt2:</div><div><br></div><div><div>domain=218.101.10.135</div><div>user=039413170</div><div>pwd=xxxxxxxx</div><div>proxy=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]</div><div>[% IF sip_adv_ips.size -%]</div><div>contact=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]</div><div>[% ELSE -%]</div><div>contact=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]</div><div>[% END %]</div></div><div><br></div><div>I have not made any changes to specify the interface. </div><div><br></div><div>I have changed
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">sems.db_reg_agent.fetch_extra_</span><wbr style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">sockets_from_peer is set to 'yes'. and run ngcpcfg apply ',change sems option' then rebooted. no change. </span></div><div><br></div><div>The registration message is going out the correct interface, with the wrong source address. </div><div><br></div><div>My interfaces:</div><div><br></div><div><div><br></div><div>eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500</div><div> inet 192.168.x.30 netmask 255.255.255.0 broadcast 192.168.152.255</div><div> inet6 fe80::250:56ff:fe92:11c4 prefixlen 64 scopeid 0x20<link></div><div> ether 00:x:x:92:11:c4 txqueuelen 1000 (Ethernet)</div><div><br></div><div>eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500</div><div> inet 103.37.37.211 netmask 255.255.255.240 broadcast 103.242.37.223</div><div> inet6 fe80::250:56ff:fe92:7da5 prefixlen 64 scopeid 0x20<link></div><div> ether 00:x:x:92:7d:a5 txqueuelen 1000 (Ethernet)</div><div><br></div><div>eth2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500</div><div> inet 203.x.180.42 netmask 255.255.255.252 broadcast 203.167.180.43</div><div> ether 00:xx:56:92:06:c1 txqueuelen 1000 (Ethernet)</div><div><br></div><div>eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500</div><div> inet 203.x.154.94 netmask 255.255.255.252 broadcast 203.167.154.95</div><div> inet6 fe80::250:56ff:fe92:4ff3 prefixlen 64 scopeid 0x20<link></div><div> ether 00:xx:56:92:4f:f3 txqueuelen 1000 (Ethernet)</div><div><br></div><div>lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536</div><div> inet 127.0.0.1 netmask 255.0.0.0</div><div> inet6 ::1 prefixlen 128 scopeid 0x10<host></div><div> loop txqueuelen 1 (Local Loopback)</div><div><br></div><div><br></div><div>My routes:</div><div><br></div><div>Kernel IP routing table</div><div>Destination Gateway Genmask Flags Metric Ref Use Iface</div><div>default 103.242.37.209 0.0.0.0 UG 0 0 0 eth1</div><div>103.242.37.208 0.0.0.0 255.255.255.240 U 0 0 0 eth1</div><div>192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0</div><div>203.167.x.92 0.0.0.0 255.255.255.252 U 0 0 0 eth3</div><div>203.167.x.40 0.0.0.0 255.255.255.252 U 0 0 0 eth2</div><div>218.101.10.135 203-167-154-93. 255.255.255.255 UGH 0 0 0 eth3</div></div><div><br></div><div>The traffic departs the correct interace, eth3 but has a source addresss of eth1.</div><div><br></div><div><div><img src="cid:ii_jhqpef6b0_163a86e7eea02e26" width="611" height="261" style="margin-right: 0px;"><br></div><br></div><div><br></div><div>Any help would be much appricated. </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 29, 2018 at 12:49 AM, Andrew Pogrebennyk <span dir="ltr"><<a href="mailto:apogrebennyk@sipwise.com" target="_blank">apogrebennyk@sipwise.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="gmail-">On 05/16/2018 10:13 AM, Chris Hoffmann wrote:<br>
> Hi,<br>
> <br>
> Version 6.1.<br>
> <br>
> I have also updated my misleading subject line. To clarify, the<br>
> registration comes out the correct interface, but the capture shows it<br>
> coming from the wrong ip address. It shows it coming from my main<br>
> external interface eth1. <br>
> <br>
> Thanks,<br>
> <br>
> Chris <br>
<br>
</span>Hi, check that the contact in your reg_agent.conf.customtt.tt2 is<br>
pointing to the correct interface.<br>
Also you should check that the config.yml key<br>
sems.db_reg_agent.fetch_extra_<wbr>sockets_from_peer is set to 'yes'.<br>
This will make the kamailio-lb forward the registration from the<br>
interface taken from contact header.<br>
<br>
BR,<br>
Andrew<br>
</blockquote></div><br></div>