<div dir="ltr">So after running:<div><br></div><div> ngcp-network --set-interface=eth3 --advertised-ip=x.x.x.94</div><div><br></div><div>I then ran ngcpcfg apply 'made a change'</div><div><br></div><div>Checking the captures this does not appear to have changed anything. The registration is still showing the address of eth1 :(</div><div><br></div><div>Have i missed anything? </div><div><br></div><div><br></div><div>Here is my network.yml</div><div><br></div><div><br></div><div><div>hosts:</div><div> self:</div><div> dbnode: '1'</div><div> eth0:</div><div> hwaddr: 00:50:56:92:xx:xx</div><div> ip: 192.168.152.30</div><div> netmask: 255.255.255.0</div><div> type:</div><div> - web_ext</div><div> - ssh_ext</div><div> - web_int</div><div> - rtp_int_eth0</div><div> - sip_ext_incoming</div><div> eth1:</div><div> ip: y.y.y.211</div><div> netmask: 255.255.255.240</div><div> type:</div><div> - sip_ext</div><div> - rtp_ext</div><div> - web_ext</div><div> eth2:</div><div> ip: z.z.z.42</div><div> netmask: 255.255.255.252</div><div> type:</div><div> - rtp_int_eth2</div><div> - sip_ext_incoming</div><div> eth3:</div><div> advertised_ip:</div><div> - x.x.x.94</div><div> ip: x.x.x.94</div><div> netmask: 255.255.255.252</div><div> type:</div><div> - rtp_int_eth3</div><div> - sip_ext_incoming</div><div> interfaces:</div><div> - lo</div><div> - eth0</div><div> - eth1</div><div> - eth2</div><div> - eth3</div></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 15, 2018 at 6:49 PM, Henk <span dir="ltr"><<a href="mailto:henk@voipdigit.nl" target="_blank">henk@voipdigit.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi Chris,</p>
<p>You can set-up an alias address for Kamailio like this:</p>
<p>ngcp-network --set-interface=eth0 --advertised-ip=x.y.z.t</p>
<p>After that just generate the configs again and it should work. <br>
</p>
<p>Best regards,</p>
<p>Henk Plessius</p>
<p>VoipDigit<br>
</p><div><div class="h5">
<br>
<div class="m_6760899672747682929moz-cite-prefix">On 14-5-2018 23:32, Chris Hoffmann
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hi All,
<div><br>
</div>
<div>I have a new VoIP provider on a new pysical interface that
requres me to do SIP registration. I have configured the
details on the peer and set the details in reg_agent.conf.tt2.</div>
<div><br>
</div>
<div>When i do a packet capture, i see the registration being
sent out the correct interface, but from the wrong IP address
(my primary interface IP is used). Is there any way i can set
the socket for the registration? </div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Chris. </div>
</div>
<br>
<fieldset class="m_6760899672747682929mimeAttachmentHeader"></fieldset>
<br>
</div></div><span class=""><pre>______________________________<wbr>_________________
Spce-user mailing list
<a class="m_6760899672747682929moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a>
<a class="m_6760899672747682929moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/<wbr>listinfo/spce-user</a>
</pre>
</span></blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/<wbr>listinfo/spce-user</a><br>
<br></blockquote></div><br></div>