question about latest version of mod_limit
Hello, I have the following setup in the dialplan. Then, I fire up sipp to send 5calls/s and I expect to get limit-pass=false in most of the INFO output. However, I am getting all "limit-pass=pass". Does anyone know what is wrong with my dialplan? <context name="internal"> <extension name="test-limit"> <condition field="destination_number" expression="^9(.*)$"> <action application="limit_hash_execute" data="192.168.1.102 6000 1/1 transfer to-next" /> <action application="set" data="limit-pass=false"/> <action application="info" /> <action application="hangup" /> </condition> </extension> <extension name="to-next"> <condition field="destination_number" expression="^to-next$"> <action application="set" data="limit-pass=true"/> <action application="info" /> <action application="hangup" /> </condition> </extension> </context>
Possibly the calls are being disconnected too quickly? Try adding a sleep for 1000ms on each one and see what happens. -MC On Thu, Aug 6, 2009 at 4:26 AM, mark morreny <markmorreny@gmail.com> wrote:
Hello,
I have the following setup in the dialplan. Then, I fire up sipp to send 5calls/s and I expect to get limit-pass=false in most of the INFO output. However, I am getting all "limit-pass=pass".
Does anyone know what is wrong with my dialplan?
<context name="internal">
<extension name="test-limit">
<condition field="destination_number" expression="^9(.*)$">
<action application="limit_hash_execute" data="192.168.1.102 6000 1/1 transfer to-next" /> <action application="set" data="limit-pass=false"/> <action application="info" /> <action application="hangup" />
</condition>
</extension> <extension name="to-next"> <condition field="destination_number" expression="^to-next$"> <action application="set" data="limit-pass=true"/> <action application="info" /> <action application="hangup" />
</condition> </extension> </context>
_______________________________________________ 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
You are using it wrong. <action application="limit_hash_execute" data="192.168.1.102 6000 1/1 bridge sofia/gateway/etc" /> The purpose of limit_hash_execute is to have a resource that is released if the command doesnt complete properly. If you want to transfer when the res. is over-limit, use limit_hash, not limit_hash_execute. Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca On 6-Aug-09, at 5:26 AM, mark morreny wrote:
Hello,
I have the following setup in the dialplan. Then, I fire up sipp to send 5calls/s and I expect to get limit-pass=false in most of the INFO output. However, I am getting all "limit-pass=pass".
Does anyone know what is wrong with my dialplan?
<context name="internal">
<extension name="test-limit">
<condition field="destination_number" expression="^9(.*)$">
<action application="limit_hash_execute" data="192.168.1.102 6000 1/1 transfer to-next" /> <action application="set" data="limit-pass=false"/> <action application="info" /> <action application="hangup" />
</condition>
</extension> <extension name="to-next"> <condition field="destination_number" expression="^to-next$"> <action application="set" data="limit-pass=true"/> <action application="info" /> <action application="hangup" />
</condition> </extension> </context> _______________________________________________ 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
participants (3)
-
mark morreny
-
Mathieu Rene
-
Michael Collins