osmo-sip-connector does not yet support full DTMF support. The current
implementation only supports DTMF tones to be send from MNCC to SIP,
but not in the opposite direction.
Change-Id: I578e50b0a42d88b05cf6da80443b71494b5eb26f
Related: OS#2777
See also Ia6fe5ead4b601931c1bf41b29fc1b237aac37d2c in osmo-mgw.git, which
changes the initial single-character implementation to match this specification
of string tokens separated by spaces.
Change-Id: If15a88c3b5b40fd1d24ad0f94f3231f678669ab1
osmocom.org has been migrated to a new host, but the docs upload hasn't
moved yet. So explicitly upload to rita.osmocom.org.
Related: OS#3338
Change-Id: Ia1518313af007a5a665b3e06619d929e15ff277d
A while ago, we have introduced some new message types and IEs,
related to TCAP-like transaction management and Supplementary
Services. Let's document this extension.
Change-Id: Ib1331246097db736d98baf1a162574cadca9ee36
Otherwise it will depend on a setting this up in a seperate step.
This way it's more decoupled from the build host.
Change-Id: Iea1f5810bc7d4370724fdd7eb875c9a27b3d82af
Those diagrams represent the current design of the way how
GSM <-> SIP codec selection should work in the future.
Related: OS#1683
Change-Id: If92379b41d859bdf7be4b7689dc0bbca7cb6e682
This feature has been available since March 2013. It was introduced in
libosmocore 8e878738d16ad4f8776dc0130ebff78dea422ee7.
Change-Id: I650eb77d4b701a199a9e193cfb0e32565940a788
This is the first update since the libosmocore changes to the 'show
online-help' generated output. Hence the produced document now benefits from
the structural improvements:
- not repeating common commands for every node;
- using section names that match the VTY prompt.
Change-Id: I98cdfcb6c1c7db49ab106e775be92e4c6adeab17
This is the first update since the libosmocore changes to the 'show
online-help' generated output. Hence the produced document now benefits from
the structural improvements:
- not repeating common commands for every node;
- using section names that match the VTY prompt.
Drop most of the sgsn_vty_additions.xml -- they merely repeat what the online
VTY doc already explains. Many of these more verbose explanations have been
absorbed into the VTY online doc in osmo-sgsn.git change-id
I35984014424412e91437b7ed71576aef3819cb1e.
Adjust remaining sgsn_vty_additions.xml to match the new node ID scheme.
Change-Id: I71863e5056ad369d2055e9882a52a00fa999ab04
This is the first update since the libosmocore changes to the 'show
online-help' generated output. Hence the produced document now benefits from
the structural improvements:
- not repeating common commands for every node;
- using section names that match the VTY prompt.
Change-Id: I79804ec0e61cc19a679f079a083a5ea2ea3ee2de
Add new (generic) logging commands, talloc context print commands.
Add the jitter buffer logging category.
Remove the common commands from the individual sections.
Change-Id: I8e92c821b26908d4baa37745c57b9e15bda2a373
This is the first update since the libosmocore changes to the 'show
online-help' generated output. Hence the produced document now benefits from
the structural improvements:
- not repeating common commands for every node;
- using section names that match the VTY prompt.
Update msc_vty_additions.xml to match the new node ID scheme.
Change-Id: I6f1698dbc205334cf69234f88b124abfce54cc9a
This is the first update since the libosmocore changes to the 'show
online-help' generated output. Hence the produced document now benefits from
the structural improvements:
- not repeating common commands for every node;
- using section names that match the VTY prompt.
Update bsc_vty_additions.xml to match the new node ID scheme.
Change-Id: I0d856563eee88527fda4c6940aa6cea779175aaa
This chapter defines the protocol used between osmo-trx and
osmo-bts-trx.
Most of the text comes originally from osmo-trx.git/README, as it's the
only known documentation of the protocol other than the code itself.
Change-Id: I56c418eef0f826ae1aadbed5b151fbed241c7885
The rules in build/Makefile.vty-reference.inc require a libosmocore
source tree. Make the top-level Makefile check that LIBOSMO_DIR is
set to a valid directory before running the build.
This transforms an obscure build error into:
Directory '~/source/gsm/libosmocore' not found, please set LIBOSMO_DIR to
the path of your libosmocom source tree: make LIBOSMO_DIR=/path/to/libosmocore
Makefile:80: recipe for target 'check-deps' failed
Change-Id: Ic201373df115bb6f8c9a2bc30d18ff4c2a660deb
Related: OS#2787
Since the NITB split, GSUP is used in all three network elements, so
make the protocol a shared chapter
Change-Id: Id2d7c27ef16eb0ebe5f60d625a1fcf42f1603f4f
Philipp Maier
Daniel Willmann
Pau Espin
Harald Welte
Daniel Willmann