OpenBSC

openbsc@lists.osmocom.org

9 participants
4171 discussions

RFC: generic CTRL interface for VTY config settings

by Harald Welte

Dear all, we always had said the VTY is a human CLI, while the CTRL interface is for interfacing with other software. This was primarily related to asking users to not parse the VTY output of "show" commands or the like. For configuration via VTY, we have to provide a stable interface anyway, as otherwise loading config files would not be possible across [non-major] software upgrades. While that is right in principle, the fact that we don't have a generic configuration store / API / MIB means that one would explicitly have to add CTRL command for all relevant settings, which may have been realistic in 2010, but is unrealistic with the hundreds of VTY configuration parameters today. I was thinking wither it might make sense to add a generic CTRL interface GET/SET for "configuration" mode VTY settings. This would mean we write code once, and immediately expose all our VTY nodes to CTRL. Thinking of the following example done via VTY: ----------------------------------- OsmoBSC> enable OsmoBSC# configure terminal OsmoBSC(config)# network OsmoBSC(config-net)# bts 0 OsmoBSC(config-net-bts)# trx 1 OsmoBSC(config-net-bts-trx)# timeslot 0 OsmoBSC(config-net-bts-trx-ts)# training_sequence_code 3 ----------------------------------- We could have something like the following CTRL command: SET network.bts.0.trx.1.timeslot.0.training_sequence_code 3 The devil is a bit in the details of the syntax * the normal '.' as separator looks generally OK, I think we have [almost?] no VTY commands that include a ',' * we somehow need some kind of separator to tell where individual VTY commands are separated, like SET network."bts 0"."trx 1"."timeslot 0".training_sequence_code 3 or SET network|bts.0|trx.1|timeslot.0|training_sequence_code 3 or SET network#bts.0#trx.1#timeslot.0#training_sequence_code 3 or SET network.bts#0.trx#1.timeslot#0.training_sequence_code 3 SET network.bts@0.trx@1.timeslot@0.training_sequence_code 3 I think the last examples would be more "natural" for existing CTRL interface code, as the dot separat separates tokens, and we simply expand the '#' or '@' to spaces in the context of VTY commands The generic vty-cfg-via-CTRL code then would basically emulate a user entering the sequence of commands - including the "exclusion" of not allowing multiple concurrent VTY or vty-cfg-via-CTRL users at the same time What do you guys think? Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

4 years, 6 months

testing TTCN3 test stability

by Harald Welte

I think this might be of interest to some of the other developers. Soemtimes we have a problem that the test suite itself is not 100% stable, and it's not easy to reproduce a test that fails sporadically every Nth time. As the "execute" statement in the "control" section actually returns a verdict type, you can use the following construct in a control section: control { for (var integer i := 0; i < 10000; i := i+1) { var verdicttype v; v := execute( TC_paging_ps_ptp_lac() ); if (v != pass) { break; } } } This way you keep running the test suite until the given test fails for the first time. Then go do something else for some hour(s) and by the time you get back, hopefully you will have reproduced the problem. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

4 years, 6 months

Inexpensive Huawei GSM Picocells

by Saturn Rocket

4 years, 6 months

Question about OsmoGGSN project

by morteza ali Ahmadi

Hi, osmocom team members We have run OsmoGGSN project using the attached config file in this email and the following command: osmo-ggsn As you can see in the config file, we have set IP 127.0.0.2 for GGSN. After executing the above command, a tunnel named tun4 is created. To communicate with SGSN, we use the SGSN emulator in OsmoGGSN as follow: sgsnemu -l 127.0.0.1 -r 127.0.0.2 After executing the above command, we see that 2 packets are sent from SGSN to GGSN. These packets are "Echo request" and "Create PDP context request" and GGSN responses to SGSN with the packets "Echo response" and "Create PDP context response". To test tun4, we send a GTP <DNS> packet containing an arbitrary query to GGSN and we see that this GTP <DNS> packet is received in Loopback (lo) interface and also, the DNS packet is received in tun4 interface. But there is no DNS response to our query neither in tun4 interface nor lo interface. A screenshot of the lo interface and tun4 interface in the wireshark is attached in this email (right is lo and left is tun4). How can we receive DNS responses to our DNS query? (Does tun4 require routing or something else?) -- *When there is much light, The shadow is deep...*

4 years, 6 months

Ettus USRP E100 usage for current osmo-trx

by Ivan Babanov

Hello all! Does anybody have any actual information about the possibility to run osmo-trx on Ettus E100 board? I see some references in manuals about the possibility of running it, but I can't find details on how to do it. I tried several ways: 1. Build from source on target HW. Unfortunately "autoreconf" crashes with some perl module dependency. 2. Install binaries. Binaries for arm available only for Debian 9, so I built an image and installed Debian 9.0 on SD-card. Installation of binaries was unsuccessful because of some unmet dependencies. 3. Build from scratch on Debian 9.0. I was partially successful in it. I was able to build osmocore and osmo-trx. The problem was to run it because now, uhd_find_devices shows an empty list. It looks like that kernel module usrp_e.ko should be loaded, but I have no idea where to find its sources. And one more question: Is it a proper place to ask questions related to BTS and TRX? Should I move my question to some other mail list? Thank you Ivan

4 years, 6 months

OsmoHNBGW M3UA IPSP mode

by Mirko Kovacevic

Hello, not many discussions found on OsmoHNBGW topic. 1. Can we connect O' HNBGW directly to SGSN without STP (IPSP mode)? 2. If not, I am wondering do OSMOCOM have development support for IPSP M3UA mode in SIGTRAN development files or elsewhere? Thank you in advance, and keep shaking mobile development world. Mirko K.

4 years, 7 months

SMPP Alert Notifications

by Keith

Hi Osmocom Community. I'd like to extend the SMPP protocol alert notifications to be able to differentiate between IMSI_ATTACH, NORMAL and PERIODIC LURs The reason is to be able to react to an initial attach by sending a "Welcome" SMS. SMPP specifies only three status possibilities: 0 = Available 1 = Disabled 2 = Not Available (Detaching) I've added 3 for IMSI_ATTACH - Actually I ended up using != PERIODIC because not all phones send an ATTACH after a DETACH, some send NORMAL LUR. With this the ESME can respond to an alert notification that has status 3 by looking up the IMSI to see if it's known/autorised etc (this is outside of osmo-hlr in my use case, although I guess it could also be done by checking what the HLR says inside the MSC) Anyway.. I'm wondering if anybody else ever did this, and do we want/accept this functionality in master osmo-msc? Or.. any better ideas on how to do it? Thanks k/

4 years, 7 months

OsmoBSC - SCCP Connection to Nokia MSC

by Sonny Lafuente

Hi Community, Happy New Year! Would like to ask if anyone here have experience integrating OsmoBSC to Nokia MSC? Currently we are doing the integration in Nokia MSC and we encountered issue. Basically, in the SCCP part, the BSC is trying to send UDT (BSSAP) Reset but no response from the MSC. After the default timer of the RESET, we observed a SACK SST and SACK UDTS. In the SACK SST, we saw the trace that there is no Calling indicator which is my BSC point code. When checking the trace we saw this Affected Subsystem Number: 254. I’ve red some documentations in OSMO but I don’t find any SCCP management configuration in OSMO so I think this one is on MSC side. Below is the Trace we captured. BSC Point code - 2262 Nokia Point code - 7039 Regards, Sonny

4 years, 7 months

set a c/c++ standard for all osmocom core network projects

by Alexander 'lynxis' Couzens

Hi, I would like to start a discussion to set for all osmocom core network projects a language standard (could be also set for other osmocom projects). The current state is the code is compiled with the compilers choice of c/c++. This produce unexpected build failures on newer or older system. I would like to start setting it to c11/c++11 + gnu extensions. This is a more random choice of standard. I would argue to have at least c99 for c. Any feedback? Best, lynxis -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604

4 years, 7 months

OsmoBSC(config-net-bts) cell reselection parameters dont show up after set up

by Mario Lucas

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 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC