Difference between revisions of "How to setup Mediatrix"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
(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...") |
(→Software Deployment) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 9: | Line 9: | ||
== Register configured Mediatrix Gateways on DLS == | == 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: | Set: | ||
− | + | * '''Generic File Name''': ?macaddress=%mac%&version=%version%&product=%product% | |
− | + | * '''Transfel Protocol''': HTTP | |
− | + | * '''Host Name''': {IP/Hostname of DLS}:18080 | |
− | + | * '''Location''': /DeploymentService/DlsMediatrixServlet/ | |
[[File:Mediatrix1.jpg]] | [[File:Mediatrix1.jpg]] | ||
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: | ||
+ | |||
+ | |||
+ | * '''Generic File Name''': ?macaddress=%mac%&version=%version%&product=%product% | ||
+ | |||
+ | * '''Transfel Protocol''': HTTP | ||
+ | |||
+ | * '''Host Name''': {IP/Hostname of DLS}:18080 | ||
+ | |||
+ | * '''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. | ||
+ | |||
+ | |||
+ | <h1>Software Deployment</h1> | ||
+ | |||
+ | Software deployment follows the standard DLS procedure, with a key difference for ZIP files: | ||
+ | |||
+ | - ZIP file must be placed in the FTP/HTTPS root folder.<br> | ||
+ | - Its contents must also be extracted in the same root folder. | ||
+ | |||
+ | <div style="background-color:#eae6ff; border-left: 4px solid #6554c0; padding: 10px; margin-top: 16px;"> | ||
+ | <strong>Note:</strong> Do not unpack the zip file contents to a subfolder, otherwise it won't be properly <br> acknowledged by DLS and consequently Mediatrix software deployment won't be possible. | ||
+ | </div> | ||
+ | |||
+ | |||
+ | <h2>Supported Formats by DGW Version</h2> | ||
+ | |||
+ | <table border="1" cellpadding="6" cellspacing="0"> | ||
+ | <tr> | ||
+ | <th>DGW Version</th> | ||
+ | <th>Supported Format(s)</th> | ||
+ | <th>Notes</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>< 2.0.37</td> | ||
+ | <td>.zip only</td> | ||
+ | <td>Must extract contents to root. Subfolders not supported.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>2.0.37 – 43.x</td> | ||
+ | <td>.zip and .bin</td> | ||
+ | <td>Both formats supported. .bin is preferred.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>≥ 2.0.44</td> | ||
+ | <td>.bin only</td> | ||
+ | <td>.zip is ignored. Deployment silently fails.</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | |||
+ | |||
+ | <div style="background-color:#eae6ff; border-left: 4px solid #6554c0; padding: 10px; margin-top: 16px;"> | ||
+ | <strong>Note:</strong> Using a <code>.zip</code> file with DGW ≥ 44 will not trigger an error, <br> but DLS will silently ignore the package and the deployment will fail without notice. | ||
+ | </div> | ||
+ | |||
+ | <h2>Upgrade Tip</h2> | ||
+ | <p> | ||
+ | Devices running <strong>DGW < 2.0.37</strong> must first upgrade to <strong>DGW 44.0</strong> before installing any higher version. | ||
+ | </p> | ||
+ | |||
+ | <h2>Recommendation</h2> | ||
+ | <p> | ||
+ | Use the <code>.bin</code> format for all current and future Mediatrix firmware deployments. | ||
+ | </p> |
Latest revision as of 07:52, 1 August 2025
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.
Contents
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:
- Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
- Transfel Protocol: HTTP
- Host Name: {IP/Hostname of DLS}:18080
- Location: /DeploymentService/DlsMediatrixServlet/
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. 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)
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 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.
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:
- Generic File Name: ?macaddress=%mac%&version=%version%&product=%product%
- Transfel Protocol: HTTP
- Host Name: {IP/Hostname of DLS}:18080
- Location: /DeploymentService/DlsMediatrixServlet/
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
Software deployment follows the standard DLS procedure, with a key difference for ZIP files:
- ZIP file must be placed in the FTP/HTTPS root folder.
- Its contents must also be extracted in the same root folder.
Note: Do not unpack the zip file contents to a subfolder, otherwise it won't be properly
acknowledged by DLS and consequently Mediatrix software deployment won't be possible.
Supported Formats by DGW Version
DGW Version | Supported Format(s) | Notes |
---|---|---|
< 2.0.37 | .zip only | Must extract contents to root. Subfolders not supported. |
2.0.37 – 43.x | .zip and .bin | Both formats supported. .bin is preferred. |
≥ 2.0.44 | .bin only | .zip is ignored. Deployment silently fails. |
Note: Using a.zip
file with DGW ≥ 44 will not trigger an error,
but DLS will silently ignore the package and the deployment will fail without notice.
Upgrade Tip
Devices running DGW < 2.0.37 must first upgrade to DGW 44.0 before installing any higher version.
Recommendation
Use the .bin
format for all current and future Mediatrix firmware deployments.