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
Hello
Our goal was to send status sms via the vty interface. But all of our
sms were cropped. In contrast sms from one MS to another MS are
displayed correctly (despite the fact, that the text at the database
contains several '@' at the end / the user_data contains several
zero-octets). Therefore i have inspect the code and found several bugs.
The main problem is that the "user_data_len" is not correctly used. As
per GSM 03.40, 9.2.3.16 TP‑User‑Data‑Length (TP‑UDL):
"If the TP‑User‑Data is coded using the GSM 7 bit default alphabet, the
TP‑User‑Data‑Length field gives an integer representation of the number
of septets within the TP‑User‑Data field to follow."
Currently the "user_data_len" contains the number of octets (returned
from gsm_7bit_encode(...) at gsm_utils.c (libosmocore)).
The big problem here is that this information is not unique, e.g.:
1.) 46 non-extension characters + 1 extension character => (46 * 7 bit +
(1 * (2 * 7 bit))) / 8 bit = 42 octets
2.) 47 non-extension characters => (47 * 7 bit) / 8 bit = 41,125 = 42 octets
3.) 48 non-extension characters => (48 * 7 bit) / 8 bit = 42 octects
But the MS has to know the correct "user_data_len" to decode the correct
number of characters.
For this reason i updated the gsm_7bit_encode() function to return the
correct number of septets. However sometimes it is needed to know the
correct number of octets (e.g. at gsm_04_11.c: gsm340_gen_tpdu(...)) =>
i added a function to gsm_utils.c named:
uint8_t get_octet_len(const uint8_t sept_len)
I have also fixed the problem, that the sms are wrongly stored /
displayed on the database. But the solution on the function
*sms_from_result(...) (at db.c) is not really "beautiful". This is
because there exists no "user_data_len" field at the database. To store
the right value for "user_data_len" (which is further needed) i have to
get the length from the "text" field. Unfortunately this is not enough.
If the text contains extension characters like {[]} etc. then the
"user_data_len" has to be bigger because these characters needs two
septets. Therefore i use a switch statement so search for these
characters. A better solution for that is to store the right
"user_data_len" to the database (on the encoding / decoding procedure).
But i don't know if this is a suitable solution for all of you (because
you have to change your database structure etc.).
Best Regards
Dennis Wehrle
Hi all,
so far we do not have any statement about the licensing of the content on
our wiki. This means the default copyright rules apply: All the content is
copyrighted, and nobody has any rgiht to reproduce it at all.
I would like to propose an official license for the content in the wiki:
Create Commons CC-BY-SA. The alternative would be to go for CC-BY-NC-SA,
disallowing commercial use of the content.
I'm not certain if NC is really what we want. After all, even somebody
using OpenBSC in a commercial environment should be able to make copies
of the reference documentation we have available - as long as he will
releas the result again (which the SA part already covers).
If the major contributors to the wiki would agree to a license, I would
update the wiki accordingly.
Thanks,
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)
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
Hi!
This patchset adds new VTY commands that allows to route IPA flows.
Patch 3/3 includes one feature that changes the current default
behaviour of OpenBSC since you explicity have to make a "ipa setup"
to enable OML and RSL links. If you like it, I can make a similar
patch for HSL femto, so the only initial open socket is the one at
port 4242 for telnet configuration.
BTW, the original command syntax was proposed by Harald.
Successfully tested bootstrapping the nanoBTS. See the patches for
more details.
Comments welcome!
Pablo Neira Ayuso (3):
libcommon: add make_sock_stream_connect()
libabis: add VTY commands to route IPA flows
libabis: add IPA VTY command to setup ip.access nanoBTS OML and RSL
links
openbsc/include/openbsc/ipaccess.h | 3 +
openbsc/include/openbsc/socket.h | 2 +
openbsc/include/openbsc/vty.h | 1 +
openbsc/src/ipaccess/Makefile.am | 4 +-
openbsc/src/libabis/Makefile.am | 2 +-
openbsc/src/libabis/e1_input.c | 2 +
openbsc/src/libabis/input/ipaccess.c | 962 +++++++++++++++++++++++++++++-
openbsc/src/libbsc/bsc_vty.c | 1 +
openbsc/src/libcommon/socket.c | 54 ++
openbsc/src/openbsc.cfg.ipa-proxy | 18 +
openbsc/src/openbsc.cfg.nanobts | 3 +
openbsc/src/openbsc.cfg.nanobts.multitrx | 3 +
openbsc/tests/db/Makefile.am | 5 +-
13 files changed, 1043 insertions(+), 17 deletions(-)
create mode 100644 openbsc/src/openbsc.cfg.ipa-proxy
--
1.7.2.3
Hi Pablo!
I've recently received a bug report that somehow the config-file-stored
configuration of which log levels/subsystems to enable on stderr don't work.
This may be related to the legacy "-d DINP:DNM:... style log level
specifications, e.g. we first read the config file and then set some default
logging options usign the legacy version.
Maybe you can find some time to investigate and fix the issue.
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)
Hi!
I'm experiencing problems with pysim-prog. Using the example available
in the README file.
# ./pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z lila -j 0
Insert card now (or CTRL-C to cancel)
I get stuck here forever. The same message shows if I remove the
supersim card from the reader.
Running pysim inside strace shows:
write(1, "Insert card now (or CTRL-C to cancel)\n", 38) = 38
ioctl(3, TIOCMBIS, [TIOCM_RTS]) = 0
select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout)
ioctl(3, TCFLSH, 0) = 0
ioctl(3, TIOCMBIC, [TIOCM_RTS]) = 0
select(4, [3], [], [], {1, 0}) = 0 (Timeout)
select(0, NULL, NULL, NULL, {0, 500000}) = 0 (Timeout)
ioctl(3, TIOCMBIS, [TIOCM_RTS]) = 0
select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout)
ioctl(3, TCFLSH, 0) = 0
ioctl(3, TIOCMBIC, [TIOCM_RTS]) = 0
... [and so on]
The pl2303 module is loaded correctly, and I have used it before to
access some embedded devices via serial line:
pl2303 2-2:1.0: pl2303 converter detected
usb 2-2: pl2303 converter now attached to ttyUSB0
usb 2-2: USB disconnect, device number 11
pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
Any clue on what's wrong?
Thanks!
Hi "Mr. Unknown",
it has come to my attention that you are running a copy of our OpenBSC
website (http://openbsc.osmocom.org/) at http://openbsc.microembedded.com/
We appreciate your enthusiasm for OpenBSC and like to thank you for
your work on the Chinese translation.
However, it would have been good to coordinate about this with us. Making
a copy of the website as a sub-domain to your company "MicroEmbedded" may
seem to some people as if you were representing the OpenBSC project (which
you are not), or that OpenBSC is somehow a work of your MicroEmbedded company.
After some checking, it seems that the final line on each page "注: BscHack (英文原文出 处,以上翻译整理仅供 OpenBSC 爱好者参考! email: support(a)microembedded.com )"
provides a link to the orignal page at bs11-abis.gnumonks.org.
Once again in this link you provide your e-mail address, followed by the
company footer of your web-page.
The contents of the OpenBSC website has copyright, and we do not think it is
appropriate for you to associate your company in this way with OpenBSC. You
are not a member of the project, you have not contributed to the OpenBSC
software, and you have not contacted us about obtainign permission to make
such a translated copy.
Furthermore, there are several problems with your website:
1) it is out of date, as you have used a very old version of the OpenBSC
website to translate. As a result, quite some of your links back to
the original OpenBSC site are broken.
2) You have introduced capitalization changes like "$ Sqlite" which will not
work, as the command is "$ sqlite"
If your intentions in running a translated OpenBSC site are honest, I would
like to invite you to do so in working together with us. We can provide
you with the respective space on the official homepage, and you can contribute
your translated content there.
In return, we may put a "thank you" link to microembedded.com in the Thanks
section at http://openbsc.osmocom.org/trac/wiki#Thanks
We hope this is acceptable to you. In any case, we hope you can understand
that we will not tolerate you putting your company name next to a copy of the
OpenBSC wiki.
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 List,
I'm a long time listener, first time caller - but have been enjoying
experimenting with OpenBSC for a little while now.
I've come across a new (to me) nanoBTS with some strange behavior: it seems
to come up normally and pull an IP over DHCP, and interacts as expected with
the ipaccess-find and ipaccess-config tools, but *never* attempts to
establish an OML link.
After provisioning the correct settings with ipaccess-config, the unit
reboots and slow-flashes the orange light (no OML) and there is *no* network
traffic initiated by the nanoBTS past the DHCP exchange; however, I can ping
the unit using ipaccess-find and ping.
After running a reset with the dongle and a repeat of the above, I get the
same results.
Any ideas?
Thank You,
-MM
Hello all,
I want a confirmation.
I 've seen in openBSC features that openBSC handles handover between cells
inside one BSC. So I think it's possible to connect several nanoBTS to
openBSC and move from one cell to another without losing the outgoing call.
Am I right ?
Thank you.
Chris