On Mon, Jul 24, 2023 at 10:15:53AM -0800, Mychaela Falconia wrote:
Back to this thread's OP, I also recommend
sticking with 2023-02
release for the time being - the non-SDP-fied OsmoMSC plus matching
You are welcome to use a release marked stable, but...
I find it odd to read here handwavy dismissal with the words "completely
broken" paired with "I have no time" and then basing recommendations to
others
on that.
Current master passes the test suite, and it works very well for others. The
codecs patches in question have run at various CCC events.
The codecs behavior in osmo-msc makes a lot more sense in current master. But
osmo-sip-connector is not yet up to speed. It would help to use
osmo-sip-connector from branch neels/codecs3.
In the older release, things are much worse: it actually may require fixating
the setup on a single codec, and hardcoding that specific codec in
osmo-sip-connector's source with a manual build, to be able to get the codec
that you expect through to SIP. So it may be infinitely more fun to configure a
new setup with current master of osmo-msc, and seeing codec choices from the MS
actually showing up in SIP *at all*.
~N