Feedback
Contents
call fallback through called-number (dial peer)
- call fallback
- call fallback active
- call fallback cache-size
- call fallback cache-timeout
- call fallback expect-factor
- call fallback icmp-ping
- call fallback icmp-ping (dial peer)
- call fallback instantaneous-value-weight
- call fallback jitter-probe dscp
- call fallback jitter-probe num-packets
- call fallback jitter-probe precedence
- call fallback jitter-probe priority-queue
- call fallback key-chain
- call fallback map address-list
- call fallback map subnet
- call fallback monitor
- call fallback probe-timeout
- call fallback reject-cause-code
- call fallback threshold delay loss
- call fallback threshold icpif
- call fallback wait-timeout
- call filter match-list
- call forward all
- call forward cancel
- call-forward-to-voicemail
- call history max
- call-history-mib
- call-progress-analysis
- call language voice
- call language voice load
- call leg dump event-log
- call leg event-log
- call leg event-log dump ftp
- call leg event-log errors-only
- call leg event-log max-buffer-size
- call leg history event-log save-exception-only
- callmonitor
- call preserve
- call-route
- call-router h323-annexg
- call-routing hunt-scheme
- call rscmon update-timer
- call rsvp-sync
- call rsvp-sync resv-timer
- call service stop
- call spike
- call start
- call threshold global
- call threshold interface
- call threshold poll-interval
- call treatment action
- call treatment cause-code
- call treatment isdn-reject
- call treatment on
- call-waiting
- called-number (dial peer)
call fallback
To enable a call request to fall back to a specific dial peer in case of network congestion, use the callfallback command in dial peer configuration mode. To disable PSTN fallback for a specific dial peer, use the no form of this command.
Command Default
This command is enabled by default if the callfallbackactive command is enabled in global configuration mode
Usage Guidelines
Disabling the callfallback command for a dial peer causes the call fallback subsystem not to fall back to the specified dial peer. Disabling the command is useful when internetworking fallback capable H.323 gateways with the Cisco CallManager or third-party equipment that does not run fallback. Connected calls are not affected by this feature.
Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers.
call fallback cache-size
Specifies the call fallback cache size for network traffic probe entries.
call fallback cache-timeout
Specifies the time after which the cache entries of network conditions are purged.
call fallback instantaneous-value-weight
Configures the call fallback subsystem to take an average from the last two cache entries for call requests.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe precedence
Specifies the priority of the jitter-probe transmission.
call fallback jitter-probe priority-queue
Assigns a priority queue for jitter-probe transmissions.
call fallback key-chain
Specifies use of MD5 authentication for sending and receiving SAA probes.
call fallback map address-list
Specifies that the call fallback router keep a cache table by IP addresses of distances for several destination peers that are sitting behind the router.
call fallback map subnet
Specifies that the call fallback router keep a cache table by subnet addresses of distances for several destination peers that are sitting behind the router.
call fallback probe-timeout
Sets the timeout for an SAA probe for call fallback purposes.
call fallback threshold delay loss
Specifies that the call fallback threshold use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
dial-peer voice number
Enters dial peer configuration mode.
show call fallback config
Displays the call fallback configuration.
call fallback active
To enable the Internet Control Message Protocol (ICMP)-ping or Service Assurance Agent (SAA) (formerly Response Time Reporter [RTR]) probe mechanism for use with the dial-peer monitorprobe or voice-port busyoutmonitorprobe commands, use the callfallbackactive command in global configuration mode. To disable these probe mechanisms, use the no form of this command.
Command Default
This command is disabled by default. If the command is entered without an optional keyword, the default is RTR.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented for Cisco 7500 series.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
The callfallbackactive command creates and maintains a consolidated cache of probe results for use by the dial-peer monitorprobe or voice-port busyoutmonitorprobe commands.
Enabling the callfallbackactive command determines whether calls should be accepted or rejected on the basis of probing of network conditions. The callfallbackactive command checks each call request and rejects the call if the network congestion parameters are greater than the value of the configured threshold parameters of the destination. If this is the case, alternative dial peers are tried from the session application layer.
Use thecallfallbackthresholddelayloss or callfallbackthresholdicpif command to set the threshold parameters.
Connected calls are not affected by this command.
Caution
The callfallbackactiveicmp-ping command must be entered before the callfallbackicmp-ping command can be used. If you do not enter this command first, the callfallbackicmpping command will not work properly.
NoteThe Cisco SAA functionality in Cisco IOS software was formerly known as Response Time Reporter (RTR). The command-line interface still uses the keyword rtr for configuring RTR probes, which are now actually SAA probes.
Examples
The following example enables the callfallbackactivecommand and globally enables ICMP pinging to probe target destinations. The second command specifies values for the ping packets:
Router(config)# call fallback active icmp-ping Router(config)# call fallback icmp-ping codec g729 interval 10 loss 10Related Commands
Command
Description
call fallback cache-size
Specifies the call fallback cache size for network traffic probe entries.
call fallback cache-timeout
Specifies the time after which the cache entries of network conditions are purged.
call fallback instantaneous-value-weight
Specifies the call fallback subsystem to take an average from the last two cache entries for call requests.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe precedence
Specifies the priority of the jitter-probe transmission.
call fallback jitter-probe priority-queue
Assigns a priority queue for jitter-probe transmissions.
call fallback key-chain
Specifies use of MD5 authentication for sending and receiving SAA probes.
call fallback map address-list
Specifies that the call fallback router keep a cache table by IP addresses of distances for several destination peers that are sitting behind the router.
call fallback map subnet
Specifies that the call fallback router keep a cache table by subnet addresses of distances for several destination peers that are sitting behind the router.
call fallback probe-timeout
Sets the timeout for an SAA probe for call fallback purposes.
call fallback threshold delay loss
Specifies that the call fallback threshold use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
dial-peer voice number
Enters dial peer configuration mode.
call fallback cache-size
To specify the call fallback cache size for network traffic probe entries, use the callfallbackcachesize command in global configuration mode. To restore the default value, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced..
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were introduced on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
The cache size can be changed only when the callfallbackactive command is not enabled.
The overflow process deletes up to one-fourth of the cache entries to allow for additional calls beyond the specified cache size. The cache entries chosen for deletion are the oldest entries in the cache.
If the cache size is left unchanged, it can be changed only when fallback is off. Use the no form of the callfallback command to turn fallback off.
Examples
The following example specifies 120 cache entries:
Router(config)# call fallback cache-size 120Related Commands
Command
Description
call fallback
Enables a call request to fall back to a specific dial peer in case of network congestion
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback cache-timeout
Specifies the time after which the cache entries of network conditions are purged.
show call fallback cache
Displays the current ICPIF estimates for all IP addresses in the cache.
show call fallback config
Displays the call fallback configuration.
call fallback cache-timeout
To specify the time after which the cache entries of network conditions are purged, use the callfallbackcachetimeout command in global configuration mode. To disable the callfallbackcache-timeout command, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
Enabling the callfallbackcachetimeout command sends a Service Assurance Agent (SAA) probe out to the network to determine the amount of congestion in terms of configured thresholds. The network condition is based upon delay and loss, or Calculated Planning Impairment Factor (ICPIF) thresholds. Use thecallfallbackthresholddelayloss or callfallbackthresholdicpif command to set the threshold parameters.
The cache keeps entries for every network congestion - checking probe sent and received between timeouts. The cache updates after each probe returns the current condition of network traffic. To set the probe frequency, use the callfallbackprobetimeout command.
When a call comes into the router, the router matches a dial peer and obtains the destination information. The router calls the fallback subsystem to look up the specified destination in its network traffic cache. If the delay/loss or ICPIF threshold exists and is current, the router uses that value to decide whether to permit the call into the Voice over IP (VoIP) network. If the router determines that the network congestion is below the configured threshold (by looking at the value in the cache), the call is connected.
After each call request, the timer is reset. Purging of the cache occurs only when the cache has received no call requests during the timeout period (seconds). When the cache timeout expires, the entire cache is deleted, and a probe is sent to start a new cache entry. A call cannot be completed until this probe returns with network traffic information.
The network congestion probes continue in the background as long as the entry for the last call request remains in the cache.
Examples
The following example specifies an elapsed time of 1200 seconds before the cache times out:
Router(config)# call fallback cache-timeout 1200Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback cache-size
Specifies the call fallback cache size.
call fallback probe-timeout
Specifies the time after which the cache entries of network conditions are purged.
call fallback threshold delay loss
Configures the call fallback threshold to use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
show call fallback cache
Displays the current ICPIF estimates for all IP addresses in the cache.
show call fallback config
Displays the call fallback configuration.
call fallback expect-factor
To set a configurable value by which the call fallback expect factor feature will be activated, use the callfallbackexpect-factorcommand in global configuration mode. To disable the expect factor, use the no form of this command.
Usage Guidelines
The expect-factor is the level of expected voice quality that the user may have during a call. For example, you expect higher voice quality from a call on your home than on your cell phone. The expect-factor is a subjective value determined by the local administrators.
Call fallback is used by the software to generate a series of probes across an IP network to help make a Impairment/Calculated Impairment Planning Factor (ICPIF) calculation. The value calculated by the probes, ICPIF, is modified by the configured expect factor using the following formula:
ICPIF = Idd + Ie-A
Idd represents the impairment due to end-end delay, Ie, represents the impairment due to packet loss and the impact of the codec being used on the call, and A represents the expect-factor value. The expect-factor is the value to be subtracted from the calculated ICPIF value. This expect factor is known as the Advantage Factor (A) as specified in G.107 and takes into account the user’s expected level of voice quality based upon the type of call being made.
Examples
The following example shows the callfallbackexpect-factorcommand and the callfallbackthresholdicpicf command being configured. A calculated ICPIF value of 20 based on Idd and Ie from the probes set on a IP network would not activate the call fallback feature in this configuration. Even though the calculated ICPIF value of 20 exceeds the configured threshold of 10, subtraction of the expect-value of 15 would leave a value of 5, which is below the threshold value.
Router(config)# call fallback expect-factor 15 Router(config)# call fallback threshold icpif 10Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers.
call fallback cache-size
Specifies the call fallback cache size for network traffic probe entries.
call fallback cache-timeout
Specifies the time after which the cache entries of network conditions are purged.
call fallback instantaneous-value-weight
Configures the call fallback subsystem to take an average from the last two cache entries for call requests.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe precedence
Specifies the priority of the jitter-probe transmission.
call fallback jitter-probe priority-queue
Assigns a priority queue for jitter-probe transmissions.
call fallback key-chain
Specifies use of MD5 authentication for sending and receiving SAA probes.
call fallback map address-list
Specifies that the call fallback router keep a cache table by IP addresses of distances for several destination peers that are sitting behind the router.
call fallback map subnet
Specifies that the call fallback router keep a cache table by subnet addresses of distances for several destination peers that are sitting behind the router.
call fallback probe-timeout
Sets the timeout for an SAA probe for call fallback purposes.
call fallback threshold delay loss
Specifies that the call fallback threshold use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
dial-peer voice number
Enters dial peer configuration mode.
show call fallback config
Displays the call fallback configuration.
call fallback icmp-ping
To specify Internet Control Message Protocol (ICMP) ping as the method for network traffic probe entries to IP destinations and configure parameters for the ping packets, use the callfallbackicmp-ping command in global configuration mode. To restore the default value, use the no form of this command.
call fallback icmp-ping [ count packets | sizebytes ] intervalseconds [ [ loss [percent] ] ] timeoutmilliseconds
no call fallback icmp-ping [ count packets | sizebytes ] intervalseconds [ [ loss [percent] ] ] timeoutmilliseconds
Syntax Description
Command Default
If this command is not configured, Response Time Reporter (RTR) is the probe method used.
Usage Guidelines
The values configured by the global configuration version of the callfallbackicmp-ping command are appllied globally for measurements on probes and pings. If the callfallbackicmp-ping is configured in dial-peer configuration mode, these values override the global configuration for the specific dial peer.
One of these two commands must be in effect before the monitorprobeicmp-ping command can be used. If neither of the callfallback commands is in effect, the monitorprobeicmp-ping command will not work properly.
Examples
The following example shows how to configure an ICMP ping probe with a G.729 profile to probe the link with an interval value of 10 seconds and a packet-loss threshold of 10 percent:
call fallback active icmp-ping call fallback icmp-ping codec g729 interval 10 loss 10Related Commands
Command
Description
call fallback active
Forces a voice port into the busyout state.
call fallback icmp-ping (dial peer)
Specifies Internet Control Message Protocol (ICMP) ping as the method for network traffic probe entries to IP destinations.
monitor probe icmp-ping
Enables dial-peer status changes based on the results of probes.
call fallback icmp-ping (dial peer)
To specify Internet Control Message Protocol (ICMP) ping as the method for network traffic probe entries to IP destinations, use the callfallbackicmp-ping command in dial-peer configuration mode. To restore the default value, use the no form of this command.
Command Default
If this command is not entered, the globally configured method is used for measurements.
Usage Guidelines
The principal use of this command is to specify ICMP ping as the probe method, even though the option for selecting RTR is also available.
If the callfallbackicmp-ping command is not entered, the callfallbackactive command in global configuration is used for measurements. If the callfallbackicmp-ping command is entered, these values override the global configuration.
One of these two commands must be in effect before the monitorprobeicmp-ping command can be used. If neither of the callfallback commands is in effect, the monitorprobeicmp-ping command will not work properly.
NoteThe Cisco Service Assurance Agent (SAA) functionality in Cisco IOS software was formerly known as Response Time Reporter (RTR). The command-line interface still uses the keyword rtr for configuring RTR probes, which are now actually the SAA probes.
Examples
The following example specifies that ICMP ping is used for monitoring the session target IP address and for updating the status of the dial peer:
Router(config)# dial-peer voice 10 voip Router(config-dial-peer)# call fallback icmp-pingRelated Commands
Command
Description
call fallback
Enables a call request to fall back to a specific dial peer in case of network congestion
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
monitor probe icmp-ping
Specifies that ICMP ping is the method used for probes.
show call fallback config
Displays the call fallback configuration.
call fallback instantaneous-value-weight
To configure the call fallback subsystem to take an average from the last two probes registered in the cache for call requests, use the callfallbackinstantaneousvalueweight command in global configuration mode. To return to the default before the average was calculated, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
Probes that return the network congestion information are logged into the cache to determine whether the next call request is granted. When the network is regularly busy, the cache entries reflect the heavy traffic conditions. However, one probe may return with low traffic conditions, which is in contrast to normal conditions. All call requests received between the time of this probe and the next use this entry to determine call acceptance. These calls are allowed through the network, but before the next probe is sent and received, the normal, heavy traffic conditions must have returned. The calls sent through congest the network and cause worsen traffic conditions.
Use the callfallbackinstantaneousvalueweightcommand to gradually recover from heavy traffic network conditions. While the system waits for a call, probes update the cache. When a new probe is received, the percentage is set and indicates how much the system is to rely upon the new probe and the previous cache entry. If the percentageis set to 50 percent, the system enters a cache entry based upon an average from the new probe and the most recent entry in the cache. Call requests use this blended entry to determine acceptance. This allows the call fallback subsystem to keep conservative measures of network congestion.
The configured percentateapplies to the new probe first. If the callfallbackinstantaneousvalueweightcommand is configured with the default percentageof 66 percent, the new probe is given a higher value to calculate the average for the new cache entry.
call fallback jitter-probe dscp
To specify the differentiated services code point (DSCP) of the jitter-probe transmission, use the callfallbackjitter-probedscpcommand in global configuration mode. To disable this feature and restore the default value of jitter-probe precedence, use the no form of this command.
Usage Guidelines
Network devices that support differentiated services (DiffServ) use a DSCP in the IP header to select a per-hop behavior (PHB) for a packet. Cisco implements queuing techniques that can base their PHB on the IP precedence or DSCP value in the IP header of a packet. On the basic of DSCP or IP precedence, traffic can be put into a particular service class. Packets within a service class are treated alike.
The callfallbackjitter-probedscp command allows you to set a DSCP for jitter-probe packets. The specified DSCP is stored, displayed, and passed in probing packets to the Service Assurance Agent (SAA). This command enables the router to reserve some bandwidth so that during network congestion some of the jitter-probe packets do not get dropped. This command avoids the conflict that occurs with traditional precedence bits.
The callfallbackjitter-probedscp command is mutually exclusive with the callfallbackjitter-probeprecedence command. Only one of these command can be enabled on the router. When the callfallbackjitter-probedscp command is configured, the precedence value is replaced with the DSCP value. The nocallfallbackjitter-probedscp command restores the default value for precedence.
Examples
The following example specifies the jitter-probe DSCP as 10. DSCP configuration replaces the set jitter-probe precedence value with the DSCP value.
call fallback jitter-probe dscp 10The following configuration disables the DSCP value and restores the default value for precedence, which is set to 2:
no call fallback jitter-probe dscpRelated Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe precedence
Specifies the priority of the jitter-probe transmission.
call fallback jitter-probe priority-queue
Assigns a priority queue for jitter-probe transmissions.
show call fallback config
Displays the call fallback configuration.
call fallback jitter-probe num-packets
To specify the number of packets in a jitter probe used to determine network conditions, use the callfallbackjitterprobenumpackets command in global configuration mode. To restore the default number of packets, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
A jitter probe, consisting of 2 to 50 packets, details the conditions of the network. More than one packet is used by the probe to calculate an average of delay/loss or Calculated Planning Impairment Factor (ICPIF). After the packets return to the probe, the probe delivers the traffic information to the cache where it is logged for call acceptance/denial. Use thecallfallbackthresholddelayloss or callfallbackthresholdicpif command to set the threshold parameters. The newly specified number of packets take effect only for new probes.
To get a more realistic estimate on the network congestion, increase the number of packets. If more probing packets are sent, better estimates of network conditions are obtained, but the bandwidth for other network operations is negatively affected. Use fewer packets when you need to maximize bandwidth.
call fallback jitter-probe precedence
To specify the priority of the jitter-probe transmission, use the callfallbackjitter-probeprecedencecommandinglobal configuration mode. To restore the default priority, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
Every IP packet has a precedence header. Precedence is used by various queueing mechanisms in routers to determine the priority of traffic passing through the system.
Use the callfallbackjitter-probeprecedencecommand if there are different queueing mechanisms in your network. Enabling the callfallbackjitter-probeprecedencecommand sets the precedence for jitter probes to pass through your network.
If you require your probes to be sent and returned quickly, set the precedence to a low number (0 or 1): the lower the precedence, the higher the priority given.
The callfallbackjitter-probeprecedence command is mutually exclusive with the callfallbackjitter-probedscp command. Only one of these commands can be enabled on the router. Usually the callfallbackjitter-probeprecedence command is enabled. When the callfallbackjitter-probedscp command is configured, the precedence value is replaced by the DSCP value. To disable DSCP and restore the default jitter probe precedence value, use the nocallfallbackjitter-probedscp command.
Examples
The following example specifies a jitter-probe precedence of 5, or low priority.
call fallback jitter-probe precedence 5The following configuration restores the default value for precedence:
no call fallback jitter-probe precedenceRelated Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback jitter-probe dscp
Specifies the dscp of the jitter-probe transmission.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe priority-queue
Assigns a priority queue for jitter-probe transmissions.
show call fallback config
Displays the call fallback configuration.
call fallback jitter-probe priority-queue
To assign a priority queue for jitter-probe transmissions, use thecallfallbackjitter-probepriority-queuecommandinglobal configuration mode. To return to the default state, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
This command is applicable only if the queueing method used is IP Real-Time Transport Protocol (RTP) priority. This command is unnecessary when low latency queueing (LLQ) is used because these packets follow the priority queue path (or not) based on the LLQ classification criteria.
This command works by choosing between sending the probe on an odd or even Service Assurance Agent (SAA) port number. The SAA probe packets go out on randomly selected ports chosen from within the top end of the audio User Datagram Protocol (UDP) defined port range (16384 to 32767). The port pair (RTP Control Protocol [RTCP] port) is selected, and by default, SAA probes for call fallback use the RTCP port (odd) to avoid going into the priority queue, if enabled. If call fallback is configured to use the priority queue, the RTP port (even) is selected.
Examples
The following example specifies that a probe be sent to an SAA port:
Router(config)# call fallback jitter-probe priority-queue
NoteIn order for this command to have any effect on the probes, the IP priority queueing must be set for UDP voice ports numbered from 16384 to 32767.
Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe precedence
Specifies the jitter-probe precedence.
ip rtp priority
Provides a strict priority queueing scheme for delay-sensitive data.
show call fallback config
Displays the call fallback configuration.
call fallback key-chain
To specify the use of message digest algorithm 5 (MD5) authentication for sending and receiving Service Assurance Agents (SAA) probes, use the callfallbackkeychain command in global configuration mode. To disable MD5, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
This command is used to enable the SAA probe authentication using MD5. If MD5 authentication is used, the keys on the sender and receiver routers must match.
Examples
The following example specifies "sample" as the fallback key chain:
Router(config)# call fallback key-chain sampleRelated Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
key chain
Enables authentication for routing protocols by identifying a group of authentication keys.
key-string
Specifies the authentication string for a key.
show call fallback config
Displays the call fallback configuration.
call fallback map address-list
To specify that the call fallback router keep a cache table by IP addresses of distances for several destination peers, use the callfallbackmapaddresslist command in global configuration mode. To restore the default values, use the no form of this command.
call fallback map map target ip-address address-list ip-address1 . .. ip-address7
no call fallback map map target ip-address address-list ip-address1 . .. ip-address7
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
Use this command when several destination peers are in one common node.
Call fallback map setup allows the decongestion of traffic caused by a high volume of call probes sent across a network to query a large number of dial peers. One router/common node can keep the distances in a cache table of the numerous IP addresses/destination peers in a network. When the fallback is queried for network congestion to a particular IP address (that is, the common node), the map addresses are searched to find the target IP address. If a match is determined, the probes are sent to the target address rather than to the particular IP address.
In the figure below, the three routers (1, 2, and 3) keep the cache tables of distances for the destination peers behind them. When a call probe comes from somewhere in the IP cloud, the cache routers check their distance tables for the IP address/destination peer where the call probe is destined. This distance checking limits congestion on the networks behind these routers by directing the probe to the particular IP address and not to the entire network.
Examples
The following example specifies call fallback map address-list configurations for 172.32.10.1 and 172.46.10.1:
Router(config)# call fallback map 1 target 172.32.10.1 address-list 172.32.10.2 172.32.10.3 172.32.10.4 172.32.10.5 172.32.10.6 172.32.10.7 172.32.10.8 Router(config)# call fallback map 2 target 172.46.10.1 address-list 172.46.10.2 172.46.10.3 172.46.10.4 172.46.10.5 172.46.10.6 172.46.10.7 172.46.10.8Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback map subnet
Specifies that the call fallback router keep a cache table by subnet addresses of distances for several destination peers that are sitting behind the router.
show call fallback config
Displays the call fallback configuration.
call fallback map subnet
To specify that the call fallback router keep a cache table by subnet addresses of distances for several destination peers, use the callfallbackmapsubnet command in global configuration mode. To restore the default values, use the no form of this command.
call fallback map map target ip-address subnet ip-network netmask
no call fallback map map target ip-address subnet ip-network netmask
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command is supported on the Cisco AS5850 in this release.
Usage Guidelines
Use this command when several destination peers are in one common node.
Call fallback map setup allows the decongestion of traffic caused by a high volume of call probes sent across a network to query a large number of dial peers. One router/common node can keep the distances in a cache table of the numerous IP addresses within a subnet (destination peers) in a network. When the fallback is queried for network congestion to a particular IP address (that is, the common node), the map addresses are searched to find the target IP address. If a match is determined, the probes are sent to the target address rather than to the particular IP address.
In the figure below, the three routers (1, 2, and 3) keep the cache tables of distances for the destination peers behind them. When a call probe comes from somewhere in the IP cloud, the cache routers check their distance tables for the subnet address/destination peer where the call probe is destined. This distance checking limits congestion on the networks behind these routers by directing the probe to the particular subnet address and not to the entire network.
Examples
The following examples specify the callfallbackmapsubnet configuration for two different IP addresses:
Router(config)# call fallback map 1 target 209.165.201.225 subnet 209.165.201.224 255.255.255.224 Router(config)# call fallback map 2 target 209.165.202.225 subnet 209.165.202.224 255.255.255.224Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback map address-list
Specifies that the call fallback router keep a cache table by IP addresses of distances for several destination peers that are sitting behind the router.
show call fallback config
Displays the call fallback configuration.
call fallback monitor
To enable the monitoring of destinations without call fallback to alternate dial peers, use the callfallbackmonitorcommandinglobal configuration mode. To disable monitoring without fallback, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were introduced on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
The callfallbackmonitorcommand is used as a statistics collector of network conditions based upon probes (detailing network traffic) and connected calls. There is no H.323 call checking/rejecting as with the callfallbackactive command. All call requests are granted regardless of network traffic conditions.
Configure thecallfallbackthresholddelayloss or callfallbackthresholdicpif command to set threshold parameters. The thresholds are ignored, but for statistics collecting, configuring one of the thresholds allows you to monitor cache entries for either delay/loss or Calculated Planning Impairment Factor (ICPIF) values.
Examples
The following example enables the callfallbackmonitorcommand:
Router(config)# call fallback monitorRelated Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback threshold delay loss
Specifies that the call fallback threshold use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
show call fallback config
Displays the call fallback configuration.
call fallback probe-timeout
To set the timeout for a Service Assurance Agent (SAA) probe for call fallback purposes, use the callfallbackprobetimeoutcommand in global configuration mode. To restore the default value, use thenoform of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were implemented on the Cisco 7200 series and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
SAA probes collect network traffic information based upon configured delay and loss or Calculated Planning Impairment Factor (ICPIF) values and report this information to the cache for call request determination. Use thecallfallbackthresholddelayloss or callfallbackthresholdicpif command to set the threshold parameters.
When the probe timeout expires, a new probe is sent to collect network statistics. To reduce the bandwidth taken up by the probes, increase the probe - timeout interval (seconds). Probes do not have a great effect upon bandwidth unless several thousand destinations are involved. If this is the case in your network, use a longer timeout. If you need more network traffic information, and bandwidth is not an issue, use a lower timeout. The default interval, 30 seconds, is a low timeout.
When the callfallbackcachetimeout command is configured or expires, new probes are initiated for data collection.
Examples
The following example configures a 120-second interval:
Router(config)# call fallback probe-timeout 120Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback cache-timeout
Specifies the time after which the cache entries of network conditions are purged.
call fallback threshold delay loss
Specifies that the call fallback threshold use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
show call fallback config
Displays the call fallback configuration.
call fallback reject-cause-code
To enable a specific call fallback reject cause code in case of network congestion, use the callfallbackrejectcausecodecommand in global configuration mode. To reset the code to the default of 49, use the no form of this command.
Usage Guidelines
Enabling the callfallbackrejectcausecodecommanddetermines the code to display when calls are rejected because of probing of network conditions.
NoteConnected calls are not affected by this command.
Examples
The following example enables the callfallbackrejectcausecodecommand and specifies cause code 34:
call fallback reject-cause-code 34Related Commands
Command
Description
call fallback cache-size
Specifies the call fallback cache size for network traffic probe entries.
call fallback cache-timeout
Specifies the time after which the cache entries of network conditions are purged.
call fallback instantaneous-value-weight
Specifies that the call fallback subsystem take an average from the last two cache entries for call requests.
call fallback jitter-probe num-packets
Specifies the number of packets in a jitter probe that are used to determine network conditions.
call fallback jitter-probe precedence
Specifies the priority of the jitter - probe transmission.
call fallback jitter-probe priority-queue
Assigns a priority queue for jitter-probe transmissions.
call fallback key-chain
Specifies MD5 authentication for sending and receiving SAA probes.
call fallback map address-list
Specifies that the call fallback router keep a cache table by IP addresses of distances for several destination peers that are sitting behind the router.
call fallback map subnet
Specifies that the call fallback router keep a cache table by subnet addresses of distances for several destination peers that are sitting behind the router.
call fallback probe-timeout
Sets the timeout for an SAA probe for call fallback purposes.
call fallback threshold delay loss
Specifies that the call fallback threshold use only packet delay and loss values.
call fallback threshold icpif
Specifies that call fallback use the ICPIF threshold.
show call fallback config
Displays the call fallback configuration.
call fallback threshold delay loss
To specify that the call fallback threshold use only packet delay and loss values, use the callfallbackthresholddelaylosscommandinglobal configuration mode. To restore the default value, use the no form of this command.
call fallback threshold delay milliseconds loss percent
no call fallback threshold delay milliseconds loss percent
Usage Guidelines
During times of heavy voice traffic, two parties in a conversation may notice a significant delay in transmission or hear only part of a conversation because of voice-packet loss.
Use the callfallbackthresholddelaylosscommand to configure parameters for voice quality. Lower values of delay and loss allow higher quality of voice. Call requests match the network information in the cache with the configured thresholds of delay and loss.
The amount of delay set by the callfallbackthresholddelayloss command should not be more than half the amount of the time-to-wait value set by the callfallbackwait-timeout command; otherwise the threshold delay will not work correctly. Because the default value of the callfallbackwait-timeout command is set to 300 ms, the user can configure a delay of up to 150 ms for the callfallbackthresholddelayloss command. If the user wants to configure a higher threshold, the time-to-wait delay has to be increased from its default (300 ms) using the callfallbackwait-timeoutcommand.
NoteThe delay configured by the callfallbackthresholddelayloss command corresponds to a one-way delay, whereas the time-to-wait period configured by the callfallbackwait-timeout command corresponds to a round-trip delay.
If you enable the callfallbackactivecommand, the call fallback subsystem uses the last cache entry compared with the configured delay/loss threshold to determine whether the call is connected or denied. If you enable the callfallbackmonitorcommand, all calls are connected, regardless of the configured threshold or voice quality. In this case, configuring the callfallbackthresholddelaylosscommand allows you to collect network statistics for further tracking.
NoteThe callfallbackthresholddelaylosscommand differs from the call fallback threshold icpif command because thecallfallbackthresholddelaylosscommanduses only packet delay and loss parameters, and the call fallback threshold icpif command uses packet delay and loss parameters plus other International Telecommunication Union (ITU) G.113 factors to gather impairment information.
Setting this command does not affect bandwidth. Available bandwidth for call requests is determined by the call fallback subsystem using probes. The number of probes on the network affects bandwidth.
Examples
The following example configures a threshold delay of 20 ms and a threshold loss of 50 percent:
Router(config)# call fallback threshold delay 20 loss 50Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback monitor
Enable the monitoring of destinations without call fallback to alternate dial peers.
call fallback threshold icpif
Specifies the ICPIF threshold.
call fallback wait-timeout
Specifies the time to wait for a response to a probe.
show call fallback config
Displays the call fallback configuration.
call fallback threshold icpif
To specify that call fallback use the Calculated Planning Impairment Factor (ICPIF) threshold, use the callfallbackthresholdicpifcommand in global configuration mode. To restore the default value, use the no form of this command.
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)T
The PSTN Fallback feature and enhancements were introduced on the Cisco 7200 series routers and integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(8)T
Support for the Cisco AS5850 is not included in this release.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
During times of heavy voice traffic, the parties in a conversation may notice a significant delay in transmission or hear only part of a conversation because of voice-packet loss.
Use the callfallbackthresholdicpifcommand to configure parameters for voice quality. A low ICPIF value allows for higher quality of voice. Call requests match the network information in the cache with the configured ICPIF threshold. If you enable the callfallbackactivecommand, the call fallback subsystem uses the last cache entry compared with the configured ICPIF threshold to determine whether the call is connected or denied. If you enable thecallfallbackmonitorcommand, all calls are connected regardless of the configured threshold or voice quality. In this case, configuring the callfallbackthresholdicpifcommand allows you to collect network statistics for further tracking.
A lower ICPIF value tolerates less delay and loss of voice packets (according to ICPIF calculations). Use lower values for higher quality of voice. Configuring a value of 34 equates to 100 percent packet loss.
The ICPIF is calculated and used according to the International Telecommunication Union (ITU) G.113 specification.
NoteThe callfallbackthresholddelaylosscommand differs from the call fallback threshold icpif command because the callfallbackthresholddelaylosscommand uses only packet delay and loss parameters, while the call fallback threshold icpif command uses packet delay and loss parameters plus other ITU G.113 factors to gather impairment information.
Setting this command does not affect bandwidth. Available bandwidth for call requests is determined by the call fallback subsystem using probes. The number of probes on the network affects bandwidth.
Examples
The following example sets the ICPIFthresholdto 20:
Router(config)# call fallback threshold icpif 20Related Commands
Command
Description
call fallback active
Enables a call request to fall back to alternate dial peers in case of network congestion.
call fallback monitor
Enables the monitoring of destinations without call fallback to alternate dial peers.
call fallback threshold delay loss
Specifies the call fallback threshold delay and loss values.
show call fallback config
Displays the call fallback configuration.
call fallback wait-timeout
To modify the time to wait for a response to a probe, use the callfallbackwait-timeoutcommand in global configuration mode. To return to the default value, use the no form of this command.
Usage Guidelines
This command is enabled by default. The time to wait for a response to a probe is set to 300 ms. This command allows the user to modify the amount of time to wait for a response to a probe. The milliseconds argument allows the user to configure a time-to-wait value from 100 ms and 3000 ms. A user that has a higher-latency network may want to increase the value of the default timer.
The time-to-wait period set by the callfallbackwait-timeout command should always be greater than or equal to twice the amount of the threshold delay time set by the callfallbackthresholddelayloss command; otherwise the probe will fail.
NoteThe delay configured by the callfallbackthresholddelayloss command corresponds to a one-way delay, whereas the time-to-wait period configured by callfallbackwait-timeout command corresponds to a round-trip delay. The threshold delay time should be set at half the value of the time-to-wait value.
call filter match-list
To enter the call filter match list configuration mode and create a call filter match list for debugging voice calls, use the callfiltermatch-listcommand in global configuration mode. To remove the filter, use the no form of this command.
call filter match-list number { voice | gatekeeper }
no call filter match-list number { voice | gatekeeper }
Syntax Description
number
Numeric label that uniquely identifies the match list. The range is 1 to 16.
voice
Sets the conditions for filtering voice call debugging.
gatekeeper
Defines the conditions on the gatekeeper.
The gatekeeper keyword is available only if the Cisco IOS image contains the gatekeeper debug filter functionality or a combination of gateway and gatekeeper debug filter functionality.
Usage Guidelines
After the conditions are set with this command, use the debugconditionmatch-list command in privileged EXEC mode to get the filtered debug output and debug voice calls.
Examples
The following example shows that the call filter match list designated as list 1 filters the debug output for an incoming calling number matching 8288807, an incoming called number matching 6560729, and on incoming port 7/0:D:
call filter match-list 1 voice incoming calling-number 8288807 incoming called-number 6560729 incoming port 7/0:Dcall forward all
To define a a feature code for a Feature Access Code (FAC) to access Call Forward All (CFA) on an analog phone, use the callforwardallcommand in STC application feature access-code configuration mode. To return the code to its default, use the no form of this command.
Syntax Description
keypad-character
Character string that can be dialed on a telephone keypad (0-9, *, #). Default: 1.
Before Cisco IOS Release 12.4(20)YA, this is a single character. In Cisco IOS Release 12.5(20)YA and later releases, the string can be any of the following:
- A single character (0-9, *, #)
- Two digits (00-99)
- Two to four characters (0-9, *, #) and the leading or ending character must be an asterisk (*) or number sign (#)
In Cisco IOS Release 15.0(1)M and later releases, the string can also be any of the following:
- Three digits (000-999)
- Four digits (0000-9999)
Usage Guidelines
This command changes the value of the feature code for Call Forward All from the default (1) to the specified value.
In Cisco IOS Release 12.4(20)YA and later releases, if the length of the keypad-character argument is at least two characters and the leading or ending character of the string is an asterisk (*) or a number sign (#), phone users are not required to dial a prefix to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 78#, the phone user dials only 78#, without the FAC prefix, to access the corresponding feature.
In Cisco IOS Release 15.0(1)M and later releases, if the length of the keypad-character argument is three or four digits, phone users are not required to dial a prefix or any special characters to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 788, the phone user dials only 788, without the FAC prefix, to access the corresponding feature.
In Cisco IOS Release 12.4(20)YA and later releases, if you attempt to configure this command with a value that is already configured for another FAC, for a speed-dial code, or for the Redial FSD, you receive a 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 showstcappfeaturecodes command.
In Cisco IOS Release 12.4(20)YA and later releases, if you attempt to configure this command with a value that precludes or is precluded by another FAC, by a speed-dial code, or by the Redial FSD, you receive a message. If you configure a feature code to a value that precludes or is precluded by another code, the system always executes the call feature with the shortest code and ignores the longer code. For example, #1 will always preclude #12 and #123. You must configure a new value for the precluded code in order to enable phone user access to that feature.
To display a list of all FACs, use the showstcappfeaturecodes command.
Examples
The following example shows how to change the value of the feature code for Call Forward All from the default (1). This configuration also changes the value of the prefix for all FACs from the default (**) to ##. With this configuration, a phone user must press ##3 on the keypad and then dial a target number, to forward all incoming calls to the target number.
Router(config)# stcapp feature access-code Router(config-stcapp-fac)# prefix ## Router(config-stcapp-fac)# call forward all 3 Router(config-stcapp-fac)# exitThe following example shows how to configure all-numeric three or four digit flexible feature access codes so that users are not required to dial a prefix or special characters:
VG224(config-stcapp-fac)# call forward all 111 do not use prefix. call forward all is 111Related Commands
Command
Description
call-forward all
Configures call forwarding so that all incoming calls to a particular directory number are forwarded to another directory number.
call forward cancel
Defines a feature code for a feature access code (FAC) to cancel the call-forward-all condition.
call forward to voicemail
Configures call forwarding to voicemail so that all incoming calls are forwarded to voicemail.
prefix (stcapp-fac)
Defines the prefix for feature access codes (FACs).
show stcapp feature codes
Displays all feature access codes (FACs).
stcapp feature access-code
Enables feature access codes (FACs) and enters STC application feature access-code configuration mode for changing values of the prefix and features codes from the default.
call forward cancel
To define a a feature code for a Feature Access Code (FAC) to access Call Forward All Cancel, use the callforwardcancelcommand in STC application feature access-code configuration mode. To return the feature code to its default, use the no form of this command.
Syntax Description
keypad-character
Character string that can be dialed on a telephone keypad (0-9, *, #). Default: 2.
Before Cisco IOS Release 12.4(20)YA, this is a single character. In Cisco IOS Release 12.4(20)YA and later releases, the string can be any of the following:
- A single character (0-9, *, #)
- Two digits (00-99)
- Two to four characters (0-9, *, #) and the leading or ending character must be an asterisk (*) or number sign (#)
In Cisco IOS Release 15.0(1)M and later releases, the string can also be any of the following:
- Three digits (000-999)
- Four digits (0000-9999)
Usage Guidelines
This command changes the value of the feature code for Call Forward All Cancel from the default (2) to the specified value.
In Cisco IOS Release 12.4(20)YA and later releases, if the length of the keypad-character argument is at least two characters and the leading or ending character of the string is an asterisk (*) or a number sign (#), phone users are not required to dial a prefix to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 78#, the phone user dials only 78#, without the FAC prefix, to access the corresponding feature.
In Cisco IOS Release 15.0(1)M and later releases, if the length of the keypad-character argument is three or four digits, phone users are not required to dial a prefix or any special characters to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 788, the phone user dials only 788, without the FAC prefix, to access the corresponding feature.
In Cisco IOS Release 12.4(20)YA and later releases, if you attempt to configure this command with a value that is already configured for another FAC, for a speed-dial code, or for the Redial FSD, you receive a 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 showstcappfeaturecodes command.
In Cisco IOS Release 12.4(20)YA and later releases, if you attempt to configure this command with a value that precludes or is precluded by another FAC, by a speed-dial code, or by the Redial FSD, you receive a message. If you configure a feature code to a value that precludes or is precluded by another code, the system always executes the call feature with the shortest code and ignores the longer code. For example, #1 will always preclude #12 and #123. You must configure a new value for the precluded code in order to enable phone user access to that feature.
To display a list of all FACs, use the showstcappfeaturecodes command.
NoteTo disable call-forward-all on a particular directory number associated with SCCP endpoints connected to Cisco Unified CME through an analog voice gateway, use the nocall-forwardallcommand in ephone-dn or ephone-dn-template configuration mode.
Examples
The following example shows how to change the value of the feature code for Call Forward Cancel from the default (2). This configuration also changes the value of the prefix for all FACs from the default (**) to ##. With this configuration, a phone user must press ##3 on the phone keypad to cancel all-call forwarding.
Router(config)# stcapp feature access-code Router(config-stcapp-fac)# prefix ## Router(config-stcapp-fac)# call forward cancel 3 Router(config-stcapp-fac)# exitRelated Commands
Command
Description
call forward all
Defines the feature code in the feature access code (FAC) for forwarding all calls.
call-forward all
Configures call forwarding so that all incoming calls to a particular directory number are forwarded to another directory number.
prefix (stcapp-fac)
Defines the prefix for feature access codes (FACs).
show stcapp feature codes
Displays all feature access codes (FACs).
stcapp feature access-code
Enables feature access codes (FACs) and enters STC application feature access-code configuration mode for changing values of the prefix and features codes from the default.
call-forward-to-voicemail
To configure forwarding of calls to voicemail so that all incoming calls to a directory number are forwarded to voicemail, use the forward-to-voicemailcommand. The stcappfeatureaccess-code command must be enabled on the Cisco voice gateway. To disable call forwarding, use theno form of this command.
Usage Guidelines
In Cisco IOS Release 15.0(1)M and later releases, if the length of the keypad-character argument is three or four digits, phone users are not required to dial a prefix or any special characters to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 788, the phone user dials only 788, without the FAC prefix, to access the corresponding feature.
The FAC for forward-to-voicemail follows the same rules as for other FAC, such as callforwardall, in terms of allowable string as its FAC code.
Examples
The following example show how to configure forward-to-voicemail using a four digit code:
VG224(config-stcapp-fac)# forward-to-voicemail 1234 do not use prefix. forward-to-voicemail is 1234Related Commands
Command
Description
call-forward all
Configures call forwarding so that all incoming calls to a particular directory number are forwarded to another directory number.
call forward cancel
Defines a feature code for a FAC to cancel the call-forward-all condition.
show stcapp feature codes
Displays all FACs.
stcapp feature access-code
Enables FACs and enters STC application feature access-code configuration mode for changing values of the prefix and features codes from the default.
call history max
To retain call history information and to specify the number of call records to be retained, use the callhistorymax command in global configuration mode.
Command Default
If this command is not configured, no call history is maintained for disconnected calls. If the command is configured, the default value for number of records is 15.
Usage Guidelines
The number of disconnected calls displayed is the number specified in the number argument. This maximum number helps to reduce CPU usage in the storage and reporting of this information.
call-history-mib
To define the history MIB parameters, use the call-history-mibcommand in global configuration mode. To disable the configured parameters, use the no form of this command.
call-history-mib { max-size num-of-entries | retain-timer seconds }
no call-history-mib { max-size num-of-entries | retain-timer seconds }
Syntax Description
max-size
Specifies the maximum size of the call history MIB table.
number-of-entries
Number of entries in the call history MIB table. The valid range is from 0 to 500. The default value is 100.
retain-timer
Specifies the timer for entries in the call history MIB table.
seconds
Time in minutes, for removing an entry. The valid range is from 0 to 500. The default time is 15 minutes.
Usage Guidelines
CISCO-CALL-HISTORY-MIB describes the objects defined and used for storing the call information for all calls. The MIB contains a table that stores the past call information. The call information will include the destination number, the call connect time, the call disconnect time and the disconnection cause. These calls could be circuit switched or they could be virtual circuits. The history of each call will be stored. An entry will be created when a call gets disconnected. At the time of creation, the entry will contain the connect time and the disconnect time and other call information.
The history table is characterized by two values, the maximum number (number-of-entries) of entries that could be stored in a period of time (seconds).
The max-size value specifies the maximum size of the call history MIB table.
Theretain-timer value specifies the length of time, in minutes, that entries will remain in the call history MIB table. Setting the value to 0 prevents any call history from being retained.
call-progress-analysis
To activate call progress analysis (CPA) for a digital signal processor (DSP) farm profile on the Cisco Unified Border Element (Cisco UBE), use the call-progress-analysis command in DSP farm profile configuration mode. To disable this command from your configuration, use the no form of this command.
Command History
Release Modification 15.3(2)T
This command was introduced.
Cisco IOS XE Release 3.9S
This command was integrated into Cisco IOS XE Release 3.9S.
Usage Guidelines
Use the call-progress-analysis command to activate CPA on Cisco UBE. This command is applicable only for local transcoding interface (LTI)-based DSP farm profiles, which has associate application CUBE applied on the respective DSP farm profiles. This command is not available on Skinny Call Control Protocol (SCCP)-based DSP farm profiles. If CPA is not activated on the DSP farm profile, you cannot configure the CPA timing and threshold parameters for VoIP calls.
call language voice
To configure an external Tool Command Language (Tcl) module for use with an interactive voice response (IVR) application, use the calllanguagevoicecommandinglobal configuration mode.
Usage Guidelines
The built-in languages are English (en) , Chinese (ch) , and Spanish (sp) . If you specify "en" , "ch" , or sp" , the new Tcl module replaces the built-in language functionality. When you add a new Tcl module, you create your own prefix to identify the language. When you configure and load the new languages, any upper-layer application (Tcl IVR) can use the language.
You can use the language abbreviation in the language argument of any callapplicationvoice command. The language and the text-to-speech (TTS) notations are available for the IVR application to use after they are defined by the Tcl module.
Examples
The following example adds Russian (ru) as a Tcl module:
call language voice ru tftp://box/unix/scripts/multi-lang/ru_translate.tclRelated Commands
Command
Description
call application voice
Configures an application.
debug voip ivr
Specifies the type of VoIP IVR debug output that you want to view.
param language
Configures the language parameter in a service or package on the gateway.
show language voice
Displays information about configured languages and applications.
call language voice load
To load or reload a Tool Command Language (Tcl) module from the configured URL location, use the calllanguagevoiceload command in EXEC mode.
Usage Guidelines
You cannot use this command if the interactive voice response (IVR) application using the language that you want to configure has an active call. A language that is configured under an IVR application is not necessarily in use. To determine if a call is active, use the showcallapplicationvoice command.
call leg dump event-log
To flush the event log buffer for call legs to an external file, use the calllegdumpevent-logcommand in privileged EXEC mode.
Usage Guidelines
This command immediately writes the event log buffer to the external file whose location is defined with the calllegevent-logdumpftp command in global configuration mode.
NoteThe calllegdumpevent-log command and the calllegevent-logdumpftp command are two different commands.
Examples
The following example writes the event log buffer to an external file named leg_elogs:
Router(config)# call leg event-log dump ftp ftp-server/elogs/leg_elogs.log username myname password 0 mypass Router(config)# exit Router# call leg dump event-logRelated Commands
Command
Description
call leg event-log
Enables event logging for voice, fax, and modem call legs.
call leg event-log dump ftp
Enables the voice gateway to write the contents of the call-leg event log buffer to an external file.
call leg event-log max-buffer-size
Sets the maximum size of the event log buffer for each call leg.
monitor call leg event-log
Displays the event log for an active call leg in real-time.
show call leg
Displays event logs and statistics for voice call legs.
call leg event-log
To enable event logging for voice, fax, and modem call legs, use the calllegevent-log command in global configuration mode. To reset to the default, use the no form of this command.
Usage Guidelines
This command enables event logging for telephony call legs. IP call legs are not supported.
NoteTo prevent event logging from adversely impacting system performance for production traffic, the system includes a throttling mechanism. When free processor memory drops below 20%, the gateway automatically disables all event logging. It resumes event logging when free memory rises above 30%. While throttling is occurring, the gateway does not capture any new event logs even if event logging is enabled. You should monitor free memory on the gateway and enable event logging only when necessary to isolate faults.
Examples
The following example enables event logging for all telephony call legs:
call leg event-logRelated Commands
Command
Description
call leg dump event-log
Flushes the event log buffer for call legs to an external file.
call leg event-log dump ftp
Enables the voice gateway to write the contents of the call-leg event log buffer to an external file.
call leg event-log error-only
Restricts event logging to error events only for voice call legs.
call leg event-log max-buffer-size
Sets the maximum size of the event log buffer for each call leg.
call leg history event-log save-exception-only
Saves to history only event logs for call legs that had at least one error.
monitor call leg event-log
Displays the event log for an active call leg in real-time.
show call leg
Displays event logs and statistics for voice call legs.
call leg event-log dump ftp
To enable the gateway to write the contents of the call-leg event log buffer to an external file, use the calllegevent-logdumpftpcommand in global configuration mode. To reset to the default, use the no form of this command.
call leg event-log dump ftp server [ :port ] file username username password [ ecryption-type ] password
no call leg event-log dump ftp
Syntax Description
server
Name or IP address of FTP server where the file is located.
: port
(Optional) Specific port number on the server.
/ file
Name and path of the file.
username username
Username required for accessing the file.
password encryption-type
(Optional) The Cisco proprietary algorithm used to encrypt the password. Values are 0 or 7. 0 disables encryption; 7 enables encryption. If you specify 7, you must enter an encrypted password (a password already encrypted by a Cisco router).
password
Password required for accessing the file.
Usage Guidelines
This command enables the gateway to automatically write the event log buffer to the named file either after an active call leg terminates or when the event log buffer becomes full. The default buffer size is 4 KB. To modify the size of the buffer, use the calllegevent-logmax-buffer-size command. To manually flush the event log buffer, use the calllegdumpevent-logcommand in privileged EXEC mode.
NoteThe calllegdumpevent-log command and the calllegevent-logdumpftp command are two different commands.
Enabling the gateway to write event logs to FTP could adversely impact gateway memory resources in some scenarios, for example, when:
- The gateway is consuming high processor resources and FTP does not have enough processor resources to flush the logged buffers to the FTP server.
- The designated FTP server is not powerful enough to perform FTP transfers quickly.
- Bandwidth on the link between the gateway and the FTP server is not large enough.
- The gateway is receiving a high volume of short-duration calls or calls that are failing.
You should enable FTP dumping only when necessary and not enable it in situations where it might adversely impact system performance.
Examples
The following example enables the gateway to write call leg event logs to an external file named leg_elogs.log on a server named ftp-server:
call leg event-log dump ftp ftp-server/elogs/leg_elogs.log username myname password 0 mypassThe following example specifies that call leg event logs are written to an external file named leg_elogs.log on a server with the IP address 10.10.10.101:
call leg event-log dump ftp 10.10.10.101/elogs/leg_elogs.log username myname password 0 mypassRelated Commands
Command
Description
call leg dump event-log
Flushes the event log buffer for call legs to an external file.
call leg event-log
Enables event logging for voice, fax, and modem call legs.
call leg event-log error-only
Restricts event logging to error events only for voice call legs.
call leg event-log max-buffer-size
Sets the maximum size of the event log buffer for each call leg.
call leg history event-log save-exception-only
Saves to history only event logs for call legs that had at least one error.
monitor call leg event-log
Displays the event log for an active call leg in real-time.
show call leg
Displays event logs and statistics for voice call legs.
call leg event-log errors-only
To restrict event logging to error events only for voice call legs, use the calllegevent-logerrors-onlycommand in global configuration mode. To reset to the default, use the no form of this command.
Usage Guidelines
This command limits the severity level of the events that are logged; it does not enable logging. You must use this command with the calllegevent-log command, which enables event logging for call legs.
Examples
The following example shows how to capture event logs only for call legs with errors:
Router(config)# call leg event-log Router(config)# call leg event-log errors-onlyRelated Commands
Command
Description
call leg event-log
Enables event logging for voice, fax, and modem call legs.
call leg event-log dump ftp
Enables the gateway to write the contents of the call-leg event log buffer to an external file.
call leg event-log max-buffer-size
Sets the maximum size of the event log buffer for each call leg.
call leg history event-log save-exception-only
Saves to history only event logs for call legs that had at least one error.
monitor call leg event-log
Displays the event log for an active call leg in real-time.
show call leg
Displays event logs and statistics for voice call legs.
call leg event-log max-buffer-size
To set the maximum size of the event log buffer for each call leg, use the calllegevent-logmax-buffer-sizecommand in global configuration mode. To reset to the default, use the no form of this command.
Usage Guidelines
If the event log buffer reaches the limit set by this command, the gateway allocates a second buffer of equal size. The contents of both buffers is displayed when you use the showcallleg command. When the first event log buffer becomes full, the gateway automatically appends its contents to an external FTP location if the calllegevent-logdumpftpcommand is used.
A maximum of two buffers are allocated for an event log. If both buffers are filled, the first buffer is deleted and another buffer is allocated for new events (buffer wraps around). If the calllegevent-logdumpftp command is configured and the second buffer becomes full before the first buffer is dumped, event messages are dropped and are not recorded in the buffer.
Examples
The following example sets the maximum buffer size to 8 KB:
call leg event-log max-buffer-size 8Related Commands
Command
Description
call leg dump event-log
Flushes the event log buffer for call legs to an external file.
call leg event-log dump ftp
Enables the voice gateway to write the contents of the call-leg event log buffer to an external file.
monitor call leg event-log
Displays the event log for an active call leg in real-time.
show call leg
Displays event logs and statistics for voice call legs.
call leg history event-log save-exception-only
To save to history only event logs for call legs that had at least one error, use the callleghistoryevent-logsave-exception-only command in global configuration mode. To reset to the default, use the no form of this command.
Usage Guidelines
Call leg event logs move from the active to the history table after the call leg terminates. If you use this command, event logs are saved only for those legs that had errors. Event logs for normal legs that do not contain any errors are not saved.
NoteThis command does not affect records saved to an FTP server by using the calllegdumpevent-log command.
Examples
The following example saves to history only call leg records that have errors:
call leg history event-log save-exception-onlyRelated Commands
Command
Description
call leg dump event-log
Flushes the event log buffer for call legs to an external file.
call leg event-log
Enables event logging for voice, fax, and modem call legs.
call leg event-log error-only
Restricts event logging to error events only for voice call legs.
call leg event-log max-buffer-size
Sets the maximum size of the event log buffer for each call leg.
show call leg
Displays event logs and statistics for voice call legs.
callmonitor
To enable call monitoring messaging functionality on a SIP endpoint in a VoIP network, use the callmonitor command in voice-service configuration mode. To return to the default, use the no form of this command.
Usage Guidelines
Use this command in voice service configuration mode to allow a SIP endpoint, such as an external feature server, to watch call activity on a VoIP network.
To view call activity, use the showcallmoncommand.
call preserve
To enable the preservation of H.323 VoIP calls, use thecallpreserve command in h323, voice-class, and voice-service configuration modes. To reset to the default, use the no form of this command.
Command Modes
h323
Voice-class configuration (config-voice-class)
Voice-service configuration (config-voi-serv)Usage Guidelines
The callpreservecommand activates H.323 VoIP call preservation for following types of failures and connections:
Failure Types
- WAN failures that include WAN links flapping or degraded WAN links
- Cisco Unified CallManager software failure, such as when the ccm.exe service crashes on a Cisco Unified CallManager server.
- LAN connectivity failure, except when a failure occurs at the local branch
Connection Types
- During Cisco Unified CallManager reloads
- When a Transmission Control Protocol (TCP) connection between one or both endpoints and Cisco Unified CallManager used for signaling H.225.0 or H.245 messages is lost or flapping
- Between endpoints that are registered to different Cisco Unified CallManagers in a cluster and the TCP connection between the two Cisco Unified CallManagers is lost
- Between IP phones and the PSTN at the same site
- When the softswitch reloads.
- When the H.225.0 or H.245 TCP connection between the gateway and the softswitch is lost, and the softswitch does not clear the call on the endpoint
- When the H.225.0 or H.245 TCP connection between softswitch and the endpoint is lost, and the soft-switch does not clear the call on the gateway
- Call flows that involve a Cisco IP in IP (IPIP) gateway running in media flow-around mode that reload or lose connection with the rest of the network
When bidirectional silence and RTP and RTCP inactivity detection are configured, they are enabled for all calls by default. To enable them for H.323 VoIP preserved calls only, you must use the callpreservecommand’s limit-media-detection keyword.
H.323 VoIP call preservation can be applied globally to all calls and to a dial peer.
Examples
The following example enables H.323 VoIP call preservation for all calls.
voice service voip h323 call preserveThe following configuration example enables H.323 VoIP call preservation for dial peer 1.
voice-class h323 4 call preserve dial-peer voice 1 voip voice-class h323 4The following example enables H.323 VoIP call preservation and enables RTP and RTCP inactivity detection and bidirectional silence detection for preserved calls only:
voice service voip h323 call preserve limit-media-detectionThe following example enables RTP and RTCP inactivity detection. Note that for H.323 VoIP call preservation VAD must be set to off (novad command).
dial-peer voice 10 voip no vad gateway timer receive-rtcp ip rtcp report-intervalThe following configuration example enables bidirectional silence detection:
gateway timer media-inactive ip rtcp report intervalcall-route
To enable Header-Based routing, at the global configuration level, use the call-route command in voice service VoIP SIP configuration mode. To disable Header-Based routing, use the no form of this command.
call-route { dest-route-string | p-called-party-id | history-info | url }
no call-route { dest-route-string | p-called-party-id | history-info | url }
Command Default
Support for call routing based on the header in a received INVITE message is disabled.
Command History
Release
Modification
12.4(22)YB
This command was introduced.
15.0(1)M
This command was integrated into Cisco IOS Release 15.0(1)M.
15.1(2)T
This command was modified. The history-info keyword was added.
Cisco IOS XE Release 3.3S
This command was integrated into Cisco IOS XE Release 3.3S.
15.2(1)T
This command was modified. The url keyword was added.
15.3(3)M
This command was modified. The dest-route-string keyword was added.
Cisco IOS XE Release 3.10S
This command was modified. The dest-route-string keyword was added.
Usage Guidelines
Use the call-route command to enable the Cisco Unified Border Element to route calls based on the Destination-Route-String, P-Called-Party-ID or History-Info header in a received INVITE message. If multiple call routes are configured, call routing enabled based on destination route string takes precedence over other header configurations. Destination route string configuration is applicable only for outbound dial-peer matching.
Examples
The following example shows how to enable call routing based on the header value:
Router> enable Router# configure terminal Router(config)# voiceservicevoip Router(conf-voi-serv)# sip Router(conf-serv-sip)# call-route dest-route-string Router(conf-serv-sip)# call-route p-called-party-id Router(conf-serv-sip)# call-route history-info Router(conf-serv-sip)# call-route urlcall-router h323-annexg
To enable the Annex G border element (BE) configuration commands by invoking H.323 Annex G configuration mode, use the call-router command in global configuration mode. To remove the definition of a BE, use the no form of this command.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T. This command does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series in this release.
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.
call-routing hunt-scheme
To enable capacity based load-balancing, use the call-routinghunt-schemecommand in gatekeeper configuration mode. To disable this function, use the no form of this command.
Usage Guidelines
Use the call-routinghunt-schemecommand to turn on load balancing based on capacity of gateway and verify that the gateway capacity reporting is enabled.
call rscmon update-timer
To change the value of the resource monitor throttle timer, use the callrscmonupdate-timer command in privileged EXEC mode. To revert to the default value, use the no form of this command.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T. This command does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series in this release.
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
This command specifies the duration of the resource monitor throttle timer. When events are delivered to the resource monitor process, the throttle timer is started and the event is processed after the timer expires (unless the event is a high-priority event). The timer ultimately affects the time it takes the gateway to send Resource Availability Indicator (RAI) messages to the gatekeeper. This command allows you to vary the timer according to your needs.
call rsvp-sync
To enable synchronization between Resource Reservation Protocol (RSVP) signaling and the voice signaling protocol, use the callrsvp-sync command in global configuration mode. To disable synchronization, use the no form of this command.
Command Default
Synchronization is enabled between RSVP and the voice signaling protocol (for example, H.323).
Command History
Release
Modification
12.1(3)XI
This command was introduced on the Cisco 2600 series, 3600 series, 7200 series, Cisco AS5300, Cisco AS5800, and Cisco MC3810.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
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.
Examples
The following example enables synchronization between RSVP and the voice signaling protocol:
call rsvp-syncRelated Commands
Command
Description
call rsvp-sync resv-timer
Sets the timer for reservation requests.
call start
Forces the H.323 Version 2 gateway to use fast connect or slow connect procedures for a dial peer.
debug call rsvp-sync events
Displays the events that occur during RSVP synchronization.
h323 call start
Forces an H.323 Version 2 gateway to use fast connect or slow connect procedures for all VoIP services.
ip rsvp bandwidth
Enables the use of RSVP on an interface.
show call rsvp-sync conf
Displays the RSVP synchronization configuration.
show call rsvp-sync stats
Displays statistics for calls that have attempted RSVP reservation.
call rsvp-sync resv-timer
To set the timer on the terminating VoIP gateway for completing RSVP reservation setups, use the callrsvp-syncresv-timer command in global configuration mode. To restore the default value, use the no form of this command.
Command History
Release
Modification
12.1(3)XI
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3600 series, Cisco 7200 series, Cisco AS5300, Cisco AS5800, and Cisco MC3810.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
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
The reservation timer is started on the terminating gateway when the session protocol receives an indication of the incoming call. This timer is not set on the originating gateway because the resource reservation is confirmed at the terminating gateway. If the reservation timer expires before the RSVP setup is complete, the outcome of the call depends on the acceptable quality of service (QoS) level configured in the dial peer; either the call proceeds without any bandwidth reservation or it is released. The timer must be set long enough to allow calls to complete but short enough to free up resources. The optimum number of seconds depends on the number of hops between the participating gateways and the delay characteristics of the network.
Examples
The following example sets the reservation timer to 30 seconds:
call rsvp-sync resv-timer 30Related Commands
Command
Description
call rsvp -sync
Enables synchronization of RSVP and the H.323 voice signaling protocol.
debug call rsvp -syncevents
Displays the events that occur during RSVP synchronization.
show call rsvp -syncconf
Displays the RSVP synchronization configuration.
show call rsvp -syncstats
Displays statistics for calls that have attempted RSVP reservation.
call service stop
To shut down VoIP call service on a gateway, use the callservicestopcommand in voice service SIP or voice service H.323 configuration mode. To enable VoIP call service, use the no form of this command. To set the command to its defaults, use the defaultcallservicestop command
Command Modes
Voice service SIP configuration (conf-serv-sip)
Voice service H.323 configuration (conf-serv-h323)Usage Guidelines
Use the callservicestop command to shut down the SIP or H.323 services regardless of whether the shutdown or noshutdown command was configured in voice service configuration mode.
Use the nocallservicestop command to enable SIP or H.323 services regardless of whether the shutdown or noshutdown command was configured in voice service configuration mode.
Use the defaultcallservicestop command to set the command to its defaults. The defaults are as follows:
- Shut downSIP or H.323 service, if the shutdown command was configured in voice service configuration mode.
- Enable SIP or H.323 service, if the noshutdown command was configured in voice service configuration mode.
Examples
The following example shows SIP call service being shut down on a Cisco gateway:
Router> enable Router# configure terminal Router(config)# voice service voip Router(conf-voi-serv)# sip Router(conf-serv-sip)# call service stopThe following example shows H.323 call service being enabled on a Cisco gateway:
Router> enable Router# configure terminal Router(config)# voice service voip Router(conf-voi-serv)# h323 Router(conf-serv-h323)# no call service stopThe following example shows SIP call service being enabled on a Cisco gateway because the noshutdown command was configured in voice service configuration mode:
Router> enable Router# configure terminal Router(config)#voice service voip Router(conf-voi-serv)# no shutdown Router(conf-voi-serv)# sip Router(conf-serv-sip)# default call service stopThe following example shows H.323 call service being shut down on a Cisco gateway because the shutdown command was configured in voice configuration mode:
Router> enable Router# configure terminal Router(config)# voice service voip Router(conf-voi-serv)# shutdown Router(conf-voi-serv)# h323 Router(conf-serv-h323)# default call service stopRelated Commands
Command
Description
bandwidth audio as-modifier
Allows SIP SDP bandwidth-related options.
billing b-channel
Enables the H.323 gateway to access B-channel information for all H.323 calls.
outbound-proxy
Configures an outbound proxy server.
telephony-service ccm-compatible
Enables the detection of a Cisco CallManager system in the network and allows the exchange of calls.
call spike
To configure the limit on the number of incoming calls received in a short period of time (a call spike), use the callspike command in global or dial peer voice configuration mode. To disable this command, use theno form of this command.
call spike call-number [ steps number-of-steps size milliseconds ]
no call spike
Dial Peer Voice Configuration Mode
call spike threshold [ steps number-of-steps size milliseconds ]
Syntax Description
call -number
Incoming call count for the spiking threshold. Range is 1 to 2147483647.
steps number -of-steps
(Optional) Specifies the number of steps for the spiking sliding window. Range is from 3 to 10. The default is 5.steps for the spiking sliding window.
size milliseconds
(Optional) Specifies step size in milliseconds. Range is from 100 to 250. The default is 200.
threshold
Threshold for the incoming call count for spiking. Range is 1 to 2147483647.
Command Default
The limit on the number of incoming calls received during a specified period is not configured.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. This release does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on Cisco 1750 and Cisco 1751 routers. Support for other Cisco platforms was not included in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers. Support for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 was not included in this release.
12.2(11)T
Support was added for the Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, and Cisco AS5850.
15.1(3)T
This command was modified. Support for this command was added in the dial peer level.
Usage Guidelines
A call spike occurs when a large number of incoming calls arrive from the Public Switched Telephone Network (PSTN) in a short period of time (for example, 100 incoming calls in 10 milliseconds). Setting this command allows you to control the number of call requests that can be received in a configured time period. The sliding window buffers the number of calls that get through. The counter resets according to the specified step size.
The period of the sliding window is calculated by multiplying the number of steps by the size. If an incoming call exceeds the configured call number during the period of the sliding window the call is rejected.
If the callspike is configured at both the global and dial-peer levels, the dial-peer level takes precedence and the call spike is calculated. If the call spike threshold is exceeded the call gets rejected, and the call spike calculation is done at the global level.
Examples
The following example shows how to configure the callspike command with a call-number and the of 1, a sliding window of 10 steps, and a step size of 200 milliseconds. The period of the sliding window is 2 seconds. If the gateway receives more than 1 call within 2 seconds the call is rejected.
Router(config)# call spike 1 steps 10 size 200The following example shows how to configure the callspike command with a call number of 30, a sliding window of 10 steps, and a step size of 2000 milliseconds:
Router(config)# call spike 30 steps 10 size 2000The following example shows how to configure the callspike command in dial peer voice mode with threshold of 20, a sliding window of 7, and a step size of 2000 milliseconds:
Router(config)# dial-peer voice 400 voip Router(config-dial-peer)# call spike 20 steps 7 size 2000call start
To force an H.323 Version 2 gateway to use either fast connect or slow connect procedures for a dial peer, use the callstart command in H.323 voice-service configuration mode. To restore the default setting, use the no form of this command.
Syntax Description
fast
Gateway uses H.323 Version 2 (fast connect) procedures.
slow
Gateway uses H.323 Version 1 (slow connect) procedures.
system
Gateway defaults to voice-service configuration mode.
interwork
Gateway interoperates between fast-connect and slow-connect procedures.
Note The interwork keyword is applicable to IP-to-IP gateways only and supports basic audio calls Dual-tone multi-frequency (DTMF), fax, and audio transcoding calls are not supported).
sync-rsvp slow-start
(Optional) Gateway uses Resource Reservation Protocol (RSVP) synchronization for slow-start calls.
Command History
Release
Modification
12.1(3)XI
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3600 series, Cisco 7200 series, Cisco AS5300, Cisco AS5800, and Cisco MC3810.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
12.2(2)XA
This command was changed to use the H.323 voice-service configuration mode from the voice-class configuration mode.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
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 implemented on the Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, and Cisco AS5850.
12.3(4)T
The synch-rsvpslow-startkeywords were added.
12.3(8)T
The interwork keyword was added.
Cisco IOS XE Release 3.3S
This command was integrated into Cisco IOS XE Release 3.3S.
Usage Guidelines
In Cisco IOS Release 12.1(3)XI and later releases, H.323 VoIP gateways by default use H.323 Version 2 (fast connect) for all calls, including those initiating RSVP. Previously, gateways used only slow-connect procedures for RSVP calls. To enable Cisco IOS Release 12.1(3)XI gateways to be backward-compatible with earlier releases of Cisco IOS Release 12.1T, the callstart command allows the originating gateway to initiate calls using slow connect.
The callstart command is configured as part of the voice class assigned to an individual VoIP dial peer. It takes precedence over theh323callstartcommand that is enabled globally to all VoIP calls, unless the system keyword is used, in which case the gateway defaults to Version 2.
The sync-rsvpslow-startkeyword, when used in H.323 voice-class configuration mode, controls RSVP synchronization for all slow-start calls handled by the gateway. When the sync-rsvpslow-startkeyword is used in an H.323 voice-class definition, the behavior can be specified for individual dial peers by invoking the voice class in dial-peer voice configuration mode. This command is enabled by default in some Cisco IOS images, and in this situation the showrunning-config command displays this information only when the noform of the command is used.
NoteThe callstart command supports only H.323 to H.323 calls.
The interwork keyword is only used with IP-to-IP gateways connecting fast connect from one side to slow connect on the other for basic audio calls. Configure the interwork keyword in voice-class H.323 configuration mode or on both the incoming and outgoing dial peers. Codecs must be specified on both dial peers for interworking to function. When the interwork keyword is configured, codecs need to be specified on both dial-peers and the codectransparent command should not be configured.
Examples
The following example shows slow connect for the voice class 1000 being selected:
voice service class h323 1000 call start slow ! dial-peer voice 210 voip voice-class h323 1000The following example shows the gateway configured to use the H.323 Version 1 (slow connect) procedures:
h323 call start slowRelated Commands
Command
Description
acc-qos
Selects the acceptable quality of service for a dial peer.
call rsvp-sync
Enables synchronization between RSVP and the H.323 voice signaling protocol.
call rsvp-sync resv-timer
Sets the timer for RSVP reservation setup.
codec transparent
Enables codec capabilities to be passed transparently between endpoints in a Cisco IPIPGW.
debug call rsvp-sync events
Displays the events that occur during RSVP synchronization.
h323
Enables H.323 voice service configuration commands.
req-qos
Selects the desired quality of service to use in reaching a dial peer.
show call rsvp-sync conf
Displays the RSVP synchronization configuration.
show call rsvp-sync stats
Displays statistics for calls that attempted RSVP reservation.
show running-config
Displays the contents of the currently running configuration file.
voice class h323
Enters voice-class configuration mode and creates a voice class for H.323 attributes.
call threshold global
To enable the global resources of a gateway, use the callthresholdglobalcommand in global configuration mode. To disable the global resources of the gateway, use the no form of this command.
call threshold global trigger-name low percent high percent [busyout] [treatment]
no call threshold global trigger-name
Syntax Description
trigger -name
Specifies the global resources on the gateway.
The trigger-nameargument can be one of the following:
- cpu-5sec --CPU utilization in the last 5 seconds.
- cpu-avg --Average CPU utilization.
- io-mem --I/O memory utilization.
- proc-mem --Processor memory utilization.
- total-calls --Total number of calls.
- total-mem --Total memory utilization.
low percent
Value of low threshold: Range is from 1 to 100% for the utilization triggers; 1 to 10000 calls for the total-calls.
high percent
Value of high threshold: Range is from 1 to 100% for the utilization triggers; 1 to 10000 calls for the total-calls.
busyout
(Optional) Busy out the T1/E1 channels if the resource is not available.
treatment
(Optional) Applies call treatment from the session application if the resource is not available.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. Support for the Cisco AS5300, Cisco AS5350, and Cisco AS5400 is not included in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on the Cisco 1750 and Cisco 1751 routers. Support for other Cisco platforms is not included in this release
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers. 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 implemented on the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5800 in this release.
Usage Guidelines
Use this command to enable a trigger and define associated parameters to allow or disallow new calls on the router. Action is enabled when the trigger value goes above the value specified by the high keyword and is disabled when the trigger drops below the value specified by the lowkeyword.
You can configure these triggers to calculate Resource Availability Indicator (RAI) information. An RAI is forwarded to a gatekeeper so that it can make call admission decisions. You can configure a trigger that is global to a router or is specific to an interface.
Examples
The following example shows how to busy out the total calls when a low of 5 or a high of 5000 is reached:
call threshold global total-calls low 5 high 5000 busyoutThe following example shows how to busy out the average CPU utilization if a low of 5 percent or a high of 65 percent is reached:
call threshold global cpu-avg low 5 high 65 busyoutRelated Commands
Command
Description
call threshold (interface)
Enables interface resources of a gateway.
call threshold poll-interval
Enables a polling interval threshold for CPU or memory.
clear call threshold
Clears enabled triggers and their associated parameters.
show call threshold
Displays enabled triggers, current values for configured triggers, and number of API calls that were made to global and interface resources.
call threshold interface
To enable interface resources of a gateway, use the call threshold interface command in global configuration mode. To disable the interface resources of the gateway, use the no form of this command.
call threshold interface type number { int-bandwidth { class-map name [ l2-overhead percentage ] | low low-threshold high high-threshold } [ midcall-exceed ] | int-calls low value high value }
no call threshold interface type number { int-bandwidth | int-calls }
Syntax Description
type
Interface type. For more information, use the question mark (?) online help function.
number
Interface or subinterface number. For more information about the numbering syntax for your networking device, use the question mark (?) online help function.
int-bandwidth
Configures the threshold bandwidth for VoIP media through an interface.
class-map name
Specifies a traffic class for the VoIP media traffic that is configured through Modular Quality of Service (MQS).
l2-overhead percentage
(Optional) Configures the Layer 2 overhead as the percentage of the configured bandwidth. This is the value by which the configured bandwidth will be deducted to obtain the IP bandwidth. The default value is 10 percent.
low low-threshold
Specifies the low threshold for the aggregate interface bandwidth value in Kbps. The range is from 8 to 2000000.
high high-threshold
Specifies the high threshold for the aggregate interface bandwidth value in Kbps. The range is from 8 to 2000000.
midcall-exceed
(Optional) Allows the bandwidth that exceeds the configured threshold during midcall media renegotiation.
int-calls
Specifies the number of calls that are transmitted through the interface.
low value
Specifies the low threshold for the number of calls allowed. The range is from 1 to 10000.
high value
Specifies the high threshold for the number of calls allowed. The range is from 1 to 10000.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. Support for the Cisco AS5300, Cisco AS5350, and Cisco AS5400 is not included in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on Cisco 1750 and Cisco 1751 routers. This command does not support any other Cisco platforms in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers. This command is not supported on Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 routers in this release.
15.2(2)T
This command was modified. The int-bandwidth, class-map name, l2-overhead percentage, low low-threshold, high high-threshold, and midcall-exceed keywords and arguments were added.
Usage Guidelines
Use this command to specify thresholds that allow or disallow new calls on the router.
Examples
The following example shows how to enable thresholds as low as 5 and as high as 2500 for interface calls on Ethernet interface 0/1:
Router> enable Router# configure terminal Router(config)# call threshold interface Ethernet 0/1 int-calls low 5 high 2500The following example shows how to configure the Cisco Unified Border Element (Cisco UBE) to reject new SIP calls when the VoIP media bandwidth on Gigabit Ethernet interface 0/0 exceeds 400 kbps and continues to have 100 Kbps:
Router> enable Router# configure terminal Router(config)# call threshold interface GigabitEthernet 0/0 int-bandwidth low 100 high 400The following example shows how to configure Cisco UBE to reject new SIP calls when the VoIP media bandwidth on Gigabit Ethernet interface 0/0 exceeds the configured bandwidth for priority traffic in the “voip-traffic” class:
Router> enable Router# configure terminal Router(config)# class-map match-all voip-traffic Router(config-cmap)# policy-map voip-policy Router(config-pmap)# class voip-traffic Router(config-pmap-c)# priority 440 Router(config-pmap-c)# end Router# configure terminal Router(config)# call threshold interface GigabitEthernet 0/0 int-bandwidth class-map voip-traffic l2-overhead 10Related Commands
Command
Description
call threshold (global)
Enables global resources of a gateway.
call threshold poll-interval
Enables a polling interval threshold for CPU or memory.
clear call threshold
Clears enabled triggers and their associated parameters.
show call threshold
Displays enabled triggers, current values for configured triggers, and the number of API calls that were made to global and interface resources.
call threshold poll-interval
To enable a polling interval threshold for assessing CPU or memory thresholds, use the callthresholdpoll-interval command in global configuration mode. To disable this command, use the no form of this command.
call threshold poll-interval { cpu-average | memory } seconds
no call threshold poll-interval { cpu-average | memory }
Syntax Description
cpu -average
The CPU average interval, in seconds. The default is 60.
memory
The average polling interval for the memory, in seconds. The default is 5.
seconds
Window of polling interval, in seconds. Range is from 10 to 300 for the CPU average interval, and from 1 to 60 for the memory average polling interval.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. Support for the Cisco AS5300, Cisco AS5350, and Cisco AS5400 is not included in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on Cisco 1750 and Cisco 1751 routers. This release does not support any other Cisco platforms in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 7200 series routers. This release does not support the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5800.
Examples
The following example shows how to specify that memory thresholds be polled every 10 seconds:
call threshold poll-interval memory 10Related Commands
Command
Description
call threshold
Enables the global resources of the gateway.
clear call threshold
Clears enabled triggers and their associated parameters.
show call threshold
Displays enabled triggers, current values for configured triggers, and number of API calls that were made to global and interface resources.
call treatment action
To configure the action that the router takes when local resources are unavailable, use the calltreatmentactioncommand in global configuration mode. To disable call treatment action, use the no form of this command.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. This command does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on the Cisco 1750 and Cisco 1751 routers. This command does not support any other Cisco platforms in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 7200 series routers. This command does not support the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 in this release.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T. Support was added for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5800.
Usage Guidelines
Use this command to define parameters to disconnect (with cause code), or hairpin, or whether a message or busy tone is played to the user.
Examples
The following example shows how to enable the call treatment feature with a "hairpin" action:
call treatment on call treatment action hairpinThe following example shows how to enable the call treatment feature with a "playmsg" action. The file "congestion.au" plays to the caller when local resources are not available to handle the call.
call treatment on call treatment action playmsg tftp://keyer/prompts/conjestion.auRelated Commands
Command
Description
call threshold
Clears enabled triggers and their associated parameters.
call treatment on
Enables call treatment to process calls when local resources are unavailable.
clear call treatment stats
Clears the call treatment statistics.
show call treatment
Displays the call treatment configuration and statistics for handling calls on the basis of resource availability.
call treatment cause-code
To specify the reason for the disconnection to the caller when local resources are unavailable, use the calltreatmentcause-codecommand in global configuration mode. To disable the call treatment cause-code specification, use the no form of this command.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. This command does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on the Cisco 1750 and Cisco 1751 routers. This command does not support any other Cisco platforms in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 7200 series routers. This command does not support the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 in this release.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T. Support was added for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5800.
Examples
The following example shows how to configure a call treatment cause code to reply with "no-Qos" when local resources are unavailable to process a call:
call treatment on call treatment cause-code no-QosRelated Commands
Command
Description
call threshold
Clears enabled triggers and their associated parameters.
call treatment on
Enables call treatment to process calls when local resources are unavailable.
clear call treatment stats
Clears the call treatment statistics.
show call treatment
Displays the call treatment configuration and statistics for handling calls on the basis of resource availability.
call treatment isdn-reject
To specify the rejection cause code for ISDN calls when all ISDN trunks are busied out and the switch ignores the busyout trunks and still sends ISDN calls into the gateway, use the calltreatmentisdn-rejectcommand in global configuration mode. To disable call treatment, use the no form of this command.
Syntax Description
cause-code 34
No circuit/channel available—The connection cannot be established because no appropriate channel is available to take the call.
cause-code 38
Network out of order—The destination cannot be reached because the network is not functioning correctly, and the condition might last for an extended period of time. An immediate reconnect attempt will probably be unsuccessful.
cause-code 41
Temporary failure—An error occurred because the network is not functioning correctly. The problem will be resolved shortly.
cause-code 42
Switching equipment congestion—The destination cannot be reached because the network switching equipment is temporarily overloaded.
cause-code 43
Access information discarded—Discarded information element identifier. The network cannot provide the requested access information.
cause-code 44
Requested circuit/channel not available—The remote equipment cannot provide the requested channel for an unknown reason. This might be a temporary problem.
cause-code 47
Resources unavailable, unspecified—The requested channel or service is unavailable for an unknown reason. This might be a temporary problem.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. This command does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on the Cisco 1750 and Cisco 1751 routers. This command does not support any other Cisco platforms in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 7200 series routers. This command does not support the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 in this release.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5800.
Usage Guidelines
Use this command only when all ISDN trunks are busied out and the switch ignores the busyout trunks and still sends ISDN calls into the gateway. The gateway should reject the call in the ISDN stack using the configured cause code.
Under any other conditions, the command has no effect.
Examples
The following example shows how to configure the call treatment to reply to an ISDN call with an ISDN rejection code for "temporary failure" when local resources are unavailable to process a call:
call treatment on call treatment isdn-reject 41Related Commands
Command
Description
call threshold
Clears enabled triggers and their associated parameters.
call treatment on
Enables call treatment to process calls when local resources are unavailable.
clear call treatment stats
Clears the call treatment statistics.
show call treatment
Displays the call treatment configuration and statistics for handling calls on the basis of resource availability.
call treatment on
To enable call treatment to process calls when local resources are unavailable, use the calltreatmentoncommand in global configuration mode. To disable call treatment, use the no form of this command.
Command History
Release
Modification
12.2(2)XA
This command was introduced.
12.2(4)T
The command was integrated into Cisco IOS Release 12.2(4)T. This command does not support the Cisco AS5300, Cisco AS5350, and Cisco AS5400 series in this release.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
12.2(4)XM
This command was implemented on the Cisco 1750 and Cisco 1751 routers. This command does not support any other Cisco platforms in this release.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 7200 series routers. This command does not support the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5850 in this release.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T. Support was added for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco AS5800.
Usage Guidelines
Use this command to enable a trigger and define associated parameters to disconnect (with cause code), or hairpin, or whether a message or busy tone is played to the user.
Examples
The following example shows how to enable the call treatment feature with a "hairpin" action:
call treatment on call treatment action hairpinThe following example shows how to enable the call treatment feature with a "playmsg" action. The file "congestion.au" plays to the caller when local resources are not available to handle the call.
call treatment on call treatment action playmsg tftp://keyer/prompts/conjestion.auThe following example shows how to configure a call treatment cause code to reply with "no-QoS" when local resources are unavailable to process a call:
call treatment on call treatment cause-code no-QoSRelated Commands
Command
Description
call threshold
Clears enabled triggers and their associated parameters.
call treatment action
Configures the action that the router takes when local resources are unavailable.
call treatment cause-code
Specifies the reason for the disconnection to the caller when local resources are unavailable.
call treatment isdn-reject
Specifies the rejection cause-code for ISDN calls when local resources are unavailable.
clear call treatment stats
Clears the call treatment statistics.
show call treatment
Displays the call treatment configuration and statistics for handling calls on the basis of resource availability.
call-waiting
To enable call waiting, use the call-waitingcommand in interface configuration mode. To disable call waiting, use the no form of this command.
Usage Guidelines
This command is applicable to Cisco 800 series routers.
You must specify this command when creating a dial peer. This command does not work if it is not specified within the context of a dial peer. For information on creating a dial peer, refer to the Cisco800SeriesRoutersSoftwareConfigurationGuide.
Related Commands
Command
Description
destination-pattern
Specifies either the prefix, the full E.164 telephone number, or an ISDN directory number (depending on the dial plan) to be used for a dial peer.
dial peer voice
Enters dial peer configuration mode, defines the type of dial peer, and defines the tag number associated with a dial peer.
port (dial peer)
Enables an interface on a PA-4R-DTR port adapter to operate as a concentrator port.
ring
Sets up a distinctive ring for telephones, fax machines, or modems connected to a Cisco 800 series router.
show dial peer voice
Displays configuration information and call statistics for dial peers.
called-number (dial peer)
To enable an incoming Voice over Frame Relay (VoFR) call leg to get bridged to the correct plain old telephone service (POTS) call leg when a static FRF.11 trunk connection is used, use the callednumbercommand in dial peer configuration mode. To disable a static trunk connection, use the no form of this command.
Usage Guidelines
The callednumbercommand is used only when the dial peer type is VoFR and you are using the frf11-trunk (FRF.11) session protocol. It is ignored at all times on all other platforms using the Cisco-switched session protocol.
Because FRF.11 does not provide any end-to-end messaging to manage a trunk, the callednumbercommand is necessary to allow the router to establish an incoming trunk connection. The E.164 number is used to find a matching dial peer during call setup.
Examples
The following example shows how to configure a static FRF.11 trunk connection to a specific telephone number (555-0150), beginning in global configuration mode:
voice-port 1/0/0 connection trunk 55Router0 exit dial-peer voice 100 pots destination pattern 5550150 exit dial-peer voice 200 vofr session protocol frf11-trunk called-number 5550150 destination pattern 55Router0Related Commands
Command
Description
codec (dial peer)
Specifies the voice coder rate of speech for a VoFR dial peer.
connection
Specifies a connection mode for a voice port.
destination pattern
Specifies either the prefix, the full E.164 telephone number, or an ISDN directory number (depending on the dial plan) to be used for a dial peer.
dtmf relay (VoFR)
Enables the generation of FRF.11 Annex A frames for a dial peer.
fax rate
Establishes the rate at which a fax is sent to the specified dial peer.
preference
Indicates the preferred order of a dial peer within a rotary hunt group.
session protocol
Establishes a session protocol for calls between the local and remote routers via the packet network.
session target
Specifies a network-specific address for a specified dial peer or destination gatekeeper.
signal type
Sets the signaling type to be used when connecting to a dial peer.
vad (dial peer)
Enables VAD for the calls using a particular dial peer.
