Hello,
second try to add support to bs11_config for bport0/1 configuration. This
time with enum abis_bs11_line_cfg.
It seems sometimes creating bport1 fails, even LMT shows create obj
greyed out. Don't know why yet.
Regards,
Daniel Willmann
Daniel Willmann (1):
Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config
openbsc/include/openbsc/abis_nm.h | 10 +++++++++-
openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++--
openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++
3 files changed, 64 insertions(+), 3 deletions(-)
Hi Holger!
I'm currently reviewing changeset 2d501ea26a219176b1c556449e45ebd90d4accfb
and just noticed that you introduce a new 'int rf_locked' member to struct
gsm_bts_trx, which I believe is not needed.
We are already tracking the administrative state of all objects in the BTS
and mirror their state.
The specific state you are looking for should be in
gsm_bts_trx.nm_state.administrative
I would appreciate if you could fix this.
--
- 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!
While enroute to FOSS.in in Bangalore, I took the time to test and debug
the various issues I could find with the code in the system_information branch.
At least in all of my tests, the system information messages, including rest
octets and neighbor cell lists are looking perfectly fine. Especially now
that with my latest patch, wireshark is able to dissect the SI messages properly,
it is much easier to debug :)
If you want to give it a try, I recommend using something like git revision
63b152ebb74355acfde76e9ce1113f2d823c0804 of that branch.
Please note: We currently only support the relative bitmask format for the
neighbor cell lists. That means, you cannot have neighbors with ARFCN's
spanning a range of more than 111, i.e. your lowest and highest ARFCN have
to be within a distance of 111 ARFCN's.
Unless there are major objections, I intend to merge this branch ASAP (or
rather do a 'git diff master..system_information' and apply the resulting diff
as one commit to master)
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)
Dear openBSC users,
This project sounds interesting and promising.
I would like to collect MSISDN (mobile numbers) for people attending a fundraising gallery. Then I send them SMS (using the MSISDN list I made) with 5 bucks donation link.
Of course I can run with a pen and paper and do that, but instead I would like to use technology to help me.
Is this possible to do with openBSC? Or even other GNURadio modules?
I am not interested in:
using openBSC to make/receive phone calls nor IMSI and TMSI.
Bands of interest are:
900/1800 GSM
2100 UMTS
In case this is not possible using GNU Radio modules. Is there commercial solutions to do that?
Peace,
Mohammad Halawah
Project Engineer
JETZT REGISTRIEREN: Vierteljährlicher Newsletter über die Welt der mobilen Lösungen! http://www.smartmachine.net/newsletter.html <http://www.smartmachine.net/newsletter.html>
REGISTER NOW: Quarterly newsletter about the world of mobile solutions! http://www.smartmachine.net/en/newsletter.html <http://www.smartmachine.net/en/newsletter.html>
smartmachine Forschung & Entwicklung GmbH
Sterneckstraße 33
5020 Salzburg
Austria
O: + 43 662 880440-52
F: + 43 662 880440-99
M: + 43 664 1101 206
E: mohammad.halawah(a)smartmachine.net <mailto:martin.leitner@smartmachine.net>
Hi!
Today I spent some time investigating the cheap 16-in-1 SIM cards on which
we can set our own Ki. This means that those cards can be used for
cryptographic authentication with OpenBSC. Finally, we will have not only
IMSI-based identification, but actual authentication!
I've created a page in the Wiki about those cards:
http://openbsc.gnumonks.org/trac/wiki/MagicSIM
Using this information, I could send the RUN GSM ALGORITHM APDU to the card and
retreive SRES + Kc. The result matched what I can also obtain using the
COMP128v1 code from http://www.scard.org/gsm/a3a8.txt
I will add Comp128v1 support to OpenBSC as soon as I have tested acutal
authentication using this 16-in-1 SIM card.
By the way: It would really be great if somebody could hack up a small command
line program that can be used to program the Operator Name, Ki, ICCID, IMSI and
preferred PLMN into the 16-in-1 SIM.
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!
As Dieter has noticed, GSM traces from gammu / nokia DCT3 phones show the
complete SYS INFO decode inside wireshark. However, the RSL messages BCCH
INFORMATION do not decode it.
I've revolved this problem and submitted a patch to the wireshark team,
you can get it from https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4268
Please note: This patch does not yet address the problem for the SI5/SI6 in
SACCH FILLING. The solution is not as easy, since in this case a generic
L3 IE is handed of to the GSM_A_DTAP rather than GSM_A_CCCH dissector.
If anyone wants to help out with fixing this for the SACCH, I'm sure many
OpenBSC users and wireshark guys will be happy to receive a patch/fix.
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 All!
While looking at a wireshark trace (with the newly discovered wireshark system
information dissector, for which I'll submit a patch to wireshark later
tonight), I just realized that in SI1 we still shend a Cell Allocation of a
hardcoded ARFCN 123.
So unless you run in GSM900 and you use ARFCN 123, the SI1 content will
disagree with the actual radio carrier.
This is likely to cause confusion with at least some phones.
We already have code to generate the channel lists inside SI messages, but this
code is so far not used in the master branch.
So this is just a reminder "There is a known Issue". If you want to experiment
with a supposed fix for it, try using the system_information branch.
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)
Sorry for this posting, but due a timewaster from berlin the last nanoBTS type 139 is for sale again.
It is a siemens branded (MOGIS) nanoBTS type 139, pictures you can see on http://umts.zerber.us
It is my last one, there is no PoE included, so the special price is 1900 euro plus shipping.
I am currently not in switzerland, I try to get some TETRA equipment,
so the shipment will be in the second week of december.
Payment to my bank account or PayPal.
I sold already a lot of this nanoBTS to members from the openBSC-Group for a good price,
thank you to all of you.
Thank you, Rohit for the link.
N.
On Mon, 2009-11-23 at 09:04 +0530, Rohit Joshi wrote:
> It suggest patch found conflict in code. Read this to get started on
> handling patch rejects http://elinux.org/Handling_Patch_Rejects
>
>
> 2009/11/23 ನಾಗೇಶ್ <openbscuser(a)gmail.com>:
> > Hi,
> > When applying patch (as described in Debian_Getting_Started page), I get
> > messages as shown in screenshot. What do these mean ?
> >
> > N.
> >
>
>
>
Hey Guys,
this is just a small head about the current work and how it relates to the
OpenBSC project. So far I had developed in a branch and used rebase on it but
I'm going to do regular releases so I have to stop modifying the history.
Now I have the following branches:
on-waves/mgcp:
- This includes the MGCP media gateway implementation. The MSC in use
has a mapping from the Circuit Identity Code (Multiplex + Timeslot)
to an MGCP Endpoint. To ease development I have one bsc process
and one mgcp one. To properly "connect" audio bsc and mgcp share
a secret which is the RTP port to be used... E.g. I can bind all
RTP ports ahead of time (also nice for tunneling data).
There is some overlap with the current rtp proxy code but I'm not
yet sure how these two fit together... So the future might be I
include the MGCP code in the BSC and use the existing proxy code..
but I really don't know right now.
on-waves/sccp:
- This includes the SCCP implementation. It has a test case and is working
quite reliable. Addressing (SSN) is achieved with something like a
sockaddr and it is mostly following the socket semantic. Instead of
accept and select I do have callbacks... this might change in the
future.
- There is no MTP* implementation in the code base...
- The one "problem" with it is the memcpy... and "queuing" inside the
code but both will be addressed over time.
on-waves/gsm0808:
- This is the current BSC app and GSM080 (BSSMAP/DTAP) code..
- This branch will rename the bssap.c to gsm_08_08.c and remove
all traces of SCCP from it, some code will move from bsc_msc_ip.c
to the bssap.
- an API will be created that can be used by the bsc_msc_ip.c and
the bsc_hack.c/gsm_04_08.c code.
- In terms of OpenBSC I want this to be done after the congress to not
create a mess right now.
on-waves/bsc-master:
- This will be my release branch. I will pull from the three branches, update
version, put in hacks, or short term things that are necessary.
- Think of it as a incubator for "master"
as there is little danger of breaking things I have merged the MGCP and SCCP
branches into master as well. I hope there is agreement (otherwise there is
always git revert)
z.
Hello
Sorry for my ignorance but I am a complete newbie to the OpenBSC. We are
trying to run the OpenBSC with the nanoBTS as an university project.
I have tried to follow the step by step instructions from the OpenBSC
wiki page (both Debian_Getting_Started and OpenBSC_LCR) but I have faced
some problems during the LCR installation. I am putting a whole
installation screen below because I am not sure which part of it might
be relevant for diagnosing the problem.
We have also tried this on 2.6.27.4 and 2.6.29.1 linux kernel versions
(both with mISDN modules included, at least we believe so) and both gave
the same problem..
I would really appreciate any suggestion for solving the problem.
Thanks in advance.
Sorry for some polish parts in it but it is due to our Debian version...
----------------------------------------------------------------------------
user@pc1123:~$ cd lcr
user@pc1123:~/lcr$ sh autogen.sh
autom4te: cannot open autom4te.cache/requests: Brak dostępu
aclocal: autom4te failed with exit status: 1
autom4te: cannot open autom4te.cache/requests: Brak dostępu
autoheader: '/usr/bin/autom4te' failed with exit status: 1
autom4te: cannot open autom4te.cache/requests: Permission denied
automake: autoconf failed with exit status: 1
autom4te: cannot open autom4te.cache/requests: Permission denied
user@pc1123:~/lcr$ su
Hasło:
pc1123:/home/user/lcr# $ ./configure --prefix=/opt/lcr --with-asterisk
--with-gsm
bash: $: command not found
pc1123:/home/user/lcr# $ ./configure --prefix=/opt/lcr --with-asterisk
--with-gsm
bash: $: command not found
pc1123:/home/user/lcr# ./configure --prefix=/opt/lcr --with-asterisk
--with-gsm
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking asterisk/compiler.h usability... yes
checking asterisk/compiler.h presence... yes
checking for asterisk/compiler.h... yes
checking openssl/rsa.h usability... no
checking openssl/rsa.h presence... no
checking for openssl/rsa.h... no
checking for main in -lcrypto... no
checking for openbsc/include/openbsc/gsm_data.h... yes
checking for main in -lm... yes
checking for main in -lncurses... yes
checking for main in -lpthread... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking mISDNuser/mbuffer.h usability... no
checking mISDNuser/mbuffer.h presence... no
checking for mISDNuser/mbuffer.h... no
checking for assert.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for pid_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking whether gcc needs -traditional... no
checking whether lstat dereferences a symlink specified with a trailing
slash... yes
checking whether lstat accepts an empty string... no
checking whether lstat dereferences a symlink specified with a trailing
slash... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking return type of signal handlers... void
checking for AIX... no
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for working strnlen... yes
checking for working strtod... yes
checking for vprintf... yes
checking for _doprnt... no
checking for gettimeofday... yes
checking for memmove... yes
checking for memset... yes
checking for mkdir... yes
checking for socket... yes
checking for strcasecmp... yes
checking for strchr... yes
checking for strerror... yes
checking for strncasecmp... yes
checking for strstr... yes
checking for strtol... yes
checking for strtoul... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
pc1123:/home/user/lcr# make
make all-am
make[1]: Wejście do katalogu `/home/user/lcr'
g++ -DHAVE_CONFIG_H -I. -DWITH_GSM -I./openbsc/include -Wall
-I/usr/include/mISDNuser -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 main.h:135,
from gsm.cpp:12:
/usr/local/include/mbuffer.h:18:21: error: global.h: Nie ma takiego
pliku ani katalogu
/usr/local/include/mbuffer.h:19:29: error: enc_statistics.h: Nie ma
takiego pliku ani katalogu
In file included from main.h:135,
from gsm.cpp:12:
/usr/local/include/mbuffer.h:32: error: 'PictureStructure' does not name
a type
/usr/local/include/mbuffer.h:39: error: 'int64' does not name a type
/usr/local/include/mbuffer.h:40: error: 'int64' does not name a type
/usr/local/include/mbuffer.h:41: error: 'int64' does not name a type
/usr/local/include/mbuffer.h:42: error: 'int64' does not name a type
/usr/local/include/mbuffer.h:48: error: 'byte' does not name a type
/usr/local/include/mbuffer.h:61: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:62: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:63: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:64: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:67: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:68: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:69: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:71: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:73: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:74: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:75: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:76: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:79: error: 'PicMotionParams' does not name
a type
/usr/local/include/mbuffer.h:80: error: 'PicMotionParams' does not name
a type
/usr/local/include/mbuffer.h:101: error: 'StatParameters' does not name
a type
/usr/local/include/mbuffer.h:111: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:114: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:122: error: 'byte' does not name a type
/usr/local/include/mbuffer.h:160: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:161: error: expected ';' before '*' token
/usr/local/include/mbuffer.h:179: error: variable or field 'init_dpb'
declared void
/usr/local/include/mbuffer.h:179: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:179: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:179: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:179: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:179: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:179: error: 'dpb' was not declared in this
scope
/usr/local/include/mbuffer.h:180: error: variable or field 'free_dpb'
declared void
/usr/local/include/mbuffer.h:180: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:180: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:180: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:180: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:180: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:180: error: 'dpb' was not declared in this
scope
/usr/local/include/mbuffer.h:182: error: variable or field
'free_frame_store' declared void
/usr/local/include/mbuffer.h:182: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:182: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:182: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:182: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:182: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:182: error: 'f' was not declared in this
scope
/usr/local/include/mbuffer.h:183: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:183: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:183: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:183: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:183: error: 'PictureStructure' was not
declared in this scope
/usr/local/include/mbuffer.h:183: error: expected primary-expression
before 'int'
/usr/local/include/mbuffer.h:183: error: expected primary-expression
before 'int'
/usr/local/include/mbuffer.h:183: error: expected primary-expression
before 'int'
/usr/local/include/mbuffer.h:183: error: expected primary-expression
before 'int'
/usr/local/include/mbuffer.h:183: error: initializer expression list
treated as compound expression
/usr/local/include/mbuffer.h:184: error: variable or field
'free_storable_picture' declared void
/usr/local/include/mbuffer.h:184: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:184: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:184: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:184: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:184: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:184: error: 'p' was not declared in this
scope
/usr/local/include/mbuffer.h:185: error: variable or field
'store_picture_in_dpb' declared void
/usr/local/include/mbuffer.h:185: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:185: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:185: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:185: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:185: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:185: error: 'p' was not declared in this
scope
/usr/local/include/mbuffer.h:185: error: 'FrameFormat' was not declared
in this scope
/usr/local/include/mbuffer.h:185: error: 'output' was not declared in
this scope
/usr/local/include/mbuffer.h:186: error: variable or field
'replace_top_pic_with_frame' declared void
/usr/local/include/mbuffer.h:186: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:186: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:186: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:186: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:186: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:186: error: 'p' was not declared in this
scope
/usr/local/include/mbuffer.h:186: error: 'FrameFormat' was not declared
in this scope
/usr/local/include/mbuffer.h:186: error: 'output' was not declared in
this scope
/usr/local/include/mbuffer.h:187: error: variable or field 'flush_dpb'
declared void
/usr/local/include/mbuffer.h:187: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:187: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:187: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:187: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:187: error: 'FrameFormat' was not declared
in this scope
/usr/local/include/mbuffer.h:187: error: 'output' was not declared in
this scope
/usr/local/include/mbuffer.h:188: error: variable or field
'dpb_split_field' declared void
/usr/local/include/mbuffer.h:188: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:188: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:188: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:188: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:188: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:188: error: 'fs' was not declared in this
scope
/usr/local/include/mbuffer.h:189: error: variable or field
'dpb_combine_field' declared void
/usr/local/include/mbuffer.h:189: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:189: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:189: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:189: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:189: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:189: error: 'fs' was not declared in this
scope
/usr/local/include/mbuffer.h:190: error: variable or field
'dpb_combine_field_yuv' declared void
/usr/local/include/mbuffer.h:190: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:190: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:190: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:190: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:190: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:190: error: 'fs' was not declared in this
scope
/usr/local/include/mbuffer.h:191: error: variable or field 'init_lists'
declared void
/usr/local/include/mbuffer.h:191: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:191: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:192: error: variable or field
'reorder_ref_pic_list' declared void
/usr/local/include/mbuffer.h:192: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:192: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:192: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:192: error: 'list' was not declared in this
scope
/usr/local/include/mbuffer.h:192: error: expected primary-expression
before 'char'
/usr/local/include/mbuffer.h:192: error: expected primary-expression
before 'int'
/usr/local/include/mbuffer.h:193: error: variable or field
'init_mbaff_lists' declared void
/usr/local/include/mbuffer.h:193: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:193: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:194: error: variable or field
'alloc_ref_pic_list_reordering_buffer' declared void
/usr/local/include/mbuffer.h:194: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:194: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:195: error: variable or field
'free_ref_pic_list_reordering_buffer' declared void
/usr/local/include/mbuffer.h:195: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:195: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:196: error: variable or field
'fill_frame_num_gap' declared void
/usr/local/include/mbuffer.h:196: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:196: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:196: error: 'InputParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:196: error: 'p_Inp' was not declared in
this scope
/usr/local/include/mbuffer.h:196: error: 'FrameFormat' was not declared
in this scope
/usr/local/include/mbuffer.h:196: error: 'output' was not declared in
this scope
/usr/local/include/mbuffer.h:199: error: variable or field
'compute_colocated' declared void
/usr/local/include/mbuffer.h:199: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:199: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:199: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:199: error: 'p' was not declared in this
scope
/usr/local/include/mbuffer.h:199: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:199: error: 'listX' was not declared in
this scope
/usr/local/include/mbuffer.h:202: error: variable or field
'compute_colocated_JV' declared void
/usr/local/include/mbuffer.h:202: error: 'Slice' was not declared in
this scope
/usr/local/include/mbuffer.h:202: error: 'currSlice' was not declared in
this scope
/usr/local/include/mbuffer.h:202: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:202: error: 'p' was not declared in this
scope
/usr/local/include/mbuffer.h:202: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:202: error: 'listX' was not declared in
this scope
/usr/local/include/mbuffer.h:203: error: variable or field
'copy_storable_param_JV' declared void
/usr/local/include/mbuffer.h:203: error: 'ImageParameters' was not
declared in this scope
/usr/local/include/mbuffer.h:203: error: 'p_Img' was not declared in
this scope
/usr/local/include/mbuffer.h:203: error: expected primary-expression
before 'int'
/usr/local/include/mbuffer.h:203: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:203: error: 'd' was not declared in this
scope
/usr/local/include/mbuffer.h:203: error: expected primary-expression
before '*' token
/usr/local/include/mbuffer.h:203: error: 's' was not declared in this
scope
In file included from main.h:150,
from gsm.cpp:12:
mISDN.h:57: error: field 'upqueue' has incomplete type
gsm.cpp: In member function 'int Pgsm::bchannel_open(int)':
gsm.cpp:135: error: aggregate 'sockaddr_mISDN addr' has incomplete type
and cannot be defined
gsm.cpp:136: error: aggregate 'mISDNhead act' has incomplete type and
cannot be defined
gsm.cpp:144: error: 'ISDN_P_B_RAW' was not declared in this scope
gsm.cpp:171: error: 'PH_ACTIVATE_REQ' was not declared in this scope
gsm.cpp:173: error: 'MISDN_HEADER_LEN' was not declared in this scope
gsm.cpp: In member function 'void Pgsm::bchannel_send(unsigned int,
unsigned int, unsigned char*, int)':
gsm.cpp:240: error: 'MISDN_HEADER_LEN' was not declared in this scope
gsm.cpp:241: error: 'buf' was not declared in this scope
gsm.cpp:248: error: invalid use of incomplete type 'struct mISDNhead'
mISDN.h:117: error: forward declaration of 'struct mISDNhead'
gsm.cpp:248: error: 'PH_DATA_REQ' was not declared in this scope
gsm.cpp:249: error: invalid use of incomplete type 'struct mISDNhead'
mISDN.h:117: error: forward declaration of 'struct mISDNhead'
gsm.cpp: In member function 'void Pgsm::trau_receive(void*)':
gsm.cpp:312: error: 'PH_DATA_REQ' was not declared in this scope
gsm.cpp: In member function 'virtual int Pgsm::handler()':
gsm.cpp:1486: error: 'MISDN_HEADER_LEN' was not declared in this scope
gsm.cpp:1487: error: 'buffer' was not declared in this scope
gsm.cpp:1502: error: invalid use of incomplete type 'struct mISDNhead'
mISDN.h:117: error: forward declaration of 'struct mISDNhead'
gsm.cpp:1504: error: 'PH_DATA_CNF' was not declared in this scope
gsm.cpp:1507: error: 'PH_DATA_IND' was not declared in this scope
gsm.cpp:1510: error: 'PH_ACTIVATE_IND' was not declared in this scope
gsm.cpp:1513: error: 'PH_DEACTIVATE_IND' was not declared in this scope
gsm.cpp: In function 'int gsm_sock_open(char*)':
gsm.cpp:1554: error: aggregate 'sockaddr_mISDN addr' has incomplete type
and cannot be defined
gsm.cpp:1555: error: aggregate 'mISDN_devinfo devinfo' has incomplete
type and cannot be defined
gsm.cpp:1559: error: 'IMGETCOUNT' was not declared in this scope
gsm.cpp:1577: error: 'IMGETDEVINFO' was not declared in this scope
gsm.cpp:1582: error: 'ISDN_P_TE_S0' was not declared in this scope
gsm.cpp:1585: error: 'ISDN_P_TE_E1' was not declared in this scope
gsm.cpp:1592: error: 'ISDN_P_TE_S0' was not declared in this scope
make[1]: *** [gsm.o] Błąd 1
make[1]: Opuszczenie katalogu `/home/user/lcr'
make: *** [all] Błąd 2
------------------------------------------------------------------------------------------
Hi,
I was wondering if anyone heard of a nanoBTS without EFR support ?
I have one here that responds with BIND_NACK if the codec is EFR but
works ok if I set V1
Sylvain
Hi all,
I have written this small patch yesterday. It is removing the "auto release"
after timeout from lchan and will directly release the channel ones the ref
count drops to zero.
This means that any use of the lchan after a put_lchan is illegal (the code
using a timeout used to workaround this issue). I have changed three call
sites to follow this convention, I have added a BUG_ON into the abis_rsl
method.
From a quick test (Location Updating Request and a call) the BUG_ON in the
abis_rsl.c is hit by:
- The lchan release code (okay... a false warning and avoided by
increasing use_count and decreasing it...)
- CM Service Request Ack and such is sent without anyone holding
a reference to it. I think this warning is safe to ignore for now as
no one has simply claimed the channel. I plan to fix this in
January/February when moving our MSC code over to the On Waves
BSC abstraction.
The benefit of this change is that we free our channels a lot earlier. I think
this change would be beneficial for the 26C3 and I would like to hear opinions
and see some testing with it.
regards
z.
Hi Harald,
I have one problem with the BTS on cold start. OpenBSC is sending the RSL
connect, Radio Carrier/Baseband attributes too early and we are receiving
NACKs from the BTS and the RSL link is never established.
The first question is if others have seen this problem? I have solved the
problem my moving the OP start/set attributes/RSL connect of the RC and
Baseband out of the state change code into the "Software Activated Report".
Doing a quick check it seems to still work and solve my cold start problem. Do
you think this is a legitimate workaround for the problem right now?
In the future we probably should attempt to have a better state machine,
report errors, retry and such things...
regards
holger
this patch fixes double free of paging request.
the function paging_T3113_expired() must call paging_remove_request()
first. then the cbfn may be called. the cbfn function cannot eventually
remove the paging request again, because it is not in the list anymore.
the result of paging timeout was a crash.
diff --git a/openbsc/src/paging.c b/openbsc/src/paging.c
index 5a9643c..164a08b 100644
--- a/openbsc/src/paging.c
+++ b/openbsc/src/paging.c
@@ -224,11 +243,13 @@ static void paging_T3113_expired(void *data)
sig_data.bts = req->bts;
sig_data.lchan = NULL;
+ /* must be destroyed before calling cbfn, to prevent double free
*/
+ paging_remove_request(&req->bts->paging, req);
+
dispatch_signal(SS_PAGING, S_PAGING_COMPLETED, &sig_data);
if (req->cbfn)
req->cbfn(GSM_HOOK_RR_PAGING, GSM_PAGING_EXPIRED, NULL,
NULL,
req->cbfn_param);
- paging_remove_request(&req->bts->paging, req);
}
static int _paging_request(struct gsm_bts *bts, struct gsm_subscriber
*subscr,
Hi,
Does anyone see a reason why callref would be cleared in gsm48_cc_tx_release ?
That prevents proper dispatch of the subsequent REL_CNF (since
trans->callref is now 0) and I don't really see what was the intent in
putting it there ?
Sylvain
this patch will correct some callref behavior.
if a message with an unknown callref is received, a release is sent to
the other layer.
if a release with an unknown callref is received, it is ignored.
no message is sent, if the callref is already gone.
diff --git a/openbsc/src/gsm_04_08.c b/openbsc/src/gsm_04_08.c
index d6e161a..3f12546 100644
--- a/openbsc/src/gsm_04_08.c
+++ b/openbsc/src/gsm_04_08.c
@@ -1705,6 +1705,10 @@ static int mncc_recvmsg(struct gsm_network *net,
struct gsm_trans *trans,
{
struct msgb *msg;
+ /* don't send message, if call is not associated anymore */
+ if (!mncc->callref)
+ return 0;
+
if (trans)
if (trans->lchan)
DEBUGP(DCC, "(bts %d trx %d ts %d ti %x sub %s)
"
@@ -3242,10 +3246,12 @@ int mncc_send(struct gsm_network *net, int
msg_type, void *arg)
if (!trans) {
struct gsm_subscriber *subscr;
+ if (msg_type == MNCC_REL_REQ)
+ return 0; /* drop */
if (msg_type != MNCC_SETUP_REQ) {
DEBUGP(DCC, "(bts - trx - ts - ti -- sub %s) "
"Received '%s' from MNCC with "
- "unknown callref %d\n",
data->called.number,
+ "unknown callref %x\n",
data->called.number,
get_mncc_name(msg_type), data->callref);
/* Invalid call reference */
return mncc_release_ind(net, NULL,
data->callref,
diff --git a/openbsc/src/mncc.c b/openbsc/src/mncc.c
index f62541c..1874750 100644
--- a/openbsc/src/mncc.c
+++ b/openbsc/src/mncc.c
@@ -301,8 +301,20 @@ int mncc_recv(struct gsm_network *net, int
msg_type, void *arg)
/* create callref, if setup is received */
if (!call) {
- if (msg_type != MNCC_SETUP_IND)
+ if (msg_type == MNCC_REL_IND)
return 0; /* drop */
+ if (msg_type != MNCC_SETUP_IND) {
+ struct gsm_mncc rel;
+
+ DEBUGP(DMNCC, "(call %x) Rejecting message %s
with unknown ref.\n",
+ callref, get_mncc_name(msg_type));
+ memset(&rel, 0, sizeof(struct gsm_mncc));
+ rel.callref = callref;
+ mncc_set_cause(&rel, GSM48_CAUSE_LOC_PRN_S_LU,
+ GSM48_CC_CAUSE_INVAL_TRANS_ID);
+ mncc_send(net, MNCC_REL_REQ, &rel);
+ return 0;
+ }
/* create call */
if (!(call = talloc_zero(tall_call_ctx, struct
gsm_call))) {
struct gsm_mncc rel;
Me2
It is always the case with BS11:
- boot BS11 (until finished)
- run bsc_hack
(not working)
- run bsc_hack again
(working)
-----Ursprüngliche Nachricht-----
Von: openbsc-bounces(a)lists.gnumonks.org [mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Bjoern Heller
Gesendet: Mittwoch, 18. November 2009 12:22
An: Holger Freyther
Cc: openbsc(a)lists.gnumonks.org
Betreff: Re: [RFC] nanoBTS startup sequence (problems on coldstart)
Me2.
Need to restart bsc_hack the first time after nanobts coldboot.
Best Regards
Björn Heller
Hello :)
Now I've implemented the TP-VPF-ENHANCED. To achieve that I added some
goto-stuff - i hope that's ok. I think it makes sense here.
It's again untested, but compiles fine. I'm working at the moment on a
way to test SMS-PDU decoding.
If that's easier you can simply merge the branch tp-vp from
git://github.com/stefreak/openbsc.git :)
The patch is attached.
Greetings,
Steffen
Hello Holger,
On Sat, 14 Nov 2009 19:45:43 +0100, "Holger Freyther" <zecke(a)selfish.org> wrote:
>
> Good question. I think Dieter knows this best. We have two options that
> influence the transmit power. One is the power a mobile station should use to
> communicate with us ("ms max power") and then something I don't know
> ("max_power_red") but we do have links to the spec in the vty_interface.c
"max_power_red" is the power used by the BTS, it reduces the maximum
power by a certain amount. Those are the results from a measurement
I already posted a while ago to the list:
nanoBTS 1800, ARCN 840, no voice/data traffic:
NM_ATT_RF_MAXPOWR_R RF output
0 20 dBm
1 18 dBm
2 16 dBm
4 12 dBm
8 4.4 dBm
9 2.0 dBm
10 0.4 dBm
11 -1.6 dBm
12 -3.6 dBm
Please be aware that the value "max_power_red" from the config file
is divided by two to get NM_ATT_RF_MAXPOWR_R ("max_power_red" is the
actual reduction in dB).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
i am not sure, if the variables bts and trx will be used in the future, so i left them as comments.
-----Ursprüngliche Nachricht-----
Von: openbsc-bounces(a)lists.gnumonks.org [mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Holger Freyther
Gesendet: Dienstag, 17. November 2009 10:20
An: openbsc(a)lists.gnumonks.org
Betreff: Re: patch: fix of compiler warnings
On Monday 16 November 2009 18:52:32 Andreas.Eversberg wrote:
> diff --git a/openbsc/src/bsc_init.c b/openbsc/src/bsc_init.c
> index 815fe2b..3b451b1 100644
> --- a/openbsc/src/bsc_init.c
> +++ b/openbsc/src/bsc_init.c
> @@ -433,8 +433,8 @@ int nm_state_event(enum nm_evt evt, u_int8_t
> obj_class, void *obj,
> static int sw_activ_rep(struct msgb *mb)
> {
> struct abis_om_fom_hdr *foh = msgb_l3(mb);
> - struct gsm_bts *bts = mb->trx->bts;
> - struct gsm_bts_trx *trx = gsm_bts_trx_num(bts,
> foh->obj_inst.trx_nr);
> +// struct gsm_bts *bts = mb->trx->bts;
> +// struct gsm_bts_trx *trx = gsm_bts_trx_num(bts,
> foh->obj_inst.trx_nr);
was this intentional? Is the warning that these are unused? In this case we
will just nuke the variable declaration.
hi,
one of my nokia phones 6310i:
V 04.20
04-03-02
NPE-4
(c) NPM.
when the subscriber is paged, the phone will answer with
"CHREQ_T_PAG_R_ANY" value (ra=0x83). because the phone does not tell use
what it wants, i must assume that there may be a need for a traffic
channel. without this patch, the call will be made with wrong channel
type:
<0200> paging.c:113 Going to send paging commands: imsi:
'262XXXXXXXXXXX' tmsi: '0x3044ea7a'
<0010> abis_rsl.c:1179 Activating ARFCN(121) TS(0) SS(0) lctype SDCCH
chan_nr=0x20 r=PAGING ra=0x83
can we figure out which subscriber did the channel request? if so, we
can check what channel type is required. (we can look through the
transactions and select the required channel type. if a transaction with
higher rate is paging, we can assign this channel type.)
any ideas?
regards,
andreas
diff --git a/openbsc/src/gsm_04_08_utils.c
b/openbsc/src/gsm_04_08_utils.c
index 6ffb109..2c30d13 100644
--- a/openbsc/src/gsm_04_08_utils.c
+++ b/openbsc/src/gsm_04_08_utils.c
@@ -283,7 +283,7 @@ static const enum gsm_chan_t ctype_by_chreq[] = {
[CHREQ_T_VOICE_CALL_TCH_H] = GSM_LCHAN_TCH_H,
[CHREQ_T_DATA_CALL_TCH_H] = GSM_LCHAN_TCH_H,
[CHREQ_T_LOCATION_UPD] = GSM_LCHAN_SDCCH,
- [CHREQ_T_PAG_R_ANY] = GSM_LCHAN_SDCCH,
+ [CHREQ_T_PAG_R_ANY] = GSM_LCHAN_TCH_F,
[CHREQ_T_PAG_R_TCH_F] = GSM_LCHAN_TCH_F,
[CHREQ_T_PAG_R_TCH_FH] = GSM_LCHAN_TCH_F,
};
this patches fixes the generation of the config file.
after saving of configuration, no location update was possible anymore.
it is self explaining...
diff --git a/openbsc/src/vty_interface.c b/openbsc/src/vty_interface.c
index 9aa9706..c6e60c0 100644
--- a/openbsc/src/vty_interface.c
+++ b/openbsc/src/vty_interface.c
@@ -784,7 +784,7 @@ DEFUN(cfg_net_encryption,
"encryption a5 (0|1|2)",
"Enable or disable encryption (A5) for this network\n")
{
- gsmnet->auth_policy = atoi(argv[0]);
+ gsmnet->a5_encryption = atoi(argv[0]);
return CMD_SUCCESS;
}
hi,
i did may tests with the "holger/subscr-ref-handling" branch. i had no
subscriber usage leak within may hours of testing. about hunded calls
were made with many out-of-range failures, hold/retrieve, and battery
removal during call. at the end, all subscribers usage returned back to
0.
i did not test SMS, just location updates and voice calls.
regards,
andreas
Hi!
I've applied a series of fixes and extensions to the GPRS branch, and
would like to invited interested nanoBTS users to give it another try.
Right now, I am getting fully through GPRS routing area update and attach
request, i.e. the phones can fully register to the GPRS network.
Minimal PDP context activation and deactivation has been implemented, i.e.
the phone will send a ACTIVATE PDP CONTEXT REQUEST, and the network will
simply ACK it. However, since the network does not add any IPCP options,
the phone will typically DEACTIVATE the context immediately after that.
Have fun,
--
- 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,
I am trying to compile the source code but, I am stuck with the dbi.h
header file. Where can I get this include file so that I can
successfully compile ?
N.
Hi,
I am following instruction from this page :
http://openbsc.gnumonks.org/trac/wiki/Debian_Getting_Started
When I do make menuconfig I get to the point until I have to select the
mISDN modules. Firstly, I had to download the 2.6.31.6 kernel which is
different as described in the page above. And, secondly, when I do
select (based on the best 'guess'), there is no change at all ! I am
forced to select 'Exit' - it does not proceed further.
Is there anything you would like to suggest ?
I am running minimal Ubuntu Linux
(https://help.ubuntu.com/community/Installation/MinimalCD) as a guest OS
using VirtualBox hosted on Ubuntu 9.10.
N.
Hi,
Your tutorial on getting started with Debian system is good. Once
the installation is over, what tests would you suggest to know the
system is ok ? Similarly, how would one ensure that the machine running
OpenBSC is talking nice with the BTS ?
N
Never mind, I think, I found it.
http://bs11-abis.gnumonks.org/trac/wiki/BS11_Getting_Started
Thanks !
-------- Forwarded Message --------
From: ನಾಗೇಶ್ <openbscuser(a)gmail.com>
Reply-to: openbscuser(a)gmail.com
To: openbsc <openbsc(a)lists.gnumonks.org>
Subject: Testing an OpenBSC installation.
Date: Thu, 12 Nov 2009 23:24:32 +0530
Hi,
Your tutorial on getting started with Debian system is good. Once
the installation is over, what tests would you suggest to know the
system is ok ? Similarly, how would one ensure that the machine running
OpenBSC is talking nice with the BTS ?
N
Hey,
I think in the next days I will go around the sourcecode and change a couple
of logging messages. My two primary goals are increase the usefulness to figure
out what was going wrong and the second to be able to put some of these into
the syslog. Should we use DEBUG* to also log to syslog or introduce a new set
of macros?
Log Levels:
I think Harald has expressed the wish to introduce log levels. Should we
follow the log levels of syslog(3)?
Messages:
I would like to collect formats for various actions. Currently I'm thinking of
the following but would like to have more input.
subscriber:
When talking about a subscriber use TMSI, IMSI and Extension.
lchan:
Include refcount, channel type, link_id, subscriber
sccp:
Talk about SCCP source local reference and pointer
transaction:
Print the transaction?
gsm0408:
Print the lchan which prints the subscriber?
comments?
holger
From: Steffen Neubauer <stefreak(a)stefreak.de>
- Added function "gsm340_scts" to decode the service center time stamp
into a UTC/GMT timestamp
- in function gsm340_validity_period: can now decode validity period
format absolute.
I hope it's good ;)
Greetings,
Steffen
Hello guys,
If I run the latest version of openbsc and tried to register with my MS
(Nokia 6310) to it, my phone finally says No Access.
I see sending Channel Release several time in the debugging output. I
also see increase/decrease usage several time. It has been a while not
looking at the meaning of debug messages. I just use the standard config
file for nanobts and changed a few parameters like unit_id, band, mcc
and mnc, that's all. I noticed that I can't add an accept parameter,
like before. Also in the config file I can't find anything like that, am
I missing something?
kind regards,
nordin.
Hello Harald,
On Mon, 2 Nov 2009 22:47:18 +0900, "Harald Welte" <laforge(a)gnumonks.org> wrote:
>
> This is actually very funny. According to the protocol, a RA update should
> only be performed if the MS was/is already GPRS ATTACHED to this network
> before. It clearly wasn't in this case, as the OpenBSC network never
> offered GPRS support. Still, it tries it. That's why we're rejecting it.
Not sure if I understand it in detail, from my understanding an RA Update
is performed when the Routing Area has changed (or the periodic RA update
timer has expired). So if the phone is already attached to a network,
shouldn't we receive the RA update if it selects our new RA ?
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello,
I never used it much, but when I try to send an SMS
from a MS to another one it is not delivered to the second MS.
OpenBSC displays that the SMS was received.
If I do a Location Update on the second Phone the SMS gets delivered.
Also if I enter the command "sms send pending".
How can I setup automatic delivery?
Am I right, that OpenBSC first looks, if the second subscriber is
connected
to the network and then delivers the message?
regards
Bjoern
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Björn Heller
Jabber: tec(a)jabber.hellercom.de
Hi!
Since the current two main developers of OpenBSC (Holger and myself) are
travelling almost all the time and not in the vicinity of a BS-11, I fear
that we sometimes might introduce code that is incompatible with the BS-11
or introduces regressions on it.
Threfore, I would like to see if there are any volunteers here who are willing
to regularly check out the latest code and test it if it still works on their
BS-11.
Anyone?
Thanks in advance,
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)
Got it ;)
Voice-calls working.
Thanks everyone!!!
Best Regards
Björn Heller
Am 05.11.2009 um 13:02 schrieb Holger Freyther <zecke(a)selfish.org>:
> On Thursday 05 November 2009 12:50:32 Bjoern Heller wrote:
>> Ok, found the BTS, but
>> in ipaccess config I get a "no matching signalling link for hh-
>>
>>> proto=0xff" back. I used the command from the wiki...
>
>
> update the source? I fixed that last week.
>
> z.
>
>
Hello everybody!
Got my ip.access today by mail! *happy.
Is there any configuration tool for it?
Or how do I configure it to listen on an specific IP?
Best Regards
Björn Heller
Hello Sylvain,
On Tue, 03 Nov 2009 07:03:15 +0000, 246tnt(a)gmail.com wrote:
>
> Initially I had a segfault when receiving a GMM ATTACH. The MCC/MNC in the
> CELL ID transmitted in the GMM ATTACH REQUEST are not the one I set in
> openbsc.cfg, they seem hardcoded to 001/01 but I haven't found from where
> yet. So currently you need to set 1/1 in your openbsc.cfg as well.
Its in bsc_init.c, the variable "nanobts_attr_bts":
NM_ATT_IPACC_CGI, 0, 7, 0x00, 0xf1, 0x10, 0x00, 0x01, 0x00, 0x00,
I did modify patch_nm_tables() and added:
// this overwrites nanobts_attr_bts[54], but we set it later anyway
gsm48_ra_id_by_bts(&nanobts_attr_bts[49], bts);
nanobts_attr_bts[54] = htons(bts->cell_identity) & 0xFF;
nanobts_attr_bts[55] = (htons(bts->cell_identity) >> 8) & 0xFF;
Additionally I fixed setting the BSIC:
nanobts_attr_bts[45] = bts->bsic;
I have not yet provided a patch because its not fully tested,
however Harald is informed.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Sylvain,
On Mon, 2 Nov 2009 01:05:20 +0100, "Sylvain Munaut" <246tnt(a)gmail.com> wrote:
>
> I found out the problem.
>
> In gprs_bssgp_tx_dl_ud, then length encoded in the PDU TLV is
> incorect. It uses msg->len but at that point it already did a
> msgb_push to add space for the header so msg->len is already too big.
> You need to save the size of msg->len before the msgb_push and then
> use that when encoding the PDU TLV length.
Thanks for the info, I tried it here but it did not help for the
"GMM ATTACH REQUEST", the nanoBTS still reboots when it receives
the data of the "GPRS IDENTITY REQUEST" which is sent afterwards.
I finally found the reason for this behaviour (at least I hope
it is the reason), I had to specify the correct BVCI parameter
for the call to gprs_ns_sendmsg() in gprs_bssgp_tx_dl_ud(). If
I use "925" instead of "0" it works. The phone sends an "GMM
IDENITY RESPONSE" and continues to send "GMM ATTACH REQUEST"
because it does not yet receive an accept.
> BTW, do you sometimes hangout in #openbsc ?
No, usually not (its a bit difficult for me to do my work and
look at what is happing on IRC).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Dear Tim!
I hope you don't mind I'm Cc'ing the mailing list. This means that other
people can get involved in the discussion - and also means that I only
have to write my summary about what needs to be done once, even if you
for some reason are unable to complete the actual implementation :)
On Mon, Nov 02, 2009 at 01:25:13PM -0500, Newman, Timothy wrote:
> I'm working at Virginia Tech and it looks like we are going to start playing
> with the cell broadcast gsm stuff. I'd like to just go ahead and add it into
> openbsc.
This is great news, thanks. Which BTS type are you using with OpenBSC?
> Other than the brief read through of some of the 3GPP documents related to
> cell broadcast, I'm not too familiar with the interworkings of it.
It's not really difficult. What needs to be done
1) enable a channel configuration that adds a CBCH to one of the SDCCH/4 in
a combined CCCH, or one of the SDCCH/8. I'd prefer the SDCCH/4, since
that is supported by both BS-11 and nanoBTS. However, feel free to implement
both options
2) encode the CBCH message (very similar to SMS encoding) TS 03.38 / 03.41
3) have a function to send the CBCH to the BTS over RSL (TS 08.58)
4) later: Implement the Scheduling (Chapter 2.1 of TS 04.12) for DRX
There's two options for cell broadcast:
1) you can set a default cell broadcast message once by the BSC. The BTS then
transmit that CB in every idle fame of the CBCH (TS 08.58 SMS BROADCAST CMD)
2) you want to sent multiple different CB messages, then the BSC needs to do
the scheduling and send them to the BTS's (TS 08.58 SMS BROADCAST REQ)
> I'm a little unclear how long this may take to add this functionality into
> openbsc. If you had to estimate how long it would take (e.g. 1, 2, 6, 12
> months), what would you say? Just give me your estimate and I'll multiply
> this by 4 because it will be students working on the project and they need a
> little (a lot) of ramp of time for this also.
If I or any other of the OpenBSC developers was doing it, I would say this is a
matter of days, one week max for all of the options described above. However,
you need to consider that your studends also have to read up the 3GPP specs,
are unfamiliar with the terminlology, don't know the OpenBSC codebase, probably
have not that much experience with "plain C" programming in an select-loop single
threaded design, ... so a factor of four might not be sufficient.
Regards,
Harald
p.s.: I would be interested in learning what you're using OpenBSC for at
Virginia Tech. If you have a minute to elaborate on that, I'm very curious.
Other people on the mailing list might share that interest, especially those
users from academic institutions. If you prefer to respond privately, that
would also be OK with me.
--
- 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)
Special offer for the last nanoBTS type 139,
Siemens (MOGIS) branded, new in box, but without POE-Adapter!
Only one available, only 1900 Euro plus shipment.
Contact me at womax(at)gmx(dot)ch