Browse Source

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
pmaier/mgw2
Philipp Maier 7 months ago
parent
commit
9e46544486
  1. 5
      doc/examples/osmo-hnbgw/osmo-hnbgw.cfg
  2. 22
      doc/manuals/chapters/running.adoc

5
doc/examples/osmo-hnbgw/osmo-hnbgw.cfg

@ -23,3 +23,8 @@ hnbgw
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/*

22
doc/manuals/chapters/running.adoc

@ -117,3 +117,25 @@ hnbgw
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/*
----

Loading…
Cancel
Save