WAN Failover - SIP external server
-
Hi All,
I was hoping someone could help me with finding an answer to a problem I am having with my pfSense failover.The situation is that I have my primary WAN operating, I also have my secondary WAN connection set as a failover connection.
If I drop my primary WAN and the secondary kicks in, I my phones that connect to an external SIP server wont register any longer. When I reconnect my primary connection my phones still dont recover untill I disconnect the Secondary WAN and reset the States table.
Please if anyone could offer some guidance here I would really appreciate it.
I am running v2.2
"State Killing on Gateway Failure" - Is Unchecked / deactivated
-
Not sure about proper solution, but as a quick fix, you can tunnel your PBX or VoIP phones over VPN to some online VPS
PBX => VPN => VPS => SIP Provider
VPN can run over failover group, so you will have your incoming call availability lost during only the failover switch. As oppose to re-register interval. Which you will have anyway on failover: provider will not know about changed WAN IP address until the next SIP register
As additional benefit, you can have a completely static, NAT-free path between PBX and SIP server over single-double-triple …. NAT. At least, OpenVPN successfully pass through NAT, maintaining it's state with Keep Alive
-
I was hoping someone could help me with finding an answer to a problem I am having with my pfSense failover.
The failover is working proper as you mentioned, or am I wrong with it?
The situation is that I have my primary WAN operating, I also have my secondary WAN connection set as a failover connection.
Ok, but why not using load balancing together with policy based routing?
If I drop my primary WAN and the secondary kicks in, I my phones that connect to an external SIP server wont register any longer.
Is this the WAN connection from the ISP that offers also the VOIP line?
Is this a STUN Server or the SIP Gateway from the ISP?When I reconnect my primary connection my phones still dont recover untill I disconnect the Secondary WAN and reset the States table.
For sure it would be better to know for us who is offering the VOIP service and Who the Internet
services!Please if anyone could offer some guidance here I would really appreciate it.
I would try the following out, load balancing together with policy based routing because if
one WAN is failing the entire traffic will take the other WAN port only, so you get also a failover
but without the hassle of a unused WAN line.Pointing something to the SIP problem must be stated because on the poor informations
you where pulling out about.