-
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
clear backhaul-session-manager group stats
clear call application interface
clear controller call-counters
clear controller t1 call-counters
clear h323 gatekeeper endpoint
clear h323 gatekeeper statistics
clear sip-ua tcp tls connection
clear statistics dial-peer voice
ccs connect (controller)
To configure a common channel signaling (CCS) connection on an interface configured to support CCS frame forwarding, use the ccs connect command in controller configuration mode. To disable the CCS connection on the interface, use the no form of this command.
ccs connect {serial | atm} number [dlci | pvc vpi/vci | pvc name] [cidnumber]
no ccs connect {serial | atm} number [dlci | pvc vpi/vci | pvc name] [cidnumber]
Syntax Description
Command Default
No CCS connection is made.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure a CCS connection. If the CCS connection is over Frame Relay, specify a serial interface and the DLCI. If the CCS connection is over ATM, specify atm, the slot number, and the PVC.
If you have executed the ccs encap frf11 command, the cidnumber option allows you to specify any CID from 5 to 255. If you do not issue the ccs encap frf11 command, Cisco encapsulation is used, and any CID value other than 254 is ignored.
Note
CDP and keepalives are disabled by default on a D-channel interface.
Examples
To configure a Frame Relay CCS frame-forwarding connection on DLCI 100 by using the default CID of 254, enter the following command:
ccs connect serial 1 100or:
ccs connect serial 1 100 10To configure a CCS frame-forwarding connection over an ATM PVC, enter the following command:
ccs connect atm0 pvc 100/10or:
ccs connect atm0 pvc 10/100 21or:
ccs connect atm0 pvc mypvc_10 21To configure a Frame Relay CCS frame-forwarding connection on DLCI 100 using a CID of 110, enter the following command:
ccs connect serial 1 100 110Related Commands
ccs connect (interface)
To configure a common channel signaling (CCS) connection on an interface configured to support CCS frame forwarding, use the ccs connect command in interface configuration mode. To disable the CCS connection on the interface, use the no form of this command.
ccs connect {serial | atm} number [dlci | pvc vpi/vci | pvc name] [cid-number]
no ccs connect {serial | atm} number [dlci | pvc vpi/vci | pvc name] [cid-number]
Syntax Description
Command Default
No CCS connection is made.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to configure a CCS connection. If the CCS connection is over Frame Relay, specify a serial interface and the DLCI. If the CCS connection is over ATM, specify atm, the interface number (0), and the PVC. If you have executed the ccs encap frf11 command, the cid-number option allows you to specify any CID from 5 to 255. If you do not issue the ccs encap frf11 command, Cisco encapsulation is used, and any CID value other than 254 is ignored.
Note
Examples
To configure a Frame Relay CCS frame-forwarding connection on DLCI 100 by using the default CID of 254, enter the following command:
ccs connect serial 1 100or
ccs connect serial 1 100 10To configure a CCS frame-forwarding connection over an ATM PVC, enter the following command:
ccs connect atm0 pvc 100/10or
ccs connect atm0 pvc 10/100 21or
ccs connect atm0 pvc mypvc_10 21To configure a Frame Relay CCS frame-forwarding connection on DLCI 100 using a CID of 110, enter the following command:
ccs connect serial 1 100 110Related Commands
ccs encap frf11
To configure the common channel signaling (CCS) packet encapsulation format for FRF.11, use the ccs encap frf11 command in interface configuration mode. To disable CCS encapsulation for FRF11, use the no form of this command.
ccs encap frf11
no ccs encap frf11
Syntax Description
This command has no keywords or arguments.
Command Default
By default, the format is a Cisco packet format, using a channel ID (CID) of 254
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows the specification of the standard Annex-C format. Use this command to define the packet format for the CCS packet; it places the FRF.11 Annex-C (Data Transfer Syntax) standard header on the CCS packets only.
Once the ccs encap frf11 command is executed, you can use the ccs connect command to specify a CID other than 254.
Examples
The following example shows how to configure a serial interface for Frame Relay:
interface Serial1:15ccs encap frf11ccs connect Serial0 990 100Related Commands
ces-clock
To configure the clock for the CES interface, use the ces-clock command in controller configuration mode. To disable the ces clock, use the no form of this command.
ces-clock {adaptive | srts | synchronous}
no ces-clock {adaptive | srts | synchronous}
Syntax Description
Command Default
The default setting is synchronous
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is used on Cisco 3600 series routers that have OC-3/STM-1 ATM CES network modules.
Examples
The following example configures the CES clock mode for synchronous residual time stamp:
ces-clock srtsRelated Commands
cgma-agent
To enable the Cisco Gateway Management Agent (CGMA) on the Cisco IOS gateway, use the cgma-agent command in global configuration mode. To disable the CGMA, use the no form of this command.
cgma-agent [tcp-port number] | [time-period seconds]
no cgma-agent
Syntax Description
Command Default
Default number value is 5000.
Default seconds value is 45.Command History
Usage Guidelines
Use this command to enable the CGMA on the Cisco IOS gateway. The CGMA communicates with the third-party management system to provide real-time information for gateway management, including the following:
•
•
•
Examples
The following example shows that the CGMA is enabled on TCP port 5300 and that the CGMA times out after 300 seconds and closes its connection to the third-party management system because of inactivity in the link:
Router(config)# cgma-agent tcp-port 5300 time-period 300Router# show running-configBuilding configuration...Current configuration : 1797 bytes!version 12.2service configno service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname gw1!...resource-pool disable!ip subnet-zerono ip domain-lookup!no ip dhcp-client network-discoveryisdn switch-type primary-ni!!!!!!cgma-agent tcp-port 5300 time-period 300fax interface-type modemmta receive maximum-recipients 2!!controller T1 0framing esflinecode b8zspri-group timeslots 1-24!!interface Ethernet0ip address 209.165.200.225 255.255.255.0!interface Serial0:23no ip addressisdn switch-type primary-niisdn protocol-emulate networkisdn incoming-voice modemisdn T310 10000no cdp enable!voice-port 0:D!dial-peer voice 1213 voipdestination-pattern 12135551000session target ipv4:209.165.200.229!dial-peer voice 1415 potsdestination-pattern 14155551000direct-inward-dialport 0:D!dial-peer voice 12136 voipdestination-pattern 12136661000session target ipv4:209.165.200.229!dial-peer voice 14156 potsincoming called-number .direct-inward-dial!gateway!endchannel-group
To configure serial WAN on a T1 or E1 interface, use the channel-group command in controller configuration mode. To clear a channel group, use the no form of this command.
Cisco 2600 Series
channel-group channel-group-number timeslots range [speed kbps] [aim aim-slot-number]
no channel-group channel-group-number
Cisco 2611 (Cisco Signaling Link Terminal [SLT])
channel-group channel-number
no channel-group channel-number
Cisco 2600XM Series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745
channel-group channel-group-number {timeslots range [speed {56 | 64}] | unframed} [aim aim-slot-number]
no channel-group [channel-group-number timeslots range]
Cisco AS5350 and Cisco AS5400 Series
channel-group channel-group-number
no channel-group channel-group-number
Cisco MC3810
channel-group channel-number timeslots range [speed kbps}]
no channel-group [channel-number timeslots range]
Syntax Description
Command Default
The T1/E1 line is connected to the Motorola MPC-860x processor serial communication controller (SCC) or network module with two voice or WAN interface card (VIC or WIC) slots and 0/1/2 FastEthernet ports DSCC4 by default on Cisco 2600 series, Cisco 2600XM, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745 routers.
There is no default behavior or values on the Cisco SLT (Cisco 2611).
The serial interface object encapsulation is set to HDLC on a network access server (NAS) (Cisco AS5350 and Cisco AS5400 series routers).
The default line speed is 56 kbps when a T1 controller is configured on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.
The default line speed is 64 kbps when an E1 controller is configured on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to direct High-Level Data Link Control (HDLC) traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card. A channel group is created using Advanced Integration Module (AIM) HDLC resources when a channel-group command with the aim keyword is parsed during system initialization or when the command is entered during configuration. You must specify the aim keyword under a T1/E1 controller port to direct HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745.
Note
If previous channel-group commands are configured with the aim keyword, subsequent channel-group commands without the aim keyword are rejected. Similarly, if a regular channel-group command is followed by another channel-group command with the aim keyword implemented, the second command is rejected on the Cisco 2600 and Cisco 2600XM.
A channel group using AIM HDLC resources is deleted only when a no channel-group command is entered.
By default, the channel-group command on a NAS sets the serial interface object encapsulation to HDLC. You must override the default by entering the encapsulation ss7 command for that serial interface object. Once you override the default, encapsulation cannot be changed again for that object. The SS7 encapsulation option is new to the Integrated Signaling Link Terminal feature and is available only for interface serial objects created by the channel-group command. The Integrated Signaling Link Terminal feature added SLT functionality on Cisco AS5350 and Cisco AS5400 platforms.
A digital SS7 link can be deleted by entering the no channel-group channel-group-number command on the associated T1/E1 controller. The link must first be stopped using the no shutdown command. It is not necessary to remove the channel ID association first.
Use the channel-group command in configurations where the router or access server must communicate with a T1 or E1 fractional data line. The channel group number may be arbitrarily assigned and must be unique for the controller. The time slot range must match the time slots assigned to the channel group. The service provider defines the time slots that comprise a channel group.
Note
The channel group number can be 0 or 1 on the Cisco SLT (Cisco 2611).
The channel-group command also applies to Voice over Frame Relay, Voice over ATM, and Voice over HDLC on the Cisco MC3810.
Examples
The following example shows basic configuration directing HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card, starting in global configuration mode:
Router(config)# controller e1 1/0Router(config-controller)# clock source internalRouter(config-controller)# channel-group 0 timeslots 1-31 aim 0The following example explicitly sets the encapsulation type to PPP to override the HDLC default:
Router# configure terminalRouter(config)# controller t1 6/0Router(config-controller)# channel-group 2 timeslots 3 aim 0Router(config-controller)# exitRouter(config)# interface serial 6/0:2Router(config-if)# encapsulation pppRouter(config-if)# ip address 12.0.0.1 255.0.0.0Router(config-if)# no shutdownRouter(config-if)# endThe following example shows how to explicitly set the encapsulation type to SS7 to override the HDLC default using the Integrated Signaling Link Terminal feature. This example uses an 8PRI DFC card inserted into slot 7, and DS0-timeslot 3 on trunk 5 of that card is used as an SS7 link:
Router# configure terminalRouter(config)# controller t1 7/5Router(config-controller)# channel-group 2 timeslots 3Router(config-controller)# exitRouter(config)# interface serial 7/5:2Router(config-if)# encapsulation ss7Router(config-if)# channel-id 0Router(config-if)# no shutdownRouter(config-if)# endThe following example defines three channel groups. Channel-group 0 consists of a single time slot, channel-group 8 consists of seven time slots and runs at a speed of 64 kbps per time slot, and channel-group 12 consists of two time slots.
Router(config-controller)# channel-group 0 timeslots 1Router(config-controller)# channel-group 8 timeslots 5,7,12-15,20 speed 64Router(config-controller)# channel-group 12 timeslots 2The following example configures a channel group on controller T1 0 on a Cisco MC3810:
Router(config)# controller T1 0Router(config-controller)# channel-group 10 timeslots 10-64The following example configures a channel group on controller E1 1 and specifies that all time slots are used for data:
controller e1 1 channel-group 1 unframed
Note
Related Commands
channel-id
To assign a session channel ID to an SS7 serial link or assign an SS7 link to an SS7 session set on a Cisco AS5350 or Cisco AS5400, use the channel-id command in interface configuration mode. To disable a session channel ID link, use the no form of this command.
channel-id channel-id [session-set session-set-id]
no channel-id
Syntax Description
Command Default
No default behavior or values
Command Modes
Interface configuration
Command History
12.2(11)T
This command was introduced on the Cisco AS5350 and Cisco AS5400.
12.2(15)T
The session-set session-set-id keyword and argument were added.
Usage Guidelines
The channel-id command is visible only if the object's encapsulation type is changed to SS7.
Before an SS7 serial link can be enabled using the no shutdown command, you must enter the channel-id command in interface configuration mode to assign a session channel ID to the SS7 serial link. This ID is unique to the Cisco AS5350 and Cisco AS5400, and the command is visible only for provisioned objects whose encapsulation type is the new SS7 value.
The channel identifier is reserved when you explicitly assign an ID using the channel-id command for the associated serial interface object. This fails if the selected channel identifier is currently assigned to another link or if all channel identifiers are already assigned.
A channel identifier is released when the no channel-id command is entered. The link must first be shut down to do this. If the no channel-id command is used with the Mulitple OPC Support for the Cisco Signaling Link Terminal feature, the associated SS7 link has no channel ID. In this state the link is not fully configured and is incapable of supporting signaling traffic.
If the session-set keyword is omitted, the command is applied to SS7 session set 0, which is the default. Reissuing the session-set keyword with a different SS7 session ID is sufficient to remove the associated SS7 link from its existing SS7 session set and add it to the new one.
Examples
The following example shows a unique session channel ID zero being assigned to the Cisco AS5350 or Cisco AS5400:
Router(config-if)# channel-id 0The following example assigns an SS7 link to an SS7 session set on a Cisco AS5350 or Cisco AS5400:
Router(config-if)# channel-id 0 session-set 1Related Commands
clear backhaul-session-manager group stats
To reset the statistics or traffic counters for a specified session group, use the clear backhaul-session-manager group stats command in privileged EXEC mode.
clear backhaul-session-manager group stats {all | name group-name}
Syntax Description
Command Default
The statistical information accumulates
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A session is the connection between a client and a server, and a session group is a collection of sessions in a group to implement switchover in case of a session failure. This command clears all statistics that pertain to the backhaul session manager group.
Examples
The following example clears all statistics for all available session groups:
Router(config)# clear backhaul-session-manager group stats allRelated Commands
show backhaul-session-manager group
Displays status, statistics, or configuration of a specified group or all session groups.
clear call application interface
To clear application interface statistics and event logs, use the clear call application interface command in privileged EXEC mode.
clear call application interface [[{aaa | asr | flash | http | ram | rtsp | smtp | tftp | tts} [server server]] [event-log | stats]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command resets statistic counters to zero and clears event logs for application interfaces. If you do not use any keywords or arguments, this command clears statistics and event logs for all application interfaces.
Examples
The following example clears statistics and event logs for application interfaces:
Router# clear call application interfaceRelated Commands
clear call application stats
To clear application-level statistics in history and subtract the statistics from the gateway-level statistics, use the clear call application stats command in privileged EXEC mode.
clear call application [app-tag application-name] stats
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command resets application-level counters in history to zero and subtracts the counters from the gateway-level history. If you do not specify an application name, this command clears statistics for all applications at the application level and gateway level.
Note
Examples
The following example clears statistics for the application named sample_app:
Router# clear call application stats sample_appRelated Commands
clear call fallback cache
To clear the cache of the current Calculated Planning Impairment Factor (ICPIF) estimates for all IP addresses or a specific IP address, use the clear call fallback cache command in EXEC mode.
clear call fallback cache [ip-address]
Syntax Description
ip-address
(Optional) Specifies the target IP address. If no IP address is specified, all IP addresses are cleared.
Command Default
If no IP address is specified, all IP addresses are cleared.
Command Modes
EXEC
Command History
Usage Guidelines
If no IP address is specified, this command clears the cache of all ICPIF estimates for all IP addresses.
Examples
The following example clears the cache of the ICPIF estimate for IP address 10.0.0.0:
Router# clear call fallback cache 10.0.0.0Related Commands
show call fallback cache
Displays the current ICPIF estimates for all IP addresses in the call fallback cache.
clear call fallback stats
To clear the call fallback statistics, use the clear call fallback stats command in EXEC mode.
clear call fallback stats
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example clears the call fallback statistics:
Router# clear call fallback statsRelated Commands
clear call threshold
To clear enabled call threshold statistics, use the clear call threshold command in privileged EXEC mode.
clear call threshold {stats | total-calls [value] | interface int-name int-calls [value]}
Syntax Description
Command Default
The default setting of 0 for total-calls and int-calls resets all threshold statistics immediately.
stats is the default keyword.Command Modes
Privileged EXEC
Command History
Examples
The following example resets all call threshold statistics:
clear call threshold statsThe following example also resets the counter for all call volume in the gateway:
clear call threshold total-callsThe following example resets the counter when the call volume on Ethernet interface 0/1 reaches 5000 calls:
clear call threshold interface ethernet 0/1 int-calls 5000Related Commands
clear call treatment stats
To clear call treatment statistics, use the clear call treatment stats command in privileged EXEC mode.
clear call treatment stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the call treatment statistics:
clear call treatment statsRelated Commands
clear call voice
To clear one or more voice calls detected as inactive because there is no RTP or RTCP activity, use the clear call voice command in EXEC or privileged EXEC mode.
clear call voice causecode identifier{id identifier | media-inactive | calling-number number | called-number number}
Syntax Description
Command Default
This command is disabled, and no calls are cleared.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
This command can be used to clear all voice calls detected as media inactive or it can be used to clear individual voice calls. There is no no form of this command.
Examples
The following example clears inactive voice calls with the cause code ID of 112B:
Router# clear call voice causecode 1 id 112BRelated Commands
show call active voice
Displays active voice calls, based on specified parameters.
clear call-router routes
To remove the dynamic routes cached in the border element (BE), enter the clear call-router routes command in privileged EXEC mode.
clear call-router routes
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to remove dynamic routes cached in the BE:
Router# clear call-router routesRelated Commands
call-router
Enables the Annex G BE configuration commands.
show call history
Displays the fax history table for a fax transmission.
clear controller call-counters
To clear the system DS0 high water marks (HWM) and all individual controller statistics, use the clear controller call-counters command in privileged EXEC mode.
clear controller call-counters {system-hwm | all}
Syntax Description
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear controller call-counters all command clears the system DS0 HWMs and all individual controller statistics, including Total Calls and Total Duration. The clear controller call-counters system-hwm command clears the system DS0 HWMs and leaves all other call-counter statistics untouched.
Refer to the comments below for the meaning of call counters displayed before and after executing clear controller call-counters and clear controller t1 call-counters related commands.
•
•
•
This value is reset to the current and active DS0s when call counters are cleared. For example, initially the HWM is 0. When a new call comes in, the HWM is 1. When the next call comes in, the HWM is 2.
If 20 calls come in, the HWM is 20 and the active DS0s are 20. If 5 calls get disconnected, the DS0 active is 15, but the HWM is 20. When a clear controller command is input for the specified controller, the HWM is reset to 15, which is the current and active DS0s also. If 10 calls get disconnected, the Active DS0s is set to 5 and the HWM remains at 15 until another clear controller command is input. If Active DS0s exceed 15, then the HWM is updated.
•
Examples
The following sample output shows what happens after the HWMs are cleared:
Router# clear controller call-counters system-hwm!Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:08:5123 pri 1 00:09:21T1 1/3/0:8:DS0's Active: 1DS0's Active High Water Mark: 1TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:01:3923 pri 0 00:00:00System's DS0's Active High Water Mark: 3In the example above, the system HWM is reset to the total number of active calls in the system, which is 3. The number was 4. When a call goes down, HWM values are untouched. Only the DS0 Active value changes. Above, there is only one call on 1/3/0:3. Observe the HWM for individual controllers. Total number of active calls is 1.
The following is sample output when the clear controller call-counters system-hwm command is used:
Router# clear controller call-counters system-hwm!Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 1DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:12:1623 pri 1 00:10:20T1 1/3/0:8:DS0's Active: 0DS0's Active High Water Mark: 1TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:02:5023 pri 0 00:00:00System's DS0's Active High Water Mark: 1In the previous example, only the system HWM is reset to active. For controllers 1/3/0:3 and 1/3/0:8, the HWMs are untouched.
The following is sample output when the all keyword is used, clearing at the system level:
Router# clear controller call-counters all!Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 0DS0's Active High Water Mark: 0TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:00:0023 pri 0 00:00:00T1 1/3/0:8:DS0's Active: 0DS0's Active High Water Mark: 0TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:00:0023 pri 0 00:00:00System's DS0's Active High Water Mark: 0In the previous example, clearing at the system level using the clear controller call-counters command clears all DS0 controllers in the system and also clears the system HWMs.
The following is sample output showing four active calls:
Related Commands
clear controller t1 call-counters
To clear the system DS0 high water marks (HWM) and all individual controller statistics, use the clear controller t1 command in privileged EXEC mode.
clear controller t1 [slot] call-counters timeslots | firmware-status
slot
(Optional) Clears an individual T1 controller.
call-counters timeslots
Clears the call counters in the specified T1 time slots.
firmware-status
Clears the Neat crash history.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Refer to the comments below for the meaning of call counters displayed before and after executing clear controller t1 call-counters related commands.
•
If a timeslot or timeslot range is specified, only the counters for those channels are cleared. The TotalCalls field shows the time slots that have calls connected since the last clear was done and does not show the number of active calls in the controller. The TotalDuration field shows the same information as the TotalCalls field.
•
•
This value is reset to the current and active DS0s when the clear controller t1 1/3/0 call-counters command is entered. For example, initially the HWM is 0. When a new call comes in, the HWM is 1. When the next call comes in, the HWM is 2.
If 20 calls come in, the HWM is 20 and the active DS0s are 20. If 5 calls get disconnected, the DS0 active is 15, but the HWM is 20. When a clear controller command is input for the specified controller, the HWM is reset to 15, which is the current and active DS0s also. If 10 calls get disconnected, the Active DS0s is set to 5 and the HWM remains at 15 until another clear controller command is input. If Active DS0s exceed 15, then the HWM is updated.
•
Examples
The following is sample output that shows two controllers numbered 1/3/0:3 and 1/3/0:8. Note the differences in the output shown by the show controllers t1 call-counters command and how the clear controller t1 call-counters command affects the output:
Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 0DS0's Active High Water Mark: 0TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:00:0023 pri 0 00:00:00T1 1/3/0:8:DS0's Active: 0DS0's Active High Water Mark: 0TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:00:0023 pri 0 00:00:00System's DS0's Active High Water Mark: 0
Note
The following is sample output that shows that four calls have been initiated on the 1/5/12, 1/5/13, 1/5/14, and 1/5/15 controllers:
Router# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00tty 1/5/12 Router Async interface 00:01:05 PPP: 55.61.1.1tty 1/5/13 Router Async interface 00:00:48 PPP: 55.62.1.1tty 1/5/14 Router Async interface 00:00:33 PPP: 55.54.1.1tty 1/5/15 Router Async interface 00:00:19 PPP: 55.52.1.1Interface User Mode Idle Peer AddressRouter# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:01:5823 pri 1 00:02:27T1 1/3/0:8:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:02:1423 pri 1 00:02:46System's DS0's Active High Water Mark: 4In the example above, if a clear controller command is entered for a controller that has active calls, which have been connected during the last 30 minutes, the TotalCalls and TotalDuration fields are reset to zero.
The following is sample output that shows controller 1/3/0:3, with time slots 22 and 23 connected and active. When the clear controller t1 1/3/0:3 call-counters command is entered, the corresponding fields are set to zero.
Router# clear controller t1 1/3/0:3 call-counters!Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:29:1423 pri 1 00:29:47Router# clear controller t1 1/3/0:3 call-countersRouter# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:00:10 <<<<<<23 pri 0 00:00:10 <<<<<<The following is sample output when a call is cleared on 1/5/12:
Router# clear line 1/5/12[confirm][OK]!Router# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00tty 1/5/13 Router Async interface 00:03:04 PPP: 55.62.1.1tty 1/5/14 Router Async interface 00:02:49 PPP: 55.54.1.1tty 1/5/15 Router Async interface 00:02:35 PPP: 55.52.1.1Interface User Mode Idle Peer AddressRouter# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:03:4423 pri 1 00:04:14T1 1/3/0:8:DS0's Active: 1DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:04:0023 pri 1 00:03:34System's DS0's Active High Water Mark: 4After a call gets disconnected, only the DS0 Active field changes to reflect the current active call on the controller. In the above example, 1/3/0:8 DS0 Active is changed to 1.
The following is sample output that shows call counters are cleared for an individual controller on 1/3/0:8:
Router# clear controller t1 1/3/0:8 call-counters!Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:07:4623 pri 1 00:08:15T1 1/3/0:8:DS0's Active: 1DS0's Active High Water Mark: 1TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:00:3523 pri 0 00:00:00System's DS0's Active High Water Mark: 4In the previous example, after clearing call counters for controller 1/3/0:8, TotalCalls and TotalDuration reset. In addition the DS0 HWM is also cleared to the number of active DS0s. Whenever the DS0 HWM is cleared, it does not reset to zero, but rather it is set to Active DS0s. For 1/3/0:8, the HWM is 1 after clearing because DS0 Active is 1 (1 active call). TotalDuration is 35 seconds for time slot 22, and TotalCall is 0 because they got reset when the clear controller call-counters command was entered. Total calls on this time slot is incremented when a new call comes in on this time slot.
The following is sample output when controller 1/5/15 is cleared:
Router# clear line 1/5/15[confirm][OK]Router# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 0DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:12:4023 pri 1 00:10:20T1 1/3/0:8:DS0's Active: 0DS0's Active High Water Mark: 1TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 0 00:02:5023 pri 0 00:00:00System's DS0's Active High Water Mark: 1The following is sample output showing four active calls:
Router# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00tty 1/5/16 Router Async interface 00:01:01 PPP: 55.1.1.1tty 1/5/17 Router Async interface 00:00:47 PPP: 55.2.1.1tty 1/5/18 Router Async interface 00:00:28 PPP: 55.3.1.1tty 1/5/19 Router Async interface 00:00:14 PPP: 55.4.1.1Interface User Mode Idle Peer AddressRouter# show controllers t1 call-countersT1 1/3/0:3:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:00:5723 pri 1 00:01:30T1 1/3/0:8:DS0's Active: 2DS0's Active High Water Mark: 2TimeSlot Type TotalCalls TotalDuration1 pri 0 00:00:002 pri 0 00:00:003 pri 0 00:00:004 pri 0 00:00:005 pri 0 00:00:006 pri 0 00:00:007 pri 0 00:00:008 pri 0 00:00:009 pri 0 00:00:0010 pri 0 00:00:0011 pri 0 00:00:0012 pri 0 00:00:0013 pri 0 00:00:0014 pri 0 00:00:0015 pri 0 00:00:0016 pri 0 00:00:0017 pri 0 00:00:0018 pri 0 00:00:0019 pri 0 00:00:0020 pri 0 00:00:0021 pri 0 00:00:0022 pri 1 00:01:1223 pri 1 00:01:45System's DS0's Active High Water Mark: 4Related Commands
clear csm-statistics modem
To clear the call switching module (CSM) statistics for a modem or group of modems, use the clear csm-statistics modem command in privileged EXEC mode.
clear csm-statistics modem [slot/port | modem-group-number]
Syntax Description
slot/port
(Optional) Identifies the location (and thereby the identity) of a specific modem.
modem-group-number
(Optional) Designates a defined modem group.
Command Default
No default behaviors or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear csm-statistics modem command to clear CSM statistics for a particular modem or group of modems. If the slot/port argument is specified, the CSM call statistics for calls using the identified modem is cleared. If a modem group number is specified, then the CSM call statistics for calls using the modems associated with that group are cleared. If no argument is specified, all CSM call statistics for all modems are cleared.
Examples
The following example clears CSM call statistics for calls coming in on modems associated with modem group 2:
Router# clear csm-statistics modem 2Related Commands
clear csm-statistics voice
Clears the CSM statistics for a particular or for all DSP channels.
clear csm-statistics voice
To clear the call switching module (CSM) statistics for a particular or for all digital signal processor (DSP) channels, use the clear csm-statistics voice command in privileged EXEC mode.
clear csm-statistics voice [slot/dspm/dsp/dsp-channel]
Syntax Description
Command Default
No default behaviors or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear csm-statistics voice command to clear CSM statistics for a particular DSP channel. If the slot/dspm/dsp/dsp-channel argument is specified, the CSM call statistics for calls using the identified DSP channel are cleared. If no argument is specified, all CSM call statistics for all DSP channels are cleared.
Examples
The following example clears CSM call statistics for calls coming in on all DSP channels:
Router# clear csm-statistics voiceRelated Commands
clear csm-statistics modem
Clears the CSM statistics for a modem or group of modems.
clear h323 gatekeeper call
To force the disconnection of a specific call or of all calls active on a particular gatekeeper, use the clear h323 gatekeeper call command in privileged EXEC mode.
clear h323 gatekeeper call {all | local-callID local-callID}
Syntax Description
Command Default
No default behaviors or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you want to force a particular call to be disconnected (as opposed to all active calls on the gatekeeper), use the CallID number to identify that specific call. You can find the local CallID number for a specific call by using the show gatekeeper calls command; the ID number is displayed in the LocalCallID column.
Examples
The following example shows that an active call on the gatekeeper is being forced to disconnect. The local ID number of the active call is 12-3339.
Router# clear h323 gatekeeper call local-callID 12-3339The following example shows that all active calls on the gatekeeper are being forced to disconnect:
Router# clear h323 gatekeeper call allThe following sample output from the show gatekeeper calls command displays information about a specific active call having a call ID of 12-3339:
Router# show gatekeeper callsTotal number of active calls =1Gatekeeper Call Info====================LocalCallID Age (secs) BW12-3339 94 768 (Kbps)Endpt(s): Alias E.164Addr CallSignalAddr Port RASSignalAddr Portsrc EP: epA 10.0.0.11 1720 10.0.0.11 1700dst EP: epB2zoneB.comsrc PX: pxA 10.0.0.1 1720 10.0.0.11 24999dst PX: pxB 172.21.139.90 1720 172.21.139.90 24999Related Commands
show gatekeeper calls
Displays the status of each ongoing call of which a gatekeeper is aware.
clear h323 gatekeeper endpoint
To unregister endpoints, use the clear h323 gatekeeper endpoint command in privileged EXEC mode.
clear h323 gatekeeper endpoint {alias e164 digits | alias h323id name | all | id number | ipaddr address [port]}
Syntax Description
Command Default
Default for the port argument is 1720.
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco 3660 and Cisco MC3810.
Usage Guidelines
Using this command forces the gatekeeper to send an unregistration request (URQ) message to the specified endpoint or all endpoints and removes the endpoint from the gatekeeper registration database.
For gatekeeper cluster configurations, this command must be entered on the gatekeeper where the endpoint is registered. Use the show gatekeeper endpoints command to locate the endpoint in a gatekeeper cluster.
Note
Examples
The following example shows how to unregister all endpoints:
GK# clear h323 gatekeeper endpoint allGK# show gatekeeper endpointsGATEKEEPER ENDPOINT REGISTRATION================================CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags--------------- ----- --------------- ----- --------- ---- -----Total number of active registrations = 0Related Commands
clear h323 gatekeeper statistics
To clear statistics about gatekeeper performance, use the clear h323 gatekeeper statistics command in privileged EXEC mode.
clear h323 gatekeeper statistics
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
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 the Cisco AS5850.
Usage Guidelines
This command resets the gatekeeper performance counters to zero and records the time at which the last clear was performed.
Examples
The following example shows output for the show gatekeeper performance statistics command. See the show gatekeeper performance statistics command for more information.
clear h323 gatekeeper statisticsshow gatekeeper performance statisticsRAS inbound message counters:Originating ARQ: 0 Terminating ARQ: 0 LRQ: 0RAS outbound message counters:ACF: 2 ARJ: 0 LCF: 2 LRJ: 0ARJ due to overload: 0LRJ due to overload: 0Load balancing events: 0Real endpoints: 2Related Commands
show gatekeeper performance statistics
Displays information about the number of calls accepted and rejected by the gatekeeper.
clear h323 gateway
To clear the H.323 gateway counters, use the clear h323 gateway command in privileged EXEC mode.
clear h323 gateway [cause-code stats | h225 | ras]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(4)T
This command was introduced on all Cisco H.323 platforms except for the Cisco AS5300, Cisco AS5350, and Cisco AS5400.
Usage Guidelines
To clear all H.323 counters, use the clear h323 gateway command without any of the optional keywords. After you have used the clear h323 gateway command, the respective counters are set to zero.
Examples
In the following example from a Cisco 3640 router, the clear h323 gateway command is used without keywords to clear all H.323 counters:
Router# clear h323 gatewayAll H.323 stats cleared at 01:54:38In the following example from a Cisco 3640 router, the clear h323 gateway command is used with the cause-code stats keyword to clear the disconnect cause-code stats counters:
Router# clear h323 gateway cause-code statsCause code stats cleared at 01:54:08In the following example from a Cisco 3640 router, the clear h323 gateway command is used with the h225 keyword to clear the H.225 counters:
Router# show h323 gateway h225H.225 stats cleared at 01:53:18In the following example from a Cisco 3640 router, the clear h323 gateway command is used with the ras keyword to clear the RAS counters:
Router# clear h323 gateway rasRAS stats cleared at 01:53:25Related Commands
clear interface cable-modem
To reset the controller for a specified cable modem daughter card, use the clear interface cable-modem command in privileged EXEC mode. This command does not have a no version.
clear interface cable-modem
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how the clear interface cable-modem command clears the interface on the selected slot and port:
Router# clear interface cable-modem*May 17 16:36:57.344: %CABLE_MODEM_HWIC-6-RESET: Interface Cable-Modem0/2/0 has been reset: clear command *May 17 16:37:05.348: %LINK-3-UPDOWN: Interface Cable-Modem0/2/0, changed state to down *May 17 16:37:06.348: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cable-Modem0/2/0, changed state to down *May 17 16:37:19.740: %LINK-3-UPDOWN: Interface Cable-Modem0/2/0, changed state to up *May 17 16:37:27.996: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cable-Modem0/2/0, changed state to upRelated Commands
show interfaces
Displays statistics for all interfaces configured.
show interfaces cable-modem
Displays statistics for all interfaces configured on the port.
clear ip sctp statistics
Note
Cisco IOS IP Application Services Command Reference. See the following URL for the current location: http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124tcr/tiap_r/index.htm
Note
To clear statistics counts for Stream Control Transmission Protocol (SCTP) activity, use the clear ip sctp statistics command in privileged EXEC mode.
clear ip sctp statistics
Syntax Description
This command has no arguments or keywords.
Command Default
This command has no default value. If this command is not entered, statistics counts for SCTP activity continue to be logged.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command clears both individual and overall statistics.
Examples
The following command shows how to empty the buffer that holds SCTP statistics. No output is generated from this command.
Router# clear ip sctp statisticsRelated Commands
clear mgcp src-stats
To clear the statistics gathered for Media Gateway Control Protocol (MGCP) System Resource Check (SRC) Call Admission Control (CAC) on an MGCP gateway, use the clear mgcp src-stats command in privileged EXEC mode.
clear mgcp src-stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear mgcp src-stats command to clear the MGCP gateway buffer that holds SRC CAC statistics gathered during the most recent inspection interval.
Examples
The following example clears MGCP VoIP SRC CAC statistics:
Router# clear mgcp src-statsRelated Commands
show mgcp statistics
Displays MGCP statistics regarding received and transmitted network messages.
clear mgcp statistics
To reset the Media Gateway Control Protocol (MGCP) statistical counters, use the clear mgcp statistics command in privileged EXEC mode.
clear mgcp statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
None
Examples
The following is an example of how to enter the command:
Router# clear mgcp statisticsRelated Commands
mgcp
Starts the MGCP daemon.
show mgcp statistics
Displays statistics for received and transmitted packets.
clear mrcp client statistics
To clear all Media Resource Control Protocol (MRCP) statistics, use the clear mrcp client statistics command in privileged EXEC mode.
clear mrcp client statistics {all | hostname {hostname | ip-address}}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 3640, Cisco 3660, Cisco AS5300, Cisco AS5350, and Cisco AS5400.
Usage Guidelines
This command resets all MRCP session statistics to 0. Use the show mrcp client statistics hostname command to display the current statistics.
Examples
The following example resets the statistics for the host called "asr_server":
Router# clear mrcp client statistics hostname asr_serverRelated Commands
show mrcp client statistics hostname
Displays cumulative information about MRCP sessions.
clear rlm group
To clear all time stamps to zero, use the clear rlm group link command in privileged EXEC mode.
clear rlm group group-number link
Syntax Description
group-number
Redundant Link Manager (RLM) group number. Range is from 0 to 255. There is no default value.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the time stamps on RLM group 1:
Router# clear rlm group 1 link!02:48:17: rlm 1: [State_Up, rx ACTIVE_LINK_BROKEN] over link [10.1.1.1(Loopback1), 10.1.4.1]02:48:17: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] requests activation02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is deactivated02:48:17: rlm 1: [State_Recover, rx LINK_BROKEN] over link [10.1.1.2(Loopback2), 10.1.4.2]02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] = socket[10.1.1.1, 10.1.4.1]02:48:17: rlm 1: [State_Recover, rx USER_SOCKET_OPENED] over link [10.1.1.1(Loopback1), 10.1.4.1] for user RLM_MGR02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is opened02:48:17: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] = socket[10.1.1.2, 10.1.4.2]02:48:17: rlm 1: [State_Recover, rx USER_SOCKET_OPENED] over link [10.1.1.2(Loopback2), 10.1.4.2] for user RLM_MGR02:48:17: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] is opened02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.5.1] = socket[10.1.1.1, 10.1.5.1]02:48:17: rlm 1: [State_Recover, rx USER_SOCKET_OPENED] over link [10.1.1.1(Loopback1), 10.1.5.1] for user RLM_MGR02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.5.1] is opened02:48:17: rlm 1: link [10.1.1.2(Loopback2), 10.1.5.2] = socket[10.1.1.2, 10.1.5.2]02:48:17: rlm 1: [State_Recover, rx USER_SOCKET_OPENED] over link [10.1.1.2(Loopback2), 10.1.5.2] for user RLM_MGR02:48:17: rlm 1: link [10.1.1.2(Loopback2), 10.1.5.2] is opened02:48:17: rlm 1: [State_Recover, rx LINK_OPENED] over link [10.1.1.1(Loopback1), 10.1.4.1]02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] requests activation02:48:17: rlm 1: [State_Recover, rx LINK_OPENED] over link [10.1.1.2(Loopback2), 10.1.4.2]02:48:17: rlm 1: [State_Recover, rx START_ACK] over link [10.1.1.1(Loopback1), 10.1.4.1]02:48:17: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is activatedRelated Commands
clear rpms-proc counters
To clear statistics counters for the number of leg 3 authentication, authorization, and accounting (AAA) preauthentication requests, successes, and rejects, use the clear rpms-proc counters command in privileged EXEC mode.
clear rpms-proc counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears statistics counters for leg 3 AAA preauthentication requests, successes, and rejects:
Router# clear rpms-proc countersRelated Commands
show rpms-proc counters
Displays statistics for the number of leg 3 AAA preauthentication requests, successes, and rejects.
clear rudpv0 statistics
To clear the counters that track RUDP statistics, enter the clear rudpv0 statistics command in privileged EXEC mode.
clear rudpv0 statistics
Syntax Description
This command has no arguments or keywords.
Command Default
The statistical information accumulates.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Examples
The following example shows how to clear RUDP statistics on a Cisco 2611 (Cisco SLT):
clear rudpv0 statisticsRelated Commands
clear rudpv1 statistics
To clear the counters that track Reliable User Datagram Protocol (RUDP) statistics, use the clear rudpv1 statistics command in privileged EXEC mode.
clear rudpv1 statistics
Syntax Description
This command has no arguments or keywords.
Command Default
The statistical information accumulates.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears all RUDP statistics for all available session groups:
Router# clear rudpv1 statisticsRelated Commands
debug rudpv1
Displays debugging information for RUDP.
show rudpv1
Displays RUDP information.
clear sctp statistics
Note
Cisco IOS IP Application Services Command Reference. See the following URL for the current location: http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124tcr/tiap_r/index.htmTo clear statistics counts for Stream Control Transmission Protocol (SCTP) activity, use the clear sctp statistics command in privileged EXEC mode.
clear sctp statistics
Syntax Description
This command has no arguments or keywords.
Command Default
This command has no default value. If this command is not entered, statistics counts for SCTP activity continue to be logged.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command clears both individual and overall statistics.
Examples
The following command shows how to empty the buffer that holds SCTP statistics. No output is generated from this command.
Router# clear sctp statisticsRelated Commands
clear sgcp statistics
To clear all Simple Gateway Control Protocol (SGCP) statistics, use the clear sgcp statistics command in privileged EXEC mode.
clear sgcp statistics
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
None
Examples
The following example shows all SGCP statistics being cleared:
Router# clear sgcp statisticsRelated Commands
clear sip-ua statistics
To reset the Session Initiation Protocol (SIP) user-agent (UA) statistical counters, use the clear sip-ua statistics command in privileged EXEC mode.
clear sip-ua statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear all SIP statistics counters that are displayed by the show sip-ua statistics command.
Examples
The following example shows all SIP-UA statistics being cleared:
Router# clear sip-ua statisticsRelated Commands
clear sip-ua tcp connection
To clear a session initiation protocol (SIP) TCP connection, use the clear sip-ua tcp connection command in privileged EXEC mode.
clear sip-ua tcp connection {id connection-id [target ipv4:address:port] | [id connection-id] target ipv4:address:port}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.3(8)T
This command was introduced.
12.4(6)T
This command was replaced by the clear sip-ua tcp tls connection command.
Usage Guidelines
Inappropriate usage of the clear sip-ua tcp connection command can lead to erroneous call behavior, inappropriate usage of connections, and failure of calls.
Examples
To cear the connection entry only at the upper transport layer, assign the target IP address and port:
Router# clear sip-ua tcp connection target ipv4:172.18.194.183:5060To clear the connection entry only at the lower TCP or User Datagram Protocol (UDP) layer, specify the connection:
Router# clear sip-ua tcp connection id 1To completely clear a valid connection to target 172.18.194.183, port 5060, consider the following output example from the show sip-ua connections command:
Router# show sip-ua connections tcp detailTotal active connections : 1No. of send failures : 0No. of remote closures : 0No. of conn. failures : 0No. of inactive conn. ageouts : 0Max. tcp send msg queue size of 1, recorded for 172.18.194.183:5060---------Printing Detailed Connection Report---------Note:** Tuples with no matching socket entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port>'to overcome this error condition++ Tuples with mismatched address/port entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port> id <connid>'to overcome this error conditionRemote-Agent:172.18.194.183, Connections-Count:1Remote-Port Conn-Id Conn-State WriteQ-Size=========== ======= =========== ===========5060 1 Established 0Then execute the clear sip-ua tcp connection command:
Router# clear sip-ua tcp connection id 1 target ipv4:172.18.194.183:5060Purging the entry from sip tcp processPurging the entry from reusable global connection tableThe result is that all connections are cleared after inputting the clear sip-ua tcp connection command:
Router# show sip-ua connections tcp detailTotal active connections : 0No. of send failures : 0No. of remote closures : 0No. of conn. failures : 0No. of inactive conn. ageouts : 0Max. tcp send msg queue size of 1, recorded for 172.18.194.183:5060---------Printing Detailed Connection Report---------Note:** Tuples with no matching socket entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port>'to overcome this error condition++ Tuples with mismatched address/port entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port> id <connid>'to overcome this error conditionRemote-Agent:172.18.194.183, Connections-Count:0Related Commands
clear sip-ua tcp tls connection
To clear a session initiation protocol (SIP) TCP connection, use the clear sip-ua tcp tls connection command in privileged EXEC mode.
clear sip-ua tcp tls connection {id connection-id [target ipv4:address:port] | [id connection-id] target ipv4:address:port}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.4(6)T
This command was introducted to replace the clear sip-ua tcp connection command.
Usage Guidelines
Inappropriate usage of the clear sip-ua tcp tls connection command can lead to erroneous call behavior, inappropriate usage of connections, and failure of calls.
Examples
To cear the connection entry only at the upper transport layer, assign the target IP address and port:
Router# clear sip-ua tcp tls connection target ipv4:172.18.194.183:5060To clear the connection entry only at the lower TCP or User Datagram Protocol (UDP) layer, specify the connection:
Router# clear sip-ua tcp tls connection id 1To completely clear a valid connection to target 172.18.194.183, port 5060, consider the following output example from the show sip-ua connections command:
Router# show sip-ua connections tcp tls detailTotal active connections : 1No. of send failures : 0No. of remote closures : 0No. of conn. failures : 0No. of inactive conn. ageouts : 0Max. tcp send msg queue size of 1, recorded for 172.18.194.183:5060---------Printing Detailed Connection Report---------Note:** Tuples with no matching socket entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port>'to overcome this error condition++ Tuples with mismatched address/port entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port> id <connid>'to overcome this error conditionRemote-Agent:172.18.194.183, Connections-Count:1Remote-Port Conn-Id Conn-State WriteQ-Size=========== ======= =========== ===========5060 1 Established 0Then execute the clear sip-ua tcp connection command:
Router# clear sip-ua tcp tls connection id 1 target ipv4:172.18.194.183:5060Purging the entry from sip tcp processPurging the entry from reusable global connection tableThe result is that all connections are cleared after inputting the clear sip-ua tcp connection command:
Router# show sip-ua connections tcp tls detailTotal active connections : 0No. of send failures : 0No. of remote closures : 0No. of conn. failures : 0No. of inactive conn. ageouts : 0Max. tcp send msg queue size of 1, recorded for 172.18.194.183:5060---------Printing Detailed Connection Report---------Note:** Tuples with no matching socket entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port>'to overcome this error condition++ Tuples with mismatched address/port entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port> id <connid>'to overcome this error conditionRemote-Agent:172.18.194.183, Connections-Count:0Related Commands
clear sip-ua udp connection
To clear a SIP UDP connection, use the clear sip-ua udp connection command in privileged EXEC mode.
clear sip-ua udp connection {id value [target ip-address] | [id value] target ip-address}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Inappropriate usage of the clear sip-ua udp connection command without understanding the issue or the implications can lead to erroneous call behavior, inappropriate usage of connections, and failure of calls.
Examples
To purge the connection entry only at the upper transport layer, assign the target IP address and port.
Router# clear sip-ua udp connection target ipv4:172.18.194.183:5060To purge the connection entry only at the lower TCP/UDP layer, assign the connection ID.
Router# clear sip-ua udp connection id 1
Note
To completely purge a valid connection to target 172.18.194.183, port 5060, consider the following example.
Before executing the clear sip-ua udp connection command, running the show sip-ua connections command gave the following output.
Router# show sip-ua connections udp detailTotal active connections : 1No. of send failures : 0No. of remote closures : 0No. of conn. failures : 0No. of inactive conn. ageouts : 0Max. udp send msg queue size of 1, recorded for 172.18.194.183:5060---------Printing Detailed Connection Report---------Note:** Tuples with no matching socket entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port>'to overcome this error condition++ Tuples with mismatched address/port entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port> id <connid>'to overcome this error conditionRemote-Agent:172.18.194.183, Connections-Count:1Remote-Port Conn-Id Conn-State WriteQ-Size=========== ======= =========== ===========5060 1 Established 0Then execute the clear sip-ua udp connection command:
Router# clear sip-ua udp connection id 1 target ipv4:172.18.194.183:5060Purging the entry from sip udp processPurging the entry from reusable global connection tableThe final result is that all connections are cleared after executing the clear sip-ua udp connection command:
Router# show sip-ua connections udp detailTotal active connections : 0No. of send failures : 0No. of remote closures : 0No. of conn. failures : 0No. of inactive conn. ageouts : 0Max. udp send msg queue size of 1, recorded for 172.18.194.183:5060---------Printing Detailed Connection Report---------Note:** Tuples with no matching socket entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port>'to overcome this error condition++ Tuples with mismatched address/port entry- Do 'clear sip <tcp/udp> conn t ipv4:<addr>:<port> id <connid>'to overcome this error conditionRemote-Agent:172.18.194.183, Connections-Count:0Related Commands
clear ss7 sm stats
To clear the counters that track Session Manager statistics, use the clear ss7 sm stats command in privileged EXEC mode.
clear ss7 sm stats
Syntax Description
This command has no arguments or keywords.
Command Default
The statistical information accumulates.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Examples
The following example shows how to clear Session Manager statistics on a Cisco 2611:
clear ss7 sm statsRelated Commands
show ss7 sm stats
Displays Session Manager information about number of packets queued, received, and so forth.
clear statistics dial-peer voice
To reset voice call counters and recent call details stored in a dial peer, use the
clear statistics dial-peer voice command in privileged EXEC configuration mode.clear statistics dial-peer voice [tag]
Syntax Description
tag
(Optional) Identification tag number of a specific dial peer. A valid entry is any integer that identifies a specific dial peer. Range is from 1 to 2147483647.
Command Default
If the tag argument is not used, counters in all the configured voice dial peers are cleared.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear statistics dial-peer voice command resets the following statistical information about calls:
•
•
•
•
•
•
•
•
•
•
•
Examples
The following example clears voice dial-peer statistics using tag 1234:
Router# clear statistics dial-peer voice 1234Clear voice call statistics stored in this voice dial-peer [confirm]yRouter#The following example clears statistics in all the configured voice dial peers:
Router# clear statistics dial-peer voiceClear voice call statistics stored in all voice dial-peers [confirm]yRouter#Related Commands
clear subscription
To clear all active subscriptions or a specific subscription, use the clear subscription command in privileged EXEC mode.
clear subscription {all | session-id session-id | statistics}
Syntax Description
all
All active subscriptions.
session-id session-id
Subscription session to be cleared.
statistics
Global subscription statistics and all subscription history records.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To cancel a specific subscription, use the session-id argument. You can obtain the session ID by viewing show subscriptions output. When this command is used, the applications associated with subscriptions receive the ev_subscribe_cleanup event. On receiving this event, the script closes the subscription.
Examples
The following example shows global statistics and history records being cleared:
Router# clear subscription statisticsRelated Commands
clear voice accounting method
To clear VoIP AAA accounting statistics for a specific accounting method on the gateway, use the clear voice accounting method command in privileged EXEC mode.
clear voice accounting method method-list-name
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example clears accounting statistics for method list "h323":
Router# clear voice accounting method h323Related Commands
voice statistics type csr
Configures the collection of signaling and VoIP AAA accounting statistics.
clear voice dsp
To "cold-start" one or more digital signal processor (DSP) voice channels, use the clear voice dsp command in privileged EXEC mode.
clear voice dsp {channels | error} [slot[/dsp][/channel]] [slot[/dsp][/channel]]
Syntax Description
Command Default
If this command is not used, active calls continue on the DSP voice channels.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The clear voice dsp command allows you to cold-start DSPs. Execution of this command causes the configured firmware to be downloaded to the specified DSP or a range of DSPs. This command can be executed irrespective of the state of the DSPs. All the active channels of the DSPs are prematurely terminated.
Examples
The following example clears all active calls on slot 2, DSP 1:
Router# clear voice dsp 2/1The following example clears the active calls on slot 2, DSP 1, channel 1:
Router# clear voice dsp 2/1/1Related Commands
show voice dsp
Displays the current status or selective statistics of DSP voice channels
clear voice statistics
To clear voice-statistic collection settings on the gateway to reset the statistics collection, use the clear voice statistics command in privileged EXEC mode.
clear voice statistics [csr [accounting | signaling]] | [iec]
Syntax Description
Command Default
If no keywords are specified, all accounting and signaling statistics, and all IECs are cleared.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears all accounting and signaling statistics, and all Cisco VoIP IECs:
Router# clear voice statisticsThe following example clears all accounting and signaling statistics:
Router# clear voice statistics csrThe following example clears only accounting statistics:
Router# clear voice statistics csr accountingThe following example clears only signaling statistics:
Router# clear voice statistics csr signalingThe following example clears only Cisco VoIP IECs:
Router# clear voice statistics iecRelated Commands
voice statistics type csr
Configures the collection of signaling and VoIP AAA accounting statistics.
clear vsp statistics
To clear all Voice Streaming Processing (VSP) statistics that are displayed when using the show vsp command is used, use the clear vsp statistics command in privileged EXEC mode.
clear vsp statistics
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 3640, Cisco 3660, Cisco AS5300, Cisco AS5350, and Cisco AS5400.
Usage Guidelines
This command resets all cumulative VSP statistics to 0. Use the show vsp statistics command to display the current statistics.
Examples
The following example resets the statistics for VSP sessions:
Router# clear vsp statisticsRelated Commands
