- OpenBSC - lists.osmocom.org

shutdown FSM breaks ttcn3-bsc-test
by Neels Hofmeyr 25 Jun '20

25 Jun '20

dear Pau, please fix either osmo-bts or ttcn3-bsc-tests so that running ttcn3-bsc-tests works again. The failure I get for each and every BSC test: Verdict: fail reason: "Timeout waiting for BTS0 oml-connection-state ""degraded" When I downgrade osmo-bts to 580a27e97c3f0e139dfd7b0c10de24463d4b5294 (just before the shutdown FSM was introduced), the tests work again. (I didn't bisect, just picked that commit.) This failure is particularly harmful now because we're currently struggling with quite a couple of other reasons that cause the ttcn3-bsc-tests to fail. So when we fix those, jenkins won't show the fix, but yet a different error. I'm reluctant to revert your patches now, hopefully you can find a fix quickly to move forward instead. BTW, I also have introduced another new segfault in osmo-bsc myself, testing the fix now and merging it directly when successful, so that we don't all go insane. ~N

2 1

Introducing E1 / Abis support to osmo-mgw
by Harald Welte 20 Jun '20

20 Jun '20

Hi Philipp (and lurkers on this list), I've just pushed an update to the @laforge/trau@ branch of libosmo-abis, which contains the new code modules for E1 / TRAU usage, and also a small test program and test data. The test program takes a raw binary dump created from an E1 timeslot with TRAU frames captured of a BS-11 and converts that to RTP packets. You can feed those RTP packets into osmo-gapk to play them back. The audio is clear, there are just a few seconds of quiet at the beginning before anything is audible. The patches also add an "I460" mode to e1_input. So from the osmo-mgw side, I think we need to * link against libosmo-abis and call e1inp_init + e1inp_vty_init() * use existing VTY code to configure E1 line numbers / drivers / ports * call e1inp_ts_config_i460() on every timeslot we want to use (this should *not* happen on all timeslots, as some of them are used for signalling by the BSC) * call osmo_i460_subchan_add() / osmo_i460_subchan_del() for each i.460 sub-slot we want to use * build the processing chain like in libosmo-abis/contrib/trau2rtp/trau2rtp.c via i460 -> trau_sync -> osmo_trau_frame_decode_16k/osmo_trau_frame_decode_8k -> osmo_trau2rtp I believe this should be at a stage where it can be integrated into osmo-mgw. The API may not be 100% stable yet, but it shouldn't change completely. The main missing bits are: * allow selection of sync pattern in trau_sync.c (or auto-detect?) * handling of T-bits for alignment of air-interface timing with downlink TRAU frame timing I will next be hacking on a small tool that will speak the 'osmo-e1d' protocol but use binary capture files that are looped over and over again. This way you should be able to use libosmo-abis e1_input without any physical card and still get TRAU frame data. At a lower priority, I'd like to look into support for HRv1 and AMR TRAU frames on 16k sub-slots. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

updated videos / presentations on setting up Osmocom CNI
by Harald Welte 03 Jun '20

03 Jun '20

Hi! I just realized that since OsmoCon was discontinued after 2018 didn't result in sufficient turn-out, and only the 2017 incarnation contained some entry-level talks, we actually only have introductory level presentations / videos about a setup that still covers OsmoNITB. (https://media.ccc.de/v/osmocon17-4002-running_a_basic_circuit_switched_osmo…) This may or may not be a reason why some people still want to set up OsmoNITB in 2020. While our wiki and user manuals all have deprecated OsmoNITB years ago, people who only look for videos might be mislead. Also, I'm sure that several other presentation (like the one about 3G / osmo-iuh before the CNI split) would similarly benefit from an update. So I think we should try to create/update some slide decks and record related lectures / tutorials at some point this year. I wouldn't bother setting up a virtual conference or some kind of remote interaction at this point. Recording some talks and/or screencasts allows us to create and release them one-by-one. I would like to get started by collecting a list of topics at https://osmocom.org/issues/4578 before we start to actually work on the presentations. One question is also how to record, but let's first work on the content before we worry about recording and publication. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

ttcn3-bsc-test: LCLS test cases broken since build #987 (May 29)
by Vadim Yanitskiy 03 Jun '20

03 Jun '20

Hi all, as was noticed during the weekly review, all TTCN-3 BSC test cases from LCLS group are failing since build #987 (May 29) [1], so I am trying to investigate this. Until now I thought that it's somehow related to my IPA/RSL refactoring patch set, so I spent half of a day reading the code of those test cases and trying to figure out what could be the reason. But then I checked ttcn3-bsc-test-latest [2]. I should have done this first, of course. Magically all LCLS test cases are green there. So I assume that it's not related to the recent IPA/RSL changes, and most likely caused by recent changes to osmo-bsc and/or libosmo-*. I already tried to downgrade osmo-bsc to v1.6.0 (Jan 3) with no luck. If anyone was working on something related to RSL, MGCP or LCLS, please let me know - this might help to find the problem faster. Thanks! [1] https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/ [2] https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test-latest/ -- - Vadim Yanitskiy <vyanitskiy at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 1

Osmo-SIP-Connector Version 6
by Sonny Lafuente 30 May '20

30 May '20

Hi Community, Does anyone here tried to upgrade the your working OSMO environment to its latest version? I have the experience where I upgraded my working osmo to the latest version and I have encountering some problem between the connection of osmo-nitb and osmo-sip-connector. For the latest sip connector update it will communicate the connection going to osmo-msc. Since I don’t use the osmo-msc instead I am using the osmo-nitb for the standalone project. Below is the error I have experiencing right now in the osmo-sip-connector and osmo-nitb. SIP Connector Logs: <0001> mncc.c:845 Incompatible version(5) expected 6 <0001> mncc.c:936 Reconnected to /tmp/msc_mncc <0001> mncc.c:841 Got hello message version 5 <0001> mncc.c:845 Incompatible version(5) expected 6 <0001> mncc.c:936 Reconnected to /tmp/msc_mncc <0001> mncc.c:841 Got hello message version 5 <0001> mncc.c:845 Incompatible version(5) expected 6 OSMO-NITB Logs: Fri May 29 13:13:16 2020 <0006> mncc_sock.c:84 MNCC Socket has LOST connection Fri May 29 13:13:16 2020 <0001> gsm_04_08.c:463 Clearing all currently active transactions!!! Fri May 29 13:13:21 2020 <0006> mncc_sock.c:271 MNCC Socket has connection with external call control application Fri May 29 13:13:21 2020 <0006> mncc_sock.c:84 MNCC Socket has LOST connection Fri May 29 13:13:21 2020 <0001> gsm_04_08.c:463 Clearing all currently active transactions!!! Here are the configuration file of osmo-nitb and osmo-sip-connector and how we run the command. SIP Connector: Command to run: ./osmo-sip-connector -c ~/osmo-sip-connector.cfg Config File: # sip local 192.168.1.166 5062 remote 192.168.1.166 5060 sofia-sip log-level 2 mncc socket-path /tmp/msc_mncc app OSMO NITB: Command to run: ./osmo-nitb -C -c ~/osmo-nitb.cfg -T -P -l /home/hlr.sqlite3 -M /tmp/msc_mncc Config File: line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive network network country code 94 mobile network code 1 short name 1 long name 1 auth policy accept-all authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 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 t3109 1 timer t3105 1 timer t3113 60 timer t3103 1 timer t3122 10 timer t3101 10 dyn_ts_allow_tch_f 0 subscriber-keep-in-ram 1 bts 0 type sysmobts band GSM900 cell_identity 1 location_area_code 1 base_station_id_code 63 ms max power 0 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator descending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1000 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr hr efr amr amr tch-h modes 0 amr tch-h start-mode auto gprs mode gprs gprs 11bit_rach_support_for_egprs 0 gprs routing area 1 gprs network-control-order nc0 gprs cell bvci 2 gprs cell timer blocking-timer 3 gprs cell timer blocking-retries 3 gprs cell timer unblocking-retries 3 gprs cell timer reset-timer 3 gprs cell timer reset-retries 3 gprs cell timer suspend-timer 10 gprs cell timer suspend-retries 3 gprs cell timer resume-timer 10 gprs cell timer resume-retries 3 gprs cell timer capability-update-timer 10 gprs cell timer capability-update-retries 3 gprs nsei 101 gprs ns timer tns-block 3 gprs ns timer tns-block-retries 3 gprs ns timer tns-reset 3 gprs ns timer tns-reset-retries 3 gprs ns timer tns-test 30 gprs ns timer tns-alive 3 gprs ns timer tns-alive-retries 10 gprs nsvc 0 nsvci 101 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 127.0.0.2 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0 gprs nsvc 1 remote udp port 0 gprs nsvc 1 remote ip 0.0.0.0 no force-combined-si trx 0 rf_locked 0 arfcn 74 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config TCH/F hopping enabled 0 trx 1 rf_locked 0 arfcn 65 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config TCH/F hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h amr nitb subscriber-create-on-demand subscriber-create-on-demand random 100000 199999 no assign-tmsi smpp local-tcp-ip 127.0.0.1 2776 system-id password policy closed smpp-first esme root password password default-route Thank you. Sonny

4 5

How to 'POWERON' the osmo-trx
by cruise 11 May '20

11 May '20

hello: I installed the osmo-NITB on ubuntu18.04, including osmo-trx,osmo-bts,and openbsc. The following is the print messages when these three applications start up. *1.osmo-trx* $ sudo osmo-trx-uhd -C osmo-trx-usrp_b200.cfg Info: SSE3 support compiled in and supported by CPU Info: SSE4.1 support compiled in and supported by CPU Tue May 5 12:36:27 2020 DLGLOBAL <0007> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Tue May 5 12:36:27 2020 DLCTRL <000e> control_if.c:911 CTRL at 127.0.0.1 4236 Tue May 5 12:36:27 2020 DMAIN <0000> osmo-trx.cpp:484 [tid=139758118945664] Config Settings Log Level............... 0 Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 GSM BTS Address......... 127.0.0.1 Channels................ 1 Tx Samples-per-Symbol... 4 Rx Samples-per-Symbol... 4 EDGE support............ 0 Extended RACH support... 0 Reference............... 1 Filler Burst Type....... Empty bursts Filler Burst TSC........ 0 Filler Burst RACH Delay. 0 Multi-Carrier........... 0 Tuning offset........... 0 RSSI to dBm offset...... 28 Swap channels........... 0 Tx Antennas............. '<default>' Rx Antennas............. '<default>' Tue May 5 12:36:27 2020 DMAIN <0000> osmo-trx.cpp:438 [tid=139758118945664] Setting SCHED_RR priority 18 Tue May 5 12:36:27 2020 DDEVDRV <0006> log.cpp:460 [tid=139758008424192] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; UHD_3.14.0.HEAD-0-g6875d061 Tue May 5 12:36:27 2020 DDEV <0005> UHDDevice.cpp:470 [tid=139758118945664] Using discovered UHD device type=b200,name=Lab_B210,serial=86680AA,product=B210 Tue May 5 12:36:28 2020 DDEVDRV <0006> b200_impl.cpp:386 [tid=139758008424192] [B200] Detected Device: B210 Tue May 5 12:36:29 2020 DDEVDRV <0006> b200_iface.cpp:441 [tid=139758008424192] [B200] Loading FPGA image: /home/cruise/openBSC/osmo-trx/usrp_b210_fpga.bin... Tue May 5 12:36:45 2020 DDEVDRV <0006> b200_impl.cpp:433 [tid=139758008424192] [B200] Operating over USB 3. Tue May 5 12:36:45 2020 DDEVDRV <0006> b200_impl.cpp:484 [tid=139758008424192] [B200] Detecting internal GPSDO.... Tue May 5 12:36:46 2020 DDEVDRV <0006> gps_ctrl.cpp:253 [tid=139758008424192] [GPS] No GPSDO found Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:587 [tid=139758008424192] [B200] Initialize CODEC control... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:650 [tid=139758008424192] [B200] Initialize Radio control... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:957 [tid=139758008424192] [B200] Performing register loopback test... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:966 [tid=139758008424192] [B200] Register loopback test passed Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:957 [tid=139758008424192] [B200] Performing register loopback test... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:966 [tid=139758008424192] [B200] Register loopback test passed Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:758 [tid=139758008424192] [B200] Setting master clock rate selection to 'automatic'. Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:1013 [tid=139758008424192] [B200] Asking for clock rate 16.000000 MHz... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:1024 [tid=139758008424192] [B200] Actually got clock rate 16.000000 MHz. Tue May 5 12:36:47 2020 DMAIN <0000> UHDDevice.cpp:211 [tid=139758118945664] Antennas configured successfully Tue May 5 12:36:47 2020 DDEVDRV <0006> multi_usrp.cpp:502 [tid=139758008424192] [MULTI_USRP] Setting master clock rate selection to 'manual'. Tue May 5 12:36:47 2020 DDEVDRV <0006> b200_impl.cpp:1013 [tid=139758008424192] [B200] Asking for clock rate 26.000000 MHz... Tue May 5 12:36:47 2020 DDEVDRV <0006> b200_impl.cpp:1024 [tid=139758008424192] [B200] Actually got clock rate 26.000000 MHz. Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:275 [tid=139758118945664] Rates configured for B210 4 SPS Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:235 [tid=139758118945664] Supported Tx gain range [0; 89.75] Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:240 [tid=139758118945664] Supported Rx gain range [0; 76] Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:244 [tid=139758118945664] Default setting Tx gain for channel 0 to 44.875 Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:251 [tid=139758118945664] Default setting Rx gain for channel 0 to 38 Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:569 [tid=139758118945664] Device configuration: Single USRP: Device: B-Series Device Mboard 0: B210 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: FE-RX2 TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: FE-TX2 Tue May 5 12:36:47 2020 DMAIN <0000> osmo-trx.cpp:532 [tid=139758118945664] -- Transceiver active with 1 channel(s) *_/when the osmo-bts-trx launched later, the following messages will arise, shows that the osmo-trx received the 'POWEROFF' command and feed back the 'RESPONSE' to osmo-bts-trx./_* Tue May 5 12:42:44 2020 DTRXCTRL <0002> Transceiver.cpp:832 [tid=139758118945664][chan=0] command is 'POWEROFF' Tue May 5 12:42:44 2020 DTRXCTRL <0002> Transceiver.cpp:977 [tid=139758118945664][chan=0] response is 'RSP POWEROFF 0' ** *_/POWERON command was not launched. and the USRP TX/RX LED was not lighted./_* *2.osmo-bts-trx* $ sudo osmo-bts-trx ((*)) | / \ OsmoBTS <0017> control_if.c:911 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:104 Available via telnet 127.0.0.1 4241 <0012> input/ipaccess.c:1024 enabling ipaccess BTS mode, OML connecting to 192.168.122.1:3002 <000b> trx_if.c:1174 phy0.0: Open transceiver ** *_/About one minutes later, the osmo-bts-trx will exit automatically, and the following messages was printed./_* <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 90 0f 00 c8 <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 88 12 06 00 00 00 00 00 00 <000d> abis.c:143 Signalling link down <0001> bts.c:293 Shutting down BTS 0, Reason Abis close Shutdown timer expired *3. osmo-nitb* $ sudo osmo-nitb -c osmo-nitb-ipa.cfg <001e> telnet_interface.c:104 Available via telnet 127.0.0.1 4242 <0020> input/ipaccess.c:985 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports <0025> control_if.c:911 CTRL at 127.0.0.1 4249 DB: Database initialized. DB: Database prepared. In a word, the hardware USRP TX/RX LED has not been lighted, it seems not work. How to poweron it?

4 6

DGSM merge: need feedback on open questions
by Neels Hofmeyr 01 May '20

01 May '20

Hi all, we need to wrap up the DGSM work and get it to a state that can be merged to master. There are still open issues that I am not sure how to solve, which I've mentioned on some occasions, but it seems to not have been loud enough. I would easily choose one way, but am not sure about others' opinions. (1) One open point is the GSUP peer identification. I've added a comment explaining it in https://gerrit.osmocom.org/c/osmo-hlr/+/16459/9 Me personally, I would strip down basically all of that complexity again and go with the simplest solution, a nul terminated size limited char string for GSUP peer id. The patch became what it is because vague requirements were thrown in the mix and I tried to accomodate them, and now it ended up being a rather ugly shim around a simple char string, really. (2) Another open question is the freeing behavior in osmo_gsup_req (for proper async handling of DGSM, and to ensure proper GSUP responses). I've added a comment explaining that in https://gerrit.osmocom.org/c/osmo-hlr/+/16205/29 The gist for both issues is that I could write patches that would have a large ripple effect throug many files and follow-up patches, but if we again disagree on the outcome, the work would multiply. So, DGSM works and is ready, except that we need to agree on what will be accepted by review. I need opinions to be able to complete this (or possibly a "go" to do whatever I think is right and merge that). Thanks! ~N

3 4

POWEROFF after the osmo-NITB has been installed
by cruise 30 Apr '20

30 Apr '20

Hello: I installed the osmo-NITB on ubuntu18.04, including osmo-trx,osmo-bts,and openbsc. I run these three applications in three terminals successively, it seems ok, but the tx/rx leds on usrp-b210 hardware platform are not lighted, and the print message in the osmo-trx terminal shows : Thu Apr 30 15:28:28 2020 DTRXCTRL <0002> Transceiver.cpp:832 [tid=139871716352896][chan=0] command is 'POWEROFF' Thu Apr 30 15:28:28 2020 DTRXCTRL <0002> Transceiver.cpp:977 [tid=139871716352896][chan=0] response is 'RSP POWEROFF 0' I try to send some commands on another terminal which launch a telnet session which connects to the osmo-bts control interface(port number is 4238) , but it not working. what can i do next? thanks a lot.

2 1

version problem of libosmocore during installing osmoTRX
by cruise 30 Apr '20

30 Apr '20

$ git clone git：//git.osmocom.org/osmo-trx $ git branch * master $ ./configure ... checking for LIBOSMOCORE... no configure: error: Package requirements (libosmocore >= 1.3.0) were not met: No package 'libosmocore' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Then, check the information of libosmocore: $dpkg -l |grep libosmocore ii libosmocore:amd64 0.9.0-7 amd64 Open Source MObile COMmunications CORE library (metapackage) ii libosmocore6:amd64 0.9.0-7 amd64 Osmo Core library $ sudo apt-get install libosmocore ... libosmocore has already been the newest version (0.9.0-7)。 why???what can i do?

2 1

Docker containers.
by Andrew Back 25 Apr '20

25 Apr '20

Appreciate that the Osmocom Docker configurations exist principally for automated testing and here it may not make sense, but I wondered if builds are published to a registry? The Makefile in the make project located in the docker-playground repo sets docker.io as registry and has a target for docker push. Also see OBS Release.key files in project sub-directories, but couldn't find container builds being published anywhere. Was hoping I could just pull containers for the latest project versions, without cloning and building the containers in docker-playground. Also saw the comments from 2017 on Docker shortcomings and assuming SCTP works OK now in Docker networking? Regards, Andrew

2 5