DGW Release Notes v45.0.1809

The MX profile now attempts a connection to the Virtuo server. If the unit is managed by the Virtuo server, it will get provisioned by it.

When NTP server is temporarily unreachable on startup before any TLS communications, the unit will use the most recent among:

• Previously persisted date/time
• Firmware build date/time
• Unit produced date

Then TLS communications can establish successfully.

When the unit starts with a reachable NTP server, the unit system time will be synchronized properly.

The Mediatrix S7/G7/C7 Series and the Sentinel 100/400 can now activate, for FXS ports, the Visual Message Waiting Indicator (VMWI) light with a high voltage signal, which is needed by some phone models frequently found in hospitality environment.

The actual voltage depends on the platform:

• The Mediatrix S7 LP Series support up to 115 Vdc
• The Mediatrix S7 Series (non-LP), C7/G7 Series and Sentinel 100/400 support up to 80 Vdc

Since most phone that have VMWI with a high voltage light typically need 90 Vdc, it is recommended, for increased reliability, to use the S716 LP or the S724 LP.

See the Pots.FxsDefaultVisualMessageWaitingIndicatorType parameter on how to configure this feature.

LIMITATION on the S7 LP Series: If a phone has a REN (Ringer Equivalence Number) of 4 or higher, the unit may falsely detect that the phone has gone "off-hook" for a very brief period. This false detection may cause incoming calls to be rejected by the unit since it considers the line temporarily in-use.

LIMITATION on the C7 Series (Revision 0): The high voltage VMWI is not available on units of the Mediatrix C7 Series with a Serial Number starting with one of the following:

• Mediatrix C710 (Rev. 0): 0027800xxxxxxxxxxxx or 27800xxxxxxxxxxxx
• Mediatrix C711 (Rev. 0): 0027900xxxxxxxxxxxx or 27900xxxxxxxxxxxx
• Mediatrix C731 (Rev. 0): 0028200xxxxxxxxxxxx or 28200xxxxxxxxxxxx

The new ContactOverrideEnable parameter was added which enables the modification of the Contact header of REGISTER requests with the IP address and port of the proxy. The new parameter is available in the DGW Web interface under SIPProxy/Configuration.

Two new CA certificates have be included in the MX profile to trust the Virtuo cloud-EMS provisioning service.

The MS profile is no longer built.

IN-14241

When RTP packets from an unwanted source is received during an active call, the audio is no longer heard. 

Fixed the Mipt.EnforceSymmetricRtpEnable parameter. Now when the parameter is set to "Enable", it will ignore all packets from a different IP source.

The new ContactOverrideEnable parameter was added which enables the modification of the Contact header of REGISTER requests with the IP address and port of the proxy. The new parameter is available in the DGW Web interface under SIP Proxy/Configuration.

The SIP proxy uses this contact override mechanism to ensure that the server sends calls to the proxy when contacting the registered endpoints. When forwarding REGISTERs, the proxy replaces the host/port of the contacts by the SIP proxy host/port and adds a proprietary URI parameter named "x-mtx-ob" containing the original host/port encoded in base 64. When receiving a request with the parameter x-mtx-ob, the proxy replaces the request-URI host/port by the host/port of the x-mtx-ob parameter and removes the parameter. The request is then forwarded to the new destination.

When the Ems service was attempting to contact the Virtuo server, some confusion was created because the Conf service was updating script execution statuses and was issuing notifications about script download and execution. To reduce this confusion, when the Conf service executes a script on behalf of the Ems service, the Conf service no longer updates the ScriptsStatsCurrentTransferState, ScriptsStatsLastTransferResult, and ScriptsStatsLastTransferDateTime parameters and no longer issues the notifications related to script downloads.

The Hoc.StaticSntpServers table could not get values from a profile at upgrade time because the previous versions already filled this table using the default value of the obsolete Hoc.StaticSntpServersHost parameter.

The default value of the obsolete Hoc.StaticSntpServersHost parameter is no longer used to provide a value to the Hoc.StaticSntpServers parameter. When upgrading:

• if the Hoc.StaticSntpServers table contains only the default value from Hoc.StaticSntpServersHost parameter, it is removed and replaced with the value provided in the profile.
• if the profile contains no value for the Hoc.StaticSntpServersHost parameter, the table then contains only empty entries.

The EpServ.DefaultSecondCallDisconnectAction and EpServ.EpSpecificSecondCall.DisconnectAction parameters are now available from CWMP.