OpenBSC

openbsc@lists.osmocom.org

10 participants
4277 discussions

Handover log
by Alexander Chemeris 08 Jan '18

08 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 02 Jan '18

02 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

help !!!
by Liang hengshuo 30 Dec '17

30 Dec '17

When I run pysim ,I cannot read the card ,and always tell me this: lab434@lab434-OptiPlex-7050:~/pysim$ ./pySim-read.py -p0 Reading ... ICCID: Traceback (most recent call last): File "./pySim-read.py", line 99, in <module> print("IMSI: %s" % (dec_imsi(res),)) File "/home/lab434/pysim/pySim/utils.py", line 57, in dec_imsi l = int(ef[0:2]) * 2 # Length of the IMSI string ValueError: invalid literal for int() with base 10: 'ff' Anything you know may help me ,thank you !

2 1

gerrit load
by Neels Hofmeyr 30 Dec '17

30 Dec '17

I noticed that gerrit places constant load on the server. When I first checked, it was between 30 and 60% CPU load, now is more like 10-15%, but still it is constant load. I'm pretty sure we're not all clicking around in gerrit all the time, so what would it be: Gerrit does things in the background, like checking whether unmerged patches have merge conflicts to the current master. I'm not perfectly sure how often this happens, but my guess is that it happens a lot. We have around 150 open patches on gerrit. If not for sanity, maybe the CPU load on the gerrit server could be another reason to reduce that number. Related: I notice that the sync of gerrit's git repositories takes longer than it used to. It would be a minute max, while just now I got >10min, and I remember Pau noting something similar recently. I think we should plain abandon patches that have been idling around for more than 3 months. That would discard about 30, so not that many. Then we have quite a number that are currently in Merge Conflict... Seems that we don't get around looking at each one and deciding to kick it or keep it. ~N

6 6

Use osmocombb and openbsc to do man-in-the-middle attacks
by 西电__张皓 25 Dec '17

25 Dec '17

Hello, I would like to use openbsc to do a fake base station and osmocombb to do an attack cell phone, to implement a man-in-the-middle attack. I have two questions: 1. How do I send location updates and authentication information between openbsc and osmocombb, 2. How to modify the code thank you very much

1 0

Branch cleanup in osmo-mgw.git
by Harald Welte 25 Dec '17

25 Dec '17

Dear all, I'm seeing plenty of branches which I believe were forgotten to clean up: gerrit/lynxis/pre_release gerrit/neels/client_vty gerrit/neels/new_mgw gerrit/neels/osmo-mgw gerrit/neels/pending gerrit/neels/pmaier/mgw2 gerrit/neels/pmaier_mgw gerrit/neels/pmaier_mgw6 gerrit/neels/split gerrit/neels/wip gerrit/pmaier/aoip2 gerrit/pmaier/mgw gerrit/pmaier/mgw2 gerrit/pmaier/mgw3 gerrit/pmaier/mgw4 gerrit/pmaier/mgw5 gerrit/pmaier/mgw6 gerrit/pre_release I would appreciate if the respective authors could have a look and remove them if the respective branch is confirmed to be no longer needed. Thanks! 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

Jenkins integration of OsmoBSC TTCN-3 test suite
by Harald Welte 21 Dec '17

21 Dec '17

Dear all, the last couple of weeks I've been spending a lot of time creating an OsmoBSC test suite. A lot of this was infrastructure work, as e.g. there was no RSL implementation available yet for TTCN-3. The code can be found at http://git.osmocom.org/osmo-ttcn3-hacks/tree/bsc there's a README.txt file included with more details (and further test ideas). I've also found some time for the docker + jenkins integration, whose results can now be seen at http://git.osmocom.org/osmo-ttcn3-hacks/tree/bsc (click on 'expand all' to see details). During the writing of the test suite I discovered a quite large number of bugs in OsmoBSC and some of its dependencies, see the list below. I'll stop working on the test coverage for now and focus on other areas of testing first (as well as fixing some of the now-known bugs). Any help is greatly appreciated. List of bugs uncovered/documented: OsmoBSC user manual doesn't specify how to configure M3UA link (asp/as) https://osmocom.org/issues/2767 OsmoBSC BSSMAP CIPHER MODE REJECT is missing mandatory cause IE https://osmocom.org/issues/2766 OsmoBSC refuses configuration with both FR and HR codecs https://osmocom.org/issues/2763 OsmoBSC: Assignment of "Signalling" channel fails https://osmocom.org/issues/2762 OsmoBSC ASSIGNMENT FAIL doesn't contain useful cause https://osmocom.org/issues/2759 rate_ctr_group_alloc with identical index doesn't return error https://osmocom.org/issues/2757 T3113 default of 60s seems way too large https://osmocom.org/issues/2756 Paging on LAI not working https://osmocom.org/issues/2754 Paging on CI not working https://osmocom.org/issues/2753 Paging on LAC+CI not working https://osmocom.org/issues/2752 Paging on CGI not working https://osmocom.org/issues/2751 OsmoBSC allows COMPLETE L3 INFO for SACCH https://osmocom.org/issues/2750 OsmoBSC allows COMPLETE LAYER3 on SAPI !=0 https://osmocom.org/issues/2749 OsmoBSC continues to page subscribers even after BSSMAP RESET https://osmocom.org/issues/2736 RF channel teradown timers (T3109) way too large https://osmocom.org/issues/2734 T3101 default is way too large at 10s https://osmocom.org/issues/2733 OsmoBSC sends invalid zero-length BSSAP payload in SCCP RLSD https://osmocom.org/issues/2732 OpenBSC doesn't release lchan if MSC does a hard SCCP disconnect https://osmocom.org/issues/2731 BSC doesn't release RF conenction or SCCP connection after main signalling link is closed https://osmocom.org/issues/2730 CTRL "msc_connection_status" reports "disconnected" even ater MSC is connected https://osmocom.org/issues/2729 Align better with 48.103 for AoIP user plane https://osmocom.org/issues/2728 OsmoBSC doesn't release lchan if MSC refuses connection (CR -> CREF) https://osmocom.org/issues/2726 OsmoBSC doesn't release lchan if MSC doesn't answer to CR https://osmocom.org/issues/2725 OsmoBSC doesn't send BCCH filling after RSL connection unless BTS sends unsolicited message https://osmocom.org/issues/2719 ipaccess_bts_handle_ccm() gets ID_REQ/ID_RESP/ID_ACK wrong https://osmocom.org/issues/2718 libosmo-abis doesn't use ipa_ccm_make_id_resp() https://osmocom.org/issues/2717 BSC doesn't terminate OML connection if RSL is never established https://osmocom.org/issues/2716 "show trx" doesn't show missing RSL connection https://osmocom.org/issues/2715 OsmoBSC doesn't refuse/close RSL connections from unknown Unit ID https://osmocom.org/issues/2714 -- - 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

Re: Build failure of network:osmocom:nightly/openbsc in Debian_9.0/x86_64
by Neels Hofmeyr 20 Dec '17

20 Dec '17

This is most probably related to / fixed by https://gerrit.osmocom.org/5516 : [ 142s] [0;m<001e> rate_ctr.c:195 counter group 'msc' already exists for index 0 [ 142s] [0;m/usr/src/packages/BUILD/openbsc/tests/testsuite.dir/at-groups/1/test-source: line 25: 20213 Segmentation fault $abs_top_builddir/tests/gsm0408/gsm0408_test On Tue, Dec 19, 2017 at 08:14:06PM +0000, OBS Notification wrote: > Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC