EasyCwmp

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000317easycwmp[All Projects] Helppublic2018-03-19 08:302018-04-04 18:31
Reportershasta 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
Platformmips32OSlinuxOS Version
Summary0000317: easycwmp doesn't send (passive / active) notification
DescriptionUpgrade easycwmp from 1.1.2 to 1.6.1, found that notify is no arg now.
#ubus list -v
'tr069' @bd50a229
        "notify":{}
        "inform":{"event":"String"}
        "command":{"name":"String"}

So I tested notification function as below:
#sh /usr/sbin/easycwmp set notification Device.IP.Diagnostics.IPPing.Host 2
#sh /usr/sbin/easycwmp apply notification

In easycwmp config file I see:

config notifications
        list active 'Device.IP.Diagnostics.IPPing.Host'

then I tried to modify Device.IP.Diagnostics.IPPing.Host:

#sh /usr/sbin/easycwmp set value Device.IP.Diagnostics.IPPing.Host 192.168.100.123
#sh /usr/sbin/easycwmp apply value

and got response message:
{ "status": "1" }

then I call ubus to send notify:
#ubus call tr069 notify

Response (please ignore date):
2012-01-01 01:49:30 [easycwmp] NOTICE - triggered ubus notification
2012-01-01 01:49:31 [easycwmp] NOTICE - checking if there is notify value change
2012-01-01 01:49:31 [easycwmp] NOTICE - external script init
2012-01-01 01:49:31 [easycwmp] NOTICE - external: execute check_value_change
2012-01-01 01:49:32 [easycwmp] NOTICE - external script exit


and nothing happened, no Inform, no VALUE CAHNGE event.
Do I missed something or issue wrong command for notification?
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0000855)
mohamed.kallel (manager)
2018-03-26 13:10

Do not set the host with easycwmp command. This will not trigger notification.
And also do test notification a parameter which defined in easycwmp config. You have to user another config file like wireless.
(0000856)
nromero (reporter)
2018-04-04 18:31

Hi shasta.

/usr/sbin/easycwmp is used to act as the ACS, so the changes made with "set value" will not trigger a notification to the ACS (since it will be redundant for the ACS to receive the value it "sent" in the first place).

In order to trigger a "4 VALUE CHANGE" event you need to set the notification to "2" as you did and apply the changes with "/usr/sbin/easycwmp apply".

Then, change the parameter value "manually". For example, try with the parameter "Device.WiFi.SSID.1.SSID" which is defined in /etc/config/wireless, as mohamed.kallel said.

Then call "ubus call tr069 notify" and it will identify the change and trigger a "4 VALUE CHANGE" event.

- Issue History
Date Modified Username Field Change
2018-03-19 08:30 shasta New Issue
2018-03-26 13:10 mohamed.kallel Note Added: 0000855
2018-04-04 18:31 nromero Note Added: 0000856


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker