OpenBSC

openbsc@lists.osmocom.org

10 participants
4277 discussions

multi drop config - almost done
by Thomas Ansorg 18 Dec '10

18 Dec '10

hello after compiling the new software, bs11_config tells me for bts1 (the working one): bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY LMT LOGON: ACK PHASE: 3 Normal MBCCU0: Load MBCCU1: No Load Abis-link: Restoring BS11 ATTRIBUTES: BS-11 ESN PCB Serial Number: 001104 BS-11 ESN Hardware Code Number: 135-2044/03.07 BS-11 ESN Firmware Code Number: 135-2044/03.07 PLL Set Value=1006, Work Value=1038 SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=1 (Full Slot) TEI: 25 BS11 Line Interface ATTRIBUTES: PLL Mode: Standalone BS11 CCLK ATTRIBUTES: CCLK Accuracy: High (1) CCLK Type=0 BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW (GSM) BPORT0 ATTRIBUTES: Line Configuration: Multi-Drop (1) BPORT1 ATTRIBUTES: Line Configuration: Multi-Drop (1) LMT LOGOFF: ACK *************************************************************************** i set the bport multi thing on my own the 2nd bts said this: bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY LMT LOGON: ACK PHASE: 3 Normal MBCCU0: Load MBCCU1: No Load Abis-link: Restoring BS11 ATTRIBUTES: BS-11 ESN PCB Serial Number: 001112 BS-11 ESN Hardware Code Number: 135-2044/03.03 BS-11 ESN Firmware Code Number: 135-2044/03.03 PLL Set Value=1073, Work Value=1073 SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=6 (Full Slot) TEI: 26 BS11 Line Interface ATTRIBUTES: PLL Mode: Standalone BS11 CCLK ATTRIBUTES: CCLK Accuracy: High (1) CCLK Type=0 BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW (GSM) BPORT0 ATTRIBUTES: Line Configuration: Multi-Drop (1) BPORT1 GET ATTR NACK LMT LOGOFF: ACK ***************************************************************************** as you can see, i set the port to 0 on both, bts1 works on ts1, tei 25 and bts2 on ts6, tei 26. does this configuration match with the attached config-file? unfortunately i couldnt test it thoroghly today, it was late :-( there is a strange errormessage at the end of bts2 report, a possible problem? anyway, i wasnt able to create a bport, neither in connected nor disconnected mode T. -- Wer Rechtschreibfehler findet, darf sie behalten!

2 1

Re: 3G (NodeB / femtocell) roadmap
by Joe Eggleston 18 Dec '10

18 Dec '10

On Thu, Dec 16, 2010 at 5:33 AM, Sylvain Munaut <246tnt(a)gmail.com> wrote: > But each time you have to search for whatever name the operator has > for it (like "Home 3G" for SFR, or "Sure Signal" for Vodafone, ...) > In case this is helpful to anyone else, I stumbled on this page that has a pretty good list of the providers using the various femtocells: http://www.thinkfemtocell.com/Examples/where-can-i-buy-a-femtocell.html

1 0

TRX is not responding error message
by Peter Hasse 18 Dec '10

18 Dec '10

Hi One of our nanoBTSs startet to reboot very frequently. The debug telnet console shows this error: 12168:WARN:OAM_RES:res_trx_status.c#231:TRX is not responding - reinitialising the unit... 13251:DBG:OAM_IM:Stopping "Primary OML Fallback Client" > 13251:DBG:OAM_IM:Stopping "Secondary OML Server" > 13251:DBG:OAM_IM:Stopping "Secure Secondary OML Server" 13252:DBG:OAM_IM:Not stopping "IML Site Server" - has not been started 13252:DBG:OAM_IM:Not stopping "Secure IML Site Server" - has not been started 13252:DBG:OAM_IM:Stopping "IML Bts Server" > 13252:DBG:OAM_IM:Stopping "Secure IML Bts Server" 13252:DBG:OAM_IM:Stopping "IRL Patched Routing Link" 13252:DBG:OAM_IM:Failed to inject event=1="STOP" into link source (token=9) 13284:DBG:IP_CHAN_SERVER:Closed server listening on port 3006 > 13284:DBG:IP_CHAN_SERVER:Closed server listening on port 3026> 13285:DBG:IP_CHAN_SERVER:Closed server listening on port 3014> 13285:DBG:IP_CHAN_SERVER:Closed server listening on port 3034> 13458:DBG:IP_CHAN_RX_A:15190:ipChanConn: EVENT 0x00001743 rxd in STATE connected 13458:DBG:IP_CHAN_RX_A:15191:ipChanConn: EVENT 0x00001741 rxd in STATE disconnectclosing here is the output of openBSC <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=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) IPACCESS(0xe1): RSL CONNECT ACK IP=192.168.0.1 PORT=3003 STREAM=0x00 <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=CHANNEL(03) INST=(00,00,00) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure Another nanoBTS with same firmware and config works perfekt with the same openBTS installation. Switching to the second firmware bank and flashing a different firmware didnt solve the problem. Any hint where to look for more information ? mfg Peter

2 3

Problem in the communication with a real MSC
by Luca Bertoncello 17 Dec '10

17 Dec '10

Hi, List! I'm trying to connect OpenBSC with a real MSC. Unfortunately I have many problems. The first is, that every minute or so, I got these errors: <000f> bsc_msc_ip.c:1047 The connection to the MSC was lost. <000f> bsc_msc_ip.c:976 Lost MSC connection. Freing stuff. <000f> bsc_msc.c:236 Attempting to reconnect to the MSC. <000f> bsc_msc.c:230 Attempting to reconnect to the MSC. <000f> bsc_msc.c:137 Attempting to connect MSC at 192.168.2.103:5000 <000f> bsc_msc.c:170 MSC Connection in progress <000f> bsc_msc.c:99 (Re)Connected to the MSC. <000f> bssap.c:92 Reset ACK from MSC I think, it is not normal, that the communication with the MSC was lost. Both of them (OpenBSC and MSC) are on the same Gigabit network, so there is no connection problem... Any idea? Another problem: I get very oft the error: <0000> chan_alloc.c:441 (bts=1,trx=0,ts=0,ss=0) Recycling Channel. Any idea? Thanks a lot! -- _______________________________________________________________________ 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

3 3

3G (NodeB / femtocell) roadmap
by Harald Welte 16 Dec '10

16 Dec '10

Hi all, i just wanted to keep you posted with the 2011 roadmap for 3G integration into our "Free Software Mobile Network" stack. This message summarizes the plan of what I expect to be working on. Comments welcome. 3G support directly in OpenBSC is, however, a bit more difficult than we originally anticipated. The primary problems are: * 3G and 2G share the same core network (CN = MSC/VLR/HLR/AuC/SGSN/GGSN) but have different radio access netowrk (RAN = BTS+BSC vs. NodeB+RNC) * the interface between RAN and CN is different, i.e. 'A' interface (08.08) in GSM case, RANAP in 3G case. * The encoding of the two protocols could not be any different. Hand-coded vs. complex ASN.1 structures So with OpenBSC, we face the following challenges: 1) We implement the GSM-RAN functionality and the CN in one process, without any separation or standardized interfaces between them 2) Implementing RANAP in C can be done, but is probably quite cumbersome given the tons of code asn1c generates and how difficult it seems to get all the memory allocation/freeing right in all the cases What we instead decided to do is: a) Split the BSC part from the CN by implementing the A interface (this is already finished, we now have osmo-bsc to do exactly that) b) Implement a new MSC part, using the A interface towards the BSC This is still possible using our existing code in the original OpenBSC, though we have not completed/finished it yet. The real goal is to have a new MSC, written in a higher-order language that provides proper tools for working with ASN.1 - e.g. Erlang. I have just started working on this and am more or less finished with the lower layers like SCCP and am moving into 08.08 and the actual layer3 protocols. There is already some initial funding secured for the first months of this work, and funding will likely continue. c) Once the 2G functionality of the Erlang MSC is working, add the RANAP interface to it. At this point we should more or less be able to directly connect the Alcatel-Lucent femtocells, as they basically consist of HomeNodeB plus an internal RNC handling the RRC protocol. d) Adding support for ip.access/Cisco/AT&T will need an implementation of their URSL protocol, which is proprietary. URSL can either be added to the new MSC directly, or a URSL<->RANAP translater be developed. e) Adding support for the Ubiquisys/SFR femtocell would require us to implement the UMA protocol stack. This can once again be either done as part of the MSC or using an external translator/gateway program. 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)

4 7

problems installing openbsc
by Thomas Ansorg 16 Dec '10

16 Dec '10

hello all 2day i decided to install openbsc completely neu (had some trouble with the bs11_config), according to the website. libosmocore went thru without problems, openbsc came to the ./configure when the problem occured. the error was: ./configure: line 3673: syntax error near unexpected token `LIBOSMOSCCP,' ./configure: line 3673: ` PKG_CHECK_MODULES(LIBOSMOSCCP, libosmo-sccp >= 0.0.2)' of course i looked at line 3673, but i'm a linux newbie, so i didnt really understand. in the /usr/local/lib/pkgconfig are 3 files: libosmocodec.pc: prefix=/usr/local exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: Osmocom Codec related utilities Library Description: C Utility Library Version: 0.1.27.16-ab12 Libs: -L${libdir} -losmocodec Cflags: -I${includedir}/ libosmocore.pc: prefix=/usr/local exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: Osmocom Core Library Description: C Utility Library Version: 0.1.27.16-ab12 Libs: -L${libdir} -losmocore Cflags: -I${includedir}/ and libosmovty.pc: prefix=/usr/local exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: Osmocom VTY Interface Library Description: C Utility Library Version: 0.1.27.16-ab12 Libs: -L${libdir} -losmovty Cflags: -I${includedir}/ up to the configure call, everything worked fine, libosmocore was complete installed. a makefile wasnt created -> bad! what went wrong? T. -- Wer Rechtschreibfehler findet, darf sie behalten!

2 1

problems with 2nd bs11| verbose mode
by Thomas Ansorg 15 Dec '10

15 Dec '10

hi to enable as many as possible of you to help me, heres what bs11_config said (the old version): bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY LMT LOGON: ACK PHASE: 3 Normal MBCCU0: Load MBCCU1: Load Abis-link: Restoring BS11 ATTRIBUTES: BS-11 ESN PCB Serial Number: BS-11 ESN Hardware Code Number: BS-11 ESN Firmware Code Number: PLL Set Value=1006, Work Value=1038 SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=1 (Full Slot) TEI: 25 BS11 Line Interface ATTRIBUTES: PLL Mode: Standalone BS11 CCLK ATTRIBUTES: CCLK Accuracy: Medium (0) BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW LMT LOGOFF: ACK thats the working one, the non-working says exactly the same, except pll(1073) and work(1073) the abis link on the 2nd is also up, but handys dont find it. the intension ist a multi drop config, but before that, the 2 bs11 should work on its own, right? T. -- Wer Rechtschreibfehler findet, darf sie behalten!

2 1

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

multi drop still don't work
by Thomas Ansorg 14 Dec '10

14 Dec '10

hello i set one bs11 to ts 1, tei 25 and the other one to ts 6, tei 25(also tried 26 with the 2nd), according to openbsc.cfg.2-2. the cabling is also correct, due to a schematic from harald. but the 2nd bs11 not recognised. the funny thing ist, when i configure the 2nd bs11 exactly like the 1st one(the working one, ts 1, tei 25), it don't work. the parameter from bs11_config query are the same like the 1st, but i don't get the abis link up -- Wer Rechtschreibfehler findet, darf sie behalten!

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC