OpenBSC February 2018

openbsc@lists.osmocom.org

14 participants
26 discussions

by Vadim Yanitskiy

Hi Rafael, Please pay your attention at the following warnings: > hlr.c:79 250026920931392: IMSI known, but has no auth data; > Returning slightly inaccurate cause 'IMSI Unknown' via GSUP and > sgsn_auth.c:236 MM(250026920931392/e550701e) > Missing auth tuples, authorization not possible > sgsn_auth.c:248 MM(250026920931392/e550701e) > Got authorization update: state unknown -> rejected Are you sure you do have all required auth information in HLR? > IMSI 250 02 6920931392 BTW: is it a random IMSI? Otherwise, this IMSI belongs to a Russian carrier - Megafon. If I am correct, and this SIM is a commercial SIM, you won't be able to get the auth data for them. With best regards, Vadim Yanitskiy.

7 years, 7 months

Build failed in Jenkins: Coverity-Upload (jenkins-job-builder) #20

by jenkins＠lists.osmocom.org

See <http://jenkins.osmocom.org/jenkins/job/osmocom-coverity/20/display/redirect> ------------------------------------------ [...truncated 1.05 MB...] checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for ANSI C header files... (cached) yes checking byteswap.h usability... yes checking byteswap.h presence... yes checking for byteswap.h... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for UHD... no checking for UHD... yes checking whether C compiler accepts -msse3... yes checking whether C compiler accepts -msse4.1... yes checking whether gcc has __builtin_cpu_supports built-in... yes checking for LIBUSB... yes checking for FFTWF... yes checking boost/config.hpp usability... yes checking boost/config.hpp presence... yes checking for boost/config.hpp... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating CommonLibs/Makefile config.status: creating GSM/Makefile config.status: creating Transceiver52M/Makefile config.status: creating Transceiver52M/arm/Makefile config.status: creating Transceiver52M/x86/Makefile config.status: creating tests/Makefile config.status: creating tests/CommonLibs/Makefile config.status: creating tests/Transceiver52M/Makefile config.status: creating config.h config.status: executing tests/atconfig commands config.status: executing depfiles commands config.status: executing libtool commands + make -j 6 make all-recursive make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' Making all in CommonLibs make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/CommonLibs' CXX BitVector.lo CXX Threads.lo CXX Timeval.lo CXX Logger.lo CXX Sockets.lo CXX LinkedLists.lo CXXLD libcommon.la ar: `u' modifier ignored since `D' is the default (see `U') make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/CommonLibs' Making all in GSM make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/GSM' CXX GSMCommon.lo CXXLD libGSM.la ar: `u' modifier ignored since `D' is the default (see `U') make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/GSM' Making all in Transceiver52M make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' Making all in arm make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/arm' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/arm' Making all in x86 make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/x86' CC convert.lo CC convolve.lo CC libarch_sse_3_la-convolve_sse_3.lo CC libarch_sse_3_la-convert_sse_3.lo CC ../common/convolve_base.lo CC libarch_sse_4_1_la-convert_sse_4_1.lo CC ../common/convert_base.lo CCLD libarch_sse_4_1.la CCLD libarch_sse_3.la ar: `u' modifier ignored since `D' is the default (see `U') ar: `u' modifier ignored since `D' is the default (see `U') CCLD libarch.la ar: `u' modifier ignored since `D' is the default (see `U') make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/x86' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' CXX radioInterface.lo CXX radioVector.lo CXX radioClock.lo CXX signalVector.lo CXX sigProcLib.lo CXX radioBuffer.lo CXX Transceiver.lo CXX ChannelizerBase.lo CXX Channelizer.lo CXX Synthesis.lo CC common/fft.lo CXX Resampler.lo CXX radioInterfaceResamp.lo CXX radioInterfaceMulti.lo CXX UHDDevice.lo CXX osmo-trx.o CXXLD libtransceiver.la ar: `u' modifier ignored since `D' is the default (see `U') CXXLD osmo-trx make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' Making all in tests make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' Making all in CommonLibs make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/CommonLibs' CXX BitVectorTest.o CXX InterthreadTest.o CXX VectorTest.o CXX PRBSTest.o CXX SocketsTest.o CXX TimevalTest.o CXX LogTest.o CXXLD BitVectorTest CXXLD VectorTest CXXLD SocketsTest CXXLD TimevalTest CXXLD PRBSTest CXXLD InterthreadTest CXXLD LogTest make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/CommonLibs' Making all in Transceiver52M make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/Transceiver52M' CC convolve_test-convolve_test.o CCLD convolve_test make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/Transceiver52M' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' + make install Making install in CommonLibs make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/CommonLibs' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/CommonLibs' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/CommonLibs' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/CommonLibs' Making install in GSM make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/GSM' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/GSM' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/GSM' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/GSM' Making install in Transceiver52M make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' Making install in arm make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/arm' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/arm' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/arm' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/arm' Making install in x86 make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/x86' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/x86' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/x86' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M/x86' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin' /bin/bash /home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/libtool --mode=install /usr/bin/install -c osmo-trx '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin' libtool: install: /usr/bin/install -c osmo-trx /home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin/osmo-trx /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/share/usrp/rev2' /usr/bin/install -c -m 644 std_inband.rbf '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/share/usrp/rev2' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/share/usrp/rev4' /usr/bin/install -c -m 644 std_inband.rbf '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/share/usrp/rev4' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/Transceiver52M' Making install in tests make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' Making install in CommonLibs make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/CommonLibs' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/CommonLibs' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/CommonLibs' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/CommonLibs' Making install in Transceiver52M make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/Transceiver52M' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/Transceiver52M' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/Transceiver52M' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests/Transceiver52M' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx/tests' make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-trx' + popd ~/osmo-ci/coverity/source-Osmocom Emitted 2324 C/C++ compilation units (100%) successfully 2324 C/C++ compilation units (100%) are ready for analysis The cov-build utility completed successfully. + cd /home/osmocom-build/osmo-ci/coverity/source-Osmocom + rm -f Osmocom.tgz + tar czf Osmocom.tgz cov-int + set +x curl \ --form token="$token" \ --form email=holger(a)freyther.de --form file=(a)Osmocom.tgz \ --form version=Version --form description=AutoUpload \ https://scan.coverity.com/builds?project=Osmocom % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 curl: (51) SSL: no alternative certificate subject name matches target host name 'scan.coverity.com' Build step 'Execute shell' marked build as failure

7 years, 7 months

fairwaves HO patches

by Neels Hofmeyr

Hi Ivan, as I'm working towards load-based handover and incorporating your patches, I found that most of it is concerned with libmsc. In contrast, I am currently working on osmo-bsc, in libbsc, and would like to ask your advice. Some parts of the patch aren't easy to understand for me, and I'd like to make sure that I am not dismissing parts of it as non-applicable to libbsc even though they might be important. Since your patches were written, the code has changed. Now that we have the separate osmo-bsc, we will need two layers of handover: intra-BSC and inter-BSC. Intra-BSC is a handover between two cells that are serviced by the same BSC, and the higher layers (MSC) should not even notice that anything has happened -- MSC has asked the BSC to service a call by BSSAP Assignment, and the BSC is free to choose and change around the lchans it assigns to that. That is the layer I'm currently dug into. Inter-BSC is a handover between cells that are serviced by two different BSCs. That seems to be the land your patch is improving. The MSC is involved and so is MNCC. (Both MSC and BSC levels will need their own DTAP cache, and they are by definition completely independent -- MSC caches the DTAP coming from MNCC during Inter-BSC handover, BSC caches DTAP from MSC during Intra-BSC handover.) Since your patch is applied onto openbsc.git, where all of BSC and MSC are still one osmo-nitb, I want to make sure that I sort your patch right. Do some of its semantics apply to osmo-bsc master, even if the code changed? The smaller patches are either already applied to osmo-bsc master, or I've submitted them on gerrit just now: handover_decision: Add more log messages to get more information about HO causes in logs handover_decision: Fix condition for power budget handover attempt handover_logic: set correct link to bts for subscriber_connection in case of moving this connection to another bts Remaining are a small and *the* complex one: transaction: Add new function trans_find_by_lchan handover: Implement proper handover procedure handling at any stage of the call Here is the last one with inline questions, I hope they are not too stupid; or too long, it ended up being a lot to read. Thanks in advance for taking a look: > commit f7f4dc5e3b0dd61b8322946597147baef5d0464b > Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> > Date: Wed Aug 23 18:09:50 2017 +0300 > > handover: Implement proper handover procedure handling at any stage of the call > > Enhancements for each stage of handover procedure should be implemented in order to support handover at any stage of the call. > For these purposes new in_handover state and ho_queue for call control messages was introduced for gsm_subscriber_connection. > > Stage 1: HO-Command is sent to MS > gsm_subscriber_connection state should be changed to in_handover=1. > In this state all transmission of signalling layer messages (except RR messages needed for handover procedure) > should be suspended until resuming is indicated. > All call control messages for connection received from network side should be buffered in ho_queue. > All call control messages for connection received from MS side should be ignored. > Channel mode modification procedures should be also suspended. > > Stage 2: HO-Detect is received from MS > Audio path should be switched on network side. > > Stage 3-1: HO-Complete is received from MS > Resumption procedure after successful handover should be performed: > - gsm_subscriber_connection state should be changed to normal (in_handover=0). > - all buffered call control messages (ho_queue) should be sent to MS on new lchan. > - suspended channel mode modification procedures should be performed on new lchan. > > Stage 3-2: HO-Fail is received from MS > Resumption procedure after failed handover should be performed: > - gsm_subscriber_connection state should be changed to normal (in_handover=0). > - all buffered call control messages (ho_queue) should be sent to MS on old lchan. > - suspended channel mode modification procedures should be performed on old lchan. > > Stage 3-3: T3103 expired: Handover has failed without HO-Complete or HO-Fail > Resumption procedure should not be performed in case of T3103 expired: > - gsm_subscriber_connection state should be changed to normal (in_handover=0). > - all buffered call control messages (ho_queue) should be cleaned without sending them to MS. > - suspended channel mode modification procedures should not be performed. > > Change-Id: Icb9b5c35ef0c894af2ea762e539f1a9216447fb7 > > diff --git a/openbsc/include/openbsc/bsc_api.h b/openbsc/include/openbsc/bsc_api.h > index 3a931199..baacbeda 100644 > --- a/openbsc/include/openbsc/bsc_api.h > +++ b/openbsc/include/openbsc/bsc_api.h > @@ -51,5 +51,6 @@ int gsm0808_cipher_mode(struct gsm_subscriber_connection *conn, int cipher, > int gsm0808_page(struct gsm_bts *bts, unsigned int page_group, > unsigned int mi_len, uint8_t *mi, int chan_type); > int gsm0808_clear(struct gsm_subscriber_connection *conn); > +int gsm0808_ho_clear(struct gsm_subscriber_connection *conn); > > #endif > diff --git a/openbsc/include/openbsc/gsm_data.h b/openbsc/include/openbsc/gsm_data.h > index ac573c49..542b2611 100644 > --- a/openbsc/include/openbsc/gsm_data.h > +++ b/openbsc/include/openbsc/gsm_data.h > @@ -138,6 +138,8 @@ struct gsm_subscriber_connection { > struct gsm_network *network; > > int in_release; > + int in_handover; > + struct llist_head ho_queue; > struct gsm_lchan *lchan; /* BSC */ > struct gsm_lchan *ho_lchan; /* BSC */ > struct gsm_bts *bts; /* BSC */ > diff --git a/openbsc/src/libbsc/bsc_api.c b/openbsc/src/libbsc/bsc_api.c > index 8a4c85ff..71e82d03 100644 > --- a/openbsc/src/libbsc/bsc_api.c > +++ b/openbsc/src/libbsc/bsc_api.c > @@ -253,11 +253,14 @@ struct gsm_subscriber_connection *bsc_subscr_con_allocate(struct gsm_lchan *lcha > conn->bts = lchan->ts->trx->bts; > lchan->conn = conn; > llist_add_tail(&conn->entry, &net->subscr_conns); > + INIT_LLIST_HEAD(&conn->ho_queue); > return conn; > } > > void bsc_subscr_con_free(struct gsm_subscriber_connection *conn) > { > + struct msgb *msg; > + > if (!conn) > return; > > @@ -283,6 +286,11 @@ void bsc_subscr_con_free(struct gsm_subscriber_connection *conn) > conn->secondary_lchan->conn = NULL; > } > > + while (!llist_empty(&conn->ho_queue)) { > + msg = msgb_dequeue(&conn->ho_queue); > + msgb_free(msg); > + } > + > llist_del(&conn->entry); > talloc_free(conn); > } > @@ -747,6 +755,17 @@ int gsm0808_clear(struct gsm_subscriber_connection *conn) > return 0; > } > > +/* > + * Release handover RF Channel. > + */ > +int gsm0808_ho_clear(struct gsm_subscriber_connection *conn) > +{ > + if (conn->ho_lchan) > + bsc_clear_handover(conn, 1); > + > + return 0; > +} > + > static void send_sapi_reject(struct gsm_subscriber_connection *conn, int link_id) > { > struct bsc_api *api; > diff --git a/openbsc/src/libbsc/handover_logic.c b/openbsc/src/libbsc/handover_logic.c > index af4e8013..b7085c34 100644 > --- a/openbsc/src/libbsc/handover_logic.c > +++ b/openbsc/src/libbsc/handover_logic.c > @@ -186,10 +186,17 @@ static void ho_T3103_cb(void *_ho) > { > struct bsc_handover *ho = _ho; > struct gsm_network *net = ho->new_lchan->ts->trx->bts->network; > + struct msgb *msg; > > DEBUGP(DHO, "HO T3103 expired\n"); > rate_ctr_inc(&net->bsc_ctrs->ctr[BSC_CTR_HANDOVER_TIMEOUT]); > > + ho->new_lchan->conn->in_handover = 0; > + while (!llist_empty(&ho->new_lchan->conn->ho_queue)) { > + msg = msgb_dequeue(&ho->new_lchan->conn->ho_queue); > + msgb_free(msg); > + } > + (Your ho_queue seems to live in libbsc, while most of the patch seems to be concerned with libmsc. But nevermind, from jolly's patches I already have a similar queue in osmo-bsc, and we'll probably use yours for libmsc.) > ho->new_lchan->conn->ho_lchan = NULL; > ho->new_lchan->conn = NULL; > lchan_release(ho->new_lchan, 0, RSL_REL_LOCAL_END); > @@ -214,6 +221,8 @@ static int ho_chan_activ_ack(struct gsm_lchan *new_lchan) > > gsm48_send_ho_cmd(ho->old_lchan, new_lchan, 0, ho->ho_ref); > > + new_lchan->conn->in_handover = 1; > + In current osmo-bsc master, we already set conn->ho_lchan before sending out the chan activation request. I'd actually assume setting the flag only now, after the activ ack, is a bit too late? > /* start T3103. We can continue either with T3103 expiration, > * 04.08 HANDOVER COMPLETE or 04.08 HANDOVER FAIL */ > ho->T3103.cb = ho_T3103_cb; > @@ -221,7 +230,8 @@ static int ho_chan_activ_ack(struct gsm_lchan *new_lchan) > osmo_timer_schedule(&ho->T3103, 10, 0); > > /* create a RTP connection */ > - if (is_ipaccess_bts(new_lchan->ts->trx->bts)) > + if (is_ipaccess_bts(new_lchan->ts->trx->bts) && > + new_lchan->tch_mode != GSM48_CMODE_SIGN) > rsl_ipacc_crcx(new_lchan); Please explain ... what case / behavior is this fixing? Do we ever see CMODE_SIGN handovers? Would we also need to check for GSM48_CMODE_DATA_*? > @@ -273,6 +283,11 @@ static int ho_gsm48_ho_compl(struct gsm_lchan *new_lchan) > if (is_e1_bts(new_lchan->conn->bts)) > switch_trau_mux(ho->old_lchan, new_lchan); > > + if (ho->old_lchan->conn->mncc_rtp_connect_pending) { > + new_lchan->abis_ip.connect_port = ho->old_lchan->abis_ip.connect_port; > + new_lchan->abis_ip.connect_ip = ho->old_lchan->abis_ip.connect_ip; > + } > + So if an RTP connect to MNCC is pending, we copy the old lchan's RTP port and IP? Which is this, the MNCC / call router side IP and port? Why not set this at the initiation of the HO already? > @@ -295,27 +310,9 @@ static int ho_gsm48_ho_compl(struct gsm_lchan *new_lchan) > static int ho_gsm48_ho_fail(struct gsm_lchan *old_lchan) > { > struct gsm_network *net = old_lchan->ts->trx->bts->network; > - struct bsc_handover *ho; > - struct gsm_lchan *new_lchan; > - > - ho = bsc_ho_by_old_lchan(old_lchan); > - if (!ho) { > - LOGP(DHO, LOGL_ERROR, "unable to find HO record\n"); > - return -ENODEV; > - } > > rate_ctr_inc(&net->bsc_ctrs->ctr[BSC_CTR_HANDOVER_FAILED]); > > - new_lchan = ho->new_lchan; > - > - /* release the channel and forget about it */ > - ho->new_lchan->conn->ho_lchan = NULL; > - ho->new_lchan->conn = NULL; > - handover_free(ho); > - > - lchan_release(new_lchan, 0, RSL_REL_LOCAL_END); > - > - I'm puzzled by this removal. No actions during ho_fail? Is this really intended, or just some rebase artifact? > return 0; > } > > diff --git a/openbsc/src/libmsc/gsm_04_08.c b/openbsc/src/libmsc/gsm_04_08.c > index e5402d0a..84338d72 100644 > --- a/openbsc/src/libmsc/gsm_04_08.c > +++ b/openbsc/src/libmsc/gsm_04_08.c > @@ -147,6 +147,15 @@ static int gsm48_conn_sendmsg(struct msgb *msg, struct gsm_subscriber_connection > sign_link->trx->bts->nr, > sign_link->trx->nr, msg->lchan->ts->nr, > gh->proto_discr, gh->msg_type); > + > + if (conn->in_handover) { > + msgb_enqueue(&conn->ho_queue, msg); > + DEBUGP(DCC, "(bts %d trx %d ts %d) Suspend message sending to MS, " > + "active HO procedure.\n", > + sign_link->trx->bts->nr, > + sign_link->trx->nr, msg->lchan->ts->nr); > + return 0; > + } (here DTAP handled in libmsc ends up in the ho_queue that otherwise seems to live in libbsc ... as I said above this queue will probably move to libmsc altogether to become part of osmo-msc master.) > } > > return gsm0808_submit_dtap(conn, msg, 0, 0); > @@ -1749,11 +1758,8 @@ static int switch_for_handover(struct gsm_lchan *old_lchan, > struct rtp_socket *old_rs, *new_rs, *other_rs; > > /* Ask the new socket to send to the already known port. */ > - if (new_lchan->conn->mncc_rtp_bridge) { > - LOGP(DHO, LOGL_DEBUG, "Forwarding RTP\n"); > - rsl_ipacc_mdcx(new_lchan, > - old_lchan->abis_ip.connect_ip, > - old_lchan->abis_ip.connect_port, 0); > + if (new_lchan->ts->trx->bts->network->mncc_state) { > + /* Audio path should be switched after receiving ho detect message.*/ > return 0; > } I notice that in the current head, the entire switch_for_handover() has been dropped; it was doing libbsc lchan stuff from within libmsc. Hence we must have added similar logic in osmo-bsc.git and completely dropped this. I think the commit re-implementing handover in osmo-bsc is http://git.osmocom.org/osmo-bsc/commit/?id=39c609b7c924524172ad311bdf89f92b… It appears that lchan->abis_ip.connect_ip and connect_port aren't used at all in osmo-bsc master, but are still present in the struct. I'll ask others about that. In any case, the code base has changed substantially, and this patch hunk no longer applies at all. Am I interpreting this hunk correctly: it moves the ipacc_mdcx to tell the new lchan about its RTP peer to a later stage? In current osmo-bsc master, it seems that this ipacc_mdcx happens as soon as the ipacc_crcx is complete, seen in osmo-bsc/src/osmo-bsc/osmo_bsc_audio.c in handle_abisip_signal(), always using the IP:port the MSC sent us. > > @@ -1821,8 +1827,10 @@ static int handle_abisip_signal(unsigned int subsys, unsigned int signal, > if (subsys != SS_ABISIP) > return 0; > > + net = lchan->ts->trx->bts->network; > + > /* RTP bridge handling */ > - if (lchan->conn && lchan->conn->mncc_rtp_bridge) > + if (lchan->conn && net->mncc_state) > return tch_rtp_signal(lchan, signal); What are the semantics here? It seems odd to move from a check of a conn-specific state (conn->mncc_rtp_bridge) to a check of a global value (net->mncc_state). In any case, this is MNCC related and should not impact Intra-BSC handover, right? > > /* in case we use direct BTS-to-BTS RTP */ > @@ -1851,7 +1859,6 @@ static int handle_abisip_signal(unsigned int subsys, unsigned int signal, > > /* check if any transactions on this lchan still have > * a tch_recv_mncc request pending */ > - net = lchan->ts->trx->bts->network; > llist_for_each_entry(trans, &net->trans_list, entry) { > if (trans->conn && trans->conn->lchan == lchan && trans->tch_recv) { > DEBUGP(DCC, "pending tch_recv_mncc request\n"); > @@ -2017,6 +2024,13 @@ static int tch_recv_mncc(struct gsm_network *net, uint32_t callref, int enable) > switch (bts->type) { > case GSM_BTS_TYPE_NANOBTS: > case GSM_BTS_TYPE_OSMO_SYSMO: > if (ipacc_rtp_direct) { > LOGP(DCC, LOGL_ERROR, "Error: RTP proxy is disabled\n"); > return -EINVAL; > } > + /* RTP bridge handling */ > + if (lchan->conn && net->mncc_state) { > + return 0; > + } If we have a conn and using external MNCC, don't continue at all? I'm not following, would be nice if the comment explained why we need to drop out here. (added some more code context manually) > /* In case, we don't have a RTP socket to the BTS yet, the BTS > * will not be connected to our RTP proxy and the socket will > * not be assigned to the application interface. This method > * will be called again, once the audio socket is created and > * connected. */ > if (!lchan->abis_ip.rtp_socket) { > DEBUGP(DCC, "queue tch_recv_mncc request (%d)\n", enable); > return 0; > } > if (enable) { > /* connect the TCH's to our RTP proxy */ > rc = rsl_ipacc_mdcx_to_rtpsock(lchan); > if (rc < 0) > return rc; > /* assign socket to application interface */ > rtp_socket_upstream(lchan->abis_ip.rtp_socket, > net, callref); > } else > rtp_socket_upstream(lchan->abis_ip.rtp_socket, > net, 0); > break; > > @@ -3325,6 +3339,41 @@ static void mncc_recv_rtp_err(struct gsm_network *net, uint32_t callref, int cmd > return mncc_recv_rtp(net, callref, cmd, 0, 0, 0, 0); > } > > +static void mncc_recv_rtp_modify(struct gsm_lchan *lchan, uint32_t callref) This is to tell the call router that the payload type has changed, right? I've asked in the redmine about whether/how we'd convey an RTP payload change to the MNCC in case of an Intra-BSC handover... https://osmocom.org/issues/1606#note-45 > +{ > + int msg_type; > + struct gsm_network *net = lchan->ts->trx->bts->network; > + > + LOGP(DMNCC, LOGL_NOTICE, "%s sending pending RTP modify ind.\n", > + gsm_lchan_name(lchan)); > + > + switch (lchan->abis_ip.rtp_payload) { > + case RTP_PT_GSM_FULL: > + msg_type = GSM_TCHF_FRAME; > + break; > + case RTP_PT_GSM_EFR: > + msg_type = GSM_TCHF_FRAME_EFR; > + break; > + case RTP_PT_GSM_HALF: > + msg_type = GSM_TCHH_FRAME; > + break; > + case RTP_PT_AMR: > + msg_type = GSM_TCH_FRAME_AMR; > + break; > + default: > + LOGP(DMNCC, LOGL_ERROR, "%s unknown payload type %d\n", > + gsm_lchan_name(lchan), lchan->abis_ip.rtp_payload); > + msg_type = 0; > + break; > + } > + > + mncc_recv_rtp(net, callref, MNCC_RTP_MODIFY, > + lchan->abis_ip.bound_ip, > + lchan->abis_ip.bound_port, > + lchan->abis_ip.rtp_payload, > + msg_type); > +} > + > static int tch_rtp_create(struct gsm_network *net, uint32_t callref) > { > struct gsm_bts *bts; > @@ -3374,6 +3423,9 @@ static int tch_rtp_create(struct gsm_network *net, uint32_t callref) > LOGP(DMNCC, LOGL_DEBUG, "RTP create: codec=%s, chan_type=%s\n", > get_value_string(gsm48_chan_mode_names, m), > get_value_string(gsm_chan_t_names, lchan->type)); > + if (trans->conn->in_handover) { > + return 0; > + } Am I reading right: if we're doing handover, the MSC shouldn't sent another BSSAP Assignment to the BSC; instead, the BSC level figures out another lchan and done ... ? > return gsm0808_assign_req(trans->conn, m, > lchan->type != GSM_LCHAN_TCH_H); > } > @@ -3420,23 +3472,21 @@ static int tch_rtp_connect(struct gsm_network *net, void *arg) > * same package! > */ > trans->conn->mncc_rtp_connect_pending = 1; > + if (trans->conn->in_handover) { > + lchan->abis_ip.connect_port = rtp->port; > + lchan->abis_ip.connect_ip = rtp->ip; > + return 0; > + } > return rsl_ipacc_mdcx(lchan, rtp->ip, rtp->port, 0); We're not telling the BTS about the call router's IP:port anymore? Please explain... > } > > static int tch_rtp_signal(struct gsm_lchan *lchan, int signal) > { > struct gsm_network *net; > - struct gsm_trans *tmp, *trans = NULL; > + struct gsm_trans *trans; > > net = lchan->ts->trx->bts->network; > - llist_for_each_entry(tmp, &net->trans_list, entry) { > - if (!tmp->conn) > - continue; > - if (tmp->conn->lchan != lchan && tmp->conn->ho_lchan != lchan) > - continue; > - trans = tmp; > - break; > - } > + trans = trans_find_by_lchan(lchan); > > if (!trans) { > LOGP(DMNCC, LOGL_ERROR, "%s IPA abis signal but no transaction.\n", > @@ -3459,7 +3509,7 @@ static int tch_rtp_signal(struct gsm_lchan *lchan, int signal) > maybe_switch_for_handover(lchan); > break; > case S_ABISIP_MDCX_ACK: > - if (lchan->conn->mncc_rtp_connect_pending) { > + if (lchan->conn->mncc_rtp_connect_pending && !lchan->conn->in_handover) { if we're in handover, we don't need to tell MNCC that RTP got connected, because that already happened when the call got established initially? So mncc_rtp_connect_pending has a second meaning during handover? > lchan->conn->mncc_rtp_connect_pending = 0; > LOGP(DMNCC, LOGL_NOTICE, "%s sending pending RTP connect ind.\n", > gsm_lchan_name(lchan)); > mncc_recv_rtp_sock(net, trans, MNCC_RTP_CONNECT); > } > break; > @@ -3471,6 +3521,134 @@ static int tch_rtp_signal(struct gsm_lchan *lchan, int signal) > return 0; > } > > +static void ho_queue_clean(struct gsm_subscriber_connection *conn) > +{ > + struct msgb *msg; > + while (!llist_empty(&conn->ho_queue)) { > + msg = msgb_dequeue(&conn->ho_queue); > + msgb_free(msg); > + } > +} > + > +static void ho_resumption(struct gsm_lchan *lchan, struct gsm_trans *trans) > +{ > + struct msgb *msg; > + enum gsm48_chan_mode m; > + > + while (!llist_empty(&lchan->conn->ho_queue)) { > + msg = msgb_dequeue(&lchan->conn->ho_queue); > + gsm48_conn_sendmsg(msg, lchan->conn, trans); > + } > + > + if (trans->conn->mncc_rtp_create_pending && > + lchan->tch_mode == GSM48_CMODE_SIGN) { > + m = mncc_codec_for_mode(lchan->type); > + gsm0808_assign_req(lchan->conn, m, lchan->type != GSM_LCHAN_TCH_H); Wait, now we *do* send a BSSAP Assignment after all? (excuse if I'm being noob, I'm still finding my way through handover in general) shouldn't we rather dequeue the cached DTAP after this instead of before? > + } > + > + if (trans->conn->mncc_rtp_connect_pending) { > + rsl_ipacc_mdcx(lchan, lchan->abis_ip.connect_ip, lchan->abis_ip.connect_port, 0); > + } > +} > + > +static int ho_complete(struct gsm_lchan *new_lchan) > +{ > + struct gsm_trans *trans; > + > + new_lchan->conn->in_handover = 0; > + trans = trans_find_by_lchan(new_lchan); > + if (!trans) { > + LOGP(DHO, LOGL_ERROR, "%s HO detected, but no transaction for new_lchan.\n", > + gsm_lchan_name(new_lchan)); > + ho_queue_clean(new_lchan->conn); > + return 0; > + } > + > + ho_resumption(new_lchan, trans); > + return 0; > +} > + > +static int ho_fail(struct gsm_lchan *old_lchan) > +{ > + struct gsm_trans *trans; > + > + old_lchan->conn->in_handover = 0; > + trans = trans_find_by_lchan(old_lchan); > + if (trans) > + ho_resumption(old_lchan, trans); > + else { > + LOGP(DHO, LOGL_ERROR, "%s HO fail, but no transaction for old_lchan.\n", > + gsm_lchan_name(old_lchan)); > + ho_queue_clean(old_lchan->conn); > + } > + > + gsm0808_ho_clear(old_lchan->conn); > + return 0; > +} > + > +static int ho_detect(struct gsm_lchan *new_lchan) > +{ > + struct gsm_trans *trans; > + struct gsm_lchan *old_lchan; > + > + trans = trans_find_by_lchan(new_lchan); > + > + if (!trans) { > + LOGP(DHO, LOGL_ERROR, "%s HO detected, but no transaction for new_lchan" > + " with enabled tch_recv.\n", > + gsm_lchan_name(new_lchan)); > + return 0; > + } > + > + if (!new_lchan->conn->mncc_rtp_bridge) { > + LOGP(DHO, LOGL_ERROR, "%s HO detected, but connection not in mncc_rtp_bridge mode.\n", > + gsm_lchan_name(new_lchan)); > + return 0; > + } > + > + old_lchan = bsc_handover_pending(new_lchan); > + if (!old_lchan) { > + LOGP(DHO, LOGL_ERROR, "%s HO detected, but no old_lchan for handover.\n", > + gsm_lchan_name(new_lchan)); > + return 0; > + } > + > + LOGP(DHO, LOGL_DEBUG, "HO detected, forwarding RTP\n"); > + rsl_ipacc_mdcx(new_lchan, > + old_lchan->abis_ip.connect_ip, > + old_lchan->abis_ip.connect_port, 0); > + > + mncc_recv_rtp_modify(new_lchan, trans->callref); > + > + return 0; > +} > + > +/* some other part of the code sends us a signal */ > +static int handle_lchan_signal(unsigned int subsys, unsigned int signal, > + void *handler_data, void *signal_data) > +{ > + struct lchan_signal_data *lchan_data; > + struct gsm_lchan *lchan; > + > + lchan_data = signal_data; > + switch (subsys) { > + case SS_LCHAN: > + lchan = lchan_data->lchan; > + if (!lchan->conn) > + return 0; > + switch (signal) { > + case S_LCHAN_HANDOVER_DETECT: > + return ho_detect(lchan); > + case S_LCHAN_HANDOVER_COMPL: > + return ho_complete(lchan); > + case S_LCHAN_HANDOVER_FAIL: > + return ho_fail(lchan); > + } > + break; > + } > + > + return 0; > +} > > static struct downstate { > uint32_t states; > @@ -3853,6 +4031,11 @@ static int gsm0408_rcv_cc(struct gsm_subscriber_connection *conn, struct msgb *m > gsm48_cc_msg_name(msg_type), trans?(trans->cc.state):0, > gsm48_cc_state_name(trans?(trans->cc.state):0)); > > + if (conn->in_handover) { > + DEBUGP(DCC, "Message unhandled, handover procedure.\n"); > + return 0; > + } > + If in handover, drop all CC on the floor? How about a call release, i.e. I hang up while I'm coincidentally being handovered? > /* Create transaction */ > if (!trans) { > DEBUGP(DCC, "Unknown transaction ID %x, " > > > Thanks again! ~N

7 years, 7 months

osmo-nitb and osmo-bts-trx problems with voice, no connection (using LimeSDR)

by Norbertas Kremeris

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><mailto:axilirator@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><mailto:pespin@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><mailto:pespin@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><mailto:laforge@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.

7 years, 7 months

docker-playground and make -C

by Neels Hofmeyr

About git://git.osmocom.org/docker-playground -- I just hit an obscure case that got me really confused: In debian-stretch-titan/, the docker image that is built will obviously be tagged 'debian-stretch-titan', from $PWD. However, when I do, from the root dir: make -C debian-stretch-titan then somehow the $PWD is still resolved in the root dir, and all of my images get tagged as 'docker-playground'. wtf. So this didn't work: for d in debian-stretch-titan osmo-bsc-master osmo-stp-master osmo-mgw-master ttcn3-bsc-test ; do make -C $d done It just got me lots of untagged images, and the last one tagged as docker-playground. but this worked: for d in debian-stretch-titan osmo-bsc-master osmo-stp-master osmo-mgw-master ttcn3-bsc-test ; do cd $d make cd .. done That's one hell of a thing to be aware of there, you can try to refresh your images all you like if they keep being tagged with the wrong names >:( ~N

7 years, 7 months

msc_vlr_tests patches

by Neels Hofmeyr

Hi Max, thanks for looking at the msc_vlr_tests.c. That 'while (0)' was a curious artifact indeed :) Some parts of it I actually wouldn't have liked to be merged: 1) pass nr as param / always print the test number. The reason why I wanted that number output only in verbose mode is, I don't want to adjust unrelated *.err output when adding a test in any position that is not the last. The test nr was introduced only for running a specific test manually, and for that the -v option provides the test number to whoever is invoking it manually. The individual tests do not at all need to know their number, so I would prefer not passing it as parameter. The idea is to keep the manual invocation overhead out of the production testing code. 2) pass IMSI as param / print the IMSI. The IMSI used in the tests is (incidentally) the same throughout the tests and doesn't really need to change in any way. It is but a local variable that ensures there are no string constant typos within a test function. It mayybe could be one or more global string constants, but doesn't make sense as a parameter passed to each and every test: some tests also (might) use two IMSIs. Running the same tests with differing IMSIs is not needed, and I don't see a patch introducing that. What was the idea there to justify the bloat? (If we were to pass imsi and number to each and every msc_vlr_test* function, it would be better to introduce a context struct that we can modify without having to edit every function signature. But I'd prefer them parameter-less.) 3) you moved gsm_network creation into a separate function, but that function is still called only once. So it's just cosmetic, or was there another purpose? ~N

7 years, 7 months

osmo-nitb and osmo-bts-trx problems with voice, no connection (using LimeSDR)

by Norbertas Kremeris

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.

7 years, 8 months

Warning: OsmoMSC config file / VTY changes

by Harald Welte

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)

7 years, 8 months

3G femtocells and core network in Python

by benoit michau

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

7 years, 8 months

spend time to properly separate handover 2?

by Neels Hofmeyr

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

7 years, 8 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC February 2018