If a message that has triggered the E-Routing-Error contains no
session related IEs, they will also be absent in the error message.
Change-Id: Iaf9d8e77c8734672cfd8a265b8cfdb3bc929a31b
The special 'all' keyword has been deprecated a long time ago
due to its ambiguity, and replaced by 'force-all'.
Change-Id: I759d96716e964d499c0724d481b2f3e5062fb052
Somehow despite all the warnings everywhere about keeping wiki + code
in sync, this didn't get updated :(
Change-Id: I37e4ea4e6ac8291a36761ecc1849f06847a69557
Several fixes and improvements to the documentation.
This documentation still doesn't contain infrmation about TRXDv1, it
will be added in a follow-up commit.
Change-Id: I36e6206b90435964842f9f1ebd982cdaf9777018
Message formats of the new messages look mostly the same (IMSI,
Message Class, Source Name, Destination Name, AN-APDU). That is, because
AN-APDU is storing results, error reasons etc. This can be seen clearly
in osmo-msc.git:
* src/libmsc/msc_a_remote.c:msc_a_remote_fsm_communicating()
* src/libmsc/msc_i_remote.c:msc_i_remote_fsm_ready()
The message squence charts in the E Procedures section are directly
based on Neels' interMSC_HO_GSUP_msgs.txt [1].
It seems that using AN-APDU made some other new IEs redundant: RR Cause,
BSSAP Cause, Session Management Cause had been added to GSUP for the MSC
handover, and are documented now, but they are currently not used in
osmo-msc.git. The new message OSMO_GSUP_MSGT_E_ABORT is not used either,
so I left a stub for it in the message format section.
I mentioned in the Source Name IE section, that source and destination
names are sent as nul-terminated strings. This is for legacy reasons,
Neels wrote a nice summary in the commit message of [2].
[1] https://osmocom.org/attachments/3720/interMSC_HO_GSUP_msgs.txt
[2] Change-Id: I9ca8c9eef104519ed1ea46e2fef46dcdc0d554eb (osmo-msc)
Related: OS#3774, OS#3619
Change-Id: I6b9f23d08cfe53c8b77f51c6afb900c2badc9e2c
Move the "IMEI" and "IMEI Check Result" IEs from the "Session
(transaction) management" chapter (which describes session IEs) to the
"Information Elements" chapter. Add a comment to prevent this mistake in
the future.
Related: OS#2541
Change-Id: I6fd66419350e018a763b8fac3daf567b339a2637
Change-Id: I9a0536f285f98f24fec4d7318f1923782ed2e18c
Related Change-Id: Ie0150756c33c1352bc4eb49421824542c711175c
Related Change-Id: I549b6c8840a1e86caac09e77fb8bc5042d939e62
Make this part of the specification, so we can simplify libosmocore
code by knowing that error message is (request message | 0x000001).
Related: I46d9f2327791978710e2f90b4d28a3761d723d8f (libosmocore)
Change-Id: Iec1b4ce4b7d8eb157406f006e1c4241e8fba2cd6
Most likely, this was a copy-paste error. SGSN is not involved
in Supplemeptary Services handling, they are pure CS data.
Moreover, HLR is not the only entity that can initiate both
Process Supplementary Service Error and Response messages,
there is also EUSE (External USSD handling Entity).
Change-Id: I46ad7311747f2b392244c49d3df1e152e6f1bfe3
Change hardcoded ../common paths, which will break when moving the
project specific manuals in other repositories, to ./common so they
use the dynamically created symlink that always points to the right
path.
(moving manuals to project repositories 8/19)
Related: OS#3385
Change-Id: Id984f5e85481f7877567ee6d21f7ca455d773ef1
We reference the port list appendix where all the ports used by various
Osmocom projects are listed and it's unlikely that pointing out the
osmo-nitb port would significantly help the reader, so just remove the
reference.
Change-Id: I354d50314ba248835191fa3da122032201618a0e
Surrounding with '@' didn't seem to yield the intended result, the
charactars appeared in the compiled document.
Change-Id: I66e7949fa4a6c2164bf9572a2beaf8ace169fa1c
Those graphs + message sequence charts are not yet used by any
of our manuals, but they should become used by the OsmoMSC user
manual once SGs interface support is added.
Related: OS#2583
Change-Id: Idfd3a66c18131b5458d183b8e66f62eaaab65991
Add an informative note on how DTMF signalling is done in mobile
networks and mention the limitations regarding DTMF, when internal MNCC
is used.
Change-Id: Iedcf4ad5e0e4697c6a05ebdd4f43173c14c7c448
Related: OS#2777
The list that describes the MNCC message types lacks the message types
used for DTMF.
Change-Id: I4251b296e043e7583518d6672e614b376331d25e
Related: OS#2777
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
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 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
Since the NITB split, GSUP is used in all three network elements, so
make the protocol a shared chapter
Change-Id: Id2d7c27ef16eb0ebe5f60d625a1fcf42f1603f4f
Depends on the ENABLE and VIEW nodes to be named, as in a recent libosmocore
patch.
Depends: Iefb8b78094208a1a4c5d70bd6c69a3deca8da54f (libosmocore)
Change-Id: Ic2f3b18cced72db6fa5bad02ae58c602bb2c0213
This describe rate counter dumper added to osmo-python-tests in
I12b369434e4ee9b38f92872f297e1f3d4f0698c2
Change-Id: I52d735f373f2e7aa1f12941fc450c0e9740ccdeb
Related: OS#2550
* use example new counter names with ':' separator
* mention that 'counter' is obsolete
* mention group name and index
* use bold and monospace fonts to improve visibility
Change-Id: Ia962367bb93cb826002db6c950d23ae2102ac713
Related: OS#2550
osmo-mgw currently uses the VTY port constant of
osmo-bsc_mgcp. We decided to re use the same port
number for osmo-mgw, this is not mentioned in the
manuals yet.
Add the port number of osmo-mgw to the manuals
(common)
Change-Id: I41f7f2a7f850613707eddea610557b688de7a904
We agreed to re-use the port of osmo-bsc-mgcp, so there is
no need for this patch anymore.
This reverts commit ad4a01e2a4.
Change-Id: I8629db5e975cc218c80c747a39c0fdca5f5d6e10
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
- Mention that the CONFIG node is used to parse config files.
- Mention that it is not well defined whether CONFIG node items have immediate
effect.
- Add a 'telnet' here and there to clarify.
Change-Id: I882346c69f12c67d0e41d563c99d4de4efd8b8f6
The basic logging concepts like filters and levels which are
target-independent. It's counter-intuitive that they are described
inside vty target section.
* fix that by putting them in separate sections which are referenced
from target sections as necessary
* move all targets into subsections under "Log targets" section
Change-Id: I5acde815c66eb3d57e06ecd8dc65fe338216fe63
Related: OS#1913
Add OsmoMSC and OsmoHLR to bibliography (even though the OsmoHLR manual does
not yet exist, a reference to it has been added in OsmoMSC's manual).
Change-Id: I9ecff2837fbf5fdc19675a726f6d70c21eb178ee
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
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
Add semicoli in fig-gprs-pcubts digraph.
Remove section from GMM Implementation about non-existence of HLR.
The SGSN can access osmo-hlr via GSUP (and will have to do so in the
libvlr future).
Change-Id: I0164f418e453672321eed00bbc454c1e223ea158
Add high level description on and a config example for dynamic timeslots in a
new chapter featured in the OsmoBSC and OsmoNITB manuals.
From the OsmoBTS manual's chapter on dynamic timeslots, add references to the
above.
Change-Id: I44ff1e4c2340c65ff23e85408fc6d6a45ea9e046
Fix A5 description concerning A5/2 (not in use).
Fix UICC: 'Circuit Card', not 'Chip Circuit', and replace 'FIXME'.
NITB: like OsmoNITB just without Osmo, reference OsmoNITB.
Add some words/explanations (FPGA, MSC, OXCO, UICC, VTY).
Fix minor typos ('Freee', 'usees', over-eager dashes '-',
capitalisation).
Use 'an' before acronyms pronounced starting with a vocal ('S', 'M').
Use 'a' before 'U'.
Unify style:
Use semicoli ';' instead of periods '.' or commas ',' where appropriate.
Use lower case letters after semicoli.
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.
Vadim Yanitskiy
Harald Welte
Daniel Willmann
Pau Espin
Martin Hauke
Oliver Smith
Philipp Maier
Neels Hofmeyr