How to setup Mediatrix - Revision history

Pola.drakopoulou: /* Software Deployment */

2025-08-01T07:52:52Z

‎Software Deployment

Maria.nani: /* Software Deployment */

2024-07-22T08:01:40Z

‎Software Deployment

Konstantinos Kontogiannis at 09:42, 4 June 2018

2018-06-04T09:42:18Z

Konstantinos Kontogiannis at 13:03, 18 August 2016

2016-08-18T13:03:55Z

Konstantinos Kontogiannis at 12:15, 18 August 2016

2016-08-18T12:15:22Z

Konstantinos Kontogiannis at 12:14, 18 August 2016

2016-08-18T12:14:28Z

Konstantinos Kontogiannis at 11:12, 18 August 2016

2016-08-18T11:12:09Z

Konstantinos Kontogiannis: Created page with "
{{up}} How to collection and tutorials for OpenScape Deployment Service
{{Breadcrumb|0|0|How To}} The Mediatrix Gateway is treated by DLS..."

2016-08-18T10:54:27Z

Created page with "<div class="breadcrumb"> {{up}} How to collection and tutorials for OpenScape Deployment Service </div> {{Breadcrumb|0|0|How To}} The Mediatrix Gateway is treated by DLS..."

New page

<div class="breadcrumb">
{{up}} [[How to collection and tutorials for OpenScape Deployment Service]]
</div>

{{Breadcrumb|0|0|How To}}

The Mediatrix Gateway is treated by DLS like a DCMP enabled device. DLS cannot contact directly with the Mediatrix Gateway. The DCMP-like configuration is part of the Plug&Play and Registration of the Mediatrix Gateways on DLS and is described below. The actual DCMP configuration of DLS is not applicable for Mediatrix Gateways.

== Register configured Mediatrix Gateways on DLS ==

On the Mediatrix Web Management the following settings must be configured in order for Mediatrix to be aware of the DLS IP and initial settings.

Go to '''Management''' > '''Configuration Scripts'''> '''Execute Scripts'''.

Set:

a. Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%

b. Transfel Protocol: HTTP

c. Host Name: {IP/Hostname of DLS}:18080

d. Location: /DeploymentService/DlsMediatrixServlet/

[[File:Mediatrix1.jpg]]

The above settings could either be set manually or automatically with DHCP.
After configuring the above, press '''Apply & Execute Now'''. The Mediatrix Gateway will register on DLS.

== Plug & Play ==

The following steps are required in order to register a Mediatrix Gateway to DLS

1.Go to IP Device Configuration and create a new Virtual Device with Device Family Mediatrix Gateway. Required for the Plug&Play is the Device ID, which is the MAC Address of the Mediatrix in capital letters without semicolons (i.e. 0090F803768F)

@@ Line 72: / Line 72: @@
-== Software Deployment ==
+<h1>Software Deployment</h1>
-The procedure for the Software Deployment is the typical one with one exception. The Mediatrix Firmware is a zip file. The zip files need to be put in the selected FTP/HTTPS Server’s folder and the content of the zip files also need to be extracted there. Both are needed. The rest of the procedure is the exact same. The Software Deployment job is treated like the rest of the Jobs.
+Software deployment follows the standard DLS procedure, with a key difference for ZIP files:
-''' NOTE: Do not unpack the zip file contents to a subfolder otherwise it won't be properly acknowledged by DLS and consequently Mediatrix s/w deployment won't be possible.'''
+- ZIP file must be placed in the FTP/HTTPS root folder.<br>
-Since DGW 2.0 version 37 (released in September 2016) a new firmware file format, the BIN format, has been introduced for Mediatrix devices. This new format is easier to use than the previous ZIP format as it does not have to be extracted on a file server prior to the installation. The ZIP file format is now deprecated and will no longer be supported once the DGW version 44.0 is released. We highly recommend that on the next maintenance upgrade of your Mediatrix devices, you use the BIN format.
+<div style="background-color:#eae6ff; border-left: 4px solid #6554c0; padding: 10px; margin-top: 16px;">
-All devices with a firmware prior to DGW 2.0 version 37 will not be upgradable directly to a firmware version higher than 44.0. Upgrading these devices to a version higher than 44.0 will first require a transitional upgrade to version 44.0.

← Older revision		Revision as of 08:01, 22 July 2024
Line 76:		Line 76:
	The procedure for the Software Deployment is the typical one with one exception. The Mediatrix Firmware is a zip file. The zip files need to be put in the selected FTP/HTTPS Server’s folder and the content of the zip files also need to be extracted there. Both are needed. The rest of the procedure is the exact same. The Software Deployment job is treated like the rest of the Jobs.		The procedure for the Software Deployment is the typical one with one exception. The Mediatrix Firmware is a zip file. The zip files need to be put in the selected FTP/HTTPS Server’s folder and the content of the zip files also need to be extracted there. Both are needed. The rest of the procedure is the exact same. The Software Deployment job is treated like the rest of the Jobs.

−	''' NOTE:Do not unpack the zip file contents to a subfolder otherwise it won't be properly acknowledged by DLS and consequently Mediatrix s/w deployment won't be possible.'''	+	''' NOTE: Do not unpack the zip file contents to a subfolder otherwise it won't be properly acknowledged by DLS and consequently Mediatrix s/w deployment won't be possible.'''
		+
		+	Since DGW 2.0 version 37 (released in September 2016) a new firmware file format, the BIN format, has been introduced for Mediatrix devices. This new format is easier to use than the previous ZIP format as it does not have to be extracted on a file server prior to the installation. The ZIP file format is now deprecated and will no longer be supported once the DGW version 44.0 is released. We highly recommend that on the next maintenance upgrade of your Mediatrix devices, you use the BIN format.
		+
		+	All devices with a firmware prior to DGW 2.0 version 37 will not be upgradable directly to a firmware version higher than 44.0. Upgrading these devices to a version higher than 44.0 will first require a transitional upgrade to version 44.0.

← Older revision		Revision as of 09:42, 4 June 2018
Line 75:		Line 75:

	The procedure for the Software Deployment is the typical one with one exception. The Mediatrix Firmware is a zip file. The zip files need to be put in the selected FTP/HTTPS Server’s folder and the content of the zip files also need to be extracted there. Both are needed. The rest of the procedure is the exact same. The Software Deployment job is treated like the rest of the Jobs.		The procedure for the Software Deployment is the typical one with one exception. The Mediatrix Firmware is a zip file. The zip files need to be put in the selected FTP/HTTPS Server’s folder and the content of the zip files also need to be extracted there. Both are needed. The rest of the procedure is the exact same. The Software Deployment job is treated like the rest of the Jobs.
		+
		+	''' NOTE:Do not unpack the zip file contents to a subfolder otherwise it won't be properly acknowledged by DLS and consequently Mediatrix s/w deployment won't be possible.'''

@@ Line 9: / Line 9: @@
 == Register configured Mediatrix Gateways on DLS ==
-On the Mediatrix Web Management the following settings must be configured in order for Mediatrix to be aware of the DLS IP and initial settings.
+On the '''Mediatrix Web Management''' the following settings must be configured in order for Mediatrix to be aware of the DLS IP and initial settings.
@@ Line 16: / Line 16: @@
 Set:
-* Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
+* '''Generic File Name''': ?macaddress=%mac%&version=%version%&product=%product%
-* Transfel Protocol: HTTP
+* '''Transfel Protocol''': HTTP
-* Host Name: {IP/Hostname of DLS}:18080
+* '''Host Name''': {IP/Hostname of DLS}:18080
-* Location: /DeploymentService/DlsMediatrixServlet/
+* '''Location''': /DeploymentService/DlsMediatrixServlet/
 [[File:Mediatrix1.jpg]]
@@ Line 35: / Line 35: @@
 . On DLS, proceed with the following steps:
-a. Go to IP Device Configuration and create a new Virtual Device with Device Family Mediatrix Gateway. Required for the Plug&Play is the Device ID, which is the MAC Address of the Mediatrix in capital letters without semicolons (i.e. 0090F803768F)
+a. Go to '''IP Device Configuration''' and create a new Virtual Device with Device Family Mediatrix Gateway. Required for the Plug&Play is the Device ID, which is the MAC Address of the Mediatrix in capital letters without semicolons (i.e. 0090F803768F)
 [[File:Mediatrix2.jpg]]
-b. Go to Mediatrix Gateway Configuration and do the rest of the configuration.
+b. Go to '''Mediatrix Gateway Configuration''' and do the rest of the configuration.
-* In the Configuration Scripts Tab the “Time Unit” and the “Period” indicate how often the Mediatrix Gateway will contact DLS for Jobs waiting to be executed (DCMP-like configuration)
+* In the '''Configuration Scripts''' Tab the '''Time Unit''' and the '''Period''' indicate how often the Mediatrix Gateway will contact DLS for Jobs waiting to be executed (DCMP-like configuration)
 [[File:Mediatrix3.jpg]]
-* In the Configuration Tab the complete list of settings can be added by Copy/Paste from another already registered Mediatrix Gateway or from a Template/Profile, in order to set values different from the default ones. The Configuration text area can be left empty. The current settings of the Mediatrix Gateway will not be affected.
+* In the '''Configuration''' Tab the complete list of settings can be added by Copy/Paste from another already registered Mediatrix Gateway or from a Template/Profile, in order to set values different from the default ones. The Configuration text area can be left empty. The current settings of the Mediatrix Gateway will not be affected.
@@ Line 58: / Line 58: @@
-* Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
+* '''Generic File Name''': ?macaddress=%mac%&version=%version%&product=%product%
-* Transfel Protocol: HTTP
+* '''Transfel Protocol''': HTTP
-* Host Name: {IP/Hostname of DLS}:18080
+* '''Host Name''': {IP/Hostname of DLS}:18080
-* Location: /DeploymentService/DlsMediatrixServlet/
+* '''Location''': /DeploymentService/DlsMediatrixServlet/
 [[File:Mediatrix5.jpg]]

@@ Line 58: / Line 58: @@
-a. Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
+* Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
-b. Transfel Protocol: HTTP
+* Transfel Protocol: HTTP
-c. Host Name: {IP/Hostname of DLS}:18080
+* Host Name: {IP/Hostname of DLS}:18080
-d. Location: /DeploymentService/DlsMediatrixServlet/
+* Location: /DeploymentService/DlsMediatrixServlet/
 [[File:Mediatrix5.jpg]]

← Older revision		Revision as of 11:12, 18 August 2016
Line 33:		Line 33:
	The following steps are required in order to register a Mediatrix Gateway to DLS		The following steps are required in order to register a Mediatrix Gateway to DLS

−	1.Go to IP Device Configuration and create a new Virtual Device with Device Family Mediatrix Gateway. Required for the Plug&Play is the Device ID, which is the MAC Address of the Mediatrix in capital letters without semicolons (i.e. 0090F803768F)	+	1. On DLS, proceed with the following steps:
		+
		+	a. Go to IP Device Configuration and create a new Virtual Device with Device Family Mediatrix Gateway. Required for the Plug&Play is the Device ID, which is the MAC Address of the Mediatrix in capital letters without semicolons (i.e. 0090F803768F)
		+
		+	[[File:Mediatrix2.jpg]]
		+
		+	b. Go to Mediatrix Gateway Configuration and do the rest of the configuration.
		+
		+	* In the Configuration Scripts Tab the “Time Unit” and the “Period” indicate how often the Mediatrix Gateway will contact DLS for Jobs waiting to be executed (DCMP-like configuration)
		+
		+	[[File:Mediatrix3.jpg]]
		+
		+
		+	* In the Configuration Tab the complete list of settings can be added by Copy/Paste from another already registered Mediatrix Gateway or from a Template/Profile, in order to set values different from the default ones. The Configuration text area can be left empty. The current settings of the Mediatrix Gateway will not be affected.
		+
		+
		+	[[File:Mediatrix4.jpg]]
		+
		+
		+
		+	2. On the Mediatrix Web Management the following settings must be configured in order for Mediatrix to know the DLS IP and initial settings.
		+
		+	Go to '''Management''' > '''Configuration Scripts''' > '''Execute Scripts'''. Set:
		+
		+
		+	a. Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
		+
		+	b. Transfel Protocol: HTTP
		+
		+	c. Host Name: {IP/Hostname of DLS}:18080
		+
		+	d. Location: /DeploymentService/DlsMediatrixServlet/
		+
		+	[[File:Mediatrix5.jpg]]
		+
		+	The above settings could either be set manually or automatically with DHCP.
		+	After configuring the above, press '''Apply & Execute Now'''. The Plug & Play shall start.
		+
		+
		+	== Software Deployment ==
		+
		+	The procedure for the Software Deployment is the typical one with one exception. The Mediatrix Firmware is a zip file. The zip files need to be put in the selected FTP/HTTPS Server’s folder and the content of the zip files also need to be extracted there. Both are needed. The rest of the procedure is the exact same. The Software Deployment job is treated like the rest of the Jobs.