<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Hi,</div><div dir="ltr"><br></div><div dir="ltr">Did you try the ngcp-network command?</div><div dir="ltr">I think correct way would be configuring the </div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);"><span class="emphasis"><span style="font-style: italic;">/etc/ngcp-config/network.yml</span></span> file</span></div><div dir="ltr">Look at <a href="https://www.sipwise.org/doc/mr6.5.2/spce/?_href=ar01s04.html#_network_configuration">https://www.sipwise.org/doc/mr6.5.2/spce/?_href=ar01s04.html#_network_configuration</a></div><div dir="ltr"><br></div><div dir="ltr">Tomi</div><div dir="ltr"><br>On 9 Jan 2019, at 21.07, Scott Fertig <<a href="mailto:scottf@zstaff.wcoil.com">scottf@zstaff.wcoil.com</a>> wrote:<br><br></div><div dir="ltr"><span>Hello,</span><br><span>After a new install and following the initial steps in the manual for 6.5.2 it appears all my processes are listening on 127.0.0.1 or on ipv6 instead of the external IPv4 addresses. I was able to get the web interface to listen after modifying the nginx config but was certain this was not the way to actually "fix" the issue. Unfortunately it appears that Kamailio, and rtpengine are still listening on 127.0.0.1 and ipv6. Can anyone let me know the proper way to fix this? I am using a public static IPv4 address. I am not certain how this ended up like this since my interface is named the standard eth0 and is properly working.</span><br><span></span><br><span>Thanks!</span><br><span></span><br><span>--Scott</span><br><span></span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>Spce-user mailing list</span><br><span><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a></span><br><span><a href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a></span><br></div></body></html>