Hello,
For those who use nanoBTS for OpenBSC, I made a short video about how to
properly reset the nanoBTS when something goes wrong.
In the video demonstrates how to manually shirt the TIB pins
For 110 series (Oval Shaped) : http://www.youtube.com/watch?v=VjW2EAP7wss
For 165 series (Rectangular) : http://www.youtube.com/watch?v=9H-H5J8XxOE
And happy holidays to all
Cheers,
Pierre
The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it. This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).
For more information see:
https://lists.osmocom.org/mailman/admin/openbsc/bounce
Hello list,
I'm Nikola and I'm quite new to OpenBSC. Last two days I played little bit
with OpenBSC compilation on FreeBSD and with few changes the work is done.
I am sending the diff file. Not sure about __BYTE_ORDER declaration but
hope someone can help (I am not developer).
Regards,
Nikola
diff --git a/openbsc/src/libbsc/arfcn_range_encode.c b/openbsc/src/libbsc/arfcn_range_encode.c
index 02a75a5..45a49da 100644
--- a/openbsc/src/libbsc/arfcn_range_encode.c
+++ b/openbsc/src/libbsc/arfcn_range_encode.c
@@ -213,7 +213,7 @@ int range_enc_range512(uint8_t *chan_list, int f0, int *w)
write_orig_arfcn(chan_list, f0);
range512 = (struct gsm48_range_512 *) &chan_list[0];
- range512->form_id = chan_list[0] = 0x44;
+ range512->form_id = 0x44;
/* W(1) */
range512->w1_hi = HIGH_BITS(w, 1, 9, 7);
hi,
just found a bug in range 512 channel list encoding. the useless write of 0x44 to chan_list[0] will destroy the LSB, which is part of frequency 0, previously written by write_orig_arfcn(). after fixing this, a frequency of ARFCN 512 encodes correctly.
regards,
andreas
Hi Andreas,
I can confirm, that the patches for the local release and for the TRAU
mux are working with Nokia InSite, finally the handover is available
and working for us with your patches :-)
The local release problem also affected the SMS service, it seems this
patch also solves that problem too.
I will send you the software versions on my two InSite and metrosite
units to keep track and check if we can get a newer version that solves this BTS SW
bug. Note that the Insite units are very old, it is more likely to get
newer software for the MetroSite which is also affected by this
problem.
Thanks again for your hard work!
BR,
Csaba