Changelog

Version 6.4.13

Latest build: 0.0.10RC

=== 2025.09.23 - Build 0.0.10RC

Issue ID Description

36292

OneIoT ACS > Security vulnerabilities > Unauthenticated XML External Entity (XXE) takeover account and read sensitive server-side files

=== 2025.09.22 - Build 0.0.9

Issue ID Description

36025

API > FTGetDeviceParameters / FTSetDeviceParameters > API must provide responce directly from ACS, not DB

=== 2025.09.15 - Build 0.0.8

Issue ID Description

36290

OneIoT ACS > USP > Try to register device > Device not registered

=== 2025.09.15 - Build 0.0.7

Issue ID Description

36260

OneIoT ACS > USP > Monitoring > New / Existing monitor > Periodic! > Monitor-related tasks are not generated

36276

OneIoT ACS > TR-069 > Events > Parameter monitoring > "GREATER" condition > Event not triggered

=== 2025.09.11 - Build 0.0.6

Issue ID Description

36258

OneIoT ACS > USP > Group Update > Any task > Condition not met > Task sent to device

36253

OneIoT ACS > TR-069 > Monitoring > Monitor for existing device > 2 PERIODIC > Monitor-related tasks are not generated

36260

OneIoT ACS > USP > Monitoring > New / Existing monitor > Periodic! > Monitor-related tasks are not generated

=== 2025.09.10 - Build 0.0.5

Issue ID Description

36246

OneIoT ACS > 1M devices > Register device > "mac mapping" errors in log file

Requires DB change

=== 2025.09.04 - Build 0.0.4

Issue ID Description

35700

CPE Admin > Settings > Alerts and Events > Events > Add option to create hardcoded event settings per domainPE

35780

OneIoT ACS > Settings > ACS Settings > "skipUGTaskProcessingIfUGTaskSentExists" description > Add "Device Profile" and "Events" tabs to description

35766

Provision Portal > Provisioning for device > Set Parameter > Status code mapping

35826

API > FTACSWS > USP > "FTGetDeviceParameters" with "source=0" > Incorrect response

36113

OneIoT ACS > Profile with "0 BOOTSTRAP" event > 2 "Install" tasks > Incorrect tasks sequence

36162

OneIoT ACS > "0 BOOTSTRAP" > Profile > Root GPA task rejected > All following profile tasks rejected

Doc updated: https://friendlytech-my.sharepoint.com/:w:/g/personal/vadim_kasperovich_friendly-tech_com/EXqfvVFGLhBGpdFTo_EZDX4BA9M0HsofsP2Yf94AqKyJAg?e=3fyegU

Requires DB change

Requires acs_configuration.xml change

Requires logback.xml change

=== 2025.08.29 - Build 0.0.3

Issue ID Description

35857

OneIoT ACS > TR-069 > Update Group Custom RPC > Any method > Task rejected on long response

35663

CPE Admin > TR-069 / USP > Device Profile > Add task > Upload > Change upload task type > Device Update > Device Activity > "Upload" task is displayed with an empty "Parameter name" field

35975

OneIoT ACS > Start ACS > Error occured

34522

OneIoT ACS > REST > subscribeCpeParameterEvent > Don’t send null values

36060

OneIoT ACS > USP > Monitoring > Bulk data > Deactive monitor > Activate monitor > Task failed

34526

CPE Admin > TR-069 / USP > Device profile with event > "SPV" > Device update > Device activity > "GPV" > Irrelevant "Creator" name

34379

CPE Admin > Device Profile > Upload / Download task > Edit > Remove task > Device Activity > URL value is cleared

35761

OneIoT ACS > USP > MQTT / WebSocket > Firmware > Delete "TransferComplete!" event subscription > Response is not sent

32333

CPE Admin > USP > Device Update > File Download > Firmware Image > Object instance selection is absent

=== 2025.08.18 - Build 0.0.2

Issue ID Description

36111

OneIoT ACS > CpeParameterNameCache merged

35759

OneIoT ACS > USP > MTP = "MQTT" > Incorrect "Responce Information" value

35459

OneIoT ACS > Monitoring > Monitoging data streaming via Kafka

35666

OneIoT ACS > USP > Events > TransferComplete! > Download task > Firmware image > TransferComplete! event > Task related to event in pending state

35668

OneIoT ACS > USP > Events > OperationComplete > Device brings "OperationComplete" event > Event not generated

35664

OneIoT ACS > USP > Device Profile > Events > Boot!(Reboot) > Reboot device > Event not generated

36102

OneIoT ACS > "MonitoringSelectNodeTr" = "true" > Monitoring object > Device online > Connection request > Tasks are generated for monitored object

35906

OneIoT ACS > "Web service" URL > Trigger any hardcoded event > Incorrect "SOAPAction" value is sent by OneIoT ACS

=== 2025.08.08 - Build 0.0.1

Issue ID Description

35631

OneIoT ACS > TR-069 > Device Update > Software Manager > Install > DUStateChangeComplete > "Fault" element is absent from trace

35870

OneIoT ACS > Improved parameter saving mechanism

35708

OneIoT ACS > TR-069 / USP > Bulk data > Stop monitor > Delete monitor > DeleteObject tasks are not generated

34480

OneIoT ACS > TR-069 / USP > Monitoring > Bulk data > Deactive monitor > Activate monitor > No SPV "BulkData.Profile.{i}.Enable=1" task

35681

OneIoT ACS > Register device with XMPP > Incorrect "xmppServerHostAcs" parameter is sent to device

34527

CPE Admin > TR-069 / USP / LWM2M > Active device profile > Edit > Parameters > Add "SPV" > Device

35637

OneIoT ACS > USP > Register 2 devices with the same serial > Devices are duplicated

35782

OneIoT ACS > "skipUGTaskProcessingIfUGTaskSentExists=true" > Events > Event with 2 tasks > The second task is sent to the device before the first one is completed

=== 2025.04.17 - Build Master

is 6.4.13 now

Version 6.4.12

Latest build: 0.0.6

=== 2025.07.24 - Build 0.0.6

Issue ID Description

36037

OneIoT ACS > Monitor with FCC diagnostics > Diagnostics are sent in a single session

36121

OneIoT ACS > TR-069 > Windstream > Bootstrap scenarios fixes

=== 2025.06.12 - Build 0.0.5

Issue ID Description

35848

OneIoT ACS > TR-069 > Custom RPC > Any method > Task rejected

=== 2025.06.06 - Build 0.0.4

Issue ID Description

35824

OneIoT ACS > MySQL > TR-069 / USP > SPV / GPV on 2 identical parameters of different instances of multiple instances object > Incorrect task is sent to device

=== 2025.06.04 - Build 0.0.3

Issue ID Description

35269

OneIoT ACS > TR-069 > Active monitor > New monitor > Excessive GPV tasks

35659

OneIoT ACS > USP > Device Profile > Edit profile > Request full data tree from existing devices + parameter monitoring task > Save > Edit > Apply provision data to existing > Error is present in log

35456

OneIot ACS > Device comes with "Retry count" in inform > Save "Retry count" value in "CPE" table to be displayed in GUI

35739

OneIoT ACS > Group Update > FCC diagnostic > Incorrect timestamp values are stored in the "ug_fcc_speed_result" DB table for the "BOM" / "EOM" fields

35701

CPE Admin > Reports > FCC Report > Add BOM and EOM column

DB update required

=== 2025.05.30 - Build 0.0.2

Issue ID Description

33800

OneIoT ACS > USP > Monitoring > Edit > Add parameter > QoE task is duplicated for the other added parameter

35657

OneIoT ACS > TR-069 > Active event > Stop > Start > Inform > Notification "Off" > Inform > "Set parameter attributes" task with "Notification "Active" is not generated

35726

OneIoT ACS > Device offline > "overwriteProvisionParameters" = "0" > 2 tasks FTSetDeviceParameters with "reprovision"= "0" > Second GPV tasks is absent

35287

OneIoT ACS > Device offline > "overwriteProvisionParameters" = "1" > 2 tasks FTSetDeviceParameters with "reprovision"= "1" > Irrelevant SPV and GPV tasks for the first request are sent to the device

34368

OneIoT ACS > Multi-ISP > TR-069 > Device in specific domain > Register with credential related to superdomain > Device is not reassigned to superdomain

35284

OneIoT ACS > Device offline > 2 tasks FTSetDeviceParameters with "reprovision"= "0" > Incorrect order of the tasks

35318

OneIoT ACS > "acs_configuration.xml" > "httpSessionLimit" tag > Incorrectly written protocol name

=== 2025.05.21 - Build 0.0.1

Issue ID Description

32854

OneIoT ACS > TR-069 > Any parameter with "Access list"="All" > SPA with "Access list"="ACS only" > Completed > Access list value not changed in DB

34374

OneIoT ACS > TR-069 > Device profile with monitoring > Edit > Delete monitoring parameter > Register new device > Irrelevant task

33686

CPE Admin > Device Update > Incorrect "last updated" displayed

35353

OneIoT ACS > USP > Multiple instances object > SPV task using wildcard-based request > Particular object instance is sent

33284

OneIoT ACS > TR-069 > Wrong credentials > No "RetryCount"-related entry in "server.log"

15138

OneIoT ACS > acs_configuration.xml > xmppUseDotForConnectionObjSet > Typo in description

35576

OneIoT ACS > "cpe_software_parameter_exec_unit" DB table > The "ExecutionFaultCode" value stored incorrectly

=== 2025.04.17 - Build Master

is 6.4.12 now

Version 6.4.11

Latest build: 0.0.11

=== 2025.05.28 - Build 0.0.11

Issue ID Description

35769

OneIoT ACS > Device registration under load > Hazelcast lock

=== 2025.05.22 - Build 0.0.10

Issue ID Description

35742

OneIoT ACS > Big amount of devices > Group Update > File download > Export > Import > Activate > Update group is stuck

=== 2025.05.02 - Build 0.0.9

Issue ID Description

35660

OneIoT ACS > Monitoring > Huge KPI data > Low performance

=== 2025.04.30 - Build 0.0.8

Issue ID Description

35650

CPE Admin > MySQL > USP > Group Update / Events / Device profile > Upload > Vendor Configuration File > Task with incorrect URL generated

=== 2025.04.25 - Build 0.0.7

Issue ID Description

35633

OneIoT ACS > TR-069 > Device Update > Software Manager > Install > DUStateChangeComplete > "9012" Fault code > Task transefered to "Completed" state

35631

OneIoT ACS > TR-069 > Device Update > Software Manager > Install > DUStateChangeComplete > "Fault" element is absent from trace

=== 2025.04.23 - Build 0.0.6

Issue ID Description

35624

OneIoT ACS > USP > Group Update > Action > Task in "Failed" state

=== 2025.04.23 - Build 0.0.5

Issue ID Description

35627

OneIoT ACS > TR-069 > Device Update > Software Manager > Install > Task is stuck in "Sent" state

35614

OneIoT ACS > RN > Duplicated rows are present

=== 2025.04.15 - Build 0.0.4

Issue ID Description

35564

OneIoT ACS > Hardcoded events > 2 Periodic > Add new event "1118 - device comes with periodic"

35610

OneIoT ACS > Fixed issue with device parameter update delay

=== 2025.04.15 - Build 0.0.3

Issue ID Description

35572

OneIoT ACS > Group Update > Group without "Online devices" > Update group performance optimization

35565

OneIoT ACS > SPV task to PreSharedKey > Incorrect parameter type "hexBinary" used

35390

OneIoT ACS > Managed license > Devices not automatically deleted

35566

OneIoT ACS > Auto-Deletion mechanism > Introduces flexibility to schedule the deletion job via config file

35567

OneIoT ACS > OneIoT ACS > OneIoT ACS > Load increased due to thread pool

35569

OneIoT ACS > Hazelcast and ACS Under Load > Connection Failures and Delays

34528

OneIoT ACS > JIO > Production > HZ Separation > Jboss nodes failure

35323

OneIoT ACS > More than two diagnostics > "8 DIAGNOSTICS COMPLETE" > Get diagnostics result tasks duplicated

35090

CPE Admin > Clean DB > TR-069 > Device Profile > New / Edit > Events > 11 DU STATE CHANGE COMPLETE" > Save and Activate > Open created profile > Irrelevant "11 DU STATE CHANGE COMPLETE0" is present

34374

OneIoT ACS > TR-069 > Device profile with monitoring > Edit > Delete monitoring parameter > Register new device > Irrelevant task

35457

OneIoT ACS > Reports > Software modules > Report upgrade

35433

CPE Admin > Reports > Add new report "Deleted Devices"

33223

CPE Admin > LWM2M / USP > Device registered with installed deployment unit > Reports > Software Module > No data found

17308

CPE Admin > Settings > External system > "Losant" sub-tab > "Enable Integration" hint icon > Unclear hint text

Note: Requires ACS restart to take effect, since Quartz job scheduling occurs during application startup.

Added acs_configuration.xml parameter:

<!--Legal value: cron expression | Default value: 0 0 2 * * ? (at 02:00) | Cron expression which defines the time of the automatically delete start. Syntax help: https://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html-->

<autoDeleteCron>0 0 2 * * ?</autoDeleteCron>

Added acs_configuration.xml parameter:

<!--Legal values: 0, 1 | Default value: 1 (enabled) | If set to 1 ACS will synchronize all modifications operations (for the tables: cpe_parameter, cpe_pending_task, cpe, cpe_next_session_time) through the Hazelcast between all ACS nodes-->

<enableRowLockProtection>1</enableRowLockProtection>

The following configuration should be adjusted on all big customers with high load:

Configuration on hazelcast server in hazelcast.xml:

<property name="hazelcast.backpressure.max.concurrent.invocations.per.partition">300</property>

<property name="hazelcast.event.thread.count">32</property>

<property name="hazelcast.io.thread.count">32</property>

<property name="hazelcast.io.input.thread.count">16</property>

<property name="hazelcast.io.output.thread.count">16</property>

<property name="hazelcast.io.write.through">false</property>

<property name="hazelcast.io.balancer.interval.seconds">5</property>

<property name="hazelcast.operation.generic.thread.count">16</property>

<property name="hazelcast.operation.response.thread.count">32</property>

<property name="hazelcast.operation.thread.count">32</property>

Configuration in hazelcast-client.xml:

<connection-strategy async-start="true" reconnect-mode="ASYNC">

<connection-retry>

<initial-backoff-millis>1000</initial-backoff-millis>

<max-backoff-millis>10000</max-backoff-millis>

<multiplier>2</multiplier>

<jitter>0.5</jitter>

<cluster-connect-timeout-millis>-1</cluster-connect-timeout-millis>

</connection-retry>

</connection-strategy>

DB update required

=== 2025.04.01 - Build 0.0.2

Issue ID Description

33519

OneIoT ACS > USP > MQTT > MTP = "STOMP" > Heart-beat enabled > ACS doesn’t send heart-beats

32353

CPE Admin > USP > Device Update > Advanced View > "Device.LocalAgent.AddCertificate()" command > Execute > Method not found

=== 2025.03.18 - Build 0.0.1

Issue ID Description

32979

OneIoT ACS > USP > MQTT / STOMP > "Validate to_id"="false" > Register device with incorrect ACS EndpointID > Error message is sent

34349

OneIoT ACS > USP > GPV task on at least 2 objects > Non-composite tasks are sent to device instead of 1 composite

32477

CPE Admin > USP > Device Update > Device history > "OperationComplete" event is not displayed

33710

OneIoT ACS > USP > Monitoring > Bulk Data > Impossible to set arbitrary name of the parameter in the report body

Master is 6.4.11 now

Version 6.4.10

Latest build: 0.0.19

=== 2025.10.06 - Build 0.0.19

Issue ID Description

36276

OneIoT ACS > TR-069 > Events > Parameter monitoring > "GREATER" condition > Event not triggered

=== 2025.09.25 - Build 0.0.18

Issue ID Description

36292

OneIoT ACS > Security vulnerabilities > Unauthenticated XML External Entity (XXE) takeover account and read sensitive server-side files

=== 2025.09.19 - Build 0.0.17

Issue ID Description

36311

OneIoT ACS > Register device > "setCPEParams" with reprovision 1 > Transaction ID is "null"

36310

OneIoT ACS > Register device > "addCPEObject" with reprovision 1 > Add object task is duplicated

=== 2025.09.19 - Build 0.0.16

Issue ID Description

36320

OneIoT ACS > "Web service" URL > Trigger any hardcoded event > Incorrect "SOAPAction" value is sent by OneIoT ACS

=== 2025.08.12 - Build 0.0.15

Issue ID Description

36121

OneIoT ACS > TR-069 > Windstream > Bootstrap scenarios fixes

=== 2025.07.22 - Build 0.0.14.3

Issue ID Description

35870

OneIoT ACS > Improved parameter saving mechanism

=== 2025.06.17 - Build 0.0.14.2

Issue ID Description

36125

OneIoT ACS > TR-069 > Windstream > CustomRPC fix

=== 2025.05.30 - Build 0.0.14.1

Issue ID Description

35760

OneIoT ACS > CPEs are either displayed as offline or stuck in a "retrieving status" state in the UI

=== 2025.04.28 - Build 0.0.14

Issue ID Description

35644

OneIoT ACS > Update with FCC diagnostic > FCC Report > "Upload diagnostic failed" is displayed on Comments when a download test is executed

=== 2025.04.17 - Build 0.0.13

Issue ID Description

35610

OneIoT ACS > Fixed issue with device parameter update delay

=== 2025.04.16 - Build 0.0.12

Issue ID Description

35596

OneIoT ACS > Group Update > Period not empty > Activate > Wait for next period interval > Update transferred to "Completed" state

=== 2025.04.09 - Build 0.0.11

Issue ID Description

35572

OneIoT ACS > Group Update > Group without "Online devices" > Update group performance optimization

35565

OneIoT ACS > SPV task to PreSharedKey > Incorrect parameter type "hexBinary" used

35390

OneIoT ACS > Managed license > Devices not automatically deleted

35566

OneIoT ACS > Auto-Deletion mechanism > Introduces flexibility to schedule the deletion job via config file

35567

OneIoT ACS > OneIoT ACS > OneIoT ACS > Load increased due to thread pool

35569

OneIoT ACS > Hazelcast and ACS Under Load > Connection Failures and Delays

34528

OneIoT ACS > JIO > Production > HZ Separation > Jboss nodes failure

Note: Requires ACS restart to take effect, since Quartz job scheduling occurs during application startup.

Added acs_configuration.xml parameter:

<!--Legal value: cron expression | Default value: 0 0 2 * * ? (at 02:00) | Cron expression which defines the time of the automatically delete start. Syntax help: https://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html-->

<autoDeleteCron>0 0 2 * * ?</autoDeleteCron>

Added acs_configuration.xml parameter:

<!--Legal values: 0, 1 | Default value: 1 (enabled) | If set to 1 ACS will synchronize all modifications operations (for the tables: cpe_parameter, cpe_pending_task, cpe, cpe_next_session_time) through the Hazelcast between all ACS nodes-->

<enableRowLockProtection>1</enableRowLockProtection>

The following configuration should be adjusted on all big customers with high load:

Configuration on hazelcast server in hazelcast.xml:

<property name="hazelcast.backpressure.max.concurrent.invocations.per.partition">300</property>

<property name="hazelcast.event.thread.count">32</property>

<property name="hazelcast.io.thread.count">32</property>

<property name="hazelcast.io.input.thread.count">16</property>

<property name="hazelcast.io.output.thread.count">16</property>

<property name="hazelcast.io.write.through">false</property>

<property name="hazelcast.io.balancer.interval.seconds">5</property>

<property name="hazelcast.operation.generic.thread.count">16</property>

<property name="hazelcast.operation.response.thread.count">32</property>

<property name="hazelcast.operation.thread.count">32</property>

<property name="hazelcast.backpressure.max.concurrent.invocations.per.partition">300</property>

Configuration in hazelcast-client.xml:

<connection-strategy async-start="true" reconnect-mode="ASYNC">

<connection-retry>

<initial-backoff-millis>1000</initial-backoff-millis>

<max-backoff-millis>10000</max-backoff-millis>

<multiplier>2</multiplier>

<jitter>0.5</jitter>

<cluster-connect-timeout-millis>-1</cluster-connect-timeout-millis>

</connection-retry>

</connection-strategy>

=== 2025.04.06 - Build 0.0.10

Issue ID Description

35435

OneIoT ACS > Update with FCC diagnostic > FCC Report > "Upload diagnostic failed" is displayed on Comments when a download test is executed

35513

CPE Admin > USP firmware update issue

=== 2025.03.02 - Build 0.0.9

Issue ID Description

34439

OneIoT ACS > config_custom_data > Set Parameter Attributes > TR181 device > Set Attribute failed in 2nd 0bootstrap event

=== 2025.02.28 - Build 0.0.8

Issue ID Description

35345

OneIoT ACS > Device with line breaks in parameter name > Device Update > Part of device tree is duplicated

35349

OneIoT ACS > CPE Parameter Name Cache: Fixed issue with cache entries > Not entire table loaded into the cache

35355

OneIoT ACS > Device Profile with Download Task > Event with Download Task > Both download tasks executed in the same session

=== 2025.02.21 - Build 0.0.7

Issue ID Description

35278

OneIoT ACS > Active monitor > Delete device > Re-register device > Monitoring related tasks completed > Device-related data is absent from DB

35315

OneIoT ACS > TR069 Device → HTTP push → 503 Response → Retries should be configured

new acs_configuration.xml parameter added:

<!-- Legal values: 0 - 20 | Default value: 10 | TR069 device http push request retry attempts in case of 500 or 503 response from device -->

<pushRetriesOn500>10</pushRetriesOn500>

=== 2025.02.19 - Build 0.0.6

Issue ID Description

35300

OneIoT ACS > Group Update > New / Edit > "Send to" = "group" > Save and activate > Update is stuck in "Running" state and tasks are not created

35297

CPE Admin / CSR > TR-181 > Specific device > Device Update > Delete device > An error occurred

35278

OneIoT ACS > Active monitor > Delete device > Re-register device > Monitoring related tasks completed > Device-related data is absent from DB

=== 2025.02.17 - Build 0.0.5

Issue ID Description

35289

OneIoT ACS > FCC diagnostics > wan_usage.repeat > Initial attempt shouldn’t be counted in total retries attempts

35290

OneIOT ACS > Startup > Parameter names cache load > Load time is growing each 100K

35254

OneIoT ACS > Group Update > Update with FCC diagnostic > Completed > Report > FCC report > "Test not performed: Device is Offline" is displayed

=== 2025.02.10 - Build 0.0.4

Issue ID Description

35247

OneIoT ACS > Device > Parameters > Device tree not updated on high load

34065

OneIoT ACS > USP > MTP = "STOMP" > Malformed USP record > OneIoT ACS sends a STOMP "ERROR" frame

34434

OneIoT ACS version > USP > X.509 certificate > STOMP > Device certificate signed by server certificate > Device is not connected

=== 2025.02.07 - Build 0.0.3

Issue ID Description

17307

CPE Admin > Settings > External system > "Losant" sub-tab > Secong word of check box name is capitalized

34479

OneIoT ACS > USP > Monitoring > Bulk data > New > No "Add object" task related to monitored parameter

35138

OneIoT ACS > Hardcoded Event > Add additional info into SOAP message

34831

OneIoT ACS > Hardcoded Event > 1116 - cpe comes with bootstrap > Add option to send MAC

SDD: https://friendlytech.sharepoint.com/:w:/r/Shared%20Documents/RD/prerelease/ACS/ACS%20v.6.4.10/Docs/SDD%20events.docx?d=w26a8e81dff904b599964676340998b3f&csf=1&web=1&e=Uzwtxo

Requires:

DB change required

acs_configuration.xml changed

hardcoded_event_soap_template.xml added

=== 2025.01.29 - Build 0.0.2

Issue ID Description

35134

OneIoT ACS > TR-069 > Register new device > Device Update > Open > Data absent from DB

Requires Hikari DB pool

=== 2024.12.06 - Build 0.0.1

Issue ID Description

32444

OneIoT ACS > USP > Register device with "Boot!" event > Advanced View > Mentioned event is absent from device tree

Version 6.4.9

Latest build: 0.0.18

=== 2025.03.06 - Build 0.0.18

Issue ID Description

35349

OneIoT ACS > CPE Parameter Name Cache: Fixed issue with cache entries > Not entire table loaded into the cache

=== 2025.02.25 - Build 0.0.17

Issue ID Description

35278

OneIoT ACS > Active monitor > Delete device > Re-register device > Monitoring related tasks completed > Device-related data is absent from DB

35345

OneIoT ACS > Device with line breaks in parameter name > Device Update > Part of device tree is duplicated

=== 2025.02.19 - Build 0.0.16

Issue ID Description

35297

CPE Admin / CSR > TR-181 > Specific device > Device Update > Delete device > An error occurred

=== 2025.02.13 - Build 0.0.15

Issue ID Description

35254

OneIoT ACS > Group Update > Update with FCC diagnostic > Completed > Report > FCC report > "Test not performed: Device is Offline" is displayed

=== 2025.02.12 - Build 0.0.14

Issue ID Description

35138

OneIoT ACS > Hardcoded Event > Add additional info into SOAP message

34831

OneIoT ACS > Hardcoded Event > 1116 - cpe comes with bootstrap > Add option to send MAC

35169

OneIoT ACS > Device with "0 BOOTSTRAP" > retrieveMacAddressesOnBootstrap=1 > "1116 - cpe comes with bootstrap" > Clarification is required regarding retrieving MAC address

35163

OneIoT ACS > Cluster > "hardcoded_event_soap_template.xml" > Change value > No sync between nodes

35290

OneIOT ACS > Startup > Parameter names cache load > Load time is growing each 100K

DB update required

=== 2025.02.09 - Build 0.0.13

Issue ID Description

35247

OneIoT ACS > Device > Parameters > Device tree not updated on high load

=== 2025.01.30 - Build 0.0.12

Issue ID Description

34533

OneIoT ACS > Path traversal vulnerability in %ACS_HOSTNAME%

=== 2025.01.29 - Build 0.0.11

Issue ID Description

35134

OneIoT ACS > TR-069 > Register new device > Device Update > Open > Data absent from DB

35138

OneIoT ACS > Hardcoded Event > Add additional info into SOAP message

34831

OneIoT ACS > Hardcoded Event > 1116 - cpe comes with bootstrap > Add option to send MAC

Added configuration parameter:

<!--Legal values: 0, 1 | Default value: 0 (disabled) | If 1 and enableHardcodedEvents is 1 and device comes with '0 BOOTSTRAP' event - GPV will be created on "InternetGatewayDevice.WANDevice." or "Device.Ethernet.Link."-->

<retrieveMacAddressesOnBootstrap>0</retrieveMacAddressesOnBootstrap>

Added files in jboss configuration folder:

hardcoded_event_soap_template.xml - required

Requires Hikari DB pool

=== 2025.01.24 - Build 0.0.10

Issue ID Description

34439

ACS > config_custom_data > Set Parameter Attributes > TR181 device > Set Attribute failed in 2nd 0bootstrap event

33669

OneIoT ACS > Infinite locking removed

34545

OneIoT ACS > Implementation of optimization

35080

OneIoT ACS > Group Update > "ORA-01438" fix

34542

OneIoT ACS > Fixed locks on cpe_parameter merge

34543

OneIoT ACS > Added hikari pool size into acs stats

34544

OneIoT ACS > Moved FTDS and QUARTZDS from wildfly to hikari pool

Merged with 6.4.3 RIL and 6.4.7 performance versions

hazelcast-client.xml change:

Add before <near-cache> tag:

<near-cache name="CpeParameter*">

<in-memory-format>OBJECT</in-memory-format>

<invalidate-on-change>true</invalidate-on-change>

<eviction eviction-policy="LFU" max-size-policy="ENTRY_COUNT" size="10000"/>

</near-cache>

=== 2025.01.14 - Build 0.0.9

Issue ID Description

34479

OneIoT ACS > USP > Monitoring > Bulk data > New > No "Add object" task related to monitored parameter

=== 2025.01.08 - Build 0.0.8

Issue ID Description

34490

OneIoT ACS > Hardcoded Events > ACS keeps sending event

=== 2024.12.11 - Build 0.0.7

Issue ID Description

34353

CPE Admin > Oracle > TR-069 > Events > New > "Events" subtab > "11 DU STATE CHANGE COMPLETE" event > Save > Open > An error occurred

=== 2024.12.06 - Build 0.0.6

Issue ID Description

34003

OneIoT ACS > LWM2M > TLV > Put on /3/0/13 > "PUT" request with incorrect value

13172

CPE Admin > Oracle > Device Profile > Export / Import > Profile is associated with wrong "product_class_group" id

33502

OneIoT ACS > Update group > Task > Diagnostics > FCC > Add batching settings

33501

OneIoT ACS > Update group > Task > Diagnostics > FCC > Improvement of duration and repetition settings

Requires DB change

Requires existent Update Groups with FCC task stop

=== 2024.12.03 - Build 0.0.5

Issue ID Description

33867

CPE Admin > USP > Events > New / Edit > Boot! event > Extend to show cause value from Boot! event

33346

OneIoT ACS > USP > Device Update > Software managment > Uninstall > "Uninstall()" command is generated for one deployment unit only

33458

OneIoT ACS > USP > Device Update > File Download > Firmware Image > Send > Subscription instance for the "OperationComplete" notification is not added

31082

OneIoT ACS > USP > Add object task on at least 2 objects > Non-composite tasks are sent to device instead of 1 composite

34066

OneIoT ACS > USP > WebSocket > Malformed USP record > OneIoT ACS sends incorrect status code

34152

OneIoT ACS > USP > Work with registration process optimisation

34031

REST API > LWM2M > Issue with sending large value data in device/history method

34061

OneIoT ACS > ACS WS > LWM2M with cumulative data push > subscribeCpeParameterEvent > Send data in one API call

33212

OneIoT ACS > "Multi-instance resource/s observe mode" = "PER_RESOURCE" > "subscribeCpeParameterEvent" > Device History > Incorrect values displayed for "4 VALUE CHANGE"

33112

OneIoT ACS > LWM2M > "Resource tree. Build mode"=SKELETON > "Resource tree. Disabled objects" is empty > Register device with declared "/0" object > Mentioned object is absent in device tree

33039

OneIoT ACS > LWM2M > FOTA > CoAP over TCP > Firmware failed

  1. Added support for delivery protocols: CoAP_TCP(4), CoAP_TLS(5)

  2. Applied to software and firmware functionalities

  3. Properties extended (possible values):

Software content delivery protocol

Firmware content delivery protocol

Requires db change

Requires logback.xml replace

=== 2024.11.22 - Build 0.0.4

Issue ID Description

34200

OneIoT ACS > Update group > Diagnostics > FCC > WAN Usage repetition period reached > Test is not stopped

34227

OneIoT ACS > Update group > Diagnostics > FCC > Add failed state with "Device offline" comment

34232

OneIoT ACS > Group Update > FCC diagnostics > Device sends diagnostic results > Incorrect timestamp stored into DB

33202

OneIoT ACS > USP > Device Update > File Upload > Description > Send update > Incorrect URL sent to the device

34251

OneIoT ACS > Group Update > FCC diagnostics > Device sends diagnostic results > Incorrect timestamp stored into DB

34249

OneIoT ACS > At least 100 devices > Group Update > FCC diagnostics > Error in log file

=== 2024.11.20 - Build 0.0.3

Issue ID Description

33195

OneIoT ACS > "Bootstrap WRITE mode=OBJECT" > Any device start bootstrap > All write operations with the same token

32965

OneIoT ACS > LWM2M > "Bootstrap WRITE mode"="RESOURCE" > "Default content type"="EMPTY" > Incorrect content format is used for bootstrap write operations

30902

OneIoT ACS > Oracle > LWM2M > Bootstraped device > Settings > LWM2M > Bootstrap > Log > Response is absent

32560

OneIoT ACS > LWM2M > Bootstrap > Bootstrap configuration with "Access Control" object > Bootstrap read not performed

33164

OneIoT ACS > USP > BULK DATA Profile is not pushed by ACS

33148

OneIoT ACS > USP > Software manager > Install > GPV task is generated for an incorrect object

33065

OneIoT ACS > LWM2M > "JSON" / "SenML JSON" > Register device > Irrelevant "Manufacutrer" name is present

33809

OneIoT ACS > LWM2M > "Write. Resources update mode"="Partial Update" > Device Update > Advanced View > SPV for any single instances resource > "POST" request with incorrect URI is sent

30896

CPE Admin > USP > Group Update / Events / Device profile > Upload > Vendor Configuration File > Task with incorrect URL generated

32647

OneIoT ACS > USP > Group Update > File Upload > Vendor log file > Incorrect ".cfg" file format is used

Changes described in SDD SDD_LWM2M_Bootstrap_Redesign.docx

Configuration changes:

Removed: Enable discover resources after writing

Added: Bootstrap validation mode

=== 2024.11.01 - Build 0.0.2

Issue ID Description

33358

OneIoT ACS > USP > GPV > Valid object without instances > Correct empty response is considered an error

33516

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > No wildcard > New device > Excessive task generated

33658

OneIoT ACS > LWM2M > "Write. Resources update mode" = "Replace" > Device Update > SPV > "POST" request instead of "PUT" request is sent

34026

OneIoT ACS > LwM2M > Device sent CID > ACS doesn’t save CID in DB

Properties update (Common tab):

Write. Resources update mode renamed to Write. Multi-instance resources update mode

New: Write. Single-instance resources update mode

=== 2024.10.10 - Build 0.0.1

Issue ID Description

33791

CPE Admin > USP > Device Update > Software Manager > Install > "ExecutionEnvRef" input argument is absent from the "OPERATE" message

32830

OneIoT ACS > USP > MTP = "WebSocket" > Malformed USP record > OneIoT ACS doesn’t close the connection

32834

OneIoT ACS > USP > MTP = "STOMP" > Malformed USP record > OneIoT ACS sends a STOMP "ERROR" frame and closes the TCP connection

33459

OneIoT ACS > USP > Register > Adding subscription instance for the "Boot!" event is incorrect

31072

OneIoT ACS > USP > Device Update > Advanced View > Add object > Impossible to initiate adding object task with "allow_partial"="true"

32325

OneIoT ACS > USP > MTP = "MQTT" > SUBSCRIBE packet with QoS = "1" > Subscribe Ack > ACS sends PUBLISH packets with QoS = "0"

32399

OneIoT ACS > USP > E2E session context functionality > Trace doesn’t contain "sequence_id" and "expected_id" fields

32772

CPE Admin > USP > Device Update > Advanced view > Impossible to initiate "Device.DeviceInfo.FirmwareImage.{i}.Activate()" command with mandatory input arguments

31111

CPE Admin > USP > Device Update > Advanced View > Impossible to initiate GetInstances / GetSupportedProtocol task

31133

OneIoT ACS > USP > Device Update > Advanced View > Impossible to initiate SendOnBoardRequest task with "send_resp"="false"

31122

OneIoT ACS > USP > Device Update > Advanced View > Impossible to initiate Reboot task with "send_resp"="false"

31128

OneIoT ACS > USP > Device Update > Device Diagnostics > Any diagnostics > Impossible to initiate diagnostics task with "send_resp"="true"

Version 6.4.8

Latest build: 0.0.7

=== 2024.11.26 - Build 0.0.7

Issue ID Description

34251

OneIoT ACS > Group Update > FCC diagnostics > Device sends diagnostic results > Incorrect timestamp stored into DB

34249

OneIoT ACS > At least 100 devices > Group Update > FCC diagnostics > Error in log file

34270

OneIoT ACS > Fixed Windstream issue

=== 2024.11.21 - Build 0.0.6

Issue ID Description

34200

OneIoT ACS > Update group > Diagnostics > FCC > WAN Usage repetition period reached > Test is not stopped

34227

OneIoT ACS > Update group > Diagnostics > FCC > Add failed state with "Device offline" comment

34232

OneIoT ACS > Group Update > FCC diagnostics > Device sends diagnostic results > Incorrect timestamp stored into DB

33516

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > No wildcard > New device > Excessive task generated

33658

OneIoT ACS > LWM2M > "Write. Resources update mode" = "Replace" > Device Update > SPV > "POST" request instead of "PUT" request is sent

34026

OneIoT ACS > LwM2M > Device sent CID > ACS doesn’t save CID in DB

Properties update (Common tab):

Write. Resources update mode renamed to Write. Multi-instance resources update mode

New: Write. Single-instance resources update mode

Moved from 6.4.7

=== 2024.10.23 - Build 0.0.5

Issue ID Description

32749

OneIoT ACS > LWM2M 1.1 > Monitor fot at least 2 resources > Incorrect content format for "CoAP PUT" request

33997

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > Restart ACS > "RST" message is generated by OneIoT ACS on "Notify" messages

Requires DB change

CpeParameterName cache: skipping parameters with instances which are not in INTEGER scope

=== 2024.09.27 - Build 0.0.4

Issue ID Description

33823

OneIoT ACS > MySQL > Group Update > FCC latency > 8 DIAGNOSTICS COMPLETE > GPV task not sent to device

=== 2024.09.26 - Build 0.0.3

Issue ID Description

33803

OneIoT ACS > Reports > FCC report > FCC latency test > "Failed" test status > Comment is absent

=== 2024.09.24 - Build 0.0.2

Issue ID Description

33611

CPE Admin > Events > CPE Restore on 0 Bootstrap > Provisioning task during backup restore not working

33365

OneIoT ACS > Settings > Events > To fix long lifetime thread issue. Change permanent thread to scheduler

33364

OneIoT ACS > Settings > Events > To change default settings for Attempts, Interval and Timeout

32948

OneIoT ACS > Underprivileged data type stored in DB

32753

CPE Admin > Settings > System Settings > ACS Settings > "qoeMonitoringDefaultPeriod" parameter > Change description

26339

OneIoT ACS > Multiple diagnostics > Diagnostics fail due to overlapping

33237

CPE Admin > LWM2M > Opaque > "SPV" task with huge a value > Task is not generated

DB change required

=== 2024.09.19 - Build 0.0.1

Issue ID Description

33644

CPE Admin > Reports > FCC report > Diagnostic not executed > Deprecated "cpe" word is present

33472

CPE Admin / CSR > Critical & High security defects 2

33698

OneIoT ACS > Device registration > Device tree not saved

33103

OneIoT ACS > LWM2M > Platform does not save data sent in response to Cancel Observation

Version 6.4.7

Latest build: 0.0.37

=== 2025.03.20 - Build 0.0.37

Fixed CBOR parsing

=== 2024.12.24 - Build 0.0.36

UG improved spreading

=== 2024.12.24 - Build 0.0.35

UG improved spreading

=== 2024.12.23 - Build 0.0.34

Issue ID Description

34393

OneIoT ACS > Settings > Protocols > LWM2M > Configuration > Lifecycle > Allow reused address device state > Hint > Spelling error

34391

OneIoT ACS > LWM2M > Register device > All tasks are completed > New device with same address but different endpoint > Error

Protection for concurrent address usage.

1. New property: Lifecycle → Allow reused address device state

Allows to enable special state for devices which address was reused by other device (registration with same address and diff endpoint name)

2. Deactivation of the existing device (online must be only one device at time per address)

3. ACSStats improvements:

Address duplicates. Self-Overridden - will be increased if same endpoint name will be registered during already online onboard device

Address duplicates. Overridden - will be increased if new endpoint name will be registered during already online onboard device

Removed schema retrieving in oracle

=== 2024.12.17 - Build 0.0.33

UG improved spreading

removed schema retrieving in oracle

=== 2024.12.16 - Build 0.0.32

UG added spreading by 700 concurrent devices per each 700 seconds

=== 2024.12.09 - Build 0.0.31

UG performance fixes

=== 2024.12.02 - Build 0.0.30

UG performance fixes

=== 2024.11.26 - Build 0.0.29

UG performance fixes

Performance test should be performed with

<httpSessionLimit>64</httpSessionLimit>

=== 2024.11.18 - Build 0.0.28

UG diagnostics fix

UG 15K start fix

UG crash because of PK_QOE_CPE violated exception fix

=== 2024.11.11 - Build 0.0.27

UG ORA-01438 fix

UG crash because of PK_QOE_CPE violated exception fix

=== 2024.10.23 - Build 0.0.26

Added TR069 requests overload protection

=== 2024.10.23 - Build 0.0.25

Issue ID Description

34026

OneIoT ACS > LwM2M > Device sent CID > ACS doesn’t save CID in DB

=== 2024.10.15 - Build 0.0.24

Issue ID Description

33997

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > Restart ACS > "RST" message is generated by OneIoT ACS on "Notify" messages

Requires DB change

=== 2024.10.15 - Build 0.0.23

Issue ID Description

33988

OneIoT ACS > Azure > LWM2M > Offline device goes online > Resource value changed > Device twin reported property is not updated

=== 2024.10.10 - Build 0.0.22

Issue ID Description

33658

OneIoT ACS > LWM2M > "Write. Resources update mode" = "Replace" > Device Update > SPV > "POST" request instead of "PUT" request is sent

33516

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > No wildcard > New device > Excessive task generated

Properties update (Common tab):

Write. Resources update mode renamed to Write. Multi-instance resources update mode

New: Write. Single-instance resources update mode

=== 2024.10.06 - Build 0.0.21

Issue ID Description

33669

OneIoT ACS > Infinite locking removed

Requires hazelcast-client.xml change.

Add bewfor <near-cache> tag:

<near-cache name="CpeParameter*">

<in-memory-format>OBJECT</in-memory-format>

<invalidate-on-change>true</invalidate-on-change>

<eviction eviction-policy="LFU" max-size-policy="ENTRY_COUNT" size="10000"/>

</near-cache>

=== 2024.09.19 - Build 0.0.20

Issue ID Description

33472

CPE Admin / CSR > Critical & High security defects 2

33698

OneIoT ACS > Device registration > Device tree not saved

33103

OneIoT ACS > LWM2M > Platform does not save data sent in response to Cancel Observation

=== 2024.09.18 - Build 0.0.19

Issue ID Description

33766

OneIoT ACS > GPN on root (empty) object > Removed unneeded HC call during creating GPN on root (empty) object

=== 2024.09.10 - Build 0.0.18

Issue ID Description

33493

CPE Admin > Reports > FCC report > Start / End test > Add microseconds

DB change required

=== 2024.09.07 - Build 0.0.17

Issue ID Description

33669

OneIoT ACS > Infinite locking removed

33671

OneIoT ACS > Removed unneeded requests to the cache

33672

OneIoT ACS > All HC nodes stats are available in ACS log

33673

OneIoT ACS > Additional logging for crisis places added

=== 2024.09.06 - Build 0.0.16

Issue ID Description

33523

OneIoT ACS > LWM2M > Firmware > "Firmware process mode" = "notify" > "GET" with "Observe: 0" on "/5/0/3" is not sent

33427

OneIoT ACS > LWM2M > Monitoring > At least 2 resources > Edit monitor > Delete one resource > "Observation "Off" task not sent to device

33342

OneIoT ACS > LWM2M > "Resource Instance" parameter > subscribeCpeParameterEvent > Register device > SetNotification task isn’t generated

33438

OneIoT ACS > LWM2M > "Request queue. Enable queue mode" = true > Device profile with monitor > New device > "Observe" requests > Response is absent > Next request is sent by OneIoT ACS

33360

OneIoT ACS > LWM2M > Several monitors with "GET" monitoring type > "GET" request related to only one monitor is performed

DB change required (changeSet "v6.4.7.a-5")

=== 2024.08.30 - Build 0.0.15

Issue ID Description

33496

OneIoT ACS > LWM2M 1.0 > Partial Update > Device Update > SPV > 2+ resources > Task generated on 1 resource

33649

OneIoT ACS > TR-069 > Fix interrupting TR incoming threads

=== 2024.08.12 - Build 0.0.14

Issue ID Description

33368

OneIoT ACS > LWM2M 1.1 > "Write. Resources update mode" = "Partial update with existing" / "Partial update" > Multiple instances resource > Add instance > "POST" request with incorrect "URI"

33347

OneIoT ACS > Immediate regsitration update after the registration request > Can’t find a CPE with the given registration id

Note: to check functionality - just send reg-update after reg request, before GET /3/0. It must be succeeded.

=== 2024.07.29 - Build 0.0.13

Issue ID Description

33402

OneIoT ACS > ACS WS > LwM2M with cumulative data push request > subscribeCpeParameterEvent > Incorrect tamestamp in generated message

=== 2024.07.29 - Build 0.0.12

Issue ID Description

33402

OneIoT ACS > ACS WS > LwM2M with cumulative data push request > subscribeCpeParameterEvent > Incorrect timestamp in generated message

Parameter change date is taken from LwM2M device now instead of the current ACS time

=== 2024.07.23 - Build 0.0.11

Issue ID Description

33353

OneIoT ACS > LWM2M > Monitoring > "Monitoring type" = "Observe" > Save and activate > Tasks not generated

32928

OneIoT ACS > LWM2M > "Use sub-branches for tree root GET/DISCOVER requests"="false" > Advanced View > Root > Get current > GPV task remains in pending state

33057

OneIoT ACS > LWM2M 1.0 > "Write. Resources update mode" = "Partial update with existing" > Multiple instance resource > SPV on instance > "POST" request with incorrect "URI"

33351

CPE Admin / CSR > LWM2M > Device Update > Advanced View > GPV task on the "Root" object > An error occurred

26322

OneIoT ACS > LWM2M > Device Profile > Register new device > Incorrect order of GPV task on root objects

32526

OneIoT ACS > LWM2M > 1.1 > Device Profile > Register device > Incorrect task sequence

33357

CPE Admin > Reports > FCC report > Report with "Speed tire = 0.25" > Select > Incorrect speed tire value displayed

=== 2024.07.17 - Build 0.0.10

Issue ID Description

33342

OneIoT ACS > LWM2M > "Resource Instance" parameter > subscribeCpeParameterEvent > Register device > SetNotification task isn’t generated

=== 2024.07.12 - Build 0.0.9

Issue ID Description

32299

OneIoT ACS > USP > MTP = "Websocket" > Device is online > Internet connection lost > Device connection status doesn’t change to "offline" for more than two hours

33334

OneIoT ACS > LWM2M > Monitoring > "Monitoring type" = "Get" > Save and activate > Edit > Change "Monitoring type" > Save > "GET" request on monitoring parameter is sent by OneIoT ACS

33298

OneIoT ACS > LWM2M > Monitoring > Monitor with "Monitoring type" = "Send" > "Observe" operation is sent by OneIoT ACS

33299

OneIoT ACS > LWM2M > Monitoring > Monitor with "Monitoring type" = "Get" > Registration update > "GET" request on monitoring parameter is not sent by OneIoT ACS

33293

OneIoT ACS > LwM2M > Monitoring > To add passive monitoring feature

33330

OneIoT ACS > LWM2M > Device Profile > Register new device > Incorrect GPV task is generated by OneIoT ACS

Running monitoring mode change update. Will be no task, but monitored parameters will behave according mode.

DB update required: <changeSet id="v6.4.7.a-1" author="eldad">

Scenario to reproduce:

  • register device

  • remove some object instance cpe resource in db

For ex.:

SELECT * FROM ftacs.lwm2m_cpe_resources where cpe_id = 108581 and cpe_parameter_id = (select id from cpe_parameter_name where name = 'Root.Connectivity Monitoring.0.');

  • try to Get current for it

=== 2024.07.11 - Build 0.0.8

Issue ID Description

33297

OneIoT ACS > LWM2M > 1011 Event > HTTP GET request is not standard compliant

32733

OneIoT ACS > Multi-domain / Multi-ISP > Specific domain user > Settings > System Settings > External System > MQTT > Create configuration > Impossible to delete created configuration

32701

OneIoT ACS > LWM2M > Longitude > Incorrect float values parser

33102

OneIoT ACS > LWM2M 1.0 > "Bootstrap WRITE mode" = "INSTANCE" > "Senml JSON" / "Senml CBOR" > Bootstrap > Irrelevant content type is used by OneIoT ACS

32966

OneIoT ACS > Settings > Protocol > LWM2M > Configuration > Bootstrap > Default content type > Incorrect "singular" word is used

32964

OneIoT ACS > LWM2M > Bootstrap request > Bootstrap finished > Settings > Protocols > LWM2M > Bootstrap > Log > Bootstrap log record is absent

32965

OneIoT ACS > LWM2M > "Bootstrap WRITE mode"="RESOURCE" > "Default content type"="EMPTY" > Incorrect content format is used for bootstrap write operations

33287

ACS > To add OAUTH2.0 authentication on Hardcoded Events

Hint updated for properties: 'Device default content type', 'Default content type'

JBOSS libraries changed: unpack cxf.zip to: JBOSS_HOME/modules/system/layers/base/org/apache/cxf

DB changes required. Liquibase scripts provided

=== 2024.07.03 - Build 0.0.7

Issue ID Description

33288

ACS > To add hardcoded event for 1boot

33229

OneIoT ACS > "cpe_parameter_name" table > Big amount of multiple instances parameters > Cache storing restructuring request

DB changes required (changeSet id="v6.4.7.a-2")

=== 2024.07.01 - Build 0.0.6

Issue ID Description

33292

OneIoT ACS > Clean DB > Start > OneIoT ACS is not started

33222

OneIoT ACS > subscribeCpeParameterEvent > Device brings value > Event message isn’t generated

33182

ACS > Group Update > Reactivation > Add reactivation fail handling

=== 2024.06.27 - Build 0.0.5

Issue ID Description

33209

OneIoT ACS > LWM2M > "Notification Observation attributes" > Activate Event > Incorrect Pmin / Pmax values sent

33063

OneIoT ACS > LWM2M 1.1 > TLV > "Write. Resources update mode" = "Partial update" > Multiple instance resource > SPV on instance > Request with incorrect structure

33020

OneIoT ACS > LWM2M > "Write. Resources update mode" = "Replace" > Multiple instance resource > Add instance > "POST" request is sent by OneIoT ACS

33021

OneIoT ACS > LWM2M 1.1 > "Write. Resources update mode" = "Partial update with existing" > Multiple instance resource > Add instance > "POST" request with added instance is sent by OneIoT ACS

33051

OneIoT ACS > LWM2M 1.1 > Multiple instance resource > Add instance > Request with incorrect structure

33285

OneIoT ACS > TR-069 > Specific device > Empty "ProductClass" > Add device registration capability

33284

OneIoT ACS > TR-069 > Wrong credentials > No "RetryCount"-related entry in "server.log"

33283

OneIoT ACS > Specific product class > Inform without "6 Connection Request" > Add ability to block processing

33282

OneIoT ACS > External system > Add ability to exclude unnecessary external system

33281

OneIoT ACS > TR-069 > Wrong credentials > Reducing connection attempt with OneIoT ACS

32617

OneIoT ACS > USP > MTP = "MQTT" > MQTT v5.0 > CONNECT with "Request Response Information" > CONNACK doesn’t contain "Response Information"

32317

OneIoT ACS > USP > MTP = "MQTT" > MQTT v5.0 > PUBLISH packet > "Properties" don’t contain "Content Type"

31068

OneIoT ACS > USP > Device Update > Advanced View > Add object > GPV task is not generated

32207

CPE Admin / CSR > USP > Device removes instance during offline > Reregister > Device Update > Advanced View > Instance remains in tree

32189

OneIoT ACS > USP > MTP = "MQTT" > Device is online > Internet connection lost > 1.5*Device.MQTT.Client.{i}.KeepAliveTime interval > Device connection status doesn’t change to "offline"

32762

OneIoT ACS > USP > Monitoring > Request for notification retry mechanism

30741

OneIoT ACS > USP > "overwriteProvisionParameters"=1 > Device Update > Parameter in Provision Manager > SPV with reprovision=1 > Parameter not updated

32943

OneIoT ACS > LWM2M 1.0 > Advanced View > Root > Get current > "GET" request on "Root" object is sent

32942

OneIoT ACS > LWM2M 1.1 > Advanced View > Root > Discover > "FETCH" request is sent by OneIoT ACS

31163

OneIoT ACS > LWM2M 1.1 > "Composite Read/Write/Observe operation handling mode"="PREFER" > Device Update > Advanced View > GPV task on the "Root" object > Read-composite task (CON-FETCH) is absent

Removed property Write. Multi-instance resource TLV/s type. Server always packs resource instances inside resource TLV.

Changed hint for property: Write. Multi-instance resource TLV/s type

In some bug exists sentance about incorrect request structure for TLV with assuming that tlv array (resource instance/s) must be inside payload - please try, new property:

Write. Multi-instance resource TLV/s type - Resource instance will cover requirement. But not sure that customers case about it.

Hint and property name changed.

Note: to see FETCH for '/' make sure that property 'Lifecycle → Use sub-branches for tree root GET/DISCOVER requests' is disabled.

=== 2024.06.26 - Build 0.0.4

Issue ID Description

33063

OneIoT ACS > LWM2M 1.1 > TLV > "Write. Resources update mode" = "Partial update" > Multiple instance resource > SPV on instance > Request with incorrect structure

33020

OneIoT ACS > LWM2M > "Write. Resources update mode" = "Replace" > Multiple instance resource > Add instance > "POST" request is sent by OneIoT ACS

33021

OneIoT ACS > LWM2M 1.1 > "Write. Resources update mode" = "Partial update with existing" > Multiple instance resource > Add instance > "POST" request with added instance is sent by OneIoT ACS

33051

OneIoT ACS > LWM2M 1.1 > Multiple instance resource > Add instance > Request with incorrect structure

=== 2024.06.26 - Build 0.0.3

Issue ID Description

33271

OneIoT ACS > TR-069 > Try to register new device > Device isn’t registered

33208

CPE Admin > Device Update > File Download > Firmware upgrade > Incorrect file type is sent

DB update required

=== 2024.06.04 - Build 0.0.2

Issue ID Description

33184

REST API > Issue in sending large value data to customer subscribed URL

33252

OneIoT ACS > LWM2M > Register > All GPV tasks on root objects failed

33229

OneIoT ACS > "cpe_parameter_name" table > Big amount of multiple instances parameters > Cache storing restructuring request

=== 2024.05.30 - Build 0.0.1

Issue ID Description

32691

OneIoT ACS > LWM2M > Bootstrap configuration with 2 instances for any object > Device sends bootstrap request > Impossible to send "BOOTSTRAP-WRITE" operation on object

32939

OneIoT ACS > LWM2M 1.1 > "Use sub-branches for tree root GET/DISCOVER requests"="true" > Advanced View > Root > Get current > "GET" requests are sent

32940

OneIoT ACS > LWM2M 1.1 > "Use sub-branches for tree root GET/DISCOVER requests"="true" > Advanced View > Root > Discover > "Discover" requests are processed without queue mode

32678

OneIoT ACS > LWM2M > X.509 certificate > "LWM2M Server X509 TLS endpoint" port is not listened

32572

CPE Admin > Device Update > LWM2M > Advanced View > Add object > Readeable resources are absent from created instance

10726

OneIoT ACS > LWM2M > Device Update > Advanced View > "LWM2M Security" resource is absent from the tree

30795

IoT ACS > Settings > Protocols > LWM2M > Configuration > Lifecycle > Create resource tree for declared resources on registration > Hint doesn’t match behavior

32549

OneIoT ACS > LWM2M > Register device with "/23" object > Excessive GPV task is generated for mentioned object

10726

OneIoT ACS > LWM2M > Device Update > Advanced View > "LWM2M Security" resource is absent from the tree

32763

OneIoT ACS > LWM2M > "Notification observation attributes" non-default > Activate event > Incorrect observation attribute values are sent to device

25923

OneIoT ACS > LWM2M > Resources missing > Not coming in new builds

32558

OneIoT ACS > Device Update > LWM2M > File Download > Software package > GET requests on /9/0/12, /9/0/0 and /9/0/1 are absent

32764

QoE GUI > LWM2M > Monitoring > Object > Single device > Object-related KPI graph is not displayed

33170

OneIoT ACS > Fix of the deadlock, which found on Airtel. Now all data modify operations with cpe_parameter table are synchronized by cpe_id

33128

OneIoT ACS > TR-069 > subscribeCpeParameterEvent > Notification is set > Factory reset > Notification task is not generated

33127

OneIoT ACS > Group update > FCC latency diagnostics > Device is offline > Additional GPV task is generated every minute

33132

OneIoT ACS > Group Update > FCC speed test > WAN usage threshold > "Download" field with "0" value > Save and activate > GPV task on "BytesSent" parameter is absent

32969

OneIoT ACS > TR-069 > config_custom_data.xml > Notification task is duplicated

32515

CPE Admin > Oracle > Settings > Whitelist > Serial Number > Check known serial > An error occurred

27515

OneIoT ACS > LWM2M > Acsstats security

32939

OneIoT ACS > LWM2M 1.1 > "Use sub-branches for tree root GET/DISCOVER requests"="true" > Advanced View > Root > Get current > "GET" requests are sent

32691

OneIoT ACS > LWM2M > Bootstrap configuration with 2 instances for any object > Device sends bootstrap request > Impossible to send "BOOTSTRAP-WRITE" operation on object

Configuration changes:

Extended Bootstrap WRITE mode - added OBJECT mode.

OBJECT mode supported only for formats: TLV, SenML-JSON, SenML-CBOR

Renamed property: "Use sub-branches for tree root GET/DISCOVER requests" → "Use sub-branches for tree root GET/FETCH/DISCOVER requests"

Property 'Use sub-branches for tree root GET/DISCOVER requests' hint updated:

Note: GET/FETCH depends from device version and property 'Composite Read/Write/Observe operation handling mode'

Lifecycle configuration changes:

New: Resource tree. Undeclared object instances

Changed default value: Resource tree. Disabled objects to 0,21,23

To check it - remove 0 from Resource tree. Disabled objects. And register new device.

Lifecycle configuration changes:

Removed: Skip device tree processing on registration

Removed: Create resource tree for declared resources on registration

New: Resource tree. Build mode — it is created instead of previous two.

New: Resource tree. Disabled objects — it is created to hide /23 or make be visible /0 objects.

Note to update existing customers:

If 'Skip device tree processing on registration' before update was enabled - make sure that you have set 'Resource tree. Build mode':

to NONE if 'Create resource tree for declared resources on registration' was disabled,

to SKELETON if 'Create resource tree for declared resources on registration' was enabled.

Remove default value from ObjectVersion. Was 1.0, as cause of issue for 25923.

Defect3. Xml definition contains 2 versions by server model. Lwm2m and object versions. For 4th resource it contains only object version. Lwm2m was default 1.0 on server.

Changed to use object ver tag in first priority. If it’s missing or null - server will take lwm2m version from xml

Task behavior changes (if device was registered with obj id = XXX, and on the fly XXX was removed, XXX related parameter still in device tree):

If GET task per resource which doesn’t have definition in local registry - it will be failed with msg: Resource definition/s not found

If GET task per multiple resources and at least one is success - task will be completed

Note1: OMA registry REST API 'www.openmobilealliance.org' doesn’t work. I.e. currently functionality with automatic resource definition uploading is not working. Smth wrong with URL. Need review and probably open new bug

Note2: currently impossible to have 2 same-path resources with different versions. This will be reviewed in next iterations, with multiple-resource version feature development.

Note3: fix for already produced versions with resource duplicators will be realized later. Thinking about solution. DB path or server on start…​

Changed behavior:

Software process will be finalized by GET /9/* request. Results of GET:

On timeout - fail.

On response:

Update device resources on content response.

If verification by version is enabled and file ver filled - versions /9/*/1 and target must be same for success. Otherwise - fail

If verification by version is enabled and file ver NOT filled - success

If verification by version is disabled - success

Added monitoredParameterCache child-parameters when monitoring task is processing for resource with children.

web.xml file changed

Property 'Use sub-branches for tree root GET/FETCH/DISCOVER requests' hint updated:

Note: GET/FETCH/DISCOVER depends from device version and property 'Composite Read/Write/Observe operation handling mode'

Master is 6.4.7 now

Version 6.4.6

Latest build: 0.0.16RC

=== 2025.02.26 - Build 0.0.16RC

Issue ID Description

26339

OneIoT ACS > Multiple diagnostics > Diagnostics fail due to overlapping

=== 2024.12.05 - Build 0.0.15

Issue ID Description

34201

One IoT > LWM2M > Execute resource > Device method not found

=== 2024.09.18 - Build 0.0.14

Issue ID Description

33472

CPE Admin / CSR > Critical & High security defects 2

33611

CPE Admin > Events > CPE Restore on 0 Bootstrap > Provisioning task during backup restore not working

DB change required

=== 2024.09.17 - Build 0.0.13

Issue ID Description

33347

OneIoT ACS > Immediate regsitration update after the registration request > Can’t find a CPE with the given registration id

33493

CPE Admin > Reports > FCC report > Start / End test > Add microseconds

DB change required

=== 2024.06.12 - Build 0.0.12

Issue ID Description

33330

OneIoT ACS > LWM2M > Read on object > Not found any device parameter

33342

OneIoT ACS > LWM2M > "Resource Instance" parameter > subscribeCpeParameterEvent > Register device > SetNotification task isn’t generated

Scenario to reproduce:

  • register device

  • remove some object instance cpe resource in db

For ex.:

SELECT * FROM ftacs.lwm2m_cpe_resources where cpe_id = 108581 and cpe_parameter_id = (select id from cpe_parameter_name where name = 'Root.Connectivity Monitoring.0.');

  • try to Get current for it

=== 2024.06.12 - Build 0.0.11

Issue ID Description

33209

OneIoT ACS > LWM2M > "Notification Observation attributes" > Activate Event > Incorrect Pmin / Pmax values sent

=== 2024.05.31 - Build 0.0.10

Issue ID Description

33159

OneIoT ACS > Group Update > FCC speed test > WAN usage threshold > "Upload" field with "0" value > Save and activate > Upload diagnostics task is not generated

33194

OneIoT ACS > FCC result row creating when cpe failing or rejecting task

=== 2024.05.27 - Build 0.0.9

Issue ID Description

33128

OneIoT ACS > TR-069 > subscribeCpeParameterEvent > Notification is set > Factory reset > Notification task is not generated

33127

OneIoT ACS > Group update > FCC latency diagnostics > Device is offline > Additional GPV task is generated every minute

33132

OneIoT ACS > Group Update > FCC speed test > WAN usage threshold > "Download" field with "0" value > Save and activate > GPV task on "BytesSent" parameter is absent

=== 2024.05.22 - Build 0.0.8

Issue ID Description

33109

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > Observation task is set > Registration request > Observation task is not generated

33119

OneIoT ACS > FCC Latency test > Design change

33120

OneIoT ACS > CPE Admin > FCC diagnostics > To add an option to disable "WAN Usage Threshold"

FCC changes

Configuration changes: fcc.properties changed

=== 2024.05.20 - Build 0.0.7

Issue ID Description

10726

OneIoT ACS > LWM2M > Device Update > Advanced View > "LWM2M Security" resource is absent from the tree

30795

IoT ACS > Settings > Protocols > LWM2M > Configuration > Lifecycle > Create resource tree for declared resources on registration > Hint doesn’t match behavior

32549

OneIoT ACS > LWM2M > Register device with "/23" object > Excessive GPV task is generated for mentioned object

32678

OneIoT ACS > LWM2M > X.509 certificate > "LWM2M Server X509 TLS endpoint" port is not listened

To check it - remove 0 from Resource tree. Disabled objects. And register new device.

Lifecycle configuration changes:

New: Resource tree. Undeclared object instances

Changed default value: Resource tree. Disabled objects to 0,21,23

Lifecycle configuration changes:

Removed: Skip device tree processing on registration

Removed: Create resource tree for declared resources on registration

New: Resource tree. Build mode — it is created instead of previous two.

New: Resource tree. Disabled objects — it is created to hide /23 or make be visible /0 objects.

Note to update existing customers:

If 'Skip device tree processing on registration' before update was enabled - make sure that you have set 'Resource tree. Build mode':

to NONE if 'Create resource tree for declared resources on registration' was disabled,

to SKELETON if 'Create resource tree for declared resources on registration' was enabled.

=== 2024.05.08 - Build 0.0.6

Issue ID Description

33086

OneIoT ACS > Group update > FCC diagnostics > GET for WAN usage threshold > Long value in responce > Error in ACS log

=== 2024.05.03 - Build 0.0.5

Issue ID Description

32764

QoE GUI > LWM2M > Monitoring > Object > Single device > Object-related KPI graph is not displayed

Added monitoredParameterCache child-parameters when monitoring task is processing for resource with children.

=== 2024.04.29 - Build 0.0.4

Issue ID Description

32705

OneIoT ACS > LWM2M > Bootstrap > X.509 certificate > SENML JSON / SENML CBOR > "Bootstrap WRITE mode=INSTANCE" > PUT /0/x > Incorrect value sent to the device

32354

OneIoT ACS > LWM2M > "CBOR resource mask (regExp)" with empty value > Register device with any resource with CBOR data > Value of resource with CBOR data is displayed as parsed

31152

OneIoT ACS > LWM2M > Bootstrap > PSK > "Bootstrap WRITE mode=INSTANCE" > PUT /0 > Incorrect value sent to the device

32660

OneIoT ACS > LWM2M > Multiple instance opaque resource with "Base64" encoded data > GET > Incorrect data is displayed

Fixed configuration property 'Opaque. Value encoding mode'. Added CBOR value. CpeAdmin requires it to create view components for values.

CpeAdmin changes:

Please use version: 6.4.6 0.0.2+

1. LWM2M. Resources with CBOR mask applicable values will be presented as cbor@value. Sample: cbor@[123,123,123[123,123]]

Prefix cbor@ - will be cleared and value will be shown as: [123,123,123[123,123]]

2. LWM2M. For editing opaque values added first item in type dropdown: Raw data.

Note: lwm2m opaque types are stored in db property: select valid_values from iot_configuration_property where program_name='LWM2M.Configuration.Commons.opaqueResourceType'

Property params filled by server on start. (already existing logic)

Configuration changes:

Removed:

Opaque resource type

Added:

Opaque. Friendly text pattern (regExp)

Opaque. Value decoding mode  — it is similar to previous version property (Opaque resource type) regarding values UI displaying.

Opaque. Opaque. Value encoding mode - this one responsible for values sending to device (Write/SET operations)

Emulator changes:

Please use version: 1.7.196+

Fixed senml-json/cbor value encodings

Added feature to pass any value in opaque resource types. Example:

<parameter name="/19/0/0/5" type="opaque" value="This raised exception a year ago. Now is possible"/>

Note: opaquehex type must contain only HEX string. Otherwise it will rise up exception

Note: opaque type may contain:

  • any string which is not hex. Note: for json formats it will be based64

  • base64 string (passed as-is). Note: hex strings are always base64 strings.

  • if value can be matched as hex [a-z0-9] - it must be based https://base64.guru/converter/encode/hex. Otherwise will be displayable differences in GET results for octet stream and json formats.

Sample of emulator resources:

<parameter name="/19/0/0/0" type="opaque" value="[10270, 0, [1706005259, 86400, [[37, 98]]]]"/> <!-- isBase64 = false, if string contains [] - emul automaticatlly convert value to cbor than to base64 -->

<parameter name="/19/0/0/1" type="opaque" value="gxkoHgCDGmWvkwsaAAFRgIGCGCUYYg=="/> <!-- isBase64 = true, value will be decoded, than encoded to hex bytes  https://base64.guru/converter/encode/hex -->

<parameter name="/19/0/0/2" type="opaque" value="ODMxOTI4MWUwMDgzMWE2NWFmOTMwYjFhMDAwMTUxODA4MTgyMTgyNTE4NjI="/> <!-- Server can understand it. isBase64 = true, value will be decoded, than encoded to hex bytes  https://base64.guru/converter/encode/hex -->

<parameter name="/19/0/0/3" type="opaquehex" value="8319281e00831a65af930b1a00015180818218251862"/> <!-- passed as-is. Emulator will rise error if value is not hex -->

<parameter name="/19/0/0/4" type="opaque" value="aXQgaXMgdmFsdWUgNjQ="/> <!-- isBase64 = true, value will be decoded, than encoded to hex bytes  https://base64.guru/converter/encode/hex -->

<parameter name="/19/0/0/5" type="opaque" value="8319281e00831a65af930b1a00015180818218251862"/> <!-- isBase64 = true, this will rise the differences in octet-stream/tlv/cbor and json formats. Because for json value will be passed as-is. In byte formats value will be decoded as hex bytes. Correct way to pass such values to encode it (hex string to base64 string):  https://base64.guru/converter/encode/hex -->

<!--<parameter name="/19/0/0/6" type="opaquehex" value="[10270, 0, [1706005259, 86400, [[37, 98]]]]"/>--> <!-- this will raise emulator internal exception as it is not hex value -->

<parameter name="/19/0/0/7" type="opaque" value="must raise the exception but won't. now is possible to use it"/> <!-- this will be passed as hex encoded bytes https://www.hexator.com/ -->

Server changes:

Refactored functionality of the encoding/decoding opaque resources

Extended opaque encode/decode modes (see new configuration properties)

Fixed issues related to cbor, opaque and bootstrap resource encoding/decoding

  • /0/0/3 (psk identity) may be free text

  • /0/0/5 (psk key) is hex value, in db stored as hex by spec.

Returned bootstrap to finish with double pair of the req-response (californium or client issue - lib doesn’t catch the ACK response, but client sends response as req in final bs req)

=== 2024.04.26 - Build 0.0.3

Issue ID Description

32921

OneIoT ACS > Group Update / Events > Creating grouped tasks which get stuck (merged with 6.4.5 0.0.8)

32801

ACS > Security vulnerabilities

32947

One IoT > LWM2M > Payload is not parsed

32874

OneIoT ACS > SMM > Unable to manage container on Sagemcom F5380 device

32919

OneIoT ACS > Group update > Diagnostics > To add FCC Speed and Latency diagnostics

merged with 6.4.5 0.0.13

jboss update required

Subscription to parameter logic changed: now parameter sent to subscriber EACH time it received from CPE (not only on value change)

Previous behaviour (value change) can be enabled by adding -Dftacs.subscription.parameter.onlyValueChange=1 to JAVA_OPTS

fcc.properties jboss configuration file added

Requires DB change

=== 2024.04.04 - Build 0.0.2

Issue ID Description

32738

CPE Admin > USP > Group Update > Diagnostics > Incorrect "Failed" state is present

32426

OneIoT ACS > USP > E2E session context functionality > Register device > Incorrect increasing of "expected_id" field value

32400

OneIoT ACS > USP > E2E session context functionality > Duplicate message is not ignored

30867

OneIoT ACS > USP > config_custom_data.xml > Observation "On" task is absent

30719

OneIoT ACS > USP > Value change > ValueChange event is not generated

32427

OneIoT ACS > USP > MQTT / STOMP > Register device with incorrect ACS EndpointID > USP record with incorrect "to_id" field is not ignored

32517

OneIoT ACS > LWM2M > WhiteListEnabled=1 > Lifetime>=Whitelist. Lifetime for devices aren’t included (in seconds) > Tasks are transferred to the completed state

32692

OneIoT ACS > Settings > Protocols > LWM2M > Configuration > Common > Impossible to configure default content type for bootstrap mode

24739

OneIoT ACS > LWM2M > Protocol version 1.1 > LWM2M Server resource of version 1.1 > Resource is duplicated

Added new property in bootstrap tab: Default content type

Device registration flow is extended to check resource duplications and clear it in DB.

1. EXISTING Device must send a registration request

2. Server will check and remove corrupted objects/resources (if coap definition was removed but device still has some data in lwm2m_cpe_resources table):

SELECT cr.* FROM lwm2m_cpe_resources cr

WHERE cr.cpe_id = ?1

AND cr.coap_resource_id > 0

AND ((REGEXP_LIKE(cr.path, '^/[0-9]+/[0-9]+/[0-9]+/{0,1}[0-9]*$') AND cr.coap_resource_id NOT IN (SELECT id FROM lwm2m_coap_resources))

OR (REGEXP_LIKE(cr.path, '^[/][0-9]+[/]{0,1}[0-9]*$') AND cr.coap_resource_id NOT IN (SELECT object_id FROM lwm2m_coap_objects)))

  1. Server will check and remove resource duplicates by path (will leave only max(id) one resource):

SELECT cr1.* FROM lwm2m_cpe_resources cr1 WHERE cr1.cpe_id = ?1 AND cr1.path IN (SELECT cr.path FROM lwm2m_cpe_resources cr WHERE cr.cpe_id = cr1.cpe_id GROUP BY cr.path HAVING COUNT(cr.id) > 1)

  1. Some preparation for deprecation of table lwm2m_cpe_resources.

coap_resource_id column will have value 0. It is unused.

coap_resource_instance_id column will have value 0. It is unused.

Columns will be removed in feature versions.

=== 2024.03.22 - Build 0.0.1

Issue ID Description

32808

OneIoT ACS > LWM2M > "Device default content type"="JSON" > SPV on any object instance > Incorrect payload

32763

OneIoT ACS > LWM2M > "Notification observation attributes" non-default > Activate event > Incorrect observation attribute values are sent to device

Version 6.4.5

Latest build: 0.0.19

=== 2024.07.15 - Build 0.0.19

Issue ID Description

33342

OneIoT ACS > LWM2M > "Resource Instance" parameter > subscribeCpeParameterEvent > Register device > SetNotification task isn’t generated

=== 2024.06.12 - Build 0.0.18

Issue ID Description

33209

OneIoT ACS > LWM2M > "Notification Observation attributes" > Activate Event > Incorrect Pmin / Pmax values sent

From 6.4.6

=== 2024.06.06 - Build 0.0.17

Issue ID Description

33197

OneIoT ACS > LWM2M > "-Dftacs.subscription.parameter.onlyValueChange=1" > subscribeCpeParameterEvent > Huge resource value > Constant value > Webhook generated

=== 2024.06.06 - Build 0.0.16

Issue ID Description

33198

OneIoT ACS > subscribeCpeParameterEvent > Device brings value > Event message isn’t generated

33197

OneIoT ACS > LWM2M > "-Dftacs.subscription.parameter.onlyValueChange=1" > subscribeCpeParameterEvent > Huge resource value > Constant value > Webhook generated

=== 2024.06.05 - Build 0.0.15

Issue ID Description

33184

REST API > Issue in sending large value data to customer subscribed URL

33128

OneIoT ACS > TR-069 > subscribeCpeParameterEvent > Notification is set > Factory reset > Notification task is not generated

=== 2024.05.13 - Build 0.0.14

Issue ID Description

32763

OneIoT ACS > LWM2M > "Notification observation attributes" non-default > Activate event > Incorrect observation attribute values are sent to device

From 6.4.6

=== 2024.04.22 - Build 0.0.13

Issue ID Description

32950

OneIoT ACS > LWM2M > ACS WS > subscribeCpeParameterEvent > Resource with instances > CBOR > Value changed > No monitoring results

32974

OneIoT ACS > LWM2M > ACS WS > subscribeCpeParameterEvent > Notify with constant value > Event message not generated

Fixed behavior for subscriptions in case if a value is the same (repeated)

New property: LWM2M → Configuration → Observation → Multi-instance resource/s observe mode

=== 2024.04.16 - Build 0.0.12

Issue ID Description

32921

OneIoT ACS > Group Update / Events > Creating grouped tasks which get stuck

=== 2024.04.10 - Build 0.0.11

Issue ID Description

32874

OneIoT ACS > SMM > Unable to manage container on Sagemcom F5380 device

Subscription to parameter logic changed: now parameter sent to subscriber EACH time it received from CPE (not only on value change)

Previous behaviour (value change) can be enabled by adding -Dftacs.subscription.parameter.onlyValueChange=1 to JAVA_OPTS

=== 2024.04.01 - Build 0.0.10

Issue ID Description

32874

OneIoT ACS > SMM > Unable to manage container on Sagemcom F5380 device

32702

CPE Admin > Reports > Add "Software modules" report

=== 2024.03.26 - Build 0.0.9

Issue ID Description

32702

CPE Admin > Reports > Add "Software modules" report

=== 2024.02.26 - Build 0.0.8

Issue ID Description

32740

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > "monitoring.log" > No monitoring results

=== 2024.02.24 - Build 0.0.7

Issue ID Description

32742

OneIoT ACS > Create monitor with empty values for all attributes > Incorrect "CoAP PUT" request with attributes is sent to device

30978

OneIoT ACS > LWM2M 1.1 > "Composite Read/Write/Observe operation handling mode"="PREFER" > Monitoring with at least 2 resources > CON-FETCH message with "Observe "On" option is absent

32288

CPE Admin > Monitor with attributes for LWM2M > Device Update > Device Activity > Irrelevant "QoE: set periodic inform interval" task with "0" value is displayed

32708

OneIoT ACS > LWM2M > Monitoring > New / Edit > Attributes are not stored into ClickHouse DB

The period will be passed in next priority:

pmax (max value if multiple passed)

pmin (max value if multiple passed)

qoeMonitoringDefaultPeriod, default 60sec (acs settings, new property)

Monitoring period in case if passed both: pmin and pmax attrs for one or different params - will be taken the max value across all items.

Added validation for values pmin > pmax

=== 2024.02.23 - Build 0.0.6

Issue ID Description

32706

OneIoT ACS > Monitoring > Monitoring data > MQTT data streaming

26402

CPE Admin > Settings > UploadExtensions > Backup operation is not affected by these settingsnew ACS WS methods added:

 
<ftac:addExtensionForGroup>

<arg0>

<groupId>1</groupId>

<extension>.cfg</extension>

</arg0>

</ftac:addExtensionForGroup>

<ftac:removeExtensionForGroup>

<arg0>

<groupId>1</groupId>

</arg0>

</ftac:removeExtensionForGroup>

Requires DB change

=== 2024.02.21 - Build 0.0.5

Issue ID Description

32583

OneIoT ACS > LWM2M > "Partial Update" > SPV for more than 1 resource > SPV tasks are generated for each resource

32663

OneIoT > LWM2M > 1.1 > Add instance of multiple instances resource > Incorect "CoAP PUT" request sent to device

32558

OneIoT ACS > Device Update > LWM2M > File Download > Software package > GET requests on /9/0/12, /9/0/0 and /9/0/1 are absent

32694

OneIoT ACS > LWM2M > Wrong CoAP option for blockwise Pull request (moved from 6.3)

Removed: Settings → LWM2M → Configuration → Common → Default mechanism to write Resource values

Instead of created new: Settings → LWM2M → Configuration → Common → Write. Resources update mode

Changed hint according new property: Settings → LWM2M → Configuration → Common → Synchronize multi-instance resource before replace

Fix: after successful software update server sends GET /9/XXX request for branch which was updated. This request is not the part of software state-machine. Only resource synchronization.

LWM2M Delete request logging added

Added SoftwareModules object data saving in table cpe_software_parameter

Requires DB change

=== 2024.02.15 - Build 0.0.4

Issue ID Description

32434

CPE Admin > TR-069 > Device Profile > New/Edit > Download file > Save and activate > Task is absent from "Device Activity" list

32436

OneIoT ACS > ignoreBootstrapExistingCPE=0 > Profile task in pending > 0 BOOTSTRAP > Registration is not completed > GPN on root object is duplicated

32290

OneIoT ACS > Group Update > "Threshold" > Incorrect "Update status" is displayed

25860

OneIoT ACS > BulkData > Existing monitor > Add parameter / Change "Perform every" > Irrelevant tasks are sent to device

Merge lwm2m observe attriubtes changes from 6.4.4 0.0.9

=== 2024.02.12 - Build 0.0.3

Issue ID Description

32600

OneIoT ACS > LWM2M > Discarded registration update request > Incorrect "4.00" response

32646

OneIoT ACS > Device Update > LWM2M > Firmware without reboot > Firmware value is not updated

27618

OneIoT ACS > Subscribe for event > Parameter value isn’t returned

32615

CPE Admin > Device Update > File Download > Restore > Backup created from the profile is absent

Subscription req sample:

{

"models": [

"string"

],

"monitored": true,

"parameters": [

"Root.ManagementServer.Last connection",

"Root.ManagementServer.ConnectionRequestURL",

"Root.ManagementServer.Security Mode",

"Root.ManagementServer.Last server address"

],

"serials": [

"testmaks77777"

],

"urls": [

"http://localhost:33333"

]

}

Moved DB connections leak fix from 6.4.1

=== 2024.01.30 - Build 0.0.2

Issue ID Description

11855

OneIoT ACS > TR-069 / USP > Monitoring > Parameter > GPV to retrieve first value > Received data isn’t stored into QoE DB

30893

OneIoT ACS > USP > Group Update > "Backup" task > Task is not sent to device

=== 2024.01.30 - Build 0.0.1

Issue ID Description

32354

OneIoT ACS > LWM2M > "CBOR resource mask (regExp)" with empty value > Register device with any resource with CBOR data > Value of resource with CBOR data is displayed as parsed

34572

OneIoT ACS > Table ug_task_to_cpe_task overloading in case of Profile Events

Version 6.4.4

Latest build: 0.0.9

=== 2024.02.15 - Build 0.0.9

Issue ID Description

32683

OneIoT ACS > LWM2M > subscribeCpeParameterEvent > Attributes are not sent to device

30783

OneIoT ACS > LWM2M > Events > Implementation of observation attributes for monitored parameter

30784

OneIoT ACS > LWM2M > Device Profile > Implementation of observation attributes for monitored parameter

Moved DB connections leak fix from 6.4.1

Attributes for notification config changes:

Profile observation attributes - changed hint and default value

Notification observation attributes - new property, default attributes for: subscription, cust_config_data.xml, events

Events observation attributes - removed (Notification observation attributes used instead of due realization specific)

Custom data observation attributes - removed (Notification observation attributes used instead of due realization specific)

=== 2024.02.02 - Build 0.0.8

Azure IoT hub device status issue fixed

=== 2024.01.31 - Build 0.0.7

Issue ID Description

32645

OneIoT ACS > Extenal System > AzureIOT Hub > Incorrect functionality

=== 2024.01.15 - Build 0.0.6

Merge lwm2m fixes from Jio 6.4.1 0.0.121 build. !It doesn’t contain/related to new engine functionality by lwm2m device resources lifecycle!

=== 2024.01.09 - Build 0.0.5

Issue ID Description

32481

OneIoT ACS > LWM2M > Firmware update > Get on /5/0 > Irrelevant content type is used

32314

CPE Admin > Group Update > Update with rectivation > "Ends" = specific day > Specific day reached > Update remains in "Reactivation" state

=== 2024.01.05 - Build 0.0.4

Issue ID Description

32417

OneIoT ACS > Settings > Protocols > LWM2M > Firmware > CoAP Server IP > Incorrect hint

=== 2024.01.04 - Build 0.0.3

Issue ID Description

32509

OneIoT ACS > LWM2M > Bootstrap device > Settings > Protocols > LWM2M > Bootstrap > Log > Log is absent

DB change required (sample for mysql):

ALTER TABLE `ftacs`.`lwm2m_bs_session_log_details`

CHANGE COLUMN `activity_type` `activity_type` VARCHAR(16) NULL DEFAULT NULL ,

CHANGE COLUMN `descr` `descr` LONGTEXT NULL DEFAULT NULL ,

CHANGE COLUMN `message_origination` `message_origination` VARCHAR(8) NULL DEFAULT NULL ,

CHANGE COLUMN `response_trace` `response_trace` LONGTEXT NULL DEFAULT NULL ,

CHANGE COLUMN `status` `status` VARCHAR(32) NULL DEFAULT NULL ;

ALTER TABLE `ftacs`.`lwm2m_bs_session_log`

CHANGE COLUMN `endpoint_host` `endpoint_host` VARCHAR(64) NULL DEFAULT NULL ,

CHANGE COLUMN `security_type` `security_type` VARCHAR(16) NULL DEFAULT NULL ,

CHANGE COLUMN `status` `status` VARCHAR(32) NULL DEFAULT NULL ;

=== 2023.12.22 - Build 0.0.2

Issue ID Description

32445

OneIoT ACS > LWM2M > JSON / SENML-JSON / SENML-CBOR content type > GET Observ=0 on instance > GET Observ=1 > Irrelevant content type is used

32176

OneIoT ACS > Update group > Blocking issue

32413

OneIoT ACS > Code uses integer to create a transaction for API

Added configuration parameter

<!-- Legal values: 0, 1 | Default value: 1 (enabled) | If 1 - ACS will block any UG task processing in case of any UG task is already in sent state -->

<skipUGTaskProcessingIfUGTaskSentExists>1</skipUGTaskProcessingIfUGTaskSentExists>

tables changed:

cpe_set_param_backup

cpe_transaction_repeats

cpe_completed_task

cpe_failed_task

cpe_pending_task

cpe_rejected_task

ug_task_to_cpe_task

ug_transaction

WS types changed:

CpeTaskWS

TransactionIdResponse

invokeRPCResponse

WS methods changed:

reprovisionCPE

setCPEParams

rebootCPE

uploadFiles

factoryReset

deleteCPEObject

setCPEParamAttribs

invokeRPCMethod

downloadFiles

invokeCpeMethod

changeDUState

getTasksByTransId

Requires DB change

=== 2023.12.15 - Build 0.0.1

Issue ID Description

32186

OneIoT ACS > Settings > LWM2M > Configuration > Common > Unclear hints wording

30918

OneIoT ACS > LWM2M > Bootstrap > "Bootstrap WRITE mode" = "RESOURCE" > "Bootstrap process timeout (ms)" is reached > Tasks continue to be sent to the device

32242

OneIoT ACS > LWM2M > Add object > GPV task is not sent to device

32397

OneIoT ACS > USP > Device that supports bulk data > Start monitor > Irrelevant "Observation" task is generated

32282

OneIoT ACS > USP > Register device > Incorrect "NotifType" values in added Subscription instances

31129

OneIoT ACS > USP > Device Update > Device Diagnostics > Any diagnostics > "Operate" message doesn’t contain "command_key" field

32417

OneIoT ACS > Settings > Protocols > LWM2M > Firmware > CoAP Server IP > Incorrect hint

30677

OneIoT ACS > LWM2M > Events / Device Profile > GREATER / GREATER_EQUAL / LESS / LESS_EQUAL > "cpeParameterMonitor" event isn’t generated

15109

OneIoT ACS > LWM2M / MQTT / USP > Group Update > "Action" task > Irrelevant condition > Save and Activate > Update ignores condition

30668

CPE Admin > LWM2M v1.1 > Device Update > Advanced view > Object with writable parameters > Add Object > Save > Instance is missing from tree

27582

OneIoT ACS > LWM2M > Register > whiteListEnabled=1 > Open device > Irrelevant task is sent every second

32173

OneIoT ACS > LWM2M / USP > whiteListEnabled=1 / whiteListDisabledForExistingCpe=0 > Existing device is operable (LWM2M)

Merge with 6.4.3 0.0.26

Whitelist protection/check for lwm2m (related to 32173, 27582):

0. Whitelist configuration for LWM2M Devices

0.1. whiteListEnabled = true - Whitelist enable for LWM2M

0.2. whiteListEnabledForSensors - isn’t used for LWM2M

0.3. whiteListDisabledForExistingCpe - allows not in whitelist devices to be operable (automatically like it is in whitelist) which were registered after enabling this option

1. new/existing (ANY) device in whitelist: allow all operations. Reg, reg-update fully available.

2. NEW device not in whitelist

2.1. new device not in whitelist lf >= Value 'Whitelist. Lifetime for devices aren’t included (in seconds)'. Device lifecycle: reg, get /3/0, set device status = OFFLINE. (all tasks in PENDING)

2.2. new device not in whitelist lf < Whitelist. Lifetime for devices aren’t included (in seconds): reg, get /3/0, SET /1/0/1=Whitelist. Lifetime for devices aren’t included (in seconds), set device status = OFFLINE. (all tasks in PENDING)

2.3. during the push: tasks won’t be send to device. All tasks in PENDING.

2.4. during reg-update: response FORBIDDEN(4.03). Payload: Device not in white list. Device is removed from system.

3. EXISTING device not in whitelist

3.1 Setting whiteListDisabledForExistingCpe = true - behavior same as p.1 (all are allowed)

3.2 Setting whiteListDisabledForExistingCpe = false - behavior same as p.2 (restrict device)

4. Exceptional situations

4.1. Case: Setting: whiteListDisabledForExistingCpe = true. Steps: register device not in whitelist. Tasks in pending. Set setting: whiteListDisabledForExistingCpe = false. Register device. All tasks are going on to execute.

I.e. state of the whitelist is not historical. There is no requirement to do it.

Version 6.4.3

Latest build: 0.0.48

=== 2025.09.05 - Build 0.0.48

DBA request. Added /*+ result_cache */ to profile_condition select query.

=== 2025.07.14 - Build 0.0.47

Issue ID Description

35975

OneIoT ACS > Start ACS > Error occurred

=== 2025.07.04 - Build 0.0.46

Improved connection request process: added http pool and apache http lib

Added cache to profile operations

=== 2025.05.09 - Build 0.0.45

fixed customer issue: Device Parameter Update Delay

described in issues document in p.8

=== 2025.04.09 - Build 0.0.44

Issue ID Description

35390

OneIoT ACS > Managed license > Devices not automatically deleted

35572

OneIoT ACS > Group Update > Group without "Online devices" > Update group performance optimization

=== 2025.02.19 - Build 0.0.43

Issue ID Description

35266

OneIoT ACS > Device > Session time increased

35297

CPE Admin / CSR > TR-181 > Specific device > Device Update > Delete device > An error occurred

=== 2025.02.09 - Build 0.0.42

Issue ID Description

35247

OneIoT ACS > Device > Parameters > Device tree not updated on high load

=== 2025.01.20 - Build 0.0.41

Issue ID Description

35062

OneIoT ACS > Added smart lock merge protection

=== 2025.01.13 - Build 0.0.40

Issue ID Description

34542

OneIoT ACS > Fixed locks on cpe_parameter merge

34543

OneIoT ACS > Added hikari pool size into acs stats

=== 2025.01.03 - Build 0.0.39

Issue ID Description

34439

ACS > config_custom_data > Set Parameter Attributes > TR181 device > Set Attribute failed in 2nd 0bootstrap event

34544

OneIoT ACS > Moved FTDS and QUARTZDS from wildfly to hikari pool

=== 2024.12.06 - Build 0.0.38

Issue ID Description

34545

OneIoT ACS > Implementation of optimization

=== 2024.11.15 - Build 0.0.37

Issue ID Description

34546

OneIoT ACS > Fixed CPE processing issue when httpSessionLimit=0

34547

OneIoT ACS > Removed connection close on empty message

=== 2024.11.08 - Build 0.0.36

Issue ID Description

34548

OneIoT ACS > Fixed cpe_parameter table lock during merge

34549

OneIoT ACS > Added httpSessionLimit acs configuration parameter

=== 2024.10.08 - Build 0.0.35

Issue ID Description

34550

OneIoT ACS > Implemented solution for the deadlocks

=== 2024.09.13 - Build 0.0.34

Issue ID Description

33698

OneIoT ACS > Device registration > Device tree not saved

=== 2024.06.21 - Build 0.0.33

Issue ID Description

33451

OneIoT ACS > Only TR, MQTT and USP modules

33283

OneIoT ACS > Specific product class > Inform without "6 Connection Request" > Add ability to block processing

=== 2024.06.17 - Build 0.0.32

Issue ID Description

34553

OneIoT ACS > Fix of the duplicates in Device History

=== 2024.06.04 - Build 0.0.31

Issue ID Description

33186

OneIot ACS > CPE With Empty Product Class > CPE Not Processed > High CPE Sessions

33118

OneIoT ACS > Config_custom_data.xml > Notiification not sent post 0 bootstrap for already register device

Empty ProductClass from Inform handling allowed. It is saved to DB with value "EMPTY"

=== 2024.05.17 - Build 0.0.30

Issue ID Description

33234

OneIoT ACS > Fix of the deadlock, which found on Airtel

=== 2024.04.06 - Build 0.0.29

Issue ID Description

32176

OneIoT ACS > Update group > Blocking issue

33235

OneIoT ACS > Removed locks in cache

Added configuration parameter

<!-- Legal values: 0, 1 | Default value: 1 (enabled) | If 1 - ACS will block any UG task processing in case of any UG task is already in sent state -->

<skipUGTaskProcessingIfUGTaskSentExists>1</skipUGTaskProcessingIfUGTaskSentExists>

=== 2024.04.03 - Build 0.0.28

Issue ID Description

32911

ОneIoT ACS > config_custom_data > Set Parameter Attributes > TR-181 > Status Pending > Notification "Off" generated

=== 2024.02.01 - Build 0.0.27

Issue ID Description

33232

OneIoT ACS > Fixed issue with ug_task_to_cpe_task table overloading in case of Profile Events using

33233

OneIoT ACS > Moved DB connections leak fix from 6.4.1

=== 2023.12.15 - Build 0.0.26

Issue ID Description

31152

OneIoT ACS > LWM2M > Bootstrap > PSK > "Bootstrap WRITE mode=INSTANCE" > PUT /0 > Incorrect value sent to the device

Clarification:

Identity: is sent as opaque encoded. I.e. input value: ffff. In wireshark: 66666666

Key: MUST BE HEX previously. Is sent AS IS. I.e. input value: ffff. In wireshark: ffff. Because it is participated in math of cipher operations during DTLS. DTLS is coming to play before CoAP protocol layer parsing.

=== 2023.12.07 - Build 0.0.25

Issue ID Description

32431

OneioT ACS > LWM2M > Profile > FOTA > 5/0/3=3 received > No execute for 5/0/2

=== 2023.12.05 - Build 0.0.24

Issue ID Description

32423

OneIoT ACS > LWM2M > Delete object > Create any task > Task is not sent to device

=== 2023.11.29 - Build 0.0.23

Issue ID Description

32208

OneIoT ACS > Hazelcast nodes separation > "bulk_data.xml" > No sync between nodes

=== 2023.11.29 - Build 0.0.22

Issue ID Description

32295

OneIoT ACS > TR-069 / USP > Bulk data > Monitoring > Exclude parameter from monitor > "Delete object" task is duplicated

=== 2023.11.27 - Build 0.0.21

Issue ID Description

32376

OneIoT ACS > LWM2M > Register device > Device offline > Update request > Device is deleted

32225

OneIoT ACS > LWM2M > Monitor without attributes > Incorrect task with pmin=0 and pmax=0 sent to device

Lwm2m merge 6.4.2 0.0.23 Cbor type extension;

=== 2023.11.22 - Build 0.0.20

Issue ID Description

30753

OneIot ACS > LWM2M > Monitoring > Add parameter > Change "Perform every" > Save > New "Perform every" set only for added parameter

30999

OneIot ACS > LWM2M > "Check monitoring configurations on Notify request"=true > Edit monitor > Change "Perform every" value > NOTIFY REQUEST > Task with new interval value isn’t sent to device

Monitoring attribute update is operation which requires to stop monitoring for parameter and run it again.

On monitoring parameter attribute update the stop tasks will be generated immediately, start - on device visit according configuration properties (reg - always, reg update/notify - optional).

=== 2023.11.20 - Build 0.0.19

Fixed issue with infinite bulk data config update

=== 2023.11.17 - Build 0.0.18

Issue ID Description

32208

OneIoT ACS > Hazelcast nodes separation > "bulk_data.xml" > No sync between nodes

=== 2023.11.16 - Build 0.0.17

Issue ID Description

32322

CPE Admin / CSR > LWM2M > Register device > Device Update > Device is online > Select device > Delete > An error occurred

32292

CPE Admin > LWM2M > Monitoring > Activate > Edit any attribute > Save > Changes not saved

32216

CPE Admin > Monitoring > Edit active monitor > Edit attributes > Save > Attributes are not saved

32225

OneIoT ACS > LWM2M > Monitor without attributes > Incorrect task with pmin=0 and pmax=0 sent to device

32231

OneIoT ACS > ACSWS > updateMonitoring > Active monitor with "Send to="All" > Fault occurred while processing

Requires config files update: hazelcast-client.xml, hazelcast-client-prov.xml

=== 2023.11.10 - Build 0.0.16

Issue ID Description

32212

CPE Admin > Device Update > Resource 19 data is not observed in objects tree

32232

OneIoT ACS > Provision separation mode > MNGMNT cluster > Provision Manager > Add > Provision task is not updated on PROV cluster

=== 2023.11.08 - Build 0.0.15

Issue ID Description

32244

OneIoT ACS > LWM2M > "Firmware process mode" = "notify" > Firmware > Tasks with "Observe=1" for "/5/0/3" and "/5/0/5" resources are not sent

=== 2023.11.07 - Build 0.0.14

Issue ID Description

32254

OneIoT ACS > LWM2M > Bootstrap with any security mode > Bootstrap failed

32252

OneIoT ACS > Provision separation mode > OneIoT ACS started with errors in logs

=== 2023.11.07 - Build 0.0.13

Issue ID Description

32252

OneIoT ACS > Provision separation mode > OneIoT ACS started with errors in logs

=== 2023.11.03 - Build 0.0.12

Issue ID Description

32226

CPE Admin > Device Update > Trace a device > Register device > Incorrect "Start trace" button name is displayed

32232

OneIoT ACS > Provision separation mode > MNGMNT cluster > Provision Manager > Add > Provision task is not updated on PROV cluster

32229

OneIoT ACS > Provision separation > Hazelcast statistics not stored to DB

32208

OneIoT ACS > Hazelcast nodes separation > "bulk_data.xml" > No sync between nodes

Hazelcast config files changed:

files: jvm.options and hz-start.bat

changes:

-Dcom.sun.management.jmxremote.local.only=false

-Djava.rmi.server.hostname=PUBLIC_IP

PUBLIC_IP need to be changed to the IP address

Hazelcast nodes separation.doc updated

=== 2023.11.02 - Build 0.0.11

Issue ID Description

32223

OneIoT ACS > Hazelcast nodes separation > "standalone_*.xml" > No QoE-related datasources > OneIoT ACS is not started

30896

CPE Admin > USP > Group Update / Events / Device profile > Upload > Vendor Configuration File > Task with incorrect URL generated

=== 2023.11.01 - Build 0.0.10

Issue ID Description

32199

OneIoT ACS > Hazelcast statistics not stored to DB

32208

OneIoT ACS > Hazelcast nodes separation > "bulk_data.xml" > Incorrect sync behavior

32201

OneIoT ACS > LWM2M / MQTT / TR-069 > Device Update > Trace a device > Register device > Trace not started

hazelcast-client-prov.xml and hazelcast-client.xml files are updated

=== 2023.11.01 - Build 0.0.9

Issue ID Description

14920

OneIoT ACS > Bulk data > HTTPS > Activate monitor > Incorrect username and password sent to device

=== 2023.10.31 - Build 0.0.8

Merge lwm2m with 6.4.1 0.0.97

=== 2023.10.30 - Build 0.0.7

Issue ID Description

32184

OneIoT ACS > ACS REST API > Method with authorization > Impossible to apply token without "Bearer" prefix

32183

OneIoT ACS > ACS REST API > Swagger > "/login" > Suggestion to change subsequence in example

=== 2023.10.27 - Build 0.0.6

Issue ID Description

14920

OneIoT ACS > Bulk data > HTTPS > Activate monitor > Incorrect username and password sent to device

=== 2023.10.27 - Build 0.0.5

Issue ID Description

30778

OneIoT ACS > ACSWS > LWM2M > Implementation of observation attributes for monitored parameter (may be checked by UI task: 30785)

30782

OneIoT ACS > LWM2M > Monitoring > Implementation of observation attributes for monitored parameter (may be checked by UI task: 30785)

30946

OneIoT ACS > "lwm2m_models/omamodels/oma_v1.0" directory > LWM2M_Device-v1_0.xml > Incorrect file content

30678

OneIoT ACS > LWM2M > Events / Device Profile > UPDATE REQUEST > "CPEEventMonitor" event not generated

31064

OneIoT ACS > LWM2M > 1.1 > "Request queue. Enable queue mode" = "1" > Existing device profile > Register new device > "FETCH" request > Next request is processed

31081

OneIoT ACS > MySQL > LWM2M > 1.1 > Device profile with more than 1 parameter > Register new device > Duplicate "FETCH" request is present

31044

OneIoT ACS > LWM2M > Firmware download task > /5/0/2 executed > "/5/0/3"=3 > Reboot device > Any error code in "5/0/5" > Firmware is stuck

30965

OneIoT ACS > LWM2M 1.0 without predefined content type > "Device default content type" = "APPLICATION_SENML_JSON" > Tasks sent in the SENML-JSON content type

27527

OneIoT ACS > USP > Device Update > USP device that supports file upload > File Upload menu is absent

30880

OneIoT ACS > Device in blacklist > Device Update > SPV > Task is sent to device (lwm2m, any task will be generated but won’t be pushed)

For compatibility with existing (created with previous version software) monitoring configurations - required to run db script. Liquibase contains marge scripts for old-new monitoring;

Changed hint for Settings → LWM2M → Configuration → Common → Device default content type

Merge lwm2m with 6.4.1 0.0.95

Fix device history log (created date was set as event date + delay till server does db transaction, sometimes it may be 10+ min)

=== 2023.10.24 - Build 0.0.4

Issue ID Description

30902

OneIoT ACS > Oracle > LWM2M > Bootstraped device > Settings > LWM2M > Bootstrap > Log > Response is absent

31056

OneIoT ACS > Settings > Protocols > LWM2M > Configuration > Endpoints > Bootstrap Server X509 TLS endpoint port > Wrong port set by default

31103

OneIoT ACS > MySQL > LWM2M > Device bootstraped with X.509 cert > Settings > Protocols > LWM2M > Bootstrap > Log > Log is absent

26336

CPE Admin > Settings > Protocols > LWM2M > Configuration > Network > Parameter that required ACS reboot > Hint > Information about required reboot is absent

27582

OneIoT ACS > LWM2M > Register > whiteListEnabled=1 > Open device > Irrelevant task is sent every second (TODO partially, left check for flags of the whitelist)

34555

OneIoT ACS > Configuration files are changed

34556

OneIoT ACS > Main DB changes

If property change requires the server restart: in hint bottom line it will be marked: * Restart required

New property: Settings → LWM2M → Configuration → Lifecycle → Whitelist. Lifetime for devices aren’t included (in seconds)

Just moved from hardcoded value to configurable one.

Property work described in hint of this property

master merged with 6.4.3_RC

=== 2023.10.12 - Build 0.0.3

Issue ID Description

31131

OneIoT ACS > Subscribe for event ACS REST API > Authentication required

30796

OneIoT ACS > FCC diagnostics > Upload diagnostics > Inform with "8 DIAGNOSTICS COMPLETE" is missing from trace

30744

CSR > Device Update > Diagnostic > Trace or ping > Missing interface

25932

CPE Admin > Group Update > Task failed > Failed task is missing from the chart

14920

OneIoT ACS > Bulk data > HTTPS > Activate monitor > Incorrect username and password sent to device

34557

OneIoT ACS > ACS REST API implementation

Requires DB change

=== 2023.10.11 - Build 0.0.2

Issue ID Description

15033

LWM2M/MQTT Emulation tool > LWM2M > OSCORE > Try to register > Device not registered

34558

OneIoT ACS > Hazelcast provision separation

=== 2023.09.28 - Build 0.0.1

Issue ID Description

12868

OneIoT ACS > USP > Device Update / Device Profile / Group Update > Download file > Irrelevant data stored into external QoE DB

27615

OneIoT ACS > USP > Device Update > File Download > Vendor configuration file > Send > Incorrect task sent to device

27651

OneIoT ACS > USP > Vendor log file > Upload > Incorrect task generated

Add functionality RN here

Branch created to be merged into master when it will became 6.4.3

Version 6.4.2

Latest build: 0.0.23

=== 2023.11.24 - Build 0.0.23

Merge lwm2m with 6.4.1 0.0.97

Fix issue with types (big values for cbor integers caused task fail during the parse);

=== 2023.10.11 - Build 0.0.22

Merge lwm2m with 6.4.1 0.0.90

=== 2023.10.11 - Build 0.0.21

Merge lwm2m with 6.4.1 0.0.89

Change lwm2m configuration properties description and default value (Settings → LWM2M → Configuration → Observation):

-Custom data observation attributes (add description note about '&' usage in xml file)

-Profile observation attributes (replace in default value: & → &)

-Events observation attributes (replace in default value: & → &)

-Monitoring observation attributes (replace in default value: & → &)

Note: if 6.4.2 is already installed and just updated to a new build - the default values must be changed manually for web usage.

=== 2023.09.14 - Build 0.0.20

Merge lwm2m with 6.4.1 0.0.79

=== 2023.09.13 - Build 0.0.19

Merge lwm2m with 6.4.1 0.0.78

=== 2023.09.13 - Build 0.0.18

Merge lwm2m with 6.4.1 0.0.77

=== 2023.09.07 - Build 0.0.17

Issue ID Description

30970

CPE Admin > Device Profile > "Backup" task > File with incorrect name is generated

Merge lwm2m with 6.4.1 0.0.76

=== 2023.09.06 - Build 0.0.16

Issue ID Description

30954

OneIoT ACS > -Dftacs.mode=PROV > No "RedirectCpe" task > Delete device > Device not removed from "cpe_state_prov_server" table

30958

CPE Admin > -Dftacs.mode=PROV > Device Update > "RedirectCpe" task is sent to device > Depricated "CPE" word is used

30925

OneIoT ACS > -Dftacs.mode=PROV > Device with "0 BOOTSTRAP" > Provision task failed > Redirect task is sent to device

Merge lwm2m with 6.4.1 0.0.74

=== 2023.09.05 - Build 0.0.15

Issue ID Description

30954

OneIoT ACS > -Dftacs.mode=PROV > No "RedirectCpe" task > Delete device > Device not removed from "cpe_state_prov_server" table

fixed lock issue in quartz on this query:

SELECT * FROM `QRTZ_LOCKS` WHERE `SCHED_NAME` = ? AND `LOCK_NAME` = ? FOR UPDATE

=== 2023.09.04 - Build 0.0.14

Issue ID Description

30942

OneIoT ACS > ACSWS > getCpeListOnProv > Response is empty

30925

OneIoT ACS > -Dftacs.mode=PROV > Device with "0 BOOTSTRAP" > Provision task failed > Redirect task is sent to device

=== 2023.08.30 - Build 0.0.13

Issue ID Description

30925

OneIoT ACS > -Dftacs.mode=PROV > Device with "0 BOOTSTRAP" > Provision task failed > Redirect task is sent to device

30914

OneIoT ACS > -Dftacs.mode=MNMGNT > Provision Manager > Add > Provision task is not updated on PROV node

=== 2023.08.29 - Build 0.0.12

Issue ID Description

30925

OneIoT ACS > -Dftacs.mode=PROV > Device with "0 BOOTSTRAP" > Provision task failed > Redirect task is sent to device

30914

OneIoT ACS > -Dftacs.mode=MNMGNT > Provision Manager > Add > Provision task is not updated on PROV node

LWM2M. Realization processing of the CID for datapush

=== 2023.08.25 - Build 0.0.11

Merge with 6.4.1 0.0.72 Fix lwm2m enpoints error on server start

=== 2023.08.25 - Build 0.0.10

Issue ID Description

30861

OneIoT ACS > MySQL > LWM2M > Register new device > The Get tasks are not generated

30817

OneIoT ACS > Firmware download > "5/0/2/" executed > Registration request from device > OneIoT ACS does not respond to registration request from device

lwm2m registration rebuilding (JIO stuck)

=== 2023.08.23 - Build 0.0.9

Issue ID Description

30877

OneIoT ACS > TR-069 / USP > Monitoring > New > Monitor-related tasks are not sent

=== 2023.08.22 - Build 0.0.8

Issue ID Description

30895

OneIoT ACS > -Dftacs.mode=PROV > Register new device > SPV task with ACS redirect URL is not sent to device

=== 2023.08.21 - Build 0.0.8

RC

Merged lwm2m with 6.4.1 2023.08.17 0.0.70 Must-have fix. Caches.

=== 2023.08.17 - Build 0.0.7

Merged lwm2m with 6.4.1 2023.08.17 0.0.68

=== 2023.08.17 - Build 0.0.6

Issue ID Description

30834

OneIoT ACS > LWM2M v1.0 > Monitoring > Several parameters > Task sent as composite

30878

CPE Admin > Monitoring > Edit running monitor > Save > An error occurs

Merged lwm2m with 6.4.1 2023.08.16 0.0.67

=== 2023.08.14 - Build 0.0.5

Issue ID Description

29664

CPE Admin / CSR > Device Update > Device in blacklist > Device Settings > Get current > An unexpected occurrence happened

Merged lwm2m with 6.4.1 2023.08.11 0.0.65

=== 2023.08.10 - Build 0.0.4

Issue ID Description

30768

OneIoT ACS > LWM2M > Firmware download > Update result "8" > Incorect error text

30861

OneIoT ACS > MySQL > LWM2M > Register new device > The Get tasks are not generated

30862

OneIoT ACS > LWM2M > Firmware > POST on "/5/0/2" > Registration request > Excessive request is generated

30778

OneIoT ACS > ACSWS > LWM2M > Implementation of observation attributes for monitored parameter

30780

OneIoT ACS > Settings > LWM2M > Configuration > Observation > Change attribute functionality

30781

OneIoT ACS > LWM2M > config_custom_data.xml > Implementation of attributes for parameter

30782

OneIoT ACS > LWM2M > Monitoring > Implementation of observation attributes for monitored parameter

Changed java type of the cpe_parameter.id. Integer → Long

Requires ACS DB change

Merged lwm2m with 6.4.1 2023.08.08 0.0.61

Requires DB change (created tables qoe_monitoring_parameter_attribute, qoe_monitoring_task)

Fix cache sync (lwm2m load test fail for some devices, skype 30798)

=== 2023.08.07 - Build 0.0.3

Provision separation server functionality added

1. New ACS start parameter -Dftacs.mode=ALL|PROV|MNGMNT If absent, value is ALL - standard (old) behaviour

2. New ACS config parameter added: redirectAcsURL: Legal values: URL ([HTTP]://[IP]:[PORT]/[PATH]) for redirecting CPE to management ACS | Default value: empty (disabled) | Working only in -Dftacs.mode=PROV

3. New table added: cpe_state_prov_server Required only for PROV mode

4. New /ACSWebServiceAdditional methods added: moveCpeToManagement, getCpeListOnProv Used only for PROV mode

Provision ACS configuration:

1. Table cpe_state_prov_server should be present in DB

2. -Dftacs.mode=PROV

3. Hazelcast instance with the next configuration should be running:

<cluster-name>provision</cluster-name>

<member-server-socket-endpoint-config><port>5721</port>

  1. acs_configuration.xml parameter redirectAcsURL should be set

Management ACS configuration:

1. -Dftacs.mode=MNGMNT

2. Two hazelcast instances should be running. Cluster names: dev, provision

3. Hazelcast 2nd instance configuration changes:

  1. -Dcom.sun.management.jmxremote.port=9210 (hz-start)

  2. hazelcast.xml

<cluster-name>provision</cluster-name>
<member-server-socket-endpoint-config><port>5721</port>
<client-server-socket-endpoint-config><port>5702</port>
<rest-server-socket-endpoint-config><port auto-increment="false">8092</port>

Requires ACS DB change

=== 2023.08.03 - Build 0.0.2

Merged lwm2m with 6.4.1 2023.08.03 0.0.59

=== 2023.07.31 - Build 0.0.1

Issue ID Description

29663

OneIoT ACS > LWM2M > overwriteProvisionParameters=1 > FTSetDeviceParameters > Duplicated tasks created

30683

OneIoT ACS > USP > Events / Device Profile > Boot! > Reboot device > "cpeEventMonitor" event isn’t generated

27475

OneIoT ACS > USP > Group Update > Upload file task > Task is not sent to device

30704

OneIoT ACS > MQTT > Monitor > All (new and existing) > New device > Device is not monitored

30680

OneIoT ACS > LWM2M > Deregister > "UNREGISTRATION REQUEST" event not generated

30679

OneIoT ACS > LWM2M > Events / Device Profile > 4 VALUE CHANGE / NOTIFY REQUEST > "CPEEventMonitor" event isn’t generated

30678

OneIoT ACS > LWM2M > Events / Device Profile > UPDATE REQUEST > "CPEEventMonitor" event not generated

30677

OneIoT ACS > LWM2M > Events / Device Profile > GREATER / GREATER_EQUAL / LESS / LESS_EQUAL > "cpeParameterMonitor" event isn’t generated

26399

OneIoT ACS > LWM2M > Device Update > SPV failed > GPV task is absent

26404

OneIoT ACS > USP > Register device > "get_supported_dm" request doesn’t contain "first_level_only" and "return_params" fields

30738

OneIoT ACS > USP > Connect group of devices with new model > Not all devices are registered

27631

OneIoT ACS > LWM2M > "Define CoAP token length by device"="1" > Device with 0-byte token length > The ACS sends incorrect token length

27582

OneIoT ACS > LWM2M > Register > whiteListEnabled=1 > Open device > Irrelevant task is sent every second

27606

OneIoT ACS > LWM2M > PSK > Register device with incorrect PSK ID/Key > "1014 - cpe login failed" hardcoded event is not generated

26384

OneIoT ACS > LWM2M > Group Update > 3k devices > File Download > Firmware > PULL > CoAP > Task failed for several devices (emulator ver. 1.7.174+ required)

30717

CPE Admin > Device Update > Software Manager > Install > Add "Manual UUID" check-box and "UUID" input field

26199

QoE GUI > Big amount of devices > Stop monitor > Stop monitoring tasks are not generated for part of devices

Merged lwm2m with 6.4.1 2023.07.26 0.0.55

Lwm2m firmware processor optimization (remove duplication /5/0 firmware resource sync and /3/0/3 version check in cases when device is doing reboot in final steps of the process

=== 2023.06.30 - Build 25934

Issue ID Description

30684

OneIoT ACS > LWM2M > FOTA > Group of devices > Correct Update Result > GET on /3/0/3 is missing for part of devices

OneIoT ACS > LWM2M > "config_custom_data.xml" > Tasks are sent continuously

=== 2023.06.29 - Build 6.4.1

branched, master now 6.4.2

Version 6.4.1

Latest build: 0.0.135

=== 2025.07.01 - Build 0.0.135

Issue ID Description

35784

OneIoT ACS > JIO > Production nodes down

Requires Full restart

=== 2025.05.14 - Build 0.0.134

Issue ID Description

35529

OneIoT ACS > LWM2M 1.1 > Register > Tasks on declared objects failed

=== 2025.03.20 - Build 0.0.133

Issue ID Description

34360

OneIoT ACS > JIO > Security findings

=== 2024.12.12 - Build 0.0.132

Issue ID Description

35734

OneIoT ACS > Enabling near-cache configuration

=== 2024.05.15 - Build 0.0.131

Added hazelcast-client.xml to the JBOSS config dir

Functionality described in "Hazelcast nodes separation.doc"

=== 2024.05.13 - Build 0.0.130

Fix NPE for resource registry (found on customer side)

=== 2024.04.08 - Build 0.0.129

Issue ID Description

32947

One IoT > LWM2M > Payload is not parsed

=== 2024.02.06 - Build 0.0.128

LWM2M fixed pending task update/delete deadlock

LWM2M added thread leak detection and interrupting stuck threads

=== 2024.02.01 - Build 0.0.127

LWM2M if existing cpe comes with updated FW version and there is FW task in sent state ⇒ move task to completed

=== 2024.01.29 - Build 0.0.126

californium_threadsCount recommended value is 100 for 16 core server

recommended db pool size for FTDS: 500

Parameter saving bulk thread fixed. Now DB is not overloaded

Overload checker (from prev build) is disabled. Need to be designed properly

LWM2M resources processing during cpe registration refactoring: heavy operations with parameter model cpe initialization moved to the application start

LWM2M metrics per request added. New log file metrics.log.

LM2M logging changed to the jio requirements:

Device Registration – Success

Device Registration – Failure (with reason/error code+text)

FW upgrade - Success

FW upgrade – Failure (with reason/error code+text)

Bootstrap (optional) - Success

Bootstrap (optional) – Failure (with reason/error code+text)

Complete FOTA upgrade cycle with (Success/Failure/ error code).

Changes in logback.xml:

<appender name="METRICS_LOG" class="ch.qos.logback.core.rolling.RollingFileAppender">

<file>${jboss.server.log.dir}/metrics.log</file>

<encoder>

<charset>UTF-8</charset>

<outputPatternAsHeader>true</outputPatternAsHeader>

<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5p [%c{26}] \(%t\) %msg%n</pattern>

</encoder>

<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">

<fileNamePattern>${jboss.server.log.dir}/metrics_%d{dd-MM-yyyy}.log.zip</fileNamePattern>

</rollingPolicy>

</appender>

<logger name="com.friendly.lwm2m.core.statistics.MetricsService" level="INFO" additivity="false" >

<appender-ref ref="METRICS_LOG" />

</logger>

<logger name="com.friendly.lwm2m.core.service.cpe.repository.BulkSQLProcessorLWM2MCpeResource" level="INFO" additivity="false" >

<appender-ref ref="BULK_PROCESS_LOG" />

</logger>

<logger name="com.friendly.lwm2m" level="INFO"/>

Requires Hazelcast restart

=== 2024.01.25 - Build 0.0.125_m3

LWM2M optmizations

Added threshold for rejecting lwm2m registration requests in case of cpu or db bool is overloaded

acs_configuration.xml changes:

<!-- Legal values: 0 - 10000 | Default value: 0 (disabled) | Max allowed active connections count. If > 0 ACS will block new session with device creation -->

<dbThreshold>0</dbThreshold>

logback.xml changes:

<appender name="BLOCKED_CPE_LOG" class="ch.qos.logback.core.rolling.RollingFileAppender">

<file>${jboss.server.log.dir}/blocked_cpe.log</file>

<encoder>

<charset>UTF-8</charset>

<outputPatternAsHeader>true</outputPatternAsHeader>

<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5p [%c{26}] \(%t\) %msg%n</pattern>

</encoder>

<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">

<fileNamePattern>${jboss.server.log.dir}/blocked_cpe_%d{dd-MM-yyyy}.log.zip</fileNamePattern>

</rollingPolicy>

</appender>

<logger name="com.friendly.dm.core.utils.OverloadChecker" level="WARN" additivity="false" >

<appender-ref ref="BLOCKED_CPE_LOG" />

</logger>

=== 2024.01.24 - Build 0.0.125_m2

Lwm2m optimizations;

=== 2024.01.20 - Build 0.0.125_m

Refactoring custom database connections mechanism;

Refactoring transaction mechanism;

Refactoring bulk processors' mechanism;

=== 2024.01.18 - Build 0.0.124

Hikari datasource https://github.com/brettwooldridge/HikariCP/tree/dev

Work instructions:

1. Works without total configuration changes. Just add: /standalone/configuration/ftacs_hikari.properties

2. It replaces wildfly datasource FTDS. I.e. configuration of the DB FTDS will be only via ftacs_hikari.properties. FTDS may be removed from standalone totally

3. If file ftacs_hikari.properties doesn’t exist - system will try to find FTDS in standalone as it is before

4. In log datasource will have init record: "==================== FTACS DS Wildfly|Hikari datasource configured ===================="

Wilfly|Hikari - Hikari it is new one. Wildfly - old way.

5. ftacs_hikari.properties sample content:

poolName=FTDS

driverClassName=com.mysql.cj.jdbc.Driver

jdbcUrl=jdbc:mysql://localhost:3306/ftacs

username=ftacs

password=ftacs

registerMbeans=false

maximumPoolSize=512

minimumIdle=32

idleTimeout=60000

connectionTimeout=300000

maxLifetime=600000

dataSource.cachePrepStmts=true

dataSource.prepStmtCacheSize=256

dataSource.prepStmtCacheSqlLimit=2048

dataSource.useServerPrepStmts=true

=== 2024.01.16 - Build 0.0.123

LWM2M endpoints start only after context initialization finished

LWM2M resources file loading only if haven’t been loaded or modified

Fixed cpe tasks processing

=== 2024.01.15 - Build 0.0.122

Queries optimization: update cpe, delete from cpe_parameter, update cpe_profile

=== 2024.01.15 - Build 0.0.121

Removed cache by value search

=== 2024.01.14 - Build 0.0.120

LWM2M fix tokens holder caches (Jio’s stucked prod);

=== 2024.01.12 - Build 0.0.119

LWM2M Fix endpoints initialization before FTBeanFactory (ft services not available for lwm2m endpoints before initialization bug);

LWM2M Beautify cluster rest api call logging if node isn’t started;

LWM2M Fix bug to remove cpe on expired lifetime reg-update;

=== 2023.12.25 - Build 0.0.118

Fixed cpe supported methods cache

Fixed cpe_resources processing in case of multi instance coap path

Fixed nullpointer during rejecting the task

=== 2023.12.11 - Build 0.0.117

Fixed cpe_parameter query for Oracle

=== 2023.12.07 - Build 0.0.116

Issue ID Description

32420

OneIoT ACS > JIO > SIT > FOTA failure

=== 2023.11.24 - Build 0.0.115

LWM2M: fixed lwm2m_cpe_resource sequence processing

=== 2023.11.21 - Build 0.0.114

LWM2M: fixed cpe on lifetime handling

=== 2023.11.21 - Build 0.0.113

LWM2M: Fixed existing cpe address set

=== 2023.11.20 - Build 0.0.112

LWM2M: fixed caches clearing

=== 2023.11.20 - Build 0.0.111

LWM2M: fixed tokens issue

LWM2M: sql optimizations

LWM2M: statistics collection disabling by config flag

LWM2M: DB connections leak fix

=== 2023.11.16 - Build 0.0.110

LWM2M: cpe_parameter and lwm2m_cpe_resource optimizations

LWM2M: oracle fixes

LWM2M: moved the most of operations with lwm2m_cpe_resources to the cache

=== 2023.11.13 - Build 0.0.109

Lwm2m optimization for cpe_parameter queries;

=== 2023.11.13 - Build 0.0.108

Lwm2m fix issue with management parameters;

=== 2023.11.13 - Build 0.0.107

Fixed lwm2m methods saving

=== 2023.11.13 - Build 0.0.106

Optimize the lwm2m resource/parameters queries number to db;

=== 2023.11.13 - Build 0.0.105

Added caches for manufacturer, product_class, product_class_group

Added cache for LWM2M security

Added stateless sql connector for bulk insert operations

Refactor in lwm2m queries count: cpe_pending_task, monitoring and config_custom_data

Requires hazelcast service start param: -Dhz.jet.enabled=true

=== 2023.11.10 - Build 0.0.104

Merge 32212 from master (lwm2m opaque parsing);

Lwm2m resources optimization;

Lwm2m configuration improvements. Californium properties moved to config:

-MID tracker type

-MID tracker group count

-The maximum latency assumed for message transmission (ms)

-The default exchange lifetime (ms)

-The default NON-lifetime (ms)

=== 2023.11.10 - Build 0.0.103

Lwm2m optimizations (resources/parameters/remove auxiliar call getCpeResourcesNameIdPathForNameIds);

=== 2023.11.10 - Build 0.0.102

Firmware cache obj optimization;

LWM2M resources requests optimization;

LWM2M queries optimizations. Queries inside loop moved outside in bulk mode

Fixed issue with multithreading resource processing in lwm2m

=== 2023.11.09 - Build 0.0.101

Applied a set of optimizations in LWM2M registration and fota flow

Requires DB change

Recommendations: change firmware upgrade

LWM2M.Configuration.Firmware.notify_pmax/LWM2M.Configuration.Firmware.notify_pmin

to the corresponding values based on the time with is needed for firmware file download

LWM2M.Configuration.Network.californium_threadsCount - need to be set to the expected concurrent request count but not more than 2K

FTDS max-pool size need to be set as concurrent request count + 20%

Requires DB change

=== 2023.11.02 - Build 0.0.100

Fixed NoClassDefFound exception in hazelcast

=== 2023.11.01 - Build 0.0.99

Added lwm token class to the hazel config

=== 2023.11.01 - Build 0.0.98

Lwm2m token storage optimization;

=== 2023.10.31 - Build 0.0.97

Issue ID Description

31158

OneIoT > ARAD >Device update >New device model registration issue (very big device lifetime)

Fix TR069 issue with cached param type (edit.jsp);

Fix lwm2m behavior with busy-device-address. Forbidden response will by only if device queue is not waiting for task/request and will be empty (not queued requests);

Add new metric to acsstat:

Address duplicates. Overridden (node: %s) - count of the overridden device queues. Registration req for online device for busy address and not busy queue (queue doesn’t wait for response, task and hasn’t queued requests)

=== 2023.10.30 - Build 0.0.96

Fix issue with device history date. Delayed db operation always saves record with initial date + delay time.

Fix issue with attempt of the device registration with already busy host:port. If host:port is busy by the online device - server returns error on registration request.

Fix issue with token storage memory overloading;

Added new metrics in acsstats:

Address duplicates. Forbidden (node: 192.168.99.118) 0 - count of the forbidden requests. Cpe tries to register with already busy ip:port and other endpoint

Address duplicates. Registrations (node: 192.168.99.118) 0 - detected registration request for not finished registration for previous one for that address;

Address duplicates. Removed (node: 192.168.99.118) 0 - device registered by already solved address. But device is not online. Clear cache/queue to allow register new one.

Tokens in use (node: 192.168.99.118) 2 - current number of the tokens in storage;

=== 2023.10.26 - Build 0.0.95

Lwm2m token storage improvements (load related)

=== 2023.10.23 - Build 0.0.94

Adoption for merge with 6.4.3. Just for more easy merge next code changes;

=== 2023.10.23 - Build 0.0.93

Cache and trace improvements;

=== 2023.10.17 - Build 0.0.92

Issue ID Description

31119

OneIoT ACS > LWM2M > "Firmware process mode" = "notify" > Firmware > Executing "5/0/2" > "5/0/3" = "3" > Reboot > Register > Requests with "Observe=1" for "5/0/5" and "5/0/3" are present

=== 2023.10.05 - Build 0.0.91

Issue ID Description

31105

OneIoT ACS > LWM2M > "Update account info firmware version automatically"="true" > Device Update > File Download > Firmware task > Task completed without device reboot > "Zip" field is not updated

=== 2023.10.05 - Build 0.0.90

Issue ID Description

31105

OneIoT ACS > LWM2M > "Update account info firmware version automatically"="true" > Device Update > File Download > Firmware task > Task completed without device reboot > "Zip" field is not updated

LWM2M fix fota stucks during the load (~10 from 1k devices tasks are stucked in pending state, numbers are not persistent);

=== 2023.10.05 - Build 0.0.89

Removed the device entity pre-saving (I.E. one cache excluded).

New configuration properties (it is not new, but moved to configuration from hardcode):

Settings → LWM2M → Configuration → Network → The default timeout after which a peer is considered inactive (sec) (library low-level configuration. Server restart required. description in hint)

Settings → LWM2M → Configuration → Network → The default number of active peers to support (library low-level configuration. Server restart required. description in hint)

Settings → LWM2M → Configuration → Network → Request. Acknowledgment timeout scale --- this one changes behavior. Before it default value was eq 1, eq each retransmission attempt was directly in one timeout. For current value timeout will be multiplied by 2 for server offloading. (library low-level configuration. Server restart required)

Improved acsstats. For the lwm2m protocol it will look like this:

Device finished registrations (node: 192.168.99.118) 592 - number of the devices registration finished (server is going to run tasks)

Device queues current (node: 192.168.99.118) 897 - current size of the device queues

Device queues de-registrations (node: 192.168.99.118) 0 - number of the delete requests (from device)

Device queues registrations (node: 192.168.99.118) 928 - number of the registration requests (from device)

Devices in cache 897 - number of the cached devices

Devices in registration 79 - number of the preliminary held device registration-related data (like pre-saved devices, it waits for /3/0 response or timeout).

Registered CId/s 0 - number of the CIds of the devices (actual for PSK mode)

Sessions in progress. Firmware 482 - number of the currently running firmware sessions

Sessions in progress. Software 0 - number of the currently running software sessions

Transactions in progress 0 - number of the server virtual transactions currently running

=== 2023.10.03 - Build 0.0.88

Lwm2m cpe parameters/resources lock;

Lwm2m cpe resources locks;

Renaming property (see 0.0.85): "Update ZIP as firmware version automatically" → "Update account info firmware version automatically"

=== 2023.09.29 - Build 0.0.87

Lwm2m thread optimizations;

=== 2023.09.27 - Build 0.0.86

Issue ID Description

31070

OneIoT ACS > LWM2M > "Update ZIP as firmware version automatically"="true" > Device with /3/0/3 resource > "Zip" filed is empty

=== 2023.09.27 - Build 0.0.85

For new functionality in 0.0.84 added configuration property:

Settings → LWM2M → Configuration → Common → Update ZIP as firmware version automatically (default: disabled)

=== 2023.09.26 - Build 0.0.84

Issue ID Description

31066

OneIoT ACS > LWM2M > Firmware download task > /5/0/2/ executed > Reboot device > Firmware download task is stuck

Added new functionality to avoid system load via monitoring of the /3/0/3 resources (cust_device1.zip):

  • if device sends /3/0/3 resource it will automatically set as ZIP in account info

  • Attention: don’t use config_cust_data.xml or profile with this resource /3/0/3 to avoid double-observation;

=== 2023.09.20 - Build 0.0.83

Issue ID Description

30944

OneIoT ACS > LWM2M > Bootstrap with any security mode > Bootstrap failed

Fix thread leaking;

=== 2023.09.19 - Build 0.0.82

Fix thread leaking;

=== 2023.09.18 - Build 0.0.81

Fix thread leaking;

=== 2023.09.15 - Build 0.0.80

Issue ID Description

31020

OneIoT ACS > PENDING_INACTIVE > Device update > LWM2M > Last connection older than "Inactivity. Device online timeout" > Device status not changed

31024

OneIoT ACS > LWM2M > "config_custom_data.xml" > Profile with condition > New device > Condition reached > Profile task is not generated

=== 2023.09.14 - Build 0.0.79

Issue ID Description

31016

OneIoT ACS > LWM2M > Bootstrap > PSK > PUT /0/*/3 > Incorrect value sent to the device

=== 2023.09.13 - Build 0.0.78

Fix issue with multiple devices status change (wrong check for sql query, as result system stucked);

=== 2023.09.13 - Build 0.0.77

LWM2M Configuration changes:

  • Renamed: Device online timeout (in seconds) to Inactivity. Device online timeout (in seconds)

  • Added: Inactivity. Device minimal lifetime for online check (in seconds) see property description. It’s additional filter for inactivity timer target devices. No sense to do device inactive if lifetime is less than 1 hour for ex.

Recommendation to use (to make devices inactive if lifetime gt or eq 1 hour to offload high load system):

  • Inactivity. Device online timeout (in seconds) = 3600 (1hr).

  • Inactivity. Device minimal lifetime for online check (in seconds) = 3600 (1hr)

Rebuilt lwm2m cache mechanisms, added cache clearing on device state changing to offline/inactive;

Reduced lwm2m device entity cache size from 1.8kB to 1.6kB;

Added lwm2m device resources clearing on removing device from cache;

Added acsstats for lwm2m http://localhost:8080/acsstats → Protocol statistics: → LWM2M Protocol:

  • Pre-saved devices (Waiting /3/0 response) xxx

  • Firmware sessions in progress xxx

  • Software sessions in progress xxx

  • Device transactions in progress xxx

  • Devices in cache xxx

  • Available CId/s xxx

  • Device queues (Per-node). Node: xxx xxx

=== 2023.09.07 - Build 0.0.76

Issue ID Description

30944

OneIoT ACS > LWM2M > Bootstrap with any security mode > Bootstrap failed

=== 2023.09.05 - Build 0.0.75

fixed lock issue in quartz on this query:

SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = ? AND LOCK_NAME = ? FOR UPDATE

=== 2023.09.04 - Build 0.0.74

Issue ID Description

30862

OneIoT ACS > LWM2M > Firmware > POST on "/5/0/2" > Registration request > Excessive request is generated

30944

OneIoT ACS > LWM2M > Bootstrap with any security mode > Bootstrap failed

30930

OneIoT ACS > Firmware download > "5/0/2/" executed > Registration request from device > Firmware task is stuck

30898

OneIoT ACS > LWM2M > Profile with condition by firmware version > Register new device > Device rebooted after request on "/5/0/2" > All profile tasks are deleted

=== 2023.08.31 - Build 0.0.73

Fix wrong check for profile download tasks; Jio.

=== 2023.08.25 - Build 0.0.72

Fix ipv6 on server start.

=== 2023.08.25 - Build 0.0.71

Issue ID Description

30898

OneIoT ACS > LWM2M > Profile with condition by firmware version > Register new device > Device rebooted after request on "/5/0/2" > All profile tasks are deleted

lwm2m device registration rebuild (6.4.2 0.0.10);

=== 2023.08.19 - Build 0.0.70

Issue ID Description

30881

OneIoT ACS > LWM2M > Existing device profile > Register new device > GET /3/0 > Response > Rigistration request > Profile task are duplicated (fix for profile: DownloadProfile, SetParameterValuesProfile, SetParameterNotificationProfile tasks)

=== 2023.08.18 - Build 0.0.69

Issue ID Description

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated (issue with cpeparametername cache) (essential changes for caches for concurrency usage)

=== 2023.08.17 - Build 0.0.68

Issue ID Description

30881

OneIoT ACS > LWM2M > Existing device profile > Register new device > GET /3/0 > Response > Rigistration request > Profile task are duplicated (partially. only for custom_config_data)

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated (issue with cpeparametername cache)

=== 2023.08.16 - Build 0.0.67

Issue ID Description

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated

=== 2023.08.14 - Build 0.0.66

Issue ID Description

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated

=== 2023.08.14 - Build 0.0.65

Issue ID Description

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated

=== 2023.08.11 - Build 0.0.64

Issue ID Description

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated

=== 2023.08.11 - Build 0.0.63

Issue ID Description

29664

CPE Admin / CSR > Device Update > Device in blacklist > Device Settings > Get current > An unexpected occurrence happened

30869

OneIoT ACS > LWM2M > Large volume of registration > Registration request > GET tasks for supported objects are not generated

LWM2M fix concurrent device registration. Trace and pre-saving concurrency exceptions.

LWM2M fix device offline on concurrency environment (offline status tracker time has wrong select conditions)

=== 2023.08.10 - Build 0.0.62

Fix cache sync (lwm2m load test fail for some devices, skype 30798)

=== 2023.08.08 - Build 0.0.61

Issue ID Description

30819

OneIoT ACS > MySQL > LWM2M > config_custom_data.xml > Device profile with condition on monitored resource > Observation "On" task is duplicated

30809

OneIoT ACS > Incomplete Observe Tasks are marked as Complete and are not resent

=== 2023.08.07 - Build 0.0.60

Issue ID Description

26199

QoE GUI > Big amount of devices > Stop monitor > Stop monitoring tasks are not generated for part of device

=== 2023.08.03 - Build 0.0.59

Issue ID Description

30816

OneIoT ACS > MySQL > CPE Admin > Device Update > Open any LWM2M device > Delete > OK > An error occurred

=== 2023.08.02 - Build 0.0.58

Issue ID Description

30824

OneIoT ACS > Device lifetime is incorrect

=== 2023.08.01 - Build 0.0.57

Issue ID Description

30819

OneIoT ACS > MySQL > LWM2M > config_custom_data.xml > Device profile with condition on monitored resource > Observation "On" task is duplicated

30816

OneIoT ACS > MySQL > CPE Admin > Device Update > Open any LWM2M device > Delete > OK > An error occurred

30809

OneIoT ACS > Incomplete Observe Tasks are marked as Complete and are not resent

=== 2023.08.01 - Build 0.0.56

Issue ID Description

26199

QoE GUI > Big amount of devices > Stop monitor > Stop monitoring tasks are not generated for part of device

=== 2023.07.27 - Build 0.0.55

Lwm2m firmware optimizations (jio);

=== 2023.07.27 - Build 0.0.54

Issue ID Description

26199

QoE GUI > Big amount of devices > Stop monitor > Stop monitoring tasks are not generated for part of devices

=== 2023.07.26 - Build 0.0.53

Issue ID Description

30803

LWM2M Stucked tasks (Jio pre-prod issue)

=== 2023.07.21 - Build 0.0.52

Issue ID Description

30788

OneIoT > LWM2M > Device with tasks in sent state > Delete > Register > An error in "server.log" file

=== 2023.07.18 - Build 0.0.51

Issue ID Description

30764

LWM2M Duplicated firmware/software

=== 2023.07.13 - Build 0.0.50

Issue ID Description

29660

OneIoT ACS > TR-069 > Device profile > "Backup" check-box > Task with incorrect URL is generated

Released

=== 2023.07.12 - Build 0.0.49

Issue ID Description

29660

OneIoT ACS > TR-069 > Device profile > "Backup" check-box > Task with incorrect URL is generated

=== 2023.07.11 - Build 0.0.48

Issue ID Description

30730

OneIoT ACS > JIO > Preproduction > FOTA failure (test possible only with customer specific device)

=== 2023.07.07 - Build 0.0.47

Issue ID Description

29660

OneIoT ACS > TR-069 > Device profile > "Backup" check-box > Task with incorrect URL is generated

=== 2023.07.07 - Build 0.0.46

Issue ID Description

29660

OneIoT ACS > TR-069 > Device profile > "Backup" check-box > Task with incorrect URL is generated

=== 2023.07.05 - Build 0.0.45

Issue ID Description

27648

OneIoT ACS > LWM2M > Data-links for objects with high number are read as negative numbers

=== 2023.07.04 - Build 0.0.44

Issue ID Description

30703

OneIoT ACS > LWM2M > Bootstrap > Device is not bootstraped

=== 2023.06.30 - Build 0.0.43

Issue ID Description

25934

OneIoT ACS > LWM2M > "config_custom_data.xml" > Tasks are sent continuously

30684

OneIoT ACS > LWM2M > FOTA > Group of devices > Correct Update Result > GET on /3/0/3 is missing for part of devices

=== 2023.06.27 - Build 0.0.42

Issue ID Description

29660

OneIoT ACS > TR-069 > Device profile > "Backup" check-box > Task with incorrect URL is generated

27443

OneIoT ACS > LWM2M > "Device online timeout" more than 0 > Online timeout is reached > Device status not changed

25934

OneIoT ACS > LWM2M > "config_custom_data.xml" > Tasks are sent continuously

27604

OneIoT ACS > LWM2M > Registered device > "config_custom_data.xml" > Tasks are duplicated

=== 2023.06.21 - Build 0.0.41

Issue ID Description

27555

OneIoT ACS > LWM2M 1.1 > Device Update > Advanced View > SPV for at least two parameters > GPV task is absent

27607

OneIoT ACS > LWM2M > Enable verification by version=false > Send firmware > "GET /3/0/3" request is absent

27576

OneIoT ACS > LWM2M > Events > Custom group > Parameters > Observation "On" task generated each Update request

27502

OneIoT ACS > Device Update > Software Manager > Install / Uninstall > Add UUID value generation

25934

OneIoT ACS > LWM2M > "config_custom_data.xml" > Tasks are sent continuously

27600

OneIoT ACS > LWM2M > Device with non 8-bytes length token > ACS send only 8-bytes length token (added token length for blockwise)

27604

OneIoT ACS > LWM2M > Registered device > "config_custom_data.xml" > Tasks are duplicated

27439

OneIoT ACS > Settings > Protocols > LWM2M > Configuration > Software > "CoAP Server IP" > Incorrect default value is used

27630

OneIoT ACS > Oracle cluster > Start OneIoT ACS > ACS starts with exception

27578

OneIoT ACS > Blacklist > New / existing device > Register > Device is registered and operable

=== 2023.06.12 - Build 0.0.40

Issue ID Description

27571

OneIoT ACS > LWM2M > Monitoring > Start monitor > Update request > Observation "On" task duplicated

27570

OneIoT ACS > LWM2M > Monitoring > Stop / Delete monitor > Observation "Off" task isn’t generated

27565

OneIoT ACS > LWM2M / USP / MQTT > License > Registered > Limit reached > Try to register existing device > Device is not registered

25884

OneIoT ACS > USP > Moniotring > GPV task related to monitor is absent

27590

OneIoT ACS > Settings > useMultipleSetTasks > Setting affects all devices of protocols

26152

CPE Admin > Settings > File server > Add authentication details > Existing task needs rebuilding

27532

CPE Admin > Device profile > Edit profile > Save > Profile reset to default value

27579

OneIoT ACS > Group Update > "Threshold" > Incorrect final update status

27551

OneIoT ACS > TR-181 > "config_custom_data.xml" > Tasks are sent continuously

27600

OneIoT ACS > LWM2M > Device with non 8-bytes length token > ACS send only 8-bytes length token (see comment in btnet)

27613

OneIoT ACS > Update with "VALUE_CHANGE" condition > Irrelevant condition > Update ignores condition

Merged with 6.3 0.0.101 (token length)

Requires acs_configuration.xml change

=== 2023.05.31 - Build 0.0.39

Issue ID Description

27551

OneIoT ACS > TR-181 > "config_custom_data.xml" > Tasks are sent continuously

27544

OneIoT ACS > Cluster > "config_custom_data.xml" > Any changes > Open file on another node > Some data is duplicated

27506

OneIoT ACS > TR-069 > Device Diagnostics > 8 DIAGNOSTIC COMPLETE inform with diagnostic result > Diagnostics result is not saved

27502

OneIoT ACS > Device Update > Software Manager > Install/Uninstall > Add UUID value generation

26414

OneIoT ACS > TR-069 > Device Update > Diagnostics > Any diagnostics > 8 DIAGNOSTIC COMPLETE > GPV task with diagnostic results request is absent

Requires DB change

=== 2023.05.30 - Build 0.0.38

Issue ID Description

27427

OneIoT ACS > LWM2M > File download > Software package > Device not responding > Registration update > Task is not resent to the device

27448

СPE Admin > Settings > Protocols > LWM2M > Resources > Resource with "Unsigned Integer" > Incorrect "String" type is displayed

26361

OneIoT ACS > Settings > Protocols > LWM2M > Configuration > Common > Device default content type > "Without content type" is absent

27518

OneIoT ACS > LWM2M > Multi-instance write/read operation issues

27525

OneIoT ACS > LWM2M > Device Update > Advanced View > SPV for instance of multiple instance resource > GPV task is absent

27555

OneIoT ACS > LWM2M 1.1 > Device Update > Advanced View > SPV for at least two parameters > GPV task is absent

=== 2023.04.26 - Build 0.0.37

Issue ID Description

26321

OneIoT ACS > LWM2M > Device Profile > Re-register new device > Excessive GPV task is generated

27421

OneIoT ACS > LWM2M > Software download > PULL+CoAP > Task failed

26420

OneIoT ACS > LWM2M > Software manager > "Enable verification by version" = true > /9/*/1 resource is not provided > Version verification is not ignored

26419

OneIoT ACS > LWM2M > Software manager > "Enable verification by version" = true > File with empty version > Task transferred to "Failed" state

27427

OneIoT ACS > LWM2M > File download > Software package > Device not responding > Registration update > Task is not resent to the device

Merged last changes lwm2m with 6.3 0.0.99

Implemented Akamai CDN integration (see the doc with the feature description)

=== 2023.04.13 - Build 0.0.36

Issue ID Description

26243

OneIoT ACS > LWM2M > "Delete resource before bootstrap"="true" > Resources from "Additional instances" section are not deleted before "WRITE" operations

25828

OneIoT ACS > LWM2M > File server with authorization > HTTP / HTTPs > Software update > Download task is failed

25782

OneIoT ACS > LWM2M > Settings > Configuration > Software > Software content delivery method is absent

26295

CPE Admin > Settings > Protocols > LWM2M > Configuration > Bootstrap > Any parameter > Hint > Default parameter is absent

21523

CPE Admin / CSR > "Use discovery for tree root"="true" > Device Update > Advanced View > Root > Get current > Device Activity > Irrelevant task is displayed

26318

OneIoT ACS > MySQL > LWM2M > Register new device > Device lost connection > Device sends registration request again > Tasks are duplicated

26401

OneIoT ACS > Big amount of devices > Devices registration > An error occurred

=== 2023.04.05 - Build 0.0.35

Issue ID Description

26240

OneIoT ACS > Settings > USP > Configuration > Incorrect measurement unit name is present

25788

OneIoT ACS > LWM2M > Software manager > "Update Result" with "52" error code > Incorrect description

26102

CPE Admin > Settings > LWM2M > Configuration > Firmware > Incorrect parameter name

25783

OneIoT ACS > LWM2M > Settings > Configuration > Software > Observe attributes Update Result (/9/XXX/9) > Incorrect hint

=== 2023.03.30 - Build 0.0.34

Branched 6.4. Master currently became 6.4.1

Main goal:

Make insert queries to cpe_parameter, cpe_log and cpe_changed_parameter with as big as possible number of rows

Restrictions (most of them are for cpe_parameter table, because its updating is doing up from 2 places, instead of cpe_log and cpe_changed_parameter):

  1. Data from CPE should to be inserted in DB ASAP

  2. Insertion of the data to DB needs to be exactly in the same order as it came from cpe

  3. Very important to support p.2 on multinodes env

  4. Parameters from Inform should be inserted before parameters at the end of session

  5. If flow is blocked by restrictions 2 and 3, it must be blocked only for the cpe which is upon restrictions

  6. It is not permitted to execute more than one insert for the same cpe_id at the same time (possible deadlock on DB)

  7. Prevent big amount of the data in hazelcast store

  8. Flow blocks because of restrictions above shouldn’t block http thread (thread for the processing request from CPE)

Few examples on restrictions:

  1. CPE A has sent parameter B at 00:00:00. If we are waiting for the data from other CPEs in order to make insert with big amount of rows, it is not correct to insert data from CPE A, for example, at 00:00:10

  2. CPE A has sent parameter P with value V1 in Inform, in the same session it have done GPV task for parameter P and brings new value V2. According to restriction V1 shouldn’t be inserted AFTER V2

  3. CPE A has sent parameter P with value V1 in Inform on ACS N1, after 0.5 seconds it comes with new session on ACS N2 and brings P with V2. According to restriction V1 shouldn’t be inserted AFTER V2

  4. CPE A was registering on ACS and has sent parameter P with value V1 in Inform, in the same session it has done GPN/GPA/GPV, but GPV has been rejected, as result, at the end of the session ACS has CPE tree with empty values. According to restriction V1 from Inform shouldn’t be overwriting with empty from the end of the session

  5. There is a queue of 1K devices with parameters for DB insert, one of this 1K have sent parameter before this queue, and it is blocking the flow. According to restriction flow should continue to run with skipping of the blocked CPE (passing it on next iteration)

  6. If other restrictions will be implemented, this will not happened

  7. It is incorrect to pass parameters from CPE to the hazelcast store in order to support ordering of the data, because in this case bottle neck will be on HC

  8. If CPE has passed parameters before and now it is passing other set of parameters, CPE should not “wait” while ACS and DB are processing previous one

Flow:

There 3 main part of the flow:

  1. Data add to the queue (need to be asynchronous because of restrictions 5 and 8)

    1. If CPE is currently in data processing or executing on DB (previous data insertion) ⇒ wait (restrictions 2, 3, 4)

    2. Save parameters in ACS RAM (restriction 7)

    3. Add cpe to the pending data queue (restrictions 2, 4) in HC (restriction 3)

  2. Data processing by the queue (creating arrays from the available data in order to pass to db bulk inserts). Continuous background thread (ACS lifetime) whish is started on ACS start

    1. If local ACS RAM storage is empty → wait not more than 500ms (restriction 1)

    2. Iterating over the pending cpe ques, in the same order that they have been added (restrictions 2, 3, 4)

    3. Fill rows for insertion array while one of two happens: array size will be 1K (the maximum amount of rows for single insert) OR queue is empty

    4. Pass rows to DB (background)

  3. Executing query on DB. Background process in order to minimize waiting pause if queue is containing more than 1k rows (restriction 1)

    1. Open connection/transaction and execute the query

    2. Remove cpe from the HC pending queue, in other words – unlock it. It will give unlock in flow p. 1.a.

new log files created:

bulk_process.log – contains all information about bulk processing (like rows count, waiting time, locks and others)

long_request.log – contains information about requests time btw ACS and CPE, in addition, it contains stack traces of the long requests (more than 20 sec running). It is very helpful on the step of troubleshooting the communication problems btw ACS and CPE (it shows if it is network or some other issues inside ACS)

Requires logback.xml change

=== 2023.03.19 - Build 0.0.33

Issue ID Description

26351

OneIoT ACS > LWM2M > Monitoring > Edit > Save > Changes are not applied

=== 2023.03.19 - Build 0.0.32

Fixed performance issues

=== 2023.03.16 - Build 0.0.31

Merge lwm2m changes with 6.3 0.0.95

Requires DB change

Added cpe.lifetime column, changed functionality for device status update for TR and LWM2M protocols

=== 2023.03.15 - Build 0.0.30

Merge lwm2m changes with 6.3 0.0.93

Improved queries on update active monitoring

Requires DB change

=== 2023.03.14 - Build 0.0.29

Issue ID Description

14739

CPE Admin > LWM2M > Group Update > SPV task > "Show group update report" > GPV task is absent

Merge lwm2m changes with 6.3 0.0.91

Optimization in UG queries

need standalone_mysql.xml change

socketTimeout=60000&connectTimeout=60000 added to FTDS

=== 2023.03.07 - Build 0.0.28

Merge lwm2m changes with 6.3 0.0.90

Optimization with cpe protocol identify added to another places in UG process

=== 2023.03.07 - Build 0.0.27

Optimization in UG: there were issues with setting correct cpe state when UG is running on big amount of CPEs

Optimization in stop QoE monitor: bulk inserting rows into cpe_pending_task instead of multiple inserts

Optimization in cpe protocol identification in UG and QoE stop: cpe protocol identified by product_class_group entry

instead of each cpe identification. 1 query to DB is executing instead of N(cpe count) queries

=== 2023.03.06 - Build 0.0.26

Optimization in UG. Query which updates statuses in ug_cpe_completed occured lock on DB. Optimization done.

=== 2023.03.01 - Build 0.0.25

Moved LWM2M device status checker to quartz in order to disallow concurrent status check on multi-node env

=== 2023.02.20 - Build 0.0.24

Issue ID Description

26160

CPE Admin / CSR > LWM2M > Trace a device > Register device > Show trace > Incorrect log is displayed

26254

OneIoT ACS > Group Update > Reactivation > "Re-run only for devices that have failed to update" > Offline device > Second reactivation > Task deleted / Update completed

changes in /ACSWebServiceConfiguration/configureAccountInfoMapping and /ACSWebServiceConfiguration/getAccountInfoMapping WS methods

Attribute activeConnection have been moved from data element to the data→param element

changes in config_custom_data.xml

Attribute activeConnection have been moved from data element to the data→param element

Correct structure example:

<dataList>

<data column="cust1" name="MACAddress" >

<param name="MACAddress" activeConnection="true"/>

<param name="Device.Ethernet.Interface.1.MACAddress" activeConnection="false"/>

</data>

</dataList>

Requires DB change

=== 2023.02.13 - Build 0.0.23

Issue ID Description

26178

CPE Admin > LWM2M v1.1 > Group Update > "Send to"="All" > Multiple parameters > Activate update > Task isn’t sent to all devices

25860

OneIoT ACS > BulkData > Existing monitor > Add parameter / Change "Perform every" > Irrelevant tasks are sent to device

Fixed java.util.ConcurrentModificationException in qoe cache

=== 2023.02.01 - Build 0.0.22

Issue ID Description

26062

CPE Admin > Update group > Device upgraded > Firmware task not showing in activity logs

21564

OneIoT ACS > "config_custom_data.xml" > activeConnection="true" > Device without "ExternalIPAddress" in inform > Notification task not generated

11281

OneIoT ACS > ACS WS > stopSOAPTracingForUnknownCPEs > Tracing is not stopped

10942

OneIoT ACS > TR-069 / USP > ACS WS > addCPEObjectWithoutTask > Fault occurred while processing

23621

OneIoT ACS > Monitoring > "Send to" = group > Monitor is active > Edit > Change group > Save > Relevant tasks are not generated to the group

25923

OneIoT ACS > LWM2M > Resources missing > Not coming in new builds (server SOAP method deleteLWM2MResourceDefinitions)

26029

OneIoT ACS >QD LWM2M > "REJECT" / "FAIL" strategy > Several tasks > Device doesn’t respond > Next task send with incorrect interval

26160

CPE Admin / CSR > LWM2M > Trace a device > Register device > Show trace > Incorrect log is displayed

LWM2M changes merged with 6.3 0.0.84 RC

Added hazelcast metrics collection functionality

Requires DB change

Requires hazelcast start scripts change

updated hz-start.bat and jvm.options, added:

-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=9110

-Dcom.sun.management.jmxremote.authenticate=false

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.local.only=true

-Dhazelcast.jmx=true

=== 2023.01.04 - Build 0.0.21

Issue ID Description

24696

OneIoT ACS > Whitelist > Serial Number > Add file > Register device not in list > Device registered

25768

OneIoT ACS > Bulk data > JSON not supported > Monitoring > Activate > Irrelevant parameter in SPV task

25882

OneIoT ACS > Cluster > "qoeMonitorMode" = 0 > "cpe_parameter_name.csv" / "monitor_results_{timestamp}.csv" > No synchronization between nodes

26087

Hazelcast address configuration

25860

OneIoT ACS > BulkData > Existing monitor > Add parameter / Change "Perform every" > Irrelevant tasks are sent to device

25864

OneIoT ACS > Monitoring > "Send to" = Group > Device turns matching to group > No monitoring tasks

23621

OneIoT ACS > Monitoring > "Send to" = group > Monitor is active > Edit > Change group > Save > Relevant tasks are not generated to the group

=== 2022.12.29 - Build 0.0.20

Issue ID Description

26026

OneIoT ACS > LWM2M > Software > Observe on /9/0/9 first request > No response > Task transferred to incorrect "Failed" state

26029

OneIoT ACS > LWM2M > "REJECT" / "FAIL" strategy > Several tasks > Device doesn’t respond > Next task send with incorrect interval

=== 2022.12.28 - Build 0.0.19

Merged with 6.3 0.0.75 lwm2m

f

=== 2022.12.23 - Build 0.0.18

Issue ID Description

26043

OneIoT ACS > LWM2M > "Enable verification by version"="true" > Firmware update task > /3/0/3 value is equal to target file version > Incorrect task state

Merged with 6.3 0.0.73 lwm2m

=== 2022.12.16 - Build 0.0.17

Issue ID Description

26027

OneIoT ACS > LWM2M > Software > Set attributes for "/9/0/9" resource > No response > Task transferred to incorrect "Failed" state

Merged with 6.3 0.0.72 RC lwm2m

=== 2022.12.06 - Build 0.0.16

Issue ID Description

15082

CPE Admin / CSR > LWM2M > Device Update > Advanced View > Add object> "Add to provision" unselected > Task provisioned

11490

OneIoT ACS > Cluster > MQTT > Update Group > Task > Set parameter value > Task from one node remains in pending state

25883

LWM2M Software update fail cases

12058

CPE Admin > USP > Device Update > Device Activity > Part of profile tasks is absent

23638

CPE Admin > Settings > External System > Azure PnP > Measurement units unification request

14808

CPE Admin > LWM2M > Specific device > Group Update > SPV task for several resources > Activate > Task is failed

15037

CPE Admin / CSR > LWM2M > Resource with "time" value type > "Content-Format=text/plain" > Value does not convert to UTC format

Fixed exception throwing on event check

Fix MQTT > Smart home devices > Dusun mapping > ZWAVE empty sensor list reported by gateway > ZigBee3.0 sensors removed from gateway device tree

Smarthome. Add return manufacturer on hub registration;

Merged with 6.3 0.0.67 lwm2m + TR069.

Added hardcoded event: 1116 - cpe comes with bootstrap

Requires db change

=== 2022.10.20 - Build 0.0.15

Added AllInterfaces=1 to PortMapping task on manageable device

=== 2022.10.13 - Build 0.0.14

Issue ID Description

25775

OneIoT ACS > LWM2M > Software manager > "Software content delivery protocol"="CoAP" > Run software update task > Software download is failed

25769

OneIoT ACS > LWM2M > Settings > Configuration > Software > Change instances view representation

25770

OneIoT ACS > Device update > Connection request to a device behind the NAT using port forwarding

Configuration parameter added:

<!--Legal values: 0 - 65535 | Default value: 0 (disabled) | A port number of the manageable device on which connection request should be mapped-->

<manageableCpePort>0</manageableCpePort>

Requires db change

=== 2022.10.10 - Build 0.0.13

Issue ID Description

21511

OneIoT ACS > LWM2M > TCP > Firmware via PULL+CoAP > Firmware download not started;

24742

LWM2M Software management support added;

=== 2022.09.21 - Build 0.0.12

Issue ID Description

14861

CPE Admin / CSR > Add ability to delete Model names and manufacturers

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

16284

OneIoT ACS > LWM2M > Update object definition with version < > from current > Register LWM2M 1.0 device > Methods for object are absent

23625

OneIoT ACS > ACS WS > MQTT > subscribeCpeParameterEvent > Event message isn’t generated to external server

13281

OneIoT ACS > USP > New device > It is possible to register a new device with already used endpoint

13172

CPE Admin > Oracle > Device Profile > Export / Import > Profile is associated with wrong "product_class_group" id

13413

CPE Admin > Reports > Group update > Suggestion to add "Completion date" column

9398

CPE Admin > Group Update > Reactivation > Edit > Show list > No device update status

17293

CPE Admin > Multi-server environment > System > Overview > ACS shutdwon is not reflected in the view

13029

CPE Admin > USP > Group Update > "Install" task > Device Update > Device Activity > Task remains in the "Pending" state

Requires DB change

=== 2022.08.10 - Build 0.0.11

Issue ID Description

11657

OneIoT ACS > LWM2M > Device Update > Device History > Irrelevant "4 VALUE CHANGE" activities are present

Merge with 6.3 0.0.38 version (lwm2m improvements);

Full merge with 6.3 0.0.41

=== 2022.06.29 - Build 0.0.10

Issue ID Description

15151

CPE Admin > Device Update > Custom RPC > Call any RPC method > An unexpected occurrence happened

14920

OneIoT ACS > Bulk data > HTTPS > Activate monitor > Incorrect username and password sent to device

14669

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with "reprovision"=1 > Provision Manager > Duplicated records

11246

ACS > "dataStoreDaysAmount" more than 0 > CPEs are deleted > Files are not deleted from FTP

11176

ACS > Multi-Domain / Multi-ISP > Events > Event for specific domain > Tasks sent to irrelevant CPEs

10533

CPE Admin > Settings > Whitelist > IPv6 functionality isn’t provided

8830

ACS > Whitelist > Whitelist cache isn’t synced between nodes

14861

CPE Admin / CSR > Add ability to delete Model names and manufacturers

New ACS WS method: deleteManufacturerAndModel

White List cache migrated to hazelcast

Merged with 6.3

=== 2022.06.16 - Build 0.0.9

Issue ID Description

14536

CPE Admin / CSR > LWM2M > Device Update > Device Info > List of methods > Full path of "Reboot" method displayed

14711

CPE Admin > Settings > LWM2M > Configuration > Observation > Typo in hint

10684

OneIoT ACS > Settings > External system > "Azure" sub-tab > Incorrect hint for "Use full parameter name" parameter

15139

OneIoT ACS > LWM2M > IPv6 > Any push task > Error in ACS log

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

15179

CPE Admin > Settings > LWM2M > Configuration > Observation > Wrong hint

16290

OneIoT ACS > LWM2M > Security import > Different identities have a different security type > Server type with "NO_SEC" security mode is absent from the list

16291

OneIoT ACS > LWM2M > Security import > endpointLike% > "LWM2M" server type > Edit > Incorrect endpoint mask is present

14541

OneIoT ACS > Settings > LWM2M > Configuration > Lifecycle > Hint of "FAILED" strategy is absent

Fix issue with lwm2m security import (were unable to import lwm2m + bs security with the different identities);

Merge with 6.3 0.0.20 version (lwm2m improvements);

=== 2022.01.31 - Build 0.0.8

Issue ID Description

14536

CPE Admin / CSR > LWM2M > Device Update > Device Info > List of methods > Full path of "Reboot" method displayed

=== 2022.01.31 - Build 0.0.7

Issue ID Description

14907

CPE Admin > Settings > LWM2M > Configuration > Bootstrap > Typo in hint

14541

OneIoT ACS > Settings > LWM2M > Configuration > Lifecycle > Hint of "FAILED" strategy is absent

15001

CPE Admin > Group Update > Delete all relevant devices > Tasks sent to all devices of the current model

15013

OneIoT ACS > Cluster > LWM2M > Register a new device > Custom resource > GPV task not sent to device

15000

CPE Admin > Settings > External System > "Oracle SCEF" sub-tab > Non-default values are present

14937

OneIoT ACS > Definition for any resource with version 1.1 > Restart ACS > Register LWM2M device with 1.0 protocol > GPV task not generated

14912

CPE Admin > Settings > LWM2M > Resource > Any resource > Download file with 1.1 version > Download file with 1.0 version > Incorrect version displayed

Issue described in 15001 Also fixed for Events and Monitoring

Requires DB change

=== 2022.01.22 - Build 0.0.6

Issue ID Description

14937

OneIoT ACS > Definition for any resource with version 1.1 > Restart ACS > Register LWM2M device with 1.0 protocol > GPV task not generated

14943

CPE Admin > Settings > LWM2M > Configuration > Lifecycle > Typo in hint

14658

CPE Admin > LWM2M > "Location" resource > Device Update > Device Info > "Latitude" and "Longitude" are set to incorrect fields

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

11438

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with different "reprovision" > Duplicated tasks created

12183

OneIoT ACS > Monitoring > Individual > Edit > Set send to: "All (New and existing)" > Monitor tasks are sent only for new devices

12136

OneIoT ACS > Settings > Events > Delete specific event URL > Save > Trigger event > Event sent to incorrect URL

=== 2022.01.13 - Build 0.0.5

Issue ID Description

14739

CPE Admin > LWM2M > Group Update > SPV task > "Show group update report" > GPV task is absent

14658

CPE Admin > LWM2M > "Location" resource > Device Update > Device Info > "Latitude" and "Longitude" are set to incorrect fields

14796

OneIoT ACS > LWM2M > "REJECTED" / "FAILED" strategy > Device not responding > Retransmission count reached > Request queue timeout reached > Task remains in "Sent" state

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

14691

CPE Admin > LWM2M > "useMultipleSetTasks" = "1" > Group Update > Multiple SPV task > Activate > Multiplied only part of parameters

13281

OneIoT ACS > USP > New device > It is possible to register a new device with already used endpoint

14606

OneIoT ACS > LWM2M > Monitoring > Edit > Change "Perform every" value > New pmin / pmax values not sent to device

14852

CPE Admin > Group Update > "Backup" task > Incorrect file generated

14697

CPE Admin > Device Update > Device Info > Search any address > Save > Value not saved

12085

OneIoT ACS > Monitoring > Running > Edit > "Send to" = Group > Edit group > Change condition > Relevant tasks aren’t sent to device

12016

CPE Admin > Device is busy > Implement delayed connection request

14912

CPE Admin > Settings > LWM2M > Resource > Any resource > Download file with 1.1 version > Download file with 1.0 version > Incorrect version displayed

Add 10034 feature (text encoding for opaque resources)

Fixed LF in hub model name issue

=== 2021.12.21 - Build 0.0.4

Issue ID Description

9715

CPE Admin > Group Update / Events / Device Profile > New / Edit > Tasks > Action > Incorrect items wording

14554

CPE Admin > Settings > LWM2M > Security import > endpointLike% > Security imported with incorrect endpoint mask

14649

CPE Admin > Settings > Events > Hardcoded Events > Any event > Add URL > Save > An error occured

=== 2021.11.23 - Build 0.0.3

Issue ID Description

13422

OneIoT ACS > LWM2M > Online > Restart ACS > Device remains in "Online" state:

13470

OneIoT ACS > LWM2M v1.1 > Update request > LWM2M protocol version changed to 1.0

14551

CPE Admin > Settings > LWM2M > Configuration > Lifecycle > "Manufacturer name for devices without /3/0/0 resource" > Add information to parameter tip

13450

CPE Admin > Settings > LWM2M > Security > Import > File with incorrect URL > Incorrect URL added

11269

OneIoT ACS > ACS WS > deleteCPEForProductClass > "model" tag is absent

12179

OneIoT ACS > Monitor > Multiple instances parameter > Truncate > Truncate interval > Data from "cpe_data" isn’t truncated

12136

OneIoT ACS > Settings > Events > Delete specific event URL > Save > Trigger event > Event sent to incorrect URL

12137

OneIoT ACS > Settings > Events > Change specific event URL > Save > Trigger event > Irrelevant event generated

12917

OneIoT ACS > Cluster > Edit "ftacs_task.properties" file on any node > Save > Changes are not synced across all nodes

11947

CPE Admin > FCC Diagnostics > Device Update > Show trace > Inform with 8DC is absent from the trace

11863

CPE Admin > Device under monitor > "Inform" doesn’t contain monitored data > GPV > Device Update > Show trace > GPVR is absent from the trace

11008

OneIoT ACS > Monitoring > New / Edit > CSV isn’t updated

11935

ACS- >Profile tasks creation duplicated

11438

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with different "reprovision" > Duplicated tasks created

11673

CPE Admin > Update group > Offline device > Eliminate duplicated pending tasks

12093

OneIoT ACS > Monitoring > Monitor for several models > Edit > Delete model > Save > Relevant tasks aren’t sent to devices

Smarthome. Remove Accton functionality from project (2QA: don’t need to check, only make sure server starts and smarthome functionality is working basically);

  • fixed timer (every 5 sec) check expired online or inactive cpes by lifetime - device will by moved to offline;

  • add onetime check online cpes on server start - device will be moved to inactive state if online timer active and strategy for taks is PENDING_INACTIVE;

LWM2M Security import. Add line number in error message;

LWM2M Security import. Add validation for endpoint masks. Error descr: Line#%s. The specified endpoint mask already exists or matches existing security endpoint mask: %s;

(acs part) 11485 CPE Admin > "force.qoe.stop.all" = "1" > Monitoring > New / Edit > Notification message request

Merged with 6.2 0.0.58

=== 2021.05.11 - Build 0.0.2

Issue ID Description

11192

OneIoT ACS > MQTT > Monitoring > Existing monitor > More than 2 devices > Exclude any device > Save > No "Observation"Off" task

Smarthome rest encoding. Bugfix;

Merge with 6.2;

=== 2021.03.11 - Build 0.0.1

Issue ID Description

13069

OneIoT ACS > LWM2M > Device with protocol version 1.1 > Execute "Bootstrap-Request Trigger" > Method not found

13029

CPE Admin > USP > Group Update > "Install" task > Device Update > Device Activity > Task remains in the "Pending" state

11490

OneIoT ACS > Cluster > MQTT > Update Group > Task > Set parameter value > Task from one node remains in pending state

11489

OneIoT ACS > Cluster > MQTT > Device Update > Send any task > Task remains in pending state

11398

CPE Admin > Settings > LWM2M > Resource > Add any resource file version 1.1 > Incorrect version is displayed

13393

CPE Admin > Settings > LWM2M > Configuration > Network > Typos in input fields name

Add update queue to FSH MQTT integration module (to prevent 'duplicate entry' when trying to handle two or more updates of the same parameter from the agent)

Coordinates are now stored in cust_device1.latitude and cust_device1.longitude. In order to migrate existing coordinates - execute CoordinatesMigration.sql.

Version 6.4.0

Latest build: 0.0.35

=== 2024.06.20 - Build 0.0.35

  1. If device sends wrong auth credentials twice or more - send InformResponse in order to reduce RetryCount Informs (found on RIL)

  2. Added ability to make builds without unneeded systems, like: axioma, azure, pnp, thingsboard, losant, lwm2m (reduces CPU in x2)

=== 2023.05.31 - Build 0.0.34

Issue ID Description

27506

OneIoT ACS > TR-069 > Device Diagnostics > 8 DIAGNOSTIC COMPLETE inform with diagnostic result > Diagnostics result is not saved

26414

OneIoT ACS > TR-069 > Device Update > Diagnostics > Any diagnostics > 8 DIAGNOSTIC COMPLETE > GPV task with diagnostic results request is absent

=== 2023.03.19 - Build 0.0.33

Issue ID Description

26351

OneIoT ACS > LWM2M > Monitoring > Edit > Save > Changes are not applied

=== 2023.03.19 - Build 0.0.32

Fixed performance issues

=== 2023.03.16 - Build 0.0.31

Merge lwm2m changes with 6.3 0.0.95

Requires DB change

Added cpe.lifetime column, changed functionality for device status update for TR and LWM2M protocols

=== 2023.03.15 - Build 0.0.30

Merge lwm2m changes with 6.3 0.0.93

Improved queries on update active monitoring

Requires DB change

=== 2023.03.14 - Build 0.0.29

Issue ID Description

14739

CPE Admin > LWM2M > Group Update > SPV task > "Show group update report" > GPV task is absent

Merge lwm2m changes with 6.3 0.0.91

Optimization in UG queries

need standalone_mysql.xml change

socketTimeout=60000&connectTimeout=60000 added to FTDS

=== 2023.03.07 - Build 0.0.28

Merge lwm2m changes with 6.3 0.0.90

Optimization with cpe protocol identify added to another places in UG process

=== 2023.03.07 - Build 0.0.27

Optimization in UG: there were issues with setting correct cpe state when UG is running on big amount of CPEs

Optimization in stop QoE monitor: bulk inserting rows into cpe_pending_task instead of multiple inserts

Optimization in cpe protocol identification in UG and QoE stop: cpe protocol identified by product_class_group entry

instead of each cpe identification. 1 query to DB is executing instead of N(cpe count) queries

=== 2023.03.06 - Build 0.0.26

Optimization in UG. Query which updates statuses in ug_cpe_completed occured lock on DB. Optimization done.

=== 2023.03.01 - Build 0.0.25

Moved LWM2M device status checker to quartz in order to disallow concurrent status check on multi-node env

=== 2023.02.20 - Build 0.0.24

Issue ID Description

26160

CPE Admin / CSR > LWM2M > Trace a device > Register device > Show trace > Incorrect log is displayed

26254

OneIoT ACS > Group Update > Reactivation > "Re-run only for devices that have failed to update" > Offline device > Second reactivation > Task deleted / Update completed

changes in /ACSWebServiceConfiguration/configureAccountInfoMapping and /ACSWebServiceConfiguration/getAccountInfoMapping WS methods

Attribute activeConnection have been moved from data element to the data→param element

changes in config_custom_data.xml

Attribute activeConnection have been moved from data element to the data→param element

Correct structure example:

<dataList>

<data column="cust1" name="MACAddress" >

<param name="MACAddress" activeConnection="true"/>

<param name="Device.Ethernet.Interface.1.MACAddress" activeConnection="false"/>

</data>

</dataList>

Requires DB change

=== 2023.02.13 - Build 0.0.23

Issue ID Description

26178

CPE Admin > LWM2M v1.1 > Group Update > "Send to"="All" > Multiple parameters > Activate update > Task isn’t sent to all devices

25860

OneIoT ACS > BulkData > Existing monitor > Add parameter / Change "Perform every" > Irrelevant tasks are sent to device

Fixed java.util.ConcurrentModificationException in qoe cache

=== 2023.02.01 - Build 0.0.22

Issue ID Description

26062

CPE Admin > Update group > Device upgraded > Firmware task not showing in activity logs

21564

OneIoT ACS > "config_custom_data.xml" > activeConnection="true" > Device without "ExternalIPAddress" in inform > Notification task not generated

11281

OneIoT ACS > ACS WS > stopSOAPTracingForUnknownCPEs > Tracing is not stopped

10942

OneIoT ACS > TR-069 / USP > ACS WS > addCPEObjectWithoutTask > Fault occurred while processing

23621

OneIoT ACS > Monitoring > "Send to" = group > Monitor is active > Edit > Change group > Save > Relevant tasks are not generated to the group

25923

OneIoT ACS > LWM2M > Resources missing > Not coming in new builds (server SOAP method deleteLWM2MResourceDefinitions)

26029

OneIoT ACS >QD LWM2M > "REJECT" / "FAIL" strategy > Several tasks > Device doesn’t respond > Next task send with incorrect interval

26160

CPE Admin / CSR > LWM2M > Trace a device > Register device > Show trace > Incorrect log is displayed

LWM2M changes merged with 6.3 0.0.84 RC

Added hazelcast metrics collection functionality

Requires DB change

Requires hazelcast start scripts change

updated hz-start.bat and jvm.options, added:

-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=9110

-Dcom.sun.management.jmxremote.authenticate=false

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.local.only=true

-Dhazelcast.jmx=true

=== 2023.01.04 - Build 0.0.21

Issue ID Description

24696

OneIoT ACS > Whitelist > Serial Number > Add file > Register device not in list > Device registered

25768

OneIoT ACS > Bulk data > JSON not supported > Monitoring > Activate > Irrelevant parameter in SPV task

25882

OneIoT ACS > Cluster > "qoeMonitorMode" = 0 > "cpe_parameter_name.csv" / "monitor_results_{timestamp}.csv" > No synchronization between nodes

26087

Hazelcast address configuration

25860

OneIoT ACS > BulkData > Existing monitor > Add parameter / Change "Perform every" > Irrelevant tasks are sent to device

25864

OneIoT ACS > Monitoring > "Send to" = Group > Device turns matching to group > No monitoring tasks

23621

OneIoT ACS > Monitoring > "Send to" = group > Monitor is active > Edit > Change group > Save > Relevant tasks are not generated to the group

=== 2022.12.29 - Build 0.0.20

Issue ID Description

26026

OneIoT ACS > LWM2M > Software > Observe on /9/0/9 first request > No response > Task transferred to incorrect "Failed" state

26029

OneIoT ACS > LWM2M > "REJECT" / "FAIL" strategy > Several tasks > Device doesn’t respond > Next task send with incorrect interval

=== 2022.12.28 - Build 0.0.19

Merged with 6.3 0.0.75 lwm2m

f

=== 2022.12.23 - Build 0.0.18

Issue ID Description

26043

OneIoT ACS > LWM2M > "Enable verification by version"="true" > Firmware update task > /3/0/3 value is equal to target file version > Incorrect task state

Merged with 6.3 0.0.73 lwm2m

=== 2022.12.16 - Build 0.0.17

Issue ID Description

26027

OneIoT ACS > LWM2M > Software > Set attributes for "/9/0/9" resource > No response > Task transferred to incorrect "Failed" state

Merged with 6.3 0.0.72 RC lwm2m

=== 2022.12.06 - Build 0.0.16

Issue ID Description

15082

CPE Admin / CSR > LWM2M > Device Update > Advanced View > Add object> "Add to provision" unselected > Task provisioned

11490

OneIoT ACS > Cluster > MQTT > Update Group > Task > Set parameter value > Task from one node remains in pending state

25883

LWM2M Software update fail cases

12058

CPE Admin > USP > Device Update > Device Activity > Part of profile tasks is absent

23638

CPE Admin > Settings > External System > Azure PnP > Measurement units unification request

14808

CPE Admin > LWM2M > Specific device > Group Update > SPV task for several resources > Activate > Task is failed

15037

CPE Admin / CSR > LWM2M > Resource with "time" value type > "Content-Format=text/plain" > Value does not convert to UTC format

Fixed exception throwing on event check

Fix MQTT > Smart home devices > Dusun mapping > ZWAVE empty sensor list reported by gateway > ZigBee3.0 sensors removed from gateway device tree

Smarthome. Add return manufacturer on hub registration;

Merged with 6.3 0.0.67 lwm2m + TR069.

Added hardcoded event: 1116 - cpe comes with bootstrap

Requires db change

=== 2022.10.20 - Build 0.0.15

Added AllInterfaces=1 to PortMapping task on manageable device

=== 2022.10.13 - Build 0.0.14

Issue ID Description

25775

OneIoT ACS > LWM2M > Software manager > "Software content delivery protocol"="CoAP" > Run software update task > Software download is failed

25769

OneIoT ACS > LWM2M > Settings > Configuration > Software > Change instances view representation

25770

OneIoT ACS > Device update > Connection request to a device behind the NAT using port forwarding

Configuration parameter added:

<!--Legal values: 0 - 65535 | Default value: 0 (disabled) | A port number of the manageable device on which connection request should be mapped-→

<manageableCpePort>0</manageableCpePort>

Requires db change

=== 2022.10.10 - Build 0.0.13

Issue ID Description

21511

OneIoT ACS > LWM2M > TCP > Firmware via PULL+CoAP > Firmware download not started;

24742

LWM2M Software management support added;

=== 2022.09.21 - Build 0.0.12

Issue ID Description

14861

CPE Admin / CSR > Add ability to delete Model names and manufacturers

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

16284

OneIoT ACS > LWM2M > Update object definition with version < > from current > Register LWM2M 1.0 device > Methods for object are absent

23625

OneIoT ACS > ACS WS > MQTT > subscribeCpeParameterEvent > Event message isn’t generated to external server

13281

OneIoT ACS > USP > New device > It is possible to register a new device with already used endpoint

13172

CPE Admin > Oracle > Device Profile > Export / Import > Profile is associated with wrong "product_class_group" id

13413

CPE Admin > Reports > Group update > Suggestion to add "Completion date" column

9398

CPE Admin > Group Update > Reactivation > Edit > Show list > No device update status

17293

CPE Admin > Multi-server environment > System > Overview > ACS shutdwon is not reflected in the view

13029

CPE Admin > USP > Group Update > "Install" task > Device Update > Device Activity > Task remains in the "Pending" state

Requires DB change

=== 2022.08.10 - Build 0.0.11

Issue ID Description

11657

OneIoT ACS > LWM2M > Device Update > Device History > Irrelevant "4 VALUE CHANGE" activities are present

Merge with 6.3 0.0.38 version (lwm2m improvements);

Full merge with 6.3 0.0.41

=== 2022.06.29 - Build 0.0.10

Issue ID Description

15151

CPE Admin > Device Update > Custom RPC > Call any RPC method > An unexpected occurrence happened

14920

OneIoT ACS > Bulk data > HTTPS > Activate monitor > Incorrect username and password sent to device

14669

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with "reprovision"=1 > Provision Manager > Duplicated records

11246

ACS > "dataStoreDaysAmount" more than 0 > CPEs are deleted > Files are not deleted from FTP

11176

ACS > Multi-Domain / Multi-ISP > Events > Event for specific domain > Tasks sent to irrelevant CPEs

10533

CPE Admin > Settings > Whitelist > IPv6 functionality isn’t provided

8830

ACS > Whitelist > Whitelist cache isn’t synced between nodes

14861

CPE Admin / CSR > Add ability to delete Model names and manufacturers

New ACS WS method: deleteManufacturerAndModel

White List cache migrated to hazelcast

Merged with 6.3

=== 2022.06.16 - Build 0.0.9

Issue ID Description

14536

CPE Admin / CSR > LWM2M > Device Update > Device Info > List of methods > Full path of "Reboot" method displayed

14711

CPE Admin > Settings > LWM2M > Configuration > Observation > Typo in hint

10684

OneIoT ACS > Settings > External system > "Azure" sub-tab > Incorrect hint for "Use full parameter name" parameter

15139

OneIoT ACS > LWM2M > IPv6 > Any push task > Error in ACS log

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

15179

CPE Admin > Settings > LWM2M > Configuration > Observation > Wrong hint

16290

OneIoT ACS > LWM2M > Security import > Different identities have a different security type > Server type with "NO_SEC" security mode is absent from the list

16291

OneIoT ACS > LWM2M > Security import > endpointLike% > "LWM2M" server type > Edit > Incorrect endpoint mask is present

14541

OneIoT ACS > Settings > LWM2M > Configuration > Lifecycle > Hint of "FAILED" strategy is absent

Fix issue with lwm2m security import (were unable to import lwm2m + bs security with the different identities);

Merge with 6.3 0.0.20 version (lwm2m improvements);

=== 2022.01.31 - Build 0.0.8

Issue ID Description

14536

CPE Admin / CSR > LWM2M > Device Update > Device Info > List of methods > Full path of "Reboot" method displayed

=== 2022.01.31 - Build 0.0.7

Issue ID Description

14907

CPE Admin > Settings > LWM2M > Configuration > Bootstrap > Typo in hint

14541

OneIoT ACS > Settings > LWM2M > Configuration > Lifecycle > Hint of "FAILED" strategy is absent

15001

CPE Admin > Group Update > Delete all relevant devices > Tasks sent to all devices of the current model

15013

OneIoT ACS > Cluster > LWM2M > Register a new device > Custom resource > GPV task not sent to device

15000

CPE Admin > Settings > External System > "Oracle SCEF" sub-tab > Non-default values are present

14937

OneIoT ACS > Definition for any resource with version 1.1 > Restart ACS > Register LWM2M device with 1.0 protocol > GPV task not generated

14912

CPE Admin > Settings > LWM2M > Resource > Any resource > Download file with 1.1 version > Download file with 1.0 version > Incorrect version displayed

Issue described in 15001 Also fixed for Events and Monitoring

Requires DB change

=== 2022.01.22 - Build 0.0.6

Issue ID Description

14937

OneIoT ACS > Definition for any resource with version 1.1 > Restart ACS > Register LWM2M device with 1.0 protocol > GPV task not generated

14943

CPE Admin > Settings > LWM2M > Configuration > Lifecycle > Typo in hint

14658

CPE Admin > LWM2M > "Location" resource > Device Update > Device Info > "Latitude" and "Longitude" are set to incorrect fields

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

11438

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with different "reprovision" > Duplicated tasks created

12183

OneIoT ACS > Monitoring > Individual > Edit > Set send to: "All (New and existing)" > Monitor tasks are sent only for new devices

12136

OneIoT ACS > Settings > Events > Delete specific event URL > Save > Trigger event > Event sent to incorrect URL

=== 2022.01.13 - Build 0.0.5

Issue ID Description

14739

CPE Admin > LWM2M > Group Update > SPV task > "Show group update report" > GPV task is absent

14658

CPE Admin > LWM2M > "Location" resource > Device Update > Device Info > "Latitude" and "Longitude" are set to incorrect fields

14796

OneIoT ACS > LWM2M > "REJECTED" / "FAILED" strategy > Device not responding > Retransmission count reached > Request queue timeout reached > Task remains in "Sent" state

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

14691

CPE Admin > LWM2M > "useMultipleSetTasks" = "1" > Group Update > Multiple SPV task > Activate > Multiplied only part of parameters

13281

OneIoT ACS > USP > New device > It is possible to register a new device with already used endpoint

14606

OneIoT ACS > LWM2M > Monitoring > Edit > Change "Perform every" value > New pmin / pmax values not sent to device

14852

CPE Admin > Group Update > "Backup" task > Incorrect file generated

14697

CPE Admin > Device Update > Device Info > Search any address > Save > Value not saved

12085

OneIoT ACS > Monitoring > Running > Edit > "Send to" = Group > Edit group > Change condition > Relevant tasks aren’t sent to device

12016

CPE Admin > Device is busy > Implement delayed connection request

14912

CPE Admin > Settings > LWM2M > Resource > Any resource > Download file with 1.1 version > Download file with 1.0 version > Incorrect version displayed

Add 10034 feature (text encoding for opaque resources)

Fixed LF in hub model name issue

=== 2021.12.21 - Build 0.0.4

Issue ID Description

9715

CPE Admin > Group Update / Events / Device Profile > New / Edit > Tasks > Action > Incorrect items wording

14554

CPE Admin > Settings > LWM2M > Security import > endpointLike% > Security imported with incorrect endpoint mask

14649

CPE Admin > Settings > Events > Hardcoded Events > Any event > Add URL > Save > An error occured

=== 2021.11.23 - Build 0.0.3

Issue ID Description

13422

OneIoT ACS > LWM2M > Online > Restart ACS > Device remains in "Online" state:

13470

OneIoT ACS > LWM2M v1.1 > Update request > LWM2M protocol version changed to 1.0

14551

CPE Admin > Settings > LWM2M > Configuration > Lifecycle > "Manufacturer name for devices without /3/0/0 resource" > Add information to parameter tip

13450

CPE Admin > Settings > LWM2M > Security > Import > File with incorrect URL > Incorrect URL added

11269

OneIoT ACS > ACS WS > deleteCPEForProductClass > "model" tag is absent

12179

OneIoT ACS > Monitor > Multiple instances parameter > Truncate > Truncate interval > Data from "cpe_data" isn’t truncated

12136

OneIoT ACS > Settings > Events > Delete specific event URL > Save > Trigger event > Event sent to incorrect URL

12137

OneIoT ACS > Settings > Events > Change specific event URL > Save > Trigger event > Irrelevant event generated

12917

OneIoT ACS > Cluster > Edit "ftacs_task.properties" file on any node > Save > Changes are not synced across all nodes

11947

CPE Admin > FCC Diagnostics > Device Update > Show trace > Inform with 8DC is absent from the trace

11863

CPE Admin > Device under monitor > "Inform" doesn’t contain monitored data > GPV > Device Update > Show trace > GPVR is absent from the trace

11008

OneIoT ACS > Monitoring > New / Edit > CSV isn’t updated

11935

ACS- >Profile tasks creation duplicated

11438

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with different "reprovision" > Duplicated tasks created

11673

CPE Admin > Update group > Offline device > Eliminate duplicated pending tasks

12093

OneIoT ACS > Monitoring > Monitor for several models > Edit > Delete model > Save > Relevant tasks aren’t sent to devices

Smarthome. Remove Accton functionality from project (2QA: don’t need to check, only make sure server starts and smarthome functionality is working basically);

  • fixed timer (every 5 sec) check expired online or inactive cpes by lifetime - device will by moved to offline;

  • add onetime check online cpes on server start - device will be moved to inactive state if online timer active and strategy for taks is PENDING_INACTIVE;

LWM2M Security import. Add line number in error message;

LWM2M Security import. Add validation for endpoint masks. Error descr: Line#%s. The specified endpoint mask already exists or matches existing security endpoint mask: %s;

(acs part) 11485 CPE Admin > "force.qoe.stop.all" = "1" > Monitoring > New / Edit > Notification message request

Merged with 6.2 0.0.58

=== 2021.05.11 - Build 0.0.2

Issue ID Description

11192

OneIoT ACS > MQTT > Monitoring > Existing monitor > More than 2 devices > Exclude any device > Save > No "Observation"Off" task

Smarthome rest encoding. Bugfix;

Merge with 6.2;

=== 2021.03.11 - Build 0.0.1

Issue ID Description

13069

OneIoT ACS > LWM2M > Device with protocol version 1.1 > Execute "Bootstrap-Request Trigger" > Method not found

13029

CPE Admin > USP > Group Update > "Install" task > Device Update > Device Activity > Task remains in the "Pending" state

11490

OneIoT ACS > Cluster > MQTT > Update Group > Task > Set parameter value > Task from one node remains in pending state

11489

OneIoT ACS > Cluster > MQTT > Device Update > Send any task > Task remains in pending state

11398

CPE Admin > Settings > LWM2M > Resource > Add any resource file version 1.1 > Incorrect version is displayed

13393

CPE Admin > Settings > LWM2M > Configuration > Network > Typos in input fields name

Add update queue to FSH MQTT integration module (to prevent 'duplicate entry' when trying to handle two or more updates of the same parameter from the agent)

Coordinates are now stored in cust_device1.latitude and cust_device1.longitude. In order to migrate existing coordinates - execute CoordinatesMigration.sql.

Version 6.3

Latest build: 0.0.103

=== 2024.07.17 - Build 0.0.103

Issue ID Description

33355

ACS > Mqtt > FSH device > Dusun > Enchance sensor mapping

=== 2024.02.13 - Build 0.0.102

Issue ID Description

32694

OneIoT ACS > LWM2M > Wrong CoAP option for blockwise Pull request

=== 2024.01.25 - Build 0.0.101

Issue ID Description

27456

OneIoT ACS > LWM2M > CBOR > Server not decoding or displaying CBOR data

LWM2M. Add log for delete request;

LWM2M. Fix search method by registration id;

=== 2023.05.31 - Build 0.0.100

Issue ID Description

27456

One IoT > LWM2M > CBOR > Server not decoding or displaying CBOR data

27580

One IoT > FOTA > RST sent

=== 2023.04.18 - Build 0.0.99

Issue ID Description

27420

OneIoT ACS > LWM2M > JSON / SENML_JSON > Resource matches "CBOR resource mask (regExp)" > Non opaque value type > Value displayed as parsed

=== 2023.04.11 - Build 0.0.98

Issue ID Description

26391

OneIoT ACS > LWM2M > Reads on objects failing due to certain characters

=== 2023.03.30 - Build 0.0.97

Issue ID Description

12092

CPE Admin > TR-069 > Oracle > Device Update > Device History > Activity type > "1 BOOT" is absent

LWM2M add debug messages to bootstrap process

LWM2M Fix issue with pct attribute during the bootstrap process. BS was failed with RST response

DB update required

=== 2023.03.23 - Build 0.0.96

Issue ID Description

26350

OneIoT ACS > LWM2M > Monitoring > Edit > Save > Changes are not applied

=== 2023.03.16 - Build 0.0.95

Issue ID Description

26324

OneIoT ACS > Oracle > LWM2M > Monitor > Observation On task is not sent to device

=== 2023.03.15 - Build 0.0.94

Issue ID Description

26324

OneIoT ACS > Oracle > LWM2M > Monitor > Observation On task is not sent to device

Requires DB change

=== 2023.03.15 - Build 0.0.93

Issue ID Description

26320

OneIoT ACS > manageableCpePort=0 > Child and gateway are registered > manageableCpePort more than 0 > GPV tasks on root object > "Add object" task is not generated to gateway

26324

OneIoT ACS > Oracle > LWM2M > Monitor > Observation On task is not sent to device

=== 2023.03.14 - Build 0.0.92

Issue ID Description

26324

OneIoT ACS > Oracle > LWM2M > Monitor > Observation On task is not sent to device

Fix issue with wrong error message during lwm2m security manifest import (Wrong domain exception was hidden);

=== 2023.03.10 - Build 0.0.91

Issue ID Description

26324

OneIoT ACS > Oracle > LWM2M > Monitor > Observation On task is not sent to device

26320

OneIoT ACS > manageableCpePort=0 > Child and gateway are registered > manageableCpePort more than 0 > GPV tasks on root object > "Add object" task is not generated to gateway

=== 2023.03.07 - Build 0.0.90

Issue ID Description

26308

OneIoT ACS > LWM2M > Not found any device parameter

=== 2023.03.06 - Build 0.0.89

Issue ID Description

12183

OneIoT ACS > Monitoring > Individual > Edit > Set send to: "All (New and existing)" > Monitor tasks are sent only for new devices

26301

OneIoT ACS > TR-069 > Monitoring > Bulk data > Edit monitor > Change parameter or "Perform Every" > Relevant task is not sent to device

=== 2023.03.03 - Build 0.0.88

Issue ID Description

26253

OneIoT ACS > Group Update > SPV > Reactivation > "Re-run only for devices that have failed to update" > Second reactivation > Tasks failed / Update completed

=== 2023.02.27 - Build 0.0.87

Issue ID Description

26253

OneIoT ACS > Group Update > SPV > Reactivation > "Re-run only for devices that have failed to update" > Second reactivation > Tasks failed / Update completed

26170

OneIoT ACS > USP > Bulk data > Stop monitor > Task failed

26283

OneIoT ACS > Hardcoded query for LwM2M reg update check can’t be disabled

Settings > LWM2M > Configuration > Lifecycle > "Device offline status tracking" added. Default value "true"

=== 2023.02.27 - Build 0.0.86

Issue ID Description

25888

OneIoT ACS > LWM2M > Firmware update > GET /5/0 > Failed response > Task transferred to incorrect "Rejected" state

26244

OneIoT ACS > LWM2M > Device Update > Firmware download task > Device doesn’t respond > Task transferred to "Pending" state > Update request > Task not sent to device

26268

OneIoT ACS > TR-069 > Group Update > SPV > "Re-run only for devices that have failed to update" > SPV task failed / Update completed

26253

OneIoT ACS > Group Update > SPV > Reactivation > "Re-run only for devices that have failed to update" > Second reactivation > Tasks failed / Update completed

=== 2023.02.22 - Build 0.0.85

Issue ID Description

26195

OneIoT ACS > MQTT > FSH > Wulian > PowerSwitch > Value > AccessType > Workaround

26170

OneIoT ACS > USP > Bulk data > Stop monitor > Task is failed

26185

OneIoT ACS > LWM2M > Send firmware > Device returns new version on "GET /3/0/3" request > Value for "/3/0/3" resource not changed

26058

QoE GUI > USP > Monitor on multiple instances parameter > KPIs > KPI with instances is displayed

26254

OneIoT ACS > Group Update > Reactivation > "Re-run only for devices that have failed to update" > Offline device > Second reactivation > Task deleted / Update completed

26252

OneIoT ACS > LWM2M > Enable verification by version=true > File without version > Send firmware > Firmware task transferred to "Failed" state

26253

OneIoT ACS > Group Update > SPV > Reactivation > "Re-run only for devices that have failed to update" > Second reactivation > Tasks failed / Update completed

26244

OneIoT ACS > LWM2M > Device Update > Firmware download task > Device doesn’t respond > Task transferred to "Pending" state > Update request > Task not sent to device

=== 2023.01.30 - Build 0.0.84

Issue ID Description

26144

OneIoT ACS > Smart Home CSR > Smart gateway admin user > Fill in address > Device Update > List > User location > Unexpected characters

26185

OneIoT ACS > LWM2M > Send firmware > Device returns new version on "GET /3/0/3" request > Value for "/3/0/3" resource not changed

26184

OneIoT ACS > LWM2M > Send firmware with incorrect URI > Send any firmware again > Firmware download task stuck in "Sent" state

26169

QoE GUI > USP > Bulk data > Monitor > KPI isn’t created

=== 2023.01.25 - Build 0.0.83

Issue ID Description

26139

OneIoT ACS > LWM2M > Send firmware > Task with "Observe=1" for "/5/0/3" resource is not sent

26005

OneIoT ACS > ispMode=1 / 2 > LWM2M > Device in domain with no Losant integration > Switch to domain with Losant integration > Message isn’t generated

26065

OneIoT ACS > LWM2M > Group Update > Update with several tasks including download > Activate > Incorrect sequence of tasks execution

=== 2023.01.23 - Build 0.0.82

Issue ID Description

26078

CPE Admin > Oracle > USP > Start any diagnostic > Diagnostic failed with error 7003

26151

OneIoT ACS > Settings > LWM2M > Configuration > Firmware > Enable verification by version > Typo in the hint (Requires DB change)

26146

OneIoT ACS > Beeline > MQTT > Devices are not registered

26098

OneIoT ACS > LWM2M > It is possible to register device with specific symbol

26065

OneIoT ACS > LWM2M > Group Update > Update with several tasks including download > Activate > Incorrect sequence of tasks execution

=== 2023.01.19 - Build 0.0.81

Issue ID Description

26081

OneIoT ACS > USP > It is possible to register two devices with the same serial number

26126

CPE Admin > USP > Group Update > Any diagnostic > Task fails with reason "Task Not Supported"

26151

OneIoT ACS > Settings > LWM2M > Configuration > Firmware > Enable verification by version > Typo in the hint

26147

OneIoT ACS > Oracle > USP > Device registration > Error during device re-registration

26133

OneIoT ACS > LWM2M > Try to register device > Device is not registered

=== 2023.01.18 - Build 0.0.80

Issue ID Description

26134

OneIoT ACS > USP > Register device > "Get_supported_dm" request it not sent to device

26138

OneIoT ACS > LWM2M > Enable verification by version=true > Send firmware > Firmware task transfered to "Failed" state

26144

Smart Home CSR > Smart gateway admin user > Fill in address > Device Update > List > User location > Unexpected characters

26119

CPE Admin > Multi-Domain > Settings > LWM2M > Security > Existing endpoint > Import > Incorrect validation of endpoint masks

26129

CPE Admin / CSR > Device Update > USP > Device Diagnostics > Download diagnostics > Diagnostic failed

26133

OneIoT ACS > LWM2M > Try to register device > Device is not registered

=== 2023.01.13 - Build 0.0.79

Issue ID Description

25980

OneIoT ACS > USP > Bulk data > Monitoring > "Add object" task on "Device.BulkData.Profile." not generated

26081

OneIoT ACS > USP > It is possible to register two devices with the same serial number

26066

OneIoT ACS > Settings > LWM2M > Configuration > Common > Define content type by /3/0 response > Unclear hint description

26065

OneIoT ACS > LWM2M > Group Update > Update with several tasks including download > Activate > Incorrect sequence of tasks execution

26098

OneIoT ACS > LWM2M > It is possible to register device with specific symbol

=== 2023.01.06 - Build 0.0.78

Issue ID Description

24736

OneIoT ACS > LWM2M > Device with "Online" state > Stop all nodes > Start any node > Start another node > Device transferred to incorrect "Online" state

26066

OneIoT ACS > Settings > LWM2M > Configuration > Common > Define content type by /3/0 response > Unclear hint description

Fix for Windstream: if cpe has the same serial number in Gateway and Manageable ⇒ skip this Manageable object (if only 1 instance ⇒ skip this CPE)

=== 2023.01.04 - Build 0.0.77

Issue ID Description

22584

OneIoT ACS > acs_configuration.xml > "udpPingServers" tag > Typo in description

23621

OneIoT ACS > Monitoring > "Send to" = group > Monitor is active > Edit > Change group > Save > Relevant tasks are not generated to the group

26078

CPE Admin > Oracle > USP > Start any diagnostic > Diagnostic failed with error 7003

26081

OneIoT ACS > USP > It is possible to register two devices with the same serial number

13009

OneIoT ACS > USP > Device Update > Device Diagnostic > Create any diagnostic > Task is failed

=== 2023.01.02 - Build 0.0.76

Issue ID Description

26066

OneIoT ACS > Settings > LWM2M > Configuration > Common > Define content type by /3/0 response > Unclear hint description

26021

OneIoT ACS > LWM2M > Displaying HEX data instead of CBOR payload

26044

OneIoT ACS > LWM2M > SENML-JSON / JSON > CBOR data not parsed

26076

OneIoT ACS > "Define content type by /3/0 response=true" > Device registered with "ct" attribute value > Content format determinated by response on GET /3/0

=== 2022.12.27 - Build 0.0.75

Issue ID Description

26066

OneIoT ACS > Settings > LWM2M > Configuration > Common > Define content type by /3/0 response > Unclear hint description

26048

OneIoT ACS > LWM2M > SENML-JSON / SENML-CBOR content type > Time value not converted

26052

OneIoT ACS > LWM2M / USP > It is possible to register two devices with the same serial number (only for lwm2m)

=== 2022.12.26 - Build 0.0.74

Issue ID Description

26049

OneIoT ACS > Settings > LWM2M > Configuration > Common > Content type names unification request

26021

OneIoT ACS > LWM2M > Displaying HEX data instead of CBOR payload

26044

OneIoT ACS > LWM2M > SENML-JSON / JSON > CBOR data not parsed

=== 2022.12.23 - Build 0.0.73

Issue ID Description

26045

OneIoT ACS > Settings > LWM2M > Configuration > Common > Define content type by /3/0 response > Spelling error in hint

26042

OneIoT ACS > LWM2M > "Enable verification by version"="true" > Firmware update task > /3/0/3 value is equal to target file version > Incorrect task state

26038

OneIoT ACS > LWM2M > Group Update > More than 1 firmware download tasks > Only first task sent to device

26041

CPE Admin > LWM2M > Group Update > More than 1 firmware download tasks > Chart displayed incorrectly

=== 2022.12.16 - Build 0.0.72

Issue ID Description

10444

CPE Admin / CSR > USP > Update CPE > Device Diagnostics > Wi-Fi neighboring diagnostics > Create > An error occured (emul also fixed 1.7.165)

26021

OneIoT ACS > LWM2M > Displaying HEX data instead of CBOR payload

26031

OneIoT ACS > LWM2M > CPEadmin > Observe >Incorrect representation of a parameter name

26013

CPE Admin > LWM2M > Monitor for at least 2 parameters > Device Update > Device Activity > Incorrect parameter names are displayed

LWM2M Configuration: extended property drop-down Device default content type with SenML-CBOR, SenML-JSON values

LWM2M Configuration: Define content type by /3/0 response. If true - and device doesn’t send ct in registration request - ct will be defined as ContentFormat option in /3/0 response otherwise from Device default content type

Monitor restart required.

=== 2022.12.13 - Build 0.0.71

Issue ID Description

25998

OneIoT ACS > LWM2M > Monitoring with at least 4 resources > Register device without some resources > Part of discover tasks are not sent

=== 2022.12.09 - Build 0.0.70

Issue ID Description

25995

OneIoT ACS > LWM2M > Firmware update > Send download file task > No response > Task transferred to "Pending" state > Excessive task is sent

25998

OneIoT ACS > LWM2M > Monitoring with at least 4 resources > Register device without some resources > Part of discover tasks are not sent

=== 2022.12.08 - Build 0.0.69

LWM2M Configuration: load factor = retransmit wait = 1f;

=== 2022.12.07 - Build 0.0.68

Issue ID Description

7699

OneIoT ACS > LWM2M > UPDATE REQUEST > Pending task is not pushed to device

25967

OneIoT ACS > LWM2M > Firmware update > Task completed > 2 min > Firmware update > Task is not sent to device

25986

OneIoT ACS > LWM2M > Send any task > Device not responding > "Request. Max re-transmission count" more than 4 > Incorrect retransmission count

=== 2022.12.06 - Build 0.0.67

Issue ID Description

25967

OneIoT ACS > LWM2M > Firmware update > Task completed > 2 min > Firmware update > Task is not sent to device

=== 2022.12.05 - Build 0.0.66

Issue ID Description

25985

OneIoT ACS > LWM2M > Send any task > Device not responding > Retransmission > Incorrect number of "REPEATS" in DB

25986

OneIoT ACS > LWM2M > Send any task > Device not responding > "Request. Max re-transmission count" more than 4 > Incorrect retransmission count

=== 2022.12.01 - Build 0.0.65

Issue ID Description

25953

OneIoT ACS > LWM2M > Register new device > GET /3/0 > Device lost connection > 2 min > Register device > Pending task is not pushed to device

25967

OneIoT ACS > LWM2M > Firmware update > Task completed > 2 min > Firmware update > Task is not sent to device

25906

OneIoT ACS > LWM2M > Firmware update > Polling for "/5/0/3" resource > No response > Task transferred to incorret "Failed" state

=== 2022.12.01 - Build 0.0.64

Issue ID Description

34666

OneIoT ACS > Fix of Windstream issue

Fix USP pending tasks stuck in the task queue issue. The issue seems to occurre if an exception is thrown during device

registration procedure (e.g. wrong parameter value [string instead of long …​ etc.] provided by the device)

Add USP HTTP bulk data push support with JSON NameValuePair type of payload encoding (see A.2 and A.7.2.4)

=== 2022.11.29 - Build 0.0.63

Issue ID Description

25953

OneIoT ACS > LWM2M > Register new device > GET /3/0 > Device lost connection > 2 min > Register device > Pending task is not pushed to device

25964

OneIoT ACS > LWM2M > Firmware update > Send download file task > No response > Task transferred to "Pending" state > Update request > Task does not send to device

25963

OneIoT ACS > LWM2M > Firmware update > Send download file task > No response > Task transferred to "Pending" state > Excessive task is sent

=== 2022.11.23 - Build 0.0.62

Issue ID Description

7699

OneIoT ACS > LWM2M > UPDATE REQUEST > Pending task is not pushed to device

25940

OneIoT ACS > LWM2M > Reboot task fails with "Device method not found"

25902

OneIoT ACS > LWM2M > Firmware update > Set attributes for "/5/0/5" resource > No response > Task transferred to incorrect "Failed" state

25891

OneIoT ACS > LWM2M > Firmware update > Reset state for "/5/0/1" or "/5/0/0" resource > No response > Task transferred to incorrect "Failed" state

25906

OneIoT ACS > LWM2M > Firmware update > Polling for "/5/0/3" resource > No response > Task transferred to incorret "Failed" state

25939

OneIoT ACS > LWM2M > Update group > Tasks are sent 2 times

=== 2022.11.15 - Build 0.0.61

Issue ID Description

25858

OneIoT ACS > Register child device > Register gateway device > "Add object" task is not generated to gateway

=== 2022.11.15 - Build 0.0.60

Issue ID Description

25858

OneIoT ACS > Register child device > Register gateway device > "Add object" task is not generated to gateway

=== 2022.11.15 - Build 0.0.59

Issue ID Description

25905

OneIoT ACS > LWM2M > Firmware update > Polling for "/5/0/3" resource is failed > Task transferred to incorrect "Failed" state

=== 2022.11.11 - Build 0.0.58

Issue ID Description

25858

OneIoT ACS > Register child device > Register gateway device > "Add object" task is not generated to gateway

25909

OneIoT ACS > TR-181 gateway with child device > "Add object" task with port forwarding > Irrelevant parameters are present

25908

OneIoT ACS > TR-098 gateway with child device > "Add object" task with port forwarding > Irrelevant "AllInterfaces" parameter is present

L&G. Fixed an issue where SenMl CBOR objlink values weren’t decoded correctly and remained empty in db.

=== 2022.11.11 - Build 0.0.57

Issue ID Description

25855

OneIoT ACS > Gateway with child device > Delete gateway > Record not deleted from "cpe_manageable_push" table

=== 2022.11.07 - Build 0.0.56

Issue ID Description

25893

OneIoT ACS > New device registered > "1116 - cpe comes with bootstrap" hardcoded event is not generated

Losant integration. Moved device info from the root object to the separate deviceinfo object (field). Enabled by default pushing only params of type Number

=== 2022.11.07 - Build 0.0.55

Added hardcoded event: 1116 - cpe comes with bootstrap

Requires db change

=== 2022.11.04 - Build 0.0.54

Smarthome. Fix issue with IR control learning parameter; Was broken from moving to REST API communication change;

=== 2022.11.03 - Build 0.0.53

Issue ID Description

7699

OneIoT ACS > LWM2M > UPDATE REQUEST > Pending task is not pushed to device

25863

OneIoT ACS > LWM2M > FW update > Engine doesn’t store in DB statuses for resources 5/0/3 and 5/0/5

11657

OneIoT ACS > LWM2M > Device Update > Device History > Irrelevant "4 VALUE CHANGE" activities are present

25876

OneIoT ACS > LWM2M > Firmware update > Implementation of negative test cases

=== 2022.11.02 - Build 0.0.52

Issue ID Description

25858

OneIoT ACS > Register child device > Register gateway device > "Add object" task is not generated to gateway

25856

OneIoT ACS > Gateway with child device > Child device > Connection request > Incorrect URL for connection request

25847

OneIoT ACS > Any gateway > Register child device > "Add object" task is not generated

=== 2022.10.31 - Build 0.0.51

Issue ID Description

25779

Need to add preferred content in BS operation; (fix parsing, internal issue)

=== 2022.10.28 - Build 0.0.50

Issue ID Description

25847

OneIoT ACS > Any gateway > Register child device > Add object" task is not generated

Smarthome. Add return manufacturer on hub registration;

=== 2022.10.24 - Build 0.0.49

Issue ID Description

25817

OneIoT ACS > TR-181 gateway > Register child device > Add object" task is not generated

25813

OneIoT ACS > Change "manageableCpePort" parameter > SPV task with changed port is not generated

25770

OneIoT ACS > Device update > Connection request to a device behind the NAT using port forwarding

25812

OneIoT ACS > Child device re-registered with new IP > SPV task with changed IP is not generated

25810

CPE Admin > Device Update > Open child device > Connection request > Connection request task with incorrect URL

25811

OneIoT ACS > Register child device > Register gateway device > "Add object" task is not generated to gateway

Fixed exception throwing on event check

Fix MQTT > Smart home devices > Dusun mapping > ZWAVE empty sensor list reported by gateway > ZigBee3.0 sensors removed from gateway device tree

Configuration parameter added:

<!--Legal values: 0 - 65535 | Default value: 0 (disabled) | A port number of the manageable device on which connection request should be mapped-->

<manageableCpePort>0</manageableCpePort>

Requires db change

=== 2022.10.13 - Build 0.0.48

Issue ID Description

25796

OneIoT ACS > ACS WS > subscribeCpeParameterEvent > "monitored=true" > By model > "Observation On" task is not generated

=== 2022.10.13 - Build 0.0.47

Issue ID Description

25779

Need to add preferred content in BS operation;

=== 2022.10.10 - Build 0.0.46

Added 'monitored' bool field to SubscribeCpeParameterEvent method body. if monitored == false the notification request task won’t be generated.

Fixed 'lwm2m opaque resource displayed as raw data in CPEAdmin instead of hex after get single resource task is executed'.

=== 2022.09.27 - Build 0.0.45

Issue ID Description

24676

OneIoT ACS > LWM2M > Device info / Account info > Losant > Device info and account info data is not separated in payload

=== 2022.09.15 - Build 0.0.44

Issue ID Description

24675

OneIoT ACS > LWM2M > Device created / deleted > Losant > Payload doesn’t contain device status

Merge with 6.2 0.0.85;

Added possibility to run udp ping tasks without period (must be passed as null from UI)

=== 2022.09.15 - Build 0.0.43

Added configuration parameter:

<!-- Legal values: 0 - 100 | Default value: 0 (disabled) | If > 0 ACS will block new session with device creation -->

<cpuThreshold>0</cpuThreshold>

=== 2022.09.12 - Build 0.0.42

Add uplink Axioma integration feature

=== 2022.09.01 - Build 0.0.41

Issue ID Description

23663

OneIoT ACS > Oracle > "Composite Read/Write/Observe operation handling mode"="PREFER" > Register new LWM2M device > All composite tasks are failed

=== 2022.08.29 - Build 0.0.40

Issue ID Description

22574

CPE Admin / CSR > Device Update > LWM2M > Add object > Executable resources are missing

Fix USP device not registered without onboarding over WebSocket MTP

=== 2022.08.19 - Build 0.0.39

Issue ID Description

23631

OneIoT ACS > ACS WS > subscribeCpeParameterEvent > Events duplicated

=== 2022.08.18 - Build 0.0.38

Issue ID Description

22607

OneIoT ACS > LWM2M > Bootstrap > "Bootstrap WRITE mode"="INSTANCE" > Bootstrap configuration with multiple instances object > Resources are sent separately

22570

OneIoT ACS > LWM2M > PENDING_INACTIVE strategy > "Polling" process mode > Start firmware update > Device doesn’t respond > Incorrect "Online" device status

22571

OneIoT ACS > LWM2M > PENDING_INACTIVE strategy > "Polling" process mode > Start firmware update > Device doesn’t respond > Task in Pending state > Task transferred to incorrect "Sent" state

5000

- 5sec

300000

- 5min

23623

OneIoT ACS > ACS WS > LWM2M / USP > subscribeCpeParameterEvent > Tasks are not generated to device

LWM2M add example for hint in all values which measured in (ms):

Example:

On notification event from UdpPingServer all valid UG will be sent

=== 2022.08.02 - Build 0.0.37

Issue ID Description

21546

OneIoT ACS > LWM2M > Account Info changed > Losant > HTTP request isn’t generated

Fixed an issue where the encoded Tlv instance (payload) included the object instance id while targeting the same object instance id in URI (e.g. localhost/1/0) of write operation (e.g. during bootstrap)

=== 2022.08.02 - Build 0.0.36

Issue ID Description

21546

OneIoT ACS > LWM2M > Account Info changed > Losant > HTTP request isn’t generated

=== 2022.08.02 - Build 0.0.35

Issue ID Description

22589

OneIoT ACS > Group Update > UDP echo ping > Incorrect value is used for "SourceIPAddress" parameter

=== 2022.07.29 - Build 0.0.34

Added support of the UDP echo ping

Requires DB change

ACS WS type udpPingTask added and all methods for UpdateGroup extended with new type

REST API ACS methods added: udpEchoIpRefresh and udpEchoStarted

=== 2022.07.25 - Build 0.0.33

Jio. LWM2M Firmware process add check for IDLE /5/0/5 state during the registration

=== 2022.07.21 - Build 0.0.32

Issue ID Description

21550

CPE Admin > LWM2M > "Enable verification by version"="true" > Group Update > Firmware update task > /3/0/3 value is equal to target file version > Incorrect "Pending" state is displayed

21558

OneIoT ACS > LWM2M > PENDING strategy > "Polling" process mode > Start firmware update > Device doesn’t respond > Task transferred to incorrect "Rejected" state

=== 2022.07.21 - Build 0.0.31

Issue ID Description

21550

CPE Admin > LWM2M > "Enable verification by version"="true" > Group Update > Firmware update task > /3/0/3 value is equal to target file version > Incorrect "Pending" state is displayed

=== 2022.07.20 - Build 0.0.31

Issue ID Description

21559

OneIoT ACS > Config_custom_data.xml > Not working properly

=== 2022.07.15 - Build 0.0.30

Issue ID Description

21550

CPE Admin > LWM2M > "Enable verification by version"="true" > Group Update > Firmware update task > /3/0/3 value is equal to target file version > Incorrect "Pending" state is displayed

=== 2022.07.14 - Build 0.0.29

Issue ID Description

21541

OneIoT ACS > LWM2M > "Enable verification by version"="true" > Start firmware > Device reboted with new firmware version > Incorrect task state

21520

OneIoT ACS > Settings > LWM2M > Configurations > Lifecycle > "Use discovery for tree root" parameter > Spelling error

=== 2022.07.13 - Build 0.0.28

Issue ID Description

21525

OneIoT ACS > LWM2M > Firmware update task > /3/0/3 value is equal to target file version > No inform comment

LWM2M. Enable AES-CBC cipher suites (disabled by default in scandium cipher library); Will be tested by customer;

=== 2022.07.08 - Build 0.0.27

LWM2M remove cpe address map usage; Only one cpe address uri;

LWM2M Settings: Lifecycle.Use discovery for tree root. As workaround for customer for removed discovery functionality;

LWM2M Settings: Enable verification by version. For UG and cases if device doesn’t support fw state update after installation;

=== 2022.07.04 - Build 0.0.26

Add LwM2M instance bootstrap. The WRITE mode can be switched via the 'Bootstrap WRITE mode' config. option.

Fix PSK identity bootstrap

SenML CBOR fix for Visive

=== 2022.07.04 - Build 0.0.25

LWM2M FW (additional debug and refactoring state check after reboot);

=== 2022.06.30 - Build 0.0.24

Issue ID Description

21475

OneIoT ACS > LWM2M version 1.1 > Multiple parameters > Send Update > Complex SPV task parameters duplicated

=== 2022.06.28 - Build 0.0.23

LWM2M Security/Bootstrap import any object extension;

=== 2022.06.22 - Build 0.0.22

Issue ID Description

20432

CPE Admin > Monitored CPE > Update group > Firmware upgrade task is stuck in "Sent" state

=== 2022.06.17 - Build 0.0.21

Issue ID Description

15169

OneIoT ACS > LWM2M > Firmware update > PUSH > Error in ACS log

21436

OneIoT ACS > Clean install > Device Update > "Manufacturer" drop-down > Irrelevant "Smartico" value is present

20430

OneIoT ACS > CBOR resource mask (regExp) > Edit > Excluded resource > Device Update > Advanced view > Excluded CBOR resouce value displayed as parsed value

=== 2022.06.15 - Build 0.0.20

LWM2M Fix server start without ipv6 address param (sample: -Dftacs.ipv6.address=[fe80::a0a3:88cc:309f:328a])

Fix lwm2m registry empty address value;

=== 2022.06.13 - Build 0.0.19

Issue ID Description

20416

OneIoT ACS > Settings > LWM2M > Configuration > Observation > "Use GET requests instead of DISCOVERY" > Typo in "DISCOVERY" word

20414

OneIoT ACS > Settings > LWM2M > Configuration > Network > "Request queue. Request delay timeout (ms) " hint > Typo in hint text

20420

OneIoT ACS > LWM2M > "Use GET requests instead of DISCOVERY" check box selected > Start monitor > GET with "Observe:0" not sent

LWM2M OMA registry improvements. Add connection and so timeouts in configuration properties (Settings → LWM2M → Configuration → OMA Registry: OMA registry connection timeout (ms), OMA registry socket timeout (ms));

LWM2M OMA registry improvements. If OMA registry address is empty - server won’t try to connect to oma registry;

LWM2M cbor mask change fix. Server restart isn’t required if property changed. Settings → LWM2M → Configuration → Common → CBOR resource mask (regExp)

=== 2022.06.08 - Build 0.0.18

LWM2M Discovery or get opportunity property added for monitoring. Settings → LWM2M → Configuration → Observation → Use GET requests instead of DISCOVER true/false;

LWM2M add property Settings → LWM2M → Configuration → Network → Request queue. Request delay timeout (ms). In queue mode each request from server may be delayed. L&G specific functionality;

Removing log4j dependencies, and adopting to logback library; Nothing needed for build for both logging libraries, only server configuration

=== 2022.06.02 - Build 0.0.17

Issue ID Description

20386

OneIoT ACS > TR-098 > Group Update > Trace diagnostics > Add results to monitoring data > 8 DIAGNOSTIC COMPLETE > Incorrect GPV task

20385

OneIoT ACS > TR-181 > Group Update > Trace diagnostics > Add results to monitoring data > Incorrect GPA task

20376

OneIoT ACS > Group Update > UDP echo diagnostics with "Add results to monitoring data" > GPV task with icorrect name parameter is created

=== 2022.05.09 - Build 0.0.16

Add Dusun integration

=== 2022.05.05 - Build 0.0.15

Issue ID Description

10415

CPE Admin > Group Update > Re-run only for devices that have failed to update > Tasks completed > Update remains in "Reactivation" state

16283

OneIoT ACS > LWM2M > Protocol version 1.1 > "Bootstrap-Request Trigger" > Method not found

17305

OneIoT ACS > Settings > LWM2M > Configuration > Observation > Spelling error in hint

13394

CPE Admin > Settings > USP > Configuration > Measurement units unification request

14711

CPE Admin > Settings > LWM2M > Configuration > Observation > Typo in hint

10684

OneIoT ACS > Settings > External system > "Azure" sub-tab > Incorrect hint for "Use full parameter name" parameter

=== 2022.04.28 - Build 0.0.14

Issue ID Description

15179

CPE Admin > Settings > LWM2M > Configuration > Observation > Wrong hint

16290

OneIoT ACS > LWM2M > Security import > Different identities have a different security type > Server type with "NO_SEC" security mode is absent from the list

16291

OneIoT ACS > LWM2M > Security import > endpointLike% > "LWM2M" server type > Edit > Incorrect endpoint mask is present

14541

OneIoT ACS > Settings > LWM2M > Configuration > Lifecycle > Hint of "FAILED" strategy is absent

15233

OneIoT ACS > "xmppServerConnectAlgorithm"="DNS-SRV" > Register device > Excessive tasks are generated

15146

OneIoT ACS > Multi-Domain > Device under specific domain > Delete device > Delete domain > Register device > Device registered to incorrect domain

17292

OneIoT ACS > Group Update > Two diagnostics > Device activity > First diagnostic has "Failed" state

10415

CPE Admin > Group Update > Re-run only for devices that have failed to update > Tasks completed > Update remains in "Reactivation" state

=== 2022.04.21 - Build 0.0.13

Fix issue with lwm2m security import (were unable to import lwm2m + bs security with the different indentities);

=== 2022.03.24 - Build 0.0.12

Added xmppServerConnectAlgorithm acs_configuration.xml parameter

Requires acs_configuration.xml update

=== 2022.02.18 - Build 0.0.11

Add the ability to bootstrap any LWM2M object resource

=== 2022.02.18 - Build 0.0.10

Issue ID Description

15091

OneIoT ACS > LWM2M > IPv6 > Any push task > Error in ACS log

15119

OneIoT ACS > Group Update > Minutely reactivation count reached > Update remains in "Reactivation" state

10415

CPE Admin > Group Update > Re-run only for devices that have failed to update > Tasks completed > Update remains in "Reactivation" state

=== 2022.02.16 - Build 0.0.9

Issue ID Description

14536

CPE Admin / CSR > LWM2M > Device Update > Device Info > List of methods > Full path of "Reboot" method displayed

14592

OneIoT ACS > acs_configuration.xml > updateGroupRandomStaticList > Typo in description

9103

OneIoT ACS > "acs_configuration.xml" file > Descriptions > Irrelevant words "CPE" are present

13490

OneIoT ACS > LWM2M > FTSetProvisionDeviceParameters > Multiple identical requests with "reprovision=1" > Excessive tasks created

LWM2M Fix issue with ipv6 for node interaction during the push tasks operation:

When device comes with ipv6 address – server is not able correctly define own address and during the push tasks operation trying to send some request to the wrong address

Requires acs_configuration.xml update

=== 2022.01.31 - Build 0.0.8

Issue ID Description

14536

CPE Admin / CSR > LWM2M > Device Update > Device Info > List of methods > Full path of "Reboot" method displayed

=== 2022.01.31 - Build 0.0.7

Issue ID Description

14907

CPE Admin > Settings > LWM2M > Configuration > Bootstrap > Typo in hint

14541

OneIoT ACS > Settings > LWM2M > Configuration > Lifecycle > Hint of "FAILED" strategy is absent

15001

CPE Admin > Group Update > Delete all relevant devices > Tasks sent to all devices of the current model

15013

OneIoT ACS > Cluster > LWM2M > Register a new device > Custom resource > GPV task not sent to device

15000

CPE Admin > Settings > External System > "Oracle SCEF" sub-tab > Non-default values are present

14937

OneIoT ACS > Definition for any resource with version 1.1 > Restart ACS > Register LWM2M device with 1.0 protocol > GPV task not generated

14912

CPE Admin > Settings > LWM2M > Resource > Any resource > Download file with 1.1 version > Download file with 1.0 version > Incorrect version displayed

Issue described in 15001 Also fixed for Events and Monitoring

Requires DB change

=== 2022.01.22 - Build 0.0.6

Issue ID Description

14937

OneIoT ACS > Definition for any resource with version 1.1 > Restart ACS > Register LWM2M device with 1.0 protocol > GPV task not generated

14943

CPE Admin > Settings > LWM2M > Configuration > Lifecycle > Typo in hint

14658

CPE Admin > LWM2M > "Location" resource > Device Update > Device Info > "Latitude" and "Longitude" are set to incorrect fields

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

11438

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with different "reprovision" > Duplicated tasks created

12183

OneIoT ACS > Monitoring > Individual > Edit > Set send to: "All (New and existing)" > Monitor tasks are sent only for new devices

12136

OneIoT ACS > Settings > Events > Delete specific event URL > Save > Trigger event > Event sent to incorrect URL

=== 2022.01.13 - Build 0.0.5

Issue ID Description

14739

CPE Admin > LWM2M > Group Update > SPV task > "Show group update report" > GPV task is absent

14658

CPE Admin > LWM2M > "Location" resource > Device Update > Device Info > "Latitude" and "Longitude" are set to incorrect fields

14796

OneIoT ACS > LWM2M > "REJECTED" / "FAILED" strategy > Device not responding > Retransmission count reached > Request queue timeout reached > Task remains in "Sent" state

14550

OneIoT ACS > LWM2M v1.1 > "useMultipleSetTasks=1" > Monitoring > Monitor with 3 parameters and more > Not all observation tasks sent to device

14691

CPE Admin > LWM2M > "useMultipleSetTasks" = "1" > Group Update > Multiple SPV task > Activate > Multiplied only part of parameters

13281

OneIoT ACS > USP > New device > It is possible to register a new device with already used endpoint

14606

OneIoT ACS > LWM2M > Monitoring > Edit > Change "Perform every" value > New pmin / pmax values not sent to device

14852

CPE Admin > Group Update > "Backup" task > Incorrect file generated

14697

CPE Admin > Device Update > Device Info > Search any address > Save > Value not saved

12085

OneIoT ACS > Monitoring > Running > Edit > "Send to" = Group > Edit group > Change condition > Relevant tasks aren’t sent to device

12016

CPE Admin > Device is busy > Implement delayed connection request

14912

CPE Admin > Settings > LWM2M > Resource > Any resource > Download file with 1.1 version > Download file with 1.0 version > Incorrect version displayed

Add 10034 feature (text encoding for opaque resources)

Fixed LF in hub model name issue

=== 2021.12.21 - Build 0.0.4

Issue ID Description

9715

CPE Admin > Group Update / Events / Device Profile > New / Edit > Tasks > Action > Incorrect items wording

14554

CPE Admin > Settings > LWM2M > Security import > endpointLike% > Security imported with incorrect endpoint mask

14649

CPE Admin > Settings > Events > Hardcoded Events > Any event > Add URL > Save > An error occured

=== 2021.11.23 - Build 0.0.3

Issue ID Description

13422

OneIoT ACS > LWM2M > Online > Restart ACS > Device remains in "Online" state:

13470

OneIoT ACS > LWM2M v1.1 > Update request > LWM2M protocol version changed to 1.0

14551

CPE Admin > Settings > LWM2M > Configuration > Lifecycle > "Manufacturer name for devices without /3/0/0 resource" > Add information to parameter tip

13450

CPE Admin > Settings > LWM2M > Security > Import > File with incorrect URL > Incorrect URL added

11269

OneIoT ACS > ACS WS > deleteCPEForProductClass > "model" tag is absent

12179

OneIoT ACS > Monitor > Multiple instances parameter > Truncate > Truncate interval > Data from "cpe_data" isn’t truncated

12136

OneIoT ACS > Settings > Events > Delete specific event URL > Save > Trigger event > Event sent to incorrect URL

12137

OneIoT ACS > Settings > Events > Change specific event URL > Save > Trigger event > Irrelevant event generated

12917

OneIoT ACS > Cluster > Edit "ftacs_task.properties" file on any node > Save > Changes are not synced across all nodes

11947

CPE Admin > FCC Diagnostics > Device Update > Show trace > Inform with 8DC is absent from the trace

11863

CPE Admin > Device under monitor > "Inform" doesn’t contain monitored data > GPV > Device Update > Show trace > GPVR is absent from the trace

11008

OneIoT ACS > Monitoring > New / Edit > CSV isn’t updated

11935

ACS- >Profile tasks creation duplicated

11438

OneIoT ACS > overwriteProvisionParameters=1 > FTSetDeviceParameters with different "reprovision" > Duplicated tasks created

11673

CPE Admin > Update group > Offline device > Eliminate duplicated pending tasks

12093

OneIoT ACS > Monitoring > Monitor for several models > Edit > Delete model > Save > Relevant tasks aren’t sent to devices

Smarthome. Remove Accton functionality from project (2QA: don’t need to check, only make sure server starts and smarthome functionality is working basically);

  • fixed timer (every 5 sec) check expired online or inactive cpes by lifetime - device will by moved to offline;

  • add onetime check online cpes on server start - device will be moved to inactive state if online timer active and strategy for taks is PENDING_INACTIVE;

LWM2M Security import. Add line number in error message;

LWM2M Security import. Add validation for endpoint masks. Error descr: Line#%s. The specified endpoint mask already exists or matches existing security endpoint mask: %s;

(acs part) 11485 CPE Admin > "force.qoe.stop.all" = "1" > Monitoring > New / Edit > Notification message request

Merged with 6.2 0.0.58

=== 2021.05.11 - Build 0.0.2

Issue ID Description

11192

OneIoT ACS > MQTT > Monitoring > Existing monitor > More than 2 devices > Exclude any device > Save > No "Observation"Off" task

Smarthome rest encoding. Bugfix;

Merge with 6.2;

=== 2021.03.11 - Build 0.0.1

Issue ID Description

13069

OneIoT ACS > LWM2M > Device with protocol version 1.1 > Execute "Bootstrap-Request Trigger" > Method not found

13029

CPE Admin > USP > Group Update > "Install" task > Device Update > Device Activity > Task remains in the "Pending" state

11490

OneIoT ACS > Cluster > MQTT > Update Group > Task > Set parameter value > Task from one node remains in pending state

11489

OneIoT ACS > Cluster > MQTT > Device Update > Send any task > Task remains in pending state

11398

CPE Admin > Settings > LWM2M > Resource > Add any resource file version 1.1 > Incorrect version is displayed

13393

CPE Admin > Settings > LWM2M > Configuration > Network > Typos in input fields name

Add update queue to FSH MQTT integration module (to prevent 'duplicate entry' when trying to handle two or more updates of the same parameter from the agent)

Coordinates are now stored in cust_device1.latitude and cust_device1.longitude. In order to migrate existing coordinates - execute CoordinatesMigration.sql.

Version 6.2

Latest build: 0.0.85

=== 2022.09.19 - Build 0.0.85

Issue ID Description

24718

CPEadmin > LWM2M > Security > Import > Server Error;

=== 2022.07.25 - Build 0.0.84

Jio. LWM2M Firmware process add check for IDLE /5/0/5 state during the registration

=== 2022.07.20 - Build 0.0.83

Issue ID Description

21559

OneIoT ACS > Config_custom_data.xml > Not working properly

=== 2022.07.18 - Build 0.0.82

Issue ID Description

21549

CPE Admin > LWM2M > "Enable verification by version"="true" > Group Update > Firmware update task > /3/0/3 value is equal to target file version > Incorrect "Pending" state is displayed

=== 2022.07.15 - Build 0.0.81

Issue ID Description

21549

CPE Admin > LWM2M > "Enable verification by version"="true" > Group Update > Firmware update task > /3/0/3 value is equal to target file version > Incorrect "Pending" state is displayed

=== 2022.07.14 - Build 0.0.80

Issue ID Description

21538

OneIoT ACS > LWM2M > "Enable verification by version"="true" > Start firmware > Device reboted with new firmware version > Incorrect task state

21535

OneIoT ACS > Settings > LWM2M > Configurations > Lifecycle > "Use discovery for tree root" parameter > Hint > Spelling error

=== 2022.07.12 - Build 0.0.79

Issue ID Description

21525

OneIoT ACS > LWM2M > Firmware update task > /3/0/3 value is equal to target file version > No inform comment (feature for 6.3 but here implemented too)

LWM2M. Enable AES-CBC cipher suites (disabled by default in scandium cipher library); Will be tested by customer;

=== 2022.07.09 - Build 0.0.78

LWM2M remove cpe address map usage; Only one cpe address uri;

LWM2M Settings: Lifecycle.Use discovery for tree root. As workaround for customer for removed discovery functionality;

LWM2M Settings: Enable verification by version. For UG and cases if device doesn’t support fw state update after installation;

=== 2022.06.30 - Build 0.0.77

Issue ID Description

21460

OneIoT ACS > Monitoring > Group with non "Account Info" criteria > Device turns matching to group > No monitoring tasks

Fix of the issue described in bug

  1. If monitor with group activated for current model, acs checks group criteria on each inform from device

  2. Quartz cron task added. Executed at 01:00 every day. It checks and stops monitoring for cpes that are not in group

=== 2022.06.22 - Build 0.0.76

Issue ID Description

20432

CPE Admin > Monitored CPE > Update group > Firmware upgrade task is stuck in "Sent" state

=== 2022.06.15 - Build 0.0.75

Issue ID Description

20413

OneIoT ACS > Settings > LWM2M > Configuration > Network > "Request queue. Request delay timeout (ms) " hint > Typo in hint text

20419

OneIoT ACS > Settings > LWM2M > Configuration > Network > "Request queue. Request delay timeout (ms)" > Unification of position request

LWM2M Fix server start without ipv6 address param (sample: -Dftacs.ipv6.address=[fe80::a0a3:88cc:309f:328a])

Fix lwm2m registry empty address value;

=== 2022.06.09 - Build 0.0.74

LWM2M OMA registry improvements. Add connection and so timeouts in configuration properties (Settings → LWM2M → Configuration → OMA Registry: OMA registry connection timeout (ms), OMA registry socket timeout (ms));

LWM2M OMA registry improvements. If OMA registry address is empty - server won’t try to connect to oma registry;

LWM2M cbor mask change fix. Server restart isn’t required if property changed. Settings → LWM2M → Configuration → Common → CBOR resource mask (regExp)

=== 2022.05.19 - Build 0.0.73

LWM2M Discovery or get opportunity property added for monitoring. Settings → LWM2M → Configuration → Observation → Use GET requests instead of DISCOVER true/false;

LWM2M add property Settings → LWM2M → Configuration → Network → Request queue. Request delay timeout (ms)

  1. In queue mode each request from server may be delayed. L&G specific functionality;

=== 2022.05.18 - Build 0.0.72

Issue ID Description

12085

OneIoT ACS > Monitoring > Running > Edit > "Send to" = Group > Edit group > Change condition > Relevant tasks aren’t sent to device

LWM2M Fix memory leak for L&G devices (not persistent one). Doesn’t need QA; Continue fix 0.0.72

=== 2022.04.08 - Build 0.0.71

Issue ID Description

15199

OneIoT ACS > GUI > System tab > Strange values displayed for ACS MEM usage

=== 2022.04.05 - Build 0.0.70

Issue ID Description

15199

OneIoT ACS > GUI > System tab > Strange values displayed for ACS MEM usage

=== 2022.04.04 - Build 0.0.69

Issue ID Description

15144

OneIoT ACS > Do not insert new CPEs with no serial, product class and OUI

15199

OneIoT ACS > GUI > System tab > Strange values displayed for ACS MEM usage

=== 2022.03.30 - Build 0.0.68

Added xmppServerConnectAlgorithm acs_configuration.xml parameter

Requires acs_configuration.xml update

=== 2022.03.14 - Build 0.0.67

Issue ID Description

15144

OneIoT ACS > Do not insert new CPEs with no serial, product class and OUI

=== 2022.02.17 - Build 0.0.66

Issue ID Description

15091

OneIoT ACS > LWM2M > IPv6 > Any push task > Error in ACS log

=== 2022.02.08 - Build 0.0.65

LWM2M Fix issue with ipv6 for node interaction during the push tasks operation:

When device comes with ipv6 address – server is not able correctly define own address and during the push tasks operation trying to send some request to the wrong address

=== 2022.01.17 - Build 0.0.64

Issue ID Description

13390

OneIoT ACS > Bulk data > Monitoring > Delete monitor > Irrelevant SPV task sent to device

Uncommented cpe_next_session_time functionality on TR069 end session

=== 2022.01.12 - Build 0.0.63

Added external url support to bulk_data.xml

If external url is required add the next attributes to <bulkData> tag in the file:

<bulkData host="https://localhost:8443" external="true" username="user" password="pass">

=== 2021.29.09 - Build 0.0.24

Issue ID Description

11675

OneIoT ACS > LWM2M > Device Profile > Profile applied to device on each "UPDATE REQUEST"

13273

OneIoT ACS > LWM2M > Cluster with LB > Send any task > Unstable system behavior

13335

OneIoT ACS > LWM2M > LG > Monitoring "off" and "on" tasks inconsistent

=== 2021.28.09 - Build 0.0.23

Issue ID Description

13327

OneIoT ACS > Reports > Group update > Big amount of devices > Some devices displayed in "Pending" state

=== 2021.27.09 - Build 0.0.22

Issue ID Description

13237

OneIoT ACS > LWM2M > LG > Registering devices with unescaped characters in JSON payload

  • Added two config. options 'Special JSON characters handling mode' and 'List of special JSON characters' to fine tune processing of unescaped spec. chars

  • use spec. XML chars in lwm2m_resources.xml to add unescapped spec. JSON chars e.g.

<parameter name="/3/0/0" type="STRING" value="Quectel_Ltd&#10;&#13;Quectel_BC66Revision: MTK_2625&#34;"/>

=== 2021.22.09 - Build 0.0.21

Issue ID Description

13273

OneIoT ACS > LWM2M > Cluster with LB > Send any task > Unstable system behavior

13200

OneIoT ACS > LWM2M > Strategy to process tasks on response timeout = REJECT > Response timed out > Task failed

=== 2021.21.09 - Build 0.0.20

LWM2M Add management server param: last server address (ip:port);

Add LWM2M Multinode address support opportunity:

  • Parameter ManagementServer.ConnectionRequestURL: ip1=device ip1[, ip2=device ip2]. ip1 and ip2 is nodes where device have sent reg update or reg requests;

  • added due LB solved different device ports for each node (now any node may access to device if it is available-ONLINE);

LWM2M rebuild tasks mechanism - for some reasons task may occurred in sent state for forever;

LWM2M On device removing - firmware resources was cleared partially;

LWM2M FW if first req failed by timeout (device isn’t responded) - task to pending; fw session invalidated (ready for next attempt); device state changed according strategy;

=== 2021.13.07 - Build 0.0.19

Issue ID Description

13179

OneIoT ACS > acs_configuration.xml > Typo in tag description

Added acs_configuration.xml parameter updateGroupRandomStaticList

Added cpe_serial.location_id field.

On cpe deletion, this field is filling with the value from cpe.location_id

On cpe registration, if ispMode=1 and cpe registered before, cpe.location_id is filling from cpe_serial.location_id

Requires ftacs DB changes

LWM2M FW add logging details for timeout failures;

LWM2M FW add session invalidation on timeout failures;

LWM2M hide error trace details if no connection available for OMA registry communication (singly row that fail to connect is enough);

LWM2M Rebuilt device lifecycle.

1. CpeAdmin Settings → LWM2M → Configuration → Network Setting: Strategy to process tasks on response timeout added new value PENDING_INACTIVE; All cases of that parameter:

PENDING - task will be returned to pending state on timeout;

PENDING_OFFLINE - task will be returned to pending state + cpe.is_online = 0 (offline) on timeout;

PENDING_INACTIVE - task will be returned to pending state + cpe.is_online = 2 (no communication) on timeout;

REJECT - task will be rejected (have some issues with ui rendering, reason is missed;

  1. Device will change state only when smth will attempted to send to (task, request, eny);

  2. cpe.is_online = 2 will be occur only if in lifetime bounds of the device aren’t expired and there is no communication with device are occured;

4. Old property: CpeAdmin Settings → LWM2M → Configuration → Common Device status handling strategy - please ignore. Server won’t use it. New builds won’t create it in db with clear db install, but for existing - please remove it manually;

=== 2021.12.28 - Build 0.0.62

Fixed LF in hub model name issue

=== 2021.12.21 - Build 0.0.61

Issue ID Description

14651

CPE Admin > Settings > Events > Hardcoded Events > Any event > Add URL > Save > An error occured

=== 2021.12.14 - Build 0.0.60

Issue ID Description

12348

OneIoT ACS > License limited by device count > Apply unlimited license > Impossible to register devices

13189

OneIoT ACS > ispMode=1 / 2 > Delete device > "cpe_serial.location_id=null"

13330

OneIoT ACS > LWM2M > LG > More than 68 resources in single task > Task is not generated

13390

OneIoT ACS > Bulk data > Monitoring > Delete monitor > Irrelevant SPV task sent to device

13391

OneIoT ACS > Bulk data > Monitoring > Edit > Unselect at least 2 parameter > Save > Some parameter is absent in the task

14651

CPE Admin > Settings > Events > Hardcoded Events > Any event > Add URL > Save > An error occured

=== 2021.11.23 - Build 0.0.59

Issue ID Description

14631

CPE Admin > Group update > Diagnostic speed test

=== 2021.11.12 - Build 0.0.58

Issue ID Description

14571

OneIoT ACS > New device registered > GPN task for root object not sent

=== 2021.11.11 - Build 0.0.57

Issue ID Description

13382

ACS > Audiocodes > XMPP > DNS-SRV algorithm failure

Moved to the hazelcast-5

Reorganized cpe_parameter_name cache in order to make lower RAM consumption

Requires new hazelcast version

=== 2021.11.10 - Build 0.0.56

Issue ID Description

13422

OneIoT ACS > LWM2M > Online > Restart ACS > Device remains in "Online" state:

LWM2M Security import. Add line number in error message;

LWM2M Security import. Add validation for endpoint masks. Error descr: Line#%s. The specified endpoint mask already exists or matches existing security endpoint mask: %s;

  • fixed timer (every 5 sec) check expired online or inactive cpes by lifetime - device will by moved to offline;

  • add onetime check online cpes on server start - device will be moved to inactive state if online timer active and strategy for taks is PENDING_INACTIVE;

=== 2021.11.05 - Build 0.0.55

SmartHome add processing URL encoded requests for the rest for the FSH;

2021.11.1 0.0.54

Add update queue to FSH MQTT integration module (to prevent 'duplicate entry' when trying to handle two or more updates of the same parameter from the agent)

=== 2021.10.29 - Build 0.0.53

Issue ID Description

13200

OneIoT ACS > LWM2M > Strategy to process tasks on response timeout = REJECT > Response timed out > Task failed

9997

OneIoT ACS > LWM2M > Device profile > GPV tasks for root objects not sent

LWM2M Add lwm2m task timeout strategy: FAILED;

LWM2M Devices without /3/0. New setting: Settings → LWM2M → Configuration → Lifecycle → Manufacturer for devices without /3/0/0 resource default: Unknown Manufacturer;

LWM2M Devices without /3/0. New setting: Settings → LWM2M → Configuration → Lifecycle → Model name for devices without /3/0/1 resource default: Unknown Model;

Property rename Settings → LWM2M → Configuration → Common: Default mechanism to change Resource Instances → Default mechanism to write Resource values

LWM2M Add opportunity to use property Default mechanism to write Resource values not only for add resource operation (Set parameter possible currently too);

=== 2021.10.19 - Build 0.0.52

LWM2M Monitoring check on Notify requests;

LWM2M Beautify configuration properties;

=== 2021.10.18 - Build 0.0.51

LWM2M add check for device lifetime timer (if device responded after timer did work);

=== 2021.10.17 - Build 0.0.50

LWM2M fix monitoring check on registration (+ with bootstrap);

=== 2021.10.16 - Build 0.0.49

LWM2M fix RST on notify after server restart;

=== 2021.10.16 - Build 0.0.48

LWM2M Add filter for monitoring don’t send monitoring on tasks if already run;

=== 2021.10.16 - Build 0.0.47

LWM2M Fix lwm2m caches for monitoring;

=== 2021.10.16 - Build 0.0.46

LWM2M Fix push stop tasks on monitoring stop during notification;

=== 2021.10.15 - Build 0.0.45

LWM2M Fix tree re-asking on registration after bootstrap;

=== 2021.10.15 - Build 0.0.44

LWM2M Ping functionality on timeout;

LWM2M Check profile/monitoring on notify requests;

LWM2M Fix check profile/monitoring on registration requests;

=== 2021.10.12 - Build 0.0.43

Changed CTN service: if mac address not in inform,

acs will get it from cpe.actve_conn_name_id+"MACAddress" parameter,

If not exist ⇒ no CTN store action

=== 2021.10.12 - Build 0.0.42

LWM2M Add queue timeout to reset waiting messages;

LWM2M Add task sent state only when response from device received;

CTN;

=== 2021.10.12 - Build 0.0.42

LWM2M Add update cpe.updated on any device response;

=== 2021.10.11 - Build 0.0.41

LWM2M Re-fix-2 device monitoring check for update requests for online devices with already performed monitoring;

=== 2021.10.11 - Build 0.0.40

Issue ID Description

13327

OneIoT ACS > Reports > Group update > Big amount of devices > Some devices displayed in "Pending" state

LWM2M Re-fix device monitoring check for update requests for online devices with already performed monitoring;

=== 2021.10.11 - Build 0.0.39

LWM2M Fix device monitoring check for update requests for online devices with already performed monitoring;

=== 2021.10.11 - Build 0.0.38

LWM2M Fix monitoring and profile check flag on reg-update;

=== 2021.10.11 - Build 0.0.37

LWM2M Fix cpe data caching;

=== 2021.10.10 - Build 0.0.36

LWM2M Fix task batching for lwm2m;

=== 2021.10.10 - Build 0.0.35

LWM2M sticky tasks fix;

=== 2021.09.10 - Build 0.0.34

LWM2M monitoring tasks only for online devices;

=== 2021.09.10 - Build 0.0.33

LWM2M Device monitoring unstable task behavior;

=== 2021.09.10 - Build 0.0.18

LWM2M Security import template extension (bootstrap name, domain, endpoint mask comparing mode, bs/lwm servers); Details will be provided in additional doc;

FSH Fix isp domain in case if registering device domain was add after server start;

Reviewed LWM2M device lifecycle; Details will be provided in additional doc;

=== 2021.09.07 - Build 0.0.17

LWM2M Security import template extension;

1) Diagnostic task moved to completed after 8 DC event receiving (like Reboot and FactoryReset tasks)

2) Diagnostic from UpdateGroup task name renamed to DiagnosticUpdateGroup (was SetParameterValues)

=== 2021.08.26 - Build 0.0.16

Issue ID Description

13058

OneIoT ACS > LWM2M / USP > Monitoring > All (New and existing) > New device > "Observation "On" task duplicated

=== 2021.08.26 - Build 0.0.15

Issue ID Description

13033

OneIoT ACS > Cluster > LWM2M > Try to register device to specific node > Device is not registered

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

12890

CPE Admin > Group Update > "Reactivation" state > Edit > Save > Update reactivated

=== 2021.08.25 - Build 0.0.14

Issue ID Description

13035

OneIoT ACS > MQTT > FSH > 2-nd CONNECT topic > Device model without one sensor > Device tree is not updated

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

=== 2021.08.21 - Build 0.0.13

Issue ID Description

12981

OneIoT ACS > Cluster > "bulk_data.xml" > Edit host > Host record cleared on other node

Added REGEXP condition to Profile→Event→Parameter and Events→Parameter

=== 2021.08.20 - Build 0.0.12

Issue ID Description

12981

OneIoT ACS > Cluster > "bulk_data.xml" > Edit host > Host record cleared on other node

12962

OneIoT ACS > Bulk data > JSON not supported > Monitoring > Irrelevant value in SPV task sent

13028

OneIoT ACS > Start ACS > IPv6 > Exception in ACS log

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

13036

OneIoT ACS > LWM2M > Monitoring / Device Profile / Events > Observation "On" task is not sent to device

12851

OneIoT ACS > LWM2M > Device Profile > "Download file" sub-tab > Save > Open > Values are not saved

13038

OneIoT ACS > LWM2M > "Device status handling strategy"="Online" > Task with "Request device to connect" > Task sent to device after update request

13036

OneIoT ACS > LWM2M > Monitoring / Device Profile / Events > Observation "On" task is not sent to device

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

13042

OneIoT ACS > LWM2M > Register device > Restart ACS > Update request > Error in ACS log

13041

OneIoT ACS > LWM2M / USP > Oracle > "config_custom_data.xml" > "Observation "On"" task not sent to device

Host in bulk_data.xml must be defined with port, example:

<bulkData host="http://BulkDataHost:Port (e.g. http://friendly-tech.com:8080)">;

=== 2021.08.19 - Build 0.0.11

Issue ID Description

12981

OneIoT ACS > Cluster > "bulk_data.xml" > Edit host > Host record cleared on other node

12962

OneIoT ACS > Bulk data > JSON not supported > Monitoring > Irrelevant value in SPV task sent

12961

OneIoT ACS > Bulk data > Monitoring > Delete monitor > Tasks not created

12960

OneIoT ACS > Bulk data > Monitoring > Remove parameter from monitor > Tasks not created

11197

OneIoT ACS > "config_custom_data.xml" > Relevant "Notification 'Active'" task isn’t generated to device

=== 2021.08.19 - Build 0.0.10

Fix wrong build 0.0.9 (same as previous but built correctly);

=== 2021.08.18 - Build 0.0.9

Issue ID Description

13003

OneIoT ACS > LWM2M > Version 1.1 > JSON > Device Update > Send request for one instance of writable parameter > SPV task failed

12996

OneIoT ACS > Cluster > LWM2M > Device ignores requests > Device responded > Multiple GPV tasks sent to device

12995

OneIoT ACS > LWM2M > Version 1.1 > Device Update > Send request for several instances of writable parameter > Tasks aren’t sent

Fix ipv6 for lwm2m rebuilding process;

=== 2021.08.18 - Build 0.0.8

Issue ID Description

11197

OneIoT ACS > "config_custom_data.xml" > Relevant "Notification 'Active'" task isn’t generated to device

12992

OneIoT ACS > TR-069 / USP > Stop active monitor > Notification task is not sent to device

12983

OneIoT ACS > LWM2M > Resource with writable only parameter > Send request > GPV task generated

12976

OneIoT ACS > LMW2M > Monitoring > Object > Observation task is not sent to device

12851

CPE Admin > LWM2M > Device Profile > "Download file" sub-tab > Save > Open > Values are not saved

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

LWM2M Rebuilding endpoints cache mechanism. Requires check lwm2m functionality in standalone and cluster env-s;

=== 2021.08.13 - Build 0.0.7

Issue ID Description

12976

OneIoT > LMW2M > Monitoring > Object > Observation task is not sent to device

=== 2021.08.12 - Build 0.0.6

Issue ID Description

12966

OneIoT ACS > LWM2M > Register > Deregister > Device is online {

Removed 'PENDING_INACTIVE' option from 'Strategy to process tasks on response timeout' (make sure it is not selected)

Add new 'Common' config option 'Device status handling strategy' for backward compatability, select INACTIVE if you need the device to have inactive/undefined state

}

=== 2021.08.11 - Build 0.0.5

Implemented L+G request. Added 'PENDING_INACTIVE' option to 'Strategy to process tasks on response timeout'. If the 'PENDING_INACTIVE' option is selected the following behavior is applied:

  1. If a request to the device timeouts, the device switches to inactive state (is_online = 2 and the task [responsible for the request] moved to pending state)

  2. While in the inactive state two scenarious are possible

a) the device can be 'pushed' to try again to execute the submitted tasks, if at least one task succedds (i.e. the response is received) the device is considered to be online again (is_online = 1)

b) the device sends the 'Registration Update' / 'Registration' request that switches the state to online and triggers the whole bunch of tasks to be sent to the device (if one of them timeouts goto 1).

Revert LWM2M monitoring to the 'before .i. template like parameters' state (only works with CpeAdmin 6.0 or 6.2 0.0.5)

=== 2021.08.10 - Build 0.0.32

LWM2M Push tasks on online devices on monitoring start/stop;

LWM2M Device deactivation timer;

=== 2021.08.10 - Build 0.0.31

LWM2M remove cpe.updated change on inactive state set;

LWM2M Fix timeout tasks - task was re-sent to device;

LWM2M Allow device registration if initial /3/0 request is failed by timeout;

LWM2M CoAP Ping Timeout (ms) set default to 7 sec. Achieved on customer device;

=== 2021.08.09 - Build 0.0.4

Issue ID Description

11266

ACS > CPE Profile > Avoid profile being sent multiple times

12889

OneIoT ACS > Events > Activate CPEEventMonitor > Deactivate CPEEventMonitor > ACS is stuck

Added bulk data collection support:

Added bulk_data.xml file to jboss configuration folder

<bulkData host="http://BulkDataHost">

<model name="707GR1"/>

<model name="G-2425G-A" path="InternetGatewayDevice.X_ALU-COM_BulkData." />

<model name="HG8145X6" />

<model name="HG8145X5" />

<model name="Telia X2" />

<model name="707GR1" />

</bulkData>

ACS enables bulk data only on the models from this file, if Device.BulkData. object is on another path, path attribute must be used

On monitoring activation (not diagnostic monitoring) on Bulk Data collection supported CPE,

ACS will NOT send SetPeriodic and SetNotification,

instead ACS will do operations according to the flow

Bulk data flow is described in Bulk_Data_Requirements_and_Flow.doc

=== 2021.08.04 - Build 0.0.3

Issue ID Description

12892

OneIoT ACS > Start ACS > Exceptions in ACS log

=== 2021.07.30 - Build 0.0.2

LWM2M Firmware - cpe address change for fota session after reboot;

=== 2021.07.28 - Build b

Issue ID Description

9068

OneIoT ACS > whiteListEnabled=1 > Whitelist with IP range > Device within IP from range isn’t registered

10044

CPE Admin / CSR > USP > Device Update > Device Diagnostic > Create diagnostic > Task isn’t sent to device

11197

OneIoT ACS > "config_custom_data.xml" > Relevant "Notification 'Active'" task isn’t generated to device

9513

OneIoT ACS > "failed.backup.SetParameterValues" ≥ "1" > No "Pending removal&rollback" tasks sent to device

11840

CPE Admin > Settings > USP > Add security > COAP with PUBLIC_KEY > Save > An error occurred

10232

OneIoT ACS > FTCreateDevice > USP > Device is not created

10226

CPE Admin > LWM2M / MQTT / USP > Group Update > "Action" task > Factory reset > Reprovision tasks aren’t generated to device

9522

OneIoT ACS > USP > SPV task completed > Relevant hardcoced event isn’t generated

9453

OneIoT ACS > Events > 1015 - download sent > Empty IP address tag

11606

CPE Admin / CSR > LWM2M / USP > Device Update > Device History > "4 VALUE CHANGE" event > Old value > Irrelevant value is present

8176

CPE Admin > Events > New / Edit > "Send to" with parameter from CPE inform message > Inform received > Event isn’t triggered

11562

OneIoT ACS > Multi-protocols > Updating parameter tree when device switches between protocols

0.0.1

Fix MQTT device not created upon second registration

=== 2021.07.10 - Build 0.0.30

LWM2M Monitoring fix. When monitoring changed for not online cpes - tasks won’t be created on device visit;

=== 2021.07.10 - Build 0.0.29

LWM2M Queue mode fix (old problem with unclear task states and retransmission timeouts);

LWM2M monitoring, firmware, other tasks states rebuild mechanism - missed task identifier during tracking timeouts;

=== 2021.06.10 - Build 0.0.28

Add lwm2m task name batching - LWM2M → Configuration → Network → Task batch size per one processing iteration. Default: 300. Value ⇐ 0 means don’t split to chunks.

=== 2021.06.10 - Build 0.0.27

Add sync lwm2m cache on device state change;

Add device state change according strategy on timeout for coap ping;

Set default value for coap ping timeout to 30 sec;

Add synchronization block for coap ping per device to avoid multiple ping requests till previous was finished;

=== 2021.05.10 - Build 0.0.26

Fix device server address cache synchronization;

Add CoAP timeout support {

see 'CoAP Ping Timeout' and 'Enable CoAP Ping' config options

}

=== 2021.04.10 - Build 0.0.25

Issue ID Description

13386

OneIoT ACS > LWM2M > Monitoring > All (New and existing) > New device > "Observation "On" task is absent

Version 6.1

Latest build: v.6.1

=== 2021.08.05 - Build v.6.1

Issue ID Description

12848

OneIoT ACS > Monitoring > Scheduled to > Running > Edit > Save > Monitor stopped

b 0.0.26

=== 2021.08.02 - Build v.6.1

b 0.0.25

Fix MQTT device not created upon second registration

Fix MQTT manufacturer duplicate entry issue (manufacturer and model name not assigned to MQTT device)

LWM2M Firmware - cpe address change for fota session after reboot;

=== 2021.07.07 - Build v.6.1

b 0.0.24

LWM2M Firmware. Fixed issue with task return to pending state on device registration after FW update (before reporting FW state);

=== 2021.06.24 - Build v.6.1

Issue ID Description

12348

OneIoT ACS > License limited by device count > Apply unlimited license > Impossible to register devices

12293

One-IoT ACS > LWM2M > Ver. 1.0 > Multi instance resources are addressed individually on write requests {

12177

OneIoT ACS > LWM2M > Accepting registration update after registration lifetime got expired

b 0.0.23

see 'Default mechanism to change Resource Instances' config option to specify a mechanism to change Resource Instances

}

=== 2021.06.23 - Build v.6.1

b 0.0.22

LWM2M Firmware. Fix /5/0 resource request after successful updating and registration;

LWM2M Firmware. Add additional debug details;

FSH Added Dusun model;

=== 2021.06.06 - Build v.6.1

b 0.0.21

Fixed issue with WiFi diagnostics on InternetGatewayDevice.LANDevice.i.WiFi.NeighboringWiFiDiagnostic.DiagnosticsState

=== 2021.06.02 - Build v.6.1

b 0.0.20

LWM2M Firmware multi-node support (FW session might be finished on other node after device registration on FW update)

=== 2021.05.26 - Build v.6.1

b 0.0.19

Fixed start monitor timeout on WS

=== 2021.05.20 - Build v.6.1

Issue ID Description

12050

CPE Admin / CSR > Device Update > Custom RPC > Send any request > Request not stored to "Custom RPC" list

12040

OneIoT ACS > Clean install DB > USP > Try to register > Registration isn’t complete

11991

CPE Admin > USP > Software Manager > Install > Manually > Unexpected occurrance happened

b 0.0.18

=== 2021.05.19 - Build v.6.1

Issue ID Description

11924

OneIoT ACS > TR-069 > Oracle > Monitoring > Active monitor > Make changes > Tasks are not generated

11904

OneIoT ACS > USP > Monitor > All (New and existing) > GPV and "Observation "On" tasks duplicated

b 0.0.17

Added support of pattern-like (.i.) parameter names for lwm2m and usp

=== 2021.05.14 - Build v.6.1

Issue ID Description

12018

CPE Admin > Monitoring > Scheduled > Edit > Change activation time > Save > An unexpected occurrence happened

12007

CPE Admin > Oracle > USP / LWM2M > Monitoring > Edit > Save > An error occured

12006

OneIoT ACS > Group Update > 2 conditions > First condition irrelevant > Task not sent

b 0.0.16

=== 2021.05.13 - Build v.6.1

Issue ID Description

12012

OneIoT ACS > TR-069 > Monitoring > Monitor with multiple instances object parameter > Reconnect device > Tasks are sent for specified parameters

12007

CPE Admin > Oracle > USP / LWM2M > Monitoring > Edit > Save > An error occured

12006

OneIoT ACS > Group Update > 2 conditions > First condition irrelevant > Task not sent

11924

OneIoT ACS > TR-069 > Oracle > Monitoring > Active monitor > Make changes > Tasks are not generated

b 0.0.15

=== 2021.05.13 - Build v.6.1

Issue ID Description

11960

OneIoT ACS > Group Update > Download newest firmware > Schedule to > Add new firmware via "File management" > Update gets inactive

b 0.0.14

Improved performance of the UG processing: queries for retrieving UG actions are moved from CPE thread to the main UG thread

Improved performance of the Connection Request processing: queries for retrieving CR parameters optimization

It is recommended to set "worker name="http-worker" io-threads" to the: task-max-threads/8

hazelcast config changed under element <map name="default"> added:

<near-cache>

<in-memory-format>OBJECT</in-memory-format>

<invalidate-on-change>false</invalidate-on-change>

<eviction eviction-policy="NONE" max-size-policy="ENTRY_COUNT" size="5000"/>

<cache-local-entries>true</cache-local-entries>

</near-cache>

=== 2021.05.08 - Build v.6.1

Issue ID Description

11948

OneIoT ACS > LWM2M / USP > Connect group of devices with new model > Only one random device from group is registered

11904

OneIoT ACS > USP > Monitor > All (New and existing) > GPV and "Observation "On" tasks duplicated

11971

OneIoT ACS > LWM2M > Group Update > Condition > IPSO > Condition reached > Task not sent

11984

OneIoT ACS > Group Update > 2 conditions > "AND" logic is applied

11983

OneIoT ACS > Group Update > "Threshold" > Incorrect final update status

b 0.0.13

=== 2021.04.30 - Build v.6.1

b 0.0.12

Performance optimizations of the queries and caches.

Changed standalone_*.xml:

1) removed transport from jboss cache

2) It is recommended to set "worker name="http-worker" task-max-threads" to the: expected concurrent CPEs * 2

=== 2021.04.22 - Build v.6.1

Issue ID Description

11876

CPE Admin > Device Profile > Parameter absent from the device > SPV > Error text contains the "CPE" word

11795

CPE Admin > MQTT / USP > Cluster > Device Update > Device Info > "Trace" button > No trace information

11901

OneIoT ACS > Group Update > Tasks are not generated to device

11766

OneIoT ACS > Windows > TR-069 > Enable encryption > SPV > Encrypted value sent to device

11877

CPE Admin > Windows > Encryption > Any parameter > Encryption isn’t performed

11638

OneIoT ACS > Multi-Domain / Multi-ISP > MQTT / USP / LWM2M > Events > Active event for specific domain > Stop > Tasks sent to irrelevant devices

11833

CPE Admin > Multi-ISP > Device Profile > Child domain > Incorrect profile applied

b 0.0.11

=== 2021.04.20 - Build v.6.1

Issue ID Description

11802

CPE Admin > Monitoring > New > Monitoring with deselected "End Date" check box > Immediately transferred to "Completed" state

11539

ACS > Rejected GPV on root object > Over-writing previous parameter values in DB with NULL

11811

CPE Admin > LWM2M > Device Profile > Advanced view > Virtual parameter > Task failed (params need to be recreated)

11605

CPE Admin > MQTT > Device Update > Device Settings > Edit > Fields are available for editing (params need to be recreated)

10083

CPE Admin > LWM2M > Device profile > Monitoring > Add download task > Condition reached > Task isn’t generated

11638

OneIoT ACS > Multi-Domain / Multi-ISP > MQTT / USP / LWM2M > Events > Active event for specific domain > Stop > Tasks sent to irrelevant devices

11818

OneIoT ACS > Multi-Domain > LWM2M > Events > New > Tasks not created

11824

OneIoT ACS > Multi-ISP > TR-069 > Monitoring > Monitor for specific domain > Stop > Profile periodic isn’t set

11825

CPE Admin > Group Update > Action > Irrelevant condition > Save and Activate > Relevant condition > Update is not executed

11839

CPE Admin > CPE Profile > Two conditions > Profile applied to devices that met only 1 condition

11841

OneIoT ACS > Cluster > Second node > Events > Add task > NSLoopback diagnostic > Tasks are not generated

11833

CPE Admin > Multi-ISP > Device Profile > Child domain > Incorrect profile applied

11820

OneIoT ACS > LWM2M / USP > Monitoring > Stop / Delete monitoring > Observation "Off" task isn’t generated

10401

OneIoT ACS > Group Update > Reactivation > Ends after X reactivations > X reactivations > Incorrect status

11819

OneIoT ACS > Multi-ISP > Specific domain user > Monitoring > Activate monitor > Tasks are not generated

b 0.0.10

=== 2021.04.13 - Build v.6.1

Issue ID Description

11779

CPE Admin > Device Profile > Events > Add task > NSLoopback diagnostics > Save > Error message appears

10191

OneIoT ACS > Partner > Truncate monitoring data

11766

OneIoT ACS > Windows > TR-069 > Enable encryption > SPV > Encrypted value sent to device

11805

CPE Admin > Update CPE > Select a serial > Start trace while connection request

11793

CPE Admin > LWM2M > Device Update > Device History > "4 VALUE CHANGE" > Incorrect old and new values displayed

11776

CPE Admin > Settings > USP > Add new security with several protocols > Save > Open > Only one protocol present

11780

CPE Admin > LWM2M > Device Profile > "4 VALUE CHANGE" event > Edit > Deselect > Event remains selected

11791

CPE Admin > LWM2M > Events > "4 VALUE CHANGE" > Open > Edit parameters for "4 VALUE CHANGE" event > Save > Changes not saved

b 0.0.9

=== 2021.04.06 - Build v.6.1

Issue ID Description

11675

OneIoT ACS > LWM2M > Device Profile > Profile apllied to device on each "UPDATE REQUEST"

11652

OneIoT ACS > LWM2M > Device is offline more than 11 hours > File Download > Add file > Send update > File is missing from list

11680

CPE Admin > LWM2M / USP > Group Update > Irrelevant condition > Condition repeat interval > Update transferred to "Completed" state

11548

OneIoT ACS > "config_custom_data.xml" > MQTT > Custom field is empty

11539

ACS > Rejected GPV on root object > Over-writing previous parameter values in DB with NULL

11759

OneIoT ACS > Windows > ACS WS > enableEncryption > Parameter and its object > Encryption isn’t performed

11638

OneIoT ACS > Multi-Domain / Multi-ISP > MQTT / USP / LWM2M > Events > Active event for specific domain > Stop > Tasks sent to irrelevant devices

11587

OneIoT ACS > Multi-Domain / Multi-ISP > Monitoring > Monitor for specific domain > Stop > Tasks for irrelevant devices are generated

4736

OneIoT ACS > Multi-Domain / Multi-ISP > Monitoring > Monitor for specific domain > Irrelevant CPEs are monitored

10938

OneIoT ACS > ACS WS > getUpdateGroupById > No "id" values in "cpeIds" array in response

11677

CPE Admin > Oracle > Group Update > Create update with "Period 1" checkbox > Tasks aren’t sent to the device

11732

CPE Admin > Oracle > Settings > Whitelist > Serial Number > Check known serial > An error occurred

11640

CPE Admin > USP > Device Update > Device History > ValueChange > Event displayed as a text

11639

OneIoT ACS > LWM2M > Monitoring > New > Save & Activate > Value changed > "Observation "On"" task isn’t generated

b 0.0.8

FSH fix account info merge;

FSH location id update for ispmode=1 (on existing devive/reconnect update location id won’t be changed/reseted to super domain);

Stop/Start/Update monitoring refactoring: decreased using group filtering queries, improved task generating

Added force_qoe_stop.properties

All existing monitorings need to be recreated

=== 2021.03.30 - Build v.6.1

Issue ID Description

11401

OneIoT ACS > Settings > LWM2M > Configuration > Endpoints > Change any default port > Default port is available for registration

10429

OneIoT ACS > USP > Authentication failed > "DemoClass" manufacturer stored in DB

10142

CPE Admin > Settings > USP > Security with more than 1 MTP > Device not registered

11605

CPE Admin > MQTT > Device Update > Device Settings > Edit > Fields are available for editing

9013

OneIoT ACS > USP > "Download" task isn’t generated

11589

OneIoT ACS > Multi-ISP > LWM2M > Device registered in any domain > Change domain for device security > Re-register device > Domain not changed

11671

OneIoT ACS > USP > Group Update > New > Task > Download file / Restore > Task remains in "Pending" state

11516

CPE Admin > LWM2M > "useMultipleSetTasks" = "1" > Group Update > Multiple parameters > Activate > No GPV task

11514

CPE Admin > LWM2M > "useMultipleSetTasks" = "0" > Group update > Multiple parameters > Activate > Composite task sent to device

11671

OneIoT ACS > USP > Group Update > New > Task > Download file / Restore > Task remains in "Pending" state

10218

CPE Admin > USP > Group Update > New > Action > Task completed > Pending state displayed for completed tasks

11669

CPE Admin > USP > Group Update / Device Profile / Events > Tasks > "Get parameter" task is absent

11504

CPE Admin > System > All nodes displayed as down

11539

ACS > Rejected GPV on root object > Over-writing previous parameter values in DB with NULL

10938

OneIoT ACS > ACS WS > getUpdateGroupById > No "id" values in "cpeIds" array in response

11204

OneIoT ACS > QoE Datasources disabled > Start ACS > Exceptions in log

10278

CPE Admin > Settings > ACS Settings > Relevance of "qoeMonitorRecreateTimeout" parameter

11593

CPE Admin > Settings > ACS Settings > Typo in "qoeTruncateMonotoringParameter" parameter

b 0.0.7

=== 2021.03.11 - Build v.6.1

Issue ID Description

11554

OneIoT ACS > retrieveMacAddressesOnNewDeviceArrive = 1 > Register new device > 1011 event is not generated

11204

OneIoT ACS > QoE Datasources disabled > Start ACS > Exceptions in log

11172

OneIoT ACS > Multi-Domain / Multi-ISP > Events > Event for specific domain > Tasks sent to irrelevant CPEs

10401

CPE Admin > Group Update > Reactivation > Ends after X reactivations > X reactivations > Incorrect status

4736

OneIoT ACS > Multi-Domain / Multi-ISP > Monitoring > Monitor for specific domain > Irrelevant CPEs are monitored

10294

OneIoT ACS > Device in blacklist > Try to register > Device is registered

10217

CPE Admin > LWM2M / MQTT / USP > Group Update > "Action" task > Irrelevant condition > Save and Activate > Update ignores condition

11530

OneIoT ACS > Multiple warnings in "server.log"

11423

OneIoT ACS > TR-069 / LWM2M > Firmware name with space > Task failed

10359

OneIoT ACS > Linux > USP > Device Update > List > Trace a device > Register device > Trace data is absent

b 0.0.6

Disable alarm group processing if qoe doesn’t configured;

Fix FSH gateway registration;

=== 2021.03.05 - Build v.6.1

Issue ID Description

11522

OneIoT ACS > Cluster > Start jboss > Exception in hazelcast log

11523

OneIoT ACS > LWM2M > Register device > No GPV tasks for the "Root." parameters

9231

OneIoT ACS > USP > Events > Add sub-task > Condition reached > Task isn’t generated

b 0.0.5

=== 2021.02.25 - Build v.6.1

Issue ID Description

11272

CPE Admin > MQTT > Device Update > Device Info > Reprovision > Tasks from default TR profile sent to device

10808

CPE Admin > LWM2M > Device Update > Delete object > "Delete object" task is absent from device trace

10359

OneIoT ACS > Linux > USP > Device Update > List > Trace a device > Register device > Trace data is absent

11401

OneIoT ACS > Settings > LWM2M > Configuration > Endpoints > Change any default port > Default port is available for registration

10940

CPE Admin > LWM2M > Group Update > Multiple parameters > Activate update > Task isn’t sent

10965

OneIoT ACS > LWM2M / USP / MQTT > whiteListEnabled=1 / whiteListDisabledForExistingCpe=0 > Existing device is operable

10791

CPE Admin > LWM2M > Device Update > Start trace > Register device > Start monitoring > Show trace > Trace log format is corrupted

10142

CPE Admin > Settings > USP > Security with more than 1 MTP > Device not registered

10221

CPE Admin > USP > Group Update > Task with condition > Tasks completed > Pending state displayed for completed tasks

10265

CPE Admin > MQTT > Device Update > Registered device > "Update" button of Emulation tool > Device isn’t updated

10217

CPE Admin > LWM2M / MQTT / USP > Group Update > "Action" task > Irrelevant condition > Save and Activate > Update ignores condition

10083

CPE Admin > LWM2M > Device profile > Monitoring > Add download task > Condition reached > Task isn’t generated

11222

OneIoT ACS > MQTT > Monitoring > New > Save & Activate > "Observation "On"" task isn’t generated

10152

OneIoT ACS > USP / MQTT > Configuration with IPv6 support > Device is not registered

9231

OneIoT ACS > USP > Events > Add sub-task > Condition reached > Task isn’t generated

11423

OneIoT ACS > TR-069 / LWM2M > Firmware name with space > Task failed

11204

OneIoT ACS > QoE Datasources disabled > Start ACS > Exceptions in log

11172

OneIoT ACS > Multi-Domain / Multi-ISP > Events > Event for specific domain > Tasks sent to irrelevant CPEs

11049

OneIoT ACS > "acs_configuration.xml" > Incorrect "enableThingsboard" tag description

10938

OneIoT ACS > ACS WS > getUpdateGroupById > No "id" values in "cpeIds" array in response

10401

CPE Admin > Group Update > Reactivation > Ends after X reactivations > X reactivations > Incorrect status

10294

OneIoT ACS > Device in blacklist > Try to register > Device is registered

10275

OneIoT ACS > TR-069 > Whitelist=1 > CPE is not in whitelist > ParameterKey missing from "PerdiodicInformInterval" SPV

10233

CPE Admin > Oracle > Device Update > Manufacturer > Two identical manufacturers with different registers are present

10197

CPE Admin > Oracle > Device Profile > Create profile with "Backup" > Open profile > "Backup" check-box deselected

10153

CPE Admin > Oracle > Events > USP > Parameters > Add task with condition > Save > Condition and task are not saved

4755

CPE Admin > Multi-Domain / Multi-ISP > CPE Profile > "DEFAULT" profile is absent

4736

OneIoT ACS > Multi-Domain / Multi-ISP > Monitoring > Monitor for specific domain > Irrelevant CPEs are monitored

9837

CPE Admin > Reports > Adding report for CPEs that don’t have neither provision data nor backup file

5557

OneIoT ACS > Implement selective encryption

b 0.0.4

FSH Rest api + soap api refactoring

FSH registration - removed update cust device info (wrong behavior, fsh sends account update itself)

1) Added Trigger Events / Monitoring to External systems

Added rest methods:

http://[ASC_IP]:[ACS_PORT]/rest/subscribeCpeParameterEvent

http://[ASC_IP]:[ACS_PORT]/rest/unsubscribeCpeParameterEvent

http://[ASC_IP]:[ACS_PORT]/rest/subscribeHardcodedEvent

http://[ASC_IP]:[ACS_PORT]/rest/unsubscribeHardcodedEvent

subscribeCpeParameterEvent:

request:

{

"serials": ["",...],

or

"models": ["",...]

"parameters": ["",...],

"urls": ["json:http://localhost:8080/ftacs/ACS",...], URL FORMAT: [type: json or soap]:http://[IP]:[PORT]  example:  json:http://localhost:8080/rest/server

"domain": ""

}

response:

{

"token": ""

}

unsubscribeCpeParameterEvent:

request:

{

"token": ""

}

response:

{

"code": 200,

"description": "OK"

}

subscribeHardcodedEvent:

request:

{

"events": ["",..],   event id

"urls": ["",....], URL reqular format for hardcoded events

"domain": ""

}

response:

{

"code": 200,

"description": "OK"

}

unsubscribeHardcodedEvent:

request:

{

"events": ["",..],   event id

"urls": ["",....], URL reqular format for hardcoded events

"domain": ""

}

response:

{

"code": 200,

"description": "OK"

}

2) Added ACSWebService methods:

disableEncryption(StringArrayWS parameterNames)

enableEncryption(StringArrayWS parameterNames)

3) Added Multi-model Group Update

Changed web services:

ACSWebService.createUpdateGroup

ACSWebService.createAndStartUpdateGroup

ACSWebService.updateUpdateGroup

ACSWebServiceAdditional.getAllUpdateGroups

ACSWebServiceAdditional.getUpdateGroupById

From now:

ug_period.ug_id=update_group.id

ug_reactivate.ug_id=update_group.id

ug_transaction.ug_id=update_group.id

ug_cpe_completed.ug_id=update_group.id

ALL other: ug_*.ug_id=update_group_child.id

Requires UI and DB changes

=== 2021.02.05 - Build v.6.1

Issue ID Description

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

11377

CPE Admin > Settings > LWM2M > Configuration > Firmware > "Firmware update process timeout" > Incorrect default value

11378

CPE Admin > Clean install > Settings > LWM2M > Configuration > Endpoints > Incorrect default value of "CoAP server host" field

10447

LWM2M/MQTT Emulation tool > LWM2M > Group Update > Download file > Firmware Image > Activate > Task failed

b 0.0.3

=== 2021.02.04 - Build v.6.1.0

Issue ID Description

10911

OneIoT ACS > LWM2M > FTDownloadFile > FTP with required username and password > Task not sent

11197

OneIoT ACS > "config_custom_data.xml" > Relevant "Notification 'Active'" task isn’t generated to device

11199

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > Any method > Task not sent

11033

OneIoT ACS > Cluster environment > Settings > ACS Settings > Change any value > Save > Change not applied to all nodes

11367

OneIoT ACS > Cluster > LWM2M / MQTT > Monitoring > New / Edit > Save > An error occured

b 0.0.2

Merged with 6.0

1) Added config_custom_data.xml for account info mappings configuration

Changed configureAccountInfoMapping behaviour: currently <dataList> sent throw this method is final account mapping configuration

(if some column is not sent - it will be deleted)

1) On ACS start: ACS reads from DB current account mapping config and replaces/creates/deletes config_custom_data.xml

2) On WS call: if configuration changed, ACS will change config_custom_data.xml and send topic to other nodes with updated changes

3) On config_custom_data.xml change (only on running ACS, changes on stopped ACS are ignored according to p.1):

If any changes provided - ACS will update DB and send topic to other nodes

4) On topic receive: only config_custom_data.xml will be updated (no DB updates)

2) Added XMPP ServerConnectAlgorithm parameter support:

By default, while configuring XMPP, ACS sends ServerConnectAlgorithm=ServerTable

On GPVR ACS checks if cpe has parameter SupportedServerConnectAlgorithms and if cpe has ServerTable in it value

If cpe doesn’t have ServerTable in supported algorithms, ACS sends DNS-SRV

While configuring XMPP, ACS sends two separate SPVs:

  1. XMPP.Connection.i., ManagementServer.

  2. XMPP.Connection.i.Server.1.*

3) 11110 OneIoT ACS > High load > Group actions activation takes enormous amount of time

Moved to hazelcast, requires standalone_*.xml change

4) The reference to the XMPP.Connection instance without dot at the end (ManagementServer.ConnReqXMPPConnection value)

5) Fixed issue with old cpes deleting cron task. There was an issue with infinite loop on cpe delete

6) Added synchronization cust_device1 userStatus with FSH;

Optimized code for internal iot events;

Removed azure and thingsboard integration from build

updated standalone_*.xml (merged with ver 5)

removed debug mode from standalone.bat

7) fixed queries with cpe.serial: changed 'upper' usage to 'lower'

=== 2021.01.28 - Build v.6.1.0

b 0.0.1

  • reseted version to 6.1.0 and build to 0.0.1

  • LWM2M resource duplication fixes;

  • added FSH REST API service (first release)

  • LWM2M FW: wrapped unexpected reboot without informing downloaded/updated states;

  • LWM2M FW: added opportunity to continue FW on initial reset fail;

  • LWM2M FW: add read /5/0 before process to sync resource; Configurable;

#11341 License initialization fix;

Version 6.0

Latest build: v.6.0

=== 2021.07.27 - Build v.6.0

b 0.0.100

Fix MQTT device not created upon second registration

Fix MQTT manufacturer duplicate entry issue (manufacturer and model name not assigned to MQTT device)

=== 2021.06.24 - Build v.6.0

Issue ID Description

12293

One-IoT ACS > LWM2M > Ver. 1.0 > Ìulti instance resources are addressed individually on write requests {

12177

OneIoT ACS > LWM2M > Accepting registration update after registration lifetime got expired

b 0.0.99

see 'Default mechanism to change Resource Instances' config option to specify a mechanism to change Resource Instances

}

=== 2021.06.22 - Build v.6.0

b 0.0.98

Add Dusun manufacturer for FSH;

=== 2021.04.14 - Build v.6.0

b 0.0.97

Fixed circular reference issue for jio

=== 2021.04.01 - Build v.6.0

b 0.0.96

FSH adoptation for isp mode 1; Cpe will be registered by superDomain, and after registration domain will be changed to configured in MQTT/TR security;

=== 2021.03.11 - Build v.6.0

b 0.0.95

Fix FSH rest hub registration;

=== 2021.03.10 - Build v.6.0

Issue ID Description

11553

OneIoT ACS > retrieveMacAddressesOnNewDeviceArrive = 1 > Register new device > 1011 event is not generated

b 0.0.94

=== 2021.03.09 - Build v.6.0

b 0.0.93

Fix api - sensorsByType for smarthome;

=== 2021.03.03 - Build v.6.0

b 0.0.92

FSH Rest API adopting; For FSH 3.0.8 server;

=== 2021.02.26 - Build v.6.0

b 0.0.91

FSH Rest api + soap api refactoring

FSH registration - removed update cust device info (wrong behavior, fsh sends account update itself)

=== 2021.02.18 - Build v.6.0

Issue ID Description

11436

CPE Admin > Retrieve mode is not working

b 0.0.90

=== 2021.02.15 - Build v.6.0

Issue ID Description

11425

LWM2M/MQTT Emulation tool > LWM2M > Firmware name with space > PULL + HTTP / HTTPS > Download file not started

11423

OneIoT ACS > TR069 / LWM2M > Firmware name with space > Task is failed

11428

CPE Admin > Cluster > LWM2M > Group Update > Task > SPV > Save > An error occurred

b 0.0.89

=== 2021.02.12 - Build v.6.0

Issue ID Description

11423

OneIoT ACS > TR069 / LWM2M > Firmware name with space > Task is failed

b 0.0.88

=== 2021.02.08 - Build v.6.0

b 0.0.87

Fixed multiple instance resource not stored to DB issue (SEWL). ACS failed to store observation result of multiple instance resources in case if

resource values provided (discovered) only via notification mechanism {

1. Add multiple instance resource to lwm2m_resources.xml (e.g. <parameter name="/10263/0/2" type="opaquehex" acs_name="" value="" /> or an equivalent)

2. Register device

3. Deregister device (without deleting it)

4. Start monitoring the specified multinstance resource (CpeAdmin → Monitoring)

5. Replace added parameter in lwm2m_resources.xml to the following (or equivalent) parameters:

<parameter name="/10263/0/2/0" type="opaquehex" acs_name="" value="" />

<parameter name="/10263/0/2/1" type="opaquehex" acs_name="" value="83186d03861a600af6800018ff1affffffff18ff00" />

6. Register device again

Result: Correspond multiple instance resource in CpeAdmin is not emtpy (expecially /10263/0/2/1 = [109, 3, [1611331200, 0, 255, 4294967295, 255, 0]])

}

=== 2021.02.08 - Build v.6.0

Issue ID Description

11386

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > PULL > CoAP > Requested firmware not found

11377

CPE Admin > Settings > LWM2M > Configuration > Firmware > "Firmware update process timeout" > Incorrect default value

11378

CPE Admin > Clean install > Settings > LWM2M > Configuration > Endpoints > Incorrect default value of "CoAP server host" field

0800

200 413

b 0.0.86

=== 2021.02.04 - Build v.6.0

Issue ID Description

11367

OneIoT ACS > Cluster > LWM2M / MQTT > Monitoring > New / Edit > Save > An error occured

b 0.0.85

=== 2021.02.02 - Build v.6.0

b 0.0.84

LWM2M FW Fixed configuration issues with delivery method and protocol;

=== 2021.01.31 - Build v.6.0

b 0.0.83

LWM2M FW add read /5/0 resource before firmware process (configurable);

#11341 License initialization fix;

=== 2021.01.28 - Build v.6.0

Issue ID Description

11323

OneIoT ACS > Cluster > LWM2M > Device Update > File Download > Firmware Image > PULL > CoAP > Incorrect URL sent to device

b 0.0.82

  • LWM2M FW: wrapped unexpected reboot without informing downloaded/updated states;

  • LWM2M FW: added opportunity to continue FW on initial reset fail;

Added cluster support to IoT configurations

=== 2021.01.20 - Build v.6.0

b 0.0.81

#11307: Fix urgent issue with LWM2M FW, related to duplicated resources;

Code optimizations, removing unused folders, dependencies (jms-utils);

=== 2021.01.08 - Build v.6.0

Issue ID Description

10447

CPE Admin > LWM2M > Group Update > Download file > Firmware Image > Activate > Task failed

b 0.0.80

=== 2021.01.05 - Build v.6.0

b 0.0.79

Fix cbor format, autodetection;

=== 2021.01.05 - Build v.6.0

b 0.0.78

LWM2M SEWL/L&G CBOR format fixed; Now possible pass as raw bytes as HEX ready string;

=== 2020.12.16 - Build v.6.0

b 0.0.77

fixed queries with cpe.serial: changed 'upper' usage to 'lower'

=== 2020.12.15 - Build v.6.0

b 0.0.76

Added synchronization cust_device1 userStatus with FSH;

Optimized code for internal iot events;

Removed azure and thingsboard integration from build

updated standalone_*.xml (merged with ver 5)

removed debug mode from standalone.bat

=== 2020.12.09 - Build v.6.0

Issue ID Description

11033

OneIoT ACS > Cluster environment > Settings > ACS Settings > Change any value > Save > Change not applied to all nodes

b 0.0.75

Fixed issue with old cpes deleting cron task. There was an issue with infinite loop on cpe delete

To configure MQTT certificates without changing the jar file:

Use the following environment variables (args) to configure mqtt certificates: ft.mqtt.x509.keystore.path, ft.mqtt.x509.keystore.password, ft.mqtt.x509.pk.password, ft.mqtt.x509.truststore.path, ft.mqtt.x509.truststore.password

Edit "startACS.bat" or another ACS start script to add the relevant variable, e.g:

standalone.bat -c standalone_mysql.xml -b 0.0.0.0 -Djboss.node.name=st50 -Dmqtt.activeApi=api-v1,api-v2 -Dftacs.ip.address=127.0.0.1 -Dftacs.usedDBMS=MySQL -Dft.mqtt.x509.keystore.path=<path>

and -Dft.mqtt.x509.keystore.password=<password>

and -Dft.mqtt.x509.pk.password=<private key password>

and -Dft.mqtt.x509.truststore.path=<path>

and -Dft.mqtt.x509.truststore.password=<password>

=== 2020.12.08 - Build v.6.0

b 0.0.74

  1. The reference to the XMPP.Connection instance without dot at the end (ManagementServer.ConnReqXMPPConnection value)

  2. 11033 OneIoT ACS > Cluster environment > Settings > ACS Settings > Change any value > Save > Change not applied to all nodes

=== 2020.12.04 - Build v.6.0

Issue ID Description

11197

OneIoT ACS > "config_custom_data.xml" > Relevant "Notification 'Active'" task isn’t generated to device

11199

OneIoT ACS > LWM2M > Device Update > File Download > Firmware > Any method > Task not sent

b 0.0.73

Moved to hazelcast, requires standalone_*.xml change

=== 2020.11.30 - Build v.6.0

Issue ID Description

10911

OneIoT ACS > LWM2M > FTDownloadFile > FTP with required username and password > Task not sent

b 0.0.71

1) Added config_custom_data.xml for account info mappings configuration

Changed configureAccountInfoMapping behaviour: currently <dataList> sent throw this method is final account mapping configuration

(if some column is not sent - it will be deleted)

1) On ACS start: ACS reads from DB current account mapping config and replaces/creates/deletes config_custom_data.xml

2) On WS call: if configuration changed, ACS will change config_custom_data.xml and send topic to other nodes with updated changes

3) On config_custom_data.xml change (only on running ACS, changes on stopped ACS are ignored according to p.1):

If any changes provided - ACS will update DB and send topic to other nodes

4) On topic receive: only config_custom_data.xml will be updated (no DB updates)

2) Added XMPP ServerConnectAlgorithm parameter support:

By default, while configuring XMPP, ACS sends ServerConnectAlgorithm=ServerTable

On GPVR ACS checks if cpe has parameter SupportedServerConnectAlgorithms and if cpe has ServerTable in it value

If cpe doesn’t have ServerTable in supported algorithms, ACS sends DNS-SRV

While configuring XMPP, ACS sends two separate SPVs:

  1. XMPP.Connection.i., ManagementServer.

  2. XMPP.Connection.i.Server.1.*

3) 11110 OneIoT ACS > High load > Group actions activation takes enormous amount of time

=== 2020.11.16 - Build v.6.0

b 0.0.70

Fixed exception "Can’t start endpoint"

=== 2020.11.13 - Build v.6.0

Issue ID Description

10802

OneIoT ACS > LWM2M > Monitoring > Cancel observations using reset operation > Clarification request {

b 0.0.69

Cancel observation (now) works as follows:

Case 1: Resource observation is canceled with needReset = 1

  • Client sends Notify (resource is changed) before/after Registration Update, RST is sent in response

  • Client sends Registration Update, GET observe=1 request is sent (once)

Case 2: Resource observation is canceled with needReset = 0

  • Client sends Notify (resource is changed), RST is sent in response

  • GET observe=1 never sent

}

Miscelenious optimizations for load testing

=== 2020.10.16 - Build v.6.0

Issue ID Description

10965

OneIoT ACS > LWM2M / USP / MQTT > whiteListEnabled=1 / whiteListDisabledForExistingCpe=0 > Existing device is operable

10920

OneIoT ACS > LWM2M / USP / MQTT > ACS WS > addCPE > No record added to DB

10911

OneIoT ACS > LWM2M > FTDownloadFile > FTP with required username and password > Task not sent

b 0.0.68

=== 2020.10.09 - Build v.6.0

Issue ID Description

10953

CPE Admin > TR-069 > Device Update > Software Management > Install > Task remains in the sent state

9970

API > LWM2M > FTAddObject > Task failed

9954

CPE Admin > LWM2M > Device Update > Advanced view > Add Object > Input fields for parameters are absent

b 0.0.67

=== 2020.10.06 - Build v.6.0

Issue ID Description

10833

OneIoT ACS > TR-069 / USP > Device Profile > New / Edit > "Backup" selected > Activate > "Backup" isn’t generated

10816

CPE Admin > LWM2M device > "Connectivity statistics" object > "Start" resource > Irrelevant value displayed

10817

OneIoT ACS > LWM2M > Resources > Object with executable resource > "String" value type (object needs to be removed and added again)

10813

OneIoT ACS > LWM2M > Device Update > File Download > Firmware Image > Task not sent (Added trace)

b 0.0.66

Fixed server is not asking for block 1 (SEWL) {

Reproduction steps:

  1. Register an LWM2M device (lifetime=86k)

  2. Start observing resource

  3. Restart the server

  4. Update the observing resource with value > 1024 bytes to trigger blockwise transfer

Expected result: blocks (representing the value of the observing resource) retrieved from the device (correct value is stored to DB)

}

Fixed FOTA failed on boottest because of spaces in the filename (SEWL) {

Reproduction steps:

  1. Add FW file with spaces in the filename

  2. Start FW update (delivery method = PULL)

Expected result: FW update succeeded

}

=== 2020.09.25 - Build v.6.0

Issue ID Description

10898

OneIoT ACS > QoE monitoring > Single device > Select any device > No data to display

10755

CPE Admin > Device Update > Delete device > No entry in “ftacs.cpe_deleted” DB table

b 0.0.65

=== 2020.09.23 - Build v.6.0

Issue ID Description

10734

CPE Admin > Group Update > "Reprovision" task with condition > Irrelevant devices provisioned

10793

OneIoT ACS > "Wi-Fi rescan" exist > Add FCC diagnostics > "8 Diagnostic Complete" with partial diagnostics result > GPV for missing data isn’t sent to device

b 0.0.64

=== 2020.09.21 - Build v.6.0

Issue ID Description

10742

CPE Admin > Multi-Domain / Multi-ISP > Domain user > Settings > External System > Change check-box > Save > Check-box changed to input field

b 0.0.63

=== 2020.09.14 - Build v.6.0

b 0.0.62

Fixed oracle compatibility issue for LWM2M (no resource discovery tasks sent upon registration)

=== 2020.09.07 - Build v.6.0

b 0.0.61

Optimizations for load testing

=== 2020.08.14 - Build v.6.0

Issue ID Description

10630

CPE Admin > Device Profile > Edit > Events > Add or edit any event > Save > All events are absent from profile

10389

OneIoT ACS > System > Licence with device limit > Try to register > "Blocked by License" counter doesn’t work

b 0.0.60

=== 2020.08.05 - Build v.6.0

Issue ID Description

10629

OneIoT ACS > TR-069 > Monitoring > Stop active monitor > Irrelevant "Notification "Reset" task sent to device

10279

CPE Admin > Settings > USP > Configuration > Unclear reduction

10019

CPE Admin > Settings > External system > "Azure" sub-tab > Incorrect "Azure Hub connection string" and "Azure Hub protocol" titles

10631

OneIoT ACS > LWM2M > Group Update > SPV task > Duplicated GPV task generated

10587

OneIoT ACS > License > Limitation by RegisteredCPE / ManagedCPE > Limitation isn’t applied

b 0.0.59

Added multi tenant 'Is integration enabled' Azure configuration option

Updated Azure IoT Hub SDK to 1.24.0 version

=== 2020.08.05 - Build v.6.0

Issue ID Description

10019

CPE Admin > Settings > External system > "Azure" sub-tab > Incorrect "Azure Hub connection string" and "Azure Hub protocol" titles

10027

CPE Admin > Settings > External system > "Azure" sub-tab > "Synchronization timeout (in seconds)" hint sign > Incorrect hint description

10015

CPE Admin > Settings > External system > Incorrect "LifeCell" sub-tab name

10014

CPE Admin > Settings > External system > "Jio" sub-tab > Incorrect "Commons" sub-tab name

10030

CPE Admin > Settings > LWM2M > "Configuration" sub-tab > "Commons" sub-tab > "Device default content type" hint > No spaces in the text

10018

CPE Admin > Settings > External system > "Jio" sub-tab > Incorrect "JIO SCEF Manufacturer" and "JIO SCEF Model Name" field hint names

10601

OneIoT ACS > Group Update > New > Scheduled to > Reactivation > Ends on > Reactivation tasks are not generated

10595

OneIoT ACS > ispMode=0 > Monitoring > An error appears in log file

b 0.0.58

=== 2020.07.30 - Build v.6.0

Issue ID Description

10389

OneIoT ACS > System > Licence with device limit > Try to register > "Blocked by License" doesn’t work

10596

OneIoT ACS > Settings > License > License with "-1" value > License isn’t locked

10587

OneIoT ACS > License > Limitation by RegisteredCPE / ManagedCPE > Limitation isn’t applied

b 0.0.57

Fixed SEWL FW issue (no FW session invalidation)

=== 2020.07.23 - Build v.6.0

Issue ID Description

10389

OneIoT ACS > System > Licence with device limit > Try to register > "Blocked by License" doesn’t work

10559

OneIoT ACS > License > Limitation by "RegisteredCPE" and "RegisteredCPE%Protocol%" > Limitation by "RegisteredCPE" tag isn’t applied

10517

OneIoT ACS > License > Registered devices limit > Limitation isn’t applied

b 0.0.56

LWM2M Log improvements: Registration and FW processes will contain device endpoint name as soon as it become possible to get from device

Add check for general count of the devices. License check alg is (ordered by check steps):

  • if manaaged exceeded - block

  • if registered exceeded - block

  • if managed by protocol exceeded - block

  • if registered by protocol exceeded - block

Log message on the block case: WARN License limit blocking registered[%s] managed[%s] registeredByProtocol[%s] managedByProtocol[%s]

=== 2020.07.20 - Build v.6.0

Issue ID Description

10549

One IoT ACS > "ispMode = "0" > Register device > An error occurs

b 0.0.55

=== 2020.07.16 - Build v.6.0

Issue ID Description

10398

OneIoT ACS > Group Update > New > Scheduled to > Reactivation > Ends on > Incorrect reactivation behavior

10517

OneIoT ACS > License > Registered devices limit > Limitation isn’t applied

10184

ACS > Partner > Truncate monitoring data

b 0.0.54

Config parameters added:

  • qoeTruncateMonotoringParameter (Legal values: 0, 1 | Default value: 0 (disabled) | If 1 - Enable the truncate for selected monitored parameters).

  • qoeTruncateInterval (Legal values: any positive number | Default value: 24 (hours) | TruncateInterval specifies the interval for removal of monitoring data of selected parameters from DB).

ACS WS methods changed: updateMonitoring, createMonitoring added NOT required attribute isTemporary to the name.string element

Implemented qoe data deletion functionality according to the document in bt#10184

=== 2020.07.09 - Build v.6.0

Issue ID Description

10465

CPE Admin > LWM2M > Group Update > Re-run > Task failed > Reactivation > Task not sent to device

10430

CPE Admin > Group Update > Task failed > Incorrect update status

b 0.0.53

=== 2020.07.03 - Build v.6.0

b 0.0.52

Azure fix. Management parameters won’t be updated now in direction Azure -→ FT IoT; Issue with provisioning of the devices;

=== 2020.06.26 - Build v.6.0

b 0.0.51

LWM2M Registration without /3/0 feature - feedback fixes;

=== 2020.06.25 - Build v.6.0

Issue ID Description

10421

OneIoT ACS > LWM2M > Configuration with IPv6 support > Device is not registered

b 0.0.50

=== 2020.06.25 - Build v.6.0

b 0.0.49

LWM2M Registration without /3/0 feature;

Specific setting "Allow device registration without /3/0 resource" added to Settings > LWM2M > Configuration > Commons

=== 2020.06.23 - Build v.6.0

Issue ID Description

10422

OneIoT ACS > Oracle > An error appears after ASC startup

b 0.0.48

Fixed: 10425

=== 2020.06.23 - Build v.6.0

Issue ID Description

10398

CPE Admin > Group Update > New > Scheduled to > Reactivation > Ends on > Incorrect reactivation behavior

b 0.0.47

=== 2020.06.22 - Build v.6.0

b 0.0.46

Fixed: 10378, 10385, 10341

=== 2020.06.18 - Build v.6.0

Issue ID Description

10379

One IoT ACS > "ispMode = "0" > Try to register device > Device isn’t registered

10389

CPE Admin > System > Licence with device limit > Try to register > "Blocked by License" doesn’t work

10360

CPE Admin > System > "CPU Load (%)" > Incorrect "NaN" state displayed

b 0.0.45

Fixed deletion of CPEs with protocolId == null (by Vitaliy)

=== 2020.06.09 - Build v.6.0

b 0.0.44

Fix Azure integration;

=== 2020.05.29 - Build v.6.0

b 0.0.43

Fixed: 10276

=== 2020.05.20 - Build v.6.0

b 0.0.42

Fixed 'java.lang.IllegalStateException: Duplicate key CPELogEventName' issue in the serve logs

=== 2020.05.07 - Build v.6.0

b 0.0.41

fixed: 10141

=== 2020.05.06 - Build v.6.0

b 0.0.40

fixed: 10017, 10025, 10073(some values not saved in oracle db)

=== 2020.05.06 - Build v.6.0

b 0.0.39

LWM2M ipv6;

fixed: 10137

=== 2020.05.05 - Build v.6.0

b 0.0.38

fixed: 10073

=== 2020.05.01 - Build v.6.0

Issue ID Description

10052

CSR > TR-069 > Device Update > Diagnostics > Create diagnostic > Error message appears

10035

CPE Admin / CSR > Device Update > Device Info > Replace > Create device > Replace device > An error occurred

10022

CPE Admin > Device Update > Port Mapping > Add > Save > An error occurred

b 0.0.37

=== 2020.04.27 - Build v.6.0

b 0.0.36

fixed: 10011, 10001, 9961, 9922, 9870, 9856, 9440, 9267, 9263, 7863

=== 2020.04.17 - Build v.6.0

b 0.0.35

fixed: 8796, 9977, 9324

=== 2020.04.17 - Build v.6.0

Issue ID Description

9969

API > FTCreateNonTRHTTPDevice > Incorrect credentials for "config_url" > Response message contains typo

9967

OneIoT ACS > Register device with ACS > "cpe" DB table > Device "location_id" is null

9947

API > Oracle > TR-069 > FTDownloadFile > Task completed > Incorrect response

9920

OneIoT ACS > Multi-ISP > Device profile > Specific domain profile isn’t applied for lower layer domain(s)

4563

OneIoT ACS > MySQL > Monitoring > "Account Info" changed > "ftacs_qoe.cust_device" and / or "cust_device.csv" not updated

b 0.0.34

fixed:

=== 2020.04.13 - Build v.6.0

Issue ID Description

9921

OneIoT ACS > ACS Statistics > Irrelevant "CPE" word

9920

OneIoT ACS > Multi-ISP > Device profile > Specific domain profile isn’t applied for lower layer domain(s)

9910

CPE Admin > Group Update > Edit existsing update with "Download diagnostics" task > An error occurred

9834

OneIoT ACS > Group Update / Events > New / Edit > Tasks > SPV tasks failed

9057

CPE Admin > Group Update > Add vendor log file > Activate > Incorrect file format

7899

OneIoT ACS > Monitoring > "Account Info" with "Latitude" and "Longitude" > No relevant values in "cust_device.csv"

4563

OneIoT ACS > MySQL > Monitoring > "Account Info" changed > "ftacs_qoe.cust_device" and / or "cust_device.csv" not updated

b 0.0.33

fixed:

2020.04.1 v.6.0 b 0.0.32

Dynamic LWM2M (OMA) object definition loader

Fixed: 9553, 9899, 9751, 9855, 9776

=== 2020.03.24 - Build v.6.0

Issue ID Description

9845

OneIoT ACS > CPE Profile > Tasks are completed > "2001 - profile sent" event isn’t generated

9833

CPE Admin / CSR > Oracle > Device Update > List > Trace device > Error message appears

9686

СPE Admin > Group Update > Specific device > Update with "Trace Diagnostic" > Open created update > An error occured

9521

OneIoT ACS > TR-069 > Trigger SPV task > Relevant hardcoded event isn’t generated

9235

CPE Admin > TR-069 / USP > Group Update > "Backup" task > Filename contains "CPE"

9100

OneIoT ACS > addNonTRHTTPCPE > Execute > Device isn’t created

8309

OneIoT ACS > Monitoring > "Account Info" > Some CSV files are not created

b 0.0.31

fixed:

=== 2020.03.18 - Build v.6.0

Issue ID Description

9770

OneIoT ACS > Linux with MySQL > Try to start ACS > ACS isn’t started

b 0.0.30

fixed:

=== 2020.03.17 - Build v.6.0

b 0.0.29

Fixed the folowing bugs:

9393, 9553, 9456, 9455, 9400, 9374, 9169, 9520

=== 2020.03.13 - Build v.6.0

b 0.0.28

Fixed urgent QoE for LWM2M/MQTT/Other from TR protocols;

=== 2020.03.04 - Build v.6.0

Issue ID Description

9521

OneIoT ACS > TR-069 > Trigger SPV task > Relevant hardcoded event isn’t generated

9513

OneIoT ACS > "failed.backup.SetParameterValues" ≥ "1" > No "Pending removal&rollback" tasks sent to device

b 0.0.27

Fixed:

=== 2020.03.02 - Build v.6.0

b 0.0.26

Fixed the folowing bugs:

9378, 9263, 9118, 9269, 8795, 9476, 9257, 9102, 9231, 9221, 9195, 9137

=== 2020.02.18 - Build v.6.0

b 0.0.25

Fixed observation cache invalidation issue (requested by SEWL)

=== 2020.02.04 - Build v.6.0

Issue ID Description

9406

OneIoT ACS > "attempsForSendingMonitorResult>=2" > Trigger event > Incorrect attemp interval

9307

OneIoT ACS > MySQL > Profile with "Apply provision data" and "Request full data tree" > Unnecessary Get tasks

9276

CPE Admin > Device Profile > New / Edit > Profile with inform condition > Profile is not applied

9267

OneIoT ACS > TR-069 > "null" value type > Parameter type change > Parameter value type not changed

9266

CPE Admin > Device Update > Software Manager > Install / Update / Uninstall > Error message appears

9259

OneIoT ACS > Events > New > Task for count of events per duration period > Incorrect functionality

9256

ACS > Events > CPEEventMonitorResult > Count of events per duration period > Irrelevant "CPEEventMonitorResult"

9232

CPE Admin > Events > Add "Upload file" task > Trigger event > URL displayed without filename

9230

CPE Admin > Device Profile > New > Change predefined parameter value > Parameter Monitoring > Any condition > Save > Open > Changed values not saved

9228

OneIoT ACS > TR-069 > Events > New / Edit > Device group based on parameter > Event isn’t triggered

9214

OneIoT ACS > CPE Profile > Task failed > "2003 - profile failed" event isn’t generated

9180

OneIoT ACS > acs_configuration.xml > Incorrect "overwriteProvisionParameters" description

9179

OneIoT ACS > acs_configuration.xml > Incorrect "isNeedToRetrieveTreeOnFirmwareUpgrade" value

9132

OneIoT ACS > qoeDataStoreMode=1 > Exception occurs

9109

OneIoT ACS > "server.log" file > Typo in info message

9100

OneIoT ACS > addNonTRHTTPCPE > Execute > Device isn’t created

9074

OneIoT ACS > XMPP > Send task > Connection request doesn’t work

9068

OneIoT ACS > whiteListEnabled=1 > Whitelist with IP range > Device within IP from range isn’t registered

9001

OneIoT ACS > IspEnable=1 > Incorrect device to domain assignment

8999

OneIoT ACS > IspEnable=2 > Device with ACS User assigned to specific domain > Device not assigned to domain

8887

OneIoT ACS > WSDL > "removeSpecificCPEProvisionData" method > "cpeCustomRPCIds" parameter > Error

8779

CPE Admin > Settings > ACS Settings > Duplicated parameters

8176

CPE Admin > Events > New / Edit > "Send to" with parameter from CPE inform message > Inform received > Event isn’t triggered

7863

OneIoT ACS > CPE Profile > Active profile > Edit > Save > Changes are not applied

7781

OneIoT ACS > Monitoring > Scheduled > Activated > Change "Perform every" > Save > "Not active" state

7601

OneIoT ACS > Update Group > Update with "Stop execution if one of the tasks failed" > Task failed > Update state is "Pending" for device

5936

OneIoT ACS > CPE Profile > Active profile > Edit > Download file > Reset session > No reset session task is generated

b 0.0.24

Fixed:

=== 2020.01.31 - Build v.6.0

b 0.0.23

Merged with ACS b.0.0.202

=== 2020.01.30 - Build v.6.0

b 0.0.22

Add LWM2M SenML encoder - feature of 1.1 ver.;

Optimized account synch for FSH;

=== 2020.01.21 - Build v.6.0

b 0.0.21

Optimized logging.

=== 2020.01.15 - Build v.6.0

b 0.0.20

Compatibility fix with Oracle DB (bug 9227)

26.12.2019 v.6.0 b 0.0.19

LWM2M and MQTT bug fixing

19.12.2019 v.6.0 b 0.0.18

Fixed resources discovery during LWM2M bootstrap

Removed rejected tasks for lwm2m (from now failed only for negative results)

05.12.2019 v. 6.0 b. 0.0.17

Fix queries for oracle;

Fix iotproperties cache;

03.12.2019 v. 6.0 b. 0.0.16

Fixed MQTT module compatability with Oracle database (bug id 8842)

USP firmware update support

Miscellaneous fixes to the Dynamic Configurations module

15.11.2019 v. 6.0 b. 0.0.15

LWM2M Dynamic configuration

ExtSystem Dynamic configuration

Tables for IoT Dyn. Config:

iot_configuration_group

iot_configuration_property

22.10.2019 v. 6.0 b. 0.0.14

Qoe fix

16.10.2019 v. 6.0 b. 0.0.13

USP implementation (support of CoAP, WebSocket, STOMP MTPs)

Miscellaneous fixes to Lwm2m CoAP blockwise transfer

19.09.2019 v. 6.0 b. 0.0.12

Merged with ACS b.0.0.191

17.09.2019 v. 6.0 b. 0.0.11

Merged with ACS b.0.0.190 and QoE UI b.0.0.49

08.07.2019 v. 6.0 b. 0.0.3

LWM2M Californium version up (15 update)

Whitelist for sensors SLT

02.04.2019 v. 6.0 b. 0.0.2

SLT services

Dynamic configuration (only server)

Whitelists for device serials

02.04.2019 v. 6.0.0 b. 0.0.1

Implementation completed. Alpha build of version 6 is released.

Version 5.X

Latest build: v. 5.0.1 b. 0.0.248

=== 06.01.2022 - Build v. 5.0.1 b. 0.0.248

Issue ID Description

14887

ACS > Cluster > "force.qoe.stop.all" = "1" > Tasks are generated by all nodes

=== 24.05.2021 - Build v. 5.0.1 b. 0.0.247

Added near cache support

hazelcast config changed under element <map name="default"> added:

<near-cache>

<in-memory-format>OBJECT</in-memory-format>

<invalidate-on-change>false</invalidate-on-change>

<eviction eviction-policy="NONE" max-size-policy="ENTRY_COUNT" size="5000"/>

<cache-local-entries>true</cache-local-entries>

</near-cache>

=== 14.05.2021 - Build v. 5.0.1 b. 0.0.246

Fixed issue with updateMonitoring.

There was an error on UI call of the updateMonitoring WS in case when any monitoring with more then 1 model exists in the system

=== 30.03.2021 - Build v. 5.0.1 b. 0.0.245

Issue ID Description

11722

ACS > Monitoring > New > Activate > Tasks are not generated

=== 02.03.2021 - Build v. 5.0.1 b. 0.0.244

Issue ID Description

11498

ACS > Monitoring > Start any monitor > GPV task being generated upon every "Perform every interval"

=== 02.03.2021 - Build v. 5.0.1 b. 0.0.243

Issue ID Description

11482

ACS > Cluster > Edit "force_qoe_stop.properties" file on any node > Save > Changes are not synced across all nodes

=== 01.03.2021 - Build v. 5.0.1 b. 0.0.242

Issue ID Description

11482

ACS > Cluster > Edit "force_qoe_stop.properties" file on any node > Save > Changes are not synced across all nodes

=== 25.02.2021 - Build v. 5.0.1 b. 0.0.241

Issue ID Description

11479

ACS > Monitoring > Specific environment > 50k devices > Stop running monitoring > All tasks completed > Open device > Irrelevant checkpoint added

11478

ACS > Specific environment > 50k devices > Stop monitor > Procedure takes up to 64 minutes

=== 23.02.2021 - Build v. 5.0.1 b. 0.0.240

Issue ID Description

11458

ACS > Monitoring > Stop running monitoring > Tasks are not generated

=== 18.02.2021 - Build v. 5.0.1 b. 0.0.239

Issue ID Description

11448

ACS > Active connection parameters mapping > Active connection object is static

=== 17.02.2021 - Build v. 5.0.1 b. 0.0.238

Issue ID Description

11439

ACS > Monitoring > Stop running monitoring > Tasks are not generated

=== 17.02.2021 - Build v. 5.0.1 b. 0.0.237

Issue ID Description

11435

ACS > Monitoring > New > Activate > No data written to "ftacs.qoe_cpe"

All existing monitorings need to be recreated

=== 16.02.2021 - Build v. 5.0.1 b. 0.0.236

Issue ID Description

11435

ACS > Monitoring > New > Activate > No data written to "ftacs.qoe_cpe"

=== 16.02.2021 - Build v. 5.0.1 b. 0.0.235

Issue ID Description

11431

ACS > Monitoring > Monitor with "Not active" state > Activate > Monitor not activated

11430

ACS > Monitoring > New > Activate > Tasks are not generated

=== 12.02.2021 - Build v. 5.0.1 b. 0.0.234

Moved all caches to hazelcast.

On cluster env data from DB will be loaded only once on the first node start with clean hazelcast

Start time on other nodes and restart will be 2-3 minutes

Added WARNING to acs log if Hazelcast is running in buil-in mode

(if there no running hazelcast standalone on the same machine)

Changed built-in Hazelcast in order to run in Tcp mode instead of Udp mode

(it will allow to start standalone hazelcast in the same network without errors of the mismatch mode)

Stop/Start/Update monitoring refactoring: decreased using group filtering queries, improved task generating

Added force_qoe_stop.properties

Requires DB change

=== 09.12.2020 - Build v. 5.0.1 b. 0.0.233

Fixed issue with old cpes deleting cron task. There was an issue with infinite loop on cpe delete

=== 08.12.2020 - Build v. 5.0.1 b. 0.0.232

The reference to the XMPP.Connection instance without dot at the end (ManagementServer.ConnReqXMPPConnection value)

=== 30.11.2020 - Build v. 5.0.1 b. 0.0.231

Added XMPP ServerConnectAlgorithm parameter support:

By default, while configuring XMPP, ACS sends ServerConnectAlgorithm=ServerTable

On GPVR ACS checks if cpe has parameter SupportedServerConnectAlgorithms and if cpe has ServerTable in it value

If cpe doesn’t have ServerTable in supported algorithms, ACS sends DNS-SRV

While configuring XMPP, ACS sends two separate SPVs:

  1. XMPP.Connection.i., ManagementServer.

  2. XMPP.Connection.i.Server.1.*

=== 20.11.2020 - Build v. 5.0.1 b. 0.0.230

Issue ID Description

11160

ACS > Specific CPE > FCC diagnostic > SPA failed > 8 DIAGNOSTIC COMPLETE > GPV tasks are not generated

=== 17.11.2020 - Build v. 5.0.1 b. 0.0.229

Issue ID Description

11133

ACS > Oracle > "config_custom_data.xml" > Mapping isn’t performed

=== 17.11.2020 - Build v. 5.0.1 b. 0.0.228

Issue ID Description

11137

CPE Admin > Monitoring > Activate > An error occurred

11133

ACS > Oracle > "config_custom_data.xml" > Mapping isn’t performed

=== 17.11.2020 - Build v. 5.0.1 b. 0.0.227

Issue ID Description

11133

ACS > Oracle > "config_custom_data.xml" > Mapping isn’t performed

=== 16.11.2020 - Build v. 5.0.1 b. 0.0.226

Added config_custom_data.xml for account info mappings configuration

Changed configureAccountInfoMapping behaviour: currently <dataList> sent throw this method is final account mapping configuration

(if some column is not sent - it will be deleted)

1) On ACS start: ACS reads from DB current account mapping config and replaces/creates/deletes config_custom_data.xml

2) On WS call: if configuration changed, ACS will change config_custom_data.xml and send topic to other nodes with updated changes

3) On config_custom_data.xml change (only on running ACS, changes on stopped ACS are ignored according to p.1):

If any changes provided - ACS will update DB and send topic to other nodes

4) On topic receive: only config_custom_data.xml will be updated (no DB updates)

=== 12.11.2020 - Build v. 5.0.1 b. 0.0.225

Issue ID Description

11111

ACS > ACSWebServiceConfiguration > configureAccountInfoMapping > Mapping by model > Mapping isn’t performed

=== 11.11.2020 - Build v. 5.0.1 b. 0.0.224

Issue ID Description

11112

ACS > AccountInfoMapping > Parameter for model + parameter without model > Specified model mapped only

11111

ACS > ACSWebServiceConfiguration > configureAccountInfoMapping > Mapping by model > Mapping isn’t performed

10063

CPE Admin > CPE Profile > Condition > Add options 'is null' & 'is not null' for account_info fields

=== 10.11.2020 - Build v. 5.0.1 b. 0.0.223

Changed namespace to xmlns:fri="http://www.friendlytech.com/"

=== 06.11.2020 - Build v. 5.0.1 b. 0.0.222

Added feature for mapping device parameters values into account info fields

Requires DB change

1) Added new Web Service Endpoint on address http://IP:PORT/ACSServer-ACS/ACSWebServiceConfiguration

2) Added new methods in ACSWebServiceConfiguration endpoint:

configureAccountInfoMapping

getAccountInfoMapping

configureAccountInfoMapping:

Request example:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ftac="http://ftacs.com/">

<soapenv:Header/>

<soapenv:Body>

<ftac:configureAccountInfoMapping>

<dataList>

<data column="cust1" name="WAN Username" activeConnection="true">

<param manufacturer="ALCL" model="G-140W-C" name="Username" />

<param manufacturer="SERCOMM" model="Smart Box TURBO+" name="X_SC_HostName"/>

</data>

<data column="cust10" name="Inform interval, sec" activeConnection="false">

<param name="InternetGatewayDevice.ManagementServer.PeriodicInformInterval" />

<param name="Device.ManagementServer.PeriodicInformInterval" />

</data>

<data column="cust3" name="SSID" activeConnection="false">

<param name="InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID" />

<param name="InternetGatewayDevice.LANDevice.1.WLANConfiguration.5.SSID" />

<param name="Device.WiFi.SSID.1.SSID" />

<param name="Device.WiFi.SSID.2.SSID" />

</data>

</dataList>

</ftac:configureAccountInfoMapping>

</soapenv:Body>

</soapenv:Envelope>

Response: empty body

getAccountInfoMapping

Request without arguments

Response: as configureAccountInfoMapping request

Mapping feature description:

Mapping initialization:

On device Inform or GetParameterValuesResponse ACS is checking if there any new parameters mapping for device since:

it last connection

or

if device comes with 0 BOOTSTRAP

or

if device is new or created from API

If ACS founds any new mappings for device:

1) If device is new or created from API - ACS creates SetParameterAttributes separate tasks (each parameter in separate message) with active notification

2) If device is not new - ACS checks if parameter is legal for device (exists in cpe_parameter table) and creates active notification task,

in addition ACS makes insert or update of the cust_device1 table according to the mapping rules with values from cpe_parameter table

Mapping processing:

On device Inform or GetParameterValuesResponse ACS is checking if there any mappings for device and saves data if message from device contains it

If empty dataList provided - all customization deleted

If data with exact column provided - all parameters are replaced

If data with some column is not provided - it is not removed or updated

If several parameters for one cust column exists - value will be saved from the first met parameter on device

If manufacturer or/and model changed for existing parameter or parameter removed - ACS sends "notification off" tasks (heavy loading operation)

=== 06.11.2020 - Build v. 5.0.1 b. 0.0.221

Issue ID Description

10063

CPE Admin > CPE Profile > Condition > Add options 'is null' & 'is not null' for account_info fields

Added namespace xmlns:fri="http://friendly-tech.com/" for all (CPEEventMonitorResult, cpeParameterMonitorResult, deviceEventMonitorResult) FTACS events when sendToFEMS=1

=== 28.10.2020 - Build v. 5.0.1 b. 0.0.220

Issue ID Description

11044

ACS > MySQL > Single node > No "Hazelcast" installed > Running > An error occurred

=== 27.10.2020 - Build v. 5.0.1 b. 0.0.219

Issue ID Description

11036

CPE Admin > Cluster environment > Events > New / Edit > Scheduled > Save > Incorrect event state

=== 26.10.2020 - Build v. 5.0.1 b. 0.0.218

Issue ID Description

11036

CPE Admin > Cluster environment > Events > New / Edit > Scheduled > Save > Incorrect event state

11034

ACS > Events > Deactivate event with cpeParameterMonitor > No deactivation tasks generated

11030

CPE Admin > Cluster environment > Settings > Whitelist > Add > Save > Whitelist duplicated

=== 08.10.2020 - Build v. 5.0.1 b. 0.0.217

Moved topics from activemq to hazelcast

Affected functionality:

AcsConfig/Whitelist sync between nodes, UpdateGroup pause, Qoe activation/deactivation

Requires standalone_*.xml change

=== 18.09.2020 - Build v. 5.0.1 b. 0.0.216

Issue ID Description

10855

ACS > FCC diagnostics completed > Device Diagnostics > Start diagnostic > Irrelevant data written into DB

10839

ACS > "Wi-Fi rescan" exist > Add FCC diagnostics > "8 Diagnostic Complete" with partial diagnostics result > GPV for missing data isn’t sent to devic

=== 17.09.2020 - Build v. 5.0.1 b. 0.0.215

1) Fix of issue with UG reactivation

2) Add SPV for DiagnosticState=None after Completed state received

=== 16.09.2020 - Build v. 5.0.1 b. 0.0.214

Issue ID Description

10849

ACS > Monitoring > Value for monitored parameter > Data isn’t stored into DB

10834

CPE Admin > Monitoring > CPE with monitored object > No graphs displayed

=== 15.09.2020 - Build v. 5.0.1 b. 0.0.213

Issue ID Description

10839

ACS > "Wi-Fi rescan" exist > Add FCC diagnostics > "8 Diagnostic Complete" with partial diagnostics result > GPV for missing data isn’t sent to device

=== 03.09.2020 - Build v. 5.0.1 b. 0.0.212

Issue ID Description

10722

ACS > Multi-nodes > Syncing between nodes doesn’t work

9755

ACS > Delete device > Remove provision portal related data

Added hazelcast cache sync support (requires hazelcast running)

=== 01.09.2020 - Build v. 5.0.1 b. 0.0.211

Issue ID Description

10719

ACS > WifiNeighboringDiagnostic > Provision Manager > Parameters don’t get overwritten

Changed standalone xml in order to disable ajp connector (customer request)

=== 14.07.2020 - Build v. 5.0.1 b. 0.0.210

Fixed number of rows requested by acs in queries for UG tasks and RPC methods

=== 06.07.2020 - Build v. 5.0.1 b. 0.0.209

Fixed issue: creating new transaction of type "Profile-" on each Inform. Currently, created only if tasks on profile created

=== 05.06.2020 - Build v. 5.0.1 b. 0.0.208

Issue ID Description

10184

ACS > Partner > Truncate monitoring data

=== 29.05.2020 - Build v. 5.0.1 b. 0.0.207

Issue ID Description

10204

ACS > Whitelist > CPE is not in whitelist > ParameterKey missing in PerdiodicInformInterval SPV

10184

ACS > Partner > Truncate monitoring data

=== 21.05.2020 - Build v. 5.0.1 b. 0.0.206

Issue ID Description

10184

ACS > Partner > Truncate monitoring data

Config parameters added:

  • qoeTruncateMonotoringParameter (Legal values: 0, 1 | Default value: 0 (disabled) | If 1 - Enable the truncate for selected monitored parameters).

  • qoeTruncateInterval (Legal values: any positive number | Default value: 24 (hours) | TruncateInterval specifies the interval for removal of monitoring data of selected parameters from DB).

ACS WS methods changed: updateMonitoring, createMonitoring added NOT required attribute isTemporary to the name.string element

Implemented qoe data deletion functionality according to the document in bt#10184

Requires DB change

=== 05.05.2020 - Build v. 5.0.1 b. 0.0.205

CPE parameters saving changed according to Eldad recommendations:

Please validate with Vadim that all the set value to the bind variables in this merge

are done properly with the correct data type per column, including set null if needed.

example - lets say these CPEs has lots of parameters and many of them are empty,

"value" column in the table is varchar2 and we should set it always as string even if its empty.

e.g. mergeStatementInsert.setNull(ColSourceIndex,java.sql.Types.VARCHAR);

This should be verified for all columns in the merge.

=== 02.04.2020 - Build v. 5.0.1 b. 0.0.204

Fixed 9923 CPE Admin > Update Group > Upload > Vendor Log File <i> > Incorrect file extension sent

Implemented functionality:

On “deleteCPE” method request:

if “totalDelete” set as “true”, ACS must delete relevant data in “ftacs.prov” and “ftacs.cust_device1”

DB tables too. Then relevant device serial number must be written in the “cpe_deleted” table

with current server time.

if “totalDelete” set as “false”, delete device as it was previously.

ACSWebService.deleteCPE changed

Requires DB change

=== 13.02.2020 - Build v. 5.0.1 b. 0.0.203

Issue ID Description

9338

ACS > Update Group > Trace diagnostics > Diagnostic is failed

Hardcoded events loop fix

=== 26.12.2019 - Build v. 5.0.1 b. 0.0.202

Requires db change

Added active connection name ID storing in DB in table cpe

Working only for InternetGatewayDevice

On Inform acs checks if ExternalIPAddress is equals to the IP from ConnectionRequestURL, if so, acs updates cpe.active_conn_name_id

If there no ExternalIP or ConnectionRequestURL - nothing to do

=== 19.12.2019 - Build v. 5.0.1 b. 0.0.201

Issue ID Description

9206

ACS > Update Group > "The newest firmware" > Firmware for device is absent > "Download" task created

9205

ACS > CPE Profile > "The newest firmware" > Firmware with identical software version > "Profile: Download" task created

9204

ACS > CPE Profile > "The newest firmware" > Firmware for device is absent > "Profile: Download" task created

fixed:

Added Skipped cpe status in UG (needed for UI usage on UG report)

=== 13.12.2019 - Build v. 5.0.1 b. 0.0.200

Issue ID Description

9136

ACS > Diagnostic "A" from "Update Group" + diagnostic "B" from "Update CPE" > GPV tasks related to diagnostic "B" are not generated

Added "The newest firmware" feature (according to the "The newest firmware.docx") (requires DB and UI change)

WS changed:

added newest and fileVersion elements to profileWS.profileFileWS and updateGroupWS.downloadTaskWS.cpeFileWS

=== 06.12.2019 - Build v. 5.0.1 b. 0.0.199

Issue ID Description

9133

ACS > Update CPE > Device Diagnostics > Any diagnostic > Create > Incorrect CWMP ID

=== 06.12.2019 - Build v. 5.0.1 b. 0.0.198

Issue ID Description

9133

ACS > Update CPE > Device Diagnostics > Any diagnostic > Create > Incorrect CWMP ID

=== 27.11.2019 - Build v. 5.0.1 b. 0.0.197

1) added additional logging to the UG execution steps

2) fixed issue with cpe_parameter_name saving, now cpe_parameter_name inserts executed in separate transactions

=== 15.11.2019 - Build v. 5.0.1 b. 0.0.196

Issue ID Description

8224

ACS > Reprovision CPE > Issue push

8192

ACS > Update Group > New > GPV,GPA,GPN for "ManufacturerOUI" > Activate > GPV and GPA tasks not generated

1) Added configuration parameter:

<!--Legal values: ejabberd, openfire | Default: openfire | XMPP server type-->

<xmppServerType>openfire</xmppServerType>

In order to support ejabberd server for XMPP CR

2) 8830 ACS > Whitelist > Whitelist cache isn’t synced between nodes FIXED

Requires standalone_*.xml change, topic added:

<jms-topic name="customer1WhiteListSyncTopic" entries="topic/customer1WhiteListSyncTopic java:jboss/exported/jms/topic/customer1WhiteListSyncTopic"/>

3) 8965 ACS > Update group > Random > Task is sent to all devices FIXED

4) standalone_*.xml configuration for clustered env changed:

1. at the socket-binding-group section at the end of file:

<outbound-socket-binding name="jms1">

<remote-destination host="192.168.1.1" port="7600"/>

</outbound-socket-binding>

<outbound-socket-binding name="jms2">

<remote-destination host="192.168.1.2" port="7600"/>

</outbound-socket-binding>

2. subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0" - add http connectors:

<http-connector name="http-jms1" socket-binding="jms1" endpoint="http-acceptor"/>

<http-connector name="http-jms2" socket-binding="jms2" endpoint="http-acceptor"/>

3. change cluster-connection element:

<cluster-connection name="my-cluster" address="jms" connector-name="http-connector" static-connectors="http-jms1 http-jms2"/>

4. change RemoteConnectionFactory element:

<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-jms1 http-jms2" use-global-pools="false" thread-pool-max-size="20"/>

Requires removing of: data, tmp folders

5) 8242 ACS > Update Group > Upload diagnostic > SPV with incorrect upload URL

6) Fixed issue with concurrent merge/delete on cpe_parameter table for the same cpe, now operations waits for unlock from each other

=== 30.10.2019 - Build v. 5.0.1 b. 0.0.195

1) Backup in profile sends after provision (if it is in Profile)

2) Added possibility to not send it to existing devices

WS changed: profileBackup → sendBackupForExisting added

DB changes required

=== 10.10.2019 - Build v. 5.0.1 b. 0.0.194

Issue ID Description

8806

CPE Admin > Events > Add task 'Store in provision' > Values are not pushed to CPE during Reprovision or 0 BOOTSTRAP

=== 25.09.2019 - Build v. 5.0.1 b. 0.0.193

Events → Call External API → method name: if method name starts with "FT", the prefix "http://www.friendly-tech.com/"

will be added to SOAPAction header

=== 24.09.2019 - Build v. 5.0.1 b. 0.0.192

Issue ID Description

8683

CPE Admin > Events > New > Parameters Monitoring > Add "Call API" > Save and Activate > API request is not executed

Added backup functionality to profile. After all profile tasks created, backup task will be send to cpe

DB changed

Requires new UI build

ACSWS changed: profileWS object changet (createProfile and updateProfile WS methods), callApiTask object changed

fixed (requires db and ui change):

=== 18.09.2019 - Build v. 5.0.1 b. 0.0.191

Added new actions in Events/Profile → Parameters Monitoring → Add task:

1) Call api: sends http post request to the defined url, supported keywords: [serial], [oui], [modelname]

2) Add to provision: creates provision parameter with reprovision=2 and new value from CPE

Requires DB change

ACSWS changed: changed WS object - updateGroupTaskWSList

=== 16.09.2019 - Build v. 5.0.1 b. 0.0.190

Added CPE Inform parameters cache synchronization between acs nodes

Each 10 seconds acs sends JMS topic (requires standalone_*.xml change) to other nodes with the list of changes in inform cache

Added to standalone_*.xml:

<jms-topic name="customer1InformParametersSyncTopic" entries="topic/customer1InformParametersSyncTopic java:jboss/exported/jms/topic/customer1InformParametersSyncTopic"/>

=== 30.08.2019 - Build v. 5.0.1 b. 0.0.189

Issue ID Description

8281

ACS > Update Group > Reactivation > Hourly > Incorrect reactivation behavior

=== 26.08.2019 - Build v. 5.0.1 b. 0.0.188

Issue ID Description

8279

ACS > CPE Profile > Rejected tasks > "2002 - profile rejected" event is not generated

8278

ACS > CPE Profile > "Request full data tree from existing CPEs" > Failed tasks > "2003 - profile failed" event is not generated

=== 25.08.2019 - Build v. 5.0.1 b. 0.0.187

Issue ID Description

2001

- profile sent

2002

- profile rejected

2003

- profile failed

Request from customer:

1) API for get Profile ID by Profile name

2) New ACS events: Profile sent

Profile sent (completed) - when all requests are completed

Profile failed - when at least one request failed

Profile rejected - when at least one request rejected

These events should be sent after all

profile related actions have been processed including get all tree (if

applicable). Profile ID should be included in the event content

New events added:

New WS added:

ACSWebServiceAdditional.getProfileIdByName

=== 14.07.2019 - Build v. 5.0.1 b. 0.0.187

Issue ID Description

8238

ACS > Update Group > Diagnostic > Add results to monitoring data > No "monitor_results_{timestamp}.csv" files

8241

ACS > Update Group > IPPing diagnostic task > Update CPE > Diagnostic > Incorrect result displayed

=== 10.07.2019 - Build v. 5.0.1 b. 0.0.186

fixed error with XMPP connection logging in case of xmppServerHostAcs is empty

=== 08.07.2019 - Build v. 5.0.1 b. 0.0.185

Issue ID Description

8225

ACS > Update Group > Diagnostic > 8 diagnostic complete > No relevant GPV tasks

getParameterDataListFromCPE fixed flags values and attributes

fixed issue with beans loading on start

=== 26.06.2019 - Build v. 5.0.1 b. 0.0.184

Issue ID Description

8196

ACS > Update Group > Any diagnostic > No tasks sent to CPE(s)

=== 18.06.2019 - Build v. 5.0.1 b. 0.0.183

XMPP connection fix: connection checked each 20seconds in non-blocking thread (bezeq issue with blocked threads on push)

=== 10.06.2019 - Build v. 5.0.1 b. 0.0.182

Issue ID Description

8189

CPE Admin > Update Group > New > Some GPV and GPA tasks missing when executed

=== 10.06.2019 - Build v. 5.0.1 b. 0.0.181

Issue ID Description

8190

ACS > Update Group > Update with condition > CPE is out of condition > "Condition" task isn’t generated again

=== 07.06.2019 - Build v. 5.0.1 b. 0.0.180

Issue ID Description

8187

ACS > Update Group > Activate update with condition > Update remains in running state for 5 minutes

=== 06.06.2019 - Build v. 5.0.1 b. 0.0.179

Issue ID Description

8183

CPE Admin > Events > Event with custom group > Tasks generated to devices in every subsequent session

8179

ACS > Update Group > Activate update with condition > Tasks are not generated

=== 04.06.2019 - Build v. 5.0.1 b. 0.0.178

Issue ID Description

8175

CPE Admin > Events > New / Edit > "Send to" with parameter from CPE inform message > Inform received > Event isn’t triggered

8156

CPE Admin > Update Group > Update with condition > Condition tasks generated every 5 seconds

8124

CPE Admin > CPE Profile > New > Change predefined parameter value > Parameter Monitoring > Any condition > Save > Open > Changed values not saved

8177

ACS > Events > New / Edit > "Send to" with parameter from CPE inform message > Inform from new CPE > Event triggered

Added diagnostic functionality to UpdateGroup (requires DB change). UpdateGroupWS object changed, new action type added to UpdateGroupWS.tasks

=== 23.05.2019 - Build v. 5.0.1 b. 0.0.177

Issue ID Description

8118

ACS > Events > New > "M UPLOAD" event > Any Task > "M UPLOAD" event received > No tasks generated

Bugs fixed:

=== 14.05.2019 - Build v. 5.0.1 b. 0.0.176

Issue ID Description

8085

CPE Admin > Settings > Events > Edit URLs > Change "FEMS" state > Save > Changes are not saved

8080

CPE Admin > Settings > Events > Edit URLs > Delete > OK > Irrelevant URL displayed

8066

ACS > updateReceiverUrls > Data is not updated in DB table

8057

ACS > Oracle > ChangeHardcodedEvent > Bad SQL grammar

8055

ACS > Oracle > CreateReceiverUrls > Bad SQL grammar

Bugs fixed:

=== 02.05.2019 - Build v. 5.0.1 b. 0.0.175

Requires DB change

1) Added action support in CPE events and Profile events

2) Added condition to the actions (CPE/Profile events and Update Group)

3) CPE event redesign like in ver 6

3) WS changes:

Removed: deactivate/activateProactiveAlerts

Added: createEvent, createAndStartEvent, startEvent, stopEvent, updateEvent, deleteEvent

Changed tasks object in UpdateGroup object

=== 25.03.2019 - Build v. 5.0.1 b. 0.0.174

Transfer tasks deletion added before update group execution for cpe

=== 22.03.2019 - Build v. 5.0.1 b. 0.0.173

1) If any of xmppServerHostAcs or xmppServerHostCpe is empty, xmpp tasks will not generated

2) ACSWebService→changeHardcodedEventsNotification - removed

Added:

ACSWebService→changeHardcodedEvent

ACSWebService→createReceiverUrls

ACSWebService→updateReceiverUrls

ACSWebService→removeReceiverUrls

3) DB tables added: event_hardcoded_url, event_receiver_url

4) Multiple urls can be defined for each hardcoded event. URLs are stored in DB, if there is no URLs for event, old logic with config parameters will be used

The logic of the field event_receiver_url.use_ftacs_ns is the same as logic of the acs_configuration.xml→sentToFEMS

Note: the urls are updated not immediately, there is delay in max 60 seconds

5) Qoe UI changed

=== 28.02.2019 - Build v. 5.0.1 b. 0.0.172

1) Hardcoded events stored in DB (requires DB change)

2) Added new event "1115 - parameters updated in DB". Sentr after inserting to DB of the parameters from CPE is finished

3) Added WS changeHardcodedEventsNotification - it can switch on/off hardcoded event notification, acs config flag enableHardcodedEvents

also works and it value is prior to the DB.

For example enableHardcodedEvents=1, and notification on "1003 - download failed" = 0, notification on download task will not be sent

On other side, if enableHardcodedEvents=0, and notification on "1003 - download failed" = 1, notification on download task also will not be sent

Note: the value of notification is updated not immediately, there is delay in max 60 seconds

=== 20.02.2019 - Build v. 5.0.1 b. 0.0.171

ACSWebServiceAdditional → getCpeParametersForList changed

1) Bulk request for selecting data from cpe_parameter table for all requested cpes and names used

instead of multiple request for each cpe-name pair

2) Requests with empty names list not supported (use getCpeParameter instead)

3) If objects requested, method will not return all child (use getCpeParameter instead),

it will return only attributes for requested object

=== 15.02.2019 - Build v. 5.0.1 b. 0.0.170

For blocked cpe by: white list, black list, license. ACS sending InformResponse and SetParameterValues with periodic * 5 from Default Profile

Note: in case of blocking by Time expiration, ACS will not sent SPV with periodic (only InformResponse)

=== 05.02.2019 - Build v. 5.0.1 b. 0.0.169

While 4 VALUE CHANGE Inform processing, if processParametersAsync is 0, ACS will save all non-TR mandatory parameter values to the cpe_parameter table

=== 11.01.2019 - Build v. 5.0.1 b. 0.0.168

Issue ID Description

7830

ACS > Update Group > Stop running update > Reports > Update group report > Incorrect "Pending" state displayed

=== 10.01.2019 - Build v. 5.0.1 b. 0.0.167

Fixed:

Issue 1: cpe parameters not saved in case of session with GPN, GPV or GPA ends by timeout

Issue 2: If active UG stopped, pending tasks are deleted (it is OK), but cpe state in UG report is pending (it is not OK)

=== 08.01.2019 - Build v. 5.0.1 b. 0.0.166

Issue ID Description

6079

CPE Admin > Monitoring > Scheduled > Stop > Irrelevant stop monitor tasks

=== 19.12.2018 - Build v. 5.0.1 b. 0.0.165

Deadlock fixes:

1) update cpe state and firmware

2) update/delete/merge operations with pending tasks

3) changed quarts configuration in order to handle locks

=== 17.12.2018 - Build v. 5.0.1 b. 0.0.164

Added configuration parameter processParametersAsync

Legal values: 0, 1 | Default value: 1 (enabled) | If 1 - ACS will save parameters from CPE asynchronously after session ending (old behaviour),

if 0 - ACS will save parameters synchronously before empty message sending

=== 11.12.2018 - Build v. 5.0.1 b. 0.0.163

1) XMPP activation on each GPNR which contains [Root].XMPP. object

2) UG fix: initializing updated field in UG cpes

3) overwriteProvisionParameters behaviour changed:

Legal values: 0, 1, 2 | Default value: 1 (enabled with deleting failed) |

If 1 - on setCPEParams ACS will overwrite existent provision parameter with new data (old behaviour) with deleting failed,

if 2 - the same as 1 without deleting failed,

if 0 - ACS will overwrite by the next rule depending on 'reprovision' flag value: 0 NOT overwrites any parameter, 1 (and 2) - overwrites ALL except 0

=== 03.12.2018 - Build v. 5.0.1 b. 0.0.162

Issue ID Description

7725

ACS > Update Group > Period > Activate > Tasks generated for the first set of CPEs only

Bug fixed:

=== 22.11.2018 - Build v. 5.0.1 b. 0.0.161

Fix of the stuck threads while Update Group execution in case of DB failure

=== 11.10.2018 - Build v. 5.0.1 b. 0.0.160

Issue ID Description

7625

ACS > ExternalLog.xml > "enabled=0" > Set "enabled=1" > New "Inform" received > "json" file isn’t updated

=== 10.10.2018 - Build v. 5.0.1 b. 0.0.159

Issue ID Description

7293

ACS > External Trace Enhancement > Ruckus

Feature added:

Configuration file added: externalLog.xml, must be placed in configuration dir

Root element in XML: <externalLog enabled="1" fileName="informOutput.json">

Feature enabling: existent externalLog.xml file with "enable" parameter equals 1

Feature disabling: absent xml or "enable=0"

Log file ("fileName" attribute) will be stored in jboss log dir

File supports "on fly" modifications (like change/create/delete)

=== 08.10.2018 - Build v. 5.0.1 b. 0.0.158

Fixed issue:

1) Retrieve mode + edit tree

2) Register CPE

3) Do "Get Current" on root object

4) Defect: Full tree requested in GPA and GPV

=== 05.10.2018 - Build v. 5.0.1 b. 0.0.157

Bug ID: 7616 ACS > CPE with edited tree > Reregister > No GPV and GPA tasks

=== 04.10.2018 - Build v. 5.0.1 b. 0.0.156

Fixed issues with parser:

On empty message from cpe (after InformResponse):

1) ACS used System.out.println operation for logging,

this operation is blocking operation, on production with big loading, this block produces big cpu usage

2) JAXB parser generates an exception ("Premature end of file"), exception generation produces Thread execution stack generation,

which produces big cpu load. This stack trace is never used by ACs,

because empty message is normal message as a part of TR069 session

The native jaxb classes was extended as a part of this issue fix.

Fixed issue with retrieve mode + edit tree

=== 27.09.2018 - Build v. 5.0.1 b. 0.0.155

1) Added pool for jms connections to perform connection opening as non-blocking operation

2) Removed unneeded stacktrace generation while exception on empty message from cpe. This stack trace may produce long wait times

3) Added additional check for qoe session to avoid unneeded jms topic sending

=== 21.09.2018 - Build v. 5.0.1 b. 0.0.154

On inserting/updating rows in cpe_parameter table in case of exceptions, ACS will do retries (5 max)

=== 12.09.2018 - Build v. 5.0.1 b. 0.0.153

Issue ID Description

7519

ACS > Monitoring > Running > Edit > Change interval > Wait for "qoeMonitorCpeSyncDuration" > No relevant tasks

=== 10.09.2018 - Build v. 5.0.1 b. 0.0.152

Issue ID Description

7515

ACS > getAccountInfo > Incorrect response structure

=== 04.09.2018 - Build v. 5.0.1 b. 0.0.151

Issue ID Description

7495

ACS > WSDL > removeSpecificCPEProvisionData clarification

7442

CPE Admin > Update a CPE > Advanced View > Edit Tree > Get full tree > Irrelevant values recorded to DB

7407

ACS > Profile > Some parameters in profile are not pushed to device

1) Bug fixed:

2) WS method ACSWebServiceAdditional→getAccountInfo added

=== 30.08.2018 - Build v. 5.0.1 b. 0.0.150

1) If UG task is in sent - no CR to the cpe at the end of session

2) fixed prov duplicate in case of the next flow:

overwriteProvisionParameters = false

CPE is deleted

preprov cpe with parameters A (with value V1) and B with reprov=1

preprov cpe with parameter A (with value V2) with reprov=1

connect CPE

Defect: provisions with name A are duplicated

=== 27.08.2018 - Build v. 5.0.1 b. 0.0.149

Using <ParameterPath></ParameterPath> instead of <ParameterPath /> in GPN

=== 13.07.2018 - Build v. 5.0.1 b. 0.0.148

Fixed issue with concurrent threads on GPNR and cpe parameter saving

=== 10.07.2018 - Build v. 5.0.1 b. 0.0.147

Issue ID Description

7166

ACS > Implement "Platform health check"

7295

ACS > acsstats page wrong display of avg.

1) Added REST API, available on domain: http://IP:PORT/rest/*

2) Added system health check method: http://IP:PORT/rest/healthCheck

3) bugs fixed:

4) update_group.reactivation field added. Requires DB changes. When UG state changes to the

Scheduled For Reactivation (4), this field will contain next activation datetime

=== 04.07.2018 - Build v. 5.0.1 b. 0.0.146

Issue ID Description

7265

ACS > "failed.backup.SetParameterValues" = "1" or "0" > Provision Manager > Irrelevant data present

7234

ACS > "overwriteProvisionParameters" = "1" > "failed.backup.SetParameterValues" = "1" > Provision Manager > Provision data

Provision rollback feature:

1) Value V1 for parameter A for cpe C is exists in prov manager (reprovision=1 or 2)

2) New value V2 for parameter A cpe C is sent to the ACS

Case 1: V2 sent with reprovision = 0

ACS waits for task completion and: if task is failed V1 stays in prov manager (ignoring overwriteProvisionParameters flag)

if task is not failed and overwriteProvisionParameters=1, V1 removed from prov manager

Case 2: V2 sent with reprovision=1:

ACS waits for task completion and: if task is failed V1 stays in prov manager (ignoring overwriteProvisionParameters flag)

if task is not failed V2 overrides V1 in prov manager

Case 3: V2 sent with reprovision=2:

ACS overrides V1 with V2 without any checking and task state waiting

Current behavior is independent form failed.backup.SetParameterValues.

The failed.backup.SetParameterValues = 1 must be used if the last correct value of the parameter A must be set on cpe C

Bugs fixed:

=== 03.07.2018 - Build v. 5.0.1 b. 0.0.145

1) Bug fixed: 7234 ACS > "overwriteProvisionParameters" = "1" > "failed.backup.SetParameterValues" = "1" > Provision Manager > Provision data not overwritten

2) Length of parameter value for cpe_parameter_extended table increased from 255 to 1024

3) Added additional attempt to insert row into cpe_parameter_extended table in case of failing the first insert

=== 26.06.2018 - Build v. 5.0.1 b. 0.0.144

Issue ID Description

7084

ACS > "failed.backup.SetParameterValues" = "1" > Provision Manager > Provision related data is cleared

=== 22.06.2018 - Build v. 5.0.1 b. 0.0.143

Issue ID Description

7084

ACS > "failed.backup.SetParameterValues" = "1" > Provision Manager > Provision related data is cleared

6693

ACS > Whitelist > AudioCodes MP26X > IP Range > CPE isn’t allowed to connect to the ACS

6692

ACS > ignoreBootstrapExistingCPE=0 > FTSetDeviceParameters > "0 BOOTSTRAP" > Exception in ACS log appears

6398

ACS > Update CPE > CPE fault > Trace > Child fault code is absent

1) -Dftacs.useCpeNamespaces flag support added. If it is set to 0, namespaces for soap are used the same for all devices, as in v. 4.3,

if absent or 1 - acs uses namespaces which cpe sends in Inform message (ver 5 standard behaviour)

2) changed in standalone_*.xml:

a) JMS topics transport moved from standard http port (usual 8080) to 7600 port

b) Added deployment-timeout="900" (default is 300) to deployment-scanner

c) One more feature added to standalone_mysq.xml, persistence of DB connection, if DB connection fail,

ACS can restore it later without restart ACS.

Using attribute autoReconnect=true in tag connectivity-url

In Oracle it was already configured in the previous versions

3) Added hardcoded event "1114 - setvalue rollback"

4) bugs fixed:

=== 12.06.2018 - Build v. 5.0.1 b. 0.0.142

Removed NoMoreRequests tag from ACS responses

=== 06.06.2018 - Build v. 5.0.1 b. 0.0.140

Issue ID Description

6259

ACS > MySQL > 2 profiles with condition > Profile with higher version is not applied

fixed:

=== 05.06.2018 - Build v. 5.0.1 b. 0.0.139

Issue ID Description

6259

ACS > MySQL > 2 profiles with condition > Profile with higher version is not applied

fixed:

Added WS method:

createOrUpdateCpeSubDevice

Requires DB change

=== 15.05.2018 - Build v. 5.0.1 b. 0.0.138

1) acs_configuration.xml parameters added:

<!-- Legal values: any positive number >= 1 | Default value: 0 (disabled) | if >0 ACS will delete cpes which last connection time is older than N days -->
<dataStoreDaysAmount>400</dataStoreDaysAmount>
<!-- Legal values: 1 - 1000 | Concurrent number of CPEs for old data (older than dataStoreDaysAmount days) deletion -->

<concurrentDataStoreCleanThreads>100</concurrentDataStoreCleanThreads>

Feature description:

Once a day at 02:00AM ACS processes the job for cleaning CPEs data.

CPEs, which last connection date (cpe.updated) is older than dataStoreDaysAmount days will be removed with all existing data (like delete CPE call from UI).

Because of performance purposes the selection of the candidates for removing from cpe table is made by portions of 1000 CPEs for MySQL DB, and 4000 CPEs for Oracle DB.

The number of concurrent calls of the deleteCpe can be setted by concurrentDataStoreCleanThreads

Changing of the dataStoreDaysAmount, concurrentDataStoreCleanThreads can be done in runtime, the changes will be affected before the next portion (1000/4000) CPEs selecting

Additional logging added to standalone_*.xml file, the new log is saving to old_data_clean.log.

2) next tables were removed from deleteCPE procedure:

error_log

cpe_log

cpe_changed_parameter

cpe_pending_task

cpe_completed_task

cpe_failed_task

cpe_rejected_task

cpe_file_history

cpe_provision_history

cpe_diagnostic

cpe_get_diagnostic

cpe_set_diagnostic

transaction

=== 25.04.2018 - Build v. 5.0.1 b. 0.0.137

Issue ID Description

6788

ACS > Monitor > Group based on software version > Activate > Relevant set task are not sent to CPE(s)

=== 17.04.2018 - Build v. 5.0.1 b. 0.0.136

1) Fixed issue with empty SPV while failed.backup.SetParameterValues functionality flow

2) standalone*.xml changing ⇒ topic QoeCpeUpdatedTopic needs to be added

=== 16.04.2018 - Build v. 5.0.1 b. 0.0.135

deleteCPE with deleteFromCpeSerial fix

=== 27.03.2018 - Build v. 5.0.1 b. 0.0.134

Issue ID Description

6679

ACS > Register new CPE > Exception in ACS log appears

=== 23.03.2018 - Build v. 5.0.1 b. 0.0.133

Implemented:

1. As a part of a CPE deletion process and before it is actually deleted,

sync its ftacs.cpe.updated value to ftacs.cpe_serial.updated and then delete the CPE as usual

2. Change deleteCPE method logic in the following way:

If deleteFromCpeSerial is true � delete the CPE record even if it is present in the cpe_serial DB table only

=== 01.03.2018 - Build v. 5.0.1 b. 0.0.132

Issue ID Description

6641

ACS > "ignoreBootstrapExistingCPE" = 0 > Task in "Pending state" > 0 BOOTSTRAP > Value is not changed

6623

ACS > Monitoring > Select "All (New and existing)" > Activate > Register CPE > Deselect "All (New and existing)" > Save > Stop > Monitor stop tasks not generated

=== 01.03.2018 - Build v. 5.0.1 b. 0.0.131

Issue ID Description

6634

ACS > Two monitors for the same CPE > Different interval > Stop > PeriodicInformInterval task is not generated

6627

ACS > "ignoreBootstrapExistingCPE" = 0 or 1 > Task in "Sent state" > 0 BOOTSTRAP > Task is rejected

6625

ACS > "Retrieve Mode" enabled > Add object > "SPV" performed before "GPN" for new object

6624

ACS > acs_configuration.xml > "ignoreBootstrapExistingCPE" > Incorrect default value in description

6623

ACS > Monitoring > Select "All (New and existing)" > Activate > Register CPE > Deselect "All (New and existing)" > Save > Stop > Monitor stop tasks not generated

6621

ACS > "qoeDataStoreMode" = 1 or 2 > Monitoring > Value longer than 1024 symbols > Data is not inserted to DB

6613

ACS > Add object > Duplicated "GPV" tasks

6367

ACS > Linux > "qoeDataStoreMode" = 0 or 2 > Monitoring > Activate > Monitor result file created > Exception received

6270

ACS > Reprovision CPE > "Add Object" with related parameter > GetParameterAtrributes > Incorrect sequence

6074

ACS > Monitoring > More then one running monitor > Same group > Exclude any CPE > Tasks are duplicated

=== 26.02.2018 - Build v. 5.0.1 b. 0.0.130

Issue ID Description

6615

ACS > Monitoring > New > Any group > Deselect "All (New and existing)" > Activate > Register CPE > Monitor related tasks generated

6611

ACS > Monitoring > New / Edit > Custom group > Edit group > Activate > Tasks generated for irrelevant CPE(s)

Push on WS methods with flag "push" will be executed asynchronously

=== 22.02.2018 - Build v. 5.0.1 b. 0.0.129

Issue ID Description

6573

ACS > Update Group > New / Edit > Select "Group filter" > Activate > No tasks sent

=== 17.02.2018 - Build v. 5.0.1 b. 0.0.128

Issue ID Description

6573

ACS > Update Group > New / Edit > Select "Group filter" > Activate > No tasks sent

1) fixed issue with CR thread stuck on big amount of offline CPEs

2) 6574 ACS > Offline CPE > OverwriteProvisionParameters = 0 > Irrelevant data remains in provision manager

3) Delete object fixed stuck in sent (while DeleteObjectResponse handling, status 1 will be handled as status 0)

=== 16.02.2018 - Build v. 5.0.1 b. 0.0.127

1) added configuration parameter:

<!--Legal values: 0, 1 | Default value: 1 (enabled) | If 1 - on setCPEParams ACS will overwrite existent provision parameter with new data (old behaviour), if 0 - ACS will overwrite by the next rule depending on 'reprovision' flag value: 0 NOT overwrites any parameter, 1 (and 2) - overwrites ALL except 0-->

<overwriteProvisionParameters>1</overwriteProvisionParameters>

2) Refactoring on custom view (UG, Events and Qoe filters) update process: currently update is asynchronous and it is not locks UI

for long time.

3) Fixed issue with config synchronization

=== 30.01.2018 - Build v. 5.0.1 b. 0.0.126

1) Fixed issue with dependency injection on linux platform

2) Fixed query for deleting from prov_history tables unneeded data

=== 23.01.2018 - Build v. 5.0.1 b. 0.0.125

Issue ID Description

6422

ACS > Retry group of SPV > "rejectedRetryCount" >= 3 > SPV and tasks are duplicated

6408

ACS > Update Group > Reactivation > No suitable devices > Update transferred into completed state

6376

ACS > Update group > Reactivation > Previous iteration(s) data being lost

=== 17.01.2018 - Build v. 5.0.1 b. 0.0.124

Issue ID Description

1036

- set parameter attributes sent

1037

- setvalue sent

1038

- config rejected

1039

- config sent

1040

- provision rejected

1041

- provision sent

1110

- SPV download sent

1111

- SPV download failed

1112

- SPV download rejected

1113

- SPV download succeeded

6405

ACS > Retry group of SPV > At least two parameters > Incorrect functionality

6402

ACS > SetParameterValues.download.path > CPE Profile > Hardcoded event not generated

6376

CPE Admin > Update group > Reactivation > Previous iteration(s) data being lost

6370

ACS > Events > CPEEventMonitorResult > Count of events per duration period > Incorrect functionality

6273

CPE Admin > Events > Active event > Deactivate > Delete > Stop tasks duplicated

6369

ACS > Update Group > New > "Send to" = "Individual" > Period > Update group applied to all CPEs

6409

ACS > Profile > Task rejected > Add hardcoded event generated

6408

ACS > Update Group > Reactivation > No suitable devices > Update transferred into completed state

6414

ACS > Oracle > Update Group > New > Today / Yesterday > Tasks related to update are not generated

1) Update Group: fixed issue with UG with reactivated option and w/o CPEs for executing on start point

2) Update Group: fixed issue with Today filter, it was depended on DATETIME, but must only on DATE

3) new hardcoded events added:

4) Hardcoded events functionality refactoring

5) bugs fixed:

=== 04.01.2018 - Build v. 5.0.1 b. 0.0.123

1) xmppServerHost - removed. xmppServerHostAcs, xmppServerHostCpe - added

2) XMPP CPE account creation executed asynchronously because of possibility of the big delay with response to CPE

3) Connection request sent concurrently with all supported methods by CPE

4) 6391 ACS > Update CPE > SPV > Incorrect event generated

5) QoE: in case of object monitoring, Passive notifications tasks will not be generated

6) QoE: in case of object monitoring, on prov ACS session (qoeMonitorCpeSyncDuration time triggered or CR called), GPN, GPV and GPA

will be generated for monitored objects

7) QoE: fixed issue with account info change, so that cpe comes out from monitoring by group

8) Added 2 new WS methods: updateAccountInfo, clearAccountInfo

=== 27.12.2017 - Build v. 5.0.1 b. 0.0.122

Issue ID Description

6380

ACS > Non-TR CPE > setCPEParams > Empty value > SPV task is rejected

=== 21.12.2017 - Build v. 5.0.1 b. 0.0.121

1) fixed issue with added csv auth on monitor_results synchronization

2) fixed issue with QoEUI Message Listener, while QOEUIDS is undefined (simple ACS is running)

3) 6360 ACS > Oracle > SPA > More than 1 parameter > Different policy types > SPA task generated for one parameter

=== 20.12.2017 - Build v. 5.0.1 b. 0.0.120

Issue ID Description

6355

ACS > SPV > More than 1 parameter > Different policy types > Incorrect functionality

=== 17.12.2017 - Build v. 5.0.1 b. 0.0.119

1) Fixed CPEs manufacturer updating

2) Added authorization to the csv/ and ftacs/csv URLs. Credentials are the same as ACS WS.

Requires two file replacing in csv.war/WEB-INF (jboss-web.xml, web.xml)

=== 16.12.2017 - Build v. 5.0.1 b. 0.0.118

1) AccessList tag in SetParameterAttributes is sent, by default, in old format: <AccessList/>

To send it in new format: <AccessList soap-enc:arrayType="cwmp:AccessListValueType[0]" />

Startup variable -Dftacs.accessListNewFormat=1 must be used

2) From now required friendly-*.jar libraries placed into the war. JBOSS_HOME\modules\com\friendly can be deleted

3) Requires cpe_parameter_extended.cpe_id to optimize query on parameter deleting

=== 15.12.2017 - Build v. 5.0.1 b. 0.0.117

1) fixed 1112 event

2) fixed "Cpe events on parameter definition with instance functionality"

=== 14.12.2017 - Build v. 5.0.1 b. 0.0.116

Issue ID Description

1033

- set parameter attributes failed

1034

- set parameter attributes rejected

1035

- set parameter attributes succeeded

1) fixed task rejection issue

2) added hardcoded events:

3) fixed cpe parameter event monitor

=== 14.12.2017 - Build v. 5.0.1 b. 0.0.115

1) fixed issue with 111* events

=== 14.12.2017 - Build v. 5.0.1 b. 0.0.114

1) fixed issue with "Retry factory reset/download/upload functionality"

2) fixed issues with new succeeded events

=== 13.12.2017 - Build v. 5.0.1 b. 0.0.113

Issue ID Description

1017

- upload sent

1018

- upload rejected

1019

- factory reset sent

1020

- factory reset failed

1021

- factory reset succeeded

1022

- factory reset rejected

1023

- setvalue rejected

1024

- get parameter values failed

1025

- get parameter values rejected

1026

- get parameter values succeeded

1027

- get parameter names failed

1028

- get parameter names rejected

1029

- get parameter names succeeded

1030

- get parameter attributes failed

1031

- get parameter attributes rejected

1032

- get parameter attributes succeeded

1110

- SPV download sent

1111

� SPV download failed

1112

� SPV download rejected

1113

� SPV download succeeded

1) ACS, Smarthome and QoEUI from now are in one ACS build, each product contains own version and release notes file,

the name of new build: ACSServer_All_5_0.war

2) acs_configuration.xml synchronization by topic added

3) xmppUseSerialAsCpeUsername configuration parameter added (Legal values: 0, 1 | Default value: 1 | If 1 - ACS will send CPEs username as

serial number to the CPE upon XMPP initialization, if 0 - the combination

OUI-ProductClass-SerialNumber will be used)

4) Additional hardcoded events added:

for support of the 1110-1113 events, parameter "SetParameterValues.download.path" from "ftacs_task.properties" must be used

5) Cpe events on parameter definition with instance mask added (Device.Ethernet.Interface.{i}.Stats.PacketsSent)

6) Retry factory reset/download/upload functionality added, timeouts (in seconds) must be defined in ftacs_task.properties in parameters:

reject.timeout.Download

reject.timeout.Upload

reject.timeout.FactoryReset

7) Retry group of SPV feature added, transaction will be retried, instead of single SPV according to the rejection functionality

Feature enabling: reject.resend.SetParameterValues (0 or 1)

8) Pending removal&rollback on failed task added, transaction of the failed task will be rolled back and retried according to the value from:

failed.backup.SetParameterValues

9) current acs build requires additional DB tables: cpe_transaction_repeats, cpe_set_param_backup

=== 01.12.2017 - Build v. 5.0.1 b. 0.0.112

1) UG activation and parameters saving/updating/deleting thread pools are separated.

2) cpeIdsInSession cache becomes asynchronous

3) If UG running with onlineCpesOnly flag and reexecution on offline cpes in proccess ⇒ ACS will not send

Connection Request in case of cpe.updated (last connection) not changed since previous execution

=== 27.11.2017 - Build v. 5.0.1 b. 0.0.111

Fixed stuck in parameter saving point. ACS uses jvm built it synchronize on object policy for preventing concurrent threads

data modification in cpe_parameter table for the same CPE.

But it may be stuck in notifying concurrent threads when current is finished

Added: notify call by ACS instead of jvm waiting

=== 23.11.2017 - Build v. 5.0.1 b. 0.0.110

Fixed issue with CTN store

=== 21.11.2017 - Build v. 5.0.1 b. 0.0.109

Issue ID Description

6243

ACS > "null" value type > Parameter type change > Parameter value type not changed

5989

ACS > Set Parameter Attribute > AccessList tag

1) bugs fixed:

2) Delete not existent parameters from DB on GPNR functionality now is asynchronous to allow next task processing

(due to possible stuck on big DB and loading)

3) Update group period fix. Bug was: in case of period like 01:05 - 02:00 UG executed during all day

=== 20.11.2017 - Build v. 5.0.1 b. 0.0.108

Issue ID Description

5989

ACS > Set Parameter Attribute > AccessList tag

6242

ACS > Registered CPE > Not existing parameter > "null" value types are set

Library updated: JBOSS_HOME_DIR/modules/com/friendly/utils/main/friendly-requestObjects-1.0.jar

=== 17.11.2017 - Build v. 5.0.1 b. 0.0.107

Issue ID Description

4757

ACS > Update Group > "Online devices" > Update group report > Some tasks have an incorrect state

=== 17.11.2017 - Build v. 5.0.1 b. 0.0.106

Issue ID Description

4757

ACS > Update Group > "Online devices" > Update group report > Some tasks have an incorrect state

=== 17.11.2017 - Build v. 5.0.1 b. 0.0.105

Issue ID Description

6230

ACS > Update Group > Offline CPE > "Online devices" checkbox > Activate > Update transferred into completed state

=== 16.11.2017 - Build v. 5.0.1 b. 0.0.104

Issue ID Description

6225

ACS > Monitoring > Running > Edit > Change "Perform every" and delete parameter > Duplicated tasks generated

6223

ACS > Update group > XMPP CPE > Offline CPE > No "Online devices" checkbox > Activate > Update remains in "Running" state

6222

ACS > Update group > XMPP CPE > Offline CPE > Online devices > Activate > Tasks related to update group aren’t deleted

=== 14.11.2017 - Build v. 5.0.1 b. 0.0.103

Issue ID Description

6221

ACS > Update Group > New > 100,5k CPEs > Amount 2000 > Exception in ACS log

=== 14.11.2017 - Build v. 5.0.1 b. 0.0.102

1) ConnectionRequestURL parameter is taken from DB instead of cache

2) Change CPE state while cpe Update Group fix (incorrect array size in case of CPEs count in period equals 2K, 3K ,4K…​.)

3) Change DB query to use lower index on CPE table.

4) DB connectors improvements on standalone_DBType.xml

5) Activation date was changed on any operation while Update Group with periods running, fixed, now update activation date only on activation task/cpe status only. On new Update Group it will come empty.

6) After finishing fist cycle Update Group start next cycle on offline cpe from the first cycle, trying to recheck the status again and resend tasks(Online Devices Only checked). Always run the first group and don’t continue to the full list of CPE’s. Fixed, now it will continue to recheck on all offline CPE’s from the previous cycle.

7) Fixed CPE state moving from pending to completed on Update Group with Reboot or FactoryReset task. After putting pending task it was stuck on this state forever.

=== 10.11.2017 - Build v. 5.0.1 b. 0.0.101

Changed behaviour for UG running with flag "Online CPEs only":

currently tasks will be created, after that push will be executed with t/0 30 seconds,

if CPE is not coming on push → created tasks will be deleted for current cpe

=== 06.11.2017 - Build v. 5.0.1 b. 0.0.100

1) fixed issue with empty parameter name on start on Oracle

2) fixed issue sometime happens on linux with monitoring queries (sql quieries file was duplicated, duplicate removed)

=== 31.10.2017 - Build v. 5.0.1 b. 0.0.99

Issue ID Description

6075

ACS > Monitoring > Monitor with custom group > Edit > Switch to All/Individual > Save > Change isn’t saved

=== 18.10.2017 - Build v. 5.0.1 b. 0.0.98

Issue ID Description

6056

ACS > Oracle > Monitoring > Running > Individual > Edit > All > Save > No relevant tasks

6054

ACS > Oracle > Monitoring > New / Edit > Start creating group > Finish > Error occurred

6044

ACS > Monitoring > Running > Edit > Specific device > 2 models > Delete specific model > Save > No relevant tasks

6034

ACS > Monitoring > Running > Edit > Remove CPE from monitor > Save > Tasks are not sent to removed CPEs

6029

ACS > Oracle > Monitoring > "Apply for new" deselected > Activate > Tasks are sent to new devices

5981

ACS > 2 profiles for same model > Different condition types > Profile with higher version is not applied

=== 16.10.2017 - Build v. 5.0.1 b. 0.0.97

Issue ID Description

6047

ACS > String to boolean > Case sensitive > Parameter type isn’t changed

6045

ACS > Monitoring > Running > Edit > Remove CPE from monitor > Save > Reconnect with "0 BOOTSTRAP" > Monitor related tasks are generated

6044

ACS > Monitoring > Running > Edit > Specific device > 2 models > Delete specific model > Save > No relevant tasks

6035

ACS > Monitoring > Running monitor > Edit > Change "Send to" > Save > Irrelevant "QoE: Set Periodic Inform Interval" duplicated task generated

6034

ACS > Monitoring > Running > Edit > Remove CPE from monitor > Save > Tasks are not sent to removed CPEs

5995

ACS > release notes.txt > Incorrect CPE Admin build is specified

5985

ACS > acs_configuration.xml > urlForSendMonitorResult > Incorrect description

Added new WS: create/delete/updateCustomView - must be called from UI on each operation with custom filters

=== 11.10.2017 - Build v. 5.0.1 b. 0.0.96

Issue ID Description

6040

ACS > Monitoring > 2 monitors for the same model > Stop second monitor > First monitor keep collecting data with irrelevant interval

6036

CPE Admin > Monitoring > 2 models > Delete 1 model > Save > Changes are not applied CPEAdmin

6034

ACS > Monitoring > Running > Edit > Remove CPE from monitor > Save > Tasks are not sent to removed CPEs

6033

CPE Admin > Monitoring > Activate > Edit > "Created" column > Incorrect value is displayed

6029

ACS > Oracle > Monitoring > "Apply for new" deselected > Activate > Tasks are sent to new devices

6022

ACS > Monitoring > "Apply for new" deselected > Stop / Delete monitor > Tasks are sent to new devices

5995

ACS > release notes.txt > Incorrect CPE Admin build is specified

5993

ACS > acs_configuration.xml > retrieveMacAddressesOnNewDeviceArrive > Incorrect description

=== 05.10.2017 - Build v. 5.0.1 b. 0.0.95

Issue ID Description

6027

ACS > CPE with data in provision manager > Update Group > Update group with "CPE Reprovision" action task > No tasks with data from provision manager are generated

6023

ACS > Monitored CPE > Profile applied > Activation monitor tasks are not recreated

6022

ACS > Monitoring > "Apply for new" deselected > Stop / Delete monitor > Tasks are sent to new devices

6021

CPE Admin > Monitoring > Scheduled > Edit > Change to immidiately > Save > Changes are not saved

6008

CPE Admin > Oracle > Monitoring > New > Save Activate > Created monitor displayed in inactive state

6025

CPE Admin > Update Group > Update grout with "CPE Reprovision" action task > Activate > Incorrect display of generated tasks

=== 03.10.2017 - Build v. 5.0.1 b. 0.0.94

1) 6019 ACS > Whitelist does not work

2) 6013 CPE Admin > Monitoring > Scheduled to date > Save > Edit > Save > An error occurred

3) 6010 CPE Admin > Monitoring > Edit > Use "Save" / "Save and Activate" > An error occured CPEAdmin

4) 6008 CPE Admin > Oracle > Monitoring > New > Save Activate > Created monitor displayed in inactive state CPEAdmin

5) 5997 CPE Admin > Monitoring > Activate > Stop > Tasks aren’t generated

=== 22.09.2017 - Build v. 5.0.1 b. 0.0.93

1) QoE monitoring Web Services redesign. Currently all actions on inserting/updating/scheduling are fully on ACS side. Requires: db scripts, CpeAdmin version not older than V5.0.1 Build 8.9.2

=== 12.09.2017 - Build v. 5.0.1 b. 0.0.92

1) 5983 ACS > 1011 event > Empty MAC > Incorrect value specified

2) 5981 ACS > 2 profiles for same model > Different condition types > Profile with higher version is not applied

3) 5978 ACS > "hardcodedEventsProtocol"= SNMP > Trigger event > Event is not trapped by SNMP server

4) Removed spaces from the DeviceIdStruct elements.

5) 5983 ACS > 1011 event > Empty MAC > Incorrect value specified

6) retrieveMacAddressesOnNewDeviceArrive behavior changed: if Device. ⇒ request "Device.Ethernet.Link." object

7) GPV, SPV and GPN messages will be executed without cpe supported methods check

replace module.xml on path: JBOSS_HOME_DIR\modules\org\snmp4j\main\

=== 08.09.2017 - Build v. 5.0.1 b. 0.0.91

1) Removed spaces from the DeviceIdStruct elements

2) Bug 5975 fix

Library updated: JBOSS_HOME_DIR/modules/com/friendly/utils/main/friendly-requestObjects-1.0.jar

=== 27.07.2017 - Build v. 5.0.1 b. 0.0.90

1) Added SPA for notification Active for ConnReqJasbberId parameter

2) Removed redundant ids from XMPP pending tasks

=== 26.07.2017 - Build v. 5.0.1 b. 0.0.89

Fixed libraries issue

=== 26.07.2017 - Build v. 5.0.1 b. 0.0.88

Fixed XMPP issues:

1) Serial in mixed case:

was: Username and Password parameters was sent in original case, instead of in lower, because of xmpp server limitations

now: this values sent in lower

2) Parameter types issue:

was: if there is no XMPP parameters in cpe_parameter_name table, ACS sent all types as 'string',

but there are parameters like Enable or Port, which have different types

now: added hardcoded workaround for parameter types

=== 21.07.2017 - Build v. 5.0.1 b. 0.0.87

Fixed XMPP parameter value:

Parameter: ManagementServer.ConnReqAllowedJabberIDs

Value was: xmppUsername@xmppServerHost

Value fixed to: xmppUsername@xmppServerHost/

=== 21.07.2017 - Build v. 5.0.1 b. 0.0.86

Issue ID Description

5781

ACS > Software Management > Install > Reconnect CPE after manual uninstall > "Softwre modules."

bugs fixed:

=== 20.07.2017 - Build v. 5.0.1 b. 0.0.85

Issue ID Description

5287

CPE Admin > Update CPE > Software Manager > Install > Save > Task is not generated

bugs fixed:

=== 18.07.2017 - Build v. 5.0.1 b. 0.0.84

Issue ID Description

5287

CPE Admin > Update CPE > Software Manager > Install > Save > Task is not generated

bugs fixed:

=== 14.07.2017 - Build v. 5.0.1 b. 0.0.83

Issue ID Description

5733

ACS > XMPP CPE > Register with ACS > Delete CPE > Register CPE again > No relevant XMPP "set" tasks are generated

5734

ACS > "acs_configuration.xml" > "xmppService" and "xmppServerHost" tags duplicating each other

5735

ACS > "acs_configuration.xml" > Irrelevant "xmppService" / "xmppServerHost" tag description

bugs fixed:

=== 07.07.2017 - Build v. 5.0.1 b. 0.0.82

1. XMPP settings set on CPE changed. Currently, there is no need to create special profile for XMPP settings.

They will sent automatically if ACS detects XMPP feature on CPE. The flow is the next:

1) Check parameters from Inform for containing any XMPP parameter

2) If so ⇒ create SPV tasks with priority 1 (highest) with XMPP settings. Use Connection.1. and Server.1. instances for this

3) While GPNR processing check XMPP parameters exists, if so, check if set tasks have been generated during Inform proccessing

4) If so, check if Connection.1. and Server.1. objects are exists. If one of them not ⇒ delete failed set tasks for XMPP settings

and generate new one with required AddObject and Sets

5) If not, generate required AddObject and Set tasks

2. Added checking for enabling RPC method before sending task:

1) If CPE doesn’t support message which need to be generated during current task processing ⇒ delete task and go to the next

2) This is not for GetRPCMethods task. This task will be generated without any checkings

3) Added RPC Methods list udating during Custom RPC response processing

3. Changed functionality for identifying if existing CPE is created from API or created before by TR flow:

was - check if any parameter in cpe_parameter table exists.

become - check for cpe methods containing in cache, if not ⇒ in DB

4. Fixed bug: 5648 ACS > Update group > Task execution stopped

Bug reproduced with UG with big amount of CPES (~1 000 000) and stopped execution on the middle on the point when ACS

identifying if there new cpes for the current update (for example, which comes from custom view filter)

The main cause of the bug is attempt to delete big array (~500 000) from another big array (~1 000 000).

This operation came to the stuck in JVM

Changes: added optimization during working with big arrays

=== 21.06.2017 - Build v. 5.0.1 b. 0.0.81

ROLLBACK: 5204 ACS > External trace > server.log > Line by line trace information can’t be configured

Changes in standalone_*.xml:

1) Log to the file (will be saved in log directory):

<!-- ============================================ -->

<!-- Log for message tracing -->

<!-- ============================================ -->

<file-handler name="EXTERNAL_TRACE_LOG">

<formatter>

<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %m%n%n"/>

</formatter>

<file relative-to="jboss.server.log.dir" path="externalTrace.log"/>

<append value="true"/>

</file-handler>

OR:

2) Log to the SYSLOG:

<!-- ============================================ -->

<!-- Log for message tracing -->

<!-- ============================================ -->

<custom-handler name="EXTERNAL_TRACE_LOG" class="org.jboss.logmanager.handlers.SyslogHandler" module="org.jboss.logmanager">

<formatter>

<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %m%n%n"/>

</formatter>

<properties>

<property name="appName" value="ACS"/>

<property name="serverHostname" value="localhost"/>

<property name="facility" value="LOG_AUDIT"/>

</properties>

</custom-handler>

=== 14.06.2017 - Build v. 5.0.1 b. 0.0.80

Issue ID Description

5572

ACS > Custom RPC > SetParameterAttributes > AccessList array type attribute is present > Incorrect attribute sent

=== 12.06.2017 - Build v. 5.0.1 b. 0.0.79

CustomRPC for the SPA, GPA, GPV

=== 25.05.2017 - Build v. 5.0.1 b. 0.0.78

1) 5287 CPE Admin > Update CPE > Software Manager > Install > Save > Task is not generated Defect 2 fixed

2) Added CTN config support

3) CustomRPC for the SPV fix. Note: template in UI need to be changed, ParameterKey tag must be added with empty value: <ParameterKey></ParameterKey>

=== 24.05.2017 - Build v. 5.0.1 b. 0.0.77

1) -Dftacs.multiDomain - removed

2) acs_comfiguration.xml parameter ispMode added

3) ACS will overwrite cpe.location_id only in case of ispMode=2 and acs user locationId is not equal to the cpe locationId

=== 19.05.2017 - Build v. 5.0.1 b. 0.0.76

Issue ID Description

5411

ACS > WebServiceAdditional > getCPEParameters > Duplicate method for miltiple CPEs - getCpeParametersForList method added

5369

ACS > addNonTRHTTPCPE > Unexisting domain ID > CPE created

5366

ACS > addNonTRHTTPCPE > Empty "serialNumber" tag > CPE unexpectedly created

changes in jboss dir:

/modules/org/apache/axis/main/module.xml replaced in release

=== 11.05.2017 - Build v. 5.0.1 b. 0.0.75

Issue ID Description

5359

ACS > SPA > SPA for the same parameter > Pending tasks are not replaced

5308

CPE Admin / CSR > Update CPE > Custom RPC > GetParameterNames > Request is marked as failed

5191

CPE Admin > Multi-Domain / Multi-ISP > Domain with subdomain > Update group > Subdomain CPEs are ignored by update

1) Bugs fixed:

2) -Dftacs.usedDBMS not used, current DB type identified from -c parameter

3) If multi domain is used, -Dftacs.multiDomain=1 must be added to the start parameters of the ACS.

If it is absent (by default) the system is working as previous

4) Multi domain feature is also working for the profiles, the current profile priority logic is:

1. Profile with the SAME domain as cpe is top priority (profile in A.B.C will be applied to the A.B.C cpe)

2. Profile with the domain in nearest hierarchy is used

(we have 2 profiles in: A and A.B domains, and cpe in A.B.C domain, profile from A.B will be used)

3. Profile version and condition works as previous, but in case of one level

(2 profiles: A.B with ver=1.0.1 and A with ver=1.0.9 and cpe in A.B or A.B.*, A.B will be used)

for conditions: if conditioned profile is in A, but there is non condition profile in A.B - A.B will be used

=== 07.05.2017 - Build v. 5.0.1 b. 0.0.74

Non TR HTTP processing changes:

1) prop file on ftp will be created on each call of the addNonTRHTTPCPE

2) Result file name always: serial.cfg

=== 26.04.2017 - Build v. 5.0.1 b. 0.0.73

Issue ID Description

5305

ACS > Oracle > "addNonTRHTTPCPE" > Create "IP Phone" CPE > Perform any change > Exception in ACS log

Bugs fixed:

=== 25.04.2017 - Build v. 5.0.1 b. 0.0.72

Added locationId to the addNonTRHTTPCPE

=== 20.04.2017 - Build v. 5.0.1 b. 0.0.71

Issue ID Description

5290

ACS > Registered devices license limit reached (100% registered devices) > Deleted devices cannot register with ACS

Bugs fixed:

=== 20.04.2017 - Build v. 5.0.1 b. 0.0.70

Issue ID Description

5290

ACS > Registered devices license limit reached (100% registered devices) > Deleted devices cannot register with ACS

Bugs fixed:

=== 19.04.2017 - Build v. 5.0.1 b. 0.0.69

Added support for non TR HTTP devices

1) added WS method addNonTRHTTPCPE

2) this cpe supports only the following methods: SPV/GPV/GPN/GPA

3) added new check on CPE type before pushing a CPE, if CPE is HTTP based - process tasks as http based CPE

=== 06.04.2017 - Build v. 5.0.1 b. 0.0.68

Issue ID Description

5156

API > Multi-domain / Multi-ISP > FTCreateDevice > Impossible to create device for subdomain with user associated with a higher-level domain

Bugs fixed:

=== 05.04.2017 - Build v. 5.0.1 b. 0.0.67

Issue ID Description

5204

ACS > External trace > server.log > Line by line trace information can’t be configured

5163

ACS > addCPEaddCPEToBlackList > "manufacturer" and "model" fields are mandatory

Bugs fixed:

=== 05.04.2017 - Build v. 5.0.1 b. 0.0.66

Issue ID Description

5204

ACS > External trace > server.log > Line by line trace information can’t be configured

5203

ACS > WebService > createProfile > Condition > Inform > Profile not applied

Bugs fixed:

=== 28.03.2017 - Build v. 5.0.1 b. 0.0.65

Issue ID Description

5177

ACS > FTCreateDevice > Manufacturer and modelname are not in whitelist > Java exception thrown

Bugs fixed:

=== 22.03.2017 - Build v. 5.0.1 b. 0.0.64

Issue ID Description

5125

ACS > WebServiceAdditional > getCPEParameters > requestCPE = 0 > Ignore nonexistent parameters

5122

ACS > FTCreateDevice > Java exception thrown

5118

ACS > CPE Profile > Incorrect task sequence ACS

4916

CPE Admin > CPE Profile > Condition > User’s Info > Activate > Not applied to matching CPE

4912

ACS > Blacklist column "manufacturer" is case-sensitive

4863

CPE Admin > Update Group > New / Edit > Backup > Irrelevant user displayed

Bugs fixed:

Table added: qoe_cpe_parameter_name

Library updated: JBOSS_HOME_DIR/modules/com/friendly/utils/main/friendly-requestObjects-1.0.jar

=== 07.02.2017 - Build v. 5.0.1 b. 0.0.62

Bugs fixed: 4890

=== 06.02.2017 - Build v. 5.0.1 b. 0.0.61

Bugs fixed: 4890, 4886, 4881, 4768

=== 25.01.2017 - Build v. 5.0.1 b. 0.0.60

Bug 4757 fix

For namespaces in GetRPCMethodsResponse fix (bezeq device issue):

friendly-requestObjects-1.0.jar

Must be placed to: JBOSS_HOME_DIR/modules/com/friendly/utils/main

=== 19.01.2017 - Build v. 5.0.1 b. 0.0.59

Exception on start fix

=== 18.01.2017 - Build v. 5.0.1 b. 0.0.58

1) Reboot task will be moved to completed only after M Reboot pr 1 BOOT event receiving

2) FactoryReset task will be moved to completed only after 0 BOOTSTRAP event receiving

3) While 0 BOOTSTRAP event processing for existent CPE, only confirmed tasks will be deleted from DB (instead of all as prev)

4) If any of UpdateGroup task is in state "Sent", no else UG tasks will be processed

=== 28.12.2016 - Build v. 5.0.1 b. 0.0.57

CommandKey in Reboot fix

=== 20.12.2016 - Build v. 5.0.1 b. 0.0.56

Bug fixed: 4705, 4672

=== 16.12.2016 - Build v. 5.0.1 b. 0.0.55

Bug fixed: 4652

=== 15.12.2016 - Build v. 5.0.1 b. 0.0.54

1) fixed auto retrieve mode on failed|rejected task

2) Bugs fixed: 4684, 4677, 4665, 4654

=== 07.12.2016 - Build v. 5.0.1 b. 0.0.53

Bugs fixed: 4644, 4645

=== 06.12.2016 - Build v. 5.0.1 b. 0.0.52

Bugs fixed: 4642, 4641, 4608, 4545

=== 29.11.2016 - Build v. 5.0.1 b. 0.0.51

Added ACSWebServiceAdditional.getTasksByTransId

=== 17.11.2016 - Build v. 5.0.1 b. 0.0.50

Bugs fixed: 4413,4495,4561,3456,4562,4560 (requires httpclient-4.5.jar replacement on path: \modules\system\layers\base\org\apache\httpcomponents\main\)

=== 15.11.2016 - Build v. 5.0.1 b. 0.0.49

Bugs fixed: 4413, 4533, 4534, 4539, 4540, 4542

=== 07.11.2016 - Build v. 5.0.1 b. 0.0.48

Bugs fixed: 4530, 4488, 4508

=== 03.11.2016 - Build v. 5.0.1 b. 0.0.47

1) Bugs fixed: 4471, 4475, 4488, 4490, 4491, 4494, 4495, 4496, 4497, 4498, 4503, 4508, 4509, 4511

2) Added parameter: onDiagnosticCompleteRetrievePath

Legal values: empty (or closed tag), CPE Parameter names (full path) separated by "," (e.g. "InternetGatewayDevice.ManagementServer.") | Default value: empty (or closed tag) | on which GPV task will be sent to CPE in case of 8 DIAGNOSTIC COMPLETE event and no running diagnostic found in DB

3) Added parameter: blockPendingTillDownloadProcessing

Legal values: 0, 1 | Default value: 0 (disabled) | If 1 and CPE has any Download with reset session is in sent task - no pending will be processed

4) Added parameter: retrieveMacAddressesOnNewDeviceArrive

Legal values: 0, 1 | Default value: 0 (disabled) | If 1 and enableHardcodedEvents is 1 and CPE is new - GPV will be created on "InternetGatewayDevice.WANDevice." or "Device.Ethernet."

5) Added QoE and blocked by license information to the /acsstats page

=== 18.10.2016 - Build v. 5.0.1 b. 0.0.46

1) QoE redesign (requires DB changes and UI changes (requires CpeAdmin build 834)):

1) removed product_class_group_* csvs and DB tables

2) removed qoe_notificatioon and qoe_periodic tables

3) dictionary csvs/db table data now generating with monitor_results_* csvs

4) qoeMonitorMode=2 is deprecated, currently if qoeMonitorMode=1 nodes count doesn’t metter, synchronization is supported between all nodes

5) qoeMacStoreEnabled is deprecated, now mac is always saved when cpe registered in qoe module

6) standalone_*.xml changed

2) Bugs fixed: 4468, 4413, 4255

=== 01.09.2016 - Build v. 5.0.0 b. 0.0.45

Bugs fixed: 4401

=== 31.08.2016 - Build v. 5.0.0 b. 0.0.44

Bugs fixed: 4399

=== 31.08.2016 - Build v. 5.0.0 b. 0.0.43

Bugs fixed: 4390

=== 30.08.2016 - Build v. 5.0.0 b. 0.0.42

Bugs fixed: 4371

=== 30.08.2016 - Build v. 5.0.0 b. 0.0.41

Improved reflection usage performance to avoid OutOfMemory: Metaspace errors

=== 29.08.2016 - Build v. 5.0.0 b. 0.0.40

Bugs fixed: 4371, 4372

=== 29.08.2016 - Build v. 5.0.0 b. 0.0.39

1) Wildfly 10 migration

2) InformCache is loading asynchronously, the message after finish loading in log is: "fillCpeDataCache: On method end"

3) Bug fixes: 4372, 4371, 4362, 4357, 4355

=== 17.08.2016 - Build v. 5.0.0 b. 0.0.38

Issue fixed: in case of acs can’t processes any of parameter from cpe, it must process others instead of failing full tree store

=== 16.08.2016 - Build v. 5.0.0 b. 0.0.37

Bug 4347 fix

=== 11.08.2016 - Build v. 5.0.0 b. 0.0.36

Bug 4343 fix

=== 10.08.2016 - Build v. 5.0.0 b. 0.0.35

Fixed bug with qoe:

1) cpe A exists in cpe.csv

2) cpe A not exists in ACS DB

3) cpe A comes with 2 periodic

4) NullPointerException happens ⇒ CPE receives error message from ACS ⇒ CPE registration fails

=== 10.08.2016 - Build v. 5.0.0 b. 0.0.34

ACSWebServiceAdditional changes:

1) removed getCpeById

2) added getCpesByIds - will work as getCpeById, but processes array of ids instead of single id

3) changed getCpeParameters to make possibility to work with array of cpe ids. Changed first argument and return value

=== 04.08.2016 - Build v. 5.0.0 b. 0.0.33

Bugs fixed: 4325, 4334

=== 01.08.2016 - Build v. 5.0.0 b. 0.0.32

Bug 4325 fixed

=== 28.07.2016 - Build v. 5.0.0 b. 0.0.31

Bug 4325 fixed

=== 26.07.2016 - Build v. 5.0.0 b. 0.0.30

1) Startup variable added: "ftacs.useCpeNamespaces", if 1 acs will use soap namespaces returned by CPE, if absent or 0 - acs will use default namespaces (as in v.4)

2) Jar updated: modules\com\friendly\utils\main\friendly-requestObjects-1.0.jar MD5:754B9A592F444C1550F96BF5B1060537

3) Bugs fixed: 4320, 4319, 4317, 4315, 4310, 4277, 4262, 4202

=== 15.07.2016 - Build v. 5.0.0 b. 0.0.29

1) WS fix: retrieveLicenseDecrypted, getCpeParameters

2) Bugs fixed: 4308, 4277, 4240, 4223

=== 12.07.2016 - Build v. 5.0.0 b. 0.0.28

Added additional WS with retrieve methods, definition is available on address:

http://IP:PORT/ACSServer-ACS/ACSWebServiceAdditional?wsdl

=== 24.06.2016 - Build v. 5.0.0 b. 0.0.27

1) Bugs fixed: 4299, 4297, 4296, 4295, 4277, 4273, 4271, 4270, 4269, 4267, 4266, 4262, 4240, 4238, 4234, 4223, 4072, 2476

2) standalone.xml changed, actual standalone.xml is on 144.76.98.112

3) DB changed

4) acs-configuration.xml changed to acs_configuration.xml as in v.4

5) usedDBMS removed from acs_configuration.xml

6) start script: standalone.bat -c standalone_mysql/oracle.xml -b 0.0.0.0 -Djboss.node.name=NODE_NAME -Dftacs.ip.address=NODE_IP -Dftacs.usedDBMS=CURRENT_DBMS(Oracle/MySQL)

7) QoE changes: added object monitoring, firmware filter on group monitoring

Currently there is a posibility to switch between DBMS without any file changing

=== 26.05.2016 - Build v. 5.0.0 b. 0.0.26

Issue ID Description

2476

(Defects 5 and 6), 4237, 4236, 4234, 4231, 4063, 3700

=== 20.05.2016 - Build v. 5.0.0 b. 0.0.25

Fixed issue with AddObject

=== 20.05.2016 - Build v. 5.0.0 b. 0.0.24

Fixed issue with tree retrieving on bootstrap (bug 4205)

=== 20.05.2016 - Build v. 5.0.0 b. 0.0.23

Bugs fixed: 2737, 4205, 2974, 4076, 4063, 3700, 2476

=== 13.05.2016 - Build v. 5.0.0 b. 0.0.22

Bugs fixed: 4202, 4176

=== 13.05.2016 - Build v. 5.0.0 b. 0.0.21

Bugs fixed: 4191, 4190, 4185, 4179, 4176, 4174, 4173, 4172, 4142

=== 10.05.2016 - Build v. 5.0.0 b. 0.0.20

Bugs fixed: 4167

=== 29.04.2016 - Build v. 5.0.0 b. 0.0.19

Bugs fixed: 4153, 4142, 4127, 4118, 4047, 3799

=== 20.04.2016 - Build v. 5.0.0 b. 0.0.18

Bugs fixed: 4127, 4125, 4120, 4118, 4117, 4116, 4113, 4077, 4049

External Trace Log feature added:

  1. Add external_trace.properties file to wildfly configuration directory

  2. In case of saving traces to the log file � edit standalone.xml section: <subsystem xmlns="urn:jboss:domain:logging:2.0">

  3. external_trace.properties file may be changed/added/deleted on fly

external_trace.properties format:

# URL where the trace need to be sent

trace.url=http://localhost

# One of: SOAP, SYSLOG

trace.protocol=SYSLOG

trace.acs.[MESSAGE_NAME]

trace.cpe.[MESSAGE_NAME]

trace.url used only if SOAP protocol selected

SOAPAction names: CPEMessage - in case of message from CPE, ACSMessage � in case of message from ACS

Log4j settings:

There are two options:

1) Log to the file (will be saved in log directory):

<!-- ============================================ -->

<!-- Log for message tracing -->

<!-- ============================================ -->

<periodic-rotating-file-handler name="EXTERNAL_TRACE_LOG">

<formatter>

<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %s%E%n%n"/>

</formatter>

<file relative-to="jboss.server.log.dir" path="externalTrace.log"/>

<suffix value=".yyyy-MM-dd"/>

<append value="true"/>

</periodic-rotating-file-handler>

2) Log to the SYSLOG:

<!-- ============================================ -->

<!-- Log for message tracing -->

<!-- ============================================ -->

<custom-handler name="EXTERNAL_TRACE_LOG" class="org.jboss.logmanager.handlers.SyslogHandler" module="org.jboss.logmanager">

<formatter>

<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %s%E%n%n"/>

</formatter>

<properties>

<property name="appName" value="ACS"/>

<property name="serverHostname" value="localhost"/>

<property name="facility" value="LOG_AUDIT"/>

</properties>

</custom-handler>

For both options:

<!-- Enable log for message tracing -->

<logger category="com.friendly.dm.trace.DMMessage" use-parent-handlers="false">

<level name="INFO"/>

<handlers>

<handler name="EXTERNAL_TRACE_LOG"/>

</handlers>

</logger>

Setting use-parent-handlers="false" prevents writing messages to the server.log

=== 13.04.2016 - Build v. 5.0.0 b. 0.0.17

Bugs fixed: 4078, 4077, 4076, 4070, 4054, 4047, 4044, 4043, 4042, 4028, 4022, 4015, 3993, 3980, 3946, 3563

=== 24.03.2016 - Build v. 5.0.0 b. 0.0.16

Bugs fixed: 3481, 3799, 3831, 3834, 3877, 3877, 3886, 3914, 3917, 3926, 3933, 3940, 3941, 3946, 3974,

3980, 3981, 3984, 3993, 4004, 4011, 4012, 4014, 4015

Software management added to UpdateGroup

=== 21.03.2016 - Build v. 5.0.0 b. 0.0.15

Bug 4005 fixed

=== 21.03.2016 - Build v. 5.0.0 b. 0.0.14

Backup and restore features added to UpdateGroup

=== 02.03.2016 - Build v. 5.0.0 b. 0.0.13

Bugs fixed: 3799, 3851, 3848, 3834, 3831, 3855

=== 25.02.2016 - Build v. 5.0.0 b. 0.0.12

1) Added XMPP connection request support:

1.1 Jabber server installation requires (for example, http://www.igniterealtime.org/projects/openfire/)

1.2 Profile changes requires, those parameters needs to be added to profile for CPEs with XMPP support:

InternetGatewayDevice.ManagementServer.ConnReqXMPPConnection = InternetGatewayDevice.XMPP.Connection.1.

InternetGatewayDevice.ManagementServer.ConnReqAllowedJabberIDs = <FTACS jabber ID>

InternetGatewayDevice.XMPP.Connection.1.Server.1.ServerAddress = <Jabber server hostname>

InternetGatewayDevice.XMPP.Connection.1.Server.1.Port = <Jabber server port>

InternetGatewayDevice.XMPP.Connection.1.Server.1.Enable = true

InternetGatewayDevice.XMPP.Connection.1.Domain = <Jabber server hostname>

InternetGatewayDevice.XMPP.Connection.1.Username = <empty (will be added by ACS at runtime)>

InternetGatewayDevice.XMPP.Connection.1.Password = <empty (will be added by ACS at runtime)>

InternetGatewayDevice.XMPP.Connection.1.Resource = <empty (will be added by ACS at runtime)>

InternetGatewayDevice.XMPP.Connection.1.Enable = true

1.3 ACS config changes, parameters: xmppUsername, xmppPassword, xmppService, xmppServerHost, xmppServerPort

2) Changes in standalone.xml:

2.1 Section datasources: added settings for db connection restore after db fail

2.2 Added settings for https support

3) acs.keystore added to conf folder

4) acs_configuration changes, added parameters:

<!--Legal values: any string | Default value: ftacs | XMPP FTACS Account Username-->

<xmppUsername>ftacs</xmppUsername>

<!--Legal values: any string | Default value: ftacs | XMPP FTACS Account Password-->

<xmppPassword>ftacs</xmppPassword>

<!--Legal values: any string | XMPP Service Name-->

<xmppService>st03</xmppService>

<!--Legal values: domain name | Default value: empty | XMPP server address-->

<xmppServerHost>st03</xmppServerHost>

<!--Legal values: 0 - 65535 | Default value: 5222 | A port number of the XMPP server-->

<xmppServerPort>5222</xmppServerPort>

<!-- Legal values: 0, 1 | Default value: 0 (disabled) | If 1 - ACS will start tree retrieving on receiving new firmware version from CPE -->

<isNeedToRetrieveTreeOnFirmwareUpgrade>false</isNeedToRetrieveTreeOnFirmwareUpgrade>

5) Bugs fixed: 3857, 3855, 3854, 3851, 3850, 3848, 3834, 3831, 3799, 2736, 2545, 2459, 2376, 2289

6) Added libraries for supporting XMPP

=== 10.02.2016 - Build v. 5.0.0 b. 0.0.11

1) Fixed ACS version on statistics page

2) Bugs fixed: 1983, 2353, 2376, 2521, 3537 (ACS and DB changes, changes on FT API needed), 3667, 3688, 3799, 3810, 3811, 3835, 3842

3) Bugs fixed: 3819, 3834, 3831, 3844, 2545, 3630

=== 05.02.2016 - Build v. 5.0.0 b. 0.0.10

1) Statistics page added. Available on: http://URL:PORT/acsstats

2) Added ACS started notification in server log: FriendlyTR69 Management Server V[version from version.xml] Build [build from version.xml] started

3) Bugs fixed: 3834, 3831, 3830, 3825, 3819, 3813, 3668, 3630, 3425, 2865, 2545

=== 03.02.2016 - Build v. 5.0.0 b. 0.0.9

1) Manufacturer name saving in upper case.

2) Fix long parameter values saving for Oracle

=== 02.02.2016 - Build v. 5.0.0 b. 0.0.8

1) Fix of memory leak while using datasource in the license module

2) Fix of memory leak in parser module

3) Performance changes in standalone.xml

4) Bug 3817 fixed

=== 01.02.2016 - Build v. 5.0.0 b. 0.0.7

Transaction creating on Oracle fix

=== 26.01.2016 - Build v. 5.0.0 b. 0.0.6

Bugs fixed: 1990, 2348, 2426, 2736, 2974, 3279, 3662, 3810, 3811, 3813, 3815, 3816 3817, 3819, 3820

=== 22.01.2016 - Build v. 5.0.0 b. 0.0.5

Fixed in GPNR processing

=== 21.01.2016 - Build v. 5.0.0 b. 0.0.4

Bugs: 3803, 3802, 3801 fixed

=== 21.01.2016 - Build v. 5.0.0 b. 0.0.3

Added WS exceptions logging

=== 20.01.2016 - Build v. 5.0.0 b. 0.0.2

Fixed Set Provision flow

=== 17.01.2016 - Build v. 5.0.0 b. 0.0.1

Initial