OpenBSC February 2018

openbsc@lists.osmocom.org

14 participants
30 discussions

osmo-nitb and osmo-bts-trx problems with voice, no connection (using LimeSDR)
by Norbertas Kremeris 14 Feb '18

14 Feb '18

Hello all, I have run into some problems while building and running osmo-nitb, osmo-bts-trx and osmo-trx on Ubuntu 16.04. I am trying to create a self-contained gsm network box. I have successfully built libosmocore, libosmo-abis, libosmo-netif, libosmo-sccp, openbsc, osmo-bts and osmo-trx all from git sources, and i am also using linux call router. All make checks pass corrently without issues. As for the SDR side, i am have the latest UHD, SoapySDR and SoapyUHD, and latest LimeSuite library for LimeSDR support. SMS send/receive works correctly without any issues. Calling, however, works neither with osmo-nitb as standalone, neither with osmo-nitb with -m parameter + LCR. when trying to call, the receiving phone rings, but when trying to answer it randomly either gets stuck and does not answer, drops the call instantly or actually takes the call (and the elapsed seconds counter starts counting), but all you can hear is random noises coming both from the calling and from receiving phones, while the calling phone still shows that the call has not been answered, as in still calling. this is the debug info from osmo-trx: <0000> rsl.c:606 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK <0011> lapd_core.c:920 Store content res. (dl=0xb668cec8) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=0, V(R)=1 (dl=0xb668cec8 state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=0, V(R)=1 (dl=0xb668cec8 state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=1, V(R)=2 (dl=0xb668cec8 state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=1, V(R)=2 (dl=0xb668cec8 state LAPD_STATE_MF_EST) <0000> rsl.c:1639 CRCX does not specify a remote IP <0000> rsl.c:1646 CRCX does not specify a remote port <0000> rsl.c:1650 speech mode: 16 <0000> rsl.c:1656 payload type: 3 <0000> rsl.c:1636 connect_ip 16777343 <0000> rsl.c:1643 connect_port 12405 <0000> rsl.c:1650 speech mode: 0 <0000> rsl.c:1656 payload type: 3 <0009> pcu_sock.c:668 PCU socket not connected, dropping message <0011> lapd_core.c:1556 N(S) sequence error: N(S)=2, V(R)=3 (dl=0xb668cec8 state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=2, V(R)=3 (dl=0xb668cec8 state LAPD_STATE_MF_EST) <0009> pcu_sock.c:668 PCU socket not connected, dropping message <0009> pcu_sock.c:668 PCU socket not connected, dropping message <0009> pcu_sock.c:668 PCU socket not connected, dropping message <0000> rsl.c:606 (bts=0,trx=0,ts=3,ss=0) Tx CHAN ACT ACK <000e> l1sap.c:96 RTP clock out of sync with lower layer: 2080 vs 160 (2291865->2291921) <0011> lapd_core.c:920 Store content res. (dl=0xb66a83dc) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=0, V(R)=1 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=0, V(R)=1 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <0000> rsl.c:1639 CRCX does not specify a remote IP <0000> rsl.c:1646 CRCX does not specify a remote port <0000> rsl.c:1650 speech mode: 16 <0000> rsl.c:1656 payload type: 3 <0011> lapd_core.c:1556 N(S) sequence error: N(S)=1, V(R)=2 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=1, V(R)=2 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=2, V(R)=3 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2292212->2292182) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=2, V(R)=3 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2292208->2292246) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2292246->2292212) <0000> rsl.c:1636 connect_ip 16777343 <0000> rsl.c:1643 connect_port 12917 <0000> rsl.c:1650 speech mode: 0 <0000> rsl.c:1656 payload type: 3 <0011> lapd_core.c:1556 N(S) sequence error: N(S)=3, V(R)=4 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <0011> lapd_core.c:1556 N(S) sequence error: N(S)=3, V(R)=4 (dl=0xb66a83dc state LAPD_STATE_MF_EST) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 2080 vs 160 (2292814->2292870) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2293165->2293131) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2293178->2293221) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2293221->2293191) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2293200->2293239) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2293239->2293204) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2293404->2293447) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2293447->2293417) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2293417->2293455) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2293455->2293421) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2293443->2293486) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2293486->2293456) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2293469->2293507) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2293507->2293473) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2293677->2293720) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594080 vs 160 (2293720->2293681) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2293789->2293832) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594080 vs 160 (2293832->2293794) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1760 vs 160 (2293967->2294014) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2294014->2293984) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2293989->2294027) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2294027->2293993) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2294240->2294283) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2294283->2294253) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2294257->2294296) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2294296->2294262) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2294262->2294305) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594080 vs 160 (2294305->2294266) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1760 vs 160 (2294283->2294331) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2294331->2294296) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 480 vs 160 (2294318->2294331) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2294335->2294374) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2294374->2294340) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2294409->2294452) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594080 vs 160 (2294452->2294413) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1760 vs 160 (2294929->2294976) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2294976->2294946) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2294951->2294989) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2294989->2294955) <0000> rsl.c:689 (bts=0,trx=0,ts=2,ss=0) Sending Connection Failure: cause = 0x01 <0011> lapdm.c:1144 ((nil)) RLL Message 'REL_REQ' received without LAPDm context. (sapi 0) <0000> rsl.c:1433 (bts=0,trx=0,ts=2,ss=0) Sending RTP delete indication: cause = Normal event, unspecified <0000> rsl.c:580 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2295705->2295748) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2295752->2295718) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2295817->2295860) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2295869->2295835) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2295960->2296003) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594400 vs 160 (2296003->2295973) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1440 vs 160 (2295978->2296016) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2296016->2295982) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 1600 vs 160 (2296030->2296073) <000e> l1sap.c:96 RTP clock out of sync with lower layer: 82594240 vs 160 (2296077->2296043) <0000> rsl.c:689 (bts=0,trx=0,ts=3,ss=0) Sending Connection Failure: cause = 0x01 <0011> lapdm.c:1144 ((nil)) RLL Message 'REL_REQ' received without LAPDm context. (sapi 0) <0000> rsl.c:1433 (bts=0,trx=0,ts=3,ss=0) Sending RTP delete indication: cause = Normal event, unspecified <0000> rsl.c:580 (bts=0,trx=0,ts=3,ss=0) Tx RF CHAN REL ACK osmo-nitb -c config.cfg -C -m -P <0004> abis_rsl.c:1852 BTS 0 CHAN RQD: reason: call re-establishment (ra=0x4f, neci=0x01, chreq_reason=0x02) <000a> bsc_api.c:415 Sending (bts=0,trx=0,ts=2,ss=0) ChanModify for speech: SPEECH_V1 on channel TCH_F <0004> abis_rsl.c:1852 BTS 0 CHAN RQD: reason: answer to paging (ra=0x27, neci=0x01, chreq_reason=0x01) <000a> bsc_api.c:415 Sending (bts=0,trx=0,ts=3,ss=0) ChanModify for speech: SPEECH_V1 on channel TCH_F <0004> abis_rsl.c:1358 (bts=0,trx=0,ts=2,ss=0) CONNECTION FAIL: RELEASING state ACTIVE CAUSE=0x01(Radio Link Failure) <0004> abis_rsl.c:1358 (bts=0,trx=0,ts=3,ss=0) CONNECTION FAIL: RELEASING state ACTIVE CAUSE=0x01(Radio Link Failure) versions of software: osmo-nitb --version OpenBSC version 1.0.0.14-98a2ba ~/Desktop/osmo/openbsc$ git log -1 commit 98a2ba4c57e95d2ce1e1e8147ea5a8d51788a191 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jan 10 22:25:17 2018 +0600 ((*)) | / \ OsmoBTS OsmoBTS version 0.7.0.77-54be ~/Desktop/osmo/osmo-bts$ git log -1 commit 54be46949e93e07e9e57b706388ebb832e5fad0a Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Fri Feb 9 12:08:38 2018 +0100 osmo trx: ~/Desktop/osmo/osmo-trx$ git log -1 commit 77ce99ac6720896f504a0581a5c57b2929a13cef Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Mon Feb 5 13:05:06 2018 +0100 older osmo-bts-trx does actually work at least somewhat, but then voice transmission stops after 10-20 seconds, or sometimes even after 4 minutes of talking, while . The older version is: commit 9982b95069c58a3cb9b97bb6bc75932db81886ad Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 24 18:42:30 2017 +0200 "OsmoBTS version 0.6.0.21-9982b-dirty" I would, however, like to use a newer, preferably the master branch version from git. Any help in dealing with this issue would be very greatly appreciated.

1 0

Warning: OsmoMSC config file / VTY changes
by Harald Welte 14 Feb '18

14 Feb '18

Dear all, please note that some obsolete VTY commands have been removed from osmo-msc last night,, so in case your configs are no longer parsed, have a look at the recent changes to doc/examples/osmo-msc/osmo-msc.cfg which will point you to: - auth policy closed - location updating reject cause 13 Those really serve no purpose at all in OsmoMSC anymore, and I think it's better to remove them completely rather than silently accept them for "compatibility reasons". This is of course debatable, if somebody has better suggestion. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

3G femtocells and core network in Python
by benoit michau 13 Feb '18

13 Feb '18

Dear osmocom people, here is a quick email to announce the initial release (or more exactly, an update) of the "corenet" application I have been working on those last months. It is basically a 3G and 4G core network, entirely written in Python: it handles 3G femtocells and 4G eNodeBs, and handsets connecting through them. The 3G part has been made possible thanks to the accelerate3g5 program of last year. I wanted also to thank the people running the osmocom community and the sysmocom company. More information is available here: https://osmocom.org/projects/cellular-infrastructure/wiki/Accelerate3g5_--_… And the application itself is available on github: https://github.com/mitshell/corenet/ Do not hesitate to test it and to provide any feedback. Benoit

1 0

spend time to properly separate handover 2?
by Neels Hofmeyr 13 Feb '18

13 Feb '18

I'm on the load-based handover patches: it is adding a second handover decision algorithm. What keeps slightly itching me about it is that it is not really cleanly separate from the first (current) handover algorithm. - For example, in the VTY, we have the 'handover algorithm (1|2)' command, and the 'handover *' namespace is shared between ho 1 and ho 2. So when I look at the VTY commands under 'handover', a considerable number of those apply only to handover algorithm 2, while some, like rxlev averaging window settings and similar, apply to both. (I marked the ho2 ones in the VTY docs, but still) - The patches also add penalty timers and ho failure counters in generic places. In ho algorithm 2, these penalty timers and failure counts are heeded and cause ho / assignment to be omitted if appropriate. Not so in ho1. The point being, if we add a third, fourth, fifth HO algo at some point, this would probably become a tad intransparent. I wonder now whether I should spend time on jolly's patches to more cleanly separate the two algorithms. For example, in the structs and code, more clearly set and apply the penalty timers and failure counts *only* if ho algo 2 is actually used, probably even moving all of it out to context structs only known within the ho2 code. (Otherwise, some code adds penalty timers which might never be looked at or cleaned up until the conn is discarded..) On the other hand, some shared concepts make sense to be re-used. If HO algo 3 (hypothetically) wants penalty timers as well, will separating merely amount to code dup? Do we want separate sets of parameters for ho1 and ho2? For example, for the rxlev window averaging, is it better to have one setting used for both ho1 and ho2, or do I expect each algo to remember its own rxlev averaging settings? The current patch state kind of throws both in one pot; I tried to put some struct members in a { }ho2 sub-struct, but it's a bit half-hearted. I'm deciding back and forth. Truly modularizing all of it would make for more code, like opaque struct pointers to store context, specific to each ho algorithm, at e.g. subscr_conn; and function callbacks to take actions in certain triggers (like setting a penalty timer for ho failure); fully separate VTY namespaces for each algo. In other words, a proper API, sort of like the auth algo code does. It is easier to just patch it all in there and re-use existing members, but will that bite us in the future... Any thoughts? ~N

3 2

Test please ignore..
by Holger Freyther 10 Feb '18

10 Feb '18

1 0

Build failed in Jenkins: Coverity-Upload (jenkins-job-builder) #6
by jenkins＠lists.osmocom.org 09 Feb '18

09 Feb '18

See <http://jenkins.osmocom.org/jenkins/job/osmocom-coverity/6/display/redirect> ------------------------------------------ [...truncated 819.23 KB...] CXX gprs_rlcmac.lo CXX gprs_bssgp_pcu.lo CXX gprs_rlcmac_sched.lo CXX gprs_rlcmac_meas.lo CXX gprs_rlcmac_ts_alloc.lo CXX gprs_ms.lo gprs_bssgp_pcu.cpp:967:2: warning: #warning "This causes ASAN to complain. It is not critical for normal operation but should be fixed nevertheless" [-Wcpp] #warning "This causes ASAN to complain. It is not critical for normal operation but should be fixed nevertheless" ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31:0, from ./pcu_l1_if.h:27, from gprs_rlcmac_meas.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l2(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:96:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l2(m) ((void *)(m->l2h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:516:22: note: in expansion of macro ‘msgb_l2’ return osmo_hexdump(msgb_l2(msg), msgb_l2len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31, from ./pcu_l1_if.h:27, from gprs_rlcmac_meas.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31:0, from ./pcu_l1_if.h:27, from gprs_rlcmac_meas.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l3(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:98:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l3(m) ((void *)(m->l3h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:523:22: note: in expansion of macro ‘msgb_l3’ return osmo_hexdump(msgb_l3(msg), msgb_l3len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31, from ./pcu_l1_if.h:27, from gprs_rlcmac_meas.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31:0, from ./pcu_l1_if.h:27, from gprs_rlcmac.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l2(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:96:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l2(m) ((void *)(m->l2h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:516:22: note: in expansion of macro ‘msgb_l2’ return osmo_hexdump(msgb_l2(msg), msgb_l2len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31, from ./pcu_l1_if.h:27, from gprs_rlcmac.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31:0, from ./pcu_l1_if.h:27, from gprs_rlcmac.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l3(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:98:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l3(m) ((void *)(m->l3h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:523:22: note: in expansion of macro ‘msgb_l3’ return osmo_hexdump(msgb_l3(msg), msgb_l3len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31, from ./pcu_l1_if.h:27, from gprs_rlcmac.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10:0, from ./gprs_bssgp_pcu.h:31, from gprs_rlcmac_sched.cpp:20: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l2(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:96:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l2(m) ((void *)(m->l2h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:516:22: note: in expansion of macro ‘msgb_l2’ return osmo_hexdump(msgb_l2(msg), msgb_l2len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10, from ./gprs_bssgp_pcu.h:31, from gprs_rlcmac_sched.cpp:20: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10:0, from ./gprs_bssgp_pcu.h:31, from gprs_rlcmac_sched.cpp:20: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l3(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:98:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l3(m) ((void *)(m->l3h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:523:22: note: in expansion of macro ‘msgb_l3’ return osmo_hexdump(msgb_l3(msg), msgb_l3len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10, from ./gprs_bssgp_pcu.h:31, from gprs_rlcmac_sched.cpp:20: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/prim.h:20:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gsm/l1sap.h:5, from ./bts.h:31, from gprs_rlcmac_ts_alloc.cpp:24: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l2(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:96:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l2(m) ((void *)(m->l2h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:516:22: note: in expansion of macro ‘msgb_l2’ return osmo_hexdump(msgb_l2(msg), msgb_l2len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/prim.h:20, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gsm/l1sap.h:5, from ./bts.h:31, from gprs_rlcmac_ts_alloc.cpp:24: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/prim.h:20:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gsm/l1sap.h:5, from ./bts.h:31, from gprs_rlcmac_ts_alloc.cpp:24: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l3(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:98:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l3(m) ((void *)(m->l3h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:523:22: note: in expansion of macro ‘msgb_l3’ return osmo_hexdump(msgb_l3(msg), msgb_l3len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/prim.h:20, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gsm/l1sap.h:5, from ./bts.h:31, from gprs_rlcmac_ts_alloc.cpp:24: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ Makefile:775: recipe for target 'gprs_rlcmac_meas.lo' failed make[1]: *** [gprs_rlcmac_meas.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... Makefile:775: recipe for target 'gprs_rlcmac_ts_alloc.lo' failed make[1]: *** [gprs_rlcmac_ts_alloc.lo] Error 1 In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10:0, from ./gprs_bssgp_pcu.h:31, from gprs_bssgp_pcu.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l2(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:96:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l2(m) ((void *)(m->l2h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:516:22: note: in expansion of macro ‘msgb_l2’ return osmo_hexdump(msgb_l2(msg), msgb_l2len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10, from ./gprs_bssgp_pcu.h:31, from gprs_bssgp_pcu.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10:0, from ./gprs_bssgp_pcu.h:31, from gprs_bssgp_pcu.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l3(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:98:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l3(m) ((void *)(m->l3h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:523:22: note: in expansion of macro ‘msgb_l3’ return osmo_hexdump(msgb_l3(msg), msgb_l3len(msg)); ^~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:24:0, from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/gprs/gprs_ns.h:10, from ./gprs_bssgp_pcu.h:31, from gprs_bssgp_pcu.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ Makefile:775: recipe for target 'gprs_rlcmac_sched.lo' failed make[1]: *** [gprs_rlcmac_sched.lo] Error 1 gprs_bssgp_pcu.cpp: At global scope: gprs_bssgp_pcu.cpp:76:12: warning: ‘int parse_ra_cap(tlv_parsed*, MS_Radio_Access_capability_t*)’ defined but not used [-Wunused-function] static int parse_ra_cap(struct tlv_parsed *tp, MS_Radio_Access_capability_t *rac) ^~~~~~~~~~~~ Makefile:775: recipe for target 'gprs_bssgp_pcu.lo' failed make[1]: *** [gprs_bssgp_pcu.lo] Error 1 Makefile:775: recipe for target 'gprs_rlcmac.lo' failed make[1]: *** [gprs_rlcmac.lo] Error 1 In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31:0, from pcu_l1_if.h:27, from gprs_ms.h:28, from gprs_ms.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l2(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:96:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l2(m) ((void *)(m->l2h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:516:22: note: in expansion of macro ‘msgb_l2’ return osmo_hexdump(msgb_l2(msg), msgb_l2len(msg)); ^~~~~~~ In file included from gprs_coding_scheme.h:27:0, from rlc.h:22, from tbf.h:25, from gprs_ms.h:27, from gprs_ms.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ In file included from /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/write_queue.h:31:0, from pcu_l1_if.h:27, from gprs_ms.h:28, from gprs_ms.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h: In function ‘const char* msgb_hexdump_l3(const msgb*)’: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:98:21: error: invalid conversion from ‘void*’ to ‘const unsigned char*’ [-fpermissive] #define msgb_l3(m) ((void *)(m->l3h)) ~^~~~~~~~~~~~~~~~~ /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/msgb.h:523:22: note: in expansion of macro ‘msgb_l3’ return osmo_hexdump(msgb_l3(msg), msgb_l3len(msg)); ^~~~~~~ In file included from gprs_coding_scheme.h:27:0, from rlc.h:22, from tbf.h:25, from gprs_ms.h:27, from gprs_ms.cpp:22: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/core/utils.h:55:7: note: initializing argument 1 of ‘char* osmo_hexdump(const unsigned char*, int)’ char *osmo_hexdump(const unsigned char *buf, int len); ^~~~~~~~~~~~ Makefile:775: recipe for target 'gprs_ms.lo' failed make[1]: *** [gprs_ms.lo] Error 1 make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/src' Makefile:461: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 [WARNING] Build command ./build_Osmocom.sh exited with code 2. Please verify that the build completed successfully. Emitted 1854 C/C++ compilation units (100%) successfully [WARNING] Recoverable errors were encountered during 6 of these C/C++ compilation units. 1854 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 2

Call not go through via osmocomBB/limesdr using osmo-bsc
by Sandi Suhendro 07 Feb '18

07 Feb '18

Dear list, Hope some one can look my configuration since I cannot hear voices when make calls outside network via asterisk, but cannot make calls between phone on the same network. please advise this config using osmocomBB. here is the osmo-mgw -c ~/osmobsc/osmo-mgw-for-bsc.cfg https://pastebin.com/NmQQ5hM6 the log : https://pastebin.com/sNy2DxW9 here is the osmo-mgw -c ~/osmobsc/osmo-mgw-for-msc.cfg https://pastebin.com/TCAq3YkL the log : https://pastebin.com/pEbe74BF osmo-msc config : https://pastebin.com/GS2YvjPf the log : https://pastebin.com/Ag52HaED osmo-bsc config: https://pastebin.com/nKQ0czW7 osmo-bts config: https://pastebin.com/s5FamjMv osmo-hlr config : https://pastebin.com/RLgVEURS the log : https://pastebin.com/cAPf1DNs osmo-stp https://pastebin.com/anB0hsc5 hope someone can help to look and give advise really appreciate. Thanks in advance. -- Best Regards, DUO

2 3

RFC: making libosmo-mgcp a non-installed static library
by Harald Welte 05 Feb '18

05 Feb '18

Hi all, I recently proposed the patch https://gerrit.osmocom.org/#/c/6270/ and I would like to get some input from a wider audience. Basically, it turns libosmo-mgcp (the mgw/server side MGCP lib) into an internal library similar to 'libmsc' in osmo-msc, which we don't expect to be used by other programs except osmo-mgw. Hence, there's no need to install it as a shared library, which introduces requirements about ABI/API stability and the like. osmo-bsc_nat uses libosmo-legacy-mgcp, and once we should rewrite osmo-bsc_nat, we might need some of the libosmo-mgcp related functions, but at this point it's unclear what exactly would be needed and if current libosmo-mgcp can provide that. As needed, we can introduce a related shared library at that point. Do you guys agree with this move, or do you think there is a point in having a public shared library with preferably stable API for the MGW side of MGCP? I think it just constrains us as to what we can do in terms of code changes within the MGW - for no clear benefit. 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)

2 1

strange registering behaviour on osmo-bsc
by Sandi Suhendro 02 Feb '18

02 Feb '18

Dear list, I test again with new build for osmo-bsc osmo-msc-osmo-hlr I dont know if the osmo-hlr and osmo-bsc has been fixing or I have mistake for configuration which I did not change from the success I test before, but now I cannot register my phone and even make the network error and keep on emergency only when registering on the phone. at osmo-hlr I got this : 20180201190135844 DAUC <0003> hlr.c:79 510106127044410: IMSI known, but has no auth data; Returning slightly inaccurate cause 'IMSI Unknown' via GSUP Does the new osmo-bsc on master cannot use? or maybe I need to investigate more? Thanks for any feedback! -- Best Regards, DUO

2 4

On the use of 'decmatch' in TTCN-3
by Harald Welte 01 Feb '18

01 Feb '18

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)

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC February 2018