Age | Commit message (Collapse) | Author | Files | Lines |
|
After libosmocore commit
If1e851ac605c8d2fde3da565b0bd674ea6350c2e
b27e6feb699712345373e87a48187dc622e4fa92
the openbsc master build is broken.
Apply the msgb_wrap_with_TL() rename to msgb_push_tl() to unbreak the build.
Also related is commit e8cd09dd6f3378a8137afb581dcd7ed554daa24c in this
repository, which removed the locally defined msgb_wrap_with_TL() definition.
The libosmocore mistake should have become obvious then and there...
Change-Id: I6fece7bbbea84962daff885e54f0bc0108c8d0a5
|
|
Change-Id: If2180828e2acd28d96754c593c317c2868644c4b
|
|
OSMO-MSC backport
Adds (no) alert-notifications as a per-esme vty command,
in order to allow some ESMEs to be excluded from alerts.
The default is still to send alert notifications to all esme,
so no changes are required to the config file to maintain
identical operation after this patch.
Change-Id: I2b52f2778b24eebc82b2e5e2fb3c2250b1f9e5b0
|
|
Backport of https://gerrit.osmocom.org/11792/
When using smpp-first, after the ESME accepts our STATUS REPORT,
we were sending it locally into gsm340_rx_sms_submit() anyway.
In the case of the ESME mirroring the report back to us, this
would result in two copies of the status report in the SMS
database, which were also both then delivered to the MS.
Some MS then display the REPORT to the user as if it were
a normal SMS.
With this patch, we check if it is the sms_report that has had
receiver set in sms_route_mt_sms() and not the original SMS we
are reporting on, which of course already has receiver set.
Change-Id: I2136489bd21c4755463278a4048a446e5bc4a9d2
|
|
Add new environment variables WITH_MANUALS and PUBLISH to control if
the manuals should be built and uploaded. Describe all environment vars
on top of the file.
Related: OS#3385
Change-Id: I89be11d346d50169282c991235ffc47dacc30b11
|
|
EXTRA_DIST files need to be distributed, no matter if the systemd option
is configured or not.
Change-Id: I8dbb17571df5d6cea040498af2fe57f087bdeb24
|
|
There's increasing gap in functionality between ipaccess utils from this
repo and from osmo-bsc due to ongoing development in new repository. To
avoid potential user confusion let's drop them similar to the way SGSN
was removed earlier.
Change-Id: I9c04f9b469e60802461a2a6e421d3ba27e6dafa1
|
|
Set AM_DISTCHECK_CONFIGURE_FLAGS in Makefile.am instead of
DISTCHECK_CONFIGURE_FLAGS. This is the recommended way from the
automake manual, as otherwise the flag can't be changed by the user
anymore.
Related: OS#3718
Change-Id: I88cc2058bc4ff07d092b060d4cc4e28c3203c625
|
|
Rename the manuals to their proper names.
Change-Id: I8c020361c141c758bfb32562dbd7f34f4fd81c39
|
|
Add both manuals to manuals/OsmoMGCP and manuals/OsmoNAT. Build them
just like the existing OsmoNITB manual:
$ cd manuals/OsmoMGCP
$ make
The commit history only consisted of the initial commit and was not
imported.
Related: OS#3385
Change-Id: Ibace91bc518079765e12529596a1763b6c5a04b5
|
|
Move from doc/manuals to manuals/OsmoNITB as we have two more manuals
(OsmoMGCP and OsmoNAT) that need to be moved to manuals/. Make the
manuals build without a toplevel configure.ac file from autotools:
$ cd manuals/OsmoNITB
$ make
openbsc/configure.ac is not used to integrate the manuals, as it would
be extra effort to integrate all three of the manuals there. This is
not worth it for the legacy codebase.
Related: OS#3385
Change-Id: I0036ad8dbecd23695305ac491c7ee87caa44c7f9
|
|
Moved to doc/manuals/, with full commit history, in preceding merge commit.
Now incorporate in the build system.
Build with:
$ autoreconf -fi
$ ./configure --enable-manuals
$ make
Shared files from osmo-gsm-manuals.git are found automatically if
- the repository is checked out in ../osmo-gsm-manuals; or
- if it osmo-gsm-manuals was installed with "make install"; or
- OSMO_GSM_MANUALS_DIR is set.
Related: OS#3385
Change-Id: I4466d820cb3a5609a4a8534b1581684f891a04cd
|
|
Change-Id: I298828d47ce86c13301f5ab245934fbcf8d8d2d3
|
|
Replace the symlink with a full copy, as the manuals are in the project
repositories now.
Related: OS#3385
|
|
It doesn't seem to have an effect on the generated PDFs though.
Change-Id: I0556a3f8dafc051f20a3854fc9006edf4ec1a0d3
|
|
... to match the /etc/xml/catalog file on debian (no "www" in hostname)
Change-Id: Id9f3579c7f2bc3af13fe30b5268f249b6f59ed0d
|
|
The initial goal was to make sure we don't have overall FORCE rules causing
unnecessary rebuilds -- annoying while writing documentation. As I looked
through possible dependencies, I finally understood what's going on here.
Remove code dup and nicely sort which belongs where in build/Makefile.*.inc. In
each, describe in a top comment how to use it, and also unify how they are
used:
- Rename Makefile.inc to Makefile.docbook.inc and refactor
- Add Makefile.vty-reference.inc
- Add Makefile.common.inc
Make sure that we accurately pick up all dependencies.
Drop use of the macro called 'command', that silenced the actual command lines
invoked and replaced them with short strings: it obscures what is actually
going on and makes the Makefiles hard to read and understand.
Each manual's makefile is greatly reduced to few definitions and a Makefile
include, e.g. one for asciidoc, one for VTY reference.
Move common/bsc_vty_additions.xml to OsmoBSC/vty/libbsc_vty_additions.xml, link
from OsmoNITB. It applies only to OsmoBSC and OsmoNITB.
Add a script that combines a VTY reference file with *all* additions files
found in a manual's vty/ dir. Call this from Makefile.vty-reference.inc.
Change-Id: I9758e04162a480e28c7dc83475b514cf7fd25ec0
|
|
Change node IDs to use the names derived from the node prompt,
in the process fix the node references to not place the vty_additions in the
wrong places.
Related: I8fa555570268b231c5e01727c661da92fad265de (libosmocore)
Change-Id: I48edb65be94be56c4b57293d8edc1b30271acc12
|
|
OsmoMSC will need the same SMPP chapter as OsmoNITB.
In smpp.adoc, replace program name with parameter, add parameter to
OsmoNITB's main adoc and move smpp.adoc to common/chapters.
Change-Id: I15febdea6569316dad3eed5f9dc7158adb5b078c
|
|
Change-Id: I993a3c3bf617b9823f49898364b5f728a4549330
|
|
Upcoming OsmoMSC will reference the same, hence MNCC becomes a common chapter.
Move the file and adjust various wording to include OsmoMSC.
Change-Id: I404758ff7f1372e841ffe33c75455f513fff3caf
|
|
All parts referencing GFDL can be easily disabled by removing the
'gfdl-enabled' attribute from the document.
Change-Id: I2489726ad2e90301bceadfada926e31ae0f85986
|
|
Change-Id: I4cedd07a33633bdd2350d2bda0a22cc0c631c0a9
|
|
Change-Id: I594b89094413758146bb25f5262902e263f8f3d1
|
|
Change-Id: Ia4c2d71eeca853ef277e802e9e8e200eb3414bca
|
|
Change-Id: I2c621def499dc0564d31eb9440e22e79948a5466
|
|
Change-Id: I69adeef85adda6f08b31b7d176f51e16968c1435
|
|
Unfortunately a glob like osmo-x__*.{svg,png} doesn't work, so have the
suffixes in separate globs.
Add dashes to indicate that failure should be ignored.
Change-Id: I6bc4d9ea72b43a573acbc860c23397f748de2c7b
|
|
Change-Id: If3d92fe19d402d77b0db0eb9d00efef0a8d02122
|
|
Change-Id: If81e44c9a0774e5de39cc536989cef5cb214a224
|
|
Generate *.check files from asciidoc output and grep for WARNINGs.
Add *.check files to gitignore and to 'make clean'.
Change-Id: Ibccc83a3415930a528f2e8e4e4dda3b81c6d0b64
|
|
Change-Id: I80798e79b4ccee64f26f58f9754de02b2958e33e
|
|
|
|
|
|
|
|
|
|
|
|
The manuals existed in different form for several years in an internal
sysmocom repository. However, since they had just recently been
converted from docboox-xml to asciidoc and all files have been
re-shuffled for enabling the public release, there's not much point in
keeping the history with git-filter-branch.
|
|
Change-Id: I4ca2ce35f68ca5e2a82dc70e240e76c741199adb
|
|
From RFC 4867:
octet-align: Permissible values are 0 and 1. If 1, octet-aligned
operation SHALL be used. If 0 or if not present,
bandwidth-efficient operation is employed.
Change-Id: Ic4db7f6d18f650f36f3186965096771f748de5fd
|
|
Remove locally defined function which conflicts with the one in
libosmocore.
Change-Id: Ifcc13c4f8998af7680fc17414b2720feee7d386a
|
|
Not really critical since only user of this function doesn't check the
return value.
Fixes commit: 4a2cc9eb0a0f9424c16b26fcb757483a39d67482
Change-Id: I438349bffaa46a10ad8983090a4b17aed7e00d82
|
|
Change-Id: If5de6e981e9af7b667dd3365d758f868f38bf6e0
|
|
* Refactor code to have unified checks on all paths activating Osmux.
* Improve checkings at activation time and add logging.
* Code now enforces endp osmux status to be enabled before processing
the frame through endp->osmux.out. Before, a delayed or bad pkt could
arrive and be processed by an endp with osmux not enabled, using
endp->osmux.out that was not initialized and ended up crashing:
libosmo-netif/src/osmux.c:281:3: runtime error: member access within null pointer of type 'struct msgb'
This could also happen if a BSC started sending or we received (non legacy dummy) osmux
frames before we received the BSC CRCX ACK agreeing on osmux negotiation
and switching to ACTIVATING state.
Related: SYS#4350
Change-Id: I3536169c94e65f999aaa9c9e43cc7dab8551d30f
|
|
State ACTIVATING is set once negotiation between the 2 parts went
successfuly.
Change-Id: I21eb30fa8d48f3d592ff197bd74e673fdac51c1d
|
|
Change-Id: I285f1cb693b243ecd404337f2bb5b74ddd32b123
|
|
Change-Id: If9249fb0ee2e33c7dd2ab817480776acaa784cc2
|
|
Prior to this commit, the check was only done on legacy dummy frames.
Change-Id: Ief4e62fe68a11a60d90292c72d1263fd1f728356
|
|
enabled
Change-Id: I5244cb9304adef3aa612b8126bf95e77562c801c
|
|
Change-Id: I9f686404517bf8a2044cf59dd5bfaf90eb4f798f
|