3e9b2ec257
If subscriber A is calling B and has sent a CC Setup message we will allocate the MO and MT transaction and link them together. When the BTS or the lchan is failing the BSC API will send a clear request, as part of the clear request all pending transactions will be released. As part of taking down the transaction, the remote leg will be informed and will send a MNCC_REL_REQ. This results in a call to trans_free. The llist_for_each_entry_safe does not handle removing other elements from the list and we would segfault. One way to fix this is to move the transaction list into the subscriber connection. This might require to create the subscriber connection for MT handling earlier. Otherwise one could have one transaction list inside the subscriber connection and a global list for MT- transactions. |
||
---|---|---|
.. | ||
contrib | ||
doc | ||
include | ||
src | ||
tests | ||
tools | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
Makefile.am | ||
README | ||
configure.ac | ||
git-version-gen | ||
openbsc.pc.in |
README
About OpenBSC ============= OpenBSC is a minimalistic implementation of the GSM Network, with particular emphasis on the functionality typically provided by the BSC, MSC, HLR, VLR and SMSC. Its currently supported interfaces towards the BTS are: * Classic A-bis over E1 using a mISDN based E1 interface. In other words, you can connect existing GSM Base Transceiver Station (BTS) through E1 to OpenBSC. So far, we have only tested the Siemens BS-11 Test reports with other BTS are much appreciated! * A-bis over IP as used by the ip.access nanoBTS product family You can find the project documentation at http://openbsc.gnumonks.org/ This project is still in its early days, and there are lots of areas where it doesn't behave as per GSM spec. Harald Welte <laforge@gnumonks.org> libosmocore =========== Please note that as of March 2010, OpenBSC has a dependency to a library called "libosmocore". You can obtain that library from git://git.osmocom.org/libosmocore.git