Hi all,
here is just a small information of what is going on and what will
happen in the near future.
Done:
- Create bsc_api.c for the BSC API handling
- Create osmo_msc.c for the callbacks...
- Start to remove lchan usage from MSC code
What will happen:
- No MSC code will directly touch/use/know about the lchan
- Move the gsm48_recvmsg into the BSC API and dispatch
- The transaction will be anchored inside the subscriber con
and no transactions will clear the channel immediately
- Need to add API for Cipher, Handover, Assignment handling
- pick a better name for subscriber_connection.
What can happen after this:
- We can reimplement the bottom of the BSC API with SCCP
and have a true MSC codebase...
If any of you is adding new L3 code, please do not use the LCHAN
directly but the subscriber connection.
thanks
holger
Show replies by date