dexter submitted this change.

View Change

running.adoc: explain MGW configuration

OsmoHNBGW now requires a co-located OsmoMGW instance. Lets add add some
info on how to configure it.

Change-Id: Id47f4f365cee78ce28d1534c4e3e98a59bdb0621
Related: OS#5152
---
M doc/examples/osmo-hnbgw/osmo-hnbgw.cfg
M doc/manuals/chapters/running.adoc
2 files changed, 27 insertions(+), 0 deletions(-)

diff --git a/doc/examples/osmo-hnbgw/osmo-hnbgw.cfg b/doc/examples/osmo-hnbgw/osmo-hnbgw.cfg
index 9286b2a..a683187 100644
--- a/doc/examples/osmo-hnbgw/osmo-hnbgw.cfg
+++ b/doc/examples/osmo-hnbgw/osmo-hnbgw.cfg
@@ -23,3 +23,8 @@
  iuh
   local-ip 0.0.0.0
   hnbap-allow-tmsi 1
+ mgcp
+  mgw remote-ip 127.0.0.1
+  mgw remote-port 2427
+  mgw reset-endpoint rtpbridge/*
+
diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc
index f40027a..6ad59a5 100644
--- a/doc/manuals/chapters/running.adoc
+++ b/doc/manuals/chapters/running.adoc
@@ -117,3 +117,25 @@
   local-ip 10.9.8.7
   local-port 29169
 ----
+
+==== Configure co-located media gateway
+
+OsmoHNBGW requires a co-located OsmoMGW instance. The purpose of the co-located
+media gateway is to relay the RTP traffic between hNodeB and the core network.
+
+For security reasons the RAN network is kept separate and isolated from the
+core network. Both networks will usually have no transparent routing in between
+them. The co-located media gateway provides an interface between hNodeB and core
+network across this boundary.
+
+The configuration is done under the hnbgw node along with `iucs` and `iups`.
+
+An example configuration for OsmoHNBGW's MGCP client:
+
+----
+hnbgw
+ mgcp
+  mgw remote-ip 127.0.0.1
+  mgw remote-port 2427
+  mgw reset-endpoint rtpbridge/*
+----

To view, visit change 26797. To unsubscribe, or for help writing mail filters, visit settings.