Hi,
Erich, I'm using OpenBTS with USRP B100 & SBX.
I encountered new problem, maybe it's similar to initial problem.
Calls and MO SMS works fine (not in 100%, but it's ok). But MT SMS
does not work (actually I received only 1 SMS from many attempts).
Mobile log (error part, from line 454):
<0001> gsm48_rr.c:429 new SAPI 3 link state idle -> established
<000e> gsm48_rr.c:5042 Radio link SAPI3 is established
<0005> gsm48_mm.c:3911 (ms 1) Received 'RR_EST_IND' from RR in state
wait for network command (sapi 3)
<0001> gsm48_rr.c:662 MON: f=50 lev=>=-47 snr= 0 ber= 0 LAI=001 01
0001 ID=0001 TA=3 pwr=19 TS=0/0
<0001> gsm48_rr.c:2864 MEAS REP: pwr=19 TA=3 meas-invalid=0
rxlev-full=-47 rxlev-sub=-47 rxqual-full=0 rxqual-sub=0 dtx 0 ba 0
no-ncell-n 0
<0001> gsm48_rr.c:4767 Indicated ta 3 (actual ta 3)
<0001> gsm48_rr.c:4769 Indicated tx_power 19
<0001> gsm48_rr.c:4767 Indicated ta 3 (actual ta 3)
<0001> gsm48_rr.c:4769 Indicated tx_power 19
<0001> gsm48_rr.c:4984 MDL-Error (cause 4) ignoring
Dropping frame with 71 bit errors
<0001> gsm48_rr.c:4767 Indicated ta 3 (actual ta 3)
<0001> gsm48_rr.c:4769 Indicated tx_power 19
<0001> gsm48_rr.c:662 MON: f=50 lev=>=-47 snr=10 ber= 42 LAI=001 01
0001 ID=0001 TA=3 pwr=19 TS=0/0
<0001> gsm48_rr.c:2864 MEAS REP: pwr=19 TA=3 meas-invalid=0
rxlev-full=-47 rxlev-sub=-47 rxqual-full=0 rxqual-sub=0 dtx 0 ba 0
no-ncell-n 0
<0001> gsm48_rr.c:3389 channel release request with cause 0x62
<0001> gsm48_rr.c:355 new state dedicated -> release pending
In trace (from packet 5509):
BTS send SABM
MS receive SABM
MS respond with UA
BTS receive UA
BTS send I frame
MS receive SABM (extra message?)
MS respond with UA
BTS receive UA
BTS send DM (disconnect request? because of extra UA respond from MS?)
BTS send Channel Release
after that MS receive I frame and send RR with ack but as I understand
this does not matter because of Chan Release..
Thanks,
Pavel
On Thu, Jan 10, 2013 at 6:02 PM, Erich Dachleger <edachleger(a)yahoo.com> wrote:
> What do you use to generate the network?
> The osmocombb-phone or other bts?
> cheers
> Erich
>
> ________________________________
> Fra: Pavel Baturko <pabftk(a)gmail.com>
> Til: baseband-devel(a)lists.osmocom.org
> Sendt: Mandag, 7. januar 2013 21.04
> Emne: MDL-Error in case of OsmocomBB+OpenBTS
>
> Hi list,
>
> I'm trying to connect my OsmocomBB phone to OpenBTS and I always got
> MDL-Error in mobile app log when MS trying to perform LU.
> Part of log (full mobile log in attach):
> <0001> gsm48_rr.c:355 new state connection pending -> dedicated
> <0005> gsm48_mm.c:3911 (ms 1) Received 'RR_EST_CNF' from RR in state wait
> for RR connection (location updating) (sapi 0)
> <0005> gsm48_mm.c:404 starting T3210 (loc. upd. timeout) with 20.0 seconds
> <0005> gsm48_mm.c:924 new state wait for RR connection (location updating)
> -> location updating initiated
> <0001> gsm48_rr.c:4984 MDL-Error (cause 3) ignoring
> <0001> gsm48_rr.c:4987 MDL-Error (cause 3) aborting
> <0001> gsm48_rr.c:355 new state dedicated -> idle
>
> In wireshark trace (from OpenBTS, attached) I see that MS sends LURequest
> (packet 359) and BTS responds with LUAccept (packet 440) but MS never
> receive this message because of error.
>
> As I understand this is "unsolicited UA response" from 08.58 (9.3.22) but I
> do not know how to fix that or properly debug.
> I'm using latest sylvain/testing and official OpenBTS 2.8. "Usual" (not with
> OsmocomBB) phones works with OpenBTS fine and OsmocomBB phones works fine
> with "usual" (not OpenBTS) networks.
>
> Thanks,
> Pavel
>
>
Hi list!
As described in Nico Golde's talk at 29c3, mobile operators can deactivate
encryption on MT SMSes. To check if a MT is encrypted I've started 'mobile'
with GSMTAP, and I've sent an sms to the mobile. Encryption seems to be
requested by the network. Now the question is: how can I be sure that
encryption is always activated? Should I exaustively send messages to the
mobile in order to look for unecrypted messages? Or is there some other
way? People who give stats about MNO do exaustive tests, or simply generate
a bunch of events and campute stats on those results?
Thanks for your answers/opinions.
Dario.
Hi guys
This is a question related to the compilation system of osmocom-bb. For an
unknown reason, something has gone wrong with my compiled binaries, so now
I would like to clean up everything as it was freshly checked out, before
restarting the compilation. How can I do it? Make clean and make distclean
seem not to be enough, since my compilation now fails with:
cd ./doc && tar cf html.tar */html
make[3]: Leaving directory
`/home/dario/Projects/mobile/osmocom-bb/src/shared/libosmocore/build-target'
make[2]: Leaving directory
`/home/dario/Projects/mobile/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: Leaving directory
`/home/dario/Projects/mobile/osmocom-bb/src/shared/libosmocore/build-target'
cd host/layer23 && ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBOSMOCORE... no
configure: error: Package requirements (libosmocore) were not met:
No package 'libosmocore' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS
and LIBOSMOCORE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [host/layer23/Makefile] Error 1
How can I clean up everything?
Any help appreciated.
Thanks
Dario.
Hi list,
I'm trying to connect my OsmocomBB phone to OpenBTS and I always
got MDL-Error in mobile app log when MS trying to perform LU.
Part of log (full mobile log in attach):
<0001> gsm48_rr.c:355 new state connection pending -> dedicated
<0005> gsm48_mm.c:3911 (ms 1) Received 'RR_EST_CNF' from RR in state wait
for RR connection (location updating) (sapi 0)
<0005> gsm48_mm.c:404 starting T3210 (loc. upd. timeout) with 20.0 seconds
<0005> gsm48_mm.c:924 new state wait for RR connection (location updating)
-> location updating initiated
<0001> gsm48_rr.c:4984 MDL-Error (cause 3) ignoring
<0001> gsm48_rr.c:4987 MDL-Error (cause 3) aborting
<0001> gsm48_rr.c:355 new state dedicated -> idle
In wireshark trace (from OpenBTS, attached) I see that MS sends LURequest
(packet 359) and BTS responds with LUAccept (packet 440) but MS never
receive this message because of error.
As I understand this is "unsolicited UA response" from 08.58 (9.3.22) but I
do not know how to fix that or properly debug.
I'm using latest sylvain/testing and official OpenBTS 2.8. "Usual" (not
with OsmocomBB) phones works with OpenBTS fine and OsmocomBB phones works
fine with "usual" (not OpenBTS) networks.
Thanks,
Pavel
I've done it and now everything works, thanks. But I've noticed that this
requirement is not documented anywhere. Wiki should be updated or new users
will stuck at this point.
On Mon, Jan 7, 2013 at 7:00 PM, Erich Dachleger <edachleger(a)yahoo.com>wrote:
> Did you install libosmocore first?One must do that now
> regards
> erich
>
>
Hi list,
I want to play with the mobile_app with TX and SIM-card support, so I checkout the sylvain/testing branch described in the wiki but the following error message occurs.
The master branch work's very fine on my HW (C123).
Can someone give me a hint, what should I do to get a working testset with SIM support?
Here the shell-output by makeing sylvain/testing branch
......
CC gsm411_sms.o
gsm411_sms.c: In Funktion »gsm340_rx_tpdu«:
gsm411_sms.c:228:19: Warnung: Variable »sms_mms« gesetzt, aber nicht verwendet [-Wunused-but-set-variable]
gsm411_sms.c: In Funktion »gsm411_rx_rp_ud«:
gsm411_sms.c:375:2: Warnung: Format »%li« erwartet Argumenttyp »long int«, aber Argument 7 hat Typ »int« [-Wformat]
gsm411_sms.c: In Funktion »gsm411_tx_sms_submit«:
gsm411_sms.c:657:3: Warnung: Übergabe des Arguments 4 von »gsm411_smc_init« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/home/kasio/osmocom-bb/src/shared/libosmocore/include/osmocom/gsm/gsm0411_smc.h:46:6: Anmerkung: »int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)« erwartet, aber Argument hat Typ »int (*)(struct gsm411_smc_inst *, int, struct msgb *)«
gsm411_sms.c:657:3: Fehler: zu viele Argumente für Funktion »gsm411_smc_init«
/home/kasio/osmocom-bb/src/shared/libosmocore/include/osmocom/gsm/gsm0411_smc.h:46:6: Anmerkung: hier deklariert
gsm411_sms.c:659:3: Fehler: zu viele Argumente für Funktion »gsm411_smr_init«
/home/kasio/osmocom-bb/src/shared/libosmocore/include/osmocom/gsm/gsm0411_smr.h:27:6: Anmerkung: hier deklariert
gsm411_sms.c: In Funktion »gsm411_rcv_sms«:
gsm411_sms.c:911:4: Warnung: Übergabe des Arguments 4 von »gsm411_smc_init« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/home/kasio/osmocom-bb/src/shared/libosmocore/include/osmocom/gsm/gsm0411_smc.h:46:6: Anmerkung: »int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)« erwartet, aber Argument hat Typ »int (*)(struct gsm411_smc_inst *, int, struct msgb *)«
gsm411_sms.c:911:4: Fehler: zu viele Argumente für Funktion »gsm411_smc_init«
/home/kasio/osmocom-bb/src/shared/libosmocore/include/osmocom/gsm/gsm0411_smc.h:46:6: Anmerkung: hier deklariert
gsm411_sms.c:913:4: Fehler: zu viele Argumente für Funktion »gsm411_smr_init«
/home/kasio/osmocom-bb/src/shared/libosmocore/include/osmocom/gsm/gsm0411_smr.h:27:6: Anmerkung: hier deklariert
make[3]: *** [gsm411_sms.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/kasio/osmocom-bb/src/host/layer23/src/mobile'
make[2]: *** [all-recursive] Fehler 1
make[2]: Verlasse Verzeichnis '/home/kasio/osmocom-bb/src/host/layer23/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlasse Verzeichnis '/home/kasio/osmocom-bb/src/host/layer23'
make: *** [host/layer23/layer23] Fehler 2
kasio@T60:~/osmocom-bb/src$
Thanks a lot for your help.
kasio
Hey Baseband,
I've got a stock of SIMs I bought and programmed already, but I
unfortunately (and stupidly) forgot to set the SMSC. This is causing me
heaps of issues, as each phone now has to have the SMSC set manually. I was
hoping to hack up a quick script which just inserts the SMSC onto the SIM
without needing to regenerate the ki or IMSI. Lining those up with my
database is rife with hazard.
Looking at the pySim-prog, it looks like this probably isn't possible; all
of the data seems to get bundled together and so changing the SMSC length
will cause other data to be corrupted. Is that right? I just wanted to see
what ya'll think would be the best way for me to remedy my particular
stupidity.
Thanks!
Hi list,
I'm running layer23 apps on the Application Processor of the OpenMoko
GTA02, which is also an ARM. I noticed that some parts of code try to
access words in memory which are not naturally aligned.
[ The first symptom was "Err from socket: Bad address" given by
osmocon. This is because a bogus length header read from the L2 unix
socket was overflowing a static 4K buffer. The bogus length was due
to an unaligned uint16_t write in osmo_send_l1() -- for an
L1CTL_DATA_REQ I think. ]
The easy and inefficient workaround for this is to ask the kernel[1]
to fix up these accesses:
echo 3 > /proc/cpu/alignment
Cheers,
Alex
[1] http://lxr.linux.no/#linux+v3.7.1/Documentation/arm/mem_alignment
