- A
- B
- cac master through call application stats
- call application voice through call denial
- call fallback through called-number (dial peer)
- caller-id (dial peer) through ccm-manager switchover-to-backup
- ccs connect (controller) through clear vsp statistics
- clid through credentials (sip-ua)
- default (auto-config application) through direct-inward-dial
- disable-early-media through dualtone
- E
- F
- G
- H
- icpif through irq global-request
- isdn bind-l3 through ixi transport http
- K
- L
- map q850-cause through mgcp package-capability
- mgcp persistent through mmoip aaa send-id secondary
- mode (ATM/T1/E1 controller) through mwi-server
- N
- O
- package through pattern
- periodic-report interval through proxy h323
- Q
- R
- sccp through service-type call-check
- session through sgcp tse payload
- show aal2 profile through show call filter match-list
- show call history fax through show debug condition
- show dial-peer through show gatekeeper zone prefix
- show gateway through show modem relay statistics
- show mrcp client session active through show sip dhcp
- show sip service through show trunk hdlc
- show vdev through show voice statistics memory-usage
- show voice trace through shutdown (voice-port)
- signal through srv version
- ss7 mtp2-variant through switchover method
- target carrier-id through timeout tsmax
- timeouts call-disconnect through timing clear-wait
- timing delay-duration through type (voice)
- U
- vad (dial peer) through voice-class sip encap clear-channel
- voice-class sip error-code-override through vxml version 2.0
- W
- Z
- timeouts call-disconnect
- timeouts initial
- timeouts interdigit (voice port)
- timeouts power-denial
- timeouts ringing
- timeouts wait-release
- timeouts teardown lmr
- timer accessrequest sequential delay
- timer cluster-element
- timer irr period
- timer lrq seq delay
- timer lrq seq delay centisec
- timer lrq window
- timer lrq window decisec
- timer media-inactive
- timer receive-rtcp
- timer receive-rtp
- timer server retry
- timer server timeout
- timers
- timers buffer-invite
- timers comet
- timers connect
- timers connection aging
- timers disconnect
- timers expires
- timers hold
- timers keepalive
- timers notify
- timers prack
- timers refer
- timers register
- timers rel1xx
- timers trying
- timing clear-wait
timeouts call-disconnect
To configure the delay time for which a Foreign Exchange Office (FXO) voice port waits before disconnecting an incoming call after disconnect tones are detected, use the timeouts call-disconnect command in voice-port configuration mode. To reset to the default, use the no form of this command.
timeouts call-disconnect {seconds | infinity}
no timeouts call-disconnect
Syntax Description
Command Default
60 seconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use this command to change the time for which an FXO voice port remains connected after the calling party hangs up, when a call is not answered. Use of the infinity keyword is not recommended for disabling the disconnect supervision feature.
Examples
The following example configures voice port 0/0/1 to remain connected for 3 seconds while a disconnect tone is received by the voice port:
voice-port 0/0/1
timeouts call-disconnect 3
Related Commands
timeouts initial
To configure the initial digit timeout value for a specified voice port, use the timeouts initial command in voice-port configuration mode. To reset to the default, use the no form of this command.
timeouts initial seconds
no timeouts initial seconds
Syntax Description
seconds |
Initial timeout duration, in seconds. Range is 0 to 120. The default is 10. |
Command Default
10 seconds
Command Modes
Voice-port configuration
Command History
|
|
|
|---|---|
11.3(1)T |
This command was introduced on Cisco 3600 series routers. |
Usage Guidelines
Use the timeouts initial command to specify the number of seconds for which the system waits for the caller to input the first digit of the dialed digits. The timeouts initial timer is activated when the call is accepted and is deactivated when the caller inputs the first digit. If the configured timeout value is exceeded, the caller is notified through the appropriate tone and the call is terminated.
To disable the timeouts initial timer, set the seconds value to 0.
Examples
The following example sets the initial digit timeout value to 10 seconds:
voice-port 1/0/0
timeouts initial 10
Related Commands
|
|
|
|---|---|
timeouts interdigit |
Configures the interdigit timeout value for a specified voice port. |
timeouts interdigit (voice port)
To configure the interdigit timeout value for a specified voice port, use the timeouts interdigit command in voice-port configuration mode. To reset to the default, use the no form of this command.
timeouts interdigit seconds
no timeouts interdigit seconds
Syntax Description
seconds |
Interdigit timeout duration, in seconds. Range is 0 to 120. The default is 10. |
Command Default
10 seconds
Command Modes
Voice-port configuration
Command History
|
|
|
|---|---|
11.3(1)T |
This command was introduced on Cisco 3600 series. |
Usage Guidelines
Use this command to specify the number of seconds for which the system waits (after the caller inputs the initial digit) for the caller to input a subsequent digit of the dialed digits. The timeouts interdigit timer is activated when the caller inputs a digit and is restarted each time the caller inputs another digit until the destination address is identified. If the configured timeout value is exceeded before the destination address is identified, the caller is notified through the appropriate tone and the call is terminated.
To disable the timeouts interdigit timer, set the seconds value to 0.
Examples
The following example sets the interdigit timeout value on the Cisco 3600 series for 10 seconds:
voice-port 1/0/0
timeouts interdigit 10
The following example sets the interdigit timeout value on the Cisco MC3810 for 10 seconds:
voice-port 1/1
timeouts interdigit 10
Related Commands
|
|
|
|---|---|
timeouts initial |
Configures the initial digit timeout value for a specified voice port. |
timeouts power-denial
To set the duration of the power denial timeout for the specified FXS voice port, use the timeouts power-denial command in voice-port configuration mode. To reset the timeout to the default, use the no form of this command.
timeouts power-denial ms
no timeouts power-denial
Syntax Description
ms |
Length of power denial, in milliseconds (ms). Range: 0 to 2500. Default: 750. |
Command Default
Default is 750 ms.
Command Modes
Voice-port configuration
Command History
|
|
|
|---|---|
12.2(13)T |
This command was introduced. |
12.4(2)T |
The maximum value of the ms argument was increased from 1500 to 2500. |
Usage Guidelines
This command sets the duration of the power denial that the voice gateway applies to the FXS port when a call disconnects. During the power denial duration the caller hears silence. To disable the power denial on a port, use the no supervisory disconnect lcfo command.
Examples
The following example sets the power-denial duration to 500 ms:
voice-port 2/0
timeouts power-denial 500
Related Commands
|
|
|
|---|---|
supervisory disconnect lcfo |
Signals a disconnect on an FXS loop-start port by applying a power denial using a LCFO. |
timeouts ringing
To configure the timeout value for ringing, use the timeouts ringing command in voice-port configuration mode. To reset to the default, use the no form of this command.
timeouts ringing {seconds | infinity}
no timeouts ringing
Syntax Description
Command Default
infinity for SCCP-controlled analog ports; 180 seconds for all other ports.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
This command allows you to limit the length of time for which a caller can continue ringing a telephone when there is no answer.
In Cisco IOS Release 12.4(11)T and later the default for this command is set to infinity for SCCP-controlled analog ports to prevent this timeout from expiring before the ringing no-answer timeout that is configured on Cisco Unified CallManager Express with the timeouts ringing command in telephony-service mode.
Examples
The following example configures voice port 0/0/1 to allow ringing for 600 seconds:
voice-port 0/0/1
timeouts ringing 600
Related Commands
timeouts wait-release
To configure the delay timeout before the system starts the process for releasing voice ports, use the timeouts wait-release command in voice-port configuration mode. To reset to the default, use the no form of this command.
timeouts wait-release {seconds | infinity}
no timeouts wait-release
Syntax Description
Command Default
30 seconds
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use this command to limit the time a voice port can be held in a call failure state. After the timeout, the release sequence is enabled.
You can also use this command for voice ports with Foreign Exchange Station (FXS) loop-start signaling to specify the time allowed for a caller to hang up before the voice port goes into the parked state.
Examples
The following example configures voice port 0/0/1 to stay in the call-failure state for 180 seconds while a busy tone, reorder tone, or out-of-service tone is sent to the voice port:
voice-port 0/0/1
timeouts wait-release 180
Related Commands
|
|
|
timeouts initial |
Configures the initial digit timeout value for a voice port. |
timeouts interdigit |
Configures the interdigit timeout value for a voice port. |
timeouts teardown lmr
To configure the time for which a Land Mobile Radio (LMR) voice port waits before tearing down an LMR connection after detecting no voice activity, use the timeouts teardown lmr command in voice-port configuration mode. To reset to the default, use the no form of this command.
timeouts teardown lmr {seconds | infinity}
no timeouts teardown lmr {seconds | infinity}
Syntax Description
Command Default
180 seconds
Command Modes
Voice-port configuration
Command History
|
|
|
|---|---|
12.3(4)XD |
This command was introduced. |
12.3(7)T |
This command was integrated into Cisco IOS Release 12.3(7)T. |
Usage Guidelines
The timeouts teardown lmr command has an effect on an ear and mouth (E&M) voice port only if the signal type for that port is LMR.
Examples
The following example configures voice port 1/0/1 on a Cisco 3745 to remain connected for 6 seconds after no voice activity is detected by the voice port:
voice-port 1/0/1
timeouts teardown lmr 6
Related Commands
timer accessrequest sequential delay
To configure the intermessage delay used when a border element (BE) is trying to determine a route from a list of neighboring BEs, use the timer accessrequest sequential delay command in Annex G configuration mode. To reset the default value, use the no form of this command.
timer accessrequest sequential delay value
no timer
Syntax Description
value |
Amount of allowed intermessage delay (in increments of 100 ms). Range is from 0 to 10. The default is 1 (100 ms). |
Command Default
1 (100 ms)
Command Modes
Annex G configuration
Command History
Usage Guidelines
Setting the value of the delay to 0 causes the BE to broadcast or "blast" the AccessRequest messages to all eligible neighbors.
Examples
The following example shows a timer delay of 1000 ms.
Router(config)# call-router h323-annexg be20
Router(config-annexg)# timer accessrequest sequential delay 10
Related Commands
|
|
|
|---|---|
call-router |
Enables the Annex G border element configuration commands. |
timer cluster-element
To configure the length of time between dynamic capacity messages to the local gatekeeper, use the timer cluster-element command in gatekeeper configuration mode. To stop sending dynamic updates, use the no form of this command.
timer cluster-element {announce | resource-update} seconds
no timer cluster-element
Syntax Description
Command Default
Disabled by default.
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
Use the timer cluster-element command to manage the length of time between resource updates and time between announcement messages sent to the gatekeeper. The announcement indication is exchanged at a set interval of time and carries information about the call and endpoint capacity for the zone. This allows the alternate gatekeepers to manage the bandwidth for a single zone even though the gatekeepers are in separate physical devices.
The gatekeeper assumes that the alternate gatekeeper has failed (and assumes that any previously allocated bandwidth is now available) if the gatekeeper does not receive an announcement message within six announcement periods or if the TCP connection with the gatekeeper is detected to be broken.
Lower this interval for closer tracking between elements. Raise it to lower messaging overhead.
Examples
The following command sets the announcement period to 20 seconds:
Router(config-gk)# timer cluster-element announce 20
The following command resets the announcement period to the default value:
Router(config-gk)# no timer cluster-element announce
The following example shows the time between resource update messages to gatekeepers in local cluster being set to 20 seconds:
Router(config-gk)# timer cluster-element resource-update 20
Related Commands
timer irr period
To configure the information request response (IRR) timer, or the periodic interval of IRR messages sent by the gatekeeper, use the timer irr period command in gatekeeper configuration mode. To disable, use the no form of this command.
timer irr period minutes
no timer irr period
Syntax Description
minutes |
Length, in minutes, of the interval between IRR messages. Range is from 1 to 60. The default is 4. |
Command Default
4 minutes
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.2(11)T |
This command was introduced. |
Usage Guidelines
Use this command to configure IRR frequency that is included in the admission confirm (ACF) message. The IRR frequency is set to 240 seconds (4 minutes), based on an average 4-minute call hold time. The IRR allows the gatekeepers to terminate calls for which a disengage request (DRQ) has not been received. If missing DRQs are not a problem, the IRR frequency can be set to a larger value than 4 minutes, minimizing the number of unnecessary IRRs sent by a gateway.
Examples
The following example shows that the IRR timer has been configured with a value of 45, meaning that IRR messages are sent by the gatekeeper every 45 minutes:
gatekeeper
.
.
.
lrq reject-resource-low
no irq global-request
timer lrq seq delay 10
timer lrq window 6
timer irr period 45
no shutdown
Related Commands
timer lrq seq delay
To define the time interval between successive sequential location requests (LRQs), use the timer lrq seq delay command in gatekeeper configuration mode. To reset to the default, use the no form of this command.
timer lrq seq delay time
no timer lrq seq delay
Syntax Description
time |
Time interval, in 100-millisecond units. Range is 1 to 10 (0.1 to 1 second). The default is 5 (500 milliseconds). |
Command Default
5 units (500 milliseconds)
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.1(5)XM |
This command was introduced. |
12.2(2)T |
This command was integrated into Cisco IOS Release 12.2(2)T. |
12.2(2)XB1 |
This command was implemented on Cisco AS5850. |
Usage Guidelines
The LRQ sequential timing source (SEQ) delay is used to set the time between sending LRQs to remote gatekeepers for address resolution. To resolve an address, the gatekeeper might have several remote zones configured, and it can send the LRQs simultaneously (blast) or sequentially (seq). The gatekeeper chooses the best route based on availability and cost. Using LRQs sequentially results in lower network traffic, but it can increase latency of calls when the most preferred route is unavailable.
Lowering the time increases traffic on the network but might reduce the call setup time.
Examples
The following command sets the LRQ delay timer to 100 milliseconds:
timer lrq seq delay 1
The following command resets the LRQ delay timer to the default value:
no timer lrq seq delay
Related Commands
|
|
|
|---|---|
timer lrq window |
Defines the time window during which the gatekeeper collects responses to one or more outstanding LRQs. |
timer lrq seq delay centisec
To define the time interval between successive sequential location requests (LRQs), use the timer lrq seq delay centices command in gatekeeper configuration mode. To reset to the default, use the no form of this command.
timer lrq seq delay centisec time
no timer lrq seq delay centisec
Syntax Description
time |
Time interval, in 100-millisecond units. Range is 1 to 10 (0.1 to 1 second). The default is 1(100 milliseconds). |
Command Default
Timers are set to their default value.
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The LRQ sequential timing source (SEQ) delay is used to set the time between sending LRQs to remote gatekeepers for address resolution. To resolve an address, the gatekeeper might have several remote zones configured, and it can send the LRQs simultaneously (blast) or sequentially (seq). The gatekeeper chooses the best route based on availability and cost. Using LRQs sequentially results in lower network traffic, but it can increase latency of calls when the most preferred route is unavailable.
Lowering the time increases traffic on the network but might reduce the call setup time.
Note 
This command cannot be configured at the same time as the timer lrq seq delay command.
Examples
The following command sets the LRQ delay timer to 100 milliseconds:
timer lrq seq delay centisec 1
The following command resets the LRQ delay timer to the default value:
no timer lrq seq delay centisec
Related Commands
|
|
|
|---|---|
timer lrq window decisec |
Defines the time window during which the gatekeeper collects responses to one or more outstanding LRQs. |
timer lrq window
To define the time window during which the gatekeeper collects responses to one or more outstanding LRQs, use the timer lrq window command in gatekeeper configuration mode. To reset to the default, use the no form of this command.
timer lrq window seconds
no timer lrq window
Syntax Description
seconds |
Time window, in seconds. Range is 1 to 15. The default is 3. |
Command Default
3 seconds
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.1(5)XM |
This command was introduced. |
12.2(2)T |
This command was integrated into Cisco IOS Release 12.2(2)T. |
12.2(2)XB1 |
This command was implemented on Cisco AS5850. |
Usage Guidelines
Increasing the time can increase the call success rate but might reduce the overall time for call setup.
Examples
The following command sets the timer to 5 seconds:
timer lrq window 5
The following command sets the timer to the default value:
no timer lrq window
Related Commands
|
|
|
|---|---|
timer lrq seq delay |
Defines the time interval between successive sequential LRQs. |
timer lrq window decisec
To define the time window during which the gatekeeper collects responses to one or more outstanding LRQs, use the timer lrq window decisec command in gatekeeper configuration mode. To reset to the default, use the no form of this command.
timer lrq window decisec time
no timer lrq window decisec
Syntax Description
time |
Time window, in seconds. Range is 1 to 15. The default is 2. |
Command Default
Timers are set to their default value.
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.4(4)T |
This command was introduced. |
Usage Guidelines
Increasing the time can increase the call success rate but might reduce the overall time for call setup.
Note This command cannot be in effect at the same time as the timer lrq window command.
Examples
The following command sets the timer to 5 seconds:
timer lrq window decisec 2
The following command sets the timer to the default value:
no timer lrq window decisec
Related Commands
|
|
|
|---|---|
timer lrq seq delay centsec |
Defines the time interval between successive sequential LRQs. |
timer media-inactive
To enable the timer for media inactivity detection using the digital signal processor (DSP) (based on RTP as the only criterion) and to configure a multiplication factor based on the real-time control protocol (RTCP) timer interval, use the timer media-inactive command in gateway configuration mode. To reset to the default, use the no form of this command.
timer media-inactive multiple
no timer media-inactive multiple
Syntax Description
multiple |
Multiples of the RTCP report transmission interval. Range is 4 to 1000. The default is 5, and the recommended value is 5. |
Command Default
A call is considered inactive if no RTP packet activity is detected for a period of time calculated as five times the interval set by the ip rtcp report interval command.
Command Modes
Gateway configuration
Command History
|
|
|
|---|---|
12.4(4)T |
This command was introduced. |
Usage Guidelines
When the timer media-inactive command is used, the gateway uses the inactivity timer as a combination of the timer media-inactive command and the ip rtcp report interval command. The timer media-inactive command uses DSP statistics. This capability is based on the configuration of callfeature parameters using application command-line interface (CLI) to enable control.
The media are considered inactive only if there is no transfer of RTP packets in the send direction and no RTP packets in the receive direction. If RTP is present in either the send or receive direction, it is considered active. In this mode, DSP filters out any comfort noise packets, and the presence of any comfort noise packet is considered inactivity in either direction.
The multiple argument (or multiplication factor) is multiplied by the interval that is set using the ip rtcp report interval command. This command configures the average interval between successive RTCP report transmissions for a given voice session. For example, if the value argument is set to 25,000 milliseconds, an RTCP report is sent every 25 seconds, on average. If no RTP packets are received during the calculated interval, the call is disconnected. The gateway signals the disconnect to the VoIP network and the time-division multiplexing (TDM) network so that upstream and downstream devices can clear their resources.
Examples
The following example uses the ip rtcp report interval command to set the reporting interval to 5000 milliseconds, and then the timer media-inactive command to set the multiplication factor to 10. The result is that calls detected as inactive for 50 seconds (5,000 milliseconds times 10) will be disconnected.
Router(config)# ip rtcp report interval 5000
Router(config)# gateway
Router(config-gateway)# timer media-inactive 10
Router(config-gateway)# exit
Related Commands
|
|
|
|---|---|
ip rtcp report interval |
Configures the minimum interval of RTCP report transmissions. |
timer receive-rtcp
To enable the Real-Time Control Protocol (RTCP) timer and to configure a multiplication factor for the RTCP timer interval for Session Initiation Protocol (SIP) or H.323, use the timer receive-rtcp command in gateway configuration mode. To reset to the default, use the no form of this command.
timer receive-rtcp timer
no timer receive-rtcp timer
Syntax Description
timer |
Multiples of the RTCP report transmission interval. Range is 0 to 1000. Default is 0. Recommended value is 5. |
Command Default
The default value for the timer argument is 0 multiples, which disables the timer so that no silence detection is in effect.
Command Modes
Gateway configuration
Command History
Usage Guidelines
The timer receive-rtcp command uses library-based detection and the receipt of either Real-Time Protocol (RTP) or RTCP packets is considered activity on a call. Silence detection occurs only if there are no packets received for both RTP and RTCP.
When the ip rtcp report interval and timer receive-rtcp commands are used, the gateway uses RTCP report detection, rather than RTP packet detection, to determine whether calls on the gateway are still active or should be disconnected. RTCP report detection is therefore more reliable than RTP packet detection because there can be periods during voice calls when one or both parties are not sending RTP packets.
One common example of a voice session in which no RTP is sent is when a caller dials into a conference call and mutes that endpoint. If voice activity detection (VAD, also known as silence suppression) is enabled, no RTP packets are sent while the endpoint is muted. However, the muted endpoint continues to send RTCP reports at the interval specified by the ip rtcp report interval command.
The timer receive-rtcp timer argument (or m factor for multiplication factor) is multiplied by the interval that is set using the ip rtcp report interval command. If no RTP or RTCP packets are received during the calculated interval, the call is disconnected. The gateway signals the disconnect to the VoIP network and the time-division multiplex (TDM) network so that upstream and downstream devices can clear their resources. The gateway sends a Q.931 DISCONNECT message to the TDM network and a SIP BYE or H.323 ReleaseComplete message to the VoIP network to clear the call when the timer expires. The Q.931 DISCONNECT message is sent with a cause code value of 3 (no route) for SIP calls and a cause code value of 41 (temporary failure) for H.323 calls. No Q.931 Progress Indicator (PI) value is included in the DISCONNECT message.
To show timer-related output for SIP calls, use the debug ccsip events command. To show timer-related output for H.323 calls, use the debug cch323 h225 command.
Examples
The following example sets the multiplication factor to 10 (or x * 10, where x is the interval that is set with the ip rtcp report interval command):
Router(config)# gateway
Router(config-gateway)# timer receive-rtcp 10
Router(config-gateway)# exit
Related Commands
timer receive-rtp
To configure the Real-Time Transport Protocol (RTP) timeout interval to clear connections that pause indefinitely, use the timer receive-rtp command in gateway configuration mode. To reset the timer to the default value, use the no form of this command.
timer receive-rtp seconds
no timer receive-rtp
Syntax Description
seconds |
Timer value, in seconds. Range: 180 to 86400. Default: 1200. |
Defaults
1200 seconds (20 minutes)
Command Modes
Gateway configuration (config-gateway)
Command History
|
|
|
|---|---|
12.3(8)T |
This command was introduced. |
12.4(20)T |
This command was modified. The recommended timer range is defined as 1200 seconds. |
Usage Guidelines
This command is used to configure the RTP timeout interval in seconds. The timeout value is used to clear connections that pause indefinitely. The recommended value is 1200 seconds, or 20 minutes.
Examples
The following example shows the RTP timeout interval set to the recommended 1200 seconds (20 minutes).
Router(config-gateway)# timer receive-rtp 600
Related Commands
timer server retry
To set the gatekeeper's retry timer for failed Gatekeeper Transaction Message Protocol (GKTMP) connections, use the timer server retry command in gatekeeper configuration mode. To reset the timer to its default, use the no form of this command or the default server timer retry command.
server timer retry seconds
no server timer retry
default server timer retry
Syntax Description
seconds |
Number of seconds for which the gatekeeper should wait before retrying the GKTMP server. Range is from 1 through 300. The default is 30. |
Command Default
30 seconds
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.2(11)T |
This command was introduced. |
Usage Guidelines
After the gatekeeper detects that its GKTMP server TCP connection has failed, the gatekeeper retries the server after an interval based on the setting of this timer, and keeps retrying until the connection is established.
This timer applies only to deployments where static triggers are used between the gatekeeper and the GKTMP server. If dynamic triggers are used, the server must determine and implement a retry mechanism if the TCP connection to the gatekeeper fails.
Examples
The following example shows that the retry timer has been set to 45 seconds:
Router# show gatekeeper configuration
.
.
.
h323id tet
gw-type-prefix 1#* default-technology
gw-type-prefix 9#* gw ipaddr 1.1.1.1 1720
timer server retry 45
no shutdown
.
.
.
Related Commands
|
|
|
|---|---|
timer server timeout |
Specifies the timeout value for a response from a back-end GKTMP server. |
timer server timeout
To specify the timeout interval for a response from a back-end Gatekeeper Transaction Message Protocol (GKTMP) application server, use the timer server timeout command in gatekeeper configuration mode. To reset to the default, use the no form of this command.
timer server timeout time
no timer server timeout
Syntax Description
time |
Timeout interval, in 100-ms units. Range is 1 to 50 (0.1 to 5 seconds). Default is 3 (300 ms). |
Command Default
3 units
Command Modes
Gatekeeper configuration
Command History
|
|
|
|---|---|
12.1(2)XM |
This command was introduced. |
12.2(2)T |
This command was integrated into Cisco IOS Release 12.2(2)T. |
12.2(2)XB1 |
This command was implemented on the Cisco AS5850. |
Usage Guidelines
Use this command to specify the timeout interval for a response from a back-end GKTMP application server.
Examples
The following command sets the timeout interval to 400 ms:
timer server timeout 4
The following command resets the timeout interval to the default value:
no timer server timeout
Related Commands
timers
To configure the Session Initiation Protocol (SIP) signaling timers, use the timers command in SIP UA configuration mode. To restore the default value, use the no form of this command.
timers {trying number | connect number | disconnect number | expires number}
no timers
Syntax Description
Command Default
trying, connect, and disconnect—500 ms
expires—180000 ms
Command Modes
SIP UA configuration
Command History
Usage Guidelines
If you used an earlier version of this command to configure timers, the timer settings are maintained. The output of the show running-config command reflects both previous and current timers.
To reset this command to the default value, you can also use the default command.
Examples
The following example sets the trying timers to the default of 500 ms.
Router(config)# sip-ua
Router(config-sip-ua)# timers trying 500
Related Commands
timers buffer-invite
To enable the Session Initiation Protocol (SIP) buffer-invite timer and to configure the timer interval, use the timers buffer-invite command in SIP UA configuration mode. To restore the default value, use the no form of this command.
timers buffer-invite timer
no timers buffer-invite
Syntax Description
timer |
Buffer-invite timer value, in ms. Range is 50 to 5000. |
Command Default
Disabled
Command Modes
SIP UA configuration
Command History
|
|
|
|---|---|
12.3(8)T |
This command was introduced. |
Usage Guidelines
Use this command to enable the SIP buffer-invite timer and to configure the timer interval.
Examples
The following example sets retransmission time to 500 milliseconds:
Router(config)# sip-ua
Router(config-sip-ua)# timers buffer-invite 500
Related Commands
|
|
|
|---|---|
sip-ua |
Enables SIP UA configuration commands. |
timers comet
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits before retransmitting conditions-met (COMET) requests, use the timers comet command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers comet time
no timers comet
Syntax Description
time |
Waiting time, in milliseconds. Range is 100 to 1000. The default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Usage Guidelines
COMET, or conditions met, indicates whether preconditions for a given call or session have been met. This command is applicable only with calls involving quality of service (QoS) (calls other than best-effort).
Examples
The following example sets retransmission time to 500 milliseconds:
Router(config)# sip-ua
Router(config-sip-ua)# timers comet 500
Related Commands
timers connect
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits for a 200 response to an ACK request, use the timers connect command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers connect number
no timers connect number
Syntax Description
number |
Waiting time, in milliseconds. Range is from 100 to 1000. The default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Usage Guidelines
If you used the previous more generic timers command to configure timers, your previous timer settings are maintained. The output of the show running-config command reflects both timers.
To reset this command to the default value, you can also use the default command.
Examples
The following example sets connect time to 200 milliseconds:
sip-ua
timers connect 200
Related Commands
|
|
|
|---|---|
sip-ua |
Enables the SIP UA configuration commands. |
timers connection aging
To globally set the time before the Session Initiation Protocol (SIP) user agent (UA) ages out a TCP or UDP connection because of inactivity, use the timers connection aging command in SIP UA configuration mode. To reset this time to the default value, use the no form of this command.
timers connection aging timer-value
no timers connection aging
Syntax Description
timer-value |
Time to wait, in minutes, before aging out a TCP or UDP connection because of inactivity. Range is from 5 to 30. Default is 5. |
Command Default
5 minutes
Command Modes
SIP UA configuration
Command History
|
|
|
|---|---|
12.3(8)T |
This command was introduced. |
Usage Guidelines
The minimum value of this connection is 5 minutes.
Examples
The following example ages out a connection in 10 minutes:
sip-ua
timers connection aging 10
Related Commands
timers disconnect
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits for a 200 response to a BYE request, use the timers disconnect command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers disconnect time
no timers disconnect time
Syntax Description
time |
Waiting time, in milliseconds. Range is 100 to 1000. The default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Usage Guidelines
If you used the previous more generic timers command to configure timers, your previous timer settings are maintained. The output of the show running-config command reflects both timers.
To reset this command to the default value, you can also use the default command.
Examples
The following example sets disconnect time to 200 milliseconds:
sip-ua
timers disconnect 200
Related Commands
|
|
|
|---|---|
sip-ua |
Enables the SIP UA configuration commands. |
timers expires
To set how long a Session Initiation Protocol (SIP) INVITE request is valid, use the timers expire command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers expires time
no timers expires
Syntax Description
time |
Expiration time, in ms. Range is 60,000 to 300,000. Default is 180000. |
Command Default
180000 ms
Command Modes
SIP UA configuration
Command History
Usage Guidelines
If you used the previous more generic timers command to configure timers, your previous timer settings are maintained. The output of the show running-config command reflects both timers.
To reset this command to the default value, you can also use the default command.
Examples
The following example sets the expiration time to 180,000 ms:
sip-ua
timers expires 180000
Related Commands
|
|
|
|---|---|
default |
Enables a default aggregation cache. |
sip-ua |
Enables the SIP UA configuration commands. |
timers |
Configures the SIP signaling timers. |
timers hold
To enable the Session Initiation Protocol (SIP) hold timer and configure the timer interval before disconnecting a held call, use the timers hold command in SIP UA configuration mode. To restore the default value, use the no form of this command.
timers hold time
no timers hold
Syntax Description
time |
Specifies the time (in minutes) to wait before sending a BYE request. Range is from 15 to 2880 minutes. The default is 2880. |
Command Default
Enabled
time: 2880 minutes
Command Modes
SIP UA configuration mode
Command History
|
|
|
|---|---|
12.3(1) |
This command was introduced. |
Usage Guidelines
The hold timer is typically activated when a gateway receives a call hold request from the other endpoint, for example, a SIP phone.
Examples
The following example sets the hold timer to expire after 75 minutes:
Router(config-sip-ua)# timers hold 75
Related Commands
timers keepalive
To set the keepalive timers interval between sending Options message requests when the session initiation protocol (SIP) servers are in the down state, use the timers keepalive command in SIP user agent configuration mode. To restore the keepalive timers to the default value of 120 seconds when active or 30 seconds when down, use the no form of this command.
timers keepalive {active | down} seconds
no timers keepalive {active | down} seconds
Syntax Description
Command Default
The default value for the active state is 120 seconds and the default value for the down state is 30 seconds.
Command Modes
SIP user agent configuration
Command History
|
|
|
|---|---|
12.4(6)T |
This command was introduced. |
Usage Guidelines
Use this command to change the keepalive message time interval in seconds between the sending Options message requests when the SIP server or servers are either in the active or down state.
Examples
The following example sets the keepalive message time interval to 20 seconds when the SIP server is in the active state:
sip-ua
timers keepalive active 20
The following example sets the keepalive message time interval to 10 seconds when the SIP server is in the down state:
sip-ua
timers keepalive down 10
Related Commands
timers notify
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits before retransmitting a Notify message, use the timers notify command in SIP user-agent configuration mode. To reset to the default, use the no form of this command.
timers notify time
no timers notify
Syntax Description
time |
Waiting time, in milliseconds. Range is 100 to 1000. The default is 500. |
Defaults
500 milliseconds
Command Modes
SIP user-agent configuration
Command History
Usage Guidelines
A Notify message informs the user agent that initiated the transfer or Refer request about the outcome of the SIP transaction.
Examples
The following example sets retransmission time to 500 milliseconds:
Router(config)# sip-ua
Router(config-sip-ua)# timers notify 500
Related Commands
|
|
|
|---|---|
show sip-ua statistics |
Displays response, traffic, timer, and retry statistics |
show sip-ua timers |
Displays the current settings for SIP UA timers |
timers prack
To set how long the Session Initiation Protocol (SIP) user agent (UA) wait s before retransmitting a provisional response acknowledgement (PRACK) request, use the timers prack command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers prack time
no timers prack
Syntax Description
time |
Waiting time, in milliseconds. Range is 100 to 1000. The default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Usage Guidelines
PRACK allows reliable exchanges of SIP provisional responses between SIP endpoints. When the retransmission value is set, retransmissions are sent with an exponential backoff of up to 4 seconds. That is, the retransmission interval for each packet increases exponentially until 4 seconds is reached.
Examples
The following example sets retransmission time to 500 milliseconds:
Router(config)# sip-ua
Router(config-sip-ua)# timers prack 500
Related Commands
timers refer
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits before retransmitting a Refer request, use the timers refer command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers refer time
no timers refer
Syntax Description
time |
Waiting time, in milliseconds. Range is from 100 to 1000. Default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Usage Guidelines
A SIP Refer request is sent by the originating gateway to the receiving gateway and initiates call forward and call transfer capabilities.
Examples
The following example sets retransmission time to 500 milliseconds:
Router(config)# sip-ua
Router(config-sip-ua)# timers refer 500
Related Commands
|
|
|
|---|---|
show sip-ua statistics |
Displays response, traffic, timer, and retry statistics. |
show sip-ua timers |
Displays the current settings for SIP UA timers. |
timers register
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits before sending register requests, use the timers register command in SIP user-agent configuration mode. To reset this value to the default, use the no form of this command.
timers register milliseconds
no timers register
Syntax Description
milliseconds |
Waiting time, in milliseconds. Range is from 100 to 1000. Default is 500. |
Defaults
500 milliseconds
Command Modes
SIP user-agent configuration
Command History
|
|
|
|---|---|
12.2(15)ZJ |
This command was introduced. |
12.3(4)T |
This command was integrated into Cisco IOS Release 12.3(4)T. |
12.4(22)T |
Support for IPv6 was added. |
Examples
The following example sends register requests every 500 milliseconds:
sip-ua
retry invite 9
retry register 9
timers register 500
Related Commands
|
|
|
|---|---|
retry register |
Sets the total number of SIP registers to send. |
timers rel1xx
To set how long the Session Initiation Protocol (SIP) user agent (UA) waits before retransmitting a reliable1xx response, use the timers rel1xx command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers rel1xx time
no timers rel1xx
Syntax Description
time |
Waiting time, in milliseconds. Range is 100 to 1000. The default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Examples
The following example sets retransmission time to 400 milliseconds:
Router(config)# sip-ua
Router(config-sip-ua)# timers rel1xx 400
Related Commands
timers trying
To set how long the Session Initiation Protocol (SIP) user agent (UA) wait s for a 100 response to a SIP INVITE request, use the timers trying command in SIP UA configuration mode. To reset to the default, use the no form of this command.
timers trying time
no timers trying
Syntax Description
time |
Waiting time, in milliseconds. Range is 100 to 1000. The default is 500. |
Command Default
500 milliseconds
Command Modes
SIP UA configuration
Command History
Usage Guidelines
If you used the previous more generic timers command to configure timers, your previous timer settings are maintained. The output of the show running-config command reflects both timers.
To reset this command to the default value, you can also use the default command.
Examples
The following example sets trying time to 500 milliseconds.
sip-ua
timers trying 500
Related Commands
|
|
|
|---|---|
sip-ua |
Enables the SIP UA configuration commands. |
timing clear-wait
To set the minimum amount of time between the inactive seizure signal and the call being cleared for a specified voice port, use the timing clear-wait command in voice-port configuration mode. To reset to the default, use the no form of this command.
timing clear-wait time
no timing clear-wait
Syntax Description
time |
Minimum time, in milliseconds, between an inactive seizure signal and the call being cleared. Cisco 3600 series range is from 200 to 2000. The default for both is 400. |
Command Default
400 milliseconds
Command Modes
Voice-port configuration
Command History
|
|
|
|---|---|
11.3(1)T |
This command was introduced on Cisco 2600 and Cisco 3600 series routers. |
Usage Guidelines
This command is supported on E&M ports only.
Examples
The following example sets the clear-wait duration on a voice port to 300 milliseconds:
voice-port 1/0/0
timing clear-wait 300
Feedback