- Sentinel 100
- Sentinel 400
- Mediatrix S7 and S7 LP Series
- Mediatrix G7 Series
- Mediatrix C7 Series
- Mediatrix 4100 Series
- Mediatrix 3000 Series
- Mediatrix 4400 Series
- Mediatrix LP Series
The DGW 2.0 platform contains major differences compared to the MGCP 5.0 platform. You may thus encounter some behavioral differences after upgrading to DGW 2.0. Media5 strongly recommends to fully test your scenarios in a controlled environment before deploying a live unit running DGW 2.0.
Although this procedure has been used with success to upgrade from MGCP 5.0 to DGW 2.0, please note that this procedure has not been fully tested by our QA team.
|DHCP vendor options||The DHCP vendor options from MGCP 5.0 are no longer supported. The following parameters will now need to be configured manually or via configuration scripts:|
|Image Primary Server||Fpu.MfpTransferSrvHostname|
|Image Secondary Server||Fpu.MfpTransferSrvHostname|
|File fetching host||Conf.ScriptsTransferSrvHostname|
|SIP Presence Compositor||SipEp. DefaultStaticPresenceCompositorServerHost|
MGCP 5.0 supported a netmask of 255.255.255.254 (/31) and a default router 0.0.0.0.
In DGW 2.0, the limitation is a netmask of 255.255.255.252 (/30).
A network configuration with /31 will not be transferred, and the rest of the configuration will not be transferred as well.
Please note that the following MIB variables may not contain the “:” character, or any other special characters (é à è : > < | ^ * ? etc). If one of these characters is present, some parts of the configuration will not be transferred during the upgrade process.
|Public and private keys||
DGW 2.0 contains a single key parameter for the configuration file encryption (Conf.ScriptsSecretKey). Therefore only one of the public and private keys will be transferred, according to the following algorithm:
|DHCP WAN Address||On units with two network interfaces, DGW 2.0 assigns the address ‘192.168.0.10’ to the LAN interface. If the DHCP server provides an address to the WAN interface in the 192.168.0.0/24 subnet, the unit disables the WAN interface. In this condition, the unit’s Power LED will blink and no configuration script will be fetched.|
|Config file fetching server||When using the File Fetching feature in MGCP 5.0 or the Configuration Script feature in DGW 2.0, a valid server IP/FQDN address and protocol must be configured. To avoid upgrade problem, the server must be reachable by the Mediatrix unit during the upgrade or downgrade procedure.|
The firmware versions are subject to change. Please refer to our the Support Portal .
The DGW 220.127.116.114 firmware pack, is the first transition load and is installed using UMN. All other firmware packs are installed using the DGW Web interface.
The firmware versions are subject to changes. Please refer to our Support Portal .
Perform this procedure if you plan to use the FTP transport protocol.
If the file server is located behind a firewall, make sure that TCP port 21 is open.
If the file server is located behind a firewall, make sure the UDP port 69 is open.
If the file server is located behind a firewall, make sure the TCP port 80 is open.
If the file server is located behind a firewall, make sure the TCP port 443 is open.
Warning messages received during this procedure will also be available as comments in the DGW 2.0 script files. If an error message is received, the procedure must be restarted once the error is corrected.
The UMN then takes the unit's MGCP 5.0 configuration file located in the UnitManager\CfgFile folder, and converts it to the DGW format. The new file is saved as XXXXXXXXXXXX_DGW_Script.cfg in the UnitManager\CfgFile folder of the server (HTTP or TFTP), where the Xs correspond to the unit's MAC address.
You can unzip the files on any computer. However, keep in mind that the upgrade will be performed using the firmware pack files located on the file server only. Therefore, the folder containing the unzipped files must be copied to the file server (MediatrixXXXX folder).
Do not change the name of the unzipped folder.
The MediatrixXXXX folder is typically installed at the root folder of the file server. You may choose another path, but the root of the path must be on the file server, otherwise the upgrade will fail.
The extracted firmware folders should have these names (depending on the model):
If a Factory reset is done at any time after the upgrade procedure, the configuration file for SIP 5.0 will be lost and the Mediatrix unit will not be configured after the Downgrade Procedure to SIP 5.0 is completed. If for some reason the DGW unit becomes unreachable, the partial reset feature will allow the unit to obtain or use a known IP address.
The unit will restart again and be ready for configuration. The unit will download the configuration scripts and complete the migration to DGW 2.0. Once the configuration scripts are downloaded, the Mediatrix unit will restart once again.
Once the unit is using DGW 2.0, it must be redetected in UMN to continue using UMN to manage it.
Our QA tests cover ten versions back for each new release. If you are upgrading from a load older than ten releases back, you must install an intermediate version before upgrading to the newest one.
Depending on the type of protocol you will use, the following procedures must be completed.
If you are not sure of the version number of your firmware pack, refer to Examples of Firmware Pack Versions.
If you choose Disable, the unit must be manually restarted in order to complete the upgrade.
This provides a delay for the telephony calls to be terminated before the unit is restarted. When there are no active calls, the unit will restart immediately. If you wish to allow a delay for the services, set the same parameter under System/Services.
Remember that the name is case sensitive.
This must be consistent with the file server you have configured.
If the MediatrixXXXX folder was copied in the root of the file server, this field must remain empty.
Make sure the file server is started.
When the firmware pack update fails, the Mediatrix unit tries to download the firmware three times.
|Firmware Pack||Version Number|
Depending on your Mediatrix unit model, one of the following firmware pack should be extracted to the root of your server (FTP, TFTP, HTTPS or HTTP ). Refer to Extracting the Firmware Pack ZIP File.
|MGCP 5.0 Parameter||DGW 2.0 Equivalents|
|localHostStaticAddress||Bni.NetworkInterfaces.StaticIpAddr (Uplink - Wan)|
Copyright © 2018 Media5 Corporation.
This document contains information that is proprietary to Media5 Corporation.
Media5 Corporation reserves all rights to this document as well as to the Intellectual Property of the document and the technology and know-how that it includes and represents.
This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever, without written prior approval by Media5 Corporation.
Media5 Corporation reserves the right to revise this publication and make changes at any time and without the obligation to notify any person and/or entity of such revisions and/or changes.