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/.
Harald Welte laforge at gnumonks.orgHi Holger!
On Wed, Jun 10, 2009 at 04:51:47PM +0200, Holger Freyther wrote:
> some of us started to look into the various 08.0x specs and even SCCP (not me
> yet) and I think our common goal is to go towards a more "normal" BSS/MSC and
> in the same way keeping the spirit of bsc_hack to allow to run a whole network
> with one executable.
exactly.
> To keep this short ('m quite tired at the moment) my goal/approach is to
> create a libmsc.a and move the db.c, gsm_subscriber.c and on the way to move
> policy out of gsm_04_08.c to the libmsc.a. bsc and msc would communicate with
> an API that resembles the DTAP, BSSMAP interface. The MNCC use case Andreas
> and Harald are working on should remain supported, same as the bsc_hack.c.
yes. Basically the split you are introducing is below the MNCC and the
bsc_hack application cases. They both use [parts of] MSC and BSC functionality,
i.e. can be implemented on top of the libmsc + libbsc combination that you're
aiming for.
> I will start this work in a branch called holger/msc and will seek for
> feedback once I have something that is worthwhile to share.
great. good luck!
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20090611/3d1baadf/attachment.bin>