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/.
Sipos Csaba dchardware at gmail.comHi Caleb, The segfault is introduced with this patch: http://cgit.osmocom.org/libosmocore/commit/?id=f5a079f739c57d8be7c59149fd45475c402a45fc Is is not really a bugfix, but if you just comment out the following part from lapd_core.c added by the above patch and recompile openbsc, it will help: dl->tx_hist = NULL; The problem is probably related to the RESET function, because Nokia units are being reset during the initialization phase, and bootstrapped after that. The reason for this is if this reset is not concluded, then the BTS will not apply certain configuration parameters (e.g. change in ARFCN, transmit power, timeslot configuration). I strongly suggest you anyway, to start with TCF/F FR configuration, and if you see major alarm "BCF operation degraded: difference between PCM and BTS clock", it means that your E1 card is not able to provide accurate enough timing for the BTS. According to Nokia, you need +-5Hz accuracy on the E1 to meet the timing requirements, but even then at least 20-25 minutes of operation is needed for the BTS clock to be synced and the alarm goes away. Usually DAHDI or other E1 cards clock are not precise enough but don't worry: even with the alarm you can make pretty good quality phone calls, but remember: if you experience severe call quality degradation, or the phones cannot camp, or they loosing the network all the time, it is going to be a timing related problem. Anyway, do you have the Nokia InSite manager software? If not just write me a mail and I can help with that. You definitely going to need that and an LMP cable to do the initial setup, before you can get started with OpenBSC. BR, Csaba