April 2020 - OpenBSC - lists.osmocom.org

GSM Silent call
by samir 04 May '26

04 May '26

Hi, I have read that silent-calls in GSM can be used to make a call to a target MS and listen to it without having the target knowing it. Is this theoretically possible ? If yes, can it be done in OpenBSC ?

4 3

SMS: UCS-2 concatenation with UTF16 emoticons
by Keith 26 Apr '26

26 Apr '26

Hi all, I noticed that SMS with emoticons on the boundary of the concatenated segments are not displaying correctly on the destination handset. * - imagine the disaster when that kiss-blowing smiley face thing at the end of your SMS turns out as a diamond with a ? for the recpipient! OMG, the potential butterfly effect is too much to think about... :)) So... This is my analysis: We have 140 bytes for the message, less the 6 bytes for the user header data in the case of concatenated SMS , leaving 134 bytes. It's well know that this means 67 characters per segment for an SMS using UCS-2 encoding. But, it we fill the message with emoticons that are using 4 bytes per 'character', then we have space for 134/4 = 33 and a half. Ooops. Still, the destination handset should reassemble the message and stick the two "halves" of the emoticon together, right? - except I'm not observing this. To rule out us doing something wrong in osmo, I wonder might somebody else (who has an unlimited SMS package) from a commercial provider try sending some crafted SM from one emoji-enabled phone to another, something like this: 😱abcdefghijklmnopqrstuvwxyz123456789abcdefghijklmnopqrstuvwxyz123😱56789 That's likely going to get mangled by mailing list or your mua, so it is: [4 byte emoji]abcdefghijklmnopqrstuvwxyz123456789abcdefghijklmnopqrstuvwxyz123[4 byte emoji]56789 You could also try various messages filled with emojis. Of course, if you bring up your osmo network with SMPP-mirror you can watch the trace in wireshark, you'll see when the last emoji gets chopped in two. You could try the same message on osmo and your commerical network. If it's actually a problem of the phones, you should get [4 byte emoji]abcdefghijklmnopqrstuvwxyz123456789abcdefghijklmnopqrstuvwxyz123[two diamonds with ?]56789 Thanks! Keith.

6 7

ip.access nano 3G S8 Configuration
by John Thewlis - Meath Broadband 20 Apr '26

20 Apr '26

We are trying to setup this AP as part of the 3.5G Osmocom project. We have the software stack operational and are now preparing the nano for testing. When we try to login via telnet at port 8090 we are getting a constant refusal to connect:- root@osm/openbsc/openbsc/src/ipaccess# telnet 192.168.192.30 8090 Trying 192.168.192.30... telnet: Unable to connect to remote host: Connection refused The device seems to be locked as indicated by the leds on the front panel. We have tried resetting the nano to see if this would help but to no avail. Any ideas as to how to access the device for initial configuration?. Thanks John

7 7

Need nano3G (S8 - Model 237A)
by Akib Sayyed 16 Apr '26

16 Apr '26

Dear List I am extremely sorry for off the topic question. I am willing to buy nano3G Nodeb. Is anyone in list have spare which can be sold. Please let me know. -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

8 10

Splitting out M3UA and MTP3 out of Open BSC into a separate library
by Arran Cudbard-Bell 15 Apr '26

15 Apr '26

Hi, Developing a module for FreeRADIUS to support EAP-SIM and EAP-AKA authentication against a HLR. The HLR we were targeting only supported a SCTP/M3UA/SCCP/TCAP/MAP stack, so we couldn't use SUA. Ripping the M3UA/MTP3 code out of OpenBSC worked surprisingly well. We ended up running the event loop in a separate thread to work around the threading issues. Unfortunately the HLR implements the ANSI variant of everything, whereas OpenBSC and supporting libraries seem to have been written to be compatible with the ITU standards. ...but the differences are fairly minor at MTP3 and SCCP layers, and i've started work on a patchset for libosmo-sccp. https://gerrit.osmocom.org/#/c/73/ Anyway, trying to gauge interest in splitting those layers out of Open BSC into a separate library, would be happy to take on M2UA as well for consistency. It would almost certainly get more projects using the code. There's very little out there even in Perl land for working with SS7. Thanks, -Arran Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

9 9

[PATCH 4/4] core/conv: Add optimized Viterbi decoding
by Vadim Yanitskiy 15 Apr '26

15 Apr '26

Hi Tom and all, After a quick look at the 4th patch, related to your optimized Viterbi decoder, I have noticed that currently the convolutional code definitions from the 'src/gsm/gsm0503_conv.c' are out of the 'tests/conv' test coverage... So, I would like to extend the test coverage. All I need are the test vectors, which I'll add to existing ones. Some of them I already found in your 4th patch, but some pending I need to write myself. Right now I have a simple question... Let's look at one example: { .name = "GSM RACH (non-recursive, flushed, not punctured)", .code = &gsm_conv_rach, .in_len = 14, .out_len = 36, // ??? .has_vec = 0, .vec_in = { }, .vec_out = { }, } As I noticed, the 'in_len' may be taken from the code definition: const struct osmo_conv_code gsm0503_rach = { .N = 2, .K = 5, .len = 14, // The 'in_len' is here! .next_output = xcch_output, .next_state = xcch_state, }; But I don't know how to calculate the 'out_len'... Could you please give me some hint? I already started to work on your 4th patch: https://gerrit.osmocom.org/1542 https://gerrit.osmocom.org/1543 With best regards, Vadim Yanitskiy.

2 2

Video Recordings of OsmoCon 2017
by Harald Welte 09 Feb '26

09 Feb '26

Hi all, the Osmocom Conference 2017 last week was an overwhelming success. We received lots of positive feedback from all sides. Thanks to all the speakers, to the attendees as well as to the anonymous sponsor of the travel grant funds. It is my great pleasure that due to the great support by C3VOC (The CCC Video Operation Center), we have full recordings of all talks given at OsmoCon 2017. You can find the videos on the C3VOC site at https://media.ccc.de/search/?q=osmocon They are also linked individually from the OsmoCon 2017 homepage at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017 I hope the video recordings will be of help for everyone who could not make it to the event in person. We will also be collecting the slides and put them up on the wiki during the next few days. Please don't hesitate to raise any feedback and/or questions. Technical feedback/questions regarding Osmocom software / projects should be addressed to the appropriate mailing lists, such as openbsc(a)lists.osmocom.org. Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de. Looking forward to the next OsmoCon, which we'll expect to be spanning ore than just a single day. 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 2

GPRS - local and foreign TLLIs
by Luca Melette 04 Feb '26

04 Feb '26

Hello everybody, after setting up a nanoBTS with OpenBSC/SGSN/GGSN, I had some troubles trying to connect my smartphone to the GPRS cell. Investigating the BTS-to-SGSN traffic, I saw that the frames sent by the SGSN were all marked with the same N(U) value (at LLC layer), the value was 0. With some debug, I found that the there was a mismatch in the TLLI storage, used to keep the status of attached terminals. The mentioned code is contained in gprs_llc.c, involving LL Entity functions and gprs_llc_tx_ui(). /* look-up or create the LL Entity for this (TLLI, SAPI) tuple */ lle = lle_by_tlli_sapi(msgb_tlli(msg), sapi); if (!lle) { struct gprs_llc_llme *llme; LOGP(DLLC, LOGL_ERROR, "LLC TX: unknown TLLI 0x%08x, " "creating LLME on the fly\n", msgb_tlli(msg)); llme = llme_alloc(msgb_tlli(msg)); lle = &llme->lle[sapi]; } The TX function uses the previously received TLLI to lookup for the LLE. The lle_by_tlli_sapi() performs the search, but preliminary it applies a foreign2local TLLI conversion to ensure to have a local one. Since no valid entry for the searched TLLI is found, a new one is created. And the problem is here. The new entry has the foreign TLLI. Next time the lookup fails again, and a new entry is created. This way, the counter N(U) is always reset, and the mobile do not recognize the message sequence and no attach is possible. My question is about foreign and local TLLIs. I patched the lookup, avoiding the conversion, so that the LLE is found and everything works fine... but... What is the sense of the conversion? Should the TLLI be always stored as a local one? Can this problem be solved with another foreign2local while allocating new entries? Actually, my problem has been solved with that workaround. But I'm curious to know what is the right way. Hope somebody can answer :) Thanks. Cheers, LM

5 6

OsmoNITB timeslots configuration and UmTRX
by Родион Гадыршин 27 Jan '26

27 Jan '26

Hello, list. I have umtrx v2.1 and I have already built GSM and GPRS components. Now I want to know which way of configuring timeslots in osmobsc.cfn is the best. I want GPRS, calls and SMS work. My current configuration is: timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 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 PDCH hopping enabled 0 timeslot 5 phys_chan_config PDCH hopping enabled 0 timeslot 6 phys_chan_config PDCH hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 Is there a better way to configure? Maybe better use TCH/F_TCH/H_PDCH, but I have heard, that TCH/F is currently not working in dynamic configurations - only TCH/H does. And there is no only TCH/H_PDCH mode. So, could you please give me an advice?

3 2

On the use of 'decmatch' in TTCN-3
by Harald Welte 27 Jan '26

27 Jan '26

Hi, I know that TTCN-3 is still new to a lot of you, but we are writing tons of integration testing against the various osmocom programs in it. It is quite amazing technology, and I would like to ask you to bear with me reading this mail :) Pau was stating the question earlier today on not finding an example on how to use decmatch. Indeed, it took me some months to find that gem in the TTCN-3 world. It solves the problem that you often have during test of layered protocol stacks: you have separate encoders/decoders for each protocol layer, and now you want to match on some of the *inner* payload. So normally, you have some kind of header definition + a binary (octetstring) payload. This happens in RSL with the L3_INFO IE, and just the same on BSSAP/DTAP where again the L3 message (for example call control) is encapsulated inside one information element. Now you have multiple options of addressing the problem: a) hand-written calls to the decoder function b) write na 'emulation' for the entire protocol layer c) use decmatch. a) would look like this (pseudo-code): var octetstring l3oct; var RSL_Message rsl RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, ?)) -> value rsl { var PDU_ML3_MS_NW l3 := dec_PDU_ML3_MS_NW(rsl.payload); if (match(l3, some_template)) { ... do something } ... } Which uses the built-in pattern-matching on the RSL port to match any message that matches the tr_RSL_DATA_REQ template, and stores the resulting RSL message in a variable. It then uses an explicit call to the decoder function of the L3 message, and then uses regular conditional expressions for further matching on that inner L3 payload. This is more or less how you would write in C, python or any other quite imperative programming languages. It's very verbose, time consuming and un-abstract/elegant. TTCN-3 has many declarative aspects to it. Code like the above is a waste of your time :) b) would mean that you implement some test component that handles the RSL messages on its bottom side test port, and the L3 messages on its top side test port. That is a possible way, and if you need a lot of state/logic of RSL, it maeks sense. But what if you really simply want to have a match? Then it would be a lot of effort and a large detour. c) decmatch to the rescue! You can write RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, decmatch tr_RRM_RR_STATUS)) which means: * do a receive on the RSL test port, and match on an incoming RSL message that matches the tr_RSL_DATA_REQ template, with channel number specified, link_id any (?), *and* if the octetstring payload, if decoded, matches the template tr_RRM_RR_STATUS ! This is *extremely* powerful and expressive. It allows you to condense complex, parametric template matching over multiple proocol layers. It would in the end match RSL DATA REQUEST, only if they contained a [valid] encoded RR STATUS. See https://gerrit.osmocom.org/6229 for the actual test case I used for the above examples. Please also note that I never had to even write the function name of the decoder (dec_PDU_ML3_MS_NW), but TTCN-3 *automatically* figures out which decoder function it must call in order to decode from the binary octetstring. Happy (TTCN-3) hacking + Osmocom bugfixing, 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 3

osmo-gsm-manuals in project repos: I see no .pdf
by Neels Hofmeyr 08 Jan '26

08 Jan '26

Hi Oliver, so I merged the stuff to add the manuals to the individual git repositories, since you said that it works. But when I do --enable-manuals I don't see any PDF files generated. Also a manual 'make pdf' says "nothing to be done". (I probably should have tried it before merging after all) So what am I doing wrong? Alternatively, can you fix it please? ~N

3 3

Pysim error: SW match failed
by Martin Nagy 16 Aug '25

16 Aug '25

Hi all, After buying a super Sim Kit (16 in 1) from China, I tried the reader (green PCB inside a blue transparent plastic case with a blue LED) and SIM (identified as a fakesupersim) with pysim tool. However i am getting the following error: /pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z 1234 -j 1 -t auto Insert card now (or CTRL-C to cancel) Autodetected card type fakemagicsim Generated card parameters : > Name : 26C3 > SMSP : e1ffffffffffffffffffffffff058100945555ffffffffffff000000 > ICCID : 8949262427518313026 > MCC/MNC : 262/42 > IMSI : 262422461512085 > Ki : 7b74741a1ee14337ec23f9ab92a13648 > OPC : ccd867d60797d8d45354a51b3ef568ff Programming ... Traceback (most recent call last): File "./pySim-prog.py", line 530, in <module> card.program(cp) File "/home/nadicek/pysim/pysim/pySim/cards.py", line 231, in program self._scc.update_binary('6f30', hplmn + 'ff' * (tl-3)) File "/home/nadicek/pysim/pysim/pySim/commands.py", line 53, in update_binary return self._tp.send_apdu_checksw(pdu) File "/home/nadicek/pysim/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1])) RuntimeError: SW match failed ! Expected 9000 and got 9804. I checked mailing lists and haven’t found anybody who had similar problem with pysim. Also I have tried forcing different models of SIM, but nothing is working. Obviously I can remove this check from the script file (__init__.py in /pySim/transport), however somebody had a reason to put such condition there. I would like to ask if it is safe to remove that line of code and the purpose of that line of code. Thanks a lot and best regards Martin

3 3

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

dynamic traffic channels
by Neels Hofmeyr 20 May '25

20 May '25

On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote: > [translated from german] > is it certain that we switch a channel to PDCH only when > gprs mode != none? A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we send a PDCH ACT message. We send a PDCH ACT message - during init (CHANNEL OML's state changed to enabled -> send PDCH ACT), - and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH. So the question is, when we receive a channel release ack, could that be the PDCH release and we switch PDCH right back on by accident? No, because we only receive a chan rel ack when the *TCH/F* is being released. That is because the PDCH release is initiated "internally" from the PDCH DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches on, which existed before dyn PDCH: if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) { LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n", gsm_lchan_name(lchan)); return 0; } In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but not in the rsl_rx_dyn_pdch(). This is analogous to the ip.access way -- the ip.access nanobts replies to a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel release ack. Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH for clarity? (But we shouldn't actually send a release ack, to stay compatible.) Even though it works as-is, we should indeed add another flag check: - We do check the flags that no ACT/DEACT is already pending; - And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE; - But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE. This should never happen, but it would make sense to ensure that. ~Neels

3 5

Problem while running NIB on Open Cellular Base sation
by Brackley Casinga 31 Jan '24

31 Jan '24

Hi, My name is Brackley Cassinga Form DRC, we run a community network called pamoja net where we offer gsm services using osmocom open source software and OC Base station. Recently I have tried to install another base station as the same installed but I could not find any resource guiding through all the steps to take to run NIB on a base station. I'm currently running Ubuntu and I will appreciate if you could guide me on the installation of BSC,hlr,MSC , in order to run a basic gsm network. Thank you. Regards -- *Ir Brackley heshima Casinga **Pacifique* *CEO and Founder of kwanzatechnologie* KwanzaTechnologies ,GlobalElectronics +243977265291 | +243977265291 | Pcassinga(a)gmail.com/ brackley(a)ensemblepourladifference.org www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> | Skype: Brackley cassinga <https://webapp.wisestamp.com/#> Av Semliki N 43

2 1

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

GSUP client
by Reza Hosseini 24 Apr '20

24 Apr '20

Dear Mr. Welte, In order to be more familiar with the further development of the osmo-euse file, I need to know which libraries and which programming style I should use to be on the right track. Is it possible to provide me please the some lines of your code which is sending the USSD code via the GSUP client to hlr and called up data from OSMO-HLR? I need this for my master's thesis (Education Purpose), so I don't need a license for it. Many thanks for your consideration, Reza

2 1

Fwd: OSMOCOM TRX_BTS_BSC Connection Issue
by Aalto Koskinen 22 Apr '20

22 Apr '20

Hi, I looked at the forum for answers before posting, but I unfortunately couldn't get answers to what I was looking for. I looked into particular https://www.mail-archive.com/openbsc@lists.osmocom.org/msg09819.html for solving my issue. Setup: USRP B210 as radio head. NITB modules as components for 2G Network and BTS-TRX and TRX-UHD modules. Issue: - TRX-UHD and BTS-TRX fail. NITB Module works. Components of NITB network are able to connect to each other. - I have the RSP POWEROFF message originating in log from TRX-UHD module and the BTS module is shuttiing down. - BTS connects via OML but fails to connect RSL. - As per the previous email archive, I wanted to login to VTY and check the logs, but, it logs out as the BTS module shuts down (I cannot connect and see what's happening). I looked through the configuration files and seem correct to me. Any suggestions would be appreciated on solving the issue. I am trying to create a test 2G OSMOCOM network. Logs are written below and configuration as attachments. Thanks for your help! *OSMO_BTS_TRX log:* systemd[1]: Started Osmocom osmo-bts for osmo-trx. osmo-bts-trx[23221]: <0017> control_if.c:911 CTRL at 127.0.0.1 4238 osmo-bts-trx[23221]: <0010> telnet_interface.c:104 Available via telnet 127.0.0.1 4241 osmo-bts-trx[23221]: <0012> input/ipaccess.c:1024 enabling ipaccess BTS mode, OML connecting to 192.168.0.9:3002 osmo-bts-trx[23221]: <000b> trx_if.c:1174 phy0.0: Open transceiver osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: <000d> abis.c:142 Signalling link down osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason Abis close osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF) osmo-bts-trx[23221]: Shutdown timer expired osmo-bts-trx[23221]: ((*)) osmo-bts-trx[23221]: | osmo-bts-trx[23221]: / \ OsmoBTS *OSMO_TRX_UHD log:* ubuntu-HP-EliteBook-8470p systemd[1]: Started Osmocom SDR BTS L1 Transceiver (UHD Backend). ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21 2020 DLGLOBAL <0007> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21 2020 DLCTRL <000e> control_if.c:911 CTRL at 127.0.0.1 4236 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21 2020 DMAIN <0000> osmo-trx.cpp:485 [tid=140554411180864] Config Settings ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Log Level............... 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Device args............. ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TRX Base Port........... 5700 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TRX Address............. 127.0.0.1 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: GSM BTS Address......... 127.0.0.1 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Channels................ 1 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Tx Samples-per-Symbol... 4 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Rx Samples-per-Symbol... 4 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: EDGE support............ 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Extended RACH support... 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Reference............... 1 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Filler Burst Type....... Empty bursts ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Filler Burst TSC........ 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Filler Burst RACH Delay. 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Multi-Carrier........... 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Tuning offset........... 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RSSI to dBm offset...... 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Swap channels........... 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Tx Antennas............. '<default>' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Rx Antennas............. '<default>' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21 2020 DMAIN <0000> osmo-trx.cpp:439 [tid=140554411180864] Setting SCHED_RR priority 18 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: [INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; UHD_3.14.1.1-release ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21 2020 DDEV <0005> UHDDevice.cpp:470 [tid=140554411180864] Using discovered UHD device type=b200,name=MyB210,serial=31A92EA,product=B210 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:22 2020 DDEVDRV <0006> b200_impl.cpp:386 [tid=140554300024576] [B200] Detected Device: B210 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:22 2020 DDEVDRV <0006> b200_impl.cpp:433 [tid=140554300024576] [B200] Operating over USB 2. ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:22 2020 DDEVDRV <0006> b200_impl.cpp:587 [tid=140554300024576] [B200] Initialize CODEC control... huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:650 [tid=140554300024576] [B200] Initialize Radio control... huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:957 [tid=140554300024576] [B200] Performing register loopback test... huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:966 [tid=140554300024576] [B200] Register loopback test passed huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:957 [tid=140554300024576] [B200] Performing register loopback test... huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:966 [tid=140554300024576] [B200] Register loopback test passed huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:758 [tid=140554300024576] [B200] Setting master clock rate selection to 'automatic'. huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:1013 [tid=140554300024576] [B200] Asking for clock rate 16.000000 MHz... huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:1024 [tid=140554300024576] [B200] Actually got clock rate 16.000000 MHz. huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DMAIN <0000> UHDDevice.cpp:214 [tid=140554411180864] Antennas configured successfully huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> multi_usrp.cpp:502 [tid=140554300024576] [MULTI_USRP] Setting master clock rate selection to 'manual'. huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:1013 [tid=140554300024576] [B200] Asking for clock rate 26.000000 MHz... ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEVDRV <0006> b200_impl.cpp:1024 [tid=140554300024576] [B200] Actually got clock rate 26.000000 MHz. ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEV <0005> UHDDevice.cpp:275 [tid=140554411180864] Rates configured for B210 4 SPS ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEV <0005> UHDDevice.cpp:235 [tid=140554411180864] Supported Tx gain range [0; 89.75] ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEV <0005> UHDDevice.cpp:240 [tid=140554411180864] Supported Rx gain range [0; 76] ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEV <0005> UHDDevice.cpp:244 [tid=140554411180864] Default setting Tx gain for channel 0 to 44.875 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEV <0005> UHDDevice.cpp:251 [tid=140554411180864] Default setting Rx gain for channel 0 to 38 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DDEV <0005> UHDDevice.cpp:569 [tid=140554411180864] Device configuration: Single USRP: ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Device: B-Series Device ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Mboard 0: B210 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX Channel: 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX DSP: 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX Dboard: A ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX Subdev: FE-RX2 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX Channel: 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX DSP: 0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX Dboard: A ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX Subdev: FE-TX2 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DMAIN <0000> Threads.cpp:119 [tid=140554180474624] Thread 140554180474624 (task 8317) set name: CtrlService0 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DMAIN <0000> osmo-trx.cpp:533 [tid=140554411180864] -- Transceiver active with 1 channel(s) ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:28 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:28 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:33 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:33 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:38 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:38 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:43 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:43 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:49 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:49 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:54 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:54 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:59 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:59 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0'

3 9

Asterisk - Osmosom connection issue
by Laurent Kza 21 Apr '20

21 Apr '20

Hi all, I am new to the use of the Osmocom project, it is indeed a very nice job. I am currently trying to set up a configuration with a Asterisk PBX server and I have 2 questions: 1/ RTP configuration The SIP part (sip-connector vs Asterisk connection) works well so far, the communication starts but with no audio. I noticed that the RTP flux is sent to localhost instead of my server address (set as remote in sip-connector.cfg) and I was wondering if there is any possibility to send the RTP flow to an address which is not localhost ? sip local 0.0.0.0 5069 remote 127.0.0.1 5060 2/ codec issue In a configuration where all the Osmocom servers (MSC, MGW, BSC…) and Asterisk are on the same machine, it got a message from my asterisk server, saying that no codec can be found to start a communication. By default, the wiki/manuals states that gsm has to be used but perhaps I am missing something in the BSC configuration, especially in the codec choice. <--- SIP read from UDP:10.184.10.162:5069 ---> INVITE sip:899@127.0.0.1:5060 SIP/2.0 Via: SIP/2.0/UDP 10.184.10.162:5069;rport;branch=z9hG4bKpe1UXZU1amUja Max-Forwards: 70 From: <sip:422@0.0.0.0:5069>;tag=vyQKX32r72ZyQ To: <sip:899@127.0.0.1:5060> Call-ID: cd65c5a0-fdbf-1238-51a9-000c29cfd753 CSeq: 949096397 INVITE Contact: <sip:10.184.10.162:5069> User-Agent: sofia-sip/1.12.11devel Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE Supported: timer, 100rel Content-Type: application/sdp Content-Length: 133 v=0 o=Osmocom 0 0 IN IP4 127.0.0.1 s=GSM Call c=IN IP4 127.0.0.1 t=0 0 m=audio 4016 RTP/AVP 3 a=rtpmap:3 GSM/8000 a=sendrecv <-------------> --- (13 headers 8 lines) --- Sending to 10.184.10.162:5069 (no NAT) Sending to 10.184.10.162:5069 (no NAT) Using INVITE request as basis request - cd65c5a0-fdbf-1238-51a9-000c29cfd753 No matching peer for '422' from '10.184.10.162:5069' == Using SIP RTP CoS mark 5 Got SDP version 0 and unique parts [Osmocom 0 IN IP4 127.0.0.1] Found RTP audio format 3 Found audio description format GSM for ID 3 [2020-04-20 17:38:19] NOTICE[14918][C-00000015]: chan_sip.c:10957 process_sdp: No compatible codecs, not accepting this offer! Thanks for your help Laurent

2 1

GSUP client
by Reza Hosseini 16 Apr '20

16 Apr '20

Hello Mr. Welte, I am writing to ask you please, if it is possible to provide me with documents on the GSUP Client program. I have to implement my own application and send the required GSUP messages to the HLR to get subscriber data from hlr in Osmocom. Many thanks for your considerations. Reza

2 1

pcsc_scan not reading
by michael schumi 15 Apr '20

15 Apr '20

i am trying to read the sim card using sim reader but not able to read i used command pcsc_scan but its taking huge time for scanning and only scanning waiting for the first reader... like this please check whats the issue

2 1

pysim contributions
by Sebastián Viviani 15 Apr '20

15 Apr '20

Hello, apologies for the generic question, but how can I contribute to the pysim project? I made a couple of fixes and added some stuff I needed for some tests, but looks like github rejects the pull requests, project is not listed in gerrit, there is no specific mail list, and the osmocom git repo rejects any push :-( Kind regards

2 1

open source mobile communications in the context of search and rescue
by Philipp Borgers 15 Apr '20

15 Apr '20

Hi, we are looking for some help creating open source mobile communication infrastructure in the context of a search and rescue (SAR) mission at sea. We would like to use the osmocom stack as sensing and communication infrastructure at sea. How precise is the timing advance for localization? Neels mentioned that "modern" mobile stations equipped with a GPS receiver can report the location to the operator. Could you point me to the right standard? Is there any reliable and open source tooling to determine the direction of the signal with multiple receivers (e.g. SDRs) in close proximity? You can find out more about the project here: https://www.hs-augsburg.de/searchwing/ Sorry for the mostly German content. Thanks for your help! Best Regards Philipp Borgers

2 1

debug call failure on new nitb setup please?
by Craig Comstock 14 Apr '20

14 Apr '20

Hi, I am setting up a nitb/nano3g right now and have the basics working with the nano3g talking to hnbgw and services running on my nitb box (rpi 3-something). I have two of the same phones: ZTE Obsidian with Android 5.1 which are able to connect to my network. When I try to call the other phone I don't get connected. It takes about 1 minute for the call to fail. Once the phone mentioned some problem with "access configuration for normal calls". Attached are my configs and logs from nano3g trace log and hnbgw journal during a failed call. Any help would be appreciated. I am sure I did something obviously wrong. I'll try and read the configs carefully to make sure that matches with what is up on the wiki. Thanks, Craig

4 4

Hello
by Reza Hosseini 14 Apr '20

14 Apr '20

Dear Developers, I am trying to build the osmo-euse-demo on the Osmocom VM, executing the following commands: #Install required development libraries: sudo apt-get install libosmo-gsup-client-dev #Get the source code and a missing header file wget https://raw.githubusercontent.com/osmocom/osmo-hlr/master/src/osmo-euse-dem… wget https://raw.githubusercontent.com/osmocom/osmo-hlr/master/include/osmocom/h… mkdir -p osmocom/hlr/ mv logging.h osmocom/hlr/ #Compile source gcc -I. -o osmo-euse-demo osmo-euse-demo.c -losmocore -losmo-gsup-client -losmogsm -ltalloc #Run ./osmo-euse-demo But i am now facing this error : E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? Can you please tell me what is the reasin behind this error !? And how can i solve it ? Many thanks for your consideraion, Reza

2 1

OsmoSTP connection
by Igor Kim 08 Apr '20

08 Apr '20

Hello dears! I try to connect 2 STPs to each other via Sigtran M3UA protocol. But I don't understand, why my connection is fault. Could you please check my configuration? STP1 STP2 point-code 0.12.4 point-code 0.12.4 port 2905 port 2906 IP 172.18.141.1 IP 172.18.142.2 Me configuration is: STP1 cs7 instance 1 network-indicator reserved point-code 0.12.4 asp stp2 2906 2905 m3ua local-ip 172.18.141.1 remote-ip 172.18.142.2 role asp sctp-role client as stp2 m3ua asp stp2 traffic-mode override routing-key 0 0.25.0 route-table system STP2 cs7 instance 1 network-indicator reserved point-code 0.25.0 asp stp1 2905 2906 m3ua local-ip 172.18.142.2 remote-ip 172.18.141.1 role sg as stp1 m3ua asp stp1 traffic-mode override routing-key 0 0.12.4 route-table system listen m3ua 2906 accept-asp-connections dynamic-permitted Thanks in advance!

2 1

“osmo-euse-demo.c“
by Reza Hosseini 08 Apr '20

08 Apr '20

Dera Developers, I am trying to make the “osmo-euse-demo.c“ file to execute it Ubuntu in order to demonstrate the core Network vulnerebalities. But in this Phase i’m facing the following error. Can you please tell me how can i solve this error. Or how can i have Access to the already maked file of “osmo-euse-demo.c“ to execute it . Kind Regards, Reza root@reza-VirtualBox:/home/reza/osmocom/include# cc -v -I/home/reza/osmocom/include osmo-euse-demo.c Using built-in specs. COLLECT_GCC=cc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.5.0-3ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/7/cc1 -quiet -v -I /home/reza/osmocom/include -imultiarch x86_64-linux-gnu osmo-euse-demo.c -quiet -dumpbase osmo-euse-demo.c -mtune=generic -march=x86-64 -auxbase osmo-euse-demo -version -fstack-protector-strong -Wformat -Wformat-security -o /tmp/ccz56pXg.s GNU C11 (Ubuntu 7.5.0-3ubuntu1~18.04) version 7.5.0 (x86_64-linux-gnu) compiled by GNU C version 7.5.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu" ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/7/../../../../x86_64-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /home/reza/osmocom/include /usr/lib/gcc/x86_64-linux-gnu/7/include /usr/local/include /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed /usr/include/x86_64-linux-gnu /usr/include End of search list. GNU C11 (Ubuntu 7.5.0-3ubuntu1~18.04) version 7.5.0 (x86_64-linux-gnu) compiled by GNU C version 7.5.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: b62ed4a2880cd4159476ea8293b72fa8 COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-mtune=generic' '-march=x86-64' as -v -I /home/reza/osmocom/include --64 -o /tmp/ccRIXQie.o /tmp/ccz56pXg.s GNU assembler version 2.30 (x86_64-linux-gnu) using BFD version (GNU Binutils for Ubuntu) 2.30 COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/ LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/7/collect2 -plugin /usr/lib/gcc/x86_64-linux-gnu/7/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper -plugin-opt=-fresolution=/tmp/ccu0YtNb.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker /lib64/ld-linux-x86-64.so.2 -pie -z now -z relro /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/Scrt1.o /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/7/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/7/../../.. /tmp/ccRIXQie.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/7/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/crtn.o /tmp/ccRIXQie.o: In function `osmo_gsup_message_type_name': osmo-euse-demo.c:(.text+0x36): undefined reference to `osmo_gsup_message_type_names' osmo-euse-demo.c:(.text+0x3b): undefined reference to `get_value_string' /tmp/ccRIXQie.o: In function `osmo_gsup_session_state_name': osmo-euse-demo.c:(.text+0x54): undefined reference to `osmo_gsup_session_state_names' osmo-euse-demo.c:(.text+0x59): undefined reference to `get_value_string' /tmp/ccRIXQie.o: In function `gsm0480_op_code_name': osmo-euse-demo.c:(.text+0x75): undefined reference to `gsm0480_op_code_names' osmo-euse-demo.c:(.text+0x7a): undefined reference to `get_value_string' /tmp/ccRIXQie.o: In function `euse_tx_ss': osmo-euse-demo.c:(.text+0xf4): undefined reference to `msgb_free' osmo-euse-demo.c:(.text+0x12d): undefined reference to `osmo_strlcpy' osmo-euse-demo.c:(.text+0x171): undefined reference to `msgb_data' osmo-euse-demo.c:(.text+0x187): undefined reference to `msgb_length' osmo-euse-demo.c:(.text+0x19d): undefined reference to `gsm0480_msgb_alloc_name' osmo-euse-demo.c:(.text+0x1d2): undefined reference to `osmo_panic' osmo-euse-demo.c:(.text+0x1eb): undefined reference to `osmo_gsup_encode' osmo-euse-demo.c:(.text+0x1fa): undefined reference to `msgb_free' osmo-euse-demo.c:(.text+0x213): undefined reference to `osmo_gsup_client_send' /tmp/ccRIXQie.o: In function `euse_tx_ussd_reject': osmo-euse-demo.c:(.text+0x261): undefined reference to `gsm0480_gen_reject' osmo-euse-demo.c:(.text+0x274): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x2be): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x2ed): undefined reference to `osmo_panic' /tmp/ccRIXQie.o: In function `euse_tx_ussd_resp_7bit': osmo-euse-demo.c:(.text+0x34a): undefined reference to `gsm0480_gen_ussd_resp_7bit' osmo-euse-demo.c:(.text+0x35d): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x3b8): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x3e7): undefined reference to `osmo_panic' /tmp/ccRIXQie.o: In function `euse_rx_proc_ss_req': osmo-euse-demo.c:(.text+0x4b9): undefined reference to `gsm0480_parse_facility_ie' osmo-euse-demo.c:(.text+0x509): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x595): undefined reference to `logp2' /tmp/ccRIXQie.o: In function `gsupc_read_cb': osmo-euse-demo.c:(.text+0x6e3): undefined reference to `osmo_gsup_decode' osmo-euse-demo.c:(.text+0x701): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x714): undefined reference to `msgb_hexdump' osmo-euse-demo.c:(.text+0x746): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x764): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x777): undefined reference to `msgb_hexdump' osmo-euse-demo.c:(.text+0x7b6): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x7f9): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x83c): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x855): undefined reference to `msgb_free' /tmp/ccRIXQie.o: In function `main': osmo-euse-demo.c:(.text+0x8bd): undefined reference to `talloc_named_const' osmo-euse-demo.c:(.text+0x8d4): undefined reference to `osmo_init_logging2' osmo-euse-demo.c:(.text+0x98c): undefined reference to `osmo_gsup_client_create' osmo-euse-demo.c:(.text+0x99d): undefined reference to `osmo_select_main' collect2: error: ld returned 1 exit status root@reza-VirtualBox:/home/reza/osmocom/include# cc -v -I/home/reza/osmocom/include osmo-euse-demo.c -o osmosample Using built-in specs. COLLECT_GCC=cc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.5.0-3ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-o' 'osmosample' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/7/cc1 -quiet -v -I /home/reza/osmocom/include -imultiarch x86_64-linux-gnu osmo-euse-demo.c -quiet -dumpbase osmo-euse-demo.c -mtune=generic -march=x86-64 -auxbase osmo-euse-demo -version -fstack-protector-strong -Wformat -Wformat-security -o /tmp/ccHY0eog.s GNU C11 (Ubuntu 7.5.0-3ubuntu1~18.04) version 7.5.0 (x86_64-linux-gnu) compiled by GNU C version 7.5.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu" ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/7/../../../../x86_64-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /home/reza/osmocom/include /usr/lib/gcc/x86_64-linux-gnu/7/include /usr/local/include /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed /usr/include/x86_64-linux-gnu /usr/include End of search list. GNU C11 (Ubuntu 7.5.0-3ubuntu1~18.04) version 7.5.0 (x86_64-linux-gnu) compiled by GNU C version 7.5.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: b62ed4a2880cd4159476ea8293b72fa8 COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-o' 'osmosample' '-mtune=generic' '-march=x86-64' as -v -I /home/reza/osmocom/include --64 -o /tmp/cciVuWmr.o /tmp/ccHY0eog.s GNU assembler version 2.30 (x86_64-linux-gnu) using BFD version (GNU Binutils for Ubuntu) 2.30 COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/ LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-o' 'osmosample' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/7/collect2 -plugin /usr/lib/gcc/x86_64-linux-gnu/7/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper -plugin-opt=-fresolution=/tmp/ccDFZPnC.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker /lib64/ld-linux-x86-64.so.2 -pie -z now -z relro -o osmosample /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/Scrt1.o /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/7/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/7/../../.. /tmp/cciVuWmr.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/7/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/crtn.o /tmp/cciVuWmr.o: In function `osmo_gsup_message_type_name': osmo-euse-demo.c:(.text+0x36): undefined reference to `osmo_gsup_message_type_names' osmo-euse-demo.c:(.text+0x3b): undefined reference to `get_value_string' /tmp/cciVuWmr.o: In function `osmo_gsup_session_state_name': osmo-euse-demo.c:(.text+0x54): undefined reference to `osmo_gsup_session_state_names' osmo-euse-demo.c:(.text+0x59): undefined reference to `get_value_string' /tmp/cciVuWmr.o: In function `gsm0480_op_code_name': osmo-euse-demo.c:(.text+0x75): undefined reference to `gsm0480_op_code_names' osmo-euse-demo.c:(.text+0x7a): undefined reference to `get_value_string' /tmp/cciVuWmr.o: In function `euse_tx_ss': osmo-euse-demo.c:(.text+0xf4): undefined reference to `msgb_free' osmo-euse-demo.c:(.text+0x12d): undefined reference to `osmo_strlcpy' osmo-euse-demo.c:(.text+0x171): undefined reference to `msgb_data' osmo-euse-demo.c:(.text+0x187): undefined reference to `msgb_length' osmo-euse-demo.c:(.text+0x19d): undefined reference to `gsm0480_msgb_alloc_name' osmo-euse-demo.c:(.text+0x1d2): undefined reference to `osmo_panic' osmo-euse-demo.c:(.text+0x1eb): undefined reference to `osmo_gsup_encode' osmo-euse-demo.c:(.text+0x1fa): undefined reference to `msgb_free' osmo-euse-demo.c:(.text+0x213): undefined reference to `osmo_gsup_client_send' /tmp/cciVuWmr.o: In function `euse_tx_ussd_reject': osmo-euse-demo.c:(.text+0x261): undefined reference to `gsm0480_gen_reject' osmo-euse-demo.c:(.text+0x274): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x2be): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x2ed): undefined reference to `osmo_panic' /tmp/cciVuWmr.o: In function `euse_tx_ussd_resp_7bit': osmo-euse-demo.c:(.text+0x34a): undefined reference to `gsm0480_gen_ussd_resp_7bit' osmo-euse-demo.c:(.text+0x35d): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x3b8): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x3e7): undefined reference to `osmo_panic' /tmp/cciVuWmr.o: In function `euse_rx_proc_ss_req': osmo-euse-demo.c:(.text+0x4b9): undefined reference to `gsm0480_parse_facility_ie' osmo-euse-demo.c:(.text+0x509): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x595): undefined reference to `logp2' /tmp/cciVuWmr.o: In function `gsupc_read_cb': osmo-euse-demo.c:(.text+0x6e3): undefined reference to `osmo_gsup_decode' osmo-euse-demo.c:(.text+0x701): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x714): undefined reference to `msgb_hexdump' osmo-euse-demo.c:(.text+0x746): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x764): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x777): undefined reference to `msgb_hexdump' osmo-euse-demo.c:(.text+0x7b6): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x7f9): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x83c): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x855): undefined reference to `msgb_free' /tmp/cciVuWmr.o: In function `main': osmo-euse-demo.c:(.text+0x8bd): undefined reference to `talloc_named_const' osmo-euse-demo.c:(.text+0x8d4): undefined reference to `osmo_init_logging2' osmo-euse-demo.c:(.text+0x98c): undefined reference to `osmo_gsup_client_create' osmo-euse-demo.c:(.text+0x99d): undefined reference to `osmo_select_main' collect2: error: ld returned 1 exit status root@reza-VirtualBox:/home/reza/osmocom/include# vim osmo osmocom/ osmo-euse-demo.c root@reza-VirtualBox:/home/reza/osmocom/include# vim osmo osmocom/ osmo-euse-demo.c root@reza-VirtualBox:/home/reza/osmocom/include# vim osmo osmocom/ osmo-euse-demo.c root@reza-VirtualBox:/home/reza/osmocom/include# cc -v -I/home/reza/osmocom/include osmo-euse-demo.c -o osmosamplemc Using built-in specs. COLLECT_GCC=cc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.5.0-3ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-o' 'osmosamplemc' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/7/cc1 -quiet -v -I /home/reza/osmocom/include -imultiarch x86_64-linux-gnu osmo-euse-demo.c -quiet -dumpbase osmo-euse-demo.c -mtune=generic -march=x86-64 -auxbase osmo-euse-demo -version -fstack-protector-strong -Wformat -Wformat-security -o /tmp/cciw60w9.s GNU C11 (Ubuntu 7.5.0-3ubuntu1~18.04) version 7.5.0 (x86_64-linux-gnu) compiled by GNU C version 7.5.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu" ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/7/../../../../x86_64-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /home/reza/osmocom/include /usr/lib/gcc/x86_64-linux-gnu/7/include /usr/local/include /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed /usr/include/x86_64-linux-gnu /usr/include End of search list. GNU C11 (Ubuntu 7.5.0-3ubuntu1~18.04) version 7.5.0 (x86_64-linux-gnu) compiled by GNU C version 7.5.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: b62ed4a2880cd4159476ea8293b72fa8 COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-o' 'osmosamplemc' '-mtune=generic' '-march=x86-64' as -v -I /home/reza/osmocom/include --64 -o /tmp/ccDvwYka.o /tmp/cciw60w9.s GNU assembler version 2.30 (x86_64-linux-gnu) using BFD version (GNU Binutils for Ubuntu) 2.30 COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/ LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-v' '-I' '/home/reza/osmocom/include' '-o' 'osmosamplemc' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/7/collect2 -plugin /usr/lib/gcc/x86_64-linux-gnu/7/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper -plugin-opt=-fresolution=/tmp/ccbULaab.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker /lib64/ld-linux-x86-64.so.2 -pie -z now -z relro -o osmosamplemc /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/Scrt1.o /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/7/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/7/../../.. /tmp/ccDvwYka.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/7/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/crtn.o /tmp/ccDvwYka.o: In function `osmo_gsup_message_type_name': osmo-euse-demo.c:(.text+0x36): undefined reference to `osmo_gsup_message_type_names' osmo-euse-demo.c:(.text+0x3b): undefined reference to `get_value_string' /tmp/ccDvwYka.o: In function `osmo_gsup_session_state_name': osmo-euse-demo.c:(.text+0x54): undefined reference to `osmo_gsup_session_state_names' osmo-euse-demo.c:(.text+0x59): undefined reference to `get_value_string' /tmp/ccDvwYka.o: In function `gsm0480_op_code_name': osmo-euse-demo.c:(.text+0x75): undefined reference to `gsm0480_op_code_names' osmo-euse-demo.c:(.text+0x7a): undefined reference to `get_value_string' /tmp/ccDvwYka.o: In function `euse_tx_ss': osmo-euse-demo.c:(.text+0xf4): undefined reference to `msgb_free' osmo-euse-demo.c:(.text+0x12d): undefined reference to `osmo_strlcpy' osmo-euse-demo.c:(.text+0x171): undefined reference to `msgb_data' osmo-euse-demo.c:(.text+0x187): undefined reference to `msgb_length' osmo-euse-demo.c:(.text+0x19d): undefined reference to `gsm0480_msgb_alloc_name' osmo-euse-demo.c:(.text+0x1d2): undefined reference to `osmo_panic' osmo-euse-demo.c:(.text+0x1eb): undefined reference to `osmo_gsup_encode' osmo-euse-demo.c:(.text+0x1fa): undefined reference to `msgb_free' osmo-euse-demo.c:(.text+0x213): undefined reference to `osmo_gsup_client_send' /tmp/ccDvwYka.o: In function `euse_tx_ussd_reject': osmo-euse-demo.c:(.text+0x261): undefined reference to `gsm0480_gen_reject' osmo-euse-demo.c:(.text+0x274): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x2be): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x2ed): undefined reference to `osmo_panic' /tmp/ccDvwYka.o: In function `euse_tx_ussd_resp_7bit': osmo-euse-demo.c:(.text+0x34a): undefined reference to `gsm0480_gen_ussd_resp_7bit' osmo-euse-demo.c:(.text+0x35d): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x3b8): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x3e7): undefined reference to `osmo_panic' /tmp/ccDvwYka.o: In function `euse_rx_proc_ss_req': osmo-euse-demo.c:(.text+0x4b9): undefined reference to `gsm0480_parse_facility_ie' osmo-euse-demo.c:(.text+0x509): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x595): undefined reference to `logp2' /tmp/ccDvwYka.o: In function `gsupc_read_cb': osmo-euse-demo.c:(.text+0x6e3): undefined reference to `osmo_gsup_decode' osmo-euse-demo.c:(.text+0x701): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x714): undefined reference to `msgb_hexdump' osmo-euse-demo.c:(.text+0x746): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x764): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x777): undefined reference to `msgb_hexdump' osmo-euse-demo.c:(.text+0x7b6): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x7f9): undefined reference to `log_check_level' osmo-euse-demo.c:(.text+0x83c): undefined reference to `logp2' osmo-euse-demo.c:(.text+0x855): undefined reference to `msgb_free' /tmp/ccDvwYka.o: In function `main': osmo-euse-demo.c:(.text+0x8bd): undefined reference to `talloc_named_const' osmo-euse-demo.c:(.text+0x8d4): undefined reference to `osmo_init_logging2' osmo-euse-demo.c:(.text+0x98c): undefined reference to `osmo_gsup_client_create' osmo-euse-demo.c:(.text+0x99d): undefined reference to `osmo_select_main' collect2: error: ld returned 1 exit status

2 1

OpenMSC: validity_minutes not set when sms is from SMPP + SMS not added in pending list.
by Denis Artru 07 Apr '20

07 Apr '20

Hello all, 1) When an SMS is received from SMPP, the validity_minutes is not set (value 0). The consequence is that email is deleted from database too early in case of failure. In file: src/libmsc/smpp_openbsc.c function submit_to_sms translate convert from submit_sm_t to gsm_sms. But some field of gsm_sms are not filled, in particularly validity_minutes. I think that validity_minutes must be computed from submit_sm_t.schedule_delivery_time or submit_sm_t.validity_period. Sorry I don’t know exactly content of these values. 2) In file src/libmsc/sms_queue.c function sub_ready_for_sm, before sending SMS using the function gsm411_send_sms, the SMS is not place in pending list. Like it is done in functions sms_submit_pending and sms_send_next. The consequence is that when handset do a Location Updating Request, only one SMS is send if they are many SMS for this subscribers. Because in function sms_sms_cb call of pending = sms_find_pending(network->sms_queue, sig_sms->sms->id); will always return 0. I try the following fix and was working but I don’t know if it possible that an SMS was already in the list? + struct gsm_sms_queue *smsq = net->sms_queue; + struct gsm_sms_pending *pendingSms = sms_pending_from(smsq, sms); + if (!pendingSms) { + LOGP(DLSMS, LOGL_ERROR, + "Failed to create pending SMS entry.\n"); + sms_free(sms); + return 0; + } + llist_add_tail(&pendingSms->entry, &smsq->pending_sms); gsm411_send_sms(net, vsub, sms); return 0; } Thanks you, Denis

2 2

GSUP protocol
by Reza Hosseini 04 Apr '20

04 Apr '20

Dear Osmocom developpers, I already installed osmocomnitb and now i am trying to Show the core Network vulnerablites in Wireshark. In order to use existing Osmocom libraries for GSUP protocol processing and USSD coding / decoding, I have to use the file "osmo-hlr / src / osmo-euse-demo.c" in my osmocom directory, the " http: // git "contains. osmocom.org/osmo-hlr/tree/src/osmo-euse-demo.c "Pool. But i don’t find the following libarries to patch it. #include <string.h> #include <stdio.h> #include <errno.h> #include <signal.h> #include <osmocom/core/msgb.h> #include <osmocom/core/select.h> #include <osmocom/core/application.h> #include <osmocom/core/utils.h> #include <osmocom/core/logging.h> #include <osmocom/gsm/gsup.h> #include <osmocom/gsm/gsm0480.h> #include <osmocom/gsm/protocol/gsm_04_80.h> #include <osmocom/gsupclient/gsup_client.h> #include <osmocom/hlr/logging.h> How can i have Access to the .exe (already maked) of this library. Kind regads, Reza

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC April 2020