On Sun, Feb 21, 2016 at 02:10:32PM +0100, Holger Freyther wrote:
The initial idea was that at the "MSC" the
"Complete Layer3 message" (the initial message) would arrive. The MSC would then
create an instance of a msc_subscriber_connection (and add a backpointer to the
gsm_subscriber_connection which then probably should be called bsc_subscriber_connection).
The MM, CC and other code should then refer to the msc_subscriber_connection. In case of
osmo-cscn the msc_subscriber_conn would point to the "Iu" definition and for
osmo-nitb it would still have the gsm_subscriber_conn backpointer.
The other part was that there should be something like msc_api inside the MM/CC code that
either directly maps to the BSC code or in case of osmo-cscn send it to the HNBGW.
The thing is, I need to get to know most of the code first. And I'm so far
just trying "to reach the other side" and would like to look at the
rackety bridge I built in a second iteration. I presume the basic building
blocks will be useful to rearrange them in a bigger picture, which I'm in
my head still busy enriching with the details.
So I would first like to see IuCS do something useful and then let's look
at the hopefully limited madness I created to obtain that.
Today I'm going to hunt segfaults in hnbgw so I can continue testing.
~Neels
--
- Neels Hofmeyr <nhofmeyr(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
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte