The application will transfer the call to the specified number/dialplan/context if the resource is currently over-limit. Note that you can also do rate-limiting with this application by specifying an interval, 5/1 will limit the resource to 5 calls per second. Here is the syntax for the main application: ]]" /> It uses a hashtable as data structure (faster) and has some additional features. Mod_hash provides a hashtable backend for limit. You may choose to take advantage of the db backend mod_db to allow multiple servers to limit the number of calls and stay aware of how many calls has in session across all participating servers. NB: if the limit is on the destination number, and then the call is transferred to another extension even in same context, limit will be decreased Backends db Note: limit is not decreased if you transfer the call using the "REFER" method, eg using the TRANSFER button on the phone. Limit_ignore_transfer=false - calls that are transferred cause the call count for that realm_id to decrement This is useful where calls that come into a gateway are transferred to an extension, but you want to preserve the call count. Limit_ignore_transfer=true - causes the current call count to not be reset when the call is transferred. More specifically, the delete is limited by uuid, hostname, realm and id. These channel variables are used at hang up to remove the record. The following channel variables are set when limit is called. hash_remote | | Channel Variables Variables Set by Limit It hen adds that to normal hash usage on the current server. It seems it queries each remote hash endpoint every 5 seconds for the entire hash list. Configure your server names and credentials in conf/autoload_configs/. The hash_remote API uses the event socket. You can access data from other FreeSWITCH systems with the hash_remote API. Manually reset the interval counter to zero prior to the next interval starting: Only implemented in Hash, not DB or hiredis. Otherwise, it removes all limits held by the given UUID.
If realm/resource is specified, it removes only that limit. Manually decrease the usage by one by removing the "usage" entry for that UUID. NB: if the limit is on the destination number, and then the call is transferred to another extension even in same context, limit will be decreased limit_usage uuid_limit_release Retrieve current usage for a given resource, all backends. Only supported in DB, not hash or hiredis. Retrieve current status of a given backend.
The application to execute application arguments NB: if the limit is on the destination number, and then the call is transferred to another extension even in same context, limit will be decreased application Setting the value to zero will set a limit of zero, meaning no concurrent executions.
If set to a negative value then there is no limit the limit system simply acts as a counter. The maximum number of concurrent executions or an interval in executions/sec. The resource on which to limit application execution max NB: if the limit is on the destination number, and then the call is transferred to another extension even in same context, limit will be decreased limit_execute backend limit_executeĮxecute requested APP only if resource has not reached its limit If you don't give it, limit transfers to 'limit_exceeded' extension in the current dialplan and context. Transfer to this extension in the dialplan. The interval argument is ONLY supported by the hash and hiredis backend. NB: if the limit is on the destination number, and then the call is transferred to another extension even in same context, limit will be decreased If not set or set to a negative value the limit application only acts as a counter. The maximum number of concurrent calls allowed to pass or a call rate in calls/sec.
The resource on which to limit the number of calls.
0 kommentar(er)
