laforge has submitted this change. (
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32003
)
Change subject: chapters/mncc: Update the wording to be less confusing and more
up-to-date
......................................................................
chapters/mncc: Update the wording to be less confusing and more up-to-date
Change-Id: Ic8876509878e565f140508dc2e3494b0e21c566c
---
M common/chapters/mncc.adoc
1 file changed, 14 insertions(+), 4 deletions(-)
Approvals:
Jenkins Builder: Verified
laforge: Looks good to me, approved
diff --git a/common/chapters/mncc.adoc b/common/chapters/mncc.adoc
index 3c67998..e897294 100644
--- a/common/chapters/mncc.adoc
+++ b/common/chapters/mncc.adoc
@@ -56,10 +56,11 @@
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
--
To view, visit
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32003
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: Ic8876509878e565f140508dc2e3494b0e21c566c
Gerrit-Change-Number: 32003
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: merged