OpenBSC January 2018

openbsc@lists.osmocom.org

29 participants
48 discussions

osmo-python-tests py3 fail
by Neels Hofmeyr 08 Jan '18

08 Jan '18

Hi Max, in osmo-python-tests master, I did python2 setup.py install rm -rf build/ dist/ osmopython.egg-info python3 setup.py install which results in osmotestvty.py installed as py3, causing an encoding problem which I mentioned; py3 is a lot more than print() with braces, see the error log below. So in principle I still don't understand why the py2 scripts need to be made py3 compatible, and why I need to add 'from future' imports to py3 scripts now. There has to be a better way. About the need to rm the installation artifacts, there is no mention of it in the README. And even when I remove those, I still get py2 scripts installed as py3. So anyone is bound to get this error: " osmotestvty.py -p /n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc -w /n/s/osmo-dev/make/osmo-msc -v confpath /n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc, workdir /n/s/osmo-dev/make/osmo-msc Running tests for specific VTY commands test_history (__main__.TestVTY) ... Launch: ./src/osmo-msc/osmo-msc -c /n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg from /n/s/osmo-dev/make/osmo-msc Opening /dev/null Launching: PWD=/n/s/osmo-dev/make/osmo-msc './src/osmo-msc/osmo-msc' '-c' '/n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg' Terminating took 2.679s ERROR test_terminal_length (__main__.TestVTY) ... Launch: ./src/osmo-msc/osmo-msc -c /n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg from /n/s/osmo-dev/make/osmo-msc Launching: PWD=/n/s/osmo-dev/make/osmo-msc './src/osmo-msc/osmo-msc' '-c' '/n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg' Terminating took 2.679s ERROR test_unknown_command (__main__.TestVTY) ... Launch: ./src/osmo-msc/osmo-msc -c /n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg from /n/s/osmo-dev/make/osmo-msc Launching: PWD=/n/s/osmo-dev/make/osmo-msc './src/osmo-msc/osmo-msc' '-c' '/n/s/osmo-dev/make/osmo-msc/../../src/osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg' Terminating took 2.679s ERROR ====================================================================== ERROR: test_history (__main__.TestVTY) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python3.6/dist-packages/osmopython-0.0.6-py3.6.egg/EGG-INFO/scripts/osmotestvty.py", line 56, in test_history File "/usr/local/lib/python3.6/dist-packages/osmopython-0.0.6-py3.6.egg/osmopy/obscvty.py", line 223, in command return self._common_command(request, close) File "/usr/local/lib/python3.6/dist-packages/osmopython-0.0.6-py3.6.egg/osmopy/obscvty.py", line 179, in _common_command self.socket.send("%s\r" % request) TypeError: a bytes-like object is required, not 'str' " With your recent set of changes, you have not only hung all the build slaves' osmo-python-tests updates for 3 weeks, but also dismantled the installation. I wonder how it was possible for this to get past your testing. I will try to get the scripts working for me now. ~N

2 4

Re: build slaves
by Neels Hofmeyr 08 Jan '18

08 Jan '18

On Sun, Jan 07, 2018 at 05:58:40PM +0100, Max wrote: > Hi. > > Seems like jobs which update osmo-ci and osmo-python-tests on build slaves are > failing for 20+ days. This only happens for some of the slaves but not the others. > > I'd like to understand why this is happening and, ideally, fix it. However, there're > few obstacles: It's because of "ImportError: No module named setuptools" since your commit, where you obviously never checked whether setuptools is available on the build slaves: Author: Max <msuraev(a)sysmocom.de> AuthorDate: Fri Dec 15 12:12:01 2017 +0100 Commit: Max <msuraev(a)sysmocom.de> CommitDate: Fri Dec 15 20:40:41 2017 +0100 Use setuptools for packaging According to https://docs.python.org/3/library/distutils.html the setuptools are used in place of distutils anyway. Using it directly allows us to make packaging more flexible: specify dependencies, automatically find package name etc. Change-Id: I39ee53f352001e47c6df055cbec52d638480253d I see console logs fine. https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/63/label=O… https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/63/label=b… So do we really need this setuptools thing or can we just revert the change? ~N

2 2

stricter rate counter group allocation breaks applications
by Neels Hofmeyr 07 Jan '18

07 Jan '18

A recent patch to libosmocore refuses to allocate a rate counter group with an index that already exists. Per se that's a good thing, but it needs fixes in a whole range of callers. Numerous callers wrongly just pass 0 as rate counter group, so as soon as a second <thing> shows up, the application may deny service; that's unacceptable. For example, OsmoSGSN now crashes with the second subscriber showing up! causing patch: https://gerrit.osmocom.org/5418 my proposed change: https://gerrit.osmocom.org/5516 I'd like to request everyone to refrain from submitting patches that are insufficiently tested, in general of course, but in particular until after congress, please ;) ~N

2 2

build slaves
by Max 07 Jan '18

07 Jan '18

Hi. Seems like jobs which update osmo-ci and osmo-python-tests on build slaves are failing for 20+ days. This only happens for some of the slaves but not the others. I'd like to understand why this is happening and, ideally, fix it. However, there're few obstacles: - there seems to be no "console output" or logs available for those jobs - am I looking at the wrong place? - we don't seems to have any docs on the wiki about the build slaves On a related note, do we have a ticket tracking progress on automated build slave creation? -- Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

Handover log
by Alexander Chemeris 07 Jan '18

07 Jan '18

Hello, all, I wonder if anyone has thought about introducing a handover log (to a file or a DB) to OsmoBSC/OsmoNITB? For small deployments <6 BTS you can just add every BTS to neighbor lists of each other and don't worry, but once you get above that, you face a handover optimization issue. I.e. which BTS should be neighbors of which other ones. Initial assigning of the neighbors can be done by simply looking at coverage maps of each BTS. But once the network is actually used there is a lot of useful information about the network performance which can be extracted from the handover history - which cells have issues handing over to each other, etc. -- Regards, Alexander Chemeris. CTO/Founder, Fairwaves, Inc. https://fairwaves.co

2 1

Unable to make calls
by Anindya Sankar Roy 03 Jan '18

03 Jan '18

Hello, I have built osmo-bsc, osmo-msc, osmo-hlr, osmo-stp, osmo-mgcp and connected them successfuly in the same computer. When I try to make calls it gives the folowing error in MGCP osmo-mgw -c newmgw.cfg <0001> telnet_interface.c:104 telnet at 127.0.0.1 4243 <0011> mgw_main.c:336 Configured for MGCP. <0011> mgcp_protocol.c:827 DLCX: endpoint:0x1 deleting connection ... <0011> mgcp_protocol.c:832 DLCX: endpoint:0x1 endpoint is not holding a connection. <0011> mgcp_protocol.c:827 DLCX: endpoint:0x2 deleting connection ... <0011> mgcp_protocol.c:832 DLCX: endpoint:0x2 endpoint is not holding a connection. <0011> mgcp_protocol.c:453 CRCX: creating new connection ... <0011> mgcp_protocol.c:79 endpoint:1 RTP-setup: Endpoint is in loopback mode, stopping here! <0000> mgcp_network.c:188 endpoint:0x1 Failed to send dummy RTP packet. <0011> mgcp_protocol.c:650 CRCX: endpoint:0x1 connection successfully created <0011> mgcp_protocol.c:827 DLCX: endpoint:0x1 deleting connection ... <0011> mgcp_protocol.c:895 DLCX: endpoint:0x1 missing ci (connectionIdentifier), will remove all connections at once <0011> mgcp_protocol.c:453 CRCX: creating new connection ... <0011> mgcp_protocol.c:79 endpoint:1 RTP-setup: Endpoint is in loopback mode, stopping here! <0000> mgcp_network.c:188 endpoint:0x1 Failed to send dummy RTP packet. PFA configuration files for all the blocks that I have been using to run the system and also the pcap trace. Please tell me what am I doing wrong due to which I am unable to make calls. Thanks Anindya calltrace.pcap <https://drive.google.com/a/toshniwalcontrols.com/file/d/1vmDuNJuePVDB9XCHtw…>

1 0

GPS Timing Out-of-Sync Monitoring
by Ron 02 Jan '18

02 Jan '18

Hi All, Happy New Year. I’m not sure if it is appropriate to asked this in this forum or to the SDR vendor but here goes. Is there a way to monitor if the GPS Timing is still sync or not while all the OSMO elements are running? We are using an Ettus B210 with a GPSDO, osmo-trx, osmo-bts-trx, and osmo-nitb running in UBUNTU 16.04 TIA. Best Regard, Ron Menez ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>

1 0

Osmocom Year 2017 Review
by Harald Welte 01 Jan '18

01 Jan '18

Dear all, I've written up a "short" review of what I perceive as the most important events in the Osmocom Cellular Infrastructure projects in 2017. See http://osmocom.org/news/84 for all details, or below for a raw copy+paste: h1. Osmocom Review 2017 This is a review of the most significant changes and events in the Osmocom Cellular Infrastructure projects in 2017 h2. January 2017 * announce of first ever public [[OsmoCon:]] conference in April * osmo-bts ** Add Abis OML failure event reporting ** fix memory leaks in osmo-bts-{sysmo,lc15} at every channel activation * openbsc/osmo-bsc ** support multiple UARFCNs in SI2quater * osmo-hlr ** add test suite for 2G and 3G authentication ** fix UMTS AKA re-sync h2. February 2017 * weekly manual testing with related weekly test reports to mailing list * "heads-up about the (lack of a )future of osmo-nitb":http://lists.osmocom.org/pipermail/openbsc/2017-February/010300.html * "heads-up about libosmo-sccp SIGTRAN work":http://lists.osmocom.org/pipermail/openbsc/2017-February/010274.html * "sysmo-usim-tool":http://lists.osmocom.org/pipermail/openbsc/2017-February/010317.html * libosmo-abis ** unix domain socket support (for Ericsson L2TP) * osmo-bts ** fix AMR HR DTX FSM logic ** fix SACCH sending fo system information with enum value > 7 ** osmo-bts-trx: fix RXGAIN and POWER parameters on second TRX ** fix TCH/H interleaving table bit position ** sysmoBTS 1020/1100: slow power ramp-up on TRX enable * osmo-sgsn ** fix PDP context activation memory allocation bug ** integrate support for UMTS AKA * openggsn ** fix kernel-gtp tunnel creation/removal for GTPv1 ** release 0.93 h3. March 2017 * "cgit improvements":http://lists.osmocom.org/pipermail/openbsc/2017-March/010448.html (about page, change-ID hyperlinks, issue hyperlinks) * Add README.md files to all our repositories * libosmocore ** migrate gsm 05.03 coding from OsmoBTS to libosmocore ** fix SQN / SEQ handling in UMTS AKA ** 3GPP AoIP message encoding/decoding * libosmo-abis ** fix ever-increasing jitter buffer * libosmo-netif ** handle SCTP in in stream server ** doxygen documentation on stream an datagram modules * osmo-bts ** octphy: CBCH support ** include MS timing offset in RSL measurements * osmo-sgsn ** handle IMSIs with leading zeroes * osmo-bsc ** fix T3186 encoding in SI13 ** Improved Ericsson OM2000/RBS2000 support ** new ctrl2soap proxy in python * osmo-hlr ** add CTRL interface ** fix SQN/SEQ handling in UMTS AKA h3. April 2017 * "update of coding style for longer line lengths":http://lists.osmocom.org/pipermail/openbsc/2017-April/010502.html * [[osmo-dev-con:OsmoCon2017]] and [[osmo-dev-con:OsmoDevCon2017]] * libosmocore ** "control interface for osmo_fsm":http://lists.osmocom.org/pipermail/openbsc/2017-April/010542.html * libosmo-netif ** fix file descriptor leak in error paths ** work around linux kenrel SCTP bug with sender_dry_events ** RTP marker bit support * libosmo-sccp ** Add new [[libosmo-sigtran:]] library with SS7 AS/ASP Link/Linkset handling, M3UA support, new FSM based SCCP implementation ** Add [[osmo-stp:]] program * osmo-bts ** inform BSC of PCU disconnect ** fix measurement reporting period ** exclude idle channels from uplink measurement processing ** octphy: measurement reports h3. May 2017 * libosmocore ** fix embedded builds ** import and generalise 'sercomm' from osmocom-bb into libosmocore ** SSE optimized convolutional coder ** fix wrong GSM FR codec SID frame generation ** doxygen docs for libosmocoding * osmo-bsc ** TS 04.14 mobile station side loop control * osmo-bts ** consistently check all RSL and OML TLVs for minimum length value ** fix bit-order in every HR codec parameter (spec compliance) ** OML get/set attribute handling ** SI2quater support ** bypass radio link timeout for lab testing * osmo-bsc ** PCU socket support for BSC-colocated PCU for Ericsson RBS2000 ** reelase 1.0.1 * "M3UA and SUA testing as part of jenkins":http://lists.osmocom.org/pipermail/openbsc/2017-May/010698.html * "osmo-gsm-tester produces successful runs with NITB as well as new AoIP":http://lists.osmocom.org/pipermail/openbsc/2017-May/010760.html h3. June 2017 * libosmocore ** doxygen autobrief ** doxygen documentation for libosmogb * osmo-bts ** use CLOCK_MONOTONIC timer for GSM frame timer ** PDTCH loopback support h3. July 2017 * "Plan for openbsc.git split and code review":http://lists.osmocom.org/pipermail/openbsc/2017-July/010914.html * libosmocore ** PDP charging characteristics in GSUP ** PRBS sequence generators ** multicast IP related helper functions ** 'make release' target * libosmo-sccp ** SCCP address book * osmo-bts ** new virtual BTS @osmo-bts-virtual@ for testing without radio hardware ** don't send dummy UI frames on unused BCCH slots on TC=5 ** GSMTAP: don't log/send fill frames consisting of only padding * osmo-hlr ** change to default GSUP port 4222 h3. August 2017 * "Support for SMPP Delivery Receipt / GSM03.40 Status Report":http://lists.osmocom.org/pipermail/openbsc/2017-August/011023.html * "Jenkins now executing M3UA, SUA and GGSN testsuite":http://lists.osmocom.org/pipermail/openbsc/2017-August/011043.html * libosmocore ** fix crash in lapd_est_req() * libosmo-abis ** release 0.4.0 * osmo-bts ** osmo-bts-trx: fix MS power control loop ** release 0.6.0 ** support sending/removing SI13 to/from PCU * osmo-bsc ** indicate R99+ MSC in SI3 to enable UMTS AKA over GERAN * osmo-sgsn ** properly report GERAN/UTRAN mode in PDP CTX ACT REQ to GGSN * osmo-msc ** implement IuCS support ** split openbsc.git into osmo-bsc.git, osmo-msc.git and osmo-sgsn.git * openggsn ** Add IPv6 address pool and IPV6 user (inner) plane support ** release 0.94 h3. September 2017 * libosmocore.git ** "'show talloc-context' VTY introspection":http://lists.osmocom.org/pipermail/openbsc/2017-June/010771.html ** CTRL parsing unit tests ** unification of vty exit/end commands * osmo-hlr ** CTRL interface tests -- - 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2018