Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This will print test rep[orts that look like:
<0020> ipaccess-config.c:91 TEST REPORT: test_no=0x43 test_res=PARTIAL
<0020> ipaccess-config.c:140 ==> ARFCN 37, RxLev 24, RxQual 0: 262-1, LAC 13830 CI 10759
|
|
|
|
ipaccess-config stopped working after the introduction of
multi-TRX/RSL stream id support in commit 8175e95222cf1c83.
Set the oml_tei to 0xff by default and add an option to set
a different stream id.
|
|
Add support for 1900 nanoBTS by using unified bts_type
GSM_BTS_TYPE_NANOBTS for 900, 1800 and 1900 versions.
Reduce the nanoBTS enum values to one and derive the
version from the user supplied band. In the future we
might want to do auto band detection.
The configuration file needs to be changed to refer
to nanobts instead of nanobts900/nanobts1800.
Signed-off-by: Mike Haben <michael.haben@btinternet.com>
Signed-off-by: Holger Hans Peter Freyther <zecke@selfish.org>
|
|
* perform a channel usage test
$ ./ipaccess-config -l 64 192.168.100.100
paccess-config.c:142 ==> ARFCN 3, RxLev 16
[...]
<0020> ipaccess-config.c:142 ==> ARFCN 4, RxLev 33
<0020> ipaccess-config.c:142 ==> ARFCN 8, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 5, RxLev 16
<0020> ipaccess-config.c:142 ==> ARFCN 11, RxLev 5
<0020> ipaccess-config.c:142 ==> ARFCN 12, RxLev 8
<0020> ipaccess-config.c:142 ==> ARFCN 10, RxLev 6
[...]
* perform a BCCH usage test
$ ./ipaccess-config -l 65 192.168.100.100
[...]
<0020> ipaccess-config.c:107 TEST REPORT: test_no=0x41 test_res=SUCCESS
<0020> ipaccess-config.c:142 ==> ARFCN 4, RxLev 32
<0020> ipaccess-config.c:142 ==> ARFCN 8, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 12, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 20, RxLev 9
<0020> ipaccess-config.c:142 ==> ARFCN 31, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 37, RxLev 23
<0020> ipaccess-config.c:142 ==> ARFCN 49, RxLev 7
<0020> ipaccess-config.c:142 ==> ARFCN 53, RxLev 14
<0020> ipaccess-config.c:142 ==> ARFCN 57, RxLev 19
<0020> ipaccess-config.c:142 ==> ARFCN 60, RxLev 63
<0020> ipaccess-config.c:142 ==> ARFCN 71, RxLev 15
<0020> ipaccess-config.c:142 ==> ARFCN 90, RxLev 4
* perform a frequency sync test
$ ./ipaccess-config -l 66 192.168.100.100
[...]
<0020> ipaccess-config.c:107 TEST REPORT: test_no=0x42 test_res=SUCCESS
<0020> ipaccess-config.c:130 ==> ARFCN 4, Frequency Error -2
<0020> ipaccess-config.c:130 ==> ARFCN 8, Frequency Error -40
<0020> ipaccess-config.c:130 ==> ARFCN 20, Frequency Error -21
<0020> ipaccess-config.c:130 ==> ARFCN 31, Frequency Error 1
<0020> ipaccess-config.c:130 ==> ARFCN 37, Frequency Error -4
<0020> ipaccess-config.c:130 ==> ARFCN 45, Frequency Error -4
<0020> ipaccess-config.c:130 ==> ARFCN 53, Frequency Error 22
<0020> ipaccess-config.c:130 ==> ARFCN 57, Frequency Error 3
<0020> ipaccess-config.c:130 ==> ARFCN 60, Frequency Error 0
<0020> ipaccess-config.c:130 ==> ARFCN 69, Frequency Error 2
<0020> ipaccess-config.c:130 ==> ARFCN 73, Frequency Error 30
<0020> ipaccess-config.c:130 ==> ARFCN 89, Frequency Error 44
<0020> ipaccess-config.c:130 ==> ARFCN 90, Frequency Error 8
<0020> ipaccess-config.c:130 ==> ARFCN 123, Frequency Error 27
|
|
This helps us to detect the frequency error of BS-11 if it is located
next to the nanoBTS 900.
If 'ipaccess-config -l' is called, it will produce a report like
<0020> ipaccess-config.c:85 TEST REPORT: test_no=0x42 test_res=0
<0020> ipaccess-config.c:108 ==> ARFCN 220, Frequency Error 22
<0020> ipaccess-config.c:108 ==> ARFCN 1, Frequency Error -37
<0020> ipaccess-config.c:108 ==> ARFCN 10, Frequency Error 0
<0020> ipaccess-config.c:108 ==> ARFCN 20, Frequency Error 11
<0020> ipaccess-config.c:108 ==> ARFCN 53, Frequency Error 5
<0020> ipaccess-config.c:108 ==> ARFCN 63, Frequency Error -4
<0020> ipaccess-config.c:108 ==> ARFCN 84, Frequency Error 11
<0020> ipaccess-config.c:108 ==> ARFCN 101, Frequency Error 0
<0020> ipaccess-config.c:108 ==> ARFCN 123, Frequency Error -52
where in this case the ARFCN 123 is the BS-11 with a frequency error
larger than all the other (regular) BTS in the vicinity.
|
|
we also rename some existing attributes to reflect reality
|
|
Currently we send the attribute changes in a send and forget
fashion. But sometimes the nanoBTS is sending us a NACK, e.g
with a invalid unit id. Start handling the NACK and provide
an error message to the user. The error message is not yet
describing the cause of the error but this is a slight progress
to the previous silent failure.
|
|
Just a beginning...
|
|
|
|
This makes it much easier to do run-time configuration using the vty
interface.
|
|
This is Harald's reworked MNCC base, slowly heading towards integration
into master. The key changes are:
* provide much more structure to the data in gsm_mncc
* encode_* and decode_* functions now take a structure rather than tons
of individual arguments (whose order nobody can remember)
* make sure we don't have copies of the same code everywhere by introducing
mncc_set_cause() and mncc_release_ind()
* save horizontal screen space if possible
* make sure we break lines > 80 characters
|
|
|