I have a plethora of femtocells (small base stations) I want to get rid of.
If you want it, it's yours, for free. You just need to cover the shipping costs.
Else it will become the property of Trash Inc.
Here the list of 3G femtocells:
- Cisco residential signal box USC3331, model 74-12584-01, PID USC3331-EE-K9. The flash (TSSOP) is desoldered but in the box (just is case you need to dump it). Just resolder it and it should work fine.
- 2x Vodafone (Greece) Access Gateway UAP2105. One is open, but nothing is missing. 5 pair of board to board connectors are included. This is the one first model that has been hacked.
- Vodafone Sure Signal AP 2820V. A cute plug style 3G femtocell. modded for serial output and external power supply (so the serial is not mains referenced). I have doc on how to root and flash it. Sadly it misses little effort for interfacing it with osmocom, but is the best candidate for such a project.
- Vodafone Sure Signal AP 2820V. not modded.
- Ubiquisys ZP-000-05EU, aka SerComm. Flash is desoldered and in the packages. Serial output is available.
- SFR Home 3G G2, Ubiquisys ZP-004-01FR. serial is available. This is the one I hacked and reflashed for a MitM attack back in 2011
- yet another Vodafone (Greece) Access Gateway UAP2105. already open. should work, but else perfect donor board.
- SFR Home 3G G3, FEM-SER-r0. flash is desoldered and in package.
Here the list of 4G femtocells:
- Samsung Verizon 4G LTE Network Extender, model SLS-BU103
- 3x T-Mobile (USA) Personal 4G LTE CellSpot, 9961 Home Cell V1. one is open and has plenty of test points soldered.
just let me know if you are interested.
Hi all,
I have an ip.access NanoBTS 139U (Part No 139U V 139U V351800). I
believe it is operating on the 1800 MHz although admittedly that's a
guess from the part number. I've not found a definitive way of
confirming the supported band via Telnet or otherwise.
I can see the BTS attempting to connect to the BSC, but after the "Set
Radio Carrier Attributes" request from the BSC, the BTS sends a NACK
and the OML link is dropped.
<0004> abis_nm.c:984 OC=RADIO-CARRIER(02) INST=(00,00,ff): SET
RADIO ATTRIBUTE NACK CAUSE=Message cannot be performed
<0004> osmo_bsc_main.c:226 Got SET RADIO ATTRIBUTE NACK going to
drop the OML links.
I've grabbed some debug info, note that in the PCAP the packets are
wrapped in TZSP as I used a Mikrotik to stream them to Wireshark.
Log from BSC -
https://s3.eu-west-2.amazonaws.com/cdn.marrold.co.uk/files/osmocom/osmobsc_…
PCAP -
https://s3.eu-west-2.amazonaws.com/cdn.marrold.co.uk/files/osmocom/NanoBTS.…
It's worth noting that ipaccess-config tool also has an issue parsing
the frequency which may well be related:
ipaccess-config -G 10.0.130.101
ipaccess-config (C) 2009-2010 by Harald Welte and others
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
Trying to connect to ip.access BTS 10.0.130.101...
OML link established using TRX 0
getting Attributes (3): 88 91 86
rc"" 0 <0004> abis_nm.c:652
OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Get Attributes Response:
Primary OML IP is 10.0.130.111:0
<0004> abis_nm.c:658 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff):
Get Attributes Response: Unit ID is 1800/0/0
<0004> bts.c:497 (bts=0) Unsupported frequency band.
<0007> abis_nm.c:725 (bts=0) BTS config invalid, dropping BTS!
<0007> bts_ipaccess_nanobts.c:624 (bts=0) Deferring Drop of OML link.
<0007> input/ipaccess.c:431 Bad signalling message, sign_link
returned error: Invalid argument.
<0007> bts_ipaccess_nanobts.c:557 (bts=0) Dropping OML link:
Deferred link drop
Thanks in advance
Matthew / marrold
Hello,
In the next couple of days I plan on getting started on configuring a
simple Osmocom based GSM stack with all the key components, to use
with a single 1800 MHz Nano BTS.
Before I get too stuck in, I wanted to check if running in Docker
(Straight Docker, no kubernetes etc) was feasible, and if the various
packages behave when NAT etc is involved?
Thanks
Matthew / marrold
Dear Osmocom community,
we're happy to announce the next incarnation of OsmoDevCall]].
when:
November 16, 2022 at 20:00 CET
where:
https://meeting5.franken.de/b/har-xbc-bsx-wvs
This time, @fixeria will be presenting on
MS/BS power control support in OsmoBSC/OsmoBTS
For those not entirely 3gpp-acronym-savyy: That's how the uplink (phone
-> network) and downlink (network -> phone) transmit RF power level is
adjusted during an active call in GSM.
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation as outlined above
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you soon!
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello Osmocom community,
Vadim (fixeria) invited me to give a presentation on some of my topics
of expertise on OsmoDevCall; I have given some thought to which topics
I could present on, and I have two proposals:
Presentation 1: Themyscira Wireless: GSM network in sunny California.
In this presentation I will describe the community GSM network I am
building in my corner of the world, using Osmocom CNI software and
whatever BTS hardware fits the bill, currently just one sysmoBTS.
Whereas most well-known community GSM networks such as Rhizomatica
have been built in areas with no commercial cellular coverage of any
kind, my use case is very different: I live in an area where every
square mm is blasted with super-strong 4G and 5G signals from 3 major
carriers, but a community GSM network is needed in order to provide
service specifically to *vintage* mobile phones, which require 2G.
I will cover this unusual telos and the different design choices that
stem from it, I will cover my own software that interfaces to OsmoMSC
via MNCC, and I will cover my interface to USA PSTN via SIP with G.711
voice, including my own implementation of transcoding MGW.
Presentation 2: Calypso chipset history and development boards, from
TI to FreeCalypso. In this presentation I will cover the history of
TI Calypso chipset itself (silicon and DSP revisions, ABB and RF
chips), the history of TI's original support for these chips
(reference fw and development boards), how various commercial Calypso
device vendors changed things (very small changes in the case of
Openmoko, huge changes in the case of Compal), how I entered the scene
with my FreeCalypso brand, and the impact of two most recently
discovered modem modules: Huawei GTM900 and iWOW TR-800. I will cover
my motivations and upcoming new hardware plans, and at the end I would
like to engage in a discussion on how to make FreeCalypso-suitable hw
(meaning hw suitable for running full FC solution) more readily and
less expensively available to interested players.
I have added both of the above talk proposals to the wiki page:
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
but of course nothing is scheduled yet. Given that the schedule is
booked many months in advance these days, it is now up to the community
to decide what y'all are interested in, and if there is interest in
both topics, which should be scheduled first.
Sincerely,
Lady Mychaela N. Falconia,
Mother of FreeCalypso,
Dame of the Order of 2G,
Champion of Published Source Code
