video conference behaves weird if calls are joined in early state
Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)
Several weird things happen in the daemon if a video conference is created from calls which are not yet in "current" (talking) state, eg: if 2 calls are still ringing and they are joined in a conference:
- On the conf master side, the daemon log starts continiously printing "[1467910558.018|19087|video\_mixer.cpp:135 ] VideoFrame::allocBuffer() failed"
- All participants receive no (or back) video, including master (this is probably related to the error above)
This daemon behaviour can be reproduced by either manually creating 2 ringing calls and joining them, or by using the 'createConfFromParticipantList' function (via d-feet, since its not used in LRC).
Related to this, using createConfFromParticipantList() causes a crash in LRC.
This bug is blocking for the feature or being able to immediately add participants to a conference, without waiting for each call to start first.