OpenBSC May 2010

openbsc@lists.osmocom.org

15 participants
27 discussions

information about Telnet interface
by AHMET GÜLTEKİN 17 May '10

17 May '10

Hi, Can anyone give me information about how i can connect and use telnet interface. I tried by typing " telnet IP 4242" on command line of a PC which was running bsc-hack program but i couldn't succeed. I want to send SMS and use silent call property by using telnet. Please help me. Ahmet.

3 2

gssm running problem
by zero cool 13 May '10

13 May '10

Hi all, once I ran the command ./gssm_usrp.py, I got following error: zero@zero-laptop:~/airprobe/gssm/src/python$ ./gssm_usrp.py Traceback (most recent call last): File "./gssm_usrp.py", line 5, in <module> from gnuradio import gr, usrp, db_dbs_rx, blks2 ImportError: cannot import name db_dbs_rx I searched over internet and found somewhere that Josh and Eric has mentioned that this version of gssm will not work with gnuradio 3.2, it will work with 3.1, is there any other way to run this program on gnuradio-3.2.2. kindly reply me please my configuration: I am using karmic, gnuradio3.2 with modified external 52MHz clock, please help me to get out from this problem On Thu, May 13, 2010 at 3:30 PM, <openbsc-request(a)lists.gnumonks.org> wrote: > Send OpenBSC mailing list submissions to > openbsc(a)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(a)lists.gnumonks.org > > You can reach the person managing the list at > openbsc-owner(a)lists.gnumonks.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenBSC digest..." > > > Today's Topics: > > 1. Re: User location openbsc (Harald Welte) > 2. ipaccess-config changes in master (Holger Freyther) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 12 May 2010 12:52:59 +0200 > From: Harald Welte <laforge(a)gnumonks.org> > Subject: Re: User location openbsc > To: Fabrice Ismael Poundeu Tchouatieu > <fabrice.poundeu(a)smail.inf.fh-bonn-rhein-sieg.de> > Cc: openbsc(a)lists.gnumonks.org > Message-ID: <20100512105259.GP10052(a)prithivi.gnumonks.org> > Content-Type: text/plain; charset=us-ascii > > On Wed, May 12, 2010 at 11:14:27AM +0200, Fabrice Ismael Poundeu Tchouatieu > wrote: > > Hello Harald, > > can you please explain me how the subscriber location actually work > > in openbsc. i have seen that you also have a VLR implemented. How > > does this work? I actually just test the registration and calls in > > roaming mode. To which part of the Openbsc implementation > > (program-code) should i refer to for this (subscriber location > > implementation)? > > We don't really have/use any VLR. All we have is a subscriber table, > and each subscriber can have a completely different MCC/MNC as part of > his IMSI - we simply don't care. There is no distinction between > roaming and home network subscribers at all. > > All we care about is if the subscriber.authorized field is 0 or 1 in > the sql database. > > Regarding 'subscriber location' between multiple BTS: We simply store > the LAC of where the subscriber was last seen. > > -- > - Harald Welte <laforge(a)gnumonks.org> > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) > > > > ------------------------------ > > Message: 2 > Date: Thu, 13 May 2010 01:00:21 +0800 > From: Holger Freyther <zecke(a)selfish.org> > Subject: ipaccess-config changes in master > To: openbsc(a)lists.gnumonks.org > Message-ID: <4BEADEA5.6050307(a)selfish.org> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > > I have done various changes to the ipaccess-config application to work > with a multi-trx setup. I think I have tested everything on both > single-trx and multi-trx setup. If something with ipaccess-config does > not work anymore please shout and I will have a look. > > z. > > > > > ------------------------------ > > _______________________________________________ > OpenBSC mailing list > OpenBSC(a)lists.gnumonks.org > https://lists.gnumonks.org/mailman/listinfo/openbsc > > > End of OpenBSC Digest, Vol 17, Issue 7 > ************************************** > -- Thanks.....

1 0

ipaccess-config changes in master
by Holger Freyther 12 May '10

12 May '10

Hi all, I have done various changes to the ipaccess-config application to work with a multi-trx setup. I think I have tested everything on both single-trx and multi-trx setup. If something with ipaccess-config does not work anymore please shout and I will have a look. z.

1 0

network originated handover
by Open Bsc 12 May '10

12 May '10

Hi, Does anyone know how to create a network originated handover for a selected subscriber on an Ericsson network? Thanks for your answers.. Alper

3 3

OpenGGSN git repository with fixes
by Harald Welte 04 May '10

04 May '10

Hi! I've created a git repository for OpenGGSN, and imported the apparently abandoned openggsn code using git cvsimport. You can clone the repo via "git clone git://openbsc.gnumonks.org/openggsn.git Please note: This is not meant as an attempt to fork or openggsn. I just wanted to add all the fixed that had been contributed to the sourceforge bug tracker to the latest released openggsn code (including a DoS fix from 6 years ago)... so I might as well make this available to others. I'm still hoping to get in touch with the original author and see what we can do to bring those fixes back into mainline and help openggsn's future. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

OpenBSC gprs-sgsn branch merged into master !
by Harald Welte 04 May '10

04 May '10

Hi all! Since the SGSN was now built as a separate program, the modifications to OpenBSC specific files are none, and the modifications to some shared files were minimal (e.g. adding a new debug category). Thus, I have decided it is no longer useful to keep the gprs-sgsn branch as a separate branch. The GPRS code can now be found in the master branch. Also, all gprs related code is moved to src/gprs to make the distinction more clear. I don't expect any of my upcomign work on the GPRS side to touch the regular BSC codebase in src/ The ipaccess-* executables are now also built in src/ipaccess and I think we should gradually give the code more structure. Too many source file in one directory make things complicated and make it too easy to have strange dependencies. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

GPRS SGSN status update
by Harald Welte 03 May '10

03 May '10

Hi! The gprs-sgsn branch has seen quite a number of changes during the last week, most of them are related to the gb-proxy that I'm currently implementing. The Gb-proxy can multiplex several Gb connections (each to one BTS) and present them as one NS-VC with many BSSGP-VC (one for each BTS) to the SGSN. The proxy is not needed for most users OpenBSC operation. However, I have now also adapted the SGSN support inside OpenBSC to the modified NS and BSSGP code for the proxy. Furthermore, I've fixed many of its limitations and it should now be fairly generic, working with multiple BTSs, etc. Also, the SGSN is now a standalone program called osmo_sgsn. A lot of the legacy cruft has been eliminated, i.e. the SGSN code does no longer need the gsm_network/bts/trx/... data structures that are not applicable to the GPRS network model anyway. As a result, GPRS ATTACH and RA UPDATE are working again, like they did months ago. I'm now still stuck somewhere in PDP context activation, and am confident that this will be solved tomorrow. After that point, the actual data plane can be worked on, i.e. flow control and fragmentation, as well as somehow actually routing IP packets into the LLC connection. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC May 2010