PS,  I think your idea of auto attempting restarts on fail is a good
one, something like:

<param name="auto-restart"
value="<n-Attempts|Indefinitely>,<n-Seconds-Delay>”/>

See commit 956da6d

This is the kind of discussion better suited for Jira we should find a way
to migrate mailing list threads into Jira automatically and preserve the
conversation.

On Mon, Jun 2, 2014 at 12:06 PM, Anthony Minessale <
anthony.minessale@gmail.com> wrote:

auto-restart is also a per-profile setting the one noted just sets it on
all of them.
It will restart profiles who have the ip that changed present in the
rtp-ip or sip-ip.

I did just see an errant restart_all_profiles call in the code in
questions which will be corrected.

We can see if we can improve its resilience.


On Thu, May 29, 2014 at 3:32 PM, Mario G <mario_fs@mgtech.com> wrote:

I have nailed this down and this looks like it should affect other
people… I discovered why the IPV6 address changes.. It has to do with
privacy addressing (http://tools.ietf.org/html/rfc3041) which is (a good
thing) defaulted since OS X 10.7, and on windows, and other devices. When
enabled, the system will generate a temporary IPV6 address with a random
suffix in addition to the EUI-64-based address. This is so the device mac
address does not get published on the public interface.

I think FreeSWITCH will need something to handle this eventually and not
restart all profiles. If the IPV6 changes why restart IPV4 only profiles?
Also, we need a better way to handle the port busy condition when the
internal profile is restarted.
Mario G

On May 29, 2014, at 12:44 PM, Mario G <mario_fs@mgtech.com> wrote:

That would solve both my problems (I think), may have to bribe Anthony…
Mario G

I like your idea:
<param name="auto-restart"

value="<n-Attempts|Indefinitely>,<n-Seconds-Delay>”/>

On May 28, 2014, at 1:29 PM, Francis <sms@icefire.qza.net.au> wrote:

I had the same issue on a HP T5745, where the IPV6 interface would come
up late after boot and cause the profiles to restart, but the internal
would fail to load:

https://jira.freeswitch.org/browse/FS-6537

Testing from git Master last week, there is a new timer that prevents
the profile from being restarted if it has been up for less than 10
seconds. I've only tried this with manually restarting though, I still
have to test it in a scenario where the IPV6 address randomly changes.
Anthony pointed out that there is a setting in sofia.conf.xml:

  <param name="auto-restart" value="false"/>

... which prevents the profiles from auto-reloading if the IP address
changes. This is ok for me, but if you want to continue using IPV6,

then

it won't help you.
Have you tried the latest master?

PS,  I think your idea of auto attempting restarts on fail is a good
one, something like:

<param name="auto-restart"
value="<n-Attempts|Indefinitely>,<n-Seconds-Delay>"/>

would be the sweet spot.


-Francis


On 2014-05-29 04:07, Mario G wrote:

I have a mix of native IPV4/6. A mac runs FreeSWITCH using a static
IP4 address and has IPV6 addresses. For some reason (I am not an IPV6
expert) the IPV6 address changes once or twice a day. Everything on
the mac runs fine except FreeSWITCH stops all the profiles then
restarts them, it then loses the internal profile. The sequence is
below, If anyone knows of a FS param or something I can use to
workaround this please let me know. BTW, I am not using IPV6 to the
external ITSPs, but the Yealink phones have it on, I could turn it off
but was hoping for a real solution. Thanks,
Mario G

1 - Log shows: [INFO] mod_sofia.c:5286 IP change detected []->[]
[2601:9…..

2 - FreeSWITCH stops all 7 external profiles and the internal profile.

3 - All profiles are restarted, but only the external ones start
successfully. The internal does not start because the port has not
been freed by OS X yet. And FreeSWITCH never attempts to restart it
again. I am sure this is related to Jira
http://jira.freeswitch.org:8080/browse/FS-5223 but is a bigger

problem

since I have to turn off IPV6 to stop it.

4 - I have to "sofia profile internal start” to get it going again.

PS: Would love to find a way to get FS to keep trying to restart
internal rather than give up, would help both problems.