FR fragmentation and Voice

From: Volkov, Dmitry (Toronto - BCE) (dmitry_volkov@ca.ml.com)
Date: Tue Sep 03 2002 - 15:32:00 GMT-3


Can somebody confirm or disprove the following:

definitions:
VoFR - voice packets directly encapsulated into L2 FR frames
VoIP - voice packets are encapsulated into L3 packets

To use FR fragmentation - FRTS has to be enabled.
FR Fragmentation is necessary :

1) PVC is not carrying voice (is not configured as VoFR, but may carry voice
as VoIP), but is sharing the link with other PVCs that are carrying voice
(these other PVCs may carry VoFR or VoIP)
OR
2) when PVC is carrying both voice and data (VoFR and VoIP/data).
================================
option 1) FRF.12 - is the recommended fragmentation to be used by VoIP
configuration: "frame-relay fragment [frag size]" under "map-class
frema-relay [class name]"
=================================
option 2) VoFR - is anabled by "vofr" undef "frame-relay interface-dlci"
command.
fragmentation FRF.11 Annex C is enabled in this case the same way as FRF.12
("frame-relay fragment [frag size]" under "map-class frema-relay [class
name]")
CISCO proprietary fragmentation triggered by adding "cisco" after "vofr" :
"vofr cisco"
under option 2) only VoFR packets are NOT fragmented - all other including
VoIP packets may be fragmented
================================
What is the difference between FRF.11 Annex C and Cisco proprietary (with
exception of word "proprietary") ?
When better to use one and when other ?

Thank You,

Dmitry



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:42 GMT-3