-
Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2
-
Read me
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Cisco IOS Voice, Video, and Fax Commands: A through C
-
Cisco IOS Voice, Video, and Fax Commands: D through F
-
Cisco IOS Voice, Video, and Fax Commands: G through P
-
Cisco IOS Voice, Video, and Fax Commands: R through Sh
-
Cisco IOS Voice, Video, and Fax Commands: Si through Z
-
Index
-
Table Of Contents
Cisco IOS Voice, Video, and Fax Commands:
Si Through Zsignal timing idle suppress-voice
signal timing oos slave-standby
signal timing oos suppress-all
signal timing oos suppress-voice
snmp enable peer-trap poor-qov
supervisory disconnect anytone
supervisory disconnect dualtone voice-class
voice call convert-discpi-to-prog
voice-class permanent (dial-peer)
voice-class permanent (voice-port)
voip-incoming translation-rule
Cisco IOS Voice, Video, and Fax Commands:
Si Through Z
This chapter presents the commands to configure and maintain Cisco IOS voice, video, and fax applications. The commands are presented in alphabetical order beginning with Si. Some commands required for configuring voice, video, and fax may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice, Video, and Fax Configuration Guide.
signal
To specify the type of signaling for a voice port, use the signal command in voice-port configuration mode. To restore the default value for this command, use the no form of this command.
FXO and FXS Voice Ports
signal {loop-start | ground-start}
no signal {loop-start | ground-start}
E&M Voice Ports
signal {wink-start | immediate | delay-dial}
no signal {wink-start | immediate | delay-dial}
Syntax Description
Defaults
Loop-start for FXO and FXS interfaces; wink-start for E&M interfaces.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
This command applies to analog voice ports only.
Configuring the signal command for an FXO or FXS voice port changes the signal value for both voice ports on a voice port module (VPM) card.
Note
If you change the signal type for an FXO voice port on Cisco 3600 series routers, you need to move the appropriate jumper in the voice interface card of the voice network module. For more information about the physical characteristics of the voice network module, refer to the installation documentation, Voice Network Module and Voice Interface Card Configuration Note, that came with your voice network module.
Configuring this command for an E&M voice port changes only the signal value for the selected voice port. In either case, the voice port must be shut down and then activated before the configured values will take effect.
Some PBXs will miss initial digits if the E&M voice port is configured for Immediate signaling. If this occurs, use Delay-Dial signaling instead. Some non-Cisco devices have a limited number of DTMF receivers. This type of equipment must delay the calling side until a DTMF receiver is available.
Examples
The following example configures ground start signaling on the Cisco 3600 series as the signaling type for a voice port, which means that both sides of a connection can place a call and hang up:
voice-port 1/1/1signal ground-startsignal keepalive
To configure the keepalive signaling packet interval for Cisco trunks and FRF.11 trunks, use the signal keepalive command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal keepalive number
no signal keepalive number
Syntax Description
number
Specifies the keepalive signaling packet interval, in seconds. The valid range is from 1 to 65,535.
Defaults
A keepalive packet is sent every 5 seconds.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring the keepalive signaling interval, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
Examples
The following example, beginning in global configuration mode, sets the keepalive signaling interval to 3 seconds for voice class 10.
voice class permanent 10signal keepalive 3exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal pattern
To define the ABCD bit patterns that identify the idle and out-of-service (OOS) states for Cisco trunks and FRF.11 trunks, use the signal pattern command in voice-class configuration mode. To remove the signal pattern setting from the voice class, use the no form of this command.
signal pattern {idle receive | idle transmit | oos receive | oos transmit} bit-pattern
no signal pattern {idle receive | idle transmit | oos receive | oos transmit} bit-pattern
Syntax Description
Defaults
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring the signaling pattern, you must use the voice-class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. After you define the voice class, you assign it to a dial peer.
Idle Patterns
An idle state is generated if the router detects an idle signaling pattern coming from either direction. If an idle pattern is configured for only one direction (transmit or receive), an idle state can be detected only in the configured direction. Therefore, you should normally enter both the idle receive and the idle transmit keywords.
To suppress voice packets whenever the transmit or receive trunk is in the idle state, use the idle receive and idle transmit keywords in conjunction with the signal timing idle suppress-voice command.
OOS Patterns
An OOS state is generated differently in each direction under the following conditions:
•
•
To suppress voice packets whenever the transmit or receive trunk is in the OOS state, use the oos receive and oos transmit keywords in conjunction with the signal timing oos suppress-voice command.
To suppress voice and signaling packets whenever the transmit or receive trunk is in the OOS state, use the oos receive and oos transmit keywords in conjunction with the signal timing oos suppress-all command.
PBX Busyout
To "busy out" a PBX if the network connection fails, set the oos receive pattern to match the seized state (busy), and set the signal timing oos timeout value. When the timeout value expires and no signaling packets have been received, the router will send the oos receive pattern to the PBX.
Use the busy seized pattern only if the PBX does not have a specified pattern for indicating an OOS state. If the PBX has a specific OOS pattern, use that pattern instead.
Examples
The following example, beginning in global configuration mode, configures the signaling bit pattern for the idle receive and transmit states:
voice class permanent 10 signal keepalive 3 signal pattern idle receive 0101 signal pattern idle transmit 0101 exitdial-peer voice 100 vofrvoice-class permanent 10The following example, beginning in global configuration mode, configures the signaling bit pattern for the out-of-service receive and transmit states:
voice class permanent 10 signal keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001exitdial-peer voice 100 vofrvoice-class permanent 10The following example restores default signaling bit patterns for the receive and transmit idle states:
voice class permanent 10 signal keepalive 3 signal timing idle suppress-voice no signal pattern idle receive no signal pattern idle transmit exitdial-peer voice 100 vofrvoice-class permanent 10The following example configures non-default signaling bit patterns for the receive and transmit out-of-service states:
voice class permanent 10 signal keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal sequence oos
To specify which signaling pattern is sent to the PBX when the far-end keepalive message is lost or an alarm indication signal (AIS) is received from the far end, use the signal sequence oos command in the voice-class configuration mode. To restore the default value, use the no form of this command.
signal sequence oos {no-action | idle-only | oos-only | both}
no signal sequence oos
Syntax Description
Defaults
Both idle and OOS signaling patterns are sent.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring the idle or OOS signaling patterns to be sent, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. After you finish defining the voice class, you assign it to a dial peer.
Use the signal sequence oos command to specify which signaling pattern) to send. Use the signal pattern idle receive or the signal pattern oos receive command to define the bit patterns of the signaling patterns if other than the defaults.
Examples
The following example, beginning in global configuration mode, defines voice class 10, sets the signal sequence oos command to send only the idle signalin pattern to the PBX, and applies the voice class configuration to VoFR dial peer 100.
voice-class permanent 10signal-keepalive 3signal sequence oos idle-onlysignal timing idle suppress-voiceexitdial-peer voice 100 vofrvoice-class permanent 10signal-type transparentRelated Commands
signal timing idle suppress-voice
To configure the signal timing parameter for the idle state of the call, use the signal timing idle suppress-voice command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing idle suppress-voice seconds
no signal timing idle suppress-voice seconds
Syntax Description
seconds
Duration of the idle state, in seconds, before the voice traffic is stopped. The valid range is from 0 to 65,535.
Defaults
No signal timing idle suppress-voice timer is configured.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring the signal timing idle suppress-voice timer, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
The signal timing idle suppress-voice command is used when the signal-type command is set to transparent in the dial peer for the Cisco trunk or FRF.11 trunk connection. The router stops sending voice packets when the timer expires. Signaling packets are still sent.
To detect an idle trunk state, the router or concentrator monitors both transmit and receive signaling for the idle transmit and idle receive signaling patterns. These can be configured by the signal pattern idle transmit or signal pattern idle receive command, or they can be the defaults. The default idle receive pattern is the idle pattern of the local voice port. The default idle transmit pattern is the idle pattern of the far-end voice port.
Examples
The following example, beginning in global configuration mode, sets the signal timing idle suppress-voice timer to 5 seconds for the idle state on voice class 10.
voice class permanent 10signal keepalive 3 signal pattern idle receive 0101 signal pattern idle transmit 0101 signal timing idle suppress-voice 5exitdial-peer voice 100 vofrvoice-class permanent 10signal-type transparentThe following example defines voice class 10, sets the idle detection time to 5 seconds, configures the trunk to use the default transmit and receive idle signal patterns, and applies the voice class configuration to VoFR dial peer 100.
voice class permanent 10signal keepalive 3 signal timing idle suppress-voice 5exitdial-peer voice 100 vofrvoice-class permanent 10signal-type transparentRelated Commands
signal timing oos
To configure the signal timing parameter for the out-of-service (OOS) state of the call, use the signal timing oos command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing oos {restart | slave-standby | suppress-all | suppress-voice | timeout} seconds
no signal timing oos {restart | slave-standby | suppress-all | suppress-voice | timeout} seconds
Syntax Description
Defaults
No signal timing OOS pattern parameters are configured.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. The voice class must then be assigned to a dial peer.
You can enter several values for this command. However, the suppress-all and suppress-voice options are mutually exclusive.
Examples
The following example, beginning in global configuration mode, configures the signal timeout parameter for the OOS state on voice class 10. The signal timing oos timeout command is set to 60 seconds.
voice-class permanent 10signal-keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001 signal timing oos timeout 60exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal timing oos restart
To specify that a permanent voice connection be torn down and restarted after the trunk has been out-of-service (OOS) for a specified time, use the signal timing oos restart command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing oos restart seconds
no signal timing oos restart
Syntax Description
seconds
Delay duration, in seconds, for the restart attempt. There is no default duration. The range is from 0 to 65,535.
Defaults
No restart attempt is made if the trunk becomes OOS.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. You then assign the voice class to a dial peer.
The signal timing oos restart command is valid only if the signal timing oos timeout command is enabled, which controls the start time for the OOS state. The timer for the signal timing oos restart command does not start until the trunk is OOS.
Examples
The following example, beginning in global configuration mode, creates voice class 10, sets the OOS timeout time to 60 seconds and sets the restart time to 30 seconds:
voice-class permanent 10signal-keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001 signal timing oos timeout 60signal timing oos restart 30exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal timing oos slave-standby
To configure a slave port to return to its initial standby state after the trunk has been out-of-service (OOS) for a specified time, use the signal timing oos slave-standby command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing oos slave-standby seconds
no signal timing oos slave-standby
Syntax Description
Defaults
The slave port does not return to its standby state if the trunk becomes OOS.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. After you finish defining the voice class, you assign it to a dial peer.
If no signaling packets are received for the specified delay period, the slave port returns to its initial standby state. The signal timing oos slave-standby command is valid only if both of the following conditions are true:
•
•
Examples
The following example, beginning in global configuration mode, creates a voice port as a slave voice port, creates voice class 10, sets the OOS timeout time to 60 seconds, and sets the return-to-slave-standby time to 120 seconds:
voice-port 1/0/0connection trunk 5559262 answer-modeexitvoice-class permanent 10signal-keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001 signal timing oos timeout 60signal timing oos slave-standby 120exitdial-peer voice 100 vofrvoice-class permanent 10Command History
signal timing oos suppress-all
To configure the router or concentrator to stop sending voice and signaling packets to the network if it detects a transmit out-of-service (OOS) signaling pattern from the PBX for a specified time, use the signal timing oos suppress-all command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing oos suppress-all seconds
no signal timing oos suppress-all
Syntax Description
seconds
Delay duration, in seconds, before packet transmission is stopped. There is no default duration. The range is from 0 to 65,535.
Defaults
The router or concentrator does not stop sending packets to the network if it detects a transmit OOS signaling pattern from the PBX.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. After you finish defining the voice class, you assign it to a dial peer.
The signal timing oos suppress-all command is valid only if you configure an OOS transmit signaling pattern with the signal pattern oos transmit command. (There is no default oos transmit signaling pattern.)
The signal timing oos suppress-all command is valid whether or not the signal timing oos timeout command is enabled, which controls the start time for the OOS state. The timer for the signal timing oos suppress-all command starts immediately when the OOS transmit signaling pattern is matched.
Examples
The following example, beginning in global configuration mode, creates voice class 10, sets the OOS timeout time to 60 seconds, and sets the packet suppression time to 60 seconds:
voice-class permanent 10signal-keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001 signal timing oos timeout 60signal timing oos suppress-all 60exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal timing oos suppress-voice
To configure the router or concentrator to stop sending voice packets to the network if it detects a transmit out-of-service (OOS) signaling pattern from the PBX for a specified time, use the signal timing oos suppress-voice command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing oos suppress-voice seconds
no signal timing oos suppress-voice
Syntax Description
seconds
Delay duration, in seconds, before voice-packet transmission is stopped. There is no default duration. The range is from 0 to 65,535.
Defaults
The router or concentrator does not stop sending voice packets to the network if it detects a transmit OOS signaling pattern from the PBX.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. After you finish defining the voice class, you assign it to a dial peer.
The signal timing oos suppress-voice command is valid only if you configure an OOS transmit signaling pattern with the signal pattern oos transmit command. (There is no default oos transmit signaling pattern.)
The signal timing oos suppress-voice s command is valid whether or not the signal timing oos timeout command is enabled, which controls the start time for the OOS state. The timer for the signal timing oos suppress-voice command starts immediately when the OOS transmit signaling pattern is matched.
Examples
The following example, beginning in global configuration mode, creates voice class 10, sets the OOS timeout time to 60 seconds, and sets the packet suppression time to 60 seconds:
voice-class permanent 10signal-keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001 signal timing oos timeout 60signal timing oos suppress-voice 60exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal timing oos timeout
To change the delay time between the loss of signaling packets from the network and the start time for the out-of-service (OOS) state, use the signal timing oos timeout command in voice-class configuration mode. To restore the default value, use the no form of this command.
signal timing oos timeout [seconds | disabled]
no signal timing oos timeout
Syntax Description
Defaults
No signal timing OOS pattern parameters are configured.
Command Modes
Voice-class configuration
Command History
Usage Guidelines
Before configuring signal timing OOS parameters, you must use the voice class permanent command in global configuration mode to create a voice class for the Cisco trunk or FRF.11 trunk. After you finish defining the voice class, you assign it to a dial peer.
You can use the signal timing oos timeout command to enable busyout to the PBX.
The signal timing oos timeout command controls the starting time for the signal timing oos restart and signal timing oos slave-standby commands. If this command is entered with the disabled keyword, the signal timing oos restart and signal timing oos slave-standby commands are ineffective.
Examples
The following example, beginning in global configuration mode, creates voice class 10 and sets the OOS timeout time to 60 seconds:
voice-class permanent 10signal-keepalive 3 signal pattern oos receive 0001 signal pattern oos transmit 0001 signal timing oos timeout 60exitdial-peer voice 100 vofrvoice-class permanent 10Related Commands
signal-type
To set the signaling type to be used when connecting to a dial peer, use the signal-type command in dial-peer configuration mode. To return to the default signal type, use the no form of this command.
signal-type {cas | cept | ext-signal | transparent}
no signal-type
Syntax Description
Defaults
cas
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command applies to Voice over Frame Relay (VoFR) and Voice over ATM (VoATM) dial peers. It is used with permanent connections only (Cisco trunks and FRF.11 trunks), not with switched calls.
This command is used to inform the local telephony interface of the type of signaling it should expect to receive from the far-end dial peer. To turn signaling off at this dial peer, select the ext-signal option. If signaling is turned off and there are no external signaling channels, a "hot" line exists, enabling this dial peer to connect to anything at the far end.
When you connect an FXS to another FXS, or if you have anything other than an FXS/FXO or E&M/E&M pair, the appropriate signaling type on Cisco 2600 series and 3600 series routers is ext-signal (disabled).
If you have a digital E1 connection at the remote end that is running cept/MELCAS signaling and you then trunk that across to an analog port, you should make sure that you configure both ends for the cept signal type.
If you have a T1 or E1 connection at both ends and the T1/E1 is running a signaling protocol that is neither EIA-464, or cept/MELCAS, you might want to configure the signal type for the transparent option in order to pass through the signaling.
Examples
The following example shows how to disable signaling on a Cisco 2600 or 3600 series router or on a Cisco MC3810 multiservice concentrator for VoFR dial peer 200, starting from global configuration mode:
dial-peer voice 200 vofrsignal-type ext-signalexitRelated Commands
sip-server
To configure a network address for the Session Initiation Protocol (SIP) server interface, use the sip-server command in SIP user-agent configuration mode.
sip-server {dns:[host-name] | ipv4:ipaddr[:port-num]}
Syntax Description
Defaults
The default for this command is a null value.
Command Modes
SIP user-agent configuration
Command History
12.1(1)T
This command was introduced on Cisco 2600 and 3600 series routers and Cisco AS5300 universal access servers.
Usage Guidelines
If you use this command, you can then specify session target sip-server for each dial peer instead of repeatedly entering the SIP server interface address for each dial peer. To reset this command to a null value, use the default command.
Examples
The following example, beginning in global configuration mode, sets the global SIP server interface to the DNS host name of UA-1-f0.sip.com:
sip-uasip-server dns:UA-1-f0.sip.comRelated Commands
sip-ua
Enters SIP user-agent configuration mode, in which you configure the SIP user agent.
sip-ua
To enable the Session Initiation Protocol (SIP) user-agent configuration commands, with which you configure the user agent, use the sip-ua command in global configuration mode.
sip-ua
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values.
Command Modes
Global configuration
Command History
12.1(1)T
This command was introduced on Cisco 2600 and 3600 series routers and Cisco AS5300 universal access servers.
Usage Guidelines
Use the sip-ua command to enter the SIP user-agent configuration mode. Table 71 lists the SIP user-agent configuration mode commands:
Examples
The following example, beginning in global configuration mode, enters SIP user-agent configuration mode, configures the SIP user agent, then returns to global configuration mode:
sip-uaretry invite 2retry response 2retry bye 2retry cancel 2sip-server ipv4:10.0.2.254timers invite-wait-100 500exitRelated Commands
snmp enable peer-trap poor-qov
To generate poor quality of voice notification for applicable calls associated with Voice over IP (VoIP) dial peers, use the snmp enable peer-trap poor-qov command in dial-peer configuration mode. To disable this notification, use the no form of this command.
snmp enable peer-trap poor-qov
no snmp enable peer-trap poor-qov
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the snmp enable peer-trap poor-qov command to generate poor quality of voice notifications for applicable calls associated with this dial peer. If you have a Simple Network Management Protocol (SNMP) manager that uses SNMP messages when voice quality drops, you might want to enable this command. Otherwise, you should disable this command to reduce unnecessary network traffic.
Examples
The following example enables poor quality of voice notifications for calls associated with VoIP dial peer 10:
dial-peer voice 10 voipsnmp enable peer-trap poor-qovRelated Commands
ss7 mtp2-variant bellcore
To configure the router for Telcordia Technologies (formerly Bellcore) standards, use the ss7 mtp2-variant bellcore command in global configuration mode.
ss7 mtp-variant bellcore [channel] [parameters]
Syntax Description
channel
Specifies the channel, 0 through 3.
parameters
See table below for timer descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 72 for default parameters.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
This MTP2 variant has timers and parameters that can be configured using the values listed in Table 72. To restore the designated default, use the no or the default form of the command (see example below).
Note
This is true for all timers and all variants.
Examples
The following example sets the aligned/ready timer duration on channel 0 to 30,000 milliseconds:
ss7 mtp2-variant Bellcore 0T1 30000The following example restores the aligned/ready timer default value of 13,000 milliseconds:
ss7 mtp2-variant Bellcore 0no T1Related Commands
ss7 mtp2-variant itu
Specifies the mtp2-variant as ITU.
ss7 mtp2-variant ntt
Specifies the mtp2-variant as NTT.
ss7 mtp2-variant ttc
Specifies the mtp2-variant as TTC.
ss7 mtp2-variant itu
To configure the router for ITU (International Telecom United) standards, use the ss7 mtp2-variant itu command in global configuration mode.
ss7 mtp-variant itu [channel] [parameters]
Syntax Description
channel
Specifies the channel, 0 through 3.
parameters
See table below for timer descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 73 for ITU default parameters.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The ITU MTP2 variant has timers and parameters that can be configured using the values listed in Table 73. To restore the designated default, use the no or the default form of the command (see the example below).
Examples
The following example sets the emergency proving period on channel 1 to 10,000 milliseconds:
ss7 mtp2-variant itu 1t4-Emergency-Proving 10000The following example restores the emergency proving period default value of 5,000 milliseconds:
ss7 mtp2-variant itu 1default t4-Emergency-ProvingRelated Commands
ss7 mtp2-variant bellcore
Specifies the mtp2-variant as Bellcore.
ss7 mtp2-variant ntt
Specifies the mtp2-variant as NTT.
ss7 mtp2-variant ttc
Specifies the mtp2-variant as TTC.
ss7 mtp2-variant ntt
To configure the router for NTT (Japan) standards, use the ss7 mtp2-variant ntt command in global configuration mode.
ss7 mtp-variant ntt [channel] [parameters]
Syntax Description
channel
Specifies the channel, 0 through 3.
parameters
See table below for timer descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 74 for NTT default parameters.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The NTT MTP2 variant has timers and parameters that can be configured using the values listed in Table 74. To restore the designated default, use the no or the default form of the command (see the example below).
Examples
The following example sets the SUERM error rate threshold on channel 2 to 100:
ss7 mtp2-variant ntt 2SUERM-threshold 100The following example restores the SUERM error rate threshold default value of 64:
ss7 mtp2-variant ntt 2no SUERM-thresholdRelated Commands
ss7 mtp2-variant bellcore
Specifies the mtp2-variant as Bellcore.
ss7 mtp2-variant itu
Specifies the mtp2-variant as ITU.
ss7 mtp2-variant ttc
Specifies the mtp2-variant as TTC.
ss7 mtp2-variant ttc
To configure the router for TTC (Japan Telecom) standards, use the ss7 mtp2-variant ttc command in global configuration mode.
ss7 mtp-variant ttc [channel] [parameters]
Syntax Description
channel
Specifies the channel, 0 through 3.
parameters
See table below for timer descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 75 for TTC default parameters.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The TTC MTP2 variant has timers and parameters that can be configured using the values listed in Table 75. To restore the designated default, use the no or the default form of the command (see the example below).
Examples
The following example sets the maximum number of proving attempts for channel 3 to 3:
ss7 mtp2-variant ttc 3proving-attempts 3The following example restores the maximum number of proving attempts to the default value:
ss7 mtp2-variant ttc 3default proving-attemptsRelated Commands
ss7 mtp2-variant bellcore
Specifies the mtp2-variant as Bellcore.
ss7 mtp2-variant itu
Specifies the mtp2-variant as ITU.
ss7 mtp2-variant ntt
Specifies the mtp2-variant as NTT.
ss7 session
To create a Reliable User Datagram Protocol (RUDP) session, use the ss7 session command in global configuration mode. To delete the session, use the no form of this command.
ss7 session-session number {address remote-address remote-port local-address local-port}
no ss7session-session number address
Syntax Description
Defaults
No session is configured.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
You can configure a maximum of two sessions, one for each signaling link. In a redundant Media Gateway Controller configuration, session-0 is configured to one MGC and session-1 is configured to the other.
The Media Gateway Controller must be configured to send messages to the local port, and it must be configured to listen on the remote port.
You must reload the router whenever you remove a session or change the parameters of a session.
Examples
The following example sets up two sessions on a Cisco 2611:
ss7 session-0 address 255.251.255.255 7000 255.255.255.254 7000ss7 session-1 address 255.255.255.252 7002 255.255.255.254 7001
Note
Related Commands
ss7 session cumack_t
To set the Reliable User Datagram Protocol (RUDP) cumulative acknowledgment timer for a specific SS7 signaling link session, use the ss7 session cumack_t command in global configuration mode. To restore the default value, use the no form of this command.
ss7 session-session number cumack_t milliseconds
no ss7 session-session number cumack_t
Caution
Syntax Description
Defaults
The default value is 300 milliseconds.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The cumulative acknowledgment timer determines when the receiver sends an acknowledgment. If the timer is not already running, it is initialized when a valid data, null, or reset segment is received. When the cumulative acknowledgment timer expires, the last in-sequence segment is acknowledged. The RUDP typically tries to "piggyback" acknowledgments on data segments being sent. However, if no data segment is sent in this period of time, it sends a standalone acknowledgment.
Examples
The following example sets up two sessions and sets the cumulative acknowledgment timer to 320 milliseconds for each one:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7000ss7 session-0 cumack_t 320ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7001ss7 session-1 cumack_t 320Related Commands
ss7 session kp_t
To set the null segment (keepalive) timer for a specific SS7 signaling link session, use the ss7 session kp_t command in global configuration mode. To restore the default value, use the no form of this command.
ss7 session-session number kp_t milliseconds
no ss7 session-session number kp_t
Caution
Syntax Description
Defaults
The default value is 2000 milliseconds.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The null segment timer determines when a null segment (keepalive) is sent by the client Cisco 2600 series router. On the client, the timer starts when the connection is established and is reset each time a data segment is sent. If the null segment timer expires, the client sends a keepalive to the server to verify that the connection is still functional. On the server, the timer restarts each time a data or null segment is received from the client.
The value of the server's null segment timer is twice the value configured for the client. If no segments are received by the server in this period of time, the connection is no longer valid.
To disable keepalive, set this parameter to 0.
Examples
The following example sets up two sessions and sets a keepalive of 1,800 milliseconds for each one:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7000ss7 session-0 kp_t 1800ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7001ss7 session-1 kp_t 1800Related Commands
ss7 session m_cumack
To set the maximum number of segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an acknowledgment in a specific SS7 signaling link session, use the ss7 session m_cumack command in global configuration mode. To restore the default value, use the no form of this command.
ss7 session-session number m_cumack segments
no ss7 session-session number m_cumack
Caution
Syntax Description
Defaults
The default value is 3 segments.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The cumulative acknowledgment counter records the number of unacknowledged, in-sequence data, null, or reset segments received without a data, null, or reset segment being sent to the transmitter. If this counter reaches the configured maximum, the receiver sends a standalone acknowledgment (a standalone acknowledgment is a segment that contains only acknowledgment information). The standalone acknowledgment contains the sequence number of the last data, null, or reset segment received.
If you set this parameter to 0, an acknowledgment is sent immediately after a data, null, or reset segment is received.
Examples
The following example sets up two sessions and in each session sets a maximum of two segments for receipt before acknowledgment:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_cumack 2ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_cumack 2Related Commands
ss7 session m_outseq
To set the maximum number of out-of-sequence segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an extended acknowledgment in a specific SS7 signaling link session, use the ss7 session m_outseq command in global configuration mode. To restore the default value, use the no form of this command.
ss7 session-session number m_outseq segments
no ss7 session-session number m_outseq
Caution
Syntax Description
Defaults
The default value is 3 segments.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The out-of-sequence acknowledgment counter records the number of data segments that have arrived out of sequence. If this counter reaches the configured maximum, the receiver sends an extended acknowledgment segment that contains the sequence numbers of the out-of-sequence data, null, and reset segments received. When the transmitter receives the extended acknowledgment segment, it retransmits the missing data segments.
If you set this parameter to 0, an acknowledgment is sent immediately after an out-of-sequence segment is received.
Examples
The following example sets up two sessions and sets a maximum number of four out-of-sequence segments for each session:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_outseq 4ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_outseq 4Related Commands
ss7 session m_rcvnum
To set the maximum number of segments that the remote end can send before receiving an acknowledgment in a specific SS7 signaling link session, use the ss7 session m_rcvnum command in global configuration mode. To restore the default value, use the no form of this command.
ss7 session-session number m_rcvnum segments
no ss7 session-session number m_rcvnum
Caution
Syntax Description
Defaults
The default value is 32 segments.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The outstanding segments counter is the maximum number of segments that the Cisco IOS software end of the connection can send without getting an acknowledgment from the receiver. The receiver uses the counter for flow control.
Examples
The following example sets up two sessions and for each session sets a maximum of 36 segments for receipt before an acknowledgment:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_rcvnum 36ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_rcvnum 36Related Commands
ss7 session m_retrans
To set the maximum number of times that the Reliable User Datagram Protocol (RUDP) attempts to resend a segment before declaring the connection invalid in a specific SS7 signaling link session, use the ss7 session m_retrans command in global configuration mode. To restore the default value, use the no form of this command.
ss7 session-session number m_retrans number
no ss7 session-session number m_retrans
Caution
Syntax Description
Defaults
The default value is 2 times.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The retransmission counter is the number of times a segment has been retransmitted. If this counter reaches the configured maximum, the transmitter resets the connection and informs the upper-layer protocol.
If you set this parameter to 0, the RUDP attempts to resend the segment continuously.
Examples
The following example sets up two sessions and for each session sets a maximum number of three times to resend before a session becomes invalid:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_retrans 3ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_retrans 3Related Commands
ss7 session retrans_t
To set the amount of time that the Reliable User Datagram Protocol (RUDP) waits to receive an acknowledgment for a segment in a specific SS7 signaling link session, use the ss7 session retrans_t command in global configuration mode. If the RUDP does not receive the acknowledgment in this time period, the RUDP retransmits the segment. To restore the default value, use the no form of this command.
ss7 session-session number retrans_t milliseconds
no ss7 session-session number retrans_t
Caution
Syntax Description
Defaults
The default value is 600 milliseconds.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The retransmission timer is used to determine whether a packet must be retransmitted and is initialized each time a data, null, or reset segment is sent. If an acknowledgment for the segment is not received by the time the retransmission timer expires, all segments that have been transmitted—but not acknowledged—are retransmitted.
This value should be greater than the value configured for the cumulative acknowledgment timer by using the ss7 session cumack_t command.
Examples
The following example sets up two sessions and specifies 550 milliseconds as the time to wait for an acknowledgment for each session:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 retrans_t 550ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 retrans_t 550Related Commands
ss7 set failover-timer
To specify the amount of time that the SS7 Session Manager waits for the active session to recover or for the standby Media Gateway Controller to indicate that the SLT should switch traffic to the standby session, use the ss7 set failover-timer command in global configuration mode. To restore the default setting, use the no form of this command.
ss7 set failover-timer [seconds]
no ss7 set failover-timer
Syntax Description
seconds
Time in seconds that the Session Manager waits for a session to recover. Values from 1 through 10 are valid.
Defaults
The default is 3 seconds.
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
This command specifies the number of seconds that the Session Manager waits for the the active session to recover or for the standby Media Gateway Controller to indicate that the SLT should switch traffic to the standby session and to make that session the active session. If the timer expires without a recovery of the original session or an active message from the standby Media Gateway Controller, the signaling links are taken out of service.
Examples
The following example sets the failover timer to four seconds:
ss7 set failover-timer 4Related Commands
show ss7 sm set
Displays the current failover timer setting.
ss7 session
Establishes a session.
station-id
To specify the name or number that will be sent as Caller-ID information and enable Caller-ID, use the station-id voice-port configuration command at the sending Foreign Exchange Station (FXS) voice port or at a Foreign Exchange Office (FXO) port through which routed Caller-ID calls pass. To remove the name or number, use the no form of this command.
station-id [name name | number number]
no station-id [name name | number number]
Syntax Description
name
A string of 1 to 15 characters to represent the station name.
number
A string of from 1 to 15 characters to represent the station number.
Defaults
The default is no station name or number.
Command Modes
Voice-port configuration
Command History
12.1(2)XH
This command was implemented for Cisco MC3810 and for Cisco 2600 and 3600 series routers.
12.1(3)T
This command was first supported on the T Train.
Usage Guidelines
This optional command is configured on FXS voice ports that are used to originate on-net calls. The information entered is displayed by the telephone attached to the FXS port at the far end of the on-net call. It can also be configured on the FXO port of a router on which Caller ID information is expected to be received from the CO, to suit situations where a call is placed from the CO, then goes through the FXO interface, and continues to a far-end FXS port through an on-net call. In this case, if no Caller ID information is received from the CO telephone line, the far-end call recipient receives the information configured on the FXO port.
Note
Do not use this command when the Caller-ID standard is dual-tone multifrequency (DTMF). DTMF Caller ID can carry only the calling number.
If the station-id or caller-id alerting command is configured on the voice port, these automatically enable Caller-ID, and the caller-id enable command is not necessary.
This command applies to the Cisco MC3810 and to Cisco 2600 and 3600 series routers.
Examples
The following example configures a Cisco 2600 or 3600 series router voice port from which Caller-ID information is sent:
voice-port 1/0/1cptone USstation-id name A. Personstation-id number 4085551111The following example configures a Cisco MC3810 voice port from which Caller-ID information is sent:
voice-port 1/0cptone northamericastation-id name A. Personstation-id number 4085551111caller-id alerting ring 1Related Commands
subcell-mux
To enable subcell multiplexing on a Cisco MC3810 multiservice concentrator, use the subcell-mux command in voice-service configuration mode. To restore the default value, use the no form of the command.
subcell-mux
no subcell-mux
Syntax Description
This command has no arguments or keywords.
Defaults
Subcell multiplexing is not enabled.
Command Modes
Voice-service configuration
Command History
12.1(1)XA
The command was introduced for the Cisco MC3810 multiservice concentrator.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
Usage Guidelines
Use this command to enable ATM adaptation layer 2 (AAL2) common part sublayer (CPS) subcell multiplexing when the Cisco MC3810 interoperates with other equipment that uses subcell multiplexing.
Examples
The following example enables AAL2 CPS subcell multiplexing on a Cisco MC3810 multiservice concentrator:
voice service voatm session protocol aal2subcell-muxsupervisory disconnect
To enable a supervisory disconnect signal on Foreign Exchange Office (FXO) ports, use the supervisory disconnect command in voice-port configuration mode. To disable the supervisory disconnect signal, use the no form of this command.
supervisory disconnect
no supervisory disconnect
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Voice-port configuration
Command History
11.3(1)MA
This command was introduced on Cisco MC3810 multiservice concentrators.
Usage Guidelines
This command indicates whether supervisory disconnect signaling is available on the FXO port. Supervisory disconnect signaling is a power denial from the switch lasting at least 350 milliseconds. When this condition is detected, the system interprets this as a disconnect indication from the switch and clears the call.
You should configure no supervisory disconnect on the voice port if there is no supervisory disconnect available from the switch.
Note
Examples
The following example configures supervisory disconnect on a Cisco 3600 series voice port:
voice-port 2/1/0supervisory disconnectThe following example configures supervisory disconnect on a Cisco MC3810 multiservice concentrator voice port:
voice-port 1/1supervisory disconnectsupervisory disconnect anytone
To configure an Foreign Exchange Office (FXO) voice port to go on-hook if the router detects any tone from a PBX or public switched telephone network (PSTN) before the call is answered, use the supervisory disconnect anytone command in voice-port configuration mode. To restore the default, use the no form of this command.
supervisory disconnect anytone
no supervisory disconnect anytone
Syntax Description
This command has no arguments or keywords.
Defaults
The supervisory disconnect function is not enabled on voice ports.
Command Modes
Voice-port configuration
Command History
12.1(3)T
This command was introduced on the Cisco 2600, 3600, and MC3810 series.
Usage Guidelines
The supervisory disconnect anytone voice-port configuration command can be used to provide the disconnect function if the PBX or PSTN does not provide a supervisory tone. This function is enabled only during call setup (before the call is answered); examples of tones that trigger a disconnect include busy tone, fast busy tone, and dial tone. You must enable echo cancellation; otherwise, the router's own ringback tone can trigger a disconnect.
This command replaces the no supervisory disconnect signal command. If you enter the no supervisory disconnect signal command, the supervisory disconnect any-tone feature will be enabled, and "supervisory disconnect" anytone will be displayed when show commands are entered.
Examples
The following example configures voice ports 1/4 and 1/5 to go on-hook if any tone from the PBX or PSTN is detected before the call is answered:
voice-port 1/4supervisory disconnect anytoneexitvoice-port 1/5supervisory disconnect anytoneexitThe following example disables the disconnect function on voice port 1/5:
voice-port 1/5no supervisory disconnect anytoneexitRelated Commands
supervisory disconnect dualtone voice-class
To assign a previously configured voice class for Foreign Exchange Office (FXO) supervisory disconnect tone to a voice port, use the supervisory disconnect dualtone voice-class command in voice port configuration mode. To remove a voice class from a voice-port, use the no form of this command.
supervisory disconnect dualtone {mid-call | pre-connect} voice-class tag
no supervisory disconnect dualtone voice-class tag
Syntax Description
Defaults
No voice class is assigned to a voice port.
Command Modes
Voice-port configuration
Command History
12.1(3)T
This command was introduced on the Cisco 2600, 3600, and MC3810 series.
Usage Guidelines
You can apply an FXO supervisory disconnect tone voice class to multiple voice ports. You can assign only one FXO supervisory disconnect tone voice class to a voice port. If a second voice class is assigned to a voice port, the second voice class replaces the one previously assigned. You cannot assign separate FXO supervisory disconnect tone commands directly to the voice port.
This feature is applicable to analog FXO voice ports with loop-start signaling.
Examples
The following example assigns voice class 70 to FXO voice port 1/5 of a Cisco MC3810 series concentrator and specifies tone detection during the entire call duration:
voice-port 1/5no echo-cancel enablesupervisory disconnect dualtone mid-call voice-class 70The following example assigns voice class 80 to FXO voice port 0/1/1 of a Cisco 3600 series router and specifies tone detection only during call setup:
voice-port 0/1/1no echo-cancel enablesupervisory disconnect dualtone pre-connect voice-class 80Related Commands
tdm-group
To configure a list of time slots for creating clear channel groups (pass-through) for time-division multiplexing (TDM) cross-connect, use the tdm-group command in controller configuration mode. To delete a clear channel group, use the no form of this command.
tdm-group tdm-group-no timeslot timeslot-list [type {e&m | fxs [loop-start | ground-start] | fxo [loop-start | ground-start] | fxs-melcas | fxo-melcas | e&m-melcas}]
no tdm-group tdm-group-no timeslot timeslot-list [type {e&m | fxs [loop-start | ground-start] | fxo [loop-start | ground-start] | fxs-melcas | fxo-melcas | e&m-melcas}]
Syntax Description
Defaults
No TDM group is configured.
Command Modes
Controller configuration
Command History
Usage Guidelines
The tdm-group command allows specific timeslots to switch from port 0 to port 1 and vice versa. This command is similar to the channel-group command, but it does not create a serial interface to terminate the specified channels.
Note
Examples
The following example shows TDM group 1 being set up to include timeslots 13 through 20:
controller T1 1tdm-group 1 timeslots 13-20The following example configures TDM group number 20 on controller T1 1 to support FXO ground-start:
controller T1 1tdm-group 20 timeslot 20 type fxs ground-startRelated Commands
tech-prefix
To specify that a particular technology prefix be prepended to the destination pattern of a specific dial peer, use the tech-prefix command in dial-peer configuration mode. To disable the defined technology prefix for this dial peer, use the no form of this command.
tech-prefix number
no tech-prefix number
Syntax Description
Defaults
No technology prefix is defined.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Technology prefixes are used to distinguish between gateways that have specific capabilities within a given zone. In the exchange between the gateway and the gatekeeper, the technology prefix is used to select a gateway after the zone has been selected. Use the tech-prefix command to define technology prefixes.
Technology prefixes can be used as a discriminator so that the gateway can tell the gatekeeper that a certain technology is associated with a particular call (for example, 15# could mean a fax transmission), or a technology prefix can be used like an area code for more generic routing. No standard defines what the numbers in a technology prefix mean; by convention, technology prefixes are designated by a pound (#) symbol as the last character.
In most cases, there is a dynamic protocol exchange between the gateway and the gatekeeper that enables the gateway to inform the gatekeeper about technology prefixes and where to forward calls. If, for some reason, that dynamic registry feature is not in effect, you can statically configure the gatekeeper to query the gateway for this information by configuring the gw-type-prefix command on the gatekeeper. Use the show gatekeeper gw-type-prefix command to display how the gatekeeper has mapped the technology prefixes to local gateways.
Note
Examples
The following example defines a technology prefix of 14# for the specified dial peer. In this example, the technology prefix means that the H.323 gateway will ask the RAS gatekeeper to direct calls using the technology prefix of 14#.
dial-peer voice 10 voipdestination-pattern 14...tech-prefix 14#Related Commands
gw-type-prefix
Configures a technology prefix in the gatekeeper.
show gatekeeper gw-type-prefix
Displays the gateway technology prefix table.
test call fallback probe
To test a probe to a particular IP address and display the Calculated Planning Impairment Factor (ICPIF) response time reporter (RTR) values, use the test call fallback probe command in EXEC mode. This command has no impact on the cache.
test call fallback probe ip-address [codec 711/729]
Syntax Description
ip-address
Specifies the target IP address.
codec 711/729
(Optional) Specifies a specific codec type.
Defaults
This command is not configured by default.
Command Modes
EXEC
Command History
Examples
The following example demonstrates a test probe to IP address 10.1.1.4, and shows that the ICPIF value to 10.1.1.4 is 0:
Router# test call fallback probe 10.1.1.4Running a test RTR probe....ICPIF value for the test probe is 0Related Commands
test pots dial
To dial a telephone number for the plain old telephone service (POTS) port on the router by using a dial application on your workstation, use the test pots dial command in EXEC mode.
test pots port dial number[#]
Syntax Description
Command Modes
EXEC
Command History
12.1(2)XF
The command test pots port dial was introduced on the Cisco 800 series routers.
Usage Guidelines
If the telephone is on the hook when you issue the dial command, the router rings the telephone, waits until the telephone is taken off the hook, and then dials the requested number. If the telephone is off the hook and providing a dial tone when you issue the command, the router dials the requested number.
Examples
The following POTS dial command dials the telephone number 4085551234:
Router# test pots 1 dial 4085551234#For an example of the test pots port dial command with debug output, see the debug pots csm command in the Cisco IOS Debug Command Reference, Release 12.2.
Related Commands
test pots disconnect
To disconnect a telephone call for the POTS port on the router, use the test pots disconnect command in EXEC mode.
test pots port disconnect
Syntax Description
Command Modes
EXEC
Command History
Examples
The following POTS disconnect command disconnects a telephone call from POTS port 1:
Router# test pots 1 disconnectFor an example of the test pots port disconnect command with debug output, see the debug pots csm command in the Cisco IOS Debug Command Reference, Release 12.2.
Related Commands
test translation-rule
To test the execution of the translation rules on a specific name tag, use the test translation-rule command in global configuration mode. To disable the test, use the no form of this command.
test translation-rule name-tag input-number [input-numbering-type]
no test translation-rule name-tag input-number [input-numbering-type]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following example shows output from the test translation-rule command:
Router# translation-rule 21Rule 1 555.% 1408555 subscriber internationalRule 2 8.% 1408555 abbreviated internationalRouter# test translation-rule 21 45678 abbreviated*Jan 19 16:39:14.578:The replace number 45614085558Related Commands
test voice port detector
To test detector-related functions on a voice port, use the test voice port detector command in privileged EXEC mode.
Cisco 2600 and 3600 Series with Analog Voice Ports
test voice port slot/subunit/port detector {m-lead | battery-reversal | ring | tip-ground | ring-ground | ring-trip} {on | off | disable}
Cisco 2600 and 3600 Series with Digital Voice Ports
test voice port slot/port:ds0-group detector {m-lead | battery-reversal | ring | tip-ground | ring-ground | ring-trip} {on | off | disable}
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
test voice port slot/port detector {m-lead | battery-reversal | ring | tip-ground | ring-ground | ring-trip} {on | off | disable}
Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
test voice port slot:ds0-group detector {m-lead | battery-reversal | ring | tip-ground | ring-ground | ring-trip} {on | off | disable}
Syntax DescriptionDescription
For the Cisco 2600 and 3600 Series Routers with Analog Voice Ports:
For the Cisco 2600 and 3600 Series Routers with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
For All Platforms:
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test voice port detector privileged EXEC command to force a detector into specific states for testing. For each signaling type (E&M, FXO, FXS), only the applicable keywords are displayed. When you are finished testing, be sure to enter the command with the disable keyword to end the forced state. The disable keyword is available only if a test condition is already activated.
Examples
The following example forces the tip-ground detector to the off state on an FXO voice port (1/3) on a Cisco MC3810 and ends any call in progress:
Router# test voice port 1/3 detector tip-ground offThe following example ends the forced off state on an FXO voice port (1/3) on a Cisco MC3810:
Router# test voice port 1/3 detector tip-ground disableThe following example forces the ring-trip detector to the on state on an FXS port (0/0/1) on a Cisco 3600 series router and should start a call:
Router# test voice port 0/0/1 detector ring-trip onThe following example ends the forced on state on an FXS port (0/0/1) on a Cisco 3600 series router:
Router# test voice port 0/0/1 detector ring-trip disableRelated Commands
test voice port inject-tone
To inject a test tone into a voice port, use the test voice port inject-tone command in privileged EXEC mode.
Cisco 2600 and 3600 Series with Analog Voice Ports
test voice port slot/subunit/port inject-tone {local | network} {1000hz | 2000hz | 200hz | 3000hz | 300hz | 3200hz | 3400hz | 500hz | quiet | disable}
Cisco 2600 and 3600 Series with Digital Voice Ports
test voice port slot/port:ds0-group inject-tone {local | network} {1000hz | 2000hz | 200hz | 3000hz | 300hz | 3200hz | 3400hz | 500hz | quiet | disable}
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
test voice port slot/port inject-tone {local | network} {1000hz | 2000hz | 200hz | 3000hz | 300hz | 3200hz | 3400hz | 500hz | quiet | disable}
Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
test voice port slot:ds0-group inject-tone {local | network} {1000hz | 2000hz | 200hz | 3000hz | 300hz | 3200hz | 3400hz | 500hz | quiet | disable}
Syntax Description
For the Cisco 2600 and 3600 Series with Analog Voice Ports:
For the Cisco 2600 and 3600 Series with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
For All platforms:
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test voice port inject-tone privileged EXEC command to inject a test tone or to end a test tone. A call must be established on the voice port under test. When you are finished testing, be sure to enter the disable keyword to end the test tone. The disable keyword is available only if a test condition is already activated.
When you enter the disable keyword, you must enter a direction (either network or local); however, you can enter either direction, regardless of which direction you entered to inject the test tone.
Examples
The following example injects a 1-kilohertz test tone into voice port 1/1, directed toward the network (far end), on a Cisco MC3810:
Router# test voice port 1/1 inject-tone network 1000hzThe following example removes the test tone from port 0/0/1 on a Cisco 3600 series router:
Router# test voice port 0/0/1 inject-tone network disableor
Router# test voice port 0/0/1 inject-tone local disableRelated Commands
test voice port loopback
To perform loopback testing on a voice port, use the test voice port loopback command in privileged EXEC mode.
Cisco 2600 and 3600 Series with Analog Voice Ports
test voice port slot/subunit/port loopback {local | network | disable}
Cisco 2600 and 3600 Series with Digital Voice Ports
test voice port slot/port:ds0-group loopback {local | network | disable}
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
test voice port slot/port loopback {local | network | disable}
Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
test voice port slot:ds0-group loopback {local | network | disable}
Syntax Description
For the Cisco 2600 and 3600 Series with Analog Voice Ports:
For the Cisco 2600 and 3600 Series with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
All Platforms:
local
Forces a loopback at the voice port toward the customer premises equipment (CPE).
network
Forces a loopback at the voice port toward network.
disable
Ends the forced loopback.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test voice port loopback privileged EXEC command to initiate or end a loopback at a voice port. A call must be established on the voice port under test. When you are finished testing, be sure to enter the disable keyword to end the forced loopback. The disable keyword is available only if a test condition is already activated.
Examples
The following example forces a loopback toward the CPE on voice port 1/1 on a Cisco MC3810:
Router# test voice port 1/1 loopback localThe following example ends a forced loopback on port 0/0/1 on a Cisco 3600 series router:
Router# test voice port 0/0/1 loopback disableRelated Commands
test voice port relay
To test relay-related functions on a voice port, use the test voice port relay command in privileged EXEC mode.
Cisco 2600 and 3600 Series with Analog Voice Ports
test voice port slot/subunit/port relay {e-lead | loop | ring-ground | battery-reversal | power-denial | ring | tip-ground} {on | off | disable}
Cisco 2600 and 3600 Series with Digital Voice Ports
test voice port slot/port:ds0-group relay {e-lead | loop | ring-ground | battery-reversal | power-denial | ring | tip-ground} {on | off | disable}
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
test voice port slot/port relay {e-lead | loop | ring-ground | battery-reversal | power-denial |
ring | tip-ground} {on | off | disable}Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
test voice port slot:ds0-group relay {e-lead | loop | ring-ground | battery-reversal | power-denial | ring | tip-ground} {on | off | disable}
Syntax Description
For the Cisco 2600 and 3600 Series with Analog Voice Ports:
For the Cisco 2600 and 3600 Series with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
All Platforms:
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test voice port relay privileged EXEC command to force a relay into specific states for testing. For each signaling type (E&M, FXO, FXS), only the applicable keywords are displayed. When you are finished testing, be sure to enter the disable keyword to end the forced state. The disable keyword is available only if a test condition is already activated.
Examples
The following example forces the E&M e-lead relay to the on state on port 0/0/1 on a Cisco 3600 series router:
Router# test voice port 0/0/1 relay e-lead onThe following example ends a forced actuation of the battery-reversal relay on an FXS port (0/0/1) on a Cisco 3600 series router:
Router# test voice port 0/0/1 relay battery-reversal disableRelated Commands
test voice port switch
To force a voice port into fax mode, use the test voice port switch command in privileged EXEC mode.
Cisco 2600 and 3600 Series with Analog Voice Ports
test voice port slot/subunit/port switch {fax | disable}
Cisco 2600 and 3600 Series with Digital Voice Ports
test voice port slot/port:ds0-group switch {fax | disable}
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
test voice port slot/port switch {fax | disable}
Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
test voice port slot:ds0-group switch {fax | disable}
Syntax Description
For the Cisco 2600 and 3600 Series with Analog Voice Ports:
For the Cisco 2600 and 3600 Series with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
For All Platforms:
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test voice port switch privileged EXEC command to force a voice port into fax mode for testing. If no fax data is detected by the voice port, the voice port remains in fax mode for 30 seconds and then reverts automatically to voice mode. After you enter the test voice port switch fax command, you can use the show voice call or show voice call summary command to check whether the voice port is able to operate in fax mode.
The disable keyword ends the forced mode switch; however, the fax mode ends automatically after 30 seconds. The disable keyword is available only while the voice port is in fax mode.
Examples
The following example forces voice port 1/3 on a Cisco MC3810 into fax mode:
Router# test voice port 1/3 switch faxThe following example returns voice port 0/0/1 on a Cisco 3600 series router to voice mode:
Router# test voice port 0/0/1 switch disableRelated Commands
test vrm busyout
To busy out a specific digital signal processor (DSP) or channels on a specific DSP, use the test vrm busyout command in privileged EXEC mode.
test vrm busyout slot-number {first-dsp-number {last-dsp-number | channel number} | all}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test vrm busyout command to busy out either one specific DSP or a range of DSPs on a specific VFC. In addition, you can use this command to busy out a particular channel on a specified DSP or range of DSPs. To restore the activity of the busied-out DSPs, use the test vrm unbusyout command.
Examples
The following example busies out all of the DSPs and associated channels for the VFC located in slot 4:
Router# test vrm busyout 4 allThe following example busies out all of the channels from DSP1 to DSP3 for the VFC located in slot 4:
Router# test vrm busyout 4 1 3The following example busies out only channel 2 of DSP1 for the VFC located in slot 4:
Router# test vrm busyout 4 1 channel 2Related Commands
test vrm unbusyout
Restores activity to a busied-out DSP or busied-out channels on a DSP.
test vrm reset
To reset a particular digital signal processor (DSP), use the test vrm reset command in privileged EXEC mode.
test vrm reset slot-number dsp-number
Syntax Description
slot-number
Number that identifies the slot in which the voice feature card (VFC) is installed.
dsp-number
Number that identifies the DSP to be reset.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test vrm reset command to send a hard reset command to an identified DSP. When this command is used, any active calls on all channels associated with this DSP are dropped. Under most circumstances, you will never need to use this command.
Examples
The following example resets DSP 4 on the VFC installed in slot 2:
Router# test vrm reset 2 4Resetting voice device may terminate active calls [confirm}Reset command sent to voice card 4 for voice device 2.test vrm unbusyout
To restore activity to a busied-out digital signal processor (DSP) or busied-out channels on a DSP, use the test vrm unbusyout command in privileged EXEC mode.
test vrm unbusyout slot-number {first-dsp-number {last-dsp-number | channel number} | all }
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test vrm unbusyout command to restore either one specific DSP or a range of DSPs on a specific VFC. In addition, you can use this command to restore a particular channel on a specified DSP or range of DSPs. To busy out a DSP (or range of DSPs) or to busy out a particular channel, use the test vrm busyout command.
Examples
The following example restores the activity of all DSPs and associated channels for the VFC located in slot 4:
Router# test vrm unbusyout 4 allThe following example restores the activity of all channels on the DSP from DSP1 to DSP3 for the VFC located in slot 4:
Router# test vrm unbusyout 4 1 3The following example restores the activity of only channel 2 of DSP1 for the VFC located in slot 4:
Router# test vrm unbusyout 4 1 channel 2Related Commands
threshold noise
To configure a noise threshold for incoming calls, use the threshold noise command in voice-port configuration mode. To restore the default, use the no form of this command.
threshold noise {value}
no threshold noise {value}
Syntax Description
value
Number that establishes a noise threshold. Valid values are from -30 to -90 decibels (dBs). The default value is -62 dB.
Defaults
-62dB
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Cisco voice activity detection (VAD) has two layers: application programming interface (API) layer and processing layer. There are 3 states that the processing layer classifies incoming signals: speech, unknown, and silence. The state of the incoming signals is determined by the noise threshold.
In earlier Cisco IOS Releases, the noise threshold is fixed between -62dB and -78 dB. If the voice level is below the noise threshold, then the signal is classified as silence. If the incoming signal cannot be classified, the variable thresholds that are computed with the statistics of speech and noise that VAD gathers is used to make a determination. If the signal still cannot be classified, then it is marked as unknown. The final decision is made by the API. For applications such as hoot-n-holler, you could have the noise create unwanted spurious packets (for example, a voice stream) taking up bandwidth.
With Cisco IOS Release 12.2(16), the noise threshold is configurable using the threshold noise command.
Examples
The following sample configuration shows a noise threshold level of -50 dB configured on a Cisco 3600:
voice-port 1/0/0threshold noise -50timeouts call-disconnect
To configure the call disconnect timeout value for a specified voice port, use the timeouts call-disconnect command in voice-port configuration mode. To restore the default value, use the no form of this command.
timeouts call-disconnect seconds
no timeouts call-disconnect
Syntax Description
Defaults
60 seconds
Command Modes
Voice-port configuration
Command History
11.3(9)T
This command was introduced on Cisco 3600 series routers.
12.0(4)T
This command was integrated into Cisco IOS Release 12.0(4)T.
Usage Guidelines
This command applies to Cisco 3600 series routers. To disable the timeouts call-disconnect timer, set the seconds value to 0. Use the timeouts call-disconnect command to specify the number of seconds for which the originating end system waits after receiving disconnect before notifying the user to hang up by playing a fast busy tone. During this duration, the user just hears silence. If the command is disabled by setting the value to 0, the user hears silence indefinitely.
Examples
The following example sets a call-disconnect timeout value of 10 seconds on a Cisco 3600 series router voice port:
voice-port 1/0/0timeouts call-disconnect 10Related Commands
timeouts initial
To configure the initial digit timeout value for a specified voice port, use the timeouts initial command in voice-port configuration mode. To restore the default value, use the no form of this command.
timeouts initial seconds
no timeouts initial seconds
Syntax Description
Defaults
10 seconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use the timeouts initial command to specify the number of seconds for which the system will wait for the caller to input the first digit of the dialed digits. The timeouts initial timer is activated when the call is accepted and is deactivated when the caller inputs the first digit. If the configured timeout value is exceeded, the caller is notified through the appropriate tone and the call is terminated.
To disable the timeouts initial timer, set the seconds value to 0.
Examples
The following example sets the initial digit timeout value on the Cisco 3600 series to 10 seconds:
voice-port 1/0/0timeouts initial 10The following example sets the initial digit timeout value on the Cisco MC3810 multiservice concentrator to 10 seconds:
voice-port 1/1timeouts initial 10Related Commands
timeouts interdigit
Configures the interdigit timeout value for a specified voice port.
timeouts interdigit
To configure the interdigit timeout value for a specified voice port, use the timeouts interdigit command in voice-port configuration mode. To restore the default value, use the no form of this command.
timeouts interdigit seconds
no timeouts interdigit seconds
Syntax Description
Defaults
10 seconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
This command applies to both the Cisco 3600 series router and the Cisco MC3810 multiservice concentrator.
Use the timeouts interdigit command to specify the number of seconds for which the system will wait (after the caller has input the initial digit) for the caller to input a subsequent digit of the dialed digits. The timeouts interdigit timer is activated when the caller inputs a digit and is restarted each time the caller inputs another digit until the destination address is identified. If the configured timeout value is exceeded before the destination address is identified, the caller is notified through the appropriate tone and the call is terminated.
To disable the timeouts interdigit timer, set the seconds value to 0.
Examples
The following example sets the interdigit timeout value on the Cisco 3600 series for 10 seconds:
voice-port 1/0/0timeouts interdigit 10The following example sets the interdigit timeout value on the Cisco MC3810 multiservice concentrator for 10 seconds:
voice-port 1/1timeouts interdigit 10Related Commands
timeouts initial
Configures the initial digit timeout value for a specified voice port.
timeouts ringing
To configure the timeout value for ringing, use the timeouts ringing command in voice-port configuration mode. To restore the default value, use the no form of this command.
timeouts ringing {seconds | infinity}
no timeouts ringing
Syntax Description
Defaults
180 seconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The timeouts ringing command provides the capability to limit the length of time for which a caller can continue ringing a telephone when there is no answer.
Examples
The following example configures voice port 1/1 on a Cisco MC3810 to allow ringing for 600 seconds:
voice-port 1/1timeouts ringing 600The following example configures voice port 0/0/1 on a Cisco 3600 series router to allow ringing for 600 seconds:
voice-port 0/0/1timeouts ringing 600Related Commands
timeouts initial
Configures the initial digit timeout value for a voice port.
timeouts interdigit
Configures the interdigit timeout value for a voice port.
timeouts wait-release
To configure the delay timeout before the system starts the process for releasing voice ports, use the timeouts wait-release command in voice-port configuration mode. To restore the default value, use the no form of this command.
timeouts wait-release {seconds | infinity}
no timeouts wait-release
Syntax Description
Defaults
30 seconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use the timeouts wait-release command to limit the time a voice port can be held in a call failure state. After the timeout, the release sequence is enabled.
You can also use this command for voice ports with Foreign Exchange Station (FXS) loop-start signaling to specify the time allowed for a caller to hang up before the voice port goes into the parked state.
Examples
The following example configures voice port 1/1 on a Cisco MC3810 to stay in the call-failure state for 180 seconds while a busy tone, reorder tone, or out-of-service tone is sent to the voice port:
voice-port 1/1timeouts wait-release 180The following example configures voice port 0/0/1 on a Cisco 3600 series router to stay in the call-failure state for 180 seconds while a busy tone, reorder tone, or out-of-service tone is sent to the voice port:
voice-port 0/0/1timeouts wait-release 180Related Commands
timeouts initial
Configures the initial digit timeout value for a voice port.
timeouts interdigit
Configures the interdigit timeout value for a voice port.
timers
To configure the Session Initiation Protocol (SIP) signaling timers, use the timers command in the Session Initiation Protocol (SIP) user agent configuration mode. To restore the default value, use the no form of this command.
timers {trying number | connect number | disconnect number | expires number}
no timers {trying number | connect number | disconnect number | expires number}
Syntax Description
Defaults
The default for trying, connect, and disconnect is 500. The default for expires is 180,000.
Command Modes
SIP user agent configuration
Command History
Usage Guidelines
If you used the previous version of this command to configure timers, your previous timer settings will be maintained. The output of the show running configuration command will reflect both timers.
To reset this command to the default value, you can also use the default command.
Examples
The following example configures the SIP signaling timers to wait 500 milliseconds for a 100 response to an INVITE request:
sip-uatimers trying 500timing clear-wait
To indicate the minimum amount of time between the inactive seizure signal and the call being cleared for a specified voice port, use the timing clear-wait command in voice-port configuration mode. To reset the default value, use the no form of this command.
timing clear-wait milliseconds
no timing clear-wait milliseconds
Syntax Description
Defaults
400 milliseconds
Command Modes
Voice-port configuration
Command History
Examples
The following example configures the clear-wait duration on a Cisco 3600 series voice port to 300 milliseconds:
voice-port 1/0/0timing clear-wait 300The following example configures the clear-wait duration on a Cisco MC3810 multiservice concentrator voice port to 300 milliseconds:
voice-port 1/1timing clear-wait 300Related Commands
timing delay-duration
To specify the delay signal duration for a specified voice port, use the timing delay-duration command in voice-port configuration mode. To reset the default value, use the no form of this command.
timing delay-duration milliseconds
no timing delay-duration milliseconds
Syntax Description
milliseconds
Delay signal duration for delay dial signaling, in milliseconds. Valid entries are numbers from 100 to 5000. Supported on E&M ports only.
Defaults
2000 milliseconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The call direction for the timing delay-duration command is out.
Examples
The following example configures the delay signal duration on a Cisco 3600 series voice port for 3000 milliseconds:
voice-port 1/0/0timing delay-duration 3000The following example configures the delay signal duration on a Cisco MC3810 multiservice concentrator voice port for 3000 milliseconds:
voice-port 1/1timing delay-duration 3000Related Commands
timing delay-start
To specify the minimum delay time from outgoing seizure to out-dial address for a specified voice port, use the timing delay-start command in voice-port configuration mode. To reset the default value, use the no form of this command.
timing delay-start milliseconds
no timing delay-start milliseconds
Syntax Description
milliseconds
Minimum delay time, in milliseconds, from outgoing seizure to outdial address. Valid entries are numbers from 20 to 2000. Supported on E&M ports only.
Defaults
300 milliseconds on the Cisco 3600 series.
150 milliseconds on the Cisco MC3810 multiservice concentrator.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The call direction for the timing delay-start command is out.
Examples
The following example configures the delay-start duration on a Cisco 3600 series voice port for 250 milliseconds:
voice-port 1/0/0timing delay-start 250The following example configures the delay-start duration on a Cisco MC3810 multiservice concentrator voice port for 250 milliseconds:
voice-port 1/1timing delay-start 250Related Commands
timing delay-with-integrity
To specify the duration of the wink pulse for the delay dial for a specified voice port on the Cisco MC3810, use the timing delay-with-integrity command in voice-port configuration mode. To reset the default value, use the no form of this command.
timing delay-with-integrity milliseconds
no timing delay-with-integrity milliseconds
Syntax Description
milliseconds
Duration of the wink pulse for the delay dial, in milliseconds. Valid entries are numbers from 0 to 5000. Supported on E&M ports only.
Defaults
Zero (0)
Command Modes
Voice-port configuration
Command History
11.3(1)MA
This command was introduced on Cisco MC3810 multiservice concentrators.
Usage Guidelines
This command applies only to the Cisco MC3810 multiservice concentrator.
Examples
The following example configures the duration of the wink pulse for the delay dial on a Cisco MC3810 voice port for 10 milliseconds:
voice-port 1/1timing delay-with-integrity 10Related Commands
timing dial-pulse min-delay
To specify the time between wink-like pulses for a specified voice port, use the timing dial-pulse min-delay command in voice-port configuration mode. To reset the default value, use the no form of this command.
timing dial-pulse min-delay milliseconds
no timing dial-pulse min-delay milliseconds
Syntax Description
milliseconds
Time, in milliseconds, between the generation of wink-like pulses. Valid entries are integers from 0 to 5000.
Defaults
300 milliseconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use the timing dial-pulse min-delay command with PBXs that require a wink-like pulse, even though they have been configured for delay-dial signaling. If the value for this argument is set to 0, the router will not generate this wink-like pulse. The call signal direction for this command is in.
Examples
The following example configures the time between the generation of wink-like pulses on a Cisco 3600 series voice port for 350 milliseconds:
voice-port 1/0/0timing dial-pulse min-delay 350Related Commands
timing dialout-delay
To specify the dial-out delay for the sending digit on a specified voice port on the Cisco MC3810 multiservice concentrator, use the timing dialout-delay command in voice-port configuration mode. To reset the default value, use the no form of this command.
timing dialout-delay milliseconds
no timing dialout-delay milliseconds
Syntax Description
milliseconds
Dial-out delay, in milliseconds, for the sending digit or cut-through on an FXO trunk or an E&M immediate trunk. Valid entries are from 100 to 5000 milliseconds.
Defaults
300 milliseconds
Command Modes
Voice-port configuration
Command History
11.3(1)MA
This command was introduced on Cisco MC3810 multiservice concentrators.
Usage Guidelines
This command applies only to the Cisco MC3810 multiservice concentrator.
Examples
The following example configures the dial-out delay on a Cisco MC3810 multiservice concentrator voice por
