You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those versions are still available at ETSI and 3GPP, and the module builds/works just fine with one of those.
However, the RI saw a major change request in September 2021. As a side-effect, that changed/extended the API of read_indices_from_djb(…) with three more parameters. Consequently, this project here does not build with the very latest versions of the RI. I have still to investigate whether
I have to use those new parameters (= complex, meaningful values), or
I can simply define those (= static values), or
that avoids a long-standing issue with unneeded double shuffling in the mode AMR-IO (and therefore not just different parameters but a completely different code flow in my Asterisk module).
Although I consider that Change Request critical security-wise, although I know that
an audio-codec implementation is exposed to the public, I do not fix but just note this issue for now. If you need an urger fix for this, please, give this issue report a thumps-up or contact me directly so I know that anyone still uses this module.
The text was updated successfully, but these errors were encountered:
The last versions of the RI being compatible are:
Those versions are still available at ETSI and 3GPP, and the module builds/works just fine with one of those.
However, the RI saw a major change request in September 2021. As a side-effect, that changed/extended the API of
read_indices_from_djb(…)
with three more parameters. Consequently, this project here does not build with the very latest versions of the RI. I have still to investigate whetherAlthough I consider that Change Request critical security-wise, although I know that
an audio-codec implementation is exposed to the public, I do not fix but just note this issue for now. If you need an urger fix for this, please, give this issue report a thumps-up or contact me directly so I know that anyone still uses this module.
The text was updated successfully, but these errors were encountered: