[55765] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: VoIP QOS best practices

daemon@ATHENA.MIT.EDU (Ray Burkholder)
Mon Feb 10 15:08:37 2003

Date: Mon, 10 Feb 2003 14:38:31 -0500
From: "Ray Burkholder" <ray@oneunified.net>
To: "Leo Bicknell" <bicknell@ufp.org>, <nanog@nanog.org>
Errors-To: owner-nanog-outgoing@merit.edu


Many boxes are able to reorder packets.  If packets arrive too late to
be inserted into the conversion stream, they are dropped.  One dropped
packet in a sequence can usually be 'hidden' or 'faked' by the codec.
When more than one packet is missed in sequence, it becomes noticeable
to the listener.

Ray Burkholder


> -----Original Message-----
> From: Leo Bicknell [mailto:bicknell@ufp.org]=20
> Sent: February 10, 2003 14:44
> To: nanog@nanog.org
> Subject: Re: VoIP QOS best practices
>=20
>=20
> In a message written on Mon, Feb 10, 2003 at 01:19:08PM=20
> -0500, chaim fried wrote:
> > happens). There is no reason to implement QOS on the Core.=20
> Having said
> > that, there still seems to be too many issues on the tier 1 networks
> > with pacekt reordering as they affect h.261/h.263 traffic.=20
>=20
>=20
> So what's the real problem here?  Are the VOIP boxes unable to
> handle out of order packets?  Do the out of order packets simply
> arrive far enough delayed to blow the delay budget?  What=20
> percentage of
> reordered packets starts to cause issues?
>=20
> --=20
>        Leo Bicknell - bicknell@ufp.org - CCIE 3440
>         PGP keys at http://www.ufp.org/~bicknell/
> Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
>=20

home help back first fref pref prev next nref lref last post