Hello friends,
I've tried to get openbsc running on CentOS, but because of a missing
driver (which interfaces between libdbi and sqlite3) it was not a
succes. So I removed CentOS and installed Debian Lenny, as I kinda
noticed most of you work with Debian.
Anyway I managed to install and configure the openbsc with some
exceptions. Because I don't use BS-11, but a nanoBTS instead, so I
didn't patched the kernel for the mISDN card.
I tried the ipaccess-find first, which worked (after I modified my ip
hardcoded in the source).
Than I tried to configure the nanoBTS using the ipaccess-config as
described in this site http://bs11-abis.gnumonks.org/trac/wiki/nanoBTS,
but with our ip addresses ofcrouse.
That seems to work, but the program doesn't return, I don't know if that
is the case. I assume I get response if the nanoBTS gets connected with
the OpenBSC.
Than I executed the bsc_hack for the nanoBTS (thus I give the
appropriate parameters as described on the webpage), and I get the
following error:
DB: Database initialized.
DB: Database prepared.
mi_setup could not open socket Address family not supported by protocol
Can someone please tell me where to look at?
If it's a simple error, just tell me which source does something with
mi_setup, otherwise more info would be fine.
Thank you.
P.S.: I'm a bit new to Linux, so please be patient with me.
Hi,
I followed Debian_Getting_Started chapter in the wiki. There wasn't any
error but, after rebooting, the kernel crashed:
Booting 'Debian GNU/Linux, kernel 2.6.27.4'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.27.4 root=/dev/hda1 ro quiet hfcmulti.dslot=1
[Linux-bzImage, setup=0x3000, size=0x1796901]
[0.000000] Unknown boot option 'hfcmulti.dslot=1': ignoring
[0.796125] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
I tried first to delete "hfcmulti.dslot=1" at the kernel line but still have
the second line.
After checking the /boot/grub/menu.lst file, I saw that the line initdr was
missing for the kernel 2.6.27.4:
title 2.6.27.4
root
kernel
title 2.6.26.2
root
kernel
initdr
In /boot directory, I have initdr files only for 2.6.26.2 and 2.6.26.1.
Sorry I am quite weak concerning the kernel.
Can anyone help me?
Thanks a lot
Eric Cathelinaud
hi,
finally the layer 4 interface of openbsc is done. also LCR
(linux-call-router) talks to libbsc. this turns both into a complete
network. libgsm (compiled to LCR) provides audio transcoding. even
asterisk can use it via "chan_lcr" driver.
today i got my first call to a friend from mobile via fixed network.
(because harald did not answer on the first try, he could not receive
the previledge of the first call.)
before i begin providing patches and documentation, i will make some
stability tests.
have a nice weekend..
jolly
Hello Andreas,
On Sat, 9 May 2009 21:14:48 +0200, "Andreas.Eversberg" <Andreas.Eversberg(a)versatel.de> wrote:
>
> finally the layer 4 interface of openbsc is done. also LCR
> (linux-call-router) talks to libbsc. this turns both into a complete
> network. libgsm (compiled to LCR) provides audio transcoding. even
> asterisk can use it via "chan_lcr" driver.
>
> today i got my first call to a friend from mobile via fixed network.
> (because harald did not answer on the first try, he could not receive
> the previledge of the first call.)
>
> before i begin providing patches and documentation, i will make some
> stability tests.
Sounds great, congratulation :-)
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello,
I have an Issue related to my Debian OpenBSC.
Every time I fire up openbsc everything goes well like the btse
alignement/db alignement on lmt and there are no errors on lmt.
Only openBSC tells me after the initial state were the net should be
up, that the oc or some module(ill add more details later on today) is
"in test".
So this looks like the issue to me why the net wont come up.
But sometimes it works (sometimes it helps to restart the bts but it
wont help everytime).
Im a bit curious why the In test is appearing while lmt (the gui app)
tells me that everything is as it should be...
As far as I know this normally tells me that the object is in Test
mode and is checked because requested on lmt.
May this also be a timing issue on the abis link?
Im writing from iPhone in bed so enough for now.
I would be glad if someone could help/ has an idea.
By the way Ill be at SIGINT09 in Cologne helping out at the GSM
Workshop.
Who will be there too?
Best Regards
Björn Heller
Hello Christian,
On Thu, 30 Apr 2009 03:13:33 +0200, "hotshot" <hotshot(a)koeln.ccc.de> wrote:
>
> Unfortunately I see the same behavior (even with restarting the
> BS-11) as in E1-locked ('hfcmulti' and 'hfcmulti port=0x200) - a
> network scan shows either your BS-11 or the other networks and only
> sometimes you see all networks
In the latest OpenBSC version there is support to show the "Set Value"
and the "Work Value" of the PLL setting. The "Set Value" is the
configuration value from the factory. The "Work Value" is not 100%
clear yet but most certainly it is the value the PLL is actually
using. In "Locked" mode the PLL follows the E1 clock and the
"Work Value" can change quite a lot. Switching to "Standalone"
mode seems to freeze the current "Work Value". The question now
is if the PLL still used this "Work Value" in "Standalone" mode.
If yes and the "Work Value" is off by a large amount the clock is
not accurate (although its most certainly stable) and you still
won't the test network and the other networks at once.
If the "Work Value" of your BS-11 is off by a large amount from
the "Set Value" you can try to switch to "Locked" mode and watch
if the "Work Value" follows the E1 clock. If its close to the
"Set Value", switch back to "Standalone" mode.
I have not tested this and I don't know a better way yet (I don't
think the "Work Value" can be set from the outside) but you can
give it a try.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Harald,
On Fri, 17 Apr 2009 10:17:13 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote:
>
> Dieter, what I just found out is that the LI object has a user-configurable
> setting, where we can force it to be stand alone or locked to the E1.
>
> We could add this setting to the bs11_config program so people can try
> if their E1 clock or their [10 years uncalibrated] BS11 internal oscillator
> is better.
>
> What do you think?
I did a quick test with this setting and it seems to work fine
with the BS-11 (so we should not believe the documentation ;-).
Here is the LMT dump for the PLL Mode, it can be changed during
normal operation:
; Locked
Tx D0A5070000FC0102
Rx D1A5070000FC0102
; Standalone
Tx D0A5070000FC0103
Rx D1A5070000FC0103
A little bit strange is the behaviour of NM_ATT_BS11_CCLK_ACCURACY,
if the PLL Mode is set to "Standalone", it changes to "high accuracy",
however if you restart the BS-11, this attribute stays at "medium
accuracy". Maybe NM_ATT_BS11_CCLK_ACCURACY has no meaning if the
PLL Mode is set to "Standalone".
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hallo Bjoern,
> I tried it several times,
> and left the BTS on over night.
> The LMT cable wasn't always plugged in.
> When I boot up the BTS it always says that the second TRX
> has Load and the first not.
You did turn the power off for a restart, just to be sure ?
> If I try to bring up the BTS with your SW under Win.
> I get the Abis Link Up but when I try the Load DB I get some
> error messages on LMT.
> Then the second TRX goes down to No Load.
If the firmware for the first TRX is not loaded, the Abis
communication will still work because the microcontroller
which takes care about the commnunication is working. The
error messages result from the not working TRX (I guess
it would work if TRX1 instead of TRX0 is used, however I
have not tried it yet).
> And this is the condition until I reboot the BTS.
> Maybe its a software issue?
I don't think so because the communication processor loads the
same firmware in both TRX. This is done in parallel. In your
trace there is the same behavior I experience here, loading the
firmware for TRX0 ad TRX1 starts, however loading TRX0 stops
immediately. Of course I can only speak for my BS-11, but here
it is most certainly a hardware issue (at one time I could even
see an error message that the first power supply unit did not
start).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
i must check with cologechip (vendor), if the subvendor id is correct, then i will check it into the GIT.
-----Ursprüngliche Nachricht-----
Von: openbsc-bounces(a)lists.gnumonks.org [mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Harald Welte
Gesendet: Montag, 27. April 2009 10:12
An: Nico
Cc: openbsc(a)lists.gnumonks.org
Betreff: Re: [patch] support for recent Single E1 PCI ISDN cards tolinux-2.6.27.4
Hi Nico,
On Sun, Apr 26, 2009 at 12:54:36AM +0200, Nico wrote:
> Here's a patch I've been using to get a SingleE1 PCI ISDN card (recently
> bought from Junghanns.NET) to work with the hfcmulti.ko driver. I'm not
> sure the mapping between the PCI subdevice id and the driver data is
> right, but at least the card can "talk" to the BS-11 now.
Thanks for your patch. I think this should be forwarded to the mISDN folks for
mainline inclusion. Andreas Eversberg (reading this list) is heavily involved
with them, maybe he can take care of that.
> I'm curious if any of you are also using such cards and how they get
> them to work.
I've so far only worked with HFC-E1 evaluation boards so far, sorry.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)