From zero-kelvin at gmx.de  Thu Nov  1 11:42:32 2012
From: zero-kelvin at gmx.de (dexter)
Date: Thu, 01 Nov 2012 12:42:32 +0100
Subject: Future of our Osmocom Berlin User Group meeting
In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org>
References: <502d01a9.mirider@mirider.augusta.de>
	<20120818115942.GV29525@prithivi.gnumonks.org>
Message-ID: <50926028.4040500@gmx.de>

Hi folks.

We have not met each other for a couple of weeks. I think we should keep
the meeting going.

I am willing to send out the invitation-mails and take card about open
doors at the CCCB.

So far so good lets move on!
      
This is the announcement for the next Osmocom Berlin meeting.

    Nov 07, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin

There is no formal presentation scheduled for this meeting.

If you are interested to show up, feel free to do so.  There is no
registration required.  The meeting is free as in "free beer", despite
no actual free beer being around.

Regards,
Philipp Maier




From laforge at gnumonks.org  Mon Nov  5 11:47:12 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 5 Nov 2012 12:47:12 +0100
Subject: Future of our Osmocom Berlin User Group meeting
In-Reply-To: <50926028.4040500@gmx.de>
References: <502d01a9.mirider@mirider.augusta.de>
	<20120818115942.GV29525@prithivi.gnumonks.org>
	<50926028.4040500@gmx.de>
Message-ID: <20121105114712.GD29904@prithivi.gnumonks.org>

Hi Dexter,

On Thu, Nov 01, 2012 at 12:42:32PM +0100, dexter wrote:
> We have not met each other for a couple of weeks. I think we should keep
> the meeting going.
> 
> I am willing to send out the invitation-mails and take card about open
> doors at the CCCB.

thanks for taking care of this.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From zero-kelvin at gmx.de  Sun Nov 18 19:12:11 2012
From: zero-kelvin at gmx.de (dexter)
Date: Sun, 18 Nov 2012 20:12:11 +0100
Subject: Future of our Osmocom Berlin User Group meeting
In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org>
References: <502d01a9.mirider@mirider.augusta.de>
	<20120818115942.GV29525@prithivi.gnumonks.org>
Message-ID: <50A9330B.3030905@gmx.de>

Hi folks.

      This is the announcement for the next Osmocom Berlin meeting.

    Nov 21, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin

There is no formal presentation scheduled for this meeting.

If you are interested to show up, feel free to do so.  There is no
registration required.  The meeting is free as in "free beer", despite
no actual free beer being around.

Regards,
Philipp Maier




From zero-kelvin at gmx.de  Sun Nov 18 20:19:59 2012
From: zero-kelvin at gmx.de (dexter)
Date: Sun, 18 Nov 2012 21:19:59 +0100
Subject: Osmocom Berlin User Group meeting
In-Reply-To: <50A9330B.3030905@gmx.de>
References: <502d01a9.mirider@mirider.augusta.de>
	<20120818115942.GV29525@prithivi.gnumonks.org>
	<50A9330B.3030905@gmx.de>
Message-ID: <50A942EF.1030403@gmx.de>

Sorry, i messed up the subject...
> Hi folks.
>
>       This is the announcement for the next Osmocom Berlin meeting.
>
>     Nov 21, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
>
> There is no formal presentation scheduled for this meeting.
>
> If you are interested to show up, feel free to do so.  There is no
> registration required.  The meeting is free as in "free beer", despite
> no actual free beer being around.
>
> Regards,
> Philipp Maier
>
>




From laforge at gnumonks.org  Mon Nov 19 10:22:15 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 19 Nov 2012 11:22:15 +0100
Subject: Osmocom Berlin User Group meeting on Nov 21
In-Reply-To: <50A942EF.1030403@gmx.de>
References: <502d01a9.mirider@mirider.augusta.de>
	<20120818115942.GV29525@prithivi.gnumonks.org>
	<50A9330B.3030905@gmx.de> <50A942EF.1030403@gmx.de>
Message-ID: <20121119102215.GU8595@prithivi.gnumonks.org>

Hi Dexter,

JFYI: After a long break, I'll be able to participate again this week.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From holger at freyther.de  Thu Nov 22 09:26:22 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 22 Nov 2012 10:26:22 +0100
Subject: SI Generation and multi-trx setup
In-Reply-To: <5075216B.9090804@eversberg.eu>
References: <20121008202423.GC21775@xiaoyu.lan> <507402F6.4090608@eversberg.eu>
	<20121009133136.GA16080@xiaoyu.lan> <50744387.3020904@eversberg.eu>
	<20121009200225.GE1964@xiaoyu.lan> <5075216B.9090804@eversberg.eu>
Message-ID: <20121122092622.GA25233@xiaoyu.lan>

On Wed, Oct 10, 2012 at 09:19:07AM +0200, jolly wrote:

Hi,

> if we want changes of config to be present in the SI whenever a TRX
> comes up, it is required to generate it when this happens. (so forget my
> last patch, because it does not do it and also it does it wrong.) i have
> no better solution in mind right now. can you test my attached patch
> before i commit it, because i don't have multi TRX setup?

do you have time to test this yourself? I have already sent an email how
to easily install the FakeBTS code on Debian 6.0 (and later), and now I
pushed my dual trx implementation and updated the package.

$ gst
st: PackageLoader fileInPackage: #FakeBTS.
st: dual := FakeBTS.DualTrxBTS new btsId: '1/0/0'; yourself
st: dual connect: 'localhost'; waitForBTSReady.

this will create a DualTRX BTS with unit id 1 and connect it to the
localhost. If you want to re-connect just call the last line again.


cheers
	holger



From andreas at eversberg.eu  Mon Nov 26 08:46:12 2012
From: andreas at eversberg.eu (jolly)
Date: Mon, 26 Nov 2012 09:46:12 +0100
Subject: SI Generation and multi-trx setup
In-Reply-To: <20121122092622.GA25233@xiaoyu.lan>
References: <20121008202423.GC21775@xiaoyu.lan>
	<507402F6.4090608@eversberg.eu>	<20121009133136.GA16080@xiaoyu.lan>
	<50744387.3020904@eversberg.eu>	<20121009200225.GE1964@xiaoyu.lan>
	<5075216B.9090804@eversberg.eu> <20121122092622.GA25233@xiaoyu.lan>
Message-ID: <50B32C54.6080307@eversberg.eu>

Holger Hans Peter Freyther wrote:
> do you have time to test this yourself? I have already sent an email how
> to easily install the FakeBTS code on Debian 6.0 (and later), and now I
> pushed my dual trx implementation and updated the package.
>
> $ gst
> st: PackageLoader fileInPackage: #FakeBTS.
> st: dual := FakeBTS.DualTrxBTS new btsId: '1/0/0'; yourself
> st: dual connect: 'localhost'; waitForBTSReady.
>
> this will create a DualTRX BTS with unit id 1 and connect it to the
> localhost. If you want to re-connect just call the last line again.
hi holger,

...
<0019> input/ipa.c:322 accept()ed new link from 127.0.0.1 to port 3003
<0004> bsc_init.c:284 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 871
using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7
<0003> system_information.c:333 Serving cell: 871 873
<0003> bsc_init.c:104 SI1: 55 06 19 8f b3 a0 00 00 00 00 00 00 00 00 00
00 00 00 00 e5 04 00 2b
<0003> bsc_init.c:104 SI2: 59 06 1a 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 ff e5 04 00
<0003> bsc_init.c:104 SI3: 49 06 1b 00 00 00 f1 10 00 01 49 03 00 27 47
40 e5 04 00 3b 2b 2b 2b
<0003> bsc_init.c:104 SI4: 31 06 1c 00 f1 10 00 01 47 40 e5 04 00 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b
<0003> bsc_init.c:104 SI5: 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 2b 2b 2b 2b
<0003> bsc_init.c:104 SI6: 2d 06 1e 00 00 00 f1 10 00 01 27 ff 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b
...
<0019> input/ipa.c:322 accept()ed new link from 127.0.0.1 to port 3003
<0004> bsc_init.c:284 bootstrapping RSL for BTS/TRX (0/1) on ARFCN 873
using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7
<0003> bsc_init.c:104 SI5: 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 2b 2b 2b 2b
<0003> bsc_init.c:104 SI6: 2d 06 1e 00 00 00 f1 10 00 01 27 ff 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b
...

as you can see, it works. i have also tested it with BS11 and forced
voice traffic to second TRX. it works. you can apply my patch.

regards,

andreas




From holger at freyther.de  Thu Nov  8 08:33:24 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 8 Nov 2012 09:33:24 +0100
Subject: 29C3 osmo-nitb sprint and issues
In-Reply-To: <20121015074244.GF20812@xiaoyu.lan>
References: <20121015074244.GF20812@xiaoyu.lan>
Message-ID: <20121108083324.GA13476@xiaoyu.lan>

On Mon, Oct 15, 2012 at 09:42:44AM +0200, Holger Hans Peter Freyther wrote:

Hi again,

> 
> The first sprint is scheduled for the 9th, 10th (and maybe 11th) of
> November. There is no venue for it yet, maybe the CCCB. Please indicate
> if you are interested to join.

it will be the CCCB. I will be there tomorrow starting from 10h.

kind regards
	holger




From holger at freyther.de  Thu Nov  8 21:29:53 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 8 Nov 2012 22:29:53 +0100
Subject: 29C3 osmo-nitb sprint and issues
In-Reply-To: <20121108083324.GA13476@xiaoyu.lan>
References: <20121015074244.GF20812@xiaoyu.lan>
	<20121108083324.GA13476@xiaoyu.lan>
Message-ID: <20121108212953.GD25214@xiaoyu.lan>

On Thu, Nov 08, 2012 at 09:33:24AM +0100, Holger Hans Peter Freyther wrote:
> On Mon, Oct 15, 2012 at 09:42:44AM +0200, Holger Hans Peter Freyther wrote:
> 

> it will be the CCCB. I will be there tomorrow starting from 10h.
> 

It appears like this will not take place in the form I had hoped it would
take place. I am going to be at the CCCB and continue working with the
modem bank to make some simple tests.

So it appears that this sprint is off.



From holger at freyther.de  Thu Nov 22 18:17:03 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 22 Nov 2012 19:17:03 +0100
Subject: [PATH] Selecting the latest nanoBTS firmware on connect Re:
	nanoBTS bring up problem
In-Reply-To: <CABmJbFWq8dZQdvpef4sBz0Hh3arrQNabFxs-EWuDDUVr=sCLBA@mail.gmail.com>
References: <CABmJbFVtBVU0pHOtuUosC8vq-opSvu0QzN9SL0-4tY2HSHteyQ@mail.gmail.com>
	<20121025145947.GD9520@xiaoyu.lan>
	<CABmJbFWq8dZQdvpef4sBz0Hh3arrQNabFxs-EWuDDUVr=sCLBA@mail.gmail.com>
Message-ID: <20121122181703.GG25233@xiaoyu.lan>

On Thu, Oct 25, 2012 at 09:14:32PM +0400, Alexander Chemeris wrote:
> Hi Holger,

Hi Alexander,

> 
> Three variants, extracted from my previous e-mail about the NACK problem:

I pushed zecke/abis-sw-selection to our repository. Could you please give
it a try? The logic should be like from your patch (but not assuming that
the file version is 8 bytes).

thanks
	holger



From alexander.chemeris at gmail.com  Thu Nov 22 19:26:44 2012
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Thu, 22 Nov 2012 23:26:44 +0400
Subject: [PATH] Selecting the latest nanoBTS firmware on connect Re:
	nanoBTS bring up problem
In-Reply-To: <20121122181703.GG25233@xiaoyu.lan>
References: <CABmJbFVtBVU0pHOtuUosC8vq-opSvu0QzN9SL0-4tY2HSHteyQ@mail.gmail.com>
	<20121025145947.GD9520@xiaoyu.lan>
	<CABmJbFWq8dZQdvpef4sBz0Hh3arrQNabFxs-EWuDDUVr=sCLBA@mail.gmail.com>
	<20121122181703.GG25233@xiaoyu.lan>
Message-ID: <CABmJbFV7E0HfkWrog10fhQbFOJBDcK7yZEhsaWeLYvnm00CvjA@mail.gmail.com>

Hi,

I already disconnected everything, but I'll try to give it a shot at
the weekend or next week. Ping me if I forget to do that.

On Thu, Nov 22, 2012 at 10:17 PM, Holger Hans Peter Freyther
<holger at freyther.de> wrote:
> On Thu, Oct 25, 2012 at 09:14:32PM +0400, Alexander Chemeris wrote:
>> Hi Holger,
>
> Hi Alexander,
>
>>
>> Three variants, extracted from my previous e-mail about the NACK problem:
>
> I pushed zecke/abis-sw-selection to our repository. Could you please give
> it a try? The logic should be like from your patch (but not assuming that
> the file version is 8 bytes).
>
> thanks
>         holger



-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From holger at freyther.de  Thu Nov  1 09:01:39 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 1 Nov 2012 10:01:39 +0100
Subject: triplets calculation
In-Reply-To: <BLU171-W110FB8970F4D29563B6A6DA8B610@phx.gbl>
References: <BLU171-W110FB8970F4D29563B6A6DA8B610@phx.gbl>
Message-ID: <20121101090139.GC26158@xiaoyu.lan>

On Wed, Oct 31, 2012 at 04:43:51PM +0100, Yann R. Moupinda wrote:
> 
> I thought i could get the triplets stored in one of the tables of hlr.sqlite3 (AuthLastTuples) but there is no information on it. From the table AuthKeys i could find some Ki values (e.g   X'019B7083FBAFC928421A147DE795217782'). I found that there is an "osmo-auc-gen" program for computing the triplets. By using the Ki from AuthKeys and a self generated RAND (e.g  0123456789ABCDEF0123456789ABCDEF) the program doesn't run and doesn't give the triplets. The used authentication algorithm is the COMP128v1.
> 

What is the error you get? The Ki you present is 17 bytes but it must
be 16 bytes. 

$ ./osmo-auc-gen -2 -a COMP128v1 -k 12345678901234561234567890123456

holger



From holger at freyther.de  Thu Nov  1 09:17:22 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 1 Nov 2012 10:17:22 +0100
Subject: triplets calculation
In-Reply-To: <20121101090139.GC26158@xiaoyu.lan>
References: <BLU171-W110FB8970F4D29563B6A6DA8B610@phx.gbl>
	<20121101090139.GC26158@xiaoyu.lan>
Message-ID: <20121101091722.GF26158@xiaoyu.lan>

On Thu, Nov 01, 2012 at 10:01:39AM +0100, Holger Hans Peter Freyther wrote:
> On Wed, Oct 31, 2012 at 04:43:51PM +0100, Yann R. Moupinda wrote:
> What is the error you get? The Ki you present is 17 bytes but it must
> be 16 bytes. 

I assume you copied the keys out of the sqlite3 database. OsmoNITB is
using 'DBI' (a database abstraction library) to access the database and
they encode BLOBs. You will need to use the _dbd_decode_binary[1] routine
to turn this data into your Ki.

holger

[1] http://libdbi.sourceforge.net/docs/driver-guide/helperfuncs.html#INTERNAL-DBD-DECODE-BINARY



From dmisol at mail.ru  Thu Nov  1 07:02:10 2012
From: dmisol at mail.ru (=?UTF-8?B?RG1pdHJpIFNvbG92aWV2?=)
Date: Thu, 01 Nov 2012 11:02:10 +0400
Subject: =?UTF-8?B?Tm9uLXN5bmNocm9uaXplZCBoYW5kb3Zlcg==?=
Message-ID: <1351753330.633049138@f339.mail.ru>

Hi,

I'm implementing handover for OpenBTS project:?http://wush.net/trac/rangepublic/wiki/Handover
Some handsets perform handover properly, while the others (such as Nokia) do not appear at the target channel with HandoverAccess.

Handover Command contains the minimal set of parameters that looks reasonable:
-- cellDescription
-- channelDescription
-- handoverReference
-- powerCommand - tried various levels

I'll appreciate real-life traces of handover, non-sync case. As far as I know, this one is used for ipAccess..
Handover Command fields are particularly interesting. 

Thank you,
Dmitri?

From alexander.chemeris at gmail.com  Thu Nov  1 07:33:28 2012
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Thu, 1 Nov 2012 11:33:28 +0400
Subject: Non-synchronized handover
In-Reply-To: <1351753330.633049138@f339.mail.ru>
References: <1351753330.633049138@f339.mail.ru>
Message-ID: <CABmJbFU29TiBSU+q8kP7Jg=8Rxh6ML2X78O0nHfQ63KTfywC5Q@mail.gmail.com>

Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
If you find out how to issue a handover command in OpenBSC, you could try
by yourself.

Sent from my Android device.

--
Regards,
Alexander Chemeris
CEO, Fairwaves LLC
http://fairwaves.ru
01.11.2012 11:02 ???????????? "Dmitri Soloviev" <dmisol at mail.ru> ???????:

> Hi,
>
> I'm implementing handover for OpenBTS project:
> http://wush.net/trac/rangepublic/wiki/Handover
> Some handsets perform handover properly, while the others (such as Nokia)
> do not appear at the target channel with HandoverAccess.
>
> Handover Command contains the minimal set of parameters that looks
> reasonable:
> -- cellDescription
> -- channelDescription
> -- handoverReference
> -- powerCommand - tried various levels
>
> I'll appreciate real-life traces of handover, non-sync case. As far as I
> know, this one is used for ipAccess..
> Handover Command fields are particularly interesting.
>
> Thank you,
> Dmitri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121101/8fba9a6b/attachment.htm>

From laforge at gnumonks.org  Thu Nov  1 18:22:21 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 1 Nov 2012 19:22:21 +0100
Subject: Non-synchronized handover
In-Reply-To: <CABmJbFU29TiBSU+q8kP7Jg=8Rxh6ML2X78O0nHfQ63KTfywC5Q@mail.gmail.com>
References: <1351753330.633049138@f339.mail.ru>
	<CABmJbFU29TiBSU+q8kP7Jg=8Rxh6ML2X78O0nHfQ63KTfywC5Q@mail.gmail.com>
Message-ID: <20121101182221.GV15458@prithivi.gnumonks.org>

Hi Alexander and Dmitri,

On Thu, Nov 01, 2012 at 11:33:28AM +0400, Alexander Chemeris wrote:
> Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
> If you find out how to issue a handover command in OpenBSC, you could try
> by yourself.

You cannot issue a handover command manually in OpenBSC.  The way how we
test handover is to use two BTSs connected to one OsmoNITB, and use
rotary/adjustable attenuators in the Tx path to make one BTS signal
weaker than the other BTS, at which point the handover algorithm will
kick in and perform the hand-over.

The DMEAS and the DHO debug logging might be useful to monitor what is
happening while you're doing that.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From dmisol at mail.ru  Thu Nov  1 18:50:32 2012
From: dmisol at mail.ru (=?UTF-8?B?RG1pdHJpIFNvbG92aWV2?=)
Date: Thu, 01 Nov 2012 22:50:32 +0400
Subject: =?UTF-8?B?UmVbMl06IE5vbi1zeW5jaHJvbml6ZWQgaGFuZG92ZXI=?=
In-Reply-To: <20121101182221.GV15458@prithivi.gnumonks.org>
References: <1351753330.633049138@f339.mail.ru>
	<CABmJbFU29TiBSU+q8kP7Jg=8Rxh6ML2X78O0nHfQ63KTfywC5Q@mail.gmail.com>
	<20121101182221.GV15458@prithivi.gnumonks.org>
Message-ID: <1351795832.313165711@f200.mail.ru>

Thank you Harald.

I discovered that there is a single alive nanoBTS in the hackerspace :(
But we also discovered that you have a perfect OpenBSC code that can be studied :)

Regards,
Dmitri

Thu, 1 Nov 2012 19:22:21 +0100 ?? Harald Welte <laforge at gnumonks.org>:
>	
>
>
	
	
>
		
		
			
>Hi Alexander and Dmitri,
>
>
On Thu, Nov 01, 2012 at 11:33:28AM +0400, Alexander Chemeris wrote:
>
> Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
>
> If you find out how to issue a handover command in OpenBSC, you could try
>
> by yourself.
>
>
You cannot issue a handover command manually in OpenBSC.  The way how we
>
test handover is to use two BTSs connected to one OsmoNITB, and use
>
rotary/adjustable attenuators in the Tx path to make one BTS signal
>
weaker than the other BTS, at which point the handover algorithm will
>
kick in and perform the hand-over.
>
>
The DMEAS and the DHO debug logging might be useful to monitor what is
>
happening while you're doing that.
>
>
Regards,
>
	Harald
>
-- 
>
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
>
============================================================================
>
"Privacy in residential applications is a desirable marketing option."
>
??????????????????????????????????????????????????(ETSI EN 300 175-7 Ch. A6)
>
			
		
		
	

	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121101/26009842/attachment.htm>

From dmisol at mail.ru  Thu Nov  1 20:29:34 2012
From: dmisol at mail.ru (=?UTF-8?B?RG1pdHJpIFNvbG92aWV2?=)
Date: Fri, 02 Nov 2012 00:29:34 +0400
Subject: =?UTF-8?B?UmVbMl06IE5vbi1zeW5jaHJvbml6ZWQgaGFuZG92ZXI=?=
In-Reply-To: <20121101182221.GV15458@prithivi.gnumonks.org>
References: <1351753330.633049138@f339.mail.ru>
	<CABmJbFU29TiBSU+q8kP7Jg=8Rxh6ML2X78O0nHfQ63KTfywC5Q@mail.gmail.com>
	<20121101182221.GV15458@prithivi.gnumonks.org>
Message-ID: <1351801774.602150355@f205.mail.ru>

Hi Harald,

we are using exactly the same Handover Command.
Right now I have no clue to Nokia handsets behavior during handover.
So, I'm waiting for the second umTRX to start playing with handover again.

Thank you for your letter.

Regards,
Dmitri?


Thu, 1 Nov 2012 19:22:21 +0100 ?? Harald Welte <laforge at gnumonks.org>:
>	
>
>
	
	
>
		
		
			
>Hi Alexander and Dmitri,
>
>
On Thu, Nov 01, 2012 at 11:33:28AM +0400, Alexander Chemeris wrote:
>
> Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
>
> If you find out how to issue a handover command in OpenBSC, you could try
>
> by yourself.
>
>
You cannot issue a handover command manually in OpenBSC.  The way how we
>
test handover is to use two BTSs connected to one OsmoNITB, and use
>
rotary/adjustable attenuators in the Tx path to make one BTS signal
>
weaker than the other BTS, at which point the handover algorithm will
>
kick in and perform the hand-over.
>
>
The DMEAS and the DHO debug logging might be useful to monitor what is
>
happening while you're doing that.
>
>
Regards,
>
	Harald
>
-- 
>
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
>
============================================================================
>
"Privacy in residential applications is a desirable marketing option."
>
??????????????????????????????????????????????????(ETSI EN 300 175-7 Ch. A6)
>
			
		
		
	

	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121102/cb9436bf/attachment.htm>

From alexander.chemeris at gmail.com  Mon Nov  5 18:34:33 2012
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Mon, 5 Nov 2012 13:34:33 -0500
Subject: Non-synchronized handover
In-Reply-To: <20121101182221.GV15458@prithivi.gnumonks.org>
References: <1351753330.633049138@f339.mail.ru>
	<CABmJbFU29TiBSU+q8kP7Jg=8Rxh6ML2X78O0nHfQ63KTfywC5Q@mail.gmail.com>
	<20121101182221.GV15458@prithivi.gnumonks.org>
Message-ID: <CABmJbFVagWQZwCWW+taqPz3NffMesigoJ6xKudM_d0ngE_a4yg@mail.gmail.com>

Hi Harald,

On Thu, Nov 1, 2012 at 2:22 PM, Harald Welte <laforge at gnumonks.org> wrote:
> On Thu, Nov 01, 2012 at 11:33:28AM +0400, Alexander Chemeris wrote:
>> Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
>> If you find out how to issue a handover command in OpenBSC, you could try
>> by yourself.
>
> You cannot issue a handover command manually in OpenBSC.  The way how we
> test handover is to use two BTSs connected to one OsmoNITB, and use
> rotary/adjustable attenuators in the Tx path to make one BTS signal
> weaker than the other BTS, at which point the handover algorithm will
> kick in and perform the hand-over.

If this is done inside of the OpenBSC, it should be easy to hack a VTY
command to force handover. It may be a useful command as well, if you
want to do load balancing of your network. Am I missing something?

> The DMEAS and the DHO debug logging might be useful to monitor what is
> happening while you're doing that.

Thanks.

--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From dmisol at mail.ru  Mon Nov  5 19:05:33 2012
From: dmisol at mail.ru (=?UTF-8?B?RG1pdHJpIFNvbG92aWV2?=)
Date: Mon, 05 Nov 2012 23:05:33 +0400
Subject: =?UTF-8?B?UmVbMl06IE5vbi1zeW5jaHJvbml6ZWQgaGFuZG92ZXI=?=
In-Reply-To: <CABmJbFVagWQZwCWWtaqPz3NffMesigoJ6xKudM_d0ngE_a4yg@mail.gmail.com>
References: <20121101182221.GV15458@prithivi.gnumonks.org>
	<1351753330.633049138@f339.mail.ru>
	<CABmJbFVagWQZwCWWtaqPz3NffMesigoJ6xKudM_d0ngE_a4yg@mail.gmail.com>
Message-ID: <1352142333.740536122@f42.mail.ru>

as for OpenBTS handover, I studied OpenBSC code.
I'm issuing exactly the same handover command, even including the sequence of fields, not only values :)

I'm waiting for the second umTXR back to continue investigating.. ?


Mon, 5 Nov 2012 13:34:33 -0500 ?? Alexander Chemeris <alexander.chemeris at gmail.com>:
>	
>
>
	
	
>
		
		
			
>Hi Harald,
>
>
On Thu, Nov 1, 2012 at 2:22 PM, Harald Welte <laforge at gnumonks.org> wrote:
>
> On Thu, Nov 01, 2012 at 11:33:28AM +0400, Alexander Chemeris wrote:
>
>> Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
>
>> If you find out how to issue a handover command in OpenBSC, you could try
>
>> by yourself.
>
>
>
> You cannot issue a handover command manually in OpenBSC.  The way how we
>
> test handover is to use two BTSs connected to one OsmoNITB, and use
>
> rotary/adjustable attenuators in the Tx path to make one BTS signal
>
> weaker than the other BTS, at which point the handover algorithm will
>
> kick in and perform the hand-over.
>
>
If this is done inside of the OpenBSC, it should be easy to hack a VTY
>
command to force handover. It may be a useful command as well, if you
>
want to do load balancing of your network. Am I missing something?
>
>
> The DMEAS and the DHO debug logging might be useful to monitor what is
>
> happening while you're doing that.
>
>
Thanks.
>
>
--
>
Regards,
>
Alexander Chemeris.
>
CEO, Fairwaves LLC / ??? ???????
>http://fairwaves.ru
>
			
		
		
	

	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121105/0445f2b5/attachment.htm>

From mailman at lists.osmocom.org  Mon Nov  5 11:54:59 2012
From: mailman at lists.osmocom.org (mailman at lists.osmocom.org)
Date: Mon, 05 Nov 2012 12:54:59 +0100
Subject: Bounce action notification
Message-ID: <mailman.473.1352116499.1438.openbsc@lists.osmocom.org>

This is a Mailman mailing list bounce action notice:

    List:       OpenBSC
    Member:     openbsc at slewe.com
    Action:     Subscription disabled.
    Reason:     Excessive or fatal bounces.
    


The triggering bounce notice is attached below.

Questions? Contact the Mailman site administrator at
mailman at lists.osmocom.org.
-------------- next part --------------
An embedded message was scrubbed...
From: Mail Delivery System <Mailer-Daemon at ganesha.gnumonks.org>
Subject: Mail delivery failed: returning message to sender
Date: Mon, 05 Nov 2012 12:54:56 +0100
Size: 9895
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121105/d08c71b1/attachment.eml>

From holger at freyther.de  Wed Nov  7 14:21:14 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 7 Nov 2012 15:21:14 +0100
Subject: osmo_sock_init/getaddrinfo not working for GRE/SOCKET_RAW
Message-ID: <20121107142114.GA15242@xiaoyu.lan>

Dear Pablo,

getaddrinfo does not work for the combination of AF_INET, SOCK_RAW
and IPPROTO_GRE. I have attached an example application that can be
compiled with:

  $ gcc -o fr fr.c `pkg-config --cflags --libs libosmocore libosmogb`

this prints:
getaddrinfo returned NULL: Success
FAILED

gettadrinfo returns -8 which should be this:
# define EAI_SERVICE      -8    /* SERVICE not supported for `ai_socktype'.  */


I am not sure what is the most clever way to resolve this. Make SOCK_RAW
branch out early and do the socket/bind(/listen) manually, use getaddrinfo
twice with some more unspefici options, just deal with SOCK_RAW differently
now? The attached code has the benefit of at least handling INET and INET6
inside the getaddrinfo result.


any ideas?
	holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fr.c
Type: text/x-csrc
Size: 461 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121107/c9ceca0b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foo.diff
Type: text/x-diff
Size: 990 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121107/c9ceca0b/attachment-0001.bin>

From holger at freyther.de  Sun Nov 11 13:47:33 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 14:47:33 +0100
Subject: osmo_sock_init/getaddrinfo not working for GRE/SOCKET_RAW
In-Reply-To: <20121107142114.GA15242@xiaoyu.lan>
References: <20121107142114.GA15242@xiaoyu.lan>
Message-ID: <20121111134733.GE17503@xiaoyu.lan>

On Wed, Nov 07, 2012 at 03:21:14PM +0100, Holger Hans Peter Freyther wrote:
> Dear Pablo,

Hi,

I added the frame for a unit test to zecke/fr-gre-test. The reasoning
is quite simple.. the frame-relay code is seldomly used during development
and I really don't want to look stupid to have this error again.. :)

cheers
	holger




From holger at freyther.de  Thu Nov 22 18:14:38 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 22 Nov 2012 19:14:38 +0100
Subject: osmo_sock_init/getaddrinfo not working for GRE/SOCKET_RAW
In-Reply-To: <20121111134733.GE17503@xiaoyu.lan>
References: <20121107142114.GA15242@xiaoyu.lan>
	<20121111134733.GE17503@xiaoyu.lan>
Message-ID: <20121122181438.GF25233@xiaoyu.lan>

On Sun, Nov 11, 2012 at 02:47:33PM +0100, Holger Hans Peter Freyther wrote:
> On Wed, Nov 07, 2012 at 03:21:14PM +0100, Holger Hans Peter Freyther wrote:
> > Dear Pablo,
> 

ping?



From pablo at gnumonks.org  Thu Nov 22 21:36:34 2012
From: pablo at gnumonks.org (Pablo Neira Ayuso)
Date: Thu, 22 Nov 2012 22:36:34 +0100
Subject: osmo_sock_init/getaddrinfo not working for GRE/SOCKET_RAW
In-Reply-To: <20121107142114.GA15242@xiaoyu.lan>
References: <20121107142114.GA15242@xiaoyu.lan>
Message-ID: <20121122213634.GA14200@1984>

Hi Holger!

On Wed, Nov 07, 2012 at 03:21:14PM +0100, Holger Hans Peter Freyther wrote:
> Dear Pablo,
> 
> getaddrinfo does not work for the combination of AF_INET, SOCK_RAW
> and IPPROTO_GRE. I have attached an example application that can be
> compiled with:
> 
>   $ gcc -o fr fr.c `pkg-config --cflags --libs libosmocore libosmogb`
> 
> this prints:
> getaddrinfo returned NULL: Success
> FAILED

$ strace ./fr
[...]
socket(PF_NETLINK, SOCK_RAW, 0)         = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=5936, groups=00000000}, [12]) = 0
sendto(3, "\24\0\0\0\26\0\1\3+\230\256P\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"0\0\0\0\24\0\2\0+\230\256P0\27\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 108
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"@\0\0\0\24\0\2\0+\230\256P0\27\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0+\230\256P0\27\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 20

The interesting thing is that the function calls rtnetlink to obtain
address information from the kernel, and it seems it gets it right.

Let me decipher that netlink trace:

1) bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
                                                        ^^
   bind this socket to rtnetlink

2) Send the request message to ask for the address information.

sendto(3, "\24\0\0\0\26\0\1\3+\230\256P\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20

3) We get the multipart message with the information that we
requested:

recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"0\0\0\0\24\0\2\0+\230\256P0\27\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 108
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"@\0\0\0\24\0\2\0+\230\256P0\27\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},

The problem seems to be in glibc, at sysdeps/posix/getaddrinfo.c, line 125:

  { SOCK_RAW, 0, GAI_PROTO_PROTOANY|GAI_PROTO_NOSERVICE, true, "raw" }

The GAI_PROTO_NOSERVICE flag is set, while interating over the list of
addresses that it has obtained from the kernel to return the addrinfo
object, it seems to skip the raw protocol and it returns EAI_SERVICE.

I'd need to investigate further the reason why they are doing like
that.

> gettadrinfo returns -8 which should be this:
> # define EAI_SERVICE      -8    /* SERVICE not supported for `ai_socktype'.  */
> 
> 
> I am not sure what is the most clever way to resolve this. Make SOCK_RAW
> branch out early and do the socket/bind(/listen) manually, use getaddrinfo
> twice with some more unspefici options, just deal with SOCK_RAW differently
> now? The attached code has the benefit of at least handling INET and INET6
> inside the getaddrinfo result.
> 
> any ideas?

The quick thing would be to workaround libosmocore. I'll try to
investigate this issue a bit more but it may take me a while.

Hope it helps.



From pablo at gnumonks.org  Thu Nov 22 21:38:46 2012
From: pablo at gnumonks.org (Pablo Neira Ayuso)
Date: Thu, 22 Nov 2012 22:38:46 +0100
Subject: osmo_sock_init/getaddrinfo not working for GRE/SOCKET_RAW
In-Reply-To: <20121122213634.GA14200@1984>
References: <20121107142114.GA15242@xiaoyu.lan> <20121122213634.GA14200@1984>
Message-ID: <20121122213846.GA15245@1984>

On Thu, Nov 22, 2012 at 10:36:34PM +0100, Pablo Neira Ayuso wrote:
> Hi Holger!
> 
> On Wed, Nov 07, 2012 at 03:21:14PM +0100, Holger Hans Peter Freyther wrote:
> > Dear Pablo,
> > 
> > getaddrinfo does not work for the combination of AF_INET, SOCK_RAW
> > and IPPROTO_GRE. I have attached an example application that can be
> > compiled with:
> > 
> >   $ gcc -o fr fr.c `pkg-config --cflags --libs libosmocore libosmogb`
> > 
> > this prints:
> > getaddrinfo returned NULL: Success
> > FAILED
> 
> $ strace ./fr
> [...]
> socket(PF_NETLINK, SOCK_RAW, 0)         = 3
> bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
> getsockname(3, {sa_family=AF_NETLINK, pid=5936, groups=00000000}, [12]) = 0
> sendto(3, "\24\0\0\0\26\0\1\3+\230\256P\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> msg_iov(1)=[{"0\0\0\0\24\0\2\0+\230\256P0\27\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 108
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> msg_iov(1)=[{"@\0\0\0\24\0\2\0+\230\256P0\27\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> msg_iov(1)=[{"\24\0\0\0\3\0\2\0+\230\256P0\27\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
> 
> The interesting thing is that the function calls rtnetlink to obtain
> address information from the kernel, and it seems it gets it right.
> 
> Let me decipher that netlink trace:
> 
> 1) bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
>                                                         ^^
>    bind this socket to rtnetlink
> 
> 2) Send the request message to ask for the address information.
> 
> sendto(3, "\24\0\0\0\26\0\1\3+\230\256P\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
> 
> 3) We get the multipart message with the information that we
> requested:
> 
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> msg_iov(1)=[{"0\0\0\0\24\0\2\0+\230\256P0\27\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 108
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> msg_iov(1)=[{"@\0\0\0\24\0\2\0+\230\256P0\27\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> 
> The problem seems to be in glibc, at sysdeps/posix/getaddrinfo.c, line 125:
> 
>   { SOCK_RAW, 0, GAI_PROTO_PROTOANY|GAI_PROTO_NOSERVICE, true, "raw" }
> 
> The GAI_PROTO_NOSERVICE flag is set, while interating over the list of
> addresses that it has obtained from the kernel to return the addrinfo
> object, it seems to skip the raw protocol and it returns EAI_SERVICE.

To be more precise, it returns EAI_SERVICE before even iterating over
the list of address.

This behaviour seems a bit inconsistent to me, ie. requst data from
the kernel, get it all right and discard it :-)



From holger at freyther.de  Fri Nov 23 10:06:56 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 23 Nov 2012 11:06:56 +0100
Subject: osmo_sock_init/getaddrinfo not working for GRE/SOCKET_RAW
In-Reply-To: <20121122213634.GA14200@1984>
References: <20121107142114.GA15242@xiaoyu.lan> <20121122213634.GA14200@1984>
Message-ID: <20121123100656.GB11815@xiaoyu.lan>

On Thu, Nov 22, 2012 at 10:36:34PM +0100, Pablo Neira Ayuso wrote:
> Hi Holger!

Hey!

> The GAI_PROTO_NOSERVICE flag is set, while interating over the list of
> addresses that it has obtained from the kernel to return the addrinfo
> object, it seems to skip the raw protocol and it returns EAI_SERVICE.
> 
> I'd need to investigate further the reason why they are doing like
> that.

one way or another filing a bug report in the glibc bugzilla might be
a good idea.

> 
> The quick thing would be to workaround libosmocore. I'll try to
> investigate this issue a bit more but it may take me a while.

we will need a workaround as the LTS of CentOS/RHEL/Debian/Ubuntu are
unlikely to receive the patch. I am currently using this[1] patch but
I think we can make it less ugly (e.g. try to call getaddrinfo twice,
and if ai_socktype is unspecified use the caller provided one).

holger

[1] https://build.opensuse.org/package/view_file?expand=1&file=raw-socket.patch&package=libosmocore&project=home%3Azecke23&rev=23f0fda08163c3ca98c6f8006bbf8a32



From admin at manateeshome.com  Sat Nov 10 10:33:39 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Sat, 10 Nov 2012 19:33:39 +0900
Subject: ChanModify
Message-ID: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>

<000f> bsc_api.c:315 Sending ChanModify for speech 1 1

<000c> rtp_proxy.c:258 Correcting frame difference of 38886 frames

 

I used to get these messages when I make a call using osmo-nitb.

But recently I updated to newest git version and I get something like

 

<000b> bsc_api.c:374 Sending ChanModify for speech 0 1

<000b> bsc_api.c:118 Using non speech mode: 0

<000b> osmo_msc.c:73 Assignment complete should not have been reached.

 

And I get no sound for my phones.

 

There is a year gap between the previous version and the new version, so I
couldn't locate exactly what change is causing this.

Can somebody help me fixing it?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121110/5e7d0d98/attachment.htm>

From holger at freyther.de  Sat Nov 10 18:28:48 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sat, 10 Nov 2012 19:28:48 +0100
Subject: ChanModify
In-Reply-To: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
Message-ID: <20121110182848.GA16766@xiaoyu.lan>

On Sat, Nov 10, 2012 at 07:33:39PM +0900, Pierre Kim wrote:

Dear Kim,


> <000b> bsc_api.c:374 Sending ChanModify for speech 0 1
> 
> <000b> bsc_api.c:118 Using non speech mode: 0
> 
> <000b> osmo_msc.c:73 Assignment complete should not have been reached.

this message is 'wrong' and should be removed.

> And I get no sound for my phones.

 
> Can somebody help me fixing it?
> 

well please provide the following items:
1.) the command line you use to start osmo-nitb
2.) a pcap file for tracing port 3002, port 3003 and UDP (for
rtp).

cheers
	holger



From admin at manateeshome.com  Sat Nov 10 19:35:37 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Sun, 11 Nov 2012 04:35:37 +0900
Subject: ChanModify
In-Reply-To: <20121110182848.GA16766@xiaoyu.lan>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
Message-ID: <115201cdbf7a$90dde930$b299bb90$@manateeshome.com>

Here is the pcap file

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 3:29 AM
To: openbsc at lists.osmocom.org
Subject: Re: ChanModify

On Sat, Nov 10, 2012 at 07:33:39PM +0900, Pierre Kim wrote:

Dear Kim,


> <000b> bsc_api.c:374 Sending ChanModify for speech 0 1
> 
> <000b> bsc_api.c:118 Using non speech mode: 0
> 
> <000b> osmo_msc.c:73 Assignment complete should not have been reached.

this message is 'wrong' and should be removed.

> And I get no sound for my phones.

 
> Can somebody help me fixing it?
> 

well please provide the following items:
1.) the command line you use to start osmo-nitb
2.) a pcap file for tracing port 3002, port 3003 and UDP (for rtp).

cheers
	holger

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nanobts.pcap
Type: application/octet-stream
Size: 132065 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121111/da0049c6/attachment.obj>

From holger at freyther.de  Sun Nov 11 08:17:43 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 09:17:43 +0100
Subject: ChanModify
In-Reply-To: <115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
Message-ID: <20121111081743.GB16766@xiaoyu.lan>

On Sun, Nov 11, 2012 at 04:35:37AM +0900, Pierre Kim wrote:
> Here is the pcap file

Hi,
I asked for pcap and invocation. The invocation is missing.

> 
> From: openbsc-bounces at lists.osmocom.org
> [mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter
> Freyther

> 
> well please provide the following items:
> 1.) the command line you use to start osmo-nitb
> 2.) a pcap file for tracing port 3002, port 3003 and UDP (for rtp).




From admin at manateeshome.com  Sun Nov 11 10:14:32 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Sun, 11 Nov 2012 19:14:32 +0900
Subject: ChanModify
In-Reply-To: <20121111081743.GB16766@xiaoyu.lan>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
Message-ID: <11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>

I start it with
sudo ./osmo-nitb -m -P

and I did not change anything other than the operating band(PCS1900) from
the default nanobts configuration file.


-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 5:18 PM
To: Pierre Kim
Cc: openbsc at lists.osmocom.org
Subject: Re: ChanModify

On Sun, Nov 11, 2012 at 04:35:37AM +0900, Pierre Kim wrote:
> Here is the pcap file

Hi,
I asked for pcap and invocation. The invocation is missing.

> 
> From: openbsc-bounces at lists.osmocom.org 
> [mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans 
> Peter Freyther

> 
> well please provide the following items:
> 1.) the command line you use to start osmo-nitb
> 2.) a pcap file for tracing port 3002, port 3003 and UDP (for rtp).







From holger at freyther.de  Sun Nov 11 10:33:01 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 11:33:01 +0100
Subject: ChanModify
In-Reply-To: <11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
Message-ID: <20121111103300.GE10708@xiaoyu.lan>

On Sun, Nov 11, 2012 at 07:14:32PM +0900, Pierre Kim wrote:

Hi,

> I start it with
> sudo ./osmo-nitb -m -P

please try with the built-in mncc and without the proxy.

> 
> and I did not change anything other than the operating band(PCS1900) from
> the default nanobts configuration file.

You were using libosmo-abis one year ago? Please include your OpenBSC
configuration file. I think you are not using the right BTS type (or I am
too blind to see it.. or the channel modify ack was actually a nack and
the channel type was not switched to speech).



From admin at manateeshome.com  Sun Nov 11 11:50:54 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Sun, 11 Nov 2012 20:50:54 +0900
Subject: ChanModify
In-Reply-To: <20121111103300.GE10708@xiaoyu.lan>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
Message-ID: <11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>

Here's the pcap file captured from built in mncc.
It works just fine.
And the console says 
<000b> bsc_api.c:374 Sending ChanModify for speech 33 1
<000b> osmo_msc.c:73 Assignment complete should not have been reached.

And I already sent you the configuration file(directly to your email)

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 7:33 PM
To: Pierre Kim
Cc: openbsc at lists.osmocom.org
Subject: Re: ChanModify

On Sun, Nov 11, 2012 at 07:14:32PM +0900, Pierre Kim wrote:

Hi,

> I start it with
> sudo ./osmo-nitb -m -P

please try with the built-in mncc and without the proxy.

> 
> and I did not change anything other than the operating band(PCS1900) 
> from the default nanobts configuration file.

You were using libosmo-abis one year ago? Please include your OpenBSC
configuration file. I think you are not using the right BTS type (or I am
too blind to see it.. or the channel modify ack was actually a nack and the
channel type was not switched to speech).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nanobts_withoutpx.pcap
Type: application/octet-stream
Size: 20572 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121111/13de584f/attachment.obj>

From holger at freyther.de  Sun Nov 11 12:36:50 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 13:36:50 +0100
Subject: ChanModify
In-Reply-To: <11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
Message-ID: <20121111123650.GC17503@xiaoyu.lan>

On Sun, Nov 11, 2012 at 08:50:54PM +0900, Pierre Kim wrote:
> Here's the pcap file captured from built in mncc.
> It works just fine.
> And the console says 
> <000b> bsc_api.c:374 Sending ChanModify for speech 33 1
> <000b> osmo_msc.c:73 Assignment complete should not have been reached.

Hi,

the PBX is 'LCR'? The MNCC interface was not versioned and there
were some changes. I added versioning and I think Andreas had not
merged my code: http://git.misdn.eu/?p=projects/lcr.git;a=shortlog;h=refs/heads/holger/cleaning

holger



From admin at manateeshome.com  Sun Nov 11 14:17:58 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Sun, 11 Nov 2012 23:17:58 +0900
Subject: ChanModify
In-Reply-To: <20121111123650.GC17503@xiaoyu.lan>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
Message-ID: <11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>

Hmm, I am trying to build lcr from your git repo.
But it seems to be broken

chan_lcr.c:701:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
chan_lcr.c: In function 'lcr_in_setup':
chan_lcr.c:950: error: 'struct ast_channel' has no member named
'redirecting'
chan_lcr.c:951: error: 'struct ast_channel' has no member named 'caller'
chan_lcr.c: In function 'lcr_request':
chan_lcr.c:2145: error: 'requestor' undeclared (first use in this function)
chan_lcr.c:2145: error: (Each undeclared identifier is reported only once
chan_lcr.c:2145: error: for each function it appears in.)
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/manatails/gsmc/lcr'
make: *** [all] Error 2



-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 9:37 PM
To: Pierre Kim
Cc: openbsc at lists.osmocom.org
Subject: Re: ChanModify

On Sun, Nov 11, 2012 at 08:50:54PM +0900, Pierre Kim wrote:
> Here's the pcap file captured from built in mncc.
> It works just fine.
> And the console says
> <000b> bsc_api.c:374 Sending ChanModify for speech 33 1 <000b> 
> osmo_msc.c:73 Assignment complete should not have been reached.

Hi,

the PBX is 'LCR'? The MNCC interface was not versioned and there were some
changes. I added versioning and I think Andreas had not merged my code:
http://git.misdn.eu/?p=projects/lcr.git;a=shortlog;h=refs/heads/holger/clean
ing

holger






From holger at freyther.de  Sun Nov 11 16:30:08 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 17:30:08 +0100
Subject: ChanModify
In-Reply-To: <11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
Message-ID: <20121111163008.GJ17503@xiaoyu.lan>

On Sun, Nov 11, 2012 at 11:17:58PM +0900, Pierre Kim wrote:

Hi,

> Hmm, I am trying to build lcr from your git repo.
> But it seems to be broken

I think you need to take it up with Andreas but please include the version
of LCR and Asterisk you are compiling against.

holger

> chan_lcr.c:701:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
> chan_lcr.c: In function 'lcr_in_setup':
> chan_lcr.c:950: error: 'struct ast_channel' has no member named
> 'redirecting'
> chan_lcr.c:951: error: 'struct ast_channel' has no member named 'caller'
> chan_lcr.c: In function 'lcr_request':
> chan_lcr.c:2145: error: 'requestor' undeclared (first use in this function)
> chan_lcr.c:2145: error: (Each undeclared identifier is reported only once
> chan_lcr.c:2145: error: for each function it appears in.)
> make[1]: *** [chan_lcr.po] Error 1
> make[1]: Leaving directory `/home/manatails/gsmc/lcr'
> make: *** [all] Error 2



From admin at manateeshome.com  Sun Nov 11 17:00:49 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Mon, 12 Nov 2012 02:00:49 +0900
Subject: ChanModify
In-Reply-To: <20121111163008.GJ17503@xiaoyu.lan>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
Message-ID: <11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>

I am using the latest git for LCR
And Asterisk 1.6.2.9 for Debian

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Monday, November 12, 2012 1:30 AM
To: Pierre Kim
Cc: openbsc at lists.osmocom.org
Subject: Re: ChanModify

On Sun, Nov 11, 2012 at 11:17:58PM +0900, Pierre Kim wrote:

Hi,

> Hmm, I am trying to build lcr from your git repo.
> But it seems to be broken

I think you need to take it up with Andreas but please include the version
of LCR and Asterisk you are compiling against.

holger

> chan_lcr.c:701:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING 
> PROBLEM
> chan_lcr.c: In function 'lcr_in_setup':
> chan_lcr.c:950: error: 'struct ast_channel' has no member named 
> 'redirecting'
> chan_lcr.c:951: error: 'struct ast_channel' has no member named 'caller'
> chan_lcr.c: In function 'lcr_request':
> chan_lcr.c:2145: error: 'requestor' undeclared (first use in this 
> function)
> chan_lcr.c:2145: error: (Each undeclared identifier is reported only 
> once
> chan_lcr.c:2145: error: for each function it appears in.)
> make[1]: *** [chan_lcr.po] Error 1
> make[1]: Leaving directory `/home/manatails/gsmc/lcr'
> make: *** [all] Error 2






From andreas at eversberg.eu  Sun Nov 11 17:11:27 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Sun, 11 Nov 2012 18:11:27 +0100
Subject: ChanModify
In-Reply-To: <11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
Message-ID: <509FDC3F.4010908@eversberg.eu>

Pierre Kim wrote:
> I am using the latest git for LCR
> And Asterisk 1.6.2.9 for Debian
hi pierre,

could you try jolly/new branch of lcr? it will be more convenient and 
should have this bug fixed. (iirc) also it does not rely on mISDN 
anymore, if you just want to interface gsm with asterisk or gsm with sip.

regards,

andreas




From admin at manateeshome.com  Sun Nov 11 17:18:29 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Mon, 12 Nov 2012 02:18:29 +0900
Subject: ChanModify
In-Reply-To: <509FDC3F.4010908@eversberg.eu>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
Message-ID: <11ce01cdc030$95967080$c0c35180$@manateeshome.com>

This is what I get when I try to compile on jolly/new

chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
chan_lcr.c: In function 'lcr_read':
chan_lcr.c:2901: error: request for member 'integer' in something not a
structure or union
make[1]: *** [chan_lcr.po] Error 1

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Monday, November 12, 2012 2:11 AM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc at lists.osmocom.org
Subject: Re: ChanModify

Pierre Kim wrote:
> I am using the latest git for LCR
> And Asterisk 1.6.2.9 for Debian
hi pierre,

could you try jolly/new branch of lcr? it will be more convenient and should
have this bug fixed. (iirc) also it does not rely on mISDN anymore, if you
just want to interface gsm with asterisk or gsm with sip.

regards,

andreas







From andreas at eversberg.eu  Tue Nov 13 11:52:17 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Tue, 13 Nov 2012 12:52:17 +0100
Subject: ChanModify
In-Reply-To: <11ce01cdc030$95967080$c0c35180$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
Message-ID: <50A23471.3020406@eversberg.eu>

Pierre Kim wrote:
> This is what I get when I try to compile on jolly/new
>
> chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
> chan_lcr.c: In function 'lcr_read':
> chan_lcr.c:2901: error: request for member 'integer' in something not a
> structure or union
> make[1]: *** [chan_lcr.po] Error 1

hi pierre,

can you try this patch? if it works, let me know.


regards,

andreas




From admin at manateeshome.com  Tue Nov 13 12:08:29 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Tue, 13 Nov 2012 21:08:29 +0900
Subject: ChanModify
In-Reply-To: <50A23471.3020406@eversberg.eu>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
Message-ID: <12da01cdc197$9edd7b30$dc987190$@manateeshome.com>

Um... I think you forgot to attach the patch file?

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Tuesday, November 13, 2012 8:52 PM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc at lists.osmocom.org
Subject: Re: ChanModify

Pierre Kim wrote:
> This is what I get when I try to compile on jolly/new
>
> chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING 
> PROBLEM
> chan_lcr.c: In function 'lcr_read':
> chan_lcr.c:2901: error: request for member 'integer' in something not 
> a structure or union
> make[1]: *** [chan_lcr.po] Error 1

hi pierre,

can you try this patch? if it works, let me know.


regards,

andreas







From andreas at eversberg.eu  Tue Nov 13 14:12:17 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Tue, 13 Nov 2012 15:12:17 +0100
Subject: ChanModify
In-Reply-To: <12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
Message-ID: <50A25541.5080400@eversberg.eu>

Pierre Kim wrote:
> Um... I think you forgot to attach the patch file?
>
> -----Original Message-----
> From: openbsc-bounces at lists.osmocom.org
> [mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Andreas Eversberg
> Sent: Tuesday, November 13, 2012 8:52 PM
> To: Pierre Kim
> Cc: 'Holger Hans Peter Freyther'; openbsc at lists.osmocom.org
> Subject: Re: ChanModify
>
> Pierre Kim wrote:
>> This is what I get when I try to compile on jolly/new
>>
>> chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING
>> PROBLEM
>> chan_lcr.c: In function 'lcr_read':
>> chan_lcr.c:2901: error: request for member 'integer' in something not
>> a structure or union
>> make[1]: *** [chan_lcr.po] Error 1
> hi pierre,
>
> can you try this patch? if it works, let me know.
>
>
> regards,
>
> andreas
>
>
>
sorry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: try_chan_lcr_compiler_fix.patch
Type: text/x-patch
Size: 534 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121113/8602f83f/attachment.bin>

From admin at manateeshome.com  Tue Nov 13 16:29:56 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Wed, 14 Nov 2012 01:29:56 +0900
Subject: ChanModify
In-Reply-To: <50A25541.5080400@eversberg.eu>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
Message-ID: <12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>

Hello,
Your patched worked, now I can compile LCR without getting any errors.
However, this error still persists:

<000b> bsc_api.c:374 Sending ChanModify for speech 0 1
<000b> bsc_api.c:118 Using non speech mode: 0
<000b> osmo_msc.c:73 Assignment complete should not have been reached.

I still think OpenBSC itself causes this problem as it is the only thing
I've changed.
Any ideas?

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Tuesday, November 13, 2012 11:12 PM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc at lists.osmocom.org
Subject: Re: ChanModify

Pierre Kim wrote:
> Um... I think you forgot to attach the patch file?
>
> -----Original Message-----
> From: openbsc-bounces at lists.osmocom.org 
> [mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Andreas 
> Eversberg
> Sent: Tuesday, November 13, 2012 8:52 PM
> To: Pierre Kim
> Cc: 'Holger Hans Peter Freyther'; openbsc at lists.osmocom.org
> Subject: Re: ChanModify
>
> Pierre Kim wrote:
>> This is what I get when I try to compile on jolly/new
>>
>> chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING 
>> PROBLEM
>> chan_lcr.c: In function 'lcr_read':
>> chan_lcr.c:2901: error: request for member 'integer' in something not 
>> a structure or union
>> make[1]: *** [chan_lcr.po] Error 1
> hi pierre,
>
> can you try this patch? if it works, let me know.
>
>
> regards,
>
> andreas
>
>
>
sorry





From holger at freyther.de  Tue Nov 13 19:31:44 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 13 Nov 2012 20:31:44 +0100
Subject: ChanModify
In-Reply-To: <12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
References: <20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
	<12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
Message-ID: <20121113193144.GK25669@xiaoyu.lan>

On Wed, Nov 14, 2012 at 01:29:56AM +0900, Pierre Kim wrote:

Dear Pierre, Andreas,

please cherry-pick my four patches from the holger/cleaning-rebased
branch. This will make sure that both LCR and OpenBSC agree on the
size of structures for MNCC and offsets inside these structs. If this
code does not detect a mismatch we can continue from there.




From andreas at eversberg.eu  Tue Nov 13 21:10:11 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Tue, 13 Nov 2012 22:10:11 +0100
Subject: ChanModify
In-Reply-To: <20121113193144.GK25669@xiaoyu.lan>
References: <20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
	<12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
	<20121113193144.GK25669@xiaoyu.lan>
Message-ID: <50A2B733.9070705@eversberg.eu>

Holger Hans Peter Freyther wrote:
> On Wed, Nov 14, 2012 at 01:29:56AM +0900, Pierre Kim wrote:
>
> Dear Pierre, Andreas,
>
> please cherry-pick my four patches from the holger/cleaning-rebased
> branch. This will make sure that both LCR and OpenBSC agree on the
> size of structures for MNCC and offsets inside these structs. If this
> code does not detect a mismatch we can continue from there.
hi holger,

i will try to set up my bs11 with all the latest git sources tomorrow. 
then i will look at the chan modify issue.

regards,

andreas




From andreas at eversberg.eu  Wed Nov 14 10:05:53 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Wed, 14 Nov 2012 11:05:53 +0100
Subject: ChanModify
In-Reply-To: <50A2B733.9070705@eversberg.eu>
References: <20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
	<12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
	<20121113193144.GK25669@xiaoyu.lan> <50A2B733.9070705@eversberg.eu>
Message-ID: <50A36D01.2020001@eversberg.eu>


> hi holger,
>
> i will try to set up my bs11 with all the latest git sources tomorrow. 
> then i will look at the chan modify issue.
>
> regards,
>
> andreas
>
hi,

just tested and fixed lcr/new branch. it works now with master branch of 
openbsc. indeed it is quite a good idea to check version/sizeo of MNCC 
interface.

regards,

andreas




From holger at freyther.de  Wed Nov 14 15:29:32 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 14 Nov 2012 16:29:32 +0100
Subject: ChanModify
In-Reply-To: <50A36D01.2020001@eversberg.eu>
References: <11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
	<12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
	<20121113193144.GK25669@xiaoyu.lan> <50A2B733.9070705@eversberg.eu>
	<50A36D01.2020001@eversberg.eu>
Message-ID: <20121114152932.GK28837@xiaoyu.lan>

On Wed, Nov 14, 2012 at 11:05:53AM +0100, Andreas Eversberg wrote:
> just tested and fixed lcr/new branch. it works now with master
> branch of openbsc. indeed it is quite a good idea to check
> version/sizeo of MNCC interface.

Shall I rebase the LCR/MNCC patches for lcr/new? Do you advise to
use lcr/new to connect with the EventPhone at the 29C3?

holger




From andreas at eversberg.eu  Wed Nov 14 18:13:01 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Wed, 14 Nov 2012 19:13:01 +0100
Subject: ChanModify
In-Reply-To: <20121114152932.GK28837@xiaoyu.lan>
References: <11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
	<11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
	<12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
	<20121113193144.GK25669@xiaoyu.lan>
	<50A2B733.9070705@eversberg.eu> <50A36D01.2020001@eversberg.eu>
	<20121114152932.GK28837@xiaoyu.lan>
Message-ID: <50A3DF2D.50404@eversberg.eu>

Holger Hans Peter Freyther wrote:
> Shall I rebase the LCR/MNCC patches for lcr/new? Do you advise to
> use lcr/new to connect with the EventPhone at the 29C3?
hi holger,

yes i do, because jolly/new has improved audio handling. 
bridging/conferencing is not done via mISDN only, but also inside lcr. 
this way it is not required to use isdn loop interfaces to connect 
chan_lcr, sip, isdn and gsm together. it is now routed inside lcr. for 
all interfaces except isdn, you don't need mISDN at all. (if you diff 
between master and jolly/new, you might get scared.)

we can use a sip trunk to eventphone and an isdn trunk. we could use 
(for a test) isdn for two days and sip the other two days.

regards,

andreas





From holger at freyther.de  Wed Nov 14 18:17:19 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 14 Nov 2012 19:17:19 +0100
Subject: ChanModify
In-Reply-To: <50A3DF2D.50404@eversberg.eu>
References: <11ce01cdc030$95967080$c0c35180$@manateeshome.com>
	<50A23471.3020406@eversberg.eu>
	<12da01cdc197$9edd7b30$dc987190$@manateeshome.com>
	<50A25541.5080400@eversberg.eu>
	<12eb01cdc1bc$237f4c50$6a7de4f0$@manateeshome.com>
	<20121113193144.GK25669@xiaoyu.lan> <50A2B733.9070705@eversberg.eu>
	<50A36D01.2020001@eversberg.eu> <20121114152932.GK28837@xiaoyu.lan>
	<50A3DF2D.50404@eversberg.eu>
Message-ID: <20121114181719.GH7733@xiaoyu.lan>

On Wed, Nov 14, 2012 at 07:13:01PM +0100, Andreas Eversberg wrote:
> Holger Hans Peter Freyther wrote:
> 
> we can use a sip trunk to eventphone and an isdn trunk. we could use
> (for a test) isdn for two days and sip the other two days.

ah great. At the 28C3 we used the E1/ISDN over IP option in mISDN and
I would assume we do something like this again.

holger



From admin at manateeshome.com  Mon Nov 12 16:55:36 2012
From: admin at manateeshome.com (Pierre Kim)
Date: Tue, 13 Nov 2012 01:55:36 +0900
Subject: ChanModify
In-Reply-To: <509FDC3F.4010908@eversberg.eu>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
	<20121111081743.GB16766@xiaoyu.lan>
	<11b001cdbff5$5dd1b690$197523b0$@manateeshome.com>
	<20121111103300.GE10708@xiaoyu.lan>
	<11bd01cdc002$d3bcb640$7b3622c0$@manateeshome.com>
	<20121111123650.GC17503@xiaoyu.lan>
	<11ca01cdc017$5f0f9550$1d2ebff0$@manateeshome.com>
	<20121111163008.GJ17503@xiaoyu.lan>
	<11cc01cdc02e$1e769950$5b63cbf0$@manateeshome.com>
	<509FDC3F.4010908@eversberg.eu>
Message-ID: <128f01cdc0f6$903b36e0$b0b1a4a0$@manateeshome.com>

Could you tell me what version of asterisk do I have to have in order to
compile LCR successfully?

-----Original Message-----
From: openbsc-bounces at lists.osmocom.org
[mailto:openbsc-bounces at lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Monday, November 12, 2012 2:11 AM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc at lists.osmocom.org
Subject: Re: ChanModify

Pierre Kim wrote:
> I am using the latest git for LCR
> And Asterisk 1.6.2.9 for Debian
hi pierre,

could you try jolly/new branch of lcr? it will be more convenient and should
have this bug fixed. (iirc) also it does not rely on mISDN anymore, if you
just want to interface gsm with asterisk or gsm with sip.

regards,

andreas







From holger at freyther.de  Sun Nov 11 08:25:17 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 09:25:17 +0100
Subject: ChanModify
In-Reply-To: <115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
References: <113301cdbf2e$de46dfc0$9ad49f40$@manateeshome.com>
	<20121110182848.GA16766@xiaoyu.lan>
	<115201cdbf7a$90dde930$b299bb90$@manateeshome.com>
Message-ID: <20121111082517.GC16766@xiaoyu.lan>

On Sun, Nov 11, 2012 at 04:35:37AM +0900, Pierre Kim wrote:
> Here is the pcap file

Hi,

on top of the invocation please attach your configuration file as well. On
a quick look I didn't see any IPA CRCX/MDCX/DLCX. Do you see it?

holger



From holger at freyther.de  Sun Nov 11 10:43:31 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 11 Nov 2012 11:43:31 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
Message-ID: <20121111104331.GA17503@xiaoyu.lan>

Hi all,

I have rebased jolly/sms and split it up (first use the routines that were
moved to libosmocore and that create compile errors, then begin to use the
DLSMS debug area, then the actual patches in a way that all of them compile
to allow to bisect them). I am now manually testing them with the help of
the sysmocom modem bank.

There are various issues that needs to be resolved before the 29C3 to be
able to use the code. I am just listing them here for reference.

There is a double trans_free in the new code now that will lead to segfaults
and various 'soft' failures. I am just including some log messages:

gsm0411_smc.c:308 Cannot release yet current state: WAIT_CP_ACK
gsm0411_smc.c:511 Message 0x332/1 unhandled at this state WAIT_CP_ACK.
gsm0411_smc.c:517 RX Unimplemented CP msg_type: 0x332
gsm0411_smc.c:134 TX CP-ERROR, cause 97 (Message Type doesn't exist)
gsm_04_11.c:913 Transaction contains SMS.
gsm_04_11.c:441 RP-DATA (MO) without DST or TPDU ?!?
gsm_04_11.c:420 TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information)

cheers
	holger





From holger at freyther.de  Mon Nov 12 18:11:43 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 12 Nov 2012 19:11:43 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <20121111104331.GA17503@xiaoyu.lan>
References: <20121111104331.GA17503@xiaoyu.lan>
Message-ID: <20121112181143.GI31742@xiaoyu.lan>

On Sun, Nov 11, 2012 at 11:43:31AM +0100, Holger Hans Peter Freyther wrote:
> Hi all,

Hi again,

> gsm0411_smc.c:308 Cannot release yet current state: WAIT_CP_ACK
> gsm0411_smc.c:511 Message 0x332/1 unhandled at this state WAIT_CP_ACK.
> gsm0411_smc.c:517 RX Unimplemented CP msg_type: 0x332
> gsm0411_smc.c:134 TX CP-ERROR, cause 97 (Message Type doesn't exist)
> gsm_04_11.c:913 Transaction contains SMS.
> gsm_04_11.c:441 RP-DATA (MO) without DST or TPDU ?!?
> gsm_04_11.c:420 TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information)

I am now rebasing and start with testing just the SMC rework and I have seen
a crash in the cp_timer_expired routine (NULL pointer + small offset). I have
not seen how this can happen because the smc instance should be cleared at the
end of an instance.. I will continue to test with the modem bank and improve
the debugging (sadly an ABI incompatible change to the SMC/SMR structure).

holger



From 246tnt at gmail.com  Mon Nov 12 21:05:07 2012
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 12 Nov 2012 22:05:07 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <20121112181143.GI31742@xiaoyu.lan>
References: <20121111104331.GA17503@xiaoyu.lan>
	<20121112181143.GI31742@xiaoyu.lan>
Message-ID: <CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>

Hi,

> I am now rebasing and start with testing just the SMC rework and I have seen
> a crash in the cp_timer_expired routine (NULL pointer + small offset). I have
> not seen how this can happen because the smc instance should be cleared at the
> end of an instance.. I will continue to test with the modem bank and improve
> the debugging (sadly an ABI incompatible change to the SMC/SMR structure).

btw, how easy are those to reproduce ?

Do you need an automated setup or just sending a couple SMS using a
phone can trigger them ?

Cheers,

    Sylvain



From alexander.chemeris at gmail.com  Mon Nov 12 21:50:22 2012
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Tue, 13 Nov 2012 01:50:22 +0400
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
References: <20121111104331.GA17503@xiaoyu.lan>
	<20121112181143.GI31742@xiaoyu.lan>
	<CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
Message-ID: <CABmJbFWbVbqZHkpJD4t9W4uAQ+ZbYsqD7=hdSCWAdc1d17iKwg@mail.gmail.com>

Sylvain,

On Tue, Nov 13, 2012 at 1:05 AM, Sylvain Munaut <246tnt at gmail.com> wrote:
>> I am now rebasing and start with testing just the SMC rework and I have seen
>> a crash in the cp_timer_expired routine (NULL pointer + small offset). I have
>> not seen how this can happen because the smc instance should be cleared at the
>> end of an instance.. I will continue to test with the modem bank and improve
>> the debugging (sadly an ABI incompatible change to the SMC/SMR structure).
>
> btw, how easy are those to reproduce ?
>
> Do you need an automated setup or just sending a couple SMS using a
> phone can trigger them ?

Let me know if you need access to a setup with nanoBTS + sysmocom
modem bank. I'll connect everything and give you access to our
OpenVPN. We use our demo server to test OpenBTS, but it's idling most
of the time anyway.

PS I'm happy to share our test setup with other well known developers
as well. Feel free to contact me.

--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From holger at freyther.de  Mon Nov 12 22:54:40 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 12 Nov 2012 23:54:40 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
References: <20121111104331.GA17503@xiaoyu.lan>
	<20121112181143.GI31742@xiaoyu.lan>
	<CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
Message-ID: <20121112225440.GM31742@xiaoyu.lan>

On Mon, Nov 12, 2012 at 10:05:07PM +0100, Sylvain Munaut wrote:
> Hi,
> 
> > I am now rebasing and start with testing just the SMC rework and I have seen
> > a crash in the cp_timer_expired routine (NULL pointer + small offset). I have
> > not seen how this can happen because the smc instance should be cleared at the
> > end of an instance.. I will continue to test with the modem bank and improve
> > the debugging (sadly an ABI incompatible change to the SMC/SMR structure).
> 
> btw, how easy are those to reproduce ?

the crash with the entire patch set is 'easy' to reproduce. I have four devices
that SMS to each other but I am confident that only two can cause the same crash.

the cp_timer_expired is more difficult to reproduce but I think I know how it
can happen.

1.) cp_timer expired..
2.)
    nmsg = gsm411_msgb_alloc();
    inst->mn_recv(inst, GSM411_MNSMS_ERROR_IND, nmsg);
    msgb_free(nmsg);
3.) 
        case GSM411_MNSMS_ERROR_IND:
                if (gh)
                        DEBUGP(DLSMS, "MNSMS-ERROR-IND, cause %d (%s)\n",
                                gh->data[0],
                                get_value_string(gsm411_cp_cause_strs,
                                gh->data[0]));
                else
                        DEBUGP(DLSMS, "MNSMS-ERROR-IND, no cause\n");
                trans_free(trans);

at this point the smc is gone... so thanks for asking to make me reflect on the
crash. I wonder if I shouldn't just put the smc/smr patch together and debug the
result.

 

> 
> Do you need an automated setup or just sending a couple SMS using a
> phone can trigger them ?

I think it helps that the Wavecom module of our modem bank is generally not happy
with our SMS protocol handling and I end up in all the error paths.



From holger at freyther.de  Tue Nov 13 21:47:40 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 13 Nov 2012 22:47:40 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <20121112225440.GM31742@xiaoyu.lan>
References: <20121111104331.GA17503@xiaoyu.lan>
	<20121112181143.GI31742@xiaoyu.lan>
	<CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
	<20121112225440.GM31742@xiaoyu.lan>
Message-ID: <20121113214740.GD28837@xiaoyu.lan>

On Mon, Nov 12, 2012 at 11:54:40PM +0100, Holger Hans Peter Freyther wrote:

Hi,

> the cp_timer_expired is more difficult to reproduce but I think I know how it
> can happen.

zecke/smc-issues contains a testcase (that is crashing). Ideas how to resolve
the issue and checking where similar issues exist and resolve them too (e.g.
leading to a double free in the smr code).

holger




From holger at freyther.de  Wed Nov 14 07:01:38 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 14 Nov 2012 08:01:38 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <20121113214740.GD28837@xiaoyu.lan>
References: <20121111104331.GA17503@xiaoyu.lan>
	<20121112181143.GI31742@xiaoyu.lan>
	<CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
	<20121112225440.GM31742@xiaoyu.lan>
	<20121113214740.GD28837@xiaoyu.lan>
Message-ID: <20121114070138.GG28837@xiaoyu.lan>

On Tue, Nov 13, 2012 at 10:47:40PM +0100, Holger Hans Peter Freyther wrote:
Hi Andreas,

> zecke/smc-issues contains a testcase (that is crashing). Ideas how to resolve
> the issue and checking where similar issues exist and resolve them too (e.g.
> leading to a double free in the smr code).

and the same issue exists with the SMR rp_timer_expired and the OpenBSC code
calling trans_free from within the error indication and then another message
is received (and the msg is empty but the client code still casts it to a msg).

there is another part I don't fully understand:
 * gsm411_rx_rp_ack will start a new transaction but not trans_free the old
   one.
 * gsm0411_rcv_sms will search for a 'pending' transaction and then free it.

are these two supposed to work together? When was this tested the last time?

holger

> 
> 



From holger at freyther.de  Thu Nov 15 19:16:26 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 15 Nov 2012 20:16:26 +0100
Subject: FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
In-Reply-To: <20121113214740.GD28837@xiaoyu.lan>
References: <20121111104331.GA17503@xiaoyu.lan>
	<20121112181143.GI31742@xiaoyu.lan>
	<CAHL+j09Fck25CFvghpm290hrzK78=trMB0hynPS43w4p3WNqVw@mail.gmail.com>
	<20121112225440.GM31742@xiaoyu.lan>
	<20121113214740.GD28837@xiaoyu.lan>
Message-ID: <20121115191626.GP7733@xiaoyu.lan>

On Tue, Nov 13, 2012 at 10:47:40PM +0100, Holger Hans Peter Freyther wrote:

Hi,


> zecke/smc-issues contains a testcase (that is crashing). Ideas how to resolve
> the issue and checking where similar issues exist and resolve them too (e.g.
> leading to a double free in the smr code).

after re-reading GSM 04.11 on my train trip I believe the only valid place to
delete the transaction is either on RF failure or once the SMC entity is sending
the RELEASE REQUEST to the lower service.

Andreas can you confirm that? It is certainly wrong to delete/destroy the SMC
entity from within any 'error' handler.

holger
> 



From axel at walsleben.info  Tue Nov 13 18:02:20 2012
From: axel at walsleben.info (Axel Walsleben)
Date: Tue, 13 Nov 2012 19:02:20 +0100
Subject: nanoBTS for sell
Message-ID: <50A28B2C.5070508@walsleben.info>

I am selling my nanoBTS EGSM900 / 165CU.
one is on Ebay item number: 150946617641, i also have a second one, same 
technical specs.




From hwit at a-domani.nl  Tue Nov 13 18:51:46 2012
From: hwit at a-domani.nl (Hans Witvliet)
Date: Tue, 13 Nov 2012 19:51:46 +0100
Subject: G4
Message-ID: <1352832706.4254.3.camel@t43.lan0.a-domani.nl>

Hi all,

I've been hearing all sorts of rumours about nano- pico- or femto-cells
for sale in California, around $99 capable of G4/LTE.

Does anybody know if that is fact-or-fiction?

If true, might that be something for openbsc?

Hans.




From stuart at bluewave.im  Thu Nov 15 15:48:28 2012
From: stuart at bluewave.im (Stuart Baggs)
Date: Thu, 15 Nov 2012 15:48:28 +0000
Subject: 2 x nanoBTS model 139 Available
Message-ID: <FB1C25CF-FD8C-40E4-AF65-CA7970A08ED1@bluewave.im>

Hi All

We've upgraded a couple of our cells to model 165Gs and have the older model 139s we've removed available for sale. They're both in perfect working order and have been used with OpenBSC for a year now.

Thanks


From andreas at eversberg.eu  Thu Nov 15 17:12:01 2012
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Thu, 15 Nov 2012 18:12:01 +0100
Subject: gsm and isdn at 29c3
Message-ID: <50A52261.6080008@eversberg.eu>

hi list,

we (ccc meber and me) are trying to get a pri access line (primary rate 
isdn) this year. it will provide external connection for the poc 
(eventphone) and will also allow interconnection of gsm network with the 
rest of the world. it is not yet clear if we get this line, but we are 
working on it. the hardware and software side is already tested in our 
"labs".

for connection between poc and gsm network (openbsc), we like to use lcr 
(linux-call-router via mncc interface). there are two ways to connect to 
eventphone, one via isdn line (or virtual isdn over ip) and another one 
via sip trunk. we like to use both ways for better testing.

the registration process for gsm extensions is already set up by 
evenphone. visit https://www.eventphone.de to register your gsm 
extension. for syncing eventphone's database with hlr of openbsc, i can 
provide help. also i will provide helpdesk for gsm questions this year 
again.

regards,

andreas




From laforge at gnumonks.org  Fri Nov 16 21:37:56 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 16 Nov 2012 22:37:56 +0100
Subject: SMPP 3.4 interface in OsmoNITB
Message-ID: <20121116213756.GO30012@prithivi.gnumonks.org>

Hi all,

in case you follow the changelog, you will already have seen this
coming: OsmoNITB now has a SMPP interface for submitting MT-SMS.

This is by no means some kind of competition to a more complete SMSC
developed by other people on this list, but it was a quick solution to
a requirement of a commercial user.

You can use it to submit SMS identifying the recipient subscriber either
by his extension or his IMSI.  OsmoNITB will also send SMPP ALERT
NOTIFICATION in case a previously detached subscriber comes online
again.  Contrary to the spec, you don't have to subscribe ot ALERT
NOTIFICATIONS, but they will be sent to all ESME's registered.

The SMPP interface supports both store-and-forward (via database) as
well as forward/transactoin mdoe, where the SMS is attempted for
immediate delivery, not buffered and will only send a positive SUBMIT-SM
result in case it was acknowledged by the MS.

You can submit both GSM charset as well as binary messages.  UCS2 is not
tested.  multi-part SMS (or anything else using UDH) only works with
binary SMS at this point, i.e. GSM alphabet encoded multi-part messages
are broken.

The interface will soon be extended to also cover MO-SMS, where you
would configure a given destination address by VTY and then messages to
that address would be forwarded to the ESME.

Only SMPP 3.4 is currently supported.  You will need libsmpp34 from
git://git.osmocom.org/libsmpp34.git and need to build openbsc with
'--enable-smpp'

Regards,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From akibsayyed at gmail.com  Sun Nov 18 07:53:54 2012
From: akibsayyed at gmail.com (Akib Sayyed)
Date: Sun, 18 Nov 2012 10:53:54 +0300
Subject: Need to buy osmo-NITB
Message-ID: <CAMG-S90jQNnN++4+pnG4gMJZk6udZ2QsDCiV6Rr2jfLSL6SQRA@mail.gmail.com>

Hey guys i wanted to buy Osmo -NITB is it on sale ??
please let me know

-- 
Akib Sayyed
Matrix-Shell
akibsayyed at gmail.com
akibsayyed at matrixshell.com
Mob:- +91-966-514-2243
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121118/79a4896f/attachment.htm>

From holger at freyther.de  Sun Nov 18 09:21:36 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 18 Nov 2012 10:21:36 +0100
Subject: Need to buy osmo-NITB
In-Reply-To: <CAMG-S90jQNnN++4+pnG4gMJZk6udZ2QsDCiV6Rr2jfLSL6SQRA@mail.gmail.com>
References: <CAMG-S90jQNnN++4+pnG4gMJZk6udZ2QsDCiV6Rr2jfLSL6SQRA@mail.gmail.com>
Message-ID: <20121118092136.GN26426@xiaoyu.lan>

On Sun, Nov 18, 2012 at 10:53:54AM +0300, Akib Sayyed wrote:

Hi,

> Hey guys i wanted to buy Osmo -NITB is it on sale ??
> please let me know

OpenBSC is licensed under AGPLv3+. If that doesn't mean anything to you
please take a look here[1] and here[2].

holger

[1] http://simple.wikipedia.org/wiki/Free_software
[2] http://www.fsf.org/



From akibsayyed at gmail.com  Sun Nov 18 09:32:11 2012
From: akibsayyed at gmail.com (Akib Sayyed)
Date: Sun, 18 Nov 2012 12:32:11 +0300
Subject: Need to buy osmo-NITB
In-Reply-To: <20121118092136.GN26426@xiaoyu.lan>
References: <CAMG-S90jQNnN++4+pnG4gMJZk6udZ2QsDCiV6Rr2jfLSL6SQRA@mail.gmail.com>
	<20121118092136.GN26426@xiaoyu.lan>
Message-ID: <CAMG-S90LtjfpXif+CFcOvkkDsNnG31T=P50tFLOgFeufc8JLMQ@mail.gmail.com>

I meant to buy appliance  which is in product list of sysmocom with picture
not openbsc.cause its really a headache to carry laptop all the time.

my understanding is :Osmonitb is a appliance with openbsc installed in it.

please correct me if i am wrong

and i do respect licenses like GPL and AGPL.


On Sun, Nov 18, 2012 at 12:21 PM, Holger Hans Peter Freyther <
holger at freyther.de> wrote:

> On Sun, Nov 18, 2012 at 10:53:54AM +0300, Akib Sayyed wrote:
>
> Hi,
>
> > Hey guys i wanted to buy Osmo -NITB is it on sale ??
> > please let me know
>
> OpenBSC is licensed under AGPLv3+. If that doesn't mean anything to you
> please take a look here[1] and here[2].
>
> holger
>
> [1] http://simple.wikipedia.org/wiki/Free_software
> [2] http://www.fsf.org/
>



-- 
Akib Sayyed
Matrix-Shell
akibsayyed at gmail.com
akibsayyed at matrixshell.com
Mob:- +91-966-514-2243
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121118/95bd6449/attachment.htm>

From laforge at gnumonks.org  Sun Nov 18 10:58:54 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 18 Nov 2012 11:58:54 +0100
Subject: Need to buy osmo-NITB
In-Reply-To: <CAMG-S90LtjfpXif+CFcOvkkDsNnG31T=P50tFLOgFeufc8JLMQ@mail.gmail.com>
References: <CAMG-S90jQNnN++4+pnG4gMJZk6udZ2QsDCiV6Rr2jfLSL6SQRA@mail.gmail.com>
	<20121118092136.GN26426@xiaoyu.lan>
	<CAMG-S90LtjfpXif+CFcOvkkDsNnG31T=P50tFLOgFeufc8JLMQ@mail.gmail.com>
Message-ID: <20121118105854.GN8595@prithivi.gnumonks.org>

Hi Akib,

just a bit of clarification on terms:

On Sun, Nov 18, 2012 at 12:32:11PM +0300, Akib Sayyed wrote:
> my understanding is :Osmonitb is a appliance with openbsc installed in it.

OsmoNITB is one of the two version of OpenBSC, i.e. it is the free
software program.

sysmocom is selling some products which have OsmoNITB pre-installed,
this includes the sysmoBTS in NITB configuration, and the sysmoBSC/IP or
sysmoBSC/E1 hardware appliances.

As your inquiry relates to the latter, we whould handle this off-list,
as the list is for the free software program/project, and not the
sysmocom products built from it.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From akibsayyed at gmail.com  Sun Nov 18 11:53:44 2012
From: akibsayyed at gmail.com (Akib Sayyed)
Date: Sun, 18 Nov 2012 14:53:44 +0300
Subject: Need to buy osmo-NITB
In-Reply-To: <20121118105854.GN8595@prithivi.gnumonks.org>
References: <CAMG-S90jQNnN++4+pnG4gMJZk6udZ2QsDCiV6Rr2jfLSL6SQRA@mail.gmail.com>
	<20121118092136.GN26426@xiaoyu.lan>
	<CAMG-S90LtjfpXif+CFcOvkkDsNnG31T=P50tFLOgFeufc8JLMQ@mail.gmail.com>
	<20121118105854.GN8595@prithivi.gnumonks.org>
Message-ID: <CAMG-S939aZbq9aAxE=Sz+Np==43pEQKQjrS3s+JGcxD7-2Gjdg@mail.gmail.com>

Thank you All
I did sent mail regarding sysmocom products.
just waiting for reply


On Sun, Nov 18, 2012 at 1:58 PM, Harald Welte <laforge at gnumonks.org> wrote:

> Hi Akib,
>
> just a bit of clarification on terms:
>
> On Sun, Nov 18, 2012 at 12:32:11PM +0300, Akib Sayyed wrote:
> > my understanding is :Osmonitb is a appliance with openbsc installed in
> it.
>
> OsmoNITB is one of the two version of OpenBSC, i.e. it is the free
> software program.
>
> sysmocom is selling some products which have OsmoNITB pre-installed,
> this includes the sysmoBTS in NITB configuration, and the sysmoBSC/IP or
> sysmoBSC/E1 hardware appliances.
>
> As your inquiry relates to the latter, we whould handle this off-list,
> as the list is for the free software program/project, and not the
> sysmocom products built from it.
>
> Regards,
>         Harald
> --
> - Harald Welte <laforge at gnumonks.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                   (ETSI EN 300 175-7 Ch.
> A6)
>



-- 
Akib Sayyed
Matrix-Shell
akibsayyed at gmail.com
akibsayyed at matrixshell.com
Mob:- +91-966-514-2243
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121118/10d19986/attachment.htm>

From yannm1 at hotmail.com  Thu Nov 22 14:12:32 2012
From: yannm1 at hotmail.com (Yann R. Moupinda)
Date: Thu, 22 Nov 2012 15:12:32 +0100
Subject: triplets calculation
Message-ID: <DUB119-W3465906EC2C8E34BA2DC568B5B0@phx.gbl>


Hi guys,

i'm still testing the eap-sim authentication and lately i got acceptable results using 
a simple flat file containing the triplets of specific SIM cards. Next step will be to 
enable the external radius server to use the sysmoBTS database hlr.sqlite3, so the 
OpenBSC users  (Users using the OpenBSC-GSM Network) can automatically access
to the internet.

i just want to ask if there are any limitations with the sysmocom SIM cards?
 In fact, i noticed that by using the sysmocom sim cards, the eap-sim authentication
failed when the RAND values strong randomly chosen were, e.g
 046DBA898016454aB3920C58180DA2F5 or e177842fe16c47de84784be1b4141c27. 
But when i chose a RAND like this 10101010101010101010101010101010,
0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F or 00000000000000000000000000000000,
the authentication succeeded.

By using an other sim (not from sysmocom) with the same strong and weak RAND
values the authentication always succeeded.

Why does the authentication succeed buy using sysmocom sim card with weak RAND
(10101010101010101010101010101010) and fail by using strong RAND values
(e177842fe16c47de84784be1b4141c27) ?

best regards

Yann
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121122/ee372726/attachment.htm>

From holger at freyther.de  Thu Nov 22 18:13:23 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 22 Nov 2012 19:13:23 +0100
Subject: triplets calculation
In-Reply-To: <DUB119-W3465906EC2C8E34BA2DC568B5B0@phx.gbl>
References: <DUB119-W3465906EC2C8E34BA2DC568B5B0@phx.gbl>
Message-ID: <20121122181323.GE25233@xiaoyu.lan>

On Thu, Nov 22, 2012 at 03:12:32PM +0100, Yann R. Moupinda wrote:
> 
> Hi guys,

Hi,


> Why does the authentication succeed buy using sysmocom sim card with weak RAND
> (10101010101010101010101010101010) and fail by using strong RAND values
> (e177842fe16c47de84784be1b4141c27) ?

no idea, can you provide an example program (e.g. pySIM based) that illustrates
the issue?

holger



From kugghjul at gmail.com  Mon Nov 26 13:19:37 2012
From: kugghjul at gmail.com (Christoffer Jerkeby)
Date: Mon, 26 Nov 2012 14:19:37 +0100
Subject: triplets calculation
In-Reply-To: <20121122181323.GE25233@xiaoyu.lan>
References: <DUB119-W3465906EC2C8E34BA2DC568B5B0@phx.gbl>
	<20121122181323.GE25233@xiaoyu.lan>
Message-ID: <CAPvAUg+dTyDxiWHeP35waO1BRY=YX7ZjvzPL6UgaG3ZGecxSOg@mail.gmail.com>

On Thu, Nov 22, 2012 at 7:13 PM, Holger Hans Peter Freyther
<holger at freyther.de> wrote:
> On Thu, Nov 22, 2012 at 03:12:32PM +0100, Yann R. Moupinda wrote:
>>
>> Hi guys,
>
> Hi,
>
>
>> Why does the authentication succeed buy using sysmocom sim card with weak RAND
>> (10101010101010101010101010101010) and fail by using strong RAND values
>> (e177842fe16c47de84784be1b4141c27) ?
>
> no idea, can you provide an example program (e.g. pySIM based) that illustrates
> the issue?
>
> holger
>


While agreeing that you need to give an example of what goes wrong, I
happen to notice all your "bad" RAND values contains lowercase HEX
characters while your "good" ones only contains uppercase HEX
characters. I dont know if that matters in your application.

But only accepting weak keyes is not logical.

Regards Kugg



From yannm1 at hotmail.com  Tue Nov 27 12:48:12 2012
From: yannm1 at hotmail.com (Yann R. Moupinda)
Date: Tue, 27 Nov 2012 13:48:12 +0100
Subject: triplets calculation
In-Reply-To: <CAPvAUg+dTyDxiWHeP35waO1BRY=YX7ZjvzPL6UgaG3ZGecxSOg@mail.gmail.com>
References: <DUB119-W3465906EC2C8E34BA2DC568B5B0@phx.gbl>,
	<20121122181323.GE25233@xiaoyu.lan>,
	<CAPvAUg+dTyDxiWHeP35waO1BRY=YX7ZjvzPL6UgaG3ZGecxSOg@mail.gmail.com>
Message-ID: <DUB119-W129732F6B32B14EA71DB248B5E0@phx.gbl>


Hi guys,

> > no idea, can you provide an example program (e.g. pySIM based) that illustrates
> > the issue?

 
> I happen to notice all your "bad" RAND values contains lowercase HEX
> characters while your "good" ones only contains uppercase HEX
> characters. I dont know if that matters in your application.
> 
> But only accepting weak keyes is not logical.



Here the logging information from the Freeradius Server. The Client tries to authenticate using eap-sim.
In the first case, i used strong RAND values. You can see that the client didn't reply to the last eap-request
(containing the three RANDs) from Server and the authentication process broke up.
In the second case i used weak RAND and the authentication succeeded.
In both cases i used a Nokia E52 and a Laptop with a sysmocom sim card.

All RAND values included in the eap request/sim/challenge message contain lowercase HEX characters.

1st case )

Ready to process requests.

rad_recv: Access-Request packet from host 192.168.10.212 port 38803, id=29, length=238
    Service-Type = Framed-User
    Framed-MTU = 1400
    User-Name = "1901700000000654"
    NAS-Port-Id = "ap_hotspot"
    NAS-Port-Type = Wireless-802.11
    Acct-Session-Id = "8220000e"
    Acct-Multi-Session-Id = "00-0C-42-64-41-9D-A8-7E-33-3E-9C-5B-82-20-00-00-00-00-00-0E"
    Calling-Station-Id = "A8-7E-33-3E-9C-5B"
    Called-Station-Id = "00-0C-42-64-41-9D:YANN"
    EAP-Message = 0x020100150131393031373030303030303030363534
    Message-Authenticator = 0xcf4e5f6429686cc260b16bd23d82489f
    NAS-Identifier = "MT_Yann"
    NAS-IP-Address = 192.168.10.212
# Executing section authorize from file /etc/freeradius/sites-enabled/default
+- entering group authorize {...}
rlm_sim_files: authorized user/imsi 1901700000000654 
rlm_sim_files: Adding EAP-Type: eap-sim
++[sim_files] returns ok
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
++[digest] returns noop
[suffix] No '@' in User-Name = "1901700000000654", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] EAP packet type response id 1 length 21
[eap] No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[files] returns noop
++[expiration] returns noop
++[logintime] returns noop
[pap] WARNING! No "known good" password found for the user.  Authentication may fail because of this.
++[pap] returns noop
Found Auth-Type = EAP
# Executing group from file /etc/freeradius/sites-enabled/default
+- entering group authenticate {...}
[eap] EAP Identity
[eap] processing type sim
[eap] Underlying EAP-Type set EAP ID to 108
++[eap] returns handled

Sending Access-Challenge of id 29 to 192.168.10.212 port 38803
    EAP-Message = 0x016c0014120a00000f0200020001000011010100
    Message-Authenticator = 0x00000000000000000000000000000000
    State = 0x870e2a6987623891aa6e49c2b1bcc9b6
Finished request 0.
Going to the next request
Waking up in 4.9 seconds.

rad_recv: Access-Request packet from host 192.168.10.212 port 50478, id=30, length=287
    EAP-Message = 0x026c0034120a000007050000c27cfb1cfa7a257c9c89796e49bca230100100010e05001031393031373030303030303030363534
    Message-Authenticator = 0xc691af8b618d9da88f9e289557530f6f
    NAS-Identifier = "MT_Yann"
    NAS-IP-Address = 192.168.10.212
# Executing section authorize from file /etc/freeradius/sites-enabled/default
+- entering group authorize {...}
rlm_sim_files: authorized user/imsi 1901700000000654 
rlm_sim_files: Adding EAP-Type: eap-sim
++[sim_files] returns ok
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
++[digest] returns noop
[suffix] No '@' in User-Name = "1901700000000654", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] EAP packet type response id 108 length 52
[eap] No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[files] returns noop
++[expiration] returns noop
++[logintime] returns noop
[pap] WARNING! No "known good" password found for the user.  Authentication may fail because of this.
++[pap] returns noop
Found Auth-Type = EAP
# Executing group from file /etc/freeradius/sites-enabled/default
+- entering group authenticate {...}
[eap] Request found, released from the list
[eap] EAP/sim
[eap] processing type sim

[eap] Underlying EAP-Type set EAP ID to 109
++[eap] returns handled
Sending Access-Challenge of id 30 to 192.168.10.212 port 50478
    EAP-Message = 0x016d0050120b0000010d00000123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde00123456789abcdef0123456789abcd180b0500000bffb0f7777b066616d98519e625a531
    Message-Authenticator = 0x00000000000000000000000000000000
    State = 0x870e2a6986633891aa6e49c2b1bcc9b6
Finished request 1.
Going to the next request
Waking up in 4.9 seconds.
Cleaning up request 0 ID 29 with timestamp +17
Cleaning up request 1 ID 30 with timestamp +17
Ready to process requests.


2nd case )

Ready to process requests.
rad_recv: Access-Request packet from host 192.168.10.212 port 38045, id=42, length=238
    Service-Type = Framed-User
    Framed-MTU = 1400
    User-Name = "1901700000000654"
    NAS-Port-Id = "ap_hotspot"
    NAS-Port-Type = Wireless-802.11
    Acct-Session-Id = "82e0000a"
    Acct-Multi-Session-Id = "00-0C-42-64-41-9D-00-24-D7-0A-B1-2C-82-E0-00-00-00-00-00-0A"
    Calling-Station-Id = "00-24-D7-0A-B1-2C"
    Called-Station-Id = "00-0C-42-64-41-9D:YANN"
    EAP-Message = 0x020100150131393031373030303030303030363534
    Message-Authenticator = 0x6c5f2905cc845f4adc2990825cc65dc8
    NAS-Identifier = "MT_Yann"
    NAS-IP-Address = 192.168.10.212
(0) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default
(0)   group authorize {
(0)  - entering group authorize {...}
(0)   [preprocess] = ok
(0)   [chap] = noop
(0)   [auth_log] = ok
(0)   [mschap] = noop
(0)   [digest] = noop
(0) suffix : No '@' in User-Name = "1901700000000654", looking up realm NULL
(0) suffix : No such realm "NULL"
(0)   [suffix] = noop
rlm_sim_files: authorized user/imsi 1901700000000654 
rlm_sim_files: Adding EAP-Type: eap-sim
(0)   [sim_files] = ok
(0) eap : EAP packet type response id 1 length 21
(0) eap : EAP-Identity reply, returning 'ok' so we can short-circuit the rest of authorize
(0)   [eap] = ok
(0) Found Auth-Type = EAP
(0) # Executing group from file /usr/local/etc/raddb/sites-enabled/default
(0)   group authenticate {
(0)  - entering group authenticate {...}
(0) eap : EAP Identity
(0) eap : processing type sim
(0) eap : Underlying EAP-Type set EAP ID to 206
(0)   [eap] = handled
Sending Access-Challenge of id 42 to 192.168.10.212 port 38045
    EAP-Message = 0x01ce0014120a00000f0200020001000011010100
    Message-Authenticator = 0x00000000000000000000000000000000
    State = 0x27d04fcb271e5dceaedc556ddb0c5d7f
(0) Finished request 0.
Waking up in 0.3 seconds.
rad_recv: Access-Request packet from host 192.168.10.212 port 32878, id=43, length=287

    EAP-Message = 0x02ce0034120a000007050000d28837f3ec25745202083c21313d8d29100100010e05001031393031373030303030303030363534
    Message-Authenticator = 0x5dbd2219a029f2421a86fca4c24974b5
    NAS-Identifier = "MT_Yann"
    NAS-IP-Address = 192.168.10.212
(1) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default
(1)   group authorize {
(1)  - entering group authorize {...}
(1)   [preprocess] = ok
(1)   [chap] = noop
(1)   [auth_log] = ok
(1)   [mschap] = noop
(1)   [digest] = noop
(1) suffix : No '@' in User-Name = "1901700000000654", looking up realm NULL
(1) suffix : No such realm "NULL"
(1)   [suffix] = noop
rlm_sim_files: authorized user/imsi 1901700000000654 
rlm_sim_files: Adding EAP-Type: eap-sim
(1)   [sim_files] = ok
(1) eap : EAP packet type response id 206 length 52
(1) eap : No EAP Start, assuming it's an on-going EAP conversation
(1)   [eap] = updated
(1)   [files] = noop
(1)   [expiration] = noop
(1)   [logintime] = noop
(1) pap : WARNING! No "known good" password found for the user.  Authentication may fail because of this.
(1)   [pap] = noop
(1) Found Auth-Type = EAP
(1) # Executing group from file /usr/local/etc/raddb/sites-enabled/default
(1)   group authenticate {
(1)  - entering group authenticate {...}
(1) eap : Request found, released from the list
(1) eap : EAP/sim
(1) eap : processing type sim
eap: EAP-Sim length = 20
eap: ID_Len = 4
eap: EAP-SIm length chosen = 32 
eap: EAP-Sim length = 4
eap: ID_Len = 4
eap: EAP-SIm length chosen = 32 
eap: EAP-Sim length = 20
eap: ID_Len = 16
eap: EAP-SIm length chosen = 32 
(1) eap : Underlying EAP-Type set EAP ID to 207
(1)   [eap] = handled
Sending Access-Challenge of id 43 to 192.168.10.212 port 32878
    EAP-Message = 0x01cf0050120b0000010d0000000000000000000000000000000000000f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0ff0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00b050000c13e9c1dcc448cf3e4028e30d28e43c4
    Message-Authenticator = 0x00000000000000000000000000000000
    State = 0x27d04fcb261f5dceaedc556ddb0c5d7f
(1) Finished request 1.
Waking up in 0.2 seconds.
Waking up in 4.5 seconds.

rad_recv: Access-Request packet from host 192.168.10.212 port 37021, id=44, length=263
    EAP-Message = 0x02cf001c120b00000b050000eeaec0aaf45ca982cb310428eb838a8e
    Message-Authenticator = 0x3ca71ae6141b80753b4ccb402cc71e5f
    NAS-Identifier = "MT_Yann"
    NAS-IP-Address = 192.168.10.212
(2) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default
(2)   group authorize {
(2)  - entering group authorize {...}
(2)   [preprocess] = ok
(2)   [chap] = noop
(2)   [auth_log] = ok
(2)   [mschap] = noop
(2)   [digest] = noop
(2) suffix : No '@' in User-Name = "1901700000000654", looking up realm NULL
(2) suffix : No such realm "NULL"
(2)   [suffix] = noop
rlm_sim_files: authorized user/imsi 1901700000000654 
rlm_sim_files: Adding EAP-Type: eap-sim
(2)   [sim_files] = ok
(2) eap : EAP packet type response id 207 length 28
(2) eap : No EAP Start, assuming it's an on-going EAP conversation
(2)   [eap] = updated
(2)   [files] = noop
(2)   [expiration] = noop
(2)   [logintime] = noop
(2) pap : WARNING! No "known good" password found for the user.  Authentication may fail because of this.
(2)   [pap] = noop
(2) Found Auth-Type = EAP
(2) # Executing group from file /usr/local/etc/raddb/sites-enabled/default
(2)   group authenticate {
(2)  - entering group authenticate {...}
(2) eap : Request found, released from the list
(2) eap : EAP/sim
(2) eap : processing type sim
eap: EAP-Sim length = 20
eap: ID_Len = -1219474647
eap: EAP-SIm length chosen = 32 
MAC check succeed 
(2) eap : Underlying EAP-Type set EAP ID to 208
(2) eap : Freeing handler
(2)   [eap] = ok
(2) # Executing section post-auth from file /usr/local/etc/raddb/sites-enabled/default
(2)   group post-auth {
(2)  - entering group post-auth {...}
(2)   [exec] = noop
Sending Access-Accept of id 44 to 192.168.10.212 port 37021
    MS-MPPE-Recv-Key = 0x9aca37a3e1743dc8c4326d6ed4e3f7e5f4178abc80cb953e6686ef57ba470624
    MS-MPPE-Send-Key = 0x1b94a8624cea0d23c245b15cc227428d05202328550aa5413296d9de1039337c
    EAP-Message = 0x03d00004
    Message-Authenticator = 0x00000000000000000000000000000000
    User-Name = "1901700000000654"

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121127/cedf087f/attachment.htm>

From holger at freyther.de  Tue Nov 27 15:48:09 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 27 Nov 2012 16:48:09 +0100
Subject: triplets calculation
In-Reply-To: <DUB119-W129732F6B32B14EA71DB248B5E0@phx.gbl>
References: <DUB119-W3465906EC2C8E34BA2DC568B5B0@phx.gbl>
	<20121122181323.GE25233@xiaoyu.lan>
	<CAPvAUg+dTyDxiWHeP35waO1BRY=YX7ZjvzPL6UgaG3ZGecxSOg@mail.gmail.com>
	<DUB119-W129732F6B32B14EA71DB248B5E0@phx.gbl>
Message-ID: <20121127154809.GF30675@xiaoyu.lan>

On Tue, Nov 27, 2012 at 01:48:12PM +0100, Yann R. Moupinda wrote:

Hi,

> > But only accepting weak keyes is not logical.
> 
> 
> All RAND values included in the eap request/sim/challenge message contain lowercase HEX characters.

you will need to reduce the issue but I don't think it is the RAND. Use
osmo-auc-gen to generate the RAND, Sres and Kc and run the gsm algorithm
and compare the result.

The second half is done in the following script:
#!/usr/bin/env python
from pySim.transport.serial import SerialSimLink
from pySim.commands import SimCardCommands
from pySim.transport.pcsc import PcscSimLink
from pySim.utils import swap_nibbles


#sl = SerialSimLink(device='/dev/ttyUSB0', baudrate=9600)
sl = PcscSimLink(0) #opts.pcsc_dev)
sc = SimCardCommands(sl)

sl.wait_for_card()

# Print IMSI
print sc.read_binary(['3f00', '7f20', '6f07'])
(res,_) = sc.read_binary(['3f00', '7f20', '6f07'])
print swap_nibbles(res)[3:]


# The RAND as printed by osmo-auc-gen
(res, _) = sc.run_gsm('58 f7 46 05 c9 da a9 2b 15 e7 db 7e fd 53 02 3a'.replace(' ', ''))

# SRES and Kc concatinated
print res == ('29 fd 55 45 d5 ab 99 85 56 13 b4 00'.replace(' ', ''))


I think the above RAND matches your classification for 'strong', it is returns
the expected result. Make sure that you are using the right A3A8 algorithm in
your setup, I don't think it has anything to do with the RAND.


holger



From adolfocugat at gmail.com  Sat Nov 24 09:07:03 2012
From: adolfocugat at gmail.com (Adolfo Cugat)
Date: Sat, 24 Nov 2012 10:07:03 +0100
Subject: nanoBTS amplifier
Message-ID: <CAKLdXFWg4UQ76E6+covNXOWeU9YmmKqsk+izsTmkwqqzLicuNQ@mail.gmail.com>

What amplifier do you use with ip.access BTS ???

Adolfo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20121124/24490380/attachment.htm>

From holger at freyther.de  Sat Nov 24 09:58:22 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sat, 24 Nov 2012 10:58:22 +0100
Subject: nanoBTS amplifier
In-Reply-To: <CAKLdXFWg4UQ76E6+covNXOWeU9YmmKqsk+izsTmkwqqzLicuNQ@mail.gmail.com>
References: <CAKLdXFWg4UQ76E6+covNXOWeU9YmmKqsk+izsTmkwqqzLicuNQ@mail.gmail.com>
Message-ID: <20121124095822.GB12974@xiaoyu.lan>

On Sat, Nov 24, 2012 at 10:07:03AM +0100, Adolfo Cugat wrote:
> What amplifier do you use with ip.access BTS ???

it depends.



From stuart at bluewave.im  Tue Nov 27 17:51:24 2012
From: stuart at bluewave.im (Stuart Baggs)
Date: Tue, 27 Nov 2012 17:51:24 +0000
Subject: nanoBTS model 139 and model 165 for sale
Message-ID: <6393627F-0BBC-404D-8471-21352750A401@bluewave.im>

Hi All

We're selling some of our pico cell stock that has been on our shelf for a few months. We have 1 x brand new model 139 pico cell (1800 MHz GPRS), 1 x model 165g (1800 MHz GPRS/EDGE) and 1 x model 165cu (900 MHz GPRS/EDGE).

These on on offer first come first served.

Kind Regards 

Stuart Baggs
Managing Director
BlueWave Communications Limited

Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately . This message contains confidential information and is intended solely for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.