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 Alexander and others, On Wed, Jul 13, 2016 at 04:59:11PM -0400, Alexander Chemeris wrote: > > phys_chan_config TCH/F_TCH/H_PDCH > > I personally prefer this option, because it doesn't leave a place for > doubt. And ti's not something you would type 100x a day, so making it > short is not a real optimization. I also think it should be kept this way for consistency with other pchan names. From a VTY syntax POV, the '/' are ugly in the name, and we never use that anywhre else in the VTY but the channel config - but the '/' is part of the official specified names, so I chose to use them with the existing channel types when originally writing that code. > Reading this, I would be asking myself "DYN - what is that? Dynamic? > Ok, Dynamic what? Channels? Ok, which channels? Can it have SDCCH in > there? Hmm.. Don't know. Let look into the docs. Docs say no. Can it > be SDCCH in the next release of the software? Huh, don't know, I > better to put something more specific here, so I'm sure what's > happening. But how to do that?" The VTY offers a help string at tab-completion which could have the anwer to this, so I don't think that point is such an issue. -- - 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)