DGW Release Notes v46.0.2025

IN-14580

The maximum number of SIP gateways that can be created has been increased to 10. Downgrading from a version supporting 10 gateways to an older version with a limit of 5 will erase gateways in excess of 5. After downgrade, the configuration will require verification.

The SipProxy service persistent connection will no longer try to return to a higher priority target if the persistent connection with the current target does not have an error.

The wan_ip_trunk_to_lan_pbx.rrs routing ruleset was fixed and the new   lan_pbx_to_wan_ip_trunk_dm.rrs was added to route calls from the lan_ip_pbx_ca to wan_ip_trunk_ca call agent in a demarcation setup.

The following parameters can no longer be set to SSLv3 (100):

• SipEp.TransportTlsVersion
• Cert.TransferHttpsTlsVersion
• Conf.ScriptsTransferTlsVersion
• Conf.ImageTransferTlsVersion
• File.TransferHttpsTlsVersion
• Cwmp.TransportHttpsTlsVersion
• Fpu.MfpTransferTlsVersion
• Nlm.PCaptureTransferTlsVersion
• Web.TlsVersion

The following three DTMF modulations are now supported for CallerID detection on FXO interfaces:

• ETSI
• TDK
• Telebras. After a successful detection of the CallerID, the number is transmitted to the Call Router through the E164 Call Property. The outgoing SIP call will also contain the E164 Call Property information within its content.

The second part which is optional, represents the IANA format and is used in some of the SBC Web pages. Example: EST5EDT4,M3.2.0/02:00:00,M11.1.0/02:00:00;America/Montreal

 IN-14514

The new SipEp.Rfc4579ConferenceErrorRecovery parameter allows the configuration of the error recovery behaviour according to RFC4579 on conference calls made using a conference server.

This parameter offers two schemes:

• With error recovery: the processing of a SIP REFER must be completed before issuing the next REFER.
• Without error recovery: the SIP REFERs are sent simultaneously.

“With error recovery”, is the default value and the behavior that existed before introducing this parameter.

The SipEp.AddRPortEnable parameter was added to enable or disable the presence of the rport in the Via header of the SIP packet. This parameter is also available in the DGW Web interface SIP/Transport page.

The outbound proxy feature is now available in UDP. The SipProxy service uses virtual persistent connections to create a path between the outbound proxy server and the local SIP proxy. The SipProxy service will now insert a Route header pointing to its configured outbound proxy as the first route if the feature is enabled.

The outbound proxy server is configurable through the SipProxy.OutboundProxyHost parameter available in the DGW Web page under SIP Proxy/Configuration.

The Transport column was also added in the SipProxy.PersistentConnectionStatus parameter to show the transport used for the persistent connection.

The Mac address is now added to the TAC diagnostic traces.

The new "any" option was added to the Link Name parameter under System/Packet Capture which allows to capture packets from every interface of the device.

The Pots.CallerIdCustomization parameter now supports the following values.

• TelebrasDtmf
• TdkTdmf
• Bell202Fsk

New DTMF strings supported:

• In TDK DTMF, we can now receive the 'D3#' special code
• In ETSI DTMF, we can now receive a DTMF string beginning with 'A'.
• In ETSI DTMF, we can now receive and send the special codes 'B00C' (CallerID not available) and B01C' (CallerID restricted).

IN-14412

The application can now correctly send the Friendly Name in the P-Asserted-Identity and P-Preferred-Identity headers.

The MOS estimation was calculated using the wrong probability of packet loss. MOS estimation is now calculated using the proper probability of packet loss.

IN-14460

Unconnected or unpowered FXO ports are now detected properly.The new Pots.FxoLinkStateVerificationPowerDenial parameter available via CLI or SNMP was added.

When the Pots.FxoLinkStateVerificationPowerDenial parameter is enabled, the link state verification mechanism can detect if the FXO link is powered or not. The link state is displayed in the FxoLinkState parameter in the DGW Web page under POTS/Status. This parameter has no effect if the FxoLinkStateVerification parameter is disabled.