https://jira.astppbilling.org This file is an XML representation of an issue en-us 8.13.3 813003 14-01-2021 https://jira.astppbilling.org/browse/ASTPPCOM-545 ASTPP Community <p>So I found out last night with a fresh install of ASTPP 4.0.1 that freeswitch will randomly bind to ipv6 over ipv4 which stops everything from working. If you keep restarting it will randomly select ipv4 on next reboot or a couple in.<br/> I know this is how ASTPP is configured with freeswitch as we have 5 other freeswitch pbx / billing brands on the exact same VM which don't have this issue.</p> <p>Nothing was changed outside of the default ASTPP setup.</p> ASTPPCOM-545

Fresh Install ASTPP will randomly bind ipv6 over ipv4 on restart

Task Done Done Unassigned redbehrend Mon, 19 Aug 2019 20:19:01 +0530 Sun, 24 May 2020 04:33:30 +0530 Fri, 27 Sep 2019 20:49:51 +0530 0 1 <p>Hi <span class="error">&#91;~Redbehrend&#93;</span> </p> <p>That is strange. Please provide the following information: </p> <p>1. You sip profile settings<br/> 2. ifconfig output<br/> 3. freeswitch's sofia status output. </p> <p>Sorry didn't see the alert on my github here it's all defaults except for the gateway<br/> What happens is ASTPP says everything is running fine but only responds to IPV6 after restarting it a couple times IPV4 randomly gets selected.</p> <p>SIP Profiles are default by ASTPP<br/> The crucial part of it is SIP IP = $${local_ip_v4} and PORT = 5060</p> <p>ifconfig output<br/> ens3: flags=4163&lt;UP,BROADCAST,RUNNING,MULTICAST&gt; mtu 1500<br/> inet XXX.XXX.XXX.XXX netmask 255.255.254.0 broadcast XXX.XXX.XXX.XXXX<br/> inet6 XXXX::XXXX:XXX:XXXX:XXXX prefixlen 64 scopeid 0x20&lt;link&gt;<br/> inet6 XXXX::XXXX:XXX:XXXX:XXXX prefixlen 64 scopeid 0x0&lt;global&gt;<br/> ether XXXX::XXXX:XXX:XXXX:XXXX txqueuelen 1000 (Ethernet)<br/> RX packets 51490762 bytes 11173124362 (10.4 GiB)<br/> RX errors 0 dropped 0 overruns 0 frame 0<br/> TX packets 51755182 bytes 11030503652 (10.2 GiB)<br/> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0</p> <p>lo: flags=73&lt;UP,LOOPBACK,RUNNING&gt; mtu 65536<br/> inet 127.0.0.1 netmask 255.0.0.0<br/> inet6 ::1 prefixlen 128 scopeid 0x10&lt;host&gt;<br/> loop txqueuelen 1 (Local Loopback)<br/> RX packets 6777202 bytes 5778691749 (5.3 GiB)<br/> RX errors 0 dropped 0 overruns 0 frame 0<br/> TX packets 6777202 bytes 5778691749 (5.3 GiB)<br/> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0</p> <p>sofia status output</p> <p> default profile sip:mod_sofia@XXX.XXX.XXX.XXX:5060 RUNNING (0)<br/> default::gw_voip_term gateway sip:FreeSWITCH@XXX.XXX.XXX.XXX NOREG</p> <p>Checking this out more it's deff something with your guys config or maybe your version of freeswitch you are using has a bug.<br/> So with my other ipv4/ipv6 freeswitches the $${local_ip_v4} in the profile works fine.<br/> With ASTPP that profile will use a ipv6 if it's available which causes profiles to not connect internally even though they show connected in ASTPP maybe because it's using it for LAN and WAN? not sure never shared port 5060 like you guys do. If you disable ipv6 even just on wan fs_cli breaks in CLI based on your settings. So using the profile variable $${local_ip_v4} in sofia profiles breaks the config at least on my two test systems when ipv6 is enabled and you reboot because it partly binds to ipv6.</p> <p>With other freeswitch opensource projects and default freeswitch if you disable ipv6 on WAN it's fine and LAN/CLI still works. Not sure if it's sharing the ports or configs in ASTPP but you have a ipv6 auto or :: somewhere that tries to use ipv6.</p> <p>Notes: Maybe you have hard coded in the adapter names or positions instead of searching correctly when binding or during setup? So if a system has more than 1 adapter it doesn't setup right to ipv4? Not sure without looking into it more just shooting in the dark. Seems when a system doesn't name the first adapter eth1 I get errors during setup also but no idea if they are related like when I use virtual systems that name them things like ens1, vns1, etc...</p> <p>Hello,</p> <p>In fs_cli, if you execute</p> <p>eval $${local_ip_v4}</p> <p>You should get ipv4.<br/> If there is anything wrong for picking the IP by FreeSWITCH, you may overwrite the value of local_ip_v4 variable in varx.xml file of FreeSWITCH config.</p> <p>Thanks.</p> Development External issue ID 545 Rank 0|i00bzz: