Hi,
it seems that the last few commits (starting with SVN revision 308)
broke the compilation of bs11_config. As I wanted to take a look at
the boot process of my newly delivered BS11, I've just fixed bs11_config
to build again and it even seems to work.
Find attached my (ugly) patch to fix the build problems.
Regards,
Michael
--
Michael Gernoth Department of Computer Science IV
Martensstrasse 1 D-91058 Erlangen Germany University of Erlangen-Nuremberg
http://www4.informatik.uni-erlangen.de/~gernoth/
Hi all!
Like I just wrot in my blog, I have managed to get the first voice calls
between two MS on one BTS working. The Q.931 like call control never
really was the problem, and paging as well as RR/MM seems to work very stable
all the time. Bigger problems were related to the CHANNEL MODIFY that has
to be done on the 04.08 level (for the MS side) as well as the 08.58 side for
the BTS side - plus many classic programming mistakes in what used to be
so-far untested/unused code.
In any case, I have succesfully had voice calls through both the BS-11
as well as the ip.access nanoBTS.
There are still lots of things left to be done (e.g. the E1 subslot assignments
are still static, there is a big yet-to-be-explained lag on E1 based calls,
Motorola phones seem to have compatibility issues, you can call yourself and
make your own phone ring, etc). But at least the foundation is working.
Regards,
[... and it's not even two months too late for the originally planned call demo
at 25C3]
--
- 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 Philippe!
On Fri, Feb 13, 2009 at 03:31:08PM +0100, Philippe Langlois wrote:
> Can you also upload there some raw packet traces of this ip.access
> abis-over-ip ?
I'm working on a wireshark plugin, and I'll release traces + the plugin soon.
The traces will then be traces of OpenBSC talking to the nanoBTS. The traces
I currently have are from a test network, but contain things like IMSI/IMEI
numbers which I consider confidential information.
By the way: There is currently no wireshark plugin for GSM 12.21 (OML) yet, as
far as I can tell. Only 08.58 is there. Anyone interested in working on this?
Regards,
--
- 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 started a page documenting the ip.access A-bis over IP protocol at
https://bs11-abis.gnumonks.org/trac/wiki/nanoBTS
There are no NDA problems with it, since all information was derived from
looking at packet traces. I do not have access to any protocol documentation
from ip.access.
Regards,
--
- 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!
This seems to solve the mystery that zecke and me experienced yesterday
working with the B-Channels on mISDN.
Regards,
--
- 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)
Hello Bjoern,
> Can't get logged in to the LMT.
> It asks for a password (cambio menu).
> "L3proc" isn't working...
This is not the LMT COM Port, you have plugged the cable into
the wrong port. Besides the LMT COM port, which is close to the
E1 BNC connectors, there are several other COM ports which are
directly routed to the various microcontrollers. There are some
simple debug menues active during startup, but on the LMT port
you won't get any reply without sending the correct message first.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi!
I was trying to get the data model right for the TRAU mux/demux handling,
and discovered it is about time to re-do the entire 'input' side, i.e.
the interface towards the actual E1 link.
The main objectives are:
1) ability to deal with multiple BTS on one E1 link
2) ability to easily integrate E1 drivers != mISDN, e.g. zaptel while
still keeping most of the E1 related functionality in common code
3) ability to easily add things like Abis over IP later
So please stay tuned for some potentially quite big committs in that area during
the next couple of days.
--
- 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!
JFYI: Software load through the A-bis / E1 interface is only marginally
faster than through the serisal RS232 line.
The theoretical maximum speed is the 64kbps of the E1 timeslot, which should give quite a bit of improvement over the 19200bps serial line.
However, the BS-11 is throttling down the transver even via A-bis. I have
tried to increase the window size to 20 (LMT has a max of 8. I tried up to 32
but then the transfer fails)
The speed that I'm getting now is somewhere around 1232 bytes per second, which
is about 9656bps. Do they use a 9600bps serial line somewhere inside the
BS-11 to route those software updates through?
I haven't finished an entire transfer, but it seems like the transfer would
take some 36 minutes using this method. Not too far off the 45minutes
that we get with LMT or bs11_config.
I guess "in the field" this doesn't really matter since they can install
the software image while the BTS is still in operation, and then at some
point schedule a reboot which activates the new software.
p.s.: yes, I removed all delays (usleep calls) from misdn.c before testing.
--
- 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)
