-
Cisco IOS Dial Technologies Command Reference, Release 12.3 T
-
Introduction
-
Dial Technologies Commands: A through cas-group
-
Dial Technologies Commands: channel through cpp
-
Dial Technologies Commands: debounce through dial-tdm
-
Dial Technologies Commands: disconnect through group
-
Dial Technologies Commands: initiate through ipx
-
Dial Technologies Commands: isdn through isdn x25
-
Dial Technologies Commands: L
-
Dial Technologies Commands: M
-
Dial Technologies Commands: name through pptp
-
Dial Technologies Commands: pri through rotary
-
Dial Technologies Commands: script through show dial
-
Dial Technologies Commands: show dsc through show line
-
Dial Technologies Commands: show modem through show nbf
-
Dial Technologies Commands: show port through show resource
-
Dial Technologies Commands: show sessions through show vtemplate
-
Dial Technologies Commands: shutdown through x25 map
-
Table Of Contents
clear interface virtual-access
channel-group
To configure serial WAN on a T1 or E1 interface, use the channel-group command in controller configuration mode. To unassign a channel group, use the no form of this command.
Cisco 2600 Series, Cisco 3660, Cisco 3725, and Cisco 3745
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 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
Defaults
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 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, 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, 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, Cisco 3660, Cisco 3725, and Cisco 3745.
Note
Neither the Cisco AS500 series NAS nor the Cisco MC3810 is supported with the integrated voice and data WAN on T1/E1 interfaces using the AIM-ATM-VOICE-30 module.
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
When you specify 56 kbps for the speed of the underlying DS0, the channel group is limited to 14 channels on the Cisco MC3810 MultiFlex Trunk (MFT). Because the 56 kbps is the default, specify the 64 kbps when you need more than 14 channels.
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-group12 consists of a single time slot.
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 timeslots10 64
Note
Related Commands
chat-script
To create a script that will place a call over a modem, use the chat-script command in global configuration mode. To disable the specified chat script, use the no form of this command.
chat-script script-name expect-send
no chat-script script-name expect-send
Syntax Description
script-name
Name of the chat script.
expect-send
Pairs of information elements: an item to expect and an item to send in response.
Defaults
No chat scripts are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Chat scripts are used in dial-on-demand routing (DDR) to give commands to dial a modem and commands to log on to remote systems. The defined script will be used to place a call over a modem.
Some characteristics of chat scripts are as follows:
•
•
•
•
We recommend that one chat script (a "modem" chat script) be written for placing a call and another chat script (a "system" or "login" chat script) be written to log on to remote systems, where required.
Suggested Chat Script Naming Conventions
A suggested chat script naming convention is vendor-type-modulation. If you follow this convention, the syntax of the chat-script command becomes chat-script vendor-type-modulation expect-send.
For example, if you have a Telebit T3000 modem that uses V.32bis modulation, you would name your chat script telebit-t3000-v32bis.
The chat-script command could be written as follows:
chat-script telebit-t3000-v32bis ABORT ERROR ABORT BUSY ABORT "NO ANSWER" "" "AT H" OK "AT DT \T" DIALING \c TIMEOUT 30 CONNECT \cAdhering to this naming convention allows you to use partial chat script names with regular expressions to specify a range of chat scripts that can be used. This capability is particularly useful for dialer rotary groups and is explained further in the next section.
Chat scripts are in the form expect-send, where the send string following the hyphen (-) is executed if the preceding expect string fails. Each send string is followed by a return unless it ends with the escape sequence \c. The sequence ^x is translated into the appropriate control character, and the sequence \x is translated into x if \x is not one of the special sequences listed in Table 2.
See the book titled Managing uucp and Usenet by Tim O'Reilly and Grace Todino for more information about chat scripts.
Escape Sequences
The escape sequences used in chat scripts are listed in Table 3.
Expect-Send Pairs
Sample supported expect-send pairs are described in Table 4.
For example, if a modem reports BUSY when the number dialed is busy, you can indicate that you want the attempt stopped at this point by including ABORT BUSY in your chat script.
Alternate Handlers
If you use the expect-send pair ABORT SINK instead of ABORT ERROR, the system terminates abnormally when it encounters SINK instead of ERROR.
Missed Characters
After the connection is established and you press the Return key, you must often press Return a second time before the prompt appears.
For example, you might include the following as part of your chat script:
ssword:-/r-sswordThis part of the script specifies that, after the connection is established, you want ssword to be displayed. If it is not displayed, you must press Return again after the timeout passes.
Examples
The following example shows the chat-script command being used to create a chat script named t3000:
chat-script t3000 ABORT ERROR ABORT BUSY ABORT "NO ANSWER" "" "AT H" OK "AT DT \T" DIALING \c TIMEOUT 60 CONNECT \cRelated Commands
class (controller)
To create a signaling class structure that can be referred to by its name, use the class command in controller configuration mode. To remove the structure, use the no form of this command.
class name
no class name
Syntax Description
Command Modes
Controller configuration
Command History
Usage Guidelines
A signaling class allows the Cisco AS5300 and Cisco AS5800 universal access servers to provide the ANI/DNIS delimiter on incoming T1/CAS trunk lines. The digit collection logic in the call switching module (CSM) for incoming T1 CAS calls in dual tone multifrequency (DTMF) is modified to process the delimiters, the ANI digits, and the DNIS digits.
For this feature to work, a CAS signaling class with the template to process ANI/DNIS delimiters has to be defined. This creates a signaling class structure which can be referred to by its name. The name argument must match the name configured in the signaling-class cas command.
Examples
The following example defines a CAS signaling class with the template to process ANI/DNIS delimiters on channel 1:
Router(config)# signaling-class cas testRouter(config-sig-class)# profile incoming S<*a<*d<*nRouter(config)# controller T1 1/0/1Router(config-controller)# cas-custom 1Router(config-ctrl-cas)# class testRelated Commands
clear cot summary
To reset the counters, use the clear cot summary command in privileged EXEC mode.
clear cot summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
There is no display generated, but the counters in the show cot summary command would be all zeros.
Related Commands
clear counters (async)
To clear the counters of a specified asynchronous interface or specified asynchronous interface group, as displayed by the show interface async command, use the clear counters command in EXEC mode.
clear counters {async async-interface-number | group-async group-async-interface-number}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Before using this command, use the show interface async command to display the asynchronous related counters on the specified asynchronous interface.
Examples
The following example uses the show interface async command to display the asynchronous related counters on the asynchronous interface named 1. The example then uses the clear counters group-async command to clear the counters. After the counters are cleared, the configuration file for the interface is displayed.
Router# show interface async 1Async1 is down, line protocol is downmodem(slot/port)=1/0, state=IDLEdsx1(slot/unit/channel)=NONE, status=VDEV_STATUS_UNLOCKEDHardware is Async SerialInterface is unnumbered. Using address of Ethernet0 (1.18.31.9)MTU 1500 bytes, BW 115 Kbit, DLY 100000 usec, rely 255/255, load 1/255Encapsulation PPP, loopback not set, keepalive not setDTR is pulsed for 5 seconds on resetLCP ClosedClosed: IPCP, CDPCPLast input never, output never, output hang neverLast clearing of "show interface" counters 00:03:46Input queue: 0/10/0 (size/max/drops); Total output drops: 0/////Queueing strategy: weighted fairOutput queue: 0/1000/64/0 (size/max total/threshold/drops)Conversations 0/0/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsRouter#Router# clear counters group-async 1Clear "show interface" counters on this interface [confirm]Router#*Oct 17 00:42:27.083: %CLEAR-5-COUNTERS: Clear counter on interface Group-AsynceRelated Commands
clear counters line
To clear line counters, use the clear counters line command in EXEC mode.
clear counters line {type | number}
Syntax Description
type
Line type: aux, console, tty, or vty.
number
First line number to clear, which can be between 0 and 54.
Command Modes
EXEC
Command History
Usage Guidelines
This command clears the line counters shown by the show line command.
Examples
The following example shows the available options under the clear counters line command. When you issue this command, the counters (for example, Uses and Noise) displayed by the show line command are cleared.
Router# clear counters line ?<0-54> First Line numberaux Auxiliary lineconsole Primary terminal linetty Terminal controllervty Virtual terminalRouter# exitRouter> show lineTty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns* 0 CTY - - - - - 0 4 0/0A 1 TTY 115200/115200 - inout - - - 1 0 0/0A 2 TTY 115200/115200 - inout - - - 1 0 0/0A 3 TTY 115200/115200 - inout - - - 1 0 0/0* 4 TTY 115200/115200 - inout - - - 0 0 0/0* 5 TTY 115200/115200 - inout - - - 0 0 0/0* 6 TTY 115200/115200 - inout - - - 0 0 0/0* 7 TTY 115200/115200 - inout - - - 0 0 0/0* 8 TTY 115200/115200 - inout - - - 0 0 0/0* 9 TTY 115200/115200 - inout - - - 0 0 0/0* 10 TTY 115200/115200 - inout - - - 0 0 0/0* 11 TTY 115200/115200 - inout - - - 0 0 0/0* 12 TTY 115200/115200 - inout - - - 0 0 0/0* 13 TTY 115200/115200 - inout - - - 0 0 0/0* 14 TTY 115200/115200 - inout - - - 0 0 0/0* 15 TTY 115200/115200 - inout - - - 0 0 0/0A 16 TTY 115200/115200 - inout - - - 1 0 0/0A 17 TTY 115200/115200 - inout - - - 1 0 0/0A 18 TTY 115200/115200 - inout - - - 1 0 0/0A 19 TTY 115200/115200 - inout - - - 1 0 0/0A 20 TTY 115200/115200 - inout - - - 1 0 0/0A 21 TTY 115200/115200 - inout - - - 1 0 0/0Related Commands
clear dialer
To clear the values of dialer statistics for one or more serial interfaces or BRIs configured for dial-on-demand routing (DDR), use the clear dialer privileged EXEC mode command
clear dialer [interface interface-type interface-number]
Cisco 7500 Series Routers Only
clear dialer [interface serial slot/port]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If the interface keyword and the arguments are not used, dialer statistics are cleared on all interfaces.
Examples
The following example clears the dialer statistics on serial interface 1:
Router# clear dialer interface serial 1clear dialer dnis
To reset the counter statistics associated with a specific dialed number identification service (DNIS) group or number, use the clear dialer dnis command in privileged EXEC mode.
clear dialer dnis {group name | number number}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear dialer dnis EXEC command to reset the counter statistics associated with a specific DNIS group or number. This command clears the counters for a DNIS group to reset the counter statistics associated with a specific DNIS group or number. If an ISP is charging a customer for the number of calls to a DNIS, it can clear the number after a week or month by using this command.
Examples
The following example shows the result of using the clear dialer dnis command for the DNIS group named "dg1". Note that the counters have been cleared after the clear dialer dnis command has been entered.
Router# show dialer dnis group dg1DNIS Number:710284 total connections3 peak connections1 calltype mismatchesDNIS Number:41562665418 total connections5 peak connections0 calltype mismatchesDNIS Number:40855416283 total connections2 peak connections0 calltype mismatchesDNIS Number:710172 total connections1 peak connections0 calltype mismatchesRouter# clear dialer dnis group dg1Router# show dialer dnis group dg1DNIS Number:710280 total connections0 peak connections0 calltype mismatchesDNIS Number:41562665410 total connections0 peak connections0 calltype mismatchesDNIS Number:40855416280 total connections0 peak connections0 calltype mismatchesDNIS Number:710170 total connections0 peak connections0 calltype mismatchesRelated Commands
clear dialer sessions
To remove all dialer sessions and disconnect links when connected, use the clear dialer sessions command in EXEC mode.
clear dialer sessions
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example shows how to use the clear dialer sessions command:
Router# clear dialer sessionsRelated Commands
clear dsip tracing
To clear Distributed System Interconnect Protocol (DSIP) tracing statistics (trace logging), use the clear dsip tracing command in privileged EXEC mode.
clear dsip tracing {counters | tracing} [control | data | ipc]
Syntax Description
Defaults
If no option is specified, all control, data, and inter-process communication counters or tracing buffers are cleared.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear the counters displayed with the show dsip tracing EXEC command.
Examples
In the following example, the DSIP counters are cleared (including data, control, and ipc counters):
Router# clear dsip tracingRelated Commands
show dsip tracing
Displays DSIP tracing buffer information.
show dsip version
Displays DSIP version information.
clear interface virtual-access
To tear down the virtual access interface and free the memory for other dial-in uses, use the clear interface virtual-access command in EXEC mode.
clear interface virtual-access number
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command does not free the memory for uses unrelated to dial-in access.
Examples
The following example clears a specified virtual access interface. You can use the show interfaces virtual-access command to display the interface numbers before you clear any specific one.
Router# clear interface virtual access 1Related Commands
clear ip route download
To clear static routes downloaded from an authentication, authorization, and accounting (AAA) server, use the clear ip route download command in EXEC mode.
clear ip route download {* | network-number network-mask | reload}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command forces the router to reload static routes from the AAA server before the update timer expires.
Examples
The following example shows how to clear all routes:
Router# clear ip route download *Related Commands
clear line
To return a terminal line to idle state, use the clear line command in EXEC mode.
clear line line-number
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to log out of a specific session running on another line. If the line uses a modem, the modem will be disconnected.
Examples
The following example resets line 3 to idle state:
Router# clear line 3clear line async-queue
To reset the connections currently waiting to use a rotary line in the queue, use the clear line async-queue command in EXEC mode.
clear line async-queue [rotary-group]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Use this command without any argument to remove all rotary line queues and terminate the asynchronous queue manager. Use the clear line async-queue command with the rotary-group argument to reset only the specified rotary group.
Examples
The following example clears all the rotary queues and shows the resulting output:
Router# clear line async-queueClearing queued connections for ALL rotary groups ! [confirm]Clearing rotary group 1Clearing line 69Clearing line 70Clearing rotary group 2Clearing line 66Clearing line 67Clearing line 68clear modem
To reset the hardware for one or more manageable modems on an access server or router, use the clear modem command in EXEC mode.
clear modem {slot/port | all | group group-number | at-mode slot/port | test}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The modem hardware is reset for modems that are idle or busied out for long periods of time.
An AT directly connected session is usually initiated and closed from the same Telnet session when you enter the modem at-mode command and press Ctrl-C. However, you can clear an AT directly connected session that was mistakenly left open by enabling the clear modem at-mode command from a second Telnet session in to the access server.
Examples
The following example of the clear modem slot/port command resets the hardware for manageable modem 1/1:
Router# clear modem 1/1The following is an example of using the clear modem all command:
Router# clear modem allThis command will disconnect any active calls.Clear (reset) all modems? [confirm]Clearing modems................................................DoneRouter#The following examples of the clear modem group command clear the manageable modems in group 1:
Router# clear modem group 1Router# clear modem group1The following example executes the clear modem at-mode command from a Telnet session:
modem at-mode 1/1The following example executes the clear modem at-mode command from a second Telnet session while the first Telnet session is connected to the modem:
Router# clear modem at-mode 1/1clear "modem at-mode" for modem 1/1 [confirm]Router#The following output is displayed in the first Telnet session after the modem is cleared by the second Telnet session:
Direct connect session cleared by vty0 (172.19.1.164)Related Commands
clear modem counters
To clear the statistical counters on one or more manageable modems installed in an access server, use the clear modem counters command in EXEC mode.
clear modem counters [slot/port-number | group [group-number]]
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
Entering the clear modem counters command without specifying an optional keyword or argument resets the modem statistics on each modem and the summary statistics displayed in the show modem summary command.
The subcommand clear modem counters group without the group number clears counters in all modem groups. The optional modem group number is the number of a group you have previously created.
Examples
The following example of the clear modem counters slot/port command clears the statistical counters on manageable modem 1/1:
Router# clear modem counters 1/1The following example of the clear modem counters group command clears the statistical counters on all manageable modem groups:
Router# clear modem counters groupClear "show modem" counters for all modem groups [confirm]Router#*Oct 17 20:20:24.974: %CLEAR-5-COUNTERS: Clear counter on modems in all groups eRouter#Related Commands
clear modem log
To reset the log for one or more manageable modems installed in a Cisco AS5800 series access server, use the clear modem log command in EXEC mode.
clear modem log [shelf/slot/port shelf/slot/port ... | group [group-number]]
Syntax Description
Defaults
Reset logs for all modems.
Command Modes
EXEC
Command History
Usage Guidelines
Entering the clear modem log command without specifying an optional keyword or argument resets the log for all modems. Entering the clear modem log command and the group keyword without an argument clears the log for all modem groups. Use the optional shelf/slot/port or group-number argument to clear the log of a specific modem or modem group.
The group-number argument is the number of a group you have previously created using the interface group-async global configuration and group range interface configuration commands. These commands create a group of asynchronous interfaces that are associated with a group asynchronous interface on the same device.
Examples
The following example clears the modem log for shelf 1, slot 4, port 0:
Router# clear modem log 1/4/0Clear Modem log for modem 1/4/00 [confirm]yUse the show modem log command to verify that the modem log for shelf 1, slot 4, port 0 is cleared:
Router# show modem log 1/4/0Modem 1/4/00 Events Log:The following example clears the modem logs for shelf 1, slot 4, port 0 and shelf 1, slot 4, port 2:
Router# clear modem log 1/4/1 1/4/2Clear modem log for modems 1/4/01 to 1/4/02 [confirm]yUse the show modem log command to verify the modem logs for shelf 1, slot 4, port 0 and shelf 1, slot 4, port 2 are cleared:
Router# show modem log 1/4/1 1/4/2Modem 1/4/01 Events Log:Modem 1/4/02 Events Log:The following example clears the log for all modems:
Router# clear modem logClear modem log for all modems [confirm]yThe following example clears the log for all modem groups:
Router# clear modem log groupClear modem log for modems in all groups [confirm]yThe following example clears the log for modem group 0:
Router# clear modem log group 0Clear modem log for modems in group 0 [confirm]yRelated Commands
clear modempool-counters
To clear the active or running counters associated with one or more modem pools, use the clear modempool-counters command in EXEC mode.
clear modempool-counters [name]
Syntax Description
name
(Optional) Modem pool name. If you do not include this option, all counters for all modem pools will be cleared.
Command Modes
EXEC
Command History
Usage Guidelines
The clear modempool-counters command clears the counters that are displayed in the show modem-pool command. This command is used only with MICA technologies digital modems.
Examples
The following examples show three modem pools set up on the access server: System-def-Mpool, v90service, and v34service.
Router# show modem-poolmodem-pool: System-def-Mpoolmodems in pool: 20 active conn: 150 no free modems in poolmodem-pool: v90servicemodems in pool: 50 active conn: 433 no free modems in poolcalled_party_number: 4441000max conn allowed: 50, active conn: 433 max-conn exceeded, 3 no free modems in poolmodem-pool: v34servicemodems in pool: 50 active conn: 301 no free modems in poolcalled_party_number: 4443000max conn allowed: 50, active conn: 300 max-conn exceeded, 0 no free modems in poolIn the following example, the clear modempool-counters v90service command clears the running counters for the v90services modem pool.
Router# clear modempool-counters v90serviceRouter# show modem-poolmodem-pool: System-def-Mpoolmodems in pool: 20 active conn: 150 no free modems in poolmodem-pool: v90servicemodems in pool: 50 active conn: 00 no free modems in poolcalled_party_number: 4441000max conn allowed: 50, active conn: 00 max-conn exceeded, 0 no free modems in poolmodem-pool: v34servicemodems in pool: 50 active conn: 301 no free modems in poolcalled_party_number: 4443000max conn allowed: 50, active conn: 300 max-conn exceeded, 0 no free modems in poolRelated Commands
clear port
To reset the NextPort port and clear any active call to the port, use the clear port command in EXEC mode.
Cisco AS5400 with the NextPort Dial Feature Card (DFC)
clear port [slot | slot/port]
Cisco AS5800 with the Universal Port Card (UPC)
clear port [shelf/slot | shelf/slot/port]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
If you specify the shelf, slot, and port, you clear that port on that SPE. If you specify only the shelf and slot, you clear all active ports on that particular shelf and slot. If you do not specify a shelf, slot, or port, you clear all the ports on the access server.
This command also clears the Bad state on a port and resets it. However, the port is not cleared if the SPE was previously in a Bad state due to an SPE firmware download.
Examples
The following example shows output from the clear port command on the Cisco AS5400 with the NextPort DFC. This example clears slot 1, port 1:
Router# clear port 1/1This will clear port 1/01[confirm]yThe following example shows output from the clear port command on the Cisco AS5800 with the UPC. This example clears shelf 1, slot 3, port 0:
Router# clear port 1/3/0This will clear port 1/03/00[confirm]yRelated Commands
clear port log
To clear all event entries in the port level history event log, use the clear port log command in EXEC mode.
Cisco AS5400 with NextPort DFC
clear port log [slot | slot/port]
Cisco AS5800 with Universal Port Card
clear port log [shelf/slot | shelf/slot/port]
Syntax Description
Command Modes
EXEC
Command History
12.1(1)XD
This command was introduced on the Cisco AS5400.
12.1(3)T
This command was implemented on the Cisco AS5800.
Usage Guidelines
The clear port log command clears the entire port log. You cannot remove individual service events from the port log. On the Cisco AS5400 only, you can use show port modem log or the show port digital log to display specific service events, but you must use clear port log to clear the entire port event log.
Examples
The following example shows output from the clear port log command on the Cisco AS5400 with NextPort DFC. This example clears slot 1, port 1:
Router# clear port log 1/1This will clear log event history for port(s)1/01 - 1/01[confirm]yThe following example shows output from the clear port log command on the Cisco AS5800 with universal port card. This example clears shelf 1, slot 3, port 0:
Router# clear port log 01/03/00This will clear port 1/03/00[confirm]yRelated Commands
show port digital log
Displays the data event log for digital modems.
show port modem log
Displays the events generated by the modem sessions.
clear resource-pool
To reset the counter statistics associated with a specific customer profile, call discriminator, or physical resource, use the clear resource-pool command in privileged EXEC mode.
clear resource-pool {customer | discriminator | resource} {name | all}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear resource-pool privileged EXEC command to reset the counter statistics associated with a specific customer profile, call discriminator, or physical resource.
Examples
The following example shows the use of the clear resource-pool command for the specific customer named "customer-isp":
Router# clear resource-pool customer ?WORD Customer profile nameall Clear all customer profilesRouter# clear resource-pool customer customer_ispRelated Commands
clear snapshot quiet-time
To end the quiet period on a client router within two minutes, use the clear snapshot quiet-time command in EXEC mode.
clear snapshot quiet-time interface-type interface-number
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The clear snapshot quiet-time command places the client router in a state to reenter the active period within two minutes. The two-minute hold period ensures a quiet period of at least two minutes between active periods.
Examples
The following example ends the quiet period on dialer interface 1:
Router# clear snapshot quiet-time dialer 1Related Commands
show snapshot
Displays snapshot routing parameters associated with an interface.
snapshot client
Configures a client router for snapshot routing.
clear spe
To reboot all specified service processing elements (SPEs), use the clear spe command in EXEC mode.
Cisco AS5400 with the NextPort Dial Feature Card (DFC)
clear spe [slot | slot/spe]
Cisco AS5800 with the Universal Port Card (UPC)
clear spe [shelf/slot | shelf/slot/spe]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Execution of the clear spe command causes the configured firmware to be downloaded to the specified SPE or the range of SPEs and causes the power-on self-test (POST) to be executed. This command can be executed regardless of the state of the SPEs.
Note
This command downloads configured SPEs with firmware as configured. Unconfigured SPEs download with the default firmware, which is the bundled version. To configure and manage the downloading of firmware without abruptly terminating SPEs, use the firmware location or firmware upgrade commands as appropriate.
Examples
The following example clears SPEs when the clear spe command is entered on the Cisco AS5400 with the NextPort DFC. This example performs a coldstart on slot 1, SPE 1.
Router# clear spe 1/1Router# This will tear all active calls on the SPE(s), if any.[confirm]yThe following example clears SPEs when the clear spe command is entered on the Cisco AS5800 with the UPC. This example performs a coldstart on shelf 1, slot 8, SPE 0.
Router# clear spe 1/8/0Router# This will tear all active calls on the SPE(s), if any.[confirm]yRelated Commands
clear spe counters
To clear all statistics, use the clear spe counters command in EXEC mode.
Cisco AS5350 and Cisco AS5400 with the NextPort Dial Feature Card (DFC)
clear spe counters [slot | slot/spe]
Cisco AS5800 with the Universal Port Card (UPC)
clear spe counters [slot/spe | shelf/slot/spe]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The clear spe counters command clears statistical counters of all service types for the specified SPE, range of SPEs, or all the SPEs. If you do not set a parameter, you clear all SPE statistical counters.
Examples
The following example shows how to clear all statistics by entering the clear spe counters command on the Cisco AS5350 with the NextPort DFC:
Router# clear spe counters 1/3 1/7This will clear statistic counters for SPEs 1/03 - 1/07 [confirm]yThe following example shows how to clear all statistics by entering the clear spe counters command on the Cisco AS5800 with the UPC. This example clears shelf 1, slot 3, ports 0 to 11.
Router# clear spe counters 1/3/0 1/3/11This will clear statistic counters for SPEs 1/03/00 - 1/03/11[confirm]yclear spe log
To clear event entries in the slot history event log, use the clear spe log command in EXEC mode.
Cisco AS5400 with the NextPort Dial Feature Card (DFC)
clear spe log [slot]
Cisco AS5800 with the Universal Port Card (UPC)
clear spe log [shelf/slot]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The clear spe log command clears event entries in the slot history event log. If you do not specify the shelf/slot range, all service processing element (SPE) event entries clear.
If you specify the shelf/slot, only the event entries for that slot clear.
Examples
The following example shows output from the clear spe log command on the Cisco AS5400 with the NextPort DFC. This example clears the SPE log from shelf 1, slot 3:Router# clear spe log 1/03This will clear slot event history for slot(s) 3 - 3[confirm]yThe following example shows output from the clear spe log command on the Cisco AS5800 with the UPC. This example clears shelf 1, slot 8, SPE 0:
Router# clear spe log 1/8/0This will clear slot event history for slot(s) 8 - 8[confirm]yRelated Commands
clear vpdn counters
To clear the counters of a specified virtual private dial-up network (VPDN) session or tunnel or to clear all of the VPDN counters, as displayed by the show vpdn command, use the clear vpdn counters command in privileged EXEC mode.
clear vpdn counters [session {interface interface-type interface-number | id tunnel-id session-id | username username} | tunnel {l2f | l2tp | pptp} {all | hostname hostname | ip {remote | local} ip-address | id tunnel-id}]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear counters for VPDN sessions and tunnels. If no keywords are used when the clear vpdn counters command is used, all VPDN session and tunnel counters are cleared. If the session keyword is used, the specified session counters are cleared. If the tunnel keyword is used, the specified session and tunnel counters are cleared. You cannot clear the VPDN tunnel counters without also clearing the VPDN session counters.
Examples
The following example shows output from the show vpdn command before and after the clear vpdn counters command is issued:
Router# show vpdn session packets interface virtual-access 8L2TP Session Information Total tunnels 1 sessions 1PPTP session removal calls 0LocID RemID TunID Pkts-In Pkts-Out Bytes-In Bytes-Out7 2 28240 10282 10287 431844 298235Router# clear vpdn counters session interface virtual-access 8Clear "show vpdn" counters on this session [confirm]Router# show vpdn session packets interface virtual-access 8L2TP Session Information Total tunnels 1 sessions 1PPTP session removal calls 0LocID RemID TunID Pkts-In Pkts-Out Bytes-In Bytes-Out7 2 28240 0 0 0 0%No active L2F tunnels%No active PPTP tunnels%No active PPPoE tunnelsRelated Commands
show vpdn
Displays information about active L2TP or L2F tunnels or sessions in a VPDN.
clear vpdn history failure
To clear the content of the failure history table, use the clear vpdn history failure command in EXEC mode.
clear vpdn history failure
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example clears the content of the failure history table:
Router# clear vpdn history failureclear vpdn redirect
To clear the redirect counters shown in the show vpdn redirect command output, use the clear vpdn redirect command in privileged EXEC mode.
clear vpdn redirect
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(8)B
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
Clear the previous display statistics regarding redirects and forwards before entering the show vpdn redirect command again.
Examples
The following example clears the redirect counters from a previously entered show vpdn redirect command:
Router# clear vpdn redirectRelated Commands
clear vpdn tunnel
To shut down a specifiedvirtual private dial-up network (VPDN) tunnel and all sessions within the tunnel, use the clear vpdn tunnel command in privileged EXEC mode.
L2TP or PPTP Tunnels
clear vpdn tunnel {pptp | l2tp} {all | hostname remote-name [local-name] | id local-id | ip local-ip-address | ip remote-ip-address}
L2F Tunnels
clear vpdn tunnel l2f {all | hostname nas-name hgw-name | id local-id | ip local-ip-address | ip remote-ip-address}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Manual termination of a VPDN tunnel results in the immediate shutdown of the specified VPDN tunnel and all sessions within that tunnel, resulting in a sudden disruption of VPDN services.
You can shut down VPDN tunnels more gradually by issuing the vpdn softshut command, which prevents the establishment of new VPDN sessions in all VPDN tunnels that terminate on the device. Existing VPDN sessions are not affected.
A manually terminated VPDN tunnel can be restarted immediately when a user logs in. Manually terminating and restarting a VPDN tunnel while VPDN event logging is enabled can provide useful troubleshooting information about VPDN session establishment. VPDN event logging is enabled by issuing the vpdn logging command.
Examples
The following example clears all L2TP tunnels connecting to a remote peer named NAS1:
Router# clear vpdn tunnel l2tp hostname NAS1The following example clears all PPTP tunnels connecting the devices with the hostnames NAS3 and tun1:
Router# clear vpdn tunnel pptp NAS3 hostname tun1The following example clears all L2F tunnels originating from the specified IP address:
Router# clear vpdn tunnel l2f ip 10.1.1.1Related Commands
vpdn logging
Enables the logging of generic VPDN events.
vpdn softshut
Prevents new sessions from being established on a VPDN tunnel without disturbing existing sessions.
clid group
To add a calling line identifier (CLID) group to a discriminator, use the clid group command in CLID configuration mode. To remove a CLID group from a discriminator, use the no form of this command.
clid group {clid-group-name | default}
no clid group {clid-group-name | default}
Syntax Description
Defaults
CLID screening is not used.
Command Modes
CLID configuration
Command History
Usage Guidelines
Use the clid group command to add a CLID group (which specifies the calls to reject) to the discriminator. If you use the default option, CLID call screening is not used.
Examples
The following example shows a call discriminator named "clidElim" created and configured to block digital calls from the CLID group named "zot".
resource-pool profile discriminator clidElimcall-type digitalclid group zotRelated Commands
call-type
Specifies the type of calls you want to block.
resource-pool profile discriminator
Creates a call discrimination profile and assigns it a name.
clock source line
To set the E1 line clock source for the Cisco AS5200 access server, use the clock source line command in controller configuration mode. To change or remove the clocking source, use the no form of this command.
clock source line {primary | secondary}
no clock source line {primary | secondary}
Syntax Description
Defaults
Primary TDM clock source is taken from the E1 controller 0 on the Cisco AS5200.
Secondary TDM clock source is taken from the E1 controller 1 on the Cisco AS5200.
Command Modes
Controller configuration
Command History
Usage Guidelines
Configure the clock source line primary command on the controller that takes the most reliable clocking from an E1 line. Configure the clock source line secondary command on the controller that has the next best known clocking. With this configuration, the primary line clocking is backed up to the secondary line if the primary clocking shuts down.
Examples
The following example configures the Cisco AS5200 to use E1 controller 0 as the primary clocking source and the E1 controller 1 as the secondary clocking source:
controller e1 0framing esflinecode hdb3pri-group timeslots 1-23clock source line primary!controller e1 1framing esflinecode hdb3pri-group timeslots 1-23clock source line secondaryRelated Commands
copy modem
To copy modem firmware to integrated modems in an access server, use the copy modem command in EXEC mode.
copy {flash | tftp | rcp} modem
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Note
The Microcom V.34 modems and Cisco AS5200 V.110 terminal adapter will continue to use the copy modem command. On bootup, because these modems do not require download, the command displays the location of the firmware as "feature_card_flash."After you enable this command, you are asked to provide the download destination (a slot/port or all), the remote host name, and the path leading to the source modem firmware.
If a modem that you want to upgrade is busy with a call when the copy modem command is enabled, the upgrade for that modem yields until the active call is dropped. All other idle modems in the upgrade range proceed with the downloading operation.
Examples
The following example copies the modem firmware file called modem_upgrade from the TFTP server called Modem_Server to modem 2/0, which is installed in a Cisco AS5200 access server:
Router# copy tftp modemModem Numbers (<slot>/<port>[-<slot>/<port>] | group <number> | all)? 2/0Address or name of remote host [UNKNOWN]? Modem_ServerSource file name? dirt/elem/modem_upgradeAccessing file 'dirt/elem/modem_upgrade on Modem_Server...Loading dirt/elem/modem_upgrade .from 192.168.254.254 (via Ethernet0): ! [OK]Loading dirt/elem/modem_upgrade from 192.168.254.254 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 237503/278528 bytes]Router#%MODEM-5-DL_START: Modem (2/0) started firmware download%MODEM-5-DL_GOOD: Modem (2/0) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85As shown in this example, you might want to upgrade and test one modem's firmware before upgrading the firmware of all the modems on the access server, as shown in the next example.
The following example downloads the same modem firmware file from the TFTP server to all the modems in the Cisco AS5200 access server:
Router# copy tftp modemModem Numbers (<slot>/<port>[-<slot>/<port>] | group <number> | all)? allAddress or name of remote host [UNKNOWN]? Modem_ServerSource file name? dirt/elem/modem_upgradeAccessing file 'dirt/elem/modem_upgrade on Modem_Server...Loading dirt/elem/modem_upgrade .from 192.168.254.254 (via Ethernet0): ! [OK]Loading dirt/elem/modem_upgrade from 192.168.254.254 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 237503/278528 bytes]Router#%MODEM-5-DL_START: Modem (2/0) started firmware download%MODEM-5-DL_START: Modem (2/1) started firmware download%MODEM-5-DL_START: Modem (2/2) started firmware download%MODEM-5-DL_START: Modem (2/3) started firmware download%MODEM-5-DL_START: Modem (2/4) started firmware download%MODEM-5-DL_START: Modem (2/5) started firmware download%MODEM-5-DL_START: Modem (2/6) started firmware download%MODEM-5-DL_START: Modem (2/7) started firmware download%MODEM-5-DL_START: Modem (2/8) started firmware download%MODEM-5-DL_START: Modem (2/9) started firmware download%MODEM-5-DL_START: Modem (2/10) started firmware download%MODEM-5-DL_START: Modem (2/11) started firmware download%MODEM-5-DL_START: Modem (2/12) started firmware download%MODEM-5-DL_START: Modem (2/13) started firmware download%MODEM-5-DL_START: Modem (2/14) started firmware download%MODEM-5-DL_START: Modem (2/15) started firmware download%MODEM-5-DL_START: Modem (2/16) started firmware download%MODEM-5-DL_START: Modem (2/17) started firmware download%MODEM-5-DL_START: Modem (2/18) started firmware download%MODEM-5-DL_START: Modem (2/19) started firmware download%MODEM-5-DL_START: Modem (2/20) started firmware download%MODEM-5-DL_START: Modem (2/21) started firmware download%MODEM-5-DL_START: Modem (2/22) started firmware download%MODEM-5-DL_START: Modem (2/23) started firmware download%MODEM-5-DL_GOOD: Modem (2/2) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/10) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/4) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/6) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/7) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/12) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/11) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/13) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/1) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/14) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/19) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/22) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/5) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/8) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/9) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/17) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/0) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/3) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/21) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/16) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/15) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/18) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/20) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85%MODEM-5-DL_GOOD: Modem (2/23) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85The following example copies the modem firmware file called STAR.M from Flash memory to the integrated modem 1/2:
Router# copy flash modemModem Numbers (<slot>/<port> | group <number> | all)? 1/2System flash directory:File Length Name/status1 3539820 as5200-i-m.allcookies2 239203 STAR.M3 23072 BOOT.105 [3802288 bytes used, 4586320 available, 8388608 total]Source file name? STAR.MRouter#%MODEM-5-DL_START: Modem (1/2) started firmware download%MODEM-5-DL_GOOD: Modem (1/2) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85RouterRelated Commands
copy
Copies any file from a source to a destination.
spe
Enters SPE configuration mode and sets the range of SPEs.
corlist incoming
To specify the class of restrictions (COR) list to be used when a specified dial peer acts as the incoming dial peer, use the corlist incoming command in dial-peer configuration mode. To clear the previously defined incoming COR list in preparation for redefining the incoming COR list, use the no form of this command.
corlist incoming cor-list-name
no corlist incoming cor-list-name
Syntax Description
cor-list-name
Name of the dial peer COR list that defines the capabilities that the specified dial peer has when it is used as an incoming dial peer.
Defaults
No default behavior or values.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
The dial-peer cor list and member commands define a set of capabilities (a COR list). These lists are used in dial peers to indicate the capability set that a dial peer has when it is used as an incoming dial peer (the corlist incoming command) or to indicate the capability set that is required for an incoming dial peer to make an outgoing call through the dial peer (the corlist outgoing command). For example, if dial peer 100 is the incoming dial peer and its incoming COR list name is list_100, dial peer 200 has list_200 as the outgoing COR list name. If list_100 does not include all the members of list_200 (that is, if list_100 is not a superset of list_200), it is not possible to have a call from dial peer 100 that uses dial peer 200 as the outgoing dial peer.
Examples
In the following example, incoming calls from 526.... are blocked from being switched to outgoing calls to 1900.... because the COR list for the incoming dial peer (list2) is not a superset of the COR list for the outgoing dial peer (list1):
dial-peer list list1member 900_calldial-peer list list2member 800_callmember other_calldial-peer voice 526 potsanswer-address 408526....corlist incoming list2direct-inward-dialdial-peer voice 900 potsdestination pattern 1900.......direct-inward-dialtrunkgroup 101prefix 333corlist outgoing list1Related Commands
corlist outgoing
Specifies the COR list to be used by outgoing dial peers.
dial-peer cor list
Defines a COR list name.
member
Adds a member to a dial peer COR list.
corlist outgoing
To specify the class of restrictions (COR) list to be used by outgoing dial peers, use the corlist outgoing command in dial-peer configuration mode. To clear the previously defined outgoing COR list in preparation for redefining the outgoing COR list, use the no form of this command.
corlist outgoing cor-list-name
no corlist outgoing cor-list-name
Syntax Description
cor-list-name
Required name of the dial peer COR list for outgoing calls to the configured number using this dial peer.
Defaults
No default behavior or values.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
If the COR list for the incoming dial peer is not a superset of the COR list for the outgoing dial peer, calls from the incoming dial peer cannot use that outgoing dial peer.
Examples
In the following example, incoming calls from 526.... are blocked from being switched to outgoing calls to 1900.... because the COR list for the incoming dial peer (list2) is not a superset of the COR list for the outgoing dial peer (list1):
dial-peer list list1member 900_calldial-peer list list2member 800_callmember other_calldial-peer voice 526 potsanswer-address 408526....corlist incoming list2direct-inward-dialdial-peer voice 900 potsdestination pattern 1900.......direct-inward-dialtrunk group 101prefix 333corlist outgoing list1cpp authentication
Note
To enable negotiation of authentication with a router or bridge that supports the Combinet Proprietary Protocol (CPP) and that is calling in to this router, use the cpp authentication command in interface configuration mode. To disable negotiation of CPP authentication, use the no form of this command.
cpp authentication
no cpp authentication
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.2
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
Use this command for authenticating the device that is calling in to this router.
Use this command to communicate over an ISDN interface with Cisco 700 and 800 series (formerly Combinet) routers that do not support PPP but do support the CPP.
Since most Cisco routers support PPP, Cisco routers can communicate over ISDN with CPP devices by using PPP encapsulation, which supports both routing and fast switching.
This command is supported on ISDN and dialer interfaces.
This command uses names and passwords from the username password command. It does not support TACACS.
Examples
The following example configures a PRI to communicate with a bridge that does not support PPP:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4essinterface Serial1/1:23encapsulation cppcpp callback accept cpp authenticationThe following example configures a BRI to communicate with a bridge that does not support PPP:
interface bri 0 encapsulation cpp cpp callback accept cpp authenticationRelated Commands
cpp callback accept
Note
To enable the router to accept callback from a router or bridge that supports the Combinet Proprietary Protocol (CPP), use the cpp callback accept command in interface configuration mode. To disable callback acceptance, use the no form of this command.
cpp callback accept
no cpp callback accept
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.2
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
Use this command to communicate over an ISDN interface with Cisco 700 and 800 series (formerly Combinet) routers that do not support PPP but do support CPP.
Currently, most Cisco routers do support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.
This command is supported on ISDN and dialer interfaces.
Examples
The following example configures the PRI serial interface 1/1:23 to communicate with a router or bridge that does not support PPP:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4ess!interface Serial1/1:23encapsulation cppcpp callback acceptcpp authenticationThe following example configures BRI 0 to communicate with a router or bridge that does not support PPP:
interface bri 0encapsulation cppcpp callback acceptcpp authenticationRelated Commands
