Relation between IMSI and TMSI

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

zero cool smzerocool at gmail.com
Mon Nov 15 08:09:37 UTC 2010


Dear community members,
as we all know that TMSI is alotted by bsc, can anybody explain how this
happens and what kind of algorithm they (professional network) use. Can I
extract IMSI from TMSI??
Please answer !!!!

On Mon, Nov 15, 2010 at 2:05 AM, <openbsc-request at lists.gnumonks.org> wrote:

> Send OpenBSC mailing list submissions to
>        openbsc at lists.gnumonks.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.gnumonks.org/mailman/listinfo/openbsc
> or, via email, send a message with subject or body 'help' to
>        openbsc-request at lists.gnumonks.org
>
> You can reach the person managing the list at
>        openbsc-owner at lists.gnumonks.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBSC digest..."
>
>
> Today's Topics:
>
>   1. libosmocore compile error (Stuart Baggs)
>   2. Re: libosmocore compile error (Sylvain Munaut)
>   3. Re: libosmocore compile error (Stuart Baggs)
>   4. Re: libosmocore compile error (Holger Hans Peter Freyther)
>   5. Re: libosmocore compile error (Stuart Baggs)
>   6. Re: libosmocore compile error (Holger Hans Peter Freyther)
>   7. Re: libosmocore compile error (Holger Hans Peter Freyther)
>   8. bsc_hack dies (Stuart Baggs)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 14 Nov 2010 17:48:09 +0000
> From: Stuart Baggs <stuart at bluewave.im>
> Subject: libosmocore compile error
> To: OpenBSC list <openbsc at lists.gnumonks.org>
> Message-ID: <507B2AE3-06E7-4486-9AE0-F0965C15FF10 at bluewave.im>
> Content-Type: text/plain; charset=us-ascii
>
> Hi, I am trying to get a working GPRS branch up and running. I have done a
> fresh git clone of both libosmocore and openbsc master branches. Both
> compile without issue. When I try and run bsc_hack from /opt/openbsc/ I get
> this error:
>
> ./bsc_hack: error while loading shared libraries: libosmovty.so.0: cannot
> open shared object file: No such file or directory
>
> Any ideas what has gone wrong with this install? Obviously openbsc cannot
> find libosmocore libraries, but I have compiled them cas per usual. Any
> ideas?
>
> Thanks
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 14 Nov 2010 19:00:50 +0100
> From: Sylvain Munaut <246tnt at gmail.com>
> Subject: Re: libosmocore compile error
> To: Stuart Baggs <stuart at bluewave.im>
> Cc: OpenBSC list <openbsc at lists.gnumonks.org>
> Message-ID:
>        <AANLkTi=_yru5SiOApB6dQ7XAk_FgMzUymTW-CN+XLU=x at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
>
> > ./bsc_hack: error while loading shared libraries: libosmovty.so.0: cannot
> open shared object file: No such file or directory
> >
> > Any ideas what has gone wrong with this install? Obviously openbsc cannot
> find libosmocore libraries, but I have compiled them cas per usual. Any
> ideas?
>
> Well yeah ...
>
> When you install libraried in non-standard location you must tell the
> ld loader where to look
>
> Either using LD_LIBRARY_PATH en variable or /etc/ld.so.conf
>
> Cheers,
>
>    Sylvain
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 14 Nov 2010 18:49:12 +0000
> From: Stuart Baggs <stuart at bluewave.im>
> Subject: Re: libosmocore compile error
> To: Sylvain Munaut <246tnt at gmail.com>
> Cc: OpenBSC list <openbsc at lists.gnumonks.org>
> Message-ID: <2A79A19C-6D6F-4E19-B9ED-9894421F8F10 at bluewave.im>
> Content-Type: text/plain; charset=us-ascii
>
> Thanks, I though it was in the standard location. I have another issue now.
> I have installed libosmocore 0.1.27 and the latest clone of openbsc master
> branch but when compiling open_bsc I am getting:
>
> No package 'libosmo-sccp' found
>
> I though this was part of libosmocore? I have managed to get a git clone of
> libosmo-sccp but a ./configure comes up with:
>
> configure: error: cannot find install-sh, install.sh, or shtool in "."
> "./.." "./../.."
>
> I'm keen to get the GPRS branch up and running so I can start testing.
>
> On 14 Nov 2010, at 18:00, Sylvain Munaut wrote:
>
> > Hi,
> >
> >
> >> ./bsc_hack: error while loading shared libraries: libosmovty.so.0:
> cannot open shared object file: No such file or directory
> >>
> >> Any ideas what has gone wrong with this install? Obviously openbsc
> cannot find libosmocore libraries, but I have compiled them cas per usual.
> Any ideas?
> >
> > Well yeah ...
> >
> > When you install libraried in non-standard location you must tell the
> > ld loader where to look
> >
> > Either using LD_LIBRARY_PATH en variable or /etc/ld.so.conf
> >
> > Cheers,
> >
> >    Sylvain
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 14 Nov 2010 19:51:37 +0100
> From: Holger Hans Peter Freyther <holger at freyther.de>
> Subject: Re: libosmocore compile error
> To: openbsc at lists.gnumonks.org
> Message-ID: <4CE02FB9.2060909 at freyther.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 11/14/2010 07:49 PM, Stuart Baggs wrote:
>
> > configure: error: cannot find install-sh, install.sh, or shtool in "."
> "./.." "./../.."
>
> autoreconf --install --force..
>
>
>
> >
> > I'm keen to get the GPRS branch up and running so I can start testing.
>
> You don't need to pass the enable option for the BSC... normal OpenBSC does
> not require SCCP.
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 14 Nov 2010 18:59:29 +0000
> From: Stuart Baggs <stuart at bluewave.im>
> Subject: Re: libosmocore compile error
> To: Holger Hans Peter Freyther <holger at freyther.de>
> Cc: openbsc at lists.gnumonks.org
> Message-ID: <5ABF6A6C-7A7B-40C9-B079-2CB06D0C9520 at bluewave.im>
> Content-Type: text/plain; charset=us-ascii
>
> Thanks for your help. This is getting really frustrating now. I have tried
> to recompile openbsc with:
>
> autoreconf --install --force
> ./configure
>
> but the process stops on ./configure with:
>
> checking for LIBOSMOSCCP... configure: error: Package requirements
> (libosmo-sccp >= 0.0.3) were not met:
>
> No package 'libosmo-sccp' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables LIBOSMOSCCP_CFLAGS
> and LIBOSMOSCCP_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> I'm probably being really stupid, but it's been a long day. Any pointers?
>
> Thanks guys.
>
> s
>
> On 14 Nov 2010, at 18:51, Holger Hans Peter Freyther wrote:
>
> > On 11/14/2010 07:49 PM, Stuart Baggs wrote:
> >
> >> configure: error: cannot find install-sh, install.sh, or shtool in "."
> "./.." "./../.."
> >
> > autoreconf --install --force..
> >
> >
> >
> >>
> >> I'm keen to get the GPRS branch up and running so I can start testing.
> >
> > You don't need to pass the enable option for the BSC... normal OpenBSC
> does
> > not require SCCP.
> >
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sun, 14 Nov 2010 20:04:10 +0100
> From: Holger Hans Peter Freyther <holger at freyther.de>
> Subject: Re: libosmocore compile error
> To: openbsc at lists.gnumonks.org
> Message-ID: <4CE032AA.2060601 at freyther.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 11/14/2010 07:59 PM, Stuart Baggs wrote:
> > Thanks for your help. This is getting really frustrating now. I have
> tried to recompile openbsc with:
> >
> > autoreconf --install --force
> > ./configure
> >
> > but the process stops on ./configure with:
> >
> > checking for LIBOSMOSCCP... configure: error: Package requirements
> (libosmo-sccp >= 0.0.3) were not met:
> >
> > No package 'libosmo-sccp' found
> >
> > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > installed software in a non-standard prefix.
> >
> > Alternatively, you may set the environment variables LIBOSMOSCCP_CFLAGS
> > and LIBOSMOSCCP_LIBS to avoid the need to call pkg-config.
> > See the pkg-config man page for more details.
> >
> > I'm probably being really stupid, but it's been a long day. Any pointers?
>
> ....
>
>
> 1.) the autoreconf --install --force was below your quote of attempting to
> build libosmo-sccp. So it was related to libosmo-sccp. :)
>
> 2.) You have not invoked './configure', you have either invoked
> './configure
> --enable-nat' or './configure --enable-osmo-bsc' (or both). For a normal
> build
> libosmosccp is not required.
>
> To illustrate I have put the relevant part from configure.in here. So only
> if
> you have used any of the two options you will need libosmo-sccp. If you
> don't
> have libosmosccp... then don't specify the two options.
>
> I hope this helps
>
>
>
>
> AC_ARG_ENABLE([nat], [AS_HELP_STRING([--enable-nat], [Build the BSC NAT.
> Requires SCCP])],
>    [
>        PKG_CHECK_MODULES(LIBOSMOSCCP, libosmo-sccp >= 0.0.2)
>        osmo_ac_build_nat="yes"
>    ],
>    [
>        osmo_ac_build_nat="no"
>    ])
> AM_CONDITIONAL(BUILD_NAT, test "x$osmo_ac_build_nat" = "xyes")
>
> AC_ARG_ENABLE([osmo-bsc], [AS_HELP_STRING([--enable-osmo-bsc], [Build the
> Osmo
> BSC])],
>    [
>        PKG_CHECK_MODULES(LIBOSMOSCCP, libosmo-sccp >= 0.0.2)
>        osmo_ac_build_bsc="yes"
>    ],
>    [
>        osmo_ac_build_bsc="no"
>    ])
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 14 Nov 2010 21:24:09 +0100
> From: Holger Hans Peter Freyther <holger at freyther.de>
> Subject: Re: libosmocore compile error
> To: openbsc at lists.gnumonks.org
> Message-ID: <4CE04569.8070701 at freyther.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 11/14/2010 09:13 PM, Stuart Baggs wrote:
> > All compiled and installed. I'm running OpenBSC 0.3.99.20onwaves. Is this
> compatible with GPRS? I have compiled OpenGGSN and recompiled openbsc but I
> dont seem to be getting an osmo-sgsn binary created.
>
> osmo-sgsn is only in master. You will need to get osmo-sgsn from the master
> branch, bsc_msc_ip is only in the branch and will stay there.
>
>
>
> ------------------------------
>
> Message: 8
> Date: Sun, 14 Nov 2010 20:35:33 +0000
> From: Stuart Baggs <stuart at bluewave.im>
> Subject: bsc_hack dies
> To: OpenBSC list <openbsc at lists.gnumonks.org>
> Message-ID: <CF05E7EF-E369-4694-905E-D1DF7D0E203C at bluewave.im>
> Content-Type: text/plain; charset=us-ascii
>
> After 30 seconds my bsc_hack is dieing. Here is the error:
>
> root at gateway:~/openbsc/openbsc# /usr/local/sbin/bsc_hack -c
> /home/stuart/openbsc.cfg -P
> DB: Database initialized.
> DB: Database prepared.
> <000d> input/ipaccess.c:634 accept()ed new OML link from 192.168.1.51
> <0005> bsc_init.c:745 bootstrapping OML for BTS 0
> SET ATTR NACK  CAUSE=Message cannot be performed
> <000d> input/ipaccess.c:696 accept()ed new RSL link from 192.168.1.51
> <0004> bsc_init.c:941 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 870
> using MCC=234 MNC=18 LAC=1 CID=0 BSIC=63 TSC=7
> <0000> chan_alloc.c:441 (bts=0,trx=0,ts=0,ss=0) Recycling Channel.
> <0004> abis_rsl.c:588 (bts=0,trx=0,ts=0,ss=1) is back in operation.
> *** stack smashing detected ***: /usr/local/sbin/bsc_hack terminated
> ======= Backtrace: =========
> /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0x2eaed8]
> /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0x2eae90]
> /usr/local/sbin/bsc_hack[0x8060f43]
> /usr/local/sbin/bsc_hack[0x805cca0]
> /usr/local/sbin/bsc_hack[0x80663d9]
> /usr/local/sbin/bsc_hack[0x80752a2]
> /usr/local/lib/libosmocore.so.0(bsc_select_main+0x14b)[0x88e51b]
> /usr/local/sbin/bsc_hack[0x804c0a6]
> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x220b56]
> /usr/local/sbin/bsc_hack[0x804bbb1]
> ======= Memory map: ========
> 00110000-00111000 r-xp 00000000 00:00 0          [vdso]
> 0020a000-00348000 r-xp 00000000 fc:00 171        /lib/tls/i686/cmov/
> libc-2.10.1.so
> 00348000-00349000 ---p 0013e000 fc:00 171        /lib/tls/i686/cmov/
> libc-2.10.1.so
> 00349000-0034b000 r--p 0013e000 fc:00 171        /lib/tls/i686/cmov/
> libc-2.10.1.so
> 0034b000-0034c000 rw-p 00140000 fc:00 171        /lib/tls/i686/cmov/
> libc-2.10.1.so
> 0034c000-0034f000 rw-p 00000000 00:00 0
> 003c0000-003dc000 r-xp 00000000 fc:00 300        /lib/libgcc_s.so.1
> 003dc000-003dd000 r--p 0001b000 fc:00 300        /lib/libgcc_s.so.1
> 003dd000-003de000 rw-p 0001c000 fc:00 300        /lib/libgcc_s.so.1
> 00443000-0045e000 r-xp 00000000 fc:00 143        /lib/ld-2.10.1.so
> 0045e000-0045f000 r--p 0001a000 fc:00 143        /lib/ld-2.10.1.so
> 0045f000-00460000 rw-p 0001b000 fc:00 143        /lib/ld-2.10.1.so
> 004ba000-004c5000 r-xp 00000000 fc:00 151866     /usr/lib/libdbi.so.0.0.5
> 004c5000-004c6000 rw-p 0000a000 fc:00 151866     /usr/lib/libdbi.so.0.0.5
> 00569000-0056b000 r-xp 00000000 fc:00 177        /lib/tls/i686/cmov/
> libdl-2.10.1.so
> 0056b000-0056c000 r--p 00001000 fc:00 177        /lib/tls/i686/cmov/
> libdl-2.10.1.so
> 0056c000-0056d000 rw-p 00002000 fc:00 177        /lib/tls/i686/cmov/
> libdl-2.10.1.so
> 005cf000-005f3000 r-xp 00000000 fc:00 179        /lib/tls/i686/cmov/
> libm-2.10.1.so
> 005f3000-005f4000 r--p 00023000 fc:00 179        /lib/tls/i686/cmov/
> libm-2.10.1.so
> 005f4000-005f5000 rw-p 00024000 fc:00 179        /lib/tls/i686/cmov/
> libm-2.10.1.so
> 006c8000-006dd000 r-xp 00000000 fc:00 235        /lib/tls/i686/cmov/
> libpthread-2.10.1.so
> 006dd000-006de000 r--p 00014000 fc:00 235        /lib/tls/i686/cmov/
> libpthread-2.10.1.so
> 006de000-006df000 rw-p 00015000 fc:00 235        /lib/tls/i686/cmov/
> libpthread-2.10.1.so
> 006df000-006e1000 rw-p 00000000 00:00 0
> 00764000-007ea000 r-xp 00000000 fc:00 135483
> /usr/lib/libsqlite3.so.0.8.6
> 007ea000-007eb000 r--p 00086000 fc:00 135483
> /usr/lib/libsqlite3.so.0.8.6
> 007eb000-007ec000 rw-p 00087000 fc:00 135483
> /usr/lib/libsqlite3.so.0.8.6
> 00889000-008a2000 r-xp 00000000 fc:00 1806
> /usr/local/lib/libosmocore.so.0.0.0
> 008a2000-008a3000 r--p 00018000 fc:00 1806
> /usr/local/lib/libosmocore.so.0.0.0
> 008a3000-008a4000 rw-p 00019000 fc:00 1806
> /usr/local/lib/libosmocore.so.0.0.0
> 008a4000-008a5000 rw-p 00000000 00:00 0
> 00abe000-00ac7000 r-xp 00000000 fc:00 175        /lib/tls/i686/cmov/
> libcrypt-2.10.1.so
> 00ac7000-00ac8000 r--p 00008000 fc:00 175        /lib/tls/i686/cmov/
> libcrypt-2.10.1.so
> 00ac8000-00ac9000 rw-p 00009000 fc:00 175        /lib/tls/i686/cmov/
> libcrypt-2.10.1.so
> 00ac9000-00af0000 rw-p 00000000 00:00 0
> 00bca000-00bcf000 r-xp 00000000 fc:00 151877
> /usr/lib/dbd/libdbdsqlite3.so
> 00bcf000-00bd0000 r--p 00004000 fc:00 151877
> /usr/lib/dbd/libdbdsqlite3.so
> 00bd0000-00bd1000 rw-p 00005000 fc:00 151877
> /usr/lib/dbd/libdbdsqlite3.so
> 08048000-08091000 r-xp 00000000 fc:00 154760     /usr/local/sbin/bsc_hack
> 08091000-08092000 r--p 00048000 fc:00 154760     /usr/local/sbin/bsc_hack
> 08092000-08097000 rw-p 00049000 fc:00 154760     /usr/local/sbin/bsc_hack
> 08097000-0809b000 rw-p 00000000 00:00 0
> 0919b000-09228000 rw-p 00000000 00:00 0          [heap]
> b6ffe000-b6fff000 ---p 00000000 00:00 0
> b6fff000-b7802000 rw-p 00000000 00:00 0
> b7806000-b7808000 rw-p 00000000 00:00 0
> bfa5e000-bfa73000 rw-p 00000000 00:00 0          [stack]
> signal 6 received
> talloc report on 'vty' (total  37965 bytes in 3350 blocks)
>    save_cwd                       contains     29 bytes in   1 blocks (ref
> 0) 0x91bb478
>    vty_command                    contains  21352 bytes in 1719 blocks (ref
> 0) 0x91bb440
>    vty_vector                     contains  16584 bytes in 1629 blocks (ref
> 0) 0x91bb408
> full talloc report on 'openbsc' (total 137666 bytes in  63 blocks)
>    struct e1inp_line              contains  45208 bytes in   1 blocks (ref
> 0) 0x9207170
>    struct ia_e1_handle            contains     60 bytes in   1 blocks (ref
> 0) 0x91f1500
>    telnet_connection              contains      1 bytes in   1 blocks (ref
> 0) 0x91a18a0
>    struct gsm_network             contains  89224 bytes in   6 blocks (ref
> 0) 0x91a16e0
>        struct gsm_bts                 contains  88804 bytes in   2 blocks
> (ref 0) 0x91f1620
>            struct gsm_bts_trx             contains  86188 bytes in   1
> blocks (ref 0) 0x91f2090
>        BlueWave                       contains      9 bytes in   1 blocks
> (ref 0) 0x919f018
>        BlueWave                       contains      9 bytes in   1 blocks
> (ref 0) 0x91a3490
>        127.0.0.1                      contains     10 bytes in   1 blocks
> (ref 0) 0x91a2038
>    counter                        contains    580 bytes in  30 blocks (ref
> 0) 0x919b568
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3448
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3400
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a33b8
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3370
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3328
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a32e0
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3298
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3250
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3208
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a31c0
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a3178
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919d958
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919d910
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919d8c8
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919d880
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919d838
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919ea18
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919e9d0
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919e988
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919e940
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919e8f8
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919efd0
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919ef88
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919ef40
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919eef8
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919f0d0
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x919f088
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a2078
>        struct counter                 contains     20 bytes in   1 blocks
> (ref 0) 0x91a25b0
>    trau_upq_entry                 contains      0 bytes in   1 blocks (ref
> 0) 0x919b530
>    trau_map_entry                 contains      0 bytes in   1 blocks (ref
> 0) 0x919b4f8
>    transaction                    contains      0 bytes in   1 blocks (ref
> 0) 0x919b4c0
>    subch_txq_entry                contains      0 bytes in   1 blocks (ref
> 0) 0x919b488
>    signal_handler                 contains    140 bytes in   8 blocks (ref
> 0) 0x919b450
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x91f13e8
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x91eb2b8
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x919b6c0
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x919b678
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x919b630
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x919b5e8
>        struct signal_handler          contains     20 bytes in   1 blocks
> (ref 0) 0x919b5a0
>    paging_request                 contains      0 bytes in   1 blocks (ref
> 0) 0x919b418
>    gsm_call                       contains      0 bytes in   1 blocks (ref
> 0) 0x919b3e0
>    subscr_request                 contains      0 bytes in   1 blocks (ref
> 0) 0x919b3a8
>    subscriber                     contains    392 bytes in   2 blocks (ref
> 0) 0x919b370
>        struct gsm_subscriber          contains    392 bytes in   1 blocks
> (ref 0) 0x9212ce0
>    sms                            contains      0 bytes in   1 blocks (ref
> 0) 0x919b338
>    loc_updating_oper              contains      0 bytes in   1 blocks (ref
> 0) 0x919b300
>    bs11_file_list_entry           contains      0 bytes in   1 blocks (ref
> 0) 0x919b2c8
>    msgb                           contains   2060 bytes in   3 blocks (ref
> 0) 0x919b290
>        GSM 04.08                      contains   1092 bytes in   1 blocks
> (ref 0) 0x9213360
>        Abis/IP                        contains    968 bytes in   1 blocks
> (ref 0) 0x91f0f20
> Aborted
>
>
> Any ideas?
>
>
> ------------------------------
>
> _______________________________________________
> OpenBSC mailing list
> OpenBSC at lists.gnumonks.org
> https://lists.gnumonks.org/mailman/listinfo/openbsc
>
>
> End of OpenBSC Digest, Vol 23, Issue 7
> **************************************
>



-- 
Thanks.....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20101115/737b4239/attachment.htm>


More information about the OpenBSC mailing list