DGW-13730 - The maximum number of users supported by the Survivability Proxy should be increased.

Incident Number:

The maximum number of users supported by the Survivability Proxy was increased on the following platforms:

• On the Sentinel 100, the maximum went from 150 to 300.
• On the S7 series, the maximum went from 75 to 200.
• On the G7 series, the maximum went from 75 to 150.
• On the C7 series, the maximum went from 25 to 30.

DGW-13609 - Installing a licence that was previously installed prompt for some services to restart.

Incident Number:

Installing a licence that was previously installed no longer requires a service restart.

DGW-13557 - The SBC must support TLS 1.3.

Incident Number:

The SBC now supports TLS 1.3.

DGW-13553 - Web service does not support TLS 1.3.

Incident Number:

Web service now supports TLS 1.3.

DGW-13512 - Image backup and configuration scripts should support  AES-256 encryption algorithm.

Incident Number:

The AES-256 algorithm is now supported in addition to the previous default algorithm Blowfish. AES-256 is now the default value. The new algorithm can be configured in the WEB interface via the pages:

• "Management" / "Configuration Scripts" / "Export"
• "Management" / "Backup/Restore"

DGW-13505 - Two new ciphers need to be added to the CS3 cipher suite.

Incident Number:

Two new ciphers were added to the CS3 cipher suite TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 and TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256.

DGW-13462 - Support the DGW macros in SBC Ruleset Replacement Expressions.

Incident Number:

The following Ruleset Replacement Expressions are now supported by the Sbc service:

• $attr(mac)
• $attr(version)
• $attr(product)
• $attr(productseries)
• $attr(serial)
• $attr(profile)

DGW-13051 - SBC does not include the lifetime of the crypto in the SDP attributes.

Incident Number:

The crypto attribute included in the SDP payload now includes the key lifetime, hardcoded to 2^31.

DGW-13050 - Unable to add a custom header in the SIP OPTION messages sent by the SBC for the call agent keep-alive.

Incident Number:

It is now possible to add a custom header in the SIP OPTIONS messages sent by the SBC call agent keep-alive.

DGW-12976 -  SipEp service needs to support TLS version 1.3.

Incident Number:

TLS version 1.3 is now supported in the SipEp service. It now supports the new ciphers AES_256_GCM_SHA384, CHACHA20_POLY1305_SHA256, AES_128_GCM_SHA256, AES_128_CCM_8_SHA256, AES_128_CCM_SHA256.

DGW-12838 - Call transfers cannot be handled locally by the SBC. 

Incident Number: IN-14651

The new Call Transfer Handling action was added to configure how in-dialog SIP REFER requests are handled by the SBC. The following methods of SIP REFER handling can be used:

• Pass-through: pass SIP REFER request through the SBC to the remote peer (default)
• Reject: reject the SIP REFER request with a 403 Forbidden reply
• Handle internally: the SIP REFER request is handled locally by the SBC

DGW-12763 - The EpAdm service does not support to have EpAdm.UnitDisabledWhenNoGatewayReadyEnable and EpAdm.DisableSipGatewaysWhenTrunkLinesDown functionalities activated at same time.

Incident Number:

The EpAdm service now supports to have both EpAdm.UnitDisabledWhenNoGatewayReadyEnable and EpAdm.DisableSipGatewaysWhenTrunkLinesDown functionalities activated at same time.

DGW-13663 - Following a SIP REFER request, the Sbc service loses all URI parameters in the TO header of the SIP INVITE.

Incident Number:

The Mediatrix Sbc service did not properly generate the TO header in the SIP INVITE message following the SIP REFER request. All URI parameters were lost in transition from the Refer-TO header into the TO header. The Sbc service are now populated correctly the URI parameters.

DGW-13602 - Configuration Script and image backup do not support HTTP and HTTPS transfer protocol.

Incident Number:

HTTP and HTTPS is now supported as transfer protocol for configuration script and image backup.

DGW-13598 - The SBC sends an erroneous hold request to the transferor.

Incident Number:

In certain scenario, the Mediatrix SBC could send an erroneous hold request to the transferor when handling SIP REFER requests. The SBC would put some invalid SDP content. The Mediatrix SBC now properly generate a valid hold requests and the blind transfer is performed successfully.

DGW-13531 - In the SBC, the rtcp-mux attribute is missing in the SIP re-INVITE message sent from the called party

Incident Number: IN-14651

The RTP Anchoring action now includes the rtcp-mux attribute in the SIP re-INVITE message coming from the called party.

DGW-13476 - Incoming SIP calls with empty RURI or non-E164 URI that are routed to FXO ports are rejected.

Incident Number: IN-14838, IN-14845

SIP calls with empty RURI or non-E164 URI that are routed to FXO ports are now accepted and connected to the FXO line without dialing any digits.

DGW-13269 - The R2 caller may not hear the ringback tone when the SIP callee is not available.

Incident Number: IN-14766

If the SIP callee does not send a SIP 18X response within the R2.R2TimerVariants.AcceptCallTimeout delay, the ringback is now played toward the R2 caller.

DGW-13150 - SIP Redirect does not work as a hunt destination. 

Incident Number: IN-14736

Sip redirects can now be used as hunt destinations.

DGW-13075 - The parameters indexed by the EpIp are missing when querying parameters in CWMP via the command GetParameterValues on a parent parameter.

Incident Number:

The parameters indexed by the EpIp are now correctly returned when querying parameters in CWMP via the command GetParameterValues on a parent parameter.

DGW-13750 - Cannot limit TR-069 HTTPS provisioning to only TLS 1.2.

Incident Number:

When the parameter Cwmp.TransportHttpsTlsVersion is configured for TLSv1-2, instead of allowing only TLS 1.2, it also allows TLS 1.1.