### Description Document record-call option in rtpengine module
<!-- Explain what you did, what you expected to happen, and what actually happened. -->
### 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 are initialized in rtpengine. If we do not do this but use a sequence like
``` rtpengine_manage() /* A */ /* what happens is recording structures are no initialized so metadata for caller's SDP is not written ou */ start_recording() /* B */ ``` The metadata of the recording will omit the caller's SDP because this is written out during A but recording structures are only initialized in B.
https://github.com/sipwise/rtpengine/issues/385
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?
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() ```
Docs enhanced with the commit referenced above.
Closed #1221.
-
aalba6675 -
Daniel-Constantin Mierla