[Freeswitch-users] Bridge app and SIP 503
steveayre at gmail.com
Sat Feb 26 20:46:44 MSK 2011
One possible solution is
<action application="set" data="hangup_after_bridge=true"/>
<action application="set" data="sip_ignore_remote_cause=true"/>
<action application="bridge" data="..."/>
<action application="hangup" data="..."/>
Failed calls will hit the hangup and hangup with a different reason to the bleg. That will let you return something other than 503. You could instead run a lua script if you want to add some intelligence to return different responses based on what comes back from the gateway or which gateway it is.
A better solution might be to disable it on the balancer before doing fsctl pause.
Steve on iPhone
On 25 Feb 2011, at 20:11, "Bill W." <freeswitch at aastral.net> wrote:
> Hi all,
> I'm using a failover bridge string with several gateways.
> <action application="bridge"
> 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
> Does anyone have any recommendations on how to address this issue?
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
More information about the FreeSWITCH-users