On Thu, Sep 21, 2017 at 04:36:51PM +0200, Max wrote: > Hi. > > On a related note. There's clearly big difference between split BSC/MSC and > NITB > (config files, support for SCCP-lite etc) which makes the transition rather > lengthy. > > What about SGSN and related stuff? It's been transitioned to libvlr at the > time of > split as well, but does this transition have any user-visible consequences?
Slight misunderstanding: no, the SGSN has "always" had GSUP support and is not actually using libvlr. All we did is upgrade the SGSN to be able to do UMTS authentication (Milenage). There was a plan to use libvlr in the SGSN as well, but since the SGSN is now working as it is, we are unlikely to do that. > If not than we could transition gradually: > * make SGSN build optional (--enable-gprs?) in openbsc repo osmo-sgsn is in its own repository now. Makes no sense to add such config option there. > * start building OsmoSGSN from osmo-sgsn repo instead of openbsc (both .deb > and OE) yes, that is the transition. The BTS and SGSN are notably the most back- and forward compatible components in this transition, there isn't much difference except the M3UA/SCCP addition in the SGSN, which again is only needed for IuPS, i.e. 3G data. IIRC the entire 2G SGSN land is identical between openbsc.git and osmo-sgsn.git. The points needed to transition mostly apply to: BSC, STP, MSC, HLR, MGW. > * test and make sure that it works the same way (both on sysmobts and on > debian) > * disable SGSN build by default and announce that patches should be made > against new repo > * remove gprs code from openbsc leaving placeholder readme with the link to > new repo The entire openbsc.git repository will cease to be used. We will not remove parts from it, we will basically lay it to rest as a whole. ~N
