-
Cisco IOS Voice Command Reference
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
New and Modified Commands
-
Commands: A
-
Commands: B
-
Commands: cache --> call fallback jitter-probe num-packets
-
Commands: call fallback jitter-probe precedence --> ces connect
-
Commands: ces initial-delay --> codec preference
-
Commands: comfort-noise --> customer-id
-
Commands: default (MGCP profile) through direct-inward-dial
-
Commands: E
-
Commands: F
-
Commands: G
-
Commands: H
-
Commands: I
-
Commands: K
-
Commands: L
-
Commands: M
-
Commands: N
-
Commands: O
-
Commands: P through Q
-
Commands: R
-
Commands: SCCP through sgcp tse payload
-
Commands: show aal2 profile through show controllers timeslots
-
Commands: show controllers voice through show mgcp
-
Commands: show mgcp connection through show ss7 sm session
-
Commands: show ss7 sm set through shutdown (voice-port)
-
Commands: signal through suppress
-
Commands: T
-
Commands: U
-
Commands: V through W
-
Commands: Z
-
Feedback
Table Of Contents
date-format (telephony-service)
default-destination (cm-fallback)
description (voice source group)
destination-pattern (interface)
dial-peer no-match disconnect-cause
dialplan-pattern (cm-fallback)
dialplan-pattern (telephony-service)
dn-webedit (telephony-service)
dspfarm confbridge maximum sessions
dspfarm transcoder maximum sessions
dtmf-relay (Voice over Frame Relay)
Cisco IOS Voice Commands:
D
This chapter contains commands to configure and maintain Cisco IOS voice applications. The commands are presented in alphabetical order beginning with the letter D. Some commands required for configuring voice may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice Configuration Guide.
date-format (cm-fallback)
To set the date display format on all the Cisco IP phones attached to the router, use the date-format command in call-manager-fallback configuration mode. To display the date in default format, use the no form of this command.
date-format {mm-dd-yy | dd-mm-yy}
no date-format {mm-dd-yy | dd-mm-yy}
Syntax Description
mm-dd-yy
Sets to month, day, and year. Each slot needs a two-digit number. This format is the default setting.
dd-mm-yy
Sets to day, month, and year. Each slot needs a two-digit number.
Defaults
The default is mm-dd-yy.
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
The date-format command sets the date display format on all the Cisco IP phones attached to the router.
Examples
The following example sets the date format to date, month, and year for all affected Cisco IP phones:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# date-format dd-mm-yyRelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters call-manager-fallback configuration mode.
date-format (telephony-service)
To set the date display format on all the Cisco IP phones attached to a router, use the date-format command in telephony-service configuration mode. To display the date in the default format, use the no form of this command.
date-format {mm-dd-yy | dd-mm-yy}
no date-format {mm-dd-yy | dd-mm-yy}
Syntax Description
mm-dd-yy
Sets to month, day, and year. Each slot needs a two-digit number. This format is the default setting.
dd-mm-yy
Sets to day, month, and year. Each slot needs a two-digit number.
Defaults
The default is set to mm-dd-yy.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The date-format command sets the date display format on all Cisco IP phones attached to the router.
Examples
The following example sets the date format to date, month, and year for all affected Cisco IP phones:
Router(config)# telephony-serviceRouter(config-telephony-service)# date-format dd-mm-yyRelated Commands
telephony-service
Enables Cisco IOS Telephony Service and enters telephony-service configuration mode.
default (MGCP profile)
To configure an MGCP profile command to its default value, use the default command in MGCP profile configuration mode. To disable the default command, use the no form of the command for that profile parameter.
default command
no default command
Syntax Description
Defaults
No default behaviors or values
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The default (MGCP profile) command instructs the MGCP profile to use the default value of the specified command whenever the profile is called. This has the same effect as using the no form of the specified command, but the default command clearly specifies which commands are using their default values.
To use the default values for more than one command, enter each command on a separate line.
Examples
The following example shows how to configure the default values for three MGCP profile commands:
Router(config)# mgcp profile newyorkRouter(config-mgcp-profile)# default max1 retriesRouter(config-mgcp-profile)# default timeout tdinitRouter(config-mgcp-profile)# default timeout tone mwiRelated Commands
default-destination (cm-fallback)
To assign a default destination number for incoming telephone calls on the Survivable Remote Site (SRS) Telephony router, use the default-destination command in call-manager-fallback configuration mode. To disable the default destination number on the SRS Telephony router, use the no form of this command.
default-destination telephone-number
no default-destination telephone-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
The default-destination command assigns default destination numbers when a call arrives at a foreign exchange office (FXO) port without called number information. A default directory number is required to route the call.
If a default destination number is set, calls arriving on an FXO port are routed to the default destination number that is provided. If a default destination number is not set, calls arriving on the FXO port receive a secondary dial tone. The caller must then enter an extension number.
Examples
The following example shows how to set the default destination as 40802:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# default-destination 40802Related Commands
default-file vfc
To specify an additional (or different) file from the ones in the default file list and stored in voice feature card (VFC) Flash memory, use the default-file vfc command in global configuration mode. To delete the file from the default file list, use the no form of this command.
default-file filename vfc slot
no default-file filename vfc slot
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
11.3(1)NA
This command was introduced on the Cisco AS5300.
12.0(3)T
This command was integrated into Cisco IOS Release 12.0(3)T.
Usage Guidelines
When VCWare is unbundled, it automatically adds DSPWare to Flash memory, creates both the capability and default file lists, and populates these lists with the default files for that version of VCWare. The default file list includes the files that is used to boot up the system.
Use the default-file vfc command to add a specified file to the default file list, replacing the existing default for that extension type.
Examples
The following example specifies that the bas-vfc-1.0.14.0.bin file, which is stored in VFC Flash memory, be added to the default file list:
default-file bas-vfc-1.0.14.0.bin vfc 0Related Commands
cap-list vfc
Adds a voice codec overlay file to the capability file list.
delete vfc
Deletes a file from VFC Flash memory.
define
To define the transmit and receive bits for North American ear and mouth (E&M) and E&M Mercury Exchange Limited Channel-Associated Signaling (MELCAS) voice signaling, use the define command in voice-port configuration mode. To restore the default value, use the no form of this command.
define {tx-bits | rx-bits} {seize | idle} {0000 | 0001 | 0010 | 0011 | 0100 | 0101 | 0110 | 0111 | 1000 | 1001 | 1010 | 1011 | 1100 | 1101 | 1110 | 1111}
no define {tx-bits | rx-bits} {seize | idle} {0000 | 0001 | 0010 | 0011 | 0100 | 0101 | 0110 | 0111 | 1000 | 1001 | 1010 | 1011 | 1100 | 1101 | 1110 | 1111}
Syntax Description
Defaults
The default is to use the preset signaling patterns as defined in American National Standards Institute (ANSI) and European Conference of Postal and Telecommunications Administrations (CEPT) standards, as follows:
•
For North American E&M:
–
–
–
–
•
–
–
–
–
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The define command applies to E&M digital voice ports associated with T1/E1 controllers.
Use the define command to match the E&M bit patterns with the attached telephony device. Be careful not to define invalid configurations, such as all 0000 on E1, or identical seized and idle states. Use this command with the ignore command.
Examples
To configure a voice port on a Cisco 2600 or Cisco 3600 series router that is sending traffic in North American E&M signaling format to convert the signaling to MELCAS format, enter the following commands:
voice-port 1/0/0define rx-bits idle 1101define rx-bits seize 0101define tx-bits idle 1101define tx-bits seize 0101To configure a voice port on a Cisco MC3810 that is sending traffic in North American E&M signaling format to convert the signaling to MELCAS format, enter the following commands:
voice-port 0/8define rx-bits idle 1101define rx-bits seize 0101define tx-bits idle 1101define tx-bits seize 0101Related Commands
condition
Manipulates the signaling bit-pattern for all voice signaling types.
ignore
Configures a North American E&M or E&M MELCAS voice port to ignore specific receive bits.
delete vfc
To delete a file from voice feature card (VFC) Flash memory, use the delete vfc command in privileged EXEC mode.
delete filename vfc slot
Syntax Description
filename
Specifies the file in VFC Flash memory to be deleted.
slot
Specifies the slot on the Cisco AS5300 in which the specified VFC resides. Range is from 0 to 2.
Command Modes
Privileged EXEC
Command History
11.3(1)NA
This command was introduced on the Cisco AS5300.
12.0(3)T
This command was integrated into Cisco IOS Release 12.0(3)T.
Usage Guidelines
Use the delete vfc command to delete a specific file from VFC Flash memory and to remove the file from the default list or capability list if the specified file is included in those lists.
Note
Examples
The following example deletes the bas-vfc-1.0.14.0.bin file, which is stored in VFC Flash memory of the VFC located in slot 0:
Router# delete bas-vfc-1.0.14.0.bin vfc 0Related Commands
description
To specify a description of the digital signal processor (DSP) interface, use the description command in voice-port or DSP farm interface configuration mode. To describe a MGCP profile that is being defined, use the description command in MGCP profile configuration mode. To disable the interface description, use the no form of this command.
description string
no description
Syntax Description
Defaults
Enabled with a null string.
The MGCP profile has no default value.Command Modes
Voice-port configuration
DSP farm interface configuration
MGCP profile configurationCommand History
Usage Guidelines
Use the description command to describe the DSP interface connection or a defined MGCP profile. The information is displayed when a show command is used, and it does not affect the operation of the interface in any way.
Examples
The following example identifies voice port 1/0/0 on the Cisco 3600 series routers as being connected to the purchasing department:
voice-port 1/0/0description purchasing_deptThe following example identifies DSP farm interface 1/0 on the Cisco 7200 series routers router as being connected to the marketing department:
dspint dspfarm 1/0description marketing_deptThe following example shows a description for an MGCP profile:
mgcp profile newyorkdescription This is the head sales office in New York.dot ...(socket=0)S:.R:250 NAA09092 Message accepted for deliveryS:QUITR:221 madeup@abc.com closing connectionFreeing SMTP ctx at 0x6121D454returned from work_routine, context freedRelated Commands
description (dspfarm)
To include a specific description about the digital signal processor (DSP) interface, use the description command in DSPfarm interface configuration mode. To disable this feature, use the no form of this command.
description string
no description string
Syntax Description
Defaults
Enabled with a null string.
Command Modes
DSPfarm interface configuration
Command History
Usage Guidelines
Use the description command to include descriptive text about this DSP interface connection. This information is displayed when you issue a show command and does not affect the operation of the interface in any way.
Examples
The following example identifies DSPfarm interface 1/0 on the Cisco 7200 series routers router as being connected to the marketing department:
dspint dspfarm 1/0description marketing_deptdescription (ephone-dn)
To specify a directory number description to appear in the header bar of a Cisco IP Phone 7940 or Cisco IP Phone 7960 using Cisco IOS Telephony Service (ITS), use the description command in ephone-dn configuration mode. To return to the default, use the no form of this command.
description string
no description
Syntax Description
Defaults
The directory number of the first line on the phone appears in the header bar.
Command Modes
Ephone-dn configuration
Command History
12.2(11)T
This command was introduced.
12.2(11)YT
The number of characters in the string was modified.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
Use this command with Cisco ITS V2.1 or a later version.
To change the top-line black header bar display, use the description command in the ephone-dn configuration of the first line button.
A typical use for the description command is to display the entire E.164 telephone number in the header bar rather than the extension number that is displayed next to the first line button, which is the default.
Examples
The following example defines a header bar display for a phone on which the first line button is the ephone-dn 51355:
Router(config)# ephone-dn 4Router(config-ephone-dn)# number 51355Router(config-ephone-dn)# description 888-555-1355Related Commands
ephone-dn
Enters ephone directory number configuration mode and configures directory numbers for the Cisco IP phone lines.
number
Configures a valid number for a Cisco IP phone.
description (trunk group)
To add a description to a trunk group, use the description command in trunk group configuration mode. To delete the description, use the no form of this command.
description text
no description text
Syntax Description
Defaults
No default behavior or values
Command Modes
Trunk group configuration
Command History
Examples
The following example shows a description for a trunk group:
Router(config)# trunk group alpha1Router(config-trunk-group)# description carrierAgroup1Related Commands
description (voice source group)
To add a description to a voice source group, use the description command in voice source-group configuration mode. To delete the description, use the no form of this command.
description text
no description text
Syntax Description
text
Describes a voice source group, Maximum length of the voice source group description is 63 alphanumeric characters.
Defaults
No default behavior or values
Command Modes
Voice source-group configuration
Command History
Examples
The following example shows a description for a voice source group:
Router(config)# voice source-group northern1Router(cfg-source-grp)# description carrierBgroup3Related Commands
destination-pattern
To specify either the prefix or the full E.164 telephone number (depending on your dial plan) to be used for a dial peer, use the destination-pattern command in dial-peer configuration mode. To disable the configured prefix or telephone number, use the no form of this command.
destination-pattern [+] string [T]
no destination-pattern [+] string [T]
Syntax Description
Defaults
Enabled with a null string
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the destination-pattern command to define the E.164 telephone number for a dial peer.
The pattern you configure is used to match dialed digits to a dial peer. The dial peer is then used to complete the call. When a router receives voice data, it compares the called number (the full E.164 telephone number) in the packet header with the number configured as the destination pattern for the voice-telephony peer. The router then strips out the left-justified numbers that correspond to the destination pattern. If you have configured a prefix, the prefix is appended to the front of the remaining numbers, creating a dial string, which the router then dials. If all numbers in the destination pattern are stripped out, the user receives a dial tone.
There are certain areas in the world (for example, certain European countries) where valid telephone numbers can vary in length. Use the optional control character T to indicate that a particular destination-pattern value is a variable-length dial string. In this case, the system does not match the dialed numbers until the interdigit timeout value has expired.
Note
Examples
The following example shows configuration of the E.164 telephone number 555-7922 for a dial peer:
dial-peer voice 10 potsdestination-pattern +5557922The following example shows configuration of a destination pattern in which the pattern "43" is repeated multiple times preceding the digits "555":
dial-peer voice 1 voipdestination-pattern 555(43)+The following example shows configuration of a destination pattern in which the preceding digit pattern is repeated multiple times:
dial-peer voice 2 voipdestination-pattern 555%The following example shows configuration of a destination pattern in which the possible numeric values are between 5553409 and 5559499:
dial-peer voice 3 vofrdestination-pattern 555[3-9]4[0-9]9The following example shows configuration of a destination pattern in which the possible numeric values are between 5551439, 5553439, 5555439, 5557439, and 5559439:
dial-peer voice 4 voatmdestination-pattern 555[13579]439Related Commands
destination-pattern (interface)
To specify the ISDN directory number for the telephone interface, use the destination-pattern command in interface configuration mode. To disable the specified ISDN directory number, use the no form of this command.
destination-pattern isdn
no destination-pattern
Syntax Description
Defaults
A default ISDN directory number is not defined for this interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is applicable to the Cisco 800 series routers.
You must specify this command when creating a dial peer. This command does not work if it is not specified within the context of a dial peer. For information on creating a dial peer, refer to the Cisco 800 Series Routers Software Configuration Guide.
Do not specify an area code with the local ISDN directory number.
Examples
The following example specifies 555-1111 as the local ISDN directory number:
destination-pattern 5551111Related Commands
detect v54 channel-group
To enable V.54 loopback detection for the command sent from the remote device, use the detect v54 channel-group command in controller configuration mode. To disable the V.54 loopback detection, use the no form of this command.
detect v54 channel-group channel-number
no detect v54 channel-group channel-number
Syntax Description
Defaults
V.54 loopback detection is disabled.
Command Modes
Controller configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series.
Usage Guidelines
Use the detect v54 channel-group controller configuration command to enable V.54 loopback detection. The remote device sends a loopup inband payload command sequence in fractional T1 (FT1).
Examples
The following example sets the loopback detection for channel-group 1; then the loopback detection is disabled for channel-group 1.
detect v54 channel-group 1no detect v54 channel-group 1Related Commands
loopback remote v54 channel-group
Activates a remote V.54 loopback for the channel group on the far end.
device-id
To identify a gateway associated with a settlement provider, use the device-id command in settlement configuration mode. To reset to the default value, use the no form of this command.
device-id number
no device-id number
Syntax Description
Defaults
The default device ID is 0
Command Modes
Settlement configuration
Command History
12.0(4)XH1
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco AS5300.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
It is optional to identify a gateway associated with a settlement provider.
Examples
The following example sets the device-id to 1000:
settlement 0device-id 1000Related Commands
customer-id
Identifies a carrier or Internet service provider with the settlement provider.
settlement
Enters settlement configuration mode.
dial-control-mib
To specify attributes for the call history table, use the dial-control-mib command in global configuration mode. To restore the default maximum size or retention time of the call history table, use the no form of this command.
dial-control-mib {max-size number | retain-timer number}
no dial-control-mib {max-size number | retain-timer number}
Syntax Description
Defaults
The default call history table length is 50 table entries. The default retain timer is 15 minutes.
Command Modes
Global configuration
Command History
Examples
The following example configures the call history table to hold 400 entries, with each entry remaining in the table for 10 minutes:
dial-control-mib max-size 400dial-control-mib retain-timer 10dialer extsig
To configure an interface to initiate and terminate calls using an external signaling protocol, use the dialer extsig command in interface configuration mode. To discontinue control of the interface by the external signaling protocol, use the no form of this command.
dialer extsig
no dialer extsig
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Usage Guidelines
This command is used with the Network Access Server Package for Media Gateway Control Protocol feature. Configuring the dialer in-band command is a prerequisite to using this command. The configuration is blocked for profile dialers.
Examples
The following example shows output from the dialer extsig command:
Router(config)# interface Dialer1Router(config-if)# dialer extsigRelated Commands
dial-peer cor custom
See the Cisco IOS Dial Technologies Command Reference, Release 12.3 for a description of the dial-peer cor custom command.
dial-peer cor list
See the Cisco IOS Dial Technologies Command Reference, Release 12.3 for a description of the dial-peer cor list command.
dial-peer data
To create a data dial peer and to enter dial-peer configuration mode, use the dial-peer data command in global configuration mode. To remove a data dial peer, use the no form of this command.
dial-peer data tag pots
no dial-peer data tag
Syntax Description
tag
Specifies the dial-peer number. Range is from 1 to 2147483647.
pots
Specifies the incoming POTS dial peer.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
A data dial peer should be defined only for incoming data calls. The incoming called-number and shutdown commands on the data dial peer are allowed. However, the following POTS dial-peer commands are disabled to minimize the run-time impact:
•
•
•
•
•
•
Examples
The following example is a data dial-peer configuration:
dial-peer data 100 potsincoming called-number 100The following example is a voice dial-peer configuration:
dial-peer voice 2001 potsdestination-pattern 2001no digit-stripport 3/1:1Related Commands
dial-peer hunt
To specify a hunt selection order for dial peers, use the dial-peer hunt command in global configuration mode. To restore the default selection order, use the no form of this command.
dial-peer hunt hunt-order-number
no dial-peer hunt
Syntax Description
Defaults
The default is the longest match in the phone number, explicit preference, random selection (hunt order number 0).
Command Modes
Global configuration
Command History
Usage Guidelines
Use the dial-peer hunt dial-peer configuration command if you have configured hunt groups. "Longest match in phone number" refers to the destination pattern that matches the greatest number of the dialed digits. "Explicit preference" refers to the preference setting in the dial-peer configuration. "Least recent use" refers to the destination pattern that has waited the longest since being selected. "Random selection" weights all of the destination patterns equally in a random selection mode.
This command applies to POTS, Voice over IP (VoIP), Voice over Frame Relay (VoFR), Voice over ATM (VoATM), and Multimedia Mail over Internet Protocol (MMOIP) dial peers.
Examples
The following example configures the dial peers to hunt in the following order: (1) longest match in phone number, (2) explicit preference, (3) random selection.
dial-peer hunt 0Related Commands
dial-peer no-match disconnect-cause
To disconnect the incoming ISDN or channel associated signaling (CAS) call when no inbound voice or modem dial peer is matched, use the dial-peer no-match disconnect-cause command in global configuration mode. To restore the default incoming call state (call is forwarded to the dialer), use the no form of this command.
dial-peer no-match disconnect-cause cause-code-number
no dial-peer no-match disconnect-cause cause-code-number
Syntax Description
Defaults
The call is forwarded to the dialer to handle as a modem call.
Command Modes
Global configuration
Command History
Usage Guidelines
By default, calls are forwarded to the dialer to handle as a modem call when no inbound dial peer is matched. The dial-peer no-match disconnect-cause command changes that behavior to disconnect the incoming ISDN or CAS calls when no inbound voice or modem dial peer is matched.
Refer to the ISDN Cause Values table in the Cisco IOS Debug Command Reference, for a list of ISDN cause codes.
Examples
The following example shows that ISDN cause code 47 has been specified to match inbound voice or modem dial peers:
dial-peer no-match disconnect-cause 47Related Commands
dial-peer search type
To optimize voice or data dial-peer searches, use the dial-peer search type command in global configuration mode. To disable the search parameters, use the no form of this command.
dial-peer search type {data voice}|{voice data}|{none}
no dial-peer search type
Syntax Description
data
Searches for data dial peers.
none
Searches for all dial peers by order of input.
voice
Searches for voice dial peers.
Defaults
data and voice
Command Modes
Global configuration
Command History
Usage Guidelines
The search defines the search preference explicitly. If the data and voice keywords are specified, data dial peers are searched first. If no data dial peers are found, the voice dial peers are searched.
Examples
The following is sample output that shows that data dial peers are searched first and then voice dial peers are searched only if no data dial peers can be matched for an incoming call:
dial-peer search type data voiceThe following is sample output that shows that voice dial peers are searched first and then data dial peers are searched only if no voice dial peers can be matched for an incoming call:
dial-peer search type voice dataRelated Commands
dial-peer data
Enable a gateway to process incoming data calls first by assigning the POTS dial peer as data.
dial-peer terminator
To change the character used as a terminator for variable-length dialed numbers, use the dial-peer terminator command in global configuration mode. To restore the default terminating character, use the no form of this command.
dial-peer terminator character
no dial-peer terminator
Syntax Description
character
Designates the terminating character for a variable-length dialed number. Valid numbers and characters are #, *, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, and d. The default is #.
Defaults
The default terminating character is #
Command Modes
Global configuration
Command History
Usage Guidelines
There are certain areas in the world (for example, in certain European countries) where telephone numbers can vary in length. When a dialed-number string has been identified as a variable length dialed-number, the system does not place a call until the configured value for the timeouts interdigits command has expired or until the caller dials the terminating character. Use the dial-peer terminator global configuration command to change the terminating character.
Examples
The following example shows that "9" has been specified as the terminating character for variable-length dialed numbers:
dial-peer terminator 9Related Commands
dial-peer video
To define a video ATM dial peer for a local or remote video codec, to specify video-related encapsulation, and to enter dial-peer configuration mode use the dial-peer video command in global configuration mode. To remove the video dial peer, use the no form of this command.
dial-peer video tag {videocodec | videoatm}
no dial-peer video tag {videocodec | videoatm}
Syntax Description
Defaults
No video dial peer is configured
Command Modes
Global configuration
Command History
12.0(5)XK
This command was introduced for ATM interface configuration on the Cisco MC3810.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0(7)T.
Usage Guidelines
The tag value must be unique to the device.
Examples
On a Cisco MC3810, the following example sets up a local video dial peer designated as 10:
dial-peer video 10 videocodecRelated Commands
dial-peer voice
To define a particular dial peer, to specify the method of voice encapsulation, and to enter dial-peer configuration mode, use the dial-peer voice command in global configuration mode. To delete a defined dial peer, use the no form of this command. Alternately, to disable a dial peer, use the no shutdown command in dial-peer configuration mode.
Cisco 1750 and Cisco 1751 Modular Access Routers and Cisco 2600 Series
dial-peer voice tag {pots | vofr | voip}
no dial-peer voice tag {pots | vofr | voip}
Cisco 2600 Series, Cisco 2600XM, Cisco 3600 Series, Cisco 3700 Series, Cisco IAD2420 Series, and Cisco VG200
dial-peer voice tag {pots | voatm | vofr | voip}
no dial-peer voice tag {pots | voatm | vofr | voip}
Cisco 7200 Series
dial-peer voice tag {vofr}
no dial-peer voice tag {vofr}
Cisco 7204VXR and Cisco 7206VXR
dial-peer voice tag {pots | voatm | vofr | voip}
no dial-peer voice tag {pots | voatm | vofr | voip}
Cisco AS5300
dial-peer voice tag {mmoip | pots | vofr | voip}
no dial-peer voice tag {mmoip | pots | vofr | voip}
Cisco MC3810
dial-peer voice tag {pots | voatm | vofr}
no dial-peer voice tag {pots | voatm | vofr}
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Use the dial-peer voice global configuration command to switch to dial-peer configuration mode from global configuration mode and to define a particular dial peer. Use the exit command to exit dial-peer configuration mode and return to global configuration mode.
After you have created a dial peer, that dial peer remains defined and active until you delete it. To delete a dial peer, use the no form of this command. To disable a dial peer, use the no shutdown command in dial-peer configuration mode.
In store-and-forward fax on the Cisco AS5300, the POTS dial peer defines the inbound faxing line characteristics from the sending fax device to the receiving Cisco AS5300 and the outbound line characteristics from the sending Cisco AS5300 to the receiving fax device. The Multimedia Mail over Internet Protocol (MMoIP) dial peer defines the inbound faxing line characteristics from the Cisco AS5300 to the receiving Simple Mail Transfer Protocol (SMTP) mail server. This command applies to both on-ramp and off-ramp store-and-forward fax functions.
Note
Examples
The following example shows how to access dial-peer configuration mode and configure a POTS peer identified as dial peer 10 and an MMoIP dial peer identified as dial peer 20:
dial-peer voice 10 potsdial-peer voice 20 mmoipThe following example deletes the MMoIP peer identified as dial peer 20:
no dial-peer voice 20 mmoipThe following example shows how the dial-peer voice command is used to configure the extended echo canceller. In this instance, pots indicates that this is a plain old telephone service (POTS) peer using Voice over IP encapsulation on the IP backbone, and it uses the unique numeric identifier tag 133001.
Router(config)# dial-peer voice 133001 potsRelated Commands
dialplan-pattern (cm-fallback)
To create a global prefix that can be used to expand the abbreviated extension numbers (automatically obtained from the Cisco IP phones) into fully qualified E.164 numbers, use the dialplan-pattern command in call-manager-fallback configuration mode. To disable a global prefix, use the no form of this command.
dialplan-pattern tag pattern extension-length length [no-reg]
no dialplan-pattern tag [pattern extension-length length]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
Directory numbers or virtual voice ports for Cisco IP phones are entered in extension-number format. The extension number should be greater than or equal to the extension length. Otherwise, the extension number cannot be converted to a qualified E.164 number. The dialplan-pattern command creates a global prefix that can be used to expand the abbreviated extension numbers to fully qualified E.164 numbers. The dial-plan pattern is also required in order to register the Cisco IP phone lines with a gatekeeper. The dialplan-pattern command can resolve an incoming call into a fully qualified E.164 number.
The extension-length keyword enables the system to convert a full E.164 telephone number back to an extension number for the purposes of caller ID display, received-call, and missed-call lists. For example, a company uses extension number range 5000-5099 across several sites, with only the extensions from 5000 to 5009 present on the local router. An incoming call from 5066 arrives from the company's internal ISDN network and this call includes the calling number as 5553335066 in its full E.164 format.
The no-reg keyword provides dialing flexibility. You have the option not to register some specific numbers to the gatekeeper so that those numbers can be used for other telephony services.
When the called number matches the dial-plan pattern, the call is considered a local call and has a distinctive ring that identifies the call as internal. Any call that does not match the dial-plan pattern is considered an external call and has a ring different from the internal ringing. The valid dial-plan pattern with the lowest tag is used as a prefix to all local Cisco IP phones.
Examples
The following example shows how to create dialplan-pattern 1 for extension numbers from 5001 to 5099, following a telephone prefix that starts with 408555. If the following example is set, the router sees that 5553335066 matches dial-plan pattern 1. It uses the extension-length keyword to extract the last four digits of the number 5066 and to present this as the caller ID for the incoming call.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 55533350.. extension-length 4 no-regRelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters call-manager-fallback configuration mode.
dialplan-pattern (telephony-service)
To create a global prefix that can be used to expand the abbreviated extension numbers into fully qualified E.164 numbers, use the dialplan-pattern command in telephony-service configuration mode. To disable a dialplan-pattern command setting, use the no form of this command.
dialplan-pattern tag pattern extension-length length [extension-pattern extension-pattern] [no-reg]
no dialplan-pattern tag [pattern extension-length length extension-pattern extension-pattern]
Syntax Description
Defaults
No default behavior or values
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
Directory numbers for the Cisco IP phones are entered in extension-number format. The extension number should be greater than or equal to the extension length. Otherwise, the extension number cannot be converted to a qualified E.164 number. The dialplan-pattern command creates a global prefix that can be used to expand the abbreviated extension numbers to fully qualified E.164 numbers. The dial plan pattern is also required in order to register the Cisco IP phone lines with a gatekeeper. The dialplan-pattern command can resolve an incoming call with a full E.164 number to a Cisco IP phone extension number.
The extension-length keyword enables the system to convert a full E.164 telephone number back to an extension number for the purposes of caller ID display, received-call, and missed-call lists. For example, a company uses extension number range 5000-5099 across several sites, with only the extensions from 5000 to 5009 present on the local router.An incoming call from 5044 arrives from the company's internal VoIP H.323 network and this call includes the calling number as 4085555044 in its full E.164 format.
The no-reg keyword provides dialing flexibility. You have the option not to register some specific numbers to the gatekeeper so that those numbers can be used for other telephony services.
When the called number matches the dial-plan pattern, the call is considered a local call and has a distinctive ring that identifies the call as internal. Any call that does not match the dial-plan pattern is considered an external call and has a ring different from the internal ringing. The valid dial-plan pattern with the lowest tag is used as a prefix to all local Cisco IP phones.
The number of extension-pattern characters must match the extension length that is specified in this command. For example, if the extension length is three, then the extension-pattern can be 8.., 1.., 5.., and so forth.
Examples
The following example shows how to create dialplan-pattern 1 for extension numbers 5001 to 5099 with the telephone prefix starting with 555333. If the following example is set, the routers sees that the 5553335066 matches dialplan-pattern 1, and uses the extension-length keyword to extract the last four digits of the number 5066 and present this as the caller ID for the incoming call.
Router(config)# telephony-serviceRouter(config-telephony-service)# dialplan-pattern 1 55533350.. extension-length 4 no-regIn the following example the dialplan-pattern command creates dial-plan pattern 1 for extensions 801 to 899 with the telephone prefix starting with 4085559. As each number in the extension pattern is declared with the number command, two POTs dial peers are created. In the following example, they are 801 (an internal office number) and 408-555-9001 (an external number).
Router(config)# telephony-serviceRouter(config-telephony-service)# dialplan-pattern 1 4085559... extension-length 3 extension-pattern 8..Router(config-telephony-service)# ephone-dn 1Router(config-ephone-dn)# number 801Related Commands
dial-type
To specify the type of out-dialing for voice port interfaces, use the dial-type command in voice-port configuration mode. To disable the selected type of dialing, use the no form of this command.
dial-type {dtmf | pulse | mf}
no dial-type
Syntax Description
dtmf
Dual tone multifrequency (DTMF) touch-tone dialing.
pulse
Pulse (rotary) dialing.
mf
Multifrequency tone dialing.
Defaults
DTMF touch-tone dialing
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use the dial-type command to specify an out-dialing type for a Foreign Exchange Office (FXO) or E&M voice port interface. This command specifies the tone type for digit detection and out-pulsing. This command is not applicable to Foreign Exchange Station (FXS) voice ports because the ports do not generate out-dialing. This command also specifies the detection direction. Multifrequency tone dialing is not supported for FXS and FXO.
Voice ports can always detect DTMF and pulse signals. This command does not affect voice port dialing detection.
The dial-type command affects out-dialing as configured for the dial peer.
The dial-type command is not supported on FXO voice port interfaces on the Cisco MC3810. If you are using the dial-type command with E&M Wink Start signaling, use the dtmf or mf option.
SGCP 1.1+ does not support pulse dialing.
Examples
The following example shows a voice port configured on the Cisco MC3810 to support a rotary (pulse tone) dialer:
Router(config)# voice-port 1/1Router(config-voice-port)# dial-type pulseThe following example shows a voice port configured on the Cisco MC3810 to support a DTMF (touch-tone) dialer:
Router(config)# voice-port 1/1Router(config-voice-port)# dial-type dtmfThe following example shows a voice port configured on the Cisco MC3810 to support a multifrequency tone dialer:
Router(config)# voice-port 1/1Router(config-voice-port)# dial-type mfRelated Commands
sgcp
Starts and allocates resources for the SGCP daemon.
sgcp call-agent
Defines the IP address of the default SGCP call agent.
digit-strip
To enable digit stripping on a plain old telephone service (POTS) dial-peer call leg, use the digit-strip command in dial-peer configuration mode. To disable digit stripping on the dial-peer call leg, use the no form of this command.
digit-strip
no digit-strip
Syntax Description
This command has no arguments or keywords.
Defaults
Digit stripping is enabled.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
The digit-strip command is supported on POTS dial peers only.
When a called number is received and matched to a POTS dial peer, the matched digits are stripped and the remaining digits are forwarded to the voice interface.
Table 17 lists a series of dial peers configured with a specific destination pattern and shows the longest matched number after the digit is stripped based on the dial string 408 555-3048.
Table 18 lists a series of dial peers configured with a specific destination pattern and shows the number after the digit strip based on the dial string 408 555-3048 and the different dial peer symbols applied.
Examples
The following example disables digit stripping on a POTS dial peer:
dial-peer voice 100 potsno digit-stripRelated Commands
direct-inward-dial
To enable the direct inward dialing (DID) call treatment for an incoming called number, use the direct-inward-dial command in dial-peer configuration mode. To disable DID on the dial peer, use the no form of this command.
direct-inward-dial
no direct-inward-dial
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the direct-inward-dial command to enable the DID call treatment for an incoming called number. When this feature is enabled, the incoming call is treated as if the digits were received from the DID trunk. The called number is used to select the outgoing dial peer. No dial tone is presented to the caller.
Use the no form of this command to disable DID on the dial peer. When disabled, the called number is used to select the outgoing dial peer. The caller is prompted for a called number via dial tone.
This command is applicable only to plain old telephone service (POTS) dial peers. This command applies to on-ramp store-and-forward fax functions.
Examples
The following example enables DID call treatment for the incoming called number:
dial-peer voice 10 potsdirect-inward-dialdirectory (telephony-service)
To define the naming order for the local directory all the Cisco IP phone users, use the directory command in telephony-service configuration mode. To delete the naming order of the local directory, use the no form of this command.
directory {first-name-first | last-name-first}
no directory {first-name-first | last-name-first}
Syntax Description
first-name-first
First name is entered first in the Cisco IP phone directory name field.
last-name-first
Last name is entered first in the Cisco IP phone directory name field.
Defaults
first-name-first
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The directory command defines the naming order in the local directory. The actual directory of names and phone numbers is built using the name command and the number command in ephone directory number configuration mode.
When the command is configured with the first-name-first keyword, you see the directory information displayed on the phone, for example, Jane E. Smith. When the command is configured with the last-name-first keyword, you see the directory information displayed on the phone, for example, Smith, Jane E.
Note
Examples
The following example shows how to configure the local directory with the first name first:
Router(config)# telephony-serviceRouter(config-telephony-service)# directory first-name-firstThe following example shows how to configure the local directory with the last name first:
Router(config)# telephony-serviceRouter(config-telephony-service)# directory last-name-firstRelated Commands
disable-early-media 180
To specify which call treatment, early media or local ringback, is provided for 180 responses with 180 responses with Session Description Protocol (SDP), use the disable-early-media 180 command in sip-ua configuration mode. To enable early media cut-through for 180 messages with SDP, use the no form of this command.
disable-early-media 180
no disable-early-media 180
Syntax Description
This command has no arguments or keywords.
Defaults
Early media cut-through for 180 responses with SDP is enabled.
Command Modes
SIP-UA configuration
Command History
Usage Guidelines
This command provides the ability to enable or disable early media cut-through on Cisco IOS gateways for Session Initiation Protocol (SIP) 180 responses with SDP. Use the disable-early-media 180 command to configure the gateway to ignore the SDP message and provide local ringback. To restore the default treatment, early media cut-through, use the no disable-early-media 180 command.
Examples
The following example disables early media cut-through for SIP 180 responses with SDP:
Router(config-sip-ua)# disable-early-media 180Related Commands
disc_pi_off
To enable an H.323 gateway to disconnect a call when it receives a disconnect message with a progress indicator (PI) value, use the disc_pi_off command in voice-port configuration mode. To restore the default state, use the no form of this command.
disc_pi_off
no disc_pi_off
Syntax Description
This command has no arguments or keywords.
Defaults
The gateway does not disconnect a call when it receives a disconnect message with a PI value.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The disc_pi_off voice-port command is valid only if the disconnect with PI is received on the inbound call leg. For example, if this command is enabled on the voice port of the originating gateway, and a disconnect message with PI is received from the terminating switch, the disconnect message is converted to a disconnect message. But if this command is enabled on the voice port of the terminating gateway, and a disconnect message with PI is received from the terminating switch, the disconnect message is not converted to a standard disconnect message because the disconnect message is received on the outbound call leg.
Note
Examples
The following example handles a disconnect message with a PI value in the same way as a standard disconnect message for voice port 0:23:
voice-port 0:Ddisc_pi_offRelated Commands
disconnect-ack
To configure a Foreign Exchange Station (FXS) voice port to return an acknowledgment upon receipt of a disconnect signal, use the disconnect-ack command in voice-port configuration mode. To disable the acknowledgment, use the no form of this command.
disconnect-ack
no disconnect-ack
Syntax Description
This command has no arguments or keywords.
Defaults
FXS voice ports return an acknowledgment upon receipt of a disconnect signal
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The disconnect-ack command configures an FXS voice port to remove line power if the equipment on an FXS loop-start trunk disconnects first.
Examples
The following example, which begins in global configuration mode, turns off the disconnect acknowledgment signal on voice port 1/1 on a Cisco MC3810:
voice-port 1/1no disconnect-ackThe following example, which begins in global configuration mode, turns off the disconnect acknowledgment signal on voice port 1/1/0 on a Cisco 2600 series or Cisco 3600 series router:
voice-port 1/0/0no disconnect-ackCommand History
dnis (DNIS group)
To add a dialed number identification service (DNIS) number to a DNIS map, use the dnis command in DNIS-map configuration mode. To delete a DNIS number, use the no form of this command.
dnis number [url url]
no dnis
Syntax Description
Defaults
If no URL is entered, the DNIS number links to the VoiceXML application that is configured in the dial peer with the application command.
Command Modes
DNIS-map configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
To enter DNIS-map configuration mode for the dnis command, use the voice dnis-map command.
Enter the dnis command once for each telephone number that you want to map to a voice application. A separate entry must be made for each telephone number in a DNIS map. Wildcards are not supported.
URLs in DNIS entries are used only by VoiceXML applications. When an incoming called number matches a DNIS entry, it loads the VoiceXML document that is specified by the URL, provided that a VoiceXML application is configured in the dial peer using the application command.
Non-VoiceXML applications, such as TCL applications, ignore the URLs in DNIS maps and link a call to the TCL application that is configured in the dial peer using the application command.
For a DNIS map to be applied to an outbound dial peer, a VoiceXML application must be configured by using the application command with the out-bound keyword. Otherwise, the call is not handed off to the application that is specified in the URL of the DNIS map.
The number of allowable DNIS entries is limited by the amount of available configuration memory on the gateway. As a guideline, DNIS maps that contain more than several hundred DNIS entries should be maintained in an external text file.
To associate a DNIS map with a dial peer, use the dnis-map command.
Examples
The first line in the following example shows how the voice dnis-map command is used to create a DNIS map named "dmap1". The last two lines show how the dnis command is used to enter DNIS entries.
The first DNIS entry specifies the location of a VoiceXML document. The second DNIS entry does not specify a URL. A DNIS number without a URL is, by default, matched to the URL of the application that is configured in the dial peer by using the application command.
voice dnis-map dmap1dnis 5553305 url tftp://blue/sky/test.vxmldnis 5558888Related Commands
dnis-map
To associate a dialed number identification service (DNIS) map with a dial peer, use the dnis-map command in dial-peer configuration mode. To remove a DNIS map from the dial peer, use the no form of this command.
dnis-map map-name
no dnis-map
Syntax Description
Defaults
No default behavior or values
Command Modes
Dial-peer configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
A DNIS map is a table of destination numbers with optional URLs that link to specific VoiceXML documents. When configured in a dial peer, a DNIS map enables you to link multiple called numbers to a single Tool Command Language (TCL) application or to individual VoiceXML documents.
The dnis-map command must be used with the application command.
Only one DNIS map can be configured in each dial peer.
To create a DNIS map, use the voice dnis-map command to enter DNIS-map configuration mode, and then use the dnis command to add entries to the DNIS map. Or you can create an external text file of DNIS entries and link to its URL by using the voice dnis-map command.
To view the configuration information for DNIS maps, use the show voice dnis-map command.
A URL configured for a DNIS number is ignored by a TCL application; the TCL script that is configured for the application is used instead.
Note
Examples
In the following example the DNIS map named "dmap1" is associated with the VoIP dial peer 3. The outbound application "vapptest1" is associated through this dial peer with DNIS map "dmap1".
dial-peer voice 3 voipdnis-map dmap1application vapptest1 outboundRelated Commands
dn-webedit (telephony-service)
To enable adding of directory numbers through a web interface, use the dn-webedit command in telephony-service configuration mode. To disable this feature, use the no form of this command.
dn-webedit
no dn-edit
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The dn-webedit command enables adding of the directory through the Cisco IOS Telephony Service web-based graphical user interface (GUI). If the dn-webedit command is enabled, the GUI administrator can modify and assign the phone numbers associated with the Cisco IOS Telephony Service router.
If the set of numbers used by the Cisco IOS Telephony Service router are part of a larger telephone network, limitations on modification might be needed to ensure network integrity. Disabling dn-webedit prevents the administrator from allocating phone numbers and also prevents assignment of numbers that may already be used elsewhere in the network.
Examples
The following example shows how to enable editing of directory numbers through the web-based GUI interface:
Router(config)# telephony-serviceRouter(config-telephony-service)# dn-webeditRelated Commands
domain-name (annex G)
To set the domain name that is reported in service relationships, use the domain-name command in annex G neighbor configuration mode. To remove the domain name, use the no form of this command.
domain-name id
no domain-name id
Syntax Description
Command Modes
Annex G neighbor configuration mode
Defaults
No default behavior or values
Command History
Usage Guidelines
Use this command to set the domain name reported that is reported in service relationships.
Examples
The following example shows how to set a domain name to "boston1":
Router(config-annexg-neigh)# domain-name boston1Related Commands
ds0 busyout (voice)
To force a DS0 time slot on a controller into the busyout state, use the ds0 busyout command in controller configuration mode. To remove the DS0 time slot from the busyout state, use the no form of this command.
ds0 busyout ds0-time-slot
no ds0 busyout ds0-time-slot
Syntax Description
ds0-time-slot
DS0 time slots to be forced into the busyout state. Range is from 1 to 24 and can include any combination of time slots.
Defaults
DS0 time slots are not in busyout state.
Command Modes
Controller configuration
Command History
12.0(7)XK
This command was introduced on Cisco MC3810 and Cisco 2600 series and Cisco 3600 series.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
Usage Guidelines
The ds0 busyout command affects only DS0 time slots that are configured into a DS0 group and that function as part of a digital voice port. If multiple DS0 groups are configured on a controller, any combination of DS0 time slots can be busied out, provided that each DS0 time slot to be busied out is part of a DS0 group.
If a DS0 time slot is in the busyout state, only the no ds0 busyout command can restore the DS0 time slot to service.
To avoid conflicting command-line interface (CLI) commands, do not use the ds0 busyout command and the busyout forced command on the same controller.
Examples
The following example configures DS0 time slot 6 on controller T1 0 to be forced into the busyout state:
controller t1 0ds0 busyout 6The following example configures DS0 time slots 1, 3, 4, 5, 6, and 24 on controller E1 1 to be forced into the busyout state:
controller e1 1ds0 busyout 1,3-6,24Related Commands
busyout seize
Changes the busyout seize procedure for a voice port.
show running configuration
Determines which DS0 time slots have been forced into the busyout state.
ds0-group (E1)
To specify the DS0 time slots that make up a logical voice port on an E1 controller, specify the signaling type by which the router communicates with the PBX or PSTN, and define E1 channels for compressed voice calls and the channel-associated signaling (CAS) method by which the router connects to the PBX or PSTN, use the ds0-group command in controller configuration mode. To remove the group and signaling setting, use the no form of this command.
Cisco 1750 and Cisco 1751
ds0-group ds0-group-number timeslots timeslot-list [service service-type] [type {e&m-fgb | e&m-fgd | e&m-immediate-start | fgd-eana | fgd-os | fxs-ground-start | fxs-loop-start | none | r1-itu | r1-modified | r1-turkey | sas-ground-start | sas-loop-start}]
no ds0-group ds0-group-number
Cisco 2600 Series, Cisco 3600, Cisco 3725, and Cisco 3745
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-immediate-start | e&m-melcas-delay | e&m-melcas-immed | e&m-melcas-wink | e&m-wink-start | ext-sig | fgd-eana | fxo-ground-start | fxo-loop-start | fxo-melcas | fxs-ground-start | fxs-loop-start | fxs-melcas | r2-analog | r2-digital | r2-pulse}
no ds0-group ds0-group-number
Cisco MC3810
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-immediate-start | e&m-melcas-delay | e&m-melcas-immed | e&m-melcas-wink | e&m-wink-start | ext-sig | fgd-eana | fxo-ground-start | fxo-loop-start | fxo-melcas | fxs-ground-start | fxs-loop-start | fxs-melcas}
no ds0-group ds0-group-number
Cisco 7200 Series and Cisco 7500 Series Voice Ports
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-fgd | e&m-immediate-start | e&m-wink-start | fxs-ground-start | fxs-loop-start | fxo-ground-start | fxo-loop-start}
no dso-group ds0-group-number
Cisco 7700 Series Voice Ports
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-immediate-start | e&m-wink-start | fxs-ground-start | fxs-loop-start | fxo-ground-start | fxo-loop-start}
no ds0-group ds0-group-number
Cisco AS5300 and the Cisco AS5400
ds0-group ds0-group-number timeslots timeslot-list type {none | p7 | r2-analog | r2-digital | r2-lsv181-digital | r2-pulse}
no ds0-group ds0-group-number
Cisco AS5800 Voice Ports
ds0-group ds0-group-number timeslots timeslot-list type {e&m-fgb | e&m-fgd | e&m-immediate-start | fxs-ground-start | fxs-loop-start | p7 | r2-analog | r2-digital | r2-pulse | sas-ground-start | sas-loop-start | none}
no ds0-group ds0-group-number
Note
Syntax Description
Defaults
There is no DS0 group. Calls are allowed in both directions.
Command Modes
Controller configuration
Command History
Usage Guidelines
The ds0-group command automatically creates a logical voice port that is numbered as follows:
•
–
•
–
Note
Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Be sure you take the following into account when you are configuring DS0 groups:
•
•
http://www.cisco.com/go/fn•
Examples
The following example shows ranges of E1 controller time slots configured for FXS ground-start and FXO loop-start signaling on a Cisco 2600 series, Cisco 2600XM, Cisco 3660, Cisco 3725, or Cisco 3745:
E1 1/0framing esflinecode b8zsds0-group 1 timeslots 1-14 type fxs-ground-startds0-group 2 timeslots 16-30 type fxo-loop-startThe following example shows DS0 groups 1 and 2 on controller E1 1 configured on the Cisco MC3810 to support transparent CCS:
controller E1 1mode ccs cross-connectds0-group 1 timeslots 1-14 type ext-sigds0-group 2 timeslots 16-30 type ext-sigThe following example shows how to configure ranges of E1 controller time slots for FXS ground-start signaling:
controller E1 1/0ds0-group 1 timeslots 1-4 type fxs-ground-startThe following example illustrates setting the E1 channels for SS7 service on any trunking gateway in mgcp mode:
Router(config-controller)# ds0-group 0 timeslots 1-24 type none service mgcpIn the following example, the time slot maximum is 12 and the time slot is 1, so two voice-ports are created successfully.
controller E1 0/0ds0-group 0 timeslots 1-4 type e&m-immediate-startds0-group 1 timeslots 6-12 type e&m-immediate-startIf a third DS0 group is added, the voice-port is rejected even though the total number of voice channels is less than 16.
ds0-group 2 timeslots 17-18 type e&m-immediate-startRelated Commands
ds0-group (T1)
To specify the DS0 time slots that make up a logical voice port on a T1 controller, specify the signaling type by which the router communicates with the PBX or PSTN, and define T1 channels for compressed voice calls and the channel-associated signaling (CAS) method by which the router connects to the PBX or PSTN, use the ds0-group command in controller configuration mode. To remove the group and signaling setting, use the no form of this command.
Cisco 1750 and Cisco 1751
ds0-group ds0-group-number timeslots timeslot-list [service service-type] [type {e&m-fgb | e&m-fgd | e&m-immediate-start | fgd-eana | fgd-os | fxs-ground-start | fxs-loop-start | none | r1-itu | r1-modified | r1-turkey | sas-ground-start | sas-loop-start}]
no ds0-group ds0-group-number
Cisco 2600 Series, Cisco 3600, Cisco 3725, Cisco 3745, and the Cisco MC3810
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-fgd | e&m-immediate-start | e&m-wink-start | ext-sig | fgd-eana | fxo-ground-start | fxo-loop-start | fxs-ground-start | fxs-loop-start}
Cisco 7200 Series and Cisco 7500 Series Voice Ports
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-fgd | e&m-immediate-start | e&m-wink-start | fxs-ground-start | fxs-loop-start | fxo-ground-start | fxo-loop-start}
no dso-group ds0-group-number
Cisco 7700 Series Voice Ports
ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-immediate-start | e&m-wink-start | fxs-ground-start | fxs-loop-start | fxo-ground-start | fxo-loop-start}
no ds0-group ds0-group-number
Cisco AS5300 and Cisco AS5400
ds0-group ds0-group-number timeslots timeslot-list [service service-type] [type {e&m-fgb | e&m-fgd | e&m-immediate-start | fxs-ground-start | fxs-loop-start | fgd-eana | fgd-os | r1-itu | sas-ground-start | sas-loop-start | none}] [tone type] [addr info]
no ds0-group ds0-group-number
Cisco AS5800
ds0-group ds0-group-number timeslots timeslot-list type {e&m-fgb | e&m-fgd | e&m-immediate-start | fxs-ground-start | fxs-loop-start | fgd-eana | r1-itu | r1-modified | r1-turkey | sas-ground-start | sas-loop-start | none}
no ds0-group ds0-group-number
Note
Syntax Description
Defaults
There is no DS0 group. Calls are allowed in both directions.
Command Modes
Controller configuration
Command History
Usage Guidelines
The ds0-group command automatically creates a logical voice port that is numbered as follows:
•
–
•
–
Note
•
–
Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Be sure you take the following into account when you are configuring DS0 groups:
•
•
http://www.cisco.com/go/fn•
Examples
The following example shows ranges of T1 controller time slots configured for FXS ground-start and FXO loop-start signaling on a Cisco 2600 series, Cisco 2600XM, Cisco 3660, Cisco 3725, or Cisco 3745:
T1 1/0framing esflinecode b8zsds0-group 1 timeslots 1-10 type fxs-ground-startds0-group 2 timeslots 11-24 type fxo-loop-startThe following example shows DS0 groups 1 and 2 on controller T1 1 configured on the Cisco MC3810 to support transparent CCS:
controller T1 1mode ccs cross-connectds0-group 1 timeslots 1-10 type ext-sigds0-group 2 timeslots 11-24 type ext-sigThe following example shows how to configure ranges of T1 controller time slots for FXS ground-start signaling:
controller T1 1/0ds0-group 1 timeslots 1-4 type fxs-ground-startThe following example illustrates setting the T1 channels for SS7 service on any trunking gateway in mgcp mode:
Router(config-controller)# ds0-group 0 timeslots 1-24 type none service mgcpIn the following example, the time slot maximum is 12 and the time slot is 1, so two voice-ports are created successfully.
controller T1 0/0ds0-group 0 timeslots 1-4 type e&m-immediate-startds0-group 1 timeslots 6-12 type e&m-immediate-startIf a third DS0 group is added, the voice-port is rejected even though the total number of voice channels is less than 16.
ds0-group 2 timeslots 17-18 type e&m-immediate-startRelated Commands
dsn
To specify that a delivery status notice (DSN) be delivered to the sender, use the dsn command in dial-peer configuration mode. To cancel a specific DSN option, use the no form of this command.
dsn {delay | failure | success}
no dsn {delay | failure | success}
Syntax Description
Note
Defaults
The default is to send a nondelivery message in the event of a failure
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
When the delay keyword is selected, the next-hop mailer sends a message to the FROM address saying that the mail message was delayed. The definition of the delay keyword is made by each mailer and is not controlled by the sender. Each mailer in the path to the recipient that supports the DSN extension receives the same request.
When the failure keyword is selected, the next-hop mailer sends a message to the FROM address that the mail message delivery failed. Each mailer in the path to the recipient that supports the DSN extension receives the same request.
When the success keyword is selected, the next-hop mailer sends a message to the FROM address saying that the mail message was successfully delivered to the recipient. Each mailer in the path to the recipient that supports the DSN extension receives the same request.
This command is applicable to Multimedia Mail over Internet Protocol (MMoIP) dial peers.
DSNs are messages or responses that are automatically generated and sent to the sender or originator of an e-mail message by the Simple Mail Transfer Protocol (SMTP) server, notifying the sender of the status of the e-mail message. Specifications for DSN are described in RFC 1891, RFC 1892, RFC 1893, and RFC 1894.
The on-ramp DSN request is included as part of the fax-mail message sent by the on-ramp gateway when the matching MMoIP dial peer has been configured. The on-ramp DSN response is generated by the SMTP server when the fax-mail message is accepted. The DSN is sent back to the user defined by the mta send mail-from command. The off-ramp DSN is requested by the e-mail client. The DSN response is generated by the SMTP server when it receives a request as part of the fax-mail message.
Note
Because the SMTP server generates the DSNs, you need to configure both mail from: and rcpt to: on the server for the DSN feature to work. For example:
mail from: <user@mail-server.company.com>rcpt to: <fax=555-1212@company.com> NOTIFY=SUCCESS,FAILURE,DELAYThere are three different states that can be reported back to the sender:
•
•
•
Because these delivery states are not mutually exclusive, you can configure store-and-forward fax to generate these messages for all or any combination of these events.
DSN messages notify the sender of the status of a particular e-mail message that contains a fax TIFF image. Use the dsn command to specify which notification messages are sent to the user.
The dsn command allows you to select more than one notification option by reissuing the command and specifying a different notification option each time. To discontinue a specific notification option, use the no form of the command for that specific keyword.
If the failure keyword is not included when DSN is configured, the sender receives no notification of message delivery failure. Because a failure is usually significant, care should be taken to always include the failure keyword as part of the dsn command configuration.
This command applies to on-ramp store-and-forward fax functions.
Examples
The following example specifies that a DSN message be returned to the sender when the e-mail message that contains the fax has been successfully delivered to the recipient or if the message that contains the fax has failed to be delivered:
dial-peer voice 10 mmoipdsn successdsn failureRelated Commands
dsp services dspfarm
To configure digital-signal-processor (DSP) farm services for a particular digital T1/E1 packet voice trunk network module (NM-HDV) or high-density voice (HDV) transcoding/conferencing DSP farm (NM-HDV-FARM), use the dsp services dspfarm command in interface configuration mode. To disable services, use the no form of this command.
dsp services dspfarm
no dsp services dspfarm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Voice-card configuration
Command History
12.2(13)T
This command was introduced on the Cisco VG200, Cisco 2600 series, Cisco 3620, Cisco 3640, Cisco 3660, and Cisco 3700 series.
Usage Guidelines
The router on which this command is used must be equipped with one or more NM-HDVs or NM-HDV-FARMs to provide DSP resources.
The number of NM-HDVs or NM-HDV-FARMs that need to be enabled for DSP-farm services depends on the number of DSPs on the NM-HDV or NM-HDV-FARM and on the maximum number of transcoding and conferencing sessions configured on the DSP farm. DSP resources on an NM-HDV or NM-HDV-FARM are used only if this command is configured under that particular card.
Use this command before enabling DSP-farm services with the dspfarm command.
Examples
The following example configures an NM-HDV or NM-HDV-FARM, specifies the maximum number of transcoding sessions, and enables DSP-farm services:
Router# configure terminalRouter(config)# no dspfarmRouter(config)# voice-card 2Router(config-voicecard)# dsp services dspfarmRouter(config-voicecard)# exitRouter(config)# dspfarm transcoder maximum sessions 15Router(config)# dspfarmRelated Commands
dspfarm (DSP farm)
To enable digital-signal-processor (DSP) farm service, use the dspfarm command in global configuration mode. To disable the service, use the no form of this command.
dspfarm
no dspfarm
Syntax Description
This command has no arguments or keywords.
Defaults
DSP-farm service is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide DSP resources.
Before enabling DSP-farm services, you must configure the NM-HDV or NM-HDV-FARM on which DSP-farm services are to be enabled using the dsp service dspfarm command. You must also specify the maximum number of transcoding sessions to be supported by the DSP farm using the dspfarm transcoder maximum sessions command.
This command causes the system to download new firmware into the DSPs, start up the required subsystems, and wait for a service request from the transcoding and conferencing applications.
Examples
The following example configures an NM-HDV or NM-HDV-FARM, specifies the maximum number of transcoding sessions, and enables DSP-farm services:
Router# configure terminalRouter(config)# no dspfarmRouter(config)# voice-card 2Router(config-voicecard)# dsp services dspfarmRouter(config-voicecard)# exitRouter(config)# dspfarm transcoder maximum sessions 15Router(config)# dspfarmRelated Commands
dspfarm (voice-card)
To add a specified voice card to those participating in a digital signal processor (DSP) resource pool, use the dspfarm command in voice-card configuration mode. To remove the specified card from participation in the DSP resource pool, use the no form of this command.
dspfarm
no dspfarm
Syntax Description
This command has no arguments or keywords.
Defaults
A card participates in the DSP resource pool
Command Modes
Voice-card configuration
Command History
Usage Guidelines
DSP mapping occurs when DSP resources on one AIM or network module are available for processing of voice time-division multiplexing (TDM) streams on a different network module or on a voice/WAN interface card (VWIC). This command is used on Cisco 3660 routers with multiservice interchange (MIX) modules installed or on Cisco 2600 series routers with AIMs installed.
To reach voice-card configuration mode for a particular voice card, from global configuration mode enter the voice-card command and the slot number for the AIM or network module that you want to add to the pool. See the voice-card command reference for details on slot numbering.
The assignment of DSP pool resources to particular TDM streams is based on the order in which the streams are configured with the ds0-group command for T1/E1 channel-associated signaling (CAS) or with the pri-group command for ISDN PRI.
The assignment of DSP pool resources does not occur dynamically during call signaling.
Examples
The following example adds to the DSP resource map the DSP resources on the network module in slot 5 on a Cisco 3660 with a MIX module:
voice-card 5dspfarmThe following example makes available the DSP resources on an AIM on a Cisco 2600 series router:
voice-card 0dspfarmRelated Commands
dspfarm confbridge maximum sessions
To specify the maximum number of concurrent conference sessions for which digital-signal-processor (DSP) farm resources should be allocated, use the dspfarm confbridge maximum sessions command in global configuration mode. To reset to the default, use the no form of this command.
dspfarm confbridge maximum sessions number
no dspfarm confbridge maximum sessions
Syntax Description
number
Number of conference sessions. A single DSP supports 1 conference session with up to 6 participants.
Defaults
0 sessions
Command Modes
Global configuration
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide DSP resources.
Before using this command, you must disable DSP-farm service using the no dspfarm command.
The maximum number of conference sessions depends upon DSP availability in the DSP farm. A single DSP supports one conference session with up to six participants. However, you may need to allocate additional DSP resources for transcoding to support conferences. If all participants use G.711 or G.729 codecs, you need not allocate any additional DSP resources because transcoding is done in the conferencing DSP.
When you use this command, take into consideration the number of DSPs allocated for transcoding services with the dspfarm transcoder maximum sessions command.
Examples
The following example sets the maximum number of conferencing sessions to 8:
Router# dspfarm confbridge maximum sessions 8Related CommandsT
dspfarm connection interval
To specify the time interval during which to monitor Real-Time Transport Protocol (RTP) inactivity before deleting an RTP stream, use the dspfarm connection interval command in global configuration mode. To reset to the default, use the no form of this command.
dspfarm connection interval seconds
no dspfarm connection interval
Syntax Description
seconds
Interval, in seconds, during which to monitor RTP inactivity. Range is from 60 to 10800. Default is 600.
Defaults
600 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide digital-signal-processor (DSP) resources.
After each interval, RTP streams are checked for inactivity. If all RTP streams for a particular call are inactive, the RTP timer, as set with the dspfarm rtp timeout command, is started. When the RTP timer expires, the call is deleted.
Examples
The following example sets the connection interval to 60 seconds:
Router(config)# dspfarm connection interval 60Related Commands
dspfarm rtp timeout
To specify the Real-Time Transport Protocol (RTP) timeout interval used to clear hanging connections, use the dspfarm rtp timeout command in global configuration mode. To reset to the default, use the no form of this command.
dspfarm rtp timeout seconds
no dspfarm rtp timeout
Syntax Description
Defaults
1200 seconds (20 minutes)
Command Modes
Global configuration
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide digital-signal-processor (DSP) resources.
Use this command to set the RTP timeout interval for when the error condition "RTP port unreachable" occurs.
Examples
The following example sets the RTP timeout value to 600 seconds (10 minutes):
Router# dspfarm rtp timeout 600Related Commands
dspfarm transcoder maximum sessions
To specify the maximum number of transcoding sessions to be supported by the digital-signal-processor (DSP) farm, use the dspfarm transcoder maximum sessions command in global configuration mode. To reset to the default, use the no form of this command.
dspfarm transcoder maximum sessions number
no dspfarm transcoder maximum sessions
Syntax Description
Defaults
0 sessions
Command Modes
Global configuration
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide DSP resources.
Before using this command, you must disable DSP-farm service using the no dspfarm command.
Use this command in conjunction with the dspfarm confbridge maximum sessions commands.
The maximum number of transcoding sessions depends upon DSP availability in the DSP farm. A single DSP supports four transcoding sessions transmission to and from G.711 and G.729 codecs.
Examples
The following example configures an NM-HDV or NM-HDV-FARM, specifies the maximum number of transcoding sessions, and enables DSP-farm services:
Router# configure terminalRouter(config)# no dspfarmRouter(config)# voice-card 2Router(config-voicecard)# dsp services dspfarmRouter(config-voicecard)# exitRouter(config)# dspfarm transcoder maximum sessions 15Router(config)# dspfarmRelated Commands
dspint dspfarm
To enable the digital signal processor (DSP) interface, use the dspint dspfarm command in global configuration mode. This command does not have a no form.
dspint dspfarm slot/port
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
DSP mapping occurs when DSP resources on one advanced interface module (AIM) or network module are available for processing of voice time-division multiplexing (TDM) streams on a different network module or on a voice/WAN interface card (VWIC). This command is used on Cisco 3660 routers with multiservice interchange (MIX) modules installed or on Cisco 2600 series routers with AIMs installed.
To reach voice-card configuration mode for a particular voice card, from global configuration mode enter the voice-card command and the slot number for the AIM or network module that you want to add to the pool. See the voice-card command reference for details on slot numbering.
The assignment of DSP pool resources to particular TDM streams is based on the order in which the streams are configured using the ds0-group command for T1/E1 channel-associated signaling (CAS) or using the pri-group command for ISDN PRI.
The assignment of DSP pool resources does not occur dynamically during call signaling.
To disable the interface use the no shutdown command.
Examples
The following example creates a DSP farm interface with a slot number of 1 and a port number of 0.
dspint dspfarm 1/0To change codec complexity on the Cisco 7200 series, you must enter the following commands:
Router# configure terminalRouter(config)# dspint dspfarm 2/0Router(config-dspfarm)# codec medium | high ecan-extendedRelated Commands
dial-peer voice
Specifies the method of voice-related encapsulation.
rtp payload-type
Chooses the type of payload in the RTP NTE packet.
dtmf timer inter-digit
To configure the dual tone multifrequency (DTMF) interdigit timer for a DS0 group, use the dtmf timer inter-digit command in T1 controller configuration mode. To restore the timer to its default value, use the no form of this command.
dtmf timer inter-digit milliseconds
no dtmf timer inter-digit
Syntax Description
milliseconds
DTMF interdigit timer duration, in milliseconds. Range is from 250 to 3000. The default is 3000.
Defaults
3000 milliseconds
Command Modes
T1 controller configuration
Command History
Usage Guidelines
Use the dtmf timer inter-digit command to specify the duration in milliseconds the router waits to detect the end of DTMF digits. After this period, the router expects no more digits to arrive and establishes the call.
Examples
The following example, beginning in global configuration mode, sets the DTMF interdigit timer value to 250 milliseconds:
controller T1 2ds0-group 2 timeslots 4-10 type e&m-fgb dtmf dniscas-custom 2dtmf timer inter-digit 250Related Commands
dtmf-relay (Voice over Frame Relay)
To enable the generation of FRF.11 Annex A frames for a dial peer, use the dtmf-relay command in dial-peer configuration mode. To disable the generation of FRF.11 Annex A frames and return to the default handling of dial digits, use the no form of this command.
dtmf-relay
no dtmf-relay
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command applies to all Voice over Frame Relay (VoFR) and Voice over ATM (VoATM) applications on the Cisco MC3810 multiservice concentrator and to VoFR applications on the Cisco 2600 series routers and 3600 series routers.
Cisco recommends that this command be used with low bit-rate codecs.
When dtmf-relay (VoFR) is enabled, the digital signal processor (DSP) generates Annex A frames instead of passing a dual tone multifrequency (DTMF) tone through the network as a voice sample. For information about the payload format of FRF.11 Annex A frames, refer to the Cisco IOS Wide-Area Networking Configuration Guide and Cisco IOS Wide-Area Networking Command Reference, Release 12.2.
Examples
The following example shows how to enable FRF.11 Annex A frames on a Cisco 2600 series routers or 3600 series router or on an MC3810 multiservice concentrator for VoFR dial peer 200, starting from global configuration mode:
dial-peer voice 200 vofrdtmf-relayRelated Commands
dtmf-relay (Voice over IP)
To specify how an H.323 or Session Initiation Protocol (SIP) gateway relays dual tone multifrequency (DTMF) tones between telephony interfaces and an IP network, use the dtmf-relay command in dial-peer configuration mode. To remove all signaling options and send the DTMF tones as part of the audio stream, use the no form of this command.
dtmf-relay [cisco-rtp] [h245-alphanumeric] [h245-signal] [rtp-nte]
no dtmf-relay [cisco-rtp] [h245-alphanumeric] [h245-signal] [rtp-nte]
Syntax Description
Defaults
Disables DTMF tones are sent inband that is, left in the audio stream.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
DTMF is the tone generated when you press a button on a touch-tone phone. This tone is compressed at one end of a call; when the tone is decompressed at the other end, it can become distorted, depending on the codec used. The DTMF relay feature transports DTMF tones generated after call establishment out of band using either a standard H.323 out-of-band method and a proprietary RTP-based mechanism or for Session Initiation Protocol (SIP) calls, a Named Telephony Events (NTE) Real-time Transport Protocol (RTP) packet.
The gateway only sends DTMF tones in the format you specify if the remote device supports it. If the remote device supports multiple formats, the gateway chooses the format according to the following priority:
1.
2.
3.
4.
5.
The principal advantage of the dtmf-relay command is that it sends DTMF tones with greater fidelity than is possible in-band for most low-bandwidth codecs, such as G.729 and G.723. Without the use of DTMF relay, calls established with low-bandwidth codecs may have trouble accessing automated DTMF-based systems, such as voice mail, menu-based Automatic Call Distributor (ACD) systems, and automated banking systems.
Note
•
•
Examples
The following example configures DTMF relay with the cisco-rtp keyword when sending DTMF tones to dial peer 103:
dial-peer voice 103 voipdtmf-relay cisco-rtpThe following example configures DTMF relay with the cisco-rtp or h245-signal keywords when DTMF tones are sent to dial peer 103:
dial-peer voice 103 voipdtmf-relay cisco-rtp h245-signalThe following example configures the gateway to send DTMF in-band (the default) when DTMF tones to are sent dial peer 103:
dial-peer voice 103 voipno dtmf-relayThe following example shows use of the dtmf-relay command with the SIP NTE DTMF relay feature:
Router(config-dial-peer)# dtmf-relay rtp-ntedualtone
To enter the cp-dualtone configuration mode for specifying a custom call-progress tone, use the dualtone command in custom-cptone voice-class configuration mode. To configure the custom-cptone voice class not to detect a call-progress tone, use the no form of this command.
dualtone {ringback | busy | reorder | out-of-service | number-unobtainable | disconnect}
no dualtone {ringback | busy | reorder | out-of-service | number-unobtainable | disconnect}
Syntax Description
ringback
Ringback tone.
busy
Busy tone.
reorder
Reorder tone.
out-of-service
Out-of-service tone.
number-unobtainable
Number-unavailable tone.
disconnect
Disconnect tone.
Defaults
No call-progress tones are defined within the custom-cptone voice class
Command Modes
Custom-cptone voice-class configuration
Command History
Usage Guidelines
The dualtone command enters the cp-dualtone configuration mode and specifies a call-progress tone to be detected. You can specify additional call-progress tones without exiting cp-dualtone configuration mode.
Any call-progress tones that are not specified are not detected.
To delete a call-progress tone from this custom-cptone voice class, use the no form of this command and the keyword for the tone that should not be detected; for example, no dualtone busy.
You need to associate the class of custom call-progress tones with a voice port for this command to affect tone detection.
Examples
The following example enters cp-dualtone configuration mode and specifies busy tone and ringback tone in the custom-cptone voice class country-x.
voice class custom-cptone country-xdualtone busyfrequency 440 480cadence 500 500dualtone ringbackfrequency 400 440cadence 2000 4000The following example deletes ringback tone from the custom-cptone voice class country-x.
voice class custom-cptone country-xno dualtone ringbackRelated Commands
