[alcatel-nsp] SAMO Date type

[Jon Kopings]

Its Unix Epoch Time in milliseconds.
Try to 
convert it to human date here : 

http://www.epochconverter.com/

Regards

PS : Sorry for Chadwick Sorrell for the individual email I've sent (it should be reply to all, though)




________________________________
From: Chadwick Sorrell <mirotrem at gmail.com>
To: David Schubert <david.schubert at cenx.com>
Cc: alcatel-nsp at puck.nether.net
Sent: Thu, April 15, 2010 7:50:43 PM
Subject: Re: [alcatel-nsp] SAMO Date type


Unix epoch time?
On Apr 15, 2010 11:44 PM, "David Schubert" <david.schubert at cenx.com> wrote:
>
>
>When I get accounting records from the samo SOAP interface, the timestamps on the acounting data look like this.
>
>
>ex:
><service.CompleteServiceEgressPacketOctetsLogRecord>
>...
><timeRecorded>1271379851000</timeRecorded>
><outOfProfileOctetsForwarded>1243107543</outOfProfileOctetsForwarded>
>        ...
><timeCaptured>1271380452154</timeCaptured>
><children-Set></children-Set>
></service.CompleteServiceEgressPacketOctetsLogRecord>
>
>
>I cant find anywhere in the docs that actually explains explicitly how to interpret these numbers.
>
>
>One clue may be from From the SAM xml reference where I see:
>
>
>timeRecorded: type=Date; access=read-only; default=0
>How do I change the number <timeCaptured>1271380452154</timeCaptured> into a meaningful date?
>
>
>Thx
>Dave
>_______________________________________________
>>
>alcatel-nsp mailing list
>alcatel-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
>


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20100416/d2b58a87/attachment-0001.html>