Hi Luka,
Thanks! the command does well to send the notification.
I am little bit confused to understand whether the SCRIPTS/Commands
are MUST to run the freecwmp client or it is used as testing only?
I would appreciate if you give me details why the different modules
e.g. ubus shlibs etc are required and how do these work in tandem with
freecwmp?
It would be a great help to give me the design and code flow.
Regards,
Akhil
On Sun, Jan 20, 2013 at 11:26 PM, Luka Perkov <freecwmp@lukaperkov.net> wrote:
> On Fri, Jan 18, 2013 at 12:05:05PM +0000, akhil garg wrote:
>> I executed the following command to set the active notification for
>> "ManagementServer.Username"
>> "freecwmp set notification InternetGatewayDevice.ManagementServer.Username 2"
>>
>> Then executing the following command freecwmp client should send
>> INFORM RPC to ACS but it is not sending.
>> "freecwmp set value InternetGatewayDevice.ManagementServer.Username xyz"
>>
>> How can I test the Notification?
>
> You must patch the scripts or manually trigger ubus call:
>
> $ ubus -s /to/your/ubus.sock -v call tr069 notify '{ "parameter":
> "InternetGatewayDevice.ManagementServer.Username", "value": "xyz" }'
>
> I could have put ubus call for every parameter in the main freecwmp
> script but I did not. I'm reworking how freecwmp core and freecwmp
> scripts are communicating and once it's done you wont need to do this
> anymore.
>
> Luka
--
regards,
akhil
|