Hi all,
JFYI: There's some progress on the nanoBTS multi-TRX configuration.
It seems it was my mistake. Setting the TRX0 unit ID to 1801/0/0 and the TRX1
unit ID to 1801/0/1 works using ipaccess-config.
If you then connect the TIB cable (TRX0 TIB out -> TRX1 TIB in) and reboot
both nanoBTS, you will get a single A-bis OML connection from 1801/0/0 where
you get software activate requests for both transceivers.
Somehow we're not handling them correctly yet from our abis_nm code, but that
should be easy to solve. I'm working at it.
So Dieter and others: No need to worry about this at the moment, we're very
close now and I think it is no problem for the 26C3.
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)