So far three persons have indicated their interest to join
a meeting at my place.
Considering the time it takes to drive to my place, it
probably makes sense to have the meeting at the weekend
(either Saturday or Sunday) so that there is more time
for the meeting itself. I can suggest one of the following
dates for the first meeting, somewhere between 10:00 to
18:00 on each day:
25.8. (Sa) or 26.8. (Su)
1.9. (Sa) or 2.9. (Su)
8.9. (Sa) or 9.9. (Su)
So please let me know when you have time and also make
suggestions in which Osmocom topic you are interested
in so that we can have some sort of agenda for the
meeting to make best use of the time.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello everyone,
I've just finnished writing together a small web interface for the OpenBSC
HLR. It allows you to modify various parameters in the database and also
provides a set of functions to modify the HLR or sending SMSes in your own
scripts.
The project is still very alpha but it seems to work reasonably good. Feel
free to give any feedback!
Screenshots and source code is available on my website:
https://stormhub.org/simplehlr/
--
*Best regards,
Peter Caprioli*
Hello list,
First of all congratulation to developers of this project making such
wonderful project in an interesting subject. I am new to this project and
for past few days i managed to go through the documentation and get most of
it tested. Thanks for pretty good documentation in most of the areas as
well.
I have the osmo-nitb working very fine using a nano bts.
How ever when i try to install it with LCR to interconnect with external
switch, im facing some problems. Initially i thought i must use
LCR+Asterisk. But later i figured out there is a built in SIP interface on
LCR which there is no need to asterisk or chan_asterisk. I would prefer to
use this LCR SIP interface as i dont want to use asterisk and just want to
forward all calls to another SIP switch.
Now in this context there seems absolutely no documentation on both openbsc
and LCR/mISDN lists.
Can some one please shed me some light here on how to build a LCR with SIP
to be work with osmo-nitb.
All i want to test is
GSM phone > Osmo-nitb > LCR with SIP > SIP softswitch
Thank you very much for every one's effort in this project and would be
glad to see some response for this.
Best Regards
Nava.
I have some questions:
1) When I start bsc_hack bsc_init.c first establishes OML link and
initializes the bts then it establishes RSL link and bts starts
broadcasting. However, it takes so much time to start the bts. Instead of
this I want to do the following: it establishes OML link at the beginning
and only once, then when i want to start broadcasting it establishes just
the RSL link and bts will start faster since i don't have to wait for OML
link. What should be done for this?
2) If i send one or two word messages from telnet interface it is okay. But
if i send a longer message the phone could't receive the end of the message
correctly(last words may be incomplete). Did any one encounter with this
problem? What is wrong with me?
3) Could I send SMS in which extension of the sender is text not integer.
For example, i want to send an information SMS that this is a test network.
For this purpose i want to send an SMS from 'OpenBSC'. I set the extension
of the first subscriber in database as text and tried to send the SMS but
SMS wasn't delivered. What should i do?
4) Can i add SMS externally to SMS table of database?
Thanks.
Jason
Hi Andreas, Harald,
the recent "SI generation" fix broke multi trx setups. This is because
when the first (c0) TRX is going up bts->si_valid will include SI2 and
other SIs scheduled on the BCCH and once the second trx is going up the
code decides it only needs to generate the SI5 (and more).
But si_valid still includes SI2 and it will be set on the second trx. I
have fixed it locally by setting si_valid to 0 early in the set_system_infos
routine and added a warning for this case.
How should this be properly fixed for master? Will the content of a specific
SI differ from TRX0 to TRX1 of a BTS? Should the si_valid be moved to the
trx data structure?
I have attached my local patch and would like to have a review for it.
comments? ideas?
holger
Hi,
as indicated in the previous mail there are some things to be done
before we get to the venue. I would like to experiment with sprints
to solve some of the stability issues we had with osmo-nitb.
The idea is that we assemble (physically or online) and work on some
specific issues of osmo-nitb that impact the quality of service for
the upcoming event. I can provide food and snacks during these sprints
and guidance on OpenBSC code.
The first sprint is scheduled for the 9th, 10th (and maybe 11th) of
November. There is no venue for it yet, maybe the CCCB. Please indicate
if you are interested to join.
The general list of osmo-nitb issues are:
* Channel release process. There is a branch I created at the last
congress but I have never tested it. This includes making a SAPI=3
local release, using the proper timeouts for the abnormal release
making sure the SACCH is deactivated and some more issues. This
requires quite a bit of testing.
* Allow to block/unblock failing lchans. We have had this issue with
Nokia BTS but it can happen on other BTS as well. E.g. a given
timeslot might not be allocatable, or we get LCHAN ACT NACK. In that
case OpenBSC should block the lchan.
* smsqueue/auth/paths. In the past years we have seen that the smsqueue
and other parts can get stuck because of the 'subscr_get_con' not
being properly called in all error conditions. We need to review the
code and check how things get stuck.
* Handover testing and patching out the 'timestamp' adjusting or
fixing it. Right now it can be used to add a lot of delay by switching
cells.
cheers
holger
Hi guys,
i'm trying to interconnect a WLAN router with my GSM-sysmoBTS and to use the EAP-SIM authentication protocol. For that i installed a Freeradius on an external board that i use as radius server. The Freeradius should use a database file in order to realise the authentication and the idea is that Freeradius should be able to read the hlr.sqlite3 file from my sysmoBTS. I'm not so far to do this part of the work so, i first want to do some tests using the sim card from sysmoBTS (imsi und ki) and the triplets (RAND, Kc and SRES). I want to create a flat file containing this values so the Freeradius will directly use the file to get the triplets.
I thought i could get the triplets stored in one of the tables of hlr.sqlite3 (AuthLastTuples) but there is no information on it. From the table AuthKeys i could find some Ki values (e.g X'019B7083FBAFC928421A147DE795217782'). I found that there is an "osmo-auc-gen" program for computing the triplets. By using the Ki from AuthKeys and a self generated RAND (e.g 0123456789ABCDEF0123456789ABCDEF) the program doesn't run and doesn't give the triplets. The used authentication algorithm is the COMP128v1.
Has anyone an idea why it doesn't work and why there is no information in the AuthLastTuples table from sysmoBTS ?
best regards
Yann
I modified the patch for ipaccess-find based on Jim's and Holger's suggestions.
Still not sure what to do about the (coming) librt dependency, so no new
version of that patch for now.
Tobias
Tobias Engel (1):
Remove iface arg if SO_BINDTODEVICE isn't available
openbsc/src/ipaccess/ipaccess-find.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
--
1.7.10.2 (Apple Git-33)
Hello,
I am thinking about selling my Siemens BS-11 and a compatible HFC-E1 Evaluation Board.
If anyone is interested please send me a mail: baumgrass at hotmail.com .
Regards,
Bernd.
Hi,
I wrote some code that lets me test OpenBSC without using real hardware, e.g.
one is bothered to wait for the nanoBTS to open the OML connection again, one
doesn't have the unit for the right band, one doesn't have a dual trx system,
or because reproducing the issue is difficult (RF interference, LAPDm timeouts).
I have packaged the code with OBS and right now it is only available for debian
stable (it can be installed on unstable as long as the stable feeds are inside
the sources.list).
Install:
$ echo 'deb http://download.opensuse.org/repositories/home:/zecke23/Debian_6.0/ ./' > /etc/apt/sources.list.d/
$ aptitude update; aptitude install gnu-smalltalk osmo-st-openbsc-test
(the packages are signed but the key expired two years ago, so the question
is if you want to trust Debian packages from OpenSUSE)
Using:
$ gst
st> PackageLoader fileInPackage: #FakeBTS
...
st> bts := FakeBTS.BTS new.
st> bts btsId: '1/0/0'
st> bts connect: 'localhost'; waitForBTSReady.
...
Testing:
There is the FakeBTS.OpenBSCTest class that has methods to require
channels and these Lchans can be used to send RSL messages. I don't have
a public example at this point though.
Vision:
I hope this code will be used to do nightly tests of OpenBSC, specially
the error paths (e.g. timeouts on handover, timeouts on assignment,
timeouts on channel release, etc.)
There is a branch that brings DualTRX support and I am going to merge
this to master soon. What I am missing is some test launcher code (it can be
in python or ruby if someone volunteers) that will launch osmo-bsc/osmo-nitb
with a given configuration file and initialize the HLR with a set of
given subscribers.
enjoy
holger
PS: Blog post will follow once the code has matured a bit
These are some minor modifications to make openbsc run on OSX.
You have to have these MacPorts installed:
pkgconfig
automake
autoconf
libtool
libdbi
libdbi-drivers
sqlite3
... and set:
export LDFLAGS='-L/opt/local/lib'
export CPPFLAGS='-I/opt/local/include'
Everything else should work as usual.
Tobias Engel (3):
Remove interface argument when compiled on OSX
Remove unused librt dependency
Set byte order defines when compiled on OSX
openbsc/src/ipaccess/ipaccess-find.c | 4 ++++
openbsc/src/libmgcp/mgcp_network.c | 8 +++++++-
openbsc/src/libtrau/rtp_proxy.c | 8 +++++++-
openbsc/tests/mgcp/Makefile.am | 2 +-
4 files changed, 19 insertions(+), 3 deletions(-)
--
1.7.10.2 (Apple Git-33)
These are some minor modifications to make openbsc also run on OSX.
You have to have these MacPorts installed:
pkgconfig
automake
autoconf
libtool
libdbi
libdbi-drivers
sqlite3
... and set:
export LDFLAGS='-L/opt/local/lib'
export CPPFLAGS='-I/opt/local/include'
Everything else should work as usual.
Tobias Engel (3):
Define struct iphdr for OSX
Do not use --version-script linker flag on OSX
Add "extern" keywords
configure.ac | 12 ++++++++++++
include/osmocom/gsm/abis_nm.h | 10 +++++-----
src/gb/Makefile.am | 2 +-
src/gb/gprs_ns_frgre.c | 2 +-
src/gsm/Makefile.am | 2 +-
5 files changed, 20 insertions(+), 8 deletions(-)
--
1.7.10.2 (Apple Git-33)
Hello,
I'd like to directly cable a handset to a nanoBTS and thought I could:
- put attenuators on the nanoBTS TX and RX ports
- connect the other side of each attenuator to a resistive
splitter/combiner that has 6dB loss
- connect the combiner common port to the MS
Does this sound sensible and if so what size of attenuators might I
want assuming MS and BTS were each set at 6dBm? I've seen figures for
receiver sensitivity, but wasn't sure as to a "good" RF level to use
with direct cabling!
I also have 10/20 dB directional couplers and circulators if they
might find use in a better configuration.
Regards,
Andrew
--
Andrew Back
http://carrierdetect.com
Hello,
I'm working with OpenBSC since 2 month. Currently my OpenBSC setup runs with
2 mobile phones which can communicate A5/1 encrypted with each other.
I got several problems while running this system with a NanoBTS. I use
osmo-nitb.
Entries in my HLR receive wrong time values. The time values of the column
"created" and "updated" are exactly 2 hours earlier than they should be.
The system time of the controller works fine and the time in the logs from
"./osmo-nitb -e 1 -T" is correct. Are there any other timers which work with
the NanoBTS?
Furthermore my network does not run stable. Sometimes following error occurs
:
input/ipaccess.c:454 Bad signalling Message, sign link returned error
input/ipaccess.c:260 Forcing socket shutdown with no signal link set
The error usually appears after some authentification "traffic". Sometimes
the system runs stable for several hours without any errors. The error leads
to a restart of the connection. I'm not sure if this problem has something
to do with the first problem.
thanks and best regards!
Nicklas
Hi guys,
Does anyone know if the sysmoBTS has any kind of RADUIS server? By entering the " opkg search *rad* " command i didn't get anything.
Best regards
Yann
Sorry to those who receive this message twice.
I hope Osmocom community finds this small effort interesting as well.
---------- Forwarded message ----------
From: Alexander Chemeris <alexander.chemeris(a)gmail.com>
Date: Fri, Oct 19, 2012 at 5:15 PM
Subject: Open-source telecom T-shirts
To: umtrx <umtrx(a)lists.osmocom.org>, openbts-discuss(a)lists.sourceforge.net
Hi all,
We're thinking about making T-shirts with open-source telecom. I've
posted a call for ideas in my OpenBTS blog - please contribute.
Telecom needs more openness and you could help us promote this!
http://openbts.chemeris.ru/2012/10/reklama-open-source-telecom/
We plan to give them for free to the first 10-20 UmTRX buyers. Then
you'll be able to buy them from our web-shop or from one of our
friends and distributors.
If you proposal gets printed, you'll get a free T-shirt as well.
PS If you know a good online T-shirt printing service in US or Europe
- drop me a line. I've never done this in US/Europe before.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hello,
Is there anyone who has 1800MHz or 900MHz hardware and that would be
interested in swapping it for 1900MHz kit? Probably a long shot but
worth asking! If so, please contact me off-list.
Cheers,
Andrew
--
Andrew Back
http://carrierdetect.com
Hi,
I just pushed a "tobias/csd" branch to both the openbsc and libosmo-abis
git.
If you check out those branches you should be able to make CSD calls
with a BS-11 and the following parameters: V.110, 9.6kbit/s, transparent
mode.
The AT-Command to activate this mode is AT+CBST=71,0,0. (If you see an
ERROR when entering this command, your phone's baseband most likely
doesn't support transparent mode. One of the few exceptions seem to be
MediaTek and TI.)
There is no Interworking Function in the code - the V.110 frames simply
get sent from one phone to the other. This should not be a problem as
long as both sides use the exact same parameters.
The openbsc tobias/csd branch is based on Harald's laforge/csd branch
which already adds code for setting CSD channel modes.
Many thanks to Dieter Spaar who found out why I was only seeing garbled
data on the uplink, and also to GSMK who let me use lots of my time
there to figure out this CSD stuff.
Next stop would be to implement RLP to also support V.110
non-transparent mode which is supported by almost all GSM basebands.
-Tobias
Hi,
some problems with latest git clone and nanoBTS 165AU...
<0002> gsm_04_08.c:412 -> LOCATION UPDATE ACCEPT
<0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 05) Sending 0x02 to MS.
<0002> gsm_04_08.c:754 -> MM INFO
<0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 05) Sending 0x32 to MS.
<0002> gsm_subscriber.c:337 Subscriber 262620001000026 ATTACHED LAC=10
<0003> gsm_04_08.c:1158 TX APPLICATION INFO id=0x00, len=4
<0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 06) Sending 0x38 to MS.
<0000> abis_rsl.c:1542 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION
<0002> gsm_04_08.c:1045 TMSI Reallocation Completed. Subscriber:
262620001000026
<0000> chan_alloc.c:429 (bts=0,trx=0,ts=0,ss=0) starting release sequence
<0003> gsm_04_08_utils.c:231 Sending Channel Release: Chan: Number: 0 Type:
1
<0004> abis_rsl.c:618 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD
<0004> abis_rsl.c:1017 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive
channel
<0004> abis_rsl.c:1017 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive
channel
<0000> abis_rsl.c:1542 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION
<0004> bsc_api.c:638 Got data in non active state(RELEASE REQUESTED),
discarding.
<0019> input/ipaccess.c:454 Bad signalling message,sign_link returned error
<0019> input/ipaccess.c:260 Forcing socket shutdown with no signal link set
<001b> bsc_init.c:337 Lost some E1 TEI link: 1 0x81e4768
<001b> bsc_init.c:337 Lost some E1 TEI link: 2 0x81e4768
I have no clue if that is a problem of configuration, nanoBTS or abis
library. With an old version (Feb 2012), the message...
<0019> ipaccess.c:425 Bad signalling message,sign_link returned error.
...appears too, but socket is not being shut down.
Thanks,
LM
This patch relaxes the behaviour on error coming from the signalling
layer. This is probably too strict for recoverable errors.
Thanks to Lennart M�ller <mueller.lennart(a)googlemail.com> for the report.
---
src/input/ipaccess.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/input/ipaccess.c b/src/input/ipaccess.c
index d63e796..4f81c43 100644
--- a/src/input/ipaccess.c
+++ b/src/input/ipaccess.c
@@ -450,10 +450,13 @@ static int handle_ts1_read(struct osmo_fd *bfd)
goto err_msg;
}
if (e1i_ts->line->ops->sign_link(msg) < 0) {
+ /* Don't close the signalling link if the upper layers report
+ * an error, that's too strict.
+ */
LOGP(DLINP, LOGL_ERROR, "Bad signalling message,"
"sign_link returned error\n");
ret = -EINVAL;
- goto err;
+ msgb_free(msg);
}
return 0;
--
1.7.10.4
--LZvS9be/3tNcYl/X--
This patch relaxes the behaviour on error coming from the signalling
layer. This is probably too strict for recoverable errors.
Don't release msgb in this case, as this is controled by the signaling link
layer.
Thanks to Lennart M�ller <mueller.lennart(a)googlemail.com> for the report.
---
src/input/ipaccess.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/input/ipaccess.c b/src/input/ipaccess.c
index d63e796..c0c307e 100644
--- a/src/input/ipaccess.c
+++ b/src/input/ipaccess.c
@@ -450,10 +450,13 @@ static int handle_ts1_read(struct osmo_fd *bfd)
goto err_msg;
}
if (e1i_ts->line->ops->sign_link(msg) < 0) {
+ /* Don't close the signalling link if the upper layers report
+ * an error, that's too strict. BTW, the signalling layer is
+ * resposible for releasing the message.
+ */
LOGP(DLINP, LOGL_ERROR, "Bad signalling message,"
"sign_link returned error\n");
ret = -EINVAL;
- goto err;
}
return 0;
--
1.7.10.4
--ibTvN161/egqYuK8--
Hello everyone,
thanks for the ideas you gave me about how i can learn more about the communication between BSC and MSC in my sysmoBTS. Since last week i've been looking at the source codes and it's still difficult for me to follow the exchanged messages betwenn BSC and MSC. I don't have high programming skills.
Instead of using sysmoBTS as an autonomous self-contained GSM network (NITB mode), i'd like to configure it in the BSC-only mode running the osmo-bts and osmo-bsc. I read that i will need a MSC that can provide an A-over-IP interface using SCCP-lite. I saw that the "on-waves/bsc-master" branch is implementing such a SCCP and works have been done to create a GSM0808 like API and move the MSC code inside OpenBSC over to use this API. So i was wondering how far this project has been developed yet. Do you already have any interesting results that can help me? If not, it can be also interesting for me to know how you did your tests by implementing the bsc-only mode (osmo-bsc)? Did you connect it to a real MSC or did you have anything else emulating the MSC/HLR/VLR/EIR functions?
Best regards
Yann
Hi all!
I *think* Harald is pretty busy and also unlikely to attend
prospective meeting tomorrow.
Also there is bank holiday tomorrow in Germany and at least
I personally will use that to stay away from technology for
a bit, so I won't come.
Nevertheless, I thought I'd write this email to remind
people that in theory there is a meeting tomorrow and
discuss if other people attend.
I personally would propose to shift the meeting to next week
(for purely selfish reasons ;).
As far as I know, there is no formal presentation tomorrow.
Anyway, will anyone attend tomorrow or is everyone in favor
of shifting a week?
In case it takes place, for the people who did not attend so
far, the usual snippet from Harald's mails:
Oct 3, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
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.
Cheers
Nico
Hello,
the Erlang command line interface (OTP version) is available on Github:
https://github.com/josemic/Erlang-command-line-interface_otp
This is a telnet commandline server written in Erlang using OTP
libraries. It provides features such as command-completion,
command-abbreviation, command-help, reading/writing commands from/to
file and modular command-registration.
Its behaviour is kept similar to the well known, C-written, OpenBSC
telnet command line server.
It is intended for future inclusion into Osmocom's Erlang projects.
The installation instructions are found in the github wiki.
Cheers,
Michael
The recent commit to improve the SI generation lead to setting
the BCCH SIs for all TRX in a multi-trx setup. This is because
we create the SIs globally but si_valid appears to be limited
to the 'current' trx. Warn if we attempt to set SIs for the BCCH
on a trx that does not have a BCCH.
---
openbsc/src/libbsc/bsc_init.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/openbsc/src/libbsc/bsc_init.c b/openbsc/src/libbsc/bsc_init.c
index e05aec7..7a60e04 100644
--- a/openbsc/src/libbsc/bsc_init.c
+++ b/openbsc/src/libbsc/bsc_init.c
@@ -129,6 +129,11 @@ static int rsl_si(struct gsm_bts_trx *trx, enum osmo_sysinfo_type i, int si_len)
GSM_BTS_SI(bts, i), si_len);
break;
default:
+ if (bts->c0 != trx)
+ LOGP(DRR, LOGL_ERROR,
+ "Attempting to set BCCH SI%s on wrong BTS/TRX (%d/%d)\n",
+ get_value_string(osmo_sitype_strs, i),
+ bts->nr, trx->nr);
rc = rsl_bcch_info(trx, osmo_sitype2rsl(i),
GSM_BTS_SI(bts, i), si_len);
break;
@@ -149,6 +154,9 @@ static int set_system_infos(struct gsm_bts_trx *trx)
ms_pwr_ctl_lvl(bts->band, bts->ms_max_power);
bts->si_common.cell_sel_par.neci = bts->network->neci;
+ /* Zero, forget the state of the SIs */
+ bts->si_valid = 0;
+
/* First, we determine which of the SI messages we actually need */
if (trx == bts->c0) {
--
1.7.10.4
Hello everybody
First of all, let me introduce myself. My name is Yann Moupinda and I'm
a student doing his Master thesis in the field of
GSM technology. For my thesis, the company for which i'm working now,
bought a sysmoBTS from sysmocom. The
sysmoBTS is configured as a stand alone GSM network in a box (NITB)
running the osmo-nitb and the osmo-bts programs.
An important part of my thesis is to understand how the sysmoBTS works
and therefore I did some measurements with
wireshark to analyse the data flow between the BTS,BSC and
MSC/HLR/VLR/EIR. This is also to see the main differences between a
sysmoBTS and a conventional GSM Network.
I used the " tcpdump " - command on the loopback interface lo0 to
capture the data flow between the GSM components and then, the analysis
with wireshark shows me only the data flow between BTS and BSC. It's
possible to see such messages like LOCATION UPDATING REQUEST and
IDENTITY REQUEST wich are normally, transparently exchanged between
Mobile Station (MS) and the Network subsystem (MSC/HLR/VLR/EIR). All
these messages are always addressed to, or from the same BSC TCP-port
3003. So i can not see what happens behind this port (behind BSC).
In order to get the communication between BSC and MSC, i decided to
have a deeper look on the logging messages of the sysmoBTS. Even there,
i cannot recognize how the data transmission between BSC and MSC works.
Does anyone know how to get this information? Any guidance would be
appreciated.
I have included one .pcap file and a text file of the logging messages
taken while i powered on the mobile phone.
Best regards,
Yann.
Hello Everyone,
I now have OpenBSC (including GPRS) up and running with a fair amount of
stability, using an IP.Access 2G BTS. Now I am looking towards the next
stage - getting a 3G system operating.
I have the use of an IP.Access NodeB that I would like get running with
OpenBSC. In performing my due diligence, I found Harald's 3G road map from
December 2010 or so. I am wondering what the current state of development
is. I see that IP.Access' URSL protocol was an issue back then, because it
is proprietary. Has anyone managed to get far enough in their development
that they have implemented the protocol? I also see from Dieter Spaar's
blog that he is making some progress, but he states his code is not ready
for public release. Since I don't see much about 3G on the OpenBSC wiki, I
am assuming that no one has any code that they would want to share at this
point. I imagine I may have to forge ahead on my own.
I am fairly new to GSM development, and I haven't really delved into the
OpenBSC source yet (other than to discern what might have caused some
problems I encountered), so if anyone has any suggestions on where to
begin, or has some issues where I might be able to assist in order to move
development further down the road, please let me know.
Thanks!
John