-
Cisco IOS Voice Command Reference
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
New and Modified Commands
-
Commands: A
-
Commands: B
-
Commands: cache --> call fallback jitter-probe num-packets
-
Commands: call fallback jitter-probe precedence --> ces connect
-
Commands: ces initial-delay --> codec preference
-
Commands: comfort-noise --> customer-id
-
Commands: default (MGCP profile) through direct-inward-dial
-
Commands: E
-
Commands: F
-
Commands: G
-
Commands: H
-
Commands: I
-
Commands: K
-
Commands: L
-
Commands: M
-
Commands: N
-
Commands: O
-
Commands: P through Q
-
Commands: R
-
Commands: SCCP through sgcp tse payload
-
Commands: show aal2 profile through show controllers timeslots
-
Commands: show controllers voice through show mgcp
-
Commands: show mgcp connection through show ss7 sm session
-
Commands: show ss7 sm set through shutdown (voice-port)
-
Commands: signal through suppress
-
Commands: T
-
Commands: U
-
Commands: V through W
-
Commands: Z
-
Feedback
Table Of Contents
clear backhaul-session-manager group stats
clear h323 gatekeeper endpoint
clear h323 gatekeeper statistics
clear statistics dial-peer voice
ces initial-delay
To configure the size of the receive buffer of a circuit emulation service (CES) circuit, use the ces initial-delay command in interface configuration mode. To remove the initial-delay value, use the no form of this command.
ces initial-delay bytes
no ces initial-delay bytes
Syntax Description
Defaults
4000 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to ATM configuration on the Cisco MC3810 multiservice concentrator.
Examples
The following example shows configuration of the transmit buffer of the CES circuit to 8,000 bytes:
ces initial-delay 8000Related Commands
ces max-buf-size
To configure the transmit buffer of a circuit emulation service (CES) circuit, use the ces max-buf-size command in interface configuration mode. To delete the CES transmit buffer size, use the no form of this command.
ces max-buf-size size
no ces max-buf-size size
Syntax Description
Defaults
256
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to ATM configuration on the Cisco MC3810.
This command causes incoming bytes received on a CES port to be buffered by the amount configured and sent to the ATM Adaptation Layer 1 (AAL1) process as a block of data.
This command is supported on serial ports 0 and 1 when the encapsulation atm-ces command is enabled.
Examples
The following example shows configuration of the maximum CES reassembly buffer size to 1520:
ces max-buf-size 1520Related Commands
ces service
To configure the ATM circuit emulation service (CES) type, use the ces service command in interface configuration mode. To disable the ATM CES service type, use the no form of this command.
ces service structured
no ces service structured
Syntax Description
structured
Specifies that the ATM CES type is structured. Structured is the only option supported in this release.
Defaults
Structured
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to ATM configuration on the Cisco MC3810.
This command is supported on serial ports 0 and 1 when the encapsulation atm-ces command is enabled.
Examples
The following example sets the CES service to structured for serial port 0:
interface serial 0ces service structuredRelated 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
Defaults
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
Defaults
Default number value is 5000
Default seconds value is 45
Using this command with no keywords or arguments configures the default values for number and secondsCommand Modes
Global configuration
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:
•
Handshake query, status query, and response messages between the CGMA and the third-party management system
•
•
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 define the time slots that belong to each T1 or E1 circuit, use the channel-group command in controller configuration mode. To clear the time slots for the T1 or E1 circuit, use the no form of this command.
channel-group channel-number {timeslots range [speed {56 | 64}] | unframed}
no channel-group [channel-number timeslots range]
Syntax Description
Defaults
The default line speed when configuring a T1 controller is 56 kbps.
The default line speed when configuring an E1 controller is 64 kbps.Command Modes
Controller configuration
Command History
11.3 MA
This command was introduced.
12.3(1)
This command was integrated into Cisco IOS Release 12.3(1) and support was added for the unframed keyword.
Usage Guidelines
Use this 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
Examples
The following example defines three channel groups. Channel-group 0 consists of a single time slot, channel-group 8 consists of 7 time slots and runs at a speed of 64 kbps per time slot, and channel-group 12 consists of a single time slot.
channel-group 0 timeslots 1channel-group 8 timeslots 5,7,12-15,20 speed 64channel-group 12 timeslots 2
The 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 unframedRelated Commands
framing
Selects the frame type for the T1 or E1 data line
linecode
Selects the linecode type for T1 or E1 line
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
Defaults
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 0
The 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
Defaults
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 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.
Defaults
By 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 triggers and their associated parameters, 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
Defaults
See "Syntax Description" table for command defaults
Command Modes
Privileged EXEC
Command History
Examples
The following example resets all call threshold statistics:
clear call threshold statsThe following example resets the counter for the call volume in the gateway:
clear call threshold total-callsThe following example resets the counter for the call volume on Ethernet interface 0/1:
clear call threshold interface ethernet 0/1 int-callsRelated Commands
clear call treatment stats
To clear the 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-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 t1
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] | call-counters [system-hwm | all]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear controller t1 call-counters all command clears the system DS0 HWMs and all individual controller statistics, including Total Calls and Total Duration. The clear controller t1 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 t1 call-counters related commands.
•
TotalCalls for time slots are set to zero when the clear controller t1 1/0/0 call-counters timeslot 10 command is executed or the clear controller t1 1/0/0 call-counters command is executed at a controller level. 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: 4
Note
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: 4
Note
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: 4
Note
The following is sample output showing the system-hwm keyword:
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: 3
Note
The following is sample output when two calls are cleared on controllers 1/5/13 and 1/5/14:
Router# clear line 1/5/13[confirm][OK]Router# clear line 1/5/14[confirm][OK]Router# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00tty 1/5/15 Router Async interface 00:09:46 PPP: 55.52.1.1Interface User Mode Idle Peer AddressRouter# 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:11:0423 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: 3
Note
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: 1
Note
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 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: 0
Note
The 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
controller
Enters controller configuration mode.
show controllers t1 call-counters
Displays the total number of calls and call durations on a T1 controller.
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.
Defaults
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
Defaults
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
Defaults
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
Defaults
For ipaddr address [port], If a value for the port argument is not specified, the default 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.
Defaults
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 ip sctp statistics
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.
Defaults
No default behavior or values
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 that supports VoIP, 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 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
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.
Defaults
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.
Defaults
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 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.
Defaults
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 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.
Defaults
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 the voice call counters and recent call details stored in the 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. There is no default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear statistics dial-peer voice command resets the following statistical information about calls:
•
•
•
•
•
•
•
•
•
•
•
If the tag argument is used, counters in the specified voice dial peer are cleared. Otherwise, counters in all the configured voice dial peers are cleared.
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 voice port
To clear voice port calls in progress, use the clear voice port command in privileged EXEC mode. This command does not have a no form.
clear voice port [slot/port]
Syntax Description
slot/port
(Optional) The voice port slot number and port number. If you do not specify a voice port, all calls on all voice ports are cleared.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify a voice port, all calls on all voice ports are cleared. A confirmation prompt is displayed.
Examples
The following example clears all calls on voice port 1/2 on the Cisco MC3810:
Router# clear voice port 1/2clear 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 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
clid (dial-peer)
To control the presentation and use of calling-line ID (CLID) information, use the clid command in dial-peer configuration mode. To remove CLID controls, use the no form of this command.
clid {network-number number [second-number strip] | override rdnis | restrict | strip [name | pi-restrict]}
no clid {network-number number [second-number strip] | override rdnis | restrict | strip [name | pi-restrict]}
Syntax Description
Defaults
No default behavior or values
Command Modes
Dial-peer configuration
Command History
12.2(11)T
This command was introduced.
12.3(13)
The override rdnis keyword was added.
Usage Guidelines
The override rdnis keywords are supported only for POTS dial peers.
CLID is the collection of information about the billing telephone number from which a call originated. The CLID value might be the entire phone number, the area code, or the area code plus the local exchange. It is also known as caller ID. The various keywords to this command manage the presentation, restriction, or stripping of the various CLID elements.
The clid network-number command sets the presentation indicator to "y" and the screening indicator to "network-provided." The second-number strip keyword strips from the H.225 source-address field the original calling-party number, and is valid only if a network number has previously been configured.
The clid override rdnis command overrides the CLID with the RDNIS if it is available.
The clid restrict command causes the calling-party number to be present in the information element, but the presentation indicator is set to "n" to prevent its presentation to the called party.
The clid strip command causes the calling-party number to be null in the information element, and the presentation indicator is set to "n" to prevent its presentation to the called party.
Examples
The following example sets the calling-party network number to 98765 for POTS dial peer 4321:
Router(config)# dial-peer voice 4321 potsRouter(config-dial-peer)# clid network-number 98765The following example prevents the second network number from being sent in the CLID information:
Router(config-dial-peer)# clid second-number stripAn alternative method of accomplishing this result is to enter the second-number strip keywords as part of the clid network-number command. The following example sets the calling-party network number to 56789 for VoIP dial peer 1234 and also prevents the second network number from being sent:
Router(config)# dial-peer voice 1234 voipRouter(config-dial-peer)# clid network-number 56789 second-number stripThe following example overrides the calling-party number with RDNIS if available.
Router(config-dial-peer)# clid override rdnisThe following example prevents the calling-party number from being presented:
Router(config-dial-peer)# clid restrictThe following example removes the calling-party number from the CLID information and prevents the calling-party number from being presented:
Router(config-dial-peer)# clid stripclock-select
To establish the sources and priorities of the requisite clocking signals for the OC-3/STM-1 ATM Circuit Emulation Service network module, use the clock-select command in CES configuration mode.
clock-select priority-number interface slot/port
Syntax Description
Defaults
No default behavior or values
Command Modes
CES configuration
Command History
Usage Guidelines
This command is used on Cisco 3600 series routers that have OC-3/STM-1 ATM CES network modules.
To support synchronous or synchronous residual time stamp (SRTS) clocking modes, you must specify a primary reference source to synchronize the flow of constant bit rate (CBR) data from its source to its destination.
You can specify up to four clock priorities. The highest priority active interface in the router supplies primary reference source to all other interfaces that require network clock synchronization services. The fifth priority is the local oscillator on the network module.
Use the show ces clock-select command to display the currently configured clock priorities on the router.
Examples
The following example defines two clock priorities on the router:
clock-select 1 cbr 2/0clock-select 2 atm 2/0Related Commands
codec (dial-peer)
To specify the voice coder rate of speech for a dial peer, use the codec command in dial peer configuration mode. To reset the default value, use the no form of this command.
Cisco 1750 and Cisco 1751 Modular Access Routers, Cisco AS5300 and AS5800 Universal Access Servers, and Cisco MC3810 Multiservice Concentrators
codec codec [bytes payload_size]
no codec codec [bytes payload_size]
Cisco 2600 and 3600 Series Routers and Cisco 7200 and 7500 Series Routers
codec {codec [bytes payload_size] | transparent}
no codec {codec [bytes payload_size] | transparent}
Syntax Description
codec
Codec options available for the various platforms are described in Table 13, below.
bytes
(Optional) Specifies the number of bytes in the voice payload of each frame.
payload-size
(Optional) Number of bytes in the voice payload of each frame. See Table 14 for valid entries and default values.
transparent
Enables codec capabilities to be passed transparently between endpoints in a Cisco Multiservice IP-to-IP Gateway.
Note
Defaults
g729r8, 30-byte payload for VoFR and VoATM
g729r8, 20-byte payload for VoIP
See Table 14 for valid entries and default values.Command Modes
Dial peer configuration
Command History
Note
Usage Guidelines
Use this command to define a specific voice coder rate of speech and payload size for a VoIP or VoFR dial peer. This command is also used for VoATM.
A specific codec type can be configured on the dial peer as long as it is supported by the setting used with the codec complexity voice-card configuration command. The codec complexity command is voice-card specific and platform specific. The codec complexity voice-card configuration command is set to either high or medium.
If the codec complexity command is set to high, the following keywords are available: g711alaw, g711ulaw, g723ar53, g723ar63, g723r53, g723r63, g726r16, g726r24, g726r32, g728, g729r8, and g729br8.
If the codec complexity command is set to medium, the following keywords are available: g711alaw, g711ulaw, g726r16, g726r24, g726r32, g729r8, and g729br8.
The codec dial peer configuration command is particularly useful when you must change to a small-bandwidth codec. Large-bandwidth codecs, such as G.711, do not fit in a small-bandwidth link. However, the g711alaw and g711ulaw codecs provide higher quality voice transmission than other codecs. The g729r8 codec provides near-toll quality with considerable bandwidth savings.
If codec values for the dial peers of a connection do not match, the call fails.
You can change the payload of each VoIP frame by using the bytes keyword; you can change the payload of each VoFR frame by using the bytes keyword with the payload-size argument. However, increasing the payload size can add processing delay for each voice packet.
Table 14 describes the voice payload options and default values for the codecs and packet voice protocols.
For toll quality, use the g711alaw or g711ulaw keyword. These values provide high-quality voice transmission but use a significant amount of bandwidth. For nearly toll quality (and a significant savings in bandwidth), use the g729r8 keyword.
On the Cisco MC3810, this command was first supported as a voice port command. On the Cisco MC3810, you can also assign codec values to the voice port. If configuring calls to a Cisco MC3810 that is running software versions prior to 12.0(4)T, configure the codec command on the voice port. If configuring Cisco trunk permanent calls, configure the codec command on the dial peer. If you configure the codec command on the dial peer for VoFR permanent calls on the Cisco MC3810, the dial peer codec command setting overrides the codec setting configured on the voice port.
Note
Note
Note
Note
Examples
The following example shows how to configure a voice coder rate that provides toll quality voice with a payload of 120 bytes per voice frame on a Cisco 2600 or Cisco 3600 series router that is acting as a terminating node. The sample configuration begins in global configuration mode and is for VoFR dial peer 200.
dial-peer voice 200 vofrcodec g711ulaw bytes 240The following example configures a voice coder rate for VoIP dial peer 10 that provides toll quality but uses a relatively high amount of bandwidth:
dial-peer voice 10 voipcodec g711alawThe following example configures the transparent codec used by the Cisco Multiservice IP-to-IP Gateway:
dial-peer voice 1 voipincoming called-number .Tdestination-pattern .Tsession target rascodec transparentRelated Commands
codec (dsp)
To specify call density and codec complexity based on a particular codec standard, use the codec command in DSP interface dsp farm mode. To reset the card type to the default, use the no form of the command.
codec {high | med}
no codec {high | med}
Syntax Description
high
Specifies high complexity: two channels of any mix of codec.
med
Specifies medium complexity: four channels of g711/g726/g729a/fax.
Defaults
Medium complexity
Command Modes
DSP interface dsp farm
Command History
Usage Guidelines
This command is supported on only the Cisco 7200 series and Cisco 7500 series routers.
Codec complexity refers to the amount of processing required to perform compression. Codec complexity affects the number of calls, referred to as call density, that can take place on the DSPfarm interfaces. The greater the codec complexity, the fewer the calls that are handled. For example, G.711 requires less DSP processing than G.728, so as long as the bandwidth is available, more calls can be handled simultaneously by using the G.711 standard than by using G.728.
The DSPinterface dspfarm codec complexity setting affects the options available for the codec dial peer configuration command.
To change codec complexity, you must first remove any configured channel associated signaling (CAS) or DS0 groups and then reinstate them after the change.
Note
Examples
The following example configures the DSPfarm interface 1/0 on the Cisco 7200 series routers to support high compression:
dspint DSPFarm 1/0 codec highRelated Commands
codec (dial peer)
Specifies the voice codec rate of speech for a dial peer.
codec complexity
Specifies call density and codec complexity based on the codec standard you are using.
codec (voice-port)
The codec command in voice-port configuration mode on the Cisco MC3810 that was first supported in Cisco IOS Release 11.3(1)MA is no longer supported, beginning with Cisco IOS Release 12.2. Configure the codec value using the codec dial peer configuration command.
codec aal2-profile
To set the codec profile for a digital signal processor (DSP) on a per-call basis, use the codec aal2-profile command in dial-peer configuration mode. To restore the default codec profile, use the no form of this command.
codec aal2-profile {itut | custom | atmf} profile-number codec
no codec aal2-profile
Syntax Description
Defaults
ITU-T profile 1 (G.711 u-law)
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use this command to configure the DSP to operate with a specified profile type and codecs.
You must enter the session protocol aal2-trunk command before configuring the codec ATM adaptation layer 2 (AAL2) profile.
This command is used instead of the codec (dial-peer) command for AAL2 trunk applications.
Examples
The following example sets the codec AAL2 profile type to ITU-T and configures a profile number of 7, enabling codec G.729ar8:
dial-peer voice 100 voatmsession protocol aal2-trunkcodec aal2-profile itut 7 g729ar8The following example sets the codec AAL2 profile type to custom and configures a profile number of 100, enabling codec G.726r32:
dial-peer voice 200 voatmsession protocol aal2-trunkcodec aal2-profile custom 100 g726r32The following example shows BLES mode being configured on the Cisco IAD2420 series IAD:
dial-peer voice 1000 voatmsession protocol aal2-trunk...codec aal2-profile ATMF 9 g711ulawno vadRelated Commands
session protocol (dial-peer)
Establishes a session protocol for calls between the local and remote routers via the packet network.
codec complexity
To specify call density and codec complexity according to the codec standard that is being used, use the codec complexity command in voice-card configuration mode. To reset the meduim complexity default, use the no form of this command.
codec complexity {flex | high | medium} [ecan-extended]
no codec complexity
Syntax Description
Defaults
Medium complexity
Command Modes
Voice-card configuration
Command History
Usage Guidelines
Codec complexity refers to the amount of processing required to perform voice compression. Codec complexity affects the call density—the number of calls reconcile on the DSPs. With higher codec complexity, fewer calls can be handled. Select a higher codec complexity if that is required to support a particular codec or combination of codecs. Select a lower codec complexity to support the greatest number of voice channels, provided that the lower complexity is compatible with the particular codecs in use.
To change codec complexity, all of the DSP voice channels must be in the idle state.
Note
card 0 in the command-line interface (CLI). If two HCMs are installed, the codec complexity command configures both HCMs at once.The flex keyword allows the DSP to process up to 16 channels. In addition to continuing support for configuring a fixed number of channels per DSP, the flex option enables the DSP to handle a flexible number of channels. The total number of supported channels varies from 6 to 16, depending on which codec is used for a call. Therefore, the channel density varies from 6 per DSP (high-complexity codec) to 16 per DSP (g.711 codec).
Note
The high keyword selects a higher codec complexity if that is required to support a particular codec or combination of codecs. When you use the codec complexity high command to change codec complexity, the system prompts you to remove all existing DS0 or PRI groups using the specified voice-card first, then all DSPs are reset, loaded with the specified firmware image, and released. Refer to the "Switching Echo Cancellers" section of the Enhanced ITU-T G.168 Echo Cancellation feature documentation on Cisco.com for more information about removing and replacing DS0 or PRI groups.
The medium keyword selects a lower codec complexity to support the greatest number of voice channels, provided that the lower complexity is compatible with the particular codecs in use.
The ecan-extended keyword is used when either the codec complexity high or the codec complexity medium options are chosen. The default option is to use the Cisco proprietary G.165-compliant echo canceller (EC). The ecan-extended keyword selects the extended echo canceller.
You can also construct two separate configurations, one for the Cisco default EC and one for the extended EC, which you can load manually by creating new configurations for each type of EC and reloading the router.
•
•
For the Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature, each DSP can support up to two voice calls, so the host must ensure that no more than two out of the four enabled channels are active at any time.
The Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature can process up to 16 voice channels when running the high-complexity image set. Those 16 time slots need to be within a contiguous range to satisfy the Multi-channel Buffered Serial Port (McBSP) channel selection scheme. See the ds0-group and pri-group commands for more information.
In the Cisco MC3810 series, this command is valid only with HCM(s) installed, and you must specify voice card 0 in the command mode. If two HCMs are installed, the codec complexity command configures both HCMs at once.
SIP gateways do not support a codec preference order with H.323 signaling; all codecs listed are given equal preference. Specifically, they do not prefer g729r8 over g729br8 if both are defined.
Examples
The following example enters voice-card configuration mode and sets the codec complexity to flex on voice card 1 in a Cisco 2600 or Cisco 3600 series router:
voice-card 1
codec complexity flexThe following example enters voice-card configuration mode and loads high-complexity DSP firmware on voice-card 0. The dspfarm command enters the DSP resources on the AIM specified in the voice-card command into the DSP resource pool.
voice-card 0codec complexity highdspfarmIf you were to switch to medium complexity on the same voice-card by entering the codec complexity command, the following error message occurs:
voice-card 0codec complexitycodec complexity mediumThe following example sets the codec complexity to high on a Cisco MC3810 that contains one or two HCMs:
voice-card 0 codec complexity highThe following example sets the codec complexity to high on voice card 1 in a Cisco 2600 or Cisco 3600 series router:
voice-card 1 codec complexity highTo change the codec complexity configuration, enter the following command (the default is codec complexity medium):
voice-cardcodec complexity high ecan-extendedRelated Commands
codec preference
To specify a list of preferred codecs to use on a dial peer, use the codec preference command in voice-class configuration mode. To disable this functionality, use the no form of this command.
codec preference value codec-type [bytes payload-size]
no codec preference value codec-type
Syntax Description
Defaults
No default behavior or values
Command Modes
Voice-class configuration
Command History
Usage Guidelines
The routers at opposite ends of the WAN may have to negotiate the codec selection for the network dial peers. The codec preference command specifies the order of preference for selecting a negotiated codec for the connection. Table 15 describes the voice payload options and default values for the codecs and packet voice protocols.
SIP gateways do not support a codec preference order with H.323 signaling; all codecs listed are given equal preference. Specifically, they do not prefer g729r8 over g729br8 if both are defined.
Examples
The following example creates codec preference list 99 and applies it to dial peer 1919:
voice class codec 99codec preference 1 g711alawcodec preference 2 g711ulaw bytes 80codec preference 3 g723ar53codec preference 4 g723ar63 bytes 144codec preference 5 g723r53codec preference 6 g723r63 bytes 120codec preference 7 g726r16codec preference 8 g726r24codec preference 9 g726r32 bytes 80codec preference 10 g729br8codec preference 11 g729r8 bytes 50codec preference 12 gsmefrenddial-peer voice 1919 voipvoice-class codec 99The following example configures the transparent codec used by the Cisco Multiservice IP-to-IP Gateway:
voice class codec 99codec preference 1 transparentcodec preference 1 transparent
Note
Related Commands
