nanog mailing list archives

RE: Overflow circuit


From: "Mailing List Subscriptions" <jcc-list () thenetexpert net>
Date: Sat, 27 Mar 2004 00:13:10 -0800


I have been doing VoIP over sat to northern Canada and Latin America for
more than five years now, using Cisco routers with analog and digital voice
ports, and also IP phones. Other than the inevitable lag due to 500+ ms RTT,
the voice quality with the G.729 codec has been good. I have lost count of
the number of mining operations in northern Canada that rely in VoIP over
sat for communication with the civilized world. Some of the bigger
operations have in excess of 500+ Cisco IP phones.

-----Original Message-----
From: owner-nanog () merit edu [mailto:owner-nanog () merit edu] On 
Behalf Of Alexei Roudnev
Sent: Friday, March 26, 2004 11:39 PM
To: Patrick Murphy; Mailing List Subscriptions; nanog () merit edu
Subject: Re: Overflow circuit


VoIP over satellite? I am very sceptical about it. Better, 
forget such idea.




You may want to look at using H.323 gatekeepers with CAC (Call 
Admission Control).

Here is a link to a Whitepaper on this Subject.


http://www.cisco.com/en/US/partner/tech/tk652/tk701/technologi
es_white_paper09186a00800da467.shtml

Patrick

----- Original Message -----
From: "Mailing List Subscriptions" <jcc-list () thenetexpert net>
To: <nanog () merit edu>
Sent: Friday, March 26, 2004 7:54 PM
Subject: Overflow circuit




I am looking for advice on technique or products that can 
solve the 
following challenge ...

Two private line T1's between A and B - one terrestial T1 
with >200 
ms
RTT,
the other T1 is over satellite with ~500 ms RTT. The circuits are 
being
used
for mixed VoIP (70%) and data (30%) applications. To 
achieve optimal
voice
quality, we want to route all VoIP calls over the terrestial T1 
until it
is
"full", then divert all subsequent VoIP calls over the 
satellite T1 
(** while existing VoIP calls continue to be routed over 
the terrestial T1).

So it looks like I need per-flow (based on protocol, src 
IP, dst IP, 
src port, dst port) routing. It looks like MPLS Traffic 
Engineering 
can do
the
job. Is there anything else that can it with less complexity?

Ideas or recommendations?


Regards,
Joe









Current thread: