Thank you for your suggestion! Good idea! I was searching for more complicated solutions but mod_limit is perfect! You say to use rate limiting but why not simply limit the calls number instead of rate? For example a row in dialplan as: <action application="limit" data="hash inbound ${destination_number} 1" /> can avoid loops? Stephen On Mon, Mar 7, 2011 at 5:37 PM, Ken Rice <krice@freeswitch.org> wrote:
I hate this problem... Mod_limit matching ani+dnis doing rate limiting (say 5 calls with matchig ani+dnis in 2 seconds) can kill the loop and either allow you to re-route or allow then to re-route... This happens a lot more than you thing between 2nd and 3rd tier aggregators
On 3/7/11 10:24 AM, "Stephen Wilde" <wstephen80@gmail.com> wrote:
In some situation there are calls that loops among some providers and I want avoid that situation. For example, I receive the call from my client A, I send this call to my provider B but for some reason the call return to me (for example because B sends the call to A and A resends the call to me). In case of loop for me the solution can be simply to drop the call so my client can reroute to a different provider. There is anyone that can suggest me a way to drop looped calls?
Stephen
------------------------------ _______________________________________________ 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