Regarding your balancer marking the gateway as down... 503 doesn't necessarily mean the gateway is out of order, for instance it will be returned by many sip providers for dcc34 normal circuit congestion, when all channels are in use. Steve on iPhone On 25 Feb 2011, at 20:11, "Bill W." <freeswitch@aastral.net> wrote:
Hi all,
I'm using a failover bridge string with several gateways.
<action application="bridge" data="sofia/gateway/primary/dialstring|sofia/gateway/secondary/dialstring"/>
One of the gateways responded to a mis-dialed number with a "503 Service Unavailable" instead of a "484 Address Incomplete"
My FreeSWITCH servers are behind a load-balancer, and what is happening is the bridge app is passing that 503 back to the load-balancer which then marks that gateway as down.
I can't remove the 503 detection from the load balancer, because that's how I disable a gateway from within freeswitch (fsctl pause, which sends 503).
Does anyone have any recommendations on how to address this issue?
Thanks!
_______________________________________________ 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