Configuring Voice Adaptation with Endto End Fragmentation on the Interface

interface serialO encapsulation frame-relay frame-relay fragmentation voice-adaptive deactivation 30 (FR-VATS + FRF.12) frame-relay interface-dlci 100 class voice-adaptive-class (Binds voice_adaptive_class to the DLCI) frame-relay fragment 80 end-to-end (FRF.12 fragment for 384 kbps PVC on the interface)

class-map match-all voice match access-group 102

class-map match-all data match access-group 101

policy-map VOICE-TRAFFIC-SHAPING class voice priority 10 (Strict Priority) class data bandwidth 10

policy-map TRAFFIC-SHAPE class class-default shape average 729600 3648 0 (CIR = 95% of PVC [768 kbps], Bc to minCIR/ 100, Be = shape adaptive 364800 (Sets minimum CIR to 95% of 384 kbps) shape fr-voice-adapt deactivation 30 (Enables FR-VATS [default timer]) service-policy VOICE-TRAFFIC-SHAPING (Embedded LLQ to policy)

map-class frame-relay voice-adaptive-class service-policy output TRAFFIC-SHAPE (Embeds FR-VATS feature to map-class)

The figure shows an example of how to configure voice adaptation and end-to-end fragmentation on the interface. Notice that the strict priority queue which is used by FR-VATS is configured within the policy map VOICE-TRAFFIC-SHAPING and that policy is embedded within the traffic shaper policy map TRAFFIC-SHAPE, where the voice-adaptive feature is enabled. In order to tie the voice-adaptive feature to the interface, the policy map TRAFFIC-SHAPE must be embedded into the Frame Relay map-class voice-adaptive-class. Data-link Connection Identifier (DLCI) 100 is bound to the voice-adaptive feature through the map-class voice-adaptive-class. The end-to-end fragmentation configuration can be seen on the interface, and is enabled by the command frame-relay fragment 80 end-to-end. The end-to-end fragmentation configuration requires that the peer router have the same end-to-end fragmentation configuration.

Was this article helpful?

0 0

Post a comment