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
Hi,
I didn’t find anything useful yet. Everything seems normal during the IMSI attach procedure (location updating request, authentication request/response, identity request/response …), I can call and send SMS normally but the phone doesn’t get paged in any way. It seems strange that no differences can be seen during the IMSI attach procedure while some sim cards do not work.
On Mar 4, 2016, at 7:13 PM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote:
> GSM specs, it is.
>
> On 04.03.2016 17:32, robert wrote:
>>
>> I read about sim card types since it must be a sim card problem but I didn’t find anything useful.
>>
>>
>> On Mar 4, 2016, at 6:05 PM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote:
>>
>>> A good start would be a look into the specifications.
>>>
>>>
>>> On 04.03.2016 14:31, robert wrote:
>>>>
>>>> Hi,
>>>>
>>>> I tried two sim cards one that works fine and another one that doesn’t get paged, I noticed that during the location update procedure everything is exactly the same (using wireshark). The log files are also similar. Although both cards work fine if used in a normal phone (even with a motorola c123/118 …).
>>>>
>>>> Another thing to mention is that some sim cards only work when i stick them on a BTS that has the "SI type 3, GPRS indicator" as follows:
>>>> "3G Early Classmark Sending Restriction: Neither UTRAN, CDMA2000 nor GERAN IU MODE CLASSMARK CHANGE message shall be sent with the Early classmark sending"
>>>> while they can only make calls without being able to receive anything on other BTS where the "SI type 3, GPRS indicator" is as follows:
>>>> "3G Early Classmark Sending Restriction: The sending of UTRAN,CDMA2000 and GERAN IU MODE CLASSMARK CHANGE messages are controlled by the Early Classmark Sending Control parameter"
>>>> I would be very grateful if anyone has some explanations to what is going on.
>>>>
>>>>
>>>>
>>>> Best regards,
>>>> Robert,
>>>>
>>>>
>>>> On Jan 26, 2016, at 6:30 PM, Tomcsányi Domonkos <domi(a)tomcsanyi.net> wrote:
>>>>
>>>>> Hi Robert,
>>>>>
>>>>> I think it would help us out a lot if you could provide at least one complete log file from the output of the mobile app, so we can start having some ideas.
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Domi
>>>>>
>>>>>
>>>>>> 2016. jan. 26. dátummal, 17:24 időpontban robert steve <robert.steve07(a)gmail.com> írta:
>>>>>>
>>>>>> 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
>>>>>
>>>>
>>>
>>
>
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,
we are now running our own copy of patchwork at https://patchwork.osmocom.org. In addition to single patches this version can track series and has a REST API and git-pw client support. The system is currently subscribed to the GPRS, OpenBSC and OsmocomBB mailinglist.
The installation is running offlineimap every couple of minutes to fetch new mail, this means it can take some minutes for your comment or patch to be visible.
kind regards
holger
I'm trying to flash the EMI app on a C140 using this tutorial:
http://bb.osmocom.org/trac/wiki/flashing_new
I can't fine menu.e86loader.bin file so I've flashed the menu.compalram.bin
instead.
All seem to be fine, but if I press the power button the screen doesn't turn on.
I've made this procedure many times, but without success.
Instead if I flash it in the ram, it work great.
Why?
Hi,
Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air.
Best regards,
Robert,
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?
С наилучшими пожеланиями,
Яницкий Вадим.
Hallo zusammen,
ich wollte toolchain auf meinem Backtrack5r3 als VM installieren, dabei sind
Fehler aufgetreten die ich nicht verstehe.
Wie kann ich da Abhilfe schaffen?
Bis hierhin war noch alles gut.
GNU ARM toolchain
This page will describe the procedure for compiling a GNU ARM toolchain. We
will build a toolchain consisting of:
* GCC 4.8.2
* Binutils 2.21.1
* Newlib 1.19
Getting the buildscript
First of all, create a directory you want to use for building the toolchain,
and download the buildscript
<http://bb.osmocom.org/trac/raw-attachment/wiki/GnuArmToolchain/gnu-arm-buil
d.3.sh> gnu-arm-build.3.sh there. You will need to make it executable:
$ chmod +x gnu-arm-build.3.sh
Dependencies
In order to build the toolchain, you will need to install the following
packages (assuming you're using a Debian-based distribution):
$ sudo apt-get install build-essential libgmp3-dev libmpfr-dev libx11-6
libx11-dev texinfo flex bison libncurses5 \
libncurses5-dbg libncurses5-dev libncursesw5 libncursesw5-dbg
libncursesw5-dev zlibc zlib1g-dev libmpfr4 libmpc-dev
Preparation
Open a shell in the directory of gnu-arm-build.sh and create the following
directories:
$ mkdir build install src
Download the needed sources to src/:
$ cd src/
$ wget http://ftp.gnu.org/gnu/gcc/gcc-4.8.2/gcc-4.8.2.tar.bz2
$ wget http://ftp.gnu.org/gnu/binutils/binutils-2.21.1a.tar.bz2
$ wget ftp://sources.redhat.com/pub/newlib/newlib-1.19.0.tar.gz
Building the toolchain
$ cd ..
$ ./gnu-arm-build.3.sh
I will build an arm-none-eabi cross-compiler:
Prefix: <YOURPATH>/install
Sources: <YOURPATH>/src
Build files: <YOURPATH>/build
Press ^C now if you do NOT want to do this.
Dann kam folgendes, als wenn er Probleme mit den Ordnern hatte.
cid:image001.jpg@01D17613.420C17C0
Könnt ihr mir weiterhelfen?
Gruß Peseta3
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
Can it be done without using LCR ?
On Mar 4, 2016, at 10:21 AM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote:
> It should not be a problem.
>
> Have a nice day,
> Dennis
>
> On 03.03.2016 18:47, robert wrote:
>> Hi,
>>
>> Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air.
>>
>>
>> Best regards,
>> Robert,
>
On Mar 4, 2016, at 10:21 AM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote:
> It should not be a problem.
>
> Have a nice day,
> Dennis
>
> On 03.03.2016 18:47, robert wrote:
>> Hi,
>>
>> Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air.
>>
>>
>> Best regards,
>> Robert,
>
Hello,
I hope that this email finds you in good health. I am working on
implementing the call handover part of mobility management in the OsmocomBB
code as part of my Senior Year Project in University. I would like to ask
you a few things about what you have implemented. Your help will guide me a
lot in my endeavor. Please let me know whenever we can skype or call.
Thanks and Regards,
Ahmed
