Table Of Contents
Prerequisites for AutoQoS — VoIP
Restrictions for AutoQoS — VoIP
Information About AutoQoS — VoIP
Configurations for the Interface Configurations, Policy Maps, Class Maps, and ACLs
How to Configure the AutoQoS — VoIP Feature
Enabling the AutoQoS — VoIP Feature
Prerequisites for Using the auto qos Command
Restrictions for Using the auto qos Command
Configuration Examples for AutoQoS — VoIP
Configuring the AutoQoS — VoIP Feature Examples
Verifying the AutoQoS — VoIP Feature Configuration Examples
AutoQoS — VoIP
The AutoQoS — VoIP feature allows you to automate the delivery of quality of service (QoS) on your network and provides a means for simplifying the implementation and provisioning of QoS for Voice over IP (VoIP) traffic.
Feature Specifications for AutoQos — VoIP
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for AutoQoS — VoIP
•
Restrictions for AutoQoS — VoIP
•
Information About AutoQoS — VoIP
•
How to Configure the AutoQoS — VoIP Feature
•
Configuration Examples for AutoQoS — VoIP
Prerequisites for AutoQoS — VoIP
•
Ensure that no QoS policies (service policies) are attached to the interface. This feature cannot be configured if a QoS policy (service policy) is attached to the interface.
•
To include Simple Network Protocol (SNMP) traps (monitored events), the SNMP server must be enabled.
Restrictions for AutoQoS — VoIP
General Restrictions
•
The AutoQoS — VoIP feature is supported on the following interfaces, data-link connection identifiers (DLCIs), and permanent virtual circuits (PVCs) only:
–
Serial interfaces with PPP or High-Level Data Link Control (HDLC)
–
Frame Relay DLCIs in point-to-point subinterfaces only
–
ATM PVCs
The AutoQoS — VoIP feature is supported on low-speed ATM PVCs in point-to-point subinterfaces only. The AutoQoS — VoIP feature is supported on high-speed ATM PVCs in any type of subinterface.
Note
An ATM PVC is classified as low-speed if its bandwidth is less than or equal to 768 kbps; an ATM PVC is classified as high-speed if its bandwidth is greater than 768 kpbs
–
Frame Relay-to-ATM Interworking links
Serial Interface Restrictions
•
For a serial interface with a low-speed link, Multilink PPP (MLP) is configured automatically. The serial interface must have an IP address. When MLP is configured, this IP address is removed and put on the MLP bundle. To ensure that the traffic goes through the low-speed link, the following conditions must be met:
–
The AutoQoS - VoIP feature must be configured at the both ends of the link.
–
The amount of bandwidth configured must be the same on both ends of the link.
Frame Relay DLCI Restrictions
•
The AutoQoS — VoIP feature cannot be configured on a Frame Relay DLCI if a map class is attached to the DLCI.
•
If a Frame Relay DLCI is already assigned to one subinterface, the AutoQoS — VoIP feature cannot be configured from a different subinterface.
•
For low-speed Frame Relay DLCIs configured for use on Frame Relay-to-ATM networks, MLP over Frame Relay (MLPoFR) is configured automatically. The subinterface must have an IP address.
When MLPoFR is configured, this IP address is removed and put on the MLP bundle. The AutoQoS — VoIP feature must also be configured on the ATM side of the network.
•
For low-speed Frame Relay DLCIs with Frame Relay-to-ATM Interworking, the AutoQoS — VoIP feature cannot be configured if a virtual template is already configured for the DLCI.
ATM PVC Restrictions
•
For a low-speed ATM PVC, the AutoQoS — VoIP feature cannot be configured if a virtual template is already configured for the ATM PVC.
•
For low-speed ATM PVCs, MLP over ATM (MLPoATM) is configured automatically. The subinterface must have an IP address.
When MLPoATM is configured, this IP address is removed and put on the MLP bundle. The AutoQoS — VoIP feature must also be configured on the ATM side of the network.
Information About AutoQoS — VoIP
To configure the AutoQoS — VoIP feature, you need to understand the following concepts:
•
Configurations for the Interface Configurations, Policy Maps, Class Maps, and ACLs
Benefits of AutoQoS — VoIP
The key benefits of the AutoQos -VoIP feature include the following:
•
Customers can implement the QoS features required for VoIP traffic without an in-depth knowledge of the following underlying technologies:
–
PPP
–
Frame Relay
–
ATM
–
Service policies
–
Link efficiency mechanisms (LEM), such as Link Fragmentation and Interleaving (LFI)
•
The AutoQoS — VoIP feature simplifies QoS implementation and speeds up the provisioning of QoS technology over a Cisco network. It reduces human error and lowers training costs. With the AutoQoS — VoIP feature, one command (the auto qos command) enables QoS for VoIP traffic across every Cisco router and switch.
•
Customers can also use existing Cisco IOS commands to modify the configurations automatically generated by the AutoQoS — VoIP feature as needed to meet specific requirements.
•
The Cisco product, CiscoWorks QoS Policy Manager (QPM), can be used in conjunction with the AutoQoS — VoIP feature to provide a centralized, web-based tool to cost effectively manage and monitor network-wide QoS policies. The AutoQoS — VoIP feature together with CiscoWorks QPM, eases QoS implementation, provisioning, and management.
Design Considerations
General QoS Requirements
•
Recommended methods and values are configured to meet the QoS requirements for voice traffic.
•
The AutoQoS — VoIP feature takes the interface type and bandwidth into consideration when implementing the following QoS features:
–
Classification
Classification is used to differentiate the voice packets from the data packets and handle the voice packets appropriately.
–
Low latency queueing (LLQ) - Priority Queueing (PQ)
The LLQ (specifically, PQ) is applied to the voice packets to meet the latency requirements.
–
Compressed Real-Time Protocol (cRTP)
With cRTP, the 40-byte IP header of the voice packet is reduced from 2 to 4 bytes, thereby reducing voice bandwidth requirements. cRTP must be applied at both ends of a network link.
–
LFI
LFI is used to reduce the jitter of voice packets by preventing voice packets from getting delayed behind large data packets in a queue. LFI must be applied at both ends of a network link.
Bandwidth Implications
•
The bandwidth of the serial interface determines the speed of the link. The speed of the link in turn determines the configurations generated by the AutoQoS — VoIP feature.
Note
Changing the bandwidth before configuring the AutoQoS — VoIP feature is not recommended.
The AutoQoS — VoIP feature uses the bandwidth at the time the feature is configured. AutoQoS — VoIP does not respond to changes made to bandwidth after the feature is configured.
For example, if the auto qos voip command is used to configure the AutoQoS — VoIP feature on an interface with 1000 Kbps, the AutoQoS — VoIP feature generates configurations for high-speed interfaces. However, if the bandwidth is later changed to 500 Kbps, the AutoQoS — VoIP feature will not use the lower bandwidth. The AutoQoS — VoIP feature retains the higher bandwidth and continues to use the generated configurations for high-speed interfaces.
To force the AutoQoS — VoIP feature to use the lower bandwidth (and thus generate configurations for the low-speed interfaces), use the no auto qos voip command to remove the AutoQoS — VoIP feature and then reconfigure the feature.
Fragmentation for Frame Relay Networks
•
For Frame Relay networks, fragmentation is configured using a delay of 10 milliseconds (ms) and a minimum fragment size of 60 bytes. This ensures that the VoIP packets are not fragmented. However, when the G.711 coder-decoder (codec) is used on low-speed links, the fragment size configured by the AutoQoS — VoIP feature could be smaller than the size of the G.711 VoIP packet.
To solve this potential problem, choose one of the following:
–
Change the fragment size to the required value.
–
Change the size of the G.711 VoIP packet to a smaller value.
For example, if the AutoQoS — VoIP feature is configured on a Frame Relay DLCI with 128 Kbps, the fragment size configured by the AutoQoS — VoIP feature will be 160 bytes. The size of the G.711 VoIP packet will be 160 bytes, minus the bytes in the packet headers for the layers. The workaround is to either change the fragment size from 160 bytes to 220 bytes or change the size of the G.711 VoIP packet from 160 bytes to 80 bytes.
Signaling Protocols
•
The AutoQoS — VoIP feature currently identifies the following signaling protocols:
–
H.323
–
H.225 (Unicast only)
–
Session Initiation Protocol (SIP)
–
"Skinny" gateway protocol
–
Media Gateway Control Protocol (MGCP)
Note
Access control lists (ACLs) can be configured to identify any additional signaling protocols that may be needed.
Configurations for the Interface Configurations, Policy Maps, Class Maps, and ACLs
The AutoQoS — VoIP feature automatically creates configurations that are then used for the interface configurations, policy maps, class maps, and ACLs. The interface configurations, policy maps, class maps, and ACLs are created to classify VoIP packets and to provide the appropriate QoS treatment for the network traffic.
This feature also creates interface (or PVC)-specific configurations. These interface (or PVC)-specific configurations are created according to the interface type and the link speed.
Note
Links with bandwidths lower than or equal to 768 kpbs are considered low-speed links; links with bandwidths higher than 768 kpbs are considered high-speed links.
How to Configure the AutoQoS — VoIP Feature
This section contains the following tasks. Each task is identified as either required or optional.
•
Enabling the AutoQoS — VoIP Feature (required)
•
Verifying the Configuration (optional)
Enabling the AutoQoS — VoIP Feature
The only required step for enabling the AutoQoS — VoIP feature is to use the auto qos voip command. This command automatically creates configurations for interface configurations, policy maps, class maps, and ACLs. These interface configurations, policy maps, class maps, and ACLs are used to classify VoIP packets and to provide the appropriate QoS for the network traffic.
Prerequisites for Using the auto qos Command
Before using the auto qos command at an interface or an ATM PVC, ensure that the following prerequisites have been met:
•
Cisco Express Forwarding (CEF) must be enabled at the interface or ATM PVC.
•
If the interface or subinterface has a link speed of 768 kpbs or lower, configure the primary or secondary IP address of the interface by using the ip address command.
•
For all interfaces or subinterfaces, configure the amount of bandwidth by using the bandwidth command. The amount of bandwidth allocated should be based on the link speed of the interface.
•
For an ATM PVC, configure the variable bit rate (VBR) by using either the vbr-nrt command or the vbr-rt command or configure the constant bit rate (CBR) by using the cbr command.
Restrictions for Using the auto qos Command
•
The auto qos voip command is not supported on subinterfaces.
•
Do not change the bandwidth of the interface before using the auto qos command.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
bandwidth kilobits
5.
vbr-nrt output-pcr output-scr output-mbs [input-pcr] [input-scr] [input-mbs]
6.
vbr-rt peak-rate average-rate burst
7.
cbr rate
8.
pvc [name] vpi/vci [ces | ilmi | qsaal | smds]
9.
ip address ip-address mask [secondary]
10.
frame-relay interface-dlci dlci [ietf | cisco] [voice-cir cir] [ppp virtual-template-name]
11.
auto qos voip [trust] [fr-atm]
12.
exit
DETAILED STEPS
FAQs and Troubleshooting Tips
Below are answers to frequently asked questions (FAQs) and tips for troubleshooting situations that you may encounter when configuring or using the AutoQoS — VoIP feature.
Why can't I configure the AutoQoS — VoIP feature?
•
To configure the feature, CEF must be is enabled. Verify that CEF is enabled on your network.
•
Also, the feature cannot be enabled if a service policy is already attached to the interface. Determine whether there is a service policy attached to the interface. If so, remove the service policy from the interface.
Why isn't the AutoQoS — VoIP feature supported on my router?
•
The AutoQoS — VoIP feature is supported only on the IP Plus image for lower-end platforms. Verify that you have the IP Plus image installed on your router.
Why are some of my QoS configurations still present after I disable the AutoQoS — VoIP feature?
•
You have to manually disable any QoS configurations that were modified by the AutoQoS — VoIP feature.
Why did my low-speed network link go down when I enabled the AutoQoS — VoIP feature?
•
Ensure that AutoQoS — VoIP is enabled on both sides of the network link.
Why can't I establish an end-to-end connection on the Frame Relay link?
•
Check the bandwidth on both sides of the Frame Relay link. The bandwidth on both sides of the link must be the same, otherwise a fragmentation size mismatch occurs and a connection cannot be established.
Note
For more help, see the "Technical Assistance" section.
What to Do Next
If the interface configurations, policy maps, class maps, and ACLs created (on the basis of the configurations created by the AutoQoS - VoIP feature) do not meet the needs of your network, the interface configurations, policy maps, class maps, and ACLs can be modified using the appropriate Cisco IOS commands.
Note
While you can modify the interface configurations, policy maps, class maps, and ACLs, they may not be removed properly when the AutoQoS — VoIP feature is disabled using the no auto qos command. You may need to manually remove any modified interface configurations, policy maps, class maps, and ACLs. For more information about the no auto qos command, see the "Command Reference" section.
Verifying the Configuration
The AutoQoS — VoIP feature automatically generates configurations that, in turn, are used to create interface configurations, policy maps, class maps, and ACLs. These interface configurations, policy maps, class maps, and ACLs configure the QoS features on your network.
To verify the configuration (that is, the contents of the interface configurations, policy maps, class maps, and ACLs), use the following commands:
SUMMARY STEPS
1.
enable
2.
show auto qos [interface [interface type]]
3.
show policy-map interface [interface type]
4.
exit
DETAILED STEPS
Configuration Examples for AutoQoS — VoIP
This section provides the following configuration examples:
•
Configuring the AutoQoS — VoIP Feature Examples
•
Verifying the AutoQoS — VoIP Feature Configuration Examples
Configuring the AutoQoS — VoIP Feature Examples
When the auto qos voip command is used to configure the AutoQoS — VoIP feature, configurations are generated. These configurations are then used to create interface configurations, policy maps, class maps, and aCLs.
This section contains the following examples of configuring the AutoQoS — VoIP feature on the interfaces, PVCs, and links.
Configuring the AutoQoS — VoIP Feature on a High-Speed Serial Interface Example
In this example, the AutoQoS — VoIP feature is configured on the high-speed serial interface s1/2.
Router> enableRouter# configure terminalRouter(config)# interface s1/2
Router(config-if)# bandwidth 1540
Router(config-if)# auto qos voip
Router(config-if)# exit
Configuring the AutoQoS — VoIP Feature on a Low-Speed Serial Interface Example
In this example, the AutoQoS — VoIP feature is configured on the low-speed serial interface s1/3.
Router# configure terminalRouter(config)# interface s1/3
Router(config-if)# bandwidth 512
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if# auto qos voip
Router(config-if)# exit
Configuring the AutoQoS — VoIP Feature on High-Speed Frame Relay Interfaces Example
In this example, the AutoQoS — VoIP feature is configured on the high-speed serial point-to-point Frame Relay subinterface s4/1.2.
Router> enableRouter# configure terminalRouter(config)# interface s4/1.2 point-to-point
Router(config-if)# bandwidth 1540
Router(config-if)# frame-relay interface-dlci 100
Router(config-fr-dlci)# auto qos voip
Router(config-if)# exit
Configuring the AutoQoS — VoIP Feature on Low-Speed Frame Relay Interfaces Example
In this example, the AutoQoS — VoIP feature is configured on the low-speed point-to-point Frame Relay subinterface s4/2.1.
Router# configure terminalRouter(config)# interface s4/2.1 point-to-point
Router(config-if)# bandwidth 512
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# frame-relay interface-dlci 100
Router(config-fr-dlci)# auto qos voip
Router(config-if)# exit
Configuring the AutoQoS — VoIP Feature on a High-Speed ATM PVC Example
In this example, the AutoQoS — VoIP feature is configured on the high-speed point-to-point ATM PVC ATM5/0.1.
Router# configure terminalRouter(config)# interface ATM5/0.1 point-to-point
Router(config-if)# pvc 1/32
Router(config-if)# vbr-nrt 1540 1540
Router(config-if)# auto qos voip
Router(config-if)# exit
Configuring the AutoQoS — VoIP Feature on a Low-Speed ATM PVC Example
In this example, the AutoQoS — VoIP feature is configured on a low-speed point-to-point ATM PVC ATM5/0.2.
Router# configure terminalRouter(config)# interface ATM5/0.2 point-to-point
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# pvc 1/32
Router(config-if)# vbr-nrt 512 512
Router(config-if)# auto qos voip
Router(config-if)# exit
Configuring the AutoQoS — VoIP Feature for Frame Relay-to-ATM Interworking Example
In this example, the AutoQoS — VoIP feature is configured for Frame Relay-to-ATM Interworking. The AutoQoS — VoIP feature is configured on the serial point-to-point subinterface s1/3.1.
Router# configure terminalRouter(config)# interface s1/3.1 point-to-point
Router(config-if)# bandwidth 512
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# frame-relay interface-dlci 100
Router(config-if)# auto qos voip fr-atm
Router(config-if)# exit
In this configuration, the optional fr-atm keyword is used to enable the AutoQoS — VoIP feature for the Frame Relay-to-ATM Interworking.
Note
The ATM-to-ATM side of the network needs no special configuration to distinguish it from the ATM-to-Frame Relay side of the network.
Verifying the AutoQoS — VoIP Feature Configuration Examples
When the auto qos voip command is used to configure the AutoQoS — VoIP feature, configurations are generated. These configurations are then used to create interface configurations, policy maps, class maps, and ACLs. The show auto qos interface command can be used to verify the contents of the interface configurations, policy maps, class maps, and ACLs.
This section contains the following sample output of the show auto qos interface command for interfaces, PVCs, and links.
Note
The show auto qos interface command output displays only those configurations created by the AutoQoS - VoIP feature.
Sample show auto qos interface Command Output for a High-Speed Serial Interface
The following is sample output of the show auto qos command for a high-speed serial interface:
Router# show auto qos interface s6/0Serial6/0 -!interface Serial6/0service-policy output AutoQoS-Policy-UnTrustSample show auto qos interface Command Output for a Low-Speed Serial Interface
The following is sample output of the show auto qos interface command for a low-speed serial interface:
Router# show auto qos interface s6/0Serial6/0 -!interface Serial6/0no ip addressencapsulation pppno fair-queueppp multilinkmultilink-group 2001100126!interface Multilink2001100126bandwidth 512ip address 10.10.100.1 255.255.255.0service-policy output AutoQoS-Policy-UnTrustppp multilinkppp multilink fragment-delay 10ppp multilink interleaveip rtp header-compression iphc-formatSample show auto qos Interface Command Output for a High-Speed Frame Relay Interface
The following is sample output of the show auto qos command for a high-speed Frame Relay interface:
Router# show auto qos interface s6/1.1Serial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 1540000frame-relay bc 15400frame-relay be 0frame-relay mincir 1540000service-policy output AutoQoS-Policy-UnTrust
Note
The output of the show autoqos interface command for high-speed Frame Relay interfaces is similar to the output for low-speed Frame Relay interfaces. The only difference is that Frame Relay Fragmentation and cRTP are not configured for high-speed Frame Relay interfaces.
Sample show auto qos interface Command Output for a Low-Speed Frame Relay Interface
The following is sample output of the show auto qos command for a low-speed Frame Relay interface:
Router# show auto qos interface s6/1.1Serial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640Sample show auto qos interface Command Output for a High-Speed ATM PVC
The following is sample output of the show auto qos command for a high-speed ATM PVC:
Router# show auto qos interface a2/0.1ATM2/0.1: PVC 1/100 -!interface ATM2/0.1 point-to-pointpvc 1/100tx-ring-limit 3service-policy output AutoQoS-Policy-UnTrustSample show auto qos interface Command Output for a Low-Speed ATM PVC
The following is sample output of the show auto qos command for a low-speed ATM PVC:
Router# show auto qos interface a2/0.1ATM2/0.1: PVC 1/100 -!interface ATM2/0.1 point-to-pointpvc 1/100tx-ring-limit 3encapsulation aal5mux ppp Virtual-Template200!interface Virtual-Template200bandwidth 512ip address 10.10.100.1 255.255.255.0service-policy output AutoQoS-Policy-UnTrustppp multilinkppp multilink fragment-delay 10ppp multilink interleaveSample show auto qos interface Command Output for Frame Relay-to-ATM Interworking Links
The following is sample output of the show auto qos command for Frame Relay-to-ATM Interworking links:
Router# show auto qos interface s6/1.1Serial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100 ppp Virtual-Template200class AutoQoS-VoIP-FR-Serial6/1-100!interface Virtual-Template200bandwidth 512ip address 10.10.100.1 255.255.0.0service-policy output AutoQoS-Policy-UnTrustppp multilinkppp multilink fragment-delay 10ppp multilink interleave!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000Additional References
For additional information related to AutoQoS — VoIP, refer to the following references:
•
MIBs
•
RFCs
Related Documents
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
RFCs TitleNo new or modified RFCs are supported by this feature, and support for existing standards has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 T command reference publications.
New Commands
auto qos voip
To configure the AutoQoS — VoIP feature on an interface, use the auto qos voip command in interface configuration mode or Frame Relay DLCI configuration mode. To remove the AutoQoS — VoIP feature from an interface, use the no form of this command.
auto qos voip [trust] [fr-atm]
no auto qos voip [trust] [fr-atm]
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Frame Relay DLCI configuration (for use with Frame Relay DLCIs)
Command History
Usage Guidelines
To enable the AutoQoS — VoIP feature for Frame Relay-to-ATM interworking, the fr-atm keyword must be configured explicitly. However, the fr-atm keyword affects low-speed DLCIs only. It does not affect high-speed DLCIs.
Note
DLCIs with link speeds lower than or equal to 768 kpbs are considered low-speed DLCIs; DLCIs with link speeds higher than 768 kpbs are considered high-speed DLCIs.
Depending on whether the trust keyword has been configured for this command, the AutoQoS — VoIP feature automatically creates one of the two following policy maps:
•
"AutoQoS-Policy-Trust" (created if the trust keyword is configured)
•
"AutoQoS-Policy-UnTrust" (created if the trust keyword is not configured)
Both of these policy maps, designed to handle the Voice over IP (VoIP) traffic on an interface or a permanent virtual circuit (PVC), can be modified to suit the quality of service (QoS) requirements of the network. To modify these policy maps, use the appropriate Cisco IOS command.
These policy maps should not be attached to an interface or PVC by using the service-policy command. If the policy maps are attached in this manner, the AutoQoS — VoIP feature (that is, the policy maps, class maps, and access control lists (ACLs)) will not be removed properly when the no auto qos voip command is configured.
For low-speed Frame Relay DLCIs interconnected with ATM PVCs in the same network, the fr-atm keyword must be explicitly configured in the auto qos voip command to configure the AutoQoS — VoIP feature properly. That is, the command must be configured as auto qos voip fr-atm.
For low-speed Frame Relay DLCIs configured with Frame Relay-to-ATM, Multilink PPP (MLP) over Frame Relay (MLPoFR) is configured automatically. The subinterface must have an IP address. When MLPoFR is configured, this IP address is removed and put on the MLP bundle. The AutoQoS — VoIP feature must also be configured on the ATM side by using the auto qos voip command.
The auto qos voip command is not supported on subinterfaces.
The auto qos voip command is available for Frame Relay DLCIs.
Disabling AutoQoS — VoIP
The no auto qos voip command disables the AutoQoS — VoIP feature and removes the configurations associated with the feature.
When the no auto qos voip command is used, the no forms of the individual commands originally generated by the AutoQoS — VoIP feature are configured. With the use of individual no forms of the commands, the system defaults are reinstated. The no forms of the commands will be applied just as if the user had entered the commands individually. As the configuration reinstating the default setting is applied, any messages resulting from the processing of the commands are displayed.
Note
If you delete a subinterface or PVC (either ATM or Frame Relay PVCs) without configuring the no auto qos voip command, the AutoQoS — VoIP feature will not be removed properly.
Examples
The following example shows the AutoQoS — VoIP feature configured on a serial point-to-point subinterface 4/1.2. In this example, both the trust and fr-dlci keywords are configured.
Router> enableRouter# configure terminalRouter(config)# interface s4/1.2 point-to-point
Router(config-if)# bandwidth 100
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# frame-relay interface-dlci 102
Router(config-fr-dlci)# auto qos voip trust fr-dlci
Router(config-if# exit
Related Commands
show auto qos
To display the configurations created by the AutoQoS — VoIP feature on a specific interface or all interfaces, use the show auto qos command in EXEC mode.
show auto qos [interface [interface type]]
Syntax Description
interface
(Optional) Indicates that the configurations for a specific interface type will be displayed.
interface type
(Optional) Specifies the interface type.
Defaults
By default, displays the configurations created for all interface types.
Command Modes
EXEC
Command History
Usage Guidelines
When the auto qos voip command is used to configure the AutoQoS — VoIP feature, configurations are generated for each interface or permanent virtual circuit (PVC). These configurations are then used to create the interface configurations, policy maps, class maps, and access control lists (ACLs). The show auto qos command can be used to verify the contents of the interface configurations, policy maps, class maps, and ACLs.
The show auto qos interface command can be used with Frame Relay data-link connection identifiers (DLCIs) and ATM PVCs.
Examples
The following section contains sample output of the show auto qos command when the various optional keywords are specified.
Note
The show auto qos command displays only those configurations created by the AutoQoS - VoIP feature.
show auto qos interface command Example
When the interface keyword is configured along with the corresponding interface type argument, the show auto qos interface [interface type] command displays the configurations created by the AutoQoS — VoIP feature on the specified interface.
In the following example, the serial subinterface S6/1.1 has been specified:
Router# show auto qos interface s6/1.1S6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640When the interface keyword is configured but an interface type is not specified, the show auto qos interface command displays the configurations created by the AutoQoS — VoIP feature on all the interfaces or PVCs on which the AutoQoS — VoIP feature is enabled.
Router# show auto qos interfaceSerial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640ATM2/0.1: PVC 1/100 -!interface ATM2/0.1 point-to-pointpvc 1/100tx-ring-limit 3encapsulation aal5mux ppp Virtual-Template200!interface Virtual-Template200bandwidth 512ip address 10.10.100.1 255.255.255.0service-policy output AutoQoS-Policy-UnTrustppp multilinkppp multilink fragment-delay 10ppp multilink interleaveshow auto qos Command Example
The show auto qos command displays all of the configurations created by the AutoQoS — VoIP feature.
Router# show auto qosSerial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640Table 1 describes the significant fields shown in the display.
Related Commands

