Cisco IOS Dial Technologies Command Reference

 

Syntax Description

 

Command Default

Default modem settings. (The country-name keyword northamerica was the default in Cisco IOS releases earlier than release 12.0(3)XG; usa is the default country keyword for Cisco IOS Release 12.0(3)XG and later releases.)

 

Command History

 

Usage Guidelines

Use the call progress tone country configuration to specify the country for call progress tone generation. While in many cases the country is chosen automatically on the basis of the modem setting, automatic selection does not work for all users because many modems do not support all countries and many users choose the “us” or “default-t1” or “default-e1” setting on their modem.

This command affects the tones generated at the local interface and does not affect any information passed to the remote end of a connection or any tones generated at the remote end of a connection.

For dial platforms (AS5200, AS5300, and AS5800), call progress tones are used only for the resource pool management application. Resource pool management assumes that the call progress tone selection is global. Select only one call progress tone set, and it will globally override country settings on all ports.

Examples

The following example shows the call progress tone set for Japan tone parameters:

 

Related Commands

 

Syntax Description

This command has no arguments or keywords.

 

Command Default

The forced waiting period is not set.

 

Command History

 

Usage Guidelines

Use this command when the router is calling back a modem that initiated a call, then dropped the connection, but requires a rest period before subsequent input is accepted.

Examples

The following example sets a waiting period during which a callback chat script is delayed from being sent on an outgoing target line:

 

Related Commands

 

Syntax Description

 

Defaults

5000 ms

 

Command History

 

Usage Guidelines

Use the callback nodsr-wait command when the dial-out modem takes longer than 5000 ms to drop a carrier after the router signals a hang-up on the incoming call.

Increase the duration of the callback if the debug callback command displays the following failed callback attempt message:

callback process fail - timeout with DSR up

Examples

The following example sets the callback duration to 10 seconds for lines 1/0 to 1/107:

 

Related Commands

 

Syntax Description

 

Command Default

Disabled

 

Command History

 

Usage Guidelines

A called party number is a telephone number that is used to reach a remote destination. For example, a mobile laptop dials a called party number to reach the POP of an ISP. Some ISPs set up several called party numbers to enable remote clients to dial in, but to the end user, it appears and functions as one unified service.

Cisco’s implementation of a called party number is based on the dialed number identification service (DNIS). You can configure multiple DNIS numbers in a single modem pool. However, the same DNIS number cannot be used in multiple modem pools. Each modem pool must be assigned different DNIS numbers.

Use the max-conn option to provide overflow protection, which specifies a maximum number of simultaneous connections that a called party number can consume. For example, if you create one modem pool to serve two or more services or customers, this option guarantees how many modems each service or customer can have access to at any given time.

The Cisco IOS software also includes a feature that simplifies the called number configuration. By using an x variable as the last digit in a called telephone number (for example, issuing the called-number 408555121x command), clients dialing different called numbers such as 4085551214 or 4085551215 will automatically be sent to the same modem pool. The x variable is a floating place holder for digits 1 through 9.

Note Modem pools using MICA technologies or Microcom modems support incoming analog calls over ISDN PRI. However, only MICA modems support modem pooling for CT1 and CE1 configurations with channel associated signaling.

Examples

In the following example, the modem pool called v90service is virtually partitioned between two customers using different DNIS numbers. The pool-range command assigns modems 1 to 110 to the shared modem pool. The called-number 5550112 max-conn 55 command assigns the DNIS number 5550112 to the v90service modem pool. The total number of simultaneous connections is limited to 55. The called-number 5550132 max-conn 55 command assigns the DNIS number 5550132, which is for a different customer, to the same v90service modem pool. The total number of simultaneous connections is also set to 55.

The following configuration rejects the pool-range 30 command because modem TTY line 30 is already a member of the modem pool v90service, which was configured in the previous example. Each modem in the access server is automatically assigned to a unique TTY line. TTY line numbers are assigned according to your shelf, slot, or port hardware configuration.

 

Related Commands

 

Syntax Description

 

Command Default

Call Tracker call record logging is disabled.

 

Command History

 

Usage Guidelines

Syslog call records will be generated in the order of ten seconds of call termination. A small delay is needed to ensure that all subsystems finish reporting all appropriate information on call termination. Furthermore, the process of logging is considered a very low priority with respect to normal call processing and data routing. As such, logging all call records can be guaranteed if Call Tracker is properly configured. However, the delay from the time a call actually terminated can vary if the CPU is busy handling higher-priority processes.

Call Tracker records must be found within the History table for at least one minute after call termination for this capability to work. As such, one must ensure that Call Tracker history collection is not disabled with the calltracker history configuration options.

Because the call rates possible on a high-capacity access server can be rather large and the information provided by the call records is substantial, simply enabling normal syslog call records can make the use of the console difficult. As such, by using the quiet option and having a syslog server configured to capture the call records, the console can be freed from displaying any call records, yet still have the call records captured by a syslog server.

The following informational logs are available:

• CALL_RECORD provides generic data information shared for all call categories. This record is generated for both terse and verbose configuration options.
• MODEM_CALL_RECORD provides overall modem call information for modem calls only. This record is generated for both terse and verbose configuration options.
• MODEM_LINE_CALL_REC provides modem transport physical layer information used to debug modem connection problems for modem calls only. This record is generated for the verbose configuration option only.
• MODEM_INFO_CALL_REC provides modem status information used to debug modem problems for modem calls only. This record is generated for the verbose configuration option only.
• MODEM_NEG_CALL_REC provides client-host negotiation information used to debug modem negotiation problems for modem calls only. This record is generated for the verbose configuration option only.

Examples

The following example reports the Verbose Call Records for a normal modem call termination:

 

Related Commands

 

Syntax Description

This command has no arguments or keywords.

 

Command Default

Call Tracker is not enabled.

 

Command History

 

Usage Guidelines

To enable real-time call statistics from the MICA technologies modem to Call Tracker, you must configure the modem link-info poll time command.

Examples

The following example shows how to enable the Call Tracker feature:

 

Related Commands

 

Syntax Description

 

Command Default

The default maximum is dynamically calculated to be 1 times the maximum DS0 supported on a platform.

 

Command History

 

Usage Guidelines

Be careful when extending the maximum number of call entries stored in the Call Tracker history table, as this activity causes Call Tracker to use more memory resources to store the additional call data. Network access server memory consumption must be considered when increasing this parameter. The active call table is not affected by this command.

Examples

The following example sets the history table size to 50 calls:

 

Related Commands

 

Syntax Description

 

Defaults

The default number of minutes is 5000.

 

Command History

 

Usage Guidelines

Active calls are not affected by this command. Entries in the active table are retained as long as the calls are connected.

Examples

The following example sets the retention time for the history table to 5000 minutes:

 

Related Commands

 

Syntax Description

This command has no arguments or keywords.

 

Command Default

The default value of the call setup time does not contain milliseconds. It is in the hh:mm:ss form.

 

Command History

 

Usage Guidelines

This AS5400 command is used to add a milliseconds time stamp (hh:mm:ss.ms) to call detail records. These call records of originating and terminating calls are written to flat files on the subscriber server. These files may be passed periodically from the subscriber to the publisher server. Third-party applications such as billing and accounting use CDR data.

All calltracker commands (including calltracker timestamp) are only supported for dial services and not for voice.

Examples

The following configuration example shows calltracker options and a display of calltracker active including time stamp:

 

Related Commands

 

Syntax Description

 

Command Default

All calls are accepted by the network access server.

 

Command History

 

Usage Guidelines

Use the call-type call discriminator command to reject particular types of calls. Call type all is mutually exclusive for all other call types. If call type all is set in the discriminator, no other call types are allowed. Also, once a DNIS is associated with a call type in a discriminator, it cannot be used in any other discriminator.

Examples

The following example shows the call discriminator being configured to reject speech calls for the call discriminator profile named “userd3”:

 

Syntax Description

 

Command Default

No default behavior or values.

 

Command History

 

Usage Guidelines

Use the call-type cas DNIS group configuration command to set the call-type override. From the resource pooling call-type perspective, use CT1 (CAS) to support either analog calls (speech) or digital calls (switched 56K).

Switched 56K calls are digital calls that connect to High-Level Data Link Control (HDLC) framers. Unlike ISDN, it is impossible to communicate the call type in CT1. Therefore, switched 56K services in CT1 can be differentiated by the DNIS numbers. This command identifies that the call arriving with the DNIS in the DNIS group is assigned to the call type specified in the command.

Examples

The following example shows the DNIS group configuration mode being accessed to use the call-type cas command to set the call type override for CAS to speech :

 

Syntax Description

 

Command Default

No customized signaling parameters are set. If you do not specify a country name using the country name command, which is described in Table 1 , ITU is the selected default signal.

 

Command History

 

Usage Guidelines

The customization parameters set by the cas-custom channel command are applied to the same channel group number used in the cas-group channel timeslots range type signal command. These channel group numbers must match. Otherwise, the customized features specified by the cas-custom command will not be applied to the cas-group command’s configuration. The signaling customization will not take effect. See Example 1 (T1).

However, you will not need to configure or set more than one channel group number per E1 line in most cases. Though rarely used, it is possible to split a single E1 (time slots from 1 to 31) into two groups (for example, time slots from 1 to 15 on group 1 and time slots from 17 to 31 in group 2).

Cisco strongly recommends that you use the optional use-defaults keyword when specifying a particular country type; see the country name command in Table 1 . This additional keyword ensures that all the local country settings are correctly enabled. For example, issue the country greece use-defaults command. If the use-defaults option is not specified, generic ITU will be the default setting for all countries. See Example 2 (E1 on AS5800).

You can configure the system to deviate from a country’s default settings as defined by Cisco. To do this, choose from the following list of commands described in Table 1 : ani-digits min number max number, answer-signal { group-a | group-b } number, caller-digits number, category number, dnis-digits min number max number, invert-abcd, ka number, kd number, metering, nc-congestion, and unused-abcd value. To return a country back to its country specific default settings, issue the country name use-defaults command. To return a country back to the ITU standard, issue the default country name use-defaults command. See Example 4 (Localized E1 R2) and Example 7 (E1 R2 Country Defaults).

From Cisco IOS Release 12.3(11)YK and Cisco IOS Release 12.4(2)T, you can block incoming collect calls for in-line signaling with the double-answer feature, which is activated by entering the double-answer keyword. The double-answer feature sends the incoming collect call through a series of answer functions that can last up to two seconds and which causes the switch to drop the collect call while the normal calls stay connected.

See Example 8 (E1 Collect Call Blocking).

Note Incoming collect calls in Brazil send a II-8 response and to block such calls, a category B-7 response is sent instead of the usual answer signal. This is known as category based blocking. Brazil is the only country that supports category based call blocking. If the double-answer feature is configured for Brazil, it will overwrite the category blocking and will not send the category B7 response.

From Cisco IOS Release 15.3(1)T, calls will be considered as collect calls based on the user dialed numbers. If the dialed numbers have a specific pattern (9090xxxx, in case of Brazil), these calls will be classified as collect calls. Whenever an Interrupt Service Router (ISR) receives collect calls over Session Initiation Protocol (SIP) trunks with the request uniform resource identifier (URI) having the unique pattern, on the E1 R2 side, the caller category is indicated with a II-8 response. For this, a configurable dial pattern needs to be added to the ISR device.

The Collect Call Digit Pattern feature is limited to Brazil only; hence, the position of the ISR device in the Brazilian telecom network is moved slightly closer to the Public Switched Telephone Network (PSTN) so that the ISR device can initiate the outbound collect call on the E1 R2 side towards the customer premises equipment (CPE). See Example 6 (E1 Collect Call Digit Pattern).

Note Only integrated Cisco MICA technologies modems support E1 R2 signaling on Cisco 5000 series access servers and Cisco 3600 series devices.

Table 1 shows a list of command options in cas-custom mode, which is used to customize R2 signaling settings.

Examples

Example 1 (T1)

The following example shows how to configure this feature on channel 1:

Example 2 (E1 on AS5800)

The following example shows how to configure the available signaling parameters after you enter cas-custom mode; the same channel group 1 is specified in the ds0-group command and the cas-custom command.

Example 3 (E1)

The following is sample output from available signaling parameters in cas-custom mode; the same channel group 1 is specified in the cas-group command and the cas-custom command.

Example 4 (Localized E1 R2)

You can localize your R2 configuration for a specific country. Do not forget to include the use-defaults option as described in Table 1 . For example, use the country argentina use-defaults command for a R2 scenario in Argentina.

Example 5 (Collect ANI Digits)

The following example shows how to customize the signaling for channel group 1. The configuration collects three digits before it requests ANI information for analog calls received on a Cisco AS5800 in Argentina.

Example 6 (E1 Collect Call Digit Pattern)

The following example shows how to configure the collect call digit pattern and the time out value for the double answer duration. The timer value determines the waiting time for the second answer after receiving the first answer signal for collect call scenarios.

Example 7 (E1 R2 Country Defaults)

Because cas-custom mode gives you the flexibility to customize R2 parameters, the margin for user error increases. Therefore, the Cisco IOS software enables you to return a country back to its default R2 settings using the use-defaults option. The following configuration brings up the Argentina default settings, changes a few customization parameters, then returns the Argentina R2 setting back to its original state.

Example 8 (E1 Collect Call Blocking)

The following example shows how to configure the double-answer feature for incoming collect call blocking on the Cisco 2801 with R2 digital signaling with DTMF. The call blocking feature is for all countries.

To disable call blocking, use the no form of this command:

 

Related Commands

 

Syntax Description

 

Command Default

No CAS is configured on the controller. All R2 signaling types have DNIS turned on by default.

 

Command History

 

Usage Guidelines

Use this command to configure support for incoming and outgoing call signals (such as on-hook and off-hook) on each E1 controller.

If you specify the time slot range 1-31, the system software automatically uses the 16th time slot to transmit the channel associated signaling.

The signaling you configure on the access server must match the signaling used by the central office. For example if the central office switch is forwarding R2 analog signaling to a Cisco AS5800, then the access server’s E1 controller must also be configured for R2 analog signaling ( r2-analog).

All R2 signaling options have DNIS support turned on by default. If you enable the ani option, the collection of DNIS information is still performed. Specifying the ani option does not disable DNIS. DNIS is the number being called. ANI is the caller’s number. For example, if you are configuring router A to call router B, then the DNIS number is router B, the ANI number is router A. ANI is very similar to Caller ID.

To customize the R2 signaling parameters, refer to the cas-custom controller configuration command. When you enable the cas-group command, the cas-custom command is automatically setup to be polled for configuration information. However, unless you enable or turn on specific features with the cas-custom command, the cas-custom feature has an empty set of signaling parameters.

Note Only integrated MICA modems support E1 R2 signaling on Cisco access servers.

DNIS is automatically collected for modem pools and R2 tone signaling. You do not need to specify the collection of DNIS information with the cas-group command. However, if you are using non-R2 tone signaling, the system must be manually configured to collect DNIS information. For non-R2 cas signaling, DNIS collection is done only for E&M-fgb.

Examples

In most cases, you will configure the same channel-associated signaling on each E1 controller. The following examples configure signaling and customized parameters on controller E1 2 using the cas-group and cas-custom controller configuration commands.

The following example configures the E1 controller on a Cisco 5800 series access server.
To configure a Cisco 3600 series access server, replace the command:

controller e1 2/1/0

with the command:

controller e1 2

Note The actual channel associated signaling is configured on the 16th time slot, which is the reason why this time slot does not come up in the following output.

The following example shows all the supported E1 signaling types on a Cisco AS5800:

R2 signaling parameters can be customized with the cas-custom controller configuration command:

 

Syntax Description

 

Command Default

For ISDN PRI, the cas-group command is disabled.

If the channelized T1 is not configured as a PRI, the default value for line signaling is e&m-fgb and the default value for tone signaling is DTMF.

The R1 signaling default value is ani-dnis.

 

Command History

 

Usage Guidelines

Use the cas-group command to configure T1 controllers with different types of robbed-bit signaling, such as on-hook and off-hook for E&M feature group B ( e&m-fgb).

If you want to collect DNIS information on a T1 controller, you must manually configure it on the access server. DNIS collection is performed only for E&M-fgb. To collect DTMF DNIS for E&M-fgb under a controller T1 configuration, enter the cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis command. To collect MF DNIS for E&M-fgb, enter the cas-group 0 timeslots 1-24 type e&m-fgb mf dnis command.

Examples

The following example configures all 24 channels with ear and mouth robbed-bit signaling with feature group B support:

The following example configures the required signaling to support modem pooling and the digital number identification service (DNIS) over channelized T1 lines on a Cisco AS5300. The only supported signaling and tone types for modem pooling over CT1 RBS are E&M feature group B, DTMF tones, and MF tones. By configuring DNIS as part of the cas-group command, the system can collect DNIS digits for incoming calls, which can be redirected to specific modem pools setup for different customers or services. Additionally, you must be running MICA modems in the system and have at least 10% of your total modems in the default modem pool. Free modems are needed in the default pool to detect the incoming called number or DNIS before handing the call off to the appropriate modem pool. Therefore, two modems are actually needed to handle each incoming call.

Note Make sure that your switch provides inband address information for incoming analog calls before you enable this feature.

The following example configures a Cisco AS5200 to accept switched 56K digital calls on both of its T1 controllers:

The following example configures switched 56K digital services and analog modem services on one controller. Each service is assigned its own range of timeslots. Switched 56K calls are assigned to timeslots 1 through 15. Analog modem calls are assigned to timeslots 16 through 24. However, you must use different channel group numbers in each cas-group command entry.

The following example configures R1 signaling on a Cisco AS5200 (T1 interface) and specifies the collection of both ANI and DNIS information:

The following example configures R1 modified signaling on a Cisco AS5800 (T1 interface) and specifies the collection of both ANI and DNIS information:

 

Syntax Description

 

Defaults

The modem data profile is not configured.

 

Command History

 

Usage Guidelines

Multiple Profiles are supported on both the 819 ISR and EHWICs.

Examples

The following example shows how to create a modem profile:

 

Related Commands

 

Syntax Description

 

Defaults

None.

 

Command History

Examples

The following example shows the deletion of all SMS messages in memory:

 

Related Commands

 

Syntax Description

 

Defaults

None.

 

Command History

Examples

The following example shows the deletion of all SMS messages in memory:

 

Related Commands

 

Syntax Description

 

Defaults

None.

 

Command History

 

Usage Guidelines

A user is allowed to send a 4G LTE band SMS message to other valid recipients only if they have a valid text message plan.

Examples

The following example shows how the cellular lte sms send command can be configured:

 

Related Commands

 

Syntax Description

 

Command History

 

Usage Guidelines

If the all keyword is used, messages are truncated to show a preview. If the specific ID of a text message is used, then the full contents of the text are displayed.

Examples

The following example shows how to set the DBE to deactivate in quiesce mode to prepare the device for hardware maintenance:

 

Related Commands

 

Syntax Description

 

Command Default

The T1/E1 line is connected to the Motorola MPC-860x processor serial communication controller (SCC) or network module with two voice or WAN interface card (VIC or WIC) slots and 0/1/2 FastEthernet ports DSCC4 by default on Cisco 2600 series, Cisco 2600XM, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745 routers.

There is no default behavior or values on the Cisco SLT (Cisco 2611).

The serial interface object encapsulation is set to HDLC on a network access server (NAS) (Cisco AS5350 and Cisco AS5400 series routers).

The default line speed is 56 kbps when a T1 controller is configured on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.

The default line speed is 64 kbps when an E1 controller is configured on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.

 

Command History

 

Usage Guidelines

Use this command to direct HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card. A channel group is created using Advanced Integration Module (AIM) HDLC resources when a channel-group command with the aim keyword is parsed during system initialization or when the command is entered during configuration. You must specify the aim keyword under a T1/E1 controller port to direct HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745.

Note Neither the Cisco AS5400 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 Channel groups, channel-associated signaling (CAS) voice groups, DS0 groups, and time-division multiplexing (TDM) groups all use group numbers. All group numbers configured for channel groups, CAS voice groups, and TDM groups must be unique on the local Cisco MC3810 concentrator. For example, you cannot use the same group number for a channel group and for a TDM group. Furthermore, on the Cisco MC3810, only one channel group can be configured on a controller.

The channel group number can be 0 or 1 on the Cisco SLT (Cisco 2611) and Cisco ASR 901 Series Aggregation Services Routers.

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:

The following example explicitly sets the encapsulation type to PPP to override the HDLC default:

The 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:

The following example defines three channel groups. Channel-group 0 consists of a single time slot, channel-group 8 consists of seven time slots and runs at a speed of 64 kbps per time slot, and channel-group 12 consists of two time slots.

The following example configures a channel group on controller T1 0 on a Cisco MC3810:

The following example configures a channel group on controller E1 1 and specifies that all time slots are used for data:

The following example configures a channel group on controller T1 0/0 and specifies the time slots:

Note SS7 digital F-link support for the 8PRI line card requires use of a third onboard TDM stream to route trunk DS0 messages to the onboard MGCs.

 

Related Commands

 

Syntax Description

 

Command Default

No chat scripts are defined.

 

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:

• Chat scripts are case sensitive.
• You can have any number of ABORT sequences active at once.
• When a chat script starts, the default timeout is 5 seconds. Changes to the timeout persist until the next time you change them in the script.
• A string within quotation marks is treated as a single entity.

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.32 bis modulation, you would name your chat script telebit-t3000-v32bis.

The chat-script command could be written as follows:

Adhering 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 2 .

Expect-Send Pairs

Sample supported expect-send pairs are described in Table 3 .

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:

This 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 :

 

Related Commands

 

Syntax Description

 

Command Default

No signaling class structures are defined.

 

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:

 

Related Commands

 

Syntax Description

This command has no arguments or keywords.

 

Command History

Examples

There is no display generated, but the counters in the show cot summary command would be all zeros.

 

Related Commands

 

Syntax Description

 

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.

 

Related Commands

 

Syntax Description

 

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.

 

Related Commands

 

Syntax Description

 

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:

 

Syntax Description

 

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.

 

Related Commands

 

Syntax Description

This command has no arguments or keywords.

 

Command History

Examples

The following example shows how to use the clear dialer sessions command:

 

Related Commands

 

Syntax Description

 

Command Default

If no option is specified, all control, data, and inter-process communication counters or tracing buffers are cleared.

 

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):

 

Related Commands

 

Syntax Description

 

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.

 

Related Commands

 

Syntax Description

 

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:

 

Related Commands

 

Syntax Description

 

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:

 

Syntax Description

 

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:

 

Syntax Description

 

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:

The following is an example of using the clear modem all command:

The following examples of the clear modem group command clear the manageable modems in group 1:

The following example executes the clear modem at-mode command from a Telnet session:

The following example executes the clear modem at-mode command from a second Telnet session while the first Telnet session is connected to the modem: