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*
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
Dear openbsc folks,
i am following up on the osmo-nitb/ggsn/sgsn config running w/ a nanoBTS-1800.
i have been trying to get mISDN/lcr to build to be able to create the chan_lcr
into asterisk (i am more familiar w/ dahdi/asterisk for isdn cahnnels) though so
far i am not able to get it to work :
*configuration :
**host : running linux debian lenny 2.6.26-2-686)
**autoconf 2.61
**mISDN-1_1_9.1 (downloaded as a tarball) builds mISDN_dsp.ko but not mISDN_l1loop.ko
**lcr doest not build (./configure passes)
/usr/src/lcr# git-apply --verbose lcrOpenBSC.patch
Checking patch gsm_bs.cpp...
error: while searching for:
int bts_model_nanobts_init(void);
static struct log_target *stderr_target;
/* timer to store statistics */
#define DB_SYNC_INTERVAL 60, 0
static struct timer_list db_sync_timer;
error: patch failed: gsm_bs.cpp:39
error: gsm_bs.cpp: patch does not apply
/usr/src/lcr# make
(...)
gcc -DWITH_GSM_BS -I./openbsc/include -I./libosmocore/include -I./openbsc
-Wall -DCONFIG_DATA="\"/usr/local/lcr\"" -DSHARE_DATA="\"/usr/local/lcr\""
-DLOG_DIR="\"/usr/local/lcr\"" -DEXTENSION_DATA="\"/usr/local/lcr/extensions\""
-D_GNU_SOURCE -fPIC -c bchannel.c -o bchannel.po
bchannel.c:29:31: error: mISDN/mISDNcompat.h: No such file or directory
bchannel.c:30: error: 'MISDN_AF_ISDN' undeclared here (not in a function)
bchannel.c:31:24: error: mISDN/q931.h: No such file or directory
bchannel.c: In function 'bchannel_create':
bchannel.c:148: error: 'PF_ISDN' undeclared (first use in this function)
bchannel.c:148: error: (Each undeclared identifier is reported only once
bchannel.c:148: error: for each function it appears in.)
bchannel.c:174: error: 'AF_ISDN' undeclared (first use in this function)
make[1]: *** [bchannel.po] Error 1
make[1]: Leaving directory `/usr/src/lcr'
(lcr from git : commit 6e1e99808e5b1c16b00904d31f95d0b74487023e)
*questions :
**do i need misdn to build lcr if running a nanobts w/ Abis-over-ip ?
**am i missing something in the build order ?
**any packaged version of misdn for debian 2.6.26-2-686 ?
thanks for your support.
Xavier.
Thank you for the quick and helpful replies, Andreas and Holger! I had
a feeling there was an easy answer.
-Tom
> Message: 6
> Date: Wed, 29 Feb 2012 08:21:13 +0100
> From: jolly <andreas(a)eversberg.eu>
> To: Thomas Cooper <tacooper(a)vt.edu>
> Cc: openbsc(a)lists.osmocom.org
> Subject: Re: Specifying channel mode for speech
> Message-ID: <4F4DD1E9.8080409(a)eversberg.eu>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thomas Cooper wrote:
>> Osmo-bts gets the MODE_MODIFY_REQ from OpenBSC with
>> GSM48_CMODE_SPEECH_EFR to use for the channel mode. However, I would
>> like to be able to specify using GSM48_CMODE_SPEECH_V1 instead (which
>> is FR; EFR is not supported in L1). Is there an easy way to set the
>> preferred channel mode/audio support? I didn't see anything on the VTY
>> wiki or in the config file.
>>
> hi tom,
>
> you may change the line 46 at mncc_builtin.c. the first entry in this
> array is the full rate code, the second entry is the half rate codec.
> (depending on the trx configuration) just change the first entry to
> GSM48_CMODE_SPEECH_V1.
>
> regards,
>
> andreas
>
> ------------------------------
>
> Message: 8
> Date: Wed, 29 Feb 2012 09:54:24 +0100
> From: Holger Hans Peter Freyther <holger(a)freyther.de>
> To: openbsc(a)lists.osmocom.org
> Subject: Re: Specifying channel mode for speech
> Message-ID: <4F4DE7C0.5000000(a)freyther.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 02/29/2012 08:21 AM, jolly wrote:
>
>> you may change the line 46 at mncc_builtin.c. the first entry in this
>> array is the full rate code, the second entry is the half rate codec.
>> (depending on the trx configuration) just change the first entry to
>> GSM48_CMODE_SPEECH_V1.
>
> you can change this with the VTY config. Look at commit
> ab386e6120559ef2deb6a27f4455539cba920c9d that introduced it.
>
> holger
>
Hi Jolly,
On Wed, Feb 29, 2012 at 09:21:34AM +0100, jolly wrote:
> i improved the generation of neighbour cells of openbsc. the patch is
> committed at origin/jolly/rtpmux.
Thanks a lot for working on this. It's a really nasty subject with lots
of bit-fiddling and many strange cases.
> it generated the system information messages of neighbour cells in the
> same and in other bands. depending on the location of the bcch and the
> neighbour cells, the messages SI 2/5 and optionally SI 2bis/5bis and SI
> 2ter/5ter are generated.
>
> i have tested it with several configurations. i would like to commit it
> to master. any suggestions?
I've reviewed it, and the patch seems fine to me. I haven't tested it,
though. Feel free to commit it to master. And thanks for the verbose
changelog message.
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)
Osmo-bts gets the MODE_MODIFY_REQ from OpenBSC with
GSM48_CMODE_SPEECH_EFR to use for the channel mode. However, I would
like to be able to specify using GSM48_CMODE_SPEECH_V1 instead (which
is FR; EFR is not supported in L1). Is there an easy way to set the
preferred channel mode/audio support? I didn't see anything on the VTY
wiki or in the config file.
Thanks,
Tom
Hi together,
the registration for the next Easterhegg in Basel (Switzerland) is open.
-->> https://easterhegg.ch
We are still looking for workshops and lectures. You can find more
information in the attached text file.
Here our poster:
https://easterhegg.ch/eh2012-plakat-a3.pdf
Gruss
Miguel aka nobody
--
------------------------------------------------------------------
Chaostreff Basel, Birsfelderstrasse 6, 4132 Muttenz, Schweiz
WEB: https://www.chaostreff.ch Wiki: http://wiki.chaostreff.ch
Jabber: nobody_su(a)jabber.ccc.de
------------------------------------------------------------------
=== Please don't print this e-mail unless you really need to, this is
your contribution to save the environment. ===
Hi!
I'm just writiing this up as you mentioned that you were considering to
look into implementing an external SMSC. This is great news, and of
course you can do it whatever way you want to do it.
However, to put things a bit more into perspective and ensure that this
SMSC can also be used in a real GSM core network later on, I would like
to ask you to consider staying in line with how the
primitives/transacitions look like in a real GSM network.
The idea here is that with every new interface we introduce in
osmo-nitb, we should try ot move towards that of a real network. This
does't mean that it has to implement the actual detailed MAP/TCAP/SCCP
encoding as specified, but simply that they semantic of the
primitives/messages and their order and time of occurrence is the same.
Hi,
currently, when OpenBSC receives any mobile originated Supplementary
Service request, it always treats it as an USSD request (because the
only SS it supports is a USSD request for sending back the extension of
the subscriber).
What I think the code in handle_rcv_ussd is meant to be doing is:
If the request contained an USSD string, and if that string is equal to
"*#100#", return the subscriber extension. In all other cases reject the
request with "unrecognized component".
But currently it returns the extension even when the SS request wasn't
even an USSD request.
That causes several phones with Qualcomm baseband to hang and reboot
after a while because in some situations they send an interrogateSS
request to query if any call forwardings are active and cannot handle
the wrong answer they receive.
(Strangely, that happens with most "modern" HTC phones i have tried
right after logging into the network, rendering them completely useless
for use with OpenBSC)
Here is a patch:
--- a/openbsc/src/libmsc/ussd.c
+++ b/openbsc/src/libmsc/ussd.c
@@ -54,7 +54,7 @@ int handle_rcv_ussd(struct gsm_subscriber_connection
*conn, struct msgb *msg)
if (req.text[0] == 0xFF) /* Release-Complete */
return 0;
- if (strstr(USSD_TEXT_OWN_NUMBER, req.text) != NULL) {
+ if (strcmp(USSD_TEXT_OWN_NUMBER, (const char *) req.text) == 0) {
DEBUGP(DMM, "USSD: Own number requested\n");
rc = send_own_number(conn, msg, &req);
} else {
-Tobias
Trying to replicate my setup to a new machine. Not sure what I'm missing
as now my old LCR source is showing the same issue on Debian 6.06. No
difference with the current GIT commit... same error.
root@Netbox:/usr/src/lcr# make
make all-am
make[1]: Entering directory `/usr/src/lcr'
g++ -DHAVE_CONFIG_H -I. -DWITH_MISDN -DWITH_CRYPT -DWITH_GSM_BS -Wall
-DCONFIG_DATA="\"/usr/local/lcr\"" -DSHARE_DATA="\"/usr/local/lcr\""
-DLOG_DIR="\"/usr/local/lcr\""
-DEXTENSION_DATA="\"/usr/local/lcr/extensions\"" -g -O2 -MT gsm.o -MD
-MP -MF .deps/gsm.Tpo -c -o gsm.o gsm.cpp
In file included from gsm.cpp:14:
mncc.h:195: error: ‘uint32_t’ does not name a type
mncc.h:196: error: ‘uint32_t’ does not name a type
mncc.h:197: error: ‘uint32_t’ does not name a type
mncc.h:198: error: ‘uint16_t’ does not name a type
mncc.h:199: error: ‘uint32_t’ does not name a type
mncc.h:200: error: ‘uint32_t’ does not name a type
gsm.cpp: In member function ‘void Pgsm::send_mncc_rtp_connect()’:
gsm.cpp:133: error: ‘struct gsm_mncc_rtp’ has no member named ‘ip’
gsm.cpp:134: error: ‘struct gsm_mncc_rtp’ has no member named ‘port’
gsm.cpp:137: error: ‘struct gsm_mncc_rtp’ has no member named
‘payload_msg_type’
gsm.cpp:140: error: ‘struct gsm_mncc_rtp’ has no member named
‘payload_msg_type’
gsm.cpp:143: error: ‘struct gsm_mncc_rtp’ has no member named
‘payload_msg_type’
gsm.cpp:146: error: ‘struct gsm_mncc_rtp’ has no member named
‘payload_msg_type’
gsm.cpp:149: error: ‘struct gsm_mncc_rtp’ has no member named ‘payload_type’
gsm.cpp:150: error: ‘struct gsm_mncc_rtp’ has no member named
‘payload_msg_type’
gsm.cpp:150: error: ‘struct gsm_mncc_rtp’ has no member named ‘payload_type’
gsm.cpp:151: error: ‘struct gsm_mncc_rtp’ has no member named ‘msg_type’
gsm.cpp: In member function ‘void Pgsm::setup_cnf(unsigned int, unsigned
int, gsm_mncc*)’:
gsm.cpp:500: error: ‘struct gsm_mncc_rtp’ has no member named ‘msg_type’
gsm.cpp: In member function ‘void Pgsm::rtp_create_ind(unsigned int,
unsigned int, gsm_mncc*)’:
gsm.cpp:649: error: ‘struct gsm_mncc_rtp’ has no member named ‘ip’
gsm.cpp:649: error: ‘struct gsm_mncc_rtp’ has no member named ‘port’
gsm.cpp:650: error: ‘struct gsm_mncc_rtp’ has no member named ‘ip’
gsm.cpp:651: error: ‘struct gsm_mncc_rtp’ has no member named ‘port’
gsm.cpp:656: error: ‘struct gsm_mncc_rtp’ has no member named ‘ip’
gsm.cpp:656: error: ‘struct gsm_mncc_rtp’ has no member named ‘port’
gsm.cpp: In member function ‘void Pgsm::rtp_connect_ind(unsigned int,
unsigned int, gsm_mncc*)’:
gsm.cpp:669: error: ‘struct gsm_mncc_rtp’ has no member named ‘ip’
gsm.cpp:669: error: ‘struct gsm_mncc_rtp’ has no member named ‘port’
gsm.cpp:670: error: ‘struct gsm_mncc_rtp’ has no member named ‘ip’
gsm.cpp:671: error: ‘struct gsm_mncc_rtp’ has no member named ‘port’
make[1]: *** [gsm.o] Error 1
make[1]: Leaving directory `/usr/src/lcr'
make: *** [all] Error 2
Hi all!
= Schedule =
I've put together a preliminary schedule for OsmoDevCon. It can be seen
at http://laforge.gnumonks.org/tmp/OsmoDevCon.ics or as a html rendering
at http://laforge.gnumonks.org/tmp/OsmoDevCon.html
Pleaes notice that there is still a lot of flexibility, let me know if I
forgot anything or if there is something missing.
Please also note that there are some topics which were suggested and
where there is an obvious speaker/moderator, but where that person
probably doesn't really know anything about having to talk about that
topic yet (e.g. Holgers work on cellmgr-ng, Smalltalk projects, ...).
So please don't be too surprised if you find your name somewhere. We
will probably want to talk about the topic, whether you will have time
to prepare some slides or not ;)
If somebody knows a good way to render a nice overview HTML table from
the .ics file, I would appreciate that, as it would give a better
overview. I've attached a icedove screenshot for your reference
meanwhile.
= Arrival / Departure =
We are starting at 11am on friday, for people who arrive that very
morning in Berlin. There are no scheduled talks/discussions after the
lunch break on monday, but we still have the room until monday night, so
feel free to stay around for more unscheduled discussions and hacking.
= Meals =
== Lunch ==
We will probably have sponsored lunches on one or two days brought by
catering into c-base, but apart from that all meals will be on your own
expense.
Nevertheless we could try to organize something (like ordering large
pizzas) and then share the cost. This would avoid the time delays
associated with having to go to a restaurant, make an order, wait for
the food, go back to c-base, etc.
== Dinner ==
All I could offer with regard to dinner is to make reservations in
not-too-far-away restaurants, where we could go together. Please let me
know if I should take care of that or rather not.
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)
Hey Osmoworld,
Just a little intro before my rambling questions... I've been working on
connecting OpenBTS and osmo-bts/OpenBSC together, and everything works well
enough to at least send messages between the two (it's somewhat hackish but
it works for me so far). The phone sees the network and when I attempt to
connect, it is assigned a SDCCH and starts the typical location update
process. This makes me think the underlying issue is in my OpenBSC/network
setup.
Now for the problems: (probably best to check the console output below
first)
Even though the MS receives an ID request and returns an ID response, the
LU Request times out and returns cause=13 (default from config). I'm not
sure what happens after the ID response since it doesn't seem to have sent
anything else down to the MS.
I also don't know too much about the MS's job, but it seems to send 3 LU
requests every time (2 of which are unnecessary and rejected as
duplicates). I assume that's what the preceding ERROR IND messages are
referring to, but I don't know for certain.
My BTS BCCH has LAI=001/01/1, which is correctly set in both OpenBTS and
OpenBSC config files. The Location Updating Request contains
LAI=001/01/65534, which I think may be the main issue since LAC=65534 is
reserved (even looking in GSM-04.08, I couldn't find any details about
this; can you shed some light please?). The MS works with standard OpenBTS
by the way.
I've looked through the gsm_04_08 code and Wireshark capture, but no clues
stick out. I'm not too familiar with OpenBSC in general, so this could be
as simple as setting some kind of config parameter. I figured I'd ask on
here for help in case I'm just missing something basic.
Here is the console output (with debug and authorize-everyone flags on):
Wed Feb 22 13:06:24 2012 <0004> abis_rsl.c:1317 (bts=0,trx=0,ts=0,ss=0)
Activating ARFCN(51) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x0e ta=0
Wed Feb 22 13:06:24 2012 <0004> abis_rsl.c:1064 (bts=0,trx=0,ts=0,ss=0)
CHANNEL ACTIVATE ACK
Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 ESTABLISH INDICATION
Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:1023 LOCATION UPDATING REQUEST:
mi_type=0x01 MI(460020020292786) type=NORMAL
Wed Feb 22 13:06:25 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05)
Sending 0x18 to MS.
Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1439
(bts=0,trx=0,ts=0,ss=0) ERROR INDICATION cause=unknown 0x0
Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 ESTABLISH INDICATION
Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:1023 LOCATION UPDATING REQUEST:
mi_type=0x01 MI(460020020292786) type=NORMAL ignoring request due an
existing one: 0x20f1350.
Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:383 Subscriber 460020020292786:
LOCATION UPDATING REJECT LAC=1 BTS=0
Wed Feb 22 13:06:25 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05)
Sending 0x04 to MS.
Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1439
(bts=0,trx=0,ts=0,ss=0) ERROR INDICATION cause=unknown 0x0
Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 ESTABLISH INDICATION
Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:1023 LOCATION UPDATING REQUEST:
mi_type=0x01 MI(460020020292786) type=NORMAL ignoring request due an
existing one: 0x20f1350.
Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:383 Subscriber 460020020292786:
LOCATION UPDATING REJECT LAC=1 BTS=0
Wed Feb 22 13:06:25 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05)
Sending 0x04 to MS.
Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 DATA INDICATION
Wed Feb 22 13:06:25 2012 <0003> bsc_api.c:430 CLASSMARK CHANGE CM2(len=3)
CM3(len=4)
Wed Feb 22 13:06:27 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 DATA INDICATION
Wed Feb 22 13:06:27 2012 <0002> gsm_04_08.c:446 IDENTITY RESPONSE:
mi_type=0x02 MI(357966009107140)
Wed Feb 22 13:06:30 2012 <0002> gsm_04_08.c:484 Location Updating Request
procedure timedout.
Wed Feb 22 13:06:30 2012 <0002> gsm_04_08.c:383 Subscriber 460020020292786:
LOCATION UPDATING REJECT LAC=1 BTS=0
Wed Feb 22 13:06:30 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05)
Sending 0x04 to MS.
Wed Feb 22 13:06:30 2012 <0000> chan_alloc.c:429 (bts=0,trx=0,ts=0,ss=0)
starting release sequence
Wed Feb 22 13:06:30 2012 <0003> gsm_04_08_utils.c:231 Sending Channel
Release: Chan: Number: 0 Type: 1
Wed Feb 22 13:06:30 2012 <0004> abis_rsl.c:579 (bts=0,trx=0,ts=0,ss=0)
DEACTivate SACCH CMD
Wed Feb 22 13:06:31 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0)
SAPI=0 RELEASE INDICATION
Wed Feb 22 13:06:31 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=0,ss=0) RF
Channel Release CMD due error 0
Wed Feb 22 13:06:31 2012 <0004> abis_rsl.c:658 (bts=0,trx=0,ts=0,ss=0) RF
CHANNEL RELEASE ACK
Thanks for any help,
Tom Cooper
--
Graduate Research Assistant
Wireless @ Virginia Tech
tacooper(a)vt.edu
Hello David,
> I could also give a more detailed presentation on the radiomodem and
> FEC parts of OpenBTS if there is interest in such low-layer details,
> maybe on Monday afternoon if there are still people around.
I am interested too, however I have to leave on Monday afternoon. But
if I am the only one affected there is of course no need to change the
schedule.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi all!
Time is moving fast, and the OsmoDevCon is getting closer. There's
still two months, but I think we should start to put together some kind
of agenda.
First of all, I would like to ask when we should start on Friday. I
would make this somewhat dependent on when the participants will be
arrviing. So far I was thinking about 10am. Please let me know if you
arrive on Friday but significantly later than that.
I have collected a number of topics for both 'presentation' style events
as well as more round-table/discussion items at
https://bs11-abis.gnumonks.org/trac/wiki/OsmoDevCon2012#Presentations
and
https://bs11-abis.gnumonks.org/trac/wiki/OsmoDevCon2012#WorkingGroupDiscuss…
respectively.
Please feel free to add topics that you want to speak yourself about, or
that you would like to hear about. For example, we don't have anything
about OsmoSDR or SIMtrace at this point, but I'm not sure how much
interest there is about those topics.
I would like to collect topics until 2012-02-15, and then start to make
some kind of schedule.
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)
Hi list,
I just had tried to connect a nanoBTS model 165a with firmware v142b13d0 to openBSC. The BTS does connect to OML, starts with the PING - PONG and identifies itself, but nothing else happens (i.e. no software activate request). As recent firmware requires an explict IDENTITY ACK after answering an IDENTITY REQ with the RESP, I made a small patch to ipaccess.c - and voila, BTS connects OML, gets initalised (at the second attempt as usual - I'll try to dig into this later), establishes RSL and is happily showing green.
Feel free to integrate the attached patch.
Best regards,
Flo.
Hello All,
After some trials and tribulations, I think I got my OpenBSC+LCR+Asterisk
compiles and working. The MS connects once I spoof the proper MCC/MNC for
the foreign SIM I have (to ensure that no one else can connect within my
area). Then when I try to make a test call to an asterisk extension, it
give me the following:
Thu Feb 9 18:55:58 2012 <0004> abis_rsl.c:1318 (bts=0,trx=0,ts=2,ss=0)
Activating ARFCN(514) SS(0) lctype TCH/F r=CALL ra=0x4f ta=1
Thu Feb 9 18:55:58 2012 <0004> abis_rsl.c:1064 (bts=0,trx=0,ts=2,ss=0)
CHANNEL ACTIVATE ACK
Thu Feb 9 18:55:58 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=2,ss=0)
SAPI=0 ESTABLISH INDICATION
Thu Feb 9 18:55:58 2012 <0002> gsm_04_08.c:858 <- CM SERVICE REQUEST
serv_type=0x01 mi_type=0x04 M(210271915)
Thu Feb 9 18:55:58 2012 <0002> gsm_04_08.c:800 -> CM SERVICE Reject cause:
2
Thu Feb 9 18:55:58 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 2 pd 05)
Sending 0x22 to MS.
Thu Feb 9 18:55:58 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=2,ss=0)
SAPI=0 DATA INDICATION
Thu Feb 9 18:55:58 2012 <0003> bsc_api.c:430 CLASSMARK CHANGE CM2(len=3)
CM3(len=9)
Thu Feb 9 18:56:03 2012 <0000> chan_alloc.c:429 (bts=0,trx=0,ts=2,ss=0)
starting release sequence
Thu Feb 9 18:56:03 2012 <0003> gsm_04_08_utils.c:231 Sending Channel
Release: Chan: Number: 0 Type: 2
Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:579 (bts=0,trx=0,ts=2,ss=0)
DEACTivate SACCH CMD
Thu Feb 9 18:56:03 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=2,ss=0)
SAPI=0 RELEASE INDICATION
Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=2,ss=0) RF
Channel Release CMD due error 0
Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=2,ss=0):
MEAS RES for inactive channel
Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:658 (bts=0,trx=0,ts=2,ss=0) RF
CHANNEL RELEASE ACK
Any assistance would be appreciated.
Regards,
-Don
Hi dear list,
After sometimes to get it work, I have set-up a fixed IP on my ip.access nanoBTS
and thought that could be helpful to share the howto/tuto from this experience :
The best way for linux user is to use the ipaccess-telnet tool from the git
(git clone git://git.osmocom.org/libtelnet.git) rather than BTS installer from
ip.access which doesn't easily allow the access to the flags of configuration (i.e. NV
attributes) of the nanoBTS.
1/installation of ipaccess-telnet
I have installed it on a debian 5.0.9 (linux 2.6.26) after git cloning
git://git.osmocom.org/libtelnet.git
my autotools versions : autoconf 2.61-8 + automake 1:1.10.1-3
after running into the following autotools build
#autoreconf; automake --add-missing; autoreconf; autoconf; automake; ./configure
--prefix=/usr/local; make -j 2; make install
I ran into that error "ltmain.sh: No such file or directory" and used the
following command to fix that config error
#libtoolize
in the libtelnet directory and I had the ipaccess-telnet tool build/installed
2/use of ipaccess-telnet on the nanoBTS
once ipaccess-telnet is installed, one should first allow the telnet on port
3210 on the nanobts using that command
#ipaccess-config -n 0x400/0x400 BTS_IP
which set the correct mask on the flag enabling the telnet on port 3210.
Then I could telnet the nanoBTS on port 3210 w/ the following command
#ipaccess-telnet <ip> 3210
once on the CLI interface for the nanoBTS, you can get help w/
>help config
(...)
db::setnetmask <net mask> Sets nBTS IP Net Mask
db::setipaddr <ipaddr> Sets nBTS IP address
(...)
db::getflags
(...)
db::setflag <flag> Enables Config Flag
db::clearflag <flag> Disables Config Flag
(...)
>dhcp help
Expecting 3 arguments
DHCP configuration flags in database:
- DHCP enabled: TRUE
- static IP Address: TRUE
- static IP gateway config: FALSE
- static VSI config: FALSE
DHCP configuration flags in use:
- DHCP enabled: TRUE
- static IP Address: TRUE
- static IP gateway config: FALSE
- static VSI config: FALSE
DHCP uptime = 52567 seconds
DHCP state: BOUND
T1 inactive
T2 inactive
Lease Timer inactive
and the static ip configuration :
To set-up the IP address
>db::setipaddr IP
>db::setnetmask netmask
To disable the DHCP client
>dhcp dhcp false
>db::clearflag dhcp
Xavier Carcelle
Hi all,
wireshark has merged all pending patches that we were working on.
This means that the daily builds from
https://www.wireshark.org/download/automated/osx/ and
https://www.wireshark.org/download/automated/win32/ will now work
out-of-the-box for any pcap traces of OML (Siemens and ip.access
BTS) and OM2000 (Ericsson BTS). The ip.access vendor-specific RSL
extensions have also been merged.
By the way: If anyone was interested in writing a dissector for the
Nokia OML dialect, it would be much appreciated. So far, nobody has
started, but the OpenBSC code base contains an implementation of the
protocol, and the hardware seems to be used by a number of project
members, so getting traces should also not be a problem.
Regards,
Haralad
--
- 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)
Hello All,
I've been working on trying to get OpenBSC to work with Asterisk following
this as a guide:
http://openbsc.osmocom.org/trac/wiki/OpenBSC_LCRhttp://www.misdn.org/index.php/Howto_for_Debian
Basically I'm missing the mISDN_l1loop kernel module.
When trying to compile from the mISDN git repository i'm getting the
following error when trying to compile
(Ubuntu - 10.04 LTS )
./configure
configure: error: kernel build tree does not exist
build:/lib/modules/2.6.32-33-generic/build /
source:/lib/modules/2.6.32-33-generic/source
(Debian - 6.06)
passes configure
when "make modules" is running
make[3]: Entering directory `/usr/src/linux-headers-2.6.32-5-686'
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/l1oip_core.o
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/l1oip_codec.o
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/core.o
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/fsm.o
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/socket.o
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/clock.o
CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.o
/root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.c: In function
âmISDN_freedchannelâ:
/root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.c:113: error: implicit
declaration of function âflush_work_syncâ
make[6]: *** [/root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.o] Error 1
make[5]: *** [_module_/root/mISDN/standalone/drivers/isdn/mISDN] Error 2
make[4]: *** [sub-make] Error 2
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.32-5-686'
make[2]: *** [modules_] Error 2
make[2]: Leaving directory `/root/mISDN/standalone'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/root/mISDN/standalone'
make: *** [modules] Error 2
root@OpenBSC:~/mISDN#
I should note that Centos 5.7 and Gentoo give the same errors as Ubuntu....
Any assistance is appreciated.
Regards,
-Don
On 02/01/2012 05:03 PM, Ammar Naamat Hameed wrote:
> Hi,
this is a Free Software project. You can read about the values of Free
Software here[1]. If you do not release the sourcecode you are not part of our
community.
holger
[1] http://simple.wikipedia.org/wiki/Free_software
> I haven't published the source code yet, but I have attached two traces, one
> of them has the TCAP message that I don't know how to handle which is the
> (ReturnResultLast) that has only the InvokeID in it, I hope you can help
> figure out this return message.
> The other attached trace has (ReturnResultLast ForwardSM) which is normal
> reply message to a ForwardSM message about the successful receiving of the SMS
> (SMS-Deliver Report).
>
> Thanks,
> Ammar
>
> *From:* Holger Hans Peter Freyther <holger(a)freyther.de>
> *To:* openbsc(a)lists.osmocom.org
> *Sent:* Wednesday, February 1, 2012 12:20 AM
> *Subject:* Re: TCAP Stack
>
> On 02/01/2012 12:53 AM, Ammar Naamat Hameed wrote:
> > Hi,
>
> Hi,
>
> can you send me a link to the sourcecode?
>
> thanks
>
>
>
>
>
