Table Of Contents
New Functionality for Show and More Commands
Command Reference
This section provides information on VoFR commands for Cisco IOS Release 12.1(2)E for the Cisco 7500 series routers with a Versatile Interface Processor. All other commands used with Voice over Frame Relay are documented in the Cisco IOS Release 12.1 command references.
New and modified debug commands can be found in the "Debug Commands" section.
The following new and modified commands are described in this section:
•
cptone *
•
•
•
•
•
New Functionality for Show and More Commands
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression on which you wish to search or filter:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line in which the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
called-number
To enable an incoming VoFR call leg to get bridged to the correct POTS call leg when using a static FRF.11 trunk connection, use the called-number command. Use the no form of this command to disable a static trunk connection.
called-number string
no called-numberSyntax Description
string
A string of digits including wildcards that specifies the telephone number of the voice-port dial peer.
Command Modes
Dial-peer configuration
Command History
12.0(3)XG
This command was first introduced.
12.1(2)E
This command was introduced for Cisco 7500 series routers with a Versatile Interface Processor.
Usage Guidelines
This command applies to the Cisco 2600, 3600, and 7500 series routers only. It is ignored on the Cisco MC3810 and the Cisco 7200 series.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
The called-number command is used only when the dial peer type is VoFR and you are using the frf11-trunk (FRF.11) session protocol; it is ignored at all times on the Cisco MC3810, and on all other platforms when using the cisco-switched session protocol.
Because FRF.11 does not provide any end-to-end messaging to manage a trunk, the called-number command is necessary to allow the router to establish an incoming trunk connection. The E.164 number is used to find a matching dial peer during call setup.
Examples
The following example shows how to configure a Cisco 2600, 3600, or 7500 series router for a static FRF.11 trunk connection to a specific telephone number (555-2150), starting from global configuration mode:
router(config)# voice-port 1/0/0router(config-voiceport)# connection trunk 5558000router(config-voiceport)# exitrouter(config)# dial-peer voice 100 potsrouter (config-dial-peer)# destination pattern 5552150router(config-dial-peer)# exitrouter(config)# dial-peer voice 200 vofrrouter (config-dial-peer)# session protocol frf11-trunkrouter(config-dial-peer)# called-number 5552150router(config-dial-peer)# destination pattern 5558000router(config-dial-peer)#Related CommandsRelated Commands
codec (dial-peer)
To specify the voice coder rate of speech for a VoFR dial peer, use the codec dial-peer configuration command. Use the no form of this command to reset the default value.
Cisco 2600, 3600 and 7500 series routers
codec {g711alaw | g711ulaw | g723ar53 | g723ar63 | g723r53 | g723r63 | g726r16 | g726r24 |
g726r32 | g728 | g729br8 | g729r8} [bytes payload_size]
no codecCisco MC3810
codec {g711alaw | g711ulaw | g726r32 | g729ar8 | g729r8} [bytes payload_size]
no codecSyntax Description
Cisco 2600, 3600 and 7500 series routers
Cisco MC3810
Defaults
g729r8, 30-byte payload for VoFR, VoATM, and VoHDLC
g729r8, 20-byte payload for VoIP
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use this command to define a specific voice coder rate of speech and payload size for a VoFR dial peer.
Note
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
This command does not apply to the Cisco 7200 series routers.
For toll quality, use g711alaw or g711ulaw. These values provide high-quality voice transmission but use a significant amount of bandwidth. For almost toll quality (and a significant savings in bandwidth), use the g729r8 value.
On the Cisco MC3810, you can also assign CODEC values to the voice port. If configuring calls to a Cisco MC3810 running software versions prior to 12.0(3)XG, configure the codec command on the voice port. If configuring Cisco-trunk permanent calls, configure the codec command on the dial peer. If you configure the codec command on the dial peer for Voice over Frame Relay permanent calls on the Cisco MC3810, the dial peer codec command setting overrides the codec setting configured on the voice port.
Note
Examples
The following example shows how to configure a voice coder rate that provides toll quality voice with a payload of 120 bytes per voice frame on a Cisco 2600 series or 3600 series router acting as a terminating node. The example configuration, starting from global configuration mode, is for VoFR dial peer 200:
router(config)# dial-peer voice 200 vofrrouter(config-dial-peer)# codec g711alaw bytes 120router(config-dial-peer)#Related CommandsRelated Commands
cptone
To specify a regional analog voice interface-related tone, ring, and cadence setting, use the cptone voice-port configuration command. Use the no form of this command to disable the selected tone.
cptone locale
no cptone localeSyntax Description
locale
Keyword specifying an analog voice interface-related default tone, ring, and cadence setting for a specified country.
Valid entries for the Cisco MC3810 prior to release 12.0(3)XG are: argentina, australia, austria, belgium, brazil, canada, china, colombia, czechrepublic, denmark, finland, france, germany, greatbritain, greece, hongkong, hungary, iceland, india, indonesia, ireland, israel, italy, japan, korea, luxembourg, malaysia, mexico, netherlands, newzealand, norway, peru, philippines, poland, portugal, russia, singapore, slovakia, slovenia, southafrica, spain, sweden, switzerland, taiwan, thailand, turkey, unitedstates, and venezuela.
The Cisco 2600 series, 3600 series and the Cisco MC3810 comply with the ISO 3166 country name standards, which use a two-letter code to represent a country. Valid entries are listed in Table 1.
Defaults
northamerica for the Cisco MC3810 for versions prior to Release 12.0(3)XG;
us for the Cisco 2600 series, 3600 series, 7500 series, and for the Cisco MC3810 for 12.0(3)XG and higherCommand Modes
Voice-port configuration
Command History
Usage Guidelines
This command only affects the tones generated at the local interface. It does not affect any information passed to the remote end of a connection, or any tones generated at the remote end of a connection.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
Examples
The following example configures United States as the call progress tone locale on the Cisco 3600 series, beginning from global configuration mode:
router(config)# voice-port 1/0/0router(config-voiceport)# cptone usThe following example configures Singapore as the call progress tone locale on the Cisco MC3810, beginning from global configuration mode:
router(config)# voice-port 1/1router(config-voiceport)# cptone sgRelated CommandsRelated Commands
dial-peer voice
To enter dial-peer configuration mode (and specify the method of voice-related encapsulation), use the dial-peer voice global configuration command.
Cisco 2600, 3600, and 7500 series routers
dial-peer voice tag {pots | vofr |voip}
Cisco 7200 series routers
dial-peer voice tag {vofr}
Cisco MC3810
dial-peer voice tag {pots | voatm | vofr | vohdlc}
Syntax Description
Cisco 2600 series, 3600 series, 7200, and 7500
Cisco MC3810
Defaults
There is no default setting for this command.
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to all voice applications on the Cisco MC3810 and the Cisco 2600, 3600, 7200, and 7500 series routers.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
Use the dial-peer voice global configuration command to switch to the dial-peer configuration mode from the global configuration mode. Use the exit command to exit the dial-peer configuration mode and return to the global configuration mode.
Examples
The following example shows how to access dial-peer configuration mode and configure a POTS peer identified as dial peer 100, starting from global configuration mode:
router(config)# dial-peer voice 100 potsrouter(config-dial-peer)#Related CommandsRelated Commands
dtmf-relay
To enable the generation of FRF.11 Annex A frames for a dial peer, use the dtmf-relay command. Use the no form of this command to disable the generation of FRF.11 Annex A frames and return to the default handling of dial digits.
dtmf-relay
no dtmf-relaySyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
12.0(3)XG
This command was first introduced.
12.1(2)E
This command was introduced for Cisco 7500 series routers with a Versatile Interface Processor.
Usage Guidelines
This command applies to all VoFR, VoATM, and VoHDLC applications on the Cisco MC3810, and to VoFR applications on the Cisco 2600, 3600, and 7500 series routers.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
Cisco recommends that this command be used with low bit-rate CODECs.
When dtmf-relay is enabled, the DSP generates Annex A frames instead of passing a DTMF tone through the network as a voice sample. For information about the payload format of FRF.11 Annex A frames, see Annex A - Dialed Digit Transfer Syntax, in Voice over Frame Relay Implementation Agreement - FRF.11.
Examples
The following example shows how to enable FRF.11 Annex A frames on a Cisco 2600, 3600, or 7200 series router or on an MC3810 concentrator for VoFR dial peer 200, starting from global configuration mode:
router(config)# dial-peer voice 200 vofrrouter(config-dial-peer)# dtmf-relayrouter(config-dial-peer)#Related CommandsRelated Commands
fax-rate
To establish the rate at which a fax will be sent to the specified dial peer, use the fax-rate dial-peer configuration command. Use the no form of this command to reset the dial peer for voice calls.
fax-rate {2400 | 4800 | 7200 | 9600 | 14400 | disable | voice}
no fax-rateSyntax Description
Defaults
voice
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use this command to specify the fax transmission rate to the specified dial peer.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
The values for this command apply only to the fax transmission speed and do not affect the quality of the fax itself. The higher values provide a faster transmission speed but monopolize a significantly larger portion of the available bandwidth. Slower transmission speeds use less bandwidth.
If the fax-rate transmission speed is set higher than the CODEC rate in the same dial peer, the data sent over the network for fax transmission will be above the bandwidth reserved for RSVP. Because more network bandwidth will be monopolized by the fax transmission, Cisco does not recommend setting the fax-rate value higher than the value of the selected CODEC. If the fax-rate value is set lower than the CODEC value, faxes will take longer to transmit but will use less bandwidth.
Examples
The following example configures a transmission speed of 9600 bps for faxes sent to a dial peer:
router(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# fax-rate 9600router(config-dial-peer)#Related CommandsRelated Commands
frame-relay fragment
To enable fragmentation of Frame Relay frames for a Frame Relay map class, use the frame-relay fragment command. Use the no form of this command to disable Frame Relay fragmentation.
frame-relay fragment fragment_size
no frame-relay fragment
Syntax Description
Defaults
Fragmentation is disabled.
Command Modes
Map-class configuration
Command History
12.0(3)XG
This command was first introduced.
12.1(2)E
This command was introduced for Cisco 7500 series routers with a Versatile Interface Processor.
Usage Guidelines
You should enable fragmentation for low-speed links (meaning those operating at less than 768 kbps).
Frame Relay fragmentation is enabled on a per-PVC basis. Before enabling Frame Relay fragmentation, you must first associate a Frame Relay map class with a specific data link connection identifier (DLCI), then enter map-class configuration mode and enable or disable fragmentation for that map class. In addition, you must enable Frame Relay traffic shaping on the interface in order for fragmentation to work.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
Selecting a Fragmentation Format
Frame Relay frames are fragmented using one of the following formats, depending on how the PVC is configured:
•
•
•
Cisco recommends pure end-to-end FRF.12 fragmentation on PVCs that are carrying VoIP packets and on PVCs that are sharing the link with other PVCs carrying VoFR traffic.
In pure end-to-end FRF.12 fragmentation, Frame Relay frames with a payload less than the fragment size configured for that PVC are transmitted without the fragmentation header.
FRF.11 Annex C and Cisco proprietary fragmentation are used when VoFR frames are transmitted on a PVC. When fragmentation is enabled on a PVC, FRF.11 Annex C format is triggered when vofr is configured on that PVC; Cisco proprietary format is triggered when vofr cisco is configured.
In FRF.11 Annex C and Cisco proprietary fragmentation, VoFR frames are never fragmented, and all data packets (including VoIP packets) contain the fragmentation header regardless of the payload size.
Selecting a Fragment Size
You should set the fragment size based on the lowest port speed between the routers. For example, for a hub-and-spoke Frame Relay topology where the hub has a T1 speed and the remote routers have 64 kbps port speeds, the fragmentation size must be set for the 64 kbps speed on both routers. Any other PVCs that share the same physical interface must use the same fragmentation size used by the voice PVC.
With pure end-to-end FRF.12 fragmentation, you should select a fragment size that is larger than the voice packet size.
Table 2 shows the recommended fragmentation sizes for a serialization delay of 10 ms.
Examples
The following example shows how to enable pure end-to-end FRF.12 fragmentation for the "frag" map class on a Cisco 2600, 3600, 7200, or 7500 series router, starting from global configuration mode. The fragment payload size is set to 160 bytes. Frame Relay traffic shaping is required on the PVC; the only queuing type supported on the PVC when fragmentation is configured is weighted fair queuing (WFQ).
router(config)# interface serial 1/0/0router(config-if)# frame-relay traffic-shapingrouter(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay cir 128000router(config-map-class)# frame-relay bc 1000router(config-map-class)# frame-relay fragment 160router(config-map-class)# frame-relay fair-queuerouter(config-map-class)#The following example shows how to enable FRF.11 Annex C fragmentation for data on a Cisco MC3810 PVC configured for VoFR. Note that fragmentation must be configured if a VoFR PVC is to carry data. The fragment payload size is set to 160 bytes. Frame Relay traffic shaping is required on the PVC; the only queuing type supported on the PVC when fragmentation is configured is weighted fair queuing (WFQ).
router(config)# interface serial 1/1router(config-if)# frame-relay traffic-shapingrouter(config-if)# frame-relay interface-dlci 101router(config-fr-dlci)# vofrrouter(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay cir 128000router(config-map-class)# frame-relay bc 1000router(config-map-class)# frame-relay fragment 160router(config-map-class)# frame-relay fair-queuerouter(config-map-class)#The following example shows how to enable Cisco proprietary Frame Relay fragmentation for the "frag" Frame Relay map class on a Cisco 2600, 3600, 7200, or 7500 series router, starting from global configuration mode. The fragment payload size is set to 160 bytes. Frame Relay traffic shaping is required on the PVC; the only queuing type supported on the PVC when fragmentation is configured is weighted fair queuing (WFQ).
router(config)# interface serial 2/0/0router(config-if)# frame-relay traffic-shapingrouter(config-if)# frame-relay interface-dlci 102router(config-fr-dlci)# vofr ciscorouter(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay cir 128000router(config-map-class)# frame-relay bc 1000router(config-map-class)# frame-relay fragment 160router(config-map-class)# frame-relay fair-queuerouter(config-map-class)#Related CommandsRelated Commands
frame-relay interface-dlci
To assign a data link connection identifier (DLCI) to a specified Frame Relay subinterface on the router or access server, use the frame-relay interface-dlci interface configuration command. Use the no form of this command to remove this assignment.
frame-relay interface-dlci dlci [ietf | cisco] [voice-encap size] [voice-cir cir]
no frame-relay interface-dlci dlci [ietf | cisco] [voice-encap size] [voice-cir cir]Syntax Description
Defaults
No DLCI is assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
This command is typically used for subinterfaces; however, it can also be used on main interfaces. Using the frame-relay interface-dlci command on main interfaces enables the use of routing protocols on interfaces that use Inverse ARP. The frame-relay interface-dlci command on a main interface is also valuable for assigning a specific class to a single PVC where special characteristics are desired. Subinterfaces are logical interfaces associated with a physical interface. You must specify the interface and subinterface before you can use this command to assign any DLCIs and any encapsulation or broadcast options. See the "Examples" section for the sequence of commands.
This command is required for all point-to-point subinterfaces; it is also required for multipoint subinterfaces for which dynamic address resolution is enabled. It is not required for multipoint subinterfaces configured with static address mappings.
When configuring the voice-encap option on the Cisco MC3810 to enable Voice over Frame Relay, set the data fragmentation size based on the port access rate. Table 3 lists recommended data fragmentation sizes for different port access rates. Note also that when the voice-encap option is configured on the Cisco MC3810, voice traffic is not shaped, and all priority queuing, custom queuing, and weighted fair queuing is disabled on the interface.
Note
The voice-cir option on the Cisco MC3810 provides call admission control; it does not provide traffic shaping. A call setup will be refused if the unallocated bandwidth available at the time of the request is not at least equal to the value of voice-cir.
When configuring the voice-cir option on the Cisco MC3810 for Voice over Frame Relay, do not set the value of this option to be higher than the physical link speed. If Frame Relay traffic shaping is enabled for a PVC sharing voice and data, do not configure the voice-cir option to be higher than the value set with the frame-relay mincir command. Note that voice traffic is not shaped when the voice-encap option is configured; thus, in this case the frame-relay mincir command is irrelevant.
Note
Table 3
64 kbps
80 bytes
128 kbps
160 bytes
256 kbps
320 bytes
512 kbps
640 bytes
1536 kbps (full T1)
1600 bytes
2048 kbps (full E1)
1600 bytes
1 The data fragmentation size is based on back-to-back Frame Relay. If you are sending traffic through an IGX with standard Frame Relay, subtract 6 bytes from the recommended data fragmentation size.
Recommended Data Fragmentation Sizes
For more information about automatically installing router configuration files over a Frame Relay network, see the "Loading System Images and Microcode" chapter in the Configuration Fundamentals Configuration Guide.
Examples
The following example assigns DLCI 100 to a serial interface, starting from global configuration mode:
router(config)# interface serial 1/1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)#The following example enables Voice over Frame Relay on DLCI 100 on a Cisco MC3810 and sets the data fragmentation size to 80 bytes:
router(config)# interface serial0router(config-if)# frame-relay interface-dlci 100 voice-encap 80router(config-fr-dlci)#The following example enables Voice over Frame Relay on DLCI 100 on a Cisco MC3810, sets the data fragmentation size to 80 bytes, and sets the voice CIR to 24000 bps:
router(config)# interface serial0router(config-if)# frame-relay interface-dlci 100 voice-encap 80 voice-cir 24000router(config-fr-dlci)#Related CommandsRelated Commands
frame-relay voice bandwidth
To specify how much bandwidth should be reserved for voice traffic on a specific data link connection identifier (DLCI), use the frame-relay voice bandwidth command. Use the no form of this command to release the bandwidth previously reserved for voice traffic.
frame-relay voice bandwidth bps_reserved
no frame-relay voice bandwidthSyntax Description
bps_reserved
The bandwidth in bps reserved for voice traffic for the specified map class. The range is from 8000 to 45000000 bps; the default is 0, which disables voice calls.
Defaults
Disabled (zero)
Command Modes
Map-class configuration
Command History
12.0(3)XG
This command was first introduced.
12.1(2)E
This command was introduced for Cisco 7500 series routers with a Versatile Interface Processor.
Usage Guidelines
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
To use this command, you must first associate a Frame Relay map class with a specific data link connection identifier (DLCI), then enter map-class configuration mode and set the amount of bandwidth to be reserved for voice traffic for that map class.
If a call is attempted and there is not enough remaining bandwidth reserved for voice to handle the additional call, the call will be rejected. For example, if 64 kbps is reserved for voice traffic, and a CODEC and payload size is being used that requires 10 kbps of bandwidth for each call, then the first 6 calls attempted will be accepted, but the 7th call will be rejected.
Note
Calculating Required Bandwidth
The bandwidth required for a voice call depends on the bandwidth of the CODEC, the voice packetization overhead, and the voice frame payload size. The smaller the voice frame payload size, the higher the bandwidth required for the call. To make the calculation, use the following formula:
required_bandwidth = codec_bandwidth x (1 + overhead / payload_size)
As an example, the overhead for VoFR voice packet is between 6 and 8 bytes: a 2-byte Frame Relay header, a 1- or 2-byte FRF.11 header (depending on the CID value), a 2-byte CRC, and a 1-byte trailing flag. If voice sequence numbers are enabled in the voice packets, there is an additional 1-byte sequence number. Table 4 shows the required voice bandwidth for the G.729 8000 bps speech coder for various payload sizes.
