[Freeswitch-users] Freeswitch Limit execute_on_originate Question
Andre
andretodd at verizon.net
Sat Oct 26 18:37:02 MSD 2013
Hello,
I'm calling execute_on_originate to an app LimitOutbound on my bridge action
for LIMIT.
var ses = context.Session;
ses.Execute("limit", string.Format("hash outbound gw_{0} {1}
!NORMAL_TEMPORARY_FAILURE", gwnamne, PortLimit));
ses.Execute("limit", string.Format("hash outbound gw_{0} {1}/1
!NORMAL_TEMPORARY_FAILURE", gwnamne, cps));
When I call it the limit goes back to 0 after the call routes. If I use a
new thread :: the numbers don't go back to 0 until after the call however
the new thread allows the call to go through and then it hangs up after the
limit is checked.
Per a post I saw it said to use execute_on_post_originate however that too
allows the call to process then hangs up the call if the limit is reached
either on single thread or multi-threaded.
Since my limit has 3 bridge actions I expect if the first gateway is at
limit it would route to the next one until one is available or no gateways
are available. The code above (assuming 3 bridges) will call and hang up 3
times.
I hope someone can help me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20131026/fefbabd9/attachment-0001.html
Join us at ClueCon 2013 Aug 6-8, 2013
More information about the FreeSWITCH-users
mailing list