Attention is currently required from: falconia, fixeria, neels.
Patch set 3:Code-Review +2
1 comment:
Patchset:
I'm in two minds here; this seems to be a single person effort.
One very dedicated person who has proven certainly beyond doubt the level of dedication; I'm not worried here.
This stuff puts me off
I find it rather amusing [not sure if it's intended that way] and the entire format of those specs could possibly even be read as a parody of the way those specs are typicaly written.
In general I'm critical to "RTP extension". RTP is maximally flexible by allowing any payload types to be used, even if they are pure fantasy.
https://www.freecalypso.org/specs/tw-ts-002-v010100.txt contains an explanation why now different/new payload types are introduced.
Adding custom IEs to BSSMAP is not done in osmocom yet, and we have no way of indicating the BSS' custom capabilities to osmo-msc. How do you solve that?
It would likely have to be configured/enabled out of band on both BSC and MSC side. For sure we cannot merge patches that would unconditionally introduce sending non-standard IEs on the A interface. Bu that's not happening here.
BTW, if we have custom BSSMAP IEs, then I might want to add an IE to use an array of octets to describe all permitted AMR bitrates in a sane way
you can do thay, if you'd like to do it - however it would of course only work in a fully osmo-* network, and not have significance outside of that osmo-only deployment.
To view, visit change 36669. To unsubscribe, or for help writing mail filters, visit settings.