From: Petr Lapukhov (petrsoft@gmail.com)
Date: Mon Apr 24 2006 - 12:41:31 GMT-3
Dave,
AFAIK first snippet works for VoFR (Voice over FR directly). As to my
knowledge it is not tested in R&S lab.
Second snippet is VoIP stuff. Now we have basically two
way of prioritizing VoIP traffic over FR
1) FR IP RTP Priority
2) LLQ (with match protocol RTP or match access-group)
First one is more simple in terms of configuration, but second one
is more flexible. Use second if you really need MQC features.
But more work to do here:
You may also need fragmentation and Tc value adjustement,
if you want things to sound smoothly. Sometimes, you may also need
to enable RTP header compression, if you have "slow" link, or you are
instructed to use small fragment size (smaller than uncompressed
RTP packet)
So here they are:
1) Fragmentation (you may do it per map-class, or at interface level).
Fragmentation may be Voice Adaptive with LLQ. Fragmentation
is not configurable within MQC.
2) Tc Value. Basically you set it to minimum 10 ms
.
3) cRTP. This one is optional, try not to mess with it, unless you are
really forced to :) Note, that voice packet is first compressed and
then fragmented.
Oh, that's not all :) Remember, you can use RSVP + WFQ per-VC to
control voice quality too :)
HTH
Petr
2006/4/24, Schulz, Dave <DSchulz@dpsciences.com>:
>
> Group -
>
> If I am going to make sure that I reserve bandwidth for voice across the
> frame....would it be more correct to do this:
>
> map-class frame-relay FR
> frame-relay fair-queue
> frame-relay voice bandwidth 1000000
>
>
> or, this.....
>
> map-class frame-relay FR
> frame-relay ip rtp priority 16384 16383 1000
> !
>
> Dave
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:59 GMT-3