aboutsummaryrefslogtreecommitdiffstats
path: root/common/chapters/mncc.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'common/chapters/mncc.adoc')
-rw-r--r--common/chapters/mncc.adoc12
1 files changed, 7 insertions, 5 deletions
diff --git a/common/chapters/mncc.adoc b/common/chapters/mncc.adoc
index 15c9982..e897294 100644
--- a/common/chapters/mncc.adoc
+++ b/common/chapters/mncc.adoc
@@ -53,12 +53,14 @@ 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 {program-name} with external MNCC handler, you have
-to start it with the `-m` or `--mncc-sock` command line option.
+to disable the internal MNCC handler and specify the MNCC socket path in
+the configuration file.
-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.
+At the time of this writing, there are only two known open source applications implementing the
+MNCC interface compatible with the Osmocom MNCC socket:
+
+* historically `lcr`, the Linux Call Router (support for modern MNCC protocol versions may be missing)
+* `osmo-sip-connector`, the more up-to-date integration of external call routing by translating MNCC into a SIP trunk towards an external SIP PBX / switch.
=== DTMF considerations