Browse Source

update readme to add stop recording command

pull/398/head
Claudiu Boriga 8 years ago
parent
commit
bb85236b67
1 changed files with 9 additions and 0 deletions
  1. +9
    -0
      README.md

+ 9
- 0
README.md View File

@ -748,6 +748,7 @@ a string and determines the type of message. Currently the following commands ar
* delete * delete
* query * query
* start recording * start recording
* stop recording
The response dictionary must contain at least one key called `result`. The value can be either `ok` or `error`. The response dictionary must contain at least one key called `result`. The value can be either `ok` or `error`.
For the `ping` command, the additional value `pong` is allowed. If the result is `error`, then another key For the `ping` command, the additional value `pong` is allowed. If the result is `error`, then another key
@ -1413,3 +1414,11 @@ call legs, therefore all keys other than `call-id` are currently ignored.
If the chosen recording method doesn't support in-kernel packet forwarding, enabling call recording If the chosen recording method doesn't support in-kernel packet forwarding, enabling call recording
via this messages will force packet forwarding to happen in userspace only. via this messages will force packet forwarding to happen in userspace only.
`stop recording` Message
-------------------------
The `stop recording` message must contain the key `call-id` as defined above. The reply dictionary contains
no additional keys.
Disables call recording for the call. This can be sent during a call to imediatley stop recording it.

Loading…
Cancel
Save