Sbc "Drop early media" and "Drop SDP from 1xx replies" rulesets were not functional.
DGW-17218
Upgrade Dropbear SSH server to version 2025.88
DGW-17219
Upgrade wpa_supplicant client to version 2.11
ID-9495 / ID-10289
DGW-17223
Fixed wrong message for stopped DGW services.
ID-10331
DGW-17287
FQDN starting with digits are now accepted by the Hoc.InsertStaticHost parameter
DGW-17288
Upgrade to OpenSSL 3.5.0
DGW-17351
New parameters added to the Dcm.PasswordEncryption table
DGW-17356
Support RFC8760 (SIP auth SHA256) for SIP client authentication
ID-10433
DGW-17395
Web service does not send complete certificate chain in TLS handshake
New Features
DGW-17356 - Support RFC8760 (SIP auth SHA256) for SIP client authentication
The SipEp service now supports RFC 8760 authentication. Supported algorithms are:
MD5
MD5-sess
SHA-256
SHA-256-sess
SHA-512-256
SHA-512-256-sess
DGW-17351 - New parameters added to the Dcm.PasswordEncryption table
The following parameters were added to the Dcm.PasswordEncryption table.
Conf.ScriptsTransferPassword
Conf.ScriptsSecretKey
Conf.ScriptExportSecretKey
Conf.ImageTransferPassword
Conf.ImageSecretKey
Cwmp.Password
Cwmp.ConnectionRequestPassword
Fpu.MfpTransferPassword
Moh.Password
Snmp.PrivPassword
Snmp.SnmpV3Password
Note:
Moh.Password and Snmp.PrivPassword now have a maximum length of 63. Passwords with a length greater than 63 will be lost when upgrading.
DGW-17288 - Upgrade to OpenSSL 3.5.0
The application was re-built using OpenSSL 3.5.0.
The DGW application now prioritizes tls1.3 over tls1.2 when both version are supported.
DGW-17219 - Upgrade wpa_supplicant client to version 2.11
The application was re-built using wpa_supplicant client version 2.11.
DGW-17218 - Upgrade Dropbear SSH server to version 2025.88
The application was re-built using Dropbear SSH server version 2025.88.
DGW-17190 - Configuration from DGW 48.1.2503 or older may not be correctly converted when upgrading to DGW 50.0
The automatic configuration conversion for DGW 48.1.2503 or older are no more supported on DGW 50.0.
Devices must be upgraded to DGW 48.2.2567, or newer, before upgrading to DGW 50.0.
DGW-17168 - Codecs default ptime changed to 20ms
The default minimum ptime of the following parameters has been changed to 20ms
Mipt.DefaultCodecG711MulawMinPTime
Mipt.EpSpecificCodecG711Mulaw.MinPTime
Mipt.DefaultCodecG711AlawMinPTime
Mipt.EpSpecificCodecG711Alaw.MinPTime
Mipt.DefaultCodecG726r16kbpsMinPTime
Mipt.EpSpecificCodecG726r16kbps.MinPTime
Mipt.DefaultCodecG726r24kbpsMinPTime
Mipt.EpSpecificCodecG726r24kbps.MinPTime
Mipt.DefaultCodecG726r32kbpsMinPTime
Mipt.EpSpecificCodecG726r32kbps.MinPTime
Mipt.DefaultCodecG726r40kbpsMinPTime
Mipt.EpSpecificCodecG726r40kbps.MinPTime
Mipt.DefaultCodecG729MinPTime
Mipt.EpSpecificCodecG729.MinPTime
TheSipEp.InteropSdpPTimeAttributeValue parameter's default value has also been changed to 20ms
DGW-17040 - The VNC server used by the VM service can now be automatically disabled after a configurable period.
Incident Number: ID-9791
Two new settings allowing to automatically disable the VNC server after a certain delay have been added.
When the feature is enabled (Vnc.AutomaticVncShutdownEnable), a VM's VNC ID (Vm.Vm.VncDisplayId) will automatically be set to -1 (disabled) upon expiration of the specified timer (Vm.AutomaticVncShutdownTimer), starting from the virtual machine startup.
DGW-16996 - SipEp - Added new parameter TransportPersistentDisconnectOnSipTransmissionErrorEpGw
Incident Number: ID-9024
Added new parameter named SipEp.TransportPersistentDisconnectOnSipTransmissionErrorEpGw to failover on either REGISTER only or ALL requests
DGW-16770 - Telephony and network interfaces have been renamed on the Mediatrix 4102S
The network and telephony interfaces on the Mediatrix 4102S have been renamed:
wan --> eth1
lan --> eth2
Phone-Fax1 --> FXS1
Phone-Fax2 --> FXS2
Configuration scripts with the old naming are fully supported, provisioning and management are not impacted by this change.
Issues Fixed
DGW-17395 - Web service does not send complete certificate chain in TLS handshake
Incident Number: ID-10433
Fixed an issue where the Web service would not send the complete certificate chain during the TLS handhsake.
DGW-17287 - FQDN starting with digits are now accepted by the Hoc.InsertStaticHost parameter
Incident Number: ID-10331
The validation of the Hoc.InsertStaticHost parameter has been updated to accept FQDN that starts with digits.
DGW-17223 - Fixed wrong message for stopped DGW services.
Incident Number: ID-9495 / ID-10289
Replace the wrong message "Feature activation licence is required. " on the TelIf, CRout and EpAdm services when there is no telephony interfaces to "Waiting for HW dependencies to be resolved. ".
Moreover, the services that depends on the TelIf service will now display "Waiting for dependencies to be resolved (service is not started). " in that case.
DGW-17208 - Sbc "Drop early media" and "Drop SDP from 1xx replies" rulesets were not functional.
Incident Number: ID-10149
Sbc "Drop early media" and "Drop SDP from 1xx replies" rulesets are now working as expected.
Fixed an issue that preventedSbc.SignalingInterface.ForceLocalClientPort from working.
DGW-17047 - TFTP download failure caused by invalid data re-transmission
Incident Number: ID-10022
TFTP service re-transmits invalid data after not receiving a first ACK, and ignores an ACK re-transmission.
DGW-17045 - An incorrect CallerID may be displayed on incoming FXO calls after a previous cancelled call when WaitForCalleeToAnswer feature is enabled
When WaitForCalleeToAnswer is enabled, if an unanswered incoming FXO call is cancelled on the PSTN side, and there is a new incoming FXO call on a short delay, the call could display the previous CallerID instead of the current one.
The issue is now fixed by automatically cancelling and recreating the call upon detection of a new CallerID.
DGW-17043 - First FXO incoming call after Pots service start-up may fail when Pots.FxoLinkStateVerification parameter is enabled
Incident Number: ID-10039
Fixed a failed incoming FXO to SIP calls issue after Pots service start-up when Pots.FxoLinkStateVerification parameter was enabled:
When answered, only a noise is played to the caller, and the ringing tone keeps playing to the caller, as if the call was unanswered.
If unanswered, even if the call is ended by the caller, the called party phone keeps ringing.
The issue was triggered by every FXO port physical line disconnection and reconnection, requiring a POTS service restart, a unit reboot, or a SIP to FXO call.
DGW-16669 - Fixed the used RAM calculation on the Mediatrix 4102.
On the Mediatrix 4102 a calculation error that underestimated the used RAM was fixed.
Known Issues
There are no known issues.
Copyright Notice
Copyright 2025 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.