Hello,
anyone has experience to use application mobile on pirelli ?
there is no layer1.compalram.bin for this model,
any ideas how to run app mobile?
Sincerely Yours,
Tsaregorodtsev Yury
Bridge Communication Billing & Settlement Plan Limited
Fernhills Business Center, Foerster Chambers,
Todd Street Bury, Gtr Manchester, BL9 5BJ
United Kingdom
Tel: +441570200000
ICQ: 622719210
MSN: y.tsaregorodtsev(a)live.com
Skype: tsarik-108
web: www.bridgecommunication.co.uk
Hi
I wonder if there is a way to develop a Denial of Service or Conditional Access system for a GSM network based on Osmocom. The idea is to develop a commercial product intended to be used to limit unlawful communication in prisons or correctional facilities. My investigation is that this is a kind of worldwide necessity as inmates use smuggled mobile phones for criminal activities (I live in Central America and constantly see news that confirm this is urgent requirement). Currently there a few options available to achieve this purpose:
1. Government authorities require telecom operators to reduce radio signal in the vicinity of confinement facilities2. The use of radio jamming systems to propagate a noise signal3. One or two commercial solutions like iNAC Managed Access from Tecore (a very clever and patented technology)
I imagine a solution based on Osmocom as a base station simulating a roaming area in the correctional facility area, for authorized users, dummy network should appear as a FPLMN but for illegal users the fake network must grant access entering driving them into a dead end network with no communication. However I see there are several flaws for this aproach: one is that inmates could set their mobiles to manual network selection and connect themself to commercial mobile networks but I hope this could serve as a ground for further discussion. I will appreciate very much your comments. Regards,
Hi
I thought I try to flash some osmocom tools into a C118.
I have the loader loaded succesfully onto the C118.
I can do a finfo (see below)
So I wanted to backup the complete flash:
osmoload memdump 0x000000 0x200000 c118.bin
-> I get "bad crc" for every page
Same when I try to backup the loader as on the flashing wiki.
Dumping 8192 bytes of memory at 0x0 to file compal_loader.bin
bad crc 4190 (not 5c9a) at offset 0x00000000
bad crc f041 (not d50d) at offset 0x000000f0
bad crc f041 (not 3afa) at offset 0x000001e0
Is the C118 not supported for flashing?
Can somebody give me any helpful hints?
CU, Ricsi
chip 0 at 0x00000000 of 2097152 bytes in 2 regions
region 0 with 31 blocks of 65536 bytes each
block 0 with 65536 bytes at 0x00000000 on chip 0
block 1 with 65536 bytes at 0x00010000 on chip 0
block 2 with 65536 bytes at 0x00020000 on chip 0
block 3 with 65536 bytes at 0x00030000 on chip 0
block 4 with 65536 bytes at 0x00040000 on chip 0
block 5 with 65536 bytes at 0x00050000 on chip 0
block 6 with 65536 bytes at 0x00060000 on chip 0
block 7 with 65536 bytes at 0x00070000 on chip 0
block 8 with 65536 bytes at 0x00080000 on chip 0
block 9 with 65536 bytes at 0x00090000 on chip 0
block 10 with 65536 bytes at 0x000a0000 on chip 0
block 11 with 65536 bytes at 0x000b0000 on chip 0
block 12 with 65536 bytes at 0x000c0000 on chip 0
block 13 with 65536 bytes at 0x000d0000 on chip 0
block 14 with 65536 bytes at 0x000e0000 on chip 0
block 15 with 65536 bytes at 0x000f0000 on chip 0
block 16 with 65536 bytes at 0x00100000 on chip 0
block 17 with 65536 bytes at 0x00110000 on chip 0
block 18 with 65536 bytes at 0x00120000 on chip 0
block 19 with 65536 bytes at 0x00130000 on chip 0
block 20 with 65536 bytes at 0x00140000 on chip 0
block 21 with 65536 bytes at 0x00150000 on chip 0
block 22 with 65536 bytes at 0x00160000 on chip 0
block 23 with 65536 bytes at 0x00170000 on chip 0
block 24 with 65536 bytes at 0x00180000 on chip 0
block 25 with 65536 bytes at 0x00190000 on chip 0
block 26 with 65536 bytes at 0x001a0000 on chip 0
block 27 with 65536 bytes at 0x001b0000 on chip 0
block 28 with 65536 bytes at 0x001c0000 on chip 0
block 29 with 65536 bytes at 0x001d0000 on chip 0
block 30 with 65536 bytes at 0x001e0000 on chip 0
region 1 with 8 blocks of 8192 bytes each
block 31 with 8192 bytes at 0x001f0000 on chip 0
block 32 with 8192 bytes at 0x001f2000 on chip 0
block 33 with 8192 bytes at 0x001f4000 on chip 0
block 34 with 8192 bytes at 0x001f6000 on chip 0
block 35 with 8192 bytes at 0x001f8000 on chip 0
block 36 with 8192 bytes at 0x001fa000 on chip 0
block 37 with 8192 bytes at 0x001fc000 on chip 0
block 38 with 8192 bytes at 0x001fe000 on chip 0
Hi List
I have just reactivated my Pirelli Osmocom phone, and recompiled osmocom-bb.
(after rolling back libosmocore it works great)
But can it be that charging is not implemented on the Pirelli phone with OsmocomBB?
When I attach the MiniUSB cable, I can upload the code great, but when I leave it running for a longer time, it booted into the default charging pirelli screen.
I assume that the battery is not that good any more, and it seems that it is running on battery power instead of on USB power.
When I upload the RSSI app to the phone it shows me an empty battery icon in the right.
(Pirelli SW showed completely full battery icon)
Can somebody confirm that the pirelli phone is not charging in osmocom-bb?
Is there a chance tha somebody is looking into this anytime?
CU, Ricsi
PS: Is it still correct that the jolly/test branch is the best for 2 phone transceiver (for OpenBTS/OpenBSC)?
This branch should support 2 phones.
But as half rate channels are not supported you can only make one call.
(ie not possible to make a testcall without going over SIP)
Is this information still valid?
Does the current version of OsmocomBB supports
to run the layer 2 or the layer 3 on the baseband
chip, now?
I read through the arxiv of the mailing list but
have maybe overlooked this.
best,
\jo
mark.neuhaus(a)email.de wrote:
> Pleae, then tell me where to get phones with a Calypso
> baseband.
www.ebay.com
> And I'm talking about marked relevant prices.
> Don't waste my time with numbers like 5000$.
Several OsmocomBB-supported models are currently available on ebay for
dirt cheap.
> And to be relevant these phones must still be produced so
> I can get many, if I want.
How many? My company will be happy to produce 5000 Calypso-based
phones for you if you make a non-cancelable purchase order and prepay
the cost of parts and production. (5000 is the number of Calypso&co
chipsets I can buy immediately from my established supplier *without
doing any extensive searching*; one can probably get more with some
effort.)
> Beside, I think its better to work on reverse engineered
> GSM stacks like the Qualcom project as started in
It's easy to tell other people what they should work on. While you
are busy doing that, I'll just keep working on my own solution which
will actually result in a usable phone less than a year from now.
VLR,
SF
Someone (not clear who) said:
> > [...] The calypso is just to outdated to be interesting
> > for anything 'useable' beyond pure hacking-fun.
I violently disagree with that statement. I personally carry a
cellphone for one and only one purpose: so I can call my significant
other (soon to be wife) and she can cell me at any time. A handset
based on the Calypso chipset does this job wonderfully, and is IMO
the optimal tool for the job.
But the problem is that at the present time there does not exist any
cellphone at all, of any kind (dumb, smart, old, new, whatever) that
can make and receive cellular phone calls using only Free Software, as
defined by the Free Software Foundation, i.e., providing the user with
the most essential Four Freedoms:
http://www.gnu.org/philosophy/free-sw.html
Hence I am currently forced to use a cellphone that runs proprietary
firmware, such that I lack the ability to fix any of the UI design
flaws that constantly drive me nuts. This situation causes me severe
distress, hence I have committed my hobby time and cash budget to a
multi-year project to solve this pressing (for me) problem.
OsmocomBB is not a solution: it works wonders for "hacking-fun" (the
wording in the comment I'm responding to), but is utterly useless for
a practical phone which one can carry around in a pocket or purse: my
back just isn't strong enough to carry a supersized backpack containing
a full PC for running the L23 stack plus a bank of lead-acid batteries.
Hence I need a totally different Free Software GSM handset
implementation, one that actually runs on the phone itself with proper
power management exactly like the original proprietary firmware. And
because no one else is working on such a thing, I started my own, and
made quite a bit of progress:
https://bitbucket.org/falconian/freecalypso-sw
But I am using the same Calypso GSM chipset for my project as OsmocomBB
uses, simply because it is IMO the optimal tool for the job at hand:
allowing a person to communicate with his or her significant other by
way of cellular phone calls. The word "outdated" does not exist in my
vocabulary; I evaluate a tool based on how well it does the job, rather
than some arbitrary irrelevant criteria like manufacture date stamps
or whatever.
Viva la Revolucion,
SF