OpenBSC September 2010

openbsc@lists.osmocom.org

23 participants
28 discussions

Several questions
by jason mercury 06 Dec '12

06 Dec '12

I have some questions: 1) When I start bsc_hack bsc_init.c first establishes OML link and initializes the bts then it establishes RSL link and bts starts broadcasting. However, it takes so much time to start the bts. Instead of this I want to do the following: it establishes OML link at the beginning and only once, then when i want to start broadcasting it establishes just the RSL link and bts will start faster since i don't have to wait for OML link. What should be done for this? 2) If i send one or two word messages from telnet interface it is okay. But if i send a longer message the phone could't receive the end of the message correctly(last words may be incomplete). Did any one encounter with this problem? What is wrong with me? 3) Could I send SMS in which extension of the sender is text not integer. For example, i want to send an information SMS that this is a test network. For this purpose i want to send an SMS from 'OpenBSC'. I set the extension of the first subscriber in database as text and tried to send the SMS but SMS wasn't delivered. What should i do? 4) Can i add SMS externally to SMS table of database? Thanks. Jason

4 3

New utility for drawing protocol ladder diagrams
by Harald Welte 21 Feb '11

21 Feb '11

Hi! With the help of graphviz, I have written a small perl-based tool that allows you to generate ladder diagrams. It can be found at git://git.osmocom.org/gen_ladder.git For your reference, I'm attaching a sample input and output file. The bent/curved arrows are a result of graphviz trying to indicate that the message is between e.g. MS and MSC and 'bypasses' BTS and BSC. I'm still waiting for somebody with more graphviz skills to make this an option. Hope this is useful for some of you... -- - 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)

2 1

Proposed OpenBSC application interface
by Harald Welte 16 Feb '11

16 Feb '11

Hi! Collin Mulliner, Tobias Engel and myself have been meeting yesterday to discuss a generic application interface for OpenBSC. They are both doing security analysis and want to achieve a clean way how an external application can get access to a more or less transparent communication channel to the phone. The purpose of this is to be able to send intentionally malformed packets to the mobile phone GSM stack at various different levels within the stack. As of now, they have both hacked some custom code into openbsc that gets them half way where they want to be - but not quite all the way. The requirements can be summarized as follows: 1) Ability to establish a SDCCH or TCH channel by paging the phone As of now, the 'silent call' feature from the VTY already does this. 2) Ability to send arbitrary layer3 protocol messages to the phone Adding this is relatively easy (use rsl_sendmsg on the lchan from the silent call) 3) Ability to receive responses from the phone, as well as error conditions such as 'readio link failure'. We don't have a solution for this yet, and we also have no clean way to identify what might be a response from the phone to the external app, and what might be a message from the phone to the normal network code in OpenBSC 4) Ability to selectively disable partial protocol handling in OpenBSC. Let's say you want to play with the mobile phone call control implementation. In this case, you want to make sure all CC related messages go from/to the external program and not from the regular OpenBSC network code. So what I've been thinking of as a solution to the problem: * store a bypass_flags bitmask related to the subscriber structure, where we indicate values such as BYPASS_RR, BYPASS_MM, BYPASS_CC, BYPASS_SAPI3. * if we process an incoming message from the MS in gsm0408_rcvmsg(), we check if a bypass flag matching the message is found. If yes, forward the message to the external program * if we want to send a message from our own protocol stack to the MS, we check if a bypass flag matching the message is found. If yes, we drop the message that we were about to send. * any messages received from the application will be forwarded to the MS The application interface protocol will likely have a close resemblance to RSL RLL. We need to exchange the following primitives with the application, like: * ESTABLISH REQUEST -- app requests a channel be established to MS (by IMSI) * ESTABLISH CONFIRM -- network confirms a channel has been established * ESTABLISH INDICATION -- network tells app connection was made by MS * [UNIT] DATA REQUEST -- app requests data to be sent to MS * [UNIT] DATA INDICATION -- network indicates data was received from MS * ERROR INDICATION -- network tells app something went wrong * RELEASE REQUEST -- app asks network to release channel * RELEASE CONFIRM -- net tells app that channel was released (as rqd) * RELEASE INDICATION -- net tells app that channel was released (by MS) The channel_number of RSL (indicating on-air timeslot) doesn't make much sense in this context, of course. The link_identifier on the other hand is great as it allows the app to indicate SDCCH/FACCH or SACCH as well as the SAPI. The actual RSL-like protocol would be encapsulated by UDP and available on a socket of the MSC. What do you think? 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 9

RFC: Relicensing OpenBSC under AGPLv3
by Harald Welte 02 Jan '11

02 Jan '11

Hi all! This subject came to my attention again recently: Why not relicense OpenBSC under AGPLv3? Right now we are licensing under GPLv2+ (v2 or any later version). However, if an operator was to make lots of private modifications and then operate it on his own network, there would be no distribution and thus no need for him to release his modified versions of the source code. This may sound a bit strange to those who have been with the project since its early days. But we are reaching production quality now, and we already have the first number of production deployments of the software. Companies like Netzing and On-waves have been FOSS-friendly and funding parts of our development effort. They have no issues with the result being Free Software again. However, there are definitely other companies out there who are less fond of sharing... So thus my idea is to put OpenBSC under AGPLv3. This way whoever uses OpenBSC _in modified form_ to operate a communications network will have to provide the source code to that modified form on a network server at no charge. The only controversial question to me is "your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source". 1) does a gsm network count as computer network? i'd say yes. 2) is using a gsm network 'interacting with it remotely'? I'd also say yes 3) what does 'prominently offer' mean in the context of GSM? We don't want the operator to spam their users with advertisement SMS just to know that they can get the soruce code, after all. Notwithstanding those open questions, such a network operator would always have the option of simply sending back his changes for integration in the official project - and thus he would no longer use a modified version which then means there is no need for the prominent notice / download at all. We can make this very clear in the project documentation, putting further encouragement The actual relicensing should be less problematic than I thought, since AGPLv3 is compatible with GPLv3. So I could re-license all parts that I own copyright on (which should be the majority of the code base anyway) under AGPLv3, while the former GPLv2+ components (like VTY code from zebra, or contributions by other people) then become GPLv3-or-later. Of course I would want to encourage all developers/contributors to also follow the re-licensing. Particularly Holger Freyther, Dieter Spaar, Andreas Eversberg, Jan Luebbe, Sylvain Munaut, Daniel Willmann, Stefan Schmidt. So let's start with a poll: a) Do you think re-licensing to AGPLv3 is a good idea? b) If you have contributed, would you re-license your code under AGPLv3? If we have some kind of concesus in the community, I would approach On-waves whether they would want to do the same for their share of the copyright. As their "modifications" are all part of OpenBSC git repository, they would not be subject to any different conditions than before. Thanks in advance for your feedback, 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 5

Reply:- Need help on Open BSC code.
by tejas oza 15 Dec '10

15 Dec '10

Hi Holger, After trying to checkout and build the OpenBSC using command git checkout -b on-waves/bsc-master origin/bsc-master, we got error as fatal: git checkout: updating paths is incompatible with switching branches. Did you intend to checkout 'origin/bsc-master' which can not be resolved as commit? So, may be we are not correct on the path or something else. can you please advice, as we are not able to find bsc_msc_ip binary file. On Thu, Sep 30, 2010 at 9:50 AM, Holger Hans Peter Freyther < holger(a)freyther.de> wrote: > On 09/30/2010 03:04 PM, tejas oza wrote: > > Hi Guys, > > > > We are implementing the separate MSC module and we will be using the > openBSC, > > and we are mainly concerned for SMS services. So, I will be highly > obliged if > > you can provide us the documentation on openBSC code so that we can > understand > > the messages expected on separate MSC side from open BSC and the messages > to > > be sent from MSC to openBSC side. > > In the on-waves/bsc-master branch you will find a bsc_msc_ip binary that > will > be able to connect to a real MSC through somthing that is coined SCCP-Lite > (SCCP encapsulated inside the ipaccess protocol). > > If you look at bsc_hack it has no connection to anything but the BTS, so > the > BSC/MSC/VLR/HLR functionality is implemented in one binary. > > -- Thanks & Regards Tejas Oza -- Thanks & Regards Tejas Oza

4 29

[PATCH 0/1] Add bport0/1 support for bs11_config
by Daniel Willmann 14 Dec '10

14 Dec '10

Hello, second try to add support to bs11_config for bport0/1 configuration. This time with enum abis_bs11_line_cfg. It seems sometimes creating bport1 fails, even LMT shows create obj greyed out. Don't know why yet. Regards, Daniel Willmann Daniel Willmann (1): Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config openbsc/include/openbsc/abis_nm.h | 10 +++++++++- openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++-- openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++ 3 files changed, 64 insertions(+), 3 deletions(-)

4 5

Need help on Open BSC code.
by tejas oza 30 Sep '10

30 Sep '10

Hi Guys, We are implementing the separate MSC module and we will be using the openBSC, and we are mainly concerned for SMS services. So, I will be highly obliged if you can provide us the documentation on openBSC code so that we can understand the messages expected on separate MSC side from open BSC and the messages to be sent from MSC to openBSC side. -- Thanks & Regards Tejas Oza

2 1

Re: Features with nano BTS..
by Ravi Shankar 24 Sep '10

24 Sep '10

Dear sir, I am planning to buy a ip.access nano BTS to run at GSM900. What features should I quote as specification while placing the order ?? whether it (OpenBSC) will work properly with GSM900 or should I go for DCS1800 ???? Thanks.

3 2

ip.access beginner question
by Maggie Balsamic 22 Sep '10

22 Sep '10

Hi all, I've got a PCS 1900 version of the ip.access BTS that I'm trying to get working with openbsc. I'm able to connect to the ip.access using bsc_hack, but I'm not sure what my next step should be. I made basic changes to the included bsc_hack ip.access config file, but I'm guessing that I'm missing something basic. Not sure if this matters, but one oddity I've found as I follow the instructions on the wiki is that ipaccess_config did not properly set the primary-oml IP. However, I was able to get the debug telnet client working, and set the oml IP directly from the ip.access debug shell. What I'm looking for right now is what I need to do to get bsc_hack to show a phone attempting to authenticate, etc. I'm wondering if it could have something to do with the channel config at the end, since I don't know how to set that. I've included my current bsc_hack config and the debug logging from bsc_hack. Any help would be much appreciated! Thanks ========BSC_HACK OUTPUT: <0005> bsc_init.c:1123 WARNING: You are running an 'accept-all' network on a BTS that is not barred. This configuration is likely to interfere with production GSM networks and should only be used in a RF shielded environment such as a faraday cage! <0005> bsc_init.c:738 bootstrapping OML for BTS 0 <0005> abis_nm.c:518 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,01,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:518 OC=SITE-MANAGER(00) INST=(ff,ff,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Sending OPSTART <0005> abis_nm.c:518 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Software Activated Report <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=GPRS-NSE(f0) INST=(00,ff,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1795 Set BTS Attr (bts=0) <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) Sending OPSTART <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 31 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 42 12 00 08 31 36 38 61 33 30 31 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 31 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 42 12 00 08 31 36 38 61 33 30 31 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:518 OC=GPRS-NSE(f0) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:518 OC=GPRS-CELL(f1) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,01,ff) SW Activate Request: <0005> abis_nm.c:879 Software Activate Request, ACKing and Activating <0005> abis_nm.c:894 Found SW config: 42 12 00 08 31 36 38 61 33 30 32 00 13 00 0a 76 31 34 32 62 31 33 64 30 00 <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:2878 ip.access RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=0) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=1) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=2) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=3) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=4) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=5) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=6) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=7) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) Software Activated Report <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:1812 Set TRX Attr (bts=0,trx=0) <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:518 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:518 OC=GPRS-CELL(f1) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,01,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=GPRS-NSVC(f2) INST=(00,01,ff) Software Activated Report <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) IPACCESS(0xe1): RSL CONNECT ACK IP=10.1.6.35 PORT=3003 STREAM=0x00 <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=OK(ff) ADM=Unlocked <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0004> bsc_init.c:1019 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 514 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7 <0003> bsc_init.c:798 SI1: 55 06 19 8f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e5 04 00 2b <0003> bsc_init.c:798 SI2: 59 06 1a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff e5 04 00 <0003> bsc_init.c:798 SI3: 49 06 1b 00 00 00 f1 10 00 01 41 03 00 27 47 40 e5 04 00 3b 2b 2b 2b <0003> bsc_init.c:798 SI4: 31 06 1c 00 f1 10 00 01 47 40 e5 04 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b <0003> bsc_init.c:798 SI5: 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b <0003> bsc_init.c:798 SI6: 2d 06 1e 00 00 00 f1 10 00 01 27 ff 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b ========BSC_HACK CONFIG: ! ! OpenBSC configuration saved from vty ! ! password foo ! line vty no login ! network network country code 1 mobile network code 1 short name OpenBSC long name OpenBSC ! auth policy closed auth policy accept-all location updating reject cause 13 encryption a5 0 neci 1 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 0 timer t3107 0 timer t3109 0 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3141 0 bts 0 type nanobts band PCS1900 cell_identity 0 location_area_code 1 training_sequence_code 7 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1801 0 oml ip.access stream_id 255 gprs mode none trx 0 rf_locked 0 arfcn 514 nominal power 23 max_power_red 20 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 timeslot 2 phys_chan_config TCH/F timeslot 3 phys_chan_config TCH/F timeslot 4 phys_chan_config TCH/F timeslot 5 phys_chan_config TCH/F timeslot 6 phys_chan_config TCH/F timeslot 7 phys_chan_config TCH/F

2 2

nanoBTS question
by Albert Paijmans 22 Sep '10

22 Sep '10

Hi, I have been looking around and I am wondering, when you are interested in a consumer 3G / Femto or Pico cell it might be very cheap through AT&T at around $150. Might somebody be working rverse engineering on those cheaper cells? The nanoBTS from ipaccess is costing euro 3450 Mind you this is without any software or server, just a single nanoBTS unit. Does anybody have any experience and info about pricing? I find this price crazy but it is the only way in the Netherland to buy it officially. Also I have a license for GSM frequencies ad for that price they only send it to an address. Thanks Albert

3 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC September 2010