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.
Hi guys,
I think some of us would like to move to redmine and start using public tickets more frequently. So in case we move there are some topics to be discussed and I would like to start with a couple of them right now.
Tickets:
Redmine has a global linear sequence of ticket numbers. If we move from many tracs to a single redmine we can either:
* not import tickets
* only import from one project
* deal with changing ticket numbers
In terms of installations the GMR trac is broken in regard to tickets, there are some for SDR that are probably not being fixed anytime soon, baseband might be relevant and OpenBSC is unlikely to be relevant. I don't think we have ever used ticket reference in OpenBSC commit messages so in terms of OpenBSC having changing ticket numbers would not be a big deal. E.g. we could add a custom field with the old trac number?
Wiki:
We have external references that should be redirected to the new place. Is there any way besides maintaining a list in the apache2/nginx configuration and making redirects as we find broken references? Can we proactively manage this? Is anybody willing to come up with a script and nginx configuration for doing this?
kind regards
holger
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
Dear all,
I suggest to change a stock Redmine theme to something more beautiful,
for example gitmike: https://github.com/makotokw/redmine-theme-gitmike
which used by srlabs.de and looks like pretty. Furthermore, the Osmocom
logo will look better on light background.
Opinions?
С наилучшими пожеланиями,
Яницкий Вадим.
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,
I would first like to thank all those who participated in this nice
project.
I recently started working with osmocombb and was able to have it working
fine on a motorola c118.
However, I noticed that some sim cards can connect normally to the BTS, can
make calls and send SMS but can’t receive anything. They simply don't get
paged. While for some other sim cards everything seems to be working fine.
Does anyone know what might be causing this issue ?
thanks,
Robert
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
Look at this strings from your log:
<0005> subscriber.c:601 Requesting SIM file 0x2fe2
<000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000f> sim.c:697 go MF
<000f> sim.c:241 SELECT (file=0x3f00)
<000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
<000f> sim.c:876 received APDU (len=0 sw1=0x00 sw2=0x00)
<000f> sim.c:952 command failed
<000f> sim.c:151 sending result to callback function (type=1)
<0005> subscriber.c:657 SIM reading failed
Maybe something wrong with your SIM? Try another one.
Are you at the master branch?
С наилучшими пожеланиями,
Яницкий Вадим.
Hi,
Can someone confirm if the steps described in http://bb.osmocom.org/trac/wiki/flashing are still valid, as I can’t find “loader.e88loader.bin”. I’m using sylvain/testing branch.
Best regards,
Robert,
Did you enabled TX support (CFLAGS += -DCONFIG_TX_ENABLE)?
Also try to use an IMEI from existing MS, because sometimes PLMN
can reject MSes with default IMEI.
С наилучшими пожеланиями,
Яницкий Вадим.
Dear all,
IN-Berlin has confirmed the dates in April where we could book the
venue.
Can those eligible + interested in attending please quickly indicate
their preference at http://doodle.com/poll/if263cpxieavsqiq ?
Thanks!
Disclaimer: OsmoDevCon is an invitation-only event for developers with
proven history of contributing to any of the Osmocom projects. The fact
that there is a public poll about the scheduling of the event and/or
your participation in that poll does not mean a particular applicant is
invited.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
Hi!
> Can we still use osmocomBB phones (C140,C139..) with Osmo-BTS project?
Yes.
I use transceiver program from *jolly/testing* branch and
> firmware in compal_86 ( trx.highram.bin ) from *sylvian/testing* branch,
> all from osmocomBB.
>
>
Stop doing this mix. The firmware from one branch you use incompatible with
host software form another. Use one branch only!
It looks like you have a new toolchain "gnu-arm-build.3.sh". The firmware
images from this branches works better if it's compiled with older
toolchain version.
Try to use
http://bb.osmocom.org/trac/attachment/wiki/GnuArmToolchain/gnu-arm-build.2.…
or https://github.com/axilirator/gnu-arm-installer.
I know that Calypso BTS support only one timeslot.
>
>
Using two phones you will be able to serve two timeslots.
Follow this guide I recently wrote:
http://bb.osmocom.org/trac/wiki/Tutorials/CalypsoBTShttp://openbsc.osmocom.org/trac/wiki/SDR_OsmoTRX_network_from_scratch is
outdated.
С наилучшими пожеланиями,
Яницкий Вадим.
Hi all!
Moving all projects to a Redmine is a good way, I think.
In connection with the event I would like to offer my help with
post-processing some old pages (mostly OsmocomBB) and with
improving the new wiki structure.
So, my suggestions:
- Create the main page that will describe all all of the child projects
of Osmocom umbrella including recent news and plans.
- Separate the libosmocore related pages from OsmocomBB
into a new section named "Libraries", for example.
- Separate both SIMTrace and softSIM into a new sections.
It it would be nice to enable Strict-Transport-Security to avoid
some traffic interception attempts. Also what about enabling
SPF and DKIM for mailing lists?
With best regards,
Vadim Yanitskiy.
2016-02-19 4:46 GMT+06:00 <openbsc-request(a)lists.osmocom.org>:
> Send OpenBSC mailing list submissions to
> openbsc(a)lists.osmocom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osmocom.org/mailman/listinfo/openbsc
> or, via email, send a message with subject or body 'help' to
> openbsc-request(a)lists.osmocom.org
>
> You can reach the person managing the list at
> openbsc-owner(a)lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBSC digest..."
>
>
> Today's Topics:
>
> 1. Re: autoreconf v2.69 with subdir-objects: ./configure creates
> directory 'src/tests/\$(top_srcdir)' (Neels Hofmeyr)
> 2. Re: hnb_cs_lu.msc (Neels Hofmeyr)
> 3. Re: hnb_cs_lu.msc (Harald Welte)
> 4. branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;
> merging to master (Neels Hofmeyr)
> 5. Re: Moving from trac to a single redmine (Harald Welte)
> 6. Re: Moving from trac to a single redmine (Holger Freyther)
> 7. Re: branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;
> merging to master (Holger Freyther)
> 8. sysmocom/iu: your commits from today (Neels Hofmeyr)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 17 Feb 2016 15:44:35 +0100
> From: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
> To: Eric Blake <eblake(a)redhat.com>
> Cc: bug-autoconf(a)gnu.org, openbsc(a)lists.osmocom.org
> Subject: Re: autoreconf v2.69 with subdir-objects: ./configure creates
> directory 'src/tests/\$(top_srcdir)'
> Message-ID: <20160217144435.GD2106@dub6>
> Content-Type: text/plain; charset="us-ascii"
>
> Eric,
>
> you've clarified just about all of my questions.
> Many thanks for your reply!
>
> ~Neels
>
> > https://lists.gnu.org/archive/html/automake/2015-12/msg00001.html
>
Hi,
Is it possible to route a call from a phone connected to openBSC (virtual BTS) to a real network using an osmocombb phone. In other words, to give a user within my own network the ability to call another phone connected to any other operator without routing the call through internet.
Hi,
*Can we still use osmocomBB phones (C140,C139..) with Osmo-BTS project?*
I use transceiver program from *jolly/testing* branch and
firmware in compal_86 ( trx.highram.bin ) from *sylvian/testing* branch,
all from osmocomBB.
It is the only way to get phones start sync on particular arfcn.
If I write this configuration in osmo-bts.cfg:
*!! OsmoBTS () configuration saved from vty!!!log stderr logging color 0
logging timestamp 0 logging level all everything logging level rsl info
logging level oml info logging level rll notice logging level rr notice
logging level meas notice logging level pag info logging level l1c info
logging level l1p info logging level dsp debug logging level abis
notice!line vty no login!phy 0 instance 0bts 0 band 900 ipa unit-id 1801
0 oml remote-ip 127.0.0.1 trx 0 phy 0 instance 0*
I can make launch *osmo-bts-trx* program.
After launching *osmo-nitb*, Osmo-BTS is writing this log:
<000b> trx_if.c:379 transceiver (phy0.0) rejected TRX command with
response: 'RSP POWERON -22'
<0001> bts.c:203 Shutting down BTS 0, Reason SIGINT
and when shutdown timer is elapsed, Osmo-BTS exit writing this log:
Shutdown timer expired.
*What should I put into osmo-bts.cfg and openbsc.cfg to make thing work ?*
I know that Calypso BTS support only one timeslot.
Tried to modify openbsc.cfg to support only one TS, by putting:
*timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1
phys_chan_config NONE timeslot 2 phys_chan_config NONE timeslot 3
phys_chan_config NONE timeslot 4 phys_chan_config NONE timeslot 5
phys_chan_config NONE timeslot 6 phys_chan_config NONE timeslot 7
phys_chan_config NONE*
But BSC is compling with this configuration.
Thanks in advance
--
*Puno pozdrava,Mirko Kovačević*
Hi!
> Then I believe the following SPF record should be provided for
> lists.osmocom.org:
> "v=spf1 a mx a:gandharva.secretlabs.de -all"
What for "a:gandharva.secretlabs.de" is in this string?
С наилучшими пожеланиями,
Яницкий Вадим.
Hi all,
I think we are close to the point of no return. All tickets and wikis have been imported. Please have a quick look if there is something obviously broken and if not I will proceed with post-processing and renaming tonight.
kind regards
holger
Hi!
But when tried to follow this guide:
>
> http://bb.osmocom.org/trac/wiki/SIMReader
>
This guide is outdated. Currently the master branch can perform R/W
operations with SIM without any problems. Just use it.
С наилучшими пожеланиями,
Яницкий Вадим.
Hello,
In this tutorial:
http://bb.osmocom.org/trac/wiki/SIMReader
Some parts for me were confusing like this one:
"git clone git://git.osmocom.org/osmocom-bb.git
cd osmocom-bb
git checkout -b testing remotes/origin/sylvain/testing"
and this one:
diff --git a/src/target/firmware/Makefile b/src/target/firmware/Makefile
(diff --git Does not work on Ubuntu 15.04)
I tried this instead of aforementioned:
mkdir osmocombb
git clone git://git.osmocom.org/osmocom-bb.git master
cd master/src
make
cd ~/osmocombb
git clone git://git.osmocom.org/osmocom-bb.git -b sylvain/testing
testing
Then I uncommented line with #CFLAGS += -DCONFIG_TX_ENABLE inside
osmocombb/master/src/target/firmware/Makefile
cd master
make
And then followed rest of wiki guide.
Any comment?
Thanks.
Robert.
Hello,
I've installed osmocombb software on Ubuntu 15.04 according to this
guide on wiki:
http://bb.osmocom.org/trac/wiki/Software/GettingStarted
No problem so far at this point, everything compiles, layer1 runs on
Motorola C123 via cable etc.
But when tried to follow this guide:
http://bb.osmocom.org/trac/wiki/SIMReader
I'm getting errors after running make inside src directory, and beside
that I think that wiki guide is bit unclear here:
diff --git a/src/target/firmware/Makefile b/src/target/firmware/Makefile
On my Ubuntu 15.04 diff --get alone gives error 'diff: unrecognised
option '--git'.
I tried also via Vi to uncomment -# on -#CFLAGS += -DCONFIG_TX_ENABLE
line inside /src/target/firmware/Makefile and compile but to no
avail...
Any help with this?
Thanks in advance :)
Robert.
Hello guys,
I am looking for a way to disable the vocoder for voice calls, i.e.,
supply my own 260 bits every 20 ms to be sent in the uplink TCH
instead of the output from the vocoder in the Calypso DSP, and on the
downlink, receive the bits which would otherwise go into the vocoder.
My question is: is it possible to do what I seek using the know-how of
Calypso DSP black magic that has already been amassed by the OsmocomBB
project? I am thinking of the following 3 possible starting points:
1. LCR integration: the mobile app can be configured to route voice
call audio to the Linux host instead of the phone's earpiece and
mic, right? At which point does it intercept the standard voice
path? Does it intercept right where I want it, passing raw
over-the-air TCH bits to the external host, such that Asterisk or
whatever has to run the GSM codec, or is the intercept happening at
the point of linear PCM samples, such that the uplink TCH bits are
still generated by the DSP black box?
2. The burst_ind branch lets the Linux host see every burst that is
received on the downlink, right? It would therefore include TCH
bursts during voice calls, right? This way I should be able to
capture all of the raw TCH bits on the downlink - but what about
the uplink?
3. I've also read about the Calypso-as-BTS hack - way cool! In order
to work, this hack must support both receiving and transmitting
arbitrary bursts, right? If neither option 1 nor option 2 would
work, do you guys think the Calypso-as-BTS implementation code
would serve as a starting point for what I seek? I do need to run
the OsmocomBB phone in the standard MS role, not in the BTS role,
and I need to place voice calls on the network in the standard
manner - but with TCH rerouted to my own source and sink for raw
over-the-air bits.
TIA for any guidance!