From ptmk06 at googlemail.com  Tue Sep  4 15:58:40 2012
From: ptmk06 at googlemail.com (Patrick Klapper)
Date: Tue, 4 Sep 2012 17:58:40 +0200
Subject: Buying a NanoBTS 165
Message-ID: <105CCE20-5A19-4400-8CD2-13E1B3D48537@googlemail.com>

Hello,

I am interested in buying a NanoBTS 165AU for research and education.

Does anyone sell a NanoBTS 165 with GSM (A5/1, A5/2) and GPRS/EDGE support?

Regards

Patrick



From holger at freyther.de  Fri Sep 14 07:32:28 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 14 Sep 2012 09:32:28 +0200
Subject: Buying a NanoBTS 165
In-Reply-To: <105CCE20-5A19-4400-8CD2-13E1B3D48537@googlemail.com>
References: <105CCE20-5A19-4400-8CD2-13E1B3D48537@googlemail.com>
Message-ID: <20120914073228.GB22757@localhost>

On Tue, Sep 04, 2012 at 05:58:40PM +0200, Patrick Klapper wrote:
> Hello,
> 
> I am interested in buying a NanoBTS 165AU for research and education.
> 
> Does anyone sell a NanoBTS 165 with GSM (A5/1, A5/2) and GPRS/EDGE support?

Just for the record because I have seen a similar question on irc. If someone
has an older GPRS capable nanoBTS and OpenBSC can not initialize the GPRS O&M
objects there is another option than buying a new nanoBTS.

One can fix the issue, e.g by starting to record a PCAP file and checking if
the nanoBTS is sending a NACK. Alternatively you might find someone to fix the
issue for you. It should be less expensive than buying a new bts.


holger



From laforge at gnumonks.org  Wed Sep  5 06:50:02 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 5 Sep 2012 08:50:02 +0200
Subject: Sept 5, 8pm / Osmocom Berlin User Group meeting
Message-ID: <20120905065002.GM12467@prithivi.gnumonks.org>

Hi all!

This is the announcement for the next Osmocom Berlin meeting.

	Sept 05, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin

There is no formal presentation scheduled for this meeting.

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

Regards,
	Harald

[p.s.: I myself will not be able to attend tonight, but I'm sure you
 will be able to do just fine (or even better?)]
-- 
- 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 tkaturi at gmail.com  Wed Sep  5 13:10:17 2012
From: tkaturi at gmail.com (Tawanda)
Date: Wed, 5 Sep 2012 15:10:17 +0200
Subject: Tektronix K1103 pinout of the E-1 interface
Message-ID: <47A24D08-C201-47D0-8636-80444FE45FDF@gmail.com>



Sent on the Go



From holger at freyther.de  Mon Sep 10 21:56:43 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 10 Sep 2012 23:56:43 +0200
Subject: Tektronix K1103 pinout of the E-1 interface
In-Reply-To: <47A24D08-C201-47D0-8636-80444FE45FDF@gmail.com>
References: <47A24D08-C201-47D0-8636-80444FE45FDF@gmail.com>
Message-ID: <20120910215643.GK30282@localhost>

On Wed, Sep 05, 2012 at 03:10:17PM +0200, Tawanda wrote:
> 
> 
> Sent on the Go

Dear Tawanda,

did you address the wrong list? Could you please elaborate?

thanks
	holger



From msdaudi at gmail.com  Thu Sep  6 09:51:37 2012
From: msdaudi at gmail.com (Daud Suleiman)
Date: Thu, 6 Sep 2012 09:51:37 +0000
Subject: MultiARFCN OpeBSC and SysmoBTS
Message-ID: <CAMitBDku7qvw=a2OXavexDxciC2bN7hOv5A0m4a4CAtbhxBMAg@mail.gmail.com>

Hi Harald,

I can't tire of congratulating and the community for the great work you are
doing in creating a free world in your own capacity! I thank you.

Meanwhile, I would like to know a few things:

1. Is sysmoBTS capable of operating in MultiARFCN? Is multiARFCN
implemented in OpenBSC and if so how does one go about configuring it.

2. Also after the successful implementation of CSD, are there plans for PTT
over Cellular (PoC)?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120906/3f9421bf/attachment.htm>

From peter at stuge.se  Thu Sep  6 21:47:14 2012
From: peter at stuge.se (Peter Stuge)
Date: Thu, 6 Sep 2012 23:47:14 +0200
Subject: MultiARFCN OpeBSC and SysmoBTS
In-Reply-To: <CAMitBDku7qvw=a2OXavexDxciC2bN7hOv5A0m4a4CAtbhxBMAg@mail.gmail.com>
References: <CAMitBDku7qvw=a2OXavexDxciC2bN7hOv5A0m4a4CAtbhxBMAg@mail.gmail.com>
Message-ID: <20120906214714.28043.qmail@stuge.se>

Daud Suleiman wrote:
> Is multiARFCN implemented in OpenBSC and if so how does one go
> about configuring it.

One BTS with multiple TRX uses one ARFCN per TRX. It works fine.


//Peter



From laforge at gnumonks.org  Mon Sep 10 12:47:30 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 10 Sep 2012 14:47:30 +0200
Subject: MultiARFCN OpeBSC and SysmoBTS
In-Reply-To: <CAMitBDku7qvw=a2OXavexDxciC2bN7hOv5A0m4a4CAtbhxBMAg@mail.gmail.com>
References: <CAMitBDku7qvw=a2OXavexDxciC2bN7hOv5A0m4a4CAtbhxBMAg@mail.gmail.com>
Message-ID: <20120910124730.GJ6618@prithivi.gnumonks.org>

Hi Daud,

On Thu, Sep 06, 2012 at 09:51:37AM +0000, Daud Suleiman wrote:
> Hi Harald,

be aware that you sent this to a public mailinglist for openbsc related
questions, not to me personally.

> I can't tire of congratulating and the community for the great work you are
> doing in creating a free world in your own capacity! I thank you.

Thanks on behalf of the development team.

> 1. Is sysmoBTS capable of operating in MultiARFCN?

sysmoBTS is a single-TRX device.  We have a hardware option of stacking
multiple sysmoBTS boards to achieve a single BTS with multiple TRX.
By default, each TRX has separate TX output / RX input.

> Is multiARFCN implemented in OpenBSC and if so how does one go about
> configuring it.

"multiarfcn" is not an standard language, I believe only OpenBTS uses
it.  As Peter has pointed out, any BTS with multiple TRX has multiple
arfcn.  So even the first BTS supported by OpenBSC (BS-11) has two
ARFCN.

There are a variety of example configuration files in the openbsc source
tree, feel free to review them.

> 2. Also after the successful implementation of CSD, are there plans for PTT
> over Cellular (PoC)?

CSD is not yet implemented, but I hope with Tobias' help we will soon
have it working, at least for some BTS models.

PoC as present in some phones so far is not a feature of GSM/3GPP
specifciations, and it is very hard to get those specifcations.  The
newer IMS-based method is specified in 3GPP, but I'm not sure which
operators have already deployed it.  As it is a TCP/IP based service, I
think it is fully independent from OpenBSC and just like any other
user application out of scope for what we are trying to achieve.  But
we're of course happy if you want to contribute a PoC server and host it
on git.osmocom.org :)

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  Mon Sep 10 21:33:50 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 10 Sep 2012 23:33:50 +0200
Subject: Introducing libosmosim
Message-ID: <20120910213350.GT6618@prithivi.gnumonks.org>

Hi!

I've been hacking away a bit on a new library 'libosmosim' whihc is
scheduled to become part of libosmocore.  In fact, as the automake
integration has been cleaned up, I'll probably merge it master any day
now.

The idea of this library is to
* understand the EF/DF hierarchy if GSM SIM, ETSI UICC and 3GPP USIM
* provide encoding and decoding routines for at least the most important
  EFs
* decode the binary data into a generic data structure which can be used
  by some form of a GUI application
* be able to re-encode from the generic parsed structure into the
  binary form, possibly after modification from the UI
* be able to transact APDUs via T0 and T1 on PC/SC and other reader
  interfaces, e.g.  the OsmocomBB SIM interface

So the primary purpose of this is to be able to have a tool for
meaningful (human-readable/writable) modification of all files on a
programmable SIM card, such as the sysmoSIM-GR1 (and other cards where
you have the ADM PIN that gives you write permission).

Other useful purposes on the horizon of the library could be:
* implementation of a generic SIM/UICC/USIM simulator based on
  user-created input, or based on 'ripped' SIM cards (well, you have to
  provide the key in some way).

The current status is still quite experimental, but you can already see
the major parts:

* mapping of APDU and TPDU (only T=0 so far) on to 'struct msgb

struct osim_file_ops
	encode and decode callbacks for a given file

struct osim_file_desc
	node in the hierarchical description of filesystem tree

struct osim_decoded_data
	the runtime representation of a decoded file:

struct osim_decoded_element
	one decoded element in a decoded file

struct osim_card_sw
	status + bitmask + human readable description

struct osim_card_profile
	full description profile of card, including filesystem
	hierarchy, status words and card-specific commands

struc osim_reader_hdl
	represents a card reader (currently a slot in a reader,
	not sure really how to represent multi-slot readers like
	sim-banks yet).  primarily consist of osim_reader_ops

struc osim_card_hdl
	representing a card inside a reader

struc osim_chan_hdl
	currently just a dummy. intended for logical channel support

most of the existing code is in src/sim/*.c, while some
not-yet-cleaned-up example code is in utils/osmo-sim-test.c.  There are
gaps everywhere all over the place, and I think it will take quite some
time to fill those gaps.

Current roadmap:

* properly integrate all parts, so with a single call you can read in
  the tree of all EFs of a card into their in-memory representation

* verify that the APIs for encoding/decoding functions work the way
  they are before writing 'all' the EF decode/encode routines

* add more decoded element types, such as location area codes and the
  like

So if you survived this mail until this point, I think you are a prime
candidate for contributing some code.  Let me know if you're interested
in helping out.

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 chris at techworks.ie  Tue Sep 11 17:04:59 2012
From: chris at techworks.ie (Christian Gagneraud)
Date: Tue, 11 Sep 2012 18:04:59 +0100
Subject: Introducing libosmosim
In-Reply-To: <20120910213350.GT6618@prithivi.gnumonks.org>
References: <20120910213350.GT6618@prithivi.gnumonks.org>
Message-ID: <504F6F3B.1050406@techworks.ie>

On 10/09/12 22:33, Harald Welte wrote:
> Hi!
>
[...]
>
> Current roadmap:
>
> * properly integrate all parts, so with a single call you can read in
>    the tree of all EFs of a card into their in-memory representation
>
> * verify that the APIs for encoding/decoding functions work the way
>    they are before writing 'all' the EF decode/encode routines

Hi,

I wouldn't mind to write a testsuite for that, I have no knowledge about 
ISO7816-5, and i never used simtrace and co. but I see that as an 
oportunity to dig into them.

As i don't have a SIM reader, it would be nice if someone could provide 
me raw dump files.

FWIU, I should be able to test the low-level stuff like 
osim_file_decode() and osim_file_encode()

Regards,
Chris

>
> * add more decoded element types, such as location area codes and the
>    like
>
> So if you survived this mail until this point, I think you are a prime
> candidate for contributing some code.  Let me know if you're interested
> in helping out.
>
> Regards,
> 	Harald
>


-- 
Christian Gagneraud,
Embedded systems engineer.
Techworks Marine
1 Harbour road
Dun Laoghaire
Co. Dublin
Ireland
Tel: + 353 (0) 1 236 5990
Web: http://www.techworks.ie/



From chris at techworks.ie  Tue Sep 11 18:06:11 2012
From: chris at techworks.ie (Christian Gagneraud)
Date: Tue, 11 Sep 2012 19:06:11 +0100
Subject: Introducing libosmosim
In-Reply-To: <20120910213350.GT6618@prithivi.gnumonks.org>
References: <20120910213350.GT6618@prithivi.gnumonks.org>
Message-ID: <504F7D93.5050107@techworks.ie>

On 10/09/12 22:33, Harald Welte wrote:
> Hi!
>

Hi,

I've just build libosmocore and ran osmo-sim-test, but it crashes.
There's a function signature mismatch between 
osim_reader_ops.reader_open() and pcsc_reader_open(), the later requires 
an extra parameter "void *ctx".

Chris

> I've been hacking away a bit on a new library 'libosmosim' whihc is
> scheduled to become part of libosmocore.  In fact, as the automake
> integration has been cleaned up, I'll probably merge it master any day
> now.
>
> The idea of this library is to
> * understand the EF/DF hierarchy if GSM SIM, ETSI UICC and 3GPP USIM
> * provide encoding and decoding routines for at least the most important
>    EFs
> * decode the binary data into a generic data structure which can be used
>    by some form of a GUI application
> * be able to re-encode from the generic parsed structure into the
>    binary form, possibly after modification from the UI
> * be able to transact APDUs via T0 and T1 on PC/SC and other reader
>    interfaces, e.g.  the OsmocomBB SIM interface
>
> So the primary purpose of this is to be able to have a tool for
> meaningful (human-readable/writable) modification of all files on a
> programmable SIM card, such as the sysmoSIM-GR1 (and other cards where
> you have the ADM PIN that gives you write permission).
>
> Other useful purposes on the horizon of the library could be:
> * implementation of a generic SIM/UICC/USIM simulator based on
>    user-created input, or based on 'ripped' SIM cards (well, you have to
>    provide the key in some way).
>
> The current status is still quite experimental, but you can already see
> the major parts:
>
> * mapping of APDU and TPDU (only T=0 so far) on to 'struct msgb
>
> struct osim_file_ops
> 	encode and decode callbacks for a given file
>
> struct osim_file_desc
> 	node in the hierarchical description of filesystem tree
>
> struct osim_decoded_data
> 	the runtime representation of a decoded file:
>
> struct osim_decoded_element
> 	one decoded element in a decoded file
>
> struct osim_card_sw
> 	status + bitmask + human readable description
>
> struct osim_card_profile
> 	full description profile of card, including filesystem
> 	hierarchy, status words and card-specific commands
>
> struc osim_reader_hdl
> 	represents a card reader (currently a slot in a reader,
> 	not sure really how to represent multi-slot readers like
> 	sim-banks yet).  primarily consist of osim_reader_ops
>
> struc osim_card_hdl
> 	representing a card inside a reader
>
> struc osim_chan_hdl
> 	currently just a dummy. intended for logical channel support
>
> most of the existing code is in src/sim/*.c, while some
> not-yet-cleaned-up example code is in utils/osmo-sim-test.c.  There are
> gaps everywhere all over the place, and I think it will take quite some
> time to fill those gaps.
>
> Current roadmap:
>
> * properly integrate all parts, so with a single call you can read in
>    the tree of all EFs of a card into their in-memory representation
>
> * verify that the APIs for encoding/decoding functions work the way
>    they are before writing 'all' the EF decode/encode routines
>
> * add more decoded element types, such as location area codes and the
>    like
>
> So if you survived this mail until this point, I think you are a prime
> candidate for contributing some code.  Let me know if you're interested
> in helping out.
>
> Regards,
> 	Harald
>


-- 
Christian Gagneraud,
Embedded systems engineer.
Techworks Marine
1 Harbour road
Dun Laoghaire
Co. Dublin
Ireland
Tel: + 353 (0) 1 236 5990
Web: http://www.techworks.ie/



From Max.Suraev at fairwaves.ru  Wed Sep 12 19:23:40 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Wed, 12 Sep 2012 21:23:40 +0200
Subject: [PATCH] make example config usable
Message-ID: <5050E13C.5080606@fairwaves.ru>

Hello.

Attached is a trivial patch which makes example config for libosmo-sgsn actually usable.
Most likely it was typo.
-- 
best regards,
Max, http://fairwaves.ru

From Max.Suraev at fairwaves.ru  Wed Sep 12 18:35:28 2012
From: Max.Suraev at fairwaves.ru (Max)
Date: Wed, 12 Sep 2012 20:35:28 +0200
Subject: [PATCH] Rename example config so it could be used right after
 copying.
Message-ID: <mailman.57.1641744178.42898.openbsc@lists.osmocom.org>

---
 openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg |   26 --------------------------
 openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg |   26 ++++++++++++++++++++++++++
 2 files changed, 26 insertions(+), 26 deletions(-)
 delete mode 100644 openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg
 create mode 100644 openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg

diff --git a/openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg b/openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg
deleted file mode 100644
index 027c03d..0000000
--- a/openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg
+++ /dev/null
@@ -1,26 +0,0 @@
-!
-! Osmocom SGSN configuration
-!
-!
-line vty
- no login
-!
-sgsn
- gtp local-ip 10.23.23.23
- ggsn 0 remote-ip 192.168.0.101
- 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.0.101
- encapsulation udp local-port 23000
- encapsulation framerelay-gre enabled 0
-!
-bssgp
-!
diff --git a/openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg b/openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg
new file mode 100644
index 0000000..027c03d
--- /dev/null
+++ b/openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg
@@ -0,0 +1,26 @@
+!
+! Osmocom SGSN configuration
+!
+!
+line vty
+ no login
+!
+sgsn
+ gtp local-ip 10.23.23.23
+ ggsn 0 remote-ip 192.168.0.101
+ 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.0.101
+ encapsulation udp local-port 23000
+ encapsulation framerelay-gre enabled 0
+!
+bssgp
+!
-- 
1.7.9.5


--------------060008010109090003040201--



From david at taddong.com  Thu Sep 13 17:52:48 2012
From: david at taddong.com (David Perez)
Date: Thu, 13 Sep 2012 19:52:48 +0200
Subject: Problem integrating OpenBSC (osmo-nitb) with LCR
Message-ID: <50521D70.10302@taddong.com>

Hi!

First of all, let me thank you all the developers and contributors of
both OpenBSC and LCR. Congratulations for your amazing work!

I am stuck with a problem while trying to get LCR and openbsc to work
together through their unix socket (/tmp/bsc_mncc), and I was wondering
if anyone on this list would be kind enough to give me some pointers.

I include more details below, but this is the executive summary:

I have two MS that can call each other with no problem when I start
openbsc (osmo-nitb) in standalone mode (i.e. without the "--mncc-sock"
option). However, when I start omso-nitb with that option, and I also
start LCR, a call between the two MS cannot be establised.

I think the problem may be related with the fact that LCR is not being
able to identify the calling number, nor the called number, nor the IMSI
of the caller. This can be seen in the following trace/debug messages of
LCR:
---
000000 TRACE 13.09.12 18:17:49.248 CH(1): MNCC_SETUP_IND LCR<->BSC
calling imsi=  dialing number=
[...]
000000 DEBUG (in apppbx.cpp/ea_message_port() line 2476): EPOINT(1)
incoming call from callerid=imsi-, dialing=
---

AFAIK, I'm using the latest version of each tool: I am using clones of
the following git repositories, made around 10:00 AM CET today (13sep12):
---
git clone git://git.osmocom.org/libosmocore.git
git clone git://git.osmocom.org/libosmo-abis.git
git clone git://git.osmocom.org/openbsc.git
git clone git://git.misdn.eu/lcr.git/
---
At the end of this message I include a list of the last commits of these
repositories, for reference.

--- Executive summary ends here ---

The long version of the explanation of the problem follows. I hope to
have included enough information, but if you need extra details, please
do not hesitate to let me know.

First, without LCR, I start openbsc (osmo-nitb) in standalone mode, make
a call from 2203 to 2201 (extension numbers I assigned in hlr.sqlite3),
and everything works fine (the call gets established and voice flows in
both directions):

---
root at tli-pc-2001:/usr/local/bin# cat start-bsc-standalone
#!/bin/sh

echo ""
echo "Starting _new_ BSC (openbsc) (=osmo-nitb) standalone..."

/opt/new/openbsc/bin/osmo-nitb -c /etc/opt/new/openbsc/openbsc.cfg \
                               -l /var/opt/new/openbsc/hlr.sqlite3
root at tli-pc-2001:/usr/local/bin# start-bsc-standalone

Starting _new_ BSC (openbsc) (=osmo-nitb) standalone...
<0019> input/ipaccess.c:923 enabling ipaccess BSC mode
DB: Database initialized.
DB: Database prepared.
<0007> sms_queue.c:232 Attempting to send 20 SMS
<0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3002
Failure Event Report Type=communication failure Severity=critical
failure Probable cause= 03 03 11 Additional Text=
<0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3003
<0004> bsc_init.c:282 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 1
using MCC=001 MNC=01 LAC=2 CID=0 BSIC=63 TSC=7
<000b> bsc_api.c:374 Sending ChanModify for speech 33 1
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
<000b> bsc_api.c:374 Sending ChanModify for speech 33 1
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
---
Then, I shut down osmo_nitb with CTRL-C.


Then, I start osmo-nitb for use with LCR (--mncc-sock):
---
root at tli-pc-2001:/usr/local/bin# cat start-bsc-for_lcr
#!/bin/sh

echo ""
echo "Starting _new_ BSC (openbsc) (=osmo-nitb) for use with LCR..."

/opt/new/openbsc/bin/osmo-nitb -c /etc/opt/new/openbsc/openbsc.cfg \
                               -l /var/opt/new/openbsc/hlr.sqlite3 \
                               --mncc-sock --rtp-proxy

root at tli-pc-2001:/usr/local/bin# start-bsc-for_lcr

Starting _new_ BSC (openbsc) (=osmo-nitb) for use with LCR...
<0019> input/ipaccess.c:923 enabling ipaccess BSC mode
DB: Database initialized.
DB: Database prepared.
<0007> sms_queue.c:232 Attempting to send 20 SMS
<0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3002
<0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3003
<0004> bsc_init.c:282 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 1
using MCC=001 MNC=01 LAC=2 CID=0 BSIC=63 TSC=7
Failure Event Report Type=communication failure Severity=critical
failure Probable cause= 03 03 11 Additional Text=
---

Then, I start LCR:
---
root at tli-pc-2001:/usr/local/bin# cat start-lcr
#!/bin/sh

echo ""
echo "Starting _new_ LCR..."
/opt/new/lcr/sbin/lcr start
root at tli-pc-2001:/usr/local/bin#
root at tli-pc-2001:/usr/local/bin# start-lcr

Starting _new_ LCR...

** LCR  Version 1.12

000000 DEBUG (in route.c/getrulesetbyname() line 1871): ruleset main found.
000000 DEBUG (in sip.cpp/sip_init() line 1913): SIP globals initialized
000000 DEBUG (in gsm.cpp/mncc_socket_retry_cb() line 1173): Connected to
MNCC socket /tmp/bsc_mncc!
LCR 1.12 started, waiting for calls...
000000 TRACE 13.09.12 18:16:22.091 --: LCR 1.12 started, waiting for
calls...
---

It attaches OK to the MNCC socket of openbsc. This message is displayed
by openbsc:
---
<0006> mncc_sock.c:274 MNCC Socket has connection with external call
control application
---

Then, I attempt to establish the same call as before, from 2203 to 2201.
The call does not get established, and LCR shows the following messages:
---
000000 DEBUG (in port.cpp/Port() line 197): new port (1) of type 0x3101,
name 'GSM-0-in'
000000 DEBUG (in gsm.cpp/Pgsm() line 194): Created new GSMPort(GSM-0-in).
000000 DEBUG (in gsm_bs.cpp/Pgsm_bs() line 56): Created new
GSMBSPort(GSM-0-in).
000000 TRACE 13.09.12 18:17:49.248 CH(1): New call ref LCR<->BSC
callref new=0x80000001
000000 TRACE 13.09.12 18:17:49.248 CH(1): Codec negotiation LCR<->BSC
bearer capa='given by MS'  speech version='AMR given' ignored='Not
suitable for LCR' version='EFR given' ignored='Not suitable for LCR'
version='Full Rate given' version='AMR Half Rate given' ignored='Not
suitable for LCR' version='Half Rate given' ignored='Not suitable for LCR'
000000 TRACE 13.09.12 18:17:49.248 CH(1): MNCC_SETUP_IND LCR<->BSC
calling imsi=  dialing number=
000000 DEBUG (in endpoint.cpp/Endpoint() line 48): EPOINT(1): Allocating
enpoint 1 and connecting it with: ioport
000000 DEBUG (in endpoint.cpp/portlist_new() line 150): EPOINT(1)
allocating port_list, attaching to port 1
000000 DEBUG (in port.cpp/epointlist_new() line 128): PORT(1) allocating
epoint_list.
000000 TRACE 13.09.12 18:17:49.249 CH(1): MNCC_LCHAN_MODIFY LCR<->BSC
speech version='Full/Half Rate given'  mode 0x01
000000 TRACE 13.09.12 18:17:49.249 CH(1): MNCC_CALL_PROC_REQ LCR<->BSC
progress coding=3 location=1 descr=8
000000 DEBUG (in port.cpp/new_state() line 261): PORT(GSM-0-in) new
state PORT_STATE_IDLE --> PORT_STATE_IN_PROCEEDING
000000 TRACE 13.09.12 18:17:49.249 CH(1): unknown LCR<->BSC
000000 DEBUG (in message.c/_message_put() line 61): message
MESSAGE_SETUP written from 1 to 1 (memory 8bfaf48 at file gsm_bs.cpp,
line 576)
000000 DEBUG (in message.c/message_get() line 106): message
MESSAGE_SETUP reading from 1 to 1 (memory 8bfaf48)
000000 DEBUG (in apppbx.cpp/ea_message_port() line 2476): EPOINT(1)
incoming call from callerid=imsi-, dialing=
000000 TRACE 13.09.12 18:17:49.249 EP(1): SETUP  from CH(1)  caller id
number=imsi- present='not available'  complete true
000000 DEBUG (in apppbx.cpp/port_setup() line 1372): EPOINT(1) incoming
call is extension
000000 DEBUG (in apppbx.cpp/port_setup() line 1382): EPOINT(1) call from
extension 'imsi-'
the given extension doesn't exist:
"/opt/new/lcr/var/lib/lcr/extensions/imsi-/settings"
000000 DEBUG (in extension.c/read_extension() line 58): the given
extension doesn't exist:
"/opt/new/lcr/var/lib/lcr/extensions/imsi-/settings"
000000 TRACE 13.09.12 18:17:49.250 EP(1): EXTENSION (not created)
extension imsi-
000000 DEBUG (in message.c/_message_put() line 61): message
MESSAGE_DISCONNECT written from 1 to 1 (memory 8bfe800 at file
apppbx.cpp, line 4213)
000000 TRACE 13.09.12 18:17:49.250 EP(1): DISCONNECT  to CH(1)  cause
value=21 location=1-Local-PBX
000000 DEBUG (in message.c/_message_put() line 61): message MESSAGE_TONE
written from 1 to 1 (memory 8c020b8 at file apppbx.cpp, line 579)
000000 TRACE 13.09.12 18:17:49.250 EP(1): TONE  to CH(1)  directory
default  name cause_80
000000 DEBUG (in message.c/message_get() line 106): message
MESSAGE_DISCONNECT reading from 1 to 1 (memory 8bfe800)
000000 TRACE 13.09.12 18:17:49.251 CH(1): MNCC_DISC_REQ LCR<->BSC
progress coding=3 location=1 descr=8  cause coding=3 location=1 value=21
000000 DEBUG (in port.cpp/new_state() line 261): PORT(GSM-0-in) new
state PORT_STATE_IN_PROCEEDING --> PORT_STATE_OUT_DISCONNECT
000000 DEBUG (in message.c/message_get() line 106): message MESSAGE_TONE
reading from 1 to 1 (memory 8c020b8)
000000 DEBUG (in port.cpp/message_epoint() line 611): PORT(GSM-0-in)
setting tone 'cause_80' dir ''
000000 TRACE 13.09.12 18:17:49.708 CH(1): MNCC_REL_IND LCR<->BSC
000000 DEBUG (in message.c/_message_put() line 61): message
MESSAGE_RELEASE written from 1 to 1 (memory 8bf9950 at file gsm.cpp,
line 585)
000000 DEBUG (in port.cpp/free_epointlist() line 84): PORT(1) removed
epoint from port
000000 DEBUG (in port.cpp/new_state() line 261): PORT(GSM-0-in) new
state PORT_STATE_OUT_DISCONNECT --> PORT_STATE_RELEASE
000000 DEBUG (in message.c/message_get() line 106): message
MESSAGE_RELEASE reading from 1 to 1 (memory 8bf9950)
000000 DEBUG (in apppbx.cpp/ea_message_port() line 2562): EPOINT(1)
release with cause=16 location=0 (terminal '', caller id 'imsi-')
000000 TRACE 13.09.12 18:17:49.709 EP(1): RELEASE  from CH(1)  cause
value=16 location=0-User
000000 DEBUG (in apppbx.cpp/port_disconnect_release() line 2043):
EPOINT(1) current multipoint cause 0 location 0, received cause 16
location 0.
000000 DEBUG (in apppbx.cpp/port_disconnect_release() line 2045):
EPOINT(1) new multipoint cause 16 location 0.
000000 DEBUG (in action.cpp/process_hangup() line 2428): EPOINT(1):
terminal ''
000000 DEBUG (in endpoint.cpp/free_portlist() line 189): EPOINT(1)
removed port 1 from port_list of endpoint
000000 DEBUG (in apppbx.cpp/release() line 222): EPOINT(1): do pending
release (joincause 16 location 0)
000000 DEBUG (in apppbx.cpp/release() line 240): EPOINT(1) do pending
release (portcause 16 portlocation)
000000 DEBUG (in apppbx.cpp/release() line 319): EPOINT(1) do pending
release of epoint itself.
000000 DEBUG (in gsm_bs.cpp/~Pgsm_bs() line 64): Destroyed GSM BS
process(GSM-0-in).
000000 DEBUG (in gsm.cpp/~Pgsm() line 202): Destroyed GSM process(GSM-0-in).
000000 DEBUG (in port.cpp/~Port() line 209): removing port (1) of type
0x3101, name 'GSM-0-in'
000000 DEBUG (in endpoint.cpp/~Endpoint() line 138): removed endpoint 1.
---


Latest commit of each tool:
---
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmocore# git log | head -6
commit eacba189b1a03c6a213b76df07dd766697017438
Author: Holger Hans Peter Freyther <zecke at selfish.org>
Date:   Tue Sep 11 12:27:47 2012 +0200

    git: Ignore generated tests executables

root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmocore# cd ..
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2# cd libosmo-abis/
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmo-abis# git log | head -6
commit 84e5cb9b3496527d43af974f2f89396d8145d743
Author: Pablo Neira Ayuso <pablo at gnumonks.org>
Date:   Thu Aug 23 23:41:54 2012 +0200

    ipaccess: fix leak of IPA control messages in the BTS side

root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmo-abis# cd ..
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2# cd openbsc
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/openbsc# cd openbsc
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/openbsc/openbsc# git log |
head -6
commit ca5d2111131101f7b8df40207b4c597b0e53f2cb
Merge: c11889f 31b245b
Author: Holger Hans Peter Freyther <zecke at selfish.org>
Date:   Tue Sep 11 18:02:46 2012 +0200

    Merge branch 'feature/local-mscs'
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/openbsc/openbsc# cd ../..
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2# cd lcr
root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/lcr# git log | head -6
commit 6911e09b77aa1eaac35b595bb4082e1f4c59ca71
Author: Andreas Eversberg <jolly at eversberg.eu>
Date:   Sun Aug 19 20:50:10 2012 +0200

    Allow calls to multiple interfaces simultaniosuly

root at tli-pc-2001:/home/tliuser1/sw_openbsc_2/lcr#
---

Any guidance would be appreciated.

Best regards,
David.

----
David Perez
Founder & Senior Security Analyst
Taddong
david at taddong.com | +34-699982432 | www.taddong.com
----
13sep12 19:50



From adolfocugat at gmail.com  Fri Sep 14 10:36:32 2012
From: adolfocugat at gmail.com (Adolfo Cugat)
Date: Fri, 14 Sep 2012 12:36:32 +0200
Subject: nanoBTS 165B
In-Reply-To: <CAKLdXFXCCqs+esU7+-+Fh1Ns-Kpm0NV6yO=ZLTUuY7G=9iGbiA@mail.gmail.com>
References: <CAKLdXFXCCqs+esU7+-+Fh1Ns-Kpm0NV6yO=ZLTUuY7G=9iGbiA@mail.gmail.com>
Message-ID: <CAKLdXFUkv+zki33cKdN=9b7i_7MX=om6RDNt1s-UG8MpU=GhGw@mail.gmail.com>

I?m selling a ip.access nanoBTS 165B 1900Mhz EDGE BTS, this one is right
now fully functional with openBSC. More info about it, email me out of the
list.


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

From galersekali at gmail.com  Sun Sep 16 21:31:22 2012
From: galersekali at gmail.com (anak galer)
Date: Mon, 17 Sep 2012 04:31:22 +0700
Subject: ask protocol gsm
Message-ID: <CAO_+gxLy3MiVKsN_EEDiGK05CAsfResvQ69XBQc6QRxrjFRMHg@mail.gmail.com>

Hi

I want asking about protocol GSM header like this.
ex :

/* A-bis Interface Management Messages */
NM_MT_ESTABLISH_TEI             = 0x21,


where it came from 0x21, explain please.
anyone have more reference

Thank You
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120917/fb1122b7/attachment.htm>

From laforge at gnumonks.org  Mon Sep 17 06:29:50 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 17 Sep 2012 08:29:50 +0200
Subject: ask protocol gsm
In-Reply-To: <CAO_+gxLy3MiVKsN_EEDiGK05CAsfResvQ69XBQc6QRxrjFRMHg@mail.gmail.com>
References: <CAO_+gxLy3MiVKsN_EEDiGK05CAsfResvQ69XBQc6QRxrjFRMHg@mail.gmail.com>
Message-ID: <20120917062950.GH31654@prithivi.gnumonks.org>

Hi Anak Galer,

On Mon, Sep 17, 2012 at 04:31:22AM +0700, anak galer wrote:
> I want asking about protocol GSM header like this.
> ex :
> 
> /* A-bis Interface Management Messages */
> NM_MT_ESTABLISH_TEI             = 0x21,
> 
> where it came from 0x21, explain please.
> anyone have more reference

You found that value in the following file:
libosmocore/include/osmocom/gsm/protocol/gsm_12_21.h

If you read the beginning of the file, it states:

/* GSM Network Management messages on the A-bis interface
 * 3GPP TS 12.21 version 8.0.0 Release 1999 / ETSI TS 100 623 V8.0.0 */

This is the exact specification number and specification version that
the value was taken from.  You can obtain the specification free of
charge from both ETSI and 3GPP.

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 john.e.otten at gmail.com  Tue Sep 18 15:25:54 2012
From: john.e.otten at gmail.com (John Otten)
Date: Tue, 18 Sep 2012 11:25:54 -0400
Subject: GPRS and PDP Context
Message-ID: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>

Good Day,

I have been working with OpenBSC for the past few weeks and I am able to
make voice calls and send SMS messages within the private network without
issues.

I am now attempting to add GPRS to the mix, and have been having less
success.  I have been able to make it to the internet from my phones
occasionally, but in general, there appears to be an issue between
osmo-sgsn and OpenGSN.  My hope is that it is a simple configuration
issue.  However, I suspect it may be due to an issue in the code, or
perhaps something mentioned last May (I have been scouring the mail
archive) regarding foreign vs local TLLIs.

My current setup is:
One Linux workstation which runs all three pertinent executables:
osmo-nitb, osmo-sgsn and ggsn.
A nanoBTS 165BU (PCS1900)
Two Nokia 6013b phones
I am working in an RF chamber.  I have some T-Mobile SIMs so, I have the
network set to T-Mobile rather than the test network.

I had previously been able to connect to the internet perhaps 1 in 10
times, presumably because the PDP contexts were not being created (the ggsn
output would not state that it was creating a context when I tried to
connect from the phone). I modified gprs_llc.c to handle the issue that
Frank Maas mentioned in May, regarding llme_alloc not localizing the TLLI.
Now, I can usually connect with a phone more consistently (but not always)
on a fresh restart of the three executables.

However, after connecting to the internet via the phone, if I cycle the
power on the phone, I am usually not able to connect to the internet again.
Sometimes the ggsn states that it "Received create PDP context request,"
and sometimes it doesn't state it when the sgsn (apparently) makes a
request.  At times, the ggsn reports "Received packet with no
destination!!!"  During these times, when I check the PDP contexts in
osmo-sgsn, I get:

OsmoSGSN> show pdp-context all
PDP Context IMSI: 310260XXXXXXXXX, SAPI: 3, NSAPI: 5
  APN: epc.tmobile.com
  PDP Address: IPv4 192.168.100.3
 SGSN PDP Context Statistics:
  User Data  Messages ( In):        0 (0/s 0/m 0/h 0/d)
  User Data  Messages (Out):        0 (0/s 0/m 0/h 0/d)
  User Data  Bytes    ( In):        0 (0/s 0/m 0/h 0/d)
  User Data  Bytes    (Out):        0 (0/s 0/m 0/h 0/d)

The times when the ggsn does not state that it received a create PDP
context request, the "show pdp-context all" command shows nothing.

My newbie guess is that osmo-sgsn is saving the state of the phone's
connection (based on the IMSI?), and is not releasing or clearing it when
the phone is powered off.  When the phone is powered back on, it will have
different connection parameters, but it will use the original parameters
after retrieving them based on the IMSI.  I have started to look through
the code in the src/gprs directory to see if this is the case.

I am wondering if anyone might have some insight into why the connection is
not fully restored.  Or perhaps they can offer guidance where I might begin
to look in the code. I can send logs and pcap files of a typical session if
anyone is interested.

Thanks!
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120918/020e4211/attachment.htm>

From Max.Suraev at fairwaves.ru  Wed Sep 19 09:14:36 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Wed, 19 Sep 2012 11:14:36 +0200
Subject: GPRS and PDP Context
In-Reply-To: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
Message-ID: <50598CFC.2000003@fairwaves.ru>

Hello.

I have similar setup although in my case it doesn't work at all.

Could you share your configs so I can check that I hadn't missed something obvious.
Here are mine. Note that I run everything on a single machine 192.168.10.53
nanoBTS is configured and successfully connected to openbsc (green light on bts).

/etc/ggsn.conf:

listen 127.0.0.1
dynip 10.0.0.0/24
pcodns1 8.8.8.8
pcodns2 208.67.220.220

/etc/osmo_sgsn.cfg:
!
line vty

 no login

!

sgsn

 gtp local-ip 192.168.10.53
 ggsn 0 remote-ip 127.0.0.1
 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.10.53
 encapsulation udp local-port 23000
 encapsulation framerelay-gre enabled 0
!

bssgp
!

/etc/openbsc.cfg:
!   !

password foo

!

line vty

 no login
!

e1_input

 e1_line 0 driver ipa
network

 network country code 1
 mobile network code 1
 short name OpenBSC

 long name OpenBSC

 auth policy accept-all

 location updating reject cause 13
 encryption a5 0
 neci 1
 rrlp mode none

 mm info 1
 handover 0
 handover window rxlev averaging 10
 handover window rxqual averaging 1
 handover window rxlev neighbor averaging 10
 handover power budget interval 6
 handover power budget hysteresis 3
 handover maximum distance 9999
 timer t3101 10
 timer t3103 0
 timer t3105 0
 timer t3107 0
 timer t3109 0
 timer t3111 0
 timer t3113 60
 timer t3115 0
 timer t3117 0
 timer t3119 0
 timer t3141 0
 bts 0
  type nanobts
  band DCS1800
  cell_identity 0
  location_area_code 1
  training_sequence_code 7
  base_station_id_code 63
  ms max power 15
  cell reselection hysteresis 4
  rxlev access min 0
  channel allocator ascending
  rach tx integer 9
  rach max transmission 7
  ip.access unit_id 1801 0
  oml ip.access stream_id 255 line 0
  gprs mode gprs
  gprs routing area 0
  gprs cell bvci 2
  gprs nsei 101
  gprs nsvc 0 nsvci 101
  gprs nsvc 0 local udp port 23000
  gprs nsvc 0 remote udp port 23000
  gprs nsvc 0 remote ip 192.168.10.53
  trx 0
   rf_locked 0
   arfcn 514
   nominal power 23
   max_power_red 20
   rsl e1 tei 0
    timeslot 0
     phys_chan_config CCCH+SDCCH4
    timeslot 1
     phys_chan_config SDCCH8
    timeslot 2
     phys_chan_config TCH/F
    timeslot 3
     phys_chan_config TCH/F
    timeslot 4
     phys_chan_config TCH/F
    timeslot 5
     phys_chan_config PDCH
    timeslot 6
     phys_chan_config PDCH
    timeslot 7
     phys_chan_config TCH/F

-- 
best regards,
Max, http://fairwaves.ru



From john.e.otten at gmail.com  Wed Sep 19 15:35:57 2012
From: john.e.otten at gmail.com (John Otten)
Date: Wed, 19 Sep 2012 11:35:57 -0400
Subject: GPRS and PDP Context
In-Reply-To: <50598CFC.2000003@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
Message-ID: <CAA__=E-8xVA7eAWVMOhV2n4T9ur1oUeX--mUGJfBQG969GBmxg@mail.gmail.com>

Hi Max,

I am reluctant to post my actual config files. However, your config files
seem nearly identical to mine.  Below, I will describe the differences:

In your ggsn.conf file, your listen parameter is set to 127.0.0.1.  What I
did was make an alias, eth0:1, to a different IP address (192.168.10.60)
and used it for this parameter. (Actually, my main IP address used for
OpenBSC is also an alias since I was trying to match the subnet that the
BTS came from which is different from the machine I am using. We didn't
want to reconfigure the BTS from its settings just so I could play with it.
So, I made an alias, eth0:0, which on your machine would be treated as eth0
-  192.168.10.53.  In your case, you would probably not need to make the
eth0:0 alias, but if your BTS is configured to a different subnet from
192.168.10.X, then you might have to.) Anyway, you might want to make an
alias to 192,168.10.60 (or whatever address is available on your network)
and use that address for your listen parameter.

Also, in ggsn.conf, I used the IP address of my DNS server for both of the
pcodns parameters.  Also, I set the apn parameter to epc.tmobile.com which
is the access point for T-Mobile (which is the kind of SIMs I am using).  I
don't know if there is an apn that could be used for the 001 01 test
network.  Perhaps that has been discussed on the list previously.  In any
event, the apn parameter is experimental, so you may have different results.

Finally in ggsn.conf, I set the net and dynip parameters to 192.168.100.0/24,
and then made a tunnel to it after starting the ggsn executable (but before
starting osmo-sgsn) with the following command:
    sudo route add -net 192.168.100.0 netmask 255.255.255.0 gw 192.168.100.1
How did we come up with 192.168.100.1 for the gateway address? Well, after
starting ggsn, the ifconfig command will show the IP address of the tunnel
endpoint (tun0) that is created by the ggsn. In our case (and probably all
cases), this was 192.168.100.1.

Make sure you have followed the instructions on the OpenBSC_GPRS page about
setting the iptables

In the osmo_sgsn.cfg, I set the gtp local-ip to the eth0:0 alias or
192.168.10.53 (which you probably have correct in your file - assuming your
BTS is configured for the same subnet of your machine), and the ggsn 0
remote-ip parameter to the eth0:1 alias (192.168.10.60).

In the openbsc.cfg file, the only difference I see is the NCC and MNC
(because I am using T-Mobile SIMs) and I made timeslot 7 a PDCH channel
instead of a TCH/F.

A critical issue is setting up the tunnel between osmo_sgsn and ggsn,
before starting osmo_sgsn.  I also start the osmo-nitb executable last,
after the other two executables are up and running.

Finally, at the suggestion of one of the list members, I tried a different
phone that doesn't use the original Nokia baseband.  I tried a Nokia Lumia
phone (which uses the Microsoft Mobile OS) and it works *much* better.

I hope that this information helps. Good Luck!
John

On Wed, Sep 19, 2012 at 5:14 AM, ? <Max.Suraev at fairwaves.ru> wrote:

> Hello.
>
> I have similar setup although in my case it doesn't work at all.
>
> Could you share your configs so I can check that I hadn't missed something
> obvious.
> Here are mine. Note that I run everything on a single machine 192.168.10.53
> nanoBTS is configured and successfully connected to openbsc (green light
> on bts).
>
> /etc/ggsn.conf:
>
> listen 127.0.0.1
> dynip 10.0.0.0/24
> pcodns1 8.8.8.8
> pcodns2 208.67.220.220
>
> /etc/osmo_sgsn.cfg:
> !
> line vty
>
>  no login
>
> !
>
> sgsn
>
>  gtp local-ip 192.168.10.53
>  ggsn 0 remote-ip 127.0.0.1
>  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.10.53
>  encapsulation udp local-port 23000
>  encapsulation framerelay-gre enabled 0
> !
>
> bssgp
> !
>
> /etc/openbsc.cfg:
> !   !
>
> password foo
>
> !
>
> line vty
>
>  no login
> !
>
> e1_input
>
>  e1_line 0 driver ipa
> network
>
>  network country code 1
>  mobile network code 1
>  short name OpenBSC
>
>  long name OpenBSC
>
>  auth policy accept-all
>
>  location updating reject cause 13
>  encryption a5 0
>  neci 1
>  rrlp mode none
>
>  mm info 1
>  handover 0
>  handover window rxlev averaging 10
>  handover window rxqual averaging 1
>  handover window rxlev neighbor averaging 10
>  handover power budget interval 6
>  handover power budget hysteresis 3
>  handover maximum distance 9999
>  timer t3101 10
>  timer t3103 0
>  timer t3105 0
>  timer t3107 0
>  timer t3109 0
>  timer t3111 0
>  timer t3113 60
>  timer t3115 0
>  timer t3117 0
>  timer t3119 0
>  timer t3141 0
>  bts 0
>   type nanobts
>   band DCS1800
>   cell_identity 0
>   location_area_code 1
>   training_sequence_code 7
>   base_station_id_code 63
>   ms max power 15
>   cell reselection hysteresis 4
>   rxlev access min 0
>   channel allocator ascending
>   rach tx integer 9
>   rach max transmission 7
>   ip.access unit_id 1801 0
>   oml ip.access stream_id 255 line 0
>   gprs mode gprs
>   gprs routing area 0
>   gprs cell bvci 2
>   gprs nsei 101
>   gprs nsvc 0 nsvci 101
>   gprs nsvc 0 local udp port 23000
>   gprs nsvc 0 remote udp port 23000
>   gprs nsvc 0 remote ip 192.168.10.53
>   trx 0
>    rf_locked 0
>    arfcn 514
>    nominal power 23
>    max_power_red 20
>    rsl e1 tei 0
>     timeslot 0
>      phys_chan_config CCCH+SDCCH4
>     timeslot 1
>      phys_chan_config SDCCH8
>     timeslot 2
>      phys_chan_config TCH/F
>     timeslot 3
>      phys_chan_config TCH/F
>     timeslot 4
>      phys_chan_config TCH/F
>     timeslot 5
>      phys_chan_config PDCH
>     timeslot 6
>      phys_chan_config PDCH
>     timeslot 7
>      phys_chan_config TCH/F
>
> --
> best regards,
> Max, http://fairwaves.ru
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120919/7e1e735e/attachment.htm>

From peter at stuge.se  Wed Sep 19 15:48:10 2012
From: peter at stuge.se (Peter Stuge)
Date: Wed, 19 Sep 2012 17:48:10 +0200
Subject: GPRS and PDP Context
In-Reply-To: <50598CFC.2000003@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
Message-ID: <20120919154810.19091.qmail@stuge.se>

? wrote:
> I have similar setup although in my case it doesn't work at all.
..
> /etc/osmo_sgsn.cfg:
..
> ns
..
>  encapsulation udp local-ip 192.168.10.53
>  encapsulation udp local-port 23000

> /etc/openbsc.cfg:
..
>  bts 0
..
>   gprs nsvc 0 local udp port 23000
>   gprs nsvc 0 remote udp port 23000
>   gprs nsvc 0 remote ip 192.168.10.53

I don't think both processes can use the same port; move one of them
and configure the other accordingly.


//Peter



From Max.Suraev at fairwaves.ru  Thu Sep 20 16:00:01 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Thu, 20 Sep 2012 18:00:01 +0200
Subject: GPRS and PDP Context
In-Reply-To: <20120919154810.19091.qmail@stuge.se>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
Message-ID: <505B3D81.9030605@fairwaves.ru>

19.09.2012 17:48, Peter Stuge ?????:
> ? wrote:
>> I have similar setup although in my case it doesn't work at all.
> ..
>> /etc/osmo_sgsn.cfg:
> ..
>> ns
> ..
>>  encapsulation udp local-ip 192.168.10.53
>>  encapsulation udp local-port 23000
> 
>> /etc/openbsc.cfg:
> ..
>>  bts 0
> ..
>>   gprs nsvc 0 local udp port 23000
>>   gprs nsvc 0 remote udp port 23000
>>   gprs nsvc 0 remote ip 192.168.10.53
> 
> I don't think both processes can use the same port; move one of them
> and configure the other accordingly.

Thanks for suggestion.

Now it looks like this:

 /etc/osmo_sgsn.cfg:
...
encapsulation udp local-ip 192.168.10.53
encapsulation udp local-port 23333
...

/etc/openbsc.cfg:
...
gprs nsvc 0 local udp port 23000
gprs nsvc 0 remote udp port 23333
gprs nsvc 0 remote ip 192.168.10.53
...

Still no luck :(

How to obtain as much debug information as possible?

ggsn -d
osmo-sgsn -d GPRS (this causes core-dump unless executed in gdb :)
osmo-nitb -a -d GPRS

The only output I got in this configuration is:

Starting program: /usr/bin/osmo-sgsn
<0011> gprs_ns.c:171 NSVCI=65534 Creating NS-VC
<0011> gprs_ns.c:171 NSVCI=65535 Creating NS-VC
<0011> gprs_ns.c:806 Creating NS-VC for BSS at 192.168.10.55:23000
<0011> gprs_ns.c:679 NSEI=65535 Rx NS RESET (NSVCI=0, cause=O&M intervention)
<0011> gprs_ns.c:538 NSEI=101 Tx NS RESET ACK (NSVCI=101)
<0011> gprs_ns.c:865 NSEI=101 Rx NS UNBLOCK
<0012> gprs_bssgp.c:249 BSSGP BVCI=0 Rx RESET cause=Transmission capacity modified
<0012> gprs_bssgp.c:344 BSSGP BVCI=2 Rx BVC-UNBLOCK
<0012> gprs_bssgp_util.c:103 BSSGP BVCI=2 Tx STATUS, cause=Unknown BVCI
<0012> gprs_bssgp.c:249 BSSGP BVCI=2 Rx RESET cause=O&M intervention
<0012> gprs_bssgp.c:272 Cell 1-1-1-0 CI 0 on BVCI 2
<0012> gprs_bssgp.c:344 BSSGP BVCI=2 Rx BVC-UNBLOCK
<0012> gprs_bssgp.c:747 BSSGP BVCI=2 Rx Flow Control BVC

I don't even understand if phone requested ip address?
Was ip address assigned?
Is ggsn-sgsn-nitb connectivity ok?

It's good that howto briefly describes setup, but what do to when it's not working
out of the box?

Any troubleshooting tips?
Anyone with working gprs setup willing to share configuration files as a point of
reference?

-- 
best regards,
Max, http://fairwaves.ru




From david at taddong.com  Thu Sep 20 16:09:43 2012
From: david at taddong.com (David Perez)
Date: Thu, 20 Sep 2012 18:09:43 +0200
Subject: GPRS and PDP Context
In-Reply-To: <505B3D81.9030605@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
Message-ID: <505B3FC7.7010608@taddong.com>

Hi,

In order to get more information, you may telnet into osmo-sgsn on port
4245 (telnet localhost 4245), and type:
---
logging enable
logging filter all 1
logging level mm debug
---

HTH.

----
David Perez
Founder & Senior Security Analyst
Taddong
david at taddong.com | +34-699982432 | www.taddong.com
----
20sep12 1808

On 20-Sep-12 18:00, ? wrote:
> 19.09.2012 17:48, Peter Stuge ?????:
>> ? wrote:
>>> I have similar setup although in my case it doesn't work at all.
>> ..
>>> /etc/osmo_sgsn.cfg:
>> ..
>>> ns
>> ..
>>>  encapsulation udp local-ip 192.168.10.53
>>>  encapsulation udp local-port 23000
>>
>>> /etc/openbsc.cfg:
>> ..
>>>  bts 0
>> ..
>>>   gprs nsvc 0 local udp port 23000
>>>   gprs nsvc 0 remote udp port 23000
>>>   gprs nsvc 0 remote ip 192.168.10.53
>>
>> I don't think both processes can use the same port; move one of them
>> and configure the other accordingly.
> 
> Thanks for suggestion.
> 
> Now it looks like this:
> 
>  /etc/osmo_sgsn.cfg:
> ...
> encapsulation udp local-ip 192.168.10.53
> encapsulation udp local-port 23333
> ...
> 
> /etc/openbsc.cfg:
> ...
> gprs nsvc 0 local udp port 23000
> gprs nsvc 0 remote udp port 23333
> gprs nsvc 0 remote ip 192.168.10.53
> ...
> 
> Still no luck :(
> 
> How to obtain as much debug information as possible?
> 
> ggsn -d
> osmo-sgsn -d GPRS (this causes core-dump unless executed in gdb :)
> osmo-nitb -a -d GPRS
> 
> The only output I got in this configuration is:
> 
> Starting program: /usr/bin/osmo-sgsn
> <0011> gprs_ns.c:171 NSVCI=65534 Creating NS-VC
> <0011> gprs_ns.c:171 NSVCI=65535 Creating NS-VC
> <0011> gprs_ns.c:806 Creating NS-VC for BSS at 192.168.10.55:23000
> <0011> gprs_ns.c:679 NSEI=65535 Rx NS RESET (NSVCI=0, cause=O&M intervention)
> <0011> gprs_ns.c:538 NSEI=101 Tx NS RESET ACK (NSVCI=101)
> <0011> gprs_ns.c:865 NSEI=101 Rx NS UNBLOCK
> <0012> gprs_bssgp.c:249 BSSGP BVCI=0 Rx RESET cause=Transmission capacity modified
> <0012> gprs_bssgp.c:344 BSSGP BVCI=2 Rx BVC-UNBLOCK
> <0012> gprs_bssgp_util.c:103 BSSGP BVCI=2 Tx STATUS, cause=Unknown BVCI
> <0012> gprs_bssgp.c:249 BSSGP BVCI=2 Rx RESET cause=O&M intervention
> <0012> gprs_bssgp.c:272 Cell 1-1-1-0 CI 0 on BVCI 2
> <0012> gprs_bssgp.c:344 BSSGP BVCI=2 Rx BVC-UNBLOCK
> <0012> gprs_bssgp.c:747 BSSGP BVCI=2 Rx Flow Control BVC
> 
> I don't even understand if phone requested ip address?
> Was ip address assigned?
> Is ggsn-sgsn-nitb connectivity ok?
> 
> It's good that howto briefly describes setup, but what do to when it's not working
> out of the box?
> 
> Any troubleshooting tips?
> Anyone with working gprs setup willing to share configuration files as a point of
> reference?
> 



From Max.Suraev at fairwaves.ru  Thu Sep 20 16:47:31 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Thu, 20 Sep 2012 18:47:31 +0200
Subject: GPRS and PDP Context
In-Reply-To: <505B3FC7.7010608@taddong.com>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru> <505B3FC7.7010608@taddong.com>
Message-ID: <505B48A3.3000502@fairwaves.ru>

20.09.2012 18:09, David Perez ?????:
> Hi,
> 
> In order to get more information, you may telnet into osmo-sgsn on port
> 4245 (telnet localhost 4245), and type:
> ---
> logging enable
> logging filter all 1
> logging level mm debug
> ---
Thanks for the hint. Sadly it has no visible effect so it looks like problem is
someplace else.


-- 
best regards,
Max, http://fairwaves.ru



From laforge at gnumonks.org  Fri Sep 21 07:24:35 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 21 Sep 2012 09:24:35 +0200
Subject: GPRS and PDP Context
In-Reply-To: <505B3D81.9030605@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
Message-ID: <20120921072435.GG15271@prithivi.gnumonks.org>

Hi Max,

On Thu, Sep 20, 2012 at 06:00:01PM +0200, ? wrote:
> How to obtain as much debug information as possible?

I suggest you study the logging subsystem of libosmocore, which is used
in all of osmo-nitb/osmo-sgsn/osmo-bsc/etc.

> ggsn -d
> osmo-sgsn -d GPRS (this causes core-dump unless executed in gdb :)

It should be -d DGPRS, but I suggest you rather configure logging for
stdout or for your given telnet session via VTY.

I suggest to enable debug for NS, BSSGP, LLC, (G)MM

> The only output I got in this configuration is: [...]

This means that the SGSN and the BTS have connected successfully over
Gb/IP.

> I don't even understand if phone requested ip address?

Obtaining an IP address is the _last_ activity, after many other things.
NS/BSSGP is up.  Next you should see some GPRS ATTACH / GPRS ROUTING
AREA UPDATE.  Only after that, you can get to PDP CONTEXT ACTIVATE and
finally IP traffic.

> Is ggsn-sgsn-nitb connectivity ok?

At the point you're looking at, the GGSN is never used.  It is only
involved in PDP context establishment and transport of IP packets.

> It's good that howto briefly describes setup, but what do to when it's
> not working out of the box?

enable debugging for the respective protocol levels in osmo-sgsn using
VTY, and look at the Gb and GTP communication between the processes in
wireshark.  All protocol layers of both Gb and GTP protocol stacking are
fully supported in mainline wireshark, so all information you can
possibly want is visualized.

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 Max.Suraev at fairwaves.ru  Fri Sep 21 09:36:37 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Fri, 21 Sep 2012 11:36:37 +0200
Subject: GPRS and PDP Context
In-Reply-To: <20120921072435.GG15271@prithivi.gnumonks.org>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
Message-ID: <505C3525.6080305@fairwaves.ru>

21.09.2012 09:24, Harald Welte ?????:
>
> It should be -d DGPRS, but I suggest you rather configure logging for
> stdout or for your given telnet session via VTY.
>
> I suggest to enable debug for NS, BSSGP, LLC, (G)MM
Sadly with latest libosmocore from git I got segfault in log_parse_category_mask()
with osmo-sgsn --debug=DNS:DGPRS:DNS:DBSSGP:DLLC:DMM:DGMM

Is it a known bug?
>> The only output I got in this configuration is: [...]
> This means that the SGSN and the BTS have connected successfully over
> Gb/IP.
>
>> I don't even understand if phone requested ip address?
> Obtaining an IP address is the _last_ activity, after many other things.
> NS/BSSGP is up.  Next you should see some GPRS ATTACH / GPRS ROUTING
> AREA UPDATE.  Only after that, you can get to PDP CONTEXT ACTIVATE and
> finally IP traffic.
>
>> Is ggsn-sgsn-nitb connectivity ok?
> At the point you're looking at, the GGSN is never used.  It is only
> involved in PDP context establishment and transport of IP packets.
>
>> It's good that howto briefly describes setup, but what do to when it's
>> not working out of the box?
> enable debugging for the respective protocol levels in osmo-sgsn using
> VTY, and look at the Gb and GTP communication between the processes in
> wireshark.  All protocol layers of both Gb and GTP protocol stacking are
> fully supported in mainline wireshark, so all information you can
> possibly want is visualized.
>
Thank you for great hints.
Is it possible to add debug/troubleshooting section to
http://openbsc.osmocom.org/trac/wiki/OpenBSC_GPRS ?
I'm pretty sure I'm not the only one who'd find it useful.

-- 
best regards,
Max, http://fairwaves.ru




From peter at stuge.se  Fri Sep 21 12:19:40 2012
From: peter at stuge.se (Peter Stuge)
Date: Fri, 21 Sep 2012 14:19:40 +0200
Subject: GPRS and PDP Context
In-Reply-To: <505C3525.6080305@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<505C3525.6080305@fairwaves.ru>
Message-ID: <20120921121940.12741.qmail@stuge.se>

? wrote:
> > It should be -d DGPRS, but I suggest you rather configure logging for
> > stdout or for your given telnet session via VTY.
> >
> > I suggest to enable debug for NS, BSSGP, LLC, (G)MM
> 
> Sadly with latest libosmocore from git I got segfault in log_parse_category_mask()
> with osmo-sgsn --debug=DNS:DGPRS:DNS:DBSSGP:DLLC:DMM:DGMM

Please provide a backtrace.


> > All protocol layers of both Gb and GTP protocol stacking are
> > fully supported in mainline wireshark, so all information you can
> > possibly want is visualized.
> 
> Thank you for great hints.
> Is it possible to add debug/troubleshooting section to
> http://openbsc.osmocom.org/trac/wiki/OpenBSC_GPRS ?
> I'm pretty sure I'm not the only one who'd find it useful.

You mean like so:

How to troubleshoot ethernet- and IP-based GSM network components
Use a packet sniffer such as wireshark.

Seriously?


//Peter



From openbsc at ngolde.de  Fri Sep 21 15:56:07 2012
From: openbsc at ngolde.de (Nico Golde)
Date: Fri, 21 Sep 2012 17:56:07 +0200
Subject: [PATCH] logging.c: log_parse_category_mask(), skip log category
	name... (was: Re: GPRS and PDP Context)
In-Reply-To: <505C3525.6080305@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<505C3525.6080305@fairwaves.ru>
Message-ID: <20120921155607.GA20070@nybble.binarybase.org>

Hi,
* ? <Max.Suraev at fairwaves.ru> [2012-09-21 15:12]:
> 21.09.2012 09:24, Harald Welte ?????:
> >
> > It should be -d DGPRS, but I suggest you rather configure logging for
> > stdout or for your given telnet session via VTY.
> >
> > I suggest to enable debug for NS, BSSGP, LLC, (G)MM
> Sadly with latest libosmocore from git I got segfault in log_parse_category_mask()
> with osmo-sgsn --debug=DNS:DGPRS:DNS:DBSSGP:DLLC:DMM:DGMM

This seems to be caused by a bug in libosmocore. I'm 
actually surprised that nobody encountered this crash 
before. The reason is that log_parse_category_mask() checks 
for osmo_log_info->cat[i].name being NULL after passing the 
pointer to strlen.

Attached is a patch to fix this.

Cheers
Nico

From nico at ngolde.de  Fri Sep 21 15:44:58 2012
From: nico at ngolde.de (Nico Golde)
Date: Fri, 21 Sep 2012 17:44:58 +0200
Subject: [PATCH] logging.c: log_parse_category_mask(), skip log category name
 right away if name is NULL to prevent passing a NULL ptr to
 strlen
Message-ID: <mailman.58.1641744178.42898.openbsc@lists.osmocom.org>

---
 src/logging.c |   12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/src/logging.c b/src/logging.c
index 0816570..f368bea 100644
--- a/src/logging.c
+++ b/src/logging.c
@@ -167,6 +167,7 @@ void log_parse_category_mask(struct log_target* target, const char *_mask)
 	int i = 0;
 	char *mask = strdup(_mask);
 	char *category_token = NULL;
+	size_t length, cat_length;
 
 	/* Disable everything to enable it afterwards */
 	for (i = 0; i < osmo_log_info->num_cat; ++i)
@@ -176,16 +177,17 @@ void log_parse_category_mask(struct log_target* target, const char *_mask)
 	do {
 		for (i = 0; i < osmo_log_info->num_cat; ++i) {
 			char* colon = strstr(category_token, ",");
-			int length = strlen(category_token);
-			int cat_length = strlen(osmo_log_info->cat[i].name);
+
+			if (!osmo_log_info->cat[i].name)
+				continue;
+
+			length = strlen(category_token);
+			cat_length = strlen(osmo_log_info->cat[i].name);
 
 			/* Use longest length not to match subocurrences. */
 			if (cat_length > length)
 				length = cat_length;
 
-			if (!osmo_log_info->cat[i].name)
-				continue;
-
 			if (colon)
 			    length = colon - category_token;
 
-- 
1.7.10.4


--sdtB3X0nJg68CQEu--



From Max.Suraev at fairwaves.ru  Fri Sep 21 16:37:11 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Fri, 21 Sep 2012 18:37:11 +0200
Subject: [PATCH] logging.c: log_parse_category_mask(), skip log category
	name...
In-Reply-To: <20120921155607.GA20070@nybble.binarybase.org>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<505C3525.6080305@fairwaves.ru>
	<20120921155607.GA20070@nybble.binarybase.org>
Message-ID: <505C97B7.2090503@fairwaves.ru>

And this one fix another segfault uncovered by previous patch :)
Seriously, what's the magic command-line option which enables logging without causing
segfaults?

-- 
best regards,
Max, http://fairwaves.ru

From max at sec.t-labs.tu-berlin.de  Fri Sep 21 16:33:00 2012
From: max at sec.t-labs.tu-berlin.de (Max)
Date: Fri, 21 Sep 2012 18:33:00 +0200
Subject: [PATCH] fix segfault during show running-config
Message-ID: <mailman.59.1641744178.42898.openbsc@lists.osmocom.org>

---
 src/vty/logging_vty.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/vty/logging_vty.c b/src/vty/logging_vty.c
index 6166f1f..71d926d 100644
--- a/src/vty/logging_vty.c
+++ b/src/vty/logging_vty.c
@@ -547,7 +547,7 @@ static int config_write_log_single(struct vty *vty, struct log_target *tgt)
 	for (i = 0; i < osmo_log_info->num_cat; i++) {
 		const struct log_category *cat = &tgt->categories[i];
 		char cat_lower[32];
-
+		if (!osmo_log_info->cat[i].name) continue;
 		/* stupid old osmo logging API uses uppercase strings... */
 		osmo_str2lower(cat_lower, osmo_log_info->cat[i].name+1);
 		osmo_str2lower(level_lower, log_level_str(cat->loglevel));
-- 
1.7.9.5


--------------080000000307010502010601--



From holger at freyther.de  Thu Sep 27 14:38:53 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 27 Sep 2012 16:38:53 +0200
Subject: [PATCH] logging.c: log_parse_category_mask(), skip log category
	name... (was: Re: GPRS and PDP Context)
In-Reply-To: <20120921155607.GA20070@nybble.binarybase.org>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<505C3525.6080305@fairwaves.ru>
	<20120921155607.GA20070@nybble.binarybase.org>
Message-ID: <20120927143853.GB18734@localhost>

On Fri, Sep 21, 2012 at 05:56:07PM +0200, Nico Golde wrote:
> Attached is a patch to fix this.

thanks! I have applied it and moved the size_t into the scope
where the variable is used. I have moved the logging test from
the OpenBSC repository to libosmocore and modified the testcase
to cover this crash.

cheers
	holger



From laforge at gnumonks.org  Fri Sep 21 16:33:20 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 21 Sep 2012 18:33:20 +0200
Subject: GPRS and PDP Context
In-Reply-To: <505C3525.6080305@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<505C3525.6080305@fairwaves.ru>
Message-ID: <20120921163320.GG22624@prithivi.gnumonks.org>

Hi Max,

On Fri, Sep 21, 2012 at 11:36:37AM +0200, ? wrote:

> > I suggest to enable debug for NS, BSSGP, LLC, (G)MM
> Sadly with latest libosmocore from git I got segfault in log_parse_category_mask()
> with osmo-sgsn --debug=DNS:DGPRS:DNS:DBSSGP:DLLC:DMM:DGMM
> 
> Is it a known bug?

not that I'm aware of, sorry.  Any patches/fixes are appreciated.  I
guess the command-line baesed logging specification was useful early on,
when there were 3 or for subsystems.  Today it is nothing but an old
relict, and most people probably use the more comfortable VTY based
configuration.

> Is it possible to add debug/troubleshooting section to
> http://openbsc.osmocom.org/trac/wiki/OpenBSC_GPRS ?
> I'm pretty sure I'm not the only one who'd find it useful.

Sure it is possible and appreciated!

If you don't have a wiki account, please simply ask for one and you can
happily add all the information that you are missing.

-- 
- 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 Max.Suraev at fairwaves.ru  Mon Sep 24 15:18:07 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Mon, 24 Sep 2012 17:18:07 +0200
Subject: GPRS and PDP Context
In-Reply-To: <20120921072435.GG15271@prithivi.gnumonks.org>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
Message-ID: <506079AF.702@fairwaves.ru>

21.09.2012 09:24, Harald Welte ?????:
> Hi Max,
>
> On Thu, Sep 20, 2012 at 06:00:01PM +0200, ? wrote:
>> How to obtain as much debug information as possible?
> I suggest you study the logging subsystem of libosmocore, which is used
> in all of osmo-nitb/osmo-sgsn/osmo-bsc/etc.
>
Is there more comprehensive documentation for osmo-sgsn than
http://openbsc.osmocom.org/trac/wiki/osmo-sgsn_VTY ?
Something similar to
http://openbsc.osmocom.org/trac/wiki/osmo-nitb_VTY would be very helpful.

-- 
best regards,
Max, http://fairwaves.ru




From openbsc at ngolde.de  Mon Sep 24 15:42:45 2012
From: openbsc at ngolde.de (Nico Golde)
Date: Mon, 24 Sep 2012 17:42:45 +0200
Subject: GPRS and PDP Context
In-Reply-To: <506079AF.702@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<506079AF.702@fairwaves.ru>
Message-ID: <20120924154245.GA31735@nybble.binarybase.org>

Hi,
* ? <Max.Suraev at fairwaves.ru> [2012-09-24 17:38]:
> 21.09.2012 09:24, Harald Welte ?????:
> > On Thu, Sep 20, 2012 at 06:00:01PM +0200, ? wrote:
> >> How to obtain as much debug information as possible?
> > I suggest you study the logging subsystem of libosmocore, which is used
> > in all of osmo-nitb/osmo-sgsn/osmo-bsc/etc.
> >
> Is there more comprehensive documentation for osmo-sgsn than
> http://openbsc.osmocom.org/trac/wiki/osmo-sgsn_VTY ?
> Something similar to
> http://openbsc.osmocom.org/trac/wiki/osmo-nitb_VTY would be very helpful.

Unfortunately not. The best hint I can give at this point is 
a grep on sgsn_vty.c ;)
DEFUN(cfg_sgsn, cfg_sgsn_cmd,
    "sgsn",
    SGSN_STR)
--
DEFUN(cfg_sgsn_bind_addr, cfg_sgsn_bind_addr_cmd,
    "gtp local-ip A.B.C.D",
    "GTP Parameters\n"
    "Set the IP address for the local GTP bind\n"
    "IPv4 Address\n")
--
DEFUN(cfg_ggsn_remote_ip, cfg_ggsn_remote_ip_cmd,
    "ggsn <0-255> remote-ip A.B.C.D",
    GGSN_STR "GGSN Number\n" IP_STR "IPv4 Address\n")
--
DEFUN(cfg_ggsn_remote_port, cfg_ggsn_remote_port_cmd,
    "ggsn <0-255> remote-port <0-65535>",
    "")
--
DEFUN(cfg_ggsn_gtp_version, cfg_ggsn_gtp_version_cmd,
    "ggsn <0-255> gtp-version (0|1)",
    GGSN_STR "GGSN Number\n" "GTP Version\n"
    "Version 0\n" "Version 1\n")
--
DEFUN(cfg_apn_ggsn, cfg_apn_ggsn_cmd,
    "apn APNAME ggsn <0-255>",
    "")
--
DEFUN(show_sgsn, show_sgsn_cmd, "show sgsn",
      SHOW_STR "Display information about the SGSN")
--
DEFUN(show_mmctx_tlli, show_mmctx_tlli_cmd,
    "show mm-context tlli HEX [pdp]",
    SHOW_STR MMCTX_STR "Identify by TLLI\n" "TLLI\n" INCLUDE_PDP_STR)
--
DEFUN(swow_mmctx_imsi, show_mmctx_imsi_cmd,
    "show mm-context imsi IMSI [pdp]",
    SHOW_STR MMCTX_STR "Identify by IMSI\n" "IMSI of the MM Context\n"
    INCLUDE_PDP_STR)
--
DEFUN(swow_mmctx_all, show_mmctx_all_cmd,
    "show mm-context all [pdp]",
    SHOW_STR MMCTX_STR "All MM Contexts\n" INCLUDE_PDP_STR)
--
DEFUN(show_ggsn, show_ggsn_cmd,
    "show ggsn",
    "")
--
DEFUN(show_pdpctx_all, show_pdpctx_all_cmd,
    "show pdp-context all",
    SHOW_STR "Display information on PDP Context\n" "Show everything\n")

Cheers
Nico



From holger at freyther.de  Tue Sep 25 08:29:18 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Sep 2012 10:29:18 +0200
Subject: GPRS and PDP Context
In-Reply-To: <506079AF.702@fairwaves.ru>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
	<506079AF.702@fairwaves.ru>
Message-ID: <20120925082918.GL29441@localhost>

On Mon, Sep 24, 2012 at 05:18:07PM +0200, ? wrote:
> 21.09.2012 09:24, Harald Welte ?????:

> Is there more comprehensive documentation for osmo-sgsn than
> http://openbsc.osmocom.org/trac/wiki/osmo-sgsn_VTY ?
> Something similar to
> http://openbsc.osmocom.org/trac/wiki/osmo-nitb_VTY would be very helpful.

Hi,

I have created libosmocore support to dump the VTY commands into a xml
file (and wrote a schema). It is up to users to pick that up and write
a manual. Using the "contrib/dump_all_docs.py" is the easiest way to
dump the VTY commands into an XML file.


holger




From Max.Suraev at fairwaves.ru  Tue Sep 25 14:47:56 2012
From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=)
Date: Tue, 25 Sep 2012 16:47:56 +0200
Subject: GPRS and PDP Context
In-Reply-To: <20120921072435.GG15271@prithivi.gnumonks.org>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<505B3D81.9030605@fairwaves.ru>
	<20120921072435.GG15271@prithivi.gnumonks.org>
Message-ID: <5061C41C.3010906@fairwaves.ru>

21.09.2012 09:24, Harald Welte ?????:
> Obtaining an IP address is the _last_ activity, after many other things.
> NS/BSSGP is up.  Next you should see some GPRS ATTACH / GPRS ROUTING
> AREA UPDATE.  Only after that, you can get to PDP CONTEXT ACTIVATE and
> finally IP traffic.

Despite my efforts to make use of logging system I do not see anything like  GPRS
ATTACH / GPRS ROUTING AREA UPDATE.

So either I'm not running enough logging or failure is lurking somewhere in previous
steps.
Hence the questions:

- who exactly will report "GPRS ATTACH / GPRS ROUTING AREA UPDATE" messages?
- how do I check that NS/BSSGP is up?

-- 
best regards,
Max, http://fairwaves.ru




From john.e.otten at gmail.com  Mon Sep 24 18:18:25 2012
From: john.e.otten at gmail.com (John Otten)
Date: Mon, 24 Sep 2012 14:18:25 -0400
Subject: GPRS and PDP Context
In-Reply-To: <20120919154810.19091.qmail@stuge.se>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
Message-ID: <CAA__=E9uJoSxno+07QDvPLqPU3spP__R5FpyKZ_jqTQp8Z-JfQ@mail.gmail.com>

On Wed, Sep 19, 2012 at 11:48 AM, Peter Stuge <peter at stuge.se> wrote:

> ? wrote:
> > I have similar setup although in my case it doesn't work at all.
> ..
> > /etc/osmo_sgsn.cfg:
> ..
> > ns
> ..
> >  encapsulation udp local-ip 192.168.10.53
> >  encapsulation udp local-port 23000
>
> > /etc/openbsc.cfg:
> ..
> >  bts 0
> ..
> >   gprs nsvc 0 local udp port 23000
> >   gprs nsvc 0 remote udp port 23000
> >   gprs nsvc 0 remote ip 192.168.10.53
>
> I don't think both processes can use the same port; move one of them
> and configure the other accordingly.
>
>
> //Peter
>

Hmm...  They are both set to the same port in my openbsc.cfg (which appears
to be working).  The main GPRS page (
http://openbsc.osmocom.org/trac/wiki/OpenBSC_GPRS) has them both the same
when discussing the OpenBSC configuration. Should they be different? Could
my version be working because I have aliased some IP addresses on my system?

I don't want to modify a working configuration to find out, but if making
them different is a good plan, I would want to explore that option.

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120924/ec0f70ac/attachment.htm>

From peter at stuge.se  Mon Sep 24 19:23:31 2012
From: peter at stuge.se (Peter Stuge)
Date: Mon, 24 Sep 2012 21:23:31 +0200
Subject: GPRS and PDP Context
In-Reply-To: <CAA__=E9uJoSxno+07QDvPLqPU3spP__R5FpyKZ_jqTQp8Z-JfQ@mail.gmail.com>
References: <CAA__=E-wt2chCX=NNSgcRyqOwccv8P8KT=UG=ySGQQKP0RKmKQ@mail.gmail.com>
	<50598CFC.2000003@fairwaves.ru>
	<20120919154810.19091.qmail@stuge.se>
	<CAA__=E9uJoSxno+07QDvPLqPU3spP__R5FpyKZ_jqTQp8Z-JfQ@mail.gmail.com>
Message-ID: <20120924192331.21102.qmail@stuge.se>

John Otten wrote:
> > > /etc/osmo_sgsn.cfg:
> > >  encapsulation udp local-ip 192.168.10.53
> > >  encapsulation udp local-port 23000
> >
> > > /etc/openbsc.cfg:
> > >   gprs nsvc 0 local udp port 23000
> > >   gprs nsvc 0 remote udp port 23000
> > >   gprs nsvc 0 remote ip 192.168.10.53
> >
> > I don't think both processes can use the same port; move one of them
> > and configure the other accordingly.
> 
> Hmm...  They are both set to the same port in my openbsc.cfg

Connection tuples consist of IP address and port. I should perhaps
have written "the same IP and port" to be clear enough.


//Peter



From laforge at gnumonks.org  Tue Sep 18 17:49:25 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 18 Sep 2012 19:49:25 +0200
Subject: Sept 19, 8pm / Osmocom Berlin User Group meeting
Message-ID: <20120918174925.GL3968@prithivi.gnumonks.org>

Hi all!

This is the announcement for the next Osmocom Berlin meeting.

	Sept 19, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin

There is no formal presentation scheduled for this meeting.

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

Regards,
	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  Wed Sep 19 17:48:15 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 19 Sep 2012 19:48:15 +0200
Subject: Sept 19, 8pm / Osmocom Berlin User Group meeting
In-Reply-To: <20120918174925.GL3968@prithivi.gnumonks.org>
References: <20120918174925.GL3968@prithivi.gnumonks.org>
Message-ID: <20120919174815.GG1258@localhost>

On Tue, Sep 18, 2012 at 07:49:25PM +0200, Harald Welte wrote:
> Hi all!

Hi,

I am not going to make it today, I hope some other Osmocom/CCC
members will be present.

sorry





From holger at freyther.de  Thu Sep 20 06:19:31 2012
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 20 Sep 2012 08:19:31 +0200
Subject: Enabling keep-alive for sockets in libosmo-abis
Message-ID: <20120920061931.GJ25668@localhost>

Dear Pablo,


Daniel was adding keepalive support to the socket used to talk to
the bts. This was done in commit 8c2591d95e17eb6fa868e4d886a63ac62f3ca8af
of OpenBSC and somehow needs to find its way to master of OpenBSC or
libosmo-abis.

I think it belongs into libosmo-abis but I am not sure where exactly. Is
the keepalive setting something that belongs into the e1inp_line and
configuration? Do you have an idea where I should add it?

thanks
	holger



From pablo at gnumonks.org  Fri Sep 21 09:20:26 2012
From: pablo at gnumonks.org (Pablo Neira Ayuso)
Date: Fri, 21 Sep 2012 11:20:26 +0200
Subject: Enabling keep-alive for sockets in libosmo-abis
In-Reply-To: <20120920061931.GJ25668@localhost>
References: <20120920061931.GJ25668@localhost>
Message-ID: <20120921092026.GA20143@1984>

Hi Holger,

On Thu, Sep 20, 2012 at 08:19:31AM +0200, Holger Hans Peter Freyther wrote:
> Dear Pablo,
> 
> Daniel was adding keepalive support to the socket used to talk to
> the bts. This was done in commit 8c2591d95e17eb6fa868e4d886a63ac62f3ca8af
> of OpenBSC and somehow needs to find its way to master of OpenBSC or
> libosmo-abis.
> 
> I think it belongs into libosmo-abis but I am not sure where exactly. Is
> the keepalive setting something that belongs into the e1inp_line and
> configuration? Do you have an idea where I should add it?

I would add this to libosmocore, so we can reuse this code over and
over again no matter where.

Let me check this, I'll send you a patch for this.



From t-openbsc at tobias.org  Sun Sep 23 15:52:23 2012
From: t-openbsc at tobias.org (Tobias Engel)
Date: Sun, 23 Sep 2012 17:52:23 +0200
Subject: Help needed with CSD/V.110 decoding
Message-ID: <505F3037.5070103@tobias.org>

Hi,

I have been trying to implement some basic CSD functionality into
openbsc. V.110 transparent mode, to be specific, since this should be
the most simple to implement.

At first I tried with a nanobts, but that didn't seem to work at all.
Now I am using a bs-11.

The two phones I use establish a connection, but they cannot exchange
data and what I see on the Abis link also doesn't really make sense to
me. (Needless to say everything works as expected when using the same
phones on a production network.)

I attached a pcap of a CSD call I made via the bs-11. The second
attachment is the raw dump of the traffic frames I received from the
BS-11 for _one_ of the phones. (It looks pretty much the same for the
other phone.)

The first idle data frames received look ok:

00000000  00 00 c5 ff ff ff ff ff  fd ff ff ff ff ff ff ff
00000010  ff fd ff ff ff ff ff ff  ff ff fd ff ff ff ff ff
00000020  ff ff ff fd ff ff ff ff

C bits (Uplink data), D bits (all set to "1" == idle) and E bits (9.6
kbit/s) are all set as expected.

But after the synchronisation phase, things start to get strange. The
idle frames suddenly look like this:

00000460  00 00 8a ff ff fe fe fe  fa fe fe fe fe fe fe fe
00000470  fe fa ff fe fe fe fe fe  fe fe fa ff fe fe fe fe
00000480  fe fe fe fa ff fe fe fe

The BTS "forgets" to set the first bit of every octet to "1" on most
(but not all) octets. Also, the C bits now state that this is a
14.5kbit/s data frame. The E bits say the user rate now is 7.2 kbit/s.

There are only four frames with actual payload data in the dump. These
frames are at the positions I expect them to be (40600, 60520, 80440,
100400 - they were sent in intervals of 10 seconds). They look like this:

00009e90                           00 00 8a ff 2b a2 fa aa
00009ea0  fa 86 02 22 22 6e fe 1a  26 fa d7 4e d6 52 36 56
00009eb0  4e d6 fa 53 36 56 4e d6  52 36 56 fa 4f d6 52 36

What has been sent by the phone is an eight byte timestamp followed by
22 bytes of 0xaa. But I only get one data frame for each of these
transmissions (30 bytes of payload don't fit into one data frame), and
if I parse it as V.110 data, I get these 20 bytes:

00000000  15 7d 0d 10 d5 ff 33 fb  ae f5 ff ae ba ef fd ba
00000010  ef ae ba ff

So no 0xaa bytes there...


Does anybody have any idea what I might be doing wrong here?

Thanks,
-Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bs11-only-mtside-sends2.pcap
Type: application/octet-stream
Size: 8765 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120923/b46ebc0a/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bs11-only-mtside-sends2.bin
Type: application/macbinary
Size: 111880 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120923/b46ebc0a/attachment.bin>

From t-openbsc at tobias.org  Thu Sep 27 11:53:18 2012
From: t-openbsc at tobias.org (Tobias Engel)
Date: Thu, 27 Sep 2012 13:53:18 +0200
Subject: Help needed with CSD/V.110 decoding
In-Reply-To: <505F3037.5070103@tobias.org>
References: <505F3037.5070103@tobias.org>
Message-ID: <50643E2E.6040905@tobias.org>

On 23.09.12 17:52, Tobias Engel wrote:
> I have been trying to implement some basic CSD functionality into
> openbsc. V.110 transparent mode, to be specific, since this should be
> the most simple to implement.
> 
> At first I tried with a nanobts, but that didn't seem to work at all.
> Now I am using a bs-11.

As it turns out, neither the nanobts nor the bs-11 seem to support V.110
transparent mode.

The nanobts doesn't even get past the synchronisation phase in a CSD
call and the bs-11 garbles all data on the uplink (downlink works fine,
though o_O ).

One reason might be that V.110 transparent mode is only supported by
very few basebands (I only know of TI and Mediatek).

So unless somebody wants to donate an RLP implementation (for
non-transparent mode), I am going to do something else now ;)

-Tobias




From 246tnt at gmail.com  Thu Sep 27 15:30:04 2012
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 27 Sep 2012 11:30:04 -0400
Subject: Help needed with CSD/V.110 decoding
In-Reply-To: <50643E2E.6040905@tobias.org>
References: <505F3037.5070103@tobias.org>
	<50643E2E.6040905@tobias.org>
Message-ID: <CAHL+j0_nTJLdkYrMECV_2=zv6sQsXb0eTmMJbmaJri+L53pnew@mail.gmail.com>

> So unless somebody wants to donate an RLP implementation (for
> non-transparent mode), I am going to do something else now ;)

I had a quick look at RLP when I decoded the CSD captures I made on
GMR but it's only a hack and receive only. Might do a wireshark plugin
for it ...


Cheers,

    Sylvain



From taufiq.wahyudi.12 at gmail.com  Mon Sep 24 04:36:30 2012
From: taufiq.wahyudi.12 at gmail.com (TAUFIQ WAHYUDI)
Date: Sun, 23 Sep 2012 21:36:30 -0700
Subject: new comer
Message-ID: <CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g@mail.gmail.com>

hi all,

i am new comer in this group, i already have installed openbsc until to
this step, i have problems would you mind all giving me a hand in the
future?

thank you very much

Best Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120923/b3fbccbb/attachment.htm>

From peter at stuge.se  Mon Sep 24 07:21:35 2012
From: peter at stuge.se (Peter Stuge)
Date: Mon, 24 Sep 2012 09:21:35 +0200
Subject: new comer
In-Reply-To: <CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g@mail.gmail.com>
References: <CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g@mail.gmail.com>
Message-ID: <20120924072135.25899.qmail@stuge.se>

TAUFIQ WAHYUDI wrote:
> would you mind all giving me a hand in the future?

It will depend on what kind of questions you ask.

Read these two documents:

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
http://www.catb.org/esr/faqs/smart-questions.html


//Peter



From taufiq.wahyudi.12 at gmail.com  Tue Sep 25 13:05:04 2012
From: taufiq.wahyudi.12 at gmail.com (TAUFIQ WAHYUDI)
Date: Tue, 25 Sep 2012 06:05:04 -0700
Subject: OpenBSC Digest, Vol 45, Issue 15
In-Reply-To: <mailman.3.1348480803.9085.openbsc@lists.osmocom.org>
References: <mailman.3.1348480803.9085.openbsc@lists.osmocom.org>
Message-ID: <CACxKs1_G8phP6bpRY3bJ+BrTTo5Dq-zE=vos8qmfWaLHjSF=PQ@mail.gmail.com>

@peter

i have already installed libosmocore,libosmo-aabis,and openBsc,and
have been clone and integrated all the items into eclipse via egit.

i am a newbie in telco, does anyone in this forum know how to start up
openBSC ? i do want to know how does the Box work, and really confuse
how to start from.Would you guys send me a technical startup document
globally, so then i have an understanding regarding this stuff

Best Regards

On 9/24/12, openbsc-request at lists.osmocom.org
<openbsc-request at lists.osmocom.org> wrote:
> Send OpenBSC mailing list submissions to
> 	openbsc at lists.osmocom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.osmocom.org/mailman/listinfo/openbsc
> or, via email, send a message with subject or body 'help' to
> 	openbsc-request at lists.osmocom.org
>
> You can reach the person managing the list at
> 	openbsc-owner at lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBSC digest..."
>
>
> Today's Topics:
>
>    1. new comer (TAUFIQ WAHYUDI)
>    2. Re: new comer (Peter Stuge)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 23 Sep 2012 21:36:30 -0700
> From: TAUFIQ WAHYUDI <taufiq.wahyudi.12 at gmail.com>
> To: openbsc at lists.osmocom.org
> Subject: new comer
> Message-ID:
> 	<CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> hi all,
>
> i am new comer in this group, i already have installed openbsc until to
> this step, i have problems would you mind all giving me a hand in the
> future?
>
> thank you very much
>
> Best Regards
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.osmocom.org/pipermail/openbsc/attachments/20120923/b3fbccbb/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 24 Sep 2012 09:21:35 +0200
> From: Peter Stuge <peter at stuge.se>
> To: openbsc at lists.osmocom.org
> Subject: Re: new comer
> Message-ID: <20120924072135.25899.qmail at stuge.se>
> Content-Type: text/plain; charset=us-ascii
>
> TAUFIQ WAHYUDI wrote:
>> would you mind all giving me a hand in the future?
>
> It will depend on what kind of questions you ask.
>
> Read these two documents:
>
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
> http://www.catb.org/esr/faqs/smart-questions.html
>
>
> //Peter
>
>
>
> ------------------------------
>
> _______________________________________________
> OpenBSC mailing list
> OpenBSC at lists.osmocom.org
> https://lists.osmocom.org/mailman/listinfo/openbsc
>
>
> End of OpenBSC Digest, Vol 45, Issue 15
> ***************************************
>



From taufiq.wahyudi.12 at gmail.com  Tue Sep 25 13:05:49 2012
From: taufiq.wahyudi.12 at gmail.com (TAUFIQ WAHYUDI)
Date: Tue, 25 Sep 2012 06:05:49 -0700
Subject: OpenBSC Digest, Vol 45, Issue 15
In-Reply-To: <CACxKs1_G8phP6bpRY3bJ+BrTTo5Dq-zE=vos8qmfWaLHjSF=PQ@mail.gmail.com>
References: <mailman.3.1348480803.9085.openbsc@lists.osmocom.org>
	<CACxKs1_G8phP6bpRY3bJ+BrTTo5Dq-zE=vos8qmfWaLHjSF=PQ@mail.gmail.com>
Message-ID: <CACxKs1_3BW7CecBS6N6oA_hEkfhNmsjapj=gXHZuQT6a3qF8sg@mail.gmail.com>

@Peter

thank you for your help

Best Regards

On 9/25/12, TAUFIQ WAHYUDI <taufiq.wahyudi.12 at gmail.com> wrote:
> @peter
>
> i have already installed libosmocore,libosmo-aabis,and openBsc,and
> have been clone and integrated all the items into eclipse via egit.
>
> i am a newbie in telco, does anyone in this forum know how to start up
> openBSC ? i do want to know how does the Box work, and really confuse
> how to start from.Would you guys send me a technical startup document
> globally, so then i have an understanding regarding this stuff
>
> Best Regards
>
> On 9/24/12, openbsc-request at lists.osmocom.org
> <openbsc-request at lists.osmocom.org> wrote:
>> Send OpenBSC mailing list submissions to
>> 	openbsc at lists.osmocom.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://lists.osmocom.org/mailman/listinfo/openbsc
>> or, via email, send a message with subject or body 'help' to
>> 	openbsc-request at lists.osmocom.org
>>
>> You can reach the person managing the list at
>> 	openbsc-owner at lists.osmocom.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of OpenBSC digest..."
>>
>>
>> Today's Topics:
>>
>>    1. new comer (TAUFIQ WAHYUDI)
>>    2. Re: new comer (Peter Stuge)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sun, 23 Sep 2012 21:36:30 -0700
>> From: TAUFIQ WAHYUDI <taufiq.wahyudi.12 at gmail.com>
>> To: openbsc at lists.osmocom.org
>> Subject: new comer
>> Message-ID:
>> 	<CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> hi all,
>>
>> i am new comer in this group, i already have installed openbsc until to
>> this step, i have problems would you mind all giving me a hand in the
>> future?
>>
>> thank you very much
>>
>> Best Regards
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <http://lists.osmocom.org/pipermail/openbsc/attachments/20120923/b3fbccbb/attachment-0001.html>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 24 Sep 2012 09:21:35 +0200
>> From: Peter Stuge <peter at stuge.se>
>> To: openbsc at lists.osmocom.org
>> Subject: Re: new comer
>> Message-ID: <20120924072135.25899.qmail at stuge.se>
>> Content-Type: text/plain; charset=us-ascii
>>
>> TAUFIQ WAHYUDI wrote:
>>> would you mind all giving me a hand in the future?
>>
>> It will depend on what kind of questions you ask.
>>
>> Read these two documents:
>>
>> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
>> http://www.catb.org/esr/faqs/smart-questions.html
>>
>>
>> //Peter
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> OpenBSC mailing list
>> OpenBSC at lists.osmocom.org
>> https://lists.osmocom.org/mailman/listinfo/openbsc
>>
>>
>> End of OpenBSC Digest, Vol 45, Issue 15
>> ***************************************
>>
>



From mailman-bounces at lists.osmocom.org  Wed Sep 26 07:00:01 2012
From: mailman-bounces at lists.osmocom.org (mailman-bounces at lists.osmocom.org)
Date: Wed, 26 Sep 2012 09:00:01 +0200
Subject: OpenBSC unsubscribe notification
Message-ID: <mailman.1.1348642801.11293.openbsc@lists.osmocom.org>

akwonghk at gmail.com has been removed from OpenBSC.



From laforge at gnumonks.org  Sun Sep 30 15:27:35 2012
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 30 Sep 2012 17:27:35 +0200
Subject: BS-11 to sell
Message-ID: <20120930152735.GF5008@prithivi.gnumonks.org>

Hi!

In case anyone on this list is interested in owning a BS-11, I have
decided to sell off one more of the units that I still had here for my
personal use.

I'm also able to sell a compatible HFC-E1 or DAHDI/Digium card along
with it.

Price is up to negotiation.  I don't intend to give it away for free,
unless it is somebody with a known track record of osmocom.org
contributions.

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 mailman at lists.osmocom.org  Sun Sep 30 15:34:56 2012
From: mailman at lists.osmocom.org (mailman at lists.osmocom.org)
Date: Sun, 30 Sep 2012 17:34:56 +0200
Subject: Bounce action notification
Message-ID: <mailman.452.1349019296.1438.openbsc@lists.osmocom.org>

This is a Mailman mailing list bounce action notice:

    List:       OpenBSC
    Member:     jledet07 at student.aau.dk
    Action:     Subscription disabled.
    Reason:     Excessive or fatal bounces.
    


The triggering bounce notice is attached below.

Questions? Contact the Mailman site administrator at
mailman at lists.osmocom.org.
-------------- next part --------------
An embedded message was scrubbed...
From: <postmaster at ist.aau.dk>
Subject: Kan ikke leveres: BS-11 to sell
Date: Sun, 30 Sep 2012 17:34:49 +0200
Size: 11793
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120930/efa4ed36/attachment.eml>