Deployment of Media Gateway in a Network
The following diagram shows how the Media Gateway must be deployed in a network on a separate voice LAN from the management LAN. The separate voice LAN is connected to the UCX Server via the Ethernet1 port interface. (See Configure a Second Network Port for configuration instructions.)
The following table provides a list of network configuration parameters that you should prepare:
Parameter | Default Value | Selected Value |
|---|---|---|
| UCX Server IP address | 192.168.1.200 (Ethernet0) 192.168.10.200 (Ethernet1) | _____ . _____ . _____ . _____ _____ . _____ . _____ . _____ |
| MGC ELAN IP Address | _____ . _____ . _____ . _____ | |
| MGC ELAN Subnet Mask | 255.255.255.0 | _____ . _____ . _____ . _____ |
| MGC ELAN Gateway IP Address | _____ . _____ . _____ . _____ | |
| MGC TLAN IP Address | _____ . _____ . _____ . _____ | |
| MGC TLAN Subnet Mask | 255.255.255.0 | _____ . _____ . _____ . _____ |
| MGC TLAN Gateway IP Address | _____ . _____ . _____ . _____ | |
| MGC DSP Daughterboard Slot1 TLAN IP address | _____ . _____ . _____ . _____ | |
| MGC DSP Daughterboard Slot2 TLAN IP address | _____ . _____ . _____ . _____ |
The IP addresses assigned to UCX Server, MGC ELAN, MGC TLAN and MGC DSP daughterboard TLAN must be in the same subnet. (e.g. 192.168.10.x as in the diagram above).
In Release 6.0 and later, MGCs can register to the UCX Server at a remote location over the internet, however the MGC ELAN and TLAN IP addresses need to be in the same subnet.
Network Latency Limitation
If the network latency exceeds 500ms, performance of the MGC will be affected. This may include service affecting conditions like the MGC link going down. To recover from the condition, resolve the latency issue in the network and the MGC signalling connection will re-establish on its own.
This network latency issue would typically occur when the MGC is remotely registered via the internet to UCX in the Cloud.
