-
Cisco IOS Voice Command Reference
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Commands: A
-
Commands: B
-
Commands:cac master through call application stats
-
Commands: call application voice through call-denial
-
Commands: call fallback through called-number (dial-peer)
-
Commands: caller-id (dial peer) through ccm-manager switchover-to-backup
-
Commands: ccs connect (controller) through clear vsp statistics
-
Commands: clid through cptone
-
Commands: default (MGCP profile) through direct-inward-dial
-
Commands: disable-early-media 180 through dualtone
-
Commands: E
-
Commands: F
-
Commands: G
-
Commands: H
-
Commands: icpif through irq global-request
-
Commands: isdn bind-l3 through ixi transport http
-
Commands: K
-
Commands: L
-
Commands: map q850-cause through mgcp package-capability
-
Commands: mgcp persistent through mmoip aaa send-id secondary
-
Commands: mode (ATM/T1/E1 controller) through mwi-server
-
Commands: N
-
Commands: O
-
Commands: package through pattern
-
Commands: permit hostname through proxy h323
-
Commands: Q
-
Commands: R
-
Commands: sccp through service-type call-check
-
Commands: session through sgcp tse payload
-
Commands: show aal2 profile through show call filter match-list
-
Commands: show call history fax through show debug condition
-
Commands: show dial-peer video through show gatekeeper zone status
-
Commands: show gateway through show modem relay statistics
-
Commands: show mrcp client session active through show sgcp statistics
-
Commands: show sip service through show trunk hdlc
-
Commands: show vdev through show voice statistics memory-usage
-
Commands: show voice translation-profile through shutdown (voice-port)
-
Commands: signal through srv version
-
Commands: ss7 mtp2-variant through switchover method
-
Commands: target carrier-id through threshold noise
-
Commands: timeout (auto-config application) through timing clear-wait
-
Commands:timing delay-duration through type (voice)
-
Commands: U
-
Commands: vad (dial peer) through voice class dualtone-detect-params
-
Commands: voice class h323 through vxml tree memory
-
Commands: W
-
Commands: Z
-
Feedback
Table Of Contents
h225 h245-address on-connect (H.323 voice-class)
h225 h245-address on-connect (H.323 voice-service)
h225 timeout tcp call-idle (H.323 voice-service)
h323-gateway voip bind srcaddr
h323zone-id (voice source group)
history session event-log save-exception-only
http client connection idle timeout
http client connection persistent
http client connection timeout
http client secure-ciphersuite
Cisco IOS Voice Commands:
H
This chapter contains commands to configure and maintain Cisco IOS voice applications. The commands are presented in alphabetical order. Some commands required for configuring voice may be found in other Cisco IOS command referenefces. Use the command reference master index or search online to find these commands.
For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice Configuration Guide.
h225 alt-ep hunt
To configure alternate endpoint hunts for failed calls in an IP-to-IP gateway (IPIPGW), use the h225 alt-ep hunt command in H.323 voice-service configuration mode. To control the alternate endpoint hunts based on call disconnect cause codes, use the no form of this command.
h225 alt-ep hunt
no h225 alt-ep hunt [ all | cause-code ]
Syntax Description
all
Perform alternate hunt for all disconnect cause codes.
cause-code
A code returned from the destination router to indicate why an attempted end-to-end call was unsuccessful. Table 26 in the "Usage Guidelines" section describes the possible values.
Command Default
Alternate endpoint hunt is enabled for all cause codes
Command Modes
H.323 voice-service configuration
Command History
Usage Guidelines
The default behavior of the gateway is to retry all alternate endpoints received from the gatekeeper regardless of the ReasonComplete reason. Only the no alt-ep hunt command will be visible in the configuration. A code returned from the destination router to indicate why an attempted end-to-end call was unsuccessful. If the specified disconnect cause code is returned from the last destination endpoint, dial peer hunting is enabled or disabled. You can enter the keyword, decimal value, or hexadecimal value.
The disconnect cause codes are described in Table 26. The decimal and hexadecimal value of the disconnect cause code follows the description of each possible keyword.
Examples
The following example shows the alternate endpoint hunts with the user-busy disconnect cause code disabled:
Router(conf-serv-h323)# no h225 alt-ep hunt user-busyRelated Commands
h225 h245-address on-connect (H.323 voice-class)
To enable for an individual dial peer a delay in the exchange of H.225 messages for the relay of H.245 transport addresses until call connections are made, use the h225 h245-address on-connect command in H.323 voice-class configuration mode. To disable the delay of H.225 messages, use the no form of this command.
h225 h245-address on-connect
no h225 h245-address on-connect
Syntax Description
This command has no arguments or keywords.
Command Default
H.225 messages that contain H.245 addresses are delayed until calls are connected.
Command Modes
H.323 voice-class configuration
Command History
Usage Guidelines
The functionality specified by this command allows Cisco CallManager Express 3.1 (Cisco CME 3.1) or later systems to interwork with Cisco CallManager in the same network. This command should always be enabled.
When simple A-to-B calls are made from a Cisco CallManager phone to a Cisco CME IP phone, the Cisco CallManager must play in-band ringback tone locally to the originating phone. The Cisco CallManager stops the tone generation if it receives the call's H.245 address before the call is answered. The h225 h245-address on-connect command ensures that the H.245 address is not sent before the call is answered (connected). This command is enabled by default unless the no form of this command has been used. In addition, the telephony-service ccm-compatible command must also be enabled to detect calls from Cisco CallManager, which is the default.
This command can also be used in an H.323 voice-service definition to globally enable or disable this behavior.
Examples
The following example creates a voice class with the tag of 4, which delays the exchange of H.225 messages for H.245 transport address relay until a call connection is made. Voice class 4 is then applied to dial peer 36.
Router(config)# voice class h323 4Router(config-voice-class)# h225 h245-address on-connect
Router(config)# dial-peer voice 36 voip
Router(config-dial-peer)# destination-pattern 555....Router(config-dial-peer)# session target ipv4:10.5.6.7Router(config-dial-peer)# voice-class h323 4Related Commands
h225 h245-address on-connect (H.323 voice-service)
To globally delay the exchange of H.225 messages for the relay of H.245 transport addresses until call connections are made, use the h225 h245-address on-connect command in H.323 voice-service configuration mode. To globally disable the delay, use the no form of this command.
h225 h245-address on-connect
no h225 h245-address on-connect
Syntax Description
This command has no arguments or keywords.
Command Default
H.225 messages that contain H.245 addresses are delayed until calls are connected.
Command Modes
H.323 voice-service configuration
Command History
Usage Guidelines
The functionality specified by this command allows Cisco CallManager Express 3.1 (Cisco CME 3.1) or later systems to interwork with Cisco CallManager in the same network. This command should always be enabled.
When simple A-to-B calls are made from a Cisco CallManager phone to a Cisco CME IP phone, the Cisco CallManager must play in-band ringback tone locally to the originating phone. The Cisco CallManager stops the tone generation if it receives the call's H.245 address before the call is answered. The h225 h245-address on-connect command ensures that the H.245 address is not sent before the call is answered (connected). This behavior is the default when a Cisco CME system detects an incoming call from a Cisco CallManager unless the no form of this command has been used. In addition, the telephony-service ccm-compatible command must also be enabled to detect calls from Cisco CallManager, which is the default.
This command can also be used in an H.323 voice-class definition to enable or disable this behavior for individual dial peers.
Examples
The following example globally delays the exchange of H.225 messages for H.245 transport address relay until a call connection is made.
Router(config)# voice service voipRouter(conf-voi-serv)# h323Router(conf-serv-h323)# h225 h245-address on-connectRelated Commands
h225 id-passthru
To enable video call connections to pass through between endpoints regardless of software version, use the h225 id-passthru command in H.323 voice-service configuration mode. To return to the default, use the no form of this command.
h225 id-passthru
no h225 id-passthru
Syntax Description
This command has no arguments or keywords.
Command Default
Video calls are completed on endpoints using the same software version.
Command Modes
H.323 voice-service configuration
Command History
Usage Guidelines
Video calls complete when the endpoints are operating the same version of software. Use this command to allow connections between video endpoints that are using different software versions.
Examples
The following example allows video calls to connect when the polycom endpoints are using different software versions:
Router(config-serv-h323)# h225 id-passthruRelated Commands
h225 signal overlap
To activate overlap signaling to the destination gateway, use the h225 signal overlap command in H.225 voice-service configuration mode. To stop sending overlap signaling messages, use the no form of this command.
h225 signal overlap
no h225 signal overlap
Syntax Description
This command has no arguments or keywords.
Command Default
H.225 signaling overlap is disabled.
Command Modes
H.323 voice-service configuration
Command History
12.2(15)T11
This command was introduced.
12.3
This command was integrated into Cisco IOS Release 12.3.
Usage Guidelines
The terminating gateway is responsible for collecting all the called number digits. This is implemented by the dial peers matching destination patterns. When H.225 signal overlap is configured on the originating gateway, it sends the SETUP to the terminating gateway once a dial-peer match is found. The originating gateway sends all further digits received from user to the terminating gateway using INFO messages until it receives a sending complete from the user. The terminating gateway receives the digits in SETUP and subsequent INFO messages and does a dial-peer match. If a match is found, it sends a SETUP with the collected digits to the PSTN. All subsequent digits are sent to the PSTN using INFO messages at which time the call is complete.
Examples
The following example enables overlap signalling on the H.225 gateway:
Router(config)# voice service voipRouter(conf-voi-serv)# h323Router(conf-serv-h323)# h225 signal overlapRelated Commands
h323
Enables H.323 voice service configuration commands.
voice service
Enters voice-service configuration mode and specifies the voice encapsulation type.
h225 start-h245
To hold the H.245 connection procedures until after the H.225 connections are made, use the h225 start-h245 command in H.323 voice-class configuration mode. To disable the connection sequence, use the no form of this command.
h225 start-h245 on-connect
no h225 start-h245 on-connect
Syntax Description
Command Default
By default, h225 start-h245 on-connect is disabled. In case of IP-to-IP gateway (IPIPGW), the outbound gateway echoes the same h245 address and port number sent by the remote endpoint.
Command Modes
H.323 voice-class configuration (config-voice-class)
H.323 voice-service (conf-serv-h323)Command History
Usage Guidelines
The h225 start-245 on-connect command ensures that the H.245 address is not sent before the call is answered (connected).
Configure this command in H.323 voice-service configuration mode to globally enable or disable the connection behavior.
Examples
The following example shows a voice class with the tag of 4 being created, which delays the exchange of H.225 messages for H.245 transport address relay until a call connection is made.
Router(conf-serv-h323)#h225 start-h245 on-connectRelated Commands
h225 timeout call-proceeding
To set the H.225 call-proceeding (T310) disconnect timer, use the h225 timeout call-proceeding command in either voice-service or dial peer configuration mode. To revert to the default, use the no form of this command.
h225 timeout call-proceeding duration
no h225 timeout call-proceeding
Syntax Description
Command Default
60 seconds
Command Modes
For all dial peers: Voice-service configuration
For a single dial peer: Dial peer configurationCommand History
Usage Guidelines
Use this command to set a maximum duration for the time between call setup and call connect.
You can use this command in either of two configuration modes:
•
For all peers: Use voice-service configuration mode by entering the voice service voip command
•
Examples
The following example sets the disconnect timer for all dial peers:
Router(config)# voice service voipRouter(config-voi-serv)# h225 timeout call-processing 5The following example sets the disconnect timer for a single dial peer:
Router(config)# voice class h323 1Router(config-class)# h225 timeout call-processing 5Related Commands
h225 timeout keepalive
To disconnect H.323 calls when a TCP keepalive timeout occurs, use the h225 timeout keepalive command in H.323 voice-service configuration mode. To enable H.323 calls to remain active and ignore the TCP keepalive timeout, use the no form of this command.
h225 timeout keepalive
no h225 timeout keepalive
Syntax Description
This command has no arguments or keywords.
Command Default
TCP keepalives are enabled.
Command Modes
H.323 voice-service configuration
Command History
12.2(15)T12
This command was introduced.
12.3
This command was integrated into Cisco IOS Release 12.3.
12.3(4)T5
This command was integrated into Cisco IOS Release 12.3(4)T5.
Usage Guidelines
When using the default configuration of the h225 timeout keepalive command, if a TCP timeout occurs on the H.225 channel, all active calls are disconnected and corresponding H.225 TCP sockets are closed.
When the no h225 timeout keepalive command is configured and a timeout occurs, the H.225 TCP socket is closed for all calls; Active TDM-IP calls will be preserved, but IP to IP calls are disconnected. In both cases the H.225 TCP socket is closed.
Note
Examples
The following example enables TCP keepalives on H.225 VoIP call control sessions:
Router(config)# voice service voipRouter(conf-voi-serv)# h323Router(conf-serv-h323)# h225 timeout keepaliveRelated Commands
h323
Enables H.323 voice service configuration commands.
voice service
Enters voice-service configuration mode and specifies the voice encapsulation type.
h225 timeout setup
To configure the timeout value for the response of the outgoing SETUP message, use the h225 timeout setup command in voice class configuration mode. To remove the timeout value, use the no form of this command.
h225 timeout setup seconds
no h225 timeout setup
Syntax Description
Command Default
15 seconds
Command Modes
Voice class configuration
Command History
Examples
The following example configures a timeout setup value of 10 seconds:
Router(config-class)# h225 timeout setup 10Related Commands
h225 timeout tcp call-idle
Sets a timer for an idle call connection.
h225 timeout tcp establish
Configures the H.225 TCP timeout.
h225 timeout t302
To set the t302 timer when using overlap signaling, use the h225 timeout t302 command in H.225 voice-service configuration mode. To return to the default overlap signaling setting, use the no form of this command
h225 timeout t302 seconds
no h225 timeout t302 seconds
Syntax Description
Command Default
The t302 timer is disabled.
Command Modes
H.323 voice-service configuration
Command History
Usage Guidelines
Use this command to establish the maximum amount of time allowed to complete the dial-peer match when H.225 signal overlap is configured on the originating gateway.
Examples
The following example allows 15 seconds for the t302 timer to complete the dial-peer match before timing out:
Router(config)# voice service voipRouter(conf-voi-serv)# h323Router(conf-serv-h323)# h225 timeout t302 15Related Commands
h225 timeout t304
To set the t304 timer when using overlap signaling, use the h225 timeout t304 command in H.323 voice-service configuration mode. To return to the default overlap signaling setting, use the no form of this command.
h225 timeout t304 seconds
no h225 timeout t304 seconds
Syntax Description
Command Default
The timer is enabled and set to 10 seconds.
Command Modes
H.323 voice-service configuration (conf-serv-h323)
Command History
Usage Guidelines
Use the h225 timeout t304 command to configure the maximum interdigit delay on the originating gateway when H.225 overlap signaling is configured. Configure this command for the H.323 call leg on the originating gateway. If this timer expires, the call is disconnected with a cause code 28 (invalid number).
Examples
The following example allows 12 seconds for the t304 timer to complete the dial-peer match before timing out:
Router(config)# voice service voipRouter(conf-voi-serv)# h323Router(conf-serv-h323)# h225 timeout t304 12Related Commands
h225 timeout tcp call-idle (H.323 voice-service)
To set a timer for an idle call connection, use the h225 timeout tcp call-idle command in voice service h323 configuration mode. To reset to the default, use the no form of this command.
h225 timeout tcp call-idle {value value | never}
no h225 timeout tcp call-idle
Syntax Description
Command Default
10 minutes
Command Modes
H.323 voice-service configuration
Command History
Usage Guidelines
This command specifies the time to maintain an established H.225 TCP connection when there are no calls on that connection. If the timer expires, the connection is closed. If the timer is running and any new call is made on that connection, the timer stops. When all the calls are cleared on that connection, the timer starts again.
Examples
The following example sets the timer for an idle call connection to 10 minutes:
Router(conf-voi-serv)# h323Router(conf-serv-h323)# h225 timeout tcp call-idle value 10Related Commands
h225 timeout tcp establish
To set the H.225 TCP timeout value for Voice over IP (VoIP) dial peers, use the h225 timeout tcp establish command in voice class configuration mode. To reset to the default, use the no form of this command.
h225 timeout tcp establish seconds
no h225 timeout tcp establish
Syntax Description
seconds
Number of seconds for the timeout. Range is 0 to 30. The default is 15. If you specify 0, the H.225 TCP timer is disabled.
Command Default
15 seconds
Command Modes
Voice class configuration
Command History
Examples
The following example sets a timeout of 10 seconds, which is associated with the H.323 voice class labeled 1:
voice class h323 1h225 timeout tcp establish 10Related Commands
h245 passthru
To allow H.245 calls to pass through to the Cisco Unified CallManager when the IP-to-IP gateway sends an incorrect intercluster trunk (ICT) version, use the h245 passthru command in voice service configuration mode. To disable this command use, the no form of this command.
h245 passthru {all | tcsnonstd-passthru}
no h245 passthru {all | tcsnonstd-passthru}
Syntax Description
all
Passes non-standard codec through the IP-to-IP gateway.
tcsnonstd-passthru
Passes terminal capabilities set (TCS) non-standard parameter pass through (CCM data only).
Command Default
This command is disabled.
Command Modes
Voice service configuration
Command History
Usage Guidelines
When resuming a call that was placed on hold fails on a Cisco Unified CallManager, generally the call fails on the second Cisco Unified CallManager because the IP-to-IP gateway (IPIPGW) sends an incorrect intercluster trunk (ICT) version for the first Cisco Unified CallManager to the second Cisco Unified CallManager, and because the IPIPGW drops the non-standard fields in the callproc, alert, and connect messages from the second Cisco Unified CallManager to the first Cisco Unified CallManager. To resolve this behavior configure the h245 passthru command
Note
Examples
The following example show how you configure h.245 to pass through to the Cisco Unified CallManager, regardless of the intercluster trunk (ICT) version:
Router(conf-serv-h323)#h245 passthru tcsnonstd-passthruRelated Commands
allow-connections
Allows connections between specific types of endpoints in a VoIP network.
h245 timeout olc
To set the timeout value for the OpenLogicalChannel (OLC) message, use the h245 timeout olc command in H.323 voice-service configuration mode. To disable the timeout value for the OLC message, use the no form of this command.
h245 timeout olc timeout value
no h245 timeout olc timeout value
Syntax Description
Command Default
Timeout value for the OLC message is enabled and set to 4 seconds.
Command Modes
H.323 voice-service configuration
Command History
Usage Guidelines
After the originating gateway sends an OLC message during the H.245 procedure, it waits for 4 seconds for the terminating gateway to respond with an OLC acknowledgment. This behavior is enabled by default, and the timeout value of the OLC message is set to 4 seconds.
However, sometimes when a slow link, such as a satellite link, is involved in sending messages, a delay can occur. In that case, 4 seconds are not enough to receive OLC messages, and the call fails even when the terminating gateway had responded with OLC acknowledgment. To avoid the random dropping of VoIP calls, use the h245 timeout olc command to change the length of time that the originating gateway waits for OLC acknowledgment from the terminating gateway.
Examples
The following example sets the timeout value for the OLC message to 20 seconds. It also shows that you can change the setting to 15 seconds:
h245 timeout olc 20h245 timeout olc 15The following example sets the timeout value back to the default setting of 4 seconds:
no h245 timeout olc 15The output of the show run command does not show the default setting; however, it does include the command if the timeout value is modified:
voice service voiph323h245 timeout olc 20Related Commands
h323
To enable the H.323 voice service configuration commands, use the h323 command in voice service configuration mode.
h323
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Voice service configuration
Command History
Examples
The following example enters H.323 voice service configuration mode:
Router(conf-voi-serv)# h323Related Commands
h323 asr
To enable application-specific routing (ASR) and specify the maximum bandwidth for a proxy, use the h323 asr command in interface configuration mode. To remove a bandwidth setting but keep ASR enabled, use no form of this command.
h323 asr [bandwidth max-bandwidth]
no h323 asr [bandwidth max-bandwidth]
Syntax Description
Command Default
ASR is disabled.
Command Modes
Interface configuration
Command History
11.3(2)NA
This command was introduced on the Cisco 2500 series and Cisco 3600 series.
12.0(3)T
This command was integrated into Cisco IOS Release 12.0(3)T.
Usage Guidelines
This command is independent of the h323 interface command.
Note
Examples
The following example enables ASR and specifies a maximum bandwidth of 10,000 kbps:
h323 asr bandwidth 10000h323 call start
To force the H.323 Version 2 gateway to use Fast Connect or Slow Connect procedures for all H.323 calls, use the h323 call start command in voice-service configuration mode. To reset to the default, use the no form of this command.
h323 call start {fast | slow}
no h323 call start
Syntax Description
fast
Gateway uses H.323 Version 2 (Fast Connect) procedures.
slow
Gateway uses H.323 Version 1 (Slow Connect) procedures.
Command Default
fast
Command Modes
Voice-service configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.1(3)XI and later releases, H.323 Voice over IP (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.1 T, the h323 call start command forces the originating gateway to initiate calls using Slow Connect.
This h323 call start command is configured as part of the global voice-service configuration for VoIP services. It does not take effect unless the call start system voice-class configuration command is configured in the VoIP dial peer.
Examples
The following example selects Slow Connect procedures for the gateway:
voice service voiph323 call start slowRelated Commands
h323 gatekeeper
To specify the gatekeeper associated with a proxy and to control how the gatekeeper is discovered, use the h323 gatekeeper command in interface configuration mode. To disassociate the gatekeeper, use the no form of this command.
h323 gatekeeper [id gatekeeper-id] {ipaddr ipaddr [port] | multicast}
no h323 gatekeeper [id gatekeeper-id] {ipaddr ipaddr [port] | multicast}
Syntax Description
Command Default
No gatekeeper is configured for the proxy
Command Modes
Interface configuration
Command History
11.3(2)NA
This command was introduced on Cisco 2500 series and Cisco 3600 series.
Usage Guidelines
You must enter the h323 interface and h323 h323-id commands before using this command. The h323 gatekeeper command must be specified on your Cisco IOS platform or the proxy does not go online. The proxy uses the interface address as its RAS signaling address.
Examples
The following example sets up a unicast discovery to a gatekeeper whose name is unknown:
h323 gatekeeper ipaddr 192.168.5.2The following example sets up a multicast discovery for a gatekeeper of a particular name:
h323 gatekeeper id gk.zone5.com multicastRelated Commands
h323 h323-id
Registers an H.323 proxy alias with a gatekeeper.
h323 interface
Specifies the interface from which the proxy takes its IP address.
h323 h323-id
To register an H.323 proxy alias with a gatekeeper, use the h323 h323-id command in interface configuration mode. To remove an H.323 proxy alias, use the no form of this command.
h323 h323-id h323-id
no h323 h323-id h323-id
Syntax Description
h323-id
Name of the proxy. It is recommended that this name be a fully qualified e-mail ID, with the domain name being the same as that of its gatekeeper.
Command Default
No H.323 proxy alias is registered
Command Modes
Interface configuration
Command History
11.3(2)NA
This command was introduced on Cisco 2500 and Cisco 3600 series routers.
12.0(3)T
This command was integrated into Cisco IOS Release 12.0(3)T.
Usage Guidelines
Each entry registers a specified H.323 ID proxy alias to a gatekeeper. Typically, these aliases are either simple text strings or legitimate e-mail IDs.
Note
Examples
The following example registers an H.323 proxy alias called proxy1@zone5.com with a gatekeeper:
h323 h323-id proxy1@zone5.comRelated Commands
h323 interface
To select an interface whose IP address is used by the proxy to register with the gatekeeper, use the h323 interface command in interface configuration mode. To reset to the default port, use the no version of the command and then the h323 interface command.
h323 interface [port-number]
no h323 interface [port-number]
Syntax Description
Command Default
Default port number is image dependent as described in the Syntax Description.
Command Modes
Interface configuration
Command History
Usage Guidelines
At proxy startup, Cisco IOS software checks for the presence of the VoIP gateway subsystem. If the subsystem is found to be present, the proxy code opens and listens for call setup requests on the new port. The proxy then registers this port with the gatekeeper.
Examples
The following example configures Ethernet interface 0 for incoming call-setup requests:
interface ethernet0h323 interfaceRelated Commands
h323 qos
To enable quality of service (QoS) on the proxy, use the h323 qos command in interface configuration mode. To disable QoS, use the no form of this command.
h323 qos {ip-precedence value | rsvp {controlled-load | guaranteed-qos}}
no h323 qos {ip-precedence value | rsvp {controlled-load | guaranteed-qos}}
Syntax Description
ip-precedence value
RTP streams set their IP precedence bits to the specified value.
rsvp controlled-load
Controlled load class of service.
rsvp guaranteed-qos
Guaranteed QoS class of service.
Command Default
No QoS is configured
Command Modes
Interface configuration
Command History
11.3(2)NA
This command was introduced on Cisco 2500 and Cisco 3600 series routers.
Usage Guidelines
You must execute the h323 interface command before using this command.
Both IP precedence and RSVP QoS can be configured by invoking this command twice with the two different QoS forms.
Examples
The following example enables QoS on the proxy:
interface Ethernet0ip address 172.21.127.38 255.255.255.192no ip redirectsip rsvp bandwidth 7000 7000ip route-cache same-interfacefair-queue 64 256 1000h323 interfaceh323 qos rsvp controlled-loadh323 h323-id px1@zone1.comh323 gatekeeper ipaddr 172.21.127.39Related Commands
h323 interface
Specifies the interface from which the proxy takes its IP address.
h323 t120
To enable the T.120 capabilities on your router and to specify bypass or proxy mode, use the h323 t120 command in interface configuration mode.
h323 t120 {bypass | proxy}
Syntax Description
Command Default
Bypass mode
Command Modes
Interface configuration
Command History
12.1(5)T
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3600 series, Cisco 7200, and Cisco MC3810.
Usage Guidelines
The no form of this command has no function—the only possible commands are h323 t120 bypass and h323 t120 proxy.
Examples
The following example enables T.120 capabilities:
proxy h323interface ethernet0h323 t120 proxyRelated Commands
h323-annexg
To enable the border element (BE) on the gatekeeper and to enter BE configuration mode, use the h323-annexg command in gatekeeper configuration mode. To disable the BE, use the no form of this command.
h323-annexg border-element-id cost cost priority priority
no h323-annexg
Syntax Description
Command Default
Cost: 50
Priority: 50Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
The Annex G border element must be configured using the call-router command before the gatekeeper can be associated with the Annex G border element. The h323-annexg command associates the gatekeeper with a previously configured Annex G border element and indicates that the gatekeeper should interact with the BE in address resolution.
Examples
The following example enables Annex G configuration for a BE named "be20":
Router(config-gk)# h323-annexg be20 cost 10 priority 40Router(config-gk-annexg)#Related Commands
call-router
Enables the Annex G border element configuration commands.
prefix
Restricts the prefixes for which the gatekeeper should query the Annex G BE.
h323-gateway voip bind srcaddr
To designate a source IP address for the voice gateway, use the h323-gateway voip bind srcaddr command in interface configuration mode. To remove the source IP address, use the no form of the command.
h323-gateway voip bind srcaddr ip-address
no h323-gateway voip bind srcaddr
Syntax Description
Command Default
No default behaviors or values
Command Modes
Interface configuration
Command History
12.1(2)T
This command was introduced on the following platforms: Cisco 1700, Cisco 2500, Cisco 2600 series, Cisco 3600 series, Cisco 7200, Cisco S5300, and Cisco uBR924.
Usage Guidelines
You do not have to issue this command on the interface that you defined as the voice gateway interface (although it may be more convenient to do so). Use this command the interface that contains the IP address to which you want to bind.
Examples
The following example assigns a source IP address of 10.1.1.1:
h323-gateway voip bind srcaddr 10.1.1.1h323-gateway voip h323-id
To configure the H.323 name of the gateway that identifies this gateway to its associated gatekeeper, use the h323-gateway voip h323-id command in interface configuration mode. To disable this defined gateway name, use the no form of this command.
h323-gateway voip h323-id interface-id
no h323-gateway voip h323-id interface-id
Syntax Description
Command Default
No gateway identification is defined
Command Modes
Interface configuration
Command History
Examples
The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the gateway ID is GW13@cisco.com.
interface Ethernet0/0ip address 172.16.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip id
To define the name and location of the gatekeeper for a specific gateway, use the h323-gateway voip id command in interface configuration mode. To disable this gatekeeper identification, use the no form of this command.
h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}
[priority number]no h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}
[priority number]Syntax Description
Command Default
No gatekeeper identification is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command tells the H.323 gateway associated with this interface which H.323 gatekeeper to talk to and where to locate it. The gatekeeper ID configured here must exactly match the gatekeeper ID in the gatekeeper configuration.
You can configure one or two alternate gatekeepers.
The IP address of the gatekeeper does not have to be explicit; you can also use the multicast option. Multicasting saves bandwidth by forcing the network to replicate packets only when necessary. The multicast option, shown below, notifies every gatekeeper in the LAN using a universal address, 224.0.1.41.
h323-gateway voip id GK1 multicast h323-gateway voip id GK2 ipaddr 172.18.193.65 1719Examples
The following example configures Ethernet interface 0.0 as the gateway interface and defines a specific gatekeeper for it. In this example, the gatekeeper ID is GK15.cisco.com, and its IP address is 172.16.53.15 (using port 1719).
interface Ethernet0/0ip address 172.16.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip interface
To configure an interface as an H.323 gateway interface, use the h323-gateway voip interface command in interface configuration mode. To disable H.323 gateway functionality for an interface, use the no form of this command.
h323-gateway voip interface
no h323-gateway voip interface
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
Interface configuration
Command History
Examples
The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the h323-gateway voip interface command configures this interface as an H.323 interface.
interface Ethernet0/0ip address 172.16.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip tech-prefix
To define the technology prefix that the gateway registers with the gatekeeper, use the h323-gateway voip tech-prefix command in interface configuration mode. To disable this defined technology prefix, use the no form of this command.
h323-gateway voip tech-prefix prefix
no h323-gateway voip tech-prefix prefix
Syntax Description
Command Default
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command defines a technology prefix that the gateway then registers with the gatekeeper. Technology prefixes can be used as a discriminator so that the gateway can tell the gatekeeper that a certain technology is associated with a particular call (for example, 15# could mean a fax transmission), or it can be used like an area code for more generic routing. No standard currently defines what the numbers in a technology prefix mean. By convention, technology prefixes are designated by a pound sign (#) as the last character.
Note
Examples
The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the technology prefix is defined as 13#.
interface Ethernet0/0ip address 172.16.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323zone-id (voice source group)
To specify the zone identification for an incoming H.323 call, use the h323zone-id command in voice source-group configuration mode. To delete the zone ID, use the no form of this command.
h323zone-id name
no h323zone-id name
Syntax Description
Command Default
No default behavior or values
Command Modes
Voice source-group configuration
Command History
Usage Guidelines
Use this command to specify the zone to use for incoming H.323 calls in the voice source-group definition. The zone ID name matches the source zone ID of an incoming H.323 call.
Note
Examples
The following example associates zone ID "5400-gw1" with incoming calls for source IP group "northcal":
Router(config)# voice source-group northcalRouter(cfg-source-grp)# h323zone-id 5400-gw1Related Commands
h450 h450-3 timeout
To specify timeout values for call forwarding using the ITU-T H.450.3 standard, use the h450 h450-3 timeout command in H.323 voice service configuration mode. To return to the default, use the no form of this command.
h450 h450-3 timeout T1 milliseconds
no h450 h450-3 timeout T1
Syntax Description
T1
Timeout value to wait for a rerouting response.
milliseconds
Number of milliseconds. Range is from 500 to 60000. Default is 5000.
Command Default
T1 timer is 5000 milliseconds.
Command Modes
H323 voice service configuration
Command History
12.2(11)YT
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
Use this command with Cisco IOS Telephony Service (ITS) V2.1 or a later version.
This command is primarily used when the default setting for this timer does not match your network delay parameters. Refer to the ITU-T H.450.3 specification for more information on these timers.
Examples
The following example defines a T1 timeout of 3000 milliseconds:
Router(config)# voice service voipRouter(conf-voi-serv)# h323Router(conf-serv-h323)# h450 h450-3 timeout T1 3000Related Commands
h323
Enables H.323 voice service configuration commands.
voice service
Enters voice-service configuration mode.
header-passing
To enable the passing of headers to and from Session Initiation Protocol (SIP) INVITE, SUBSCRIBE, and NOTIFY messages, use the header-passing command in voice service voip sip configuration mode. To disable header passing, use the no form of this command.
header-passing
no header-passing
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
voice service voip sip configuration
Command History
Usage Guidelines
•
•
•
Examples
The following example shows header-passing enabled:
Router(conf-serv-sip)# header-passingRelated Commands
history session event-log save-exception-only
To save in history only the event logs for application sessions that have at least one error, use the history session event-log save-exception-only command in application configuration monitor mode. To reset to the default, use the no form of this command.
history session event-log save-exception-only
no history session event-log save-exception-only
Syntax Description
This command has no arguments or keywords.
Command Default
All event logs for sessions are saved to history.
Command Modes
Application configuration monitor
Command History
12.3(14)T
This command was introduced to replace the call application history session event-log save-exception-only command.
Usage Guidelines
Application event logs move from active to history after an instance terminates. If you use this command, the voice gateway saves event logs only for instances that had one or more errors. Event logs for normal instances that do not contain any errors are not saved to history.
Note
Examples
The following example saves an event log in history only if the instance had an error:
applicationmonitorhistory session event-log save-exception-onlyRelated Commands
history session max-records
To set the maximum number of application instance records saved in history, use the history session max-records command in application configuration monitor mode. To reset to the default, use the no form of this command.
history session max-records number
no history session max-records
Syntax Description
Command Default
360
Command Modes
Application configuration monitor
Command History
12.3(14)T
This command was introduced to replace the call application history session max-records command.
Usage Guidelines
This command affects the number of records that display when you use the show call application history session-level command.
Examples
The following example sets the maximum record limit to 500:
applicationmonitorhistory session max-records 500Related Commands
history session retain-timer
To set the maximum number of minutes for which application instance records are saved in history, use the history session retain-timer command in application configuration monitor mode. To reset to the default, use the no form of this command.
history session retain-timer minutes
no history session retain-timer
Syntax Description
minutes
Maximum time, in minutes, for which history records are saved. Range is 0 to 4294,967,295. Default is 15.
Command Default
15
Command Modes
Application configuration mode
Command History
12.3(14)T
This command was introduced to replace the call application history session retain-timer command.
Usage Guidelines
This command affects the number of records that display when you use the show call application history session-level command.
To enable event logging for voice applications, use the event-log command.
Examples
The following example sets the maximum time to save history records to 1 hour:
applicationmonitorhistory session retain-timer 60Related Commands
hopcount
To specify the maximum number of border element (BE) hops through which an address resolution request can be forwarded, use the hopcount command in Annex G configuration mode. To restore the default, use the no form of this command.
hopcount hopcount-value
no hopcount
Syntax Description
hopcount-value
Maximum number of BE hops through which an address resolution request can be forwarded. Range is from 1 to 255. The default is 7.
Command Default
7 hops
Command Modes
Annex G configuration
Command History
Examples
The following example sets address-resolution forwarding to a maximum of 10 hops:
Router(config)# call-router h323-annexg be20Router(config-annexg)# hopcount 10Related Commands
call-router
Enables the Annex G border element configuration commands.
show call-router status
Displays the Annex G BE status.
host (SIP URI)
To match a call based on the host field in a Session Initiation Protocol (SIP) uniform resource identifier (URI), use the host command in voice URI class configuration mode. To remove the host match, use the no form of this command.
host hostname-pattern
no host
Syntax Description
hostname-pattern
Cisco IOS regular expression pattern to match against the host field in a SIP URI. Can be up to 32 characters.
Command Default
No default behavior or values
Command Modes
Voice URI class configuration
Command History
Usage Guidelines
•
•
Examples
The following example defines a voice class that matches on the host field in a SIP URI:
voice class uri r100 siphost server1Related Commands
http client cache memory
To set the memory file and pool limits for the HTTP client cache, use the http client cache memory command in global configuration mode. To reset to the default, use the no form of this command.
http client cache memory {file file-size | pool pool-size}
no http client cache memory {file | pool}
Syntax Description
Command Default
Memory file size: 50 KB
Memory pool size: 10 MBCommand Modes
Global configuration
Command History
Usage Guidelines
A larger cache size may permit caching of frequently used files, decreasing the fetching time between the client and server and increasing performance. Allocation of memory to increase file size or pool size does not reduce the amount of memory available. Cache memory is used only when needed, and afterward returns to being memory shared with other resources.
The amount of memory required for an expected level of performance depends on a number of factors, including the type of voice gateway (for example, Cisco 2600 series or Cisco AS5400).
The recommended maximum file size is 10 MB; the recommended maximum pool size is 100 MB.
The gateway might accept invalid characters such as "#" or "!" when you input the value for this command. The gateway ignores any invalid characters.
Note
Examples
The following example sets the HTTP client cache memory pool to 50,000 KB:
http client cache memory pool 50000The following example sets the HTTP client cache memory file to 8000 KB:
http client cache memory file 8000Related Commands
http client cache query
To enable caching of query data returned from the HTTP server, use the http client cache query command in global configuration mode. To disable caching of query data, use the no form of this command.
http client cache query
no http client cache query
Syntax Description
This command has no arguments or keywords.
Command Default
Query data is not cached.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the show http client cache command to display cached query data. To protect caller privacy, values of the URL attributes are masked out with asterisks (*) in the show http client cache command output. If you use this command to enable caching of query data, use the http client cache memory command to increase the size of the HTTP client cache memory pool to accommodate the cached query data.
Examples
The following example enables caching of query data returned from the HTTP server:
Router# http client cache queryRelated Commands
http client cache refresh
To set the time limit for how long a cached entry is considered current by the HTTP client, use the http client cache refresh command in global configuration mode. To reset to the default, use the no form of this command.
http client cache refresh seconds
no http client cache refresh
Syntax Description
seconds
Lifetime of a cached HTTP entry, in seconds. Range is from 1 to 864000. The default is 86400 (24 hours).
Command Default
86,400 seconds (24 hours)
Command Modes
Global configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
This command must be used to set the refresh time only if the HTTP server does not provide the necessary information in the HTTP header to calculate this value.
The gateway might accept invalid characters such as "#" or "!" when you input the value for this command. The gateway ignores any invalid characters.
When a request is made to an expired cached entry (that is, an entry that is the same age as or older than the refresh time), the HTTP client sends the server a conditional request for an update.
An expired entry is not automatically updated unless a request from the user hits the same cached entry. Expired entries are not cleaned up until 70 percent or more of the cache pool memory is consumed; then all expired entries that lack a user reference are deleted from the cache table.
Note
Examples
The following example shows the HTTP client cache refresh to be 10 seconds:
http client cache refresh 10Related Commands
http client connection idle timeout
To set the number of seconds for which the HTTP client waits before terminating an idle connection, use the http client connection idle timeout command in global configuration mode. To reset to the default, use the no form of this command.
http client connection idle timeout seconds
no http client connection idle timeout
Syntax Description
seconds
How long, in seconds, the HTTP client waits before terminating an idle connection. Range is from 1 to 60. The default is 2.
Command Default
2 seconds
Command Modes
Global configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
The setting of this command determines when the HTTP client is disconnected from the HTTP server, which is necessary when the server does not disconnect the client after a desirable length of time.
The default value is recommended and should normally not be changed.
In the show http client connection command output, this parameter is displayed as connection idle timeout.
The gateway might accept invalid characters such as "#" or "!" when you input the value for this command. The gateway ignores any invalid characters.
Examples
The following example sets the timeout to 40 seconds:
http client connection idle timeout 40Related Commands
http client connection persistent
To enable HTTP persistent connections so that multiple files can be loaded using the same connection, use the http client connection persistent command in global configuration mode. To disable HTTP persistent connections, use the no form of this command.
http client connection persistent
no http client connection persistent
Syntax Description
This command has no arguments or keywords.
Command Default
Persistent connections are enabled
Command Modes
Global configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
The setting of this command determines whether the HTTP client requests a keepalive or closed connection from the server. The HTTP server is responsible for granting or denying the keepalive connection request from the client.
Enabling persistent connections is recommended.
In the show http client connection command output, activation of this command is displayed as persistent connection.
Examples
The following example shows the HTTP client connection persistent parameter to be enabled:
http client connection persistentRelated Commands
http client connection timeout
To set the number of seconds for which the HTTP client waits for a server to establish a connection before abandoning its connection attempt, use the http client connection timeout command in global configuration mode. To reset to the default, use the no form of this command.
http client connection timeout seconds
no http client connection timeout
Syntax Description
seconds
How long, in seconds, the HTTP client waits for a server to establish a connection before abandoning its connection attempt. Range is from 1 to 60. The default is 5.
Command Default
5 seconds
Command Modes
Global configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
The setting of this command determines when the HTTP client abandons its attempt to connect to the server, which is necessary when a connection to the server cannot be established after a desirable length of time.
The default value is recommended and should normally not be changed.
In the show http client connection command output, activation of this command is displayed as initial socket connection timeout.
The gateway might accept invalid characters such as "#" or "!" when you input the value for this command. The gateway ignores any invalid characters.
Examples
The following example shows the HTTP client connection timeout parameter to be 20 seconds:
http client connection timeout 20Related Commands
http client cookie
To enable the HTTP client to send and receive cookies, use the http client cookie command in global configuration mode. To disable cookie support, use the no form of this command.
http client cookie
no http client cookie
Syntax Description
This command has no arguments or keywords.
Command Default
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables RFC 2109-compliant support with the following exceptions:
•
•
•
•
Examples
The following example enables HTTP cookie support if it was previously disabled using the no http client cookie command:
Router(config)# http client cookieRelated Commands
http client response timeout
To configure the number of seconds for which the HTTP client waits for a server response, use the http client response timeout command in global configuration mode. To reset to the default, use the no form of this command.
http client response timeout seconds
no http client response timeout
Syntax Description
seconds
How long, in seconds, the HTTP client waits for a response from the server after making a request. Range is from 1 to 300. The default is 10.
Command Default
10 seconds
Command Modes
Global configuration
Command History
12.2(2)XB
This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.2(11)T
This command was implemented on the Cisco 3640 and Cisco 3660.
Usage Guidelines
This command is used to adjust the time allowed for the HTTP client to wait for the server to respond to a request before declaring a timeout error. Under normal conditions, the default of 10 seconds is sufficient. If more or less server response time is desired, use this command. For example, if your server responds slowly to the HTTP client requests, you may want to set this timer to wait longer.
In the show running-config command output, the value is displayed only if it is set to other than the default.
The gateway might accept invalid characters such as "#" or "!" when you input the value for this command. The gateway ignores any invalid characters.
Examples
The following example shows the HTTP client response timeout to be 5 seconds:
http client response timeout 5Related Commands
show http client cache
Displays the HTTP client cache.
show http client connection
Displays the HTTP client connection.
http client secure-ciphersuite
To set the secure encryption cipher suite for the HTTP client, use the http client secure-ciphersuite command in global configuration mode. To reset to the default, use the no form of this command.
http client secure-ciphersuite {[3des_cbc_sha] [des_cbc_sha] [null_md5] [rc4_128_md5] [rc4_128_sha]}
no http client secure-ciphersuite
Syntax Description
Command Default
All cipher suites.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command to configure one or more cipher suites, or sets of encryption and hash algorithms, on the HTTP client. You must include at least one of the keywords and can include more than one. Use the show http client secure status command to display the cipher suites configured.
Examples
The following example sets the HTTP client to use the 3des_cbc_sha and null_md5 cipher suites:
Router(config)# http client secure-ciphersuite 3des_cbc_sha null_md5Related Commands
http client secure-trustpoint
To declare the trustpoint that the HTTP client will use for HTTPS (HTTP over Secure Socket Layer (SSL)) sessions, use the http client secure-trustpoint command in global configuration mode. To delete all identity information and certificates associated with the trustpoint, use the no form of this command.
http client secure-trustpoint name
no http client secure-trustpoint name
Syntax Description
Command Default
The Public Key Infrastructure (PKI) trustpoint configured on the router, or the primary trustpoint if more than one trustpoint is configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the show http client secure status command to display the trustpoints and cipher suites configured for the client.
Examples
The following example sets the HTTP client's secure CA trustpoint to myca:
Router(config)# http client secure-trustpoint mycaRelated Commands
hunt-scheme least-idle
To enable the least-idle search method for finding an available channel in a trunk group for outgoing calls, use the hunt-scheme least-idle command in trunk group configuration mode. To delete the hunt scheme from the trunk group profile, use the no form of the command.
hunt-scheme least-idle [both | even | odd]
no hunt-scheme
Syntax Description
Command Default
Hunt scheme: least-used
Channel number: bothCommand Modes
Trunk group configuration
Command History
Usage Guidelines
Use the least-idle hunt scheme in situations where you want to reuse the most recently selected channel.
The least-idle hunt scheme looks for the channel that has just become available. The software looks at all the channels in the trunk group, regardless of member precedence, and selects the channel that has most recently come into the available queue.
If no channels are available at the time of the call request, the software returns a cause code determined by the application configured on the inbound dial peer.
If the even quantifier is set, the even-numbered channel with the shortest idle time is selected. If the odd quantifier is set, the odd-numbered channel with the shortest idle time is selected. If both is set, the most recently available channel, regardless of channel number, is selected.
Examples
The following example searches for an even-numbered idle channel having the shortest idle time within a trunk group:
Router(config)# trunk group northwestsalesRouter(config-trunk-group)# hunt-scheme least-idle evenRelated Commands
hunt-scheme longest-idle
Enables the longest-idle hunt scheme.
trunk group
Initiates a trunk group profile.
hunt-scheme least-used
To enable the least used search method for finding an available channel in a trunk group for outgoing calls, use the hunt-scheme least-used command in trunk group configuration mode. To delete the hunt scheme from the trunk group profile, use the no form of the command.
hunt-scheme least-used [both | even | odd [up | down]]
no hunt-scheme
Syntax Description
Command Default
Hunt scheme: least-used
Channel number: both
Direction: upCommand Modes
Trunk group configuration
Command History
Usage Guidelines
The least-used search method selects an idle channel from a trunk group member that has the highest number of available channels at the time that the hunt request is initiated. The high number of unused channels indicates that the trunk group member has not been very active in comparison with other trunk group members.
After selecting the trunk group member, the software searches the channels by direction and then by channel number:
•
•
•
•
If no channel is available in any of the trunk group members, the software returns the standard "no service" message.
Examples
The following example searches in ascending order for an even-numbered idle channel in a trunk group member having the highest number of available channels:
Router(config)# trunk group northwestsalesRouter(config-trunk-group)# hunt-scheme least-used even upRelated Commands
hunt-scheme longest-idle
To enable the longest-idle search method for finding an available channel in a trunk group for outgoing calls, use the hunt-scheme longest-idle command in trunk group configuration mode. To delete the hunt scheme from the trunk group profile, use the no form of this command.
hunt-scheme longest-idle [both | even | odd]
no hunt-scheme
Syntax Description
Command Default
Hunt scheme: least-used
Channel number: bothCommand Modes
Trunk group configuration
Command History
Usage Guidelines
The longest-idle hunt schemes attempts to route a call using a channel from the trunk group member that has been idle for the longest time.
If the even qualifier is set, the search looks for an even-numbered idle channel from the trunk group member that has been idle the longest. If no even-numbered idle channel is found, the search looks for an odd-numbered idle channel from the trunk group member that has the shortest idle time.
If the odd qualifier is set, the search begins looking for an odd-numbered channel from the trunk group member that has been idle the longest. If no odd-numbered idle channel is found, the search looks for an even-numbered idle channel from the trunk group member that has the shortest idle time.
If the both qualifier is set, the search looks for any (odd or even) idle channel in the trunk group member that has been idle the longest.
If no channel is available in any of the trunk group members, the software returns the standard "no service" message.
Examples
The following example searches in ascending order for an even-numbered idle channel in the trunk group member having the largest idle time:
Router(config)# trunk group northwestsalesRouter(config-trunk-group)# hunt-scheme longest-idle evenRelated Commands
hunt-scheme least-idle
Enables the least-idle hunt scheme.
trunk group
Initiates a trunk group profile.
hunt-scheme random
To enable the random search method for finding an available channel in a trunk group for outgoing calls, use the hunt-scheme random command in trunk group configuration mode. To delete the hunt scheme from the trunk group profile, use the no form of this command.
hunt-scheme random
no hunt-scheme
Syntax Description
This command has no arguments or keywords.
Command Default
Hunt scheme: least-used
Command Modes
Trunk group configuration
Command History
Usage Guidelines
The random search method selects trunk group member at random for an idle channel. After the trunk group member is selected, a channel is chosen at random. If that channel is not available, another trunk group member is chosen at random, and one of its channels is randomly chosen.
If no channel is available, the software returns the standard "no service" message.
Examples
The following example searches trunk group members in random order for an idle channel:
Router(config)# trunk group northwestsalesRouter(config-trunk-group)# hunt-scheme randomRelated Commands
hunt-scheme round-robin
To enable the round robin search method for finding an available channel in a trunk group for outgoing calls, use the hunt-scheme command in trunk group configuration mode. To delete the hunt scheme from the trunk group profile, use the no form of this command.
hunt-scheme round-robin [both | even | odd [up | down]]
no hunt-scheme
Syntax Description
Command Default
Hunt scheme: least-used
Channel number: bothCommand Modes
Trunk group configuration
Command History
Usage Guidelines
The round-robin hunt scheme searches trunk group members one after the other for an idle channel. The history of the most recently used trunk group member is saved to identify the next trunk group member to use for a new idle channel request. This method tries to balance the load of channel use across trunk group members.
For example, suppose a trunk group has three trunk group members: A, B, and C. Trunk group member A has the highest preference, B has the next highest, and C has the lowest. The software starts the search with A:
•
•
•
•
•
•
If none of the trunk group members has an idle channel available for the current channel request, the software returns the standard "no service" message.
Compare this hunt scheme with hunt-scheme sequential, in which the next request for an idle channel always starts with the first trunk group member of the trunk group, regardless of where the last idle channel was found.
If the even qualifier is set, the search looks for an even-numbered idle channel starting with the trunk group member having the highest preference. If no even-numbered idle channel is found, the search looks for an even-numbered idle channel in the next trunk group member. If no even-numbered idle channel is found in any trunk group member, the search repeats the process for an odd-numbered channel.
If the odd qualifier is set, the search begins looking for an odd-numbered channel, and if none is found in any of the trunk group members, the search repeats the process for an even-numbered channel.
If the both qualifier is set, the search looks for any idle channel in the trunk group member.
Examples
The following example searches for an even-numbered idle channel starting with the trunk group member next in order after the previously used member:
Router(config)# trunk group northwestregionRouter(config-trunk-group)# hunt-scheme round-robin evenRelated Commands
hunt-scheme sequential
Enables a "sequential idle channel" hunt scheme.
trunk group
Initiates a trunk group profile definition.
hunt-scheme sequential
To specify the sequential search method for finding an available channel in a trunk group for outgoing calls, use the hunt-scheme sequential command in trunk group configuration mode. To delete the hunt scheme from the trunk group profile, use the no form of this command.
hunt-scheme sequential [both | even | odd [up | down]]
no hunt-scheme
Syntax Description
Command Default
Hunt scheme: least-used
Channel number: both
Direction: upCommand Modes
Trunk group configuration
Command History
Usage Guidelines
The sequential hunt scheme selects an idle channel, starting with the trunk group member that has the highest preference within the trunk group. Regardless of where the last idle channel was found, an idle channel request starts searching with this highest-preference trunk group member.
For example, suppose a trunk group has three trunk group members: A, B, and C. Trunk group member A has the highest preference, B has the next highest, and C has the lowest. The software starts the search with trunk group A:
•
•
•
•
•
•
Compare this hunt scheme with hunt-scheme round-robin, where the next request for an idle channel starts with the next unused trunk group member of the trunk group.
If the even qualifier is set, the search looks for an even-numbered idle channel starting with the trunk group member having the highest preference. If no even-numbered idle channel is found, the search looks for an even-numbered idle channel in the next trunk group member. If no even-numbered idle channel is found, the search repeats the process for an odd-numbered idle channel.
If the odd qualifier is set, the search begins looking for an odd-numbered channel, starting with the trunk group member having the highest preference. If none is found in any of the trunk group members, the search repeats the process for an even-numbered channel.
If the both qualifier is set, the search looks for any idle channel in the trunk group member.
Use the sequential hunt scheme in situations that benefit from a predictable channel allocation. In addition, if one end of the routing path is defined with sequential even up and the other end with sequential odd up, glare conditions are avoided.
Examples
The following example searches in ascending order for an even-numbered idle channel starting with the trunk group member of highest precedence:
Router(config)# trunk group northwestsalesRouter(config-trunk-group)# hunt-scheme sequential even upRelated Commands
hunt-scheme round-robin
Enables a round-robin hunt scheme.
trunk group
Initiates a trunk group profile definition.
huntstop
To disable all dial-peer hunting if a call fails when using hunt groups, use the huntstop command in dial peer configuration mode. To reenable dial-peer hunting, use the no form of this command.
huntstop
no huntstop
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
Dial peer configuration
Command History
Usage Guidelines
Once you enter this command, no further hunting is allowed if a call fails on the specified dial peer.
Note
Examples
The following example shows how to disable dial-peer hunting on a specific dial peer:
dial peer voice 100 vofrhuntstopThe following example shows how to reenable dial-peer hunting on a specific dial peer:
dial peer voice 100 vofrno huntstopRelated Commands
dial-peer voice
Enters dial peer configuration mode and specifies the method of voice-related encapsulation.
