Am Wed, 23 Jun 2010 20:18:56 +0800 schrieb Holger Freyther zecke@selfish.org:
the first pointer is to the sha1/commit id[1]. So every commit has an id, it happens to be the sha1 hash over some parts of the content. Now git log will show all these as "commit". Now the openbsc version is generated by the little "./git-version-gen" utility. In fact the utility is calling "git describe" (man git-describe).
E.g. it looks like this: 0.9.0-891-gaf7edd9
0.9.0 is the last tag we had.. 891 is the number of commits since that tag gaf7edd9 is the commit/sha1. This is what you want.
I hope this helps
Unfortunately not...
I tried to give git-describe in the tree of the "sms-sending"-BSC (0.9.0-531-gb938d6b) and in the tree of the last version (0.9.0-890-g2788b96), then I tried to use git bisect:
lucabert@Luca:/tmp/bsc/openbsc$ git bisect good gb938d6b Bad rev input: gb938d6b lucabert@Luca:/tmp/bsc/openbsc$ git bisect bad g2788b96 fatal: Needed a single revision Bad rev input: g2788b96
It seems not to work... Maybe I need vacancy? I can't understand what you suppose I can do...
Thanks for your suggestion!
On 06/23/2010 08:45 PM, Luca Bertoncello wrote:
lucabert@Luca:/tmp/bsc/openbsc$ git bisect good gb938d6b Bad rev input: gb938d6b lucabert@Luca:/tmp/bsc/openbsc$ git bisect bad g2788b96 fatal: Needed a single revision Bad rev input: g2788b96
well, ever considered that the 'g' is not part of the hash? I didn't know that when splitting up the result of git describe.
Am Wed, 23 Jun 2010 20:49:03 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
On 06/23/2010 08:45 PM, Luca Bertoncello wrote:
lucabert@Luca:/tmp/bsc/openbsc$ git bisect good gb938d6b Bad rev input: gb938d6b lucabert@Luca:/tmp/bsc/openbsc$ git bisect bad g2788b96 fatal: Needed a single revision Bad rev input: g2788b96
well, ever considered that the 'g' is not part of the hash? I didn't know that when splitting up the result of git describe.
How can I know, which letter are part of the hash? :) Anyway
lucabert@Luca:/tmp/bsc/openbsc$ git bisect good b938d6b Bad rev input: b938d6b
Are these "b" not part of the hash, too?
Thanks
On 06/23/2010 09:07 PM, Sylvain Munaut wrote:
How can I know, which letter are part of the hash? :)
Huh ... hexadecimal ? 0-9 a-f ?
Well, it is always tough to deal with something new. The git-describe manpage would have been helpful here. It is separating the three parts correctly here.
Bad rev input: b938d6b
Weird, that's a valid revision in my tree.
here too,
where do you execute the git command?
Am Wed, 23 Jun 2010 21:10:17 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
Well, it is always tough to deal with something new. The git-describe manpage would have been helpful here. It is separating the three parts correctly here.
Bad rev input: b938d6b
Weird, that's a valid revision in my tree.
here too,
where do you execute the git command?
OK, I don't understand anything more... I have two directories:
~/Desktop/bscDebian (the good one) /tmp/bsc (the bad one)
Now I change to /tmp/bsc/openbsc and I give:
lucabert@Luca:/tmp/bsc/openbsc$ git-describe 0.9.0-890-g2788b96 lucabert@Luca:/tmp/bsc/openbsc$ git bisect start -- openbsc lucabert@Luca:/tmp/bsc/openbsc$ git bisect good b938d6b Bad rev input: b938d6b
Could you please explain me what I didn't understand? I'm feeling as a little boy at the first time he used a PC... :(
Thanks
On 06/23/2010 09:16 PM, Luca Bertoncello wrote:
Could you please explain me what I didn't understand? I'm feeling as a little boy at the first time he used a PC... :(
I am deeply sorry. I had an accidental commit and within an hour after noticing I have used git push --force to make it disappear. You must have pulled in between... This means that next time we will not use git push --force...
You want to use 57da4471d1511e5456d67088e2c34b1799f08b9a as commit id which contains the same tree as the rev you tried to use before...
happy bisecting
PS: With git there is something called git rebase, it allows to rewrite parts of the history, and this means the checksums are changing...
Am Wed, 23 Jun 2010 21:37:51 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
I am deeply sorry. I had an accidental commit and within an hour after noticing I have used git push --force to make it disappear. You must have pulled in between... This means that next time we will not use git push --force...
You want to use 57da4471d1511e5456d67088e2c34b1799f08b9a as commit id which contains the same tree as the rev you tried to use before...
happy bisecting
Hi, Holger and List!
last week I didn't had time enough to search for the "bad" version. Now I did it...
I "bisected" the version between the known good and the last. After 3 tries I found the version with the problem (or better: I hope!).
The last known working version is: [4f8340939e631d0254c523e86e7b8be44d1dcf2c] bsc_api: Remove some more occurences of the lchan.
Now these two versions have problems:
[f3d8e92731dbdc05ed4214ab9ff2bbb9189f42ad] [BSC] introduce the concept of 'BTS features' With this version OpenBSC crashes when the nanoBTS boots in OpenBSC. ========================= DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:632 accept()ed new OML link from 192.168.1.107 <0005> bsc_init.c:738 bootstrapping OML for BTS 0 <000d> input/ipaccess.c:694 accept()ed new RSL link from 192.168.1.107 <0004> bsc_init.c:924 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 123 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7 Segmentation fault =========================
[694a5cfe062b49ac6b3a76714b3f972d3cedd620] [BSC] RSL: Fix Channel Identification IE in RSL CHAN ACT With this version it is NOT possible to send SMS anymore.
Of course, I can not be sure which ob both version introduce the problem. I couldn't try the f3d8e92731dbdc05ed4214ab9ff2bbb9189f42ad.
Now I need your help again. How can I restrict the problem to the file which introduce the SMS-bug?
Thanks
Am Mon, 28 Jun 2010 10:15:58 +0200 schrieb Luca Bertoncello bertoncello@netzing.de:
[694a5cfe062b49ac6b3a76714b3f972d3cedd620] [BSC] RSL: Fix Channel Identification IE in RSL CHAN ACT With this version it is NOT possible to send SMS anymore.
Hi, again!
I tried to search which files are modified. I can confirm, that the release 694a5cfe062b49ac6b3a76714b3f972d3cedd620 introduced the problem.
I just revert the changes of this release (file abis_rsl.c, function rsl_chan_activate_lchan) and I can send SMS again.
Unfortunately, I don't know yet the GSM protocol so good, and I can't find the error.
I send this E-Mail to indicate the problem, and I hope the person, who introduce this change will correct the problem.
Regards
Dear Luca,
On Mon, Jun 28, 2010 at 02:52:56PM +0200, Luca Bertoncello wrote:
[694a5cfe062b49ac6b3a76714b3f972d3cedd620] [BSC] RSL: Fix Channel Identification IE in RSL CHAN ACT With this version it is NOT possible to send SMS anymore.
Hi, again!
I tried to search which files are modified. I can confirm, that the release 694a5cfe062b49ac6b3a76714b3f972d3cedd620 introduced the problem.
I just revert the changes of this release (file abis_rsl.c, function rsl_chan_activate_lchan) and I can send SMS again.
Unfortunately, I don't know yet the GSM protocol so good, and I can't find the error.
Thanks a lot for your debugging so far. It is very helpful to get qualified bug reports.
I send this E-Mail to indicate the problem, and I hope the person, who introduce this change will correct the problem.
That would be me.
What would be most helpful is two pcap files of the communication. One for the working and one for the non-working case.
Specifically the RSL CHANNEL ACTIVATE meessage is most important in that pcap.
I think with the pcap it will be very easy to solve the problem.
And yes, I have your other mails, but the day only has 24 hours, sorry...
Am Mon, 28 Jun 2010 21:25:06 +0200 schrieb Harald Welte laforge@gnumonks.org:
What would be most helpful is two pcap files of the communication. One for the working and one for the non-working case.
Specifically the RSL CHANNEL ACTIVATE meessage is most important in that pcap.
I think with the pcap it will be very easy to solve the problem.
OK! I send you two TCPDump files. The first (lastWorkingVersion.log) refers to the last know working version (4f8340939e631d0254c523e86e7b8be44d1dcf2c), the second (firstNotWorkingVersion.log) refers to the first know NOT working version (694a5cfe062b49ac6b3a76714b3f972d3cedd620). As I said, between these version there is another (f3d8e92731dbdc05ed4214ab9ff2bbb9189f42ad) that crashes by starting the communication with the nanoBTS.
And yes, I have your other mails, but the day only has 24 hours, sorry...
I know... I tried to order a couple of hour for my days, but these are undeliverable... :D
Bye
Hi Luca,
On Tue, Jun 29, 2010 at 08:51:42AM +0200, Luca Bertoncello wrote:
What would be most helpful is two pcap files of the communication. One for the working and one for the non-working case.
Specifically the RSL CHANNEL ACTIVATE meessage is most important in that pcap.
I think with the pcap it will be very easy to solve the problem.
OK! I send you two TCPDump files. The first (lastWorkingVersion.log)
Sorry, we really need pcap files, not the stdout of tcpdump (which you have sent). You can create them using something like "tcpdump -w file.name -s 0 -i eth0"
Regards, Harald
Am Tue, 29 Jun 2010 11:08:28 +0200 schrieb Harald Welte laforge@gnumonks.org:
Sorry, we really need pcap files, not the stdout of tcpdump (which you have sent). You can create them using something like "tcpdump -w file.name -s 0 -i eth0"
Ops! Here there are!
Thanks
Luca,
thanks for the pcap files.
On Mon, Jun 28, 2010 at 02:52:56PM +0200, Luca Bertoncello wrote:
Am Mon, 28 Jun 2010 10:15:58 +0200 schrieb Luca Bertoncello bertoncello@netzing.de:
[694a5cfe062b49ac6b3a76714b3f972d3cedd620] [BSC] RSL: Fix Channel Identification IE in RSL CHAN ACT With this version it is NOT possible to send SMS anymore.
Hi, again!
I tried to search which files are modified. I can confirm, that the release 694a5cfe062b49ac6b3a76714b3f972d3cedd620 introduced the problem.
It is really strange to understand how this relates to the bug you have seen, but indeed we were doing something wrong with regard to the RSL channel activation. I've fixed that now, feel free to see if 93d50e69d37b3e3bd5cd41967705b8645cfefdec fixes your problem.
Am Tue, 29 Jun 2010 17:55:31 +0200 schrieb Harald Welte laforge@gnumonks.org:
It is really strange to understand how this relates to the bug you have seen, but indeed we were doing something wrong with regard to the RSL channel activation. I've fixed that now, feel free to see if 93d50e69d37b3e3bd5cd41967705b8645cfefdec fixes your problem.
Hi, Harald!
I installed the last version of OpenBSC. Unfortunately it does not work...
Bye
On 06/30/2010 02:30 PM, Luca Bertoncello wrote:
Hi, Harald!
I installed the last version of OpenBSC. Unfortunately it does not work...
Hi,
could you at least try revision 0379c6d386? And it would be nice to know which version you have tested and how it failed? SMS Sending didn't work? or were you seeing floods of NACK messages and processing failures?
Am Wed, 30 Jun 2010 15:21:04 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
could you at least try revision 0379c6d386? And it would be nice to
How can I install a revision? I searched in the man pages of git, but I didn't found any command to install a specific revision... :(
know which version you have tested and how it failed? SMS Sending didn't work? or were you seeing floods of NACK messages and processing failures?
The problem is always the same, I described in my E-Mails. I tried to install the last version of OpenBSC (git clone ...), because Harald said, he applied a patch.
Thanks
On Wed, Jun 30, 2010 at 09:25:28AM +0200, Luca Bertoncello wrote:
Am Wed, 30 Jun 2010 15:21:04 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
could you at least try revision 0379c6d386? And it would be nice to
How can I install a revision? I searched in the man pages of git, but I didn't found any command to install a specific revision... :(
Using git you always clone a repository, i.e. you have all versions installed at the same time. you can then switch using commands like
"git checkout 0379c6d386" "git checkout master" (goes back to the current version).
I strongly suggest reading some git tutorial, there are a number of them available online.
know which version you have tested and how it failed? SMS Sending didn't work? or were you seeing floods of NACK messages and processing failures?
The problem is always the same, I described in my E-Mails. I tried to install the last version of OpenBSC (git clone ...), because Harald said, he applied a patch.
Neither Holger nor I can reproduce your problem, so we are a bit stuck here.
Am Wed, 30 Jun 2010 18:00:10 +0200 schrieb Harald Welte laforge@gnumonks.org:
The problem is always the same, I described in my E-Mails. I tried to install the last version of OpenBSC (git clone ...), because Harald said, he applied a patch.
Neither Holger nor I can reproduce your problem, so we are a bit stuck here.
Hi, Harald!
I tried your patch 93d50e69d37b3e3bd5cd41967705b8645cfefdec. Unfortunately I can't test, if it works with SMS, since I can NOT log in to the network. As Attachment the pcap-file with my try. I get always this error:
<0004> abis_rsl.c:831 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE NACKCAUSE=0x6f(Protocol error, unspecified) <0011> handover_logic.c:197 unable to find HO record
Thanks
I'm sorry... Hier the pcap-file...
Regards
On 07/01/2010 02:30 PM, Luca Bertoncello wrote:
I'm sorry... Hier the pcap-file...
Hi Luca,
I just had some time to look at the pcap but I am a bit confused. You seem to have multiple bsc_hack starts within the PCAP file? I have seen at least one NACK message, but not at the end of things.
Maybe you want to start a new toplevel thread with your problems. Do you still see the Channel Activate NACK messages? Do you still see the SMS Problem? Which phones have you tested this with?
Am Fri, 09 Jul 2010 17:45:17 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
I just had some time to look at the pcap but I am a bit confused. You seem to have multiple bsc_hack starts within the PCAP file? I have seen at least one NACK message, but not at the end of things.
Maybe you want to start a new toplevel thread with your problems. Do you still see the Channel Activate NACK messages? Do you still see the SMS Problem? Which phones have you tested this with?
Hi, Holger!
I just tried with the last version of OpenBSC. Unfortunately it still does not work... :( I uploaded the pcap-file on my server. In this session I just started OpenBSC, logged in with my mobile (Siemens S65v) and tried to send the SMS. And then closed OpenBSC.
You can download the pcap-file from http://www.lucabert.de/~lucabert/bscCantSMS.pcap.bz2
I hope, you can understand the problem now...
On 07/09/2010 07:22 PM, Luca Bertoncello wrote:
You can download the pcap-file from http://www.lucabert.de/~lucabert/bscCantSMS.pcap.bz2
I hope, you can understand the problem now...
Hi Luca,
from a quick look you seem to be passed the Chan Act NACK issues, you try a MT SMS? and the phone does not 'send' it? is that right? What one can see in the trace is that the MS tries to send it again, again, and releases the SAPIs.
Which phone is that? does it work with any other phone?
Am Sat, 10 Jul 2010 19:09:18 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
Hi, Holger!
from a quick look you seem to be passed the Chan Act NACK issues, you try a MT SMS? and the phone does not 'send' it? is that right? What one can see in the trace is that the MS tries to send it again, again, and releases the SAPIs.
Yes! So it is! I think, I said that...
Which phone is that? does it work with any other phone?
My phone is a Siemens S65v. I tried with other phones, too (Nokia, unknown model). Same problem... :(
Thanks
Hi Luca,
On Sun, Jul 11, 2010 at 08:28:49AM +0200, Luca Bertoncello wrote:
Which phone is that? does it work with any other phone?
My phone is a Siemens S65v. I tried with other phones, too (Nokia, unknown model). Same problem... :(
I have now tried the current version of libosmocore + openbsc and tested SMS with the following phones:
* Nokia 3310 * HTC TyTN II * Google/Android G1 * Sony-Ericsson K800i * Motorola C123
It was working from all of them without any problem. I really cannot reproduce the problem you are experiencing at all. Can you please
1) make sure you do a full rebuild (make distclean; ./configure; make; make install) of both libosmocore and openbsc 2) send your openbsc.cfg that was used
On Mon, Jul 12, 2010 at 04:48:12PM +0200, Harald Welte wrote:
Hi Luca,
On Sun, Jul 11, 2010 at 08:28:49AM +0200, Luca Bertoncello wrote:
Which phone is that? does it work with any other phone?
My phone is a Siemens S65v. I tried with other phones, too (Nokia, unknown model). Same problem... :(
I have now tried the current version of libosmocore + openbsc and tested SMS with the following phones:
- Nokia 3310
- HTC TyTN II
- Google/Android G1
- Sony-Ericsson K800i
- Motorola C123
I've also tested it with a Netzing NE110, and it is not able to send outgoing SMS messages.
As discussed earlier, this phone really seems like it has a protocol bug. It sends a CM SERVICE REQUEST, we answer by CM SERVICE ACCEPT, and the phone never sends any follo-up message (such as establishing the SAPI3 connection or actually sending the SMS).
I suppose nobody has tested this phone (or the underlying stack) with a GSM network that doesn't do authentication and/or encryption.
Am Mon, 12 Jul 2010 16:48:12 +0200 schrieb Harald Welte laforge@gnumonks.org:
I have now tried the current version of libosmocore + openbsc and tested SMS with the following phones:
- Nokia 3310
- HTC TyTN II
- Google/Android G1
- Sony-Ericsson K800i
- Motorola C123
It was working from all of them without any problem. I really cannot reproduce the problem you are experiencing at all. Can you please
- make sure you do a full rebuild (make distclean; ./configure;
make; make install) of both libosmocore and openbsc 2) send your openbsc.cfg that was used
Hi, Harald!
Thanks for your E-Mail. I just tried the last version from git of libosmocore and OpenBSC. I did a full rebuild in a new directory (no previous version).
I tried to send an SMS with my Siemens S65v (today I have just that or NE110. No other phones...). Again not possible.
Attached the pcap-file of the try and my config-file.
I'm not sure what this "<0011> handover_logic.c:163 unable to find HO record" means (see below):
lucabert@Luca:~/workspace/bscmanage/Debug$ /usr/local/sbin/bsc_hack -c lucabertBSC.cfg DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:632 accept()ed new OML link from 192.168.1.107 <0005> bsc_init.c:737 bootstrapping OML for BTS 0 <000d> input/ipaccess.c:694 accept()ed new RSL link from 192.168.1.107 <0004> bsc_init.c:1010 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 123 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7 <0011> handover_logic.c:163 unable to find HO record <0004> abis_rsl.c:942 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive channel <0004> abis_rsl.c:1363 RF release on (bts=0,trx=0,ts=2,ss=0) but state ACTIVE <0004> abis_rsl.c:1051 (bts=0,trx=0,ts=2,ss=0) CHAN REL ACK but state ACTIVE <0004> abis_rsl.c:1363 RF release on (bts=0,trx=0,ts=2,ss=0) but state NONE <0004> abis_rsl.c:1051 (bts=0,trx=0,ts=2,ss=0) CHAN REL ACK but state NONE signal 2 received <0005> bsc_init.c:753 shutting down OML for BTS 0
If I see in the DB after trying to send the SMS I found:
sqlite> select * from sms; id|created|sent|sender_id|receiver_id|deliver_attempts|valid_until|reply_path_req|status_rep_req|protocol_id|data_coding_scheme|ud_hdr_ind|dest_addr|user_data|header|text 53|2010-07-01 14:31:42||15|1|0|134727356|0|32|0|0|0|1000|�4||Ok 66|2010-07-02 06:56:16|2010-07-02 07:47:26|11|14|0|134721918|0|0|34|0|0|12345|@�||Abb 67|2010-07-02 06:56:35|2010-07-02 12:56:33|11|1|0|134721918|0|0|34|0|0|1000|@�||Abb �||Test-07-13 06:43:02||11|1|0|134727872|0|0|34|0|0|1000|� �||Test-07-13 06:43:14||11|1|0|134727872|0|0|34|0|0|1000|� �||Test-07-13 06:43:28||11|1|0|134727872|0|0|34|0|0|1000|�
(the first 3 SMS comes from a previous version of OpenBSC, that works).
I use a nanoBTS900 and on my PC runs a KUbuntu Hardy (8.04).
I tried the same on a Debian lenny (last version of libosmocore and OpenBSC, same configuration). Unfortunately, same result. Attached the pcap-file generated on the lenny-PC.
Here what I see in the console of lenny:
lucabert@debian503:/tmp$ /usr/local/sbin/bsc_hack -c /tmp/lucabertBSC.cfg DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:632 accept()ed new OML link from 192.168.1.107 <0005> bsc_init.c:737 bootstrapping OML for BTS 0 <000d> input/ipaccess.c:694 accept()ed new RSL link from 192.168.1.107 <0004> bsc_init.c:1010 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 123 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7 <0011> handover_logic.c:163 unable to find HO record <0004> abis_rsl.c:942 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive channel <0004> bsc_api.c:99 Got data in non active state. discarding. <0004> abis_rsl.c:942 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive channel <0004> abis_rsl.c:1363 RF release on (bts=0,trx=0,ts=2,ss=0) but state ACTIVE <0004> abis_rsl.c:1051 (bts=0,trx=0,ts=2,ss=0) CHAN REL ACK but state ACTIVE <0004> abis_rsl.c:1363 RF release on (bts=0,trx=0,ts=2,ss=0) but state NONE <0004> abis_rsl.c:1051 (bts=0,trx=0,ts=2,ss=0) CHAN REL ACK but state NONE ^Csignal 2 received <0005> bsc_init.c:753 shutting down OML for BTS 0
Thanks a lot for your answer Luca
Hi Luca,
On Tue, Jul 13, 2010 at 09:12:03AM +0200, Luca Bertoncello wrote:
I have now tried the current version of libosmocore + openbsc and tested SMS with the following phones:
- Nokia 3310
- HTC TyTN II
- Google/Android G1
- Sony-Ericsson K800i
- Motorola C123
It was working from all of them without any problem. I really cannot reproduce the problem you are experiencing at all. Can you please
- make sure you do a full rebuild (make distclean; ./configure;
make; make install) of both libosmocore and openbsc 2) send your openbsc.cfg that was used
Hi, Harald!
Thanks for your E-Mail. I just tried the last version from git of libosmocore and OpenBSC. I did a full rebuild in a new directory (no previous version).
I tried to send an SMS with my Siemens S65v (today I have just that or NE110. No other phones...). Again not possible.
I think one of the things you could ask from Netzing is to provide some more different phones to you for testing purpose. It's a small expense but should help us to identify if it is something related to your setup (i.e. your OpenBSC installation behaves different than ours), or it is related to the phones.
I suggest you ask Mr. Schneider for an OK to buy some old Nokia 3310 off eBay, and possibly a SonyEricsson K800i. This is what I mostly use for testing. At least on GPRS, the K800i was particularly "picky" i.e. it would always refuse to work if OpenBSC/OsmoSGSN did anything wrong - which made it a good device for testing.
The Netzing NE110 (as well as other MTK phones) seem to have a bug in their MO-SMS code. Dieter has told me he is looking at a workaround to this (by sending dummy authentication request/response), and he will e-mail this list once he has some results.
I'm not sure what this "<0011> handover_logic.c:163 unable to find HO record" means (see below):
this is just a status message of the handover code that discovers this newly- established channel is not part of a handover procedure, but a channel for regular channel establishment.
I use a nanoBTS900 and on my PC runs a KUbuntu Hardy (8.04).
Can you try the GSM1800 nanoBTS, and tell me the software/firmware version (as reported by ipaccess-config)? Holger, Dieter and myself all don't understand the problems you are experiencing, and it might be something that is different in your setup than ours (and we use GSM1800 nanoBTS).
Sorry for taking so much time to resolve this, but it really is a big mystery.
Regards, Harald
Am Tue, 13 Jul 2010 16:06:55 +0200 schrieb Harald Welte laforge@gnumonks.org:
Hi, Harald!
I suggest you ask Mr. Schneider for an OK to buy some old Nokia 3310 off eBay, and possibly a SonyEricsson K800i. This is what I mostly use for testing. At least on GPRS, the K800i was particularly "picky" i.e. it would always refuse to work if OpenBSC/OsmoSGSN did anything wrong - which made it a good device for testing.
I just forwarded your E-Mail to Mr. Schneider. Thanks for the suggestion!
Can you try the GSM1800 nanoBTS, and tell me the software/firmware version (as reported by ipaccess-config)? Holger, Dieter and myself all don't understand the problems you are experiencing, and it might be something that is different in your setup than ours (and we use GSM1800 nanoBTS).
Of course! I tested OpenBSC with GSM1800, too. And, unfortunately, it does not work... Attached the pcap-file and the config of OpenBSC. Here some information from ipaccess-find:
MAC Address='00:02:95:00:34:f8' IP Address='192.168.1.172' Unit ID='150/0/0' Location 1='NSAG Entw 1' Location 2='BTS_NBT131G' Equipment Version='165a029_48' Software Version='168a002_v141d0' Unit Name='BTS_140' Serial Number='00072269'
Sorry for taking so much time to resolve this, but it really is a big mystery.
Thank you for your help! Sometimes can bugs be very difficult to find... :D
Bye
-
Harald Welte -
Holger Hans Peter Freyther -
Luca Bertoncello -
Sylvain Munaut