Use Cases: Dropping calls with Tbstatus: Difference between revisions
Lucas Joyal (talk | contribs) mNo edit summary |
(change format to improve readability) |
||
| Line 1: | Line 1: | ||
The following use case provide guidance for dropping multiple calls with tbstatus: | The following use case provide guidance for dropping multiple calls with tbstatus: | ||
== Usage Example == | |||
<code> | <code> | ||
tbstatus /uct/call:"filter(drop_call=true,parameter1=value1,parameter2=value2,...)" | tbstatus /uct/call:"filter(drop_call=true,parameter1=value1,parameter2=value2,...)" | ||
</code> | </code> | ||
Be careful when sending this command, as a too broad request '''will''' drop all active calls. | Be careful when sending this command, as a too broad request '''will''' drop all active calls. | ||
== Reference == | |||
[[Filter_parameters_reference_guide_A|Filter parameters reference guide]] | |||
Latest revision as of 12:27, 29 November 2017
The following use case provide guidance for dropping multiple calls with tbstatus:
Usage Example
tbstatus /uct/call:"filter(drop_call=true,parameter1=value1,parameter2=value2,...)"
Be careful when sending this command, as a too broad request will drop all active calls.