Hello! I Need Help
I install these three programs OpenBTS, OsmocomBB, Asterisk
Then run them, Everything works well
OpenBTS sent an SMS to my phones
I answered and he checked me
I registered into OpenBTS a second phone
I tried to transfer SMS between phones - all good
but when I try to call from one to another I did not get
Asterisk writes
================================================================
*CLI> Retransmission timeout reached on transmission 755803415(a)127.0.0.1 for
seqno 179 (Critical Response) -- See
wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
================================================================
Why?
What do I do?
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp402…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hey there, I bumped into this error when testing gprsdecode from srldabs.de When I try the sample .dat files provided from srlabs.de it works fine though. Any hints?
Kind Regards
George AndguladzeSenior Software EngineerBusiness Management Technology
www.bmt.ge
Hey, I finally watched Nico's talk "let me answer that for you" and heard him say he ported layer2/3 to target.
Also found a mailing list message about him cleaning it up and putting it up on git and sending it to a few folks.
Did that code ever get shared? Would be cool to play around with and is certainly something I would eventually want to accomplish for my project of making a phone that works by itself.
-Craig
Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific
chipset.
When i run osmocon i get :- an its just sits there with no further
processing.
./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17120, hdr_len=4, dnload_len=17127
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17120, hdr_len=4, dnload_len=17127
got 1 bytes from modem, data looks like: 00 .
got 2 bytes from modem, data looks like: 2f 00 /.
got 1 bytes from modem, data looks like: 1b .
got 3 bytes from modem, data looks like: f6 02 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
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 .
got 1 bytes from modem, data looks like: 00 .
I think the cable is ok as when i run my fingers on the tip i get random
Zeros so it appears to be talking to the cable.
Also when i tried to run Mobile i get the :- even though i created the
Mobile.cfg file in /etc/osmoco
Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg'
Please check or create config file using: 'touch
/home/raz/.osmocom/bb/mobile.cfg'
I have spent some hours researching the lists and trying various things to
no avail but I want to continue until I resolve this issues and use this
great stack to learn about the GSM network.
Please advise.
Great full for any help or pointers but this maybe a timing issue that is
difficult to debug.
Thanks
Raz
hi,
i did a lot of resarch and testing on cell selection and re-selection
process the last two week.
the cell selection process, network selection process (manual and
automatic) and mobility management process were already implemented in
OsmocomBB a long time, but turned out to be buggy and incomplete. i made
test drives to check the process and debugged it.
the re-selection process is new. it is used to track surrounding cells
while listening to the BCCH of the current cell (camping on a cell).
special extension to the layer1 firmare is used to measure neighbour
cells. if an neighbour cell becomes 'better', the mobile switches to
that cell, depening on different criteria. now it is possible to move
with OsmocomBB.
the re-selection process is not handover! handover is a process where a
phone switches between cells while doing a call. handover is one next
step to implement. the process is a little more complex, because it
requires not only neighbour cell measurements, but also syncing to them
without interrupting the traffic channel. most layer 3 stuff of handover
is already implemented.
if you like to play and test your moving OsmocomBB, you can check out
the "jolly/roaming" branch. it contains the extension to layer1, as well
as sim reader and fixes from "sylvain/testing" branch. use both "mobile"
and "layer1" firmware from this branch.
in order to see some process at VTY, you can do:
enable
monitor network 1 (continously display the strongest cell and neighbour
cells)
show ms 1 (to see current states)
show neighbour-cells 1 (to see a more detailed current list of
neighbours)
andreas
Hi,
in the osmocom bb mobile.cfg I don't see any posibility to set a fixed
Kc encryption key and the tmsi.
How could I achieve that osmocom uses my defined Kc and tmsi?
cheers,
Simian
Hi all!
This is the announcement for the re-incarnation of our bi-weekly
Osmocom Berlin Meeting.
Oct 21, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin
There is no formal presentation this time, but
* there will be SDR equipment in case more people are interested
to have a look at MPT1327 and/or Tetrapol signals that can be
received in Berlin
* Harald would like to discuss OpenBSC website / documentation
improvements
The meeting is open to anyone interested in mobile communications. You
do not have to be involved with the Osmocom projects in order to attend.
Anyone interested in mobile communications protocols is welcome.
If you are interested to show up, feel free to do so. The meeting is
"free as in free beer", despite no actual free beer being around ;)
More information can be found at
http://openbsc.osmocom.org/trac/wiki/OsmocomMeeting/Berlin
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello,
I am using a SDR device (a BladeRF) and there is a nice tool called 'kal' that will show me all of my nearby GSM base stations.
In addition to listing base stations and their frequencies, I could also use that frequency info to monitor the beacon channel with gr-scan/airprobe.
So at this point I know:
- base station exists
- I know its frequency
- based on beacon channel assignments, etc., I *sort of* know how busy it is.
But what else can be learned about a particular base station with simply passive observation and no decryption (and no sim card) ? If all I have is a passive monitor with a SDR, what else can I learn frmo the beacon channel or from the station itself ?
Is it possible to learn things like software version, protocols supported, connectivity to network, or to other base stations ?
My goal is to learn about the GSM networks around me and I wonder how deeply I can understand them with just passive observation of the beacon channel (or other sources of info that can be seen with SDR).
Thank you.
Hi all!
This is an announcement for an "irregular" Berlin Osmocom User Group
event.
David Rupprecht of Ruhr-Uni Bochum has offered to give us a presentation
sharing his experience in Running OpenAirInterface.
OpenAirInterface (http://openairinterface.eurecom.fr/) is a project of
the Eurecom research institute in Sofia Antipoils / France. For many
years they have been working towards an open source SDR LTE
implementation.
The presentation will be held on
Oct 15, 8pm @ IN-Berlin, Lehrter Str. 53, 10557 Berlin
(yes, this is _NOT_ CCC Berlin where regular OSMUG meetings are held!)
The meeting is open to anyone interested in mobile communications. You
do not have to be involved with the Osmocom projects in order to attend.
Anyone interested in mobile communications protocols is welcome.
If you are interested to show up, feel free to do so. The meeting is
"free as in free beer", despite no actual free beer being around ;)
More information about the venue can be found at
http://www.in-berlin.de/space/
The official event announcement website is
http://openbsc.osmocom.org/trac/blog/david-rub-openair-20151015
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello,
I'm currently trying to use a Pirelli DP-L10 calypso phone as a
rudimentary BTS.
I have followed the instructions on
http://openbsc.osmocom.org/trac/wiki/network_from_scratch,
I'm using the jolly/testing branch of osmocom-bb and I've enabled TX
support in the Makefile.
The software runs on an xubuntu 14.04 x64 machine.
After uploading the firmware to the phones RAM via osmocon, it shows
that it's running osmocom-bb on the display, when I then try to run
transceiver with the following parameters: -e 5 -r 99 (or alternativly
-e 5 -a 958 to sync with german provider O2)
the phone just reboots and goes into a state where the keyboard
backlight is blinking with 0.5 hertz.
The last thing "transceiver" says is:
<0012> l1ctl.c:383 Reset received: Starting sync.
<000c> l1ctl.c:95 Sync Req
<000c> l1ctl_link.c:171 Sending: '01 00 00 00 83 be 00 64 27 10 03 20
03 07 00 00 00 '
and the last log messages from osmocon are:
DSP API Version: 0x3606 0x0000
LOST 7200!
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=33726, flags=0x7)
Dropping sample ':'
I'm not sure if I have configured the correct bands for
synchronization. I think it might have to do something with that.
I copy'd the default configuration from the osmocom-page stating DCS1800.
The only base station I'm seeing here is 958, which is in the GSM900R
range. Could this be the problem?
Have I overseen something simple? Have I provided all necessary
information about my setup? Any ideas?
It's probably not a power issue, I have tested it with a lab power
supply for providing the USB 5V and battery 4.2V, which resulted in
the same behavior.
Thanks,
Tobias
--
This email is encrypted with 2ROT-13.
Tobias Mädel
t.maedel(a)alfeld.de
PGP: 3A69 E9AF 3FA9 3BCF FE50 9694 494E 2F56 C304 60E1
http://tbspace.de
Hi all!
This is the announcement for the re-incarnated Osmocom Berlin meeting:
Oct 7, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin
Harald will be presenting about the Iuh protocol stack of UMTS small
cells / femtocells and his work towards implementing it as part of
Osmocom.
Agenda:
20:00h Welcome
20:15h Presentation about Iuh / osmo-iuh
21:00h Informal meeting / chatting
The meeting is open to anyone interested in mobile communications. You
do not have to be involved with the Osmocom projects in order to attend.
Anyone interested in mobile communications protocols is welcome.
If you are interested to show up, feel free to do so. There is no
registration required. The meeting is free as in "free beer", despite
no actual free beer being around.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Harald Welte <laforge(a)gnumonks.org> wrote:
> This is the announcement for the re-incarnated Osmocom Berlin meeting:
>
> Oct 7, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin
And for those who happen to be on the other side of the world (Southern
California instead of Germany, San Diego instead of Berlin), there is
this other meeting/presentation on a related topic happening about a
day and a half later in Universal Time:
http://www.meetup.com/kernel-panic/events/225595627/
> If you are interested to show up, feel free to do so. There is no
> registration required. The meeting is free as in "free beer",
Same for ours.
> despite no actual free beer being around.
While we don't serve beer either (for one thing, the venue who
graciously provide us with free meeting space would have a problem
with alcohol on the premises), we do usually have free refreshments as
in soft drinks and cookies.
M~