|
|
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.
The following new and modified commands are described in this section (modified commands are marked by an asterisk):
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
string | A string of digits including wildcards that specifies the telephone number of the voice-port dial peer. |
Disabled
Dial-peer configuration
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.
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 pots router (config-dial-peer)# destination pattern 5552150router(config-dial-peer)#exitrouter(config)#dial-peer voice 200 vofr router (config-dial-peer)# session protocol frf11-trunk router(config-dial-peer)# called-number 5552150 router(config-dial-peer)# destination pattern 5558000 router(config-dial-peer)#
codec (dial-peer)
connection
destination-pattern
dtmf-relay
fax-rate
session protocol
session target
signal-type
preference
For the Cisco 2600 series and 3600 series routers:
codec {g711alaw | g711ulaw | g723ar53 | g723ar63 | g723r53 | g723r63 | g726r16 | g726r24 |For the Cisco MC3810:
codec {g711alaw | g711ulaw | g726r32 | g729ar8 | g729r8} [bytes payload_size]
g711alaw | G.711 A-Law at 64000 bits per second (bps). |
g711ulaw | G.711 u-Law at 64000 bps. |
g723ar53 | G.723.1 ANNEX A at 5300 bps |
g723ar63 | G.723.1 ANNEX A at 6300 bps |
g723r53 | G.723.1 at 5300 bps |
g723r63 | G.723.1 at 6300 bps |
g726r16 | G.726 at 16000 bps |
g726r24 | G.726 at 24000 bps |
g726r32 | G.726 at 32000 bps |
g728 | G.728 at 16000 bps |
g729br8 | G.729 ANNEX B at 8000 bps |
g729r8 | G.729 at 8000 bps. This is the default CODEC. |
bytes | (Optional) Used to specify the number of bytes in the voice payload of each frame. |
payload_size | The number of bytes in the voice payload of each frame. Enter a ? character after the keyword bytes to get a list of valid payload values for your specific dial peer. |
g711alaw | G.711 A-Law at 64000 bits per second (bps). |
g711ulaw | G.711 u-Law at 64000 bps. |
g726r32 | G.726 at 32000 bps |
g729ar8 | G.729 ANNEX A at 8000 bps |
g729r8 | G.729 at 8000 bps. This is the default CODEC. |
bytes | (Optional) Used to specify the number of bytes in the voice payload of each frame. |
payload_size | The number of bytes in the voice payload of each frame. Enter a ? character after the keyword bytes to get a list of valid payload values for your specific dial peer. |
g729r8, 30-byte payload for VoFR, VoATM, and VoHDLC
g729r8, 20-byte payload for VoIP
Dial-peer configuration
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.
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.
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 vofr
router(config-dial-peer)# codec g711alaw bytes 120
router(config-dial-peer)#
called-number
connection
destination-pattern
dtmf-relay
fax-rate
preference
session protocol
session target
signal-type
vad (dial peer)
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]}
plar | Specifies a private line auto ring down (PLAR) connection. PLAR is handled by associating a peer directly with an interface; when an interface goes off-hook, the peer is used to set up the second call leg and conference them together without the caller having to dial any digits. |
tie-line | (This keyword is supported only on the Cisco MC3810.) Specifies a tie-line connection to a private branch exchange (PBX). |
plar-opx | (This keyword is supported only on the Cisco MC3810.) Specifies a PLAR Off-Premises eXtension connection. Using this option, the local voice port provides a local response before the remote voice port receives an answer. On FXO interfaces, the voice port will not answer until the remote side answers. |
string | Specifies the destination telephone number. Valid entries are any series of digits that specify the E.164 telephone number. |
trunk | Specifies a straight tie-line connection to a private branch exchange (PBX). |
string | Specifies the destination telephone number. Valid entries are any series of digits that specify the E.164 telephone number. |
answer-mode | (Optional; used only with the trunk keyword.) Specifies that the router should not attempt to initiate a trunk connection, but should wait for an incoming call before establishing the trunk. |
No connection mode is specified.
Voice-port configuration
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.
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.
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)#
session-protocol
voice-port
locale | Keyword specifying an analog voice interface-related default tone, ring, and cadence setting for a specified country. Valid entries for the Cisco MC3810 prior to release 12.0(3)XG are: argentina, australia, austria, belgium, brazil, china, colombia, czechrepublic, denmark, finland, france, germany, greece, hongkong, iceland, israel, italy, japan, korea, luxembourg, malaysia, netherlands, newzealand, northamerica, norway, peru, philippines, poland, portugal, russia, singapore, slovakia, southafrica, spain, sweden, switzerland, taiwan, thailand, turkey, unitedkingdom, and venezuela. The Cisco 2600 series, 3600 series and the Cisco MC3810 comply with the ISO 3166 country name standards, which use a two-letter code to represent a country. Valid entries are listed in Table 7. |
| Cptone Command Entry | Country |
|---|---|
ar | Argentina |
au | Australia |
at | Austria |
be | Belgium |
br | Brazil |
ca | Canada |
cn | China |
co | Colombia |
cz | Czech Republic |
dk | Denmark |
fi | Finland |
fr | France |
de | Germany |
gr | Greece |
hk | Hong Kong |
hu | Hungary |
is | Iceland |
in | India |
id | Indonesia |
ie | Ireland |
il | Israel |
it | Italy |
jp | Japan |
kr | Korea Republic |
lu | Luxembourg |
my | Malaysia |
mx | Mexico |
nl | Netherlands |
nz | New Zealand |
no | Norway |
pe | Peru |
ph | Philippines |
pl | Poland |
pt | Portugal |
ru | Russian Federation |
sg | Singapore |
sk | Slovakia |
si | Slovenia |
za | South Africa |
es | Spain |
se | Sweden |
ch | Switzerland |
tw | Taiwan |
th | Thailand |
tr | Turkey |
gb | Great Britain |
us | Unites States |
ve | Venezuela |
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 higher
Voice-port configuration
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.
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 us
The 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 sg
voice-port
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}For the Cisco 2600 series, 3600 series, and 7200 series:
tag | Digit(s) defining a particular dial peer. For a range of valid tag numbers, enter a ? character after the dial-peer voice command. |
pots | Specifies that this is a POTS dial peer. Not supported on the Cisco 7200 series. |
vofr | Specifies that this is a Voice over Frame Relay dial peer using FRF.11 encapsulation on the Frame Relay backbone network. |
voip | Specifies that this is a VoIP dial peer. Not supported on the Cisco 7200 series. |
For the Cisco MC3810:
tag | Digit(s) defining a particular dial peer. For a range of valid tag numbers, enter a ? character after the dial-peer voice command. |
pots | Specifies that this is a POTS peer using basic telephone service. |
voatm | Specifies that this is a Voice over ATM dial peer using the real-time AAL5 voice encapsulation on the ATM backbone network. |
vofr | Specifies that this is a Voice over Frame Relay dial peer using encapsulation on the Frame Relay backbone network. |
vohdlc | Specifies that this is a Voice over HDLC dial peer using Cisco serial encapsulation (HDLC) for voice. |
Global configuration
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.
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 pots
router(config-dial-peer)#
codec (dial-peer)
destination-pattern
dtmf-relay
preference
sequence-numbers
session protocol
session target
voice-port
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-relayThis command has no arguments or keywords.
Disabled
Dial-peer configuration
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.
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 vofr
router(config-dial-peer)# dtmf-relay
router(config-dial-peer)#
called-number
codec (dial-peer)
connection
cptone
destination-pattern
session protocol
session target
signal-type
preference
2400 | Specifies a fax transmission speed of 2400 bits per second (bps). |
4800 | Specifies a fax transmission speed of 4800 bps. |
7200 | Specifies a fax transmission speed of 7200 bps. |
9600 | Specifies a fax transmission speed of 9600 bps. |
14400 | Specifies a fax transmission speed of 14,400 bps. |
disable | Disables fax relay transmission capability. |
voice | Specifies the highest possible transmission speed allowed by the voice rate. |
voice
Dial-peer configuration
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.
The following example configures a transmission speed of 9600 bps for faxes sent to a dial peer:
router(config)# dial-peer voice 100 vofr
router(config-dial-peer)# fax-rate 9600
router(config-dial-peer)#
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-queuingThis command has no arguments or keywords.
Enabled
Interface configuration
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.
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.
The following example configures a Frame Relay DLCI carrying voice traffic to also support fancy queuing:
router(config)# interface serial 0
router(config-if)# no frag-pre-queuing
router(config-if)# frame-relay interface-dlci 100 voice-encap 320
router(config-fr-dlci)#
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_
Congestive_Discard_Threshold | (Optional) Used to specify the number of messages allowed in each queue. The range is from 1 to 4096 messages; the default is 64. |
Number_Dynamic_Conversation_ | (Optional) Used to specify the number of dynamic queues to be used for best-effort conversations---normal conversations not requiring any special network services. Valid values are 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096; the default is 16. |
Number_Reservable_Conversation_Queues | (Optional) Used to specify the number of reserved queues to be used for carrying voice traffic. The range is from 0 to 100; the default is 2. (The CLI will not allow a value less than 2 if fragmentation is configured on the frame relay map-class.) |
Max_Buffer_Size_for_Fair_Queues | (Optional) Used to specify the maximum buffer size in bytes for all of the fair queues. The range is from 0 to 4096 bytes; the default is 600. |
Disabled
Map-class configuration
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.
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/1 router(config-if)# frame-relay interface-dlci 100 router(config-fr-dlci)# class vofr router(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofr router(config-map-class)# frame-relay fair-queue router(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/1 router(config-if)# frame-relay interface-dlci 100 router(config-fr-dlci)# class vofr router(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofr router(config-map-class)# frame-relay fair-queue 255 router(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/1 router(config-if)# frame-relay interface-dlci 100 router(config-fr-dlci)# class vofr router(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofr router(config-map-class)# frame-relay fair-queue 64 256 25 router(config-map-class)#
class
frame-relay fragment
frame-relay interface-dlci
map-class frame-relay
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
fragment_size | Specifies the number of payload bytes from the original Frame Relay frame that will go into each fragment. This number excludes the Frame Relay header of the original frame. All the fragments of a Frame Relay frame except the last will have a payload size equal to fragment_size; the last fragment will have a payload less than or equal to fragment_size. Valid values are from 16 to 1600 bytes; the default is 53. |
Disabled
Map-class configuration
This command first appeared in Cisco IOS Release 12.0(3)XG.
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.
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 40 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/0 router(config-if)# frame-relay traffic-shaping router(config-if)# frame-relay interface-dlci 100 router(config-fr-dlci)# class frag router(config-fr-dlci)# exitrouter(config)#map-class frame-relay frag router(config-map-class)# frame-relay cir 128000 router(config-map-class)# frame-relay bc 1000 router(config-map-class)# frame-relay fragment 40 router(config-map-class)# frame-relay fair-queue router(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 40 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/1 router(config-if)# frame-relay traffic-shaping router(config-if)# frame-relay interface-dlci 101 router(config-fr-dlci)# vofr router(config-fr-dlci)# class frag router(config-fr-dlci)# exitrouter(config)#map-class frame-relay frag router(config-map-class)# frame-relay cir 128000 router(config-map-class)# frame-relay bc 1000 router(config-map-class)# frame-relay fragment 40 router(config-map-class)# frame-relay fair-queue router(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 40 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/0 router(config-if)# frame-relay traffic-shaping router(config-if)# frame-relay interface-dlci 102 router(config-fr-dlci)# vofr cisco router(config-fr-dlci)# class frag router(config-fr-dlci)# exitrouter(config)#map-class frame-relay frag router(config-map-class)# frame-relay cir 128000 router(config-map-class)# frame-relay bc 1000 router(config-map-class)# frame-relay fragment 40 router(config-map-class)# frame-relay fair-queue router(config-map-class)#
class
frame-relay fair-queue
frame-relay interface-dlci
frame-relay traffic-shaping
map-class frame-relay
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]
dlci | DLCI number to be used on the specified subinterface. |
ietf | cisco | (Optional) Encapsulation type: Internet Engineering Task Force (IETF) Frame Relay encapsulation or Cisco Frame Relay encapsulation. |
voice-encap size | (Optional; supported on the Cisco MC3810 only.) Specifies that data fragmentation will be used to support Voice over Frame Relay. The voice encapsulation size denotes the data fragmentation size. The valid range is from 80 to 1600 bytes. For a list of recommended data fragmentation sizes and an important note regarding the voice-encap option, see the "Usage Guidelines" section. |
voice-cir cir | (Optional; supported on the Cisco MC3810 only.) Specifies the upper limit on the voice bandwidth that may be reserved for this DLCI. The default is the CIR configured for the Frame Relay map class. For more information, see the "Usage Guidelines" section. |
No DLCI is assigned.
Interface configuration
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. Table 8 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.
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.
| Port Access Rate | Recommended Data Fragmentation Size1 |
|---|---|
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 |
| 1The 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. |
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.
The following example assigns DLCI 100 to a serial interface, starting from global configuration mode:
router(config)# interface serial 1/1
router(config-if)# frame-relay interface-dlci 100
router(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 serial0
router(config-if)# frame-relay interface-dlci 100 voice-encap 80
router(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 serial0
router(config-if)# frame-relay interface-dlci 100 voice-encap 80 voice-cir 24000
router(config-fr-dlci)#
frag-pre-queuing
frame-relay class
vofr
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
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. |
Disabled (zero)
Map-class configuration
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.
The bandwidth required for a voice call depends on the bandwidth of the CODEC, the voice packetization overhead, and the voice frame payload size. The smaller the voice frame payload size, the higher the bandwidth required for the call. To make the calculation, use the following formula:
required_bandwidth = codec_bandwidth x (1 + overhead / payload_size)
As an example, the overhead for VoFR voice packet is between 6 and 8 bytes: a 2-byte Frame Relay header, a 1- or 2-byte FRF.11 header (depending on the CID value), a 2-byte CRC, and a 1-byte trailing flag. If voice sequence numbers are enabled in the voice packets, there is an additional 1-byte sequence number. Table 9 shows the required voice bandwidth for the G.729 8000 bps speech coder for various payload sizes.
| CODEC | CODEC Bandwidth | Voice Frame Payload Size | Required Bandwidth per Call (6 byte OH) | Required Bandwidth per Call (8 byte OH) |
|---|---|---|---|---|
G.729 | 8000 bps | 120 bytes | 8400 bps | 8534 bps |
G.729 | 8000 bps | 80 bytes | 8600 bps | 8800 bps |
G.729 | 8000 bps | 40 bytes | 9200 bps | 9600 bps |
G.729 | 8000 bps | 30 bytes | 9600 bps | 10134 bps |
G.729 | 8000 bps | 20 bytes | 10400 bps | 11200 bps |
To configure the payload size for the voice frames, use the codec command from dial-peer configuration mode.
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/1 router(config-if)# frame-relay interface-dlci 100 router(config-fr-dlci)# class vofr router(config-fr-dlci)# exitrouter(config)#map-class frame-relay vofr router(config-map-class)# frame-relay voice bandwidth 64000 router(config-map-class)#
class
codec (dial-peer)
frame-relay fair-queue
frame-relay fragment
frame-relay interface-dlci
map-class frame-relay
value | An integer value from 0 to 10, where the lower the number, the higher the preference. The default value is 0 (highest preference). |
0 (highest preference)
Dial-peer configuration
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.
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 pots router (config-dial-peer)# destination pattern 5552150 router(config-dial-peer)# preference 1 router(config-dial-peer)# exitrouter(config)#dial-peer voice 20 pots router (config-dial-peer)# destination pattern 5552150 router(config-dial-peer)# preference 2 router(config-dial-peer)# exitrouter(config)#dial-peer voice 30 vofr router (config-dial-peer)# destination pattern 5552150 router(config-dial-peer)# preference 3 router(config-dial-peer)# exit router(config)#
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
session protocol
session target
signal-type
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-numbersThis command has no arguments or keywords.
Disabled
Dial-peer configuration
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.
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 vofr
router(config-dial-peer)# no sequence-numbers
router(config-dial-peer)#
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
session protocol
session target
signal-type
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. |
cisco-switched
Dial-peer configuration
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.
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 vofr
router(config-dial-peer)# session protocol frf11-trunk
router(config-dial-peer)# called-number 5552150
router(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 vofr
router(config-dial-peer)# session protocol frf11-trunk
router(config-dial-peer)#
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
preference
session target
signal-type
For Cisco 2600 series and 3600 series VoFR dial peers:
session target interface dlci [cid]For Cisco 7200 series VoFR dial peers:
session target interface dlciFor Cisco MC3810 VoFR dial peers:
session target interface dlci [cid]For Cisco 2600 series and 3600 series VoIP dial peers:
session target {ipv4:destination-address | dns:[$s$. | $d$. | $e$. | $u$.] host-name |For Cisco MC3810 Voice over ATM dial peers:
session target interface pvc {name | vpi/vci | vci}For Cisco MC3810 Voice over HDLC dial peers:
session target interfaceFor Cisco 2600 series and 3600 series VoFR dial peers:
interface | Specifies the serial interface and interface number (slot number/port number) associated with this dial peer. |
dlci | Specifies the data link connection identifier for this dial peer. The valid range is from 16 to 1007. |
cid | Specifies the DLCI subchannel to be used for data on FRF.11 calls. A CID must be specified only when the session protocol is "frf11-trunk." When the session protocol is "cisco-switched," the CID is dynamically allocated. The valid range is from 4 to 255. Note By default, CID 4 is used for data; CID 5 is used for call-control. It is recommended that you select CID values between 6 and 63 for voice traffic. If the CID is greater than 63, the FRF.11 header will contain an extra byte of data. |
For Cisco 7200 series VoFR dial peers:
interface | Specifies the interface type and interface number on the Cisco 7200 series router. For the range of valid interface numbers for the selected interface type, enter a ? character after the interface type. |
dlci | Specifies the Frame Relay DLCI. The valid range is from 16 to 1007. |
For Cisco MC3810 VoFR dial peers:
interface | Specifies the interface type and interface number on the Cisco MC3810. For the range of valid interface numbers for the selected interface type, enter a ? character after the interface type. |
dlci | Specifies the Frame Relay DLCI. The valid range is from 16 to 1007. |
cid | Specifies a subchannel ID for the Frame Relay DLCI. The valid range is from 4 to 255. |
For Cisco 3600 series VoIP dial peers:
ipv4:destination-address | The IP address of the dial peer. |
dns:host-name | Indicates that the domain name server will be used to resolve the name of the IP address. Valid entries for this parameter are characters representing the name of the host device. (Optional) You can use one of the following three wildcards with this keyword when defining the session target for VoIP peers: · $s$.---Indicates that the source destination pattern will be used as part of the domain name. · $d$.---Indicates that the destination number will be used as part of the domain name. · $e$.---Indicates that the digits in the called number will be reversed, periods will be added between each digit of the called number, and this string will be used as part of the domain name. · $u$.---Indicates that the unmatched portion of the destination pattern (such as a defined extension number) will be used as part of the domain name. |
loopback:rtp | Indicates that all voice data will be looped back to the originating source. This is applicable for VoIP peers. |
loopback:compressed | Indicates that all voice data will be looped back in compressed mode to the originating source. This is applicable for POTS peers. |
loopback:uncompressed | Indicates that all voice data will be looped back in uncompressed mode to the originating source. This is applicable for POTS peers. |
For Cisco MC3810 Voice over ATM dial peers:
interface | Specifies the interface type and interface number on the Cisco MC3810. The only valid number is 0. |
pvc | Indicates the specific ATM permanent virtual circuit for this dial peer. |
name | The PVC name. |
vpi/vci | The ATM network virtual path identifier (VPI) and virtual channel identifier (VCI) of this PVC. |
vci | The ATM network virtual channel identifier (VCI) of this PVC. |
For Cisco MC3810 Voice over HDLC dial peers:
interface | Specifies the interface type and interface number associated with this dial peer. |
The default for this command is enabled with no IP address or domain name defined.
Dial-peer configuration
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.
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 vofr
router(config-dial-peer)# destination-pattern 13102221111
router (config-dial-peer)# called-number 5552150
router(config-dial-peer)# session protocol frf11-trunk
router (config-dial-peer)# session target serial 1/0 100 20
router(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 vofr
router(config-dial-peer)# destination-pattern 13102221111
router (config-dial-peer)# session target serial 1/1 200
router(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 vofr
router(config-dial-peer)# destination-pattern 13102221111
router (config-dial-peer)# session target Serial1 200
router(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 voip
voip (config-dial-peer)# session target dns:voice_router.cisco.com
voip(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 voip
voip (config-dial-peer)# destination-pattern 1310222....
voip (config-dial-peer)# session target dns:$u$.cisco.com
voip (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 voip
voip (config-dial-peer)# destination-pattern 13102221111
voip (config-dial-peer)# session target dns:$d$.cisco.com
voip (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 voip
voip (config-dial-peer)# destination-pattern 12345
voip (config-dial-peer)# session target dns:$e$.cisco.com
The 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 voatm
voatm(config-dial-peer)# destination-pattern 13102221111
voatm (config-dial-peer)# session target atm0 pvc 20
voatm(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 vohdlc
vohdlc(config-dial-peer)# destination-pattern 13102221111
vohdlc (config-dial-peer)# session target Serial0
vohdlc(config-dial-peer)#
called-number
codec (dial-peer)
cptone
destination-pattern
dtmf-relay
session protocol
signal-type
preference
brief | Displays a shortened version of the complete active call table. |
EXEC or privileged EXEC
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.
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.
The following is sample output from the show call active voice command for a VoFR call:
3640_vofr#show call active voice GENERIC: SetupTime=25594 ms Index=1 PeerAddress=+2602110 PeerSubAddress= PeerId=800 PeerIfIndex=17 LogicalIfIndex=0 ConnectTime=25596 CallState=4 CallOrigin=2 ChargedUnits=0 InfoType=2 TransmitPackets=105992 TransmitBytes=2436775 ReceivePackets=105993 ReceiveBytes=2224812 VOFR: ConnectionId=[0x23539D01 0x99840003 0x0 0x18FAB] Subchannel=[Interface Serial1/0, DLCI 100, CID 10] SessionProtocol=cisco-switched SessionTarget=Serial1/0 100 CalledNumber= VADEnable=ENABLED CoderTypeRate=g729r8 CodecBytes=20 SignalingType=cas DTMFRelay=ENABLED UseVoiceSequenceNumbers=ENABLED GENERIC: SetupTime=25595 ms Index=1 PeerAddress=+3642200 PeerSubAddress= PeerId=100 PeerIfIndex=12 LogicalIfIndex=0 ConnectTime=25595 CallState=4 CallOrigin=1 ChargedUnits=0 InfoType=2 TransmitPackets=106177 TransmitBytes=2015629 ReceivePackets=106176 ReceiveBytes=2228655 TELE: ConnectionId=[0x23539D01 0x99840003 0x0 0x18FAB] TxDuration=2116590 ms VoiceTxDuration=2116590 ms FaxTxDuration=0 ms CoderTypeRate=g729r8 NoiseLevel=0 ACOMLevel=20 OutSignalLevel=-79 InSignalLevel=-79 InfoActivity=2 ERLLevel=20 SessionTarget=
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=
Table 10 provides an alphabetical listing of the fields in this output and a description of each field.
| Field | Description |
|---|---|
ACOM Level | Current ACOM level for the call. This value is the sum of the Echo Return Loss, Echo Return Loss Enhancement, and nonlinear processing loss for the call. |
CallOrigin | Indicates whether this router originated or answered the current call. |
CallState | Current state of the call. |
ChargedUnits | Total number of charging units applying to this peer since system startup. |
CodecBytes | Number of bytes in the voice payload of each voice frame in a VoFR call. |
CoderTypeRate | Negotiated voice coder transmit rate of speech for this dial peer. |
ConnectionId | Global call identifier of a gateway call. When the session protocol is "frf11-trunk," the ConnectionId is not consistent end-to-end since FRF.11 does not communicate end-to-end; the ConnectionId is consistent between the POTS and VoFR call legs within the router. |
CalledNumber | The called-number (if present) that is configured on the VoFR dial peer. |
ConnectTime | Value of the System UpTime when the call associated with this entry was completed. |
Dial-Peer | Tag number of the dial peer transmitting this call. |
DTMFRelay | Indicates whether DTMF relay is enabled or disabled for this dial peer. |
ERLLevel | Current Echo Return Loss (ERL) level for this call. |
FaxTxDuration | Duration in milliseconds of fax transmission from this peer to voice gateway for this call. You can derive the Fax Utilization Rate by dividing the FaxTxDuration value by the TxDuration value. |
GapFillWithSilence | Duration of voice signal replaced with silence because voice data was lost or not received on time for this call. |
GapFillWithPrediction | Duration of voice signal played out with the signal synthesized from parameters or samples of data preceding in time because voice data was lost or not received in time from the voice gateway for this call. An example of such pullout is frame-eraser or frame-concealment strategies in G.729 and G.723.1 compression algorithms. |
GapFillWithInterpolation | Duration of voice signal played out with the signal synthesized from parameters or samples of data preceding and following in time because voice data was lost or not received on time from the voice gateway for this call. |
GapFillWithRedundancy | Duration of voice signal played out with signal synthesized from redundancy parameters available because voice data was lost or not received on time from voice gateway for this call. |
HiWaterPlayoutDelay | High water mark Voice Playout FIFO Delay during this call. |
Index | Dial peer identification number. |
InfoActivity | Active information transfer activity state for this call. |
InfoType | Information type for this call. |
InSignalLevel | Active input signal level (in dB) from the telephony interface used by this call. |
LogicalIfIndex | Index number of the logical interface for this call. |
LoWaterPlayoutDelay | Low water mark Voice Playout FIFO Delay during the call. |
NoiseLevel | Active noise level for the call. |
OnTimeRvPlayout | Duration of voice playout from data received on time for this call. You can derive the Total Voice Playout Duration for Active Voice by adding the OnTimeRvPlayout value to the GapFill values. |
OutSignalLevel | Active output signal level (in dB) to telephony interface used by this call. |
PeerAddress | Destination pattern associated with this peer. |
PeerId | ID value of the peer table entry to which this call was made. |
PeerIfIndex | Voice port index number for this peer. |
PeerSubaddress | Subaddress to which this call is connected. |
ReceiveBytes | Number of bytes received by the peer during this call. |
ReceiveDelay | Average Playout FIFO Delay plus the decoder delay during the voice call. |
ReceivePackets | Number of packets received by this peer during this call. |
RemoteIPAddress | Remote system IP address for the VoIP call. |
RemoteUDPPort | Remote system UDP listener port to which voice packets are transmitted. |
RoundTripDelay | Voice packet round trip delay between the local and remote system on the IP backbone during the call. |
SelectedQoS | Selected RSVP quality of service (QoS) for the call. |
SessionProtocol | Session protocol used for the call between the local and remote router via the packet network. |
SessionTarget | Session target of the peer used for the call. |
SetupTime | Value of the System UpTime when the call associated with this entry was started. |
SignalingType | Indicates the type of call-control signaling used for this call. |
Subchannel | The interface, DLCI and CID of the subchannel used for data on a VoFR call. |
TransmitBytes | Number of bytes transmitted from this peer during the call. |
TransmitPackets | Number of packets transmitted from this peer during the call. |
TxDuration | Duration in milliseconds of transmit path open from this peer to the voice gateway for the call. |
UseVoiceSequenceNumbers | Indicates whether or not voice sequence numbers were enabled for this call. |
VADEnable | Indicates whether or not voice activation detection (VAD) was enabled for this call. |
VoiceTxDuration | Duration in milliseconds of voice transmission from this peer to the voice gateway for this call. You can derive the Voice Utilization Rate by dividing the VoiceTxDuration value by the TxDuration value. |
show call history voice
show dial-peer voice
show frame-relay pvc
show frame-relay vofr
show voice-port
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 recordFor the Cisco 2600 series, 3600 series, and 7200 series routers:
last number | Displays the last calls connected, where the number of calls displayed is defined by the argument number. A valid entry for the argument number is any number from 1 to 2147483647. |
brief | Displays a shortened version of the complete call history table. |
For the Cisco MC3810, this command has no arguments or keywords.
EXEC or privileged EXEC
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.
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 1
GENERIC:
SetupTime=8283963 ms
Index=3149
PeerAddress=3623110
PeerSubAddress=
PeerId=3400
PeerIfIndex=18
LogicalIfIndex=0
DisconnectCause=3F
DisconnectText=service or option not available, unspecified
ConnectTime=8283963
DisconectTime=8285463
CallOrigin=1
ChargedUnits=0
InfoType=2
TransmitPackets=94
TransmitBytes=2751
ReceivePackets=0
ReceiveBytes=0
VOFR:
ConnectionId=[0x3D4B232D 0x6A900627 0x0 0x4F00852]
Subchannel=[Interface Serial0/0, DLCI 160, CID 10]
SessionProtocol=frf11-trunk
SessionTarget=Serial0/0 160 10
CalledNumber=2603100
VADEnable=ENABLED
CoderTypeRate=g729r8
CodecBytes=30
SignalingType=cas
DTMFRelay=DISABLED
UseVoiceSequenceNumbers=DISABLED
GENERIC:
SetupTime=8283963 ms
Index=3150
PeerAddress=2601100
PeerSubAddress=
PeerId=1100
PeerIfIndex=7
LogicalIfIndex=0
DisconnectCause=3F
DisconnectText=service or option not available, unspecified
ConnectTime=8283964
DisconectTime=8285464
CallOrigin=2
ChargedUnits=0
InfoType=2
TransmitPackets=0
TransmitBytes=-121
ReceivePackets=94
ReceiveBytes=2563
TELE:
ConnectionId=[0x3D4B232D 0x6A900627 0x0 0x4F00852]
TxDuration=15000 ms
VoiceTxDuration=2010 ms
FaxTxDuration=0 ms
CoderTypeRate=g729r8
NoiseLevel=-68
ACOMLevel=20
SessionTarget=
The following is sample output from the show call history voice command for a VoIP call:
router#show call history voice GENERIC: SetupTime=20405 Index=0 PeerAddress= PeerSubAddress= PeerId=0
PeerIfIndex=0 LogicalIfIndex=0 DisconnectCause=NORMAL DisconnectText= ConnectTime=0
DisconectTime=20595 CallOrigin=2 ChargedUnits=0 InfoType=0 TransmitPackets=0
TransmitBytes=0 ReceivePackets=0 ReceiveBytes=0
VOIP: ConnectionId[0x19BDF910 0xAF500006 0x0 0x56590] RemoteIPAddress=17635075
RemoteUDPPort=16392 RoundTripDelay=0 SelectedQoS=0 SessionProtocol=1
SessionTarget= OnTimeRvPlayout=0 GapFillWithSilence=0 GapFillWithPrediction=0
GapFillWithInterpolation=0 GapFillWithRedundancy=0 HiWaterPlayoutDelay=0
LoWaterPlayoutDelay=0 ReceiveDelay=0 VADEnable=0 CoderTypeRate=0
TELE: ConnectionId=[0x19BDF910 0xAF500006 0x0 0x56590] TxDuration=3030
VoiceTxDuration=2700 FaxTxDuration=0 CoderTypeRate=0 NoiseLevel=0 ACOMLevel=0 SessionTarget=
Table 11 provides an alphabetical listing of the fields in this output and a description of each field.
| Field | Description |
|---|---|
ACOMLevel | Average ACOM level for this call. This value is the sum of the Echo Return Loss, Echo Return Loss Enhancement, and nonlinear processing loss for the call. |
CallOrigin | Call origin; answer versus originate. |
ChargedUnits | Total number of charging units applying to this peer since system startup. |
CoderTypeRate | Negotiated voice coder transmit rate of speech for this call. |
ConnectionID | Global call identifier for the gateway call. |
ConnectTime | The value of System UpTime when the call was connected. |
DisconnectCause | Description explaining why the call was disconnected. |
DisconnectText | Descriptive text explaining the disconnect reason. |
DisconnectTime | The value of System UpTime when the call was disconnected. |
FaxTxDuration | Duration in milliseconds of fax transmitted from this peer to the voice gateway for this call. You can derive the Fax Utilization Rate by dividing this value by the TxDuration value. |
GapFillWithSilence | Duration of voice signal replaced with silence because the voice data was lost or not received on time for this call. |
GapFillWithPrediction | Duration of voice signal played out with the signal synthesized from parameters or samples of data preceding in time because the voice data was lost or not received on time from the voice gateway for this call. |
GapFillWithInterpolation | Duration of voice signal played out with the signal synthesized from parameters or samples of data preceding and following in time because the voice data was lost or not received on time from the voice gateway for this call. |
GapFillWithRedundancy | Duration of voice signal played out with signal synthesized from redundancy parameters available because the voice data was lost or not received on time from the voice gateway for this call. |
HiWaterPlayoutDelay | High water mark Voice Playout FIFO Delay during the voice call. |
Index | Dial peer identification number. |
InfoType | Information type for this call. |
LogicalIfIndex | Index of the logical voice port for this call. |
LoWaterPlayoutDelay | Low water mark Voice Playout FIFO Delay during the voice call. |
NoiseLevel | Average noise level for this call. |
OnTimeRvPlayout | Duration of voice playout from data received on time for this call. You can derive the Total Voice Playout Duration for Active Voice by adding the OnTimeRvPlayout value to the GapFill values. |
PeerAddress | Destination pattern or number to which this call is connected. |
PeerId | ID value of the peer entry table to which this call was made. |
PeerIfIndex | Index number of the logical interface through which this call was made. For ISDN media, this would be the index number of the B channel used for the call. |
PeerSubAddress | Subaddress to which this call is connected. |
ReceiveBytes | Number of bytes received by the peer during this call. |
ReceiveDelay | Average Playout FIFO Delay plus the decoder delay during the voice call. |
ReceivePackets | Number of packets received by this peer during the call. |
RemoteIPAddress | Remote system IP address for the call. |
RemoteUDPPort | Remote system UDP listener port to which voice packets for this call are transmitted. |
RoundTripDelay | Voice packet round trip delay between the local and remote system on the IP backbone for this call. |
SelectedQoS | Selected RSVP quality of service for the call. |
SessionProtocol | Session protocol used for the call between the local and remote router via the packet network. |
SessionTarget | Session target of the peer used for the call. |
SetUpTime | Value of the System UpTime when the call associated with this entry was started. |
TransmitBytes | Number of bytes transmitted by this peer during the call. |
TransmitPackets | Number of packets transmitted by this peer during the call. |
TxDuration | Duration of the transmit path open from this peer to the voice gateway for the call. |
VADEnable | Indicates whether or not voice activation detection (VAD) was enabled for this call. |
VoiceTxDuration | Duration in milliseconds of voice transmitted from this peer to voice gateway for this call. You can derive the Voice Utilization Rate by dividing the VoiceTxDuration by the TxDuration value. |
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 record
ConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]
Media=TELE, TxDuration= 1418 ms
CallingNumber=2001
SetupTime=1157801 x 10ms
ConnectTime=1158046 x 10ms
DisconectTime=1158188 x 10ms
DisconnectText=local onhook
ConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]
Media=TELE, TxDuration= 1422 ms
CalledNumber=2002
SetupTime=1157802 x 10ms
ConnectTime=1158046 x 10ms
DisconectTime=1158188 x 10ms
DisconnectText=remote onhook
Table 12 explains the fields in the sample output.
| Field | Description |
|---|---|
ConnectionID | Global call identifier for this voice call. |
Media | Media over which the call is made. If the call is over the (telephone) access side, the entry will be TELE. If the call is over the voice network side, the entry will be either ATM, FR (for Frame Relay), or HDLC. |
LowerIFName | Physical lower interface information. Only displays if the Media is either ATM, FR, or HDLC. |
TxDuration | Length of the call. Only displays if the Media is TELE. |
CalledNumber | Number at the device receiving the call. |
CallingNumber | Number at the device initiating the call. |
SetupTime | Time the call setup started. |
ConnectTime | Time the call was connected. |
DisconnectTime | Time the call was disconnected. |
DisconnectText | Descriptive text explaining the reason for disconnect. |
show call active voice
show dial-peer voice
show frame-relay pvc
show frame-relay vofr
show voice-port
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]For the Cisco 2600 series, 3600 series, and 7200 series routers:
tag | (Optional) A specific dial peer. This option displays configuration information and call data for the dial peer identified by the argument tag. Enter a ? character after the command to get a list of valid tag numbers for your application. |
For the Cisco MC3810:
tag | (Optional) A specific dial peer. This option displays configuration information and call data for a single dial peer identified by the argument tag. Enter a ? character after the command to get a list of valid tag numbers for your application. |
summary | (Optional) Displays a summary of all voice dial peers. |
EXEC or privileged EXEC
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:
| Platform | Dial Peers Supported |
|---|---|
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.
The following is sample output from the show dial-peer voice command for a POTS dial peer:
router# show dial-peer voice 1
VoiceEncapPeer100
tag = 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 10
VoiceOverIpPeer500
tag = 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 bytes
codec = 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 700
VoiceOverFRPeer700
tag = 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 bytes
codec = 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.
Table 13 provides an alphabetical listing of the fields in these displays and a description of each field.
| Field | Description |
|---|---|
Accepted Calls | Number of calls from this peer accepted since system startup. |
acc-qos | Lowest acceptable quality of service configured for calls for this peer. |
Admin state | Administrative state of this peer. |
answer-address | Telephone number of the incoming call---associated with the incoming dial peer. |
called number | For FRF.11 trunks, the E.164 telephone number of the POTS dial peer to which this VoFR dial peer is connected. |
Charged Units | Total number of charging units applying to this peer since system startup. |
codec | Default voice coder rate of speech for this peer. |
connections/maximum | The current number of active connections/the total number of connections allowed. |
Connect Time | Accumulated connect time to the peer since system startup for both incoming and outgoing calls. |
destination-pattern | Telephone number for this dial peer. |
direct-inward-dial | Indicates whether direct-inward-dial is enabled or disabled for a POTS dial peer. |
DTMF Relay | Indicates whether DTMF Relay is enabled or disabled for this dial peer. |
Expect factor | User-requested Expectation Factor of voice quality for calls via this peer. |
fax-rate | Fax transmission rate configured for this peer. |
Failed Calls | Number of failed call attempts to this peer since system startup. |
group | Group number associated with this peer. |
Icpif | Configured Calculated Planning Impairment Factor (ICPIF) value for calls sent by a dial peer. |
incoming-called-number | Full E.164 telephone number to be used to identify the POTS dial peer. |
ip precedence | Integer specifying the IP precedence value. Valid values are from 0 to 7. A value of 0 means that no IP precedence (priority) has been set. |
Last Disconnect Cause | Encoded network cause associated with the last call. This value will be updated whenever a call is started or cleared and depends on the interface type and session protocol being used on this interface. |
Last Disconnect Text | ASCII text describing the reason for the last call termination. |
Last Setup Time | Value of the System Up Time when the last call to this peer was started. |
Operation state | Operational state of this peer. |
payload size | Number of bytes in the payload of each voice frame. |
Permission | Configured permission level for this peer. |
Poor QOV Trap | Whether Poor Quality of Voice trap messages have been enabled or disabled. |
prefix | Prefix associated with this POTS dial peer. |
Refused Calls | Number of calls from this peer refused since system startup. |
req-qos | Configured requested quality of service for calls for this dial peer. |
session-target | Session target of this peer. |
session-protocol | Session protocol used for calls between the local and remote router via the packet network. |
signaling-type | Indicates the type of call-control signaling configured on this dial peer. |
Successful Calls | Number of completed calls to this peer. |
tag | Unique dial peer ID number. |
type | The type of dial peer. |
UDP checksum | User Datagram Protocol checksum for voice packets transmitted by the dial peer. |
VAD | Whether or not voice activation detection (VAD) is enabled for this dial peer. |
voice-port | For POTS dial peers, the number of the voice port to which this dial peer is associated. |
Voice Sequence Numbers | Indicates whether voice sequence numbers are enabled or disabled for this dial peer. |
show call active voice
show call history voice
show frame-relay pvc
show frame-relay vofr
show voice-port
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]]
interface | (Optional) Indicates a specific interface for which Frame Relay fragmentation information will be displayed. |
interface | (Optional) Interface number containing the DLCI(s) for which you wish to display fragmentation information. |
dlci | (Optional) Specific DLCI for which you wish to display fragmentation information. |
Privileged EXEC
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.
The following is sample output for the show frame-relay fragment command without any parameters specified:
router#show frame-relay fragment interface dlci frag-type frag-size in-frag out-frag dropped-frag Serial0 108 VoFR-cisco 100 1261 1298 0 Serial0 109 VoFR 100 0 243 0 Serial0 110 end-to-end 100 0 0 0
The 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 16 fragment-size 45 fragment type end-to-end in fragmented pkts 0 out fragmented pkts 0 in fragmented bytes 0 out fragmented bytes 0 in un-fragmented pkts 0 out un-fragmented pkts 0 in un-fragmented bytes 0 out un-fragmented bytes 0 in assembled pkts 0 out pre-fragmented pkts 0 in assembled bytes 0 out pre-fragmented bytes in dropped reassembling pkts 0 out dropped fragmenting pkts 0 in timeouts 0 in out-of-sequence fragments 0 in fragments with unexpected B bit set 0 out interleaved packets 0
Table 14 describes the significant fields in this output.
| Field | Description |
|---|---|
interface | Subinterface containing the DLCI for which the fragmentation information pertains. |
dlci | Data link connection identifier for which the displayed fragmentation information applies. |
frag-type | Type of fragmentation configured on the designated DLCI. Supported types are end-to-end, VoFR, and VoFR-cisco. |
frag-size | Configured fragment size in bytes. |
in-frag | Total number of fragments received by the designated DLCI. |
out-frag | The total number of fragments transmitted by the designated DLCI. |
dropped-frag | Total number of fragments dropped by the designated DLCI. |
in/out fragmented pkts | Total number of frames received/transmitted by this DLCI that have a fragmentation header. |
in/out fragmented bytes | Total number of bytes, including those in the Frame Relay headers, that have been received/transmitted by this DLCI. |
in/out un-fragmented pkts | Number of frames received/transmitted by this DLCI that do not require reassembly, and therefore do not contain the FRF.12 header. These counters can be incremented only when the end-to-end fragmentation type is set. |
in/out un-fragmented bytes | Number of bytes received/transmitted by this DLCI that do not require reassembly, and therefore do not contain the FRF.12 header. These counters can be incremented only when the end-to-end fragmentation type is set. |
in assembled pkts | Total number of fully reassembled frames received by this DLCI, including the frames received without a Frame Relay fragmentation header (in un-fragmented pkts). This counter corresponds to the frames viewed by the upper-layer protocols. |
out pre-fragmented pkts | Total number of fully reassembled frames transmitted by this DLCI, including the frames transmitted without a Frame Relay fragmentation header |
in assembled bytes | Number of bytes in the fully reassembled frames received by this DLCI, including the frames received without a Frame Relay fragmentation header (in un-fragmented bytes). This counter corresponds to the total number of bytes viewed by the upper-layer protocols. |
out pre-fragmented bytes | Number of bytes in the fully reassembled frames transmitted by this DLCI, including the frames transmitted without a Frame Relay fragmentation header (out un-fragmented bytes). This counter corresponds to the total number of bytes viewed by the upper-layer protocols. |
in dropped reassembling pkts | Number of fragments received by this DLCI that are dropped for reasons such as running out of memory, receiving segments out of sequence, receiving an unexpected frame with a B bit set, or timing out on a reassembling frame. |
out dropped fragmenting pkts | Number of fragments that are dropped by this DLCI during transmission because of running out of memory. |
in timeouts | Number of reassembly timeouts that have occurred on incoming frames to this DLCI. (A frame that does not fully reassemble within two minutes is dropped and the timeout counter is incremented.) |
in out-of-sequence fragments | Number of fragments received by this DLCI that have an unexpected sequence number. |
in fragments with unexpected B bit set | Number of fragments received by this DLCI that have an unexpected B bit set. When this occurs, all fragments being reassembled are dropped and a new frame is begun with this fragment. |
out interleaved packets | Number of packets leaving this DLCI that have been interleaved between segments. |
show frame-relay pvc
show frame-relay vofr
show interfaces serial
show traffic-shape queue
interface | (Optional) Indicates a specific interface for which PVC information will be displayed. |
interface | (Optional) Interface number containing the DLCI(s) for which you wish to display PVC information. |
dlci | (Optional) A specific DLCI number used on the interface. Statistics for the specified PVC display when a DLCI is also specified. |
Privileged EXEC
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.
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.
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.
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 0
encapsulation frame-relay
frame-relay traffic-shaping
frame-relay interface-dlci 108
vofr cisco
class vofr-class
map-class frame-relay vofr-class
frame-relay fragment 100
frame-relay fair-queue
frame-relay cir 64000
frame-relay voice bandwith 25000
Router# show frame-relay pvc 108
PVC Statistics for interface Serial0 (Frame Relay DTE)
DLCI = 108, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0
input pkts 1260 output pkts 1271 in bytes 95671
out bytes 98604 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 1271 out bcast bytes 98604
pvc create time 09:43:17, last time pvc status changed 09:43:17
Service type VoFR-cisco
configured voice bandwidth 25000, used voice bandwidth 0
voice reserved queues 24, 25
fragment type VoFR-cisco fragment size 100
cir 64000 bc 64000 be 0 limit 1000 interval 125
mincir 32000 byte increment 1000 BECN response no
pkts 2592 bytes 205140 pkts delayed 1296 bytes delayed 102570
shaping inactive
shaping drops 0
Current fair queue configuration:
Discard Dynamic Reserved
threshold queue count queue count
64 16 2
Output queue size 0/max total 600/drops 0
Note 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 0
encapsulation frame-relay
frame-relay traffic-shaping
frame-relay interface-dlci 110
class frag
map-class frame-relay frag
frame-relay fragment 100
frame-relay fair-queue
frame-relay cir 64000
Router# show frame-relay pvc 110
PVC Statistics for interface Serial0 (Frame Relay DTE)
DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0
input pkts 0 output pkts 243 in bytes 0
out bytes 7290 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 243 out bcast bytes 7290
pvc create time 04:03:17, last time pvc status changed 04:03:18
fragment type end-to-end fragment size 100
cir 64000 bc 64000 be 0 limit 1000 interval 125
mincir 32000 byte increment 1000 BECN response no
pkts 486 bytes 14580 pkts delayed 243 bytes delayed 7290
shaping inactive
shaping drops 0
Current fair queue configuration:
Discard Dynamic Reserved
threshold queue count queue count
64 16 2
Output queue size 0/max total 600/drops 0
Note 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 pvc DLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103 input pkts 10 output pkts 7 in bytes 6222 out bytes 6034 dropped pkts 0 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 outbcast pkts 0 outbcast bytes 0 pvc create time 0:13:11 last time pvc status changed 0:11:46 DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104 input pkts 20 output pkts 8 in bytes 5624 out bytes 5222 dropped pkts 0 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 outbcast pkts 0 outbcast bytes 0 pvc create time 0:03:57 last time pvc status changed 0:03:48
Table 15 provides a listing of the fields in these displays and a description of each field.
| Field | Description |
|---|---|
DLCI | One of the data link connection identifier (DLCI) numbers for the PVC. |
DLCI USAGE | Lists SWITCHED when the router or access server is used as a switch, or LOCAL when the router or access server is used as a DTE. |
PVC STATUS | Status of the PVC: ACTIVE, INACTIVE, or DELETED. |
INTERFACE | Specific subinterface associated with this DLCI. |
input pkts | Number of packets received on this PVC. |
output pkts | Number of packets sent on this PVC. |
in bytes | Number of bytes received on this PVC. |
out bytes | Number of bytes sent on this PVC. |
dropped pkts | Number of incoming and outgoing packets dropped by the router at the Frame Relay level. |
in FECN pkts | Number of packets received with the FECN bit set. |
in BECN pkts | Number of packets received with the BECN bit set. |
out FECN pkts | Number of packets sent with the FECN bit set. |
out BECN pkts | Number of packets sent with the BECN bit set. |
in DE pkts | Number of DE packets received. |
out DE pkts | Number of DE packets sent. |
out bcast pkts | Number of output broadcast packets. |
out bcast bytes | Number of output broadcast bytes. |
pvc create time | Time the PVC was created. |
last time pvc status changed | Time the PVC changed status (active to inactive). |
Service-type | Type of service performed by this PVC. Can be VoFR or VoFR-cisco. |
configured voice bandwidth | Amount of bandwidth in bits per second reserved for voice traffic on this PVC. |
used voice bandwidth | Amount of bandwidth in bits per second currently being used for voice traffic. |
voice reserved queues | Queue numbers reserved for voice traffic on this PVC. |
fragment type | Type of fragmentation configured for this PVC. Possible types are:
|
fragment size | Size of the fragment payload in bytes. |
cir | Current committed information rate (CIR), in bits per second. |
bc | Current committed burst size, in bits. |
be | Current excess burst size, in bits. |
limit | Maximum number of bytes transmitted per internal interval (excess plus sustained). |
interval | Interval being used internally (may be smaller than the interval derived from Bc/CIR; this happens when the router determines that traffic flow will be more stable with a smaller configured interval). |
mincir | Minimum committed information rate (CIR) for the PVC. |
byte increment | Number of bytes that will be sustained per internal interval. |
BECN response | Frame Relay has BECN Adaptation configured. |
pkts | Number of packets associated with this PVC that have gone through the traffic shaping system. |
bytes | Number of bytes associated with this PVC that have gone through the traffic shaping system. |
pkts delayed | Number of packets associated with this PVC that have been delayed by the traffic shaping system. |
bytes delayed | Number of bytes associated with this PVC that have been delayed by the traffic shaping system. |
shaping | Shaping will be active for all PVCs that are fragmenting data; otherwise, shaping will be active if the traffic being sent exceeds the CIR for this circuit. |
shaping drops | Number of packets dropped by the traffic shaping process. |
Discard threshold | Maximum number of packets that can be stored in each packet queue. If additional packets are received after a queue is full, they will be discarded. |
Dynamic queue count | Number of packet queues reserved for best-effort traffic. |
Reserved queue count | Number of packet queues reserved for voice traffic. |
Output queue size | Size in bytes of each output queue. |
max total | Maximum number of packets of all types that can be queued in all queues. |
drops | Number of frames dropped by all output queues. |
show dial-peer voice
show frame-relay fragment
show frame-relay vofr
show interfaces serial
show traffic-shape queue
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]]]
interface | (Optional) The specific interface type and number for which you wish to display FRF.11 subchannel information. |
dlci | (Optional) The specific data link connection identifier for which you wish to display FRF.11 subchannel information. |
cid | (Optional) The specific subchannel for which you wish to display information. |
Privileged EXEC
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.
The following is sample output from the show frame-relay vofr command when an interface is not specified:
3640_vofr#show frame-relay vofr interface vofr-type dlci cid cid-type Serial0/0.1 VoFR 16 4 data Serial0/0.1 VoFR 16 5 call-control Serial0/0.1 VoFR 16 10 voice Serial0/1.1 VoFR cisco 17 4 data
The following is sample output from the show frame-relay vofr command when an interface is specified:
3640_vofr#show frame-relay vofr serial0 interface vofr-type dlci cid cid-type Serial0 VoFR 16 4 data Serial0 VoFR 16 5 call-control Serial0 VoFR 16 10 voice
The 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 16 VoFR Configuration for interface Serial0 dlci vofr-type cid cid-type input-pkts output-pkts dropped-pkts 16 VoFR 4 data 0 0 0 16 VoFR 5 call-control 85982 86099 0 16 VoFR 10 voice 2172293 6370815 0
The 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 10 VoFR Configuration for interface Serial0 dlci 16 vofr-type VoFR cid 10 cid-type voice input-pkts 2172293 output-pkts 6370815 dropped-pkts 0
Table 16 describes the fields shown in the display.
| Field | Description |
|---|---|
interface | Number of the interface that has been selected for observation of FRF.11 subchannels. |
vofr-type | Type of the VoFR DLCI being observed. |
cid | The portion of the specified DLCI that is carrying the designated traffic type. A DLCI can be subdivided into 255 subchannels. |
cid-type | The type of traffic carried on this subchannel. |
input-pkts | Number of packets received by this subchannel. |
output-pkts | Number of packets transmitted on this subchannel. |
dropped-pkts | Total number of packets discarded by this subchannel. |
show call active voice
show call history voice
show dial-peer voice
show frame-relay fragment
show frame-relay pvc
show voice-port
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]
number | Interface number. |
accounting | (Optional) Displays the number of packets and bytes of each protocol type that have been sent through the interface. |
statistics | (Optional) Displays the number of packets and bytes that have gone through the traffic-shaping engine and the route cache. |
EXEC or privileged EXEC
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.
The following is sample output from the show interfaces serial command for a VoFR application:
Router# show interfaces serial 0/0
Serial0/0 is up, line protocol is up
Hardware is CD2430 in sync mode
Internet address is 26.0.0.6/8
MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
reliablility 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, loopback not set
Keepalive not set
FR SVC disabled, LAPF state down
Broadcast queue 0/64, broadcasts sent/dropped 37/0, interface broadcasts 37
Last input 00:00:01, output 00:00:20, output hang never
Last clearing of "show interface" counters 00:16:16
Queueing strategy: dual fifo
Output queue: high size/max/dropped 0/200/0
Output queue 0/100, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
39 packets input, 2995 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
39 packets output, 2975 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Table 17 describes the significant fields shown in the display.
| Field | Description |
|---|---|
Serial... is {up | down} | Indicates whether the interface hardware is currently active (whether carrier detect is present) or if it has been taken down by an administrator. |
line protocol | Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful) or if it has been taken down by an administrator. |
Hardware is | Specifies the hardware type. |
Internet address is | Specifies the Internet address and subnet mask. |
MTU | Maximum transmission unit for the interface. |
BW | Indicates the value of the bandwidth parameter that has been configured for the interface (in kilobits per second). The bandwidth parameter is used to compute IGRP metrics only. If the interface is attached to a serial line with a line speed that does not match the default (1536 or 1544 for T1 and 56 for a standard synchronous serial line), use the bandwidth command to specify the correct line speed for this serial line. |
DLY | Delay of the interface in microseconds. |
reliability | Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes. |
txload | Transmit load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. |
rxload | Receive load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. |
Encapsulation | Encapsulation method assigned to this interface. |
loopback | Indicates whether loopback is set or not. |
keepalive | Indicates whether keepalives are set or not. |
FR SVC | Indicates whether Frame Relay switched virtual circuits are enabled or disabled. |
LAPF state | Indicates whether the LAPF protocol is up or down. |
Broadcast queue | Number of packets in the broadcast queue/size of broadcast queue. |
broadcasts sent/dropped | Number of broadcast packets sent/dropped at this interface. |
Last input | Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed. |
Last output | Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. |
output hang | Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed. |
Last clearing of "show interface" counters | Elapsed time in hours, minutes, and seconds since the counters in this display that measure cumulative statistics (such as number of bytes transmitted and received) were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago. |
Queueing strategy | Type of queuing performed on this interface. (Other queuing strategies are fifo (first-in first-out), priority-list, custom-list, and weighted fair.) |
Output queue (high size) | Number of packets in the voice queue/maximum size of the queue/number of packets dropped due to a full queue. This line only appears in the display when voice packets are being transmitted across this interface. |
Output queue (size/max/drops) | Number of packets in the output queue/maximum size of the queue/number of packets dropped due to a full queue. |
Input queue (size/max/drops) | Number of packets in the input queue/maximum size of the queue/number of packets dropped due to a full queue. |
5 minute input rate | Average number of bits and packets transmitted per second in the last 5 minutes. The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period. |
packets input | Total number of error-free packets received by the system. |
bytes | Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. |
no buffer | Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events. |
Received... broadcasts | Total number of broadcast or multicast packets received by the interface. |
runts | Number of packets that are discarded because they are smaller than the medium's minimum packet size. |
giants | Number of packets that are discarded because they exceed the medium's maximum packet size. |
throttles | Number of times the receiver on the port was disabled, possibly due to buffer or processor overload. |
input errors | Total number of no buffer, runts, giants, throttles, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts. |
CRC | Number of times the cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link. |
frame | Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems. |
overrun | Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. |
ignored | Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased. |
abort | Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment. |
packets output | Total number of messages transmitted by the system. |
bytes output | Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
underruns | Number of times that the transmitter has been running faster than the router can handle. This might never be reported on some interfaces. |
output errors | Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories. |
collisions | Number of messages retransmitted due to an Ethernet collision. This usually is the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). Some collisions are normal. However, if your collision rate climbs to around 4 or 5%, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets. |
interface resets | Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds' time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down. |
output buffer failures | Number of times that a packet was not output from the output hold queue because of a shortage of MEMD shared memory. Number of "no resource" errors on the output. |
output buffers swapped out | Number of packets stored in main memory because the output queue was full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty. |
carrier transitions | Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often. |
DCD | Status of the data carrier detect signal on this interface. |
DSR | Status of the data set ready signal on this interface. |
DTR | Status of the data terminal ready signal on this interface. |
RTS | Status of the request to send signal on this interface. |
CTS | Status of the clear to send signal on this interface. |
The following is sample output from the show interfaces serial statistics command for a VoFR application:
Router# show interfaces serial 0/0 statistics
Serial0/0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 5668 447428 5663 446995
Route cache 0 0 0 0
Total 5668 447428 5663 446995
Table 18 describes the fields shown in the display.
| Field | Description |
|---|---|
Switching path | Mechanism receiving and forwarding frames across the interface. |
Pkts In | Number of packets received by the switching mechanism. |
Chars In | Number of characters received by the switching mechanism. |
Pkts Out | Number of packets forwarded by the switching mechanism. |
Chars Out | Number of characters forwarded by the switching mechanism. |
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.
show interfaces
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]]
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. |
EXEC or Privileged EXEC
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.
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 16
Traffic queued in shaping queue on Serial1.1 dlci 16
Queuing strategy: weighted fair
Queuing 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/0
Conversation 5, linktype: ip, length: 608
source: 172.21.59.21, destination: 255.255.255.255, id: 0x0006, ttl: 255,
TOS: 0 prot: 17, source port 68, destination port 67
The 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 16 Traffic queued in shaping queue on Serial1.1 dlci 16 Queuing strategy: priority-group 4 Queuing Stats: low/1/80/0 (queue/size/max total/drops) Packet 1, linktype: cdp, length: 334, flags: 0x10000008
The 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 16 Traffic queued in shaping queue on Serial1.1 dlci 16 Queuing strategy: fcfs Queuing Stats: 1/60/0 (size/max total/drops) Packet 1, linktype: cdp, length: 334, flags: 0x10000008
Table 19 describes the fields shown in these displays.
| Field | Description |
|---|---|
Queuing strategy | When Frame Relay traffic shaping is configured, the queuing type can be weighted fair, custom-queue, priority-group, or fcfs (first-come-first-serve), depending on what is configured on the Frame Relay map-class for this DLCI. The default is fcfs for Frame Relay traffic shaping. When generic traffic shaping is configured, the only queuing type available is weighted fair queuing. |
Queuing Stats | Statistics for the configured queuing strategy:
|
Conversations active | Number of currently active conversations. |
Conversations max total | Maximum allowed number of concurrent conversations. |
Reserved Conversations active | Number of currently active conversations reserved for voice. |
Reserved Conversations allocated | Maximum configured number of conversations reserved. |
depth | Number of packets currently queued. |
weight | Number used to classify and prioritize the packet. |
discards | Number of packets discarded from queues. |
Packet | Number of queued packet. |
linktype | Protocol type of the queued packet. (cdp = Cisco Discovery Protocol) |
length | Number of bytes in the queued packet. |
flags | Number of flag characters in the queued packet. |
source | Source IP address. |
destination | Destination IP address. |
id | Packet ID. |
ttl | Time to live count. |
TOS | IP type of service. |
prot | Layer 4 protocol number. Refer to RFC 943 for a list of protocol numbers. (17 = UDP) |
source port | Port number of source port. |
destination port | Port number of destination port. |
show frame-relay fragment
show frame-relay pvc
show frame-relay vofr
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]
voice-port | Slot number or slot/port number of the voice interface for which you wish to display permanent call information. |
summary | Displays summary information about VoFR, VoATM, and VoHDLC ports used for permanent connections. |
EXEC or Privileged EXEC
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.
The following is sample output for the show voice permanent-call command:
router# show voice permanent-call 1/1 1/1 state=connect coding=G729A payload size=30 vad=off ec=8 (ms), cng=off fax=on digit_relay=on Seq num = off, VOFR Serial0,dlci = 550,cid = 6 TX INFO :slow-mode seq#= 25, sig pkt cnt= 19646, last-ABCD=1101 hardware-state ACTIVE signal type is CEPT/MELCAS voice-gate CLOSED,network-path OPEN MASTER 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 RX INFO :slow-mode, sig pkt cnt= 19648, under-run = 0, over-run = 0 missing = 0, out of seq = 0, very late = 0 playout depth = 0 (ms), refill count = 1 prev-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 24 16 24 16 24 16 24 16 24 0 0 0 0 0 0 0 0 signaling playout history 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101 1101
The following is sample output for the show voice permanent-call summary command:
router# show voice permanent-call summary 1/1 state= connect, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 880,cid = 6 1/2 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 102 1/3 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 103 1/4 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 104 1/5 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 105 1/6 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 106 1/7 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 107 1/8 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 108 1/9 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 109 1/10 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 110 1/11 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 111 1/12 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 112 1/13 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 113 1/14 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 114 1/15 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 115 1/17 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 117 1/18 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 118 1/19 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 119 1/20 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 120 1/21 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 121 1/22 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 122 1/23 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 123 1/24 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 124 1/25 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=on digit_relay=off, VOFR Serial0:1,dlci = 990,cid = 125
Table 20 describes the fields shown in these displays.
| Field | Description |
|---|---|
state | Current status of the call on this voice port. |
coding | CODEC type used for this call. |
payload size | Size in bytes of the voice payload. |
vad | Indicates whether voice activity detection is turned on or off. |
ec | Echo canceller length in milliseconds. |
cng | Indicates whether or not comfort noise generation is used. |
fax | Indicates if fax-relay is enabled. |
digit_relay | Indicates if FRF.11 Annex A DTMF digit-relay is enabled. |
Seq num | Indicates whether sequence numbers are turned on or off. |
VOFR | Indicates the interface used for this call. |
dlci | Indicates the DLCI for this call. |
cid | Indicates the DLCI subchannel for this call |
TX INFO: slow-mode |
Indicates that FRF.11 Annex B packets are being sent at the slow rate defined by the signal timing keepalive period. Sequence number of the last packet transmitted. |
sig pkt cnt | Number of signaling packets sent by this dial peer. |
last-ABCD | Last ABCD signaling state sent by this dial peer to the network. |
hardware-state | Indicates the on-hook/off-hook state of the call when the signaling protocol in use is a supported protocol. Not valid when the signal-type is "transparent." |
signal type | Indicates the type of call-control signaling used by this dial peer. |
voice-gate | Indicates whether voice packets are being sent (OPEN) or not (CLOSED). |
network-path | Indicates if any type of packet is being sent (OPEN) or not sent (CLOSED) to the network. This field will only indicate CLOSED if the port is configured as a slave using the connection trunk answer-mode command. |
RX INFO: slow-mode |
Indicates that FRF.11 Annex B packets are being received at the slow rate. Successive packets have the same sequence number. |
sig pkt cnt | Number of slow-mode signaling packets received by this dial peer. |
under-run | Valid for fast-mode only. Counts the number of times the signaling playout buffer became empty during FRF.11 Annex B fast-mode. In this mode, signaling packets are expected to be received every 20 milliseconds. |
over-run | Valid for fast-mode only. Counts the number of times the signaling playout buffer became full during FRF.11 Annex B fast-mode. In this mode, signaling packets are expected to be received every 20 milliseconds. |
missing | Indicates the number of FRF.11 Annex B packets that were counted as missing based on checking Annex B sequence numbers. |
out of seq | Indicates the number of FRF.11 Annex B packets that were counted as received in the wrong order based on checking Annex B sequence numbers. |
very late | Indicates the number of FRF.11 Annex B packets that were received with a sequence number significantly different from the expected sequence number. |
playout depth | Valid for fast-mode only. Shows the current FRF.11 Annex B signaling buffer playout depth in milliseconds. |
refill count | Indicates the number of times the FRF.11 Annex B signaling playout buffer was refilled as a result of a slow-mode to fast-mode transition. |
prev-seq# | Sequence number of the last FRF.11 Annex B signaling packet received. |
last-ABCD | Last ABCD signaling bit pattern sent to the attached PBX (telephone network side). In the out-of-service condition, this will show the OOS pattern being sent to the PBX. |
slave standby timeout | Value configured using the signal timing oos standby command for the applicable voice class permanent entry. |
max inter-arrival time | Maximum interval between the arrival of fast-mode FRF.11 Annex B packets since the last time this parameter was displayed. |
current timer | Time in milliseconds since the last signaling packet was received. |
max timeout timer | Maximum value of the "current timer" parameter since the last time it was displayed. |
restart timeout | Connection restart timeout value. |
signaling packet fast-mode inter-arrival time | Shows the last several values of the fast-mode FRF.11 Annex B signaling packed inter-arrival time. |
signaling playout history | Shows recent ABCD signaling bits received from the data network. |
show frame-relay fragment
show frame-relay pvc
show frame-relay vofr
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
number | Specifies the keepalive signaling packet interval in seconds. The valid range is from 1 to 65535 seconds. |
5 seconds
Voice-class configuration
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.
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 10
router(config-class)# signal keepalive 3
router(config-class)# exit
router(config)# dial-peer voice 100 vofr
router(config-dial-peer)# voice-class permanent 10
dial-peer voice
signal pattern
signal timing idle suppress-voice
signal timing oos
voice class permanent
voice-class permanent
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
idle receive | Specifies that the signal pattern applies to the idle state of the call for receive bits. The receive direction is from the network to the PBX. |
idle transmit | Specifies that the signal pattern applies to the idle state of the call for transmit bits. The transmit direction is from the PBX to the network. |
oos receive | Specifies that the signal pattern applies to the out-of-service state of the call for receive bits. |
oos transmit | Specifies that the signal pattern applies to the out-of-service state of the call for transmit bits. |
WORD | The ABCD bit pattern. Valid values are from 0000 to 1111. |
No signal pattern is defined.
Voice-class configuration
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.
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)# exit router(config)# dial-peer voice 100 vofr router(config-dial-peer)# voice-class permanent 10
The 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 0001 router(config-class)# exit router(config)# dial-peer voice 100 vofr router(config-dial-peer)# voice-class permanent 10
dial-peer voice
signal keepalive
signal timing idle suppress-voice
signal timing oos
signal-type
voice class permanent
voice-class permanent
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
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. |
No signal timing idle suppress-voice timer is configured.
Voice-class configuration
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.
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 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)# signal timing idle suppress-voice 5 router(config-class)# exit router(config)# dial-peer voice 100 vofr router(config-dial-peer)# voice-class permanent 10 router(config-dial-peer)# signal-type transparent
dial-peer voice
signal keepalive
signal pattern
signal timing oos
signal-type
voice class permanent
voice-class permanent
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
restart | If no signaling packets are received for this period, the permanent voice connection will be torn down and an attempt to achieve reconnection will be made. |
slave-standby | If no signaling packets are received for this period, a slave port returns to its initial standby state. This option only applies to slave ports (ports configured using the connection trunk number answer-mode command. |
suppress-all | If the transmit OOS pattern (from the PBX to the network) matches for this period of time, the router stops sending all packets to the network. |
suppress-voice | If the transmit OOS pattern (from the PBX to the network) matches for this period time, the router stops sending voice packets to the network. Signaling packets continue to be sent with the alarm indication set (AIS). |
timeout | If no signaling packets are received for this period of time, the router sends the configured receive OOS pattern to the PBX. Also, the router stops sending voice packets to the network. |
seconds | Duration in seconds for the above settings. The valid range is from 0 to 65535. |
No signal timing OOS pattern parameters are configured.
Voice-class configuration
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.
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 10 router(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 60 router(config-class)# exit router(config)# dial-peer voice 100 vofr router(config-dial-peer)# voice-class permanent 10
dial-peer voice
signal keepalive
signal pattern
signal timing idle suppress-voice
signal-type
voice class permanent
voice-class permanent
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}For the Cisco MC3810:
signal-type {cas | cept | ext-signal | transparent}
cas | North American EIA-464 Channel-Associated Signaling (robbed bit signaling). |
cept | (Supported on the MC3810 only.) Provides a basic E1 ABCD signaling protocol. Used primarily for E&M interfaces. When used with FXS/FXO interfaces, this protocol is equivalent to MELCAS. |
ext-signal | External signaling. The DSP does not generate any signaling frames. Use this option when there is an external signaling channel (for example, CCS) or when you need to have a permanent "dumb" voice pipe. |
transparent | (Supported on the MC3810 only.) Selecting this option produces different results depending on whether you are using a digital voice module (DVM) or an analog voice module (AVM). For a DVM: The ABCD signaling bits are copied from or transported through the T1/E1 interface "transparently," without modification or interpretation. This enables the MC3810 to handle arbitrary or unknown signaling protocols. For an AVM: It is not possible to provide "transparent" behavior since the MC3810 must interpret the signaling information in order to read/write the correct state to the analog hardware. This option is mapped to be equal to "cas." |
cas
Dial-peer configuration
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.
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 vofr
router(config-dial-peer)# signal-type ext-signal
router(config-dial-peer)#
codec (dial-peer)
connection
destination-pattern
dtmf-relay
preference
session protocol
session target
sequence-numbers
This command has no arguments or keywords.
Enabled
Dial-peer configuration
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.
The following example enables VAD for a VoIP dial peer, starting from global configuration mode:
router(config)# dial-peer voice 200 voip
router(config-dial-peer)# vad
router(config-dial-peer)#
comfort-noise
dial-peer voice
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]]]]
cisco | (Optional) Cisco proprietary voice encapsulation for VoFR with data carried on CID 4 and call-control on CID 5. This option is required on the Cisco MC3810 for applications using switched calls or Cisco trunks. |
data | (Optional) Used to select a subchannel (CID) for data other than the default subchannel, which is 4. |
cid | Specifies the subchannel to be used for data. Valid values are from 4 to 255; the default is 4. If data is specified, a valid CID must be entered. |
call-control | (Optional) Used to specify that a subchannel will be reserved for call-control signaling. This option is not supported on the Cisco MC3810. |
cid | (Optional) Specifies the subchannel to be used for call-control signaling. Valid values are from 4 to 255; the default is 5. If call-control is specified and a CID is not entered, the default CID will be used. |
Disabled
Frame Relay DLCI
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.
Table 21 describes special conditions and restrictions for the use of the vofr command on the Cisco MC3810.
| Type of Call | Conditions and Restrictions |
|---|---|
FRF.11 trunks | 1. Do NOT use cisco option or call-control option. 2. Use vofr or vofr data cid. |
Cisco trunks | 1. Must use vofr cisco. |
switched-vofr | 1. Must use vofr cisco. |
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.
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/1
router(config-if)# frame-relay interface-dlci 100
router(config-fr-dlci)# vofr
router(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-control router(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 15 router(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 15 router(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-control router(config-fr-dlci)#
To configure CID 10 for data with no call-control, enter the following command:
router(config-fr-dlci)# vofr data 10 router(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 cisco router(config-fr-dlci)#
frame-relay interface-dlci
class
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
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. |
No voice class is configured.
Global configuration
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.
The following example shows how to create a permanent voice class starting from global configuration mode:
router(config)# voice class permanent 10
router(config-class)#
signal keepalive
signal pattern
signal timing idle suppress-voice
signal timing oos
voice-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
tag | Specifies the unique tag number assigned to the permanent voice class. The valid range for this tag is 1 to 10000. The tag number maps to the tag number created using the voice class permanent global configuration command. |
This command has no default.
Dial-peer configuration
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810.
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 10 router(config-class)# signal keepalive 3router(config-class)#exit router(config)# dial-peer voice 100 vofr router(config-dial-peer)# voice-class permanent 10
signal keepalive
signal pattern
signal timing idle suppress-voice
signal timing oos
signal-type
voice class permanent
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:
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 sessionThis command has no keywords or arguments.
Privileged EXEC
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."
The following example shows sample output from the debug ccfr11 session command:
router# debug ccfrf11 session
INCOMING 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:Entered
CALL SETUP (MASTER):
5d22h:ccfrf11_call_setup_request:Entered
5d22h:ccfrf11_evhandle_call_setup_request:Entered
5d22h: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 successful
5d22h:ccfrf11_caps_ind:PeerTag = 810
5d22h: codec(preferred) = 512, fax_rate = 2, vad = 2
5d22h: cid = 30, config_bitmask = 1, codec_bytes = 24, signal_type=2
5d22h: required_bandwidth 6500
5d22h: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 starting
incoming 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 0x610DB7A4
freeccb_flag=1, call_disconnected_flag=1
debug ccswvoice vofr-debug
debug ccswvoice vofr-session
debug frame-relay fragment
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframe
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-debugThis command has no arguments or keywords.
Privileged EXEC
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.
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 100
cid 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=22
cause_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 CONN
ccfrf11_caps_ind:codec(preferred) = 0
debug ccfrf11 session
debug ccswvoice vofr-session
debug frame-relay fragment
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframe
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-sessionThis command has no arguments or keywords.
Privileged EXEC
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.
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 RELCOMP 3640_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 CONN 3640_vofr(config-voiceport)#
debug ccfrf11 session
debug ccswvoice vofr-debug
debug frame-relay fragment
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframe
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]
event | Displays event or error messages related to Frame Relay fragmentation. |
interface | Displays fragments received and/or transmitted on the specified interface. |
type | Interface type for which you wish to display fragments received and/or transmitted. |
number | Interface number. |
dlci | DLCI value of the PVC for which you wish to display fragments received and/or transmitted. |
Privileged EXEC
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.
The following example shows sample output from the debug frame-relay fragment command:
router#debug frame-relay fragment interface serial 0/0 109 This may severely impact network performance. You are advised to enable 'no logging console debug'. Continue?[confirm] Frame Relay fragment/packet debugging is on Displaying fragments/packets on interface Serial0/0 dlci 109 only Serial0/0(i): dlci 109, rx-seq-num 126, exp_seq-num 126, BE bits set, frag_hdr 04 C0 7E Serial0/0(o): dlci 109, tx-seq-num 82, BE bits set, frag_hdr 04 C0 52
The following example shows sample output from the debug frame-relay fragment event command:
router#debug frame-relay fragment event
This may severely impact network performance.
You are advised to enable 'no logging console debug'. Continue?[confirm]
Frame Relay fragment event/errors debugging is on
Frame-relay reassembled packet is greater than MTU size, packet dropped on serial 0/0
dlci 109
Unexpected B bit frame rx on serial0/0 dlci 109, dropping pending segments
Rx an out-of-sequence packet on serial 0/0 dlci 109, seq_num_received 17
seq_num_expected 19
debug ccfrf11 session
debug ccswvoice vofr-debug
debug ccswvoice vofr-session
debug voice vofr
debug vpm port
debug vtsp port
debug vtsp vofr subframe
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 vofr
This command has no arguments or keywords.
Privileged EXEC
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.
The following example shows sample output from the debug voice vofr command for a Cisco trunk:
router# debug voice vofr
1d05h: 1/1:VOFR, unconf ==> pending_start
1d05h: 1/1:VOFR,create VOFR
1d05h: 1/1:VOFR,search dial-peer 7100 preference 0
1d05h: 1/1:VOFR, pending_start ==> start
1d05h: 1/1:VOFR,
1d05h:voice_configure_perm_svc:
1d05h:dial-peer 7100 codec = G729A payload size = 30 vad = off dtmf relay = on
seq num = off
1d05h:voice-port 1/1 codec = G729A payload size = 30 vad = off dtmf relay = on
seq num = off
1d05h: 1/1:VOFR,SIGNAL-TYPE = cept
1d05h:init_frf11 tcid 0 master 0 signaltype 2
1d05h:Going Out Of Service on tcid 0 with sig state 0001
1d05h: 1/1:VOFR, start get event idle
1d05h: 1/1:VOFR, start get event
1d05h: 1/1:VOFR, start get event set up
1d05h: 1/1:VOFR, start ==> pending_connect
1d05h: 1/1:VOFR, pending_connect get event connect
1d05h: 1/1:VOFR, pending_connect ==> connect
1d05h: 1/1:VOFR,SIGNAL-TYPE = cept
1d05h:init_frf11 tcid 0 master 1 signaltype 2
1d05h:start_vofr_polling on port 0 signaltype 2
The 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 2 1d05h: 1/1:VOFR,SIGNAL-TYPE = cept 1d05h:Launch Voice Trunk:signal-type 2 1d05h:calculated bandwidth = 10, coding = 6, size = 30 1d05h:%Voice-port 1/1 is down. 1d05h: 1/1:VOFR, pending_start get event idle 1d05h:Codec Type = 6 Payload Size = 30 Seq# off 1d05h:%Voice-port 1/1 is up. 1d05h:init_frf11 tcid 0 master 1 signaltype 2 1d05h:status OK :cid = 100 1d05h: 1/1:VOFR, 1d05h:start FRF11 1d05h: 1/1:VOFR, pending_start ==> frf11 1d05h: 1/1:VOFR,SIGNAL-TYPE = cept
debug ccfrf11 session
debug ccswvoice vofr-debug
debug ccswvoice vofr-session
debug frame-relay fragment
debug vpm port
debug vtsp port
debug vtsp vofr subframe
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/port
slot-number | Specifies the slot number in the Cisco router where the voice interface card is installed. Valid entries are from 0 to 3, depending on the router being used and the slot where the voice interface card has been installed. |
subunit-number | Specifies the subunit on the voice interface card where the voice port is located. Valid entries are 0 or 1. |
port | Specifies the voice port. Valid entries are 0 or 1. |
EXEC or Privileged EXEC
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.
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=128
packet_id=42 transport_protocol=1 playout_delay=100 signaling_mode=0
t_ssrc=0 r_ssrc=0 t_vpxcc=0 r_vpxcc=0
*Mar 1 03:21:39.811: dsp_set_sig_state: [1/1/0] packet_len=12
channel_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=12
channel_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=128
packet_id=42 transport_protocol=3 playout_delay=100 headerbytes = 0xA0
Note 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.
debug vpm all
debug vpm dsp
debug vpm signal
debug vpm spi
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/port
slot-number | Specifies the slot number in the Cisco router where the voice interface card is installed. Valid entries are from 0 to 3, depending on the router being used and the slot where the voice interface card has been installed. |
subunit-number | Specifies the subunit on the voice interface card where the voice port is located. Valid entries are 0 or 1. |
port | Specifies the voice port. Valid entries are 0 or 1. |
Privileged EXEC
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.
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=1
packet_id=75
*Mar 1 03:17:33.691: dsp_open_voice_channel: [] packet_len=12
channel_id=1 packet_id=74 alaw_ulaw_select=0 transport_protocol=2
*Mar 1 03:17:33.695: dsp_set_playout_delay: [] packet_len=18
channel_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=1
packet_id=66 flags=0x0
*Mar 1 03:17:33.695: dsp_set_gains: [] packet_len=12 channel_id=1 packet_id=91
in_gain=0 out_gain=65506
*Mar 1 03:17:33.695: dsp_vad_enable: [] packet_len=10 channel_id=1 packet_id=78
thresh=-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=1
packet_id=75
*Mar 1 03:17:33.911: dsp_open_voice_channel: [] packet_len=12 channel_id=1
packet_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=76
mode=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=1
packet_id=66 flags=0x0
*Mar 1 03:17:33.911: dsp_set_gains: [] packet_len=12 channel_id=1 packet_id=91
in_gain=0 out_gain=65506
*Mar 1 03:17:33.911: dsp_vad_enable: [] packet_len=10 channel_id=1 packet_id=78
thresh=-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=73
coding_type=14 voice_field_size=60 VAD_flag=1 echo_length=128
comfort_noise=1 fax_detect=1 digit_relay=0
debug vtsp all
debug 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 subframe
payload | Number used to selectively display subframes of a specific payload. The payload types are: 0: Primary Payload - WARNING! This option may cause network instability |
from-dsp | Displays only the subframes received from the DSP. |
to-dsp | Displays only the subframes going to the DSP. |
Privileged EXEC
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.
The following example shows sample output from the debug vtsp vofr subframe command:
router# debug vtsp vofr subframe 2
vtsp 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 AA
AA AA AA
*Mar 6 18:21:17.449:VoFR frame received from DSP (18 bytes):9E 02 19 AA AA AA AA AA AA
AA
*Mar 6 18:21:23.969:VoFR frame received from Network (24 bytes):9E 02 19 AA AA AA AA
AA AA AA
*Mar 6 18:21:24.005:VoFR frame received from DSP (18 bytes):9E 02 19 AA AA AA AA AA AA
AA
debug vtsp all
debug vtsp port
Posted: Sun Mar 28 17:58:11 PST 1999
Copyright 1989-1999©Cisco Systems Inc.