OpenBSC April 2018

openbsc@lists.osmocom.org

15 participants
29 discussions

Save the Date: OsmoCon 2018 on October 18-19, 2018
by Harald Welte 19 Oct '18

19 Oct '18

== OsmoCon 2018 == OsmoCon (Osmocom Conference) 2018 is the technical conference for Osmocom users, operators and developers! We are happy to announce the date of OsmoCon 2018. It has been scheduled on October 18 + 19, 2018 and will happen in Berlin, Germany. For the second time, the Osmocom Conference brings together users, operators and developers of the Osmocom Open Source cellular infrastructure projects, such as OsmoBTS, OsmoBSC, OsmoSGSN, OpenGGSN and others. Join us for two days of presentations and discussions with the main developers behind Open Source Mobile Communications, as well as commercial and non-profit users of the Osmocom cellular infrastructure software. You can find some initial information in our wiki at http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018 which will be updated as more information becomes available. == Call for Participation == We're also at the same time announcing the Call for Participation and call on everyone with experiences to share around the Osmocom member projects to submit talks, workshops, discussions or other proposals. You can find the CfP at https://pretalx.sysmocom.de/osmocon2018/cfp We are particularly looking for contributions about: * updates on features/functionality/status of individual Osmocom projects * success stories on how Osmocom projects are deployed in practice * migration from OsmoNITB to the post-NITB architecture * tutorials / workshops on how to setup / analyze Osmocom projects * statistics, reporting, operations aspects of Osmocom projects * third-party open source utilities to be used with Osmocom projects Looking forward to meeting many existing and new Osmocom users at OsmCon this October! Regards, Harald Welte -- - 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 4

nanoBTS constantly restarting
by Michael Spahn 01 Jun '18

01 Jun '18

Hello all, I have recently tried migrating an OsmoNITB setup to the new standard using mostly this guide right here: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I… <https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…> However, while my nanoBTS works perfectly fine in the old setup, it just doesn not work at all in the new one. When I start osmo-bsc the LED on the BTS starts flashing green after a few seconds and then stops flashing and just stays green all the time, which is the expected behaviour. Unfortunately though, after another couple of seconds, the LED starts flashing green again and then turns red. This is what the log shows: BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=l2_bch.c:1154 **** ** l2_bch.c#1154:BCHbcchSItypeValid( prim_p->infoType ) ** IPA_SW_FATAL_ERROR ** In task "TRX Proc:L2_BCH" @ (1063). **** 　 . BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=TRX Proc:L2_BCH:l2_bch.c#1154 (1063). BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#255:TRX has logged the error: 　 . BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#256:TRX Proc:L2_BCH:l2_bch.c#1154 (1063) . BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=BCHbcchSItypeValid( prim_p->infoType ). BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#260:BCHbcchSItypeValid( prim_p->infoType ) 　 20180328072641280 DLINP <0013> input/ipaccess.c:247 Sign link vanished, dead socket 20180328072641281 DLINP <0013> input/ipaccess.c:71 Forcing socket shutdown with no signal link set 20180328072641282 DCTRL <000e> osmo_bsc_ctrl.c:160 No more BTS connected, sending TRAP. 　 Now I'm not claiming that my config is already 100% correct but I feel like this isn't a configuration issue. I'm using the most recent nightly builds of the entire osmocom library. Does anyone know what could be at fault here? Kind regards, Michael Spahn

4 9

OSmocom-LCS installation/implementation
by Sebastian F 30 Apr '18

30 Apr '18

Hi How to implement RRLP with Openbsc ? I have read that it can be done through Osmocom-LCS but it gives error on compiling. In short how to implement osmocom-LCS with openbsc ? Osmosom-LCS is not getting compiled !!! Thanks.

2 1

Opensbc support of 165CU
by Snehasish Kar 26 Apr '18

26 Apr '18

Hi Does the current openbsc version doesn't support ipaccess nanobts 165cu (Equipment_Version='165c029_67', result in abisip-find) ?? I am getting some unsupported error while running osmo-nitb. I have installed following from this link. https://osmocom.org/projects/cellular-infrastructure/wiki/Build_from_Source BR Snehasish Build from Source - Cellular Network Infrastructure - Open ...<https://osmocom.org/projects/cellular-infrastructure/wiki/Build_from_Source> osmocom.org External dependencies¶. If you want to build on specific Linux distros, you might need to install additional dependencies before the build will succeed

2 1

VLR problem
by Antony Lemmens 24 Apr '18

24 Apr '18

Hello folks, I have a strange behavior when the a MS send a Location Update, it is often rejected. I think the the problem is the "Rx GSUP LU Result without LU in progress" (see log further). It's weird because in the point of view of the HLR it seems OK : - message 0x04 Update Location Request followed by 0x10 Insert Subscriber Data Request - message 0x12 Insert Subscriber Data Result followed by 0x06 Update Location Result Is anyone experiencing the same problem? I will investigate in the code to see if I found something with the state machines or timers, if I found more detail, I will post them. Have a nice day, Antony Here is a extract of the logs of osmo-msc : 20180423132534278 DBSSAP <0010> a_iface_bssap.c:268 Rx BSSMAP COMPLETE L3 INFO (conn_id=4) 20180423132534278 DVLR <000e> vlr.c:388 New subscr, TMSI: 0xb35bd0aa 20180423132534278 DMSC <0006> a_iface_bssap.c:351 User has been accepted by MSC. 20180423132534748 DVLR <000e> gsm_04_08.c:3729 SUBSCR(MSISDN:1) VLR: update for IMSI=206012225318490 (MSISDN=1, used=2) 20180423132534748 DVLR <000e> vlr.c:769 SUBSCR(MSISDN:1) Rx GSUP LU Result without LU in progress 20180423132539279 DMM <0002> subscr_conn.c:110 Subscr_Conn(LU:3009138858)[0x1387410]{SUBSCR_CONN_S_AUTH_CIPH}: Close event, cause: CONGESTION 20180423132539279 DMM <0002> gsm_04_08.c:217 Subscriber IMSI:206012225318490: LOCATION UPDATING REJECT 20180423132539279 DMM <0002> vlr_lu_fsm.c:728 Subscr_Conn(LU:3009138858)[0x1387410]{SUBSCR_CONN_S_RELEASING}: Event SUBSCR_CONN_E_CN_CLOSE not permitted 20180423132539279 DBSSAP <0010> a_iface.c:419 (subscr IMSI:206012225318490, conn_id 4) Tx BSSMAP CLEAR COMMAND to BSC 20180423132539281 DBSSAP <0010> a_iface_bssap.c:241 (subscr IMSI:206012225318490, conn_id 4) Rx BSSMAP CLEAR COMPLETE, releasing SCCP connection

3 3

GSUP dissector merged to wireshark mainline
by Harald Welte 24 Apr '18

24 Apr '18

Hi! In case anyone wants to analyze GSUP protocol traces of Osmocom networks: The related dissector has just been merged mainline two days ago: https://code.wireshark.org/review/25477 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

Problems with A5/3 encryption
by Bruckner Jan (ETAS-SEC/ECT-Mu) 19 Apr '18

19 Apr '18

Dear list, I'm having trouble using the A5/3 encryption in my setup. A5/1 works perfectly fine [attachment a5_1.pcapng]. As soon as I switch to A5/3 and e.g. send an SMS, the last valid message I see in the Wireshark traces of the GSMTAP of osmo-bts-trx is the Ciphering Mode Command requesting A5/3. After that, several messages arrive at the bts, but it seems like it can't make any sense of them. The MS repeatedly tries to send the SMS but never succeeds [attachment a5_3.pcapng]. Both MSs are connected to the same bts. According to the Classmarks of all MSs, A5/1 as well as A5/3 are supported. This is my Setup: - USRP N210 - osmo-trx - osmo-bts-trx - osmo-nitb - osmo-pcu - osmo-sgsn - osmo-ggsn I'm using a Debian 9 VM and tried both the packages from osmocom-latest as well as osmocom-nightly. The MSs I've tested are two Nexus 6 and one Samsung Galaxy S I9000. All three with sysmocom nano USIMs. Could the decryption at the bts be incorrect? Has anyone tested/used it recently? I'll be happy to provide additional information if needed. Thanks, Jan

3 7

OSMO-BSC: Segmentation fault (core dumped)
by Ron 19 Apr '18

19 Apr '18

Hi All, We are experiencing Segmentation Fault intermittently in OSMO-BSC. We were able to create a crash file and enabled the debug in all logs of OSMO-BSC. We are using Ettus B210, intel UPBOARD and running in UBUNTU 16.04. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Attached are the debug log file, core dumped file (URL provided for download), config files used, lshw, and lscpu output. # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 92 Model name: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz Stepping: 9 CPU MHz: 800.000 CPU max MHz: 1101.0000 CPU min MHz: 800.0000 BogoMIPS: 2188.79 Virtualization: VT-x L1d cache: 24K L1i cache: 32K L2 cache: 1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts We also installed the OSMOCOM elements using source and save in the /usr/local directory. https://www.dropbox.com/s/pedh1zshhe5kmuc/core?dl=0 Best Regard, Ron Menez ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>

2 3

osmo-ttcn3-hacks / BSC tests: No mor need for IPA CCM cherry-pick!
by Harald Welte 17 Apr '18

17 Apr '18

Dear fellow Osmocmo developers, for many months it was required to cherry-pick a "HACK" patch to make the BSC tests work, presumably to work around a bug in libosmo-abis, see https://osmocom.org/issues/2718 As it turned out, libosmo-abis was not wrong, but my IPA_Emulation.ttcn, so it was good to not merge that "HACK" and keep it out of master. In Change-Id: I6d9eaf0d69457caacc03b9049a8bc57976480617 which was just merged to osmo-ttcn3-hacks master I have fixed that bug in IPA_Emulation.ttcn, so now the unmodified master of osmo-ttcn3-hacks will run fine. I'll remove the cherry-pick from our Dockerfiles, but please do make sure you also stop using it in your local clones/branches/scripts. -- - 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

MO-SMS Maximum Number of Characters for OSMO-NITB and OSMO-BSC less than 60?
by Ron 15 Apr '18

15 Apr '18

Hi All, Can anyone confirm if the maximum MO-SMS that can be sent is less than 60 characters including spaces? For OSMO-NITB, we reach a maximum of 59 characters for MO-SMS, while for OSMO-BSC, we only reach a maximum of 50 characters (MO-SMS). Is this a known issue? TIA. Best Regard, Ron Menez ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>

3 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC April 2018