Hi Jonathan,
On May 6, 2015, at 22:25 , Jonathan Morton wrote:
> So, as a proposed methodology, how does this sound:
>
> Determine a reasonable ballpark figure for typical codec and jitter-buffer
> delay (one way). Fix this as a constant value for the benchmark.
But we can do better,
On Wed, 6 May 2015, Jonathan Morton wrote:
So, as a proposed methodology, how does this sound:
Determine a reasonable ballpark figure for typical codec and jitter-buffer
delay (one way). Fix this as a constant value for the benchmark.
Commercial grade VoIP systems running in a controlled envi
Jonathan Morton writes:
> Compare these totals to twice the ITU benchmark figures, rate
> accordingly, and plot on a map.
A nice way of visualising this can be 'radius of reach within n
milliseconds'. Or, 'number of people reachable within n ms'. This paper
uses that (or something very similar)
So, as a proposed methodology, how does this sound:
Determine a reasonable ballpark figure for typical codec and jitter-buffer
delay (one way). Fix this as a constant value for the benchmark.
Measure the baseline network delays (round trip) to various reference
points worldwide.
Measure the maxi
Hi Jim, hi List,
On May 6, 2015, at 17:30 , Jim Gettys wrote:
>
>
> On Wed, May 6, 2015 at 4:50 AM, Sebastian Moeller wrote:
> Hi Simon,
>
> On May 6, 2015, at 07:08 , Simon Barber wrote:
>
> > Hi Sebastian,
> >
> > My numbers are what I've personally come up with after working for many
On Wed, May 6, 2015 at 4:50 AM, Sebastian Moeller wrote:
> Hi Simon,
>
> On May 6, 2015, at 07:08 , Simon Barber wrote:
>
> > Hi Sebastian,
> >
> > My numbers are what I've personally come up with after working for many
> years with VoIP - they have no other basis.
>
> I did not intend t
Hi Simon,
On May 6, 2015, at 07:08 , Simon Barber wrote:
> Hi Sebastian,
>
> My numbers are what I've personally come up with after working for many years
> with VoIP - they have no other basis.
I did not intend to be-little such numbers at all, I just wanted to
propose that we eithe
