Attention is currently required from: laforge.
1 comment:
Patchset:
I'm not really a big fan of removing code rather than fixing it. […]
Since you originally wrote this TRAU<->RTP code in 2020 and since you chose back then to implement HR support in TRAU-16k format instead of TRAU-8k, let me ask you: do you know of any historical E1 BTS model(s) that implement HR speech (or data) in TRAU-16k format? My admittedly naive understanding is that E1 BTS traditionally allocate one 16 kbit/s subslot for each GSM timeslot, thus when a GSM ts is configured for TCH/H, only 8 kbit/s is available for each lchan. Or does it work differently in some vendor implementations?
I am open to idea of fixing TRAU-16k-UL output code instead of removing it *if* I can see captures of Abis UL output from some historical BTS that implements this format. In that case I would first extend my ThemWi TRAU frame parsing tools to decode that format, verify that the test tool matches what the historical BTS put out, then fix the code in libosmotrau and unit-test it against the ThemWi decoding tool that was in turn verified against historical hw.
To view, visit change 39623. To unsubscribe, or for help writing mail filters, visit settings.