CWMP service should return only accessible parameter names via GetParameterNames request.
DGW-13649
The XML DataModel of the CWMP parameters is not accurate.
IN-15059
DGW-14099
An inaccurate error detection in the clock synchronization sends unnecessary Hoc notification messages.
IN-14998
DGW-14227
Unable to detect the FSK Caller-ID received when the last end-bit is missing.
DGW-14230
OpenSSL need to be updated to fix various CVE vulnerabilities.
IN-15098
DGW-14263
Some SDP media attributes of unsupported codecs are not removed from the SDP answer.
DGW-14269
Performance issue when the SBC tries to match incoming SIP message to a Call Agent that has a CNAME FQDN as its peer address.
DGW-14305
The maximum number of mappings and routes allowed in CRout service is too low.
DGW-14330
The TR-104 DigitMap parameter is placed under an incorrect path in CWMP.
DGW-14359
Add the support of LocalGroup and RemoteGroup in RTCP XR published reports.
IN-15129
DGW-14396
The parameter SipEp.InteropLockDnsSrvRecordPerCallEnable has no effect on incoming voice calls.
DGW-14424
The SBC should resolve the FQDN of the Media Interface.
DGW-14425
Need "Username (no alias)" as a new cookie method in the SBC's "Enable REGISTER cache" ruleset action.
DGW-14426
The SipProxy service cannot forward an incoming SIP INVITE from the server if the SIP INVITE uses the SipProxy's public address.
DGW-14427
SipProxy's public address is not supported in the SIP REGISTER response.
New Features
DGW-14427 - SipProxy's public address is not supported in the SIP REGISTER response.
The SIP proxy will now resolve the request-URI contained in the contact override parameter and send the SIP REGISTER response to the endpoint if the host/port in the contact URI of the SIP REGISTER response matches the address of the "received" and the "rport" of the top most Via in the response received from the SIP REGISTER or monitoring SIP OPTION.
DGW-14426 - The SipProxy service cannot forward an incoming SIP INVITE from the server if the SIP INVITE uses the SipProxy's public address.
Public IP addresses discovery is added using the "received" and the "rport" of the top most Via in the response received from the SIP REGISTER or monitoring SIP OPTION. This enables the SIP proxy to determine if the IP address is one of its own and resolve the contact override parameter in the request-URI.
DGW-14425 - Need "Username (no alias)" as a new cookie method in the SBC's "Enable REGISTER cache" ruleset action.
The SBC's ruleset action "Enable REGISTER cache" has a new value "Username (no alias)" available for the "Cookie method" parameter. When this value is selected, the contact relayed by the SBC contains the original user part and no reg-alias parameter is added.
This new value is intended to be used with SIP servers that do not support the other cookie methods. This value does not support multiple registrations per user.
DGW-14424 - The SBC should resolve the FQDN of the Media Interface.
In order to prevent interoperability issues, the SBC Media Interface,Sbc.MediaInterface.PublicIpAddrFQDN will now be resolved at each usage.
DGW-14359 - Add the support of LocalGroup and RemoteGroup in RTCP XR published reports.
Added new scalars SipEp.LocalGroup and SipEp.RemoteGroup to configure LocalGroup and RemoteGroup in RTCP XR reports.
DGW-14305 - The maximum number of mappings and routes allowed in CRout service is too low.
The maximal size of the tables Route, MappingType,MappingExpressions,SipRedirect, SipHeadersTranslation, and CallPropertiesTranslation in the CRout service have been increased to 150 entries.
DGW-14230 - OpenSSL need to be updated to fix various CVE vulnerabilities.
OpenSSL is now updated to 1.1.1k version.
DGW-14227 - Unable to detect the FSK Caller-ID received when the last end-bit is missing.
Incident Number: IN-14998
Introduced a new parameterPots/FxoInteropGroup/FxoInteropIgnoreInvalidCallerIdChecksum to help detect the received FSK Caller-ID even when the signal is slightly corrupted. This parameter is disabled by default.
Issues Fixed
DGW-14396 - The parameter SipEp.InteropLockDnsSrvRecordPerCallEnable has no effect on incoming voice calls.
Incident Number: IN-15129
The parameter SipEp.InteropLockDnsSrvRecordPerCallEnable now also has an effect on incoming voice calls.
DGW-14330 - The TR-104 DigitMap parameter is placed under an incorrect path in CWMP.
The TR-104 DigitMap parameter is no longer supported through the TR-104 parameters. Now the digitmaps must be configured through the Device.Services.X_0090F8_EpServ.Call.CallDtmfMap vendor-specific parameters.
DGW-14269 - Performance issue when the SBC tries to match incoming SIP message to a Call Agent that has a CNAME FQDN as its peer address.
Improved the SBCs performance when matching incoming SIP to a Call Agent that has a CNAME FQDN as its peer address
DGW-14263 - Some SDP media attributes of unsupported codecs are not removed from the SDP answer.
Incident Number: IN-15098
The SDP media attributes of unsupported codecs are now correctlyremoved when the negotiation rejects a codec listed in the received SDP offer.
The removal of the SDP media attribute 'rtcp-fb' is now handled correctly.
DGW-14099 - An inaccurate error detection in the clock synchronization sends unnecessary Hoc notification messages.
Incident Number: IN-15059
The notification messages sent by the Hoc service are modified:
The notification #72 now has the time value printed in its message
The notification #77 is now sent if the time difference is higher than 7 seconds, instead of every second.
DGW-13649 - The XML DataModel of the CWMP parameters is not accurate.
The content of the XML file is reviewed and updated:
The CWMP standard parameters (TR-069/TR-104/TR-106) are now described.
The vendor-specific parameters are now under the /deviceType/dataModel/parameters/parameter[parameterName = "Device"]/parameters/parameter[parameterName = "Services"] XML path, which matches the Device.Services. CWMP path.
DGW-9126 - CWMP service should return only accessible parameter names via GetParameterNames request.
CWMP service GetParameterNames response will reflect the unit current running configuration. If a service is not running, it will not be included in the response. If the TR069 server implicitly accesses a parameter of a service that is not running, an error will still be returned.
Known Issues
There are no known issues.
Copyright Notice
Copyright 2021 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.
