Attention is currently required from: falconia, pespin.

laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/32110 )

Change subject: common+trx: add rtp ecu-downstream vty option ......................................................................

Patch Set 3:

(2 comments)

Commit Message:

https://gerrit.osmocom.org/c/osmo-bts/+/32110/comment/a3ff9b45_3d88dfe2 PS3, Line 9: Current osmo-bts-trx includes a provision for invoking ECUs from : libosmocodec in the UL path from the channel decoder to the RTP : output; no other models currently do likewise, but there is no : particular reason why this ECU invokation couldn't be moved into : model-independent code. Some background knowledge: AFAIR, osmo-bts-sysmo (and hence liekly its relatives oc2g + lc15) already do some ECU magic in the DSP. Then some user discovered that audio sounded worse on -trx than on -sysmo, and they implemented the "provision for invoking ECUs" in -trx [only].

Patchset:

PS1:

...

So AFAIU you are saying that your ECU is located somewhere in the CN after osmo-msc, as in some so […]

I think rather than specifying that an ECU happens somewhere "downstream" I think it's more logical that the osmo-bts config file specifies what osmo-bts itself does. So let's rather name it in the inverse logic. something like "rtp builtin-ecu" or "rtp perform-ecu" or "rtp internal-uplink-ecu" would be most applicable in my understanding.