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
Hi lists!
It's no secret for everyone, that today OsmocomBB is not actively maintained
as well as OpenBSC, for example. I think it's mostly due to supported
hardware
limitations. Currently supported platforms is still a bit of 'black box'.
Moreover every day it's harder to find and buy a new one.
Fortunately, there are many SDR platforms available now. Especially
interesting
devices are USRP, UmTRX, bladeRF, and recently introduced LimeSDR. They can
be
easily programmed to support just about any type of wireless standard, of
course,
including some mobile telecommunication stacks. As well as for network side
back-end,
they can be used to perform MS side operations, excepting frequency-hopping
and some
phone specific features (like SIM I/O).
So, I think there is a way to bring a new live to, amazing child of the
Osmocom
umbrella, OsmocomBB. We can make one work on SDR hardware platforms
implementing
a 'bridge' between both already implemented L2/L3 and OsmoTRX. I know that
there
already was some attempts (see sylvain/ms-sdr branch) to make described
dreams
come true, but development was stopped. And now I am going to start to work
around
this direction.
What for?
- GPRS and EDGE support
- More flexible voice routing
- Multi SIM support
- Next generation networks support (UMTS, LTE)
- ...
Currently I am looking for developers interested in this subject. So, any
ideas
and contributions are welcome! Together we can realize all the things
faster and
create a new area of research and development. Also for me it's very
important to
know opinions of Osmocom community members and exactly OsmocomBB
founders/developers.
Thanks!
С наилучшими пожеланиями,
Яницкий Вадим.
Hi all,
I have been using C123 for a long time with FTDI cable.
I recently bought a C139 on which I wanted to run layer1 fw, i check the SW
version using #02# and software version is "1.3.29", UART Flag is "0"
On going through the mailing list I found these to be sufficient for using
osmocom-bb but some how there is a problem on loading.
When I use the fwg command
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the following
got 2 bytes from modem, data looks like: 04 81 ..
got 5 bytes from modem, data looks like: 1b f6 02 00 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(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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(): 4096 bytes (4096/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
handle_write(): finished
It receives prompt2 and loads the file but doesn't move ahead, the phone
does not show layer1 on the screen either.
when i use fwg command (add -m c140xor )
./osmocon -p /dev/ttyUSB0 -m c140xor -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the fwg:
got 1 bytes from modem, data looks like: 04 .
got 1 bytes from modem, data looks like: 81 .
got 5 bytes from modem, data looks like: 1b f6 02 00 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(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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(): 4096 bytes (4096/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
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: 57 W
Received MAGIC NACK from phone, you need to have "1003" at 0x803ce0
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
It now move ahead and says the received MAGIC NACK and also that you need
to have "1003" at 0x803ce0, this is a documented problem and i believe in
compal_e86 binaries must have been taken care of.
Any ideas on how can I get around this and load the firmware on my c139 ? I
am again usung the same cable FTDI which works perfectly with c123.
My setup is native Ubuntu 14.04 , host machine and Intel i5.. (hw does not
seem to be the problem)
Looking forward to hear from you guys. Thanks in advance.
Regards,
Ajay
merlinsignals.blogspot.in
Hi all,
I have been using C123 for a long time with FTDI cable.
I recently bought a C139 on which I wanted to run layer1 fw, i check the SW
version using #02# and software version is "1.3.29", UART Flag is "0"
On going through the mailing list I found these to be sufficient for using
osmocom-bb but some how there is a problem on loading.
When I use the fwg command
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the following
got 2 bytes from modem, data looks like: 04 81 ..
got 5 bytes from modem, data looks like: 1b f6 02 00 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(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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(): 4096 bytes (4096/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
handle_write(): finished
It receives prompt2 and loads the file but doesn't move ahead, the phone
does not show layer1 on the screen either.
when i use fwg command (add -m c140xor )
./osmocon -p /dev/ttyUSB0 -m c140xor -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the fwg:
got 1 bytes from modem, data looks like: 04 .
got 1 bytes from modem, data looks like: 81 .
got 5 bytes from modem, data looks like: 1b f6 02 00 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(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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(): 4096 bytes (4096/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
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: 57 W
Received MAGIC NACK from phone, you need to have "1003" at 0x803ce0
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
It now move ahead and says the received MAGIC NACK and also that you need
to have "1003" at 0x803ce0, this is a documented problem and i believe in
compal_e86 binaries must have been taken care of.
Any ideas on how can I get around this and load the firmware on my c139 ? I
am again usung the same cable FTDI which works perfectly with c123.
My setup is native Ubuntu 14.04 , host machine and Intel i5.. (hw does not
seem to be the problem)
Looking forward to hear from you guys. Thanks in advance.
Regards,
Ajay
merlinsignals.blogspot.in
I am the project lead for the SHAKTI open source processor project.
See bitbucket.org/casl
This is a large Indian processor development effort that aims to develop
a range of processors (from uController to high end servers) based
on the RISCV ISA. We work closely with UCB and Cambridge as part of this
effort.
As part of our processor family, we have just started on a mobile SoC.
The goal is to have an octa core SoC with the performance of a
snapdragon 820 or the Apple A9. the CPU core is pretty much under
control but we are exploring the DSP needed for running the lower levels
of the 3G/LTE stack.
Another group does LTE stacks and so we have complete testing equipment
available to test for compliance.
I am basically looking for co-conspirators who can help identify the
components
I can use from the osmocom stack and figure out what else we need to
develop.
Then of course we need to develop the DSP core. We are currently reusing
the UCB vector processor and we are trying to figure out if a vector thread
processor or
a conventional DSP will do the trick.
Our goal is to have am SoC that will the functionality of a basic smart
phone
but we do not intend to focus only on a basic phone with voice/data
ca[ability but with basic display (even 4 line display is OK). Plan to use
the
AD SDR board for the SDR section. So it will be a large board that is
not optimized for size.
Any comments, thoughts appreciated . In case you are wondering, yes we
realize
this a mammoth task but we are well funded ! This is part of the India
processor project. And most importantly all our work will be patent free
open source. HW will be BSD, SW will be GPL3/2
--
Regards,
Madhu
I found a 1900 band analog booster/repeater to try.
> On Jun 20, 2016, at 2:32 PM, Erich Dachleger <edachleger(a)yahoo.com> wrote:
>
> Does anybody know if it would be possible to use some of the old vodaphone-femtocells together with openbsc/osmo-bts?
> RegardsErich
>
> Den Mandag, 23. mai 2016 11.46 skrev etienne . <etiennehelluy(a)gmail.com>:
>
>
> Short answer: no & no
> 1 - A gsm repeater is an analog device. With osmocom-bb phones you would need to demodulate/remodulate bursts.
> This wi
Hi guys,
I have a lot of problems using osmocom-bb with an Openmoko GTA02. First of all, I followed all the instructions from here [1] and uploaded layer1.highram.bin via external jack serial port (second tutorial). Well, after the firmware is downloaded on the phone osmocon prints:
"
Finished, sent 54 blocks in total
Received branch ack, your code is running now!
"
and nothing is printed anymore. Moreover, I see no activity on the serial port, all LEDs on my USB adapter being off.
When I try to run cell_log from my PC, it prints the following error message and blocks / does nothing:
"
Failed to connect to '/tmp/osmocom_sap'.
Failed during sap_open(), no SIM reader
<000e> cell_log.c:804 Scanner initialized
Mobile initialized, please start phone now!
"
I've read about this error and figured out that it is not fatal, but still cell_log doesn't work, nor does the 'mobile' application. I tried the code from master and from sylvain/testing branch and I uncommented "CONFIG_TX_ENABLE". I even tried hello_world.highram.bin and that doesn't print anything after loading it. I don't know what to do anymore.
[1] http://bb.osmocom.org/trac/wiki/OpenMoko#no1
Hello everyone!
During power measurement process we can see some messages like:
PM MEAS: ARFCN=8, 55 dBm at baseband, -83 dBm at RF
If I understood correctly, in this example received signal has
-83 dBm (about 5e-12 W) strength before amplifier and 55 dBm
(about 316.2 W) strength after one. It looks like the strength
of amplified signal should be printed as -55 (about 3.2e-9 W),
because 316.2 W is very high value. Am I right? Or is it internal
signal strength representation used by DSP?
С наилучшими пожеланиями,
Яницкий Вадим.