RESTful API: Dropping calls: Difference between revisions
Lucas Joyal (talk | contribs) (Drop call via tbconfig, first draft.) |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:RESTful API: Dropping Calls}} | |||
The following use case provide guidance for dropping multiple calls: | The following use case provide guidance for dropping multiple calls: | ||
== Usage Example == | |||
<code> | <code> | ||
tbconfig --port <port> -u <username> -p <password> | tbconfig -h <hostname> --port <port> -u <username> -p <password> -d -q "parameter1=value1,parameter2=value2" /call_traces/destroy_all | ||
</code> | </code> | ||
* -d flag is used to send a HTTP DELETE request method | |||
* -q is used to append the argument in the HTTP request | |||
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 15:09, 14 December 2021
The following use case provide guidance for dropping multiple calls:
Usage Example
tbconfig -h <hostname> --port <port> -u <username> -p <password> -d -q "parameter1=value1,parameter2=value2" /call_traces/destroy_all
- -d flag is used to send a HTTP DELETE request method
- -q is used to append the argument in the HTTP request
Be careful when sending this command, as a too broad request will drop all active calls.