18 May
2016
18 May
'16
11:06 a.m.
Seems like a bug. Does it only happens for 1900?
On 05/18/2016 11:04 AM, Holger Freyther wrote:
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
On 18 May
2016, at 11:03, Max <msuraev(a)sysmocom.de> wrote:
No, SI2qter is completely optional. The presence of it is indicated in
SI3 - see commit f3f3505f493f63e9e79c72e407907783913b9c9c in openbsc.
The scheduler is in src/common/sysinfo.c - see
f3ee66207de2859cf4751b44241c0f84cf0999b4 in osmobts.
yes, but why do we schedule
SI2qter for a GSM1900 cell that has absolutely no neighbors?