I'd say you need to keep parameters for limit concise and standard. E.g. do it in the same format for all customers / trunks:
limit hash maximum_calls ${customer_id} ${customer_limit}

Once things are standard just iterate over a list of ${customer_id}'s every N minutes:
limit_usage hash maximum_calls ${customer_id}


On 14-05-14 01:39 PM, Andre Demattia wrote:
Anyone have any thoughts on this?
From: andretodd@verizon.net
Sent: ‎5/‎13/‎2014 10:13 AM
To: freeswitch-users@lists.freeswitch.org
Subject: [Freeswitch-users] Query Limit to see how many ports are in use

Hi, I want to know how can I query everything in LIMIT (hash) to find out how many active ports I'm using. I did see something about Hash_Dump All but I'm not sure what that does. limit_usage <backend> <realm> <id> requires too many parameters, I just want to know everything active.
 
 
I have disabled "nosql" the core database for faster performance (assuming this really helps with performance, let me know if it has nothing to do with performance) so that isn't an option.
 
Also, since the core db is disabled, is there a way to see the active calls with UUID so I can kill them if needed?
Thanks
Andre


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

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