[Freeswitch-users] SIP SRV failover behavior
avi at avimarcus.net
Mon Feb 4 20:11:52 MSK 2013
Not really the answer, but...
There's a gateway param called "ping", e.g:
<!--send an options ping every x seconds, failure will unregister
and/or mark it down-->
<param name="ping" value="25"/>
Then if it's marked down (via 202 or 404
any bridge string referencing that gateway will know it's down before
contact it and move on. (with error code NETWORK_OUT_OF_ORDER)
You can see that showing up in the logs, and I think in the gateway status.
I don't see a command to manually re-ping the gateway.
On Mon, Feb 4, 2013 at 6:52 PM, Jeff Pyle <jpyle at fidelityvoice.com> wrote:
> I use an SRV record as the proxy value for a sofia gateway. This
> particular record is configured for failover rather than load
> balancing. In other words, there is only one record per priority. I've
> verified Freeswitch will advance to the second host if the first becomes
> It seems Freeswitch waits around 10 minutes before it tries the first
> host again. Is this delay a configurable value?
> Is there some kind of internal blacklist the failed host occupies before
> this timer expires? Is this list manageable from the CLI?
> Besides a 408, are there other response codes that will land a host on
> this apparent blacklist?
> - Jeff
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users