I am trying to get OpenBSC working with Asterisk for a class project. I
have a NanoBTS DCS1800. I was hoping to get this to work entirely over
Ethernet, as the server is running on a controlled VM cluster with no way of
getting an add-on ISDN card in.
I have attempted to follow the OpenBSC+LCR+Asterisks route. But as
expected, LCR gives me issues when it does not find an ISDN card. I am not
familiar with LCR to tweak it. Can I use LCR without an ISDN card? What
should I look into to get this done?
I have also attempted to modify the asterisk chan_openbsc code to comply
with the libosmo break off earlier this year. With a few Makefile
adjustments, include a few more header files, and strip out some debuging
code, everything will compile. However, asterisk seg faults when the module
loads. The gdb output is:
Program received signal SIGSEGV, Segmentation fault.
0xb72fcd1d in cmd_execute_command_strict (vline=0x83d4c88, vty=0x83c2450,
cmd=0x0) at command.c:2000
2000 cmd_vector = vector_copy(cmd_node_vector(cmdvec,
vty->node));
I am not familar with this code, so all I can do is comment out things in an
attempt to debug. Eventually I keep it from crashing, and the nanoBTS will
make contact with the driver. However, since the code that gets commented
out also involves loading the cfg, the BTS does not get bootstraped. This is
all running on Gentoo, though I have also tried on Debian and Ubunto.
Any help would be appreciated.
Hello Andreas,
On Sun, 05 Dec 2010 00:28:27 +0100, "Andreas Galauner" <andreas(a)galauner.de> wrote:
>
> Also, the network sometimes is hard to find on the mobile phones. We
> blame a bad calibrated oscillator for that. As soon as we got an HFC-S
> card, we will try to recalibrate it.
As I mentioned here a few days before, its usually enough to
reset the PLL "work value" to its "set value" with bs11_config
("pll_workvalue" command) and set the PLL to standalone
("pll_standalone" command).
> Is it possible that all those problems show up because of the
> oscillator? And why did it work really well on Thursday?
I don't think that the problems with calls are related to the
oscillator, I would expect that this is related to the misdn
errors you see. Maybe the ISDN cable termination is not set
properly ?
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello everybody,
this is my first post to this list. I've been reading it for a while now
and I'm finally trying to get a bit deeper into GSM.
We have a BS11 in the C4 (Chaos Computer Club Cologne) which I got fully
working on Thursday this week.
We had several mobile phones in the network and called each other and we
could send and receive sms. All fine.
Today I wanted to test another few things and everything got weird:
I have 2 mobile phones authenticated in the network. One phone can call
the other one, it rings and after accepting the call, the first still
plays the "ringing sound", while everything on the second is silent.
Vice versa, if I call the first mobile from the second, it dials
endlessly. Sometimes OpenBSC segfaults. Before it does that, it tells me
on the console that timer T303 expired.
Another thing are those masses of "mISDN_send: error -12" messages in
the kernel log. We got those on Thursday, too but they weren't important
to us, because everything worked.
Nevertheless, sending and receiving SMS still works.
Also, the network sometimes is hard to find on the mobile phones. We
blame a bad calibrated oscillator for that. As soon as we got an HFC-S
card, we will try to recalibrate it.
Is it possible that all those problems show up because of the
oscillator? And why did it work really well on Thursday?
So far, I tried a few obvious things like rebooting, both the computer
and the BS11, cleaning and recompiling everything and I even deleted the
old HLR database.
I really don't know what to do else. <Insert helpless cry here> ;)
Does anybody of you have an idea what I can try?
We are running the latest OpenBSC from the git on a Debian testing with
a stock 2.6.32-5 kernel on i686.
Greetings,
Andy
Hello All,
Herr Thomas had raised up a discussion about problem with setting of BTS power attribute value.
In connection with this question, I recall another problem which has occurred with one of my BTS's.
It has a very strange behavior. Its output power is set to 2W. My measure device
tells me that receive level at the desired channel is about -24 dBm after station boot-up.
This value is very good, no other base station around shows better results.
But right after the very first GSM call the receive level quickly jumps down to -70 or
even -80 dBm, this value corresponds to 30mW of output power. BTS station still works
and output power is still shown as 2W.
This effect had been discovered with only one of my BTS stations, while other stations work well.
Does it mean that it's a hardware problem? Has anyone discovered this problem earlier?
Best Regards,
Sergey.
Hi,
I like to perform a TCH BER Test for nanoBTS via R&S CMU300. Does anyone know how to configure the nanoBTS using ipaccess-config to perform this BER test?
Thanks!
EGU
Hello Sergey,
On Thu, 2 Dec 2010 21:08:09 +0300, "Sergey V. Efimoff" <risky(a)mail.ru> wrote:
>
> I had once or twice seen BTS stations which had working PLL value
> very different from calibrated value. In order to get them close I had to
> use E1 hardware with high precision oscillator, then switch the
> hardware to the PLL-locked mode. This operation took me plenty
> of time.
>
> Please tell, is it possible to set the working PLL value directly?
Yes, bs11_config supports this. Its the "pll-workvalue" command. The
way how the PLL workvalue could be set was not obvious so it took a
while till we found out how this could be done. Thats the reason why
it took quite long till this command was introduced.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Sylvain,
On Thu, 2 Dec 2010 15:20:07 +0100, "Sylvain Munaut" <246tnt(a)gmail.com> wrote:
>
> The clock of the non working one might just be too off ...
>
> See http://openbsc.osmocom.org/trac/wiki/isdnsync for a tool to
> calibrate (with appropriate HW).
>
> If you don't have the equipement ... huh, good luck.
> You can always try random values until it works.
> If you have a USRP you can try to lock onto it and compare offset ...
Its possible to set the clock calibration to a fixed value, this was
a feature introduced a while ago. The original clock calibration
setting workes pretty good, at least from my experience. So if the
clock is off due to using the E1 clock as a reference, it should be
enough to set the orginal clock calibration value and switch the
PLL to standalone mode.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello all,
I'm going to be giving a presentation about free software GSM
implementations at the FSFE's Berlin meeting on December 9th, 2010. It
will be very elementary and newcomer-friendly. I'm planning to go
over OsmocomBB, OpenBTS and OpenBSC, and discuss their security and
practical implications.
The talk will start at 19:30 in Newthinking Store Tucholskystr. 48,
10117 Berlin. You can find more about it on
http://aligunduz.org/blog/free_gsm_talk_next_week.html
Considering I'm not an expert on GSM myself, it would be nice to have
people more familiar with it in attendance.
Ali Gündüz
On 12/01/2010 05:10 PM, Holger Hans Peter Freyther wrote
>* we still use the global bsc_gsmnet in many places. We need to remove that
to
*>* allow something like this.*
Is it a too much difficult process? Should i try to do this and where should
i start?
On 12/01/2010 05:07 PM, Sylvain Munaut wrote:
* >That's an option. See nv_put_prim_oml in ipaccess-config.c*
I think this is for changing the port of nanoBTS. Where should i modify the
port for bsc_hack?
Thanks.
Jason
**
*
*
hi
my 2nd bs11 doesnt work. the boot screen from bs11_config looks like
this(attached pic). both boot screens look like that, the operational
one too. the 2 bs11 are connected identical, the software is the same.
one works, the other doesnt. bad! the bootstrapping works on both, but
the handy can only detect the one of two bs11.
troubleshooting advices are welcome, openbsc website was no help
T.
--
Wer Rechtschreibfehler findet, darf sie behalten!
