Indeed... there's a specific ISDN clearing cause for it - 34 "no circuit/channel available" (NORMAL_CIRCUIT_CONGESTION). That maps to SIP 503 Service Unavailable (RFC3398).
Unallocated number implies it's not allocated anywhere and therefore shouldn't reroute, while 503 suggests you should try another route.
-Steve
Charles,if you may, I would recommend you change the behaviour of this GW sending back a 404 when it's full...That's odd.It should rather use: 503 Service unavailable.David Ponzone Direction Techniqueemail: david.ponzone@ipeva.frtel: 01 74 03 18 97gsm: 06 66 98 76 34Service Client IPevatel: 0811 46 26 26Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur.
Le 21/04/2011 à 04:45, fieldpeak a écrit :Thanks All, it is resolved now with below config.
2011/4/20, Kristian Kielhofner <kris@kriskinc.com>:
Try this:<extension name="9_GW" ><condition field="destination_number" expression="^(9\d+)$">
<action application="set" data="continue_on_fail=true"/><action application="set" data="failure_causes=UNALLOCATED_NUMBER"/>
<action application="set" data="hangup_after_bridge=true"/><action application="bridge" data="sofia/internal/$1@192.168.200.201"/>
<action application="bridge" data="sofia/internal/$1@192.168.200.202"/></condition></extension>On Wed, Apr 20, 2011 at 10:58 AM, fieldpeak <fieldpeak@gmail.com> wrote:
Hi Steve,Thanks for your so rich stuff provided.however, i tried to use error code to route as below, it failed (did
not route the next GW when recevied UNALLOCATED_NUMBER), can youplease point out is there any place wrong in the dailplan? attached is
the log, thanks.<extension name="9_GW" ><condition field="destination_number" expression="^(9\d+)$">
<action application="set" data="continue_on_fail=true"/><action application="set" data="hangup_after_bridge=false"/><action application="bridge"data="sofia/internal/$1@192.168.200.201"/></condition><condition field="brige_hangup_cause" expression="UNALLOCATED_NUMBER">
<action application="bridge" data="sofia/internal/$1@192.168.200.202"/>
</condition></extension>Regards,Charles2011/4/20, Steven Ayre <steveayre@gmail.com>:If you know the number of calls the GW can handle in advance, you can
limitthe call attempts before sending the call to the gateway:http://wiki.freeswitch.org/wiki/Limit
There are several ways to use that.You can reroute calls to a 2nd gateway on error:http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_bridge#Implementing_Failover
There are channel variables that let you control what to consider areroutable error and what is a give-up error:
http://wiki.freeswitch.org/wiki/Channel_Variables#continue_on_fail
http://wiki.freeswitch.org/wiki/Channel_Variables#failure_causes
This might also be useful, particularly with mod_limit:http://wiki.freeswitch.org/wiki/Channel_Variables#transfer_on_failYou could use mod_lcr to get a list of all the GWs, but in a random
order.That'd let you load balance (randomly) but reroute when required withoutduplicates unlike mod_distributor.
Hopefully that's enough building blocks to give you somewhere to start...-SteveOn 20 April 2011 08:27, Charles <fieldpeak@gmail.com> wrote:
i have two media GWs connected with FS for PSTN calls, FS route the
firstone in normal case, once the first GW get full (all of channels wereoccupied), i need FS route to the second GW.i found once the first GW get full, it will reply '404 not found' to FS,can FS route to the second one according to this condition or any otheralternative?although i know there is mod_distributor for load balancing, however, ineed if only first one full then route to second one, so it looks thismodule not suitable for this senario...Thanks.Regards,Charles_______________________________________________FreeSWITCH-users mailing listFreeSWITCH-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
_______________________________________________FreeSWITCH-users mailing listFreeSWITCH-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--Kristian Kielhofner_______________________________________________FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-usersUNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
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
_______________________________________________
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