Hi.
I've got following problem while trying to make osmotrx work in multitrx
setting on USRP B210:
sudo chrt 20 ./Transceiver52M/osmo-trx -c 2
sudo chrt 15 ./src/osmo-bts-trx/osmo-bts-trx -t 2 -c
~/.config/osmocom/osmo-bts-mtrx.cfg -d DRTP:DCC:DRSL:DOML:DL1C:DTRX
The bts quits from trx_if.c after checking "if (tcm->critical) {...".
The command sequence seems to be the same for both phy0.0 and phy0.1
However 0.0 one accepts SETTSC command and 0.1 rejects it:
trx_if.c:380 transceiver (phy0.1) rejected TRX command with response:
'RSP SETTSC 1 7'
So far I fail to see where this difference comes from.
Full log:
<0001> oml.c:1249 Initializing OML attribute definitions
<000b> trx_if.c:560 Open transceiver for phy0.0
<000b> trx_if.c:222 Adding new control 'CMD POWEROFF'
<000b> trx_if.c:169 Sending control 'CMD POWEROFF' to phy0.0
<000b> trx_if.c:560 Open transceiver for phy0.1
<000b> trx_if.c:348 Response message: 'RSP POWEROFF 0'
<0001> oml.c:547 Ignoring T200[0] (150 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[1] (180 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[2] (180 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[3] (1680 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[4] (520 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[5] (165 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[6] (1680 ms) as sent by BSC due to
suspected LAPDm bug!
<000b> trx_if.c:222 Adding new control 'CMD POWEROFF'
<000b> trx_if.c:169 Sending control 'CMD POWEROFF' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP POWEROFF 0'
<0001> oml.c:884 ADM state already was Unlocked
<000b> trx_if.c:222 Adding new control 'CMD RXTUNE 1783400'
<000b> trx_if.c:169 Sending control 'CMD RXTUNE 1783400' to phy0.0
<000b> trx_if.c:222 Adding new control 'CMD TXTUNE 1878400'
<000b> trx_if.c:222 Adding new control 'CMD SETTSC 7'
<000b> trx_if.c:222 Adding new control 'CMD POWERON'
<000b> trx_if.c:222 Adding new control 'CMD SETRXGAIN 1'
<000b> trx_if.c:222 Adding new control 'CMD SETPOWER 0'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 4'
<0005> paging.c:545 Paging: BS_AG_BLKS_RES = 0 != 1 not fully supported
<000b> trx_if.c:348 Response message: 'RSP RXTUNE 0 1783400'
<000b> trx_if.c:169 Sending control 'CMD TXTUNE 1878400' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP TXTUNE 0 1878400'
<000b> trx_if.c:169 Sending control 'CMD SETTSC 7' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETTSC 0 7'
<000b> trx_if.c:169 Sending control 'CMD POWERON' to phy0.0
<0005> paging.c:545 Paging: BS_AG_BLKS_RES = 0 != 1 not fully supported
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 1 7'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 2 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 3 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 4 13'
<000b> trx_if.c:348 Response message: 'RSP POWERON 0'
<000b> trx_if.c:169 Sending control 'CMD SETRXGAIN 1' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETRXGAIN 0 1'
<000b> trx_if.c:169 Sending control 'CMD SETPOWER 0' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETPOWER 0 0'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 0 4' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 0 4'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 1 7' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 1 7'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 2 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 2 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 3 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 3 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 4 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 4 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 5 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 5 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 5 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 6 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 6 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 6 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 7 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 7 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 7 13'
<0001> oml.c:884 ADM state already was Unlocked
<000b> trx_if.c:222 Adding new control 'CMD RXTUNE 1783800'
<000b> trx_if.c:169 Sending control 'CMD RXTUNE 1783800' to phy0.1
<000b> trx_if.c:222 Adding new control 'CMD TXTUNE 1878800'
<000b> trx_if.c:222 Adding new control 'CMD SETTSC 7'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 7'
<000b> trx_if.c:348 Response message: 'RSP RXTUNE 0 1783800'
<000b> trx_if.c:169 Sending control 'CMD TXTUNE 1878800' to phy0.1
<000b> trx_if.c:348 Response message: 'RSP TXTUNE 0 1878800'
<000b> trx_if.c:169 Sending control 'CMD SETTSC 7' to phy0.1
<000b> trx_if.c:348 Response message: 'RSP SETTSC 1 7'
<000b> trx_if.c:380 transceiver (phy0.1) rejected TRX command with
response: 'RSP SETTSC 1 7'
<0001> bts.c:203 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
<000b> trx_if.c:222 Adding new control 'CMD POWEROFF'
<000b> trx_if.c:169 Sending control 'CMD POWEROFF' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP POWEROFF 0'
<0001> oml.c:547 Ignoring T200[0] (150 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[1] (180 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[2] (180 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[3] (1680 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[4] (520 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[5] (165 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:547 Ignoring T200[6] (1680 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:884 ADM state already was Unlocked
<000b> trx_if.c:222 Adding new control 'CMD POWERON'
<000b> trx_if.c:169 Sending control 'CMD POWERON' to phy0.0
<000b> trx_if.c:222 Adding new control 'CMD SETRXGAIN 1'
<000b> trx_if.c:222 Adding new control 'CMD SETPOWER 0'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 4'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 1 7'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 2 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 3 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 4 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 5 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 6 13'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 7 13'
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<000b> trx_if.c:348 Response message: 'RSP POWERON 0'
<000b> trx_if.c:169 Sending control 'CMD SETRXGAIN 1' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETRXGAIN 0 1'
<000b> trx_if.c:169 Sending control 'CMD SETPOWER 0' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETPOWER 0 0'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 0 4' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 0 4'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 1 7' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 1 7'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 2 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 2 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 3 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 3 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 4 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 4 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 5 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 5 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 6 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 6 13'
<000b> trx_if.c:169 Sending control 'CMD SETSLOT 7 13' to phy0.0
<000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 7 13'
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 7'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 1 1'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 2 1'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 3 1'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 4 1'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 5 1'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 6 1'
<000b> trx_if.c:222 Adding new control 'CMD SETSLOT 7 1'
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<0001> oml.c:884 ADM state already was Unlocked
<000b> trx_if.c:138 Clock indication: fn=999376
<000b> trx_if.c:470 TX burst tn=0 fn=999396 pwr=0
<000b> trx_if.c:470 TX burst tn=1 fn=999396 pwr=0
<000b> trx_if.c:470 TX burst tn=2 fn=999396 pwr=0
...
--
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
Hi,
when trying to work with multiple BTS as noted in http://umtrx.org/multi-bts-with-osmocom-and-a-single-umtrx/ , I faced a problem related to paging. When I start the BTS, I can send SMS to any connected phone but after a few minutes no SMS is sent and I can’t even make calls. I noticed that the target phone is not being paged anymore. If I restart the openBSC instance the old pending messages get sent sometimes. Also if I run the same code but with only one OSMO-BTS instance, everything works fine.
I would really appreciate some help.
Best regards,
Hi.
While testing I've got iphone (non-jailbroken) which regularly attempts
to send following sms to number 447537410247 (uk?):
REG-REQ?v=3;t=C335D183C5A2FC0E2501543EBCEB8263D55683FB63A2E8CAF98B8874D940263F;r=165209558
without asking user for anything.
Is this some sort of Apple's backdoor? Or GCHQ is so bored that they are
trying to spy on me? :)
Have you guys seen this before?
--
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
Hi.
I've noticed check for device type around
Transceiver52M/UHDDevice.cpp:772 - seems like USRP B200 is not supported
for multitrx configurations:
sudo chrt 20 ./Transceiver52M/osmo-trx -c 2
sudo chrt 15 ./src/osmo-bts-trx/osmo-bts-trx -c
~/.config/osmocom/osmo-bts-trx.cfg -i 192.168.122.1 -t 2
Where does this limitation comes from? Is it just smth which is not
implemented (yet) or it's impossible to implement due to X and Y?
--
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
On Jun 15, 2016 10:38 PM, "Tom Tsou" <tom(a)tsou.cc> wrote:
>
> On Wed, Jun 15, 2016 at 10:08 AM, Max <msuraev(a)sysmocom.de> wrote:
> > I've tried it with manually sending POWERON - the issue with CHAN RQD is
> > gone but the phone still does not work. I'll look into OML/RSL/whatever
> > is preventing it from working.
>
> Make sure that the static variable 'settsc_enabled' is set.
>
> diff --git a/src/osmo-bts-trx/trx_if.c b/src/osmo-bts-trx/trx_if.c
> index a4c16dc..8c9a839 100644
> --- a/src/osmo-bts-trx/trx_if.c
> +++ b/src/osmo-bts-trx/trx_if.c
> @@ -47,7 +47,7 @@
> //#define TOA_RSSI_DEBUG
>
> int transceiver_available = 0;
> -int settsc_enabled = 0;
> +int settsc_enabled = 1;
> int setbsic_enabled = 0;
Could you explain why is that required?
I don't remember the code exactly, but IIRC this is equivalent to setting
or removing 'tsc' line in the config file.
Please excuse typos. Written with a touchscreen keyboard.
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
Hi Harald,
On Wed, Apr 6, 2016 at 12:59 AM, Harald Welte <laforge(a)gnumonks.org> wrote:
> Can you or somebody else interested in getting this resolved provide a
> full bug report, including
> * debug log output on OsmoNITB side for for the rsl and nm
> * debug log output on OsmoBTS side for oml / transceiver interface or
> anything else related
> * pcap file of A-bis traffic between OsmoBTS and OsmoNITB, as well as
> the control commands between osmo-bts-trx and osmo-trx
Attached are the logs for master branches of OpenBSC, OsmoBTS, and
OsmoTRX leading up to the following RACH access behavior.
<0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0x2
Hopefully, somebody more familiar than myself with A-bis and related
L1/L2 dependencies can provide some insight on why the above is
happening or where to start debugging. I'll be happy to test any
subsequent changes or look into specific parts of the A-bis code.
-TT
I am a bit ambiguous on our use of comments in gerrit.
We do discuss at least some fairly interesting things in the comments on
patches waiting for approval in gerrit.
When these discussions are attempted on openbsc@ or osmocom-net-gprs@, you
tend to block off and redirect the discussion back to the gerrit comments
infrastructure.
However, we have moved the gerrit mails to a separate and very noisy
mailing list, and these potentially interesting discussions are moved
essentially out of the public focus.
Also, if we in future would like to investigate discussion on some topic,
we need to search both the main ML and the gerrit ML.
IMHO it would make sense to copy the human originated comments to our
"human" mailing lists, so that the automatic jenkins and gerrit
notifications remain on the noisy ML while we see all discussions here.
Is that easy to achieve (filter on originator of comment),
and would you guys agree?
~Neels
--
- Neels Hofmeyr <nhofmeyr(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
* Geschäftsführer / Managing Directors: Harald Welte