/mcpQuality of Service for Voice over IP Resource Reservation Protocol 30 QoSVoIP.mif Cisco IOS software. A Cisco voice gateway configured to reserve resources via RSVP will infer the correct TSpec exclusively from the codec used on the dial peer. You cannot control TSpec values using the CLI and no other bandwidth-saving features (such as VAD) are taken into consideration. Some revisions of Microsoft NetMeeting for Windows 98 and Windows 2000 (which use RSVP) signal a bucket size in the TSpec that is not compatible with these defaults. This problem affects Microsoft NetMeeting for calls using codecs that require 32 kbps or more. In those cases, you need to create a custom profile to match the parameters signaled by Microsoft Windows. The following configuration example shows how to configure RSVP support for LLQ on a Frame Relay circuit that has two PVCs: One of the important implications of RSVP support for LLQ is that it lets you classify voice traffic based on its traffic characteristics rather than on the transport protocol (UDP) and port number (16384 through 32767). The proper operation of LLQ relies on the assumption that the priority queue is used only by well-behaved traffic (such as voice) that has a predictable rate and a very low burst size. Classification based on transport protocol and ports could allow bursty or noncritical traffic into the Configuration Example 13: RSVP Support for LLQ on Frame Relay PVCs hostname LongBay ! isdn switch-type primary-ni call rsvp-sync ! interface Serial0/0 bandwidth 1536 no ip address encapsulation frame-relay no fair-queue frame-relay traffic-shaping ! interface Serial0/0.1 point-to-point ip address 10.10.1.2 255.255.255.0 frame-relay interface-dlci 16 class VoIPoFR ip rsvp bandwidth 48 24 ! interface Serial0/0.2 point-to-point ip address 10.10.2.2 255.255.255.0 frame-relay interface-dlci 17 class VoIPoFRip rsvp bandwidth 48 24 ! ip rsvp pq-profile voice-like ! map-class frame-relay VoIPoFR no frame-relay adaptive-shaping frame-relay cir 64000 frame-relay bc 640 frame-relay mincir 64000 frame-relay fair-queue frame-relay fragment 80 ! In this example, WFQ is enabled on the PVCs and disabled on the physical interface. Each PVC has a priority queue for voice traffic. The physical interface has the dual-FIFO queue structure. FRTS is enabled and its parameters are defined in the VoIPoFR map class.