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/.
Neels Hofmeyr gerrit-no-reply at lists.osmocom.orgNeels Hofmeyr has submitted this change and it was merged. Change subject: move mncc.adoc to common chapters ...................................................................... move mncc.adoc to common chapters 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 --- M OsmoNITB/osmonitb-usermanual.adoc R common/chapters/mncc.adoc 2 files changed, 51 insertions(+), 44 deletions(-) Approvals: Harald Welte: Looks good to me, approved Jenkins Builder: Verified diff --git a/OsmoNITB/osmonitb-usermanual.adoc b/OsmoNITB/osmonitb-usermanual.adoc index 0d6fa7e..7d342c5 100644 --- a/OsmoNITB/osmonitb-usermanual.adoc +++ b/OsmoNITB/osmonitb-usermanual.adoc @@ -29,7 +29,7 @@ include::chapters/smpp.adoc[] -include::chapters/mncc.adoc[] +include::../common/chapters/mncc.adoc[] include::../common/chapters/control_if.adoc[] diff --git a/OsmoNITB/chapters/mncc.adoc b/common/chapters/mncc.adoc similarity index 65% rename from OsmoNITB/chapters/mncc.adoc rename to common/chapters/mncc.adoc index 504ce09..47dfcbe 100644 --- a/OsmoNITB/chapters/mncc.adoc +++ b/common/chapters/mncc.adoc @@ -1,5 +1,5 @@ [[mncc]] -== MNCC for external Call Control +== MNCC for External Call Control The 3GPP GSM specifications define an interface point (service access point) inside the MSC between the call-control part and the rest of the @@ -9,21 +9,24 @@ However, like for all internal interfaces, 3GPP does not give any specific encoding for the primitives passed at this SAP. -The MNCC protocol of OsmoNITB has been created by the Osmocom community +The MNCC protocol has been created by the Osmocom community and allows to control the call handling and audio processing by an external application. The interface is currently exposed using Unix Domain Sockets. The protocol is defined in the `mncc.h` header file. -OsmoNITB can run in two different modes: +It is exposed by the Osmocom MSC layer (both in the old OsmoNITB as well as the +new OsmoMSC. + +Osmocom's MSCs can run in two different modes: . with internal MNCC handler . with external MNCC handler === Internal MNCC handler -When the internal MNCC handler is enabled, OsmoNITB will switch voice -calls between GSM subscribers internally and automatically based on -the subscribers __extension__ number. No external software is required. +When the internal MNCC handler is enabled, OsmoMSC/OsmoNITB will switch voice +calls between GSM subscribers internally and automatically based on the +subscribers __extension__ number. No external software is required. NOTE: Internal MNCC is the default behavior. @@ -42,131 +45,135 @@ Using this command, you can configure the default voice codec to be used by voice calls on TCH/H channels. +[[mncc-external]] === External MNCC handler -When the external MNCC handler is enabled, OsmoNITB will not perform any -internal call switching, but delegate all call-control handling towards -the external MNCC program connected via the MNCC socket. +When the external MNCC handler is enabled, OsmoMSC/OsmoNITB will not perform +any internal call switching, but delegate all call-control handling towards the +external MNCC program connected via the MNCC socket. -If you intend to operate OsmoNITB with external MNCC handler, you have +If you intend to operate with external MNCC handler, you have to start it with the `-m` or `--mncc-sock` command line option. -At the time of this writing, the only external application implementing -the MNCC interface compatible with the OsmoNITB MNCC socket was `lcr`, -the Linux Call Router. +At the time of this writing, the only external application implementing the +MNCC interface compatible with the Osmocom MNCC socket is `lcr`, the Linux Call +Router. More widespread integration of external call routing is available via +the OsmoSIPConnector. === MNCC protocol description -The protocol follows the primitives specified in 3GPP TS 04.07 Chapter -7.1. The encoding of the primitives is provided in the `openbsc/mncc.h` -header file, which uses some common definitions from -`osmocom/gsm/mncc.h` (part of libosmocore.git). +The protocol follows the primitives specified in 3GPP TS 04.07 Chapter 7.1. +The encoding of the primitives is provided in the `mncc.h` header file +(`osmocom/msc/mncc.h` in `osmo-msc.git` or `openbsc/mncc.h` in old +`openbsc.git`), which uses some common definitions from `osmocom/gsm/mncc.h` +(part of `libosmocore.git`). -However, OsmoNITB MNCC specifies a number of additional primitives -beyond those listed in the 3GPP specification. +However, Osmocom's MNCC specifies a number of additional primitives beyond +those listed in the 3GPP specification. The different calls in the network are distinguished by their callref (call reference), which is a unique unsigned 32bit integer. +NOTE: _MSC_ below refers to both OsmoMSC and _libmsc_ of the OsmoNITB. + ==== MNCC_HOLD_IND -Direction: NITB -> Handler +Direction: MSC -> Handler A 'CC HOLD' message was received from the MS. ==== MNCC_HOLD_CNF -Direction: Handler -> NITB +Direction: Handler -> MSC Acknowledge a previously-received 'CC HOLD' message, causes the transmission of a 'CC HOLD ACK' message to the MS. ==== MNCC_HOLD_REJ -Direction: Handler -> NITB +Direction: Handler -> MSC Reject a previously-received 'CC HOLD' message, causes the transmission of a 'CC HOLD REJ' message to the MS. ==== MNCC_RETRIEVE_IND -Direction: NITB -> Handler +Direction: MSC -> Handler A 'CC RETRIEVE' message was received from the MS. ==== MNCC_RETRIEVE_CNF -Direction: Handler -> NITB +Direction: Handler -> MSC Acknowledge a previously-received 'CC RETRIEVE' message, causes the transmission of a 'CC RETRIEVE ACK' message to the MS. - ==== MNCC_RETRIEVE_REJ -Direction: Handler -> NITB +Direction: Handler -> MSC Reject a previously-received 'CC RETRIEVE' message, causes the transmission of a 'CC RETRIEVE REJ' message to the MS. ==== MNCC_USERINFO_REQ -Direction: NITB -> Handler +Direction: MSC -> Handler Causes a 'CC USER INFO' message to be sent to the MS. ==== MNCC_USERINFO_IND -Direction: NITB -> Handler +Direction: MSC -> Handler Indicates that a 'CC USER-USER' message has been received from the MS. ==== MNCC_BRIDGE -Direction: Handler -> NITB +Direction: Handler -> MSC Requests that the TCH (voice) channels of two calls shall be inter-connected. This is the old-fashioned way of using MNCC, primarily required for circuit-switched BTSs whose TRAU frames are -received via an E1 interface card on the NITB machine. +received via an E1 interface card on the MSC machine. ==== MNCC_FRAME_RECV -Direction: Handler -> NITB +Direction: Handler -> MSC Enable the forwarding of TCHF voice frames via the MNCC interface in -NITB->Handler direction for the specified call. +MSC->Handler direction for the specified call. ==== MNCC_FRAME_DROP -Direction: Handler -> NITB +Direction: Handler -> MSC Disable the forwarding of TCHF voice frames via the MNCC interface in -NITB->Handler direction for the specified call. +MSC->Handler direction for the specified call. ==== MNCC_LCHAN_MODIFY -Direction: Handler -> NITB +Direction: Handler -> MSC Modify the current dedicated radio channel from signalling to voice, or if it is a signalling-only channel (SDCCH), assign a TCH to the MS. ==== MNCC_RTP_CREATE -Direction: Handler -> NITB +Direction: Handler -> MSC Create a RTP socket for this call at the BTS/TRAU that serves this BTS. ==== MNCC_RTP_CONNECT -Direction: Handler -> NITB +Direction: Handler -> MSC Connect the RTP socket of this call to the given remote IP address and port. ==== MNCC_RTP_FREE -Direction: Handler -> NITB +Direction: Handler -> MSC Release a RTP connection for one given call. @@ -175,32 +182,32 @@ Direction: both Transfer the payload of a GSM Full-Rate (FR) voice frame between the -NITB and an external MNCC handler. +MSC and an external MNCC handler. ==== GSM_TCHF_FRAME_EFR Direction: both Transfer the payload of a GSM Enhanced Full-Rate (EFR) voice frame -between the NITB and an external MNCC handler. +between the MSC and an external MNCC handler. ==== GSM_TCHH_FRAME Direction: both Transfer the payload of a GSM Half-Rate (HR) voice frame between the -NITB and an external MNCC handler. +MSC and an external MNCC handler. ==== GSM_TCH_FRAE_AMR Direction: both Transfer the payload of a GSM Adaptive-Multi-Rate (AMR) voice frame -between the NITB and an external MNCC handler. +between the MSC and an external MNCC handler. ==== GSM_BAD_FRAME -Direction: NITB -> Handler +Direction: MSC -> Handler Indicate that no valid voice frame, but a 'bad frame' was received over the radio link from the MS. -- To view, visit https://gerrit.osmocom.org/4051 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I404758ff7f1372e841ffe33c75455f513fff3caf Gerrit-PatchSet: 2 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>