Hi Harald (sorry for the typo).
I think that line 10 is a log of the USSD call I made.
My configuration is:
- Followed the tutorial. (
http://openbsc.osmocom.org/trac/wiki/network_from_scratch (using all
configurations shown in the tutoria, except the network name, that I
changed to DCG).
- Using a Ettus USRP N210
- All libraries installed in my notebook, with Ubuntu 13.04
kernel 3.8.0-29-generic.
- Starting osmo-nitb with the following command: osmo-nitb -c
~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -m -C
--debug=DRLL:DCC:DMM:DRR:DRSL:DNM
- I manually select the network in the Network Preferences. The phone is an
old Motorola Z6.
Hope it helps. If you need more information, just ask. If you need, I can
use other configurations or command options.
Best Regard,
On Sat, Aug 24, 2013 at 5:37 PM, Alexander Chemeris <
alexander.chemeris(a)gmail.com> wrote:
> Of-list: His name is "Harald", not "Herald" :)
>
> On Sun, Aug 25, 2013 at 12:36 AM, Alexander Chemeris
> <alexander.chemeris(a)gmail.com> wrote:
> > Maicon,
> >
> > Your log doesn't show any user activity, so you either (1) haven't
> > enabled enough logging or (2) your phone is not attached to the
> > OsmoNITB network.
> >
> > If you followed instructions from
> > http://openbsc.osmocom.org/trac/wiki/network_from_scratch, then you
> > should have enough logging enabled. In this case we have only option
> > (2) left and it would be great if you specify your software and
> > hardware setup and describe the procedure you're using to select the
> > network in your phone.
> >
> > On Sat, Aug 24, 2013 at 11:46 PM, Maicon Kist <maicon.kist(a)inf.ufrgs.br>
> wrote:
> >> Hi Herald,
> >>
> >> I'm trying to check the log messages. I'm trying to understand whats
> >> happening, but so far nothing came to my mind.
> >> I'm attaching the osmo-nitb log messages right before I call the *#100#
> >> number.
> >>
> >> Do you have any suggestion?
> >>
> >> PS: SMS and calls are working perfectly.
> >>
> >> Best Regards,
> >>
> >>
> >> On Sat, Aug 24, 2013 at 11:59 AM, Alexander Chemeris
> >> <alexander.chemeris(a)gmail.com> wrote:
> >>>
> >>> On Thu, Aug 22, 2013 at 9:40 PM, Maicon Kist <maicon.kist(a)inf.ufrgs.br
> >
> >>> wrote:
> >>> > Is there a tutorial in how to make a USSD application work in a
> OpenBSC
> >>> > network?
> >>> > Firstly I'm want to implement a simple "Hello World" application. eg.
> >>> > the
> >>> > client enter with a valid USSD number (*something) and the "Hello
> World"
> >>> > application executes.
> >>>
> >>> Look at the openbsc/src/libmsc/ussd.c file - it's very easy to extend
> >>> it to respond to various USSD requests. It would be great if we have a
> >>> kind of external API for implementing external USSD applications
> >>> without touching the OsmoNITB code. Patches for this are welcome.
> >>>
> >>> --
> >>> Regards,
> >>> Alexander Chemeris.
> >>> CEO, Fairwaves LLC / ООО УмРадио
> >>> http://fairwaves.ru
> >>
> >>
> >
> >
> >
> > --
> > Regards,
> > Alexander Chemeris.
> > CEO, Fairwaves LLC / ООО УмРадио
> > http://fairwaves.ru
>
>
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
>
hi,
after upgrading to latest openbsc/master, i experienced the following
problem with sgsn:
<0013> gprs_llc.c:506 LLC SAPI=1 C FCS=0x7b8d5fCMD=UI DATA
<0013> gprs_llc.c:142 TLLI 0x990ea532 is foreign, converting to local
TLLI 0xd90ea532
<0013> gprs_llc.c:789 LLC RX: unknown TLLI 0x990ea532, creating LLME on
the fly
<0013> gprs_llc.c:142 TLLI 0x990ea532 is foreign, converting to local
TLLI 0xd90ea532
<0013> gprs_llc.c:372 LLC TX: unknown TLLI 0x990ea532, creating LLME on
the fly
<0012> gprs_bssgp.c:503 BSSGP BVCI=0 TLLI=990ea532 Rx LLC DISCARDED
<0012> gprs_bssgp.c:376 BSSGP TLLI=0x990ea532 Rx UPLINK-UNITDATA
<0013> gprs_llc.c:506 LLC SAPI=1 C FCS=0x30b960CMD=UI DATA
<0013> gprs_llc.c:142 TLLI 0x990ea532 is foreign, converting to local
TLLI 0xd90ea532
<0013> gprs_llc.c:789 LLC RX: unknown TLLI 0x990ea532, creating LLME on
the fly
<0013> gprs_llc.c:142 TLLI 0x990ea532 is foreign, converting to local
TLLI 0xd90ea532
<0013> gprs_llc.c:372 LLC TX: unknown TLLI 0x990ea532, creating LLME on
the fly
<0012> gprs_bssgp.c:503 BSSGP BVCI=0 TLLI=990ea532 Rx LLC DISCARDED
<0012> gprs_bssgp.c:376 BSSGP TLLI=0x990ea532 Rx UPLINK-UNITDATA
<0013> gprs_llc.c:506 LLC SAPI=1 C FCS=0x280569CMD=UI DATA
<0013> gprs_llc.c:142 TLLI 0x990ea532 is foreign, converting to local
TLLI 0xd90ea532
<0013> gprs_llc.c:789 LLC RX: unknown TLLI 0x990ea532, creating LLME on
the fly
<0013> gprs_llc.c:142 TLLI 0x990ea532 is foreign, converting to local
TLLI 0xd90ea532
<0013> gprs_llc.c:372 LLC TX: unknown TLLI 0x990ea532, creating LLME on
the fly
<0012> gprs_bssgp.c:503 BSSGP BVCI=0 TLLI=990ea532 Rx LLC DISCARDED
the auth-policy is configured to "accept-all". any idea how to do deeper
debugging?
regards,
andreass
Hi,
While I was playing around with openbsc project I noticed that the
libosmo-sccp libraries are built as a static libraries only and I decided that
it will be useful to build them as shared objects too.
I also enabled colored output of the test suite and ignore all tag files that
are generated by the Makefiles.
Cheers
Vasil Velichckov (3):
Build shared objects with libtool
Enable colored test results by default
Ignore the tag files that are generated by Makefile
.gitignore | 9 +++++++++
configure.ac | 2 +-
src/Makefile.am | 18 +++++++++++++-----
tests/m2ua/Makefile.am | 2 +-
tests/sccp/Makefile.am | 4 ++--
tests/testsuite.at | 1 +
6 files changed, 27 insertions(+), 9 deletions(-)
--
1.7.10.4