OpenBSC January 2019

openbsc@lists.osmocom.org

25 participants
52 discussions

Start a nNew thread

Re: Re: Re: OsmoTRX - osmo-trx-usrp-1 Aborted :: Assertion 'px != 0' failed
by Sergey Mayzus 17 Jan '19

17 Jan '19

1 0

osmo-hlr db upgrade behavior poll
by Neels Hofmeyr 17 Jan '19

17 Jan '19

Hi all, when reviewing osmo-hlr db schema upgrades, I came up with the idea that we shouldn't upgrade automatically. That's why, for schema updates, osmo-hlr now refuses to start and requires one start with the --db-upgrade option. Our systemd service file does not include that option. The result is that after an upgraded osmo-hlr binary, admins may have to take extra action to upgrade the DB. The rationale is that if someone by accident launches a newer osmo-hlr only once, with automatic upgrade the user is then stuck with the newer version DB, since we don't make a backup and we don't provide a downgrade path. I'm now wondering whether that is really necessary. In the daily churn, it creates noise. How to make this less noisy? - Users could add the --db-upgrade option to the service file to always upgrade. (But it is cumbersome to have a .service file that differs from the installed version) - We could also add a cfg file option to allow-db-upgrades. - We could drop the behavior and always upgrade. In the lack of strong opinions, this will probably stay as it is. I'd just like to hear what you guys think about it. Is it annoying or a good idea? Thanks! ~N

4 4

default TA vty config for OSMO-PCU?
by Keith 17 Jan '19

17 Jan '19

Hey list.. so i want to do some experiments setting the default TA in the PCU to the distance from the tower to the main population centre, rather than have it set to 220 (invalid) So, this email is not about the details of that issue, rather just a quick question. In the interim while this gets finally done right, would we accept adding a default-timing-advance param to the vty config? Otherwise I can patch and compile version for each BTS, but the vty config would be WAY more handy! thnx k/

2 2

SMS Sender Name Using Alphanumeric Characters
by Ron 15 Jan '19

15 Jan '19

Hi Community, Is it possible to send SMS using alphanumeric characters as a sender address? We tried it using an Open-Source SMS GW and it can send alphanumeric information in the sender address. Unfortunately, the SMS sent through API was not received to the test phone and the logs below are seen in OSMO-MSC. <000c> smpp_smsc.c:729 [entropy] Rx SUBMIT-SM (09170000023/1/1) <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. We also tried sending SMS with only Numeric information in the sender address and the SMS was received successfully by the test phone. We can share the traces taken and the configurations used if needed. TIA. Best Regard, Ron Menez ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>

3 5

A ramble about MSC, sip-connector and asterisk.
by Gullik Webjorn 15 Jan '19

15 Jan '19

Hi, Some weeks ago I managed to integrate osmobts with my asterisk server. In the beginning, I did not get any call progress, ( as opposed to running WITHOUT asterisk ). I realized that defining the msc to sipconnector socket effectively disabled all the logic related to this. To remedy the situation, I set an asterisk "progress statement" whenever the extensions.conf indicated a number belonging to my GSM network. This works OK, but now, I don't get call progress on calls toward PSTN. These extensions do not have "progress" statements, since all SIP phones interpret the call progress sip messages such as RINGING. I am interested in your comments whether msc + sipconnector should emulate mobiles as "sip phones", it does seem to just silently drop call progress messages, and is this the way it should work? The functionality IS there, since when osmobts was bridging the calls, call progress WAS there. Well, I kludged up a solution for the GSM-only situation, and this seems suboptimal. I guess some clever asterisk hacking would solve that, possibly having a redundant progress statement on ALL extensions would do it, but would I not lose "actual" call progress signals from the PSTN, since asterisk would emulate them? Another way would be a small "local" asterisk.....before the *real* one. Boldly moving on to MultiBTS and handover.... Gullik

4 4

OsmoTRX + LimeSDR + Pine64
by Alex 14 Jan '19

14 Jan '19

Hi everyone, I'm facing a little strange problem with latest version of OsmoTRX and LimeSDR on a Pine64 board. I've built everything from source (latest git commit) Here is the console output of osmo-trx-lms root@pine64:~/osmo-trx# osmo-trx-lms -C /opt/osmocom/etc/osmo-trx-limesdr.cfg Sun Jan 13 22:11:40 2019 DLGLOBAL <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Sun Jan 13 22:11:40 2019 DLCTRL <000b> control_if.c:911 CTRL at 127.0.0.1 4236 Sun Jan 13 22:11:40 2019 DMAIN <0000> osmo-trx.cpp:430 [tid=281473725702144] 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 Reference............... 0 C0 Filler Table......... 1 Multi-Carrier........... 0 Tuning offset........... 0 RSSI to dBm offset...... 0 Swap channels........... 0 Tx Antennas............. 'BAND1' Rx Antennas............. 'LNAW' Sun Jan 13 22:11:40 2019 DDEV <0002> LMSDevice.cpp:68 [tid=281473725702144] creating LMS device... Sun Jan 13 22:11:40 2019 DDEV <0002> LMSDevice.cpp:156 [tid=281473725702144] Opening LMS device.. Sun Jan 13 22:11:40 2019 DDEV <0002> LMSDevice.cpp:162 [tid=281473725702144] Devices found: 1 Sun Jan 13 22:11:40 2019 DDEV <0002> LMSDevice.cpp:172 [tid=281473725702144] Device [0]: LimeSDR Mini, media=USB 2.0, module=FT601, addr=24607:1027, serial=1D4259C8DFD3CD Sun Jan 13 22:11:40 2019 DDEV <0002> LMSDevice.cpp:181 [tid=281473725702144] Using device[0] Sun Jan 13 22:11:40 2019 DLMS <0003> LMSDevice.cpp:102 [tid=281473725702144] Reference clock 40.00 MHz Sun Jan 13 22:11:40 2019 DDEV <0002> LMSDevice.cpp:191 [tid=281473725702144] Init LMS device Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:113 [tid=281473725702144] Sample Rate: Min=100000 Max=3.072e+07 Step=0 Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:201 [tid=281473725702144] Setting sample rate to 1.08333e+06 4 Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:207 [tid=281473725702144] Sample Rate: Host=1.08333e+06 RF=3.46667e+07 Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:214 [tid=281473725702144] Setting Internal clock reference Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:218 [tid=281473725702144] Setting VCTCXO to 180 Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:113 [tid=281473725702144] LPFBWRange Rx: Min=1.4001e+06 Max=1.3e+08 Step=0 Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:113 [tid=281473725702144] LPFBWRange Tx: Min=1.4001e+06 Max=1.3e+08 Step=0 Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:242 [tid=281473725702144] LPFBW: Rx=1.4001e+06 Tx=5.2e+06 Sun Jan 13 22:11:41 2019 DMAIN <0000> LMSDevice.cpp:203 [tid=281473725702144] Antennas configured successfully Sun Jan 13 22:11:41 2019 DDEV <0002> LMSDevice.cpp:251 [tid=281473725702144] Setting LPFBW chan 0 Sun Jan 13 22:11:44 2019 DLMS <0003> LMSDevice.cpp:102 [tid=281473725702144] RX LPF configured Sun Jan 13 22:11:44 2019 DLMS <0003> LMSDevice.cpp:102 [tid=281473725702144] Filter calibrated. Filter order-4th, filter bandwidth set to 5.2 MHz.Real pole 1st order filter set to 2.5 MHz. Preemphasis filter not active Sun Jan 13 22:11:44 2019 DLMS <0003> LMSDevice.cpp:102 [tid=281473725702144] TX LPF configured Sun Jan 13 22:11:44 2019 DDEV <0002> LMSDevice.cpp:256 [tid=281473725702144] Calibrating chan 0 Sun Jan 13 22:11:44 2019 DLMS <0003> LMSDevice.cpp:102 [tid=281473725702144] Rx calibration finished Sun Jan 13 22:11:44 2019 DLMS <0003> LMSDevice.cpp:102 [tid=281473725702144] Tx calibration finished osmo-trx-lms: Threads.cpp:133: void Thread::start(void* (*)(void*), void*): Assertion `!res' failed. signal 6 received talloc report on 'OsmoTRX' (total 3427 bytes in 17 blocks) telnet_connection contains 1 bytes in 1 blocks (ref 0) 0xf748b60 logging contains 3043 bytes in 9 blocks (ref 0) 0xf6c44f0 struct trx_ctx contains 383 bytes in 5 blocks (ref 0) 0xf6c4220 msgb contains 0 bytes in 1 blocks (ref 0) 0xf6c41b0 full talloc report on 'OsmoTRX' (total 3427 bytes in 17 blocks) telnet_connection contains 1 bytes in 1 blocks (ref 0) 0xf748b60 logging contains 3043 bytes in 9 blocks (ref 0) 0xf6c44f0 Configure logging Set the log level for a specified category Main generic category TRX CTRL interface Device/Driver specific code Logging from within LimeSuite itself Library-internal global log family LAPD in libosmogsm A-bis Intput Subsystem A-bis B-Subchannel TRAU Frame Multiplex A-bis Input Driver for Signalling A-bis Input Driver for B-Channels (voice) Layer3 Short Message Service (SMS) Control Interface GPRS GTP library Statistics messages and logging Generic Subscriber Update Protocol Osmocom Authentication Protocol libosmo-sigtran Signalling System 7 libosmo-sigtran SCCP Implementation libosmo-sigtran SCCP User Adaptation libosmo-sigtran MTP3 User Adaptation libosmo-mgcp Media Gateway Control Protocol libosmo-netif Jitter Buffer Deprecated alias for 'no logging level force-all' contains 798 bytes in 1 blocks (ref 0) 0xf7019a0 logging level (main|trxctrl|dev|lms|lglobal|llapd|linp|lmux|lmi|lmib|lsms|lctrl|lgtp|lstats|lgsup|loap|lss7|lsccp|lsua|lm3ua|lmgcp|ljibuf) everything contains 150 bytes in 1 blocks (ref 0) 0xf7017f0 Configure logging Set the log level for a specified category Main generic category TRX CTRL interface Device/Driver specific code Logging from within LimeSuite itself Library-internal global log family LAPD in libosmogsm A-bis Intput Subsystem A-bis B-Subchannel TRAU Frame Multiplex A-bis Input Driver for Signalling A-bis Input Driver for B-Channels (voice) Layer3 Short Message Service (SMS) Control Interface GPRS GTP library Statistics messages and logging Generic Subscriber Update Protocol Osmocom Authentication Protocol libosmo-sigtran Signalling System 7 libosmo-sigtran SCCP Implementation libosmo-sigtran SCCP User Adaptation libosmo-sigtran MTP3 User Adaptation libosmo-mgcp Media Gateway Control Protocol libosmo-netif Jitter Buffer Log debug messages and higher levels Log informational messages and higher levels Log noticeable messages and higher levels Log error messages and higher levels Log only fatal messages contains 933 bytes in 1 blocks (ref 0) 0xf7013e0 logging level (main|trxctrl|dev|lms|lglobal|llapd|linp|lmux|lmi|lmib|lsms|lctrl|lgtp|lstats|lgsup|loap|lss7|lsccp|lsua|lm3ua|lmgcp|ljibuf) (debug|info|notice|error|fatal) contains 171 bytes in 1 blocks (ref 0) 0xf701230 struct log_target contains 214 bytes in 2 blocks (ref 0) 0xf6c4940 struct log_category contains 46 bytes in 1 blocks (ref 0) 0xf6c4a50 struct log_info contains 776 bytes in 2 blocks (ref 0) 0xf6c4560 struct log_info_cat contains 736 bytes in 1 blocks (ref 0) 0xf6c45f0 struct trx_ctx contains 383 bytes in 5 blocks (ref 0) 0xf6c4220 LNAW contains 5 bytes in 1 blocks (ref 0) 0xf748fd0 BAND1 contains 6 bytes in 1 blocks (ref 0) 0xf748ec0 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0xf6c4470 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0xf6c43f0 msgb contains 0 bytes in 1 blocks (ref 0) 0xf6c41b0 Aborted Can someone provide me a little light on this? I've some doubts about the usb power output, but I'm facing this also with a powered usb hub. Thank you and best regards Alex

2 3

SMS Sender Name using Alphanumeric
by Ron 14 Jan '19

14 Jan '19

Hi Community, Is it possible to send SMS using alphanumeric information as a sender address? We tried it using an Open-Source SMS GW and it can send alphanumeric information in the sender address. Unfortunately, the SMS sent through API was not received to the test phone and the logs below are seen in OSMO-MSC. <000c> smpp_smsc.c:729 [entropy] Rx SUBMIT-SM (09170000023/1/1) <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 259 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. <0017> sms_queue.c:155 Sending SMS 260 failed 0 times. We also tried sending SMS with only Numeric information in the sender address and the SMS was received successfully by the test phone. Also attached in this email are the traces and configuration files used and taken during the testing. Kindly advice if we missed something in our configuration. TIA. Best Regard, Ron Menez ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>

1 0

GSM MS Tx power levels (was Re: uncalibrated general-purpose SDRs (was Re: Balancing BTS'es for handover))
by Mychaela Falconia 14 Jan '19

14 Jan '19

Harald Welte wrote: > [...] the big difference is that the mobile has been calibrated to > (if I remember) 2dB accuracy, The GSM 05.05 spec indeed sets a tolerance of 2 dB under normal conditions or 2.5 dB under extreme conditions on the mobile station's maximum power output level for each band. These tolerances get looser for the lower power control level, up to 5 dB under normal conditions or 6 dB under extreme conditions for the lowest PCL. However, as someone who is intimately familiar with the actual calibration procedures performed by MS manufacturers (just did it myself less than 48 hours ago for a new batch of boards), I can tell you how it is actually done. There is a table of target power levels in dBm, and the calibration station goes through the full set of allowed PCLs (5-19 for EGSM and GSM850, or 0-15 for DCS and PCS) and steers the Tx power output (as measured by the test instrument, usually R&S CMU200) for each PCL to the dBm number in the table. But there is a hack in this setup which most MS manufacturers fail to disclose: with all GSM MS RF designs I have laid my hands on so far, including the one I've inherited from Openmoko (OK, I admit that all of my experience is with old stuff, not any of the recent stuff from MTK or Spreadtrum, but don't blame me, blame MTK and Spreadtrum for not publicly releasing their full chip docs and reference firmware source code), the MS hardware is oftentimes not actually capable of putting out the maximum power output prescribed by the spec (33 dBm for low bands or 30 dBm for high bands) while staying in the linear range of the PA (the range in which the relation between the APC control voltage and RF Vout is mostly linear), and thus the calibration procedure has to be fudged. In the case of Openmoko, they set the calibration targets for the highest power levels to 31.8 dBm and 28.8 dBm instead of 33/30 (for low and high bands, respectively), the next PCL down is set to 30.5/27.5 instead of 31/28, and then the proper official numbers from the spec further down. I have to do the same on my current GSM MS boards: when I tried putting out the full 33/30 dBm at the maximum PCL as the spec calls for, I can usually hit it if I crank the PA really high, but then it goes out of its linear range, and lacking better RF kung-fu, I have to assume that it's bad.. The maximum Tx power level fudging done by manufacturers in my or Openmoko's position is 1.2 dB, which is less than the spec tolerance of 2 dB, thus manufacturers like OM who did this fudging had no problems passing type approval tests, but I really wish I could find someone with more professional GSM MS design and manufacturing experience who could explain what actually happens, why we are not able hit the highest power levels while staying in the PA's linear range (the PA datasheet says it can put out 34.2 dBm in the low bands and 32.0 dBm in the high bands), and how the RF hw design might be improved so we can put out the highest power levels without fudging. Aside from the just-described fudging, the actual calibration tolerance (the maximum error between what the calibration procedure aims for and what actually comes out as measured by the CMU200) is less than 0.7 dB - and those ~0.5-0.6 dB errors happen mostly toward the lower power levels where the spec tolerances are the loosest; the maximum power level is calibrated to the shifted target number to better than 0.1 dB. M~

1 0

Balancing BTS'es for handover
by Gullik Webjorn 14 Jan '19

14 Jan '19

Below is a measurement on my "most distant" BTS, BTS 1. From what I see, downlink is 35 dB below uplink, which of course is natural when the MS can produce 30 dBm, and the BTS which in this case uses a bareback Limesdr min, can only produce 10 dBm. the bsc parameter ms max power is set to 15 for both bts 0 and bts 1. However, it seems MS output power is *much* stronger. Further, my understanding is that it is the BTS level measurements that decides when to handover, i.e. measurements in the upstream, and not the MS receive levels... Since there is such a mismatch between the micro BTS and the MS, maybe the RX should be attenuated, to bring upsteram levels more equal to downstream. OsmoBSC# show conns Active subscriber connections: conn ID=6, MSC=0, hodec2_fail=0, mgw_ep=rtpbridge/1@mgw BTS 0, TRX 0, Timeslot 1, Lchan 0: Type TCH_F Connection: 1, State: ESTABLISHED BS Power: 20 dBm, MS Power: 16 dBm Channel Mode / Codec: SPEECH_V1 No Subscriber Bound IP: 127.0.0.1 Port 16390 RTP_TYPE2=0 CONN_ID=0 Conn. IP: 192.168.1.70 Port 4186 RTP_TYPE=3 SPEECH_MODE=0x00 Measurement Report: Flags: MS Timing Offset: 0 L1 MS Power: 16 dBm, Timing Advance: 0 RXL-FULL-dl: -110 dBm, RXL-SUB-dl: -110 dBm RXQ-FULL-dl: 5, RXQ-SUB-dl: 5 RXL-FULL-ul: -74 dBm, RXL-SUB-ul: -73 dBm RXQ-FULL-ul: 3, RXQ-SUB-ul: 1 What are *your* experiences with "power control" and with "handover". Best Regards, Gullik

3 5

Build failed in Jenkins: Coverity-Upload (jenkins-job-builder) #356
by jenkins＠lists.osmocom.org 13 Jan '19

13 Jan '19

See <https://jenkins.osmocom.org/jenkins/job/osmocom-coverity/356/display/redire…> ------------------------------------------ [...truncated 723.64 KB...] CC RANAP_GeographicalArea.lo CC RANAP_GeographicalCoordinates.lo CC RANAP_GA-EllipsoidArc.lo CC RANAP_GA-AltitudeAndDirection.lo CC RANAP_GA-Point.lo CC RANAP_GA-PointWithAltitude.lo CC RANAP_GA-PointWithAltitudeAndUncertaintyEllipsoid.lo In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SEQUENCE_OF.h:8:0, from ../../include/osmocom/ranap/RANAP_IE-Extensions.h:15, from ../../include/osmocom/ranap/RANAP_GeographicalCoordinates.h:16, from ../../include/osmocom/ranap/RANAP_GA-Point.h:14, from ../../include/osmocom/ranap/RANAP_GeographicalArea.h:14, from RANAP_GeographicalArea.c:7: ../../include/osmocom/ranap/RANAP_GA-Polygon.h:26:23: warning: ‘struct Member’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct Member { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_GA-Polygon.h:26:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct Member { ^~~~~~~~~~~~~ CC RANAP_GA-PointWithUnCertainty.lo CC RANAP_GA-PointWithUnCertaintyEllipse.lo CC RANAP_GA-Polygon.lo CC RANAP_GA-UncertaintyEllipse.lo CC RANAP_GERAN-BSC-Container.lo CC RANAP_GERAN-Cell-ID.lo CC RANAP_GERAN-Classmark.lo CC RANAP_GlobalCN-ID.lo In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SEQUENCE_OF.h:8:0, from ../../include/osmocom/ranap/RANAP_GA-Polygon.h:14, from RANAP_GA-Polygon.c:7: ../../include/osmocom/ranap/RANAP_GA-Polygon.h:26:23: warning: ‘struct Member’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct Member { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_GA-Polygon.h:26:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct Member { ^~~~~~~~~~~~~ CC RANAP_GlobalRNC-ID.lo CC RANAP_GTP-TEI.lo CC RANAP_GuaranteedBitrate.lo CC RANAP_HigherBitratesThan16MbpsFlag.lo CC RANAP_HS-DSCH-MAC-d-Flow-ID.lo CC RANAP_IMEI.lo CC RANAP_IMEIGroup.lo CC RANAP_IMEIList.lo CC RANAP_IMEISV.lo CC RANAP_IMEISVGroup.lo CC RANAP_IMEISVList.lo CC RANAP_ImmediateMDT.lo CC RANAP_IMSI.lo CC RANAP_IncludeVelocity.lo CC RANAP_InformationExchangeID.lo CC RANAP_InformationExchangeType.lo CC RANAP_InformationRequested.lo CC RANAP_InformationRequestType.lo CC RANAP_InformationTransferID.lo CC RANAP_InformationTransferType.lo CC RANAP_IntegrityProtectionAlgorithm.lo CC RANAP_IntegrityProtectionInformation.lo CC RANAP_IntegrityProtectionKey.lo CC RANAP_InterSystemInformationTransferType.lo CC RANAP_InterSystemInformation-TransparentContainer.lo CC RANAP_IPMulticastAddress.lo CC RANAP_IuSignallingConnectionIdentifier.lo CC RANAP_KeyStatus.lo CC RANAP_IuTransportAssociation.lo CC RANAP_LA-LIST.lo CC RANAP_LAC.lo CC RANAP_LAI.lo In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SEQUENCE_OF.h:8:0, from ../../include/osmocom/ranap/RANAP_LA-LIST.h:14, from RANAP_LA-LIST.c:7: ../../include/osmocom/ranap/RANAP_LA-LIST.h:27:23: warning: ‘struct MemberA’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct MemberA { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_LA-LIST.h:27:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct MemberA { ^~~~~~~~~~~~~ CC RANAP_LastKnownServiceArea.lo CC RANAP_LastVisitedUTRANCell-Item.lo CC RANAP_LHN-ID.lo CC RANAP_Links-to-log.lo CC RANAP_ListOF-SNAs.lo CC RANAP_ListOfInterfacesToTrace.lo CC RANAP_InterfacesToTraceItem.lo CC RANAP_LoadValue.lo CC RANAP_LocationRelatedDataRequestType.lo CC RANAP_LocationRelatedDataRequestTypeSpecificToGERANIuMode.lo CC RANAP_LocationReportingTransferInformation.lo CC RANAP_ReportChangeOfSAI.lo CC RANAP_PeriodicReportingIndicator.lo CC RANAP_DirectReportingIndicator.lo CC RANAP_L3-Information.lo CC RANAP_M1Report.lo CC RANAP_M2Report.lo CC RANAP_M4Report.lo CC RANAP_M4-Collection-Parameters.lo CC RANAP_M4-Period.lo CC RANAP_M4-Threshold.lo CC RANAP_M5Report.lo CC RANAP_M5-Period.lo CC RANAP_M6Report.lo CC RANAP_M6-Period.lo CC RANAP_M7Report.lo CC RANAP_M7-Period.lo CC RANAP_Management-Based-MDT-Allowed.lo CC RANAP_MaxBitrate.lo CC RANAP_MaxSDU-Size.lo CC RANAP_MBMS-PTP-RAB-ID.lo CC RANAP_MBMSBearerServiceType.lo CC RANAP_MBMSCNDe-Registration.lo CC RANAP_MBMSCountingInformation.lo CC RANAP_MBMSHCIndicator.lo CC RANAP_MBMSIPMulticastAddressandAPNRequest.lo CC RANAP_MBMSLinkingInformation.lo CC RANAP_MBMSRegistrationRequestType.lo CC RANAP_MBMSServiceArea.lo CC RANAP_MBMSSessionDuration.lo CC RANAP_MBMSSessionIdentity.lo CC RANAP_MBMSSessionRepetitionNumber.lo CC RANAP_MDT-Activation.lo CC RANAP_MDTAreaScope.lo CC RANAP_MDT-Configuration.lo CC RANAP_MDTMode.lo CC RANAP_MDT-PLMN-List.lo CC RANAP_MDT-Report-Parameters.lo CC RANAP_MeasurementQuantity.lo CC RANAP_MeasurementsToActivate.lo CC RANAP_MSISDN.lo CC RANAP_NAS-SequenceNumber.lo CC RANAP_NAS-PDU.lo CC RANAP_NAS-SynchronisationIndicator.lo CC RANAP_NewBSS-To-OldBSS-Information.lo CC RANAP_NonSearchingIndication.lo CC RANAP_NRTLoadInformationValue.lo CC RANAP_NumberOfIuInstances.lo CC RANAP_NumberOfSteps.lo CC RANAP_Offload-RAB-Parameters.lo CC RANAP_Offload-RAB-Parameters-APN.lo CC RANAP_Offload-RAB-Parameters-ChargingCharacteristics.lo CC RANAP_OldBSS-ToNewBSS-Information.lo CC RANAP_OMC-ID.lo CC RANAP_Out-Of-UTRAN.lo CC RANAP_PagingAreaID.lo CC RANAP_PagingCause.lo CC RANAP_PDP-TypeInformation.lo CC RANAP_PDP-Type.lo CC RANAP_PDP-TypeInformation-extension.lo CC RANAP_PDP-Type-extension.lo CC RANAP_PDUType14FrameSequenceNumber.lo CC RANAP_PeriodicLocationInfo.lo CC RANAP_PermanentNAS-UE-ID.lo CC RANAP_PermittedEncryptionAlgorithms.lo CC RANAP_PermittedIntegrityProtectionAlgorithms.lo CC RANAP_LABased.lo CC RANAP_LAI-List.lo CC RANAP_LoggedMDT.lo CC RANAP_LoggingInterval.lo CC RANAP_LoggingDuration.lo CC RANAP_PLMNidentity.lo CC RANAP_PLMNs-in-shared-network.lo CC RANAP_Port-Number.lo CC RANAP_PositioningDataDiscriminator.lo CC RANAP_PositioningDataSet.lo CC RANAP_PositioningMethodAndUsage.lo In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SEQUENCE_OF.h:8:0, from ../../include/osmocom/ranap/RANAP_PLMNs-in-shared-network.h:14, from RANAP_PLMNs-in-shared-network.c:7: ../../include/osmocom/ranap/RANAP_LA-LIST.h:27:23: warning: ‘struct MemberA’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct MemberA { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_LA-LIST.h:27:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct MemberA { ^~~~~~~~~~~~~ ../../include/osmocom/ranap/RANAP_PLMNs-in-shared-network.h:27:23: warning: ‘struct MemberM’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct MemberM { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_PLMNs-in-shared-network.h:27:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct MemberM { ^~~~~~~~~~~~~ CC RANAP_PositioningPriority.lo CC RANAP_PositionData.lo CC RANAP_PositionDataSpecificToGERANIuMode.lo CC RANAP_Pre-emptionCapability.lo CC RANAP_Pre-emptionVulnerability.lo CC RANAP_PriorityLevel.lo CC RANAP_Priority-Class-Indicator.lo CC RANAP_ProvidedData.lo CC RANAP_P-TMSI.lo /bin/bash: line 1: 2491 Illegal instruction /bin/bash ../../libtool --silent --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"osmo-iuh\" -DPACKAGE_TARNAME=\"osmo-iuh\" -DPACKAGE_VERSION=\"0.3.0.13-45696\" -DPACKAGE_STRING=\"osmo-iuh\ 0.3.0.13-45696\" -DPACKAGE_BUGREPORT=\"openbsc(a)lists.osmocom.org\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DPACKAGE=\"osmo-iuh\" -DVERSION=\"0.3.0.13-45696\" -DSTDC_HEADERS=1 -I. -Wall -I../../include -I/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/ -I/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c -I/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/ -g -O2 -Wall -MT RANAP_PriorityLevel.lo -MD -MP -MF .deps/RANAP_PriorityLevel.Tpo -c -o RANAP_PriorityLevel.lo RANAP_PriorityLevel.c Makefile:2506: recipe for target 'RANAP_PriorityLevel.lo' failed make[4]: *** [RANAP_PriorityLevel.lo] Error 132 make[4]: *** Waiting for unfinished jobs.... In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SEQUENCE_OF.h:8:0, from ../../include/osmocom/ranap/RANAP_PLMNs-in-shared-network.h:14, from ../../include/osmocom/ranap/RANAP_Shared-Network-Information.h:14, from ../../include/osmocom/ranap/RANAP_ProvidedData.h:14, from RANAP_ProvidedData.c:7: ../../include/osmocom/ranap/RANAP_LA-LIST.h:27:23: warning: ‘struct MemberA’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct MemberA { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_LA-LIST.h:27:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct MemberA { ^~~~~~~~~~~~~ ../../include/osmocom/ranap/RANAP_PLMNs-in-shared-network.h:27:23: warning: ‘struct MemberM’ declared inside parameter list will not be visible outside of this definition or declaration A_SEQUENCE_OF(struct MemberM { ^ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/asn1c/asn_SET_OF.h:17:16: note: in definition of macro ‘A_SET_OF’ void (*free)(type *); \ ^~~~ ../../include/osmocom/ranap/RANAP_PLMNs-in-shared-network.h:27:2: note: in expansion of macro ‘A_SEQUENCE_OF’ A_SEQUENCE_OF(struct MemberM { ^~~~~~~~~~~~~ make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-iuh/src/ranap' Makefile:642: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-iuh/src' Makefile:454: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-iuh/src' Makefile:458: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-iuh' Makefile:382: recipe for target 'all' failed make: *** [all] Error 2 [WARNING] Build command ./build_Osmocom.sh exited with code 2. Please verify that the build completed successfully. Emitted 1161 C/C++ compilation units (100%) successfully 1161 C/C++ compilation units (100%) are ready for analysis For more details, please look at: /home/osmocom-build/osmo-ci/coverity/source-Osmocom/cov-int/build-log.txt Build step 'Execute shell' marked build as failure

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2019