Table Of Contents
signal timing idle suppress-voice
Command Reference
This section provides information on new and modified VoFR commands for Cisco IOS Release 12.0(3)XG for the Cisco 2600 series and 3600 series router platforms, and the Cisco MC3810 multiservice access concentrator. All other commands used with Voice over Frame Relay are documented in the Cisco IOS Release 12.0 command references.
New and modified debug commands can be found in the "Debug Commands" section.
Note
The Cisco 7200 series routers do not currently support Voice over Frame Relay applications.
The following new and modified commands are described in this section (modified commands are marked by an asterisk):
•
•
•
•
•
•
•
•
•
•
•
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.
Default
Disabled
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command applies to the Cisco 2600 series and 3600 series routers only. It is ignored on the Cisco MC3810 and the Cisco 7200 series.
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 series or 3600 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 Commands
codec (dial-peer)
connection
destination-pattern
dtmf-relay
fax-rate
session protocol
session target
signal-type
preferencecodec (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.
For the Cisco 2600 series and 3600 series routers:
codec {g711alaw | g711ulaw | g723ar53 | g723ar63 | g723r53 | g723r63 | g726r16 | g726r24 |
g726r32 | g728 | g729br8 | g729r8} [bytes payload_size]
no codecFor the Cisco MC3810:
codec {g711alaw | g711ulaw | g726r32 | g729ar8 | g729r8} [bytes payload_size]
no codecSyntax Description
For the Cisco 2600 series and 3600 series routers:
For the Cisco MC3810:
Default
g729r8, 30-byte payload for VoFR, VoATM, and VoHDLC
g729r8, 20-byte payload for VoIP
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared for VoIP dial peers in Cisco IOS Release 11.3(1)T.
This command was modified for VoFR dial peers in Cisco IOS Release 12.0(3)XG.
Use the codec command to define a specific voice coder rate of speech for a VoFR dial peer.
Note
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 Commands
called-number
connection
destination-pattern
dtmf-relay
fax-rate
preference
session protocol
session target
signal-type
vad (dial peer)connection
To specify a connection mode for a voice port, use the connection voice-port configuration command. Use the no form of this command to disable the selected connection mode.
connection {plar | tie-line | plar-opx} string | {trunk string [answer-mode]}
no connection {plar | tie-line | plar-opx} string | {trunk string [answer-mode]}Syntax Description
Default
No connection mode is specified.
Command Mode
Voice-port configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
The connection trunk answer-mode option was added in Cisco IOS Release 12.0(3)XG, and the connection trunk command was made available on the Cisco MC3810.
Use the connection command to specify a connection mode for a specific interface. For example, use the connection plar command to specify a PLAR interface. The string you configure for this command is used as the called number for all incoming calls over this connection. The destination peer is determined by the called number.
Use the connection trunk command to specify a straight tie-line connection to a PBX. You can use the connection trunk command for E&M-to-E&M trunks, FXO-to-FXS trunks, and FXS-to-FXS trunks. Signaling will be transported for E&M-to-E&M trunks and FXO-to-FXS trunks; signaling will not be transported for FXS-to-FXS trunks.
If you desire one of the devices in a static trunk connection to act as slave and receive calls only, use the answer-mode option with the connection trunk command when configuring that device.
Note
The connection tie-line command is used on the Cisco MC3810 when a dial plan requires that additional digits are added in front of any digits dialed by the PBX, and that the combined set of digits are used to route the call via the dial-peers and into the network. The operation is similar to the connection plar command operation, but in this case the tie-line port also waits to collect digits from the PBX. The tie-line digits are also automatically stripped by a terminating port.
If the connection command is not configured, the standard session application outputs a dial tone when the interface goes off-hook until enough digits are collected to match a dial-peer and complete the call.
Examples
The following example selects PLAR as the connection mode on the Cisco 3600 series, with a destination telephone number of 555-9262:
router(config)#voice-port 1/0/0router(config-voiceport)#connection trunk 5559262router(config-voiceport)#The following example selects tie-line as the connection mode on the Cisco MC3810, with a destination telephone number of 555-9262:
router(config)#voice-port 1/1router(config-voiceport)#connection tie-line 5559262router(config-voiceport)#The following example configures a Cisco 3600 series router for a trunk connection and specifies that it will establish the trunk only when it receives an incoming call:
router(config)#voice-port 1/0/0router(config-voiceport)#connection trunk 5559262 answer-moderouter(config-voiceport)#Related Commands
session-protocol
voice-portcptone
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
Default
northamerica for the Cisco MC3810 for versions prior to Release 12.0(3)XG;
us for the Cisco 2600 series, 3600 series, and for the Cisco MC3810 for 12.0(3)XG and higherCommand Mode
Voice-port configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
Support for the ISO 3166 two-letter country codes on the Cisco MC3810 was added in Cisco IOS Release 12.0(3)XG.
The cptone 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.
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 Commands
voice-port
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.
For the Cisco 2600 series and 3600 series:
dial-peer voice tag {pots | vofr |voip}
For the Cisco 7200 series:
dial-peer voice tag {vofr}
For the Cisco MC3810:
dial-peer voice tag {pots | voatm | vofr | vohdlc}
Syntax Description
For the Cisco 2600 series, 3600 series, and 7200 series:
For the Cisco MC3810:
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
This command applies to all voice applications on the Cisco MC3810 and the Cisco 2600 series, 3600 series, and 7200 series routers.
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 Commands
codec (dial-peer)
destination-pattern
dtmf-relay
preference
sequence-numbers
session protocol
session target
voice-port
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.
Default
Disabled
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command applies to all VoFR, VoATM, and VoHDLC applications on the Cisco MC3810, and to VoFR applications on the Cisco 2600 series and 3600 series routers.
It is recommended 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 series or 3600 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 Commands
called-number
codec (dial-peer)
connection
cptone
destination-pattern
session protocol
session target
signal-type
preferencefax-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
Default
voice
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
This command was first supported on the Cisco MC3810 in Cisco IOS Release 12.0(3)XG.
Use the fax-rate command to specify the fax transmission rate to the specified dial peer.
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 RVSP. Because more network bandwidth will be monopolized by the fax transmission, we do 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 Commands
frag-pre-queuing
To set the queuing on a Frame Relay or HDLC interface on a Cisco MC3810 to be perfomed after data fragmentation, use the frag-pre-queuing interface configuration command. Use the no form of this command to disable the queuing operation from taking place after data fragmentation, and to allow "fancy" queuing to be performed on the interface.
frag-pre-queuing
no frag-pre-queuingSyntax Description
This command has no arguments or keywords.
Default
Enabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(2)T.
This command is supported only on the Cisco MC3810.
For Frame Relay interfaces this command is enabled by default, which allows only first-come-first-served (FCFS) queuing on the interface. This command is only applicable if you use the frame-relay interface-dlci dlci voice-encap command, which disables all fancy queuing (such as priority queuing, weighted fair queuing, and custom queuing) on the interface. If you enter no frag-pre-queuing, you are allowed to configure fancy queuing on the interface. Note that if you enter no frag-pre-queuing, you must still explicitly configure the desired queuing type on the interface.
It is recommended that in most cases you enter no frag-pre-queuing for better memory usage on the Cisco MC3810, and so that fancy queuing can be configured.
Note
For HDLC encapsulation, enabling this command causes the queuing to take place after data fragmentation when the frame-relay interface-dlci dlci voice-encap command is used. Weighted fair queuing, custom queuing, and priority queuing are supported on an interface configured for Cisco HDLC when this command is enabled.
Examples
The following example configures a Frame Relay DLCI carrying voice traffic to also support fancy queuing:
router(config)#interface serial 0router(config-if)# no frag-pre-queuingrouter(config-if)# frame-relay interface-dlci 100 voice-encap 320router(config-fr-dlci)#Related Commands
frame-relay fair-queue
To enable weighted fair queuing for one or more Frame Relay PVCs, use the frame-relay fair-queue command in conjunction with the map-class frame-relay command. Use the no form of this command to disable weighted fair queuing for a Frame Relay map class.
frame-relay fair-queue [Congestive_Discard_Threshold [Number_Dynamic_Conversation_
Queues [Number_Reservable_Conversation_Queues
[Max_Buffer_Size_for_Fair_Queues]]]]
no frame-relay fair-queue [Congestive Discard Threshold [Number_Dynamic_Conversation_
Queues [Number_Reservable_Conversation_Queues
[Max_Buffer_Size_for_Fair_Queues]]]]Syntax Description
Default
Disabled
Command Mode
Map-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
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 enable or disable weighted fair queuing for that map class.
When Frame Relay fragmentation is enabled, weighted fair queuing is the only queuing strategy allowed.
If this command is entered without any accompanying numbers, the default values for each of the four parameters will be set. If you desire to alter only the value of the first parameter (Congestive Discard Threshold), you only need to enter the desired value for that parameter. If you desire to alter only the value of the second, third, or fourth parameters, you must enter values for the preceding parameters as well as for the parameter you wish to change.
Examples
The following example shows how to enable weighted fair queuing and set the default parameter values for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on an MC3810 concentrator, starting from global configuration mode:
router(config)#interface serial 1/1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class vofrrouter(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofrrouter(config-map-class)# frame-relay fair-queuerouter(config-map-class)#The following example shows how to enable weighted fair queuing and set the Congestive Discard Threshold parameter to a value other than the default value for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on an MC3810 concentrator, starting from global configuration mode:
router(config)#interface serial 1/1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class vofrrouter(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofrrouter(config-map-class)# frame-relay fair-queue 255router(config-map-class)#The following example shows how to enable weighted fair queuing and set the Number of Reservable Conversation Queues to a value of 25 for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on an MC3810 concentrator, starting from global configuration mode:
router(config)#interface serial 1/1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class vofrrouter(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofrrouter(config-map-class)# frame-relay fair-queue 64 256 25router(config-map-class)#Related Commands
class
frame-relay fragment
frame-relay interface-dlci
map-class frame-relayframe-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 fragmentSyntax Description
Default
Fragmentation is disabled.
Command Mode
Map-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
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.
Frame Relay frames are fragmented using one of the following formats, depending on how the PVC is configured:
•
•
•
Pure end-to-end FRF.12 fragmentation is recommended 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.
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.
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 series, 3600 series, or 7200 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 series, 3600 series, or 7200 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 Commands
class
frame-relay fair-queue
frame-relay interface-dlci
frame-relay traffic-shaping
map-class frame-relayframe-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
Default
No DLCI is assigned.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.0.
The voice-encap option was added in Cisco IOS Release 11.3(1) MA.
The voice-cir option was added in Cisco IOS Release 12.0(2) T.
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. 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 9
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 Commands
frag-pre-queuing
frame-relay class
vofrframe-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. To release the bandwidth previously reserved for voice traffic, use the no form of this command.
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.
Default
Disabled (zero)
Command Mode
Map-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
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. shows the required voice bandwidth for the G.729 8000 bps speech coder for various payload sizes.
To configure the payload size for the voice frames, use the codec command from dial-peer configuration mode.
Examples
The following example shows how to reserve 64 kbps for voice traffic for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on an MC3810 concentrator, starting from global configuration mode:
router(config)#interface serial 1/1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class vofrrouter(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofrrouter(config-map-class)# frame-relay voice bandwidth 64000router(config-map-class)#Related Commands
class
codec (dial-peer)
frame-relay fair-queue
frame-relay fragment
frame-relay interface-dlci
map-class frame-relaypreference
To indicate the preferred order of a dial peer within a hunt group, use the preference dial-peer configuration command. Use the no form of this command to remove the preference value on the voice port.
preference value
no preference valueSyntax Description
value
An integer value from 0 to 10, where the lower the number, the higher the preference. The default value is 0 (highest preference).
Default
0 (highest preference)
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3 MA.
This command was first supported on the Cisco MC3810 in Cisco IOS Release 11.3(1)MA.
This command was first supported on the Cisco 2600 series and Cisco 3600 series routers in Cisco IOS Release 12.0(3)T.
This command applies to POTS dial peers, Voice over IP (VoIP) dial peers, and Voice over Frame Relay (VoFR) dial peers on the Cisco 2600 series and 3600 series routers. This command applies to POTS dial peers, Voice over Frame Relay (VoFR) dial peers, Voice over ATM dial peers, and Voice over HDLC dial peers on the Cisco MC3810.
Setting the preference enables the desired dial peer to be selected when multiple dial peers within a hunt group are matched for a dial string.
Note
Examples
The following example configures POTS dial peer 10 to a preference of 1, POTS dial peer 20 to a preference of 2, and VoFR dial peer 30 to a preference of 3:
router(config)#dial-peer voice 10 potsrouter (config-dial-peer)# destination pattern 5552150router(config-dial-peer)# preference 1router(config-dial-peer)# exitrouter(config)#dial-peer voice 20 potsrouter (config-dial-peer)# destination pattern 5552150router(config-dial-peer)# preference 2router(config-dial-peer)# exitrouter(config)#dial-peer voice 30 vofrrouter (config-dial-peer)# destination pattern 5552150router(config-dial-peer)# preference 3router(config-dial-peer)# exitrouter(config)#Related Commands
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
session protocol
session target
signal-type
sequence-numbers
To enable the generation of sequence numbers in each frame generated by the DSP for VoFR applications, use the sequence-numbers command from dial-peer configuration mode. To disable the generation of sequence numbers, use the no form of this command.
sequence-numbers
no sequence-numbersSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
Sequence numbers on voice packets allow the DSPs at the playout side to detect lost packets, duplicate packets or out-of-sequence packets. This helps the DSP to mask out occasional drop-outs in voice transmission at the cost of one extra byte per packet. The benefit of using sequence numbers versus the cost in bandwidth of adding an extra byte to each voice packet on the Frame Relay network must be weighed to determine whether or not to disable this function for your application.
Another factor to consider is that this command does not affect codecs that require a sequence number, such as G.726. If you are using a codec that requires a sequence number, the DSP will generate one regardless of the configuration of this command.
Examples
The following example shows how to disable the generation of sequence numbers for VoFR frames on a Cisco 2600 series or 3600 series router or on a Cisco MC3810 concentrator for VoFR dial peer 200, starting from global configuration mode:
router(config)#dial-peer voice 200 vofrrouter(config-dial-peer)# no sequence-numbersrouter(config-dial-peer)#Related Commands
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
session protocol
session target
signal-typesession protocol
To establish a VoFR protocol for calls between the local and remote routers via the packet network, use the session protocol dial-peer configuration command. Use the no form of this command to reset the default value for this command.
session protocol {cisco-switched | frf11-trunk}
no session protocolSyntax Description
cisco-switched
Specifies proprietary Cisco VoFR session protocol. (This is the only valid session protocol for the Cisco 7200 series.)
frf11-trunk
Specifies FRF.11 session protocol.
Default
cisco-switched
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
The cisco-switched and frf11-trunk keywords were added in Cisco IOS Release 12.0(3)XG and apply only to VoFR dial peers.
For Cisco-to-Cisco dial peer connections, it is recommended that you use the default session protocol due to the advantages it offers over a pure FRF.11 implementation. When connecting to FRF.11-compliant equipment from other vendors, use the frf11-trunk session protocol.
Note
Examples
The following example shows how to configure the frf11-trunk session protocol on a Cisco 2600 series or 3600 series router for VoFR dial peer 200, starting from global configuration mode:
router(config)#dial-peer voice 200 vofrrouter(config-dial-peer)# session protocol frf11-trunkrouter(config-dial-peer)# called-number 5552150router(config-dial-peer)#The following example shows how to configure the frf11-trunk session protocol on a Cisco MC3810 concentrator for VoFR dial peer 200, starting from global configuration mode:
router(config)#dial-peer voice 200 vofrrouter(config-dial-peer)# session protocol frf11-trunkrouter(config-dial-peer)#Related Commands
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
preference
session target
signal-typesession target
To specify a network-specific address for a dial peer, use the session target dial-peer configuration command. Use the no form of this command to disable this feature.
Note
For Cisco 2600 series and 3600 series VoFR dial peers:
session target interface dlci [cid]
no session targetFor Cisco 7200 series VoFR dial peers:
session target interface dlci
no session targetFor Cisco MC3810 VoFR dial peers:
session target interface dlci [cid]
no session targetFor Cisco 2600 series and 3600 series VoIP dial peers:
session target {ipv4:destination-address | dns:[$s$. | $d$. | $e$. | $u$.] host-name |
loopback:rtp | loopback:compressed | loopback:uncompressed}
no session targetFor Cisco MC3810 Voice over ATM dial peers:
session target interface pvc {name | vpi/vci | vci}
no session targetFor Cisco MC3810 Voice over HDLC dial peers:
session target interface
no session targetSyntax Description
For Cisco 2600 series and 3600 series VoFR dial peers:
For Cisco 7200 series VoFR dial peers:
For Cisco MC3810 VoFR dial peers:
For Cisco 3600 series VoIP dial peers:
For Cisco MC3810 Voice over ATM dial peers:
For Cisco MC3810 Voice over HDLC dial peers:
Default
The default for this command is enabled with no IP address or domain name defined.
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
Use the session target command to specify a network-specific address or domain name for a dial peer. Whether you select a network-specific address or a domain name depends on the session protocol you select.
For VoFR dial peers, the "cid" option is not allowed when using the "cisco-switched" session protocol.
The session target loopback command is used for testing the voice transmission path of a call. The loopback point will depend on the call origination and the loopback type selected.
The session target dns command can be used with or without the specified wildcards. Using the optional wildcards can reduce the number of VoIP dial peer session targets you need to configure if you have groups of numbers associated with a particular router.
Examples
The following example shows how to configure serial interface 1/0, DLCI 100 as the session target for VoFR dial peer 200 (an FRF.11 dial peer) on a Cisco 2600 series or 3600 series router. We start from global configuration mode and use the "frf11-trunk" session protocol:
router(config)#dial-peer voice 200 vofrrouter(config-dial-peer)# destination-pattern 13102221111router (config-dial-peer)# called-number 5552150router(config-dial-peer)# session protocol frf11-trunkrouter (config-dial-peer)# session target serial 1/0 100 20router(config-dial-peer)#The following example shows how to configure serial interface 1/1, DLCI 200 as the session target for switched VoFR dial peer 400 on a Cisco 2600 series, 3600 series, or 7200 series router, using the "cisco-switched" session protocol and starting from global configuration mode:
router(config)#dial-peer voice 400 vofrrouter(config-dial-peer)# destination-pattern 13102221111router (config-dial-peer)# session target serial 1/1 200router(config-dial-peer)#The following example configures a session target for a VoFR dial peer on a Cisco MC3810 with a session target on serial port #1 and a DLCI of 200:
router(config)#dial-peer voice 11 vofrrouter(config-dial-peer)# destination-pattern 13102221111router (config-dial-peer)# session target Serial1 200router(config-dial-peer)#The following example configures a session target for a VoIP dial peer using DNS for a host, "voice_router," in the domain "cisco.com:"
voip(config)#dial-peer voice 10 voipvoip (config-dial-peer)# session target dns:voice_router.cisco.comvoip(config-dial-peer)#The following example configures a session target for a VoIP dial peer using DNS, with the optional $u$. wildcard. In this example, the destination pattern has been configured to allow for any four-digit extension, beginning with the numbers 1310222. The optional wildcard $u$. indicates that the router will use the unmatched portion of the dialed number—in this case, the four-digit extension, to identify the dial peer. As in the previous example, the domain is "cisco.com."
voip(config)#dial-peer voice 10 voipvoip (config-dial-peer)# destination-pattern 1310222....voip (config-dial-peer)# session target dns:$u$.cisco.comvoip (config-dial-peer)#The following example configures a session target for a VoIP dial peer using DNS, with the optional $d$. wildcard. In this example, the destination pattern has been configured for 13102221111. The optional wildcard $d$. indicates that the router will use the destination pattern to identify the dial peer in the "cisco.com" domain.
voip(config)#dial-peer voice 10 voipvoip (config-dial-peer)# destination-pattern 13102221111voip (config-dial-peer)# session target dns:$d$.cisco.comvoip (config-dial-peer)#The following example configures a session target for a VoIP dial peer using DNS, with the optional $e$. wildcard. In this example, the destination pattern has been configured for 12345. The optional wildcard $e$. indicates that the router will reverse the digits in the destination pattern, add periods between the digits, and then use this reverse-exploded destination pattern to identify the dial peer in the "cisco.com" domain.
voip(config)#dial-peer voice 10 voipvoip (config-dial-peer)# destination-pattern 12345voip (config-dial-peer)# session target dns:$e$.cisco.comThe following example configures a session target for a Voice over ATM dial peer on a Cisco MC3810. The session target is sent to ATM interface 0, and is for a PVC with a VCI of 20.
voatm(config)#dial-peer voice 12 voatmvoatm(config-dial-peer)# destination-pattern 13102221111voatm (config-dial-peer)# session target atm0 pvc 20voatm(config-dial-peer)#The following example configures a session target on serial port 0 for Voice over HDLC on a Cisco MC3810:
vohdlc(config)#dial-peer voice 13 vohdlcvohdlc(config-dial-peer)# destination-pattern 13102221111vohdlc (config-dial-peer)# session target Serial0vohdlc(config-dial-peer)#Related Commands
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
session protocol
signal-type
preferenceshow call active voice
To show the active call table, use the show call active voice command from EXEC or privileged EXEC mode.
show call active voice [brief]
Syntax Description
Command Mode
EXEC or privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
This command was modified for VoFR applications in Cisco IOS Release 12.0(3)XG, and support for the command was added to the Cisco 7200 series routers.
This command applies to all voice applications on the Cisco 2600 series, 3600 series, and 7200 series routers; it is not supported on the Cisco MC3810.
Use the show call active voice command to display the contents of the active call table, which shows all of the calls currently connected through the router.
For each call, there are two call legs, usually a POTS call leg and either a VoFR or VoIP call leg. A call leg is a discrete segment of a call connection that lies between two points in the connection. Each dial peer creates a call leg, as shown in .
Figure 20 Call Legs Example
These two call legs are associated by the connection ID. The connection ID will be the same for the two call legs within each router.
Examples
The following is sample output from the show call active voice command for a VoFR call:
3640_vofr#show call active voiceGENERIC:SetupTime=25594 msIndex=1PeerAddress=+2602110PeerSubAddress=PeerId=800PeerIfIndex=17LogicalIfIndex=0ConnectTime=25596CallState=4CallOrigin=2ChargedUnits=0InfoType=2TransmitPackets=105992TransmitBytes=2436775ReceivePackets=105993ReceiveBytes=2224812VOFR:ConnectionId=[0x23539D01 0x99840003 0x0 0x18FAB]Subchannel=[Interface Serial1/0, DLCI 100, CID 10]SessionProtocol=cisco-switchedSessionTarget=Serial1/0 100CalledNumber=VADEnable=ENABLEDCoderTypeRate=g729r8CodecBytes=20SignalingType=casDTMFRelay=ENABLEDUseVoiceSequenceNumbers=ENABLEDGENERIC:SetupTime=25595 msIndex=1PeerAddress=+3642200PeerSubAddress=PeerId=100PeerIfIndex=12LogicalIfIndex=0ConnectTime=25595CallState=4CallOrigin=1ChargedUnits=0InfoType=2TransmitPackets=106177TransmitBytes=2015629ReceivePackets=106176ReceiveBytes=2228655TELE:ConnectionId=[0x23539D01 0x99840003 0x0 0x18FAB]TxDuration=2116590 msVoiceTxDuration=2116590 msFaxTxDuration=0 msCoderTypeRate=g729r8NoiseLevel=0ACOMLevel=20OutSignalLevel=-79InSignalLevel=-79InfoActivity=2ERLLevel=20SessionTarget=The following is sample output from the show call active voice command for a VoIP call:
router#show call active voiceGENERIC:SetupTime=21072Index=1PeerAddress=+3642115PeerSubAddress=PeerId=400 PeerIfIndex=17LogicalIfIndex=0ConnectTime=26005CallState=3CallOrigin=2ChargedUnits=0 InfoType=2TransmitPackets=375413TransmitBytes=7508260ReceivePackets=377734 ReceiveBytes=7554680VOIP: ConnectionId[0x19BDF910 0xAF500007 0x0 0x58ED0]RemoteIPAddress=17635075 RemoteUDPPort=16394RoundTripDelay=0SelectedQoS=0SessionProtocol=1 SessionTarget=OnTimeRvPlayout=0GapFillWithSilence=0GapFillWithPrediction=600 GapFillWithInterpolation=0GapFillWithRedundancy=0HiWaterPlayoutDelay=110 LoWaterPlayoutDelay=64ReceiveDelay=94VADEnable=0CoderTypeRate=0GENERIC:SetupTime=21072Index=1PeerAddress=+14085271001PeerSubAddress= PeerId=200PeerIfIndex=12LogicalIfIndex=5ConnectTime=21115CallState=4CallOrigin=1 ChargedUnits=0InfoType=1TransmitPackets=377915TransmitBytes=7558300 ReceivePackets=375594ReceiveBytes=7511880TELE:ConnectionId=[0x19BDF910 0xAF500007 0x0 0x58ED0]TxDuration=16640 VoiceTxDuration=16640FaxTxDuration=0CoderTypeRate=0NoiseLevel=0ACOMLevel=4 OutSignalLevel=-440InSignalLevel=-440InfoActivity=2ERLLevel=227 SessionTarget=provides an alphabetical listing of the fields in this output and a description of each field.
Related Commands
show call history voice
show dial-peer voice
show frame-relay pvc
show frame-relay vofr
show voice-portshow call history voice
To display the call history table, use the show call history voice command from EXEC or privileged EXEC mode.
For the Cisco 2600 series, 3600 series, and 7200 series routers:
show call history voice [last number] [brief]
For the Cisco MC3810:
show call history voice record
Syntax Description
For the Cisco 2600 series, 3600 series, and 7200 series routers:
For the Cisco MC3810, this command has no arguments or keywords.
Command Mode
EXEC or privileged EXEC
Usage Guidelines
This command first appeared for VoIP applications in Cisco IOS Release 11.3(1)T.
This command was modified for VoFR applications in Cisco IOS Release 12.0(3)XG.
This command applies to all voice applications on the Cisco MC3810 and the Cisco 2600 series, 3600 series, and 7200 series routers.
Use the show call history voice command to display the call history table. The call history table contains a listing of all calls connected through this router in descending time order since Voice over IP or Voice over Frame Relay was enabled. You can display subsets of the call history table by using specific keywords. To display the last calls connected through this router, use the keyword last, and define the number of calls to be displayed with the argument number.
Examples
The following is sample output from the show call history voice command for a VoFR call using the frf11-trunk session protocol:
router#show call history voice last 1GENERIC:SetupTime=8283963 msIndex=3149PeerAddress=3623110PeerSubAddress=PeerId=3400PeerIfIndex=18LogicalIfIndex=0DisconnectCause=3FDisconnectText=service or option not available, unspecifiedConnectTime=8283963DisconectTime=8285463CallOrigin=1ChargedUnits=0InfoType=2TransmitPackets=94TransmitBytes=2751ReceivePackets=0ReceiveBytes=0VOFR:ConnectionId=[0x3D4B232D 0x6A900627 0x0 0x4F00852]Subchannel=[Interface Serial0/0, DLCI 160, CID 10]SessionProtocol=frf11-trunkSessionTarget=Serial0/0 160 10CalledNumber=2603100VADEnable=ENABLEDCoderTypeRate=g729r8CodecBytes=30SignalingType=casDTMFRelay=DISABLEDUseVoiceSequenceNumbers=DISABLEDGENERIC:SetupTime=8283963 msIndex=3150PeerAddress=2601100PeerSubAddress=PeerId=1100PeerIfIndex=7LogicalIfIndex=0DisconnectCause=3FDisconnectText=service or option not available, unspecifiedConnectTime=8283964DisconectTime=8285464CallOrigin=2ChargedUnits=0InfoType=2TransmitPackets=0TransmitBytes=-121ReceivePackets=94ReceiveBytes=2563TELE:ConnectionId=[0x3D4B232D 0x6A900627 0x0 0x4F00852]TxDuration=15000 msVoiceTxDuration=2010 msFaxTxDuration=0 msCoderTypeRate=g729r8NoiseLevel=-68ACOMLevel=20SessionTarget=The following is sample output from the show call history voice command for a VoIP call:
router#show call history voiceGENERIC:SetupTime=20405Index=0PeerAddress=PeerSubAddress=PeerId=0 PeerIfIndex=0LogicalIfIndex=0DisconnectCause=NORMALDisconnectText=ConnectTime=0 DisconectTime=20595CallOrigin=2ChargedUnits=0InfoType=0TransmitPackets=0 TransmitBytes=0ReceivePackets=0ReceiveBytes=0VOIP:ConnectionId[0x19BDF910 0xAF500006 0x0 0x56590]RemoteIPAddress=17635075 RemoteUDPPort=16392RoundTripDelay=0SelectedQoS=0SessionProtocol=1 SessionTarget=OnTimeRvPlayout=0GapFillWithSilence=0GapFillWithPrediction=0 GapFillWithInterpolation=0GapFillWithRedundancy=0HiWaterPlayoutDelay=0 LoWaterPlayoutDelay=0ReceiveDelay=0VADEnable=0CoderTypeRate=0TELE: ConnectionId=[0x19BDF910 0xAF500006 0x0 0x56590]TxDuration=3030 VoiceTxDuration=2700FaxTxDuration=0CoderTypeRate=0NoiseLevel=0ACOMLevel=0SessionTarget=provides an alphabetical listing of the fields in this output and a description of each field.
The following example displays a voice call history record for a local call between two telephones attached to the same Cisco MC3810:
router#show call history voice recordConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1418 msCallingNumber=2001SetupTime=1157801 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=local onhookConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1422 msCalledNumber=2002SetupTime=1157802 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=remote onhookexplains the fields in the sample output.
Related Commands
show call active voice
show dial-peer voice
show frame-relay pvc
show frame-relay vofr
show voice-portshow dial-peer voice
To display configuration information and call statistics for dial peers, use the show dial-peer voice command from EXEC or privileged EXEC mode.
For the Cisco 2600 series, 3600 series, and 7200 series routers:
show dial-peer voice [tag]
For the Cisco MC3810:
show dial-peer voice [tag] [summary]
Syntax Description
For the Cisco 2600 series, 3600 series, and 7200 series routers:
For the Cisco MC3810:
Command Mode
EXEC or privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
This command was modified in Cisco IOS Release 12.0(3)XG to support VoFR for the Cisco 2600 series, 3600 series, and 7200 series routers.
The following dial peers are supported on each Cisco platform:
Cisco 2600 and 3600 series
POTS, VoIP, VoFR
Cisco 7200 series
VoFR
Cisco MC3810
POTS, VoFR, VoATM, VoHDLC
Use the show dial-peer voice command to display configuration and call data for all dial peers configured for the router. To display information for one specific dial peer, use the argument tag to identify the dial peer.
Examples
The following is sample output from the show dial-peer voice command for a POTS dial peer:
router# show dial-peer voice 1VoiceEncapPeer100tag = 100, destination-pattern = `+3642200',answer-address = `',group = 100, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 1/unlimited,DTMF Relay = disabled,type = pots, prefix = `',session-target = `', voice-port = '2/0/0',direct-inward-dial = disabled,Connect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0,Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.The following is sample output from the show dial-peer voice command for a VoIP dial peer:
router# show dial-peer voice 10VoiceOverIpPeer500tag = 500, destination-pattern = `+3620...',answer-address = `',group = 500, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,type = voip, session-target = `ipv4:1.13.74.2',ip precedence: 0, UDP checksum = disabled,session-protocol = cisco, req-qos = best-effort,acc-qos = best-effort,fax-rate = voice payload size 20 bytescodec = g711alaw, payload size = 160 bytes,Expect factor = 10, Icpif = 30, signaling-type = cas,VAD = enabled, Poor QOV Trap = disabled,Connect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0,Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.The following is sample output from the show dial-peer voice command for a VoFR dial peer:
vofr# show dial-peer voice 700VoiceOverFRPeer700tag = 700, destination-pattern = `+2601...',answer-address = `',group = 700, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,type = vofr, session-target = `Serial1/0 100',called number= `',ip precedence: 0 session-protocol = cisco-switched,fax-rate = voice payload size 20 bytescodec = g729r8, payload size = 20 bytes,signaling-type = cas,VAD = enabled,Voice Sequence Numbers = enabled,Connect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0,Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.provides an alphabetical listing of the fields in these displays and a description of each field.
Related Commands
show call active voice
show call history voice
show frame-relay pvc
show frame-relay vofr
show voice-portshow frame-relay fragment
To display information about the Frame Relay fragmentation taking place in your Cisco router, enter the show frame-relay fragment command from privileged EXEC mode.
show frame-relay fragment [interface interface [dlci]]
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
When no parameters are specified with this command, the output displays a summary of each DLCI configured for fragmentation. The information displayed includes the fragmentation type, the configured fragment size, and the number of fragments transmitted, received, and dropped.
When a specific interface and DLCI are specified, additional details are displayed.
Note
Examples
The following is sample output for the show frame-relay fragment command without any parameters specified:
router#show frame-relay fragmentinterface dlci frag-type frag-size in-frag out-frag dropped-fragSerial0 108 VoFR-cisco 100 1261 1298 0Serial0 109 VoFR 100 0 243 0Serial0 110 end-to-end 100 0 0 0The following is sample output for the show frame-relay fragment command when an interface and DLCI are specified:
router# show frame-relay fragment interface Serial1/0 16fragment-size 45 fragment type end-to-endin fragmented pkts 0 out fragmented pkts 0in fragmented bytes 0 out fragmented bytes 0in un-fragmented pkts 0 out un-fragmented pkts 0in un-fragmented bytes 0 out un-fragmented bytes 0in assembled pkts 0 out pre-fragmented pkts 0in assembled bytes 0 out pre-fragmented bytesin dropped reassembling pkts 0 out dropped fragmenting pkts 0in timeouts 0in out-of-sequence fragments 0in fragments with unexpected B bit set 0out interleaved packets 0describes the significant fields in this output.
Related Commands
show frame-relay pvc
show frame-relay vofr
show interfaces serial
show traffic-shape queueshow frame-relay pvc
To display statistics about PVCs for Frame Relay interfaces, use the show frame-relay pvc command from privileged EXEC mode.
show frame-relay pvc [interface interface [dlci]]
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.0.
This command is modified in Cisco IOS Release 12.0(3)XG to include the fragmentation type and size associated with a particular PVC when fragmentation is enabled on the PVC.
When vofr or vofr cisco have been configured on the PVC, and a voice bandwidth has been allocated to the class associated with this PVC, configured voice bandwidth and used voice bandwidth are also displayed.
Statistics Reporting
To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.
Per VC counters are not incremented at all when either autonomous or SSE switching is configured; therefore, PVC values will be inaccurate if either switching method is used.
Traffic Shaping
Congestion control mechanisms are currently not supported, but the switch passes forward explicit congestion notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligibility (DE) bits unchanged from entry to exit points in the network.
If an LMI status report indicates that a PVC is not active, then it is marked as inactive. A PVC is marked as deleted if it is not listed in a periodic LMI status message.
Examples
The various displays in this section show sample output for a variety of different PVCs. Some of the PVCs carry data only; some carry a combination of voice and data.
Below is sample output from the show frame-relay pvc command for a PVC carrying voice over Frame Relay configured via the vofr cisco command. The frame-relay voice bandwidth command has been configured on the class associated with this PVC, as has fragmentation. The fragmentation employed is Cisco proprietary.
A sample configuration for this scenario is shown first; then the output for the show frame-relay pvc command.
interface serial 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 108vofr ciscoclass vofr-classmap-class frame-relay vofr-classframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000frame-relay voice bandwith 25000Router# show frame-relay pvc 108PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 108, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 1260 output pkts 1271 in bytes 95671out bytes 98604 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 1271 out bcast bytes 98604pvc create time 09:43:17, last time pvc status changed 09:43:17Service type VoFR-ciscoconfigured voice bandwidth 25000, used voice bandwidth 0voice reserved queues 24, 25fragment type VoFR-cisco fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 2592 bytes 205140 pkts delayed 1296 bytes delayed 102570shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Note that the "fragment type" field in the show frame-relay pvc display can have the following entries:
•
•
•
Below is sample output from the show frame-relay pvc command for an application employing pure FRF.12 fragmentation. A sample configuration for this scenario is shown first; then the output for the show frame-relay pvc command.
interface serial 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 110class fragmap-class frame-relay fragframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000Router# show frame-relay pvc 110PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 0 output pkts 243 in bytes 0out bytes 7290 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 243 out bcast bytes 7290pvc create time 04:03:17, last time pvc status changed 04:03:18fragment type end-to-end fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 486 bytes 14580 pkts delayed 243 bytes delayed 7290shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Note that when voice is not configured, voice bandwidth output is not displayed.
The following is sample output from the show frame-relay pvc command for multipoint subinterfaces carrying data only. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing. Note that neither fragmentation nor voice is configured on this PVC.
Router# show frame-relay pvcDLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103input pkts 10 output pkts 7 in bytes 6222out bytes 6034 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:13:11 last time pvc status changed 0:11:46DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104input pkts 20 output pkts 8 in bytes 5624out bytes 5222 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:03:57 last time pvc status changed 0:03:48provides a listing of the fields in these displays and a description of each field.
Related Commands
show dial-peer voice
show frame-relay fragment
show frame-relay vofr
show interfaces serial
show traffic-shape queueshow frame-relay vofr
To display information about the FRF.11 subchannels being used on VoFR DLCIs, use the show frame-relay vofr command from privileged EXEC mode.
show frame-relay vofr [interface [dlci [cid]]]
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
If this command is entered without specifying an interface, FRF.11 subchannel information will be displayed for all VoFR interfaces and DLCIs configured on the router.
Note
Examples
The following is sample output from the show frame-relay vofr command when an interface is not specified:
3640_vofr#show frame-relay vofrinterface vofr-type dlci cid cid-typeSerial0/0.1 VoFR 16 4 dataSerial0/0.1 VoFR 16 5 call-controlSerial0/0.1 VoFR 16 10 voiceSerial0/1.1 VoFR cisco 17 4 dataThe following is sample output from the show frame-relay vofr command when an interface is specified:
3640_vofr#show frame-relay vofr serial0interface vofr-type dlci cid cid-typeSerial0 VoFR 16 4 dataSerial0 VoFR 16 5 call-controlSerial0 VoFR 16 10 voiceThe following is sample output from the show frame-relay vofr command when an interface and a DLCI are specified:
3640_vofr#show frame-relay vofr serial0 16VoFR Configuration for interface Serial0dlci vofr-type cid cid-type input-pkts output-pkts dropped-pkts16 VoFR 4 data 0 0 016 VoFR 5 call-control 85982 86099 016 VoFR 10 voice 2172293 6370815 0The following is sample output from the show frame-relay vofr command when an interface, a DLCI, and a CID are specified:
3640_vofr#show frame-relay vofr serial0 16 10VoFR Configuration for interface Serial0 dlci 16vofr-type VoFR cid 10 cid-type voiceinput-pkts 2172293 output-pkts 6370815 dropped-pkts 0describes the fields shown in the display.
Table 17 Show Frame-Relay VoFR Field Descriptions
Related Commands
show call active voice
show call history voice
show dial-peer voice
show frame-relay fragment
show frame-relay pvc
show voice-portshow interfaces serial
Use the show interfaces serial command from EXEC or privileged EXEC mode to display information about a serial interface. When using Frame Relay encapsulation, use the show interfaces serial EXEC command to display information about the multicast DLCI, the DLCIs used on the interface, and the DLCI used for the Local Management Interface (LMI).
show interfaces serial number [accounting] [statistics]
Syntax Description
Command Mode
EXEC or privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.0.
The output for this command was modified for VoFR applications in Cisco IOS Release 12.0(3)XG.
Use this command to determine the status of the Frame Relay link. This display also indicates Layer 2 status if SVCs are configured.
Examples
The following is sample output from the show interfaces serial command for a VoFR application:
Router# show interfaces serial 0/0Serial0/0 is up, line protocol is upHardware is CD2430 in sync modeInternet address is 26.0.0.6/8MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,reliablility 255/255, txload 1/255, rxload 1/255Encapsulation FRAME-RELAY, loopback not setKeepalive not setFR SVC disabled, LAPF state downBroadcast queue 0/64, broadcasts sent/dropped 37/0, interface broadcasts 37Last input 00:00:01, output 00:00:20, output hang neverLast clearing of "show interface" counters 00:16:16Queueing strategy: dual fifoOutput queue: high size/max/dropped 0/200/0Output queue 0/100, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec39 packets input, 2995 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort39 packets output, 2975 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=updescribes the significant fields shown in the display.
The following is sample output from the show interfaces serial statistics command for a VoFR application:
Router# show interfaces serial 0/0 statisticsSerial0/0Switching path Pkts In Chars In Pkts Out Chars OutProcessor 5668 447428 5663 446995Route cache 0 0 0 0Total 5668 447428 5663 446995describes the fields shown in the display.
Note that when packets go through the traffic-shaping engine, they are counted as being "processor switched." This means that all data that has a fragmentation header will be counted as being processor switched. The same will apply to voice packets if they have been traffic-shaped.
Related Commands
show interfaces
show traffic-shape queue
To display information about the elements queued at a particular time at the VC (DLCI) level, enter the show traffic-shape queue command from privileged EXEC mode.
show traffic-shape queue [interface [dlci]]
Syntax Description
interface
The interface containing the DLCI(s) for which you wish to display information about queued elements.
dlci
The specific DLCI for which you wish to display information about queued elements.
Command Mode
EXEC or Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
The dlci option was added in Cisco IOS Release 12.0(3)XG.
When no parameters are specified with this command, the output displays information for all interfaces and DLCIs containing queued elements. When a specific interface and DLCI are specified, information is displayed about the queued elements for that DLCI only.
Examples
The following is sample output for the show traffic-shape queue command when weighted fair queuing is configured on the map-class associated with DLCI 16:
router# show traffic-shape queue Serial1/1 dlci 16Traffic queued in shaping queue on Serial1.1 dlci 16Queuing strategy: weighted fairQueuing Stats: 1/600/64/0 (size/max total/threshold/drops)Conversations 0/16 (active/max total)Reserved Conversations 0/2 (active/allocated)(depth/weight/discards) 1/4096/0Conversation 5, linktype: ip, length: 608source: 172.21.59.21, destination: 255.255.255.255, id: 0x0006, ttl: 255,TOS: 0 prot: 17, source port 68, destination port 67The following is sample output for the show traffic-shape queue command when priority queuing is configured on the map-class associated with DLCI 16:
router# show traffic-shape queue Serial1/1 dlci 16Traffic queued in shaping queue on Serial1.1 dlci 16Queuing strategy: priority-group 4Queuing Stats: low/1/80/0 (queue/size/max total/drops)Packet 1, linktype: cdp, length: 334, flags: 0x10000008The following is sample output for the show traffic-shape queue command when first-come-first-serve queuing is configured on the map-class associated with DLCI 16:
router# show traffic-shape queue Serial1/1 dlci 16Traffic queued in shaping queue on Serial1.1 dlci 16Queuing strategy: fcfsQueuing Stats: 1/60/0 (size/max total/drops)Packet 1, linktype: cdp, length: 334, flags: 0x10000008describes the fields shown in these displays.
Table 20 Show Traffic-Shape Queue Field Descriptions
Related Commands
show frame-relay fragment
show frame-relay pvc
show frame-relay vofrshow voice permanent-call
To display information about the permanent calls on a voice interface, enter the show voice permanent-call command from privileged EXEC mode.
show voice permanent-call [voice-port] [summary]
Syntax Description
Command Mode
EXEC or Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is only available on the Cisco MC3810 platform.
When no parameters are specified with this command, the output displays information for all ports containing permanent calls. When a specific interface is specified, information is displayed about the permanent calls for that interface only.
Examples
The following is sample output for the show voice permanent-call command:
router# show voice permanent-call 1/11/1 state=connect coding=G729A payload size=30 vad=offec=8 (ms), cng=off fax=on digit_relay=on Seq num = off, VOFR Serial0,dlci = 550,cid = 6TX INFO :slow-mode seq#= 25, sig pkt cnt= 19646, last-ABCD=1101hardware-state ACTIVE signal type is CEPT/MELCASvoice-gate CLOSED,network-path OPEN MASTER1101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 1101RX INFO :slow-mode, sig pkt cnt= 19648, under-run = 0, over-run = 0missing = 0, out of seq = 0, very late = 0playout depth = 0 (ms), refill count = 1prev-seq#= 25, last-ABCD=1101, slave standby timeout 25000 (ms)max inter-arrival time 0 (ms), current timer 384 (ms)max timeout timer 5016 (ms), restart timeout is 0 (ms)signaling packet fast-mode inter-arrival times (ms)16 24 16 24 16 24 16 24 16 24 16 24 16 24 16 2416 24 16 24 16 24 16 24 0 0 0 0 0 0 0 0signaling playout history1101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 1101The following is sample output for the show voice permanent-call summary command:
router# show voice permanent-call summary1/1 state= connect, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 880,cid = 61/2 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1021/3 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1031/4 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1041/5 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1051/6 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1061/7 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1071/8 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1081/9 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1091/10 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1101/11 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1111/12 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1121/13 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1131/14 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1141/15 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1151/17 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1171/18 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1181/19 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1191/20 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1201/21 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1211/22 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1221/23 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1231/24 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1241/25 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 125describes the fields shown in these displays.
Table 21 Show Voice Permanent-Call Field Descriptions
Related Commands
show frame-relay fragment
show frame-relay pvc
show frame-relay vofrsignal keepalive
To configure the keepalive signaling packet interval for Cisco trunks and FRF.11 trunks, use the signal keepalive voice-class configuration command. Use the no form of this command to restore the default value.
signal keepalive number
no signal keepalive numberSyntax Description
number
Specifies the keepalive signaling packet interval in seconds. The valid range is from 1 to 65535 seconds.
Default
5 seconds
Command Mode
Voice-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810. Before configuring the keepalive signaling interval, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
Examples
The following example, beginning in global configuration mode, sets the keepalive signaling interval to 3 seconds for voice class "10."
router(config)#voice class permanent 10router(config-class)# signal keepalive 3router(config-class)# exitrouter(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# voice-class permanent 10Related Commands
dial-peer voice
signal pattern
signal timing idle suppress-voice
signal timing oos
voice class permanent
voice-class permanentsignal pattern
To configure the ABCD bit pattern for Cisco trunks and FRF.11 trunks, use the signal pattern voice-class configuration command. Use the no form of this command to remove the signal pattern setting from the voice class.
signal pattern {idle receive | idle transmit | oos receive | oos transmit} WORD
no signal pattern {idle receive | idle transmit | oos receive | oos transmit} WORDSyntax Description
Default
No signal pattern is defined.
Command Mode
Voice-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810. Before configuring the signaling pattern, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
This command must be entered twice. When you enter the command to specify the signaling pattern for the idle transmit state, you must reenter the command to specify the signaling pattern for the idle receive state.
The idle state of a call is normally based on both the transmit and receive idle patterns matching the signaling state in the signaling packets. If only one direction is configured (transmit or receive), the idle state will be detected based only on the direction that is configured. The out-of-service transmit pattern is matched against the signaling state from the PBX (and transmitted to the network). This is used in conjunction with either the suppress-voice timing parameter or the suppress-all parameter.
The out-of-service receive pattern is the pattern sent to the PBX if the signal timing oos timeout timer expires during which no signaling packets are received from the network. The out-of-service (OOS) receive pattern is not used for pattern matching against the signaling packets received from the network. The receive packets directly indicate an OOS condition by setting the AIS alarm indication bit in the packet.
To "busy out" a PBX if the network connection fails, set the OOS receive pattern to match the seized state (busy), then set the signal timing oos timeout value. When the timeout value expires and no signaling packets have been received, the router will send the OOS receive pattern to the PBX.
Use the busy seized pattern only if the PBX does not have a special pattern specifically intended to indicate an OOS state. If the PBX does have a specific OOS pattern, use that pattern instead.
Examples
The following example, beginning in global configuration mode, configures the signaling bit pattern for the idle receive and transmit states:
router(config)#voice class permanent 10 router(config-class)# signal keepalive 3 router(config-class)# signal pattern idle receive 0101 router(config-class)# signal pattern idle transmit 0101 router(config-class)# exitrouter(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# voice-class permanent 10The following example, beginning in global configuration mode, configures the signaling bit pattern for the out-of-service receive and transmit states:
router(config)#voice class permanent 10 router(config-class)# signal keepalive 3 router(config-class)# signal pattern oos receive 0001 router(config-class)# signal pattern oos transmit 0001router(config-class)# exitrouter(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# voice-class permanent 10Related Commands
dial-peer voice
signal keepalive
signal timing idle suppress-voice
signal timing oos
signal-type
voice class permanent
voice-class permanentsignal timing idle suppress-voice
To configure the signal timing parameter for the idle state of the call, use the signal timing idle suppress-voice voice-class configuration command. Use the no form of this command to restore the default value.
signal timing idle suppress-voice seconds
no signal timing idle suppress-voice secondsSyntax Description
seconds
Specifies the duration of the idle state in seconds before the voice traffic is shut down. The valid range is from 0 to 65535 seconds.
Default
No signal timing idle suppress-voice timer is configured.
Command Mode
Voice-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810. Before configuring the signal timing idle suppress-voice timer, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
This command is used when the signal-type parameter is set to transparent in the dial peer for the Cisco trunk or FRF.11 trunk connection. The Cisco MC3810 stops sending voice packets when the timer expires. Signaling packets are still sent.
Examples
The following example, beginning in global configuration mode, configures the signal timing idle suppress-voice timer for the idle state on voice class "10."
router(config)#voice-class permanent 10router(config-class)# signal keepalive 3 router(config-class)# signal pattern idle receive 0101 router(config-class)# signal pattern idle transmit 0101 router(config-class)# signal timing idle suppress-voice 5router(config-class)# exitrouter(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# voice-class permanent 10router(config-dial-peer)# signal-type transparentRelated Commands
dial-peer voice
signal keepalive
signal pattern
signal timing oos
signal-type
voice class permanent
voice-class permanentsignal timing oos
To configure the signal timing parameter for the out-of-service (OOS) state of the call, use the signal timing oos voice-class configuration command. Use the no form of this command to restore the default value.
signal timing oos {restart | slave-standby | suppress-all | suppress-voice | timeout} seconds
no signal timing oos {restart | slave-standby | suppress-all | suppress-voice | timeout} secondsSyntax Description
Default
No signal timing OOS pattern parameters are configured.
Command Mode
Voice-class configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810. Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
You can enter several values for this command. However, the suppress-all and suppress-voice options are mutually exclusive.
Examples
The following example, beginning in global configuration mode, configures the signal timeout parameter for the out-of-service state on voice class "10."
router(config)#voice-class permanent 10router(config-class)# signal-keepalive 3 router(config-class)# signal pattern oos receive 0001 router(config-class)# signal pattern oos transmit 0001 router(config-class)# signal timing oos timeout 60router(config-class)# exitrouter(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# voice-class permanent 10Related Commands
dial-peer voice
signal keepalive
signal pattern
signal timing idle suppress-voice
signal-type
voice class permanent
voice-class permanentsignal-type
To set the signaling type to be used when connecting to a dial peer, use the signal-type command from dial-peer configuration mode. To return to the default signal-type, use the no form of this command.
For the Cisco 2600 series and 3600 series routers:
signal-type {cas | ext-signal}
no signal-typeFor the Cisco MC3810:
signal-type {cas | cept | ext-signal | transparent}
no signal-typeSyntax Description
Default
cas
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is not supported on Cisco 7200 series routers.
This command applies to VoFR, VoATM, and VoHDLC dial peers. It is used with permanent connections only (Cisco trunks and FRF.11 trunks), not with switched calls.
This command is used to inform the local telephony interface of the type of signaling it should expect to receive from the far-end dial peer. To turn signaling off at this dial peer, select the ext-signal option. If signaling is turned off and there are no external signaling channels, a "hot" line exists, enabling this dial peer to connect to anything at the far end.
On the Cisco 2600 series and 3600 series routers, there are only two possible settings for trunks (VoFR dial peers only):
•
•
When you connect an FXS to another FXS, or if you have anything other than an FXS/FXO or E&M/E&M pair, the appropriate signaling type on Cisco 2600 series and 3600 series routers is ext-signal (disabled).
On the Cisco MC3810, there are two additional signal-type settings:
•
•
If you have a digital E1 connection at the remote end that is running cept/MELCAS signaling and you then trunk that across to an analog port, you should make sure that you configure both ends for the cept signal-type.
If you have a T1 or E1 connection at both ends and the T1/E1 is running a signaling protocol that is neither EIA-464 or cept/MELCAS, you may want to configure the signal-type for the transparent option in order to pass through the signaling.
Examples
The following example shows how to disable signaling on a Cisco 2600 series or 3600 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)# signal-type ext-signalrouter(config-dial-peer)#Related Commands
codec (dial-peer)
connection
destination-pattern
dtmf-relay
preference
session protocol
session target
sequence-numbersvad (dial peer)
To enable voice activity detection (VAD) for the calls using this dial peer, use the vad dial-peer configuration command. Use the no form of this command to disable VAD.
vad
no vadSyntax Description
This command has no arguments or keywords.
Default
Enabled
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
This command was first supported on voice dial peers on the Cisco MC3810 in Cisco IOS Release 12.0(3)XG.
This command applies to Voice over IP on the Cisco 3600 series and to Voice over Frame Relay on the Cisco 2600 series, 3600 series, and the Cisco MC3810.
Use the vad command to enable voice activity detection. With VAD, silence is not transmitted over the network, only audible speech. If you enable VAD, the sound quality is slightly degraded, but the connection monopolizes much less bandwidth. If you use the no form of this command, VAD is disabled and voice data is continuously transmitted to the IP backbone.
On the Cisco MC3810, VAD can also be assigned to the voice port using the vad voice-port configuration command. On the Cisco MC3810, if you enable VAD on the dial peer for Voice over Frame Relay switched calls or permanent calls, the dial peer setting overrides the VAD setting on the voice port.
Note
Examples
The following example enables VAD for a VoIP dial peer, starting from global configuration mode:
router(config)#dial-peer voice 200 voiprouter(config-dial-peer)# vadrouter(config-dial-peer)#Related Commands
comfort-noise
dial-peer voicevofr
To enable Voice over Frame Relay (VoFR) on a specific DLCI and to configure specific subchannels on that DLCI, use the vofr command from Frame Relay DLCI configuration mode. Use the no form of the command to disable VoFR on a specific DLCI.
vofr [[cisco] | [[data cid ] [call-control [cid]]]]
no vofr [[cisco] | [[data cid ] [call-control [cid]]]]Syntax Description
Default
Disabled
Command Mode
Frame Relay DLCI
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
For switched-vofr calls, use vofr cisco or vofr call-control on the Cisco 2600 series, 3600 series, and 7200 series routers. Switched-vofr calls cannot be made using vofr by itself, or vofr data cid.
When the vofr command is used without the cisco option, all subchannels on the DLCI are configured for FRF.11 encapsulation. If the vofr command is entered without any keywords or arguments, the data subchannel will be CID 4 and there will be no call-control subchannel.
describes special conditions and restrictions for the use of the vofr command on the Cisco MC3810.
Note
If the "data" option is selected, a numeric value must be entered to complete the command. If the "call-control" option is selected, you need not enter a numeric value if you wish to accept the default call-control subchannel. See the examples below for clarification.
When the vofr command is used on a Cisco MC3810 without the "cisco" option, switched calls are not permitted. Only permanent FRF.11-trunk calls can be made.
Note
Examples
The following example shows how to enable VoFR on Serial 1/1, DLCI 100 on a Cisco 2600 series, 3600 series, or 7200 series router or on an MC3810 concentrator, starting from global configuration mode:
router(config)#interface serial 1/1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# vofrrouter(config-fr-dlci)#The above example configures CID 4 for data; no call-control CID is defined.
To configure CID 4 for data, CID 5 for call-control (both defaults), enter the following command:
router(config-fr-dlci)# vofr call-controlrouter(config-fr-dlci)#To configure CID10 for data, CID 15 for call-control, enter the following command:
router(config-fr-dlci)# vofr data 10 call-control 15router(config-fr-dlci)#To configure CID 4 for data, CID 15 for call-control, enter the following command:
router(config-fr-dlci)# vofr call-control 15router(config-fr-dlci)#To configure CID 10 for data, CID 5 for call-control, enter the following command:
router(config-fr-dlci)# vofr data 10 call-controlrouter(config-fr-dlci)#To configure CID 10 for data with no call-control, enter the following command:
router(config-fr-dlci)# vofr data 10router(config-fr-dlci)#To configure a Cisco router or MC3810 for a VoFR application with an older release of the MC3810 (prior to Release 12.0(3)XG), enter the following command:
router(config-fr-dlci)# vofr ciscorouter(config-fr-dlci)#Related Commands
frame-relay interface-dlci
classvoice class permanent
To create a voice class for a Cisco trunk or FRF.11 trunk, use the voice class permanent global configuration command. Use the no form of this command to delete the voice class.
voice class permanent tag
no voice class permanent tagSyntax Description
tag
Specifies the unique tag number you assign to the permanent voice class. The valid range for this tag is 1 to 10000. The tag number must be unique on the router.
Default
No voice class is configured.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810. It can be used for VoFR, VoATM, and VoHDLC trunks.
Note
Examples
The following example shows how to create a permanent voice class starting from global configuration mode:
router(config)#voice class permanent 10router(config-class)#Related Commands
signal keepalive
signal pattern
signal timing idle suppress-voice
signal timing oos
voice-class permanentvoice-class permanent
To assign a previously-configured voice class for a Cisco trunk or FRF.11 trunk to a dial peer, use the voice-class permanent dial-peer configuration command. Use the no form of this command to remove the voice-class assignment from the dial peer.
voice-class permanent tag
no voice-class permanent tagSyntax Description
Default
This command has no default.
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810.
Note
Examples
The following example shows how to configure a permanent voice class starting from global configuration mode, configure parameters for that voice class, and then assign the voice class to a dial peer:
router(config)#voice class permanent 10router(config-class)# signal keepalive 3router(config-class)#exitrouter(config)# dial-peer voice 100 vofrrouter(config-dial-peer)# voice-class permanent 10Related Commands
signal keepalive
signal pattern
signal timing idle suppress-voice
signal timing oos
signal-type
voice class permanentDebug Commands
This section provides information on new and modified VoFR debug commands for the Cisco 2600 series, 3600 series, and 7200 series router platforms, and the Cisco MC3810 multiservice access concentrator.
All other debug commands used with Voice over Frame Relay are documented in the Cisco IOS Release 12.0 command references.
The following new and modified commands are described in this section:
•
debug ccfrf11 session
To display the ccfrf11 function calls during call setup and teardown, use the debug ccfrf11 session command from privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug ccfrf11 session
no debug ccfrf11 sessionSyntax Description
This command has no keywords or arguments.
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command does not apply to the Cisco MC3810.
This command can be used to display debug information about the various FRF.11 VoFR SPI functions as they are called. Note that this debug command does not display any information regarding the proprietary Cisco switched-VoFR SPI.
This debug is only useful when the session protocol is "frf11-trunk."
Examples
The following example shows sample output from the debug ccfr11 session command:
router# debug ccfrf11 sessionINCOMING CALL SETUP (port setup for answer-mode):*Mar 6 18:04:07.693:ccfrf11_process_timers:scb (0x60EB6040) timer (0x60EB6098) expired*Mar 6 18:04:07.693:Setting accept_incoming to TRUE*Mar 6 18:04:11.213:ccfrf11_incoming_request:peer tag 800:callingNumber=+2602100,calledNumber=+3622110*Mar 6 18:04:11.213:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)*Mar 6 18:04:11.213:ccfrf11_evhandle_incoming_call_setup_request:calling +2602100,called +3622110 Incoming Tag 800*Mar 6 18:04:11.217:ccfrf11_caps_ind:PeerTag = 800*Mar 6 18:04:11.217: codec(preferred) = 4, fax_rate = 2, vad = 2*Mar 6 18:04:11.217: cid = 30, config_bitmask = 0, codec_bytes = 20, signal_type=2*Mar 6 18:04:11.217: required_bandwidth 8192*Mar 6 18:04:11.217:ccfrf11_caps_ind:Bandwidth reservation of 8192 bytes succeeded.*Mar 6 18:04:11.221:ccfrf11_evhandle_call_connect:EnteredCALL SETUP (MASTER):5d22h:ccfrf11_call_setup_request:Entered5d22h:ccfrf11_evhandle_call_setup_request:Entered5d22h:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)5d22h:ccfrf11_evhandle_call_setup_request:preffered_codec set(9)(24)5d22h:ccfrf11_call_setup_trunk:subchannel linking successful5d22h:ccfrf11_caps_ind:PeerTag = 8105d22h: codec(preferred) = 512, fax_rate = 2, vad = 25d22h: cid = 30, config_bitmask = 1, codec_bytes = 24, signal_type=25d22h: required_bandwidth 65005d22h:ccfrf11_caps_ind:Bandwidth reservation of 6500 bytes succeeded.CALL TEARDOWN:*Mar 6 18:09:14.805:ccfrf11_call_disconnect:peer tag 0*Mar 6 18:09:14.805:ccfrf11_evhandle_call_disconnect:Entered*Mar 6 18:09:14.805:ccfrf11_call_cleanup:freeccb 1, call_disconnected 1*Mar 6 18:09:14.805:ccfrf11_call_cleanup:Setting accept_incoming to FALSE and startingincoming timer*Mar 6 18:09:14.809:timer 2:(0x60EB6098)starts - delay (70000)*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Alive timer stopped*Mar 6 18:09:14.809:timer 1:(0x60F64104) stops*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Generating Call record*Mar 6 18:09:14.809:cause=10 tcause=10 cause_text="normal call clearing."*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Releasing 8192 bytes of reserved bandwidth*Mar 6 18:09:14.809:ccfrf11_call_cleanup:ccb 0x60F6404C, vdbPtr 0x610DB7A4freeccb_flag=1, call_disconnected_flag=1Related Commands
debug ccswvoice vofr-debug
debug ccswvoice vofr-session
debug frame-relay fragment
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframedebug ccswvoice vofr-debug
To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-debug command from privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug ccswvoice vofr-debug
no debug ccswvoice vofr-debugSyntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command does not apply to the Cisco MC3810.
This command should be used when attempting to troubleshoot a VoFR call which uses the "cisco-switched" session protocol. It provides the same information as the debug ccswvoice vofr-session command, but includes additional debugging information relating to the calls.
Examples
The following example shows sample output from the debug ccswvoice vofr-debug command:
CALL TEARDOWN:3640_vofr(config-voiceport)#*Mar 1 03:02:08.719:ccswvofr_bridge_drop:dropping bridge calls src 17 dst 16 dlci 100cid 9 state ACTIVE*Mar 1 03:02:08.727:ccswvofr:callID 17 dlci 100 cid 9 state ACTIVE event O/G REL*Mar 1 03:02:08.735:ccswvofr:callID 17 dlci 100 cid 9 state RELEASE event I/C RELCOMP*Mar 1 03:02:08.735:ccswvofr_store_call_history_entry:cause=22 tcause=22cause_text=no circuit.3640_vofr(config-voiceport)#CALL SETUP (outgoing):*Mar 1 03:03:22.651:ccswvofr:callID 23 dlci -1 cid -1 state NULL event O/G SETUP*Mar 1 03:03:22.651:ccswvofr_out_callinit_setup:callID 23 using dlci 100 cid 10*Mar 1 03:03:22.659:ccswvofr:callID 23 dlci 100 cid 10 state O/G INIT event I/C PROC*Mar 1 03:03:22.667:ccswvofr:callID 23 dlci 100 cid 10 state O/G PROC event I/C CONNccfrf11_caps_ind:codec(preferred) = 0Related Commands
debug ccfrf11 session
debug ccswvoice vofr-session
debug frame-relay fragment
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframedebug ccswvoice vofr-session
To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-session command from privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug ccswvoice vofr-session
no debug ccswvoice vofr-sessionSyntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command does not apply to the Cisco MC3810.
This command can be used to show the state transitions of the cisco-switched-vofr state machine as a call is processed. It should be used when attempting to troubleshoot a VoFR call which uses the "cisco-switched" session protocol.
Examples
The following example shows sample output from the debug ccswvoice vofr-session command:
CALL TEARDOWN:3640_vofr(config-voiceport)#*Mar 1 02:58:13.203:ccswvofr:callID 14 dlci 100 cid 8 state ACTIVE event O/G REL*Mar 1 02:58:13.215:ccswvofr:callID 14 dlci 100 cid 8 state RELEASE event I/C RELCOMP3640_vofr(config-voiceport)#CALL SETUP (outgoing):*Mar 1 02:59:46.551:ccswvofr:callID 17 dlci -1 cid -1 state NULL event O/G SETUP*Mar 1 02:59:46.559:ccswvofr:callID 17 dlci 100 cid 9 state O/G INIT event I/C PROC*Mar 1 02:59:46.567:ccswvofr:callID 17 dlci 100 cid 9 state O/G PROC event I/C CONN3640_vofr(config-voiceport)#Related Commands
debug ccfrf11 session
debug ccswvoice vofr-debug
debug frame-relay fragment
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframedebug frame-relay fragment
To display information related to Frame Relay fragmentation on a PVC, use the debug frame-relay fragment command in privileged EXEC mode. Use the no form of the command to turn off the debug function.
debug frame-relay fragment [event | interface type number dlci]
no debug frame-relay fragment [event | interface type number dlci]Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command will display event or error messages related to Frame Relay fragmentation; it is only enabled at the PVC level on the selected interface.
This command is not supported on the Cisco MC3810 for fragments received by a PVC configured via the voice-encap command.
Examples
The following example shows sample output from the debug frame-relay fragment command:
router#debug frame-relay fragment interface serial 0/0 109This may severely impact network performance.You are advised to enable 'no logging console debug'. Continue?[confirm]Frame Relay fragment/packet debugging is onDisplaying fragments/packets on interface Serial0/0 dlci 109 onlySerial0/0(i): dlci 109, rx-seq-num 126, exp_seq-num 126, BE bits set, frag_hdr 04 C0 7ESerial0/0(o): dlci 109, tx-seq-num 82, BE bits set, frag_hdr 04 C0 52The following example shows sample output from the debug frame-relay fragment event command:
router#debug frame-relay fragment eventThis may severely impact network performance.You are advised to enable 'no logging console debug'. Continue?[confirm]Frame Relay fragment event/errors debugging is onFrame-relay reassembled packet is greater than MTU size, packet dropped on serial 0/0dlci 109Unexpected B bit frame rx on serial0/0 dlci 109, dropping pending segmentsRx an out-of-sequence packet on serial 0/0 dlci 109, seq_num_received 17seq_num_expected 19Related Commands
debug ccfrf11 session
debug ccswvoice vofr-debug
debug ccswvoice vofr-session
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframedebug voice vofr
To show Cisco trunk and FRF.11 trunk call setup attempts and to show which dial peer is used in the call setup, use the debug voice vofr command from privileged EXEC mode. Use the no form of the command to turn off the debug function.
debug voice vofr
no debug voice vofrSyntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command applies to Cisco trunks and FRF.11 trunks only; it does not apply to switched calls.
This command applies to VoFR, VoATM, and VoHDLC dial peers on the Cisco MC3810.
Examples
The following example shows sample output from the debug voice vofr command for a Cisco trunk:
router# debug voice vofr1d05h: 1/1:VOFR, unconf ==> pending_start1d05h: 1/1:VOFR,create VOFR1d05h: 1/1:VOFR,search dial-peer 7100 preference 01d05h: 1/1:VOFR, pending_start ==> start1d05h: 1/1:VOFR,1d05h:voice_configure_perm_svc:1d05h:dial-peer 7100 codec = G729A payload size = 30 vad = off dtmf relay = onseq num = off1d05h:voice-port 1/1 codec = G729A payload size = 30 vad = off dtmf relay = onseq num = off1d05h: 1/1:VOFR,SIGNAL-TYPE = cept1d05h:init_frf11 tcid 0 master 0 signaltype 21d05h:Going Out Of Service on tcid 0 with sig state 00011d05h: 1/1:VOFR, start get event idle1d05h: 1/1:VOFR, start get event1d05h: 1/1:VOFR, start get event set up1d05h: 1/1:VOFR, start ==> pending_connect1d05h: 1/1:VOFR, pending_connect get event connect1d05h: 1/1:VOFR, pending_connect ==> connect1d05h: 1/1:VOFR,SIGNAL-TYPE = cept1d05h:init_frf11 tcid 0 master 1 signaltype 21d05h:start_vofr_polling on port 0 signaltype 2The following example shows sample output from the debug voice vofr command for an FRF.11 trunk:
1d05h: 1/1:VOFR,search dial-peer 7200 preference 21d05h: 1/1:VOFR,SIGNAL-TYPE = cept1d05h:Launch Voice Trunk:signal-type 21d05h:calculated bandwidth = 10, coding = 6, size = 301d05h:%Voice-port 1/1 is down.1d05h: 1/1:VOFR, pending_start get event idle1d05h:Codec Type = 6 Payload Size = 30 Seq# off1d05h:%Voice-port 1/1 is up.1d05h:init_frf11 tcid 0 master 1 signaltype 21d05h:status OK :cid = 1001d05h: 1/1:VOFR,1d05h:start FRF111d05h: 1/1:VOFR, pending_start ==> frf111d05h: 1/1:VOFR,SIGNAL-TYPE = ceptRelated Commands
debug ccfrf11 session
debug ccswvoice vofr-debug
debug ccswvoice vofr-session
debug frame-relay fragment
debug vpm port
debug vtsp port
debug vtsp vofr subframedebug vpm port
To observe the behavior of the Holst state machine, use the debug vpm port command from EXEC or privileged EXEC mode. Use the no form of the command to turn off the debug function.
debug vpm port slot-number/subunit-number/port
no debug vpm slot-number/subunit-number/portSyntax Description
Command Mode
EXEC or Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1).
This command is not supported on Cisco 7200 series routers or on the Cisco MC3810.
Use this command to limit the debug output to a particular port. The debug output can be quite voluminous for a single channel. A 12-port box might create problems. Use this debug with any or all of the other debug modes.
Execution of no debug vpm all will turn off all port level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This will help to avoid confusion about which ports you are actually debugging.
Examples
The following example shows sample output from the debug vpm port 1/1/0 command during trunk establishment after the no shutdown command has been executed on the voice port:
router# debug vpm port 1/1/0*Mar 1 03:21:39.799: htsp_process_event: [1/1/0, 0.1 , 2]act_down_inserve*Mar 1 03:21:39.807: htsp_process_event: [1/1/0, 0.0 , 14]act_go_trunkhtsp_trunk_createhtsp_trunk_sig_linkfxols_trunk*Mar 1 03:21:39.807: htsp_process_event: [1/1/0, 1.0 , 1]trunk_offhookfxols_trunk_down*Mar 1 03:21:39.807: dsp_sig_encap_config: [1/1/0] packet_len=28 channel_id=128packet_id=42 transport_protocol=1 playout_delay=100 signaling_mode=0t_ssrc=http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xg/120xg3/12xgvofr/0 r_ssrc=http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xg/120xg3/12xgvofr/0 t_vpxcc=0 r_vpxcc=0*Mar 1 03:21:39.811: dsp_set_sig_state: [1/1/0] packet_len=12channel_id=128 packet_id=39 state=0xC timestamp=0x0*Mar 1 03:21:39.811: trunk_offhook: Trunk Retry Timer Enabled*Mar 1 03:22:13.095: htsp_process_event: [1/1/0, 1.1, 39]act_trunk_setuphtsp_setup_ind*Mar 1 03:22:13.095: htsp_process_event: [1/1/0, 1.2 , 8]*Mar 1 03:22:13.099: hdsprm_vtsp_codec_loaded_ok: G726 firmware needs download*Mar 1 03:22:13.103: dsp_download: p=0x60E73844 size=34182 (t=1213310):39 FA 6D*Mar 1 03:22:13.103: htsp_process_event: [1/1/0, 1.2 , 6]act_trunk_proc_connect*Mar 1 03:22:13.191: dsp_receive_packet: MSG_TX_RESTART_INDICATION: code=0 t=1213319*Mar 1 03:22:13.191: dsp_download: p=0x60EA8924 size=6224 (t=1213319): 8 55 AE*Mar 1 03:22:13.207: dsp_receive_packet: MSG_TX_RESTART_INDICATION: code=0 t=1213320*Mar 1 03:22:13.207: htsp_process_event: [1/1/0, 1.3 , 11] trunk_upfxols_trunk_up*Mar 1 03:22:13.207: dsp_set_sig_state: [1/1/0] packet_len=12channel_id=128 packet_id=39 state=0x4 timestamp=0x0*Mar 1 03:22:13.207: dsp_sig_encap_config: [1/1/0] packet_len=28 channel_id=128packet_id=42 transport_protocol=3 playout_delay=100 headerbytes = 0xA0Note in the above display that "transport_protocol = 3" indicates Voice over Frame Relay. Also note that the second line of the display indicates that a shutdown/no shutdown command sequence was executed on the voice port.
Related Commands
debug vpm all
debug vpm dsp
debug vpm signal
debug vpm spidebug vtsp port
To observe the behavior of the VTSP state machine, use the debug vtsp port command from EXEC or privileged EXEC mode. Use the no form of the command to turn off the debug function.
debug vtsp port slot-number/subunit-number/port
no debug vtsp port slot-number/subunit-number/portSyntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is not supported on Cisco 7200 series routers or on the Cisco MC3810.
Use this command to limit the debug output to a particular port. The debug output can be quite voluminous for a single channel. A 12-port box might create problems. Use this debug with any or all of the other debug modes.
Execution of no debug vtsp all will turn off all VTSP-level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This will help to avoid confusion about which ports you are actually debugging.
Examples
The following example shows sample output from the debug vtsp port 1/1/0 command:
router# debug vtsp port 1/1/0*Mar 1 03:17:33.691: vtsp_tsp_call_setup_ind (sdb=0x613FD514, tdm_info=0x0,tsp_info=0x613FD438, calling_number= called_number= redirect_number=): peer_tag=1110*Mar 1 03:17:33.691: vtsp_do_call_setup_ind*Mar 1 03:17:33.691: dsp_close_voice_channel: [] packet_len=8 channel_id=1packet_id=75*Mar 1 03:17:33.691: dsp_open_voice_channel: [] packet_len=12channel_id=1 packet_id=74 alaw_ulaw_select=0 transport_protocol=2*Mar 1 03:17:33.695: dsp_set_playout_delay: [] packet_len=18channel_id=1 packet_id=76 mode=1 initial=60 min=4 max=200 fax_nom=300*Mar 1 03:17:33.695: dsp_echo_canceller_control: [] packet_len=10 channel_id=1packet_id=66 flags=0x0*Mar 1 03:17:33.695: dsp_set_gains: [] packet_len=12 channel_id=1 packet_id=91in_gain=0 out_gain=65506*Mar 1 03:17:33.695: dsp_vad_enable: [] packet_len=10 channel_id=1 packet_id=78thresh=-38*Mar 1 03:17:33.695: vtsp_process_event(): [, 0.S_SETUP_INDICATED, E_CC_PROCEEDING]*Mar 1 03:17:33.699: vtsp_process_event(): [, 0.S_SETUP_INDICATED,E_CC_BRIDGE]act_bridge*Mar 1 03:17:33.699: vtsp_ring_noan_timer_start: 1185370*Mar 1 03:17:33.699: vtsp_process_event(): [, 0.S_SETUP_INDICATED,E_CC_CAPS_IND]act_caps_ind*Mar 1 03:17:33.699: act_caps_ind: Encap 2, Vad 2, Codec 0x1000, CodecBytes 60,FaxRate 2, FaxBytes 30,Sub-channel 10, Bitmask 0x0 SignalType 2*Mar 1 03:17:33.703: vtsp_process_event(): [, 0.S_SETUP_INDICATED,E_CC_CAPS_ACK]act_caps_ack*Mar 1 03:17:33.703: dsp_idle_mode: [] packet_len=8 channel_id=1 packet_id=68*Mar 1 03:17:33.703: vtsp_process_event(): [, 0.S_SETUP_INDICATED,E_CC_CONNECT]act_connect*Mar 1 03:17:33.703: vtsp_ring_noan_timer_stop: 1185370*Mar 1 03:17:33.911: vtsp_process_event(): [, 0.S_CONNECT, E_DSPRM_PEND_SUCCESS]act_pend_codec_success*Mar 1 03:17:33.911: dsp_close_voice_channel: [] packet_len=8 channel_id=1packet_id=75*Mar 1 03:17:33.911: dsp_open_voice_channel: [] packet_len=12 channel_id=1packet_id=74 alaw_ulaw_select=0 transport_protocol=2*Mar 1 03:17:33.911: dsp_set_playout_delay: [] packet_len=18 channel_id=1 packet_id=76mode=1 initial=60 min=4 max=200 fax_nom=300*Mar 1 03:17:33.911: dsp_echo_canceller_control: [] packet_len=10 channel_id=1packet_id=66 flags=0x0*Mar 1 03:17:33.911: dsp_set_gains: [] packet_len=12 channel_id=1 packet_id=91in_gain=0 out_gain=65506*Mar 1 03:17:33.911: dsp_vad_enable: [] packet_len=10 channel_id=1 packet_id=78thresh=-38*Mar 1 03:17:33.911: dsp_encap_config: [] packet_len=24 channel_id=1 packet_id=92 TransportProtocol 3 SID_support=0 sequence_number=0 rotate_flag=0 header_bytes 0xA0*Mar 1 03:17:33.915: dsp_voice_mode: [] packet_len=22 channel_id=1 packet_id=73coding_type=14 voice_field_size=60 VAD_flag=1 echo_length=128comfort_noise=1 fax_detect=1 digit_relay=0Related Commands
debug vtsp all
debug vtsp vofr subframedebug vtsp vofr subframe
To display the first 10 bytes (including header) of selected VoFR subframes for the interface, use the debug vtsp vofr subframe command from privileged EXEC mode. Use the no form of the command to turn off the debug function.
debug vtsp vofr subframe payload [from-dsp] [to-dsp]
no debug vtsp vofr subframeSyntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is not supported on Cisco 7200 series routers or on the Cisco MC3810.
Each debug output displays the first 10 bytes of the FRF.11 subframe, including header bytes. The from-dsp and to-dsp options can be used to limit the debugs to a single direction. If not specified, debugs are displayed for subframes when they are received from the DSP and before they are sent to the DSP.
Use extreme caution in selecting payload options 0 and 6. These options may cause network instability.
Examples
The following example shows sample output from the debug vtsp vofr subframe command:
router# debug vtsp vofr subframe 2vtsp VoFR subframe debugging is enabled for payload 2 to and from DSP 3620_vofr#*Mar 6 18:21:17.413:VoFR frame received from Network (24 bytes):9E 02 19 AA AA AA AAAA AA AA*Mar 6 18:21:17.449:VoFR frame received from DSP (18 bytes):9E 02 19 AA AA AA AA AA AAAA*Mar 6 18:21:23.969:VoFR frame received from Network (24 bytes):9E 02 19 AA AA AA AAAA AA AA*Mar 6 18:21:24.005:VoFR frame received from DSP (18 bytes):9E 02 19 AA AA AA AA AA AAAARelated Commands
debug vtsp all
debug vtsp port
