From a001c591b36f882ae3b63020a57ce22f129cf4c0 Mon Sep 17 00:00:00 2001 From: Daniel Willmann Date: Thu, 23 Aug 2018 17:48:02 +0200 Subject: [PATCH] osmo-sip-connector: Explicitly note OsmoMSC config with external MNCC Change-Id: Ia186ea48b1012e65dc6446c839fdb548d44b6a6c --- doc/manuals/chapters/configuration.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc index 24ac3a5..5cd57fa 100644 --- a/doc/manuals/chapters/configuration.adoc +++ b/doc/manuals/chapters/configuration.adoc @@ -11,6 +11,10 @@ the same path that OsmoMSC is also using. This means that OsmoMSC and OsmoSIPConnector need to be running on the same machine or have a shared directory that supports UNIX domain sockets. +Note that you need to start `osmo-msc` with the `--mncc-sock` option and point +to the same file that osmo-sip-connector is configured to use. See the OsmoMSC +manual for more information. + The example config below assumes that OsmoMSC was started with the command line `osmo-msc -M /tmp/msc_mncc`.