DGW-15839 - Sentinel 400/RS: New fan control and temperature monitoring.

The Sentinel 400 and Sentinel RS platforms can now monitor the status of the fans and temperature, for units manufactured after January 2019.

• The SSD wear percentage, fans and temperatures status are now available in the WEB pager under "System"/"Hardware".
• New notifications added:
  • Dcm.80: Sent when a fan is in fault.
  • Dcm.90: Sent when a temperature is in fault.
  • Dcm.95: Sent when the temperature is no more in fault.
  • Dcm.100: Sent when all fans are in fault or there is an internal hardware communication problem with one of the fan controller.
• Added a new parameter Hardware.FanCheckOnBootEnable. If enabled, the fans will run at 100% for a few seconds during the booting process in order to detect hardware faults.
• The following provisioning tables were added for the Sentinel 400 and Sentinel RS
  • HardwareFanInfo:used to monitor if there are fans in fault.
  • HardwareTemperatureInfo:used to monitor the temperature, monitor the temperature faults and to set thresholds at which the temperature faults are triggered.
• CWMP: Added the complete Device.Services.X_0090F8_Dcm. tree including the following tables on Sentinel 400 and RS:
  • Device.Services.X_0090F8_Dcm.HardwareInfo.HardwareFanInfo. (FAN support)
  • Device.Services.X_0090F8_Dcm.HardwareInfo.HardwareTemperatureInfo. (Temperature support)

DGW-15808 - Generation of SSH keys should not delay initial startup.

4102 and C7 devices took a long time to perform their initial boot-up because the SSH key generation was blocking the boot sequence until that step was complete.

DGW no longer waits for the SSH keys generation at initial boot-up which allow the device to be ready faster.

The SSH keys are now generated in the background and the SSH serverstarted as soon as the key generation is complete.

DGW-15803 - SBC: Increased the maximum size of Sbc.CallAgent, Sbc.SignalingInterface and Sbc.MediaInterface tables.

The maximum size of the Sbc.CallAgent table was increased from 15 to 50.
The maximum size of the Sbc.SignalingInterface and Sbc.MediaInterface tables was increased from 10 to 25.

DGW-15653 - CLI: Remove unsecure algorithm and improve the QoS from the SSH server.

Upgraded to DropBear SSH 2022.82 for CLI management.

Following key exchange algo was removed:

• diffie-hellman-group1-sha1

Following encryption ciphers were removed:

• 3des-ctr
• 3des-cbc
• aes256-cbc
• aes128-cbc

QoS: The SSH connection now uses a AF21 class of service for better network priorisation.

DGW-15392 - Increase default media port range for SBC on Sentinel RS in MX profile.

The default media port range for the SBC was increased to 20000-49999 on the Sentinel RS in the MX profile.

DGW-15819 - Fixed clock drift issues inside virtual machines (VM).

Incident Number: IN-15472

The kvm-clock modules were statically compiled into the kernel. This caused a clock skew inside Virtual Machines for some architectures.

The appropriate module for each specific CPU platform is now loaded at run-time during the VM service startup.

DGW-15772 - Fixed Netlink buffer issue on the Sentinel CS.

Incident Number: IN-15433

Fixed a Netlink buffer issue where the application would crash randomly on the Sentinel CS using Proxmox and complex network configuration.

DGW-15135 - The SipProxy service does not always restore original contact when forwarding a REGISTER 200 OK response.

Incident Number: IN-15108

When using the contact override feature and forwarding REGISTER 200 OK response, the SipProxy service only restored the original contacts if the host/port matched the SipProxy.

The SipProxy service will now restore the contacts event if it's don't match the SipProxy host/port.

DGW-15037 - Endpoint gateway can initiate a failover to a secondary service if an INVITE request fails because of a transmission timeout.

Incident Number: IN-15276

The Endpoint Gateway will now only initiate a failover to a secondary service if the transmission timeout occurs on the REGISTER request.