OpenBSC

openbsc@lists.osmocom.org

14 participants
4246 discussions

OsmoBSC(config-net-bts) cell reselection parameters dont show up after set up
by Mario Lucas 16 Dec '20

16 Dec '20

Dear Team please help me with the following question: I want to set up following parameters in osmobsc config: cell bar quality cell reselection offset temporary offset penalty time cell reselection hysterisis These parameter play role when a MS should reselect another cell. These parameters do appear in OsmoBSC(config-net-bts) and i do set up them. But when i run «show running-config» only hysterisis is present… the rest have gone …. also gsmtap from wireshark does not show the rest of parameters. Pls help if you can …. Pls find the log from OsmoBSC(config-net-bts)# show running-config: OsmoBSC(config-net-bts)# show running-config Current configuration: ! ! log stderr logging filter all 1 logging color 0 logging print category-hex 1 logging print category 0 logging timestamp 0 logging print file 1 logging level rll notice logging level mm notice logging level rr notice logging level rsl notice logging level nm info logging level pag notice logging level meas notice logging level msc notice logging level ho notice logging level hodec notice logging level ref notice logging level nat notice logging level ctrl notice logging level filter debug logging level pcu debug logging level lcls notice logging level chan notice logging level ts notice logging level as notice logging level cbs notice logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice logging level lmgcp notice logging level ljibuf notice logging level lrspro notice ! stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive cs7 instance 0 point-code 0.23.3 network network country code 1 mobile network code 1 encryption a5 0 neci 1 paging any use tch 0 handover 0 handover algorithm 1 handover1 window rxlev averaging 10 handover1 window rxqual averaging 1 handover1 window rxlev neighbor averaging 10 handover1 power budget interval 6 handover1 power budget hysteresis 3 handover1 maximum distance 9999 dyn_ts_allow_tch_f 0 bts 0 type sysmobts band GSM900 cell_identity 6969 location_area_code 1 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 radio-link-timeout 32 channel allocator ascending rach tx integer 9 rach max transmission 7 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 1 no access-control-class-ramping access-control-class-ramping-step-interval dynamic access-control-class-ramping-step-size 1 early-classmark-sending forbidden early-classmark-sending-3g allowed ipa unit-id 6969 0 oml ipa stream-id 255 line 0 neighbor-list mode automatic codec-support fr amr tch-f modes 0 2 4 7 amr tch-f threshold ms 32 32 32 amr tch-f hysteresis ms 8 8 8 amr tch-f threshold bts 32 32 32 amr tch-f hysteresis bts 8 8 8 amr tch-f start-mode auto amr tch-h modes 0 2 4 amr tch-h threshold ms 32 32 amr tch-h hysteresis ms 8 8 amr tch-h threshold bts 32 32 amr tch-h hysteresis bts 8 8 amr tch-h start-mode auto gprs mode none trx 0 rf_locked 0 arfcn 10 nominal power 26 max_power_red 16 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config TCH/F hopping enabled 0 msc 0 ip.access rtp-base 4000 no bsc-welcome-text no bsc-msc-lost-text no bsc-grace-text codec-list fr1 hr1 fr2 fr3 hr3 type normal allow-emergency allow amr-config 12_2k forbidden amr-config 10_2k forbidden amr-config 7_95k forbidden amr-config 7_40k forbidden amr-config 6_70k forbidden amr-config 5_90k allowed amr-config 5_15k forbidden amr-config 4_75k forbidden amr-payload octet-aligned asp-protocol m3ua lcls-mode disabled lcls-codec-mismatch forbidden mgw local-port 2727 mgw remote-ip 127.0.0.1 mgw remote-port 2427 bsc mid-call-timeout 0 no missing-msc-text cbc no remote-ip no listen-port end OsmoBSC(config-net-bts)# -- Mario Lucas

4 3

Eclipse TITAN / warnings / finding errors in the log
by Harald Welte 16 Dec '20

16 Dec '20

Hi! It has recently come to my attention that people find it hard to find error messages when compiling TTCN-3 code. This is primarily due to the hundreds to thousands of compiler warnings which [at least our] code generates when building with ttcn3_compiler of TITAN. While some of those warnings indeed should be resolved, a great number of them is actually things where we know what we are doing, and where we'd normally want to disable the warnings. Unfortunately, TITAN doesn't have a system to selectively disable warnings like -Wno-foo in gcc. There are two things that help: 1) colorized output of ttcn3_compiler, which is something I submitted quite a long time ago, but which hasn't e.g. ended up yet in a number of distribution packages. Please feel free to use the eclipse-titan package we build in the OBS network:osmocom:latest feeds to get that feature 2) ttcn3_compiler actually has a '-w' command line argument to make all warnings quiet, which is also supported by ttcn3_makefilegen. You can edit the osmo-ttcn3-hacks/regen-makefile.sh to add that option to ttcn3_makefilegen Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 1

trx output power config in bts
by Mario Lucas 14 Dec '20

14 Dec '20

Dear team could you pls help me with this question In bts config we have following entries: trx 0 nominal power 23 ! to use full TRX power, set max_power_red 0 max_power_red 20 and osmotrx tx-attenuation (oml|<0-50>) So why do we need these «max_power_red 20» and «osmotrx tx-attenuation» which both as i understand weaken the signal? If we want to have a weak signal why we just don’t use only «nominal power» with whatever weak or strong signal value we want? Thank you so much -- Mario Lucas

2 1

Openbsc install limenet sdr
by Choukou Moun 13 Dec '20

13 Dec '20

Hello, Anybody have success to install openbsc on limenet sdr? I have many compilation error with sources or packages. Thank you.

2 4

Unable to send OTA updates to SIM
by bryan coxwell 08 Dec '20

08 Dec '20

The setup: - I am using Osmo-MSC, Osmo-HLR, python-smpplib, and sim-tools. My SIM card is a Sysmocom USIM-SJS1 which came with OTA keys. - Osmo-MSC has been configured to accept SMPP connections, and dcs-transparent has been set. - Using sim-tools with the --smpp flag, I generated the necessary SMPP messages to load the HelloSTK.cap file to the SIM. (Essentially, I've followed the instructions here: https://osmocom.org/projects/cellular-infrastructure/wiki/Shadysimpy) - Sim-tools outputs 6 messages, so in a separate program I use python-smpplib to push each message to the MSC over SMPP. - The send function in my program looks like this: parts = ["027000003815060115150000001dbf31df8eb85248617ff79260f7bf0abd332e2b3c> "02700000901506011515000000d85420f0f778e35b4b8e0ae5d961593444f20fdebb> "02700000901506011515000000729062e3cc920acc51be4f22fd067314bfaee313d6> "02700000901506011515000000373f30a3c12b494d3089c70a2dd46e33e3fccac790> "0270000068150601151500000083f04c39ef2df571bd5389f71b8c528e9b3edea046> "02700000601506011515000000ad6eeebc9373de8bd3a8888324ffaad4d8cd935f0c> ] for part in parts: pdu = client.send_message( source_addr_ton=smpplib.consts.SMPP_TON_INTL, source_addr='0', dest_addr_ton=smpplib.consts.SMPP_TON_INTL, destination_addr='3331112222', short_message=bytes.fromhex(part), data_coding=246, esm_class=64, registered_delivery=True, ) print(pdu.sequence) I have Wireshark running on the computer hosting the MSC, and it shows GSM SMS messages sending to the UE, however there is no response, and when I inspect the SIM card, no applet has been loaded. Am I missing something here? What could be causing this issue? Thanks!

1 0

Re: Help on using pysim to flash a SIM card
by Chunlin Yang 03 Dec '20

03 Dec '20

Hi Vadim and all, pyProg.py fails with an error, could you help (btw, I change all real info to xxx :)): support@S2600WFT:~/pysim$ python ./pySim-prog.py -p 0 -x 208 -y 93 -t sysmoUSIM-SJS1 -i 208930000000003 --op=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -k xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -s xxxxxxxxxxxxxxxxxxxxx -a xxxxxxxx Using PC/SC reader interface Ready for Programming: Insert card now (or CTRL-C to cancel) Generated card parameters : > Name : Magic > SMSP : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > ICCID : xxxxxxxxxxxxxxxxxxxx > MCC/MNC : 208/93 > IMSI : xxxxxxxxxxxxxxx > Ki : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > OPC : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > ACC : None > ADM1(hex): xxxxxxxxxxxxxxxx Programming ... Card programming failed with an execption: ---------------------8<--------------------- Traceback (most recent call last): File "./pySim-prog.py", line 719, in <module> rc = process_card(opts, first, card_handler) File "./pySim-prog.py", line 671, in process_card card.program(cp) File "/home/support/pysim/pySim/cards.py", line 713, in program self._scc.verify_chv(0x0A, h2b(p['pin_adm'])) File "/home/support/pysim/pySim/commands.py", line 206, in verify_chv return self._tp.send_apdu_checksw(self.cla_byte + '2000' + ('%02X' % chv_no) + '08' + fc) File "/home/support/pysim/pySim/transport/__init__.py", line 104, in send_apdu_checksw raise RuntimeError("SW match failed! Expected %s and got %s." % (sw.lower(), rv[1])) RuntimeError: SW match failed! Expected 9000 and got 63c9. ---------------------8<--------------------- Programming failed: Remove card from reader Thanks. Br, Andrew On Tue, Dec 1, 2020 at 1:07 AM Chunlin Yang <chliny2016(a)gmail.com> wrote: > Thanks a lot Vadim! > I have thought it might be an issue between python3 and python2. So I have > tried on both versions. > on Python3, I got same error. > But now with this command 'python ./pySim-read.py -p0', it works. I used > to use this command './pySim-read.py -p0' and it gave me the same error. > > But although 'python ./pySim-read.py -p0' works (reads out the content of > the SIM, it gives me an error/prompt at the end: > Traceback (most recent call last): > File "./pySim-read.py", line 255, in <module> > (res, sw) = card.read_ehplmn() > AttributeError: 'OpenCellsSim' object has no attribute 'read_ehplmn' > > maybe I can just ignore this prompt as I don't need ehplmn. > > Br, > Andrew > > On Tue, Dec 1, 2020 at 12:45 AM Vadim Yanitskiy <vyanitskiy(a)sysmocom.de> > wrote: > >> On 12/1/20 2:17 AM, Chunlin Yang wrote: >> > ModuleNotFoundError: No module named 'smartcard' >> > >> > BTW, I have manually imported smartcard in python, and it's successful. >> >> I guess you have two Python versions (2.7 and 3.x), so it could be that >> you've installed smartcard for 3.x and in works in the shell. >> Unfortunately, pySim has not been completely migrated to 3.x yet, so it >> starts under 2.7 by default. You can try to run it under 3.x: >> >> python3 ./pySim-read.py -p0 >> >> or install the 'smartcard' module for Python 2.7. >> >> Best regards, >> Vadim. >> >> -- >> - Vadim Yanitskiy <vyanitskiy at 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 >> >

3 3

Help on using pysim to flash a SIM card
by Chunlin Yang 01 Dec '20

01 Dec '20

Hi All,I'm following this wiki http://osmocom.org/projects/pysim/wiki I cloned pysim repo, and I cloned this repo also: git clone https://github.com/LudovicRousseau/pyscard.git *although pcsc_scan works* But when I run below: cd <pysim-path> ./pySim-read.py –p 0 *it always gives me this error:* cd ~/pysim ./pySim-read.py -p0 Traceback (most recent call last): File "./pySim-read.py", line 36, in <module> from pySim.cards import card_detect, Card File "/home/support/pysim/pySim/cards.py", line 29, in <module> from smartcard.util import toBytes ModuleNotFoundError: No module named 'smartcard' BTW, I have manually imported smartcard in python, and it's successful. Br, Andrew

2 1

Re: nano3g with genieACS
by Mykola Shchetinin 29 Nov '20

29 Nov '20

Hello Pierre, > Hi, could you share your gist that you have posted earlier in the > following url? > > https://gist.github.com/efistokl/b95538772e54e5edb7765021c2b5a745#22-config… I think the README.md of the repo https://github.com/Pentonet/pentonet-genieacs-package has the same contents as the gist you mentioned used to have. (I've just made the repo public) Also, the repository contains a package I used to set up my nano3g. I didn't document it at all though. Also, I think in the gist I didn't include these two fields: Device.Services.FAPService.1.CellConfig.UMTS.RAN.X_000295_DataOnFACHEnable = false (xsd:boolean) Device.Services.FAPService.1.CellConfig.UMTS.RAN.X_000295_FdEnabled = false (xsd:boolean) They are important for PS to work properly (as said by ip.access support). > I am trying to set up my nano3Gs once again and I remember reading this > awesome guide before, but when I visited the page today, sadly it was > not available anymore. Thanks, I am glad it was useful. Kind regards, Mykola

1 0

Humor of people involved in GSM standardization
by Harald Welte 28 Nov '20

28 Nov '20

Dear Osmocom community, I'd like to share this with you, as I believe not many have read the book "GSM and UMTS; The Creation of Global Mobile Communications" by Friedhelm Hillebrand (who by the way just received the Order of Merit of the Federal Republic of Germany for his substantial contributions to mobile communications). The document (and some others on the included CD-ROM that comes with the book) reminds me to the much more widely known "Aprils Fool RFCs" within the IETF. It's a pity that ETSI - unlike IETF - didn't go through with it and hence those documents were never officially published, so that today only some fax scans seem to exist. Enjoy! -- - Harald Welte <hwelte(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

Understanding GSM BTS Tx power levels
by Mychaela Falconia 20 Nov '20

20 Nov '20

Hello GSM network side community, I am doing some research in preparation for possibly setting up my own GSM/2G BTS in my rural town of Middle-of-Nowhere, California to serve as a replacement for our current GSM/2G service provided by T-Mobile USA, a contingency plan to be activated if and when the evil corporate owners of T-Mobile shut down their 2G service. I haven't bought my BTS hardware yet - I am still doing research and comparing options, and I also need to do some other preparatory work without which the BTS won't be of any use. I have a question about GSM BTS Tx power levels. Some BTS vendors advertise models with up to 10 W power output, but I don't understand how such high power output from a BTS can be useful when MS power output in the other direction is limited to 1 W in high bands or to 2 W in low bands. The whole point of a BTS is to provide service to subscribers, and in order for a subscriber to be able to make a call or to engage in a text conversation, there has to be two-way communication between the BTS and the MS: the MS needs to hear the downlink signal from the BTS, and the BTS needs to hear the uplink signal sent by the MS. If you have a BTS that puts out 10 W on the downlink, wouldn't the effective range be limited at the point where the BTS can no longer receive the 1 W (high bands) or 2 W (low bands) uplink put out by the MS? And if the range limit is set by the Tx power limit of standard GSM MS units, what is the point of having the BTS put out more power on the downlink than the very same 1 W or 2 W limit that applies to uplink Tx power? I can only reason that I must be missing something big here, as those BTS manufacturers who offer models with 10 W output surely make such hardware for some very valid use cases - but I would like to understand it better. Can someone perhaps explain this mystery to me? TIA, Mychaela

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC