From 945b0606cf6a6f20081f4f621c43b302c3c88702 Mon Sep 17 00:00:00 2001 From: Philipp Maier Date: Tue, 3 Aug 2021 11:33:20 +0200 Subject: [PATCH] running.adoc: add section about MGCP configuration The manual seems to lack a section about how the MGW is set up. In the osmo-bsc manual we have a "Configure MGCP to connect to an MGW" section under the "Configure primary links" section. We should have the same thing in the osmo-msc manual as well. Change-Id: I5501739e63860c436ff606bc2758b495258cd2b9 Depends: osmo-mgw I47e7ff858d5067b46d52329be5f362ff61c0dff8 --- doc/manuals/chapters/running.adoc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index 688fbbef2..565c8d0e1 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -149,3 +149,21 @@ hlr ! default port is 4222, optionally configurable by: remote-port 1234 ---- + +==== Configure MGCP to connect to an MGW + +OsmoMSC uses a media gateway (typically OsmoMGW) to direct RTP streams. By +default, an MGW is expected to receive MGCP requests on the IANA-registered +default port for MGCP (2427) on local host (127.0.0.1). + +Here is an example configuration for a remote MGW: + +---- +msc + mgw remote-ip 10.9.8.7 + mgw remote-port 2427 + mgw reset-endpoint rtpbridge/* <1> +---- +<1> The 'reset-endpoint' setting instructs the OsmoMGW to send a wildcarded +DLCX to the media gateway. This helps to clear lingering calls from the +media gateway when the OsmoMSC is restarted.