So far three persons have indicated their interest to join
a meeting at my place.
Considering the time it takes to drive to my place, it
probably makes sense to have the meeting at the weekend
(either Saturday or Sunday) so that there is more time
for the meeting itself. I can suggest one of the following
dates for the first meeting, somewhere between 10:00 to
18:00 on each day:
25.8. (Sa) or 26.8. (Su)
1.9. (Sa) or 2.9. (Su)
8.9. (Sa) or 9.9. (Su)
So please let me know when you have time and also make
suggestions in which Osmocom topic you are interested
in so that we can have some sort of agenda for the
meeting to make best use of the time.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello everyone,
I've just finnished writing together a small web interface for the OpenBSC
HLR. It allows you to modify various parameters in the database and also
provides a set of functions to modify the HLR or sending SMSes in your own
scripts.
The project is still very alpha but it seems to work reasonably good. Feel
free to give any feedback!
Screenshots and source code is available on my website:
https://stormhub.org/simplehlr/
--
*Best regards,
Peter Caprioli*
Hi,
We have two Nokia Insite BTSs and now we are configuring it to work
with OpenBSC.
But after we installed all the necessary parts (OpenGGSN, OpenSGSN,
OpenBSC) we got the following message:
"This BTS type does not support gprs"
I just wanted to ask that maybe we did something wrong, or the GPRS
support for Nokia InSite is not ready yet?
If the support is not ready yet maybe there is some alfa or beta stage
version that we can try?
Nokia Insite family supports GRPS CS-1 and CS-2 according to the
specification.
Thanks in advance!
Csaba
Hi folks
I pulled the latest repo of OpenBsc but upon compilation, it breaks while
running 'make'
Everything else compiled fine, libosmocore and libosmo-abis. I'm running
this on Ubuntu 12.04 LTS.
Here is the make error.
make[3]: Entering directory `/home/tyrus/openbsc/openbsc/src/libcommon'
CC common_vty.o
In file included from common_vty.c:30:0:
../../include/openbsc/bsc_nat.h:35:37: fatal error:
osmocom/sccp/sccp_types.h: No such file or directory
compilation terminated.
make[3]: *** [common_vty.o] Error 1
make[3]: Leaving directory `/home/tyrus/openbsc/openbsc/src/libcommon'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/tyrus/openbsc/openbsc/src'
make[1]: *** [all-recursive] Error 1
After fiddling around I couldnt find the sccp dir with its contents so when
i checked the git diff I found it was in this tree
http://git.zerfleddert.de/cgi-bin/gitweb.cgi/bs11/commitdiff/e9359db5803bae…
However when i manually created the files and dirs, it was just a
nightmare. Anyone with pointers how to fix this, ill really appreciate
-tyrus
Dear all,
(I'm sorry for cross-posting to several mailing lists, but it really
belongs to all of them. Please respond only to a mailing list you're
subscribed to.)
UmTRX sales start
===============
It's the Hardware Freedom Day and we're starting sales of UmTRX to
celebrate it! Now you could order it directly from Fairwaves web-shop
[1],
UmTRX is a completely open-source hardware SDR transceiver designed
for professional/industrial applications. We designed it for use with
OpenBTS software [2], but it also works well with OsmoBTS/OpenBSC [3].
UmTRX uses a UHD [4] with only minor changes to interact with a host
and thus works well with GnuRadio and other applications based on UHD.
1. http://shop.fairwaves.ru/
2. https://code.google.com/p/umtrx/wiki/RunningOpenBTS
3. http://openbsc.osmocom.org/trac/wiki/OsmoBTS
4. https://github.com/fairwaves/UHD-Fairwaves
Technical details
==============
UmTRX is an SDR transceiver inspired by USRP N series. If you worked
with USRP N you will find it familiar, but there are significant
differences which are described below as well.
* Single board with an integrated RF part.
* Optimized for industrial use and high MTBF.
* 1GbE Ethernet connectivity to a computer.
* Two full-duplex RF channels (side "A" and "B" in UHD).
* Single chip transceivers LMS6002D are used for AD/DA and RF
processing (300MHz to 3.8GHz)
* Stable reference clocks:
- 26MHz TCXO (integer multiple of GSM sample rate) with 100ppb
frequency stability.
- DAC for TCXO frequency fine tuning.
- Integrated GPS module for automatic TCXO frequency stabilization.
- External clock source is possible.
* Thermal sensors for temperature based calibration.
* 100mW @ 900MHz, 50mW @ 1800MHz RF output power.
* 8-28V DC input power supply.
* Spartan 6 LX75 FPGA.
PS Big thank you to Lime Microsystems for their excellent support of
open-source users! Check out their chips if you're planning to develop
and SDR system.
GSM specific info
==============
UmTRX was designed to be easy to use to use with OpenBTS and OsmoBTS.
So far it's the easiest way to get them up and running in your lab.
* Quad-band support without any changes
* 100-200m coverage (with an external duplexer and a small omni antenna).
* >2km coverage with an external 2W GSM repeater and a patch antenna
* Two independent TRXs (*).
* Single-ARFCN and Multi-ARFCN support.
(*) OpenBTS doesn't support the second channel on UmTRX yet. We're
working to implement this and plan to release this soon.
I also want to say thank you to our beta testers who received earlier
versions of UmTRX. Some of them even blogged about their experience :)
http://blog.shimaore.net/2013/03/umtrx.htmlhttp://genesysguru.com/blog/blog/2013/03/23/umtrx-is-alive-again/
UmTRX package contents
========================
* UmTRXv2.1, flashed and ready to use.
* Power supply, 12V/30W - http://www.phihong.com/assets/pdf/PSAC30U.pdf
* U.FL-to-SMA-F pigtail cables.
* Two small GSM antennas - one for Tx and one for Rx.
* An active GPS antenna.
* Thermal pads.
Note 1: The power supply comes without a 220V power cord. Make sure to
prepare one before you receive the UmTRX to be able to power it on
immediately. ;)
Note 2: You'll need a heatsink or a fan to prevent UmTRX from
overheating during long continuous operation. We provide thermal pads,
but you have to find a heatsink by yourself. HDD heatsinks are good
options, because UmTRX has almost the same size as an HDD.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hello.
Could you advice me where to read more about MNCC protocol?
openbsc/openbsc/include/openbsc/mncc.h references ETSI TS 100 940 which indeed has a
lot of variables like MNCC.RECALL.IND in call control diagrams - but where are the
reference to actual protocol?
I've tried to google but got tons of unrelated junk :(
Pardon if I'm asking smth obvious or already documented. Is there some library which
will let me easily create simple tool which speaks mncc with openbsc (libmsc)?
--
best regards,
Max, http://fairwaves.ru