This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi all,
On Wed, Feb 08, 2017 at 04:26:11PM +0100, Neels Hofmeyr wrote:
> While talking about codecs, the ip.access nanoBTS *should* in fact support the
> TCH/F_PDCH dynamic timeslots. Ivaylo, could you check whether that is part of
> your testing procedure and add it if not?
libbsc should be extended to handle those restrictions, i.e. reject a
configuration containing HR codec or a osmocom-style dynamic channel on
a bts model 'nanobts'.
Similarly, the BS11 should reject any codec except HRv1, FR and EFR
(i.e. no AMR).
In reality there are also older nanoBTSs that don't support AMR (as far
as I remember), but that shouldn't prevent us from having at least the
most basic checks in place.
For osmo-bts, we need a more sophisticated hand-shaking mechanism, as
there are many different hardware/PHYs (and associated versions)
supported by it. This is left for further study ;)
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)