JBM: JBM control gets the wrong information in case of non-20ms rendering frames
### Basic info - Commit SHA: 894ce68d9ae2e3b510ba5ceb2892d2c99dec2f4b - Platform: all ### Bug description The JBM control logic needs some information about how much signal is buffered to determine if it drops/adds/time scale modifies packets and the amount of TSM applied. For non-20ms rendering frames, this information is currently not correct ### Ways to reproduce Run VoIP decoding with either `-fr 5` or `-fr 20` leads to non-BE <!--- Below are labels that will be added but are not shown in description. This is a template to help fill them. Add further information to the first row and remove and add labels as necessary. -->
issue