From: Victor Cappuccio (cvictor@protokolgroup.com)
Date: Thu Jul 20 2006 - 18:47:02 ART
Hi Elias,
Thats fine, but check out here link http://home.satx.rr.com/n5gpi/qos.htm,
I'm wondering where this values came up, and if that information is
accurate.
Saludos,
Victor.-
VoBW = 45k per each DS0 ?? Why 45k??
*256K Circuits*
CIR = 256000
BC = 2560
Tc = .01 Secs (10ms)
Frag = 320 bytes
VoBW = 180 *using the formula above, 256/DS0 == 4 and 4 * 45 == 180*
*512K Circuits*
CIR = 512000
BC = 5120
Tc = .01 Secs (10ms)
Frag = 640 bytes
VoBW = 360 (360K of the 512K available) *using the formula above, 512/64 ==
8 and 8 * 45 == 360*
________________________________________
De: Elias Chari [mailto:elias.chari@gmail.com]
Enviado el: Jueves, 20 de Julio de 2006 04:52 p.m.
Para: Victor Cappuccio
CC: ccielab@groupstudy.com
Asunto: Re: Frame-relay RTP BW.
Hi Victor,
I would have thought this is dependent on the codec used for VoIP and it is
the sum of all simultaneous VoIP calls supported. It only selects payload
from the even numbered UDP ports. So RTP traffic is placed in the PQ and
RTCP in the default WFQ. So you don't need to worry about additional control
traffic when calculating the bandwidth for the command.
I'm not sure though whether the bandwidth allocated takes into account L-2
overheads or not. Perhaps someone else can clarify this point.
Rgds
Elias
On 7/20/06, Victor Cappuccio < cvictor@protokolgroup.com> wrote:
Hi guys,
How to calculate the RTP Bandwidth necessary for a frame-relay fragment?
For example
map-class frame-relay voip
frame-relay cir 256000
frame-relay bc 2560
frame-relay be 600
frame-relay mincir 256000
no frame-relay adaptive-shaping
frame-relay fair-queue
frame-relay fragment 250
frame-relay ip rtp priority 16384 16380 210
How the 210Kbps was calculated here?
Thanks
Victor.-
This archive was generated by hypermail 2.1.4 : Tue Aug 01 2006 - 07:13:48 ART