[69134] in North American Network Operators' Group
Re: Overflow circuit
daemon@ATHENA.MIT.EDU (Alexei Roudnev)
Sat Mar 27 02:39:11 2004
From: "Alexei Roudnev" <alex@relcom.net>
To: "Patrick Murphy" <pjm@nfld.net>,
"Mailing List Subscriptions" <jcc-list@thenetexpert.net>,
<nanog@merit.edu>
Date: Fri, 26 Mar 2004 23:39:16 -0800
Errors-To: owner-nanog-outgoing@merit.edu
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/technologies_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
> >
> >
>
