EasyCwmp - easycwmp
View Issue Details
0000398easycwmp[All Projects] Bugpublic2019-12-11 08:152019-12-13 14:08
chengang 
 
highmajoralways
newopen 
openwrtlinux4.4.60
0000398: when ACS get multiple parameter values, tr069 client response is error
An error occurred when I tried to ipping diagnostic with multiple getParameterValues
1.ACS send a request containing some getParameterValues to client for ipping diagnostic.
    
2.easycwmp client response is error.

3.When ACS send request containing any one of them,the response is normal.
Attached is the capture package file
No tags attached.
? multi-getParameterValues error.pcap (90,383) 2019-12-11 08:15
https://support.easycwmp.org/file_download.php?file_id=128&type=bug
Issue History
2019-12-11 08:15chengangNew Issue
2019-12-11 08:15chengangFile Added: multi-getParameterValues error.pcap
2019-12-11 10:11mohamed.kallelNote Added: 0000974
2019-12-12 02:45chengangNote Added: 0000975
2019-12-13 14:08mohamed.kallelNote Added: 0000976

Notes
(0000974)
mohamed.kallel   
2019-12-11 10:11   
Please try the following command on your device:

easycwmp --json-input

you willl get the folllowing prompt:

easycwmp>

Then type the following commands

{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.SuccessCount"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.FailureCount"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.AverageResponseTime"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.MinimumResponseTime"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.MaximumResponseTime"}
{"command":"end"}


and then let me know about results
(0000975)
chengang   
2019-12-12 02:45   
following is result´╝Ü
root@demo:~# easycwmp --json-input
easycwmp>
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.SuccessCount"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.FailureCount"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.AverageResponseTime"}
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.MinimumResponseTime"}
{ "parameter": "InternetGatewayDevice.IPPingDiagnostics.SuccessCount", "value": "0", "type": "xsd:unsignedInt" }
{ "parameter": "InternetGatewayDevice.IPPingDiagnostics.FailureCount", "value": "0", "type": "xsd:unsignedInt" }
{"command":"get", "class":"value", "parameter":"InternetGatewayDevice.IPPingDiagnostics.MaximumResponseTime"}
{"command":"end"}{ "parameter": "InternetGatewayDevice.IPPingDiagnostics.AverageResponseTime", "value": "0", "type": "xsd:unsignedInt" }
{ "parameter": "InternetGatewayDevice.IPPingDiagnostics.MinimumResponseTime", "value": "0", "type": "xsd:unsignedInt" }
{ "parameter": "InternetGatewayDevice.IPPingDiagnostics.MaximumResponseTime", "value": "0", "type": "xsd:unsignedInt" }
(0000976)
mohamed.kallel   
2019-12-13 14:08   
That means your data model script works fine.
May you made some modification some where that cause the issue.

Better to retest with the original version with other parmeters and see if the issue reproduced