Hello Nordin,
On Fri, 14 Aug 2009 12:54:19 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
>
> Well it should at least know it is dealing with the nanobts, which is
> not the case.
> In function bootstrap_network() of bsc_hack.c the function
> vty_read_config_file() is called, and that's it. So bsc_hack.c does
> nothing with the config file. Furthermore, I can't seem to find where
> the bts->type is filled. So my conclusion is this part is not finished yet.
Sorry, wrong. The type is set, your configuration file is wrong.
If you use "nanobts1800" instead of "nanoBTS", add
"ip.access unit_id 1800 0" (you might have to ajust the numbers)
everything will work (at least the nanoBTS is configured). I
just tried it with the version from the GIT. Why do I have to
try it, instead that you look carefully ?
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Nordin,
On Fri, 14 Aug 2009 11:42:09 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
>
> I attached the modified config file, but it's not really special about it.
> I think Harald hasn't finished that part, as we know he is a very busy
> man :)
If you look at vty_interface.c, you will notice that there a different
configuration commands for the BS-11 and the nanoBTS. For example there
is "oml ..." for the BS-11 and "ip.access ..." for the nanoBTS. So the
"oml ..." commands in the config file you posted won't work for the
nanoBTS. I have not tried it yet, but thats where I would start
to modify the config file for the nanoBTS.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello guys,
Today I've pulled the latest sources and have issues of executing
bsc_hack with config file.
It complains about:
GSM900 channel must be between 1-124.
mi_e1_line_update could not open socket Address family not supported by
protocol
But I changed the config file for the nanoBTS1800, is there something
missing?
Hey Guys,
this is just a small note of the current work in the holger/on-waves-msc-sccp
branch.
The goal of this branch is to implement A over IP and hook OpenBSC into a real
GSM network. This work is on the way thanks to on-waves.com.
The current state:
- Partially implemented SCCP. We can send UDT messages, and full connection
handling exists. I have not implemented segmenting for DT1 yet and
will try to avoid doing that.
- Split out vty_interfaces into two parts. One for the MSC
functionality and one for the BSC
- Split out gsm_subscriber into two sets. One for BSC and one for MSC.
- Do not compile gsm_04_08.c but provide the layer2->layer3 ourselves with
moving shared stuff to gsm48_utils.c. This way creating and parsing
of messages can be shared and the policy can remain in the old file.
(this is the biggest change to earlier approaches).
What will be next:
- Use bsc_msc_ip.c to initialize the the tcp connection, do the handshaking,
start sending the reset as seen in the traces.
What can be merged:
- I think I will propose to merge the vty and gsm subscriber changes after
HAR2009 as they have little chance to break stuff.
z.
Hi!
I've got a few nanoBTS, type 139 and 140.
So I need just one, the others are now for sale.
Type 140(1900), you don't disturb the existing providers, for 1300 euro,
working well with all quadband handsets.
Type 139(1800) for 1200 euro.
All equipment is in working order, supplied with PoE-Adapter.
If you buy 2, there is a 10% off.
The Unit's are located in Switzerland and can be picked up here on Lake
Constance
or shipped by german post, so you don't have to pay for expensive shipment
like from US.
BTW I can't reach Harald Welte by email to ask him where is my ordered
BS-11.
Regards,
--
- Thomas Mueller <womax(a)gmx.ch>
Hey,
I compiled with -Wall -Werror and fixed the easy ones. While doing it I
encountered one bug in the bsc_hack.c..
int ipaccess_setup(struct gsm_network *gsmnet) is called with a struct
gsm_bts*... The current ipaccess_setup need to be called once per network (as
we should only bind to the address once...).
any idea what to do?
z.
Hello,
this patch should add support to bs11_config for bport0/1 configuration.
This should enable you to configure a BS11 to run in multidrop mode and
so contol two BS11 from one E1 link.
I only have one BS11 so I was only able to verify that the objects are
indeed created/modified. If it's okay I can also directly push the patch.
Regards,
Daniel Willmann
Daniel Willmann (1):
Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config
openbsc/include/openbsc/abis_nm.h | 4 +++-
openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++--
openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++
3 files changed, 58 insertions(+), 3 deletions(-)
On Sat, Aug 08, 2009 at 02:03:06PM +0400, Sergey V. Efimov wrote:
> I've compiled mISDN module into kernel and it loads with
> hfcmulti.dslot=1 parameter.
> I think there is no difference between dynamically loadable module
> and statically compiled in.
> Also when I did not provide this parameter, nothing worked at all.
>
> Is there any issues regarding processor architecture? I use AMD64
> platform, though
> the system (Debian) has i386 architecture working in compatibility mode.
I'm using both debian on 32bit and 64bit.
Your problem might be related to the actual cabling. I believe it is
definitely a layer1 (cabling) or layer 2 (mISDN) problem.
I don't really know any other advice but to double-check the cabling, the
jumpers on the E1 board as well as the termination jumpers on the BS-11.
Everything has to be set to 120 Ohms.
--
- 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)
Hi!
I've committed the first working version of OpenBSC with vty-based
configuration file to the 'config_file' branch in git.
Using this version, all parameters such as BTS E1 card / timeslot / sub-slot /
TEI for OML and RSL, MNC, MCC, BSIC, TSC as well as the physical channel
configuration of each Um timeslot can be configured in openbsc.cfg.
As an example, I'm attaching a configuration for two bts with two trx each.
You can change the configuration interactively by using the telnet interface
by a sequence of commands like:
================
enable
configure terminal
network
bts 0
trx 0
arfcn 111
write file
================
At this point you still need to restart OpenBSC, as we don't support changing
configuration at runtime yet.
--
- 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)
