From laforge at gnumonks.org  Tue Dec 14 12:45:22 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 14 Dec 2010 13:45:22 +0100
Subject: [PATCH 0/1] Add bport0/1 support for bs11_config
In-Reply-To: <cover.1249835034.git.daniel@totalueberwachung.de>
References: <cover.1249835034.git.daniel@totalueberwachung.de>
Message-ID: <20101214124522.GF32316@prithivi.gnumonks.org>

Hi all,

getting back to a very old post:

On Sun, Aug 09, 2009 at 07:03:30PM +0200, Daniel Willmann wrote:

> It seems sometimes creating bport1 fails, even LMT shows create obj
> greyed out. Don't know why yet.

I discovered that this happens when you wnat to create BPORT1 while BPORT0 is
in star mode.  You have to set BPORT0 to multi-drop _before_ creating BPORT1.

-- 
- 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 laforge at gnumonks.org  Tue Dec 14 09:36:18 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 14 Dec 2010 10:36:18 +0100
Subject: SCCP connection establishment from MSC to BSC
In-Reply-To: <4CC6A97C.9090306@freyther.de>
References: <4CB4E966.7010806@freyther.de>
	<AANLkTikrY+WH+qvj2Z49_dAYSwM51oXWaT2xUOSqGfXX@mail.gmail.com>
	<4CB6BE45.4020808@freyther.de>
	<AANLkTi=1dJj96xkyX0x9_bz7YD+0uXmkaEQ7DhgeihYx@mail.gmail.com>
	<4CB829A1.4080003@freyther.de>
	<AANLkTimN-r5sDam6G+wEn7JS-TrDoGo--h+JzseaounZ@mail.gmail.com>
	<4CB872D4.9060001@freyther.de> <4CB873A1.5060405@freyther.de>
	<AANLkTinLQTnrO7Kg5w-nZDAtgv3A92j_iLgJZ_G_WWmV@mail.gmail.com>
	<4CC6A97C.9090306@freyther.de>
Message-ID: <20101214093618.GE10852@prithivi.gnumonks.org>

Hi zecke,

getting back t oan old thread:

On Tue, Oct 26, 2010 at 12:12:12PM +0200, Holger Hans Peter Freyther wrote:
> On 10/26/2010 11:10 AM, tejas oza wrote:
> > Hi Holger,
> > 
> > We found the below code in bsc_msc_ip.c
> > 
> > static int msc_sccp_accept(struct sccp_connection *connection, void *data)
> > {
> >     LOGP(DMSC, LOGL_DEBUG, "Rejecting incoming SCCP connection.\n");
> >     return -1;
> > }
> > 
> > So, Does the Open BSC accepts the SCCP connection request from MSC ?
> 
> As you have found in the code. the BSC does not accept connections from the
> MSC. The reason is that I have not found anything in GSM08.08 that indicates
> that the MSC will open a connection. Am I wrong with that? 

GSM 08.06 Chapter 6.1 Connection establishment:
ii) the MSC decides to perform an external handover and a new dedicated radio
    resource has t obe reserved in the new BSS.  The SCCP connection
    establishment is then initiated by the MSC

So there is at least one case in which this procedure is being used.  I know,
we only do intra-BSC handover at the moment and no external handover is supported.

But I think you might be interested in this anyway :)

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 holger at freyther.de  Tue Dec 14 14:49:48 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 14 Dec 2010 15:49:48 +0100
Subject: SCCP connection establishment from MSC to BSC
In-Reply-To: <20101214093618.GE10852@prithivi.gnumonks.org>
References: <4CB4E966.7010806@freyther.de>
	<AANLkTikrY+WH+qvj2Z49_dAYSwM51oXWaT2xUOSqGfXX@mail.gmail.com>
	<4CB6BE45.4020808@freyther.de>
	<AANLkTi=1dJj96xkyX0x9_bz7YD+0uXmkaEQ7DhgeihYx@mail.gmail.com>
	<4CB829A1.4080003@freyther.de>
	<AANLkTimN-r5sDam6G+wEn7JS-TrDoGo--h+JzseaounZ@mail.gmail.com>
	<4CB872D4.9060001@freyther.de> <4CB873A1.5060405@freyther.de>
	<AANLkTinLQTnrO7Kg5w-nZDAtgv3A92j_iLgJZ_G_WWmV@mail.gmail.com>
	<4CC6A97C.9090306@freyther.de>
	<20101214093618.GE10852@prithivi.gnumonks.org>
Message-ID: <4D07840C.2090200@freyther.de>

On 12/14/2010 10:36 AM, Harald Welte wrote:
> Hi zecke,

> 
> GSM 08.06 Chapter 6.1 Connection establishment:
> ii) the MSC decides to perform an external handover and a new dedicated radio
>     resource has t obe reserved in the new BSS.  The SCCP connection
>     establishment is then initiated by the MSC
> 
> So there is at least one case in which this procedure is being used.  I know,
> we only do intra-BSC handover at the moment and no external handover is supported.
> 
> But I think you might be interested in this anyway :)

Ah okay, I will need to look at 08.06 as well. Thanks a lot for finding it.
And yes we do not support inter-BSC hand-over and even intra-BSC handover is
slightly wrong ad we do not inform the MSC about the handover (leaving alone
the mgcp code to handle that).

holger



From 246tnt at gmail.com  Thu Dec  9 12:50:02 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 9 Dec 2010 13:50:02 +0100
Subject: Plans for GSM / OpenBSC field test at 27C3
In-Reply-To: <20101026191157.GW25165@prithivi.gnumonks.org>
References: <20101026183609.GV25165@prithivi.gnumonks.org>
	<AANLkTi=XnF1oU24==uV63T8VLivMR2rD4RB2o8c954OS@mail.gmail.com>
	<20101026191157.GW25165@prithivi.gnumonks.org>
Message-ID: <AANLkTikRygh1gKbqEtBx9HvGYB60fUDuEWgAxW8YLH1f@mail.gmail.com>

Hi,

>> I was planning to enhance pySim to allow more batch programming and
>> support for pc/sc reader (so you just have to insert, wait, remove,
>> insert, wait, ...).
>>
>> I will probably do that soon, after DeepSec.
>
> ok, great. looking forward to it.

This is done and pushed.

I merged your pcsc code first, then :
 - Split into several files (for clarity and also so that if you don't
use the pcsc code, it doesn't try to import pysmartcard and the other
way around)
 - Added option to save parameters to CSV file, or directly to an
openBSC HLR. (the extension is just 9 + 5 last digits of ICCID, change
in the code if required)
 - Added option to switch to batch mode (including saving state).
Takes about a second per card with a pcsc reader.

./pySim-prog.py -p 0 -t auto_once -n 27C3 -c 49 -x 232 -y 42 -z
ZuperZecret --batch --batch-state /tmp/batchstate.dat --write-hlr
/tmp/openbsc.sqlite3 --write-csv /tmp/out.csv

and to resume a batch you can omit the network parameters

./pySim-prog.py -p 0 -t auto_once --batch --batch-state
/tmp/batchstate.dat --write-hlr /tmp/openbsc.sqlite3 --write-csv
/tmp/out.csv

(The 'auto_once' means do auto-detection only once for the session and
assume other card are the same type to speed things up)


Cheers,

    Sylvain



From laforge at gnumonks.org  Thu Dec  9 15:44:02 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 9 Dec 2010 23:44:02 +0800
Subject: Plans for GSM / OpenBSC field test at 27C3
In-Reply-To: <AANLkTikRygh1gKbqEtBx9HvGYB60fUDuEWgAxW8YLH1f@mail.gmail.com>
References: <20101026183609.GV25165@prithivi.gnumonks.org>
	<AANLkTi=XnF1oU24==uV63T8VLivMR2rD4RB2o8c954OS@mail.gmail.com>
	<20101026191157.GW25165@prithivi.gnumonks.org>
	<AANLkTikRygh1gKbqEtBx9HvGYB60fUDuEWgAxW8YLH1f@mail.gmail.com>
Message-ID: <20101209154402.GC13457@prithivi.gnumonks.org>

Thanks a lot !

On Thu, Dec 09, 2010 at 01:50:02PM +0100, Sylvain Munaut wrote:
> I merged your pcsc code first, then :
>  - Split into several files (for clarity and also so that if you don't
> use the pcsc code, it doesn't try to import pysmartcard and the other
> way around)
>  - Added option to save parameters to CSV file, or directly to an
> openBSC HLR. (the extension is just 9 + 5 last digits of ICCID, change
> in the code if required)
>  - Added option to switch to batch mode (including saving state).
> Takes about a second per card with a pcsc reader.

this makes a lot of sense, thanks a lot.

As for the actual 27C3 deployment: I can offer at least two PC/SC readers
(Omnikey 3121 / 5121) for the GSM helpdesk that Andreas Eversberg will
be running.

Andreas: Do you have some SuperSIM to test the new pySIM patch mode and
integrate it with OpenBSC?  If not, I will send you some sample cards monday
next week.

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 Andreas.Eversberg at versatel.de  Fri Dec 10 08:48:35 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Fri, 10 Dec 2010 09:48:35 +0100
Subject: AW: Plans for GSM / OpenBSC field test at 27C3
Message-ID: <B16317F2B1592B4492FC414114171CE604A1BC5A@FLBVEXCH01.versatel.local>


> Andreas: Do you have some SuperSIM to test the new pySIM patch mode
and
> integrate it with OpenBSC?  If not, I will send you some sample cards
monday
> next week.

please send me some cards. i have not followed the pySIM talk in the
mailing list. what reader do i need?




From laforge at gnumonks.org  Fri Dec 10 14:56:43 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 10 Dec 2010 22:56:43 +0800
Subject: Plans for GSM / OpenBSC field test at 27C3
In-Reply-To: <B16317F2B1592B4492FC414114171CE604A1BC5A@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE604A1BC5A@FLBVEXCH01.versatel.local>
Message-ID: <20101210145643.GA26844@prithivi.gnumonks.org>

On Fri, Dec 10, 2010 at 09:48:35AM +0100, Andreas.Eversberg wrote:
> 
> > Andreas: Do you have some SuperSIM to test the new pySIM patch mode
> and
> > integrate it with OpenBSC?  If not, I will send you some sample cards
> monday
> > next week.
> 
> please send me some cards. i have not followed the pySIM talk in the
> mailing list. what reader do i need?

I will send you some cards on monday when I'm back in Berlin.

Any Linux PC/SC (pcsc-lite) compatible reader should do for the testing and
programming.  A lot of readers are supported by using OpenCT with pcsc-lite.

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 egu2100 at yahoo.com  Wed Dec  1 15:01:31 2010
From: egu2100 at yahoo.com (EGU 2100)
Date: Wed, 1 Dec 2010 07:01:31 -0800 (PST)
Subject: nanoBTS BER Test
Message-ID: <737921.70312.qm@web31105.mail.mud.yahoo.com>

Hi,
?
I like to perform a TCH BER Test for nanoBTS via R&S CMU300. Does anyone know how to configure the nanoBTS using ipaccess-config? to perform this BER test?
?
Thanks!
?
EGU


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

From laforge at gnumonks.org  Thu Dec  2 23:25:33 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 3 Dec 2010 07:25:33 +0800
Subject: nanoBTS BER Test
In-Reply-To: <737921.70312.qm@web31105.mail.mud.yahoo.com>
References: <737921.70312.qm@web31105.mail.mud.yahoo.com>
Message-ID: <20101202232533.GE10739@prithivi.gnumonks.org>

Hi $unknown,

it would always be great to introduce your self a bit to this list...

On Wed, Dec 01, 2010 at 07:01:31AM -0800, EGU 2100 wrote:
> Hi,
> ? I like to perform a TCH BER Test for nanoBTS via R&S CMU300. Does anyone
> know how to configure the nanoBTS using ipaccess-config? to perform this BER
> test?

to the best of my knowledge there is no OML TEST mode related to this in the
nanoBTS.  My assumption is that the CMU300 is actually just trying to establish
a TCH voice call and do the test using that voice call...

-- 
- 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 stuart at bluewave.im  Wed Dec  1 15:12:49 2010
From: stuart at bluewave.im (Stuart Baggs)
Date: Wed, 1 Dec 2010 15:12:49 +0000
Subject: GPRS Problem
Message-ID: <A54E6E51-ACFA-4D9B-8B17-A913A1917631@bluewave.im>

Hi, I am openBSC version 0.9.11.92-6d42 and I have compiled open-ggsn and the osmo-sgsn binary has been built when i recompiled openBSC. Now here is the problem. The GPRS indicator on the handset lights up, but no GPRS data passes. I have the following config files:

---------/etc/ggsn.conf---------
# TAG: listen
# Specifies the local IP address to listen to
listen 192.168.1.70

# TAG: dynip
# Dynamic IP address pool.
# Used for allocation of dynamic IP address when address is not given
# by HLR.
# If this option is not given then the net option is used as a substitute.
dynip 192.168.254.0/24

# TAG: pcodns1/pcodns2
# Protocol configuration option domain name system server 1 & 2.
pcodns1 208.67.222.222
pcodns2 208.67.220.220
--------------------------------

---------/etc/ggsn.conf---------
!
! Osmocom SGSN configuration
!
!
line vty
 no login
!
sgsn
 gtp local-ip 192.168.1.80
 ggsn 0 remote-ip 192.168.1.70
 ggsn 0 gtp-version 1
!
ns
 timer tns-block 3
 timer tns-block-retries 3
 timer tns-reset 3
 timer tns-reset-retries 3
 timer tns-test 30
 timer tns-alive 3
 timer tns-alive-retries 10
 encapsulation udp local-ip 192.168.1.60
 encapsulation udp local-port 23000
 encapsulation framerelay-gre enabled 0
!
bssgp
!
--------------------------------

I have setup the server to have 4 virtual addresses: 192.168.1.50, 192.168.1.60, 192.168.1.70, 192.168.1.80.

When I start the ggsn and do a route -n it shows thats tun0 is up with the ip range 192.168.0.0/24. I have specified it to be 192.168.1.254 via the dynip argument in the /etc/ggsn.conf file. I have setup iptables to NAT eth0 so no issues there.

Thanks

Stuart


From laforge at gnumonks.org  Thu Dec  2 14:03:44 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 2 Dec 2010 22:03:44 +0800
Subject: GPRS Problem
In-Reply-To: <A54E6E51-ACFA-4D9B-8B17-A913A1917631@bluewave.im>
References: <A54E6E51-ACFA-4D9B-8B17-A913A1917631@bluewave.im>
Message-ID: <20101202140344.GC3861@prithivi.gnumonks.org>

Hi Stuart,

what kind of output do you get from OsmoSGSN if you enable the DEBUG log
level for 'mm', 'ns', 'bssgp' and 'gprs' ?

Also, why don't you use wireshark to look at both the Gb as well as the GTP
protocol traces?

And what about using the VTY of the sgsn to inquire about the state of the NS,
BSSGP protocol, show the mm-contexts, if any?

There are so many ways to obtain more information on what exactly is going on,
please use them :)

-- 
- 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 kobayashi_maru at onlinehome.de  Wed Dec  1 15:16:57 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Wed, 01 Dec 2010 16:16:57 +0100
Subject: bs11 power setting
Message-ID: <1291216617.3647.3.camel@r-9djhc747gf8b40ha>

hello
one of my bs11 ist set to 30mw, the other one to 2w, bs11_config told
me. this is to much. how do i get the 2nd downto 30mw?

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From risky at mail.ru  Wed Dec  1 18:06:47 2010
From: risky at mail.ru (Sergey V. Efimoff)
Date: Wed, 1 Dec 2010 21:06:47 +0300
Subject: bs11 power setting
In-Reply-To: <1291216617.3647.3.camel@r-9djhc747gf8b40ha>
References: <1291216617.3647.3.camel@r-9djhc747gf8b40ha>
Message-ID: <7926F461-EC55-4759-B2B6-49183EA41639@mail.ru>

Hello Thomas,

I did not synchronize my sources for a while, so I don't know if the
current bs11_config version supports this feature.

Anyway, you can surf into the source of bs11_config utility, it is
quite simple. You only need to find the place where commands are processed
(for example, handle_state_resp() function) and add a command
which will set the desired power.

My quick-and-dirty solution for this task looks like this (in your case,
you need to set 30mW power):

abis_nm_bs11_set_trx_power(g_bts->c0, BS11_TRX_POWER_GSM_30mW);


To change TX power, you need to switch your BTS to maintenance mode, then
run your command with this hack, then restart the BTS. Voila!

Best Regards,
Sergey.

On Dec 1, 2010, at 6:16 PM, Thomas Ansorg wrote:

> hello
> one of my bs11 ist set to 30mw, the other one to 2w, bs11_config told
> me. this is to much. how do i get the 2nd downto 30mw?
> 
> T.
> -- 
> Wer Rechtschreibfehler findet, darf sie behalten!
> 
> 




From kobayashi_maru at onlinehome.de  Wed Dec  1 15:24:22 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Wed, 01 Dec 2010 16:24:22 +0100
Subject: bs11 not working
Message-ID: <1291217062.3647.11.camel@r-9djhc747gf8b40ha>

hi
my 2nd bs11 doesnt work. the boot screen from bs11_config looks like
this(attached pic). both boot screens look like that, the operational
one too. the 2 bs11 are connected identical, the software is the same.
one works, the other doesnt. bad! the bootstrapping works on both, but
the handy can only detect the one of two bs11.

troubleshooting advices are welcome, openbsc website was no help

T.

-- 
Wer Rechtschreibfehler findet, darf sie behalten!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dsc00006.jpg
Type: image/jpeg
Size: 574953 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101201/880c62d6/attachment.jpg>

From 246tnt at gmail.com  Thu Dec  2 14:20:07 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 2 Dec 2010 15:20:07 +0100
Subject: bs11 not working
In-Reply-To: <1291217062.3647.11.camel@r-9djhc747gf8b40ha>
References: <1291217062.3647.11.camel@r-9djhc747gf8b40ha>
Message-ID: <AANLkTikHLt1nxYd3PY6QAAemr4v6bMp2QCb0t9D3s5Qo@mail.gmail.com>

> troubleshooting advices are welcome, openbsc website was no help

The clock of the non working one might just be too off ...

See http://openbsc.osmocom.org/trac/wiki/isdnsync for a tool to
calibrate (with appropriate HW).

If you don't have the equipement ... huh, good luck.
You can always try random values until it works.
If you have a USRP you can try to lock onto it and compare offset ...


Cheers,

    Sylvain



From risky at mail.ru  Thu Dec  2 14:29:11 2010
From: risky at mail.ru (Sergey V. Efimoff)
Date: Thu, 2 Dec 2010 17:29:11 +0300
Subject: bs11 not working
In-Reply-To: <1291217062.3647.11.camel@r-9djhc747gf8b40ha>
References: <1291217062.3647.11.camel@r-9djhc747gf8b40ha>
Message-ID: <5B2C14B3-231F-4A1B-9EA5-79D3C60148E9@mail.ru>

Hello,

Try to check your E1 connection and impedance (see jumpers).

Sergey.

On Dec 1, 2010, at 6:24 PM, Thomas Ansorg wrote:

> hi
> my 2nd bs11 doesnt work. the boot screen from bs11_config looks like
> this(attached pic). both boot screens look like that, the operational
> one too. the 2 bs11 are connected identical, the software is the same.
> one works, the other doesnt. bad! the bootstrapping works on both, but
> the handy can only detect the one of two bs11.
> 
> troubleshooting advices are welcome, openbsc website was no help
> 
> T.
> 
> -- 
> Wer Rechtschreibfehler findet, darf sie behalten!
> <dsc00006.jpg>




From spaar at mirider.augusta.de  Thu Dec  2 18:29:39 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Thu, 02 Dec 2010 18:29:39 
Subject: bs11 not working
Message-ID: <4cf7e593.mirider@mirider.augusta.de>

Hello Sylvain,

On Thu, 2 Dec 2010 15:20:07 +0100, "Sylvain Munaut" <246tnt at gmail.com> wrote:
> 
> The clock of the non working one might just be too off ...
> 
> See http://openbsc.osmocom.org/trac/wiki/isdnsync for a tool to
> calibrate (with appropriate HW).
> 
> If you don't have the equipement ... huh, good luck.
> You can always try random values until it works.
> If you have a USRP you can try to lock onto it and compare offset ...

Its possible to set the clock calibration to a fixed value, this was
a feature introduced a while ago. The original clock calibration
setting workes pretty good, at least from my experience. So if the
clock is off due to using the E1 clock as a reference, it should be
enough to set the orginal clock calibration value and switch the
PLL to standalone mode.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From risky at mail.ru  Thu Dec  2 18:08:09 2010
From: risky at mail.ru (Sergey V. Efimoff)
Date: Thu, 2 Dec 2010 21:08:09 +0300
Subject: bs11 not working
In-Reply-To: <4cf7e593.mirider@mirider.augusta.de>
References: <4cf7e593.mirider@mirider.augusta.de>
Message-ID: <411953AA-78EE-4928-98EC-0ADCF100828A@mail.ru>

Hello Dieter,

I had once or twice seen BTS stations which had working PLL value
very different from calibrated value. In order to get them close I had to
use E1 hardware with high precision oscillator, then switch the
hardware to the PLL-locked mode. This operation took me plenty
of time.

Please tell, is it possible to set the working PLL value directly?

Best Regards,
Sergey.

On Dec 2, 2010, at 6:29 PM, Dieter Spaar wrote:

> Hello Sylvain,
> 
> On Thu, 2 Dec 2010 15:20:07 +0100, "Sylvain Munaut" <246tnt at gmail.com> wrote:
>> 
>> The clock of the non working one might just be too off ...
>> 
>> See http://openbsc.osmocom.org/trac/wiki/isdnsync for a tool to
>> calibrate (with appropriate HW).
>> 
>> If you don't have the equipement ... huh, good luck.
>> You can always try random values until it works.
>> If you have a USRP you can try to lock onto it and compare offset ...
> 
> Its possible to set the clock calibration to a fixed value, this was
> a feature introduced a while ago. The original clock calibration
> setting workes pretty good, at least from my experience. So if the
> clock is off due to using the E1 clock as a reference, it should be
> enough to set the orginal clock calibration value and switch the
> PLL to standalone mode.
> 
> Best regards,
>  Dieter
> -- 
> Dieter Spaar, Germany                           spaar at mirider.augusta.de
> 




From spaar at mirider.augusta.de  Thu Dec  2 19:22:02 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Thu, 02 Dec 2010 19:22:02 
Subject: bs11 not working
Message-ID: <4cf7f1da.mirider@mirider.augusta.de>

Hello Sergey,

On Thu, 2 Dec 2010 21:08:09 +0300, "Sergey V. Efimoff" <risky at mail.ru> wrote:
> 
> I had once or twice seen BTS stations which had working PLL value
> very different from calibrated value. In order to get them close I had to
> use E1 hardware with high precision oscillator, then switch the
> hardware to the PLL-locked mode. This operation took me plenty
> of time.
> 
> Please tell, is it possible to set the working PLL value directly?

Yes, bs11_config supports this. Its the "pll-workvalue" command. The
way how the PLL workvalue could be set was not obvious so it took a
while till we found out how this could be done. Thats the reason why
it took quite long till this command was introduced.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From jmercury313 at gmail.com  Wed Dec  1 15:35:10 2010
From: jmercury313 at gmail.com (jason mercury)
Date: Wed, 1 Dec 2010 17:35:10 +0200
Subject: socket problem again
Message-ID: <AANLkTin1viJcdfZZz5cB7cdfcafmSCYYZrgsNA=uz9UH@mail.gmail.com>

Hi ,

Here i want to restate my problem. I want to run two different bts with
different network parameters on the same PC, at the same time. I can not
achieve this with one bsc_hack because bsc has a unique mnc. I can not run
two bsc_hack at the same time because they try to use the same port. I think
that there might be two approaches to solve this:

1) Modifying the code such that i can specify different mnc for each bts
with one executable program. Maybe, two different gsm network can be defined
as network1 and network2 (similar to bts0,bts1,...). So i can give different
network parameters for different networks and run them with one program.

2) Changing the communication port of nanoBTS and OpenBSC such that i can
run two bsc_hack at the same. I think that it should be changed on both
nanoBTS and source code.

Could any one help me (at least give some hints) about how i can implement
one of these approaches. Or, You could propose some other approaches.

Thank you.

Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101201/52e2edab/attachment.htm>

From 246tnt at gmail.com  Wed Dec  1 16:07:27 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 1 Dec 2010 17:07:27 +0100
Subject: socket problem again
In-Reply-To: <AANLkTin1viJcdfZZz5cB7cdfcafmSCYYZrgsNA=uz9UH@mail.gmail.com>
References: <AANLkTin1viJcdfZZz5cB7cdfcafmSCYYZrgsNA=uz9UH@mail.gmail.com>
Message-ID: <AANLkTikhwn2NusgT8qXx-vU-8iy+hj5oG6TsD63vNC9u@mail.gmail.com>

> Here i want to restate my problem. I want to run two different bts with
> different network parameters on the same PC, at the same time. I can not
> achieve this with one bsc_hack because bsc has a unique mnc. I can not run
> two bsc_hack at the same time because they try to use the same port. I think
> that there might be two approaches to solve this:

We understand you problem and there is no "ready" solution, you have
to code it yourself.


> 1) Modifying?the code such that i can?specify different mnc for each bts
> with one executable program. Maybe, two different gsm network can be defined
> as network1 and network2 (similar to bts0,bts1,...). So i can give different
> network parameters for different networks and run them with one program.

That's an option. See nv_put_prim_oml in ipaccess-config.c


> 2) Changing the communication port of nanoBTS and OpenBSC such that i can
> run two bsc_hack at the same. I think that it should be changed on both
> nanoBTS and source code.

After a quick check it seems the nanoBTS indeed supports that.


> Could any one help me (at least give some hints) about how i can implement
> one of these approaches. Or, You could propose some other approaches.

We already gave you hint, no just look at the source and fix it (or
hire someone to do it for you)


Cheers,

    Sylvain



From holger at freyther.de  Wed Dec  1 16:10:35 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 01 Dec 2010 17:10:35 +0100
Subject: socket problem again
In-Reply-To: <AANLkTikhwn2NusgT8qXx-vU-8iy+hj5oG6TsD63vNC9u@mail.gmail.com>
References: <AANLkTin1viJcdfZZz5cB7cdfcafmSCYYZrgsNA=uz9UH@mail.gmail.com>
	<AANLkTikhwn2NusgT8qXx-vU-8iy+hj5oG6TsD63vNC9u@mail.gmail.com>
Message-ID: <4CF6737B.2060105@freyther.de>

On 12/01/2010 05:07 PM, Sylvain Munaut wrote:

> 
>> 1) Modifying the code such that i can specify different mnc for each bts
>> with one executable program. Maybe, two different gsm network can be defined
>> as network1 and network2 (similar to bts0,bts1,...). So i can give different
>> network parameters for different networks and run them with one program.
> 
> That's an option. See nv_put_prim_oml in ipaccess-config.c


we still use the global bsc_gsmnet in many places. We need to remove that to
allow something like this.



From 246tnt at gmail.com  Wed Dec  1 16:26:27 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 1 Dec 2010 17:26:27 +0100
Subject: socket problem again
In-Reply-To: <4CF6737B.2060105@freyther.de>
References: <AANLkTin1viJcdfZZz5cB7cdfcafmSCYYZrgsNA=uz9UH@mail.gmail.com>
	<AANLkTikhwn2NusgT8qXx-vU-8iy+hj5oG6TsD63vNC9u@mail.gmail.com>
	<4CF6737B.2060105@freyther.de>
Message-ID: <AANLkTimg4SmQwpGV1qLb0rm4uf6VmN1KrQU4C4_NZo8w@mail.gmail.com>

>>> 1) Modifying the code such that i can specify different mnc for each bts
>>> with one executable program. Maybe, two different gsm network can be defined
>>> as network1 and network2 (similar to bts0,bts1,...). So i can give different
>>> network parameters for different networks and run them with one program.
>>
>> That's an option. See nv_put_prim_oml in ipaccess-config.c
>
>
> we still use the global bsc_gsmnet in many places. We need to remove that to
> allow something like this.

Ooops, I completely replied to the wrong bit :)

I meant that just setting another RSL _port_ would be enough, no need
to listen on another IP.


Cheers,

    Sylvain



From jmercury313 at gmail.com  Thu Dec  2 14:44:05 2010
From: jmercury313 at gmail.com (jason mercury)
Date: Thu, 2 Dec 2010 16:44:05 +0200
Subject: socket problem again
Message-ID: <AANLkTikmZ6-CNDM0MaEqEhU0zjOg4O-aGF0=4ecBFo5Z@mail.gmail.com>

 On 12/01/2010 05:10 PM, Holger Hans Peter Freyther wrote

>* we still use the global bsc_gsmnet in many places. We need to remove that
to
*>* allow something like this.*

Is it a too much difficult process? Should i try to do this and where should
i start?

On 12/01/2010 05:07 PM, Sylvain Munaut wrote:
* >That's an option. See nv_put_prim_oml in ipaccess-config.c*

I think this is for  changing the port of nanoBTS. Where should i modify the
port for bsc_hack?

Thanks.

Jason
**
*

*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101202/0eba9501/attachment.htm>

From stuart at bluewave.im  Wed Dec  1 17:04:23 2010
From: stuart at bluewave.im (Stuart Baggs)
Date: Wed, 1 Dec 2010 17:04:23 +0000
Subject: nanoBTS Ports
Message-ID: <241D2130-22C1-45ED-8CAB-05339AE95888@bluewave.im>

Hi, I am trying to punch a nanoBTS through a firewall to an instance of openBSC over layer3. I have opended TCP port 3002 (OML) and TCP port 3003 (RSL) but no green light or any traffic captured with tcpdump. Any ideas? I havent changed the default port on the bts.


From bouchtaoui at gmail.com  Thu Dec  2 08:37:40 2010
From: bouchtaoui at gmail.com (Nordin)
Date: Thu, 02 Dec 2010 09:37:40 +0100
Subject: nanoBTS Ports
In-Reply-To: <241D2130-22C1-45ED-8CAB-05339AE95888@bluewave.im>
References: <241D2130-22C1-45ED-8CAB-05339AE95888@bluewave.im>
Message-ID: <4CF75AD4.7050100@gmail.com>

  On 1-12-2010 18:04, Stuart Baggs wrote:
> Hi, I am trying to punch a nanoBTS through a firewall to an instance of openBSC over layer3. I have opended TCP port 3002 (OML) and TCP port 3003 (RSL) but no green light or any traffic captured with tcpdump. Any ideas? I havent changed the default port on the bts.
>

Have you configured nanoBTS with ipaccess-config?
If not, check the openbsc wiki how to that.




From 246tnt at gmail.com  Wed Dec  1 19:55:56 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 1 Dec 2010 20:55:56 +0100
Subject: Moving subscr_{get/put}_channel in gsm_subscr.c (instead of
	gsm_subscr_base.c)
Message-ID: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>

Hi,


I'm now having another look at implementing MT ciphering.
For this, I need to work inside the paging system.

What I'd like is that the MSC part instead of ever using
paging_request directly, that they all use subscr_get_channel.
Then this would also encapsulate securing the channel and only call
the call back when the channel has been ciphered and is ready for the
MSC part.

This requires making some gsm_04_08 call inside the
subscr_get_channel, so I need to move that call to the 'msc' side of
gsm_subscr.c

To me, it makes sense. I don't see in what context a BSC would use
get/put channel ... the BSC doesn't decide, it's just ordered what to
do by the MSC IIUC.


I would then also replace all calls to paging_request in gsm_04_08.c
by calls to subscr_get_channel.
And also move the "paging_succeded" signal dispatch to the
subscr_get_channel call back and not directly from gsm_04_08_utils.c
(since that signal is used currently to trigger SMS delivery and other
"side" things when we have a channel, it's more a MSC thing).

Finally, I'd need to pass the msgb paging response all the way to the
paging callback because it contains important field to enable
ciphering.


Any objections to this plan ? Did I miss something ?


Cheers,

    Sylvain



From 246tnt at gmail.com  Thu Dec  2 06:59:30 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 2 Dec 2010 07:59:30 +0100
Subject: Moving subscr_{get/put}_channel in gsm_subscr.c (instead of
	gsm_subscr_base.c)
In-Reply-To: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>
References: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>
Message-ID: <AANLkTiksYxmWXvZkF4ec5Pb0MkZwSqt468xJSbhtNhX0@mail.gmail.com>

Hi,


And since a patch is worth a thousand words, I've pushed what I'm
thinking of into the sylvain/prep_27c3 branch.

I haven't moved the SS_PAGING signal dispatch. I have to check a few
things because that signal was previously
dispatched several time (once for each bts) if it expired, which
sounds weird to me.

(the paging call back also seemed to be called several time in case of expiry)


Cheers,

    Sylvain



From holger at freyther.de  Thu Dec  9 05:36:16 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 09 Dec 2010 06:36:16 +0100
Subject: Moving subscr_{get/put}_channel in gsm_subscr.c (instead
	of	gsm_subscr_base.c)
In-Reply-To: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>
References: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>
Message-ID: <4D006AD0.4080808@freyther.de>

On 12/01/2010 08:55 PM, Sylvain Munaut wrote:

> Finally, I'd need to pass the msgb paging response all the way to the
> paging callback because it contains important field to enable
> ciphering.
> 
> 
> Any objections to this plan ? Did I miss something ?

I agree with most of the changes. It is good that the MSC part starts using a
'better' way to manage the channel and has a way to properly queue requests,
maybe even re-use a channel later. From what I see it is a step in the right
direction, it doesn't seem to break osmo-bsc. Feel free to merge it.

There are some minor issues but that is mostly due us having a general issue
with paging. In a network there are two possible configs for paging. The MSC
sends a Paging Request and the BSC sends the RSL paging command (1:1) or the
MSC asks for paging and the BSS will send various items. With the current
nanoBTS config (and I think it was the case for the BS11 too) the BSS is
sending multiple requests.

The above is leaving us with two issues:
	1.) the BSC part needs to schedule paging requests and queue them
	    (and stop them on a paging response)
	2.) the MSC needs to get the paging response part

In the short-term we might want to be able to run the BSC and MSC part in two
different processes and then we would need to properly separate these things.
So I am thinking if things might not be easier in the long run if we check in
the 'open_channel' callback on the MSC side if it was a paging response and
then trigger the signal and the subscriber logic there?

regards
	holger



From 246tnt at gmail.com  Thu Dec  9 08:44:05 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 9 Dec 2010 09:44:05 +0100
Subject: Moving subscr_{get/put}_channel in gsm_subscr.c (instead of
	gsm_subscr_base.c)
In-Reply-To: <4D006AD0.4080808@freyther.de>
References: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>
	<4D006AD0.4080808@freyther.de>
Message-ID: <AANLkTim5ycGO8bKc3VbK1HPQ-qXFpPR=i-WFgjOqHo9c@mail.gmail.com>

Hi,

> So I am thinking if things might not be easier in the long run if we check in
> the 'open_channel' callback on the MSC side if it was a paging response and
> then trigger the signal and the subscriber logic there?

I don't see what you mean there.

grepping for 'open_channel' didn't yield any results.

Cheers,

    Sylvain



From holger at freyther.de  Thu Dec  9 13:57:32 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 09 Dec 2010 14:57:32 +0100
Subject: Moving subscr_{get/put}_channel in gsm_subscr.c (instead of
	gsm_subscr_base.c)
In-Reply-To: <AANLkTim5ycGO8bKc3VbK1HPQ-qXFpPR=i-WFgjOqHo9c@mail.gmail.com>
References: <AANLkTi=81u4z-X5y14Z_mCN0S6VbnOG6_OK0eyosLXLT@mail.gmail.com>	<4D006AD0.4080808@freyther.de>
	<AANLkTim5ycGO8bKc3VbK1HPQ-qXFpPR=i-WFgjOqHo9c@mail.gmail.com>
Message-ID: <4D00E04C.7040107@freyther.de>

On 12/09/2010 09:44 AM, Sylvain Munaut wrote:
> Hi,
> 
>> So I am thinking if things might not be easier in the long run if we check in
>> the 'open_channel' callback on the MSC side if it was a paging response and
>> then trigger the signal and the subscriber logic there?
> 
> I don't see what you mean there.
> 
> grepping for 'open_channel' didn't yield any results.
> 

Sorry,

I couldn't remember the callback function name and was too lazy to check it. I
was referring to compl_l3 which should be called with the Paging Response
message. In the future we should parse it on the MSC side again and then
dispatch it. This is not a show stopper to merge your changes.

holger



From gndz.ali at gmail.com  Thu Dec  2 15:49:15 2010
From: gndz.ali at gmail.com (=?ISO-8859-1?Q?Ali_G=FCnd=FCz?=)
Date: Thu, 2 Dec 2010 16:49:15 +0100
Subject: Free Software GSM Talk in Berlin on Dec. 9th
Message-ID: <AANLkTinwfeWbog5WsqL+9YuecFyKQ4xDJGCGaiC-=wYn@mail.gmail.com>

Hello all,

I'm going to be giving a presentation about free software GSM
implementations at the FSFE's Berlin meeting on December 9th, 2010. It
will be very elementary and newcomer-friendly.  I'm planning to go
over OsmocomBB, OpenBTS and OpenBSC, and discuss their security and
practical implications.

The talk will start at 19:30 in Newthinking Store Tucholskystr. 48,
10117 Berlin. You can find more about it on
http://aligunduz.org/blog/free_gsm_talk_next_week.html

Considering I'm not an expert on GSM myself, it would be nice to have
people more familiar with it in attendance.

Ali G?nd?z



From risky at mail.ru  Thu Dec  2 18:58:23 2010
From: risky at mail.ru (Sergey V. Efimoff)
Date: Thu, 2 Dec 2010 21:58:23 +0300
Subject: BS11 power problem
Message-ID: <DD4DE509-C552-4D15-B837-976E8282BFDB@mail.ru>

Hello All,

Herr Thomas had raised up a discussion about problem with setting of BTS power attribute value.
In connection with this question, I recall another problem which has occurred with one of my BTS's.
It has a very strange behavior. Its output power is set to 2W. My measure device 
tells me that receive level at the desired channel is about -24 dBm after station boot-up. 
This value is very good, no other base station around shows better results.

But right after the very first GSM call the receive level quickly jumps down to -70 or
even -80 dBm, this value corresponds to 30mW of output power. BTS station still works
and output power is still shown as 2W.

This effect had been discovered with only one of my BTS stations, while other stations work well.
Does it mean that it's a hardware problem? Has anyone discovered this problem earlier?

Best Regards,
Sergey.




From laforge at gnumonks.org  Thu Dec  2 23:22:56 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 3 Dec 2010 07:22:56 +0800
Subject: BS11 power problem
In-Reply-To: <DD4DE509-C552-4D15-B837-976E8282BFDB@mail.ru>
References: <DD4DE509-C552-4D15-B837-976E8282BFDB@mail.ru>
Message-ID: <20101202232256.GD10739@prithivi.gnumonks.org>

On Thu, Dec 02, 2010 at 09:58:23PM +0300, Sergey V. Efimoff wrote:

> But right after the very first GSM call the receive level quickly jumps down
> to -70 or even -80 dBm, this value corresponds to 30mW of output power. BTS
> station still works and output power is still shown as 2W.

In case you are running a multi-TRX BTS: is this the received power level on
the TCH of the call or on the BCCH ?  If downlink power control is active, the
BTS will not send more power than needed on a dedicated channel...

> This effect had been discovered with only one of my BTS stations, while other
> stations work well.  Does it mean that it's a hardware problem? Has anyone
> discovered this problem earlier?

Are the other BTS's configured exactly the same way?  As explained, the
difference single-trx / dual-trx and downlink power control might explain it.

otherwise, if configuration of bs-11, openbsc and the bs11 firmware is
identical, it might well be a hardware issue.  But I don't get why it would
be related to the first call or not...

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 risky at mail.ru  Fri Dec  3 12:01:45 2010
From: risky at mail.ru (Sergey V. Efimoff)
Date: Fri, 3 Dec 2010 15:01:45 +0300
Subject: BS11 power problem
In-Reply-To: <20101202232256.GD10739@prithivi.gnumonks.org>
References: <DD4DE509-C552-4D15-B837-976E8282BFDB@mail.ru>
	<20101202232256.GD10739@prithivi.gnumonks.org>
Message-ID: <7BB57E2C-CB96-467C-8524-6F521612CF07@mail.ru>

Hello Harald,

On Dec 3, 2010, at 2:22 AM, Harald Welte wrote:

> On Thu, Dec 02, 2010 at 09:58:23PM +0300, Sergey V. Efimoff wrote:
> 
>> But right after the very first GSM call the receive level quickly jumps down
>> to -70 or even -80 dBm, this value corresponds to 30mW of output power. BTS
>> station still works and output power is still shown as 2W.
> 
> In case you are running a multi-TRX BTS: is this the received power level on
> the TCH of the call or on the BCCH ?  If downlink power control is active, the
> BTS will not send more power than needed on a dedicated channel...

The receive level is shown for BCCH.

>> This effect had been discovered with only one of my BTS stations, while other
>> stations work well.  Does it mean that it's a hardware problem? Has anyone
>> discovered this problem earlier?
> Are the other BTS's configured exactly the same way?  As explained, the
> difference single-trx / dual-trx and downlink power control might explain it.

Yes, other stations are configured exactly the same way. 

> otherwise, if configuration of bs-11, openbsc and the bs11 firmware is
> identical, it might well be a hardware issue.  But I don't get why it would
> be related to the first call or not...

I am confused. I did not observe this effect earlier on this station. And I do not
observe it on other stations. I also don't know why this effect appears after
the first call. It really seems to be a hardware problem.

Best Regards,
Sergey.




From andreas at galauner.de  Sat Dec  4 23:28:27 2010
From: andreas at galauner.de (Andreas Galauner)
Date: Sun, 05 Dec 2010 00:28:27 +0100
Subject: Calls are "stuck"
Message-ID: <4CFACE9B.7080909@galauner.de>

Hello everybody,
this is my first post to this list. I've been reading it for a while now 
and I'm finally trying to get a bit deeper into GSM.

We have a BS11 in the C4 (Chaos Computer Club Cologne) which I got fully 
working on Thursday this week.
We had several mobile phones in the network and called each other and we 
could send and receive sms. All fine.

Today I wanted to test another few things and everything got weird:
I have 2 mobile phones authenticated in the network. One phone can call 
the other one, it rings and after accepting the call, the first still 
plays the "ringing sound", while everything on the second is silent.
Vice versa, if I call the first mobile from the second, it dials 
endlessly. Sometimes OpenBSC segfaults. Before it does that, it tells me 
on the console that timer T303 expired.

Another thing are those masses of "mISDN_send: error -12" messages in 
the kernel log. We got those on Thursday, too but they weren't important 
to us, because everything worked.

Nevertheless, sending and receiving SMS still works.

Also, the network sometimes is hard to find on the mobile phones. We 
blame a bad calibrated oscillator for that. As soon as we got an HFC-S 
card, we will try to recalibrate it.
Is it possible that all those problems show up because of the 
oscillator? And why did it work really well on Thursday?

So far, I tried a few obvious things like rebooting, both the computer 
and the BS11, cleaning and recompiling everything and I even deleted the 
old HLR database.
I really don't know what to do else. <Insert helpless cry here> ;)
Does anybody of you have an idea what I can try?

We are running the latest OpenBSC from the git on a Debian testing with 
a stock 2.6.32-5 kernel on i686.

Greetings,
Andy



From spaar at mirider.augusta.de  Sun Dec  5 08:17:13 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Sun, 05 Dec 2010 08:17:13 
Subject: Calls are "stuck"
Message-ID: <4cfb4a89.mirider@mirider.augusta.de>

Hello Andreas,

On Sun, 05 Dec 2010 00:28:27 +0100, "Andreas Galauner" <andreas at galauner.de> wrote:
> 
> Also, the network sometimes is hard to find on the mobile phones. We 
> blame a bad calibrated oscillator for that. As soon as we got an HFC-S 
> card, we will try to recalibrate it.

As I mentioned here a few days before, its usually enough to
reset the PLL "work value" to its "set value" with bs11_config
("pll_workvalue" command) and set the PLL to standalone
("pll_standalone" command).

> Is it possible that all those problems show up because of the 
> oscillator? And why did it work really well on Thursday?

I don't think that the problems with calls are related to the
oscillator, I would expect that this is related to the misdn
errors you see. Maybe the ISDN cable termination is not set
properly ?

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From kobayashi_maru at onlinehome.de  Tue Dec  7 16:18:35 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Tue, 07 Dec 2010 17:18:35 +0100
Subject: multi-drop-configuration
Message-ID: <1291738715.3633.11.camel@r-9djhc747gf8b40ha>

hello
the cables are built, now i want to use 2 bs11 in multi drop config. how
do i connect the 2 bs11? the e1 comes from the pc to the 1st bs11 left
half, left tx, right rx(front view). now i'm on the right half: to which
port are the 2 bnc port from the 1st to the 2nd bs11 to be connected? i
tried the 2 possible combinations, didn't work (with the
openbsc.cfg.2-2). the 2 bs11 are both set to tei=25 (bs11_config told me
so)
a schematic would be perfect.

second problem: the timer instructions in the openbsc.cfg.2-2 are not
executable, the bsc_hack program stops there. i had to remove them.
what's the matter with that, why don't these timer instructions work?

answers in german *very* welcome!
-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From laforge at gnumonks.org  Thu Dec  9 13:17:45 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 9 Dec 2010 21:17:45 +0800
Subject: multi-drop-configuration
In-Reply-To: <1291738715.3633.11.camel@r-9djhc747gf8b40ha>
References: <1291738715.3633.11.camel@r-9djhc747gf8b40ha>
Message-ID: <20101209131745.GB8300@prithivi.gnumonks.org>

Hi Thomas,

On Tue, Dec 07, 2010 at 05:18:35PM +0100, Thomas Ansorg wrote:
> the cables are built, now i want to use 2 bs11 in multi drop config. how
> do i connect the 2 bs11? the e1 comes from the pc to the 1st bs11 left
> half, left tx, right rx(front view). now i'm on the right half: to which
> port are the 2 bnc port from the 1st to the 2nd bs11 to be connected? i
> tried the 2 possible combinations, didn't work (with the
> openbsc.cfg.2-2). the 2 bs11 are both set to tei=25 (bs11_config told me
> so)

Did you make sure that the two BTS use different timeslots, and those are
the same timeslots that appear in the 

bts 0
  oml e1 line 1 timeslot 1 sub-slot full
bts 1
  oml e1 line 1 timeslot 6 sub-slot full

lines?

> second problem: the timer instructions in the openbsc.cfg.2-2 are not
> executable, the bsc_hack program stops there. i had to remove them.
> what's the matter with that, why don't these timer instructions work?

the config file format has changed since we last used the cfg.2-2, sorry
for that.  Feel free to submit a patch after you made it work :)

-- 
- 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 cr3 at cr3.us  Tue Dec  7 17:22:46 2010
From: cr3 at cr3.us (Chris Rankine)
Date: Tue, 7 Dec 2010 12:22:46 -0500
Subject: OpenBSC and Asterisk with NanoBTS and no ISDN
Message-ID: <AANLkTikFsQb8qxuqYG8AEgEc=Lt_07-F2fGkhBR0inbq@mail.gmail.com>

I am trying to get OpenBSC working with Asterisk for a class project.  I
have a NanoBTS DCS1800.  I was hoping to get this to work entirely over
Ethernet, as the server is running on a controlled VM cluster with no way of
getting an add-on ISDN card in.

I have attempted to follow the OpenBSC+LCR+Asterisks route.  But as
expected, LCR gives me issues when it does not find an ISDN card.  I am not
familiar with LCR to tweak it.  Can I use LCR without an ISDN card?  What
should I look into to get this done?

I have also attempted to modify the asterisk chan_openbsc code to comply
with the libosmo break off earlier this year.  With a few Makefile
adjustments, include a few more header files, and strip out some debuging
code, everything will compile.  However, asterisk seg faults when the module
loads.  The gdb output is:
Program received signal SIGSEGV, Segmentation fault.
0xb72fcd1d in cmd_execute_command_strict (vline=0x83d4c88, vty=0x83c2450,
cmd=0x0) at command.c:2000
2000            cmd_vector = vector_copy(cmd_node_vector(cmdvec,
vty->node));

I am not familar with this code, so all I can do is comment out things in an
attempt to debug.  Eventually I keep it from crashing, and the nanoBTS will
make contact with the driver.  However, since the code that gets commented
out also involves loading the cfg, the BTS does not get bootstraped. This is
all running on Gentoo, though I have also tried on Debian and Ubunto.

Any help would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101207/4655f8cf/attachment.htm>

From cleb at defcon-3.net  Tue Dec  7 18:27:41 2010
From: cleb at defcon-3.net (cleb at defcon-3.net)
Date: Tue, 7 Dec 2010 06:27:41 -1200 (GMT+12)
Subject: OpenBSC and Asterisk with NanoBTS and no ISDN
In-Reply-To: <AANLkTikFsQb8qxuqYG8AEgEc=Lt_07-F2fGkhBR0inbq@mail.gmail.com>
References: <AANLkTikFsQb8qxuqYG8AEgEc=Lt_07-F2fGkhBR0inbq@mail.gmail.com>
Message-ID: <66075458f35a9d49239c63265c0a5685.squirrel@defcon-3.net>

Have you been following this?
http://openbsc.osmocom.org/trac/wiki/OpenBSC_LCR

I recently configured a very similar setup with the latest git of OpenBSC,
libosmocore, mISDN,mISDNuser, and LCR. I used Asterisk 1.8, in which case
you'll need to checkout the asterisk_1_8 branch of LCR.

I know it seems a little counter-intuitive in an ethernet-only
environment, but you need to build the mISDN kernel modules so you can
create the loopback ISDN interfaces. These are needed for communication
between OpenBSC and LCR.

I configured LCR to pass all calls to Asterisk. If you need help with the
LCR/Asterisk configuration let me know. I found the following site helpful
for setting up my asterisk diaplans:
http://astbook.asteriskdocs.org/en/2nd_Edition/asterisk-book-html-chunk/asterisk-CHP-5.html

c

> I am trying to get OpenBSC working with Asterisk for a class project.  I
> have a NanoBTS DCS1800.  I was hoping to get this to work entirely over
> Ethernet, as the server is running on a controlled VM cluster with no way
> of
> getting an add-on ISDN card in.
>
> I have attempted to follow the OpenBSC+LCR+Asterisks route.  But as
> expected, LCR gives me issues when it does not find an ISDN card.  I am
> not
> familiar with LCR to tweak it.  Can I use LCR without an ISDN card?  What
> should I look into to get this done?
>
> I have also attempted to modify the asterisk chan_openbsc code to comply
> with the libosmo break off earlier this year.  With a few Makefile
> adjustments, include a few more header files, and strip out some debuging
> code, everything will compile.  However, asterisk seg faults when the
> module
> loads.  The gdb output is:
> Program received signal SIGSEGV, Segmentation fault.
> 0xb72fcd1d in cmd_execute_command_strict (vline=0x83d4c88, vty=0x83c2450,
> cmd=0x0) at command.c:2000
> 2000            cmd_vector = vector_copy(cmd_node_vector(cmdvec,
> vty->node));
>
> I am not familar with this code, so all I can do is comment out things in
> an
> attempt to debug.  Eventually I keep it from crashing, and the nanoBTS
> will
> make contact with the driver.  However, since the code that gets commented
> out also involves loading the cfg, the BTS does not get bootstraped. This
> is
> all running on Gentoo, though I have also tried on Debian and Ubunto.
>
> Any help would be appreciated.
>





From jmercury313 at gmail.com  Tue Dec  7 18:59:07 2010
From: jmercury313 at gmail.com (jason mercury)
Date: Tue, 7 Dec 2010 20:59:07 +0200
Subject: socket problem
Message-ID: <AANLkTik61PJUcEU0qONPpw2TnCAAenoX7MJM5rOcdFtd@mail.gmail.com>

Hi to all,

In order to execute two bsc_hack at the same time i have changed port for
oml link from nv_put_oml() function in ipaccess_config.c and i also changed
oml port from ipaccess.h . When i configure nanoBTS with ipaccess_config i
can establish two different oml link between two bsc_hack and two nanoBTS.
rslHowever, they can not establish  link at the same time. I could not find
where can i change rsl port of nanoBTS. I have searched the wiki and i could
not find a nanoBTS message to change the port specified for rsl link. Could
anyone give me some information about this?

Thanks.
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101207/581f7019/attachment.htm>

From 246tnt at gmail.com  Tue Dec  7 21:22:21 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 7 Dec 2010 22:22:21 +0100
Subject: socket problem
In-Reply-To: <AANLkTik61PJUcEU0qONPpw2TnCAAenoX7MJM5rOcdFtd@mail.gmail.com>
References: <AANLkTik61PJUcEU0qONPpw2TnCAAenoX7MJM5rOcdFtd@mail.gmail.com>
Message-ID: <AANLkTim+p5ye+ihSEo+F=EiQGQdoBZ5Br0ZMYvgcAZfX@mail.gmail.com>

> I could not find
> where can i change rsl port of nanoBTS. I have searched the wiki and i could
> not find a nanoBTS message to change the port specified for rsl link. Could
> anyone give me some information about this?

I already told you in a previos message : See nv_put_prim_oml in
ipaccess-config.c

The current tools don't support setting it. (we send 0 as port which
means "default" I guess). So you need to modify ipaccess-config to
allow taking the port to configure as parameter.

Cheers,

    Sylvain



From bertoncello at netzing.de  Wed Dec  8 14:26:40 2010
From: bertoncello at netzing.de (Luca Bertoncello)
Date: Wed, 8 Dec 2010 15:26:40 +0100
Subject: Compiling OpenBSC to use an extern MSC
Message-ID: <20101208152640.1ec58d3e@Luca>

Hi, list!

I'd like to try to compile OpenBSC with the A-over-IP in order to
connect it to a real MSC.
I found this document:

	http://openbsc.osmocom.org/trac/wiki/OpenBSCWithSCCP

But when I try to get the branch I get an error:

$ git checkout -b on-waves/bsc-master origin/bsc-master
git checkout: updating paths is incompatible with switching branches/forcing
Did you intend to checkout 'origin/bsc-master' which can not be
resolved as commit?

Is now this project in another branch? Can someone say me, what I have to
do to compile it?

Thanks a lot!
-- 
_______________________________________________________________________
Luca Bertoncello
Entwicklung                               Mail:  bertoncello at netzing.de 


NETZING Solutions AG                      Tel.:  0351/41381 - 23
Fr?belstr. 57, 01159 Dresden              Fax:   0351/41381 - 12
_______________________________________________________________________

Impressum: 
NETZING Solutions AG  -  Fr?belstra?e 57   -   01159 Dresden
Sitz der Gesellschaft Amtsgericht Dresden HRB 18926
Vorstand  Dieter Schneider  -  Aufsichtsratsvorsitzender Volker Kanitz
USt.Id DE211326547  Mail:  netzing.ag at netzing.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101208/a32fb339/attachment.bin>

From holger at freyther.de  Wed Dec  8 15:12:53 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 08 Dec 2010 16:12:53 +0100
Subject: Compiling OpenBSC to use an extern MSC
In-Reply-To: <20101208152640.1ec58d3e@Luca>
References: <20101208152640.1ec58d3e@Luca>
Message-ID: <4CFFA075.6050406@freyther.de>

On 12/08/2010 03:26 PM, Luca Bertoncello wrote:
> Hi, list!

> 
> Is now this project in another branch? Can someone say me, what I have to
> do to compile it?

Well,
you should be able to answer this yourself. You can type git branch to see
your local branches and git branch -a to see all branches. Also the asymmetry
of on-waves/bsc-master and origin/bsc-master looks suspicious..

Besides that OpenBSC master should come with a working BSC that can be hooked
to a MSC. What are you going to try with this?



From bertoncello at netzing.de  Thu Dec  9 07:50:23 2010
From: bertoncello at netzing.de (Luca Bertoncello)
Date: Thu, 9 Dec 2010 08:50:23 +0100
Subject: Compiling OpenBSC to use an extern MSC
In-Reply-To: <4CFFA075.6050406@freyther.de>
References: <20101208152640.1ec58d3e@Luca>
	<4CFFA075.6050406@freyther.de>
Message-ID: <20101209085023.7e284bc7@Luca>

Am Wed, 08 Dec 2010 16:12:53 +0100
schrieb Holger Hans Peter Freyther <holger at freyther.de>:

> you should be able to answer this yourself. You can type git branch

If I could, I don't ask... :D

> to see your local branches and git branch -a to see all branches.
> Also the asymmetry of on-waves/bsc-master and origin/bsc-master looks
> suspicious..

OK, I tried to switch to another branch with:

	git checkout -b on-waves/bsc-master origin/on-waves/bsc-master

I can just hope, that this is the right branch...
Unfortunately, I have another problem...
When I run the configure file I get this error:

checking for LIBOSMOSCCP... configure: error: Package requirements
(libosmo-sccp >= 0.0.3) were not met:

No package 'libosmo-sccp' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

I try to search for this library in the libosmocore repository, and to
check if there is another branch in this repository, too, but I didn't
found anything.

Could someone say me, where can I found this library?

> Besides that OpenBSC master should come with a working BSC that can
> be hooked to a MSC. What are you going to try with this?

As I said, I have a real MSC and I'd like to have OpenBSC just running
as BSC and speaking with this MSC.
Is it not, what this branch does?

Thanks
-- 
_______________________________________________________________________
Luca Bertoncello
Entwicklung                               Mail:  bertoncello at netzing.de 


NETZING Solutions AG                      Tel.:  0351/41381 - 23
Fr?belstr. 57, 01159 Dresden              Fax:   0351/41381 - 12
_______________________________________________________________________

Impressum: 
NETZING Solutions AG  -  Fr?belstra?e 57   -   01159 Dresden
Sitz der Gesellschaft Amtsgericht Dresden HRB 18926
Vorstand  Dieter Schneider  -  Aufsichtsratsvorsitzender Volker Kanitz
USt.Id DE211326547  Mail:  netzing.ag at netzing.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101209/a4cedaa7/attachment.bin>

From laforge at gnumonks.org  Thu Dec  9 13:01:02 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 9 Dec 2010 21:01:02 +0800
Subject: Compiling OpenBSC to use an extern MSC
In-Reply-To: <20101209085023.7e284bc7@Luca>
References: <20101208152640.1ec58d3e@Luca> <4CFFA075.6050406@freyther.de>
	<20101209085023.7e284bc7@Luca>
Message-ID: <20101209130102.GA8300@prithivi.gnumonks.org>

Hi Luca,

On Thu, Dec 09, 2010 at 08:50:23AM +0100, Luca Bertoncello wrote:
> > you should be able to answer this yourself. You can type git branch
> 
> If I could, I don't ask... :D

well, we seem to expect general familiarity in working with git... most
Free Software developers are used to it by now.

> No package 'libosmo-sccp' found
>
> Could someone say me, where can I found this library?

All osmocom projects (except openbsc, for historical reasons) are available
from http://git.osmocom.org/

> > Besides that OpenBSC master should come with a working BSC that can
> > be hooked to a MSC. What are you going to try with this?
> 
> As I said, I have a real MSC and I'd like to have OpenBSC just running
> as BSC and speaking with this MSC.
> Is it not, what this branch does?

This is what osmo-bsc does, whether or not you use the bsc-master or the master
branch.

-- 
- 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 bertoncello at netzing.de  Thu Dec  9 13:26:37 2010
From: bertoncello at netzing.de (Luca Bertoncello)
Date: Thu, 9 Dec 2010 14:26:37 +0100
Subject: Compiling OpenBSC to use an extern MSC
In-Reply-To: <20101209130102.GA8300@prithivi.gnumonks.org>
References: <20101208152640.1ec58d3e@Luca> <4CFFA075.6050406@freyther.de>
	<20101209085023.7e284bc7@Luca>
	<20101209130102.GA8300@prithivi.gnumonks.org>
Message-ID: <20101209142637.509f244a@Luca>

Am Thu, 9 Dec 2010 21:01:02 +0800
schrieb Harald Welte <laforge at gnumonks.org>:

> > Could someone say me, where can I found this library?
> 
> All osmocom projects (except openbsc, for historical reasons) are
> available from http://git.osmocom.org/

OK, thanks!

> > > Besides that OpenBSC master should come with a working BSC that
> > > can be hooked to a MSC. What are you going to try with this?
> > 
> > As I said, I have a real MSC and I'd like to have OpenBSC just
> > running as BSC and speaking with this MSC.
> > Is it not, what this branch does?
> 
> This is what osmo-bsc does, whether or not you use the bsc-master or
> the master branch.

Do you mean, that I don't need to compile BSC in other way to have it
speaking with a real MSC?

Thanks
Luca
-- 
_______________________________________________________________________
Luca Bertoncello
Entwicklung                               Mail:  bertoncello at netzing.de 


NETZING Solutions AG                      Tel.:  0351/41381 - 23
Fr?belstr. 57, 01159 Dresden              Fax:   0351/41381 - 12
_______________________________________________________________________

Impressum: 
NETZING Solutions AG  -  Fr?belstra?e 57   -   01159 Dresden
Sitz der Gesellschaft Amtsgericht Dresden HRB 18926
Vorstand  Dieter Schneider  -  Aufsichtsratsvorsitzender Volker Kanitz
USt.Id DE211326547  Mail:  netzing.ag at netzing.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101209/041c1ad1/attachment.bin>

From holger at freyther.de  Thu Dec  9 14:33:05 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 09 Dec 2010 15:33:05 +0100
Subject: Compiling OpenBSC to use an extern MSC
In-Reply-To: <20101209142637.509f244a@Luca>
References: <20101208152640.1ec58d3e@Luca>
	<4CFFA075.6050406@freyther.de>	<20101209085023.7e284bc7@Luca>	<20101209130102.GA8300@prithivi.gnumonks.org>
	<20101209142637.509f244a@Luca>
Message-ID: <4D00E8A1.1010004@freyther.de>

On 12/09/2010 02:26 PM, Luca Bertoncello wrote:

>> This is what osmo-bsc does, whether or not you use the bsc-master or
>> the master branch.
> 
> Do you mean, that I don't need to compile BSC in other way to have it
> speaking with a real MSC?

Hi,

master contains an application called 'osmo-bsc'. I was writing an
introduction to it a couple of days/weeks back. If you do ./configure --help
you will see it... it requires libosmo-sccp.

holger



From ozmank8 at gmail.com  Thu Dec  9 16:48:30 2010
From: ozmank8 at gmail.com (tejas oza)
Date: Thu, 9 Dec 2010 17:48:30 +0100
Subject: Successfully Implemented SMS capable MSC & VLR
Message-ID: <AANLkTi=sz5kX6xNOfDq5fNqBH-1+jrUMu8_ZvkPwOJ0r@mail.gmail.com>

Hi Holger,

If you remember we are the students from Uppsala University Sweden.
I am glad to inform you that we have done with our project. We have
successfully implemented SMS capable MSC and VLR in Erlang, integrated with
Mobile Arts SMSC, HLR and OpenBSC.
We are also planning to make our project Open source and will inform you as
soon as we will finalize it.

-- 
*Thanks & Regards

Tejas  Oza
Masters in Computer Science,
Department of Information Technology,
Uppsala University, Sweden.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101209/6da5bb63/attachment.htm>

From holger at freyther.de  Fri Dec 10 04:43:07 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 10 Dec 2010 05:43:07 +0100
Subject: Successfully Implemented SMS capable MSC & VLR
In-Reply-To: <AANLkTi=sz5kX6xNOfDq5fNqBH-1+jrUMu8_ZvkPwOJ0r@mail.gmail.com>
References: <AANLkTi=sz5kX6xNOfDq5fNqBH-1+jrUMu8_ZvkPwOJ0r@mail.gmail.com>
Message-ID: <4D01AFDB.40703@freyther.de>

On 12/09/2010 05:48 PM, tejas oza wrote:
> Hi Holger,
> 
> If you remember we are the students from Uppsala University Sweden.
> I am glad to inform you that we have done with our project. We have
> successfully implemented SMS capable MSC and VLR in Erlang, integrated with
> Mobile Arts SMSC, HLR and OpenBSC.
> We are also planning to make our project Open source and will inform you as
> soon as we will finalize it.

Hi tejas,

congratulation! I hope you enjoyed the project and learned a lot about GSM,
Erlang and Project Management. I am now very curious to see your sourcecode.

regards
	holger



From laforge at gnumonks.org  Fri Dec 10 11:43:12 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 10 Dec 2010 19:43:12 +0800
Subject: Successfully Implemented SMS capable MSC & VLR
In-Reply-To: <4D01AFDB.40703@freyther.de>
References: <AANLkTi=sz5kX6xNOfDq5fNqBH-1+jrUMu8_ZvkPwOJ0r@mail.gmail.com>
	<4D01AFDB.40703@freyther.de>
Message-ID: <20101210114312.GX13457@prithivi.gnumonks.org>

Hi all,

On Fri, Dec 10, 2010 at 05:43:07AM +0100, Holger Hans Peter Freyther wrote:

> congratulation! I hope you enjoyed the project and learned a lot about GSM,
> Erlang and Project Management. I am now very curious to see your sourcecode.

same here, I cannot wait to see the source code and play with it!

-- 
- 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 laforge at gnumonks.org  Thu Dec  9 17:31:54 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 10 Dec 2010 01:31:54 +0800
Subject: Control Interface
Message-ID: <20101209173154.GQ13457@prithivi.gnumonks.org>

Hi Daniel,

i am occasionally browsing the commitlog of the daniel/controlif branch
and am wondering what exactly is happening there.

It seems much more to me that 'controlif' is about reimplementing a lot
of the functionality that already exists in the VTY, which I think is bad.

My original understanding of the idea of SNMP support was:
1) we mostly want to export counters that we already have, but in
   a consistent/machine-parseable way.  This is read-only
2) we may want to have traps 
3) we have some (few!) things like rf_lock which should be issued (written)
   by the external SNMP process.

Has the focus changed since this last discussion?  Can anyone explain why
that is?

Even if we suddenly have a need for a lot of write/modify type settings from
the SNMP side, we should not have two ways how to modify a single parameter
inside OpenBSC.  In that case we may need some code that can sort-of
automatically 'export' all controlif parameter to the VTY, and remove the
current code that sets this parameter from the VTY.

Any ideas?

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 holger at freyther.de  Fri Dec 10 02:29:58 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 10 Dec 2010 03:29:58 +0100
Subject: Control Interface
In-Reply-To: <20101209173154.GQ13457@prithivi.gnumonks.org>
References: <20101209173154.GQ13457@prithivi.gnumonks.org>
Message-ID: <4D0190A6.3070808@freyther.de>

On 12/09/2010 06:31 PM, Harald Welte wrote:
> Hi Daniel,
> 

> 
> Has the focus changed since this last discussion?  Can anyone explain why
> that is?

The focus has not changed. There are two things I want out of it. Get
statistics from the BSCs (we will query the nat/mux, which will..), turn off
RF via the nat/mux.

I asked Daniel to start with something easy (this is why we have plenty of
strcmp and if/else), it probably just appeared easy to add get/set for
existing properties. As the second step I asked Daniel to somehow consolidate
this and look at if we can use things from the VTY.


> Even if we suddenly have a need for a lot of write/modify type settings from
> the SNMP side, we should not have two ways how to modify a single parameter
> inside OpenBSC.  In that case we may need some code that can sort-of
> automatically 'export' all controlif parameter to the VTY, and remove the
> current code that sets this parameter from the VTY.

I agree that there should not be two ways in the long run. To ease Daniels
work and have progress I asked him to ignore this problem of duplication for
now and move things forward.

Personally I would like to see the branch to be in a state that it is solving
the use case that we have discussed. This way we know what we will need from
the code, as the second step I would look into integration and see how we will
deal with the VTY overlap.

holger



From laforge at gnumonks.org  Sat Dec 11 03:28:12 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 11 Dec 2010 11:28:12 +0800
Subject: [ADM] Please try to avoid merges in the git tree
Message-ID: <20101211032812.GC26844@prithivi.gnumonks.org>

Hi all,

this is just a general request to everyone with git commit access on
the OpenBSC / Osmocom repositories.

I would appreciate to restrict the use of 'git merge' to the absolute
minimum neccessarry, as it makes the commitlog and timeline much harder
to understand.

If you're working on some private branch on a particular feature, please
rebase that private branch on current master before pushing the changes.

Thanks!

-- 
- 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 peter at stuge.se  Sat Dec 11 20:55:49 2010
From: peter at stuge.se (Peter Stuge)
Date: Sat, 11 Dec 2010 21:55:49 +0100
Subject: [ADM] Please try to avoid merges in the git tree
In-Reply-To: <20101211032812.GC26844@prithivi.gnumonks.org>
References: <20101211032812.GC26844@prithivi.gnumonks.org>
Message-ID: <20101211205549.21419.qmail@stuge.se>

Harald Welte wrote:
> If you're working on some private branch on a particular feature, please
> rebase that private branch on current master before pushing the changes.

Avoid automatic merges by setting rebase=true on branches.
(Equivalent of git pull --rebase)


//Peter



From mailman at lists.gnumonks.org  Sat Dec 11 10:37:24 2010
From: mailman at lists.gnumonks.org (mailman at lists.gnumonks.org)
Date: Sat, 11 Dec 2010 11:37:24 +0100
Subject: Bounce action notification
Message-ID: <mailman.149.1292063844.21527.openbsc@lists.gnumonks.org>

This is a Mailman mailing list bounce action notice:

    List:       OpenBSC
    Member:     Barrie.Mcclarity at zeusmail.org
    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.gnumonks.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: Sat, 11 Dec 2010 11:37:22 +0100
Size: 3326
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101211/c4655f01/attachment.eml>

From kobayashi_maru at onlinehome.de  Sun Dec 12 08:10:03 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Sun, 12 Dec 2010 09:10:03 +0100
Subject: tei and oml ts assignment
Message-ID: <1292141403.3624.8.camel@r-9djhc747gf8b40ha>

hello
how do i set the tei and timeslot for a bs11? of course i know
bs11_config and the tei_oml parameter, but it don't seem to work. i
tried ./bs11_config tei_oml 4 30 and 30 4 (to set the timeslot to 4 and
tei to 30). but when i query the bs11, it still says timeslot=1 and
tei=25. I tried it with and without disconnection of the bs11.
how do i call bs11_config correct for that purpose?

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From laforge at gnumonks.org  Sun Dec 12 09:24:38 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 12 Dec 2010 10:24:38 +0100
Subject: tei and oml ts assignment
In-Reply-To: <1292141403.3624.8.camel@r-9djhc747gf8b40ha>
References: <1292141403.3624.8.camel@r-9djhc747gf8b40ha>
Message-ID: <20101212092438.GX26844@prithivi.gnumonks.org>

Hi Thomas,

On Sun, Dec 12, 2010 at 09:10:03AM +0100, Thomas Ansorg wrote:

> how do i set the tei and timeslot for a bs11? of course i know
> bs11_config and the tei_oml parameter, but it don't seem to work. i
> tried ./bs11_config tei_oml 4 30 and 30 4 (to set the timeslot to 4 and
> tei to 30). but when i query the bs11, it still says timeslot=1 and
> tei=25. I tried it with and without disconnection of the bs11.
> how do i call bs11_config correct for that purpose?

it seems it's still hard-coded in the source code:

see line 559 of bs11_config.c:
         abis_nm_bs11_conn_oml_tei(g_bts, 0, 1, 0xff, TEI_OML);

you can change the source to use TS != 1 and any numeric value instead of TEI_OML

Feel free to fix this properly and make the timeslot and TEI a commandline
argument and send us a patch!

-- 
- 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 kobayashi_maru at onlinehome.de  Sun Dec 12 10:57:57 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Sun, 12 Dec 2010 11:57:57 +0100
Subject: wiring scheme required
Message-ID: <1292151477.5529.4.camel@r-9djhc747gf8b40ha>

hello
i still don't know how 2 bs11 in multi-drop config are connected
correctly. nothing's to find on openbsc.com.
someone may send a schematic to me, please. 

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From laforge at gnumonks.org  Sun Dec 12 16:01:22 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 12 Dec 2010 17:01:22 +0100
Subject: How RRLP 'MS assisted GPS' really works
In-Reply-To: <4cff479c.mirider@mirider.augusta.de>
References: <4cff479c.mirider@mirider.augusta.de>
Message-ID: <20101212160122.GF26844@prithivi.gnumonks.org>

Hi all,

I believe I have finally figured out how this 'MS assisted' RRLP mode works.

Not sure if I am the first or the last one to understand it, just wanted to
share what I know:

Just to recap, RRLP has three modes:
 * E-OTD of different BTS signals (AFAIK not used)
 * MS-based GPS positioning (optionally with assistance data from the GSM net)
 * MS-assisted GPS positioning (what I'm talking about now)

On Wed, Dec 08, 2010 at 08:53:48AM +0000, Dieter Spaar wrote:
> This is from the RRLP specification, those are some of the data for
> assisted measurements (those "low-level" data I refered to):
> 
>  Data sent to the phone (for every satellite)
> 
>     Doppler
>     Doppler uncertainty
>     Code phase
>     Int code phase
>     GPS bit number
>     Code phase search window
>     Azimuth
>     Elevation

Basically this tells the phone:
* which doppler shift to expect (result from movement speed of satellite),
  typically in the range of +/- 5kHz of the GPS L1 frequency
* the 'code phase', i.e. the difference between a certain GSM bit (in a
  specified timeslot/frame number/bcch carrier) and a specified GPS bit
  (TOW, bit, chip, ...)
* which azimuth/elevation to expect (not sure how the phone should use this,
  unless it knows the orientation of the antenna and has a MIMO receiver)

what happens now is that the MS will lock onto one specific satellite. It can
do this quickly, as it altready knows 
 * a certain doppler frequency shift (range)
   in which it should apply a known scrambling code sequence (the satellite
   number corresponds to a given pseudo-random sequence), and the
 * expected 'code phase', i.e. the difference between the time at which a
   certain bit is transmitted on the BCCH carrier of a GSM cell, and which chip
   of the given satellite will be expected to be received within the GSM cell.

Once it acquires the signal, it will measure the number of whole (and
fractional) GPS chips that it has observed between
 * the start of a given GSM frame number (called 'reference frame') and the
 * wrap of the GPS 1023bit pseudo-random sequence

This is then sent back to the network:

>  Data sent back from the phone (for every satellite)
> 
>     Carrier Noise Ratio
>     Doppler

this is the actually measured doppler shift for this satellite in the MS receiver

>     Whole Chips (0..1022)
>     Fractional Chips (0..1023)

and this is the number of GPS chips between the wrap of the GSM reference frame
number and the wrap of the GPS 1023 bit chip sequence.  The specification
states "The resolution of the fractional portion is approximately 0.3m"

So all the phone actually ever does is measurement of timing difference.  It
will never try to decode the actual GPS signal at all.

The network (SMLC) can then compute the GPS position, as it can get the timing
information for all the satellites the phone has received, and it already knows
all the other data (almanac/ephemeris/...) from a local database and/or its own
reference receiver.

Pretty interesting.  If only I had the time to implement it ;)

-- 
- 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 spaar at mirider.augusta.de  Sun Dec 12 17:42:12 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Sun, 12 Dec 2010 17:42:12 
Subject: How RRLP 'MS assisted GPS' really works
Message-ID: <4d050974.mirider@mirider.augusta.de>

Hello Harald,

On Sun, 12 Dec 2010 17:01:22 +0100, "Harald Welte" <laforge at gnumonks.org> wrote:
> 
> Pretty interesting.  If only I had the time to implement it ;)

I don't think that implementing is the hard part, debugging is. You
send data which might be wrong due to some bugs in your code into a
"black-box" which does something with the data. The "black-box" will
not tell you if your data are wrong, if they are, it might just take
longer till any results are returned. So you are not sure if you are
doing the things right.

I conclude the above from my experience so far: Even phones with very
extensive tracing capabilities don't tell you much about what is going
on during their GPS position calculations. And at least I am not aware
of a GPS server I have access to who will provide those data required 
for an "MS-assisted" measurement so that one could compare the own 
calculation against a reference.

If someone know about a server providing those data (I am not
talking of things like "almanac" or "ephemeris" here) or knows
about existing source code to do the calculation, I would like
to know.

BTW, the book "Server-Side GPS and Assisted-GPS in Java" contains
a few nice chapters, one should not care about "Java" in the title,
only the examples are written in Java.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From vogelchr at vogel.cx  Sun Dec 12 18:22:41 2010
From: vogelchr at vogel.cx (Christian Vogel)
Date: Sun, 12 Dec 2010 19:22:41 +0100
Subject: How RRLP 'MS assisted GPS' really works
In-Reply-To: <4d050974.mirider@mirider.augusta.de>
References: <4d050974.mirider@mirider.augusta.de>
Message-ID: <op.vnl5b2jpunbdei@enormity.dillberg.com>

Hi Dieter,

> of a GPS server I have access to who will provide those data required
> for an "MS-assisted" measurement so that one could compare the own
> calculation against a reference.

There are a few. My Trimble Thunderbolt can give you doppler and
codephase (gps often calls it "pseudorange").

> If someone know about a server providing those data (I am not
> talking of things like "almanac" or "ephemeris" here) or knows
> about existing source code to do the calculation, I would like
> to know.

there are a few open-source GPS implementations out there. The
"software defined radio" part only determines the pseudoranges
(e.g. the chips' phase with respect to each other) to the part
that does the actual trigonometric calculations, so every
implementation should be useable for that purpose.

Sparkfun sells "only the frontend" (mixer, 1-bit ADC, USB)
with sourcecode available in a book and on DVD (WTF?!)

---> http://www.sparkfun.com/products/8238

Then, I found a "GPL-GPS" Project at
     http://gps.psas.pdx.edu/
with a repository at
     http://svn.psas.pdx.edu/svn/psas/trunk/gps/gpl-gps/

There's actually quite a lot of information out there,
but there also seem to be quite a lot of half-abandoned
projects (and a few seem to have vanished since the last time I had
an interest in it around 2005).

         Chris



From dburgess at jcis.net  Sun Dec 12 19:24:22 2010
From: dburgess at jcis.net (David A. Burgess)
Date: Sun, 12 Dec 2010 11:24:22 -0800
Subject: How RRLP 'MS assisted GPS' really works
In-Reply-To: <op.vnl5b2jpunbdei@enormity.dillberg.com>
References: <4d050974.mirider@mirider.augusta.de>
	<op.vnl5b2jpunbdei@enormity.dillberg.com>
Message-ID: <90780D42-FF4E-4BFD-8456-3C35A06CADED@jcis.net>


Selling the hardware and software separately is probably a tactic to  
avoid patent infringement.

On Dec 12, 2010, at 10:22 AM, Christian Vogel wrote:

>
> Sparkfun sells "only the frontend" (mixer, 1-bit ADC, USB)
> with sourcecode available in a book and on DVD (WTF?!)
>
> ---> http://www.sparkfun.com/products/8238


David A. Burgess
Kestrel Signal Processing, Inc.




From spaar at mirider.augusta.de  Sun Dec 12 21:01:54 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Sun, 12 Dec 2010 21:01:54 
Subject: How RRLP 'MS assisted GPS' really works
Message-ID: <4d053842.mirider@mirider.augusta.de>

Hello Christian,

Thank you very much for the links.

On Sun, 12 Dec 2010 19:22:41 +0100, "Christian Vogel" <vogelchr at vogel.cx> wrote:
> 
> There are a few. My Trimble Thunderbolt can give you doppler and
> codephase (gps often calls it "pseudorange").

Thats interesting, the ublox 5 GPS module I was playing with only
provides those data if you have the so called "raw data premium
feature" enabled (whatever this means, I have not yet looked at
the details).

> Sparkfun sells "only the frontend" (mixer, 1-bit ADC, USB)
> with sourcecode available in a book and on DVD (WTF?!)
> 
> ---> http://www.sparkfun.com/products/8238

Interesting device, I wasn't aware of it (I know about the book).
Is the Source Code of the book available ? So far I have only
seen some material for download at the following site, not sure
if there is the whole content of the DVD:

   http://kom.aau.dk/project/softgps/

Would be interesting to use the code with a USRP.

> There's actually quite a lot of information out there,
> but there also seem to be quite a lot of half-abandoned
> projects (and a few seem to have vanished since the last time I had
> an interest in it around 2005).

I had a short look at some but always had the impression that
it is not exactly what I am looking for. I guess I should try
to get a GPS receiver which provides the required data, thats
probably the easiest approach.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From vogelchr at vogel.cx  Sun Dec 12 21:06:48 2010
From: vogelchr at vogel.cx (Christian Vogel)
Date: Sun, 12 Dec 2010 22:06:48 +0100
Subject: GPS calculation source code
In-Reply-To: <4d053842.mirider@mirider.augusta.de>
References: <4d053842.mirider@mirider.augusta.de>
Message-ID: <op.vnmcxmcsunbdei@enormity.dillberg.com>

Hi Dieter,

> Interesting device, I wasn't aware of it (I know about the book).
> Is the Source Code of the book available ? So far I have only
> seen some material for download at the following site, not sure
> if there is the whole content of the DVD:
>
>    http://kom.aau.dk/project/softgps/

The (blue) receiver is the old dongle sold by SparkFun during
the last years. I only remember from visiting their website, but
don't own one. I don't know if the DVD contains more than
the matlab code that can be downloaded.

>> There's actually quite a lot of information out there,
>> but there also seem to be quite a lot of half-abandoned
>> projects (and a few seem to have vanished since the last time I had
>> an interest in it around 2005).

This site (from 2003)...
     http://home.earthlink.net/~cwkelley/
...explains the calculation in the "Operations" section, it's
a rather concise summary of the basic math involved.

> I had a short look at some but always had the impression that
> it is not exactly what I am looking for. I guess I should try
> to get a GPS receiver which provides the required data, thats
> probably the easiest approach.

http://home.tiscali.nl/samsvl/oemtable.htm has a table comparing
various chipsets, some are quite ancient.

         Chris



From paul at kristianpaul.org  Sun Dec 12 23:15:29 2010
From: paul at kristianpaul.org (Cristian Paul =?iso-8859-1?Q?Pe=F1aranda?= Rojas)
Date: Sun, 12 Dec 2010 18:15:29 -0500
Subject: GPS calculation source code
In-Reply-To: <op.vnmcxmcsunbdei@enormity.dillberg.com>
References: <4d053842.mirider@mirider.augusta.de>
	<op.vnmcxmcsunbdei@enormity.dillberg.com>
Message-ID: <20101212231529.GA2383@micro.kristianpaul.local>

On Sun, Dec 12, 2010 at 10:06:48PM +0100, Christian Vogel wrote:
> >>There's actually quite a lot of information out there,
> >>but there also seem to be quite a lot of half-abandoned
> >>projects (and a few seem to have vanished since the last time I had
> >>an interest in it around 2005).

In the hardware side i think this deserver a look:

 http://www.weblab.dlr.de/rbrt/GpsNav/Namuru/Namuru.html

In sofware, gps-sdr

 http://gps-sdr.com (website seems down since last weeek, hope get back
 soon)
 http://www.ctae.org/sdr/ 

Have samples, code and doc

If you have question about code or something else just drop a mail 
to then (CTAE). most of the time will respond

saludos !

Cristian Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101212/81c95542/attachment.bin>

From kobayashi_maru at onlinehome.de  Tue Dec 14 09:21:06 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Tue, 14 Dec 2010 10:21:06 +0100
Subject: multi drop still don't work
Message-ID: <1292318466.5252.9.camel@r-9djhc747gf8b40ha>

hello
i set one bs11 to ts 1, tei 25 and the other one to ts 6, tei 25(also
tried 26 with the 2nd), according to openbsc.cfg.2-2. the cabling is
also correct, due to a schematic from harald. but the 2nd bs11 not
recognised.
the funny thing ist, when i configure the 2nd bs11 exactly like the 1st
one(the working one, ts 1, tei 25), it don't work. the parameter from
bs11_config query are the same like the 1st, but i don't get the abis
link up

-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From laforge at gnumonks.org  Tue Dec 14 11:17:56 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 14 Dec 2010 12:17:56 +0100
Subject: multi drop still don't work
In-Reply-To: <1292318466.5252.9.camel@r-9djhc747gf8b40ha>
References: <1292318466.5252.9.camel@r-9djhc747gf8b40ha>
Message-ID: <20101214111756.GB32316@prithivi.gnumonks.org>

There is not a single post of you that included all the information,
like:
* tty output of "bs11_config dump" of both the BTS
* tty output of "bs11_config" regarding the A-bis link state of both BTS
* detailed list of the procedures that you have already tried, like switching
  rx/tx wires
* detailed explanation how you have configured mISDN and the hfcmulti
  driver to run multiple d-channels on one E1 link, i.e. applying
  linux-2.6.30-hfcmulti-multibts.patch and specifying the correct module
  parameters

If you really want to enable us to help you properly, please make sure you
are as detailed and as verbose as possible!

-- 
- 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 laforge at gnumonks.org  Tue Dec 14 12:16:05 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 14 Dec 2010 13:16:05 +0100
Subject: multi drop still don't work
In-Reply-To: <20101214111756.GB32316@prithivi.gnumonks.org>
References: <1292318466.5252.9.camel@r-9djhc747gf8b40ha>
	<20101214111756.GB32316@prithivi.gnumonks.org>
Message-ID: <20101214121605.GE32316@prithivi.gnumonks.org>

I've now added support to print the BPORT configuration within bs11_config,
please use git revision 5f5189e658a146ff651103ceacfb151e92fe3fa1

This way you should be able to check if both BPORT objects exist and are
both set to multidrop mode.  On my single-BS11 setup it looks like this:

bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY

LMT LOGON: ACK

PHASE: 3 Normal               MBCCU0: Load        MBCCU1: Load        Abis-link: Restoring 

BS11 ATTRIBUTES:
        BS-11 ESN PCB Serial Number: 001115
        BS-11 ESN Hardware Code Number: 135-2044/03.07
        BS-11 ESN Firmware Code Number: 135-2044/03.07
        PLL Set Value=1110, Work Value=1110

SITE MANAGER ATTRIBUTES:
        E1 Channel: Port=0 Timeslot=1 (Full Slot)
        TEI: 25

BS11 Line Interface ATTRIBUTES:
        PLL Mode: Standalone

BS11 CCLK ATTRIBUTES:
        CCLK Accuracy: High (1)
        CCLK Type=0

BS11 Power Amplifier 0 ATTRIBUTES:
        TRX Power: 30mW (GSM)

BPORT0 ATTRIBUTES:
        Line Configuration: Star (0)
LMT LOGOFF: ACK

-- 
- 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 kobayashi_maru at onlinehome.de  Tue Dec 14 22:19:18 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Tue, 14 Dec 2010 23:19:18 +0100
Subject: problems with 2nd bs11| verbose mode
Message-ID: <1292365158.7419.9.camel@r-9djhc747gf8b40ha>

hi
to enable as many as possible of you to help me, heres what bs11_config
said (the old version):
bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY

LMT LOGON: ACK

PHASE: 3 Normal               MBCCU0: Load        MBCCU1: Load
Abis-link: Restoring 

BS11 ATTRIBUTES:
        BS-11 ESN PCB Serial Number: 
        BS-11 ESN Hardware Code Number: 
        BS-11 ESN Firmware Code Number: 
        PLL Set Value=1006, Work Value=1038

SITE MANAGER ATTRIBUTES:
        E1 Channel: Port=0 Timeslot=1 (Full Slot)
        TEI: 25

BS11 Line Interface ATTRIBUTES:
        PLL Mode: Standalone

BS11 CCLK ATTRIBUTES:
        CCLK Accuracy: Medium (0)
        

BS11 Power Amplifier 0 ATTRIBUTES:
        TRX Power: 30mW

LMT LOGOFF: ACK

thats the working one, the non-working says exactly the same, except
pll(1073) and work(1073)

the abis link on the 2nd is also up, but handys dont find it. the
intension ist a multi drop config, but before that, the 2 bs11 should
work on its own, right?

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From laforge at gnumonks.org  Wed Dec 15 06:30:44 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 15 Dec 2010 07:30:44 +0100
Subject: problems with 2nd bs11| verbose mode
In-Reply-To: <1292365158.7419.9.camel@r-9djhc747gf8b40ha>
References: <1292365158.7419.9.camel@r-9djhc747gf8b40ha>
Message-ID: <0e3eeeaf-0527-4a83-96d2-f85869c626b2@email.android.com>

if this is the output of the last version of bs11_config, then it does not seem to print the BPORT objects, not even bport0 nor does it show any GET ATTRIBUTE NACK. please do a clean rebuild of latest git and send output of 'strace -f -x -s1024 bs11_config query'
--
Sent from a mobile device, excuse my short response



From kobayashi_maru at onlinehome.de  Wed Dec 15 13:05:18 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Wed, 15 Dec 2010 14:05:18 +0100
Subject: problems installing openbsc
Message-ID: <1292418318.7740.13.camel@r-9djhc747gf8b40ha>

hello all
2day i decided to install openbsc completely neu (had some trouble with
the bs11_config), according to the website. libosmocore went thru
without problems, openbsc came to the ./configure when the problem
occured. the error was:
./configure: line 3673: syntax error near unexpected token
`LIBOSMOSCCP,'
./configure: line 3673: `        PKG_CHECK_MODULES(LIBOSMOSCCP,
libosmo-sccp >= 0.0.2)'
of course i looked at line 3673, but i'm a linux newbie, so i didnt
really understand.

in the /usr/local/lib/pkgconfig are 3 files: 
libosmocodec.pc:
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include

Name: Osmocom Codec related utilities Library
Description: C Utility Library
Version: 0.1.27.16-ab12
Libs: -L${libdir} -losmocodec
Cflags: -I${includedir}/


libosmocore.pc:
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include

Name: Osmocom Core Library
Description: C Utility Library
Version: 0.1.27.16-ab12
Libs: -L${libdir} -losmocore
Cflags: -I${includedir}/

and libosmovty.pc:
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include

Name: Osmocom VTY Interface Library
Description: C Utility Library
Version: 0.1.27.16-ab12
Libs: -L${libdir} -losmovty
Cflags: -I${includedir}/

up to the configure call, everything worked fine, libosmocore was
complete installed. a makefile wasnt created -> bad!

what went wrong?

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!




From laforge at gnumonks.org  Wed Dec 15 23:03:05 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 16 Dec 2010 00:03:05 +0100
Subject: problems installing openbsc
In-Reply-To: <1292418318.7740.13.camel@r-9djhc747gf8b40ha>
References: <1292418318.7740.13.camel@r-9djhc747gf8b40ha>
Message-ID: <20101215230305.GA24189@prithivi.gnumonks.org>

On Wed, Dec 15, 2010 at 02:05:18PM +0100, Thomas Ansorg wrote:
> hello all
> 2day i decided to install openbsc completely neu (had some trouble with
> the bs11_config), according to the website. libosmocore went thru
> without problems, openbsc came to the ./configure when the problem
> occured. the error was:
> ./configure: line 3673: syntax error near unexpected token
> `LIBOSMOSCCP,'
> ./configure: line 3673: `        PKG_CHECK_MODULES(LIBOSMOSCCP,
> libosmo-sccp >= 0.0.2)'
> of course i looked at line 3673, but i'm a linux newbie, so i didnt
> really understand.

I think you may simply be missing the pkg-config program itself.  Make sure
that is installed, and then do the "autoreconf -i" again, as well as the
./configure, make, etc...

-- 
- 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 laforge at gnumonks.org  Thu Dec 16 09:09:55 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 16 Dec 2010 10:09:55 +0100
Subject: 3G (NodeB / femtocell) roadmap
Message-ID: <20101216090955.GE24189@prithivi.gnumonks.org>

Hi all,

i just wanted to keep you posted with the 2011 roadmap for 3G integration
into our "Free Software Mobile Network" stack.  This message summarizes
the plan of what I expect to be working on.  Comments welcome.

3G support directly in OpenBSC is, however, a bit more difficult than we
originally anticipated.  The primary problems are:

* 3G and 2G share the same core network (CN = MSC/VLR/HLR/AuC/SGSN/GGSN)
  but have different radio access netowrk (RAN = BTS+BSC vs. NodeB+RNC)

* the interface between RAN and CN is different, i.e. 'A' interface
  (08.08) in GSM case, RANAP in 3G case.

* The encoding of the two protocols could not be any different. Hand-coded
  vs. complex ASN.1 structures

So with OpenBSC, we face the following challenges:

1) We implement the GSM-RAN functionality and the CN in one process,
   without any separation or standardized interfaces between them

2) Implementing RANAP in C can be done, but is probably quite cumbersome
   given the tons of code asn1c generates and how difficult it seems to
   get all the memory allocation/freeing right in all the cases

What we instead decided to do is:

a) Split the BSC part from the CN by implementing the A interface (this
   is already finished, we now have osmo-bsc to do exactly that)

b) Implement a new MSC part, using the A interface towards the BSC
   This is still possible using our existing code in the original
   OpenBSC, though we have not completed/finished it yet.  
     The real goal is to have a new MSC, written in a higher-order language
   that provides proper tools for working with ASN.1 - e.g. Erlang.  I have
   just started working on this and am more or less finished with the lower
   layers like SCCP and am moving into 08.08 and the actual layer3 protocols.
   There is already some initial funding secured for the first months of
   this work, and funding will likely continue.

c) Once the 2G functionality of the Erlang MSC is working, add the RANAP
   interface to it.  
     At this point we should more or less be able to directly
   connect the Alcatel-Lucent femtocells, as they basically consist of
   HomeNodeB plus an internal RNC handling the RRC protocol.

d) Adding support for ip.access/Cisco/AT&T will need an implementation of
   their URSL protocol, which is proprietary.  URSL can either be added
   to the new MSC directly, or a URSL<->RANAP translater be developed.

e) Adding support for the Ubiquisys/SFR femtocell would require us to implement
   the UMA protocol stack.  This can once again be either done as part of
   the MSC or using an external translator/gateway program.

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 bouchtaoui at gmail.com  Thu Dec 16 09:57:33 2010
From: bouchtaoui at gmail.com (Nordin)
Date: Thu, 16 Dec 2010 10:57:33 +0100
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <20101216090955.GE24189@prithivi.gnumonks.org>
References: <20101216090955.GE24189@prithivi.gnumonks.org>
Message-ID: <4D09E28D.9020402@gmail.com>

  Hi Harald and list,

Which model of available femtocells are you focusing on and is it easy 
to purchase one (on ebay perhaps)? Cause for 2G the ip.access's nanoBTS 
imho is best supported by openbsc. If you can give us some more 
information what device to use (as a start), than we can at least focus 
on one device and extend to other models in the future.



On 16-12-2010 10:09, Harald Welte wrote:
> Hi all,
>
> i just wanted to keep you posted with the 2011 roadmap for 3G integration
> into our "Free Software Mobile Network" stack.  This message summarizes
> the plan of what I expect to be working on.  Comments welcome.
>
> 3G support directly in OpenBSC is, however, a bit more difficult than we
> originally anticipated.  The primary problems are:
>
> * 3G and 2G share the same core network (CN = MSC/VLR/HLR/AuC/SGSN/GGSN)
>    but have different radio access netowrk (RAN = BTS+BSC vs. NodeB+RNC)
>
> * the interface between RAN and CN is different, i.e. 'A' interface
>    (08.08) in GSM case, RANAP in 3G case.
>
> * The encoding of the two protocols could not be any different. Hand-coded
>    vs. complex ASN.1 structures
>
> So with OpenBSC, we face the following challenges:
>
> 1) We implement the GSM-RAN functionality and the CN in one process,
>     without any separation or standardized interfaces between them
>
> 2) Implementing RANAP in C can be done, but is probably quite cumbersome
>     given the tons of code asn1c generates and how difficult it seems to
>     get all the memory allocation/freeing right in all the cases
>
> What we instead decided to do is:
>
> a) Split the BSC part from the CN by implementing the A interface (this
>     is already finished, we now have osmo-bsc to do exactly that)
>
> b) Implement a new MSC part, using the A interface towards the BSC
>     This is still possible using our existing code in the original
>     OpenBSC, though we have not completed/finished it yet.
>       The real goal is to have a new MSC, written in a higher-order language
>     that provides proper tools for working with ASN.1 - e.g. Erlang.  I have
>     just started working on this and am more or less finished with the lower
>     layers like SCCP and am moving into 08.08 and the actual layer3 protocols.
>     There is already some initial funding secured for the first months of
>     this work, and funding will likely continue.
>
> c) Once the 2G functionality of the Erlang MSC is working, add the RANAP
>     interface to it.
>       At this point we should more or less be able to directly
>     connect the Alcatel-Lucent femtocells, as they basically consist of
>     HomeNodeB plus an internal RNC handling the RRC protocol.
>
> d) Adding support for ip.access/Cisco/AT&T will need an implementation of
>     their URSL protocol, which is proprietary.  URSL can either be added
>     to the new MSC directly, or a URSL<->RANAP translater be developed.
>
> e) Adding support for the Ubiquisys/SFR femtocell would require us to implement
>     the UMA protocol stack.  This can once again be either done as part of
>     the MSC or using an external translator/gateway program.
>
> Regards,
> 	Harald




From 246tnt at gmail.com  Thu Dec 16 10:06:16 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 16 Dec 2010 11:06:16 +0100
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <4D09E28D.9020402@gmail.com>
References: <20101216090955.GE24189@prithivi.gnumonks.org>
	<4D09E28D.9020402@gmail.com>
Message-ID: <AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>

> Which model of available femtocells are you focusing on and is it easy to
> purchase one (on ebay perhaps)? Cause for 2G the ip.access's nanoBTS imho is
> best supported by openbsc. If you can give us some more information what
> device to use (as a start), than we can at least focus on one device and
> extend to other models in the future.

Did you read the mail ?

It explicitely mention :

in point (c) -> "the Alcatel-Lucent femtocells"
in point (d) -> "ip.access/Cisco/AT&T" femtocells
in point (e) -> "Ubiquisys/SFR femtocell"

Google for those ..


Cheers,

    Sylvain



From bouchtaoui at gmail.com  Thu Dec 16 10:19:19 2010
From: bouchtaoui at gmail.com (Nordin)
Date: Thu, 16 Dec 2010 11:19:19 +0100
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
References: <20101216090955.GE24189@prithivi.gnumonks.org>	<4D09E28D.9020402@gmail.com>
	<AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
Message-ID: <4D09E7A7.7040507@gmail.com>

  Sure I read the mail, but these are three models, I don't have the 
money to afford three femtocells. I'm glad to have just one to play 
with. Or you can give me some of yours...


On 16-12-2010 11:06, Sylvain Munaut wrote:
>> Which model of available femtocells are you focusing on and is it easy to
>> purchase one (on ebay perhaps)? Cause for 2G the ip.access's nanoBTS imho is
>> best supported by openbsc. If you can give us some more information what
>> device to use (as a start), than we can at least focus on one device and
>> extend to other models in the future.
> Did you read the mail ?
>
> It explicitely mention :
>
> in point (c) ->  "the Alcatel-Lucent femtocells"
> in point (d) ->  "ip.access/Cisco/AT&T" femtocells
> in point (e) ->  "Ubiquisys/SFR femtocell"
>
> Google for those ..
>
>
> Cheers,
>
>      Sylvain
>




From 246tnt at gmail.com  Thu Dec 16 10:24:13 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 16 Dec 2010 11:24:13 +0100
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <4D09E7A7.7040507@gmail.com>
References: <20101216090955.GE24189@prithivi.gnumonks.org>
	<4D09E28D.9020402@gmail.com>
	<AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
	<4D09E7A7.7040507@gmail.com>
Message-ID: <AANLkTimeyXj434bFn_LaAu0XzzJbcfeSLx=4WX7fsK43@mail.gmail.com>

> ?Sure I read the mail, but these are three models, I don't have the money to
> afford three femtocells. I'm glad to have just one to play with.

Maybe you can read the _rest_ of those paragraphs :

c) "... add the RANAP interface to it. At this point we should more or
less be able to directly ..."
d) "Adding support for ip.access/Cisco/AT&T will need an implementation of
  their URSL protocol"
e) "Adding support for the Ubiquisys/SFR femtocell would require us to implement
  the UMA protocol stack."

Seems pretty clear that the ones mentionned in point c) will work
first since it can use RANAP _directly_ while the two others will need
RANAP <-> URSL  or  RANAP <-> UMA  translators.


> Or you can
> give me some of yours...

Sure, our time working on the project and answering your question
isn't enough for you ? you want our money and equipment as well now
???


    Sylvain



From bongio87 at yahoo.it  Thu Dec 16 10:19:41 2010
From: bongio87 at yahoo.it (luca bongiorni)
Date: Thu, 16 Dec 2010 10:19:41 +0000 (GMT)
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
Message-ID: <729319.53456.qm@web29620.mail.ird.yahoo.com>

>in point (c) -> "the Alcatel-Lucent femtocells"
>in point (d) -> "ip.access/Cisco/AT&T" femtocells
>in point (e) -> "Ubiquisys/SFR femtocell"


About Femtocells.... i already started to work on Vodafone Sure Signal and i would like to work also on Femtocells of others countries.

Are six months that i'm searching on ebay femtocells... but i can find only Vodafone's.

Have you other online shops to suggest?! Especially for SFR and Ubiquisys?!


Thank you list





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

From 246tnt at gmail.com  Thu Dec 16 10:33:15 2010
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 16 Dec 2010 11:33:15 +0100
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <729319.53456.qm@web29620.mail.ird.yahoo.com>
References: <AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
	<729319.53456.qm@web29620.mail.ird.yahoo.com>
Message-ID: <AANLkTikJiHRGdHrBnpYEoTYJbBC+cSWN82sSFh9kJs16@mail.gmail.com>

Hi,


> Are six months that i'm searching on ebay femtocells... but i can find only Vodafone's.

Just did a quick search and I could find one of each model:

http://cgi.ebay.co.uk/Vodafone-Sure-Signal-/200554104589?pt=UK_Mobiles_Accessories_RL&hash=item2eb1f4c70d
http://cgi.ebay.com/AT-T-3G-Microcell-ATT-Femtocell-mini-cellular-tower-/230562766177?pt=PDA_Accessories&hash=item35ae9c9d61
http://annonces.ebay.fr/viewad/SFR-Home-3G-une-couverture-3G-optimale-a-domicil-/5018154940

Vodafones are prevalent that's true, but the others are no way as hard
to find as nanoBTS's.


> Have you other online shops to suggest?! Especially for SFR and Ubiquisys?!

Very often it's only the operators (or reseller for the operator) that
sell the femtocell (since they're 'customized' for a particular
network/operator).

Vodafone seems a little more "lax" in selling them (not checking if
you have a subscription or not) so that's why they're easility found
on ebay. AT&T are also found on the US ebay or craigslist without much
difficulty.

The SFR ones can be bought from SFR if you have a subscription.
They're a little less found on auction sites (I guess less people
re-sell them ?) but it's possible (
http://annonces.ebay.fr/viewad/SFR-Home-3G-une-couverture-3G-optimale-a-domicil-/5018154940
)

But each time you have to search for whatever name the operator has
for it (like "Home 3G" for SFR, or "Sure Signal" for Vodafone, ...)


Cheers,

    Sylvain



From bouchtaoui at gmail.com  Thu Dec 16 10:29:17 2010
From: bouchtaoui at gmail.com (Nordin)
Date: Thu, 16 Dec 2010 11:29:17 +0100
Subject: 3G (NodeB / femtocell) roadmap
In-Reply-To: <AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
References: <20101216090955.GE24189@prithivi.gnumonks.org>	<4D09E28D.9020402@gmail.com>
	<AANLkTikg5qxjj+gCJmrZp3ObDHmj=oYSZWyjHy9_kNL0@mail.gmail.com>
Message-ID: <4D09E9FD.3060100@gmail.com>

  Sorry, appearantly I wasn't awake as I thought.


On 16-12-2010 11:06, Sylvain Munaut wrote:
>> Which model of available femtocells are you focusing on and is it easy to
>> purchase one (on ebay perhaps)? Cause for 2G the ip.access's nanoBTS imho is
>> best supported by openbsc. If you can give us some more information what
>> device to use (as a start), than we can at least focus on one device and
>> extend to other models in the future.
> Did you read the mail ?
>
> It explicitely mention :
>
> in point (c) ->  "the Alcatel-Lucent femtocells"
> in point (d) ->  "ip.access/Cisco/AT&T" femtocells
> in point (e) ->  "Ubiquisys/SFR femtocell"
>
> Google for those ..
>
>
> Cheers,
>
>      Sylvain
>




From joe at monkey.org  Fri Dec 17 17:14:11 2010
From: joe at monkey.org (Joe Eggleston)
Date: Fri, 17 Dec 2010 12:14:11 -0500
Subject: 3G (NodeB / femtocell) roadmap
Message-ID: <AANLkTikMTWORo4SVXc=222+kyM0pa_MH2mNWOnZKogEW@mail.gmail.com>

On Thu, Dec 16, 2010 at 5:33 AM, Sylvain Munaut <246tnt at gmail.com> wrote:
> But each time you have to search for whatever name the operator has
> for it (like "Home 3G" for SFR, or "Sure Signal" for Vodafone, ...)
>


In case this is helpful to anyone else, I stumbled on this page that has a
pretty good list of the providers using the various femtocells:

http://www.thinkfemtocell.com/Examples/where-can-i-buy-a-femtocell.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101217/f6a66a5e/attachment.htm>

From bertoncello at netzing.de  Thu Dec 16 12:15:12 2010
From: bertoncello at netzing.de (Luca Bertoncello)
Date: Thu, 16 Dec 2010 13:15:12 +0100
Subject: Problem in the communication with a real MSC
Message-ID: <20101216131512.79349fa3@Luca>

Hi, List!

I'm trying to connect OpenBSC with a real MSC.
Unfortunately I have many problems.
The first is, that every minute or so, I got these errors:

<000f> bsc_msc_ip.c:1047 The connection to the MSC was lost.
<000f> bsc_msc_ip.c:976 Lost MSC connection. Freing stuff.
<000f> bsc_msc.c:236 Attempting to reconnect to the MSC.
<000f> bsc_msc.c:230 Attempting to reconnect to the MSC.
<000f> bsc_msc.c:137 Attempting to connect MSC at 192.168.2.103:5000
<000f> bsc_msc.c:170 MSC Connection in progress
<000f> bsc_msc.c:99 (Re)Connected to the MSC.
<000f> bssap.c:92 Reset ACK from MSC

I think, it is not normal, that the communication with the MSC was lost.
Both of them (OpenBSC and MSC) are on the same Gigabit network, so
there is no connection problem...
Any idea?

Another problem: I get very oft the error:

<0000> chan_alloc.c:441 (bts=1,trx=0,ts=0,ss=0) Recycling Channel.

Any idea?

Thanks a lot!
-- 
_______________________________________________________________________
Luca Bertoncello
Entwicklung                               Mail:  bertoncello at netzing.de 


NETZING Solutions AG                      Tel.:  0351/41381 - 23
Fr?belstr. 57, 01159 Dresden              Fax:   0351/41381 - 12
_______________________________________________________________________

Impressum: 
NETZING Solutions AG  -  Fr?belstra?e 57   -   01159 Dresden
Sitz der Gesellschaft Amtsgericht Dresden HRB 18926
Vorstand  Dieter Schneider  -  Aufsichtsratsvorsitzender Volker Kanitz
USt.Id DE211326547  Mail:  netzing.ag at netzing.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101216/15ec4328/attachment.bin>

From laforge at gnumonks.org  Thu Dec 16 15:38:01 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 16 Dec 2010 16:38:01 +0100
Subject: Problem in the communication with a real MSC
In-Reply-To: <20101216131512.79349fa3@Luca>
References: <20101216131512.79349fa3@Luca>
Message-ID: <20101216153801.GD25200@prithivi.gnumonks.org>

On Thu, Dec 16, 2010 at 01:15:12PM +0100, Luca Bertoncello wrote:
 
> I'm trying to connect OpenBSC with a real MSC.
> Unfortunately I have many problems.

this is to be expected.  OpenBSC (osmo-bsc) has only been tested with
one particular version of one particular MSC vendor so far.  The only
version that we ever had access to. 

So I think getting it to work with a new/different type of MSC will
most likely need some kind of adoption.  Maybe not as much work as adding
support for a new BTS vendor/model, but definitely some work.

Also, from our experience with that one MSC: Zecke had to work around quite
a number of bugs in the MSC.  Whether the same bugs or workarounds work with
your MSC is of course unknown.

> Any idea?

No, I think you will have to debug this yourself by looking at the A interface
prtoocol traces in wireshark.
-- 
- 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 Dec 16 17:56:14 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 16 Dec 2010 18:56:14 +0100
Subject: Problem in the communication with a real MSC
In-Reply-To: <20101216153801.GD25200@prithivi.gnumonks.org>
References: <20101216131512.79349fa3@Luca>
	<20101216153801.GD25200@prithivi.gnumonks.org>
Message-ID: <4D0A52BE.70505@freyther.de>

On 12/16/2010 04:38 PM, Harald Welte wrote:
> On Thu, Dec 16, 2010 at 01:15:12PM +0100, Luca Bertoncello wrote:

> 
> Also, from our experience with that one MSC: Zecke had to work around quite
> a number of bugs in the MSC.  Whether the same bugs or workarounds work with
> your MSC is of course unknown.

Not that many, some more due my own stupidity, but it is true that the code is
written to work with this one MSC but I have not really seen a spec violation
(it can do some stuff that it should not do though).



From holger at freyther.de  Thu Dec 16 18:01:29 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 16 Dec 2010 19:01:29 +0100
Subject: Problem in the communication with a real MSC
In-Reply-To: <20101216131512.79349fa3@Luca>
References: <20101216131512.79349fa3@Luca>
Message-ID: <4D0A53F9.8010009@freyther.de>

On 12/16/2010 01:15 PM, Luca Bertoncello wrote:
> Hi, List!


> 
> I think, it is not normal, that the communication with the MSC was lost.
> Both of them (OpenBSC and MSC) are on the same Gigabit network, so
> there is no connection problem...
> Any idea?

Well, who is closing the TCP connection? Is it the MSC that is unhappy? Is it
the BSC that is unhappy (e.g. you removed a log line talking about timeouts?)?
Do you see any other messages in wireshark? Which MSC is that>




> Another problem: I get very oft the error:
> 
> <0000> chan_alloc.c:441 (bts=1,trx=0,ts=0,ss=0) Recycling Channel.
> 
> Any idea?

Why do you think it is an error? It is a normal notice on channel release.
Actually you must be using on-waves/bsc-master as well.




From peter.hasse at fokus.fraunhofer.de  Thu Dec 16 14:49:06 2010
From: peter.hasse at fokus.fraunhofer.de (Peter Hasse)
Date: Thu, 16 Dec 2010 15:49:06 +0100
Subject: TRX is not responding error message
Message-ID: <4D0A26E2.60406@fokus.fraunhofer.de>

Hi

One of our nanoBTSs startet to reboot very frequently.
The debug telnet console shows this error:

12168:WARN:OAM_RES:res_trx_status.c#231:TRX is not responding - 
reinitialising the unit...

13251:DBG:OAM_IM:Stopping "Primary OML Fallback Client" >
13251:DBG:OAM_IM:Stopping "Secondary OML Server" >
13251:DBG:OAM_IM:Stopping "Secure Secondary OML Server"
13252:DBG:OAM_IM:Not stopping "IML Site Server" - has not been started
13252:DBG:OAM_IM:Not stopping "Secure IML Site Server" - has not been 
started
13252:DBG:OAM_IM:Stopping "IML Bts Server" >
13252:DBG:OAM_IM:Stopping "Secure IML Bts Server"
13252:DBG:OAM_IM:Stopping "IRL Patched Routing Link"
13252:DBG:OAM_IM:Failed to inject event=1="STOP" into link source (token=9)
13284:DBG:IP_CHAN_SERVER:Closed server listening on port 3006 >
13284:DBG:IP_CHAN_SERVER:Closed server listening on port 3026>
13285:DBG:IP_CHAN_SERVER:Closed server listening on port 3014>
13285:DBG:IP_CHAN_SERVER:Closed server listening on port 3034>
13458:DBG:IP_CHAN_RX_A:15190:ipChanConn: EVENT 0x00001743 rxd in STATE 
connected
13458:DBG:IP_CHAN_RX_A:15191:ipChanConn: EVENT 0x00001741 rxd in STATE 
disconnectclosing


here is the output of openBSC

<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) Sending OPSTART
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: 
OP_STATE=Disabled AVAIL=Dependency(05)
<0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=7)
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) Sending OPSTART
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) Software Activated 
Report
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) Software Activated 
Report
<0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE 
CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked
<0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) 
IPACCESS(0xe1): RSL CONNECT ACK IP=192.168.0.1 PORT=3003 STREAM=0x00
<0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: 
OP_STATE=Disabled AVAIL=OK(ff) ADM=Unlocked
<0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) Sending OPSTART
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure 
Event Report Type=processing failure Severity=warning level failure
<0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure 
Event Report Type=processing failure Severity=warning level failure
<0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure 
Event Report Type=processing failure Severity=warning level failure


Another nanoBTS with same firmware and config works perfekt with the 
same openBTS installation.
Switching to the second firmware bank and flashing a different firmware 
didnt solve the problem.
Any hint where to look for more information ?


mfg Peter



From laforge at gnumonks.org  Thu Dec 16 15:39:54 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 16 Dec 2010 16:39:54 +0100
Subject: TRX is not responding error message
In-Reply-To: <4D0A26E2.60406@fokus.fraunhofer.de>
References: <4D0A26E2.60406@fokus.fraunhofer.de>
Message-ID: <20101216153954.GE25200@prithivi.gnumonks.org>

On Thu, Dec 16, 2010 at 03:49:06PM +0100, Peter Hasse wrote:
> <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff)
> Failure Event Report Type=processing failure Severity=warning level
> failure
> <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff)
> Failure Event Report Type=processing failure Severity=warning level
> failure
> <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff)
> Failure Event Report Type=processing failure Severity=warning level
> failure

have you ever looked at those event reports using the abis_oml wireshark
dissector from openbsc.git/wireshark/ ?

this should give you some more information than just the BSC log.

-- 
- 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 peter.hasse at fokus.fraunhofer.de  Thu Dec 16 17:14:29 2010
From: peter.hasse at fokus.fraunhofer.de (Peter Hasse)
Date: Thu, 16 Dec 2010 18:14:29 +0100
Subject: TRX is not responding error message
In-Reply-To: <20101216153954.GE25200@prithivi.gnumonks.org>
References: <4D0A26E2.60406@fokus.fraunhofer.de>
	<20101216153954.GE25200@prithivi.gnumonks.org>
Message-ID: <4D0A48F5.5030008@fokus.fraunhofer.de>


> have you ever looked at those event reports using the abis_oml wireshark
> dissector from openbsc.git/wireshark/ ?
>
> this should give you some more information than just the BSC log.
Yes but i couldnt locate the problem.
I'm not that familar with the oml protocol, maybe i miss something.
I uploaded the pcap if somene is interestet.
http://luusa.org/~derpeter/nanoBTS-reboot.pcap


mfg Peter



From laforge at gnumonks.org  Fri Dec 17 14:34:57 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 17 Dec 2010 15:34:57 +0100
Subject: TRX is not responding error message
In-Reply-To: <4D0A48F5.5030008@fokus.fraunhofer.de>
References: <4D0A26E2.60406@fokus.fraunhofer.de>
	<20101216153954.GE25200@prithivi.gnumonks.org>
	<4D0A48F5.5030008@fokus.fraunhofer.de>
Message-ID: <20101217143457.GY25200@prithivi.gnumonks.org>

Hi Peter,

On Thu, Dec 16, 2010 at 06:14:29PM +0100, Peter Hasse wrote:
> 
> >have you ever looked at those event reports using the abis_oml wireshark
> >dissector from openbsc.git/wireshark/ ?
> >
> >this should give you some more information than just the BSC log.
> Yes but i couldnt locate the problem.
> http://luusa.org/~derpeter/nanoBTS-reboot.pcap

packet 188: 

35068:WARN:OAM_RES:res_trx_status.c#231:TRX is not responding - reinitialising the unit...

packet 189:
Aborting stalled "SET CHANNEL ATTRIBUTS" procedure.

This really looks like a hardware problem of that particular unit to me :(

-- 
- 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 kobayashi_maru at onlinehome.de  Fri Dec 17 16:41:04 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Fri, 17 Dec 2010 17:41:04 +0100
Subject: multi drop config - almost done
Message-ID: <1292604064.4359.12.camel@r-9djhc747gf8b40ha>

hello
after compiling the new software, bs11_config tells me for bts1 (the
working one):
bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY

LMT LOGON: ACK

PHASE: 3 Normal               MBCCU0: Load        MBCCU1: No Load
Abis-link: Restoring 

BS11 ATTRIBUTES:
	BS-11 ESN PCB Serial Number: 001104
	BS-11 ESN Hardware Code Number: 135-2044/03.07
	BS-11 ESN Firmware Code Number: 135-2044/03.07
	PLL Set Value=1006, Work Value=1038

SITE MANAGER ATTRIBUTES:
	E1 Channel: Port=0 Timeslot=1 (Full Slot)
	TEI: 25

BS11 Line Interface ATTRIBUTES:
	PLL Mode: Standalone

BS11 CCLK ATTRIBUTES:
	CCLK Accuracy: High (1)
	CCLK Type=0

BS11 Power Amplifier 0 ATTRIBUTES:
	TRX Power: 30mW (GSM)

BPORT0 ATTRIBUTES:
	Line Configuration: Multi-Drop (1)

BPORT1 ATTRIBUTES:
	Line Configuration: Multi-Drop (1)
LMT LOGOFF: ACK
***************************************************************************
i set the bport multi thing on my own

the 2nd bts said this:
bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY

LMT LOGON: ACK

PHASE: 3 Normal               MBCCU0: Load        MBCCU1: No Load
Abis-link: Restoring 

BS11 ATTRIBUTES:
	BS-11 ESN PCB Serial Number: 001112
	BS-11 ESN Hardware Code Number: 135-2044/03.03
	BS-11 ESN Firmware Code Number: 135-2044/03.03
	PLL Set Value=1073, Work Value=1073

SITE MANAGER ATTRIBUTES:
	E1 Channel: Port=0 Timeslot=6 (Full Slot)
	TEI: 26

BS11 Line Interface ATTRIBUTES:
	PLL Mode: Standalone

BS11 CCLK ATTRIBUTES:
	CCLK Accuracy: High (1)
	CCLK Type=0

BS11 Power Amplifier 0 ATTRIBUTES:
	TRX Power: 30mW (GSM)

BPORT0 ATTRIBUTES:
	Line Configuration: Multi-Drop (1)

BPORT1 GET ATTR NACK
LMT LOGOFF: ACK
*****************************************************************************
as you can see, i set the port to 0 on both, bts1 works on ts1, tei 25
and bts2 on ts6, tei 26. 
does this configuration match with the attached config-file? 
unfortunately i couldnt test it thoroghly today, it was late :-(
there is a strange errormessage at the end of bts2 report, a possible
problem? anyway, i wasnt able to create a bport, neither in connected
nor disconnected mode

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!
-------------- next part --------------
!
! OpenBSC configuration saved from vty
!   !
password foo
!
line vty
 no login
!
network
 network country code 262
 mobile network code 10
 short name Y-Phone
 long name Yodaphone
 handover 1
 bts 0
  type bs11
  band GSM900
  cell_identity 1
  location_area_code 1
  training_sequence_code 7
  base_station_id_code 63
  oml e1 line 0 timeslot 1 sub-slot full
  oml e1 tei 25
  trx 0
   arfcn 121
   max_power_red 0
   rsl e1 line 0 timeslot 1 sub-slot full
   rsl e1 tei 1
    timeslot 0
     phys_chan_config CCCH+SDCCH4
     e1 line 0 timeslot 1 sub-slot full
    timeslot 1
     phys_chan_config TCH/F
     e1 line 0 timeslot 2 sub-slot 1
    timeslot 2
     phys_chan_config TCH/F
     e1 line 0 timeslot 2 sub-slot 2
    timeslot 3
     phys_chan_config TCH/F
     e1 line 0 timeslot 2 sub-slot 3
    timeslot 4
     phys_chan_config TCH/F
     e1 line 0 timeslot 3 sub-slot 0
    timeslot 5
     phys_chan_config TCH/F
     e1 line 0 timeslot 3 sub-slot 1
    timeslot 6
     phys_chan_config TCH/F
     e1 line 0 timeslot 3 sub-slot 2
    timeslot 7
     phys_chan_config TCH/F
     e1 line 0 timeslot 3 sub-slot 3
  trx 1
   arfcn 123
   max_power_red 0
   rsl e1 line 0 timeslot 1 sub-slot full
   rsl e1 tei 2
    timeslot 0
     phys_chan_config TCH/F
     e1 line 0 timeslot 4 sub-slot 0
    timeslot 1
     phys_chan_config TCH/F
     e1 line 0 timeslot 4 sub-slot 1
    timeslot 2
     phys_chan_config TCH/F
     e1 line 0 timeslot 4 sub-slot 2
    timeslot 3
     phys_chan_config TCH/F
     e1 line 0 timeslot 4 sub-slot 3
    timeslot 4
     phys_chan_config TCH/F
     e1 line 0 timeslot 5 sub-slot 0
    timeslot 5
     phys_chan_config TCH/F
     e1 line 0 timeslot 5 sub-slot 1
    timeslot 6
     phys_chan_config TCH/F
     e1 line 0 timeslot 5 sub-slot 2
    timeslot 7
     phys_chan_config TCH/F
     e1 line 0 timeslot 5 sub-slot 3
 bts 1
  type bs11
  band GSM900
  location_area_code 2
  training_sequence_code 7
  base_station_id_code 63
  oml e1 line 0 timeslot 6 sub-slot full
  oml e1 tei 26
  trx 0
   arfcn 122
   max_power_red 0
   rsl e1 line 0 timeslot 6 sub-slot full
   rsl e1 tei 1
    timeslot 0
     phys_chan_config CCCH+SDCCH4
     e1 line 0 timeslot 7 sub-slot 0
    timeslot 1
     phys_chan_config SDCCH8
     e1 line 0 timeslot 7 sub-slot 1
    timeslot 2
     phys_chan_config TCH/F
     e1 line 0 timeslot 7 sub-slot 2
    timeslot 3
     phys_chan_config TCH/F
     e1 line 0 timeslot 7 sub-slot 3
    timeslot 4
     phys_chan_config TCH/F
     e1 line 0 timeslot 8 sub-slot 0
    timeslot 5
     phys_chan_config TCH/F
     e1 line 0 timeslot 8 sub-slot 1
    timeslot 6
     phys_chan_config TCH/F
     e1 line 0 timeslot 8 sub-slot 2
    timeslot 7
     phys_chan_config TCH/F
     e1 line 0 timeslot 8 sub-slot 3
  trx 1
   arfcn 124
   max_power_red 0
   rsl e1 line 0 timeslot 6 sub-slot full
   rsl e1 tei 2
    timeslot 0
     phys_chan_config TCH/F
     e1 line 0 timeslot 9 sub-slot 0
    timeslot 1
     phys_chan_config TCH/F
     e1 line 0 timeslot 9 sub-slot 1
    timeslot 2
     phys_chan_config TCH/F
     e1 line 0 timeslot 9 sub-slot 2
    timeslot 3
     phys_chan_config TCH/F
     e1 line 0 timeslot 9 sub-slot 3
    timeslot 4
     phys_chan_config TCH/F
     e1 line 0 timeslot 10 sub-slot 0
    timeslot 5
     phys_chan_config TCH/F
     e1 line 0 timeslot 10 sub-slot 1
    timeslot 6
     phys_chan_config TCH/F
     e1 line 0 timeslot 10 sub-slot 2
    timeslot 7
     phys_chan_config TCH/F
     e1 line 0 timeslot 10 sub-slot 3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101217/de8fb57b/attachment.bin>

From laforge at gnumonks.org  Fri Dec 17 18:07:20 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 17 Dec 2010 19:07:20 +0100
Subject: multi drop config - almost done
In-Reply-To: <1292604064.4359.12.camel@r-9djhc747gf8b40ha>
References: <1292604064.4359.12.camel@r-9djhc747gf8b40ha>
Message-ID: <20101217180720.GE25200@prithivi.gnumonks.org>

Hi Thomas,

On Fri, Dec 17, 2010 at 05:41:04PM +0100, Thomas Ansorg wrote:
>
> BPORT0 ATTRIBUTES:
> 	Line Configuration: Multi-Drop (1)
> 
> BPORT1 ATTRIBUTES:
> 	Line Configuration: Multi-Drop (1)
> LMT LOGOFF: ACK

this is looking fine.

> the 2nd bts said this:
> BPORT0 ATTRIBUTES:
> 	Line Configuration: Multi-Drop (1)
> 
> BPORT1 GET ATTR NACK
> LMT LOGOFF: ACK
> *****************************************************************************
> as you can see, i set the port to 0 on both, bts1 works on ts1, tei 25
> and bts2 on ts6, tei 26. 

Why do you configure the 2nd BTS to multi-drop mode?  

The 2nd BTS is at the _end_ of the line, and thus has to be configured like a
'single bts' setup !

Only those BTS that have to pass the E1 signal from BPORT0 to BPORT1 need
their BPORTs in mult-drop mode.

> does this configuration match with the attached config-file? 

i think it does. 

> there is a strange errormessage at the end of bts2 report, a possible
> problem? anyway, i wasnt able to create a bport, neither in connected
> nor disconnected mode

You do not need a BPORT1 on the 2nd bts (at the end of the chain).

Now the final question: Did you patch your hfcmulti kernel driver? What kind of
module load parameters do you use in order to run D-channels on multiple E1
timeslots?

-- 
- 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 kobayashi_maru at onlinehome.de  Fri Dec 17 20:24:50 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Fri, 17 Dec 2010 21:24:50 +0100
Subject: mISDN-problem
Message-ID: <1292617490.6278.1.camel@r-9djhc747gf8b40ha>

hello
newbie question: what does this dmesg mean?

T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!
-------------- next part --------------
26415.636794] mISDN_send: error -12
[26415.652794] mISDN_send: error -12
[26415.652797] mISDN_send: error -12
[26415.668797] mISDN_send: error -12
[26415.668800] mISDN_send: error -12
[26415.684799] mISDN_send: error -12
[26415.684802] mISDN_send: error -12
[26415.700800] mISDN_send: error -12
[26415.700803] mISDN_send: error -12
[26415.716803] mISDN_send: error -12
[26415.716806] mISDN_send: error -12
[26415.732805] mISDN_send: error -12
[26415.732808] mISDN_send: error -12
[26415.739857] mISDN_send: error -12
[26415.739860] mISDN_send: error -12
[26415.748808] mISDN_send: error -12
[26415.748811] mISDN_send: error -12
[26415.764810] mISDN_send: error -12
[26415.764813] mISDN_send: error -12
[26415.780812] mISDN_send: error -12
[26415.780815] mISDN_send: error -12
[26415.796814] mISDN_send: error -12
[26415.796817] mISDN_send: error -12
[26415.812816] mISDN_send: error -12
[26415.812820] mISDN_send: error -12
[26415.828818] mISDN_send: error -12
[26415.828822] mISDN_send: error -12
[26415.844893] mISDN_send: error -12
[26415.844896] mISDN_send: error -12
[26415.844899] mISDN_send: error -12
[26415.844901] mISDN_send: error -12
[26415.860823] mISDN_send: error -12
[26415.860826] mISDN_send: error -12
[26415.876825] mISDN_send: error -12
[26415.876828] mISDN_send: error -12
[26415.892828] mISDN_send: error -12
[26415.892831] mISDN_send: error -12
[26415.908830] mISDN_send: error -12
[26415.908833] mISDN_send: error -12
[26415.924832] mISDN_send: error -12
[26415.924836] mISDN_send: error -12
[26415.940834] mISDN_send: error -12
[26415.940838] mISDN_send: error -12
[26415.949887] mISDN_send: error -12
[26415.949890] mISDN_send: error -12
[26415.956837] mISDN_send: error -12
[26415.956840] mISDN_send: error -12
[26415.972839] mISDN_send: error -12
[26415.972842] mISDN_send: error -12
[26415.988841] mISDN_send: error -12
[26415.988845] mISDN_send: error -12
[26416.004843] mISDN_send: error -12
[26416.004846] mISDN_send: error -12
[26416.020845] mISDN_send: error -12
[26416.020849] mISDN_send: error -12
[26416.036847] mISDN_send: error -12
[26416.036850] mISDN_send: error -12
[26416.052850] mISDN_send: error -12
[26416.052853] mISDN_send: error -12
[26416.054774] mISDN_send: error -12
[26416.054777] mISDN_send: error -12
[26416.068852] mISDN_send: error -12
[26416.068855] mISDN_send: error -12
[26416.084854] mISDN_send: error -12
[26416.084857] mISDN_send: error -12
[26416.100857] mISDN_send: error -12
[26416.100860] mISDN_send: error -12
[26416.116859] mISDN_send: error -12
[26416.116862] mISDN_send: error -12
[26416.132861] mISDN_send: error -12
[26416.132864] mISDN_send: error -12
[26416.148863] mISDN_send: error -12
[26416.148866] mISDN_send: error -12
[26416.159791] mISDN_send: error -12
[26416.159794] mISDN_send: error -12
[26416.164866] mISDN_send: error -12
[26416.164869] mISDN_send: error -12
[26416.180868] mISDN_send: error -12
[26416.180871] mISDN_send: error -12
[26416.196870] mISDN_send: error -12
[26416.196873] mISDN_send: error -12
[26416.212872] mISDN_send: error -12
[26416.212875] mISDN_send: error -12
[26416.228874] mISDN_send: error -12
[26416.228877] mISDN_send: error -12
[26416.244877] mISDN_send: error -12
[26416.244880] mISDN_send: error -12
[26416.260879] mISDN_send: error -12
[26416.260882] mISDN_send: error -12
[26416.264806] mISDN_send: error -12
[26416.264808] mISDN_send: error -12
[26416.276882] mISDN_send: error -12
[26416.276885] mISDN_send: error -12
[26416.292883] mISDN_send: error -12
[26416.292886] mISDN_send: error -12
[26416.308885] mISDN_send: error -12
[26416.308888] mISDN_send: error -12
[26416.324888] mISDN_send: error -12
[26416.324891] mISDN_send: error -12
[26416.340890] mISDN_send: error -12
[26416.340893] mISDN_send: error -12
[26416.356892] mISDN_send: error -12
[26416.356895] mISDN_send: error -12
[26416.369821] mISDN_send: error -12
[26416.369824] mISDN_send: error -12
[26416.372894] mISDN_send: error -12
[26416.372897] mISDN_send: error -12
[26416.388897] mISDN_send: error -12
[26416.388900] mISDN_send: error -12
[26416.404899] mISDN_send: error -12
[26416.404902] mISDN_send: error -12
[26416.420901] mISDN_send: error -12
[26416.420904] mISDN_send: error -12
[26416.436903] mISDN_send: error -12
[26416.436906] mISDN_send: error -12
[26416.452905] mISDN_send: error -12
[26416.452908] mISDN_send: error -12
[26416.468907] mISDN_send: error -12
[26416.468910] mISDN_send: error -12
[26416.474835] mISDN_send: error -12
[26416.474838] mISDN_send: error -12
[26416.484911] mISDN_send: error -12
[26416.484914] mISDN_send: error -12
[26416.500912] mISDN_send: error -12
[26416.500915] mISDN_send: error -12
[26416.516914] mISDN_send: error -12
[26416.516917] mISDN_send: error -12
[26416.532917] mISDN_send: error -12
[26416.532920] mISDN_send: error -12
[26416.548919] mISDN_send: error -12
[26416.548922] mISDN_send: error -12
[26416.564920] mISDN_send: error -12
[26416.564924] mISDN_send: error -12
[26416.579849] mISDN_send: error -12
[26416.579852] mISDN_send: error -12
[26416.580923] mISDN_send: error -12
[26416.580926] mISDN_send: error -12
[26416.596925] mISDN_send: error -12
[26416.596928] mISDN_send: error -12
[26416.612928] mISDN_send: error -12
[26416.612931] mISDN_send: error -12
[26416.628930] mISDN_send: error -12
[26416.628933] mISDN_send: error -12
[26416.644932] mISDN_send: error -12
[26416.644935] mISDN_send: error -12
[26416.660934] mISDN_send: error -12
[26416.660937] mISDN_send: error -12
[26416.676936] mISDN_send: error -12
[26416.676939] mISDN_send: error -12
[26416.684864] mISDN_send: error -12
[26416.684867] mISDN_send: error -12
[26416.692939] mISDN_send: error -12
[26416.692942] mISDN_send: error -12
[26416.708941] mISDN_send: error -12
[26416.708944] mISDN_send: error -12
[26416.724942] mISDN_send: error -12
[26416.724946] mISDN_send: error -12
[26416.740946] mISDN_send: error -12
[26416.740949] mISDN_send: error -12
[26416.756948] mISDN_send: error -12
[26416.756951] mISDN_send: error -12
[26416.772950] mISDN_send: error -12
[26416.772953] mISDN_send: error -12
[26416.788952] mISDN_send: error -12
[26416.788955] mISDN_send: error -12
[26416.789876] mISDN_send: error -12
[26416.789879] mISDN_send: error -12
[26416.804954] mISDN_send: error -12
[26416.804957] mISDN_send: error -12
[26416.820956] mISDN_send: error -12
[26416.820959] mISDN_send: error -12
[26416.836959] mISDN_send: error -12
[26416.836962] mISDN_send: error -12
[26416.852961] mISDN_send: error -12
[26416.852964] mISDN_send: error -12
[26416.868962] mISDN_send: error -12
[26416.868965] mISDN_send: error -12
[26416.884966] mISDN_send: error -12
[26416.884969] mISDN_send: error -12
[26416.894894] mISDN_send: error -12
[26416.894897] mISDN_send: error -12
[26416.900968] mISDN_send: error -12
[26416.900971] mISDN_send: error -12
[26416.916970] mISDN_send: error -12
[26416.916973] mISDN_send: error -12
[26416.932972] mISDN_send: error -12
[26416.932975] mISDN_send: error -12
[26416.948974] mISDN_send: error -12
[26416.948977] mISDN_send: error -12
[26416.964977] mISDN_send: error -12
[26416.964980] mISDN_send: error -12
[26416.980978] mISDN_send: error -12
[26416.980981] mISDN_send: error -12
[26416.996980] mISDN_send: error -12
[26416.996984] mISDN_send: error -12
[26416.999905] mISDN_send: error -12
[26416.999908] mISDN_send: error -12
[26417.013054] mISDN_send: error -12
[26417.013057] mISDN_send: error -12
[26417.028985] mISDN_send: error -12
[26417.028988] mISDN_send: error -12
[26417.045002] mISDN_send: error -12
[26417.045005] mISDN_send: error -12
[26417.061012] mISDN_send: error -12
[26417.061015] mISDN_send: error -12
[26417.076999] mISDN_send: error -12
[26417.077002] mISDN_send: error -12
[26417.092994] mISDN_send: error -12
[26417.092997] mISDN_send: error -12
[26417.104923] mISDN_send: error -12
[26417.104926] mISDN_send: error -12
[26417.108997] mISDN_send: error -12
[26417.109000] mISDN_send: error -12
[26417.124998] mISDN_send: error -12
[26417.125001] mISDN_send: error -12
[26417.141001] mISDN_send: error -12
[26417.141004] mISDN_send: error -12
[26417.157003] mISDN_send: error -12
[26417.157006] mISDN_send: error -12
[26417.173006] mISDN_send: error -12
[26417.173009] mISDN_send: error -12
[26417.189008] mISDN_send: error -12
[26417.189011] mISDN_send: error -12
[26417.205010] mISDN_send: error -12
[26417.205013] mISDN_send: error -12
[26417.209937] mISDN_send: error -12
[26417.209940] mISDN_send: error -12
[26417.221013] mISDN_send: error -12
[26417.221016] mISDN_send: error -12
[26417.237014] mISDN_send: error -12
[26417.237017] mISDN_send: error -12
[26417.253016] mISDN_send: error -12
[26417.253019] mISDN_send: error -12
[26417.269019] mISDN_send: error -12
[26417.269022] mISDN_send: error -12
[26417.285021] mISDN_send: error -12
[26417.285024] mISDN_send: error -12
[26417.301024] mISDN_send: error -12
[26417.301027] mISDN_send: error -12
[26417.314952] mISDN_send: error -12
[26417.314955] mISDN_send: error -12
[26417.317026] mISDN_send: error -12
[26417.317029] mISDN_send: error -12
[26417.333027] mISDN_send: error -12
[26417.333030] mISDN_send: error -12
[26417.349030] mISDN_send: error -12
[26417.349033] mISDN_send: error -12
[26417.365032] mISDN_send: error -12
[26417.365035] mISDN_send: error -12
[26417.381034] mISDN_send: error -12
[26417.381037] mISDN_send: error -12
[26417.397036] mISDN_send: error -12
[26417.397040] mISDN_send: error -12
[26417.413038] mISDN_send: error -12
[26417.413042] mISDN_send: error -12
[26417.419966] mISDN_send: error -12
[26417.419969] mISDN_send: error -12
[26417.429042] mISDN_send: error -12
[26417.429045] mISDN_send: error -12
[26417.445043] mISDN_send: error -12
[26417.445046] mISDN_send: error -12
[26417.461045] mISDN_send: error -12
[26417.461048] mISDN_send: error -12
[26417.477048] mISDN_send: error -12
[26417.477051] mISDN_send: error -12
[26417.493050] mISDN_send: error -12
[26417.493053] mISDN_send: error -12
[26417.509052] mISDN_send: error -12
[26417.509055] mISDN_send: error -12
[26417.525055] mISDN_send: error -12
[26417.525058] mISDN_send: error -12
[26417.525061] mISDN_send: error -12
[26417.525063] mISDN_send: error -12
[26417.541056] mISDN_send: error -12
[26417.541059] mISDN_send: error -12
[26417.557059] mISDN_send: error -12
[26417.557062] mISDN_send: error -12
[26417.573061] mISDN_send: error -12
[26417.573064] mISDN_send: error -12
[26417.589064] mISDN_send: error -12
[26417.589067] mISDN_send: error -12
[26417.605066] mISDN_send: error -12
[26417.605069] mISDN_send: error -12
[26417.621068] mISDN_send: error -12
[26417.621071] mISDN_send: error -12
[26417.629996] mISDN_send: error -12
[26417.629999] mISDN_send: error -12
[26417.637070] mISDN_send: error -12
[26417.637073] mISDN_send: error -12
[26417.653072] mISDN_send: error -12
[26417.653075] mISDN_send: error -12
[26417.669074] mISDN_send: error -12
[26417.669077] mISDN_send: error -12
[26417.685076] mISDN_send: error -12
[26417.685079] mISDN_send: error -12
[26417.701079] mISDN_send: error -12
[26417.701082] mISDN_send: error -12
[26417.717081] mISDN_send: error -12
[26417.717084] mISDN_send: error -12
[26417.733084] mISDN_send: error -12
[26417.733087] mISDN_send: error -12
[26417.735007] mISDN_send: error -12
[26417.735010] mISDN_send: error -12
[26417.749085] mISDN_send: error -12
[26417.749088] mISDN_send: error -12
[26417.762882] base_sock_release(f6e15380) sk=f6957c00
[26613.195149] create_l2entity: ret 1 0
[26613.195156] create_l2entity: ret 2 0
[26613.195854] base_sock_release(f6e15380) sk=f6957600
[26613.195901] base_sock_release(f6f5e800) sk=f683fc00
[26936.067631] create_l2entity: ret 1 0
[26936.067637] create_l2entity: ret 2 0
[27099.476077] bsc_hack[3147]: segfault at 0 ip 08058c37 sp bf9f3610 error 4 in bsc_hack[8048000+45000]
[27099.476243] base_sock_release(f6e15380) sk=f6854c00
[27118.194096] create_l2entity: ret 1 0
[27118.194102] create_l2entity: ret 2 0
[27121.078939] l2mgr: addr:0 prim 1f04 F
[27203.842419] mISDN_send: error -12
[27203.842423] mISDN_send: error -12
[27203.858420] mISDN_send: error -12
[27203.858424] mISDN_send: error -12
[27203.874421] mISDN_send: error -12
[27203.874424] mISDN_send: error -12
[27203.879599] mISDN_send: error -12
[27203.879603] mISDN_send: error -12
[27203.890424] mISDN_send: error -12
[27203.890428] mISDN_send: error -12
[27203.906425] mISDN_send: error -12
[27203.906429] mISDN_send: error -12
[27203.922427] mISDN_send: error -12
[27203.922431] mISDN_send: error -12
[27203.938430] mISDN_send: error -12
[27203.938433] mISDN_send: error -12
[27203.954433] mISDN_send: error -12
[27203.954436] mISDN_send: error -12
[27203.970435] mISDN_send: error -12
[27203.970438] mISDN_send: error -12
[27203.984614] mISDN_send: error -12
[27203.984618] mISDN_send: error -12
[27203.986435] mISDN_send: error -12
[27203.986438] mISDN_send: error -12
[27204.002438] mISDN_send: error -12
[27204.002441] mISDN_send: error -12
[27204.018442] mISDN_send: error -12
[27204.018445] mISDN_send: error -12
[27204.034443] mISDN_send: error -12
[27204.034446] mISDN_send: error -12
[27204.050445] mISDN_send: error -12
[27204.050448] mISDN_send: error -12
[27204.066448] mISDN_send: error -12
[27204.066451] mISDN_send: error -12
[27204.082450] mISDN_send: error -12
[27204.082453] mISDN_send: error -12
[27204.089628] mISDN_send: error -12
[27204.089631] mISDN_send: error -12
[27204.098452] mISDN_send: error -12
[27204.098455] mISDN_send: error -12
[27204.114455] mISDN_send: error -12
[27204.114458] mISDN_send: error -12
[27204.130456] mISDN_send: error -12
[27204.130460] mISDN_send: error -12
[27204.146459] mISDN_send: error -12
[27204.146462] mISDN_send: error -12
[27204.162461] mISDN_send: error -12
[27204.162464] mISDN_send: error -12
[27204.178463] mISDN_send: error -12
[27204.178466] mISDN_send: error -12
[27204.194466] mISDN_send: error -12
[27204.194469] mISDN_send: error -12
[27204.194639] mISDN_send: error -12
[27204.194642] mISDN_send: error -12
[27204.210468] mISDN_send: error -12
[27204.210471] mISDN_send: error -12
[27204.226470] mISDN_send: error -12
[27204.226473] mISDN_send: error -12
[27204.242472] mISDN_send: error -12
[27204.242475] mISDN_send: error -12
[27204.258474] mISDN_send: error -12
[27204.258478] mISDN_send: error -12
[27204.274477] mISDN_send: error -12
[27204.274480] mISDN_send: error -12
[27204.290479] mISDN_send: error -12
[27204.290482] mISDN_send: error -12
[27204.299658] mISDN_send: error -12
[27204.299661] mISDN_send: error -12
[27204.306482] mISDN_send: error -12
[27204.306485] mISDN_send: error -12
[27204.322484] mISDN_send: error -12
[27204.322487] mISDN_send: error -12
[27204.338486] mISDN_send: error -12
[27204.338489] mISDN_send: error -12
[27204.354487] mISDN_send: error -12
[27204.354490] mISDN_send: error -12
[27204.370490] mISDN_send: error -12
[27204.370494] mISDN_send: error -12
[27204.386492] mISDN_send: error -12
[27204.386496] mISDN_send: error -12
[27204.402495] mISDN_send: error -12
[27204.402499] mISDN_send: error -12
[27204.404672] mISDN_send: error -12
[27204.404675] mISDN_send: error -12
[27204.418497] mISDN_send: error -12
[27204.418500] mISDN_send: error -12
[27204.434499] mISDN_send: error -12
[27204.434502] mISDN_send: error -12
[27204.450501] mISDN_send: error -12
[27204.450505] mISDN_send: error -12
[27204.466503] mISDN_send: error -12
[27204.466507] mISDN_send: error -12
[27204.482506] mISDN_send: error -12
[27204.482509] mISDN_send: error -12
[27204.498508] mISDN_send: error -12
[27204.498511] mISDN_send: error -12
[27204.509687] mISDN_send: error -12
[27204.509690] mISDN_send: error -12
[27204.514510] mISDN_send: error -12
[27204.514513] mISDN_send: error -12
[27204.530513] mISDN_send: error -12
[27204.530516] mISDN_send: error -12
[27204.546515] mISDN_send: error -12
[27204.546518] mISDN_send: error -12
[27204.562516] mISDN_send: error -12
[27204.562520] mISDN_send: error -12
[27204.578533] mISDN_send: error -12
[27204.578537] mISDN_send: error -12
[27204.594543] mISDN_send: error -12
[27204.594546] mISDN_send: error -12
[27204.610530] mISDN_send: error -12
[27204.610533] mISDN_send: error -12
[27204.614701] mISDN_send: error -12
[27204.614705] mISDN_send: error -12
[27204.626527] mISDN_send: error -12
[27204.626530] mISDN_send: error -12
[27204.642528] mISDN_send: error -12
[27204.642531] mISDN_send: error -12
[27204.658530] mISDN_send: error -12
[27204.658533] mISDN_send: error -12
[27204.674532] mISDN_send: error -12
[27204.674536] mISDN_send: error -12
[27204.690535] mISDN_send: error -12
[27204.690538] mISDN_send: error -12
[27204.706608] mISDN_send: error -12
[27204.706611] mISDN_send: error -12
[27204.719716] mISDN_send: error -12
[27204.719719] mISDN_send: error -12
[27204.722539] mISDN_send: error -12
[27204.722543] mISDN_send: error -12
[27204.738541] mISDN_send: error -12
[27204.738544] mISDN_send: error -12
[27204.754544] mISDN_send: error -12
[27204.754547] mISDN_send: error -12
[27204.770546] mISDN_send: error -12
[27204.770549] mISDN_send: error -12
[27204.786548] mISDN_send: error -12
[27204.786552] mISDN_send: error -12
[27204.802550] mISDN_send: error -12
[27204.802554] mISDN_send: error -12
[27204.818553] mISDN_send: error -12
[27204.818556] mISDN_send: error -12
[27204.824605] mISDN_send: error -12
[27204.824609] mISDN_send: error -12
[27204.834555] mISDN_send: error -12
[27204.834559] mISDN_send: error -12
[27204.850557] mISDN_send: error -12
[27204.850560] mISDN_send: error -12
[27204.866559] mISDN_send: error -12
[27204.866562] mISDN_send: error -12
[27204.882561] mISDN_send: error -12
[27204.882565] mISDN_send: error -12
[27204.898563] mISDN_send: error -12
[27204.898566] mISDN_send: error -12
[27204.914566] mISDN_send: error -12
[27204.914569] mISDN_send: error -12
[27204.929620] mISDN_send: error -12
[27204.929623] mISDN_send: error -12
[27204.930566] mISDN_send: error -12
[27204.930568] mISDN_send: error -12
[27204.946570] mISDN_send: error -12
[27204.946573] mISDN_send: error -12
[27204.962573] mISDN_send: error -12
[27204.962576] mISDN_send: error -12
[27204.978574] mISDN_send: error -12
[27204.978578] mISDN_send: error -12
[27204.994578] mISDN_send: error -12
[27204.994581] mISDN_send: error -12
[27205.010579] mISDN_send: error -12
[27205.010583] mISDN_send: error -12
[27205.026581] mISDN_send: error -12
[27205.026584] mISDN_send: error -12
[27205.034634] mISDN_send: error -12
[27205.034637] mISDN_send: error -12
[27205.042584] mISDN_send: error -12
[27205.042587] mISDN_send: error -12
[27205.058586] mISDN_send: error -12
[27205.058589] mISDN_send: error -12
[27205.074587] mISDN_send: error -12
[27205.074590] mISDN_send: error -12
[27205.090590] mISDN_send: error -12
[27205.090593] mISDN_send: error -12
[27205.106592] mISDN_send: error -12
[27205.106595] mISDN_send: error -12
[27205.122594] mISDN_send: error -12
[27205.122598] mISDN_send: error -12
[27205.138597] mISDN_send: error -12
[27205.138600] mISDN_send: error -12
[27205.139646] mISDN_send: error -12
[27205.139648] mISDN_send: error -12
[27205.154598] mISDN_send: error -12
[27205.154602] mISDN_send: error -12
[27205.170601] mISDN_send: error -12
[27205.170604] mISDN_send: error -12
[27205.186604] mISDN_send: error -12
[27205.186607] mISDN_send: error -12
[27205.202606] mISDN_send: error -12
[27205.202609] mISDN_send: error -12
[27205.218608] mISDN_send: error -12
[27205.218611] mISDN_send: error -12
[27205.234610] mISDN_send: error -12
[27205.234613] mISDN_send: error -12
[27205.244664] mISDN_send: error -12
[27205.244667] mISDN_send: error -12
[27205.250612] mISDN_send: error -12
[27205.250615] mISDN_send: error -12
[27205.266615] mISDN_send: error -12
[27205.266618] mISDN_send: error -12
[27205.282617] mISDN_send: error -12
[27205.282620] mISDN_send: error -12
[27205.298619] mISDN_send: error -12
[27205.298622] mISDN_send: error -12
[27205.314622] mISDN_send: error -12
[27205.314625] mISDN_send: error -12
[27205.330623] mISDN_send: error -12
[27205.330627] mISDN_send: error -12
[27205.346626] mISDN_send: error -12
[27205.346629] mISDN_send: error -12
[27205.349678] mISDN_send: error -12
[27205.349681] mISDN_send: error -12
[27205.362629] mISDN_send: error -12
[27205.362632] mISDN_send: error -12
[27205.378630] mISDN_send: error -12
[27205.378633] mISDN_send: error -12
[27205.394633] mISDN_send: error -12
[27205.394636] mISDN_send: error -12
[27205.410635] mISDN_send: error -12
[27205.410638] mISDN_send: error -12
[27205.426637] mISDN_send: error -12
[27205.426641] mISDN_send: error -12
[27205.442639] mISDN_send: error -12
[27205.442642] mISDN_send: error -12
[27205.454693] mISDN_send: error -12
[27205.454697] mISDN_send: error -12
[27205.458641] mISDN_send: error -12
[27205.458644] mISDN_send: error -12
[27205.474644] mISDN_send: error -12
[27205.474647] mISDN_send: error -12
[27205.490646] mISDN_send: error -12
[27205.490649] mISDN_send: error -12
[27205.506648] mISDN_send: error -12
[27205.506651] mISDN_send: error -12
[27205.522650] mISDN_send: error -12
[27205.522653] mISDN_send: error -12
[27205.538652] mISDN_send: error -12
[27205.538656] mISDN_send: error -12
[27205.554655] mISDN_send: error -12
[27205.554658] mISDN_send: error -12
[27205.559707] mISDN_send: error -12
[27205.559710] mISDN_send: error -12
[27205.570658] mISDN_send: error -12
[27205.570661] mISDN_send: error -12
[27205.586659] mISDN_send: error -12
[27205.586662] mISDN_send: error -12
[27205.602662] mISDN_send: error -12
[27205.602665] mISDN_send: error -12
[27205.618664] mISDN_send: error -12
[27205.618667] mISDN_send: error -12
[27205.634666] mISDN_send: error -12
[27205.634669] mISDN_send: error -12
[27205.650669] mISDN_send: error -12
[27205.650672] mISDN_send: error -12
[27205.664722] mISDN_send: error -12
[27205.664725] mISDN_send: error -12
[27205.666668] mISDN_send: error -12
[27205.666671] mISDN_send: error -12
[27205.682673] mISDN_send: error -12
[27205.682676] mISDN_send: error -12
[27205.698675] mISDN_send: error -12
[27205.698678] mISDN_send: error -12
[27205.714677] mISDN_send: error -12
[27205.714680] mISDN_send: error -12
[27205.730679] mISDN_send: error -12
[27205.730682] mISDN_send: error -12
[27205.746681] mISDN_send: error -12
[27205.746684] mISDN_send: error -12
[27205.762683] mISDN_send: error -12
[27205.762687] mISDN_send: error -12
[27205.769737] mISDN_send: error -12
[27205.769740] mISDN_send: error -12
[27205.778687] mISDN_send: error -12
[27205.778690] mISDN_send: error -12
[27205.794688] mISDN_send: error -12
[27205.794691] mISDN_send: error -12
[27205.810691] mISDN_send: error -12
[27205.810694] mISDN_send: error -12
[27205.826693] mISDN_send: error -12
[27205.826696] mISDN_send: error -12
[27205.842695] mISDN_send: error -12
[27205.842698] mISDN_send: error -12
[27205.858704] mISDN_send: error -12
[27205.858707] mISDN_send: error -12
[27205.874786] mISDN_send: error -12
[27205.874789] mISDN_send: error -12
[27205.874791] mISDN_send: error -12
[27205.874793] mISDN_send: error -12
[27205.890701] mISDN_send: error -12
[27205.890705] mISDN_send: error -12
[27205.906704] mISDN_send: error -12
[27205.906707] mISDN_send: error -12
[27205.922706] mISDN_send: error -12
[27205.922709] mISDN_send: error -12
[27205.938709] mISDN_send: error -12
[27205.938712] mISDN_send: error -12
[27205.954710] mISDN_send: error -12
[27205.954713] mISDN_send: error -12
[27205.970712] mISDN_send: error -12
[27205.970716] mISDN_send: error -12
[27205.979766] mISDN_send: error -12
[27205.979769] mISDN_send: error -12
[27205.986716] mISDN_send: error -12
[27205.986719] mISDN_send: error -12
[27206.002716] mISDN_send: error -12
[27206.002719] mISDN_send: error -12
[27206.018720] mISDN_send: error -12
[27206.018723] mISDN_send: error -12
[27206.034722] mISDN_send: error -12
[27206.034725] mISDN_send: error -12
[27206.050724] mISDN_send: error -12
[27206.050727] mISDN_send: error -12
[27206.066726] mISDN_send: error -12
[27206.066729] mISDN_send: error -12
[27206.073374] base_sock_release(f6e15200) sk=f71ac000
[27218.660912] create_l2entity: ret 1 0
[27218.660919] create_l2entity: ret 2 0
[27218.661448] base_sock_release(f6e15380) sk=f71ac200
[27218.661475] base_sock_release(f6f65b00) sk=f71ac000
[27401.300599] create_l2entity: ret 1 0
[27401.300605] create_l2entity: ret 2 0
[27522.894827] mISDN_send: error -12
[27522.894832] mISDN_send: error -12
[27522.897878] mISDN_send: error -12
[27522.897882] mISDN_send: error -12
[27522.910828] mISDN_send: error -12
[27522.910832] mISDN_send: error -12
[27522.926829] mISDN_send: error -12
[27522.926832] mISDN_send: error -12
[27522.942831] mISDN_send: error -12
[27522.942835] mISDN_send: error -12
[27522.958833] mISDN_send: error -12
[27522.958837] mISDN_send: error -12
[27522.974836] mISDN_send: error -12
[27522.974839] mISDN_send: error -12
[27522.990838] mISDN_send: error -12
[27522.990841] mISDN_send: error -12
[27523.002892] mISDN_send: error -12
[27523.002895] mISDN_send: error -12
[27523.006840] mISDN_send: error -12
[27523.006843] mISDN_send: error -12
[27523.022843] mISDN_send: error -12
[27523.022846] mISDN_send: error -12
[27523.038845] mISDN_send: error -12
[27523.038848] mISDN_send: error -12
[27523.054847] mISDN_send: error -12
[27523.054850] mISDN_send: error -12
[27523.070849] mISDN_send: error -12
[27523.070852] mISDN_send: error -12
[27523.086851] mISDN_send: error -12
[27523.086854] mISDN_send: error -12
[27523.102853] mISDN_send: error -12
[27523.102856] mISDN_send: error -12
[27523.107906] mISDN_send: error -12
[27523.107909] mISDN_send: error -12
[27523.118857] mISDN_send: error -12
[27523.118860] mISDN_send: error -12
[27523.134858] mISDN_send: error -12
[27523.134861] mISDN_send: error -12
[27523.150860] mISDN_send: error -12
[27523.150864] mISDN_send: error -12
[27523.166863] mISDN_send: error -12
[27523.166866] mISDN_send: error -12
[27523.182865] mISDN_send: error -12
[27523.182868] mISDN_send: error -12
[27523.198868] mISDN_send: error -12
[27523.198871] mISDN_send: error -12
[27523.212921] mISDN_send: error -12
[27523.212924] mISDN_send: error -12
[27523.214867] mISDN_send: error -12
[27523.214870] mISDN_send: error -12
[27523.230871] mISDN_send: error -12
[27523.230875] mISDN_send: error -12
[27523.246874] mISDN_send: error -12
[27523.246877] mISDN_send: error -12
[27523.262876] mISDN_send: error -12
[27523.262879] mISDN_send: error -12
[27523.278878] mISDN_send: error -12
[27523.278881] mISDN_send: error -12
[27523.294880] mISDN_send: error -12
[27523.294883] mISDN_send: error -12
[27523.310882] mISDN_send: error -12
[27523.310885] mISDN_send: error -12
[27523.317936] mISDN_send: error -12
[27523.317939] mISDN_send: error -12
[27523.326885] mISDN_send: error -12
[27523.326889] mISDN_send: error -12
[27523.342888] mISDN_send: error -12
[27523.342891] mISDN_send: error -12
[27523.358889] mISDN_send: error -12
[27523.358893] mISDN_send: error -12
[27523.374891] mISDN_send: error -12
[27523.374895] mISDN_send: error -12
[27523.390894] mISDN_send: error -12
[27523.390897] mISDN_send: error -12
[27523.406896] mISDN_send: error -12
[27523.406899] mISDN_send: error -12
[27523.422896] mISDN_send: error -12
[27523.422899] mISDN_send: error -12
[27523.422902] mISDN_send: error -12
[27523.422904] mISDN_send: error -12
[27523.438900] mISDN_send: error -12
[27523.438903] mISDN_send: error -12
[27523.454903] mISDN_send: error -12
[27523.454906] mISDN_send: error -12
[27523.470905] mISDN_send: error -12
[27523.470908] mISDN_send: error -12
[27523.486908] mISDN_send: error -12
[27523.486911] mISDN_send: error -12
[27523.502909] mISDN_send: error -12
[27523.502912] mISDN_send: error -12
[27523.518911] mISDN_send: error -12
[27523.518915] mISDN_send: error -12
[27523.527840] mISDN_send: error -12
[27523.527843] mISDN_send: error -12
[27523.534915] mISDN_send: error -12
[27523.534918] mISDN_send: error -12
[27523.550916] mISDN_send: error -12
[27523.550919] mISDN_send: error -12
[27523.566918] mISDN_send: error -12
[27523.566921] mISDN_send: error -12
[27523.582920] mISDN_send: error -12
[27523.582924] mISDN_send: error -12
[27523.598923] mISDN_send: error -12
[27523.598926] mISDN_send: error -12
[27523.614926] mISDN_send: error -12
[27523.614929] mISDN_send: error -12
[27523.630927] mISDN_send: error -12
[27523.630931] mISDN_send: error -12
[27523.632854] mISDN_send: error -12
[27523.632857] mISDN_send: error -12
[27523.646929] mISDN_send: error -12
[27523.646932] mISDN_send: error -12
[27523.662932] mISDN_send: error -12
[27523.662935] mISDN_send: error -12
[27523.678934] mISDN_send: error -12
[27523.678937] mISDN_send: error -12
[27523.694936] mISDN_send: error -12
[27523.694939] mISDN_send: error -12
[27523.710938] mISDN_send: error -12
[27523.710942] mISDN_send: error -12
[27523.726940] mISDN_send: error -12
[27523.726943] mISDN_send: error -12
[27523.737870] mISDN_send: error -12
[27523.737873] mISDN_send: error -12
[27523.742943] mISDN_send: error -12
[27523.742946] mISDN_send: error -12
[27523.758945] mISDN_send: error -12
[27523.758948] mISDN_send: error -12
[27523.774947] mISDN_send: error -12
[27523.774950] mISDN_send: error -12
[27523.790949] mISDN_send: error -12
[27523.790953] mISDN_send: error -12
[27523.806951] mISDN_send: error -12
[27523.806954] mISDN_send: error -12
[27523.822953] mISDN_send: error -12
[27523.822957] mISDN_send: error -12
[27523.838956] mISDN_send: error -12
[27523.838959] mISDN_send: error -12
[27523.842884] mISDN_send: error -12
[27523.842887] mISDN_send: error -12
[27523.854959] mISDN_send: error -12
[27523.854962] mISDN_send: error -12
[27523.870961] mISDN_send: error -12
[27523.870964] mISDN_send: error -12
[27523.886963] mISDN_send: error -12
[27523.886966] mISDN_send: error -12
[27523.902965] mISDN_send: error -12
[27523.902968] mISDN_send: error -12
[27523.918967] mISDN_send: error -12
[27523.918971] mISDN_send: error -12
[27523.934969] mISDN_send: error -12
[27523.934972] mISDN_send: error -12
[27523.947898] mISDN_send: error -12
[27523.947901] mISDN_send: error -12
[27523.950971] mISDN_send: error -12
[27523.950975] mISDN_send: error -12
[27523.966974] mISDN_send: error -12
[27523.966977] mISDN_send: error -12
[27523.982976] mISDN_send: error -12
[27523.982979] mISDN_send: error -12
[27523.998979] mISDN_send: error -12
[27523.998982] mISDN_send: error -12
[27524.014981] mISDN_send: error -12
[27524.014984] mISDN_send: error -12
[27524.030983] mISDN_send: error -12
[27524.030986] mISDN_send: error -12
[27524.046985] mISDN_send: error -12
[27524.046988] mISDN_send: error -12
[27524.052913] mISDN_send: error -12
[27524.052916] mISDN_send: error -12
[27524.062988] mISDN_send: error -12
[27524.062991] mISDN_send: error -12
[27524.078989] mISDN_send: error -12
[27524.078992] mISDN_send: error -12
[27524.094992] mISDN_send: error -12
[27524.094995] mISDN_send: error -12
[27524.110994] mISDN_send: error -12
[27524.110997] mISDN_send: error -12
[27524.126996] mISDN_send: error -12
[27524.127000] mISDN_send: error -12
[27524.142998] mISDN_send: error -12
[27524.143001] mISDN_send: error -12
[27524.157927] mISDN_send: error -12
[27524.157930] mISDN_send: error -12
[27524.158998] mISDN_send: error -12
[27524.159001] mISDN_send: error -12
[27524.175003] mISDN_send: error -12
[27524.175006] mISDN_send: error -12
[27524.191005] mISDN_send: error -12
[27524.191008] mISDN_send: error -12
[27524.207007] mISDN_send: error -12
[27524.207011] mISDN_send: error -12
[27524.223010] mISDN_send: error -12
[27524.223013] mISDN_send: error -12
[27524.239011] mISDN_send: error -12
[27524.239014] mISDN_send: error -12
[27524.255014] mISDN_send: error -12
[27524.255017] mISDN_send: error -12
[27524.262942] mISDN_send: error -12
[27524.262945] mISDN_send: error -12
[27524.271017] mISDN_send: error -12
[27524.271020] mISDN_send: error -12
[27524.287018] mISDN_send: error -12
[27524.287021] mISDN_send: error -12
[27524.303020] mISDN_send: error -12
[27524.303024] mISDN_send: error -12
[27524.319022] mISDN_send: error -12
[27524.319026] mISDN_send: error -12
[27524.335025] mISDN_send: error -12
[27524.335028] mISDN_send: error -12
[27524.351027] mISDN_send: error -12
[27524.351030] mISDN_send: error -12
[27524.367029] mISDN_send: error -12
[27524.367033] mISDN_send: error -12
[27524.367953] mISDN_send: error -12
[27524.367956] mISDN_send: error -12
[27524.383032] mISDN_send: error -12
[27524.383035] mISDN_send: error -12
[27524.399034] mISDN_send: error -12
[27524.399037] mISDN_send: error -12
[27524.415036] mISDN_send: error -12
[27524.415039] mISDN_send: error -12
[27524.431039] mISDN_send: error -12
[27524.431042] mISDN_send: error -12
[27524.447040] mISDN_send: error -12
[27524.447044] mISDN_send: error -12
[27524.463043] mISDN_send: error -12
[27524.463046] mISDN_send: error -12
[27524.472971] mISDN_send: error -12
[27524.472974] mISDN_send: error -12
[27524.479045] mISDN_send: error -12
[27524.479048] mISDN_send: error -12
[27524.495047] mISDN_send: error -12
[27524.495050] mISDN_send: error -12
[27524.511050] mISDN_send: error -12
[27524.511053] mISDN_send: error -12
[27524.527051] mISDN_send: error -12
[27524.527054] mISDN_send: error -12
[27524.543056] mISDN_send: error -12
[27524.543059] mISDN_send: error -12
[27524.559070] mISDN_send: error -12
[27524.559073] mISDN_send: error -12
[27524.575065] mISDN_send: error -12
[27524.575068] mISDN_send: error -12
[27524.577986] mISDN_send: error -12
[27524.577989] mISDN_send: error -12
[27524.591132] mISDN_send: error -12
[27524.591136] mISDN_send: error -12
[27524.607063] mISDN_send: error -12
[27524.607066] mISDN_send: error -12
[27524.623065] mISDN_send: error -12
[27524.623068] mISDN_send: error -12
[27524.639068] mISDN_send: error -12
[27524.639071] mISDN_send: error -12
[27524.655070] mISDN_send: error -12
[27524.655073] mISDN_send: error -12
[27524.671071] mISDN_send: error -12
[27524.671074] mISDN_send: error -12
[27524.683001] mISDN_send: error -12
[27524.683004] mISDN_send: error -12
[27524.687074] mISDN_send: error -12
[27524.687077] mISDN_send: error -12
[27524.703078] mISDN_send: error -12
[27524.703082] mISDN_send: error -12
[27524.719090] mISDN_send: error -12
[27524.719094] mISDN_send: error -12
[27524.735105] mISDN_send: error -12
[27524.735108] mISDN_send: error -12
[27524.751089] mISDN_send: error -12
[27524.751092] mISDN_send: error -12
[27524.767085] mISDN_send: error -12
[27524.767088] mISDN_send: error -12
[27524.783087] mISDN_send: error -12
[27524.783091] mISDN_send: error -12
[27524.788015] mISDN_send: error -12
[27524.788019] mISDN_send: error -12
[27524.799090] mISDN_send: error -12
[27524.799093] mISDN_send: error -12
[27524.815092] mISDN_send: error -12
[27524.815095] mISDN_send: error -12
[27524.831094] mISDN_send: error -12
[27524.831098] mISDN_send: error -12
[27524.847097] mISDN_send: error -12
[27524.847100] mISDN_send: error -12
[27524.863098] mISDN_send: error -12
[27524.863102] mISDN_send: error -12
[27524.879101] mISDN_send: error -12
[27524.879104] mISDN_send: error -12
[27524.893030] mISDN_send: error -12
[27524.893033] mISDN_send: error -12
[27524.895101] mISDN_send: error -12
[27524.895104] mISDN_send: error -12
[27524.911105] mISDN_send: error -12
[27524.911108] mISDN_send: error -12
[27524.927107] mISDN_send: error -12
[27524.927110] mISDN_send: error -12
[27524.943110] mISDN_send: error -12
[27524.943113] mISDN_send: error -12
[27524.959112] mISDN_send: error -12
[27524.959115] mISDN_send: error -12
[27524.975114] mISDN_send: error -12
[27524.975117] mISDN_send: error -12
[27524.991116] mISDN_send: error -12
[27524.991119] mISDN_send: error -12
[27524.998044] mISDN_send: error -12
[27524.998047] mISDN_send: error -12
[27525.007119] mISDN_send: error -12
[27525.007122] mISDN_send: error -12
[27525.023122] mISDN_send: error -12
[27525.023125] mISDN_send: error -12
[27525.039123] mISDN_send: error -12
[27525.039126] mISDN_send: error -12
[27525.055126] mISDN_send: error -12
[27525.055129] mISDN_send: error -12
[27525.071128] mISDN_send: error -12
[27525.071131] mISDN_send: error -12
[27525.087130] mISDN_send: error -12
[27525.087133] mISDN_send: error -12
[27525.103130] mISDN_send: error -12
[27525.103133] mISDN_send: error -12
[27525.103135] mISDN_send: error -12
[27525.103138] mISDN_send: error -12
[27525.119134] mISDN_send: error -12
[27525.119137] mISDN_send: error -12
[27525.122261] base_sock_release(f6e15380) sk=f71ac000
[27555.330237] create_l2entity: ret 1 0
[27555.330244] create_l2entity: ret 2 0
[27555.330941] base_sock_release(f6e15200) sk=f6854800
[27555.330988] base_sock_release(f6f73800) sk=f6957800
[27576.769047] create_l2entity: ret 1 0
[27576.769054] create_l2entity: ret 2 0
[27576.769756] base_sock_release(f6e15380) sk=f6957800
[27576.769802] base_sock_release(f6f73800) sk=f6957c00
[27636.792979] create_l2entity: ret 1 0
[27636.792985] create_l2entity: ret 2 0
[27636.793691] base_sock_release(f6e15200) sk=f71ac800
[27636.793737] base_sock_release(f6f73800) sk=f71ac000
[27665.924278] create_l2entity: ret 1 0
[27665.924285] create_l2entity: ret 2 0
[27665.924981] base_sock_release(f6e15380) sk=f6957e00
[27665.925028] base_sock_release(f6f73800) sk=f71acc00
[27917.240386] create_l2entity: ret 1 0
[27917.240392] create_l2entity: ret 2 0
[28215.151311] mISDN_send: error -12
[28215.151316] mISDN_send: error -12
[28215.151319] mISDN_send: error -12
[28215.151321] mISDN_send: error -12
[28215.167312] mISDN_send: error -12
[28215.167316] mISDN_send: error -12
[28215.167318] mISDN_send: error -12
[28215.167321] mISDN_send: error -12
[28215.183313] mISDN_send: error -12
[28215.183317] mISDN_send: error -12
[28215.183319] mISDN_send: error -12
[28215.183321] mISDN_send: error -12
[28215.199315] mISDN_send: error -12
[28215.199318] mISDN_send: error -12
[28215.199321] mISDN_send: error -12
[28215.199323] mISDN_send: error -12
[28215.215317] mISDN_send: error -12
[28215.215321] mISDN_send: error -12
[28215.215323] mISDN_send: error -12
[28215.215325] mISDN_send: error -12
[28215.231319] mISDN_send: error -12
[28215.231323] mISDN_send: error -12
[28215.231325] mISDN_send: error -12
[28215.231327] mISDN_send: error -12
[28215.247322] mISDN_send: error -12
[28215.247325] mISDN_send: error -12
[28215.247328] mISDN_send: error -12
[28215.247330] mISDN_send: error -12
[28215.263324] mISDN_send: error -12
[28215.263328] mISDN_send: error -12
[28215.263330] mISDN_send: error -12
[28215.263333] mISDN_send: error -12
[28215.279326] mISDN_send: error -12
[28215.279329] mISDN_send: error -12
[28215.279332] mISDN_send: error -12
[28215.279334] mISDN_send: error -12
[28215.295329] mISDN_send: error -12
[28215.295332] mISDN_send: error -12
[28215.295334] mISDN_send: error -12
[28215.295337] mISDN_send: error -12
[28215.311331] mISDN_send: error -12
[28215.311334] mISDN_send: error -12
[28215.311336] mISDN_send: error -12
[28215.311339] mISDN_send: error -12
[28215.327334] mISDN_send: error -12
[28215.327337] mISDN_send: error -12
[28215.327339] mISDN_send: error -12
[28215.327341] mISDN_send: error -12
[28215.343336] mISDN_send: error -12
[28215.343339] mISDN_send: error -12
[28215.343341] mISDN_send: error -12
[28215.343343] mISDN_send: error -12
[28215.359337] mISDN_send: error -12
[28215.359340] mISDN_send: error -12
[28215.359343] mISDN_send: error -12
[28215.359345] mISDN_send: error -12
[28215.375340] mISDN_send: error -12
[28215.375344] mISDN_send: error -12
[28215.375346] mISDN_send: error -12
[28215.375348] mISDN_send: error -12
[28215.391342] mISDN_send: error -12
[28215.391345] mISDN_send: error -12
[28215.391348] mISDN_send: error -12
[28215.391350] mISDN_send: error -12
[28215.407344] mISDN_send: error -12
[28215.407347] mISDN_send: error -12
[28215.407349] mISDN_send: error -12
[28215.407352] mISDN_send: error -12
[28215.423484] mISDN_send: error -12
[28215.423487] mISDN_send: error -12
[28215.423490] mISDN_send: error -12
[28215.423492] mISDN_send: error -12
[28215.439349] mISDN_send: error -12
[28215.439352] mISDN_send: error -12
[28215.439354] mISDN_send: error -12
[28215.439356] mISDN_send: error -12
[28215.449787] mISDN_send: error -12
[28215.449791] mISDN_send: error -12
[28215.449793] mISDN_send: error -12
[28215.449795] mISDN_send: error -12
[28215.455351] mISDN_send: error -12
[28215.455354] mISDN_send: error -12
[28215.455357] mISDN_send: error -12
[28215.455359] mISDN_send: error -12
[28215.471353] mISDN_send: error -12
[28215.471356] mISDN_send: error -12
[28215.471359] mISDN_send: error -12
[28215.471361] mISDN_send: error -12
[28215.487355] mISDN_send: error -12
[28215.487359] mISDN_send: error -12
[28215.487361] mISDN_send: error -12
[28215.487363] mISDN_send: error -12
[28215.503357] mISDN_send: error -12
[28215.503361] mISDN_send: error -12
[28215.503363] mISDN_send: error -12
[28215.503365] mISDN_send: error -12
[28215.519360] mISDN_send: error -12
[28215.519363] mISDN_send: error -12
[28215.519365] mISDN_send: error -12
[28215.519368] mISDN_send: error -12
[28215.535362] mISDN_send: error -12
[28215.535365] mISDN_send: error -12
[28215.535367] mISDN_send: error -12
[28215.535370] mISDN_send: error -12
[28215.551364] mISDN_send: error -12
[28215.551368] mISDN_send: error -12
[28215.551370] mISDN_send: error -12
[28215.551372] mISDN_send: error -12
[28215.554800] mISDN_send: error -12
[28215.554803] mISDN_send: error -12
[28215.554806] mISDN_send: error -12
[28215.554808] mISDN_send: error -12
[28215.567408] mISDN_send: error -12
[28215.567411] mISDN_send: error -12
[28215.567414] mISDN_send: error -12
[28215.567416] mISDN_send: error -12
[28215.583370] mISDN_send: error -12
[28215.583373] mISDN_send: error -12
[28215.583375] mISDN_send: error -12
[28215.583377] mISDN_send: error -12
[28215.599371] mISDN_send: error -12
[28215.599374] mISDN_send: error -12
[28215.599376] mISDN_send: error -12
[28215.599379] mISDN_send: error -12
[28215.615373] mISDN_send: error -12
[28215.615376] mISDN_send: error -12
[28215.615379] mISDN_send: error -12
[28215.615381] mISDN_send: error -12
[28215.631376] mISDN_send: error -12
[28215.631379] mISDN_send: error -12
[28215.631381] mISDN_send: error -12
[28215.631383] mISDN_send: error -12
[28215.647377] mISDN_send: error -12
[28215.647381] mISDN_send: error -12
[28215.647383] mISDN_send: error -12
[28215.647385] mISDN_send: error -12
[28215.659815] mISDN_send: error -12
[28215.659818] mISDN_send: error -12
[28215.659821] mISDN_send: error -12
[28215.659823] mISDN_send: error -12
[28215.663380] mISDN_send: error -12
[28215.663384] mISDN_send: error -12
[28215.663386] mISDN_send: error -12
[28215.663388] mISDN_send: error -12
[28215.679382] mISDN_send: error -12
[28215.679385] mISDN_send: error -12
[28215.679388] mISDN_send: error -12
[28215.679390] mISDN_send: error -12
[28215.695384] mISDN_send: error -12
[28215.695388] mISDN_send: error -12
[28215.695390] mISDN_send: error -12
[28215.695392] mISDN_send: error -12
[28215.711387] mISDN_send: error -12
[28215.711390] mISDN_send: error -12
[28215.711393] mISDN_send: error -12
[28215.711395] mISDN_send: error -12
[28215.727389] mISDN_send: error -12
[28215.727392] mISDN_send: error -12
[28215.727394] mISDN_send: error -12
[28215.727396] mISDN_send: error -12
[28215.743391] mISDN_send: error -12
[28215.743394] mISDN_send: error -12
[28215.743396] mISDN_send: error -12
[28215.743399] mISDN_send: error -12
[28215.759394] mISDN_send: error -12
[28215.759397] mISDN_send: error -12
[28215.759399] mISDN_send: error -12
[28215.759402] mISDN_send: error -12
[28215.764830] mISDN_send: error -12
[28215.764833] mISDN_send: error -12
[28215.764835] mISDN_send: error -12
[28215.764837] mISDN_send: error -12
[28215.775397] mISDN_send: error -12
[28215.775400] mISDN_send: error -12
[28215.775402] mISDN_send: error -12
[28215.775404] mISDN_send: error -12
[28215.791398] mISDN_send: error -12
[28215.791401] mISDN_send: error -12
[28215.791403] mISDN_send: error -12
[28215.791405] mISDN_send: error -12
[28215.807400] mISDN_send: error -12
[28215.807403] mISDN_send: error -12
[28215.807405] mISDN_send: error -12
[28215.807408] mISDN_send: error -12
[28215.823402] mISDN_send: error -12
[28215.823405] mISDN_send: error -12
[28215.823407] mISDN_send: error -12
[28215.823410] mISDN_send: error -12
[28215.839405] mISDN_send: error -12
[28215.839408] mISDN_send: error -12
[28215.839410] mISDN_send: error -12
[28215.839412] mISDN_send: error -12
[28215.855407] mISDN_send: error -12
[28215.855410] mISDN_send: error -12
[28215.855412] mISDN_send: error -12
[28215.855415] mISDN_send: error -12
[28215.869844] mISDN_send: error -12
[28215.869847] mISDN_send: error -12
[28215.869849] mISDN_send: error -12
[28215.869851] mISDN_send: error -12
[28215.871407] mISDN_send: error -12
[28215.871409] mISDN_send: error -12
[28215.871412] mISDN_send: error -12
[28215.871414] mISDN_send: error -12
[28215.887411] mISDN_send: error -12
[28215.887414] mISDN_send: error -12
[28215.887417] mISDN_send: error -12
[28215.887419] mISDN_send: error -12
[28215.903413] mISDN_send: error -12
[28215.903417] mISDN_send: error -12
[28215.903419] mISDN_send: error -12
[28215.903421] mISDN_send: error -12
[28215.919416] mISDN_send: error -12
[28215.919419] mISDN_send: error -12
[28215.919421] mISDN_send: error -12
[28215.919424] mISDN_send: error -12
[28215.935555] mISDN_send: error -12
[28215.935558] mISDN_send: error -12
[28215.935560] mISDN_send: error -12
[28215.935563] mISDN_send: error -12
[28215.951420] mISDN_send: error -12
[28215.951423] mISDN_send: error -12
[28215.951425] mISDN_send: error -12
[28215.951427] mISDN_send: error -12
[28215.967422] mISDN_send: error -12
[28215.967425] mISDN_send: error -12
[28215.967428] mISDN_send: error -12
[28215.967430] mISDN_send: error -12
[28215.974985] mISDN_send: error -12
[28215.974988] mISDN_send: error -12
[28215.974990] mISDN_send: error -12
[28215.974992] mISDN_send: error -12
[28215.983425] mISDN_send: error -12
[28215.983429] mISDN_send: error -12
[28215.983431] mISDN_send: error -12
[28215.983433] mISDN_send: error -12
[28215.999426] mISDN_send: error -12
[28215.999429] mISDN_send: error -12
[28215.999432] mISDN_send: error -12
[28215.999434] mISDN_send: error -12
[28216.015429] mISDN_send: error -12
[28216.015432] mISDN_send: error -12
[28216.015434] mISDN_send: error -12
[28216.015436] mISDN_send: error -12
[28216.031445] mISDN_send: error -12
[28216.031448] mISDN_send: error -12
[28216.031450] mISDN_send: error -12
[28216.031452] mISDN_send: error -12
[28216.047458] mISDN_send: error -12
[28216.047461] mISDN_send: error -12
[28216.047463] mISDN_send: error -12
[28216.047465] mISDN_send: error -12
[28216.063443] mISDN_send: error -12
[28216.063446] mISDN_send: error -12
[28216.063449] mISDN_send: error -12
[28216.063451] mISDN_send: error -12
[28216.079438] mISDN_send: error -12
[28216.079441] mISDN_send: error -12
[28216.079443] mISDN_send: error -12
[28216.079445] mISDN_send: error -12
[28216.079996] mISDN_send: error -12
[28216.079998] mISDN_send: error -12
[28216.080000] mISDN_send: error -12
[28216.080002] mISDN_send: error -12
[28216.095440] mISDN_send: error -12
[28216.095443] mISDN_send: error -12
[28216.095445] mISDN_send: error -12
[28216.095447] mISDN_send: error -12
[28216.111443] mISDN_send: error -12
[28216.111446] mISDN_send: error -12
[28216.111448] mISDN_send: error -12
[28216.111451] mISDN_send: error -12
[28216.127445] mISDN_send: error -12
[28216.127448] mISDN_send: error -12
[28216.127450] mISDN_send: error -12
[28216.127453] mISDN_send: error -12
[28216.143447] mISDN_send: error -12
[28216.143450] mISDN_send: error -12
[28216.143452] mISDN_send: error -12
[28216.143455] mISDN_send: error -12
[28216.159449] mISDN_send: error -12
[28216.159452] mISDN_send: error -12
[28216.159454] mISDN_send: error -12
[28216.159456] mISDN_send: error -12
[28216.175451] mISDN_send: error -12
[28216.175454] mISDN_send: error -12
[28216.175456] mISDN_send: error -12
[28216.175459] mISDN_send: error -12
[28216.185014] mISDN_send: error -12
[28216.185017] mISDN_send: error -12
[28216.185020] mISDN_send: error -12
[28216.185022] mISDN_send: error -12
[28216.191454] mISDN_send: error -12
[28216.191457] mISDN_send: error -12
[28216.191459] mISDN_send: error -12
[28216.191462] mISDN_send: error -12
[28216.207455] mISDN_send: error -12
[28216.207458] mISDN_send: error -12
[28216.207461] mISDN_send: error -12
[28216.207463] mISDN_send: error -12
[28216.223458] mISDN_send: error -12
[28216.223461] mISDN_send: error -12
[28216.223464] mISDN_send: error -12
[28216.223466] mISDN_send: error -12
[28216.239460] mISDN_send: error -12
[28216.239463] mISDN_send: error -12
[28216.239465] mISDN_send: error -12
[28216.239467] mISDN_send: error -12
[28216.255462] mISDN_send: error -12
[28216.255466] mISDN_send: error -12
[28216.255468] mISDN_send: error -12
[28216.255470] mISDN_send: error -12
[28216.271465] mISDN_send: error -12
[28216.271468] mISDN_send: error -12
[28216.271470] mISDN_send: error -12
[28216.271472] mISDN_send: error -12
[28216.287467] mISDN_send: error -12
[28216.287470] mISDN_send: error -12
[28216.287472] mISDN_send: error -12
[28216.287474] mISDN_send: error -12
[28216.290027] mISDN_send: error -12
[28216.290030] mISDN_send: error -12
[28216.290032] mISDN_send: error -12
[28216.290034] mISDN_send: error -12
[28216.303469] mISDN_send: error -12
[28216.303472] mISDN_send: error -12
[28216.303475] mISDN_send: error -12
[28216.303477] mISDN_send: error -12
[28216.319471] mISDN_send: error -12
[28216.319474] mISDN_send: error -12
[28216.319476] mISDN_send: error -12
[28216.319479] mISDN_send: error -12
[28216.335473] mISDN_send: error -12
[28216.335476] mISDN_send: error -12
[28216.335478] mISDN_send: error -12
[28216.335481] mISDN_send: error -12
[28216.351476] mISDN_send: error -12
[28216.351479] mISDN_send: error -12
[28216.351481] mISDN_send: error -12
[28216.351483] mISDN_send: error -12
[28216.367478] mISDN_send: error -12
[28216.367481] mISDN_send: error -12
[28216.367484] mISDN_send: error -12
[28216.367486] mISDN_send: error -12
[28216.383480] mISDN_send: error -12
[28216.383483] mISDN_send: error -12
[28216.383485] mISDN_send: error -12
[28216.383487] mISDN_send: error -12
[28216.395042] mISDN_send: error -12
[28216.395045] mISDN_send: error -12
[28216.395048] mISDN_send: error -12
[28216.395050] mISDN_send: error -12
[28216.399483] mISDN_send: error -12
[28216.399486] mISDN_send: error -12
[28216.399488] mISDN_send: error -12
[28216.399491] mISDN_send: error -12
[28216.415484] mISDN_send: error -12
[28216.415487] mISDN_send: error -12
[28216.415489] mISDN_send: error -12
[28216.415492] mISDN_send: error -12
[28216.431487] mISDN_send: error -12
[28216.431490] mISDN_send: error -12
[28216.431492] mISDN_send: error -12
[28216.431494] mISDN_send: error -12
[28216.447626] mISDN_send: error -12
[28216.447629] mISDN_send: error -12
[28216.447631] mISDN_send: error -12
[28216.447634] mISDN_send: error -12
[28216.463498] mISDN_send: error -12
[28216.463501] mISDN_send: error -12
[28216.463503] mISDN_send: error -12
[28216.463505] mISDN_send: error -12
[28216.479507] mISDN_send: error -12
[28216.479509] mISDN_send: error -12
[28216.479512] mISDN_send: error -12
[28216.479514] mISDN_send: error -12
[28216.495496] mISDN_send: error -12
[28216.495499] mISDN_send: error -12
[28216.495501] mISDN_send: error -12
[28216.495503] mISDN_send: error -12
[28216.500182] mISDN_send: error -12
[28216.500184] mISDN_send: error -12
[28216.500187] mISDN_send: error -12
[28216.500189] mISDN_send: error -12
[28216.511499] mISDN_send: error -12
[28216.511502] mISDN_send: error -12
[28216.511504] mISDN_send: error -12
[28216.511506] mISDN_send: error -12
[28216.527500] mISDN_send: error -12
[28216.527503] mISDN_send: error -12
[28216.527505] mISDN_send: error -12
[28216.527507] mISDN_send: error -12
[28216.543502] mISDN_send: error -12
[28216.543505] mISDN_send: error -12
[28216.543508] mISDN_send: error -12
[28216.543510] mISDN_send: error -12
[28216.559504] mISDN_send: error -12
[28216.559507] mISDN_send: error -12
[28216.559510] mISDN_send: error -12
[28216.559512] mISDN_send: error -12
[28216.575507] mISDN_send: error -12
[28216.575510] mISDN_send: error -12
[28216.575512] mISDN_send: error -12
[28216.575514] mISDN_send: error -12
[28216.591509] mISDN_send: error -12
[28216.591512] mISDN_send: error -12
[28216.591515] mISDN_send: error -12
[28216.591517] mISDN_send: error -12
[28216.605196] mISDN_send: error -12
[28216.605200] mISDN_send: error -12
[28216.605202] mISDN_send: error -12
[28216.605204] mISDN_send: error -12
[28216.607509] mISDN_send: error -12
[28216.607512] mISDN_send: error -12
[28216.607514] mISDN_send: error -12
[28216.607516] mISDN_send: error -12
[28216.623514] mISDN_send: error -12
[28216.623517] mISDN_send: error -12
[28216.623520] mISDN_send: error -12
[28216.623522] mISDN_send: error -12
[28216.639516] mISDN_send: error -12
[28216.639519] mISDN_send: error -12
[28216.639521] mISDN_send: error -12
[28216.639523] mISDN_send: error -12
[28216.655518] mISDN_send: error -12
[28216.655521] mISDN_send: error -12
[28216.655523] mISDN_send: error -12
[28216.655525] mISDN_send: error -12
[28216.671520] mISDN_send: error -12
[28216.671523] mISDN_send: error -12
[28216.671525] mISDN_send: error -12
[28216.671527] mISDN_send: error -12
[28216.687523] mISDN_send: error -12
[28216.687526] mISDN_send: error -12
[28216.687528] mISDN_send: error -12
[28216.687530] mISDN_send: error -12
[28216.703524] mISDN_send: error -12
[28216.703527] mISDN_send: error -12
[28216.703530] mISDN_send: error -12
[28216.703532] mISDN_send: error -12
[28216.710211] mISDN_send: error -12
[28216.710214] mISDN_send: error -12
[28216.710216] mISDN_send: error -12
[28216.710218] mISDN_send: error -12
[28216.719528] mISDN_send: error -12
[28216.719531] mISDN_send: error -12
[28216.719534] mISDN_send: error -12
[28216.719536] mISDN_send: error -12
[28216.735529] mISDN_send: error -12
[28216.735532] mISDN_send: error -12
[28216.735535] mISDN_send: error -12
[28216.735537] mISDN_send: error -12
[28216.751531] mISDN_send: error -12
[28216.751534] mISDN_send: error -12
[28216.751536] mISDN_send: error -12
[28216.751538] mISDN_send: error -12
[28216.767534] mISDN_send: error -12
[28216.767537] mISDN_send: error -12
[28216.767539] mISDN_send: error -12
[28216.767541] mISDN_send: error -12
[28216.783536] mISDN_send: error -12
[28216.783539] mISDN_send: error -12
[28216.783541] mISDN_send: error -12
[28216.783543] mISDN_send: error -12
[28216.799538] mISDN_send: error -12
[28216.799541] mISDN_send: error -12
[28216.799544] mISDN_send: error -12
[28216.799546] mISDN_send: error -12
[28216.815226] mISDN_send: error -12
[28216.815229] mISDN_send: error -12
[28216.815231] mISDN_send: error -12
[28216.815233] mISDN_send: error -12
[28216.815538] mISDN_send: error -12
[28216.815541] mISDN_send: error -12
[28216.815543] mISDN_send: error -12
[28216.815545] mISDN_send: error -12
[28216.831542] mISDN_send: error -12
[28216.831545] mISDN_send: error -12
[28216.831548] mISDN_send: error -12
[28216.831550] mISDN_send: error -12
[28216.847545] mISDN_send: error -12
[28216.847548] mISDN_send: error -12
[28216.847550] mISDN_send: error -12
[28216.847553] mISDN_send: error -12
[28216.863547] mISDN_send: error -12
[28216.863550] mISDN_send: error -12
[28216.863552] mISDN_send: error -12
[28216.863555] mISDN_send: error -12
[28216.879549] mISDN_send: error -12
[28216.879552] mISDN_send: error -12
[28216.879554] mISDN_send: error -12
[28216.879557] mISDN_send: error -12
[28216.895551] mISDN_send: error -12
[28216.895554] mISDN_send: error -12
[28216.895557] mISDN_send: error -12
[28216.895559] mISDN_send: error -12
[28216.911554] mISDN_send: error -12
[28216.911557] mISDN_send: error -12
[28216.911559] mISDN_send: error -12
[28216.911561] mISDN_send: error -12
[28216.920240] mISDN_send: error -12
[28216.920243] mISDN_send: error -12
[28216.920246] mISDN_send: error -12
[28216.920248] mISDN_send: error -12
[28216.927557] mISDN_send: error -12
[28216.927560] mISDN_send: error -12
[28216.927562] mISDN_send: error -12
[28216.927564] mISDN_send: error -12
[28216.943558] mISDN_send: error -12
[28216.943561] mISDN_send: error -12
[28216.943563] mISDN_send: error -12
[28216.943565] mISDN_send: error -12
[28216.959697] mISDN_send: error -12
[28216.959700] mISDN_send: error -12
[28216.959703] mISDN_send: error -12
[28216.959705] mISDN_send: error -12
[28216.975563] mISDN_send: error -12
[28216.975566] mISDN_send: error -12
[28216.975568] mISDN_send: error -12
[28216.975570] mISDN_send: error -12
[28216.991565] mISDN_send: error -12
[28216.991568] mISDN_send: error -12
[28216.991570] mISDN_send: error -12
[28216.991572] mISDN_send: error -12
[28217.007567] mISDN_send: error -12
[28217.007570] mISDN_send: error -12
[28217.007572] mISDN_send: error -12
[28217.007574] mISDN_send: error -12
[28217.023570] mISDN_send: error -12
[28217.023573] mISDN_send: error -12
[28217.023575] mISDN_send: error -12
[28217.023577] mISDN_send: error -12
[28217.025380] mISDN_send: error -12
[28217.025383] mISDN_send: error -12
[28217.025385] mISDN_send: error -12
[28217.025387] mISDN_send: error -12
[28217.039571] mISDN_send: error -12
[28217.039574] mISDN_send: error -12
[28217.039576] mISDN_send: error -12
[28217.039578] mISDN_send: error -12
[28217.055574] mISDN_send: error -12
[28217.055577] mISDN_send: error -12
[28217.055579] mISDN_send: error -12
[28217.055581] mISDN_send: error -12
[28217.071577] mISDN_send: error -12
[28217.071579] mISDN_send: error -12
[28217.071582] mISDN_send: error -12
[28217.071584] mISDN_send: error -12
[28217.087578] mISDN_send: error -12
[28217.087581] mISDN_send: error -12
[28217.087583] mISDN_send: error -12
[28217.087585] mISDN_send: error -12
[28217.103581] mISDN_send: error -12
[28217.103584] mISDN_send: error -12
[28217.103586] mISDN_send: error -12
[28217.103588] mISDN_send: error -12
[28217.119583] mISDN_send: error -12
[28217.119586] mISDN_send: error -12
[28217.119588] mISDN_send: error -12
[28217.119591] mISDN_send: error -12
[28217.130395] mISDN_send: error -12
[28217.130397] mISDN_send: error -12
[28217.130400] mISDN_send: error -12
[28217.130402] mISDN_send: error -12
[28217.135585] mISDN_send: error -12
[28217.135588] mISDN_send: error -12
[28217.135590] mISDN_send: error -12
[28217.135592] mISDN_send: error -12
[28217.151587] mISDN_send: error -12
[28217.151590] mISDN_send: error -12
[28217.151593] mISDN_send: error -12
[28217.151595] mISDN_send: error -12
[28217.167589] mISDN_send: error -12
[28217.167592] mISDN_send: error -12
[28217.167595] mISDN_send: error -12
[28217.167597] mISDN_send: error -12
[28217.183592] mISDN_send: error -12
[28217.183595] mISDN_send: error -12
[28217.183597] mISDN_send: error -12
[28217.183599] mISDN_send: error -12
[28217.199594] mISDN_send: error -12
[28217.199597] mISDN_send: error -12
[28217.199599] mISDN_send: error -12
[28217.199601] mISDN_send: error -12
[28217.215596] mISDN_send: error -12
[28217.215599] mISDN_send: error -12
[28217.215601] mISDN_send: error -12
[28217.215604] mISDN_send: error -12
[28217.231599] mISDN_send: error -12
[28217.231602] mISDN_send: error -12
[28217.231604] mISDN_send: error -12
[28217.231606] mISDN_send: error -12
[28217.235409] mISDN_send: error -12
[28217.235412] mISDN_send: error -12
[28217.235414] mISDN_send: error -12
[28217.235416] mISDN_send: error -12
[28217.247601] mISDN_send: error -12
[28217.247604] mISDN_send: error -12
[28217.247606] mISDN_send: error -12
[28217.247609] mISDN_send: error -12
[28217.263603] mISDN_send: error -12
[28217.263606] mISDN_send: error -12
[28217.263609] mISDN_send: error -12
[28217.263611] mISDN_send: error -12
[28217.279605] mISDN_send: error -12
[28217.279608] mISDN_send: error -12
[28217.279610] mISDN_send: error -12
[28217.279612] mISDN_send: error -12
[28217.295607] mISDN_send: error -12
[28217.295610] mISDN_send: error -12
[28217.295612] mISDN_send: error -12
[28217.295615] mISDN_send: error -12
[28217.311610] mISDN_send: error -12
[28217.311613] mISDN_send: error -12
[28217.311615] mISDN_send: error -12
[28217.311617] mISDN_send: error -12
[28217.327612] mISDN_send: error -12
[28217.327615] mISDN_send: error -12
[28217.327617] mISDN_send: error -12
[28217.327619] mISDN_send: error -12
[28217.340424] mISDN_send: error -12
[28217.340427] mISDN_send: error -12
[28217.340429] mISDN_send: error -12
[28217.340431] mISDN_send: error -12
[28217.343611] mISDN_send: error -12
[28217.343614] mISDN_send: error -12
[28217.343616] mISDN_send: error -12
[28217.343619] mISDN_send: error -12
[28217.359617] mISDN_send: error -12
[28217.359620] mISDN_send: error -12
[28217.359622] mISDN_send: error -12
[28217.359624] mISDN_send: error -12
[28217.375618] mISDN_send: error -12
[28217.375621] mISDN_send: error -12
[28217.375623] mISDN_send: error -12
[28217.375626] mISDN_send: error -12
[28217.391621] mISDN_send: error -12
[28217.391624] mISDN_send: error -12
[28217.391626] mISDN_send: error -12
[28217.391628] mISDN_send: error -12
[28217.395064] base_sock_release(f6e15380) sk=f71ac800
[28224.299699] create_l2entity: ret 1 0
[28224.299705] create_l2entity: ret 2 0
[28226.976955] l2mgr: addr:0 prim 1f04 F
[28563.696019] bsc_hack[3226]: segfault at 0 ip 08058c37 sp bfedc7c0 error 4 in bsc_hack[8048000+45000]
[28563.696181] base_sock_release(f6e15200) sk=f71ac000
[28574.712322] create_l2entity: ret 1 0
[28574.712328] create_l2entity: ret 2 0
[28576.273653] l2mgr: addr:0 prim 1f04 F
[28834.517626] mISDN_send: error -12
[28834.517631] mISDN_send: error -12
[28834.533626] mISDN_send: error -12
[28834.533630] mISDN_send: error -12
[28834.549627] mISDN_send: error -12
[28834.549631] mISDN_send: error -12
[28834.565629] mISDN_send: error -12
[28834.565632] mISDN_send: error -12
[28834.581632] mISDN_send: error -12
[28834.581635] mISDN_send: error -12
[28834.597634] mISDN_send: error -12
[28834.597637] mISDN_send: error -12
[28834.613635] mISDN_send: error -12
[28834.613639] mISDN_send: error -12
[28834.629639] mISDN_send: error -12
[28834.629642] mISDN_send: error -12
[28834.645641] mISDN_send: error -12
[28834.645644] mISDN_send: error -12
[28834.661643] mISDN_send: error -12
[28834.661646] mISDN_send: error -12
[28834.677645] mISDN_send: error -12
[28834.677648] mISDN_send: error -12
[28834.693647] mISDN_send: error -12
[28834.693651] mISDN_send: error -12
[28834.709650] mISDN_send: error -12
[28834.709653] mISDN_send: error -12
[28834.725651] mISDN_send: error -12
[28834.725655] mISDN_send: error -12
[28834.741654] mISDN_send: error -12
[28834.741657] mISDN_send: error -12
[28834.757656] mISDN_send: error -12
[28834.757660] mISDN_send: error -12
[28834.773658] mISDN_send: error -12
[28834.773662] mISDN_send: error -12
[28834.789661] mISDN_send: error -12
[28834.789664] mISDN_send: error -12
[28834.805663] mISDN_send: error -12
[28834.805667] mISDN_send: error -12
[28834.819967] mISDN_send: error -12
[28834.819970] mISDN_send: error -12
[28834.821665] mISDN_send: error -12
[28834.821668] mISDN_send: error -12
[28834.837668] mISDN_send: error -12
[28834.837671] mISDN_send: error -12
[28834.853670] mISDN_send: error -12
[28834.853673] mISDN_send: error -12
[28834.869672] mISDN_send: error -12
[28834.869675] mISDN_send: error -12
[28834.885681] mISDN_send: error -12
[28834.885684] mISDN_send: error -12
[28834.901676] mISDN_send: error -12
[28834.901679] mISDN_send: error -12
[28834.917679] mISDN_send: error -12
[28834.917682] mISDN_send: error -12
[28834.924982] mISDN_send: error -12
[28834.924985] mISDN_send: error -12
[28834.933682] mISDN_send: error -12
[28834.933685] mISDN_send: error -12
[28834.949683] mISDN_send: error -12
[28834.949686] mISDN_send: error -12
[28834.965685] mISDN_send: error -12
[28834.965688] mISDN_send: error -12
[28834.981687] mISDN_send: error -12
[28834.981690] mISDN_send: error -12
[28834.997690] mISDN_send: error -12
[28834.997693] mISDN_send: error -12
[28835.013692] mISDN_send: error -12
[28835.013695] mISDN_send: error -12
[28835.029694] mISDN_send: error -12
[28835.029697] mISDN_send: error -12
[28835.029993] mISDN_send: error -12
[28835.029996] mISDN_send: error -12
[28835.045697] mISDN_send: error -12
[28835.045700] mISDN_send: error -12
[28835.061698] mISDN_send: error -12
[28835.061701] mISDN_send: error -12
[28835.077701] mISDN_send: error -12
[28835.077704] mISDN_send: error -12
[28835.093703] mISDN_send: error -12
[28835.093706] mISDN_send: error -12
[28835.109705] mISDN_send: error -12
[28835.109708] mISDN_send: error -12
[28835.125708] mISDN_send: error -12
[28835.125711] mISDN_send: error -12
[28835.135011] mISDN_send: error -12
[28835.135014] mISDN_send: error -12
[28835.141710] mISDN_send: error -12
[28835.141714] mISDN_send: error -12
[28835.157712] mISDN_send: error -12
[28835.157715] mISDN_send: error -12
[28835.173715] mISDN_send: error -12
[28835.173718] mISDN_send: error -12
[28835.189716] mISDN_send: error -12
[28835.189719] mISDN_send: error -12
[28835.205720] mISDN_send: error -12
[28835.205723] mISDN_send: error -12
[28835.221721] mISDN_send: error -12
[28835.221724] mISDN_send: error -12
[28835.237723] mISDN_send: error -12
[28835.237726] mISDN_send: error -12
[28835.240027] mISDN_send: error -12
[28835.240030] mISDN_send: error -12
[28835.253725] mISDN_send: error -12
[28835.253729] mISDN_send: error -12
[28835.269727] mISDN_send: error -12
[28835.269731] mISDN_send: error -12
[28835.285730] mISDN_send: error -12
[28835.285734] mISDN_send: error -12
[28835.301732] mISDN_send: error -12
[28835.301735] mISDN_send: error -12
[28835.317734] mISDN_send: error -12
[28835.317738] mISDN_send: error -12
[28835.333737] mISDN_send: error -12
[28835.333740] mISDN_send: error -12
[28835.345040] mISDN_send: error -12
[28835.345044] mISDN_send: error -12
[28835.349739] mISDN_send: error -12
[28835.349743] mISDN_send: error -12
[28835.365741] mISDN_send: error -12
[28835.365744] mISDN_send: error -12
[28835.381743] mISDN_send: error -12
[28835.381747] mISDN_send: error -12
[28835.397745] mISDN_send: error -12
[28835.397748] mISDN_send: error -12
[28835.413748] mISDN_send: error -12
[28835.413751] mISDN_send: error -12
[28835.429750] mISDN_send: error -12
[28835.429753] mISDN_send: error -12
[28835.445752] mISDN_send: error -12
[28835.445755] mISDN_send: error -12
[28835.450054] mISDN_send: error -12
[28835.450057] mISDN_send: error -12
[28835.461755] mISDN_send: error -12
[28835.461759] mISDN_send: error -12
[28835.477756] mISDN_send: error -12
[28835.477759] mISDN_send: error -12
[28835.493759] mISDN_send: error -12
[28835.493762] mISDN_send: error -12
[28835.509761] mISDN_send: error -12
[28835.509764] mISDN_send: error -12
[28835.525763] mISDN_send: error -12
[28835.525766] mISDN_send: error -12
[28835.541766] mISDN_send: error -12
[28835.541769] mISDN_send: error -12
[28835.555070] mISDN_send: error -12
[28835.555073] mISDN_send: error -12
[28835.557768] mISDN_send: error -12
[28835.557771] mISDN_send: error -12
[28835.573770] mISDN_send: error -12
[28835.573773] mISDN_send: error -12
[28835.589772] mISDN_send: error -12
[28835.589775] mISDN_send: error -12
[28835.605774] mISDN_send: error -12
[28835.605777] mISDN_send: error -12
[28835.621777] mISDN_send: error -12
[28835.621780] mISDN_send: error -12
[28835.637779] mISDN_send: error -12
[28835.637782] mISDN_send: error -12
[28835.653781] mISDN_send: error -12
[28835.653785] mISDN_send: error -12
[28835.660084] mISDN_send: error -12
[28835.660087] mISDN_send: error -12
[28835.669784] mISDN_send: error -12
[28835.669788] mISDN_send: error -12
[28835.685788] mISDN_send: error -12
[28835.685791] mISDN_send: error -12
[28835.701788] mISDN_send: error -12
[28835.701791] mISDN_send: error -12
[28835.717790] mISDN_send: error -12
[28835.717793] mISDN_send: error -12
[28835.733792] mISDN_send: error -12
[28835.733795] mISDN_send: error -12
[28835.749795] mISDN_send: error -12
[28835.749799] mISDN_send: error -12
[28835.765099] mISDN_send: error -12
[28835.765102] mISDN_send: error -12
[28835.765795] mISDN_send: error -12
[28835.765798] mISDN_send: error -12
[28835.781799] mISDN_send: error -12
[28835.781802] mISDN_send: error -12
[28835.797802] mISDN_send: error -12
[28835.797805] mISDN_send: error -12
[28835.813803] mISDN_send: error -12
[28835.813806] mISDN_send: error -12
[28835.829806] mISDN_send: error -12
[28835.829809] mISDN_send: error -12
[28835.845808] mISDN_send: error -12
[28835.845811] mISDN_send: error -12
[28835.861810] mISDN_send: error -12
[28835.861813] mISDN_send: error -12
[28835.870113] mISDN_send: error -12
[28835.870116] mISDN_send: error -12
[28835.877813] mISDN_send: error -12
[28835.877817] mISDN_send: error -12
[28835.893815] mISDN_send: error -12
[28835.893818] mISDN_send: error -12
[28835.909816] mISDN_send: error -12
[28835.909820] mISDN_send: error -12
[28835.925819] mISDN_send: error -12
[28835.925822] mISDN_send: error -12
[28835.941821] mISDN_send: error -12
[28835.941824] mISDN_send: error -12
[28835.957824] mISDN_send: error -12
[28835.957827] mISDN_send: error -12
[28835.973826] mISDN_send: error -12
[28835.973829] mISDN_send: error -12
[28835.975125] mISDN_send: error -12
[28835.975128] mISDN_send: error -12
[28835.989828] mISDN_send: error -12
[28835.989831] mISDN_send: error -12
[28836.005830] mISDN_send: error -12
[28836.005833] mISDN_send: error -12
[28836.021832] mISDN_send: error -12
[28836.021836] mISDN_send: error -12
[28836.037835] mISDN_send: error -12
[28836.037838] mISDN_send: error -12
[28836.053908] mISDN_send: error -12
[28836.053911] mISDN_send: error -12
[28836.069839] mISDN_send: error -12
[28836.069842] mISDN_send: error -12
[28836.080143] mISDN_send: error -12
[28836.080146] mISDN_send: error -12
[28836.085842] mISDN_send: error -12
[28836.085845] mISDN_send: error -12
[28836.101844] mISDN_send: error -12
[28836.101847] mISDN_send: error -12
[28836.117846] mISDN_send: error -12
[28836.117849] mISDN_send: error -12
[28836.133848] mISDN_send: error -12
[28836.133851] mISDN_send: error -12
[28836.149850] mISDN_send: error -12
[28836.149853] mISDN_send: error -12
[28836.165853] mISDN_send: error -12
[28836.165856] mISDN_send: error -12
[28836.181855] mISDN_send: error -12
[28836.181858] mISDN_send: error -12
[28836.185157] mISDN_send: error -12
[28836.185160] mISDN_send: error -12
[28836.197857] mISDN_send: error -12
[28836.197860] mISDN_send: error -12
[28836.213859] mISDN_send: error -12
[28836.213862] mISDN_send: error -12
[28836.229861] mISDN_send: error -12
[28836.229865] mISDN_send: error -12
[28836.245863] mISDN_send: error -12
[28836.245867] mISDN_send: error -12
[28836.261866] mISDN_send: error -12
[28836.261869] mISDN_send: error -12
[28836.277874] mISDN_send: error -12
[28836.277877] mISDN_send: error -12
[28836.290172] mISDN_send: error -12
[28836.290175] mISDN_send: error -12
[28836.293884] mISDN_send: error -12
[28836.293887] mISDN_send: error -12
[28836.309873] mISDN_send: error -12
[28836.309876] mISDN_send: error -12
[28836.325875] mISDN_send: error -12
[28836.325878] mISDN_send: error -12
[28836.341877] mISDN_send: error -12
[28836.341880] mISDN_send: error -12
[28836.357879] mISDN_send: error -12
[28836.357882] mISDN_send: error -12
[28836.373882] mISDN_send: error -12
[28836.373885] mISDN_send: error -12
[28836.389884] mISDN_send: error -12
[28836.389887] mISDN_send: error -12
[28836.395186] mISDN_send: error -12
[28836.395189] mISDN_send: error -12
[28836.405887] mISDN_send: error -12
[28836.405890] mISDN_send: error -12
[28836.421888] mISDN_send: error -12
[28836.421891] mISDN_send: error -12
[28836.437890] mISDN_send: error -12
[28836.437894] mISDN_send: error -12
[28836.453893] mISDN_send: error -12
[28836.453896] mISDN_send: error -12
[28836.469895] mISDN_send: error -12
[28836.469898] mISDN_send: error -12
[28836.485897] mISDN_send: error -12
[28836.485900] mISDN_send: error -12
[28836.500201] mISDN_send: error -12
[28836.500204] mISDN_send: error -12
[28836.501898] mISDN_send: error -12
[28836.501900] mISDN_send: error -12
[28836.517902] mISDN_send: error -12
[28836.517905] mISDN_send: error -12
[28836.533904] mISDN_send: error -12
[28836.533907] mISDN_send: error -12
[28836.549907] mISDN_send: error -12
[28836.549910] mISDN_send: error -12
[28836.565915] mISDN_send: error -12
[28836.565919] mISDN_send: error -12
[28836.581911] mISDN_send: error -12
[28836.581914] mISDN_send: error -12
[28836.597913] mISDN_send: error -12
[28836.597916] mISDN_send: error -12
[28836.605216] mISDN_send: error -12
[28836.605219] mISDN_send: error -12
[28836.613916] mISDN_send: error -12
[28836.613919] mISDN_send: error -12
[28836.629918] mISDN_send: error -12
[28836.629921] mISDN_send: error -12
[28836.645919] mISDN_send: error -12
[28836.645923] mISDN_send: error -12
[28836.661921] mISDN_send: error -12
[28836.661925] mISDN_send: error -12
[28836.677924] mISDN_send: error -12
[28836.677927] mISDN_send: error -12
[28836.693927] mISDN_send: error -12
[28836.693930] mISDN_send: error -12
[28836.709929] mISDN_send: error -12
[28836.709932] mISDN_send: error -12
[28836.710228] mISDN_send: error -12
[28836.710231] mISDN_send: error -12
[28836.725931] mISDN_send: error -12
[28836.725934] mISDN_send: error -12
[28836.741933] mISDN_send: error -12
[28836.741936] mISDN_send: error -12
[28836.757935] mISDN_send: error -12
[28836.757938] mISDN_send: error -12
[28836.759494] base_sock_release(f6e15380) sk=f6957800
[29125.535433] create_l2entity: ret 1 0
[29125.535440] create_l2entity: ret 2 0
[29195.592070] mISDN_send: error -12
[29195.592075] mISDN_send: error -12
[29195.592078] mISDN_send: error -12
[29195.592080] mISDN_send: error -12
[29195.597507] mISDN_send: error -12
[29195.597511] mISDN_send: error -12
[29195.597513] mISDN_send: error -12
[29195.597515] mISDN_send: error -12
[29195.608070] mISDN_send: error -12
[29195.608073] mISDN_send: error -12
[29195.608076] mISDN_send: error -12
[29195.608078] mISDN_send: error -12
[29195.624071] mISDN_send: error -12
[29195.624075] mISDN_send: error -12
[29195.624077] mISDN_send: error -12
[29195.624079] mISDN_send: error -12
[29195.640074] mISDN_send: error -12
[29195.640077] mISDN_send: error -12
[29195.640079] mISDN_send: error -12
[29195.640081] mISDN_send: error -12
[29195.656075] mISDN_send: error -12
[29195.656078] mISDN_send: error -12
[29195.656081] mISDN_send: error -12
[29195.656083] mISDN_send: error -12
[29195.672078] mISDN_send: error -12
[29195.672081] mISDN_send: error -12
[29195.672084] mISDN_send: error -12
[29195.672086] mISDN_send: error -12
[29195.688081] mISDN_send: error -12
[29195.688084] mISDN_send: error -12
[29195.688087] mISDN_send: error -12
[29195.688089] mISDN_send: error -12
[29195.702518] mISDN_send: error -12
[29195.702521] mISDN_send: error -12
[29195.702524] mISDN_send: error -12
[29195.702526] mISDN_send: error -12
[29195.704085] mISDN_send: error -12
[29195.704088] mISDN_send: error -12
[29195.704090] mISDN_send: error -12
[29195.704092] mISDN_send: error -12
[29195.720094] mISDN_send: error -12
[29195.720097] mISDN_send: error -12
[29195.720099] mISDN_send: error -12
[29195.720102] mISDN_send: error -12
[29195.736087] mISDN_send: error -12
[29195.736090] mISDN_send: error -12
[29195.736092] mISDN_send: error -12
[29195.736094] mISDN_send: error -12
[29195.752089] mISDN_send: error -12
[29195.752093] mISDN_send: error -12
[29195.752095] mISDN_send: error -12
[29195.752097] mISDN_send: error -12
[29195.768229] mISDN_send: error -12
[29195.768232] mISDN_send: error -12
[29195.768234] mISDN_send: error -12
[29195.768237] mISDN_send: error -12
[29195.784094] mISDN_send: error -12
[29195.784097] mISDN_send: error -12
[29195.784100] mISDN_send: error -12
[29195.784102] mISDN_send: error -12
[29195.800096] mISDN_send: error -12
[29195.800099] mISDN_send: error -12
[29195.800101] mISDN_send: error -12
[29195.800103] mISDN_send: error -12
[29195.807657] mISDN_send: error -12
[29195.807660] mISDN_send: error -12
[29195.807662] mISDN_send: error -12
[29195.807664] mISDN_send: error -12
[29195.816099] mISDN_send: error -12
[29195.816102] mISDN_send: error -12
[29195.816104] mISDN_send: error -12
[29195.816106] mISDN_send: error -12
[29195.832101] mISDN_send: error -12
[29195.832104] mISDN_send: error -12
[29195.832107] mISDN_send: error -12
[29195.832109] mISDN_send: error -12
[29195.848102] mISDN_send: error -12
[29195.848105] mISDN_send: error -12
[29195.848108] mISDN_send: error -12
[29195.848110] mISDN_send: error -12
[29195.864104] mISDN_send: error -12
[29195.864107] mISDN_send: error -12
[29195.864110] mISDN_send: error -12
[29195.864112] mISDN_send: error -12
[29195.880107] mISDN_send: error -12
[29195.880110] mISDN_send: error -12
[29195.880112] mISDN_send: error -12
[29195.880115] mISDN_send: error -12
[29195.896109] mISDN_send: error -12
[29195.896113] mISDN_send: error -12
[29195.896115] mISDN_send: error -12
[29195.896117] mISDN_send: error -12
[29195.912112] mISDN_send: error -12
[29195.912115] mISDN_send: error -12
[29195.912118] mISDN_send: error -12
[29195.912120] mISDN_send: error -12
[29195.912669] mISDN_send: error -12
[29195.912672] mISDN_send: error -12
[29195.912674] mISDN_send: error -12
[29195.912676] mISDN_send: error -12
[29195.928114] mISDN_send: error -12
[29195.928117] mISDN_send: error -12
[29195.928119] mISDN_send: error -12
[29195.928121] mISDN_send: error -12
[29195.944116] mISDN_send: error -12
[29195.944119] mISDN_send: error -12
[29195.944121] mISDN_send: error -12
[29195.944123] mISDN_send: error -12
[29195.960118] mISDN_send: error -12
[29195.960122] mISDN_send: error -12
[29195.960124] mISDN_send: error -12
[29195.960126] mISDN_send: error -12
[29195.976120] mISDN_send: error -12
[29195.976123] mISDN_send: error -12
[29195.976126] mISDN_send: error -12
[29195.976128] mISDN_send: error -12
[29195.992123] mISDN_send: error -12
[29195.992126] mISDN_send: error -12
[29195.992128] mISDN_send: error -12
[29195.992131] mISDN_send: error -12
[29196.008125] mISDN_send: error -12
[29196.008128] mISDN_send: error -12
[29196.008130] mISDN_send: error -12
[29196.008132] mISDN_send: error -12
[29196.017686] mISDN_send: error -12
[29196.017690] mISDN_send: error -12
[29196.017692] mISDN_send: error -12
[29196.017694] mISDN_send: error -12
[29196.024128] mISDN_send: error -12
[29196.024130] mISDN_send: error -12
[29196.024133] mISDN_send: error -12
[29196.024135] mISDN_send: error -12
[29196.040130] mISDN_send: error -12
[29196.040133] mISDN_send: error -12
[29196.040135] mISDN_send: error -12
[29196.040138] mISDN_send: error -12
[29196.056132] mISDN_send: error -12
[29196.056135] mISDN_send: error -12
[29196.056137] mISDN_send: error -12
[29196.056140] mISDN_send: error -12
[29196.072134] mISDN_send: error -12
[29196.072137] mISDN_send: error -12
[29196.072139] mISDN_send: error -12
[29196.072141] mISDN_send: error -12
[29196.088136] mISDN_send: error -12
[29196.088139] mISDN_send: error -12
[29196.088141] mISDN_send: error -12
[29196.088143] mISDN_send: error -12
[29196.104142] mISDN_send: error -12
[29196.104146] mISDN_send: error -12
[29196.104148] mISDN_send: error -12
[29196.104150] mISDN_send: error -12
[29196.120141] mISDN_send: error -12
[29196.120144] mISDN_send: error -12
[29196.120147] mISDN_send: error -12
[29196.120149] mISDN_send: error -12
[29196.122698] mISDN_send: error -12
[29196.122701] mISDN_send: error -12
[29196.122703] mISDN_send: error -12
[29196.122705] mISDN_send: error -12
[29196.136142] mISDN_send: error -12
[29196.136146] mISDN_send: error -12
[29196.136148] mISDN_send: error -12
[29196.136150] mISDN_send: error -12
[29196.152144] mISDN_send: error -12
[29196.152148] mISDN_send: error -12
[29196.152150] mISDN_send: error -12
[29196.152152] mISDN_send: error -12
[29196.168147] mISDN_send: error -12
[29196.168150] mISDN_send: error -12
[29196.168152] mISDN_send: error -12
[29196.168155] mISDN_send: error -12
[29196.184149] mISDN_send: error -12
[29196.184152] mISDN_send: error -12
[29196.184155] mISDN_send: error -12
[29196.184157] mISDN_send: error -12
[29196.200152] mISDN_send: error -12
[29196.200156] mISDN_send: error -12
[29196.200158] mISDN_send: error -12
[29196.200160] mISDN_send: error -12
[29196.216162] mISDN_send: error -12
[29196.216165] mISDN_send: error -12
[29196.216167] mISDN_send: error -12
[29196.216170] mISDN_send: error -12
[29196.227716] mISDN_send: error -12
[29196.227719] mISDN_send: error -12
[29196.227721] mISDN_send: error -12
[29196.227724] mISDN_send: error -12
[29196.232156] mISDN_send: error -12
[29196.232160] mISDN_send: error -12
[29196.232162] mISDN_send: error -12
[29196.232164] mISDN_send: error -12
[29196.248160] mISDN_send: error -12
[29196.248163] mISDN_send: error -12
[29196.248165] mISDN_send: error -12
[29196.248167] mISDN_send: error -12
[29196.264161] mISDN_send: error -12
[29196.264164] mISDN_send: error -12
[29196.264166] mISDN_send: error -12
[29196.264168] mISDN_send: error -12
[29196.280301] mISDN_send: error -12
[29196.280304] mISDN_send: error -12
[29196.280306] mISDN_send: error -12
[29196.280308] mISDN_send: error -12
[29196.296165] mISDN_send: error -12
[29196.296169] mISDN_send: error -12
[29196.296171] mISDN_send: error -12
[29196.296173] mISDN_send: error -12
[29196.312181] mISDN_send: error -12
[29196.312184] mISDN_send: error -12
[29196.312187] mISDN_send: error -12
[29196.312189] mISDN_send: error -12
[29196.328191] mISDN_send: error -12
[29196.328195] mISDN_send: error -12
[29196.328197] mISDN_send: error -12
[29196.328199] mISDN_send: error -12
[29196.332855] mISDN_send: error -12
[29196.332858] mISDN_send: error -12
[29196.332861] mISDN_send: error -12
[29196.332863] mISDN_send: error -12
[29196.344179] mISDN_send: error -12
[29196.344182] mISDN_send: error -12
[29196.344185] mISDN_send: error -12
[29196.344187] mISDN_send: error -12
[29196.360173] mISDN_send: error -12
[29196.360176] mISDN_send: error -12
[29196.360179] mISDN_send: error -12
[29196.360181] mISDN_send: error -12
[29196.376176] mISDN_send: error -12
[29196.376179] mISDN_send: error -12
[29196.376182] mISDN_send: error -12
[29196.376184] mISDN_send: error -12
[29196.392178] mISDN_send: error -12
[29196.392181] mISDN_send: error -12
[29196.392184] mISDN_send: error -12
[29196.392186] mISDN_send: error -12
[29196.408181] mISDN_send: error -12
[29196.408184] mISDN_send: error -12
[29196.408187] mISDN_send: error -12
[29196.408189] mISDN_send: error -12
[29196.424183] mISDN_send: error -12
[29196.424186] mISDN_send: error -12
[29196.424189] mISDN_send: error -12
[29196.424191] mISDN_send: error -12
[29196.437870] mISDN_send: error -12
[29196.437873] mISDN_send: error -12
[29196.437875] mISDN_send: error -12
[29196.437878] mISDN_send: error -12
[29196.440181] mISDN_send: error -12
[29196.440184] mISDN_send: error -12
[29196.440186] mISDN_send: error -12
[29196.440189] mISDN_send: error -12
[29196.456188] mISDN_send: error -12
[29196.456191] mISDN_send: error -12
[29196.456193] mISDN_send: error -12
[29196.456195] mISDN_send: error -12
[29196.472190] mISDN_send: error -12
[29196.472193] mISDN_send: error -12
[29196.472195] mISDN_send: error -12
[29196.472197] mISDN_send: error -12
[29196.488192] mISDN_send: error -12
[29196.488195] mISDN_send: error -12
[29196.488198] mISDN_send: error -12
[29196.488200] mISDN_send: error -12
[29196.504194] mISDN_send: error -12
[29196.504197] mISDN_send: error -12
[29196.504200] mISDN_send: error -12
[29196.504202] mISDN_send: error -12
[29196.520196] mISDN_send: error -12
[29196.520199] mISDN_send: error -12
[29196.520202] mISDN_send: error -12
[29196.520204] mISDN_send: error -12
[29196.536199] mISDN_send: error -12
[29196.536202] mISDN_send: error -12
[29196.536204] mISDN_send: error -12
[29196.536206] mISDN_send: error -12
[29196.542884] mISDN_send: error -12
[29196.542887] mISDN_send: error -12
[29196.542890] mISDN_send: error -12
[29196.542892] mISDN_send: error -12
[29196.552201] mISDN_send: error -12
[29196.552204] mISDN_send: error -12
[29196.552207] mISDN_send: error -12
[29196.552209] mISDN_send: error -12
[29196.568203] mISDN_send: error -12
[29196.568206] mISDN_send: error -12
[29196.568209] mISDN_send: error -12
[29196.568211] mISDN_send: error -12
[29196.584205] mISDN_send: error -12
[29196.584208] mISDN_send: error -12
[29196.584211] mISDN_send: error -12
[29196.584213] mISDN_send: error -12
[29196.600207] mISDN_send: error -12
[29196.600210] mISDN_send: error -12
[29196.600213] mISDN_send: error -12
[29196.600215] mISDN_send: error -12
[29196.616210] mISDN_send: error -12
[29196.616213] mISDN_send: error -12
[29196.616216] mISDN_send: error -12
[29196.616218] mISDN_send: error -12
[29196.632212] mISDN_send: error -12
[29196.632215] mISDN_send: error -12
[29196.632218] mISDN_send: error -12
[29196.632220] mISDN_send: error -12
[29196.647899] mISDN_send: error -12
[29196.647902] mISDN_send: error -12
[29196.647905] mISDN_send: error -12
[29196.647907] mISDN_send: error -12
[29196.648210] mISDN_send: error -12
[29196.648213] mISDN_send: error -12
[29196.648215] mISDN_send: error -12
[29196.648217] mISDN_send: error -12
[29196.664217] mISDN_send: error -12
[29196.664220] mISDN_send: error -12
[29196.664222] mISDN_send: error -12
[29196.664224] mISDN_send: error -12
[29196.680218] mISDN_send: error -12
[29196.680222] mISDN_send: error -12
[29196.680224] mISDN_send: error -12
[29196.680226] mISDN_send: error -12
[29196.696220] mISDN_send: error -12
[29196.696224] mISDN_send: error -12
[29196.696226] mISDN_send: error -12
[29196.696228] mISDN_send: error -12
[29196.712224] mISDN_send: error -12
[29196.712227] mISDN_send: error -12
[29196.712229] mISDN_send: error -12
[29196.712231] mISDN_send: error -12
[29196.728225] mISDN_send: error -12
[29196.728228] mISDN_send: error -12
[29196.728231] mISDN_send: error -12
[29196.728233] mISDN_send: error -12
[29196.744228] mISDN_send: error -12
[29196.744231] mISDN_send: error -12
[29196.744233] mISDN_send: error -12
[29196.744235] mISDN_send: error -12
[29196.752914] mISDN_send: error -12
[29196.752917] mISDN_send: error -12
[29196.752919] mISDN_send: error -12
[29196.752921] mISDN_send: error -12
[29196.760230] mISDN_send: error -12
[29196.760233] mISDN_send: error -12
[29196.760235] mISDN_send: error -12
[29196.760238] mISDN_send: error -12
[29196.776231] mISDN_send: error -12
[29196.776235] mISDN_send: error -12
[29196.776237] mISDN_send: error -12
[29196.776239] mISDN_send: error -12
[29196.792372] mISDN_send: error -12
[29196.792375] mISDN_send: error -12
[29196.792377] mISDN_send: error -12
[29196.792380] mISDN_send: error -12
[29196.808236] mISDN_send: error -12
[29196.808239] mISDN_send: error -12
[29196.808242] mISDN_send: error -12
[29196.808244] mISDN_send: error -12
[29196.824239] mISDN_send: error -12
[29196.824242] mISDN_send: error -12
[29196.824244] mISDN_send: error -12
[29196.824247] mISDN_send: error -12
[29196.840241] mISDN_send: error -12
[29196.840244] mISDN_send: error -12
[29196.840246] mISDN_send: error -12
[29196.840249] mISDN_send: error -12
[29196.856243] mISDN_send: error -12
[29196.856246] mISDN_send: error -12
[29196.856249] mISDN_send: error -12
[29196.856251] mISDN_send: error -12
[29196.858050] mISDN_send: error -12
[29196.858053] mISDN_send: error -12
[29196.858055] mISDN_send: error -12
[29196.858057] mISDN_send: error -12
[29196.872246] mISDN_send: error -12
[29196.872249] mISDN_send: error -12
[29196.872251] mISDN_send: error -12
[29196.872254] mISDN_send: error -12
[29196.888247] mISDN_send: error -12
[29196.888250] mISDN_send: error -12
[29196.888253] mISDN_send: error -12
[29196.888255] mISDN_send: error -12
[29196.904250] mISDN_send: error -12
[29196.904253] mISDN_send: error -12
[29196.904256] mISDN_send: error -12
[29196.904258] mISDN_send: error -12
[29196.920252] mISDN_send: error -12
[29196.920255] mISDN_send: error -12
[29196.920258] mISDN_send: error -12
[29196.920260] mISDN_send: error -12
[29196.936255] mISDN_send: error -12
[29196.936258] mISDN_send: error -12
[29196.936260] mISDN_send: error -12
[29196.936263] mISDN_send: error -12
[29196.952257] mISDN_send: error -12
[29196.952260] mISDN_send: error -12
[29196.952262] mISDN_send: error -12
[29196.952264] mISDN_send: error -12
[29196.963069] mISDN_send: error -12
[29196.963072] mISDN_send: error -12
[29196.963074] mISDN_send: error -12
[29196.963076] mISDN_send: error -12
[29196.968259] mISDN_send: error -12
[29196.968262] mISDN_send: error -12
[29196.968264] mISDN_send: error -12
[29196.968267] mISDN_send: error -12
[29196.984261] mISDN_send: error -12
[29196.984264] mISDN_send: error -12
[29196.984266] mISDN_send: error -12
[29196.984268] mISDN_send: error -12
[29197.000264] mISDN_send: error -12
[29197.000267] mISDN_send: error -12
[29197.000269] mISDN_send: error -12
[29197.000271] mISDN_send: error -12
[29197.016265] mISDN_send: error -12
[29197.016268] mISDN_send: error -12
[29197.016270] mISDN_send: error -12
[29197.016273] mISDN_send: error -12
[29197.032268] mISDN_send: error -12
[29197.032271] mISDN_send: error -12
[29197.032273] mISDN_send: error -12
[29197.032275] mISDN_send: error -12
[29197.048270] mISDN_send: error -12
[29197.048273] mISDN_send: error -12
[29197.048275] mISDN_send: error -12
[29197.048277] mISDN_send: error -12
[29197.064271] mISDN_send: error -12
[29197.064274] mISDN_send: error -12
[29197.064277] mISDN_send: error -12
[29197.064279] mISDN_send: error -12
[29197.068086] mISDN_send: error -12
[29197.068089] mISDN_send: error -12
[29197.068091] mISDN_send: error -12
[29197.068093] mISDN_send: error -12
[29197.080276] mISDN_send: error -12
[29197.080279] mISDN_send: error -12
[29197.080282] mISDN_send: error -12
[29197.080284] mISDN_send: error -12
[29197.096276] mISDN_send: error -12
[29197.096279] mISDN_send: error -12
[29197.096281] mISDN_send: error -12
[29197.096284] mISDN_send: error -12
[29197.112280] mISDN_send: error -12
[29197.112283] mISDN_send: error -12
[29197.112285] mISDN_send: error -12
[29197.112287] mISDN_send: error -12
[29197.128281] mISDN_send: error -12
[29197.128285] mISDN_send: error -12
[29197.128287] mISDN_send: error -12
[29197.128289] mISDN_send: error -12
[29197.144283] mISDN_send: error -12
[29197.144286] mISDN_send: error -12
[29197.144288] mISDN_send: error -12
[29197.144291] mISDN_send: error -12
[29197.160286] mISDN_send: error -12
[29197.160289] mISDN_send: error -12
[29197.160291] mISDN_send: error -12
[29197.160293] mISDN_send: error -12
[29197.173097] mISDN_send: error -12
[29197.173100] mISDN_send: error -12
[29197.173103] mISDN_send: error -12
[29197.173105] mISDN_send: error -12
[29197.176283] mISDN_send: error -12
[29197.176286] mISDN_send: error -12
[29197.176289] mISDN_send: error -12
[29197.176291] mISDN_send: error -12
[29197.192290] mISDN_send: error -12
[29197.192293] mISDN_send: error -12
[29197.192295] mISDN_send: error -12
[29197.192297] mISDN_send: error -12
[29197.208292] mISDN_send: error -12
[29197.208296] mISDN_send: error -12
[29197.208298] mISDN_send: error -12
[29197.208300] mISDN_send: error -12
[29197.224294] mISDN_send: error -12
[29197.224298] mISDN_send: error -12
[29197.224300] mISDN_send: error -12
[29197.224302] mISDN_send: error -12
[29197.240297] mISDN_send: error -12
[29197.240300] mISDN_send: error -12
[29197.240302] mISDN_send: error -12
[29197.240304] mISDN_send: error -12
[29197.256299] mISDN_send: error -12
[29197.256302] mISDN_send: error -12
[29197.256304] mISDN_send: error -12
[29197.256307] mISDN_send: error -12
[29197.272301] mISDN_send: error -12
[29197.272304] mISDN_send: error -12
[29197.272306] mISDN_send: error -12
[29197.272308] mISDN_send: error -12
[29197.278112] mISDN_send: error -12
[29197.278115] mISDN_send: error -12
[29197.278117] mISDN_send: error -12
[29197.278119] mISDN_send: error -12
[29197.288304] mISDN_send: error -12
[29197.288307] mISDN_send: error -12
[29197.288309] mISDN_send: error -12
[29197.288312] mISDN_send: error -12
[29197.304443] mISDN_send: error -12
[29197.304446] mISDN_send: error -12
[29197.304448] mISDN_send: error -12
[29197.304451] mISDN_send: error -12
[29197.320308] mISDN_send: error -12
[29197.320311] mISDN_send: error -12
[29197.320313] mISDN_send: error -12
[29197.320316] mISDN_send: error -12
[29197.336310] mISDN_send: error -12
[29197.336314] mISDN_send: error -12
[29197.336316] mISDN_send: error -12
[29197.336318] mISDN_send: error -12
[29197.352312] mISDN_send: error -12
[29197.352315] mISDN_send: error -12
[29197.352317] mISDN_send: error -12
[29197.352319] mISDN_send: error -12
[29197.368315] mISDN_send: error -12
[29197.368318] mISDN_send: error -12
[29197.368320] mISDN_send: error -12
[29197.368322] mISDN_send: error -12
[29197.383252] mISDN_send: error -12
[29197.383255] mISDN_send: error -12
[29197.383257] mISDN_send: error -12
[29197.383259] mISDN_send: error -12
[29197.384312] mISDN_send: error -12
[29197.384315] mISDN_send: error -12
[29197.384318] mISDN_send: error -12
[29197.384320] mISDN_send: error -12
[29197.400319] mISDN_send: error -12
[29197.400321] mISDN_send: error -12
[29197.400324] mISDN_send: error -12
[29197.400326] mISDN_send: error -12
[29197.416321] mISDN_send: error -12
[29197.416324] mISDN_send: error -12
[29197.416327] mISDN_send: error -12
[29197.416329] mISDN_send: error -12
[29197.432324] mISDN_send: error -12
[29197.432327] mISDN_send: error -12
[29197.432329] mISDN_send: error -12
[29197.432331] mISDN_send: error -12
[29197.448326] mISDN_send: error -12
[29197.448329] mISDN_send: error -12
[29197.448332] mISDN_send: error -12
[29197.448334] mISDN_send: error -12
[29197.464328] mISDN_send: error -12
[29197.464331] mISDN_send: error -12
[29197.464334] mISDN_send: error -12
[29197.464336] mISDN_send: error -12
[29197.480330] mISDN_send: error -12
[29197.480333] mISDN_send: error -12
[29197.480335] mISDN_send: error -12
[29197.480337] mISDN_send: error -12
[29197.488266] mISDN_send: error -12
[29197.488270] mISDN_send: error -12
[29197.488272] mISDN_send: error -12
[29197.488274] mISDN_send: error -12
[29197.496333] mISDN_send: error -12
[29197.496336] mISDN_send: error -12
[29197.496338] mISDN_send: error -12
[29197.496341] mISDN_send: error -12
[29197.512335] mISDN_send: error -12
[29197.512338] mISDN_send: error -12
[29197.512340] mISDN_send: error -12
[29197.512342] mISDN_send: error -12
[29197.528337] mISDN_send: error -12
[29197.528340] mISDN_send: error -12
[29197.528343] mISDN_send: error -12
[29197.528345] mISDN_send: error -12
[29197.544339] mISDN_send: error -12
[29197.544342] mISDN_send: error -12
[29197.544345] mISDN_send: error -12
[29197.544347] mISDN_send: error -12
[29197.560341] mISDN_send: error -12
[29197.560344] mISDN_send: error -12
[29197.560346] mISDN_send: error -12
[29197.560348] mISDN_send: error -12
[29197.576344] mISDN_send: error -12
[29197.576347] mISDN_send: error -12
[29197.576349] mISDN_send: error -12
[29197.576352] mISDN_send: error -12
[29197.592346] mISDN_send: error -12
[29197.592349] mISDN_send: error -12
[29197.592351] mISDN_send: error -12
[29197.592354] mISDN_send: error -12
[29197.593278] mISDN_send: error -12
[29197.593281] mISDN_send: error -12
[29197.593283] mISDN_send: error -12
[29197.593285] mISDN_send: error -12
[29197.608348] mISDN_send: error -12
[29197.608351] mISDN_send: error -12
[29197.608354] mISDN_send: error -12
[29197.608356] mISDN_send: error -12
[29197.624350] mISDN_send: error -12
[29197.624353] mISDN_send: error -12
[29197.624356] mISDN_send: error -12
[29197.624358] mISDN_send: error -12
[29197.640352] mISDN_send: error -12
[29197.640355] mISDN_send: error -12
[29197.640358] mISDN_send: error -12
[29197.640360] mISDN_send: error -12
[29197.656355] mISDN_send: error -12
[29197.656358] mISDN_send: error -12
[29197.656360] mISDN_send: error -12
[29197.656362] mISDN_send: error -12
[29197.672357] mISDN_send: error -12
[29197.672360] mISDN_send: error -12
[29197.672362] mISDN_send: error -12
[29197.672364] mISDN_send: error -12
[29197.688359] mISDN_send: error -12
[29197.688362] mISDN_send: error -12
[29197.688364] mISDN_send: error -12
[29197.688366] mISDN_send: error -12
[29197.698296] mISDN_send: error -12
[29197.698299] mISDN_send: error -12
[29197.698301] mISDN_send: error -12
[29197.698304] mISDN_send: error -12
[29197.704362] mISDN_send: error -12
[29197.704365] mISDN_send: error -12
[29197.704367] mISDN_send: error -12
[29197.704369] mISDN_send: error -12
[29197.720364] mISDN_send: error -12
[29197.720367] mISDN_send: error -12
[29197.720369] mISDN_send: error -12
[29197.720371] mISDN_send: error -12
[29197.736366] mISDN_send: error -12
[29197.736369] mISDN_send: error -12
[29197.736371] mISDN_send: error -12
[29197.736374] mISDN_send: error -12
[29197.752368] mISDN_send: error -12
[29197.752371] mISDN_send: error -12
[29197.752374] mISDN_send: error -12
[29197.752376] mISDN_send: error -12
[29197.768370] mISDN_send: error -12
[29197.768373] mISDN_send: error -12
[29197.768375] mISDN_send: error -12
[29197.768377] mISDN_send: error -12
[29197.784373] mISDN_send: error -12
[29197.784376] mISDN_send: error -12
[29197.784378] mISDN_send: error -12
[29197.784380] mISDN_send: error -12
[29197.800375] mISDN_send: error -12
[29197.800378] mISDN_send: error -12
[29197.800380] mISDN_send: error -12
[29197.800382] mISDN_send: error -12
[29197.803308] mISDN_send: error -12
[29197.803310] mISDN_send: error -12
[29197.803312] mISDN_send: error -12
[29197.803314] mISDN_send: error -12
[29197.816517] mISDN_send: error -12
[29197.816520] mISDN_send: error -12
[29197.816523] mISDN_send: error -12
[29197.816525] mISDN_send: error -12
[29197.816738] base_sock_release(f6e15200) sk=f6957a00
[29283.519159] create_l2entity: ret 1 0
[29283.519166] create_l2entity: ret 2 0
[29359.262859] mISDN_send: error -12
[29359.262864] mISDN_send: error -12
[29359.278860] mISDN_send: error -12
[29359.278863] mISDN_send: error -12
[29359.294860] mISDN_send: error -12
[29359.294863] mISDN_send: error -12
[29359.310863] mISDN_send: error -12
[29359.310866] mISDN_send: error -12
[29359.326865] mISDN_send: error -12
[29359.326868] mISDN_send: error -12
[29359.331918] mISDN_send: error -12
[29359.331922] mISDN_send: error -12
[29359.342868] mISDN_send: error -12
[29359.342871] mISDN_send: error -12
[29359.358869] mISDN_send: error -12
[29359.358873] mISDN_send: error -12
[29359.374871] mISDN_send: error -12
[29359.374875] mISDN_send: error -12
[29359.390874] mISDN_send: error -12
[29359.390877] mISDN_send: error -12
[29359.406876] mISDN_send: error -12
[29359.406879] mISDN_send: error -12
[29359.422878] mISDN_send: error -12
[29359.422882] mISDN_send: error -12
[29359.436933] mISDN_send: error -12
[29359.436936] mISDN_send: error -12
[29359.438879] mISDN_send: error -12
[29359.438882] mISDN_send: error -12
[29359.454883] mISDN_send: error -12
[29359.454886] mISDN_send: error -12
[29359.470885] mISDN_send: error -12
[29359.470888] mISDN_send: error -12
[29359.486887] mISDN_send: error -12
[29359.486891] mISDN_send: error -12
[29359.502889] mISDN_send: error -12
[29359.502892] mISDN_send: error -12
[29359.518892] mISDN_send: error -12
[29359.518895] mISDN_send: error -12
[29359.534894] mISDN_send: error -12
[29359.534897] mISDN_send: error -12
[29359.541947] mISDN_send: error -12
[29359.541950] mISDN_send: error -12
[29359.550896] mISDN_send: error -12
[29359.550899] mISDN_send: error -12
[29359.566899] mISDN_send: error -12
[29359.566902] mISDN_send: error -12
[29359.582900] mISDN_send: error -12
[29359.582903] mISDN_send: error -12
[29359.598903] mISDN_send: error -12
[29359.598906] mISDN_send: error -12
[29359.614905] mISDN_send: error -12
[29359.614909] mISDN_send: error -12
[29359.630907] mISDN_send: error -12
[29359.630911] mISDN_send: error -12
[29359.646910] mISDN_send: error -12
[29359.646913] mISDN_send: error -12
[29359.646915] mISDN_send: error -12
[29359.646918] mISDN_send: error -12
[29359.662912] mISDN_send: error -12
[29359.662915] mISDN_send: error -12
[29359.678914] mISDN_send: error -12
[29359.678917] mISDN_send: error -12
[29359.694916] mISDN_send: error -12
[29359.694920] mISDN_send: error -12
[29359.710919] mISDN_send: error -12
[29359.710922] mISDN_send: error -12
[29359.726921] mISDN_send: error -12
[29359.726924] mISDN_send: error -12
[29359.742923] mISDN_send: error -12
[29359.742926] mISDN_send: error -12
[29359.751851] mISDN_send: error -12
[29359.751855] mISDN_send: error -12
[29359.758926] mISDN_send: error -12
[29359.758929] mISDN_send: error -12
[29359.774928] mISDN_send: error -12
[29359.774931] mISDN_send: error -12
[29359.790930] mISDN_send: error -12
[29359.790933] mISDN_send: error -12
[29359.806933] mISDN_send: error -12
[29359.806936] mISDN_send: error -12
[29359.822934] mISDN_send: error -12
[29359.822937] mISDN_send: error -12
[29359.838936] mISDN_send: error -12
[29359.838939] mISDN_send: error -12
[29359.854939] mISDN_send: error -12
[29359.854942] mISDN_send: error -12
[29359.856866] mISDN_send: error -12
[29359.856869] mISDN_send: error -12
[29359.870941] mISDN_send: error -12
[29359.870944] mISDN_send: error -12
[29359.886943] mISDN_send: error -12
[29359.886946] mISDN_send: error -12
[29359.902945] mISDN_send: error -12
[29359.902949] mISDN_send: error -12
[29359.918948] mISDN_send: error -12
[29359.918951] mISDN_send: error -12
[29359.934950] mISDN_send: error -12
[29359.934953] mISDN_send: error -12
[29359.950952] mISDN_send: error -12
[29359.950955] mISDN_send: error -12
[29359.961881] mISDN_send: error -12
[29359.961884] mISDN_send: error -12
[29359.966954] mISDN_send: error -12
[29359.966957] mISDN_send: error -12
[29359.982957] mISDN_send: error -12
[29359.982960] mISDN_send: error -12
[29359.998959] mISDN_send: error -12
[29359.998962] mISDN_send: error -12
[29360.014961] mISDN_send: error -12
[29360.014964] mISDN_send: error -12
[29360.030963] mISDN_send: error -12
[29360.030966] mISDN_send: error -12
[29360.046965] mISDN_send: error -12
[29360.046968] mISDN_send: error -12
[29360.062968] mISDN_send: error -12
[29360.062971] mISDN_send: error -12
[29360.066895] mISDN_send: error -12
[29360.066898] mISDN_send: error -12
[29360.078971] mISDN_send: error -12
[29360.078974] mISDN_send: error -12
[29360.094972] mISDN_send: error -12
[29360.094975] mISDN_send: error -12
[29360.110975] mISDN_send: error -12
[29360.110978] mISDN_send: error -12
[29360.126976] mISDN_send: error -12
[29360.126980] mISDN_send: error -12
[29360.142979] mISDN_send: error -12
[29360.142982] mISDN_send: error -12
[29360.158981] mISDN_send: error -12
[29360.158984] mISDN_send: error -12
[29360.171910] mISDN_send: error -12
[29360.171913] mISDN_send: error -12
[29360.174983] mISDN_send: error -12
[29360.174986] mISDN_send: error -12
[29360.190986] mISDN_send: error -12
[29360.190989] mISDN_send: error -12
[29360.206988] mISDN_send: error -12
[29360.206991] mISDN_send: error -12
[29360.222991] mISDN_send: error -12
[29360.222994] mISDN_send: error -12
[29360.238993] mISDN_send: error -12
[29360.238996] mISDN_send: error -12
[29360.254994] mISDN_send: error -12
[29360.254997] mISDN_send: error -12
[29360.270998] mISDN_send: error -12
[29360.271001] mISDN_send: error -12
[29360.276925] mISDN_send: error -12
[29360.276928] mISDN_send: error -12
[29360.286999] mISDN_send: error -12
[29360.287003] mISDN_send: error -12
[29360.303001] mISDN_send: error -12
[29360.303004] mISDN_send: error -12
[29360.319003] mISDN_send: error -12
[29360.319006] mISDN_send: error -12
[29360.335006] mISDN_send: error -12
[29360.335009] mISDN_send: error -12
[29360.351008] mISDN_send: error -12
[29360.351011] mISDN_send: error -12
[29360.367010] mISDN_send: error -12
[29360.367013] mISDN_send: error -12
[29360.381939] mISDN_send: error -12
[29360.381942] mISDN_send: error -12
[29360.383010] mISDN_send: error -12
[29360.383013] mISDN_send: error -12
[29360.399015] mISDN_send: error -12
[29360.399018] mISDN_send: error -12
[29360.415016] mISDN_send: error -12
[29360.415020] mISDN_send: error -12
[29360.431019] mISDN_send: error -12
[29360.431023] mISDN_send: error -12
[29360.447022] mISDN_send: error -12
[29360.447025] mISDN_send: error -12
[29360.463023] mISDN_send: error -12
[29360.463026] mISDN_send: error -12
[29360.479026] mISDN_send: error -12
[29360.479029] mISDN_send: error -12
[29360.486954] mISDN_send: error -12
[29360.486957] mISDN_send: error -12
[29360.495028] mISDN_send: error -12
[29360.495031] mISDN_send: error -12
[29360.511030] mISDN_send: error -12
[29360.511033] mISDN_send: error -12
[29360.527032] mISDN_send: error -12
[29360.527035] mISDN_send: error -12
[29360.543034] mISDN_send: error -12
[29360.543037] mISDN_send: error -12
[29360.559037] mISDN_send: error -12
[29360.559040] mISDN_send: error -12
[29360.575039] mISDN_send: error -12
[29360.575042] mISDN_send: error -12
[29360.591041] mISDN_send: error -12
[29360.591044] mISDN_send: error -12
[29360.591966] mISDN_send: error -12
[29360.591968] mISDN_send: error -12
[29360.607043] mISDN_send: error -12
[29360.607046] mISDN_send: error -12
[29360.623046] mISDN_send: error -12
[29360.623049] mISDN_send: error -12
[29360.639048] mISDN_send: error -12
[29360.639051] mISDN_send: error -12
[29360.655050] mISDN_send: error -12
[29360.655053] mISDN_send: error -12
[29360.671052] mISDN_send: error -12
[29360.671055] mISDN_send: error -12
[29360.687055] mISDN_send: error -12
[29360.687058] mISDN_send: error -12
[29360.696983] mISDN_send: error -12
[29360.696986] mISDN_send: error -12
[29360.703057] mISDN_send: error -12
[29360.703061] mISDN_send: error -12
[29360.719060] mISDN_send: error -12
[29360.719063] mISDN_send: error -12
[29360.735062] mISDN_send: error -12
[29360.735065] mISDN_send: error -12
[29360.751063] mISDN_send: error -12
[29360.751066] mISDN_send: error -12
[29360.767066] mISDN_send: error -12
[29360.767069] mISDN_send: error -12
[29360.783068] mISDN_send: error -12
[29360.783071] mISDN_send: error -12
[29360.799070] mISDN_send: error -12
[29360.799073] mISDN_send: error -12
[29360.801997] mISDN_send: error -12
[29360.802000] mISDN_send: error -12
[29360.815144] mISDN_send: error -12
[29360.815147] mISDN_send: error -12
[29360.831074] mISDN_send: error -12
[29360.831078] mISDN_send: error -12
[29360.847077] mISDN_send: error -12
[29360.847080] mISDN_send: error -12
[29360.863079] mISDN_send: error -12
[29360.863082] mISDN_send: error -12
[29360.879081] mISDN_send: error -12
[29360.879084] mISDN_send: error -12
[29360.895084] mISDN_send: error -12
[29360.895087] mISDN_send: error -12
[29360.907013] mISDN_send: error -12
[29360.907016] mISDN_send: error -12
[29360.911086] mISDN_send: error -12
[29360.911089] mISDN_send: error -12
[29360.927088] mISDN_send: error -12
[29360.927091] mISDN_send: error -12
[29360.943090] mISDN_send: error -12
[29360.943093] mISDN_send: error -12
[29360.959093] mISDN_send: error -12
[29360.959096] mISDN_send: error -12
[29360.975095] mISDN_send: error -12
[29360.975098] mISDN_send: error -12
[29360.991097] mISDN_send: error -12
[29360.991100] mISDN_send: error -12
[29361.007099] mISDN_send: error -12
[29361.007102] mISDN_send: error -12
[29361.012027] mISDN_send: error -12
[29361.012030] mISDN_send: error -12
[29361.023102] mISDN_send: error -12
[29361.023105] mISDN_send: error -12
[29361.039104] mISDN_send: error -12
[29361.039107] mISDN_send: error -12
[29361.055106] mISDN_send: error -12
[29361.055109] mISDN_send: error -12
[29361.071108] mISDN_send: error -12
[29361.071111] mISDN_send: error -12
[29361.087110] mISDN_send: error -12
[29361.087113] mISDN_send: error -12
[29361.103113] mISDN_send: error -12
[29361.103116] mISDN_send: error -12
[29361.117043] mISDN_send: error -12
[29361.117046] mISDN_send: error -12
[29361.119127] mISDN_send: error -12
[29361.119130] mISDN_send: error -12
[29361.135140] mISDN_send: error -12
[29361.135144] mISDN_send: error -12
[29361.151126] mISDN_send: error -12
[29361.151130] mISDN_send: error -12
[29361.167121] mISDN_send: error -12
[29361.167125] mISDN_send: error -12
[29361.183124] mISDN_send: error -12
[29361.183127] mISDN_send: error -12
[29361.199126] mISDN_send: error -12
[29361.199129] mISDN_send: error -12
[29361.215128] mISDN_send: error -12
[29361.215131] mISDN_send: error -12
[29361.222057] mISDN_send: error -12
[29361.222060] mISDN_send: error -12
[29361.231141] mISDN_send: error -12
[29361.231144] mISDN_send: error -12
[29361.247133] mISDN_send: error -12
[29361.247136] mISDN_send: error -12
[29361.263135] mISDN_send: error -12
[29361.263138] mISDN_send: error -12
[29361.279138] mISDN_send: error -12
[29361.279141] mISDN_send: error -12
[29361.295139] mISDN_send: error -12
[29361.295143] mISDN_send: error -12
[29361.311142] mISDN_send: error -12
[29361.311145] mISDN_send: error -12
[29361.327142] mISDN_send: error -12
[29361.327145] mISDN_send: error -12
[29361.327148] mISDN_send: error -12
[29361.327150] mISDN_send: error -12
[29361.343147] mISDN_send: error -12
[29361.343150] mISDN_send: error -12
[29361.359149] mISDN_send: error -12
[29361.359152] mISDN_send: error -12
[29361.375151] mISDN_send: error -12
[29361.375154] mISDN_send: error -12
[29361.391153] mISDN_send: error -12
[29361.391156] mISDN_send: error -12
[29361.407155] mISDN_send: error -12
[29361.407158] mISDN_send: error -12
[29361.423157] mISDN_send: error -12
[29361.423160] mISDN_send: error -12
[29361.432086] mISDN_send: error -12
[29361.432089] mISDN_send: error -12
[29361.439160] mISDN_send: error -12
[29361.439164] mISDN_send: error -12
[29361.455162] mISDN_send: error -12
[29361.455165] mISDN_send: error -12
[29361.471164] mISDN_send: error -12
[29361.471168] mISDN_send: error -12
[29361.487166] mISDN_send: error -12
[29361.487169] mISDN_send: error -12
[29361.494671] base_sock_release(f6e15380) sk=f6854800
[29382.645073] create_l2entity: ret 1 0
[29382.645079] create_l2entity: ret 2 0
[29386.066651] l2mgr: addr:0 prim 1f04 F
[29498.642316] mISDN_send: error -12
[29498.642320] mISDN_send: error -12
[29498.658316] mISDN_send: error -12
[29498.658320] mISDN_send: error -12
[29498.674318] mISDN_send: error -12
[29498.674322] mISDN_send: error -12
[29498.675868] mISDN_send: error -12
[29498.675871] mISDN_send: error -12
[29498.690320] mISDN_send: error -12
[29498.690323] mISDN_send: error -12
[29498.706322] mISDN_send: error -12
[29498.706326] mISDN_send: error -12
[29498.722325] mISDN_send: error -12
[29498.722328] mISDN_send: error -12
[29498.738327] mISDN_send: error -12
[29498.738330] mISDN_send: error -12
[29498.754330] mISDN_send: error -12
[29498.754333] mISDN_send: error -12
[29498.770331] mISDN_send: error -12
[29498.770335] mISDN_send: error -12
[29498.780885] mISDN_send: error -12
[29498.780888] mISDN_send: error -12
[29498.786334] mISDN_send: error -12
[29498.786337] mISDN_send: error -12
[29498.802336] mISDN_send: error -12
[29498.802339] mISDN_send: error -12
[29498.818338] mISDN_send: error -12
[29498.818341] mISDN_send: error -12
[29498.834340] mISDN_send: error -12
[29498.834343] mISDN_send: error -12
[29498.850343] mISDN_send: error -12
[29498.850346] mISDN_send: error -12
[29498.866344] mISDN_send: error -12
[29498.866348] mISDN_send: error -12
[29498.882347] mISDN_send: error -12
[29498.882351] mISDN_send: error -12
[29498.885899] mISDN_send: error -12
[29498.885902] mISDN_send: error -12
[29498.898350] mISDN_send: error -12
[29498.898353] mISDN_send: error -12
[29498.914351] mISDN_send: error -12
[29498.914354] mISDN_send: error -12
[29498.930354] mISDN_send: error -12
[29498.930357] mISDN_send: error -12
[29498.946356] mISDN_send: error -12
[29498.946359] mISDN_send: error -12
[29498.962359] mISDN_send: error -12
[29498.962362] mISDN_send: error -12
[29498.978360] mISDN_send: error -12
[29498.978363] mISDN_send: error -12
[29498.990914] mISDN_send: error -12
[29498.990917] mISDN_send: error -12
[29498.994363] mISDN_send: error -12
[29498.994366] mISDN_send: error -12
[29499.010365] mISDN_send: error -12
[29499.010369] mISDN_send: error -12
[29499.026367] mISDN_send: error -12
[29499.026370] mISDN_send: error -12
[29499.042369] mISDN_send: error -12
[29499.042372] mISDN_send: error -12
[29499.058371] mISDN_send: error -12
[29499.058374] mISDN_send: error -12
[29499.074374] mISDN_send: error -12
[29499.074377] mISDN_send: error -12
[29499.090376] mISDN_send: error -12
[29499.090379] mISDN_send: error -12
[29499.095928] mISDN_send: error -12
[29499.095931] mISDN_send: error -12
[29499.106378] mISDN_send: error -12
[29499.106381] mISDN_send: error -12
[29499.122380] mISDN_send: error -12
[29499.122383] mISDN_send: error -12
[29499.138383] mISDN_send: error -12
[29499.138386] mISDN_send: error -12
[29499.154385] mISDN_send: error -12
[29499.154388] mISDN_send: error -12
[29499.170387] mISDN_send: error -12
[29499.170391] mISDN_send: error -12
[29499.186390] mISDN_send: error -12
[29499.186393] mISDN_send: error -12
[29499.200943] mISDN_send: error -12
[29499.200946] mISDN_send: error -12
[29499.202389] mISDN_send: error -12
[29499.202392] mISDN_send: error -12
[29499.218394] mISDN_send: error -12
[29499.218397] mISDN_send: error -12
[29499.234396] mISDN_send: error -12
[29499.234399] mISDN_send: error -12
[29499.250398] mISDN_send: error -12
[29499.250401] mISDN_send: error -12
[29499.266401] mISDN_send: error -12
[29499.266404] mISDN_send: error -12
[29499.282403] mISDN_send: error -12
[29499.282406] mISDN_send: error -12
[29499.298405] mISDN_send: error -12
[29499.298408] mISDN_send: error -12
[29499.305958] mISDN_send: error -12
[29499.305961] mISDN_send: error -12
[29499.314408] mISDN_send: error -12
[29499.314411] mISDN_send: error -12
[29499.330410] mISDN_send: error -12
[29499.330413] mISDN_send: error -12
[29499.346411] mISDN_send: error -12
[29499.346415] mISDN_send: error -12
[29499.362414] mISDN_send: error -12
[29499.362417] mISDN_send: error -12
[29499.378417] mISDN_send: error -12
[29499.378420] mISDN_send: error -12
[29499.394419] mISDN_send: error -12
[29499.394422] mISDN_send: error -12
[29499.410421] mISDN_send: error -12
[29499.410424] mISDN_send: error -12
[29499.410845] mISDN_send: error -12
[29499.410848] mISDN_send: error -12
[29499.426423] mISDN_send: error -12
[29499.426426] mISDN_send: error -12
[29499.442425] mISDN_send: error -12
[29499.442428] mISDN_send: error -12
[29499.458427] mISDN_send: error -12
[29499.458430] mISDN_send: error -12
[29499.474430] mISDN_send: error -12
[29499.474433] mISDN_send: error -12
[29499.490431] mISDN_send: error -12
[29499.490434] mISDN_send: error -12
[29499.506434] mISDN_send: error -12
[29499.506437] mISDN_send: error -12
[29499.515862] mISDN_send: error -12
[29499.515865] mISDN_send: error -12
[29499.522436] mISDN_send: error -12
[29499.522440] mISDN_send: error -12
[29499.538438] mISDN_send: error -12
[29499.538441] mISDN_send: error -12
[29499.554441] mISDN_send: error -12
[29499.554444] mISDN_send: error -12
[29499.570443] mISDN_send: error -12
[29499.570446] mISDN_send: error -12
[29499.586445] mISDN_send: error -12
[29499.586449] mISDN_send: error -12
[29499.602448] mISDN_send: error -12
[29499.602451] mISDN_send: error -12
[29499.618450] mISDN_send: error -12
[29499.618453] mISDN_send: error -12
[29499.620876] mISDN_send: error -12
[29499.620879] mISDN_send: error -12
[29499.634452] mISDN_send: error -12
[29499.634455] mISDN_send: error -12
[29499.650454] mISDN_send: error -12
[29499.650457] mISDN_send: error -12
[29499.666457] mISDN_send: error -12
[29499.666460] mISDN_send: error -12
[29499.682459] mISDN_send: error -12
[29499.682462] mISDN_send: error -12
[29499.698461] mISDN_send: error -12
[29499.698464] mISDN_send: error -12
[29499.714463] mISDN_send: error -12
[29499.714466] mISDN_send: error -12
[29499.725892] mISDN_send: error -12
[29499.725895] mISDN_send: error -12
[29499.730465] mISDN_send: error -12
[29499.730468] mISDN_send: error -12
[29499.746467] mISDN_send: error -12
[29499.746471] mISDN_send: error -12
[29499.762470] mISDN_send: error -12
[29499.762473] mISDN_send: error -12
[29499.778480] mISDN_send: error -12
[29499.778483] mISDN_send: error -12
[29499.794475] mISDN_send: error -12
[29499.794478] mISDN_send: error -12
[29499.810476] mISDN_send: error -12
[29499.810480] mISDN_send: error -12
[29499.826479] mISDN_send: error -12
[29499.826482] mISDN_send: error -12
[29499.830906] mISDN_send: error -12
[29499.830909] mISDN_send: error -12
[29499.842482] mISDN_send: error -12
[29499.842485] mISDN_send: error -12
[29499.858483] mISDN_send: error -12
[29499.858486] mISDN_send: error -12
[29499.874486] mISDN_send: error -12
[29499.874489] mISDN_send: error -12
[29499.890488] mISDN_send: error -12
[29499.890491] mISDN_send: error -12
[29499.906490] mISDN_send: error -12
[29499.906493] mISDN_send: error -12
[29499.922493] mISDN_send: error -12
[29499.922496] mISDN_send: error -12
[29499.935921] mISDN_send: error -12
[29499.935924] mISDN_send: error -12
[29499.938495] mISDN_send: error -12
[29499.938498] mISDN_send: error -12
[29499.954497] mISDN_send: error -12
[29499.954500] mISDN_send: error -12
[29499.970499] mISDN_send: error -12
[29499.970502] mISDN_send: error -12
[29499.986501] mISDN_send: error -12
[29499.986504] mISDN_send: error -12
[29500.002503] mISDN_send: error -12
[29500.002506] mISDN_send: error -12
[29500.018505] mISDN_send: error -12
[29500.018508] mISDN_send: error -12
[29500.034508] mISDN_send: error -12
[29500.034511] mISDN_send: error -12
[29500.040936] mISDN_send: error -12
[29500.040939] mISDN_send: error -12
[29500.050511] mISDN_send: error -12
[29500.050514] mISDN_send: error -12
[29500.066512] mISDN_send: error -12
[29500.066515] mISDN_send: error -12
[29500.082515] mISDN_send: error -12
[29500.082518] mISDN_send: error -12
[29500.098517] mISDN_send: error -12
[29500.098520] mISDN_send: error -12
[29500.114519] mISDN_send: error -12
[29500.114522] mISDN_send: error -12
[29500.130522] mISDN_send: error -12
[29500.130525] mISDN_send: error -12
[29500.145950] mISDN_send: error -12
[29500.145953] mISDN_send: error -12
[29500.146521] mISDN_send: error -12
[29500.146524] mISDN_send: error -12
[29500.162525] mISDN_send: error -12
[29500.162528] mISDN_send: error -12
[29500.178528] mISDN_send: error -12
[29500.178531] mISDN_send: error -12
[29500.194530] mISDN_send: error -12
[29500.194533] mISDN_send: error -12
[29500.210533] mISDN_send: error -12
[29500.210536] mISDN_send: error -12
[29500.226535] mISDN_send: error -12
[29500.226538] mISDN_send: error -12
[29500.242537] mISDN_send: error -12
[29500.242540] mISDN_send: error -12
[29500.250965] mISDN_send: error -12
[29500.250968] mISDN_send: error -12
[29500.258540] mISDN_send: error -12
[29500.258543] mISDN_send: error -12
[29500.274541] mISDN_send: error -12
[29500.274545] mISDN_send: error -12
[29500.290544] mISDN_send: error -12
[29500.290548] mISDN_send: error -12
[29500.306546] mISDN_send: error -12
[29500.306549] mISDN_send: error -12
[29500.322548] mISDN_send: error -12
[29500.322551] mISDN_send: error -12
[29500.338551] mISDN_send: error -12
[29500.338554] mISDN_send: error -12
[29500.354553] mISDN_send: error -12
[29500.354556] mISDN_send: error -12
[29500.355852] mISDN_send: error -12
[29500.355854] mISDN_send: error -12
[29500.370554] mISDN_send: error -12
[29500.370558] mISDN_send: error -12
[29500.386558] mISDN_send: error -12
[29500.386561] mISDN_send: error -12
[29500.402559] mISDN_send: error -12
[29500.402562] mISDN_send: error -12
[29500.418562] mISDN_send: error -12
[29500.418565] mISDN_send: error -12
[29500.434635] mISDN_send: error -12
[29500.434638] mISDN_send: error -12
[29500.450566] mISDN_send: error -12
[29500.450569] mISDN_send: error -12
[29500.460870] mISDN_send: error -12
[29500.460873] mISDN_send: error -12
[29500.466569] mISDN_send: error -12
[29500.466572] mISDN_send: error -12
[29500.482570] mISDN_send: error -12
[29500.482574] mISDN_send: error -12
[29500.498573] mISDN_send: error -12
[29500.498576] mISDN_send: error -12
[29500.514575] mISDN_send: error -12
[29500.514578] mISDN_send: error -12
[29500.530577] mISDN_send: error -12
[29500.530580] mISDN_send: error -12
[29500.546580] mISDN_send: error -12
[29500.546583] mISDN_send: error -12
[29500.562582] mISDN_send: error -12
[29500.562585] mISDN_send: error -12
[29500.565758] mISDN_send: error -12
[29500.565761] mISDN_send: error -12
[29500.578585] mISDN_send: error -12
[29500.578588] mISDN_send: error -12
[29500.594586] mISDN_send: error -12
[29500.594589] mISDN_send: error -12
[29500.610588] mISDN_send: error -12
[29500.610591] mISDN_send: error -12
[29500.626597] mISDN_send: error -12
[29500.626600] mISDN_send: error -12
[29500.642606] mISDN_send: error -12
[29500.642610] mISDN_send: error -12
[29500.658595] mISDN_send: error -12
[29500.658598] mISDN_send: error -12
[29500.670774] mISDN_send: error -12
[29500.670777] mISDN_send: error -12
[29500.674598] mISDN_send: error -12
[29500.674601] mISDN_send: error -12
[29500.690599] mISDN_send: error -12
[29500.690603] mISDN_send: error -12
[29500.706602] mISDN_send: error -12
[29500.706605] mISDN_send: error -12
[29500.722604] mISDN_send: error -12
[29500.722607] mISDN_send: error -12
[29500.738606] mISDN_send: error -12
[29500.738609] mISDN_send: error -12
[29500.754609] mISDN_send: error -12
[29500.754612] mISDN_send: error -12
[29500.770611] mISDN_send: error -12
[29500.770614] mISDN_send: error -12
[29500.775788] mISDN_send: error -12
[29500.775791] mISDN_send: error -12
[29500.786614] mISDN_send: error -12
[29500.786617] mISDN_send: error -12
[29500.802615] mISDN_send: error -12
[29500.802618] mISDN_send: error -12
[29500.818617] mISDN_send: error -12
[29500.818620] mISDN_send: error -12
[29500.834620] mISDN_send: error -12
[29500.834623] mISDN_send: error -12
[29500.850635] mISDN_send: error -12
[29500.850638] mISDN_send: error -12
[29500.866648] mISDN_send: error -12
[29500.866651] mISDN_send: error -12
[29500.869461] base_sock_release(f6e15200) sk=f6878200
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101217/b1f77e22/attachment.bin>

From Andreas.Eversberg at versatel.de  Mon Dec 20 08:04:52 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Mon, 20 Dec 2010 09:04:52 +0100
Subject: AW: mISDN-problem
Message-ID: <B16317F2B1592B4492FC414114171CE604B088DA@FLBVEXCH01.versatel.local>

> newbie question: what does this dmesg mean?

hi thomas,

this happens, if the user space process does not read from the b-channel
socket. since the b-channels have no flow control, the packets get
dropped and an error message is printed by the kernel. what program do
you use?

andreas



From kobayashi_maru at onlinehome.de  Sat Dec 18 12:18:34 2010
From: kobayashi_maru at onlinehome.de (Thomas Ansorg)
Date: Sat, 18 Dec 2010 13:18:34 +0100
Subject: hlrsync.py question
Message-ID: <1292674714.5760.4.camel@r-9djhc747gf8b40ha>

hi
someone please tell a linux newbie like me:
what this script does
and
how it is executed (hlrsync hlr.sqlite3 dont work)

i'm just at the beginning of learning pearl,python and other script
stuff


T.
-- 
Wer Rechtschreibfehler findet, darf sie behalten!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101218/b443335d/attachment.bin>

From holger at freyther.de  Sat Dec 18 13:26:46 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sat, 18 Dec 2010 14:26:46 +0100
Subject: hlrsync.py question
In-Reply-To: <1292674714.5760.4.camel@r-9djhc747gf8b40ha>
References: <1292674714.5760.4.camel@r-9djhc747gf8b40ha>
Message-ID: <4D0CB696.6040805@freyther.de>

On 12/18/2010 01:18 PM, Thomas Ansorg wrote:
> hi
> someone please tell a linux newbie like me:
> what this script does
> and
> how it is executed (hlrsync hlr.sqlite3 dont work)
> 
> i'm just at the beginning of learning pearl,python and other script
> stuff

Hi,

why do you think this script is of interest for you? What should it do?




From satishn at cdotb.ernet.in  Wed Dec 22 12:34:39 2010
From: satishn at cdotb.ernet.in (satishn)
Date: Wed, 22 Dec 2010 18:04:39 +0530
Subject: Regarding implementation of RLC/MAC in open BSC
Message-ID: <4D11F05F.4020502@cdotb.ernet.in>

hi ,

Im new to Open BSC .In your website it is given that

"have the BTS interoperate a SGSN with Gb (NS-over-IP) interface "

Does this mean that PCU Stacks(RLC/MAC,BSSGP and NS)  are implemented
at the BTS. Does Open BSC support PCU stacks.  Kindly respond.

Regards

Satish N



From laforge at gnumonks.org  Thu Dec 23 02:14:41 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 23 Dec 2010 03:14:41 +0100
Subject: Regarding implementation of RLC/MAC in open BSC
In-Reply-To: <4D11F05F.4020502@cdotb.ernet.in>
References: <4D11F05F.4020502@cdotb.ernet.in>
Message-ID: <20101223021441.GL8073@prithivi.gnumonks.org>

On Wed, Dec 22, 2010 at 06:04:39PM +0530, satishn wrote:

> Im new to Open BSC .In your website it is given that
> "have the BTS interoperate a SGSN with Gb (NS-over-IP) interface "
> 
> Does this mean that PCU Stacks(RLC/MAC,BSSGP and NS)  are implemented
> at the BTS. 

yes, this is the mode that we support.  PCU in the BTS.

However, I see no reason why OsmoSGSN should not work with a PCU co-located
with the BSC.  However, you will have to use a proprietary BSC in that
case, as OpenBSC does not include RLC/MAC.

In a BSC-hosted PCU, the Gb Interface exported to the SGSN is the same
as in the BTS-hosted PCU.

Please note that OsmoSGSN is still not production ready.  You can use it
in a lab, but don't expect too much.

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 laforge at gnumonks.org  Thu Dec 23 02:11:14 2010
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 23 Dec 2010 03:11:14 +0100
Subject: OpenBSC / lcr integration through unix domain socket
Message-ID: <20101223021114.GK8073@prithivi.gnumonks.org>

Hi!

I've finally taken up the taks to split the 'siamese twin' of linking
lcr with bsc_hack and replace it with a PF_UNIX, SOCK_SEQPACKET socket.

I've done quite a bit of testing and it seems to work fine.  The bsc_hack
side is complete, i.e. it properly handles the loss of the lcr connection
and drops all CC transactions at that point.

The lcr side is less finished, especially
 * it will not drop all calls when the OpenBSC [socket] goes away
 * it will not re-connect if OpenBSC has disappeared

I hope those can still be adressed properly ahead of 27C3.  Andreas: Not sure
if you have some time to look at it.  I'll be working on higher priority
items for the 27C3 deployment tomorrow...

The openbsc code is in the laforge/mncc_sock branch of openbsc.git

The lcr code can be found in the mncc_sockk branch of the unofficial
lcr.git repo at git://git.osmocom.org/lcr.git

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 Andreas.Eversberg at versatel.de  Thu Dec 23 09:20:08 2010
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Thu, 23 Dec 2010 10:20:08 +0100
Subject: AW: OpenBSC / lcr integration through unix domain socket
Message-ID: <B16317F2B1592B4492FC414114171CE604B09736@FLBVEXCH01.versatel.local>

> The lcr side is less finished, especially
> * it will not drop all calls when the OpenBSC [socket] goes away
> * it will not re-connect if OpenBSC has disappeared

> I hope those can still be adressed properly ahead of 27C3.  Andreas:
Not sure
> if you have some time to look at it.  I'll be working on higher
priority
> items for the 27C3 deployment tomorrow...

hi harald,

good work. i hope we can complete it before 27c3. (my priority is on
packing/preparing for 27c3.) the missing things i will implement then.
also i will do the same thing for osmocom-bb. then i will merge
everything with the "develop" branch of lcr.

best regards,

andreas 



From jmercury313 at gmail.com  Thu Dec 23 16:14:31 2010
From: jmercury313 at gmail.com (jason mercury)
Date: Thu, 23 Dec 2010 18:14:31 +0200
Subject: OpenBSC+LCR+Asterisk installation problem
Message-ID: <AANLkTi=MB6cp7G3XT-ZW1=_FF-0aCSq5kjWvXmmWcByb@mail.gmail.com>

Hi,

I am trying to install a OpenBSC+LCR+Asterisk system according to the how to
send to the mail list by Konrad Meier on *Tue Oct 12 18:27:33  2010. *During
installation of LCR I got following error:

make[1]: Entering directory `/home/idb/openbsc/lcr'
gcc   -DWITH_GSM_BS -I./openbsc/include -I./libosmocore/include
-I./openbsc   -Wall -DCONFIG_DATA="\"/usr/local/lcr\""
-DSHARE_DATA="\"/usr/local/lcr\"" -DLOG_DIR="\"/usr/local/lcr\""
-DEXTENSION_DATA="\"/usr/local/lcr/extensions\"" -D_GNU_SOURCE -fPIC -c
chan_lcr.c -o chan_lcr.po
chan_lcr.c: In function ?lcr_indicate?:
chan_lcr.c:2274: warning: assignment from incompatible pointer type
chan_lcr.c:2289: warning: assignment from incompatible pointer type
chan_lcr.c:2316: warning: assignment from incompatible pointer type
chan_lcr.c:2381: error: dereferencing pointer to incomplete type
chan_lcr.c:2382: error: dereferencing pointer to incomplete type
chan_lcr.c: In function ?load_module?:
chan_lcr.c:2818: warning: passing argument 2 of ?ast_register_application2?
from incompatible pointer type
/usr/include/asterisk/module.h:427: note: expected ?int (*)(struct
ast_channel *, void *)? but argument is of type ?int (*)(struct ast_channel
*, void *)?
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/idb/openbsc/lcr'
make: *** [all] Error 2

Why is this occur? My ubuntu kernel is 2.6.32-24-generic and i exactly
followed the steps. I am attaching that how to again.

I also couldn't git check out OpenBSC, LCR , mISDN, mISDNuser and i download
them from http://www.linux-call-router.de/download/lcr-1.7/. I want to ask
that why i can't git clone.  When i try to git clone i take following:

git clone git://git.misdn.org/git/lcr.git/
Initialized empty Git repository in /home/idb/op/lcr/.git/
fatal: The remote end hung up unexpectedly


 If any you have idea please help.

Thanks.

Jason.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101223/259f0d06/attachment.htm>
-------------- next part --------------
sudo apt-get install linux-source build-essential autoconf automake libtool libgsm1-dev libdbi0-dev \
     libdbd-sqlite3 git-core asterisk asterisk-dev ncurses-base libncurses5-dev libncursesw5-dev sqlite3 pkg-config
cd /usr/src
sudo tar xvfj linux-source-2.6.32.tar.bz2
cd linux-source-2.6.32
sudo make oldconfig

cd /lib/modules/2.6.32-24-generic/
sudo ln -s /usr/src/linux-source-2.6.32 source

cd
mkdir openbsc
cd openbsc

git clone git://git.misdn.org/git/mISDN.git/
git clone git://git.misdn.org/git/mISDNuser.git/
git clone git://git.osmocom.org/libosmocore.git
git clone git://bs11-abis.gnumonks.org/openbsc.git
git clone git://git.misdn.org/git/lcr.git/

cd mISDN
./configure
cp mISDN.cfg.default standalone/mISDN.cfg
make modules
sudo make modules-install

cd ../mISDNuser
./configure
make
sudo make install

cd ../libosmocore/
git checkout 43558316bc4e6ddac92dd198b07a4803c21dc77b
autoreconf -i
./configure
make
sudo make install

cd ../openbsc/openbsc/
git checkout 305e2906aae7dbf45204f043394719c9a06c1227
autoreconf --install --force
./configure
make

cd ../../lcr
git checkout 69475c77e1b5eef4f101f0bf108a89d04ccd833b
git checkout mit der Version vom 6 Aug
ln -s ../libosmocore/ .
ln -s ../openbsc/openbsc/ .
sh autogen.sh
wget http://openbsc.osmocom.org/trac/raw-attachment/wiki/OpenBSC_LCR/lcrOpenBSC.patch
git apply --verbose lcrOpenBSC.patch
./configure --prefix=/opt/lcr --with-asterisk --with-gsm-bs
vim gsm_bs.cpp: change on line 60 PACKAGE_VERSION to "1.7"
make
sudo make install

sudo cp chan_lcr.so /usr/lib/asterisk/modules/

cd /usr/local/lcr
sudo vim options.conf  uncomment the following lines:
  debug 0xffff
  lock /var/tmp
  socketuser asterisk
  socketgroup asterisk
  gsm

sudo vim interface.conf
  uncomment the first [GSM] section
add: extern

[GSM]
gsm-bs
nt
layer1hold no
layer2hold no
tones yes
earlyb no
channel-in free
channel-out any
nodtmf


sudo vim gsm.conf
  uncomment both interfaces
  debug DRLL:DCC:DMM:DRR:DRSL:DNM:DSMS:DMNCC:DMNSMS:DPAG:DMUX:DMEAS
  config /usr/local/lcr/openbsc.cfg
  hlr /usr/local/lcr/hlr.sqlite3

sudo vim routing.conf
  on the [extern] section add:
  interface=GSM  remote=asterisk		: remote application=asterisk context=btsctrl
 

sudo vim /etc/asterisk/modules.conf
add under [modules]: load => chan_lcr.so


start lcr:
(sudo modprobe mISDN_core)
sudo modprobe mISDN_dsp
sudo modprobe mISDN_l1loop pri=1 nchannel=8

i couldn't load the l1loop. the following error has appeared (after modprobe mISDN_core and _dsp): FATAL: Module mISDN_l1loop not found.
Solution: sudo depmod -a
After that, i could do sudo modprobe mISDN_l1loop pri=1 nchannel=8

Proof it: sudo misdn_info 

Found 2 ports
  Port  0 'mISDN_l1loop.1':  TE/NT-mode PRI E1  (for phone lines & E1 devices)
                              8 B-channels: 1-8
                                B-protocols: RAW HDLC X75slp L2:DSP L2:DSPHDLC
  --------
  Port  1 'mISDN_l1loop.2':  TE/NT-mode PRI E1  (for phone lines & E1 devices)
                              8 B-channels: 1-8
                                B-protocols: RAW HDLC X75slp L2:DSP L2:DSPHDLC

cd


From cleb at defcon-3.net  Sun Dec 26 22:41:39 2010
From: cleb at defcon-3.net (Caleb Pal)
Date: Sun, 26 Dec 2010 14:41:39 -0800
Subject: OpenBSC+LCR+Asterisk installation problem
In-Reply-To: <AANLkTi=MB6cp7G3XT-ZW1=_FF-0aCSq5kjWvXmmWcByb@mail.gmail.com>
References: <AANLkTi=MB6cp7G3XT-ZW1=_FF-0aCSq5kjWvXmmWcByb@mail.gmail.com>
Message-ID: <004901cba54e$0ffe0950$2ffa1bf0$@net>

Are you using Asterisk 1.8? If so, you should checkout the asterisk_1_8
branch of LCR. LCR git was down, it is now back up at a slightly different
location, git://git.misdn.org/lcr.git/. mISDN and mISDNuser git are also at
the new path. 

 

HTH,

 

Caleb

 


From: openbsc-bounces at lists.gnumonks.org
[mailto:openbsc-bounces at lists.gnumonks.org] On Behalf Of jason mercury
Sent: Thursday, December 23, 2010 8:15 AM
To: openbsc at lists.gnumonks.org
Subject: OpenBSC+LCR+Asterisk installation problem

 

Hi, 

I am trying to install a OpenBSC+LCR+Asterisk system according to the how to
send to the mail list by Konrad Meier on Tue Oct 12 18:27:33  2010. During
installation of LCR I got following error:

make[1]: Entering directory `/home/idb/openbsc/lcr'
gcc   -DWITH_GSM_BS -I./openbsc/include -I./libosmocore/include -I./openbsc
-Wall -DCONFIG_DATA="\"/usr/local/lcr\"" -DSHARE_DATA="\"/usr/local/lcr\""
-DLOG_DIR="\"/usr/local/lcr\""
-DEXTENSION_DATA="\"/usr/local/lcr/extensions\"" -D_GNU_SOURCE -fPIC -c
chan_lcr.c -o chan_lcr.po
chan_lcr.c: In function 'lcr_indicate':
chan_lcr.c:2274: warning: assignment from incompatible pointer type
chan_lcr.c:2289: warning: assignment from incompatible pointer type
chan_lcr.c:2316: warning: assignment from incompatible pointer type
chan_lcr.c:2381: error: dereferencing pointer to incomplete type
chan_lcr.c:2382: error: dereferencing pointer to incomplete type
chan_lcr.c: In function 'load_module':
chan_lcr.c:2818: warning: passing argument 2 of 'ast_register_application2'
from incompatible pointer type
/usr/include/asterisk/module.h:427: note: expected 'int (*)(struct
ast_channel *, void *)' but argument is of type 'int (*)(struct ast_channel
*, void *)'
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/idb/openbsc/lcr'
make: *** [all] Error 2

Why is this occur? My ubuntu kernel is 2.6.32-24-generic and i exactly
followed the steps. I am attaching that how to again. 

I also couldn't git check out OpenBSC, LCR , mISDN, mISDNuser and i download
them from http://www.linux-call-router.de/download/lcr-1.7/. I want to ask
that why i can't git clone.  When i try to git clone i take following:

git clone git://git.misdn.org/git/lcr.git/
Initialized empty Git repository in /home/idb/op/lcr/.git/
fatal: The remote end hung up unexpectedly


 If any you have idea please help.

Thanks.

Jason.

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

From omar.atia at its.ws  Tue Dec 28 11:44:58 2010
From: omar.atia at its.ws (Omar Atia)
Date: Tue, 28 Dec 2010 13:44:58 +0200
Subject: Open BSC sources...
Message-ID: <007b01cba684$a9470990$fbd51cb0$%atia@its.ws>

Dear All,

 

I will introduce myself , It is Omar Atia from Lebanon , 8 years telecom
experience , willing to know more about open BSC , how can I get the sources
if it is free download them (not through unix), from where could I buy the
BTS stations are they available it has been sold out as written on the web
site . can we configure OpenBTS with OpenBSC ? is it configurable or not
tested yet .

 

I have a lot of questions related to this Area as I want to implement the
GSM network for testing purposes only to go deeply into it . 

 

Thanks,,,

Omar Atia
TPSG - Functional Consultant

ITS Logo.png
T.    + (961) 9 641555 ext. 416

M.   + (961) 3 001294
F.    + (961) 9 641555 ext. 217

degital signeture.pngE.     <mailto:omar.atia at its.ws> omar.atia at its.ws

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101228/e67f0883/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 160 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101228/e67f0883/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 5748 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101228/e67f0883/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 8941 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101228/e67f0883/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2395 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101228/e67f0883/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 2446 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101228/e67f0883/attachment-0001.jpg>

From muia777 at yahoo.de  Wed Dec 29 07:33:22 2010
From: muia777 at yahoo.de (Lud Gidiya)
Date: Wed, 29 Dec 2010 07:33:22 +0000 (GMT)
Subject: AW: OpenBSC Digest, Vol 24, Issue 26
In-Reply-To: <mailman.1.1293447601.1114.openbsc@lists.gnumonks.org>
Message-ID: <813626.24923.qm@web27601.mail.ukl.yahoo.com>



--- openbsc-request at lists.gnumonks.org <openbsc-request at lists.gnumonks.org> schrieb am Mo, 27.12.2010:

Von: openbsc-request at lists.gnumonks.org <openbsc-request at lists.gnumonks.org>
Betreff: OpenBSC Digest, Vol 24, Issue 26
An: openbsc at lists.gnumonks.org
Datum: Montag, 27. Dezember, 2010 13:00 Uhr

Send OpenBSC mailing list submissions to
??? openbsc at lists.gnumonks.org

To subscribe or unsubscribe via the World Wide Web, visit
??? https://lists.gnumonks.org/mailman/listinfo/openbsc
or, via email, send a message with subject or body 'help' to
??? openbsc-request at lists.gnumonks.org

You can reach the person managing the list at
??? openbsc-owner at lists.gnumonks.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenBSC digest..."


Today's Topics:

???1. RE: OpenBSC+LCR+Asterisk installation problem (Caleb Pal)


----------------------------------------------------------------------

Message: 1
Date: Sun, 26 Dec 2010 14:41:39 -0800
From: "Caleb Pal" <cleb at defcon-3.net>
Subject: RE: OpenBSC+LCR+Asterisk installation problem
To: "'jason mercury'" <jmercury313 at gmail.com>,
??? <openbsc at lists.gnumonks.org>
Message-ID: <004901cba54e$0ffe0950$2ffa1bf0$@net>
Content-Type: text/plain; charset="us-ascii"

Are you using Asterisk 1.8? If so, you should checkout the asterisk_1_8
branch of LCR. LCR git was down, it is now back up at a slightly different
location, git://git.misdn.org/lcr.git/. mISDN and mISDNuser git are also at
the new path. 

 

HTH,

 

Caleb

 


From: openbsc-bounces at lists.gnumonks.org
[mailto:openbsc-bounces at lists.gnumonks.org] On Behalf Of jason mercury
Sent: Thursday, December 23, 2010 8:15 AM
To: openbsc at lists.gnumonks.org
Subject: OpenBSC+LCR+Asterisk installation problem

 

Hi, 

I am trying to install a OpenBSC+LCR+Asterisk system according to the how to
send to the mail list by Konrad Meier on Tue Oct 12 18:27:33? 2010. During
installation of LCR I got following error:

make[1]: Entering directory `/home/idb/openbsc/lcr'
gcc???-DWITH_GSM_BS -I./openbsc/include -I./libosmocore/include -I./openbsc
-Wall -DCONFIG_DATA="\"/usr/local/lcr\"" -DSHARE_DATA="\"/usr/local/lcr\""
-DLOG_DIR="\"/usr/local/lcr\""
-DEXTENSION_DATA="\"/usr/local/lcr/extensions\"" -D_GNU_SOURCE -fPIC -c
chan_lcr.c -o chan_lcr.po
chan_lcr.c: In function 'lcr_indicate':
chan_lcr.c:2274: warning: assignment from incompatible pointer type
chan_lcr.c:2289: warning: assignment from incompatible pointer type
chan_lcr.c:2316: warning: assignment from incompatible pointer type
chan_lcr.c:2381: error: dereferencing pointer to incomplete type
chan_lcr.c:2382: error: dereferencing pointer to incomplete type
chan_lcr.c: In function 'load_module':
chan_lcr.c:2818: warning: passing argument 2 of 'ast_register_application2'
from incompatible pointer type
/usr/include/asterisk/module.h:427: note: expected 'int (*)(struct
ast_channel *, void *)' but argument is of type 'int (*)(struct ast_channel
*, void *)'
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/idb/openbsc/lcr'
make: *** [all] Error 2

Why is this occur? My ubuntu kernel is 2.6.32-24-generic and i exactly
followed the steps. I am attaching that how to again. 

I also couldn't git check out OpenBSC, LCR , mISDN, mISDNuser and i download
them from http://www.linux-call-router.de/download/lcr-1.7/. I want to ask
that why i can't git clone.? When i try to git clone i take following:

git clone git://git.misdn.org/git/lcr.git/
Initialized empty Git repository in /home/idb/op/lcr/.git/
fatal: The remote end hung up unexpectedly


 If any you have idea please help.

Thanks.

Jason.

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnumonks.org/pipermail/openbsc/attachments/20101226/abd4475f/attachment.html>

------------------------------

_______________________________________________
OpenBSC mailing list
OpenBSC at lists.gnumonks.org
https://lists.gnumonks.org/mailman/listinfo/openbsc


End of OpenBSC Digest, Vol 24, Issue 26
***************************************





SRY . I havent .?? :(

GL and HF !

Petyo


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

From holger at freyther.de  Thu Dec 30 11:03:35 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 30 Dec 2010 12:03:35 +0100
Subject: Notes from the 27C3 network
Message-ID: <4D1C6707.60608@freyther.de>

Hi all,

here are some notes about bsc_hack as it ran on the 27C3. In day0 we
discovered a nice SQL injection bug, in day1 we had plenty of segfaults,
mostly in the error and time-out paths of the MSC (but also some in the BSC
API). These included crashes due clearing the channel and removing the ->lchan
from the conn, RLL time out handling in the SMS code and some more.

The network ran without segfault (only one crash due my stupidity on a new VTY
command) after this. The biggest issue as that SMS got stuck. Code review has
found some issues immediately but this didn't fix it. On more code review an
issue with the 'subscr_get_channel' was identified.

First of all the transaction layer just stopped paging requests, e.g. stopping
the paging for someone else's subscr_get_channel, then the Call Control code
never called subscr_put_channel when it is done. I have created two band aids
for this situation but there is a bigger issue with the code.


If somebody has spare time and wants to do some simple changes one can do:


1.) The subscriber layer passes the 'subscr' pointer to the paging layer, it
should pass the request to it.
2.) It should be possible to cancel channel requests that were not scheduled yet.
3.) Once we started auth on the channel the 'request' state should be changed
too. It is not right now due 1.).
4.) ....




From abysss at gmail.com  Thu Dec 30 16:53:46 2010
From: abysss at gmail.com (Jason)
Date: Thu, 30 Dec 2010 08:53:46 -0800
Subject: Notes from the 27C3 network
In-Reply-To: <4D1C6707.60608@freyther.de>
References: <4D1C6707.60608@freyther.de>
Message-ID: <AANLkTiksGxac25Ywz+XXiGqEHmGvXo6EuqAdaj9oaQii@mail.gmail.com>

4.  Write Holger an email congratulating him and everyone that helped
for accomplishing such a formidable challenge.

Thanks to you for your leadership and all openbsc contributers for
persisting the face of such extreme complexity.  Happy new year and
keep up the excellent work :)

Cheers,
-Jason

On Thu, Dec 30, 2010 at 3:03 AM, Holger Hans Peter Freyther
<holger at freyther.de> wrote:
> Hi all,
>
> here are some notes about bsc_hack as it ran on the 27C3. In day0 we
> discovered a nice SQL injection bug, in day1 we had plenty of segfaults,
> mostly in the error and time-out paths of the MSC (but also some in the BSC
> API). These included crashes due clearing the channel and removing the ->lchan
> from the conn, RLL time out handling in the SMS code and some more.
>
> The network ran without segfault (only one crash due my stupidity on a new VTY
> command) after this. The biggest issue as that SMS got stuck. Code review has
> found some issues immediately but this didn't fix it. On more code review an
> issue with the 'subscr_get_channel' was identified.
>
> First of all the transaction layer just stopped paging requests, e.g. stopping
> the paging for someone else's subscr_get_channel, then the Call Control code
> never called subscr_put_channel when it is done. I have created two band aids
> for this situation but there is a bigger issue with the code.
>
>
> If somebody has spare time and wants to do some simple changes one can do:
>
>
> 1.) The subscriber layer passes the 'subscr' pointer to the paging layer, it
> should pass the request to it.
> 2.) It should be possible to cancel channel requests that were not scheduled yet.
> 3.) Once we started auth on the channel the 'request' state should be changed
> too. It is not right now due 1.).
> 4.) ....
>
>
>



From omar.atia at its.ws  Thu Dec 30 23:30:04 2010
From: omar.atia at its.ws (Omar Atia)
Date: Fri, 31 Dec 2010 01:30:04 +0200
Subject: Notes from the 27C3 network
In-Reply-To: <AANLkTiksGxac25Ywz+XXiGqEHmGvXo6EuqAdaj9oaQii@mail.gmail.com>
References: <4D1C6707.60608@freyther.de>
	<AANLkTiksGxac25Ywz+XXiGqEHmGvXo6EuqAdaj9oaQii@mail.gmail.com>
Message-ID: <013801cba879$7edaaa80$7c8fff80$%atia@its.ws>

Dears ,, please help ::

Before new year !!! can we compile libosmocore on SUN solaries (done)....I'm
reaching final stages in compiling , I have compiled bsc_hack and and I'm in
ipaccess now , there is issue with 

rc = setsockopt(fd, SOL_SOCKET, SO_BINDTODEVICE, ifname,
				strlen(ifname));

and issue with linux C function cfmakeraw...

in ipaccess-find.c , can we use bind instead of setsockopt cause solaries
doesn't have SO_BINDTODEVICE defined in socket.h.

Good night ...

Thanks,
Omar Atia

-----Original Message-----
From: openbsc-bounces at lists.gnumonks.org
[mailto:openbsc-bounces at lists.gnumonks.org] On Behalf Of Jason
Sent: Thursday, December 30, 2010 6:54 PM
To: Holger Hans Peter Freyther
Cc: openbsc at lists.gnumonks.org
Subject: Re: Notes from the 27C3 network

4.  Write Holger an email congratulating him and everyone that helped
for accomplishing such a formidable challenge.

Thanks to you for your leadership and all openbsc contributers for
persisting the face of such extreme complexity.  Happy new year and
keep up the excellent work :)

Cheers,
-Jason

On Thu, Dec 30, 2010 at 3:03 AM, Holger Hans Peter Freyther
<holger at freyther.de> wrote:
> Hi all,
>
> here are some notes about bsc_hack as it ran on the 27C3. In day0 we
> discovered a nice SQL injection bug, in day1 we had plenty of segfaults,
> mostly in the error and time-out paths of the MSC (but also some in the
BSC
> API). These included crashes due clearing the channel and removing the
->lchan
> from the conn, RLL time out handling in the SMS code and some more.
>
> The network ran without segfault (only one crash due my stupidity on a new
VTY
> command) after this. The biggest issue as that SMS got stuck. Code review
has
> found some issues immediately but this didn't fix it. On more code review
an
> issue with the 'subscr_get_channel' was identified.
>
> First of all the transaction layer just stopped paging requests, e.g.
stopping
> the paging for someone else's subscr_get_channel, then the Call Control
code
> never called subscr_put_channel when it is done. I have created two band
aids
> for this situation but there is a bigger issue with the code.
>
>
> If somebody has spare time and wants to do some simple changes one can do:
>
>
> 1.) The subscriber layer passes the 'subscr' pointer to the paging layer,
it
> should pass the request to it.
> 2.) It should be possible to cancel channel requests that were not
scheduled yet.
> 3.) Once we started auth on the channel the 'request' state should be
changed
> too. It is not right now due 1.).
> 4.) ....
>
>
>




From holger at freyther.de  Fri Dec 31 09:28:11 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 31 Dec 2010 10:28:11 +0100
Subject: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)
In-Reply-To: <013801cba879$7edaaa80$7c8fff80$%atia@its.ws>
References: <4D1C6707.60608@freyther.de>	<AANLkTiksGxac25Ywz+XXiGqEHmGvXo6EuqAdaj9oaQii@mail.gmail.com>
	<013801cba879$7edaaa80$7c8fff80$%atia@its.ws>
Message-ID: <4D1DA22B.6020204@freyther.de>

On 12/31/2010 12:30 AM, Omar Atia wrote:
> Dears ,, please help ::

Dear Omar,

please do not hijack threads, start a new one instead.


> 
> in ipaccess-find.c , can we use bind instead of setsockopt cause solaries
> doesn't have SO_BINDTODEVICE defined in socket.h.

For ipaccess-find is sending a broadcast packet, so it is important to select
the physical interface it should be send on. For the user it is more
convenient to write the interface name then to remember the ip address of this
interface.

Does Solaris provide another way to bind to a specific interface? What about
IP_BOUND_IF? If that is not the case we could consider doing a normal bind and
bind to the interface via an ip...

z.




From omar.atia at its.ws  Fri Dec 31 09:44:37 2010
From: omar.atia at its.ws (omar.atia at its.ws)
Date: Fri, 31 Dec 2010 09:44:37 +0000
Subject: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)
Message-ID: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>

Dears, 

Sorry for hijacking the thread , next time I will create new thread ...

I will try to bind using IP to avoid using SO_BINDTODEVICE ,and I will google IP_BOUND_IF as well.

Another issue is the linux command for vty which is the c function under linux called cfmakeraw which I removed from vty.c cause there is no library under SUN for that command or function to link with.

Can you please ensure that this commented line will not affect vty functionality ?

Thanks,
Omar atia
------Original Message------
From: Holger Hans Peter Freyther
Sender: openbsc-bounces at lists.gnumonks.org
To: openbsc at lists.gnumonks.org
Subject: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)
Sent: Dec 31, 2010 11:28 AM

On 12/31/2010 12:30 AM, Omar Atia wrote:
> Dears ,, please help ::

Dear Omar,

please do not hijack threads, start a new one instead.


> 
> in ipaccess-find.c , can we use bind instead of setsockopt cause solaries
> doesn't have SO_BINDTODEVICE defined in socket.h.

For ipaccess-find is sending a broadcast packet, so it is important to select
the physical interface it should be send on. For the user it is more
convenient to write the interface name then to remember the ip address of this
interface.

Does Solaris provide another way to bind to a specific interface? What about
IP_BOUND_IF? If that is not the case we could consider doing a normal bind and
bind to the interface via an ip...

z.




Sent via BlackBerry? from mtc touch

From holger at freyther.de  Fri Dec 31 10:24:41 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 31 Dec 2010 11:24:41 +0100
Subject: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)
In-Reply-To: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>
References: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>
Message-ID: <4D1DAF69.4030804@freyther.de>

On 12/31/2010 10:44 AM, omar.atia at its.ws wrote:
> Dears, 

> Can you please ensure that this commented line will not affect vty functionality ?


From omar.atia at its.ws  Fri Dec 31 16:10:36 2010
From: omar.atia at its.ws (Omar Atia)
Date: Fri, 31 Dec 2010 18:10:36 +0200
Subject: OpenBSC on Solaris (Sqlite3)
In-Reply-To: <4D1DAF69.4030804@freyther.de>
References: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>
	<4D1DAF69.4030804@freyther.de>
Message-ID: <000001cba905$5d4ae0b0$17e0a210$%atia@its.ws>

Dear Holger,
I have installed libdbi as prerequisite for compiling openbsc sources and linked successfully with the objects generated now I'm trying to run 

The following :

[ITSHPS]celtabs:/oradata/u01/celtabs/openbsc/openbsc/openbsc/src>./bsc_hack -c openbsc.cfg.nanobts
<0012> db.c:192 Failed to create connection.
DB: Failed to init database. Please check the option settings. 

The program has write privileges on the directory 

I'm not able to connect to DB even if I specify -l option with DB name .

The issue is that I have the following sqlite3 :

-rw-r--r--   1 celtabs  tabs      3440640 Dec 30 16:50 libdbi-0.8.4.tar
drwxrwxrwx   7 celtabs  tabs         1024 Dec 30 16:53 libdbi-0.8.4
-rw-r--r--   1 celtabs  tabs     10547200 Dec 30 17:14 sqlite3_3.5.9.orig.tar
drwxrwxrwx  12 celtabs  tabs         3584 Dec 30 17:27 sqlite3-3.5.9

I put sqlite3 path in the env . variable PATH and I'm able to login into sqlite3 , a question is it necessary  to have  dbd-sqlite3 or any sqlite3 could work ...see from the session :

[ITSHPS]celtabs:/oradata/u01/celtabs/openbsc>sqlite3
SQLite version 3.5.9
Enter ".help" for instructions
sqlite>

Kindly advise what is the issue and if I need to download dbd-sqlite3 kindly provide link for that if you please .

Thanks and happy new year .

Omar Atia




From holger at freyther.de  Fri Dec 31 16:18:42 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 31 Dec 2010 17:18:42 +0100
Subject: OpenBSC on Solaris (Sqlite3)
In-Reply-To: <000001cba905$5d4ae0b0$17e0a210$%atia@its.ws>
References: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>
	<4D1DAF69.4030804@freyther.de>
	<000001cba905$5d4ae0b0$17e0a210$%atia@its.ws>
Message-ID: <4D1E0262.9080301@freyther.de>

On 12/31/2010 05:10 PM, Omar Atia wrote:
> Dear Holger,

> Kindly advise what is the issue and if I need to download dbd-sqlite3 kindly provide link for that if you please .

Well,
there are two things to DBI. The API/framework (libdbi) and the drivers (e.g.
for sqlite). You will need to have the sqlite3 driver installed when running
OpenBSC.

z.

PS: You might be more productive with a GNU/Linux or *BSD system.




From omar.atia at its.ws  Fri Dec 31 22:32:22 2010
From: omar.atia at its.ws (Omar Atia)
Date: Sat, 01 Jan 2011 00:32:22 +0200
Subject: OpenBSC on Solaris (Sqlite3)
In-Reply-To: <4D1E0262.9080301@freyther.de>
References: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>
	<4D1DAF69.4030804@freyther.de>
	<000001cba905$5d4ae0b0$17e0a210$%atia@its.ws>
	<4D1E0262.9080301@freyther.de>
Message-ID: <000101cba93a$9af25080$d0d6f180$%atia@its.ws>

Dear holger,

Happy new year , I figured out that there should be libdbdsqlite3.so (drivers) under /usr/local/lib/dbd (as when I tried to connect with bsc_hack it writes faile to load driver ..., I need binary distribution for this driver .

I didn't find any binary distribution for solaries in the web site , I also tried to configure(got success with configure) and make driver lib but it is not making it didn't execute gcc and compile . 

The link Is as below :

http://sourceforge.net/projects/libdbi-drivers/files/

so now I have framework installed and I have the sources for the libdbdsqlite3 but I'm not able to compile , it is writing make statements without compiling ...

do you have any suggestions?

Thanks,
Omar Atia
-----Original Message-----
From: Holger Hans Peter Freyther [mailto:holger at freyther.de] 
Sent: Friday, December 31, 2010 6:19 PM
To: Omar Atia
Cc: openbsc at lists.gnumonks.org
Subject: Re: OpenBSC on Solaris (Sqlite3)

On 12/31/2010 05:10 PM, Omar Atia wrote:
> Dear Holger,

> Kindly advise what is the issue and if I need to download dbd-sqlite3 kindly provide link for that if you please .

Well,
there are two things to DBI. The API/framework (libdbi) and the drivers (e.g.
for sqlite). You will need to have the sqlite3 driver installed when running
OpenBSC.

z.

PS: You might be more productive with a GNU/Linux or *BSD system.




From holger at freyther.de  Fri Dec 31 22:39:12 2010
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 31 Dec 2010 23:39:12 +0100
Subject: OpenBSC on Solaris (Sqlite3)
In-Reply-To: <000101cba93a$9af25080$d0d6f180$%atia@its.ws>
References: <827822724-1293788679-cardhu_decombobulator_blackberry.rim.net-1793722426-@b28.c18.bise7.blackberry>	<4D1DAF69.4030804@freyther.de>	<000001cba905$5d4ae0b0$17e0a210$%atia@its.ws>	<4D1E0262.9080301@freyther.de>
	<000101cba93a$9af25080$d0d6f180$%atia@its.ws>
Message-ID: <4D1E5B90.6020403@freyther.de>

On 12/31/2010 11:32 PM, Omar Atia wrote:
> Dear holger,
> 

> so now I have framework installed and I have the sources for the libdbdsqlite3 but I'm not able to compile , it is writing make statements without compiling ...
>

search for *** in the output. it is an indication of (GNU) make that there is
an error. Most likely the configure script told you it couldn't find the
sqlite3.h and that the SQLIte3 backend was disabled or you need to pass
--enable-sqlite3 when configuring the drivers.

Is there a strong reason to use Solaris? If there is not strong reason to use
it you might be more happy with a Linux System as it comes with an easy way to
install all these dependencies.



From spaar at mirider.augusta.de  Fri Dec 31 11:38:40 2010
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Fri, 31 Dec 2010 11:38:40 
Subject: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)
Message-ID: <4d1dc0c0.mirider@mirider.augusta.de>

Hello Holger,

On Fri, 31 Dec 2010 11:24:41 +0100, "Holger Hans Peter Freyther" <holger at freyther.de> wrote:
> 
> If that is set on the socket for the telnet interface it does make a difference.

Just in case, Cygwin also misses cfmakeraw(), my private modification for
this is the following which is of course the same you quoted from the man
page.

  #if defined(__CYGWIN__)
  /* Workaround for Cygwin, which is missing cfmakeraw */
  /* Pasted from man page */
  void cfmakeraw(struct termios *termios_p)
  {
    termios_p->c_iflag &= ~(IGNBRK|BRKINT|PARMRK|ISTRIP|INLCR|IGNCR|ICRNL|IXON);
    termios_p->c_oflag &= ~OPOST;
    termios_p->c_lflag &= ~(ECHO|ECHONL|ICANON|ISIG|IEXTEN);
    termios_p->c_cflag &= ~(CSIZE|PARENB);
    termios_p->c_cflag |= CS8;
  }
  #endif /* defined(__CYGWIN__) */

Maybe there is a Solaris-specific preprocessor symbol and we can add
this function to an appropriate place.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From omar.atia at its.ws  Fri Dec 31 12:33:16 2010
From: omar.atia at its.ws (omar.atia at its.ws)
Date: Fri, 31 Dec 2010 12:33:16 +0000
Subject: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)
In-Reply-To: <4d1dc0c0.mirider@mirider.augusta.de>
References: <4d1dc0c0.mirider@mirider.augusta.de>
Message-ID: <325032783-1293798799-cardhu_decombobulator_blackberry.rim.net-328488663-@b28.c18.bise7.blackberry>

Thanks , I will check man page and write the below function inside the code if the struct is there under solaries ,

I have also another issue with gprs directory when compiling as you know ip.h in linux is different than ip.h under solaries , the difference is that solaries has struct ip with different members than linux which has struct iphdr ...I believe we can test GPRS for later stages , can you advise ? I tried to change ip.h to iphdr and change the members inside the code to ip struct members but it didn't work ? Can you advise if we can add the whole iphdr linux struct inside ip.h under solaries ? Does it affect functionality of the program ? Or we need to write the ip communication inside the program gprs_ns_frgre.c from scratch ?

Thanks,
Omar atia
Sent via BlackBerry? from mtc touch

-----Original Message-----
From: Dieter Spaar <spaar at mirider.augusta.de>
Sender: openbsc-bounces at lists.gnumonks.org
Date: Fri, 31 Dec 2010 11:38:40 
To: <openbsc at lists.gnumonks.org>
Subject: Re: OpenBSC on Solaris (WAS: Re: Notes from the 27C3 network)

Hello Holger,

On Fri, 31 Dec 2010 11:24:41 +0100, "Holger Hans Peter Freyther" <holger at freyther.de> wrote:
> 
> If that is set on the socket for the telnet interface it does make a difference.

Just in case, Cygwin also misses cfmakeraw(), my private modification for
this is the following which is of course the same you quoted from the man
page.

  #if defined(__CYGWIN__)
  /* Workaround for Cygwin, which is missing cfmakeraw */
  /* Pasted from man page */
  void cfmakeraw(struct termios *termios_p)
  {
    termios_p->c_iflag &= ~(IGNBRK|BRKINT|PARMRK|ISTRIP|INLCR|IGNCR|ICRNL|IXON);
    termios_p->c_oflag &= ~OPOST;
    termios_p->c_lflag &= ~(ECHO|ECHONL|ICANON|ISIG|IEXTEN);
    termios_p->c_cflag &= ~(CSIZE|PARENB);
    termios_p->c_cflag |= CS8;
  }
  #endif /* defined(__CYGWIN__) */

Maybe there is a Solaris-specific preprocessor symbol and we can add
this function to an appropriate place.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de