This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has submitted this change and it was merged. ( https://gerrit.osmocom.org/c/osmo-bsc/+/14840 ) Change subject: doc: Add Osmux documentation to User Manual ...................................................................... doc: Add Osmux documentation to User Manual Depends: osmo-gsm-manuals.git f3a734e6777a902abfb03257277454c7a879aeb7 Change-Id: I75dcdddc713b0dc43e2ba577ca377c20fc511f38 --- A doc/manuals/chapters/osmux_bsc.adoc M doc/manuals/osmobsc-usermanual.adoc 2 files changed, 46 insertions(+), 1 deletion(-) Approvals: osmith: Looks good to me, but someone else must approve laforge: Looks good to me, approved Jenkins Builder: Verified diff --git a/doc/manuals/chapters/osmux_bsc.adoc b/doc/manuals/chapters/osmux_bsc.adoc new file mode 100644 index 0000000..c9f387b --- /dev/null +++ b/doc/manuals/chapters/osmux_bsc.adoc @@ -0,0 +1,43 @@ +include::{commondir}/chapters/osmux/osmux.adoc[] + +=== Osmux Support in {program-name} + +==== {program-name} in a A/IP with IPA/SCCPlite network setup + +In this kind of setup, Osmux is transparent to {program-name} and no specific +configuration is required here, since the CN-side of the BSC-attached MGW is +managed directly by the MSC. + +So, in this case, only MSC and MGW (both for MSC-attached one and BSC-attached +one) need to be configured explicitly. + +==== {program-name} in a 3GPP AoIP network setup + +Osmux usage in {program-name} in managed through the VTY command `osmux +(on|off|only)`. Once enabled (`on` or `only`), {program-name} will start +appending the vendor specific _Osmux Support_ IE in _BSSMAP RESET_ and _BSSMAP +RESET-ACK_ message towards the MSC in order to announce it supports Osmux. This +way, the MSC can decide whether to use Osmux or not based on this information +when setting up a call (this time using _Osmux CID_ IE). It should be noted that +this option should not be enabled unless MSC managing {program-name} supports +handling this extension IE (like OsmoMSC), a 3rd-party MSC might otherwise +refuse the related _RESET_/_RESET-ACK_ messages. + +{program-name} will behave differently during call set up based on the VTY +command presented above: + +* `off`: If _BSSMAP Assign Request_ from MSC contains _Osmux CID_ IE, meaning + MSC wants to use Osmux for this call, then {program-name} will reject the + assignment and the call set up will fail. +* `on`: BSC will support and accept both Osmux and non-Osmux (RTP) upon call set + up. If _BSSMAP Assign Request_ from MSC contains _Osmux CID_ IE, + {program-name} will instruct its MGW to set up an Osmux connection on the + CN-side of the MGCP endpoint, and will provide the MSC with its _recvCID_ + through the extension IE _Osmux CID_ appened to the _BSSMAP Assign Complete_ + message. On the other hand, if _BSSMAP Assign Request_ doesn't contain an + _Osmux CID_ IE, {program-name} will instruct its MGW to set up a regular RTP + connection on the CN-side of the MGCP endpoint. +* `only`: Same as per `on`, except that {program-name} will accept only Osmux + calls on the CN-side, this is, if _BSSMAP Assign Request_ from MSC doesn't + contain an _Osmux CID_ IE, it will reject the assignment and the call set up + will fail. diff --git a/doc/manuals/osmobsc-usermanual.adoc b/doc/manuals/osmobsc-usermanual.adoc index 3515aaa..766a11f 100644 --- a/doc/manuals/osmobsc-usermanual.adoc +++ b/doc/manuals/osmobsc-usermanual.adoc @@ -1,4 +1,5 @@ :gfdl-enabled: +:program-name: OsmoBSC OsmoBSC User Manual =================== @@ -35,6 +36,8 @@ include::./common/chapters/cell-broadcast.adoc[] +include::{srcdir}/chapters/osmux_bsc.adoc[] + include::./common/chapters/port_numbers.adoc[] include::./common/chapters/bibliography.adoc[] @@ -42,4 +45,3 @@ include::./common/chapters/glossary.adoc[] include::./common/chapters/gfdl.adoc[] - -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/14840 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: I75dcdddc713b0dc43e2ba577ca377c20fc511f38 Gerrit-Change-Number: 14840 Gerrit-PatchSet: 3 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at gnumonks.org> Gerrit-Reviewer: osmith <osmith at sysmocom.de> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-MessageType: merged -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190723/b4703b63/attachment.htm>