voip vs. your isp

[gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)]

On 01/26/2009 02:36 PM, Matthew Gillen wrote:
> Jack Coats wrote:
>  =20
>> ...  Unless you can get a IP provider that focuses on=20
>> low latency connectivity or you manage your own network end to end, it=
=20
>> is almost impossible to guarantee any kind of high quality VOIP servic=
e.
>>
>> It doesn't have to be that way.  But from experience, most IP provider=
s=20
>> do not give priority to VOIP flagged packets, so even flagging them is=
 a=20
>> waste of time.  And if even one of the routers 'accidentally drops' th=
e=20
>> flag, all bets are off.
>>
>> If industry starts recognizing the priority flags for VOIP or other=20
>> truly time sensitive packets, there are people/companies that will tur=
n=20
>> it on for all their packets, making it a moot point again.
>>    =20
>
> The article I mentioned wasn't even complaining about not giving VoIP h=
igh
> priority.  Apparently the mechanism Comshaft uses to implement their
> congestion-control unduly hurts VoIP, since it starts adding delays to =
packets
> from "heavy users" (ie makes them lower-priority than "normal" packets)=
=2E
>
> The problem is that /their/ voice service of course isn't subject this
> de-prioritorization.  So you're sort of railroaded into their service.
>  =20
Additionally, Comcast's VOIP does not go out onto the public Internet,=20
it stays withing Comcast's network and uses Comcast's phone system networ=
k

--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846