I am, the problem is when the route changes on the FS server due to an outage on the primary link.

Is there a way to force FS to switch between the IPS dependant on the default route?

I have two profiles and each is setup with a separate SIP EXT, RTP EXT IP dependant on its WAN link details.

When the primary link goes down and the failover circuit is operational calls are still trying to route over the primary profile and SIP is broken since those public IPS are currently not in use.

---

From: Steven Ayre [mailto:steveayre@gmail.com]
Sent: Monday, May 11, 2015 3:49 AM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] need SIP IP / RTP recommendation

Set the sip-ip and rtp-ip parameters on the profiles directly rather than using ${local_ipv4} (which guesses your main WAN IP) or setting the external_ip variables in vars.xml. The later are only to simplify matters on simple setups (ie one WAN IP), for multihomed hosts such as yours you should set it on the profile directly.

On 8 May 2015 at 13:58, Jason Holden <jason.holden@start.ca> wrote:

Currently I have a client who is using multiple WAN IP addresses.

On route fail over FS still tries to use the original IP details from the external profile and not the secondary circuit details from the secondary external profile.

What have others done to address this to ensure failover works propperly?

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org