Table Of Contents
voice class h323
voice-class h323 (dial peer)
voice class permanent
voice-class permanent (dial peer)
voice-class permanent (voice-port)
voice-class sip e911
voice-class sip localhost
voice-class sip outbound-proxy
voice-class sip rel1xx
voice-class sip resource priority mode (dial peer)
voice-class sip resource priority namespace (dial peer)
voice-class sip transport switch
voice-class sip url
voice class tone-signal
voice-class tone-signal
voice confirmation-tone
voice dnis-map
voice class uri
voice class uri sip preference
voice dnis-map load
voice dsp crash-dump
voice echo-canceller extended
voice enum-match-table
voice hpi capture
voice hunt
voice iec syslog
voice local-bypass
voicemail (stcapp-fsd)
voiceport
voice-port
voice-port (MGCP profile)
voice-port busyout
voice rtp send-recv
voice service
voice source-group
voice statistics accounting method
voice statistics display-format separator
voice statistics field-params
voice statistics max-storage-duration
voice statistics push
voice statistics time-range
voice statistics type csr
voice statistics type iec
voice translation-profile
voice translation-rule
voice vad-time
voice vrf
voip-incoming translation-profile
voip-incoming translation-rule
volume
vxml audioerror
vxml tree memory
vxml version 2.0
voice class h323
To create an H.323 voice class that is independent of a dial peer and can be used on multiple dial peers, use the voice class h323 command in global configuration mode. To remove the voice class, use the no form of this command.
voice class h323 tag
no voice class h323
Syntax Description
tag
|
Unique number to identify the voice class. Range is from 1 to 10000. There is no default value.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.1(2)T
|
This command was introduced on the Cisco 1700, Cisco 2600 series, Cisco 3600 series, Cisco 7200, Cisco AS5300, Cisco uBR910, and Cisco uBR924.
|
Usage Guidelines
The voice class h323 command in global configuration mode does not include a hyphen. The voice-class h323 command in dial peer configuration mode includes a hyphen.
Examples
The following example demonstrates how a voice class is created and applied to an individual dial peer. Voice class 4 contains a command to disable the capability to detect Cisco CallManager systems in the network (this command is used by Cisco CallManager Express 3.1 and later versions). The example then uses the voice-class h323 command to apply voice class 4 to dial peer 36.
Router(config)# voice class h323 4
Router(config-class)# no telephony-service ccm-compatible
Router(config-class)# exit
Router(config)# dial-peer voice 36 voip
Router(config-dial-peer)# destination-pattern 555....
Router(config-dial-peer)# session target ipv4:10.5.6.7
Router(config-dial-peer)# voice-class h323 4
Related Commands
Command
|
Description
|
voice-class h323
|
Assigns an H.323 voice class to a VoIP dial peer.
|
voice-class h323 (dial peer)
To assign an H.323 voice class to a VoIP dial peer, use the voice-class h323 command in dial peer configuration mode. To remove the voice class from the dial peer, use the no form of this command.
voice-class h323 tag
no voice-class h323 tag
Syntax Description
tag
|
Unique number to identify the voice class. Range is from 1 to 10000.
|
Command Default
The dial peer does not use an H.323 voice class.
Command Modes
Dial peer configuration
Command History
Release
|
Modification
|
12.1(2)T
|
This command was introduced.
|
Usage Guidelines
The voice class that you assign to the dial peer must be configured using the voice class h323 in global configuration mode.
You can assign one voice class to each VoIP dial peer. If you assign another voice class to a dial peer, the last voice class assigned replaces the previous voice class.
The voice-class h323 command in dial peer configuration mode includes a hyphen and in global configuration mode does not include a hyphen.
Examples
The following example demonstrates how a voice class is created and applied to an individual dial peer. Voice class 4 contains a command to disable the capability to detect Cisco CallManager systems in the network (this command is used by Cisco CallManager Express 3.1 and later versions). The example then uses the voice-class h323 command to apply voice class 4 to dial peer 36.
Router(config)# voice class h323 4
Router(config-class)# no telephony-service ccm-compatible
Router(config-class)# exit
Router(config)# dial-peer voice 36 voip
Router(config-dial-peer)# destination-pattern 555....
Router(config-dial-peer)# session target ipv4:10.5.6.7
Router(config-dial-peer)# voice-class h323 4
Related Commands
Command
|
Description
|
show dial-peer voice
|
Displays the configuration for all dial peers configured on the router.
|
voice class h323
|
Enters voice-class configuration mode and assigns an identification tag number for an H.323 voice class.
|
voice class permanent
To create a voice class for a Cisco trunk or FRF.11 trunk, use the voice class permanent command in global configuration mode. To delete the voice class, use the no form of this command.
voice class permanent tag
no voice class permanent tag
Syntax Description
tag
|
Unique number that you assign to the voice class. Range is from 1 to 10000.
|
Command Default
No voice class is configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(3)XG
|
This command was introduced on the Cisco MC3810.
|
12.0(4)T
|
This command was integrated into Cisco IOS Release 12.0(4)T.
|
12.1(3)T
|
This command was implemented on Cisco 2600 series and Cisco 3600 series.
|
Usage Guidelines
The voice class permanent command can be used for Voice over Frame Relay (VoFR), Voice over ATM (VoATM), and Voice over IP (VoIP) trunks.
The voice class permanent command in global configuration mode is entered without a hyphen. The voice-class permanent command in dial-peer and voice-port configuration modes is entered with a hyphen.
Examples
The following example shows how to create a permanent voice class starting from global configuration mode:
Related Commands
Command
|
Description
|
signal keepalive
|
Configures the keepalive signaling packet interval for Cisco trunks and FRF.11 trunks.
|
signal pattern
|
Configures the ABCD bit pattern for Cisco trunks and FRF.11 trunks.
|
signal timing idle suppress-voice
|
Configures the signal timing parameter for the idle state of a call.
|
signal timing oos
|
Configures the signal timing parameter for the OOS state of a call.
|
signal-type
|
Sets the signaling type for a network dial peer.
|
voice-class permanent
|
Assigns a previously configured voice class for a Cisco trunk or FRF.11 trunk to a network dial peer.
|
voice-class permanent (dial peer)
To assign a previously configured voice class for a Cisco trunk or FRF.11 trunk to a network dial peer, use the voice-class permanent command in dial peer configuration mode. To remove the voice-class assignment from the network dial peer, use the no form of this command.
voice-class permanent tag
no voice-class permanent tag
Syntax Description
tag
|
Unique number assigned to the voice class. The tag number maps to the tag number created using the voice class permanent global configuration command. Range is from 1 to 10000.
|
Command Default
Network dial peers have no voice class assigned.
Command Modes
Dial peer configuration
Command History
Release
|
Modification
|
12.0(3)XG
|
This command was introduced on Cisco MC3810.
|
12.0(4)T
|
This command was integrated into Cisco IOS Release 12.0(4)T.
|
12.1(3)T
|
This command was implemented on Cisco 2600 series and Cisco 3600 series.
|
Usage Guidelines
You can assign one voice class to any given network dial peer. If you assign another voice class to a dial peer, the last voice class assigned replaces the previous voice class.
You cannot assign a voice class to a plain old telephone service (POTS) dial peer.
The voice-class permanent command in dial peer configuration mode is entered with a hyphen. The voice class permanent command in global configuration mode is entered without a hyphen.
Examples
The following example assigns a previously configured voice class to a Voice over Frame Relay (VoFR) network dial peer:
Related Commands
Command
|
Description
|
signal keepalive
|
Configures the keepalive signaling packet interval for Cisco trunks and FRF.11 trunks.
|
signal pattern
|
Configures the ABCD bit pattern for Cisco trunks and FRF.11 trunks.
|
signal timing idle suppress-voice
|
Configures the signal timing parameter for the idle state of a call.
|
signal timing oos
|
Configures the signal timing parameter for the OOS state of a call.
|
signal-type
|
Sets the signaling type for a network dial peer.
|
voice class permanent
|
Creates a voice class for a Cisco trunk or FRF.11 trunk.
|
voice-class permanent (voice-port)
To assign a previously configured voice class for a Cisco trunk or FRF.11 trunk to a voice port, use the voice-class permanent command in voice-port configuration mode. To remove the voice-class assignment from the voice port, use the no form of this command.
voice-class permanent tag
no voice-class permanent tag
Syntax Description
tag
|
Unique number assigned to the voice class. The tag number maps to the tag number created using the voice class permanent global configuration command. Range is 1 to 10000.
|
Command Default
Voice ports have no voice class assigned.
Command Modes
Voice-port configuration
Command History
Release
|
Modification
|
12.0(3)XG
|
This command was introduced on Cisco MC3810.
|
12.0(4)T
|
This command was integrated into Cisco IOS Release 12.0(4)T.
|
12.1(3)T
|
This command was implemented as a voice-port configuration command on Cisco 2600 series and Cisco 3600 series routers.
|
Usage Guidelines
You can assign one voice class to any given voice port. If you assign another voice class to a voice port, the last voice class assigned replaces the previous voice class.
The voice-class permanent command in voice-port configuration mode is entered with a hyphen. The voice class permanent command in global configuration mode is entered without a hyphen.
Examples
The following example assigns a previously configured voice class to voice port 1/1/0:
Related Commands
Command
|
Description
|
signal keepalive
|
Configures the keepalive signaling packet interval for Cisco trunks and FRF.11 trunks.
|
signal pattern
|
Configures the ABCD bit pattern for Cisco trunks and FRF.11 trunks.
|
signal timing idle suppress-voice
|
Configures the signal timing parameter for the idle state of a call.
|
signal timing oos
|
Configures the signal timing parameter for the OOS state of a call.
|
signal-type
|
Sets the signaling type for a network dial peer.
|
voice class permanent
|
Creates a voice class for a Cisco trunk or FRF.11 trunk.
|
voice-class sip e911
To enable SIP E911 system services on a dial peer, use the voice-class sip e911 command in VoIP dialpeer configuration mode. To disable SIP E911 services, use the no form of this command.
voice-class sip e911
no voice-class sip e911
Syntax Description
This command has no arguments or keywords.
Command Default
The dial peer uses the global setting.
Command Modes
VoIP dialpeer configuration mode.
Command History
Release
|
Modification
|
12.4(9)T
|
This command was introduced.
|
Usage Guidelines
The no form of this command sets the dial peer configuration to disable, which indicates that E911 will not be used for this peer. Because the no version of the command causes non default behavior, it can been seen in the show running-config output. See also the voice service voip sip e911 and debug csm neat commands.
Examples
The following examples enable and disable E911 services on a VoIP dial peer:
Router(config)# dial-peer voice 2
Router(config-dial-peer)# voice-class sip e911
*Jun 06 00:47:20.611: setting peer 2 to enable
Router(config-dial-peer)# no voice-class sip e911
*Jun 06 00:49:58.931: setting peer 2 to disable
Related Commands
Command
|
Description
|
debug csm neat
|
Turns on debugging for all Call Switching Module (CSM) Voice over IP (VoIP) calls.
|
show running-config
|
Displays the running configuration.
|
e911
|
Enables E911 system services for SIP voice service VoIP.
|
voice-class sip localhost
To define a local hostname used to generate gateway URLs, use the voice-class sip localhost command in global configuration mode. To disable a local hostname, use the no form of this command.
voice-class sip localhost [dns]:local-host-name-string
no voice-class sip localhost [dns]:local-host-name-string
Syntax Description
dns
|
(Optional) Domain name server.
|
:
|
Command delimiter.
|
local-host-name-string
|
Name used to generate gateway URLs.
|
Command Default
No local hostnames used for locally generated gateway URLs are sent.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.4(2)T
|
This command was introduced.
|
Usage Guidelines
The no voice-class sip localhost command causes the calls using that dial peer to default to the base behavior (use IP addresses in the host portion of the From, Call-ID, and Remote-Party-ID headers). This allows the administrator to turn off this feature on selected dial peers.
Examples
The following example defines a local hostname used to generate a gateway URL:
Router(config)# voice-class sip localhost dns:gateway2.customer1.com
Related Commands
Command
|
Description
|
dial-peer voice
|
Defines a particular dial peer, to specify the method of voice encapsulation, and enters dial peer configuration mode.
|
voice-class sip outbound-proxy
To configure an outbound proxy, use the voice-class outbound-proxy command in dial-peer configuration mode. To reset to, use the no form of this command.
voice-class sip outbound-proxy {ipv4: ip address | dns: host:domain}
no voice-class sip outbound-proxy
Syntax Description
ipv4: ip address
|
Configures proxy on the server, sending all initiating requests to the specified IP address destination.
|
dns: host:domain
|
Configures proxy on the server, sending all initiating requests to the specified domain destination.
|
Command Default
This command is disabled.
Command Modes
Voice-service sip configuration (conf-serv-sip)
Dial-peer configuration (config-dial-peer)
Command History
Release
|
Modification
|
12.4(15)T
|
This command was introduced.
|
Usage Guidelines
The voice-class sip outbound-proxy command, in dial-peer configuration mode, takes precedence over the command in SIP global-configuration mode.
Examples
The following example shows how to set up the voice-class sip outbound-proxy command globally to generate:
Router# configure terminal
Router(config)# voice service voip
Router(conf-voi-serv)# sip
Router(conf-serv-sip)# no outbound-proxy ipv4:10.1.1.1
The following example shows how to set up the voice-class sip outbound-proxy command globally to generate:
Router# configure terminal
Router(config)# voice service voip
Router(conf-voi-serv)# sip
Router(conf-serv-sip)# no outbound-proxy dns:sipproxy:cisco.com
The following example shows how to set up the voice-class sip outbound-proxy command on a dial peer to generate:
Router# configure terminal
Router(conf)# dial-peer voice 111 voip
Router(config-dial-peer)# voice-class sip outbound-proxy ipv4:10.1.1.1
The following example shows how to set up the voice-class sip outbound-proxy command on a dial peer to generate:
Router# configure terminal
Router(conf)# dial-peer voice 111 voip
Router(config-dial-peer)# voice-class sip outbound-proxy dns:sipproxy:cisco.com
Related Commands
Command
|
Description
|
dial-peer voice
|
Defines a particular dial peer, specifies the method of voice encapsulation, and enters dial-peer configuration mode.
|
voice service
|
Enters voice-service configuration mode and specifies a voice-encapsulation type.
|
voice-class sip rel1xx
To enable all Session Initiation Protocol (SIP) provisional responses (other than 100 Trying) to be sent reliably to the remote SIP endpoint, use the voice-class sip rel1xx command in dial peer configuration mode. To reset to the default, use the no form of this command.
voice-class sip rel1xx {supported value | require value | system | disable}
no sip rel1xx
Syntax Description
supported value
|
Supports reliable provisional responses. The value argument may have any value, as long as both the user-agent client (UAC) and user-agent server (UAS) configure it the same.
|
require value
|
Requires reliable provisional responses. The value argument may have any value, as long as both the UAC and UAS configure it the same.
|
system
|
Uses the value configured in voice service mode. This is the default.
|
disable
|
Disables the use of reliable provisional responses.
|
Command Default
system
Command Modes
Dial peer configuration
Command History
Release
|
Modification
|
12.2(2)XB
|
This command was introduced.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T. Support for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 is not included in this release.
|
12.2(11)T
|
This command was applicable to the Cisco AS5300, Cisco AS5350, and Cisco AS5400 in this release.
|
Usage Guidelines
There are two ways to configure reliable provisional responses:
•
Dial-peer mode. You can configure reliable provisional responses for the specific dial peer only by using the voice-class sip rel1xx command.
•
SIP mode. You can configure reliable provisional responses globally by using the rel1xx command.
The use of resource reservation with SIP requires that the reliable provisional feature for SIP be enabled either at the VoIP dial-peer level or globally on the router.
This command applies to the dial peer under which it is used or points to the global configuration for reliable provisional responses. If the command is used with the supported keyword, the SIP gateway uses the Supported header in outgoing SIP INVITE requests. If it is used with the require keyword, the gateway uses the Required header.
This command, in dial peer configuration mode, takes precedence over the rel1xx command in global configuration mode with one exception: If this command is used with the system keyword, the gateway uses what was configured under the rel1xx command in global configuration mode.
Examples
The following example shows how to use this command on either an originating or a terminating SIP gateway:
•
On an originating gateway, all outgoing SIP INVITE requests matching this dial peer contain the Supported header where value is 100rel.
•
On a terminating gateway, all received SIP INVITE requests matching this dial peer support reliable provisional responses.
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip rel1xx supported 100rel
Related Commands
Command
|
Description
|
rel1xx
|
Provides provisional responses for calls on all VoIP calls.
|
voice-class sip resource priority mode (dial peer)
To push the user access server (UAS) to operate in a loose or strict mode, use the voice-class sip resource priority mode command in dial peer voice configuration mode. To disable the voice-class sip resource priority mode, use the no form of this command.
voice-class sip resource priority mode [loose | strict]
no voice-class sip resource priority mode [loose | strict]
Syntax Description
loose
|
(Optional) In the loose mode, unknown values of name space or priority values received in the Resource-Priority header in Session Initiation Protocol (SIP) requests are ignored by the gateway. The request is processed as if the Resource-Priority header was not present.
|
strict
|
(Optional) In the strict mode, unknown values of name space or priority values received in the Resource-Priority header in SIP requests are rejected by the gateway using a SIP response code 417 (Unknown Resource-Priority) message response. An Accept-Resource-Priority header enumerating the supported name space and values is included in the 417 message response.
|
Command Default
The default value is loose mode.
Command Modes
Dial peer voice configuration
Command History
Release
|
Modification
|
12.4(2)T
|
This command was introduced.
|
Usage Guidelines
When the no version of this command is executed, the call operates in the loose mode.
Examples
The following example shows how to set up the voice-class sip resource priority mode command in loose mode:
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip resource priority mode loose
The following example shows how to set up the voice-class sip resource priority mode command in strict mode:
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip resource priority mode strict
Related Commands
Command
|
Description
|
voice-class sip resource priority namespace
|
Priorities mandatory call prioritization handling for initial original INVITE message requests.
|
voice-class sip resource priority namespace (dial peer)
To prioritize mandatory call prioritization handling for initial original INVITE message requests, use the voice-class sip resource priority namespace command in dial peer voice configuration mode. To disable the voice-class sip resource priority namespace command, use the no form of this command.
voice-class sip resource priority namespace [drsn | dsn | q735]
no voice-class sip resource priority namespace [drsn | dsn | q735]
Syntax Description
drsn
|
(Optional) U. S. Defense Red Switched Network (DRSN).
|
dsn
|
(Optional) U. S. Defense Switched Network (DSN).
|
q735
|
(Optional) International Telecommunications Union, Stage 3 description for community of interest supplementary services using Signaling System No. 7: Multilevel precedence and preemption, Recommendation Q.735.3, March 1993.
|
Command Default
When the no version of this command is executed using namespace, the Cisco IOS gateway transparently passes the multilevel precedence and preemption (MLPP) values that were received on the PSTN side.
Command Modes
Dial peer voice configuration
Command History
Release
|
Modification
|
12.4(2)T
|
This command was introduced.
|
Usage Guidelines
When the no version of this command is executed using the namespace, the Cisco IOS gateway transparently passes the multilevel precedence and preemption (MLPP) values that were received on the PSTN side.
Examples
The following example shows how to set up the voice-class sip resource priority namespace command in the U. S. DSN format name space:
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip resource priority namespace dsn
The following example shows how to set up the voice-class sip resource priority namespace command in the U. S. DRSN format name space:
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip resource priority namespace drsn
The following example shows how to set up the voice-class sip resource priority namespace command in the Public SS7 Network format name space:
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip resource priority namespace q735
Related Commands
Command
|
Description
|
voice-class sip resource priority mode
|
Pushes the UAS to operate in a loose or strict mode.
|
voice-class sip transport switch
To enable switching between UDP and TCP transport mechanisms for large Session Initiation Protocol (SIP) messages for a specific dial peer, use the voice-class sip transport switch command in dial peer configuration mode. To disable switching between UDP and TCP transport mechanisms for large SIP messages for a specific dial peer, use the no form of this command.
voice-class sip transport switch udp tcp
no voice-class sip transport switch udp tcp
Syntax Description
udp
|
Enables switching transport from UDP on the basis of the size of the SIP request being greater than the MTU size.
|
tcp
|
Enables switching transport to TCP.
|
Command Default
Disabled.
Command Modes
Dial peer configuration
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced.
|
Usage Guidelines
The voice-class sip transport switch command takes precedence over the global transport switch command.
Examples
The following example shows how to set up the voice-class sip transport switch command:
Router(config)# dial-peer voice 102 voip
Router(config-dial-peer)# voice-class sip transport switch udp tcp
Related Commands
Command
|
Description
|
debug ccsip transport
|
Enables tracing of the SIP transport handler and the TCP or UDP process.
|
transport switch
|
Enables switching between transport mechanisms globally if the SIP message is larger than 1300 bytes.
|
voice-class sip url
To configure URLs to either the Session Initiation Protocol (SIP), SIP security (SIPS), or telephone (TEL) format for your dial-peer SIP calls, use the voice-class sip url command in dial peer configuration mode. To reset to the default value (system), use the no form of this command.
voice-class sip url {sip | sips | system | tel}
no voice-class sip url
Syntax Description
sip
|
Generates URLs in the SIP format for calls on a dial-peer basis.
|
sips
|
Generates URLs in the SIPS format for calls on a dial-peer basis.
|
system
|
Uses the system value. This is the default.
|
tel
|
Generates URLs in the TEL format for calls on a dial-peer basis.
|
Command Default
system
Command Modes
Dial peer configuration
Command History
Release
|
Modification
|
12.2(2)XB
|
This command was introduced.
|
12.2(2)XB1
|
This command was implemented on Cisco AS5850.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T. Support for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 was not included in this release.
|
12.2(11)T
|
This command was implemented on the Cisco AS5300, Cisco AS5350, and Cisco AS5400 platforms.
|
12.4(6)T
|
The sips keyword was added to the command.
|
Usage Guidelines
This command affects only user-agent clients (UACs), because it causes the use of a SIP, SIPS, or TEL URL in the request line of outgoing SIP INVITE requests. SIP URLs indicate the originator, recipient, and destination of the SIP request; TEL URLs indicate voice-call connections.
The voice-class sip url command, in dial peer configuration mode, takes precedence over the url command in SIP global-configuration mode. However, if the voice-class sip url command is used with the system keyword, the gateway uses what was globally configured under the url command.
Examples
The following example shows how to set up the voice-class sip url command to generate URLs in the SIP format:
The following example shows how to set up the voice-class sip url command to generate URLs in the SIPS format:
The following example shows how to set up the voice-class sip url command to generate URLs in the TEL format:
Related Commands
Command
|
Description
|
sip url
|
Generates URLs in the SIP, SIPS, or TEL format.
|
url
|
Configures URLs to either session initiation protocol (SIP), SIP secure (SIPS), or telephone (TEL) format.
|
voice class tone-signal
To enter voice-class configuration mode and create a tone-signal voice class, use the voice class tone-signal command in global configuration mode. To delete a tone-signal voice class, use the no form of this command.
voice class tone-signal tag
no voice class tone-signal tag
Syntax Description
tag
|
Label that uniquely identifies the voice class. Can be up to 32 alphanumeric characters.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)XD
|
This command was introduced.
|
12.3(7)T
|
This command was integrated into Cisco IOS Release 12.3(7)T.
|
Usage Guidelines
Use the voice class tone-signal command to define wakeup, frequency selection, and guard tones to be played out before and during the voice packets for a specific voice port. Use the inject guard-tone, inject pause, and inject tone commands to define the tone signaling in this class. You can configure up to ten tones in a tone-signal voice class.
To avoid voice loss at the receiving end of an LMR system, the maximum of the sum of the durations of the injected tones and pauses in the voice class should not exceed 1500 milliseconds. You must also use the timing delay-voice tdm command to configure a delay for the voice packet equal to the sum of the durations of all the injected tones and pauses.
Note that the hyphenation in this command differs from the hyphenation used in a similar command, voice-class tone-signal, which is used in voice-port configuration mode.
Examples
The following example shows how to create a tone-signal voice class starting from global configuration mode:
voice class tone-signal mytones
Related Commands
Command
|
Description
|
inject guard-tone
|
Plays out a guard tone with the voice packet.
|
inject pause
|
Specifies a pause between injected tones.
|
inject tone
|
Specifies a wakeup or frequency selection tone to be played out before the voice packet.
|
timing delay-voice tdm
|
Specifies the delay before a voice packet is played out.
|
voice-class tone-signal
|
Assigns a previously configured tone-signal voice class to a voice port.
|
voice-class tone-signal
To assign a previously configured tone-signal voice class to a voice port, use the voice-class tone-signal command in voice-port configuration mode. To delete a tone-signal voice class, use the no form of this command.
voice-class tone-signal tag
no voice-class tone-signal tag
Syntax Description
tag
|
Unique label assigned to the voice class. The tag label maps to the tag label created using the voice class tone-signal global configuration command. Can be up to 32 alphanumeric characters.
|
Command Default
Voice ports have no tone-signal voice class assigned.
Command Modes
Voice-port configuration
Command History
Release
|
Modification
|
12.3(4)XD
|
This command was introduced.
|
12.3(7)T
|
This command was integrated into Cisco IOS Release 12.3(7)T.
|
Usage Guidelines
The voice-class tone-signal command is available on an ear and mouth (E&M) voice port only if the signal type for that port is Land Mobile Radio (LMR). Note that the hyphenation in this command differs from the hyphenation used in a similar command, voice class tone-signal, which is used in global configuration mode.
Examples
The following example assigns a previously configured voice class to voice port 1/1/0:
voice-class tone-signal mytones
Related Commands
Command
|
Description
|
voice class tone-signal
|
Enters voice-class configuration mode and assigns an identification tag number for a tone-signal voice class.
|
voice confirmation-tone
To disable the two-beep confirmation tone for private line, automatic ringdown (PLAR), or PLAR off-premises extension (OPX) connections, use the voice confirmation-tone command in voice-port configuration mode. To enable the two-beep confirmation tone, use the no form of this command.
voice confirmation-tone
no voice confirmation-tone
Syntax Description
This command has no arguments or keywords.
Command Default
The two-beep confirmation tone is heard on PLAR and PLAR OPX connections.
Command Modes
Voice-port configuration
Command History
Release
|
Modification
|
11.3(1)MA
|
This command was introduced on Cisco MC3810.
|
Usage Guidelines
Use this command to disable the two-beep confirmation tone that a caller hears when picking up the handset for PLAR and PLAR OPX connections. This command is valid only if the voice-port connection command is set to PLAR or PLAR OPX.
Examples
The following example disables the two-beep confirmation tone on voice port 1/0/0:
Related Commands
Command
|
Description
|
connection
|
Specifies a connection mode for a voice port.
|
voice dnis-map
To create or modify a Digital Number Identification Service (DNIS) map, use the voice dnis-map command in global configuration mode. To delete a DNIS map, use the no form of this command.
voice dnis-map map-name [url]
no voice dnis-map map-name
Syntax Description
map-name
|
Name of the DNIS map.
|
url
|
(Optional) URL of an external text file that contains a list of DNIS entries.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(2)XB
|
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
|
12.2(11)T
|
This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco 3640 and Cisco 3660.
|
Usage Guidelines
A DNIS map is a table of DNIS numbers associated with a single dial peer. For applications such as VoiceXML, using a DNIS map makes it possible to configure a single dial peer for all DNIS numbers used to refer to VoiceXML documents. Keep the following considerations in mind when using voice DNIS maps.
•
A separate entry must be made for each DNIS entry in a DNIS map. Wildcards are not supported.
•
If a URL is not supplied, the command enters DNIS-map configuration mode, permitting the entry of DNIS numbers by using the dnis command.
•
The URL argument points to the location of an external text file containing a list of DNIS entries (for example: tftp://dnismap.txt). This allows the administrator to maintain a single master file of all DNIS map entries, if desired, rather than configuring the DNIS entries on each gateway.
The name of the text file extension is not significant; .doc, .txt, or .cfg are all acceptable because the extension is not checked. The entries in the file should look the same as a DNIS entry configured in Cisco IOS software (for example: dnis 5553305 url tftp://global/tickets/movies.vxml).
•
External text files used for DNIS maps must be stored on TFTP servers; they cannot be stored on HTTP servers.
•
To associate a DNIS map with a dial peer, use the dnis-map command.
•
To view the configuration information for DNIS maps, use the show voice dnis-map command.
Examples
The following example shows how the voice dnis-map command is used to create a DNIS map:
The following example shows the voice dnis-map command used with a URL that specifies the location of a text file containing the DNIS entries:
voice dnis-map dmap2 tftp://keyer/dmap2/dmap2.txt
Following is an example of the contents of a text file comprising a DNIS map:
!Example dnis-map with 8 entries.
dnis 5550112 url tftp://global/ticket/vapptest1.vxml
dnis 5550111 url tftp://global/ticket/vapptest2.vxml
dnis 5550134 url tftp://global/ticket/vapptest3.vxml
Related Commands
Command
|
Description
|
dnis
|
Adds a DNIS number to a DNIS map.
|
dnis-map
|
Associates a DNIS map with a dial peer.
|
show voice dnis-map
|
Displays configuration information about DNIS maps.
|
voice dnis-map load
|
Reloads a DNIS map that has changed since the previous load.
|
voice class uri
To create or modify a voice class for matching dial peers to a Session Initiation Protocol (SIP) or telephone (TEL) uniform resource identifier (URI), use the voice class uri command in global configuration mode. To remove the voice class, use the no form of this command.
voice class uri tag {sip | tel}
no voice class uri tag
Syntax Description
tag
|
Label that uniquely identifies the voice class. Can be up to 32 alphanumeric characters.
|
sip
|
Voice class for SIP URIs.
|
tel
|
Voice class for TEL URIs.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
•
This command takes you to voice URI class configuration mode, where you configure the match characteristics for a URI. The commands that you enter in this mode define the set of rules by which the URI in a call is matched to a dial peer.
•
To reference this voice class for incoming calls, use the incoming uri command in the inbound dial peer. To reference this voice class for outgoing calls, use the destination uri command in the outbound dial peer.
•
Using the no voice class uri command removes the voice class from any dial peer where it is configured with the destination uri or incoming uri commands.
Examples
The following example defines a voice class for SIP URIs:
The following example defines a voice class for TEL URIs:
Related Commands
Command
|
Description
|
debug voice uri
|
Displays debugging messages related to URI voice classes.
|
destination uri
|
Specifies the voice class used to match the dial peer to the destination URI for an outgoing call.
|
host
|
Matches a call based on the host field in a SIP URI.
|
incoming uri
|
Specifies the voice class used to match a VoIP dial peer to the URI of an incoming call.
|
pattern
|
Matches a call based on the entire SIP or TEL URI.
|
phone context
|
Filters out URIs that do not contain a phone-context field that matches the configured pattern.
|
phone number
|
Matches a call based on the phone number field in a TEL URI.
|
show dialplan incall uri
|
Displays which dial peer is matched for a specific URI in an incoming call.
|
show dialplan uri
|
Displays which outbound dial peer is matched for a specific destination URI.
|
user-id
|
Matches a call based on the user-id field in the SIP URI.
|
voice class uri sip preference
To set the preference for selecting a voice class for Session Initiation Protocol (SIP) uniform resource identifiers (URIs), use the voice class uri sip preference command in global configuration mode. To reset to the default, use the no form of this command.
voice class uri sip preference {user-id | host}
no voice class uri sip preference
Syntax Description
user-id
|
User-id field is given preference.
|
host
|
Host field is given preference.
|
Command Default
Host field
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
•
Use this command to resolve ties when more than one voice class is matched for a SIP URI. The default is to match on the host field of the URI.
•
This command applies globally to all URI voice classes for SIP.
Examples
The following example defines the preference as the user-id for a SIP voice class:
voice class uri sip preference user-id
Related Commands
Command
|
Description
|
debug voice uri
|
Displays debugging messages related to URI voice classes.
|
destination uri
|
Specifies the voice class used to match the dial peer to the destination URI for an outgoing call.
|
host
|
Matches a call based on the host field in a SIP URI.
|
incoming uri
|
Specifies the voice class used to match a VoIP dial peer to the URI of an incoming call.
|
user-id
|
Matches a call based on the user-id field in the SIP URI.
|
show dialplan incall uri
|
Displays which dial peer is matched for a specific URI in an incoming call.
|
show dialplan uri
|
Displays which outbound dial peer is matched for a specific destination URI.
|
voice class uri
|
Creates or modifies a voice class for matching dial peers to a SIP or TEL URI.
|
voice dnis-map load
To reload a DNIS map that has been modified, use the voice dnis-map load command in privileged EXEC mode. This command does not have a no form.
voice dnis-map load map-name
Syntax Description
map-name
|
Name of the DNIS map to reload.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)XB
|
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
|
12.2(11)T
|
This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco 3640 and Cisco 3660.
|
Usage Guidelines
This command reloads a DNIS map residing on an external server. Use this command when the DNIS map file has changed since the previous load.
To create or modify a DNIS map, use the voice dnis-map command.
Examples
The following example reloads a DNIS map named "mapfile1":
Router# voice dnis-map load mapfile1
Related Commands
Command
|
Description
|
dnis
|
Adds a DNIS number to a DNIS map.
|
dnis-map
|
Associates a DNIS map with a dial peer.
|
show voice dnis-map
|
Displays configuration information about DNIS maps.
|
voice dnis-map
|
Enters DNIS map configuration mode to create a DNIS map.
|
voice dsp crash-dump
To enable the crash dump feature and to specify the destination file and the file limit, enter the
voice dsp crash-dump command in global configuration mode. To disable the feature, use the no form of the command.
voice dsp crash-dump [destination url | file-limit limit-number]
no voice dsp crash-dump
Syntax Description
destination url
|
Designates a valid file system where crash dump analysis is stored. The url argument must be set to a valid file system.
The destination url can be one of the following
• The file on a TFTP server with the following format: tftp://x.x.x.x/subfolder/filename.
The x.x.x.x value is the IP address of the TFTP server
• The file on the flashcard of the router, with the following format: slot0:filename
Note The digital signal processor (DSP) crash dump feature is disabled when either the crash-dump destination is not specified.
|
file-limit limit-number
|
The crash dump file-limit keyword must be set to a non-zero value. The default is that the crash dump capability is turned off, as the url argument is empty, and the file-number argument is zero.
The limit-number argument may range from 0 (no file will be written) to 99.
Note The DSP crash dump feature is disabled when the crash-dump file limit is set to 0.
|
Command Default
Crash dump capability is turned off.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
To configure the router to write a crash dump file, the destination url in the voice dsp crash-dump command must be set to a valid file system, and the crash dump file limit must be set to a non-zero value. The default is that the crash dump capability is turned off, as the url field is empty, and the file limit is zero.
As each crash-dump file is created, the name of the file has a number appended to the end. This number is incremented from 1 to up to the file limit for each subsequent crash dump file written. If the router reloads, the number is reset back to 1, and so file number 1 is written again. After the file number reaches the maximum file limit, no more files are written.
The file count can be manually reset by setting the file limit to zero and then setting it to a non-zero limit. This has the effect of restarting the count of files written, causing the files 1 to the file limit of 99 to be able to be written again, thus overwriting the original files.
Setting the file-number argument to zero (the default) disables the collection of the dump from the DSP. In this case, the memory is not collected from the DSP, and the stack is not displayed on the console. If the keepalive mechanism detects a crashed DSP, the DSP is simply restarted.
Setting the file-number argument to a non-zero number but having a null destination url causes the dump to be collected and the stack to be displayed on the console, but no dump file is written.
If auto-recovery is turned off for the router, no DSP dump functions are enabled, no keepalive checks are done, and no dumps are collected or written.
Note
Some types of flash need to be completely erased to free up space from deleted files, and some types of flash cannot have files overwritten with new versions until the entire flash is erased. As a result, you might want to set the file limit so that only one or two dump files are written to flash. This prevents flash from being filled up.
Note
It is not recommended to write crash dump files to internal flash or bootflash, because these files are normally used to hold configuration information and Cisco IOS software images. Cisco recommends writing crash dump files to spare flash cards, which can be inserted into slot 0 or slot 1 on many of the routers. These cards usually do not hold critical information and may be erased. Additionally, these cards can be conveniently removed from the router and sent to Cisco, so that the crash dump files can be analyzed.
Examples
The following example enables the crash dump feature and specifies the destination file in slot 0:
Router configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# voice dsp crash-dump destination slot0:banjo-152-s
1w0d:%SYS-5-CONFIG_I:Configured from console by console
Check your configuration by entering the show voice dsp crash-dump command in privileged EXEC configuration mode:
Router# show voice dsp crash-dump
Voice DSP Crash-dump status:
Destination file url is slot0:banjo-152-s
Last DSP dump file written was
tftp://112.29.248.12/tester/26-152-t2
Next DSP dump file written will be slot0:banjo-152-s1
Related Commands
Command
|
Description
|
debug voice dsp crash-dump
|
Displays crash dump debug information.
|
show voice dsp crash-dump
|
Displays voice dsp crash dump information.
|
voice echo-canceller extended
To enable the extended G.168 echo canceller (EC) on the Cisco 1700 series, Cisco ICS7750, or Cisco AS5300, use the voice echo-canceller extended command in global configuration mode. To reset to the default, use the no form of this command.
Cisco 1700 series and Cisco ICS 7750
voice echo-canceller extended
no voice echo-canceller extended
Cisco AS5300
voice echo-canceller extended [codec small codec large codec]
no voice echo-canceller extended
Syntax Description
codec
|
(Optional) Defines restricted codecs, both small and large.
|
small codec
|
Small footprint codec. Valid values for the codec argument are:
• g711
• g726
|
large codec
|
Large footprint codec. Valid values for the codec argument are:
• fax-relay
• g723
• g728
• g729
• gsmefr
• gsmfr
|
Command DefaultV
Proprietary Cisco G.165 EC is enabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
12.3(3)
|
This command was modified to allow unrestricted codecs on the Cisco AS5300. The codec keyword was made optional.
|
Usage Guidelines
Cisco 1700 series and Cisco ICS7750
You do not have to shut down all the voice ports on the Cisco 1700 series or Cisco ICS7750 to switch the echo canceller, but you should make sure that when you switch the echo canceller, there are no active calls on the router.
Because echo cancellation is an invasive process that can minimally degrade voice quality, you should disable this command if it is not needed.
Cisco AS5300
This command is available only on the Cisco AS5300 with C542 or C549 digital signal processor module (DSPM) high-complexity firmware.
The voice echo-canceller extended command enables the extended EC on a Cisco AS5300 using C549 DSP firmware with one channel of voice per DSP and unrestricted codecs. Any codec is supported.
The voice echo-canceller extended codec command enables the extended EC on a Cisco AS5300 using C542 or C549 DSP firmware with two channels of voice per DSP and restricted codecs. Only specific codecs can be used with the extended EC.
If fax-relay is not selected as the large codec, the VoIP dial peer requires that you use the
fax rate disabled command in dial peer configuration mode.
After choosing the codecs to be supported by the extended echo canceller, either remove all dial peers with different codecs not supported by your new configuration or modify the dial-peer codec selection by selecting a voice codec or fax-relay. When codecs are restricted, only one selection is allowed. You must have a VoIP dial peer configured with an extended EC-compatible codec to ensure voice quality on the connection.
This command is not accepted if there are active calls. If the EC is already in effect and a codec choice is changed, the system scans the dial peers. Any dial peers that do not conform to the new global command settings are changed, and the user is informed of the changes. Similarly, modem relay is incompatible with the extended EC and must be disabled globally for all dial peers.
Note
This command is valid only when the echo-cancel enable command and the echo-cancel coverage command are enabled.
Examples
The following example sets the extended G.168 EC on the Cisco 1700 series or Cisco ICS7750:
Router(config)# voice echo-canceller extended
The following example sets the extended G.168 EC on the Cisco AS5300 with restricted codecs:
Router(config)# voice echo-canceller extended codec small g711 large g726
The following example shows an error message that displays when a restricted codec is not allowed:
Cannot configure now, dial-peer 8800 is configured with codec=g728, fax rate=disable,
modem=passthrough system.If necessary set this command to 'no', re-configure dial-peer
codec, fax rate and/or modem. Then re-enter this command.
In the above example, dial peer 8800 is misconfigured with a codec type, g728, that was not selected for the large codec type using the voice echo-canceller extended command.
Related Commands
Command
|
Description
|
echo-cancel coverage
|
Enables the cancellation of voice that is sent out the interface and is received on the same interface.
|
echo-cancel enable
|
Enables the cancellation of voice that is sent and received on the same interface.
|
voice enum-match-table
To create an ENUM match table for voice calls, use the voice enum-match-table in global configuration mode. To delete the ENUM match table, use the no form of this command.
voice enum-match-table table-number
no voice enum-match-table table-number
Syntax Description
table-number
|
Number of the ENUM match table. Range is from 1 to 15. There is no default value.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced.
|
Usage Guidelines
The ENUM match table is a set of rules for matching incoming calls. When a call comes in, its called number is matched against the match pattern of the rule with the highest preference.
If it matches, the replacement pattern is applied to the number. The resulting number and the domain name of the rule are used to make an ENUM query.
If the called number does not match the match pattern, the next rule in order of preference is selected.
Examples
The following example creates ENUM match table 3 for voice calls:
Router(config)# voice enum-match-table 3
Router(config-enum)# rule 1 5/(.*)/ /\1/e164.cisco.com
Router(config-enum)# rule 2 4/^9011\(.*\)/ /\1/e164.arpa
In this table, rule 1 matches any number. The resulting number is the same as the called number. That number and the domain name "e164.cisco.com" are used to make an ENUM query.
Rule 2 matches any number that starts with 9011. The 9011 is removed from the incoming number. The resulting number and the domain name "e164.arpa" are used for the ENUM query.
Suppose an incoming call has a called number of 4085551212. [Rule 2 is applied] first because it has a higher preference. The first few digits, 4085, do not match the 9011 pattern of rule 2, so [rule 1 is applied] next. The called number matches rule 1, and the resulting number is 4085551212. This number and "e164.cisco.com" form the ENUM query (2.1.2.1.5.5.5.8.0.4.e164.cisco.com).
Related Commands
Command
|
Description
|
rule (ENUM configuration)
|
Defines the matching, replacement, and rejection patterns for an ENUM match table.
|
show voice enum-match-table
|
Displays the configuration of voice ENUM match tables.
|
test enum
|
Tests the functionality of an ENUM match table.
|
voice hpi capture
To allocate the Host Port Interface (HPI) capture buffer size (in bytes) and to set up or change the destination URL for captured data, use the voice hpi capture command in global configuration mode. To stop all logging and file operations, to disable data transport from the capture buffer, and to automatically set the buffer size to 328, use the no form of this command.
voice hpi capture [buffer size | destination url]
no voice hpi capture buffer size
Syntax Description
buffer size
|
(Optional) Size of HPI capture buffer, in bytes. Range is from 328 to 9000000. The default is 328.
|
destination url
|
(Optional) Destination URL for storing captured data.
|
Command Default
328 bytes (no buffer is used if it is not configured explicitly)
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(10)
|
This command was introduced.
|
12.2(11)T
|
This command was integrated into Cisco IOS Release 12.2(11)T.
|
Usage Guidelines
If you want to change the size of an existing non-zero buffer, you must first reset it to 0 and then change it from 0 to the new size.
The destination url option sets up or changes the destination URL for captured data. To disable data transport from the capture buffer, use the no form of the command. If the buffer is allocated, captured data is sent to the current URL (if it was already configured) until the new URL is specified.
If a new URL differs from the current URL and logging is enabled, the current URL is closed and all further data is sent to the new URL. Entering a blank URL or prefixing the command with no disables data transport from the capture buffer, and (if capture is enabled) captured data is stored in the capture buffer until it reaches its capacity.
Once the buffer-queueing program is running, the transport process attempts to connect to a new or existing "capture destination" URL. A version message is written to the URL, and if the message is successfully received, any further messages placed into the message queue are written to that URL. If a new URL is entered using the voice hpi capture destination url command, the open URL is closed, and the system attempts to write to the new URL. If the new URL does not work, the transport process exits. The transport process is restarted when another URL is entered or the system is restarted.
The buffer size option sets the maximum amount of memory (in bytes) that the capture system allocates for its buffers when it is active. The capture buffer is where the captured messages are stored before they are sent to the URL specified by the capture destination. The system is started by choosing the amount of memory (greater than 0 bytes) that the buffer-queueing system can allocate to the free message pool. HPI messages can then be captured until buffer capacity is reached. Entering 0 for the buffer size and prefixing the command with no stops all logging and file operations and automatically sets the buffer size to 0.
The voice hpi capture command can be saved with the router configuration so that the command is active during router startup. This allows you to capture the HPI messages sent during router bootup before the CLI is enabled. After you have configured the buffer size in the running configuration (valid range is from 328 to 9000000), save it to the startup configuration using the write command or to the TFTP server using the copy run tftp command.
Caution ![](../../../../../../i/templates/blank.gif)
Using the message logger feature in a production network environment impacts CPU and memory usage on the gateway.
Examples
The following example changes the size (in bytes) of the HPI capture buffer and initializes the buffer-queueing program:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# voice hpi capture buffer 40000
03:23:31:caplog:caplog_cli_interface:hpi capture buffer size set to 40000 bytes
03:23:31:caplog:caplog_logger_init:TRUE, Started task HPI Logger (PID 64)
03:23:31:caplog:caplog_cache_init:TRUE, malloc_named(39852), 123 elements (each 324 bytes
big)
03:23:31:caplog:caplog_logger_proc:Attempting to open ftp://172.23.184.233/c:b-38-117
03:23:32:%SYS-5-CONFIG_I:Configured from console by console
The following example sets the capture destination by entering a destination URL using FTP:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# voice hpi capture destination ftp://172.23.184.233/c:b-38-117a
04:05:10:caplog:caplog_cli_interface:hpi capture
destination:ftp://172.23.184.233/c:b-38-117a
04:05:10:caplog:caplog_logger_init:TRUE, Started task HPI Logger (PID 19)
04:05:10:caplog:caplog_cache_init:Cache must be at least 324 bytes
04:05:10:caplog:caplog_logger_proc:Terminating...
Related Commands
Command
|
Description
|
debug hpi
|
Turns on the debug output for the logger.
|
show voice hpi capture
|
Displays the capture status and statistics.
|
voice hunt
To configure an originating or tandem router so that it continues dial-peer hunting if it receives a specified disconnect cause code from a destination router, use the voice hunt command in global configuration mode. To configure the router so that it stops dial-peer hunting if it receives a specified disconnect cause code (the default condition), use the no form of this command. To restore the default dial-peer hunt setting, use the default form of this command.
voice hunt {disconnect-cause-code | all}
no voice hunt {disconnect-cause-code | all}
default voice hunt
Syntax Description
disconnect-cause-code
|
A code returned from the destination router to indicate why an attempted end-to-end call was unsuccessful. If the specified disconnect cause code is returned from the last destination endpoint, dial peer hunting is enabled or disabled. Table 242 in the "Usage Guidelines" section describes the possible values. You can enter the keyword, decimal value, or hexadecimal value.
|
all
|
Continue dial-peer hunting for all disconnect cause codes returned from the destination endpoint.
|
default
|
Restores the default dial-peer hunt setting, that is, the router stops dial-peer hunting if it receives the user-busy or no-answer disconnect cause code.
|
Command Default
The router stops dial-peer hunting if it receives the user-busy or no-answer disconnect cause code.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced for VoFR on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810. It was also introduced for VoIP on the Cisco 2600 series and Cisco 3600 series.
|
12.0(7)T
|
This command was implemented for VoIP on the Cisco AS5300 and Cisco AS5800.
|
12.0(7)XK
|
This command was implemented for VoIP on the Cisco MC3810.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T and implemented for VoIP on the Cisco MC3810.
|
12.1(3)XI
|
The invalid-number and unassigned-number keywords were added, and the command name was changed to voice hunt.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
12.2(4)T
|
Keywords were added for more disconnect cause codes.
|
12.3(8)T
|
The disconnect-cause-code argument was modified to accept nonstandard disconnect cause codes.
|
Usage Guidelines
This command is used with routers that act as originating or tandem nodes in a VoIP, VoFR, or Voice over ATM environment.
For an outgoing call from an originating VoIP gateway configured for rotary dial-peer hunting, more than one dial peer may match the same destination number. The matching dial peers may have different routes. After the voice call using the first dial peer gets disconnected, it will return a disconnect cause code. To have the router to pick up the next matching dial peer in the rotary group and set up a call, the router must be configure to continue hunting the various routes. Use this command to configure the router's hunting behavior when specified cause codes are received.
You can use this command to enable and disable dial-peer hunting when nonstandard disconnect cause codes are received. Nonstandard disconnect cause codes are those that are not defined in ITU-T Recommendation Q.931, but are used by service providers. When this command is used to disable dial-peer hunting for a specific disconnect cause code, it appears in the running configuration of the router.
The disconnect cause codes are described in Table 242. The decimal and hexadecimal value of the disconnect cause code follows the description of each possible keyword.
Table 242 Standard Disconnect Cause Codes
Keyword
|
Description
|
Decimal
|
Hex
|
access-info-discard
|
Access information discarded.
|
43
|
0x2b
|
all
|
Continue dial-peer hunting for all disconnect cause codes received from a destination router.
|
|
|
b-cap-not-implemented
|
Bearer capability not implemented.
|
65
|
0x41
|
b-cap-restrict
|
Restricted digital information bearer capability only.
|
70
|
0x46
|
b-cap-unauthorized
|
Bearer capability not authorized.
|
57
|
0x39
|
b-cap-unavail
|
Bearer capability not available.
|
58
|
0x3a
|
call-awarded
|
Call awarded.
|
7
|
0x7
|
call-cid-in-use
|
Call exists, call ID in use.
|
83
|
0x53
|
call-clear
|
Call cleared.
|
86
|
0x56
|
call-reject
|
Call rejected.
|
21
|
0x15
|
cell-rate-unavail
|
Cell rate not available.
|
37
|
0x25
|
channel-unacceptable
|
Channel unacceptable.
|
6
|
0x6
|
chantype-not-implement
|
Channel type not implemented.
|
66
|
0x42
|
cid-in-use
|
Call ID in use.
|
84
|
0x54
|
codec-incompatible
|
Codec incompatible.
|
171
|
0xab
|
cug-incalls-bar
|
Closed user group (CUG) incoming calls barred.
|
55
|
0x37
|
cug-outcalls-bar
|
CUG outgoing calls barred.
|
53
|
0x35
|
dest-incompatible
|
Destination incompatible.
|
88
|
0x58
|
dest-out-of-order
|
Destination out of order.
|
27
|
0x1b
|
dest-unroutable
|
No route to destination.
|
3
|
0x3
|
dsp-error
|
Digital signal processor (DSP) error.
|
172
|
0xac
|
dtl-trans-not-node-id
|
Designated transit list (DTL) transit not my node ID.
|
160
|
0xa0
|
facility-not-implemented
|
Facility not implemented.
|
69
|
0x45
|
facility-not-subscribed
|
Facility not subscribed.
|
50
|
0x32
|
facility-reject
|
Facility rejected.
|
29
|
0x1d
|
glare
|
Glare.
|
15
|
0xf
|
glaring-switch-pri
|
Glaring switch PRI.
|
180
|
0xb4
|
htspm-oos
|
Holst Telephony Service Provider Module (HTSPM) out of service.
|
129
|
0x81
|
ie-missing
|
Mandatory information element missing.
|
96
|
0x60
|
ie-not-implemented
|
Information element not implemented.
|
99
|
0x63
|
info-class-inconsistent
|
Inconsistency in information and class.
|
62
|
0x3e
|
interworking
|
Interworking.
|
127
|
0x7f
|
invalid-call-ref
|
Invalid call reference value.
|
81
|
0x51
|
invalid-ie
|
Invalid information element contents.
|
100
|
0x64
|
invalid-msg
|
Invalid message.
|
95
|
0x5f
|
invalid-number
|
Invalid number.
|
28
|
0x1c
|
invalid-transit-net
|
Invalid transit network.
|
91
|
0x5b
|
misdialled-trunk-prefix
|
Misdialed trunk prefix.
|
5
|
0x5
|
msg-incomp-call-state
|
Message in incomplete call state.
|
101
|
0x65
|
msg-not-implemented
|
Message type not implemented.
|
97
|
0x61
|
msgtype-incompatible
|
Message type not compatible.
|
98
|
0x62
|
net-out-of-order
|
Network out of order.
|
38
|
0x26
|
next-node-unreachable
|
Next node unreachable.
|
128
|
0x80
|
no-answer
|
No user answer.
|
19
|
0x13
|
no-call-suspend
|
No call suspended.
|
85
|
0x55
|
no-channel
|
Channel does not exist.
|
82
|
0x52
|
no-circuit
|
No circuit.
|
34
|
0x22
|
no-cug
|
Nonexistent CUG.
|
90
|
0x5a
|
no-dsp-channel
|
No DSP channel.
|
170
|
0xaa
|
no-req-circuit
|
No requested circuit.
|
44
|
0x2c
|
no-resource
|
No resource.
|
47
|
0x2f
|
no-response
|
No user response.
|
18
|
0x12
|
no-voice-resources
|
No voice resources available.
|
126
|
0x7e
|
non-select-user-clear
|
Nonselected user clearing.
|
26
|
0x1a
|
normal-call-clear
|
Normal call clearing.
|
16
|
0x10
|
normal-unspecified
|
Normal, unspecified.
|
31
|
0x1f
|
not-in-cug
|
User not in CUG.
|
87
|
0x57
|
number-changeed
|
Number changed.
|
22
|
0x16
|
param-not-implemented
|
Nonimplemented parameter passed on.
|
103
|
0x67
|
perm-frame-mode-oos
|
Permanent frame mode out of service.
|
39
|
0x27
|
perm-frame-mode-oper
|
Permanent frame mode operational.
|
40
|
0x28
|
precedence-call-block
|
Precedence call blocked.
|
46
|
0x2e
|
preempt
|
Preemption.
|
8
|
0x8
|
preempt-reserved
|
Preemption reserved.
|
9
|
0x9
|
protocol-error
|
Protocol error.
|
111
|
0x6f
|
qos-unavail
|
QoS unavailable.
|
49
|
0x31
|
rec-timer-exp
|
Recovery on timer expiry.
|
102
|
0x66
|
redirect-to-new-destination
|
Redirect to new destination.
|
23
|
0x17
|
req-vpci-vci-unavail
|
Requested VPCI VCI not available.
|
35
|
0x23
|
send-infotone
|
Send information tone.
|
4
|
0x4
|
serv-not-implemented
|
Service not implemented.
|
79
|
0x4f
|
serv/opt-unavail-unspecified
|
Service or option not available, unspecified.
|
63
|
0x3f
|
stat-enquiry-resp
|
Response to status enquiry.
|
30
|
0x1e
|
subscriber-absent
|
Subscriber absent.
|
20
|
0x14
|
switch-congestion
|
Switch congestion.
|
42
|
0x2a
|
temp-fail
|
Temporary failure.
|
41
|
0x29
|
transit-net-unroutable
|
No route to transit network.
|
2
|
0x2
|
unassigned-number
|
Unassigned number.
|
1
|
0x1
|
unknown-param-msg-discard
|
Unrecognized parameter message discarded.
|
110
|
0x6e
|
unsupported-aal-parms
|
ATM adaptation layer (AAL) parameters not supported.
|
93
|
0x5d
|
user-busy
|
User busy.
|
17
|
0x11
|
vpci-vci-assign-fail
|
Virtual path connection identifier virtual channel identifier (VPCI VCI) assignment failure.
|
36
|
0x24
|
vpci-vci-unavail
|
No VPCI VCI available.
|
45
|
0x2d
|
Examples
The following example configures the originating or tandem router to continue dial-peer hunting if it receives a user-busy disconnect cause code from a destination router:
The following example configures the originating or tandem router to continue dial-peer hunting if it receives an invalid-number disconnect cause code from a destination router:
The following example configures the originating or tandem router to continue dial-peer hunting if it receives a facility-not-subscribed disconnect cause code from a destination router:
Related Commands
Command
|
Description
|
huntstop
|
Disables all further dial-peer hunting if a call fails when using hunt groups.
|
preference
|
Indicates the preferred order of a dial peer within a rotary hunt group.
|
voice iec syslog
To enable viewing of Internal Error Codes as they are encountered in real time, use the voice iec syslog command in global configuration mode. To disable IEC syslog messages, use the no form of this command.
voice iec syslog
no voice iec syslog
Syntax Description
This command has no arguments or keywords.
Command Default
IEC syslog messages are disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Examples
The following example enables IEC syslog messages:
router(config)# voice iec syslog
Related Commands
Command
|
Description
|
clear voice statistics
|
Clears voice statistics, resetting the statistics collection.
|
show voice statistics iec
|
Displays iec statistics
|
show voice statistics interval-tag
|
Displays interval options available for IEC statistics
|
voice statistics type iec
|
Enables collection of IEC statistics
|
voice local-bypass
To configure local calls to bypass the digital signal processor (DSP), use the voice local-bypass command in global configuration mode. To direct local calls through the DSP, use the no form of this command.
voice local-bypass
no voice local-bypass
Syntax Description
This command has no arguments or keywords.
Command Default
Local calls bypass the DSP.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3(1)MA
|
This command was introduced.
|
12.0(7)XK
|
This command was implemented on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
Usage Guidelines
Local calls (calls between voice ports on a router or concentrator) normally bypass the DSP to minimize use of system resources. Use the no form of the voice local-bypass command if you need to direct local calls through the DSP. Input gain and output attenuation can be configured only if calls are directed through the DSP.
Examples
The following example configures a Cisco router to pass local calls through the DSP:
Related Commands
Command
|
Description
|
input gain
|
Configures a specific input gain value.
|
output attenuation
|
Configures a specific output attenuation value.
|
voicemail (stcapp-fsd)
To designate an SCCP telephony control (STC) application feature speed-dial code to speed dial the voice-mail number, use the voicemail command in STC application feature speed-dial configuration mode. To return the code to its default, use the no form of this command.
voicemail keypad-character
no voicemail
Syntax Description
keypad-character
|
One or two digits that can be dialed on a telephone keypad. Range is 0 to 9 for one-digit codes; 00 to 99 for two-digit codes. Default is 0 (zero) for one-digit codes; 00 (two zeroes) for two-digit codes.
Note Number of digits depends on the value set with the digit command.
|
Command Default
The default voice-mail code is 0 (zero) for one-digit codes; 00 (two zeros) for two-digit codes.
Command Modes
STC application feature speed-dial configuration
Command History
Release
|
Modification
|
12.4(2)T
|
This command was introduced.
|
12.4(6)T
|
The keypad-character argument was modified to allow two-digit codes.
|
Usage Guidelines
This command is used with the STC application, which enables certain features on analog FXS endpoints that use Skinny Client Control Protocol (SCCP) for call control.
To use the speed-dial to voice-mail feature on a phone, dial the feature speed-dial (FSD) prefix and the code that has been configured with this command (or the default if this command was not used). For example, if the FSD prefix is * (the default), and you want to dial the voice-mail phone number, dial *0.
Note that the number that will be speed-dialed for voice mail must be set on Cisco CallManager or the Cisco CallManager Express system.
This command is reset to its default value if you modify the value of the digit command. For example, if you set the digit command to 2, then change the digit command back to its default of 1, the voice-mail FSD code is reset to 0 (zero).
If you set this code to a value that is already in use for another FSD code, you receive a warning message. If you configure a duplicate code, the system implements the first matching feature in the order of precedence shown in the output of the show stcapp feature codes command.
The show running-config command displays nondefault FSD codes only. The show stcapp feature codes command displays all FSD codes.
Examples
The following example sets an FSD prefix of two pound signs (##) and a voice-mail code of 8. After these values have been configured, a phone user presses ##8 to dial the voice-mail number.
Router(config)# stcapp feature speed-dial
Router(stcapp-fsd)# prefix ##
Router(stcapp-fsd)# voicemail 8
Related Commands
Command
|
Description
|
digit
|
Designates the number of digits for STC application feature speed-dial codes.
|
prefix (stcapp-fsd)
|
Designates a prefix to precede the dialing of an STC application feature speed-dial code.
|
redial
|
Designates an STC application feature speed-dial code to dial again the last number that was dialed.
|
show running-config
|
Displays current nondefault configuration settings.
|
show stcapp feature codes
|
Displays configured and default STC application feature codes.
|
speed dial
|
Designates a range of STC application feature speed-dial codes.
|
stcapp feature speed-dial
|
Enters STC application feature speed-dial configuration mode to set feature speed-dial codes.
|
voiceport
To enable a private line automatic ringdown (PLAR) connection for an analog phone, use the voiceport command in SCCP PLAR configuration mode. To remove PLAR from the voice port, use the no form of this command.
voiceport port-number dial dial-string [digit dtmf-digits [wait-connect wait-msecs] [interval
inter-digit-msecs]]
no voiceport port-number
Syntax Description
port-number
|
Analog foreign exchange station (FXS) voice port number. Range: 2/0 to 2/23.
|
dial dial-string
|
String of up to 16 characters that can be dialed on a telephone keypad. Valid characters are 0 through 9, A through D, an * (asterisk) and # (pound sign). The voice gateway sends this string to the call-control system when the analog phone goes off hook.
|
digit dtmf-digits
|
(Optional) String of up to 16 characters that can be dialed on a telephone keypad. Valid characters are 0 through 9, A through D, an * (asterisk), # (pound sign), and comma (,). The voice gateway sends this string to the call-control system after the wait-msecs expires. Each comma represents a one second wait.
|
wait-connect wait-msecs
|
(Optional) Number of milliseconds that the voice gateway waits after voice cut-through before out-pulsing the DTMF digits. Range: 0 to 30000, in multiples of 50. Default: 50. If 0, DTMF digits are sent automatically by voice gateway after call is connected.
|
interval inter-digit-msecs
|
(Optional) Number of milliseconds between the DTMF digits. Range: 50 to 500, in multiples of 50. Default: 50.
|
Command Default
Disabled (PLAR is not set for the voice port).
Command Modes
SCCP PLAR configuration
Command History
Release
|
Modification
|
12.4(6)T
|
This command was introduced.
|
Usage Guidelines
This command enables PLAR on analog FXS ports that use Skinny Client Control Protocol (SCCP) for call control. If the digit keyword is not used, DTMF digits are not out-pulsed; the voice port uses a simple PLAR connection and the other keywords are not available.
Voice ports can be configured in any order. For example, you can configure port 2/23 before port 2/0. The show running-config command lists the ports in ascending order.
Before a PLAR port can become operational, the STC application must first be enabled in the corresponding dial-peer using the service stcapp command. If you configure a port for PLAR before enabling the STC application in the dial peer you receive a warning message.
PLAR phones support most of the same features as normal analog phones. The PLAR phone handles incoming calls and supports hookflash for basic supplementary features such as call transfer, call waiting, and conference. The PLAR phone does not support other features such as call forwarding, redial, speed dial, call park, call pick up from a PLAR phone, AMWI, or caller ID.
Examples
The following example enables the PLAR feature on port 2/0, 2/1, and 2/3. When a phone user picks up the handset on the analog phone connected to port 2/0, the system automatically rings extension 3660 and after waiting 500 milliseconds, dials 1234. The DTMF digits are out-pulsed to the destination port at an interval of 200 milliseconds.
Router(config)# sccp plar
Router(config-sccp-plar)# voiceport 2/0 dial 3660 digit 1234 wait-connect 500 interval 200
Router(config-sccp-plar)# voiceport 2/1 dial 3264 digit 678,,,9*0,,#123 interval 100
Router(config-sccp-plar)# voiceport 2/3 dial 3478 digit 34567 wait-connect 500
Related Commands
Command
|
Description
|
dial-peer voice
|
Enters dial peer configuration mode and defines a dial peer.
|
sccp plar
|
Enters SCCP PLAR configuration mode.
|
voice-port
To enter voice-port configuration mode, use the voice-port command in global configuration mode.
Cisco 1750 and Cisco 1751
voice-port slot-number/port
Cisco 2600 series, Cisco 3600 Series, and Cisco 7200 Series
voice-port {slot-number/subunit-number/port | slot/port:ds0-group-no}
Cisco 2600 and Cisco 3600 Series with a High-Density Analog Network Module (NM-HDA)
voice-port {slot-number/subunit-number/port}
Cisco AS5300
voice-port controller-number:D
Syntax Description
Cisco 1750 and Cisco 1751
slot-number
|
Number of the slot in the router in which the voice interface card (VIC) is installed. Valid entries are from 0 to 2, depending on the slot in which it has been installed.
|
port
|
Voice port number. Valid entries are 0 and 1.
|
Cisco 2600 series, Cisco 3600 Series, and Cisco 7200 Series
slot-number
|
Number of the slot in the router in which the VIC is installed. Valid entries are from 0 to 3, depending on the slot in which it has been installed.
|
subunit-number
|
Subunit on the VIC in which the voice port is located. Valid entries are 0 or 1.
|
port
|
Voice port number. Valid entries are 0 and 1.
|
slot
|
The router location in which the voice port adapter is installed. Valid entries are from 0 to 3.
|
port:
|
Indicates the voice interface card location. Valid entries are 0 and 3.
|
ds0-group-no
|
Indicates the defined DS0 group number. Each defined DS0 group number is represented on a separate voice port. This allows you to define individual DS0s on the digital T1/E1 card.
|
Cisco AS5300:
controller-number
|
T1 or E1 controller.
|
:D
|
D channel associated with ISDN PRI.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3(1)T
|
This command was introduced.
|
11.3(3)T
|
This command was implemented on the Cisco 2600 series.
|
12.0(3)T
|
This command was implemented on the Cisco AS5300.
|
12.0(7)T
|
This command was implemented on the Cisco AS5800, Cisco 7200 series, and Cisco 1750. Arguments were added for the Cisco 2600 series and Cisco 3600 series.
|
12.2(8)T
|
This command was implemented on Cisco 1751 and Cisco 1760. This command was modified to accommodate the additional ports of the NM-HDA on the Cisco 2600 series, Cisco 3640, and Cisco 3660.
|
12.2(2)XN
|
Support for enhanced MGCP voice gateway interoperability was added to Cisco CallManager Version 3.1 for the Cisco 2600 series, Cisco 3600 series, and Cisco VG200.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T and Cisco CallManager Version 3.2 and implemented on the Cisco IAD2420 series.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T. This command does not support the extended echo canceller (EC) feature on the Cisco AS5300 or the Cisco AS5800.
|
Usage Guidelines
Use the voice-port global configuration command to switch to voice-port configuration mode from global configuration mode. Use the exit command to exit voice-port configuration mode and return to global configuration mode.
Note
This command does not support the extended echo canceller (EC) feature on the Cisco AS5300.
Examples
The following example accesses voice-port configuration mode for port 0, located on subunit 0 on a VIC installed in slot 1:
The following example accesses voice-port configuration mode for a Cisco AS5300:
Related Commands
Command
|
Description
|
dial-peer voice
|
Enters dial peer configuration mode and specifies the method of voice encapsulation.
|
voice-port (MGCP profile)
The voice-port (MGCP profile) command is replaced by the port (MGCP profile) command in Cisco IOS Release 12.2(8)T. See the port (MGCP profile) command for more information.
voice-port busyout
To place all voice ports associated with a serial or ATM interface into a busyout state, use the voice-port busyout command in interface configuration mode. To remove the busyout state on the voice ports associated with this interface, use the no form of this command.
voice-port busyout
no voice-port busyout
Syntax Description
This command has no arguments or keywords.
Command Default
The voice ports on the interface are not in busyout state.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced on Cisco MC3810.
|
Usage Guidelines
This command busies out all voice ports associated with the interface, except any voice ports configured to busy out under specific conditions using the busyout monitor and busyout seize commands.
Examples
The following example places the voice ports associated with serial interface 1 into busyout state:
interface serial 1
voice-port busyout
The following example places the voice ports associated with ATM interface 0 into busyout state:
Related Commands
Command
|
Description
|
busyout forced
|
Forces a voice port into the busyout state.
|
busyout monitor
|
Places a voice port into the busyout monitor state.
|
busyout seize
|
Changes the busyout action for an FXO or FXS voice port.
|
show voice busyout
|
Displays information about the voice busyout state.
|
voice rtp send-recv
To establish a two-way voice path when the Real-Time Transport Protocol (RTP) channel is opened, use the voice rtp send-recv command in global configuration mode. To reset to the default, use the no form of this command.
voice rtp send-recv
no voice rtp send-recv
Syntax Description
This command has no arguments or keywords.
Command Default
The voice path is cut-through in only the backward direction when the RTP channel is opened.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced on Cisco 2600, Cisco 3600, Cisco 7200, Cisco 7500, Cisco AS5300, Cisco AS5800, and Cisco MC3810 platforms.
|
12.2(2)XA
|
This command was implemented on the Cisco AS5350 and Cisco AS5400.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850.
|
12.2(11)T
|
This command was integrated into the Cisco IOS Release 12.2(11)T.
|
Usage Guidelines
This command should be enabled only when the voice path must be cut-through (established) in both the backward and forward directions before a Connect message is received from the destination switch. This command affects all VoIP calls when it is enabled.
Examples
The following example enables the voice path to cut-through in both directions when the RTP channel is opened:
voice service
To enter voice-service configuration mode and to specify a voice-encapsulation type, use the voice service command in global configuration mode.
voice service {pots | voatm | vofr | voip}
Syntax Description
pots
|
Telephony voice service.
|
voatm
|
Voice over ATM (VoATM) encapsulation.
|
vofr
|
Voice over Frame Relay (VoFR) encapsulation.
|
voip
|
Voice over IP (VoIP) encapsulation.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.1(1)XA
|
This command was introduced on the Cisco MC3810.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.1(3)T
|
This command was integrated into Cisco IOS Release 12.1(3)T for VoIP on the Cisco 2600 series and the Cisco 3600 series.
|
12.1(3)XI
|
This command was implemented on the Cisco AS5300.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
12.1(5)XM
|
This command was implemented on the Cisco AS5800.
|
12.1(5)XM2
|
This command was implemented on the Cisco AS5350 and Cisco AS5400.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T and implemented on the Cisco 7200 series.
|
12.2(11)T
|
This command was implemented on the Cisco AS5350, Cisco AS5400, Cisco AS5800, and Cisco AS5850.
|
Usage Guidelines
Voice-service configuration mode is used for packet telephony service commands that affect the gateway globally.
Examples
The following example enters voice-service configuration mode for VoATM service commands:
voice source-group
To define a source IP group for voice calls, use the voice source-group command in global configuration mode. To delete the source IP group, use the no form of this command.
voice source-group name
no voice source-group name
Syntax Description
name
|
Name of the IP group. Maximum length of the source IP group name is 31 alphanumeric characters.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced.
|
Usage Guidelines
Use the voice source-group command to assign a name to a set of source IP group characteristics. The terminating gateway uses these characteristics to identify and translate the incoming VoIP call.
Carrier IDs and trunk group labels must not have the same names.
Do not mix carrier IDs and trunk group labels within a source IP group.
A terminating gateway can be configured with carrier ID source IP groups and trunk-group-label source IP groups. The name of the source IP group must be unique to the gateway.
Examples
The following example initiates source IP group "utah2" for VoIP calls:
Router(config)# voice source-group utah2
Related Commands
Command
|
Description
|
access-list
|
Defines a list of source groups for identifying incoming calls.
|
carrier-id (voice source group)
|
Specifies the carrier handling a VoIP call.
|
description (voice source group)
|
Assigns a disconnect cause to a source IP group.
|
h323zone-id (voice source group)
|
Assigns a zone ID to an incoming H.323 call.
|
translation-profile (source group)
|
Assigns a translation profile to a source IP group.
|
trunk-group-label (voice source group)
|
Specifies the trunk handling a VoIP call.
|
voice statistics accounting method
To enable voice accounting statistics to be collected for a specific accounting method list and to specify the pass criteria for call legs, use the voice statistics accounting method command in global configuration mode. To disable the collection of statistics for the accounting method, use the no form of this command.
voice statistics accounting method method-list-name pass {start-interim-stop | start-stop |
stop-only}
no voice statistics accounting method method-list-name pass {start-interim-stop | start-stop |
stop-only}
Syntax Description
method-list-name
|
Name of the accounting method list. The method-list-name argument is the same as that configured using the method command in gateway accounting AAA configuration mode.
|
pass
|
The pass criteria for call legs (PSTN or IP) and call directions (inbound or outbound) that is used by the method list.
Note The definition of pass implies that all start, stop, or interim messages are acknowledged by the designated servers. The definition of failure implies that any start, stop, or interim message is rejected or is timed out by the designated servers.
|
start-interim-stop
|
All start, interim, and stop pass criteria records are counted.
|
start-stop
|
All start and stop pass criteria records are counted.
|
stop-only
|
Only stop pass criteria records are counted.
|
Command Default
No statistics for the specified accounting method list are collected.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Examples
The following example shows that h323 is specified as the method list and that the pass criterion is stop-only:
Router(config)# voice statistics accounting method h323 pass stop-only
Related Commands
Command
|
Description
|
method
|
Specifies the AAA method list name to be used.
|
show voice statistics csr interval accounting
|
Displays statistical information by configured intervals for accounting statistics.
|
show voice statistics csr since-reset accounting
|
Displays all accounting CSRs since the last reset.
|
voice statistics display-format separator
|
Specifies the format for CSR display.
|
voice statistics field-params
|
Specifies MCD, lost-packet, packet-latency, and packet-jitter parameters.
|
voice statistics max-storage-duration
|
Specifies the maximum time for which CSRs are stored in system memory.
|
voice statistics push
|
Specifies an FTP or syslog server for downloading CSRs, the maximum file size, and the maximum message size.
|
voice statistics time-range
|
Specifies the time range to collect CSRs.
|
voice statistics type
|
Enables the collection of accounting and signaling CSRs.
|
voice statistics display-format separator
To configure the display format of the statistics on the gateway, use the voice statistics display-format separator command in global configuration mode. To return the display format of the statistics to the default value, use the no form of this command.
voice statistics display-format separator {space | tab | new-line | char char}
no voice statistics display-format separator {space | tab | new-line | char char}
Syntax Description
separator
|
Type of separator used in the displayed format.
|
space
|
A space is used for the formatting between each statistic in the displayed output.
|
tab
|
A tab is used for the formatting between each statistic in the displayed output.
|
new-line
|
A new line is used for the formatting between each statistic in the displayed output.
|
char char
|
A character is used for the formatting between each statistic in the displayed output. The char argument is a visible ASCII character used for the formatting between each statistic in the displayed output.
|
Command Default
A comma (,) is the default separator.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Examples
The following example shows that a space is specified as the display separator:
Router(config)# voice statistics display-format separator space
Related Commands
Command
|
Description
|
voice statistics accounting method
|
Enables the accounting method and the pass and fail criteria.
|
voice statistics field-params
|
Specifies MCD, lost-packet, packet-latency, and packet-jitter parameters.
|
voice statistics max-storage-duration
|
Specifies the maximum time for which CSRs are stored in system memory.
|
voice statistics push
|
Specifies an FTP or syslog server for downloading CSRs, the maximum file size, and the maximum message size.
|
voice statistics time-range
|
Specifies the time range to collect CSRs.
|
voice statistics type
|
Enables the collection of accounting and signaling CSRs.
|
voice statistics field-params
To configure the parameters of call statistics fields on the gateway, use the voice statistics field-params command in global configuration mode. To return the call statistics parameters to the default values, use the no form of this command.
voice statistics field-params {mcd value | lost-packet value | packet-latency value | packet-jitter
value}
no voice statistics field-params {mcd value | lost-packet value | packet-latency value |
packet-jitter value}
Syntax Description
mcd
|
Minimum call duration. The value argument is an integer that represents the number of milliseconds. Valid values are from 0 to 30. The default is 2.
|
lost-packet
|
Lost voice packet threshold. The value argument is an integer that represents milliseconds. Valid values are from 0 to 65535. The default is 1000.
|
packet-latency
|
Voice packet latency threshold. The value argument is an integer that represents milliseconds. Valid values are from 0 to 500. The default is 250.
|
packet-jitter
|
Voice packet jitter threshold. The value argument is an integer that represents milliseconds. Valid values are from 0 to 1000. The default is 250.
|
Command Default
MCD is 2 milliseconds.
Lost packet threshold is 1000 milliseconds.
Packet latency threshold is 250 milliseconds.
Packet jitter threshold is 250 milliseconds.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Examples
The following example configures a minimum call duration of 5 milliseconds:
Router(config)# voice statistics field-params mcd 5
The following example configures a lost packet threshold of 250 milliseconds:
Router(config)# voice statistics field-params lost-packet 250
The following example configures a packet-latency threshold of 300 milliseconds:
Router(config)# voice statistics field-params packet-latency 300
The following example configures a packet-jitter threshold of 245 milliseconds:
Router(config)# voice statistics field-params packet-jitter 245
Related Commands
Command
|
Description
|
voice statistics accounting method
|
Enables the accounting method and the pass and fail criteria.
|
voice statistics display-format separator
|
Specifies the format for CSR display.
|
voice statistics max-storage-duration
|
Specifies the maximum time for which CSRs are stored in system memory.
|
voice statistics push
|
Specifies an FTP or syslog server for downloading CSRs, the maximum file size, and the maximum message size.
|
voice statistics time-range
|
Specifies the time range to collect CSRs.
|
voice statistics type
|
Enables the collection of accounting and signaling CSRs.
|
voice statistics max-storage-duration
To configure the maximum amount of time for which collected statistics are stored in the system memory of the gateway, use the voice statistics max-storage-duration command in global configuration mode. To remove the configured maximum storage duration, use the no form of this command.
voice statistics max-storage-duration {day value | hour value | minute value}
no voice statistics max-storage-duration {day value | hour value | minute value}
Syntax Description
day value
|
Number of days for which call statistics data are to be stored. The value argument has a valid range from 0 to 365.
|
hour value
|
Number of hours for which call statistics data are to be stored. The value argument has a valid range from 0 to 720.
|
minute value
|
Number of minutes for which call statistics data are to be stored. The value argument has a valid range from 0 to 1440.
|
Command Default
If no length of time is configured, no memory is allocated for those call statistic records that have stopped after the end of their collection intervals. If no memory is allocated, only active call statistic record buffers are kept in system memory.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
The maximum storage duration means the time-to-exist duration of the call statistic records on the gateway.
The values entered using this command also apply to the collection of VoIP internal error codes (IECs).
Examples
The following example shows that the maximum storage duration for the collection of voice call statistics has been set for 60 minutes:
Router(config)# voice statistics max-storage-duration minute 60
Related Commands
Command
|
Description
|
voice statistics accounting method
|
Enables the accounting method and the pass and fail criteria.
|
voice statistics display-format separator
|
Specifies the format for CSR display.
|
voice statistics field-params
|
Specifies MCD, lost-packet, packet-latency, and packet-jitter parameters.
|
voice statistics push
|
Specifies an FTP or syslog server for downloading CSRs, the maximum file size, and the maximum message size.
|
voice statistics time-range
|
Specifies the time range to collect CSRs.
|
voice statistics type
|
Enables the collection of accounting and signaling CSRs.
|
voice statistics push
To configure the method for pushing signaling statistics, VoIP AAA accounting statistics, or Cisco internal error codes (IECs) to an FTP or syslog server, use the voice statistics push command in global configuration mode. To disable the configured push method, use the no form of this command.
voice statistics push {ftp url ftp-url [max-file-size value]} | {syslog [max-msg-size value]}
no voice statistics push {ftp url ftp-url [max-file-size value]} | {syslog [max-msg-size value]}
Syntax Description
ftp url ftp-url
|
URL of the FTP server to which voice statistics are to be pushed. The syntax of the ftp-url argument follows:
ftp://user:password@host:port//directory1/directory2
|
max-file-size value
|
(Optional) Maximum size of a voice statistics file to be pushed to an FTP server, in bytes. The valid range of the value argument is from 1024 to 4294967296. The default value is 400000000 (4 GB).
|
syslog
|
Voice statistics are pushed to a syslog server.
|
max-msg-size value
|
(Optional) Maximum size of a voice statistics file to be pushed to a syslog server, in bytes. The valid range of the value argument is from 1024 to 4294967296. The default value is 400000000 (4 GB).
|
Command Default
Voice statistics are not pushed to an FTP or syslog server.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
The gateway configuration should be consistent with the configuration on the FTP or syslog servers. This command may also be used to push Cisco VoIP internal error codes (IECs) to either an FTP server or a syslog server.
Examples
The following is a configuration example showing a specified FTP server and maximum file size:
Router(config)# voice statistics push ftp url ftp://john:doe@abc:23//directory1/directory2
max-file-size 10000
Related Commands
Command
|
Description
|
voice statistics accounting method
|
Enables the accounting method and the pass and fail criteria.
|
voice statistics display-format separator
|
Specifies the format for CSR display.
|
voice statistics field-params
|
Specifies MCD, lost-packet, packet-latency, and packet-jitter parameters.
|
voice statistics max-storage-duration
|
Specifies the maximum time for which CSRs are stored in system memory.
|
voice statistics time-range
|
Specifies the time range to collect CSRs.
|
voice statistics type
|
Enables the collection of accounting and signaling CSRs.
|
voice statistics time-range
To specify a time range to collect statistics from the gateway on a periodic basis, since the last reset, or for a specific time duration , use the voice statistics time-range command in global configuration mode. To disable the time-range settings, use the no form of this command.
Statistics Collection on a Periodic Basis
voice statistics time-range periodic interval start hh:mm {days-of-week {Monday | Tuesday |
Wednesday | Thursday | Friday | Saturday | Sunday | daily | weekdays | weekend}} [end
hh:mm {days-of-week {Monday | Tuesday | Wednesday | Thursday | Friday | Saturday |
Sunday}}]
no voice statistics time-range periodic interval start hh:mm {days-of-week {Monday | Tuesday
| Wednesday | Thursday | Friday | Saturday | Sunday | daily | weekdays | weekend}} [end
hh:mm {days-of-week {Monday | Tuesday | Wednesday | Thursday | Friday | Saturday |
Sunday}}]
Statistics Collection Since the Last Reset or Reboot of the Gateway
voice statistics time-range since-reset
no voice statistics time-range since-reset
Statistics Collection at a Specific Time Duration
voice statistics time-range specific start hh:mm day month year end hh:mm day month year
no voice statistics time-range specific start hh:mm day month year end hh:mm day month year
Syntax Description
Statistics Collection on a Periodic Basis:
|
periodic
|
Call statistics are collected for a configured period.
|
interval
|
Specifies the periodic interval during which statistics will be collected. Valid entries for this value are 5minutes, 15minutes, 30minutes, 60minutes, or 1day.
|
start/end
|
Specifies the start and ending periods of the statistics collection. If no end time is entered, then the statistics collection continues nonstop. By default, there is no end of the collection period.
|
hh:mm
|
Specifies the start and ending times for the periodic statistics collection in hours and minutes. The times entered must be in 24-hour format.
|
days-of-week
|
Specifies the start and ending days of the week that call statistics are collected. You can configure a specific day of the week, or one of the following:
• daily—Call statistics are collected daily.
• weekdays—Call statistics are collected on weekdays only.
• weekend—Call statistics are collected on weekends only.
The default value is daily.
|
Statistics Collection Since the Last Reset or Reboot of the Gateway
|
since-reset
|
Call statistics are collected only since a reset or reboot of the gateway.
Note Voice statistics collection on the gateway is reset using the clear voice statistics csr command.
|
Statistics Collection at a Specified Time Duration:
|
specific
|
Call statistics are collected for a specific time duration.
|
start/end
|
Specifies the start and end times of the statistics collection. The required arguments for both the start and end keywords are as follows:
• hh:mm—Hour and minute. The times entered must be in 24-hour format.
• day—Day of the month. Valid values are from 1 to 31.
• month—Month for the statistics collection to start. Enter the month name, for example, January, or February. The default is the current month.
• year—Year. Valid values are from 1993 to 2035. The default is the current year.
|
No statistics are collected by default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
There should be only one specific or periodic configuration at any one time. If a second specific or periodic configuration is configured, the request is rejected and a warning message displays. If the no form of the command is used during the specific time range, the corresponding collection will stop and FTP or syslog messages will not be sent.
Examples
The following example shows that the time range is periodic and set to collect statistics for a 60-minute period on weekdays only beginning at 12:00 a.m.:
Router(config)# voice statistics time-range periodic 60minutes start 12:00 days-of-week
weekdays
The following example configures the gateway to collect call statistics since the last reset (specified with the clear voice statistics csr command) or since the last time the gateway was rebooted:
Router(config)# voice statistics time-range since-reset
The following example configures the gateway to collect statistics from 10:00 a.m. on the first day of January to 12:00 a.m. on the second day of January:
Router(config)# voice statistics time-range specific start 10:00 1 January 2004 end 12:00
2 January 2004
Related Commands
Command
|
Description
|
clear voice statistics
|
Clears voice statistics, resetting the statistics collection.
|
voice statistics accounting method
|
Enables the accounting method and the pass and fail criteria.
|
voice statistics display-format separator
|
Specifies the format for CSR display.
|
voice statistics field-params
|
Specifies MCD, lost-packet, packet-latency, and packet-jitter parameters.
|
voice statistics max-storage-duration
|
Specifies the maximum time for which CSRs are stored in system memory.
|
voice statistics push
|
Specifies an FTP or syslog server for downloading CSRs, the maximum file size, and the maximum message size.
|
voice statistics type
|
Enables the collection of accounting and signaling CSRs.
|
voice statistics type csr
To configure a gateway to collect VoIP AAA accounting statistics or voice signaling statistics, independently or at the same time, use the voice statistics type csr command in global configuration mode. To disable the counters, use the no form of this command.
voice statistics type csr [accounting | signaling]
no voice statistics type csr [accounting | signaling]
Syntax Description
accounting
|
(Optional) VoIP AAA accounting statistics are collected.
|
signaling
|
(Optional) Voice signaling statistics are collected.
|
Command Default
No accounting or signaling call statistics records (CSRs) are collected on the gateway.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
If you do not specify a keyword, both accounting and signaling CSRs are collected. Accounting and signaling CSR collection can be enabled and disabled independently.
Examples
The following example shows that both types of CSRs will be collected:
Router(config)# voice statistics type csr
The following example enables accounting CSRs to be collected:
Router(config)# voice statistics type csr accounting
The following example enables signaling CSRs to be collected:
Router(config)# voice statistics type csr signaling
The following example disables the collection of both signaling and accounting CSRs:
Router(config)# no voice statistics type csr
The following example disables the collection of signaling CSRs only:
Router(config)# no voice statistics type csr signaling
Related Commands
Command
|
Description
|
voice statistics accounting method
|
Enables the accounting method and the pass and fail criteria.
|
voice statistics display-format separator
|
Specifies the format for CSR display.
|
voice statistics field-params
|
Specifies MCD, lost-packet, packet-latency, and packet-jitter parameters.
|
voice statistics max-storage-duration
|
Specifies the maximum time for which CSRs are stored in system memory.
|
voice statistics push
|
Specifies an FTP or syslog server for downloading CSRs, the maximum file size, and the maximum message size.
|
voice statistics time range
|
Specifies the time range to collect CSRs.
|
voice statistics type iec
To enable collection of Internal Error Code (IEC) statistics, use the voice statistics type iec command in global configuration mode. To disable IEC statistics collection, use the no form of this command.
voice statistics type iec
no voice statistics type iec
Syntax Description
This command has no arguments or keywords.
Command Default
IEC statistics collection is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Examples
The following example enables IEC statistics collection:
router(config)# voice statistics type iec
Related Commands
Command
|
Description
|
clear voice statistics
|
Clears voice statistics, resetting the statistics collection.
|
show voice statistics
|
Displays voice statistics
|
show voice statistics interval-tag
|
Displays interval options available for IEC statistics
|
voice statistics time-range since-reset
|
Enables collection of call statistics accumulated since the last resetting of IEC counters
|
voice translation-profile
To define a translation profile for voice calls, use the voice translation-profile command in global configuration mode. To delete the translation profile, use the no form of this command.
voice translation-profile name
no voice translation-profile name
Syntax Description
name
|
Name of the translation profile. Maximum length of the voice translation profile name is 31 alphanumeric characters.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced.
|
Usage Guidelines
After translation rules are defined, they are grouped into profiles. The profiles collect a set of rules that, taken together, translate the called, calling, and redirected numbers in specific ways. Up to 1000 profiles can be defined. Each profile must have a unique name.
These profiles are referenced by trunk groups, dial peers, source IP groups, voice ports, and interfaces for handling call translations.
Examples
The following example initiates translation profile "westcoast" for voice calls. The profile uses translation rules 1, 2, and 3 for various types of calls.
Router(config)# voice translation-profile westcoast
Router(cfg-translation-profile)# translate calling 2
Router(cfg-translation-profile)# translate called 1
Router(cfg-translation-profile)# translate redirect-called 3
Related Commands
Command
|
Description
|
rule (voice translation-rule)
|
Defines call translation criteria.
|
show voice translation-profile
|
Displays one or more translation profiles.
|
translate (translation profiles)
|
Associates a translation rule with a voice translation profile.
|
voice translation-rule
To define a translation rule for voice calls, use the voice translation-rule command in global configuration mode. To delete the translation rule, use the no form of this command.
voice translation-rule number
no voice translation-rule number
Syntax Description
number
|
Number that identifies the translation rule. Range is from1 to 2147483647.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced.
|
Usage Guidelines
Use the voice translation-rule command to create the definition of a translation rule. Each definition includes up to 15 rules that include SED-like expressions for processing the call translation. A maximum of 128 translation rules are supported.
These translation rules are grouped into profiles that are referenced by trunk groups, dial peers, source IP groups, voice ports, and interfaces.
Examples
The following example initiates translation rule 150, Which includes two rules:
Router(config)# voice translation-rule 150
Router(cfg-translation-rule)# rule 1 reject /^408\(.(\)/
Router(cfg-translation-rule)# rule 2 /\(^...\)853\(...\)/ /\1525\2/
Related Commands
Command
|
Description
|
rule (voice translation-rule)
|
Defines the matching, replacement, and rejection patterns for a translation rule.
|
show voice translation-rule
|
Displays the configuration of a translation rule.
|
voice vad-time
To change the minimum silence detection time for voice activity detection (VAD), use the voice vad-time command in global configuration mode. To reset to the default, use the no form of this command.
voice vad-time milliseconds
no voice vad-time
Syntax Description
milliseconds
|
Waiting period, in milliseconds, before silence detection and suppression of voice-packet transmission. Range is from 250 to 65536. The default is 250.
|
Command Default
250 milliseconds
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(7)XK
|
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
Usage Guidelines
This command affects all voice ports on a router or concentrator, but it does not affect calls already in progress.
You can use this command in transparent common-channel signaling (CCS) applications in which you want VAD to activate when the voice channel is idle, but not during active calls. With a longer silence detection delay, VAD reacts to the silence of an idle voice channel, but not to pauses in conversation.
This command does not affect voice codecs that have ITU-standardized built-in VAD features—for example, G.729B, G.729AB, G.723.1A. The VAD behavior and parameters of these codecs are defined exclusively by the applicable ITU standard.
Examples
The following example configures a 20-second delay before VAD silence detection is enabled:
Related Commands
Command
|
Description
|
vad (dial peer)
|
Enables voice activity detection on a network dial peer.
|
voice vrf
To configure a voice VRF, use the voice vrf command in global configuration mode. To remove the voice VRF configuration, use the no form of this command.
voice vrf vrfname
no voice vrf vrfname
Syntax Description
vrfname
|
A name assigned to the voice vrf.
|
Command Default
No voice VRF is configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.4(11)XJ
|
This command was introduced.
|
12.4(15)T
|
This command was integrated into Cisco IOS Release 12.4(15)T.
|
Usage Guidelines
You must create a VRF using the ip vrf vrfname command before you can configure it as a voice VRF.
To ensure there are no active calls on the voice gateway during a VRF change, voices services must be shut down on the voice gateway before you configure or make changes to a voice VRF.
Examples
The following example shows that a VRF called vrf1 was created and then configured as a voice VRF:
Related Commands
Command
|
Description
|
ip vrf
|
Defines a VPN VRF instance and enters VRF configuration mode.
|
voip-incoming translation-profile
To specify a translation profile for all incoming VoIP calls, use the voip-incoming translation-profile command in global configuration mode. To delete the profile, use the no form of this command.
voip-incoming translation-profile name
no voip-incoming translation-profile name
Syntax Description
name
|
Name of the translation profile.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced.
|
Usage Guidelines
Use the voip-incoming translation-profile command to globally assign a translation profile for all incoming VoIP calls. The translation profile was previously defined using the voice translation-profile command. The voip-incoming translation-profile command does not require additional steps to complete its definition.
If an H.323 call comes in and the call is associated with a source IP group that is defined with a translation profile, the source IP group translation profile overrides the global translation profile.
Examples
The following example assigns the translation profile named "global-definition" to all incoming VoIP calls:
Router(config)# voip-incoming translation-profile global-definition
Related Commands
Command
|
Description
|
show voice translation-profile
|
Displays the configurations for all voice translation profiles.
|
test voice translation-rule
|
Tests the voice translation rule definition.
|
voice translation-profile
|
Initiates a translation profile definition.
|
voip-incoming translation-rule
To set the incoming translation rule for calls that originate from H.323-compatible clients, use the voip-incoming translation-rule command in global configuration mode. To disable the incoming translation rule, use the no form of this command.
voip-incoming translation-rule {calling | called} name-tag
no voip-incoming translation-rule {calling | called} name-tag
Syntax Description
name-tag
|
Tag number by which the rule set is referenced. This is an arbitrarily chosen number. Range is from 1 to 2147483647. There is no default value.
|
calling
|
Automatic number identification (ANI) number or the number of the calling party.
|
called
|
Dial Number Information Service (DNIS) number or the number of the called party.
|
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(7)XR1
|
This command was introduced for VoIP on the Cisco AS5300.
|
12.0(7)XK
|
This command was implemented for VoIP on the Cisco 2600 series, Cisco 3600 series and Cisco MC3810.
|
12.1(1)T
|
This command was integrated into Cisco IOS Release 12.1(1)T and implemented for VoIP on the Cisco 1750, Cisco AS5300, Cisco 7200, and Cisco 7500 platforms.
|
12.1(2)T
|
This command was implemented for VoIP on Cisco MC3810.
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850.
|
12.2(11)T
|
This command was integrated into Cisco IOS Release 12.2(11)T.
|
Usage Guidelines
With this command, all IP-based calls are captured and handled, depending on either the calling number or the called number to the specified tag name.
Examples
The following example identifies the rule set for calls that originate from H.323-compatible clients:
Router(config)# voip-incoming translation-rule called 5
Related Commands
Command
|
Description
|
numbering-type
|
Matches one number type for a dial-peer call leg.
|
rule
|
Applies a translation rule to a calling party number or a called party number for both incoming and outgoing calls.
|
show translation-rule
|
Displays the contents of all the rules that have been configured for a specific translation name.
|
test translation-rule
|
Tests the execution of the translation rules on a specific name-tag.
|
translate
|
Applies a translation rule to a calling party number or a called party number for incoming calls.
|
translate-outgoing
|
Applies a translation rule to a calling party number or a called party number for outgoing calls.
|
translation-rule
|
Creates a translation name and enters translation-rule configuration mode.
|
volume
To set the receiver volume level for a POTS port on a router, use the volume command in dial peer voice configuration mode. To reset to the default, use the no form of this command.
volume number
no volume number
Syntax Description
number
|
A number from 1 to 5 representing decibels (dB) of gain. Range is as follows:
• 1: -11.99 dB
• 2: -9.7dB
• 3: -7.7dB
• 4: -5.7dB
• 5: -3.7dB
Default is 3 (-7.7 dB gain).
|
Command Default
3 (-7.7 dB gain)
Command Modes
Dial peer voice configuration
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced on Cisco 803, Cisco 804, and Cisco 813 routers.
|
Usage Guidelines
Set the volume command for each POTS port separately. Setting the volume level affects only the port for which it has been set.
Note
Only the receiver volume is set with this command.
Use the show pots volume command to check the volume status and level.
Examples
The following example shows a volume level of 4 for POTS port 1 and a volume level of 2 for POTS port 2.
destination-pattern 5551111
destination-pattern 5552222
Related Commands
Command
|
Description
|
show pots volume
|
Shows the receiver volume configured for each POTS port on a router.
|
vxml audioerror
To enable throwing an error event when audio playout fails, use the vxml audioerror command in global configuration mode. To return to the default, use the no form of this command.
vxml audioerror
no vxml audioerror
Syntax Description
This command has no arguments or keywords.
Command Default
An audio error event, error.badfetch, is not thrown when an audio file cannot be played.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.4(11)T
|
This command was introduced.
|
Usage Guidelines
Entering this command causes an audio error event, error.badfetch, to be thrown when an audio file cannot be played, for instance, because the file is in an unsupported format, the src attribute references an invalid URI, or the expr attribute evaluates to an invalid URI.
The vxml audioerror command overrides the vxml version 2.0 command, so that if both commands are entered, the audio error event will be thrown when an audio file cannot be played.
Examples
The following example enables the audio error feature:
Router(config)# vxml audioerror
Related Commands
Command
|
Description
|
vxml version pre2.0
|
Enables features compatible with versions earlier than VoiceXML 2.0.
|
vxml tree memory
To set the maximum memory size for the VoiceXML parser tree, use the vxml tree memory command in global configuration mode. To reset to the default, use the no form of this command.
vxml tree memory size
no vxml tree memory
Syntax Description
size
|
Maximum memory size, in kilobytes. Range is 64 to 100000. Default is 1000.
|
Defaults
1000 KB
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
12.4(15)T
|
The default was changed from 64 to 1000.
|
Usage Guidelines
This command limits the memory resources available for parsing VoiceXML documents, preventing large documents from consuming excessive system memory. Increasing the maximum memory size for the VoiceXML tree enables calls to use larger VoiceXML documents. If a VoiceXML document exceeds the limit, the gateway aborts the document execution and the debug vxml error command displays a "vxml malloc fail" error.
Note
In Cisco IOS Release 12.3(4)T and later releases, less memory is consumed when parsing a VoiceXML document because the document is not stored by the VoiceXML tree.
Examples
The following example sets the maximum memory size to 128 KB:
Related Commands
Command
|
Description
|
debug vxml error
|
Displays VoiceXML application error messages.
|
ivr prompt memory
|
Sets the maximum amount of memory that dynamic audio files (prompts) occupy in memory.
|
ivr record memory system
|
Sets the maximum amount of memory for storing all voice recordings on the gateway.
|
vxml version 2.0
To enable VoiceXML 2.0 features, use the vxml version 2.0 command in global configuration mode. To return to the default, use the no form of this command.
vxml version 2.0
no vxml version 2.0
Syntax Description
This command has no arguments or keywords.
Command Default
The default VoiceXML behavior is compatible with versions earlier than W3C VoiceXML 2.0 Specification.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.4(11)T
|
This command was introduced.
|
Usage Guidelines
This command enables the following VoiceXML features:
•
An audio error event, error.badfetch, is not thrown when an audio file cannot be played, for instance, because the file is in an unsupported format, the src attribute references an invalid URI, or the expr attribute evaluates to an invalid URI.
•
Support for the beep attribute of the <record> element.
•
Blind transfer compliant with W3C VoiceXML 2.0 and not the same as consultation transfer.
•
Compatibility with W3C VoiceXML 2.0 Specification.
Examples
The following example enables VoiceXML version 2.0 features:
Router(config)# vxml version 2.0