I have some questions:
1) When I start bsc_hack bsc_init.c first establishes OML link and
initializes the bts then it establishes RSL link and bts starts
broadcasting. However, it takes so much time to start the bts. Instead of
this I want to do the following: it establishes OML link at the beginning
and only once, then when i want to start broadcasting it establishes just
the RSL link and bts will start faster since i don't have to wait for OML
link. What should be done for this?
2) If i send one or two word messages from telnet interface it is okay. But
if i send a longer message the phone could't receive the end of the message
correctly(last words may be incomplete). Did any one encounter with this
problem? What is wrong with me?
3) Could I send SMS in which extension of the sender is text not integer.
For example, i want to send an information SMS that this is a test network.
For this purpose i want to send an SMS from 'OpenBSC'. I set the extension
of the first subscriber in database as text and tried to send the SMS but
SMS wasn't delivered. What should i do?
4) Can i add SMS externally to SMS table of database?
Thanks.
Jason
Hi all,
Maybe I'm missing something, but I haven't found an easy way to
download pdf versions of all the 3gpp specs. Why would you want to do
that? Well, dealing with MS-Word format is a pain. And, there's no
online full-text search of all the specs.
So, I threw together a quick web scraper to pull down the latest
version of all the 3GPP specs from the ETSI web site in pdf format.
Thought it might be useful to others -
http://monkey.org/~joe/files/fetch_3gpp.py
Feel free to contact me if you have any trouble using it.
-Joe
Hello guys,
I haven't been busy with openbsc for a while, however, I was following
the mailing-list.
I have the following question, is timing advance also implemented for
the nanoBTS? Cause I don't really know where to look in the sources,
thank you.
Nothing required actually.
The firmware is preloaded.Just configure the Nanobts using the installation
CD given.
Some jar file is there for configuring part.
> https://lists.osmocom.org/mailman/listinfo/openbsc
> or, via email, send a message with subject or body 'help' to
> openbsc-request(a)lists.osmocom.org
>
> You can reach the person managing the list at
> openbsc-owner(a)lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBSC digest..."
>
>
> Today's Topics:
>
> 1. Re: How to download firmware and configure NanoBTS the first
> time... (Harald Welte)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 16 Feb 2011 22:52:33 +0100
> From: Harald Welte <laforge(a)gnumonks.org>
> Subject: Re: How to download firmware and configure NanoBTS the first
> time...
> To: Omar Atia <omar.atia(a)its.ws>
> Cc: 'Peter Hasse' <peter.hasse(a)fokus.fraunhofer.de>,
> openbsc(a)lists.osmocom.org
> Message-ID: <20110216215233.GO25856(a)prithivi.gnumonks.org>
> Content-Type: text/plain; charset=us-ascii
>
> Omar,
>
> how should we know in what you get your particular nanoBTS units delivered?
>
> You have to talk to your supplier about that.
>
> For all I know, it is customary for the nanoBTS to ship with pre-installed
> firmware. Based on your support contract with ip.access you may receive
> firmware updates from time to time, which you can then apply either using
> tools from ip.access or using our ipaccess-config. Our tool is of course
> not officially recognized/authorized/recommended/endorsed for this purpose.
>
> 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)
>
>
>
> ------------------------------
>
> _______________________________________________
> OpenBSC mailing list
> OpenBSC(a)lists.osmocom.org
> https://lists.osmocom.org/mailman/listinfo/openbsc
>
>
> End of OpenBSC Digest, Vol 26, Issue 15
> ***************************************
>
hi harald,
i would also suggest to combine mncc.h of openbsc and osmocom-bb first, and move it to libosmocore. this way the LCR (or other mncc_socket client) does not depend on any files of openbsc and osmocom-bb, just on libosmocore.
because i like to use the same socket interface for osmocom-bb, i would suggest to to put mncc_sock.c into libosmocore too, so it must not be implemented twice.
then i would make lcr to be able to connect to both osmocom-bb and openbsc sockets. finally there is no more polling of file descriptor required at lcr.
if you agree, can you move the code to libosmocore? i will work on the socket configuration and see what i can do with the versioning.
andreas
-----Ursprüngliche Nachricht-----
Von: Harald Welte [mailto:laforge@gnumonks.org]
Gesendet: Dienstag, 22. Februar 2011 13:22
An: Andreas.Eversberg
Cc: openbsc(a)lists.gnumonks.org
Betreff: Re: fix of chan_lcr / new socket interface for openbsc
Andreas,
thanks for integrating the mncc socket patch into lcr.
I would personally like to see the following improvements:
* add some (preferrable automatically computed) version to the mncc,
to make sure you cannot run lcr + bsc_hack built from a different mncc.h
file. We could do something like a md5sum over the header at compilation
time, stored in both openbsc and lcr. Once they connect the mncc socket,
they request the remote side md5-value and compare it with the local-side
value. If they don't match, print an error message and exit the program.
* make the socket path configurable, which is required for running multiple
instances of openbsc+lcr on the same machine.
If you (or anyone else on this list) happens to have some time to work on
that, it would be greatly appreciated.
Regards,
Harald
hi,
the broken chan_lcr is now fixed in the "develop" branch of lcr git. i
have tested it with asterisk 1.8.1. the locking seems to be improved in
this asterisk version. i could not run it in a deadlock, as i could with
asterisk 1.6. i would suggest to try this out, but please keep your
current asterisk and lcr sources. if all works fine, i would like to
merge the "develop" branch into the "master" branch soon.
for the gsm users: the second change in the "develop" branch is the
socket interface between openbsc and lcr. thanks to harald welte for
providing this patch. instead of linking openbsc to lcr, openbsc runs
it's own process. (using bsc_hack as usual) lcr connects to a socket of
openbsc. with it, the gsm.conf became obsolte and has been removed from
lcr. in order to run lcr with openbsc ("master" branch of openbsc) :
bsc_hack -P -m -l <sqlite-database> -c <openbsc-config>
-P is required to enable rtp proxy for use with ipaccess bts.
-m is required to allow call control via socket interface
to get lcr from "develop" branch, do:
git-clone git://git.misdn.org/git/lcr.git/
cd lcr
sh checkout-branch.sh develop
regards,
andreas
Hi!
With the help of graphviz, I have written a small perl-based tool that
allows you to generate ladder diagrams. It can be found at
git://git.osmocom.org/gen_ladder.git
For your reference, I'm attaching a sample input and output file.
The bent/curved arrows are a result of graphviz trying to indicate
that the message is between e.g. MS and MSC and 'bypasses' BTS and BSC.
I'm still waiting for somebody with more graphviz skills to make this an
option.
Hope this is useful for some of you...
--
- 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,
I just stumbled over the following change in libosmocore
diff --git a/src/vty/Makefile.am b/src/vty/Makefile.am
index 7353ab8..8d730c3 100644
--- a/src/vty/Makefile.am
+++ b/src/vty/Makefile.am
@@ -10,5 +10,5 @@ lib_LTLIBRARIES = libosmovty.la
libosmovty_la_SOURCES = buffer.c command.c vty.c vector.c utils.c \
telnet_interface.c logging_vty.c
-libosmovty_la_LIBADD = $(top_builddir)/src/libosmocore.la
+libosmovty_la_LIBADD = -losmocore $(top_builddir)/src/libosmocore.la
endif
from commit 2822296d
The -losmocore seems wrong as it is the library we're building here and
it's not necessarily already installed.
If I remove that part libosmocore builds for me again.
Regards,
Daniel Willmann