OpenBSC March 2011

openbsc@lists.osmocom.org

20 participants
56 discussions

[Patch] Using MySQL as database for OpenBSC

by Luca Bertoncello

Hi, list! I need to use MySQL as database for OpenBSC due to the limitations of SQLite (I need concurrent access to the database). I wrote a little patch to allow it and I send it as attachment. With this patch the database is **ONLY** MySQL. Maybe in the future, if I'll have time, I'll write another patch to allow the user to choose the preferred database (SQLite3 or MySQL). Regards -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello(a)netzing.de NETZING Solutions AG Tel.: 0351/41381 - 23 Fröbelstr. 57, 01159 Dresden Fax: 0351/41381 - 12 _______________________________________________________________________ Impressum: NETZING Solutions AG - Fröbelstraße 57 - 01159 Dresden Sitz der Gesellschaft Amtsgericht Dresden HRB 18926 Vorstand Dieter Schneider - Aufsichtsratsvorsitzender Volker Kanitz USt.Id DE211326547 Mail: netzing.ag(a)netzing.de

14 years, 3 months

AW: BS-11 multidrop not working

by Andreas.Eversberg

hi, how did you load hfcmulti driver of mISDN? (check misdn_portinfo for layout) how did you configure your bts 1? did you configure TS 17/18/19 instead of TS 1/2/3? andreas -----Ursprüngliche Nachricht----- Von: openbsc-bounces(a)lists.osmocom.org [mailto:openbsc-bounces@lists.osmocom.org] Im Auftrag von Thomas Ansorg Gesendet: Montag, 14. März 2011 16:55 An: openBSC-Mailingliste Betreff: BS-11 multidrop not working hello list, may someone tell me, why my 2 bs-11 refuse to work as multidrop? i start with this config file: ! ! OpenBSC configuration saved from vty ! ! password foo ! line vty no login ! network network country code 262 mobile network code 10 short name Y-Phone long name Yodaphone handover 1 handover window rxlev averaging 10 handover window rxqual averaging 1 handover power budget interval 6 handover power budget hysteresis 4 bts 0 type bs11 band GSM900 cell_identity 1 location_area_code 1 training_sequence_code 7 base_station_id_code 63 oml e1 line 0 timeslot 1 sub-slot full oml e1 tei 25 trx 0 arfcn 121 max_power_red 0 rsl e1 line 0 timeslot 1 sub-slot full rsl e1 tei 1 timeslot 0 phys_chan_config CCCH+SDCCH4 e1 line 0 timeslot 1 sub-slot full timeslot 1 phys_chan_config SDCCH8 e1 line 0 timeslot 2 sub-slot 1 timeslot 2 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 2 timeslot 3 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 3 timeslot 4 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 0 timeslot 5 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 1 timeslot 6 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 2 timeslot 7 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 3 bts 1 type bs11 band GSM900 location_area_code 2 training_sequence_code 7 base_station_id_code 63 oml e1 line 1 timeslot 17 sub-slot full oml e1 tei 25 trx 0 arfcn 1 max_power_red 0 rsl e1 line 1 timeslot 17 sub-slot full rsl e1 tei 2 timeslot 0 phys_chan_config CCCH+SDCCH4 e1 line 1 timeslot 17 sub-slot full timeslot 1 phys_chan_config SDCCH8 e1 line 1 timeslot 18 sub-slot 1 timeslot 2 phys_chan_config TCH/F e1 line 1 timeslot 18 sub-slot 2 timeslot 3 phys_chan_config TCH/F e1 line 1 timeslot 18 sub-slot 3 timeslot 4 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 0 timeslot 5 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 1 timeslot 6 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 2 timeslot 7 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 3 each bs-11 works as single without problems. on both is trx0 activated. bts0 which is connected to pc is in multidrop config, the following bts1 in line config. but only bts0 is bootstrapped. where could the problem(s) be? T. -- Wer Rechtschreibfehler findet, darf sie behalten!

14 years, 3 months

BS-11 multidrop not working

by Thomas Ansorg

hello list, may someone tell me, why my 2 bs-11 refuse to work as multidrop? i start with this config file: ! ! OpenBSC configuration saved from vty ! ! password foo ! line vty no login ! network network country code 262 mobile network code 10 short name Y-Phone long name Yodaphone handover 1 handover window rxlev averaging 10 handover window rxqual averaging 1 handover power budget interval 6 handover power budget hysteresis 4 bts 0 type bs11 band GSM900 cell_identity 1 location_area_code 1 training_sequence_code 7 base_station_id_code 63 oml e1 line 0 timeslot 1 sub-slot full oml e1 tei 25 trx 0 arfcn 121 max_power_red 0 rsl e1 line 0 timeslot 1 sub-slot full rsl e1 tei 1 timeslot 0 phys_chan_config CCCH+SDCCH4 e1 line 0 timeslot 1 sub-slot full timeslot 1 phys_chan_config SDCCH8 e1 line 0 timeslot 2 sub-slot 1 timeslot 2 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 2 timeslot 3 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 3 timeslot 4 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 0 timeslot 5 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 1 timeslot 6 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 2 timeslot 7 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 3 bts 1 type bs11 band GSM900 location_area_code 2 training_sequence_code 7 base_station_id_code 63 oml e1 line 1 timeslot 17 sub-slot full oml e1 tei 25 trx 0 arfcn 1 max_power_red 0 rsl e1 line 1 timeslot 17 sub-slot full rsl e1 tei 2 timeslot 0 phys_chan_config CCCH+SDCCH4 e1 line 1 timeslot 17 sub-slot full timeslot 1 phys_chan_config SDCCH8 e1 line 1 timeslot 18 sub-slot 1 timeslot 2 phys_chan_config TCH/F e1 line 1 timeslot 18 sub-slot 2 timeslot 3 phys_chan_config TCH/F e1 line 1 timeslot 18 sub-slot 3 timeslot 4 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 0 timeslot 5 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 1 timeslot 6 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 2 timeslot 7 phys_chan_config TCH/F e1 line 1 timeslot 19 sub-slot 3 each bs-11 works as single without problems. on both is trx0 activated. bts0 which is connected to pc is in multidrop config, the following bts1 in line config. but only bts0 is bootstrapped. where could the problem(s) be? T. -- Wer Rechtschreibfehler findet, darf sie behalten!

14 years, 3 months

connecting + openBSC initializing problem with nanoBTS 139

by Daniel Brune

Hi there, I'm experiencing a strange problem since a few days - and I already did some resets (with the "dongle") of my nanoBTS 139U DSC1800, running firmware 120a. I cannot connect to the nanoBTS anymore with openBSC. There is an OML-link established quite fast, but then the BTS "disappears" with a socket error. It worked perfectly before, and I did not changed anything in my system so far. When I'm running the ./ipaccess-config 192.168.10.27 (the IP of the nanoBTS) is shows me a lot of information (all fine), but after the last message, the nanoBTS restarts automatically... so connection gets lost and the ipaccess-config program terminates as well. I cannot PING the nanoBTS also after that message. After 30-40s it re-appears of course, same process starts again. ipaccess-find works fine as long as the nanoBTS is in the initializing sequence. Here the content of the message: "<0005> abis_nm.c: 537 0C:BASBAND-TRANSCEIVER(04) INSI=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=835:WARN:OAM_RES:res_trx_status.c#209:TRX is not responding - reinitializing th" Directly after this one, the program terminates with a memory mapping error message back to the console. Any idea? For me it does not sound good... something like a hardware defect - which I really don't want to have now :-/ Best regards from Cologne! Daniel

14 years, 3 months

Re: TRX is not responding error message

by Daniel Brune

Hi Peter! Seems to me that I have the same problem like you with one of my nanoBTS. Did you solved it in anyway? Or real hardware problem? When did it appeared the first time? Daniel

14 years, 3 months

libosmocore lost commit

by Sylvain Munaut

Hi, I think we lost a commit with the 0.1.28 tag SNAFU. Unfortunately all I have left of it is the short log title "vty: Fix a memory leak in the vty description command" So if someone remember writing it, it'd be nice to re-commit it ... Cheers, Sylvain

14 years, 3 months

Re: [PATCH] bsc: change bsc_vty_init to take logging categories as parameter

by Pablo Neira Ayuso

On 09/03/11 13:05, Pablo Neira Ayuso wrote: > From: Pablo Neira Ayuso <pablo(a)gnumonks.org> > > This change is required to finish the integration of the VTY and > the per-application logging categories that provides: > > "vty: integration with logging framework" > > in libosmocore. > > It has been tested with osmo-nitb. The other just compiled tested. Sorry for this dup, I sent this patch with the @netfilter.org account, for that reason the ML blocked it. Then I decided to resend with @gnumonks.org. Both patches are the same.

14 years, 3 months

Re: [PATCH] bsc: vty: fix segfault if rf_ctl is not set

by Holger Hans Peter Freyther

On 03/08/2011 01:35 PM, Pablo Neira Ayuso wrote: > This is the case of osmo-nitb, since it does not call > osmo_bsc_rf_create(). > oh, I thought I create the msc_data conditionally. My bad (will apply your patch).

14 years, 3 months

cannot set static IP adress for a nanoBTS

by Daniel Brune

Hi there, using ipaccess-config -i 192.168.10.110/24 -r 192.168.10.101 is just not working as expected. The device reboots, but still asks the DHCP server for the IP address. Hardware is a nanoBTS 1800 version 139_029_35. By the way, are there known problems with specific firmwares? I'm running 120a002_v200b16d0. Is this a firmware known as working flawless? Best, Daniel

14 years, 3 months

[PATCH] wireshark: gsm-abis-oml: convert C99 structure initialization to ANSI C

by Pablo Neira Ayuso

Hi! This patch applies on top of the wireshark/0001-abis_oml.patch. It converts the C99 structure initialization which is not accepted by the wireshark developers (Harald told me that they need it to compile with non-gcc compilers which don't always support C99). I have tested it here with four pcap files that Harald passed to me. It works fine. BTW, *with* and *without* this patch, wireshark with dissector spots warnings like: 18:14:15 Warn Dissector bug, protocol A-bis OML, in packet 13: packet-gsm_abis_oml.c:940: failed assertion "DISSECTOR_ASSERT_NOT_REACHED" It seems that some TLVs that appear in the body of packets are unknown. I'll debug which are the complaining tags and get back you.

14 years, 3 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2011