RE: Beacon OWD/Delay measurements
Hi Mitch
Thanks for the answers - look forward to the new release - should be
able to hold off till then for a new install.
> 1) The Beacon can't supply OWD because the RTP protocol simply isn't
able
> to support it. We return RTT/2 because that's all we can get.
Sorry, maybe I put it wrongly. The old beacon (pre v1) used to just give
a 'delay' figure on the delay page - which I interpret as OWD - as it
depends on a) network delay from Y to Z and b) accuracy the clocks at
each end - which was an issue in many cases.
So this is the figure I am after - just not the two added together (Y to
Z plus Z to Y) - which I'm hoping can be extracted if necessary from the
source and dest machines.
> 3) Unfortunately, no historic clients exist. As Beacon development
> progressed, most version changes also required changes to the Beacon
data
> format to fix various errors or deficiencies, so an older client would
> only
> be able to talk to a very narrow range of servers anyway.
I can see the reason - just it was nice to have a lightweight client to
run on some machines rather than a full install. Maybe something we can
think about here.
Cheers
Steve
-----------------------------------------------
Steve Williams
Technical Specialist Measurement and Monitoring
Advanced Technology Group
UKERNA
Atlas Centre, Chilton, Didcot, Oxon OX11 0QS
-----------------------------------------------
S.Williams@ukerna.ac.uk
Tel: +44 (0)1235 822245
GDS Video: 0044 01100 107