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/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn Mon, Apr 04, 2016 at 10:16:00AM +0200, Neels Hofmeyr wrote: > On Sun, Apr 03, 2016 at 10:27:51PM +0200, Harald Welte wrote: > > Hi Neels, > > > > one more comment: > > > > On Sun, Apr 03, 2016 at 10:05:07PM +0200, Harald Welte wrote: > > > I therefore think the HNB-GW should try to look only like a single RNC > > > to the MSC, and very clearly only a single RANAP Reset should be sent. > > > > One further reason: The RNC-ID only has a range from 0..4095, i.e. if > > Hold on, in the RANAP specs I see the Extended RNC-ID IE: > > "The Extended RNC-ID IE shall be used if the RNC identity has a value > larger than 4095." > > It extends the range to ..65535 (9.2.1.39a in 3GPP TS 25.413 version > 12.4.0 Release 12). However, in our asn.1 the Extended RNC-ID seems to be available only for Enhanced Relocation Complete messages. 9.1.33 lists it as optional IE for an InitialUE message, but it seems I can't parse it with anything except ranap_decode_enhancedrelocationcompleterequesties(), which is not related to InitialUE messages. It thus seems that extended RNC IDs aren't widely used? I also found the words "Note: Application of the Extended RNC-ID IE to very large networks is FFS." in 9.2.1.39a. FFS meaning... For Future Something? I'm not supporting extended RNC-Ids at this point. ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160405/1b91696b/attachment.bin>