Dear Osmocom community,
Over the past several months I've been working almost exclusively on improving FR1 and EFR speech handling in the Osmocom GSM network implementation. All of my Gerrit patches since March have been in this area, and my two Themyscira-branded public domain libraries for GSM codecs are also primarily intended for use together with Osmocom, specifically for implementation of transcoding media gateways that interconnect an Osmocom GSM network with a non-GSM outside world such as G.711 PSTN.
Given the knowledge I've gained over months of working in this area, and seeing that many other Osmocom developers aren't particularly familiar with these aspects of the specs (understandable: GSM is huge, can't keep everything in one's head), I would like to do an OsmoDevCall presentation on the topic of GSM speech handling with traditional non-AMR codecs. I would like to cover the following subtopics:
* What metadata bits (BFI, UFI, SID, TAF) are defined in the specs for transport of encoded speech between network elements, beyond the familiar speech codec bits themselves.
* What exactly are regular speech frames, SID frames, silence frames (a "silence frame" for FR1 codec is NOT the same thing as a SID frame!) and bad frame gaps, and which of these categories are allowed or not allowed to exist at each of the interfaces in the spec-defined GSM architecture.
* Which transformations are supposed to happen where: which network elements are responsible for bad frame handling, error concealment, comfort noise insertion or SID propagation.
* How these architectural principles, originally defined for the T1/E1 environment with TRAUs, can be carried over to an RTP environment.
* Relevant Osmocom components: OsmoBTS and the aspect of OsmoMGW that interfaces from RTP to T1/E1 Abis.
* What behavior changes have been effected by my patches to OsmoBTS and supporting libraries that have already been merged, and which behavior changes are still on my wish list or to-do list to implement and hopefully get merged.
Looking at the OsmoDevCall wiki page, I see absolutely nothing scheduled past May, and there was no OsmoDevCall in April - are we out of presenters? But we have just one problem: it seems that some people in the senior leadership of Osmocom organization don't want me presenting on OsmoDevCall, and recently even asked specifically for presentation ideas from "anyone other than Mychaela". I see two possible solutions to this problem:
Option 1: If the leaders in question could set aside their personal dislike of me and allow me to present on highly Osmocom-relevant topics (such as the FR/HR/EFR codec presentation proposal above) no different from other Osmocom developers, that would be the best solution.
Option 2: If those who control the scheduling of presentations on the official OsmoDevCall platform (the official BigBlueButton instance for ODC) are not willing to budge, the alternative will be for me and Das Signal (my dear friend and FreeCalypso sysadmin) to set up our own BBB instance on our own server, configure it to look and feel exactly like the official one used for ODC, hold presentations there during those months when no official ODC presentation takes place due to lack of non-excluded willing presenters, and invite everyone from Osmocom to join those unofficial ODC-like presentations.
So - which of the two is it going to be?
Sincerely, Mother Mychaela, operator of a non-profit GSM network based on Osmocom, contributing to Osmocom CNI development in conjuction with that network operation.
On Fri, May 12, 2023 at 11:11:37PM -0800, Mychaela Falconia wrote:
"anyone other than Mychaela" Option 1: If the leaders in question could set aside their personal dislike of me
As a person not feeling addressed by this, let me give some context. In the Osmocom community, just like leadership, exclusion is by merit only.
An open community is carried by its members, and if specific members choose to offer services, they may also choose not to. In my personal opinion you should hold a talk. But no opinion will force any member of this community to offer technical infrastructure and invest time and effort against their own choosing. If A is uncomfortable with B, then we, including you, can only respect that.
Mychaela, you are the only member in this community where there seems to be a constant background noise of social tension against other members. Please do your part in avoiding this.
In essence, we would love to discuss technical details of GSM, on-topic. Please cut the unrelated noise, as you've been asked to before. Every time that you don't steals time and effort from others.
In this spirit, as any member of this community, you are free and absolutely welcome to invite to your talk on GSM topics.
~N
"those who control the scheduling of presentations"
Huh ... it's the presenter who pick when they want to present ... (well within the normal slots or 3rd Wed of each month). You just put the date next to your talk in the table and that's it.
If for some reason there is an issue or date conflict or whatever, then we can advise, but the normal process is the presenter picks the date they want to present as first-come-first-served.
Sylvain
Sylvain wrote:
Huh ... it's the presenter who pick when they want to present ... (well within the normal slots or 3rd Wed of each month). You just put the date next to your talk in the table and that's it.
Based on these instructions from a senior community member, I just scheduled myself for 2023-06-21, on the topic of FR/HR/EFR voice codecs in Osmocom RAN. If anyone objects, please speak up now - otherwise, I shall start preparing for this presentation so I will be ready in time.
M~