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.deOn Tue, Jul 18, 2017 at 09:48:01AM +0200, Harald Welte wrote: > > But OsmoBSC says: "Can not have full-rate and half-rate codec." Curious, is > > that a hard limitation? I'm not at all familiar with the reasons. Will we never > > be able to mix FR and HR? Why then does TCH/F_TCH/H_PDCH exist? > > I'm not sure why the BSC would ever say something like that. The BSC > normally simply picks a codec from the codecs that the MSC permits for > the given call. The MSC should be in charge of requesting a specific > codec if it wants a specific one. Been there since late in 2010: http://git.osmocom.org/openbsc/commit/?id=7bf66c5a6ee085bb84e5f1de12725d7006cf6a3c It sounds a bit like this belongs in the MSC instead. So far it's in the BSC config's 'msc' item, i.e. telling the BSC the remote MSC's config. ~N -------------- 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/20170718/045c92d2/attachment.bin>