Hi all,
Patch-file is attached - addresses a FIXME in abis_nm.c, parsing the
parameters passed by a Software Activate request. I've tested this on
three different IpAccess BTSs (including one which didn't work with the
original code), would be good if someone could check it on a BS11.
Best regards, Mike H.
Hey guys,
back in January I added ref-counting to the lchan and it has worked to some
degree, and we have seen ref-leaks as well (fixed thanks to Andreas). Currently
I'm working on integrating OpenBSC into a real MSC at on-waves.com and this
has made me read the GSM08.08 specification a bit more.
I would like to implement the following.
- Remove the refcount from lchan
- Replace it with the "transaction" concept. On certain 04.08 messgaes
(e.g. paging response, various MM messages) open a transaction
from BSC to MSC code. The channel is bound to the transaction.
The lchan is getting released when the transaction is finished, in
case of the "RSL chan" is going away too early there will be a
"clear" signal/method called from the BSC and the MSC side is asked
to let it go.
The benefit of this:
- BSC and MSC are better separated
- My MSC code could wrap the transaction into a SCCP connection
- Channel leak == transaction_free not getting called.
regards
holger
Hi Zecke,
I've been reviewing some of your patches:
> commit 45f9b3d3fc47074652be951eb74df2b0be2a230f
> Author: Holger Hans Peter Freyther <zecke(a)selfish.org>
> Date: Fri Aug 21 05:30:19 2009 +0200
>
> [paging] Use one of the two reserved LAC to page every BTS
>
> For the on-waves.com MSC case we want to page every BTS reached
> of the network. Our gsm_subscriber entry does not have a LAC
> entry set and defaults to zero. Use the reserved 0x0000 to
> indicate that we want to use every bts in the network.
>
> This will influence the paging code to start and stop paging.
The problem is that in the current code, we use LAC == 0 to indicate that the
subscriber has sent an IMSI DETACH message, i.e. switched his phone off.
You are now redefiniing the LAC 0 to something like the opposite case, which
I don't particularly like. Is there some alternative solution?
Regards,
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)