Feature #1781
closed
offer a dynamic TCH/H_PDCH pchan type
Added by neels almost 8 years ago.
Updated over 5 years ago.
Description
We now have these dynamic pchan types:
- TCH/F_PDCH (PDCH ACT style)
- TCH/F_TCH/H_PDCH (CHAN ACT style)
It would be fairly trivial to add a dedicated TCH/H_PDCH type,
i.e. a TCH/F_TCH/H_PDCH (CHAN ACT style) that has TCH/F disabled.
Downsides: it adds a bit of code bloat (more switch cases...).
Benefits: Having this pchan type prevents phones from hogging a whole
TCH/F, theoretically doubling the capacity.
A different way to allow dyn TS without TCH/F is in https://gerrit.osmocom.org/603
if one adds a VTY command.
Of course it would be a far nicer user experience to have an actual TCH/H_PDCH pchan type.
to be able to add a VTY command, https://gerrit.osmocom.org/1140 would be helpful.
So far, in the 603 patch we set dyn_ts_allow_tch_f after reading the config.
#1140 would allow setting the default to false in osmo-nitb only, and reading the config later on.
gerrit patch 1140 is now merged to master, so we could now add a VTY config for
osmo-nitb to allow/disallow TCH/F on dynamic TCH/F_TCH/H_PDCH timeslots.
(My attention is with the VLR though.)
- Project changed from OpenBSC to OsmoBTS
- Status changed from New to Rejected
If we configure a pchan of TCH/F_TCH/H_PDCH and a codec-list of only half-rate codecs, we also obtain dynamic TS that will never be used for TCH/F.
Furthermore, if the codec-list features FR after the HR codecs, then we prefer to use TCH/H, but if unavailable use TCH/F, which is the same as above with a fallback to TCH/F.
Bottom line: this feature idea is not going to be implemented because the codec-list provides all useful flexibility already.
Also available in: Atom
PDF
