On Waves branch status and the road ahead

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/.

Holger Freyther zecke at selfish.org
Fri Nov 20 17:13:33 UTC 2009


Hey Guys,

this is just a small head about the current work and how it relates to the 
OpenBSC project. So far I had developed in a branch and used rebase on it but 
I'm going to do regular releases so I have to stop modifying the history.


Now I have the following branches:


on-waves/mgcp:
	- This includes the MGCP media gateway implementation. The MSC in use
           has a mapping from the Circuit Identity Code (Multiplex + Timeslot) 
           to an MGCP Endpoint. To ease development I have one bsc process
           and one mgcp one. To properly "connect" audio bsc and mgcp share
           a secret which is the RTP port to be used... E.g. I can bind all 
           RTP ports ahead of time (also nice for tunneling data).

           There is some overlap with the current rtp proxy code but I'm not
           yet sure how these two fit together... So the future might be I 
           include the MGCP code in the BSC and use the existing proxy code..
           but I really don't know right now.


on-waves/sccp:
	- This includes the SCCP implementation. It has a test case and is working
          quite reliable. Addressing (SSN) is achieved with something like a 
          sockaddr and it is mostly following the socket semantic. Instead of 
          accept and select I do have callbacks... this might change in the 
          future.
	- There is no MTP* implementation in the code base...
	- The one "problem" with it is the memcpy... and "queuing" inside the
          code but both will be addressed over time.


on-waves/gsm0808:
	- This is the current BSC app and GSM080 (BSSMAP/DTAP) code..
        - This branch will rename the bssap.c to gsm_08_08.c and remove
          all traces of SCCP from it, some code will move from bsc_msc_ip.c
          to the bssap.
	- an API will be created that can be used by the bsc_msc_ip.c and
          the bsc_hack.c/gsm_04_08.c code.
        - In terms of OpenBSC I want this to be done after the congress to not
          create a mess right now.


on-waves/bsc-master:
	- This will be my release branch. I will pull from the three branches, update
          version, put in hacks, or short term things that are necessary.
	- Think of it as a incubator for "master"



as there is little danger of breaking things I have merged the MGCP and SCCP 
branches into master as well. I hope there is agreement (otherwise there is 
always git revert)

z.




More information about the OpenBSC mailing list