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/.
Neels Hofmeyr nhofmeyr at sysmocom.de(found this mail stuck in my outbox, sending late) On Mon, Feb 06, 2017 at 10:09:23AM +0100, Ivaylo Kostov wrote: > Hi Harald, > > I see. What was communicated to me was that NITB channel configuration > TCH/F_TCH/H_PDCH is not supported with nanoBTS. > > I will have in mind that nanoBTS does not support HR (v1) codec. Yes, we discussed TCH/F_TCH/H_PDCH for the nanoBTS. I remember to be surprised because from some discussion it appeared that the nanoBTS supports HR, and I was expecting TCH/F only. 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? ~N -- - Neels Hofmeyr <nhofmeyr at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170208/5dfdfaff/attachment.bin>