Hi!
JFYI: My dissector for the Abis-IP adaption layer of ip.access has been merged
into wireshark (as of svn revision 29059).
--
- 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 everybody
I just would like to be sure that the paging is only sent on TS0 with
OpenBSC, that is to say PCH (which is on CCCH) is only sent on TS0.
I read that it could be sent on more time slots (TS2, TS4 and TS6 also) in
the GSM specifications. Is it the case in the soft or you just keep the
normal multiplexage setting (TS0 only for CCCH+BCCH, 1 slot for dedicated
channels and 6 slots for the traffic channels)?
Thanks
Eric Cathelinaud
Hello Nordin,
On Tue, 07 Jul 2009 16:31:36 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
>
> But this means that your HTC needs more relevant GPRS settings before
> deciding to register. So it than searches for altenatives, but since the
> BA list is empty it starts all over again and the whole process repeats,
> which might result in a long procedure before it gives up. This is what
> it might could be the reason, I'm not sure.
If the GPRS Indicator is set, SYSTEM INFORMATION 13 is needed to
describe the GPRS properties. But SYSTEM INFORMATION 13 is not set
yet (not possible for the BS-11 anyway) so the phone won't find it.
Probably some phones don't care about it but some others insist to
find it before going to register.
This is probably one of the many places where there is no rule in
the specification what should be done in such a situation so its
up to the developer of the firmware (the phone could register and
return an error only when GPRS is actually needed for a data
connection). Of course I don't mean that the specification is
incomplete, it just expects that certain things are done "right"
(who would expect that people outside of the mobile phone industry
play with a BTS ;-).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Nordin,
On Mon, 06 Jul 2009 12:00:27 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
>
> I tried the parameters as you suggested for SI 1 as well as SI3, but
> with no success. But I'm still curious if someone else on the list
> registered a PDA-like mobilephone (with GPRS support) to his BTS
> (BS11/nanoBTS1800). If so, I would like to try out his/her SI's settings.
>
With the modification I have sent I can register a HTC Touch Pro to
the BS11 and the nanoBTS 1800. If GPRS is set in SYSTEM INFORMATION 3,
the phone will not register.
The process is a bit unstable, if the phone is powered on, the
location update works as expected, if I try to register manually,
it sometime fails without actually communication with the BTS.
I don't know the reason for this behaviour yet.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello guys,
I made a repository for the OpenBSC project, see:
http://repo.or.cz/w/openbsc.git
Now you can update/clone the project from
http://repo.or.cz/r/openbsc.git, like this:
git clone http://repo.or.cz/r/openbsc.git
It will be updated every hour (mirror mode).
I needed that because our firewall blocks the git port 9418.
Thank you for the tip Holger Freyther :)
If you have any questions, don't hestitate to ask.
Hello Nordin,
On Fri, 03 Jul 2009 11:21:59 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
>
> Since we haven't done anything for GPRS support, this might be the
> reason why a location update is not performed with bsc_hack.
The problem you experience with the nanoBTS 1800 most certainly
comes from an invalid System Information Type 1. It uses the bitmap
type for the channel description which is only valid for GSM900.
So all the phones should try to register with the BS-11 but for
the nanoBTS 1800 phones which strictly confirm to the specification
will ignore it and not try to register (there are some phones which
don't care).
You can try the "system_information" git branch from Harald, it
will most certainly solve the problem.
> P.S.: Is everybody on holiday...:)
I guess the people are just busy...
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
I tried the parameters as you suggested for SI 1 as well as SI3, but
with no success. But I'm still curious if someone else on the list
registered a PDA-like mobilephone (with GPRS support) to his BTS
(BS11/nanoBTS1800). If so, I would like to try out his/her SI's settings.
I still don't have the latest version as at the moment our firewall
doesn't allow to (I ask the networkadmin later for that).
Hello Nordin,
On Fri, 03 Jul 2009 14:44:50 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
>
> I hope this will at least try to do a LOCATION UPDATE REQUEST.
> But it suprises me that older mobilephones don't care about SI 1 (and
> maybe more information on the BCCH) and just try to register whatever in
> the BCCH is.
I have further investigated the problem. Besides the fact that
the channel allocation in SYSTEM INFORMATION 1 is not correct
for GSM 1800, this is probably not the reason for the problem.
Most certainly its just one wrong bit, the GPRS indicator in
the SYSTEM INFORMATION 3 rest octets.
The current setting is
0x80, 0x00, 0x00, 0x2B
but it should be
0x80, 0x00, 0x08, 0x2B
What might lead to some confusion is the meaning of "L" and "H" in
the specification of CSN.1. For the rest octets the bit value is
determined by a comparsion (XOR) to the padding byte 0x2B. So the
value 0x08 above actually means "L" for the GPRS indicator, which
means "No GPRS".
Its seem that some phones are really sensible to this setting, some
other GPRS capable phones just don't care and register to the
network even if there is no GPRS.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Harald,
On Sun, 5 Jul 2009 04:42:20 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote:
>
> where did you find this XOR? I just searched through 04.07 and 04.08 and
> didn't find any indication thereof. Sure, the padding bit sequence ix 0x2b, so
> all spare bits have to be padded with that. But where did you get the XOR
> from?
I started to search deeper because I was a bit confused how the Message
Decoding Tool from Joachim Goeller interpreted the rest octets. I looked
at some phone firmware how they do it and found it there. Later I also
found a good explanation at http://csn1.info (they sell a tool which
can be used to generate message parsing source code for various
specifications).
> Also, this would mean that if we put explicitly 0x2b into the padding of
> our messages, then it would result in all-zero 0x00 on the air, since
>
> 0x2b xor 0x2b == 0x00
The XOR is actually only used for "L" and "H", basically it means that
if a bit at an "L"/"H" position is different from the padding sequence,
its an "H". At least this is how I understand it.
> I'm now looking at an actual abis trace from a production cell with GPRS
> enabled, and it has
>
> "0x80, 0x00, 0x80, 0x0b"
Here is how I would interpret it according to GSM 04.08, 10.5.2.34:
Selection Parameter:
byte 0: 0x80 ^ 0x2B = 0xAB, (bit 7) -> H (15 bits for parameter follow)
Power Offset:
byte 2: 0x80 ^ 0x2B = 0xAB, (bit 7) -> H ( 2 bits for parameter follow)
System Information 2ter Indicator:
byte 2: 0x80 ^ 0x2B = 0xAB, (bit 4) -> L (has no parameters)
Early Classmark Sending Control:
byte 2: 0x80 ^ 0x2B = 0xAB, (bit 3) -> H (has no parameters)
Scheduling if and where:
byte 2: 0x80 ^ 0x2B = 0xAB, (bit 2) -> L
GPRS Indicator:
byte 2: 0x80 ^ 0x2B = 0xAB, (bit 1) -> H ( 4 bits for parameter follow)
> During early start of the BTS, SI3 rest octets are set to
>
> "0x80, 0x00, 0x83, 0x2b"
The only difference is that at this stage GPRS is not yet set:
GPRS Indicator:
byte 2: 0x83 ^ 0x2B = 0xA8, (bit 1) -> L
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de