Re: T200 expiring with nanoBTS, breaking voice calls

Hi Mychaela, On Thu, Apr 21, 2022 at 10:51:13PM -0800, Mychaela Falconia wrote: excellent. What can be seen is that * Frame 2801: CHAN RQD (RACH) with Access Delay = 0 * Frame 2840: CHAN ACT (SDCCH) with TA = 0 * Frame 3035: MEAS RES with TA=0, Timing Offset = 63 * Frame 3142: MEAS RES with TA=0, Timing Offset = 191 * Frame 3150: MEAS RES with TA=0, Timing Offset = 195 * Frame 3248: MEAS RES with TA=8, Timing Offset = 198 ... * Frame 5218: MEAS RES Actual TA=0, Timing Offset 12 * Frame 5312: MEAS RES Actual TA=8, Timing Offset 11 * Frame 5407: MEAS RES Actual TA=8, Timing Offset 1 * Frame 5689: CHAN ACT (TCH) with TA=8 So somehow your MS is moving extremely fast away from the cell, reporting enormous timing offset and causing a high TA to be used on the TCH. And despite that high TA, the MS still reports a timing offset of 63. I suspect some serious problem in the TA control loop either on MS or BTS side. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)