Hi Philipp,
I notice that 5 of the LCLS tests in ttcn3_bsc_tests fail saying
"unexpected number of MGW-MDCX transactions"
pass->FAIL BSC_Tests_LCLS.TC_lcls_gcr_bway_connect
pass->FAIL BSC_Tests_LCLS.TC_lcls_gcr_bway_connect_hr
pass->FAIL BSC_Tests_LCLS.TC_lcls_gcr_bway_codec_mismatch
...
pass->FAIL BSC_Tests_LCLS.TC_lcls_connect_break
pass->FAIL BSC_Tests_LCLS.TC_lcls_connect_clear
It appears that your osmo-ttcn3-hacks change
"BSC_Tests: count MGCP operations in as_media"
lacks the proper MGCP operation counts for the LCLS tests?
(The tests have been broken for four days)
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/test_resu…
Could you fix that plz?
Thanks!
~N
I have build following components from source.
1. SoapySDR v0.6.12. Lime Suite v18.06.03. UHD v3.12.0.0-rc14. SoapyUHD v0.3.45. osmo-trx v0.4.0 configure --with-lms6. osmo-nitb7. osmo-bts-trx
however i have only following options are available with osmo-trx
root@miniBTS:/home/pi/osmocom/osmo-trx# osmo-trx-lms -h
Options: -h This text -C Filename The config file to use -V Print the version of OsmoTRX
I have run each instance in separate windows but I cannot show network, log file of following screens along with config files attached. would you please help me whats going wrong, I am newbie
terminal 1 : osmo-trx-lms -C osmo-trx-limesdr.configterminal 2: osmo-nitb -c openbsc.configterminal 3: osmo-bts-trx -c osmobts.config
attached config files have grabbed from https://github.com/myriadrf/cellular-network-configs/tree/master/osmocom
Regards
Babar Ali
On Saturday, 14 July 2018, 4:31:43 AM GMT+5, Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
Hi Babar,
If you want to use a LimeSDR-mini, you should build latest master, and
use osmo-trx-lms binary. To generate that binary, you first need to
build and install latest LimeSuite master [1], and then build osmo-trx
with --with-lms configure flag. As you are building for raspberry pi3,
you may want to enable instruction set optimizations as explained in the
user manual section "12 OsmoTRX hardware architecture support" [2]. Have
a look at the wiki page too for further information [3].
Also a reminder: we have osmo-trx-lms already available as a debian
package for debian9 [4], but I think we don't enable NEON on that build.
[1] https://github.com/myriadrf/LimeSuite
[2] http://ftp.osmocom.org/docs/latest/osmotrx-usermanual.pdf
[3] https://osmocom.org/projects/osmotrx/wiki/OsmoTRX
[4]
https://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian…
On 12/07/18 01:36, Babar Ali wrote:
> Hi Harald
>
> Thank very much for your support please, i’ll test & share the results.
>
> Further kindly let me clear one more thing please, can I build osmotrx
> on RaspbianOS, I have already tried to build osmotrx v0.3 on RasbianOS
> it was build successfully but when I run osmo-trx —help, it shows only
> one option that is -C which I can use with osmo-trx, no other options
> are available, is it cannot be build completely on raspberry pi 3? or
> what’s gone wrong? any suggestions/comments in this regard please.
>
> Thank you for your support & time please.
>
> Regards
> Babar
>
> On Thursday, July 12, 2018, 1:26 AM, Harald Welte <laforge(a)gnumonks.org>
> wrote:
>
> On Wed, Jul 11, 2018 at 04:53:54PM +0000, Babar Ali wrote:
>
> > Anyone has an experience of Setuping 2G Network using NITB &
> LimeSDR Mini, which version of osmotrx is working fine with LimeSDR
> Mini.
>
>
> We have seen very good results using the new osmo-trx-lms with
> LimeSDR-mini.
>
> --
> - Harald Welte <laforge(a)gnumonks.org <mailto:laforge@gnumonks.org>>
> http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
> (ETSI EN 300
> 175-7 <tel:300%20175-7> Ch. A6)
>
--
- Pau Espin Pedrol <pespin(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
Anyone has an experience of Setuping 2G Network using NITB & LimeSDR Mini, which version of osmotrx is working fine with LimeSDR Mini.
Thank You
Regards
Babar
Hello,
I am trying some setup to have multiple channels working all together: I
have an UmTRX and a LimeSDR boards working fine.
The problem is that I cannot launch osmo-trx-uhd and osmo-trx-lms at the
same time as the VTY TCP port are defined in libosmocore.
Is it a way of disabling the VTY or change the TCP port it listen to?
Have a nice day,
Antony
Hi there,
I'm really happy to make my LimeSDR working with the master branch, good
job guys!
I'm now trying to enable the multi-arfcn multiplexed over one physical
channel but I do not succeed to have it working (No response from
transceiver for phy0.1 (CMD RXTUNE 894000)).
Do I need to configure or pass some parameters (see further for what I'm
doing)?
I am starting osmo-bts-trx with "-t 2" option, and here is the extract of
part of my configuration file:
----- osmo-trx-lms.cfg
trx
multi-arfcn enable
swap-channels disable
egprs enable
tx-sps 4
rx-sps 4
chan 0
tx-path BAND1
rx-path LNAW
----- osmo-bts-trx.cfg
phy 0
instance 0
osmotrx rx-gain 10
phy 0
instance 1
osmotrx rx-gain 10
bts 0
band 900
trx 0
phy 0 instance 0
trx 1
phy 0 instance 1
----- osmo-bsc.cfg
bts 0
type sysmobts
band GSM900
trx 0
arfcn 10
trx 1
arfcn 20
Thanks in advance,
Antony
Hi!
We've not used the old build1.osmocom.org machine since late April, so I
am finally pulling the plug and cancelling the contract as of tomorrow.
I manually looked around and the only parts that looked worth backing
up was ~osmocom-build/neels which I've now copied over to
build2.osmocom.org:~root/neels/from_build1/
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)
Good morning,
I wanted to get inter-BSC handover complete before today, and worked like a
maniac for the last two weeks.
I'm looking forward to your comments on the osmo-bsc rework, which started so
small and rippled through the entire code base like a flash flood. I hope you
will find review of it not too daunting, it fully qualifies as a code bomb.
It is refactoring no less than:
- dynamic timeslots,
- lchan states from allocation through release,
- assignment,
- handover
- handling of MGW endpoints, and
- the conn FSM.
- gsm_network->T123 timer handling,
- the way a BTS's neighbors are configured,
- handover and assignment rate counters,
- and whatnot.
- adding five new FSM implementations to osmo-bsc,
- and actually adding inter-BSC Handover, both sides (almost).
Of course I couldn't wrap things up completely, but the good news is that the
only problem left now is that I can't get a ttcn3 test written for inter-bsc MT
handover [1]. Consider the MT side broken yet, though it should be small fixes.
So the refactoring is done and all ttcn3-bsc-tests pass. Yes, *all*!
I will now submit the patches to gerrit; some though could want to go to
libosmocore, and for some other "neat" inventions of mine I'm watching the
comment space in curiosity.
I did try to separate some changes into individual commits, but the final chunk
is too inter-related to pull it apart without spending huge amounts of time to
make osmo-bsc work for each intermediate state.
I feel both like saying "sorry" and "you're welcome" about this at the same
time. Sorry about the size of the single patch; but a lot of code got extremely
easier to read and follow, and a lot safer too, into a nicer osmo-bsc future.
~N
[1]
I have a marginal test added for inter-bsc MO, but the inter-bsc MT gets me.
The problem there is that it is the first time a conn is initiated by the MSC
side. I can get that to work by using BSSAP on that Test_CT. It goes well up to
the point where osmo-bsc sends MGCP CRCX and expects a response. Now I want to
use the MSC_ConnHdlr to manage MGCP, but I can't for the life of me figure out
how to be able to do both at the same time. I tried for very long to resolve
"BSC_Tests.ttcn:2755.13-2756.31: error: Message type `(a)BSSAP_CodecPort.BSSAP_N_CONNECT_req' is not present on the outgoing list of port type `(a)BSSMAP_Emulation.BSSAP_Conn_PT'"
but it feels like a brick wall...
It's the final thing before I can say: I'm done, take a look at inter-BSC HO.
Hello,
I've had success with running a NITB based on the new architecture fine
when everything is on one host. However, I'd now like to split this
across multiple hosts. I have one host dedicated to running osmo-stp and
this appears to bind to the IP specified. However, the instance of
osmo-bsc running on another host always fails to connect and I think,
despite configuring to use a remote STP, it's trying localhost.
Packages installed from Debian 9.0/latest repo. Configs and osmo-bsc
output below. Any pointers as to where I'm going wrong would be much
appreciated.
Regards,
Andrew
//
**** osmo-bsc output:
$ sudo /usr/bin/osmo-bsc -c /etc/osmocom/osmo-bsc.cfg
<001d> osmo_ss7.c:1269 0: ASP Restart for server not implemented yet!
% GPRS not enabled on this BTS
% GPRS not enabled on this BTS
% GPRS not enabled on this BTS
% GPRS not enabled on this BTS
% GPRS not enabled on this BTS
% GPRS not enabled on this BTS
% Line 0 already exists
<0011> telnet_interface.c:104 telnet at 10.1.1.7 4242
<0013> input/ipaccess.c:853 enabling ipaccess BSC mode on 10.1.1.7 with
OML 3002 and RSL 3003 TCP ports
<0018> control_if.c:863 CTRL at 127.0.0.1 4249
<0008> osmo_bsc_sigtran.c:427 Initializing SCCP connection to MSC msc-0
<0008> osmo_bsc_sigtran.c:437 CS7 Instance identifier, A-Interface: 0
<001e> sccp_user.c:397 msc-0: Using SS7 instance 0, pc:0.0.2
<001e> sccp_user.c:411 msc-0: Creating AS instance
<001e> sccp_user.c:421 msc-0: Using AS instance as-clnt-msc-0
<001e> sccp_user.c:426 msc-0: Creating default route
<001e> sccp_user.c:446 msc-0: Creating ASP instance
<0011> socket.c:266 unable to connect socket: (null):2905: Connection
refused
<0011> socket.c:279 no suitable remote addr found for: (null):2905
<001d> osmo_ss7.c:1253 0: Unable to open stream client for ASP
asp-clnt-msc-0
<001e> sccp_user.c:481 msc-0: Using ASP instance asp-clnt-msc-0
<001e> sccp_user.c:484 msc-0: Creating SCCP instance
<0008> osmo_bsc_sigtran.c:480 (msc-0) A-interface: local (BSC) SCCP
address: RI=SSN_PC,PC=0.0.2,SSN=BSSAP
<0008> osmo_bsc_sigtran.c:482 (msc-0) A-interface: remote (MSC) SCCP
address: RI=SSN_PC,PC=0.0.1,SSN=BSSAP
<0013> input/ipa.c:265 accept()ed new link from 10.1.1.8 to port 3002
<0005> abis_nm.c:506 BTS0 feature 'EGPRS' reported via OML does not
match statically set feature: 0 != 1. Please fix.
<0005> abis_nm.c:506 BTS0 feature 'OML Alerts' reported via OML does not
match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:506 BTS0 feature 'Fullrate speech V1' reported via OML
does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:506 BTS0 feature 'Halfrate speech V1' reported via OML
does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:506 BTS0 feature 'Fullrate speech EFR' reported via OML
does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:506 BTS0 feature 'Fullrate speech AMR' reported via OML
does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:506 BTS0 feature 'Halfrate speech AMR' reported via OML
does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:573 OC=BTS(01) INST=(00,ff,ff): BTS0: ARI reported
sw[0/2]: osmobts is 0.8.1
<0005> abis_nm.c:445 BTS0 reported variant: omso-bts-trx
<0005> abis_nm.c:467 BTS0 Attribute Manufacturer Dependent State is
unreported
<0005> abis_nm.c:573 OC=BTS(01) INST=(00,ff,ff): BTS0: ARI reported
sw[0/1]: TRX_PHY_VERSION is Unknown
<0005> abis_nm.c:2809 IPA RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00
<0013> input/ipa.c:265 accept()ed new link from 10.1.1.8 to port 3003
<0004> bsc_init.c:333 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 868
using MCC-MNC 901-70 LAC=23 CID=0 BSIC=63
<0004> abis_rsl.c:2502 (bts=0,trx=0,ts=2,pchan=TCH/F_TCH/H_PDCH as
NONE): GPRS mode is 'none': not activating PDCH.
<0004> abis_rsl.c:2502 (bts=0,trx=0,ts=3,pchan=TCH/F_TCH/H_PDCH as
NONE): GPRS mode is 'none': not activating PDCH.
<0004> abis_rsl.c:2502 (bts=0,trx=0,ts=4,pchan=TCH/F_TCH/H_PDCH as
NONE): GPRS mode is 'none': not activating PDCH.
<0004> abis_rsl.c:2502 (bts=0,trx=0,ts=5,pchan=TCH/F_TCH/H_PDCH as
NONE): GPRS mode is 'none': not activating PDCH.
<0004> abis_rsl.c:2502 (bts=0,trx=0,ts=6,pchan=TCH/F_TCH/H_PDCH as
NONE): GPRS mode is 'none': not activating PDCH.
<0008> a_reset.c:92 A-RESET(msc-0)[0x1d6fff0]{DISC}: (re)sending BSSMAP
RESET message...
<0008> osmo_bsc_sigtran.c:92 Sending RESET to MSC:
RI=SSN_PC,PC=0.0.1,SSN=BSSAP
<001d> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x1d6f7e8]{AS_DOWN}: Event
AS-TRANSFER.req not permitted
<0008> a_reset.c:92 A-RESET(msc-0)[0x1d6fff0]{DISC}: (re)sending BSSMAP
RESET message...
<0008> osmo_bsc_sigtran.c:92 Sending RESET to MSC:
RI=SSN_PC,PC=0.0.1,SSN=BSSAP
<001d> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x1d6f7e8]{AS_DOWN}: Event
AS-TRANSFER.req not permitted
<0011> socket.c:266 unable to connect socket: (null):2905: Connection
refused
<0011> socket.c:279 no suitable remote addr found for: (null):2905
<0008> a_reset.c:92 A-RESET(msc-0)[0x1d6fff0]{DISC}: (re)sending BSSMAP
RESET message...
<0008> osmo_bsc_sigtran.c:92 Sending RESET to MSC:
RI=SSN_PC,PC=0.0.1,SSN=BSSAP
<001d> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x1d6f7e8]{AS_DOWN}: Event
AS-TRANSFER.req not permitted
^Csignal 2 received
<0005> bsc_init.c:96 shutting down OML for BTS 0
**** osmo-bsc.cfg:
e1_input
e1_line 0 driver ipa
ipa bind 10.1.1.7
cs7 instance 0
point-code 0.0.2
asp circ-OsmoBSC 2905 0 m3ua
remote-ip 10.1.1.5
sccp-address msc_remote
point-code 0.0.1
line vty
bind 10.1.1.7
msc
msc-addr msc_remote
network
network country code 901
mobile network code 70
bts 0
type sysmobts
band GSM-1800
location_area_code 23
ip.access unit_id 1800 0
gprs mode none
gprs nsvc 0 remote ip 192.168.0.9
gprs nsvc 0 remote udp port 23000
gprs nsvc 0 local udp port 23000
gprs nsvc 0 nsvci 1800
gprs nsei 1800
gprs cell bvci 1800
trx 0
rf_locked 0
arfcn 868
nominal power 23
timeslot 0
phys_chan_config CCCH+SDCCH4
timeslot 1
phys_chan_config SDCCH8
timeslot 2
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 3
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 4
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 5
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 6
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 7
phys_chan_config PDCH
e1_input
e1_line 0 driver ipa
msc 0
mgw remote-ip 10.1.1.6
mgw remote-port 2427
allow-emergency deny
codec-list hr3
**** osmo-stp.cfg:
log stderr
logging filter all 1
logging color 1
logging print category 1
logging timestamp 0
logging level lss7 debug
logging level lsccp debug
logging level lsua debug
logging level lm3ua debug
cs7 instance 0
xua rkm routing-key-allocation dynamic-permitted
listen m3ua 2905
accept-asp-connections dynamic-permitted
local-ip 10.1.1.5
listen sua 14001
local-ip 10.1.1.5
line vty
bind 10.1.1.5
Hello. I have some problems.I want to create a GSM network for my final
diploma project for University.I'm using USRP2 and I haven't find any
specific configuration files for this type of USRP.Do you have any
configuration files for USRP2? I'm running Kali Linux (amd64). I've
attached the config files that I've used from osmocom.org and some
printscreens.Sorry for my English.I'm looking forward for your
response.Thank you!
Hi, sorry for my English. I installed osmocombb on Kali rolling. When i'm
trying to start my own bts, it works for 4 seconds, then i can see message
"Shutdown timer expired". Bellow you can see my config files. 1 screenshot
- 2 trx firmware on motorola c115. 2 screenshot, left - follow the
commercial BTS timer, right - starting MSC, SMS, HLR. 3 screenshot -
starting osmo-bts. 4 screen - my problem. I can connect with telnet to BSC
and BTS, but BTS - only for this 4 seconds, when it's up. I didn't replaced
filters on motorola, is it my problem? Or i just need to install smth more?
Also, if i write to the wrong mail list, tell me please where should i
write with my problem?
