Hi.
In sysmobts we use ugly hack to auto-activate BCCH/CCCH on TS0 via opstart_compl(). How does channel activation looks like for osmo-bts-trx?
On a related note: how do we decide on number of AGCH? In case of sysmobts it's communicated to L1 in agch.u8NbrOfAgch via lch_par. What would be equivalent for osmo-bts-trx?
On a related note - are there some hw/sw limitations in osmo-trx which might prevent us from using 2 lchans on the same TCH/H timeslot?
See https://projects.osmocom.org/issues/1795 for details.
On 10/17/2016 05:06 PM, Max wrote:
Hi.
In sysmobts we use ugly hack to auto-activate BCCH/CCCH on TS0 via opstart_compl(). How does channel activation looks like for osmo-bts-trx?
On a related note: how do we decide on number of AGCH? In case of sysmobts it's communicated to L1 in agch.u8NbrOfAgch via lch_par. What would be equivalent for osmo-bts-trx?
On Wed, Nov 02, 2016 at 11:21:25AM +0100, Max wrote:
On a related note - are there some hw/sw limitations in osmo-trx which might prevent us from using 2 lchans on the same TCH/H timeslot?
Well, the point of TCH/H *is* 2 lchans per timeslot. If this were the case we might as well disable TCH/H completely and just use TCH/F on osmo-trx. I'm pretty sure it isn't a HW limitation, expecting a SW bug.
~Neels
-
Max -
Neels Hofmeyr