[arm-allstar] *** Status Reporting ***

[David McGough]

Hi Roger,

I really don't know what the original thinking was for splitting these 
status transmissions up. They're handled by separate timing events in 
app_rpt.


73, David KB4FXC




On Mon, 13 Aug 2018, "[UTF-8] Roger Coudé via arm-allstar" wrote:

> Here is the king of information that the status reporting sends to the server;
> node=1716&time=1534160429&seqno=42&nodes=T48039&apprptvers=hamvoip-1.5.3-08/08/2018&apprptuptime=580&totalkerchunks=0&totalkeyups=0&totaltxtime=0&timeouts=0&totalexecdcommands=0
> node=1716&time=1534160449&seqno=43&keyed=0&keytime=600
> node=1716&time=1534160459&seqno=44&nodes=T48039&apprptvers=hamvoip-1.5.3-08/08/2018&apprptuptime=610&totalkerchunks=0&totalkeyups=0&totaltxtime=0&timeouts=0&totalexecdcommands=0
> node=1716&time=1534160479&seqno=45&keyed=0&keytime=630
> Is there a reason why they alternate like that?
> 73
> Roger
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>