hi,
a while ago i've read that someone managed to have an active phone call over
osmocom for about 20mins.
i woundered if it is theoretically & technically possible to have an active,
serious (thus not a5) encryption running
for voice or data calls on the stack?
thanks in advance & greetings from vienna ;)
azet
Hi everyone. I'm admittedly more a lurker than an active participant in this
project. I find it very fascinating and regard its objectives as important.
I recently watched several of the C3 presentations, from this and previous
years. Having open, documented hardware and software seems to be an
important goal in itself. Just knowing about all the potential weaknesses in
the software stacks of most phones, as well as hidden "features" like SMS
messages that could, theoretically, do things like remotely enable the phone
mic, among other things (things that are certainly technically possible, and
also due to the closed nature of the software, completely unknown) are of
grave concern to me.
Now, given that the supported phone hardware is old and not reliably
available, I was wondering if anyone knows if the Calypso and other chips in
these old phones are still available for new designs? How much interest
would there be, say, in an open, but VERY SIMPLE, actual phone? Kind of like
the Pandora project, but without the ambition to make the most advanced
portable game player possible.
The Osmocom software would then be very easily portable to such a device.
Given the seemingly widespread interest and enthusiasm for the Osmocom,
OpenBTS, and OpenBSC projects, a real, genuinely open phone (not a
pseudo-open phone like the FreeRunner) might possibly have enough interest,
and be buildable for a low-enough cost, to merit further discussion.
Anyone want to discuss this?
Hi!
A number of people want to do some long-term evaluation of their cellular
environment and would be interested in an 'app' for OsmocomBB that continuously
scans the spectrum and dumps the cell parameters such as
* ARFCN, Signal Level, SNR
* frequency synch offset
* SCH info (BCC/NCC)
* SI (at least 1-4) from BCCH
I would love to do it, but I simply don't have the time. I thought maybe
somebody on this list is looking for a relatively simple task and has some
time. I think this is a great project to work with OsmocomBB without having
to go into the details.
The algorithm would look something like
STATE 1: Power Scan
* do power measurement over all supported bands
* pick strongest N carriers and iterate over them
STATE 2: FCCH/SCH acquisition
* try to get lock on the carrier
* if not, go back to next carrier from power scan
* if yes, continue with STATE 3
STATE 3: Wait until all relevant SI have been received
* generate GSMTAP output for the SI messages (or timeout)
* go back to STATE 2 for next strongest ARFCN
* after last ARFCN, re-start from STATE 1
This is basically the initial step of the GSM 03.22 cell (re)selection
that we already have as part of the 'mobile' program.
So all the code is there, but what's needed is a separate rady-made app,
not requiring any user interaction. It should also include some e.g. shell
script that automatically generates a new pcap file every N minutes/hours,
and make sure to never overwrite any existing PCAP file.
In the end, having this running for an extended period of time should simply
produce a large number of PCAP files without any manual interaction. Lock-ups
in any state should be detected by timers, singalling a proper L1_RESET
to make sure it continues. Unplugging / re-plugging the phone should also
not require any re-start of the program.
Optional extensions:
* software to aggregate info from the pcap files (remove duplicate
entries, e.g.)
* optional logging of GPS coordinates from a GPS receiver
If anyone has some time to give this some work, I'd most appreciate it. Please
inform the mailing list to ensure no duplicate work is created.
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)
Everyone,
Is it true you can use a MTK Chipset as a DIY GSM BTS/USRP ?
I've emailed this fellow who posted this back in December 2010
but have gotten no reply to date.
This would be excellent for use on something I'm working
on in Africa for about 50 - 100 IMPOVERISHED villages.
Awaiting anyone's input on this.
Thank you
SoftwareDefinesRadio
2010/12/15 <baseband-devel-request(a)lists.osmocom.org>
>
>
> Today's Topics:
>
> 1. Price Cheap of USRP for openbts and GSM ( ???? )
>
>
> ---------- Forwarded message ----------
> From: "麦田守望" <775725965(a)qq.com>
> To: "baseband-devel" <baseband-devel(a)lists.osmocom.org>
> Date: Wed, 15 Dec 2010 14:18:50 +0800
> Subject: Price Cheap of USRP for openbts and GSM
>
> Hello everybody
> you may have USRP USE MTK chip phone for DIY yourself BTS Simple and
> Practical i find Developmenter Contact me
>
>
if i boot the c118 from a ubuntu 10.04 lts (64bit) or a g20 arm minipc i get
this here
/opt/osmocom/bin/osmocon -m c123 -p /dev/ttyUSB0
/opt/osmocom/firmware/board/compal_e88/layer1.compalram.bin
got 2 bytes from modem, data looks like: 2f 81 /.
got 5 bytes from modem, data looks like: 00 f6 02 00 41 ....A
got 1 bytes from modem, data looks like: 01 .
got 1 bytes from modem, data looks like: 40 @
got 1 bytes from modem, data looks like: 66 f
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6d m
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6c l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65 e
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 00 .
if i boot it from my mac book or a ubuntu (32bit) i get this:
osmocon -m c123xor -p /dev/tty.usbserial
sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin
got 6 bytes from modem, data looks like: 00 00 00 00 00 00 ......
got 1 bytes from modem, data looks like: 2f /
got 1 bytes from modem, data looks like: 81 .
got 1 bytes from modem, data looks like: 1b .
got 1 bytes from modem, data looks like: f6 .
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 41 A
got 1 bytes from modem, data looks like: 01 .
got 1 bytes from modem, data looks like: 40 @
Received PROMPT1 from phone, responding with CMD
read_file(sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin):
file_size=54152, hdr_len=4, dnload_len=54159
got 1 bytes from modem, data looks like: 1b .
got 1 bytes from modem, data looks like: f6 .
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 41 A
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 43 C
Received PROMPT2 from phone, starting download
handle_write(): 1023 bytes (1023/54159)
handle_write(): 1024 bytes (2047/54159)
handle_write(): 1024 bytes (3071/54159)
handle_write(): 1024 bytes (4095/54159)
handle_write(): 1024 bytes (5119/54159)
handle_write(): 1024 bytes (6143/54159)
handle_write(): 1024 bytes (7167/54159)
handle_write(): 1024 bytes (8191/54159)
handle_write(): 1024 bytes (9215/54159)
handle_write(): 1024 bytes (10239/54159)
handle_write(): 1024 bytes (11263/54159)
handle_write(): 1024 bytes (12287/54159)
handle_write(): 1024 bytes (13311/54159)
handle_write(): 1024 bytes (14335/54159)
handle_write(): 1024 bytes (15359/54159)
handle_write(): 1024 bytes (16383/54159)
handle_write(): 1024 bytes (17407/54159)
handle_write(): 1024 bytes (18431/54159)
handle_write(): 1024 bytes (19455/54159)
handle_write(): 1024 bytes (20479/54159)
handle_write(): 1024 bytes (21503/54159)
handle_write(): 1024 bytes (22527/54159)
handle_write(): 1024 bytes (23551/54159)
handle_write(): 1024 bytes (24575/54159)
handle_write(): 1024 bytes (25599/54159)
handle_write(): 1024 bytes (26623/54159)
handle_write(): 1024 bytes (27647/54159)
handle_write(): 1024 bytes (28671/54159)
handle_write(): 1024 bytes (29695/54159)
handle_write(): 1024 bytes (30719/54159)
handle_write(): 1024 bytes (31743/54159)
handle_write(): 1024 bytes (32767/54159)
handle_write(): 1024 bytes (33791/54159)
handle_write(): 1024 bytes (34815/54159)
handle_write(): 1024 bytes (35839/54159)
handle_write(): 1024 bytes (36863/54159)
handle_write(): 1024 bytes (37887/54159)
handle_write(): 1024 bytes (38911/54159)
handle_write(): 1024 bytes (39935/54159)
handle_write(): 1024 bytes (40959/54159)
handle_write(): 1024 bytes (41983/54159)
handle_write(): 1024 bytes (43007/54159)
handle_write(): 1024 bytes (44031/54159)
handle_write(): 1024 bytes (45055/54159)
handle_write(): 1024 bytes (46079/54159)
handle_write(): 1024 bytes (47103/54159)
handle_write(): 1024 bytes (48127/54159)
handle_write(): 1024 bytes (49151/54159)
handle_write(): 1024 bytes (50175/54159)
handle_write(): 1024 bytes (51199/54159)
handle_write(): 1024 bytes (52223/54159)
handle_write(): 1024 bytes (53247/54159)
handle_write(): 912 bytes (54159/54159)
handle_write(): finished
got 1 bytes from modem, data looks like: 1b .
got 1 bytes from modem, data looks like: f6 .
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 41 A
got 1 bytes from modem, data looks like: 03 .
got 1 bytes from modem, data looks like: 42 B
Received DOWNLOAD ACK from phone, your code is running now!
OSMOCOM Layer 1 (revision osmocon_v0.0.0-737-ga4e3431-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: c1900c14ae021565
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1880!
-- its working :-)
I have tried to copy the firmware from the working machine to the bad
machines but the result is the same.
Is it possible that the usb driver from ubuntu 10.04 lts 64bit is silly????
cable (akku-king) phone all is the same on every plattform.
Have some body an Idea?
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-on-ubuntu-64bit-tp22208…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi All,
I'm really struggling to get the latest source to build on OSX. Would anyone be
kind enough to offer some assistance to getting this compiled?
Build fails with:
./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,'
./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)'
Any help or advice would be appreciated!
Many Thanks,
Matt.
Hi,
just for curiosity, I would like to get the osmocomBB running on the
Motorola C123. Everything works fine (radio starts scanning for
networks) if I use the test SIM feature. But reading a real SIM plugged
into the phone does not work for me.
The 'mobile' app shows:
<0004> subscriber.c:556 Requesting SIM file 0x2fe2
<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000e> sim.c:697 go MF
<000e> sim.c:241 SELECT (file=0x3f00)
<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
-end-
Any hints where to start debugging?
(does neither work with 3 different SIMs: swisscom, blau, super-sim)
BTW: Are there any plans to support external SIM readers via PC/SC etc.?
Thanks
Frank
Hi,
I'm playing around with Osmocom for a while now. My final goal is to use
it as a stationary phone on a PC to be able to remotly control the phone.
I checked out the sylvain/testing tree, to use my SIM card and managed to
be able to make and receive calls. Very amazing so far. :-)
Now I tried to send GSM codes (like *#21#, oder *21*{NUMBER}#) to set and
unset call diverts. It seems, that "call 1 *21*{NUMBER}#" does not work.
Normal GSM cellphones seem to handle these codes not as a normal call.
Does anybody know how one could send GSM codes to the network?
Thanks
Tim