OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Re: Issues on initial setup with BS-11
by Dieter Spaar 06 Dec '09

06 Dec '09

Hello Paul, On Wed, 02 Dec 2009 22:36:53 +0000, s4dd(a)losers.yore.ma wrote: > Any help you guys could give is much appreciated! I think the problem is the "Invalid Channel Combination!!!" error message. Try to change "phys_chan_config" of timeslot 1 from "SDCCH8" to "TCH/F". From my understanding of verify_chan_comb() "SDCCH8" is not allowed on the same TRX that already has "CCCH+SDCCH4" so I wonder why it is set in the config file (this only applies to the BS11). Sorry, I don't have a ready BS11 configuration at hand right now, so I can't test it. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

6 10

Issues on initial setup with BS-11
by s4dd＠losers.yore.ma 06 Dec '09

06 Dec '09

Hello all, I seem to have fallen at the last hurdle to achieving my first milestone - being able to see an available network from our BS-11/OpenBSC combi on a variety of MEs. Fingers crossed it's something trivial that has been overlooked. I've included some output from bs11_config and bsc_hack below in the hope that someone may spot the issue. Output from bs11_config during bootup: PHASE: 1 Load SMU Intended Abis-link: Down PHASE: 1 Load SMU Intended Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: No Load MBCCU1: No Load Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSCAC MBCCU1: No Load Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSCAC MBCCU1: Load BTSCAC Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSDRX MBCCU1: Load BTSCAC Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSDRX MBCCU1: Load BTSDRX Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSBBX MBCCU1: Load BTSDRX Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSBBX MBCCU1: Load BTSBBX Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSBBX MBCCU1: Load BTSBBX Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSARC MBCCU1: Load BTSBBX Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load BTSARC MBCCU1: Load BTSARC Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load MBCCU1: Load BTSARC Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load MBCCU1: Load BTSARC Abis-link: Down PHASE: 2 Load MBCCU MBCCU0: Load MBCCU1: Load Abis-link: Down PHASE: 3 Normal MBCCU0: Load MBCCU1: Load Abis-link: Restoring BS11 ATTRIBUTES: SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=1 (Full Slot) TEI: 25 BS11 Line Interface ATTRIBUTES: PLL Mode: E1 Locked BS11 CCLK ATTRIBUTES: BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW (GSM) LMT LOGOFF: ACK ************************************************************ Output from bs11_config with query: LMT LOGON: ACK PHASE: 3 Normal MBCCU0: Load MBCCU1: Load Abis-link: Up BS11 ATTRIBUTES: SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=1 (Full Slot) TEI: 25 BS11 Line Interface ATTRIBUTES: PLL Mode: Standalone BS11 CCLK ATTRIBUTES: BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW (GSM) LMT LOGOFF: ACK ************************************************************ bsc_hack startup: DB: Database initialized. DB: Database prepared. e1_reconfig_bts(0) e1_reconfig_ts(0,0,0) e1_reconfig_ts(0,0,1) e1_reconfig_ts(0,0,2) e1_reconfig_ts(0,0,3) e1_reconfig_ts(0,0,4) e1_reconfig_ts(0,0,5) e1_reconfig_ts(0,0,6) e1_reconfig_ts(0,0,7) 1 device found id: 0 Dprotocols: 00000018 Bprotocols: 0000000e protocol: 4 nrbchan: 30 name: hfc-e1.1 activate bchan activate bchan bootstrapping OML for BTS 0 <0020> abis_nm.c:1724 Set BTS Attr (bts=0) <0020> abis_nm.c:1741 Set TRX Attr (bts=0,trx=0) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=0) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=1) <0020> abis_nm.c:1824 Invalid Channel Combination!!! <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=2) <0020> abis_nm.c:1704 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=2) E1=(0,2,2) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=3) <0020> abis_nm.c:1704 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=3) E1=(0,2,3) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=4) <0020> abis_nm.c:1704 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=4) E1=(0,3,0) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=5) <0020> abis_nm.c:1704 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=5) E1=(0,3,1) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=6) <0020> abis_nm.c:1704 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=6) E1=(0,3,2) <0020> abis_nm.c:1821 Set Chan Attr (bts=0,trx=0,ts=7) <0020> abis_nm.c:1704 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=7) E1=(0,3,3) bootstrapping RSL for BTS/TRX (0/0) using MCC=1 MNC=1 BSIC=63 TSC=7 <0020> abis_nm.c:606 OC=RACK(a4) INST=(00,ff,ff) STATE CHG: OP_STATE=Enabled <0020> abis_nm.c:985 LMT Event LOGON Level=2 Username=FACTORY <0020> abis_nm.c:985 LMT Event LOGOFF Level=2 Username=FACTORY ************************************************************ bsc_hack config used was the vanilla cfg included with the source (openbsc.cfg.1-1). Any help you guys could give is much appreciated! Regards, Paul

2 3

Re: Issues on initial setup with BS-11
by Dieter Spaar 03 Dec '09

03 Dec '09

Hello David, On Thu, 3 Dec 2009 01:07:56 -0800, "David A. Burgess" <dburgess(a)jcis.net> wrote: > > I don't know if that's valid by the spec or not, but it's part of a > pretty standard configuration in IMSI-catchers: CCCH+SDCCH4 + > 6*SDCCH8 + TCH/F. That maximizes location updating capacity and > leaves one TCH/F for other ... mischief. Most of those IMSI-catchers > are based on commercial mini/nano-BTS equipment. Thanks for this input. I think this a limitation of the BS11 only, I have read that there are some limitations related to the SDCCH/8 of the BS11: - only one SDCCH/8 per TRX - not allowed together with SDCCH/4 on BCCH-TRX Maybe the BS11 does not have enough processing power to handle it ? Of course it could be that the documentation is wrong and it would work, I have not yet tried it. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

system_information branch updates
by Harald Welte 02 Dec '09

02 Dec '09

Hi! While enroute to FOSS.in in Bangalore, I took the time to test and debug the various issues I could find with the code in the system_information branch. At least in all of my tests, the system information messages, including rest octets and neighbor cell lists are looking perfectly fine. Especially now that with my latest patch, wireshark is able to dissect the SI messages properly, it is much easier to debug :) If you want to give it a try, I recommend using something like git revision 63b152ebb74355acfde76e9ce1113f2d823c0804 of that branch. Please note: We currently only support the relative bitmask format for the neighbor cell lists. That means, you cannot have neighbors with ARFCN's spanning a range of more than 111, i.e. your lowest and highest ARFCN have to be within a distance of 111 ARFCN's. Unless there are major objections, I intend to merge this branch ASAP (or rather do a 'git diff master..system_information' and apply the resulting diff as one commit to master) Regards, Harald -- - 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)

1 1

Howto collect MSISDN numbers
by Mohammad Halawah 30 Nov '09

30 Nov '09

Dear openBSC users, This project sounds interesting and promising. I would like to collect MSISDN (mobile numbers) for people attending a fundraising gallery. Then I send them SMS (using the MSISDN list I made) with 5 bucks donation link. Of course I can run with a pen and paper and do that, but instead I would like to use technology to help me. Is this possible to do with openBSC? Or even other GNURadio modules? I am not interested in: using openBSC to make/receive phone calls nor IMSI and TMSI. Bands of interest are: 900/1800 GSM 2100 UMTS In case this is not possible using GNU Radio modules. Is there commercial solutions to do that? Peace, Mohammad Halawah Project Engineer JETZT REGISTRIEREN: Vierteljährlicher Newsletter über die Welt der mobilen Lösungen! http://www.smartmachine.net/newsletter.html <http://www.smartmachine.net/newsletter.html> REGISTER NOW: Quarterly newsletter about the world of mobile solutions! http://www.smartmachine.net/en/newsletter.html <http://www.smartmachine.net/en/newsletter.html> smartmachine Forschung & Entwicklung GmbH Sterneckstraße 33 5020 Salzburg Austria O: + 43 662 880440-52 F: + 43 662 880440-99 M: + 43 664 1101 206 E: mohammad.halawah(a)smartmachine.net <mailto:martin.leitner@smartmachine.net>

1 0

OpenBSC, 16-in-1 SIM and COMP128v1 authentication
by Harald Welte 28 Nov '09

28 Nov '09

Hi! Today I spent some time investigating the cheap 16-in-1 SIM cards on which we can set our own Ki. This means that those cards can be used for cryptographic authentication with OpenBSC. Finally, we will have not only IMSI-based identification, but actual authentication! I've created a page in the Wiki about those cards: http://openbsc.gnumonks.org/trac/wiki/MagicSIM Using this information, I could send the RUN GSM ALGORITHM APDU to the card and retreive SRES + Kc. The result matched what I can also obtain using the COMP128v1 code from http://www.scard.org/gsm/a3a8.txt I will add Comp128v1 support to OpenBSC as soon as I have tested acutal authentication using this 16-in-1 SIM card. By the way: It would really be great if somebody could hack up a small command line program that can be used to program the Operator Name, Ki, ICCID, IMSI and preferred PLMN into the 16-in-1 SIM. Regards, Harald -- - 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)

3 3

Wireshark: Decoding of System Information on BCCH
by Harald Welte 26 Nov '09

26 Nov '09

Hi! As Dieter has noticed, GSM traces from gammu / nokia DCT3 phones show the complete SYS INFO decode inside wireshark. However, the RSL messages BCCH INFORMATION do not decode it. I've revolved this problem and submitted a patch to the wireshark team, you can get it from https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4268 Please note: This patch does not yet address the problem for the SI5/SI6 in SACCH FILLING. The solution is not as easy, since in this case a generic L3 IE is handed of to the GSM_A_DTAP rather than GSM_A_CCCH dissector. If anyone wants to help out with fixing this for the SACCH, I'm sure many OpenBSC users and wireshark guys will be happy to receive a patch/fix. Regards, Harald -- - 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)

1 0

ARFCN 123 / System Information Type 1
by Harald Welte 26 Nov '09

26 Nov '09

Hi All! While looking at a wireshark trace (with the newly discovered wireshark system information dissector, for which I'll submit a patch to wireshark later tonight), I just realized that in SI1 we still shend a Cell Allocation of a hardcoded ARFCN 123. So unless you run in GSM900 and you use ARFCN 123, the SI1 content will disagree with the actual radio carrier. This is likely to cause confusion with at least some phones. We already have code to generate the channel lists inside SI messages, but this code is so far not used in the master branch. So this is just a reminder "There is a known Issue". If you want to experiment with a supposed fix for it, try using the system_information branch. Regards, Harald -- - 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)

1 0

nanoBTS 139 for sale
by WoMax 25 Nov '09

25 Nov '09

Sorry for this posting, but due a timewaster from berlin the last nanoBTS type 139 is for sale again. It is a siemens branded (MOGIS) nanoBTS type 139, pictures you can see on http://umts.zerber.us It is my last one, there is no PoE included, so the special price is 1900 euro plus shipping. I am currently not in switzerland, I try to get some TETRA equipment, so the shipment will be in the second week of december. Payment to my bank account or PayPal. I sold already a lot of this nanoBTS to members from the openBSC-Group for a good price, thank you to all of you.

1 0

Re: Fail messages while applying patch
by ನಾಗೇಶ್ 25 Nov '09

25 Nov '09

Thank you, Rohit for the link. N. On Mon, 2009-11-23 at 09:04 +0530, Rohit Joshi wrote: > It suggest patch found conflict in code. Read this to get started on > handling patch rejects http://elinux.org/Handling_Patch_Rejects > > > 2009/11/23 ನಾಗೇಶ್ <openbscuser(a)gmail.com>: > > Hi, > > When applying patch (as described in Debian_Getting_Started page), I get > > messages as shown in screenshot. What do these mean ? > > > > N. > > > > >

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC