diff options
| author | Daniel Willmann <daniel@totalueberwachung.de> | 2018-08-23 17:48:02 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2018-11-27 18:34:29 +0100 |
| commit | a001c591b36f882ae3b63020a57ce22f129cf4c0 (patch) | |
| tree | 11dadd0aa138343c1fb43fa5e145c0901da276ce | |
| parent | 2e331aed4ecb405e273563ad2f7e66c2ba4493e8 (diff) | |
osmo-sip-connector: Explicitly note OsmoMSC config with external MNCC
Change-Id: Ia186ea48b1012e65dc6446c839fdb548d44b6a6c
| -rw-r--r-- | doc/manuals/chapters/configuration.adoc | 4 |
1 files changed, 4 insertions, 0 deletions
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`. |