Closed #1221.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1221#event-1225035271___
Kamailio (SER) - Development Mailing List
Docs enhanced with the commit referenced above.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1221#issuecomment-325573307___
Kamailio
The are separate and orthogonal
Option 1:
```
rtpengine_manage('record-call=on')
## will start recoridng no need for start_recording()
```
Option 2:
```
rtpengine_manage()
### sometime later in route script
start_recording()
```
--
You are receiving this because you are subscribed to this
Is `record-call=on` a replacement for `start_recording()` or the option has to
be given to `rtpengine_manage()` and then the start recording function still
needs to be used?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
### Description
Document record-call option in rtpengine module
### Troubleshooting
rtpengine module has an undocumented option in rtpengine_manage and
rtpengine_offer
```
rtpengine_manage("record-call=on")
```
The use case is to start the recording immediately so the recording structures
