DGW Release Notes v44.1.1605

The new CONP feature enables a SIP user to set a connected or called name in the p-asserted-identity friendly name part in order to populate the ISDN CONP service with the specified called or connected name value.

In the MX profile, the default SipProxy settings have been changed and the script Survivability_Trunks.cfg has been added in the C7 and G7 platforms for SipProxy survivability. Also, the "Short Dialing" transformation rule linked to the default SipProxy setting changes have been added on every platform.

The configuration scripts Web page was divided into two subsections. One for executing scripts and one for exporting them. On the executing subsection, a new textbox was added allowing users to input configuration lines and execute them without having to upload a file containing them. This textbox has a character limitation based on the browser used.

The notifications from Conf service are now properly identify which script (generic or specific) is being processed. The Conf.ScriptsAllowRepeatedExecution parameter now behaves correctly, i.e. when set to "disable", scripts are not re-executed when they are unchanged.

Multiple-file upgrade functionality is no longer accessible nor supported as it has been removed for DGW. For DGW upgrade instructions, please refer to the https://documentation.media5corp.com/display/DGWLATEST/Firmware+Upgrade document published on the Media5 documentation portal.

The Fpu Multiple File Upgrade logic and parameters have been removed, so the functionality can no longer be used nor does it appear in the DGW Web interface.

For more details refer to the Deprecation of the ZIP firmware file format Product change Notification published on the documentation portal. https://documentation.media5corp.com/display/MP/Product+Change+Notification?preview=/75010717/75010757/PCN181009%20-%20ZIP%20firmware%20file%20format%20Deprecation.pdf

IN-12607

The IPV4 header TTL was hardcoded to 64. The new Bni.IpGroup.IpTtlValue parameter was created to be able to the change the IPV4 header TTL in the range of 64..255.

This new parameter is only available using the CLI, a MIB browser, or in a configuration script.

The mediasec security headers (Require, Proxy-Require, Security-Client, Security-Verify) are now supported in the SIP OPTIONS (for keepalive) and SIP SUBSCRIBE (for mwi) when the mediasec security headers are enabled (through the SipEp.MediaSecurityAgreementEnable parameter).

Added support for the new 2-FXO extension card.

Macros in the Fpu.MfpUrl parameter are now supported to be able to provide the exact URL of the firmware file to be used to update the installed firmware (under Management/Firmware/Firmware Update Configuration).

Supported macros are:

• %mac% - the MAC address of the unit.
• %product% - the product name of the unit.
• %productseries% - the product series name of the unit.
• %serial% - the serial number of the unit.

The configuration scripts Web page was divided into two subsections. One for executing scripts and one for exporting them. On the executing subsection, a new textbox was added allowing users to input configuration lines and execute them without having to upload a file containing them. This textbox has a character limitation based on the browser used.

Multiple-file upgrade functionality is no longer accessible nor supported as it has been removed for DGW. For DGW upgrade instructions, please refer to the https://documentation.media5corp.com/display/DGWLATEST/Firmware+Upgrade document published on the Media5 documentation portal.

The Fpu Multiple File Upgrade logic and parameters have been removed, so the functionality can no longer be used nor does it appear in the DGW Web interface.

For more details refer to the Deprecation of the ZIP firmware file format Product change Notification published on the documentation portal. https://documentation.media5corp.com/display/MP/Product+Change+Notification?preview=/75010717/75010757/PCN181009%20-%20ZIP%20firmware%20file%20format%20Deprecation.pdf

The mediasec security headers (Require, Proxy-Require, Security-Client, Security-Verify) are now supported in the SIP OPTIONS (for keepalive) and SIP SUBSCRIBE (for mwi) when the mediasec security headers are enabled (through the SipEp.MediaSecurityAgreementEnable parameter).

The maximum range for all Interface names is set to 50 characters.

If the SipEp.InteropTlsCertificateValidation parameter is set to DnsSrvResponse and a gateway is configured as an Endpoint Gateway, certificate validation for SIP now works as expected.

The user account is now locked when failed authentication attempts via SNMPv3 surpasses the value of the loginLockedMaxRetry parameter.

IN-13964  

The 802.1Q tagging feature now applies the user priority .

When the the user performs a semi-attended call transfer with the SipEp.BlindTransferMethod parameter set to "SemiAttendedConfirmed":

• The call to the target is now correctly terminated if the transferee terminates the call with the transferor before the target answers the call from the transferor.
• The transfer is now correctly cancelled if the target rejects the call and the transferor can resume the call with the transferee.

IN-13960

The CWMP inform of the file transfer result now contains the appropriate "M Download"/"M Upload" event code.

After a rollback of a configuration with a virtual machine that has a VNC ID of -1, the Virtual Machine Configuration table in DGW is no longer available. To temporarily solve the problem, the customer has to manually change the VNC ID in the configuration file of the VM.

The Registration Cache filter on the SBC/Registration DGW Web page was cleared when clicking the "Apply" button, resulting in a filter not working. The Registration Cache filter is now applied properly.

The device now correctly handles the reception of invalid information in the first PPPoE connection after a start-up.

The Bni service defines the interface name max length (50 characters). The max length has been standardised to 50 characters for all services related to Bni.

When a user logs to the Mediatrix via the DGW Web page and chooses to have the Web browser to save and remember their password, this may cause Password or Privacy Key fields to be mistakenly filled by the Web browser, using the login credentials.

This may cause the upload of configuration scripts through the Web browser to fail because DGW tries to decrypt the file with the Privacy Key automatically filled with the login password.

This may also cause the download of configuration scripts from the Web browser to be automatically encrypted with the login password, unknowingly to the user.