diff options
authorPhilipp Maier <pmaier@sysmocom.de>2021-08-03 11:15:13 +0200
committerPhilipp Maier <pmaier@sysmocom.de>2021-08-03 11:44:57 +0200
commita23c7be0a1a24b6480bfe74f62d43e9aa8dff49e (patch)
parente8708af1e138061b78aa5ce50c61dfc0dc1137dd (diff)
running.adoc: explain mgw reset-endpoint VTY setting
When OsmoBSC is restarted, it does not automatically clear the calls on the MGW. However, this is an important part of the configuration to avoid trouble with resource leakage on the MGW, so lets make (especially novice) users aware of that option. Change-Id: I19c499c6ac83d7f9437b18b372977f6f2d518adf Depends: osmo-mgw I47e7ff858d5067b46d52329be5f362ff61c0dff8 Related: SYS#5535
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc
index ae177a926..3e48c4a59 100644
--- a/doc/manuals/chapters/running.adoc
+++ b/doc/manuals/chapters/running.adoc
@@ -139,7 +139,12 @@ Here is an example configuration for a remote MGW:
msc 0
mgw remote-ip
mgw remote-port 2427
+ mgw reset-endpoint rtpbridge/* <1>
+<1> The 'reset-endpoint' setting instructs the OsmoBSC to send a wildcarded
+DLCX to the media gateway. This helps to clear lingering calls from the
+media gateway when the OsmoBSC is restarted.
==== Configure Lb to connect to an SMLC