|
Failover routing
We have an asterisk pbx running on Centos 5.8
We are in the process of connecting to a cloud provider for call center functionality. Our current connectivity model is to have an mpls connection as our primary route for sip trunking and an IPSEC tunnel over our internet connection as the secondary path. On our firewall we have bgp configured for failover. Our cloud provider has required separate ip addresses for each path. I have provided them with the following ip addresses for them to route to the pbx:
10.100.0.107 - MPLS
10.100.0.110 - IPSEC
10.100.0.104 is our firewall
They have only provided one ip address for us to route to(216.xxx.xxx.111) and they have restricted the access to each path based on the above ip addresses because they set static routes on their end.
On my pbx the route to 216.xxx.xxx.111 goes to our firewall(10.100.0.104) with a source address of 10.100.0.107. This works when the MPLS connection is up. When the MPLS connection goes down, bgp routes the traffic to 216.xxx.xxx.111 via our IPSEC tunnel. The IPSEC tunnel won't accept the traffic because the source address 10.100.0.107 is not allowed. If I change the src address of the route to 10.100.0.110 then it works.
The default route on the pbx is set to have 10.100.0.110 as the source.
When the mpls ciruit goes down, is there a way to get the server to use the default route instead of the route to 216.xxx.xxx.111?
I'd like to avoid using scripts to monitor. I am not a networking expert, so I'm hoping I am missing an easy solution.
Please let me know if I have been unclear or left out any pertinent details.
Thank you.
|
