Forums

Resolved
0 votes
Hi All

I have a problem on my ClearOS setup. I have 2 internet connections using Wan1 and Wan2 with 1 Lan connection. Both Wan connections are set as primary in wan balancer with the first Wan1 connection getting priority using weights. Voip works fine until Wan1 goes down. Wan1 shows as offline and all traffic goes to Wan 2 except my VOIP phones don't automatically reconnect to the hosted PABX. It will reconnect on Wan 2 if i reboot ClearOS but won't do it automatically (I assume if I just reboot the network or firewall service it will also work), this isn't a problem when i am available to reboot but if i am away and unavailable the office is without phones. I had this issue on community ClerOS 6 and now i am on a trial of the latest ClearOS 7.5 Business thinking the propitiatory code might fix this as i plan to buy it anyway but the problem still persists. It is the only thing i have ever had an issue with using ClearOS over the last 6 years. Can someone try point me in the right direction of where to start looking for the problem. It's as if ClearOS is not closing the SIP ports initiated on WAN 1. If i test this by plugging out Wan1 and put it back after 5 mins or so the phones instantly work again. Other internet traffic is not affected as browsing, mails etc continue to work without users even noticing. It just refuses to route the SIP signaling after WAN change. Side note if after a reboot while sip is running fine on WAN2 if WAN2 goes down the same thing happens and SIP traffic doesn't automatically switch to WAN 1 until another reboot.
Friday, July 19 2019, 09:19 AM
Share this post:
Responses (4)
  • Accepted Answer

    Friday, July 19 2019, 10:14 AM - #Permalink
    Resolved
    0 votes
    I think it can take up to 5 mins for the connection to fully fail over. You could try looking at the /proc/sys/net/ipv4/route/gc_timeout mentioned at the end of this link.

    Are you saying it never fails over?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, July 20 2019, 08:30 PM - #Permalink
    Resolved
    0 votes
    Hi Mike....... From my limited experience/understanding of SIP, when your WAN fails-over onto WAN2, your phones will need to re-register with the hosted VoIP server, so that your change of public IP address is updated. Could it be that your phones are not automatically re-registering when they lose service, or that some default registration timeout is set quite high?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 22 2019, 05:05 AM - #Permalink
    Resolved
    0 votes
    Thanks for the responses. The fail over is happening fine as other traffic such as http, https and emails work fine on Wan 2 after fail over. Its just that the VOIP phones don't re connect to the cloud PABX when fail over happens. I tried waiting 10 minutes to see if the phones would eventually work but still not. I have checked the phone settings and the time out's are not the issue as even if i manually try to de register and re register the phone it does not work if the connection has failed over. If Wan 1 comes back online or i restart ClearOS even with Wan 1 still offline then the phones almost immediately re connect even if it's with Wan 2 after a reboot.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 22 2019, 11:25 AM - #Permalink
    Resolved
    0 votes
    Out of curiosity, if you install the conntrack package ("yum install conntrack"), if you system fails over, do your phones re-regester after their timeout period after issuing the command "conntrack -F"?
    The reply is currently minimized Show
Your Reply