- Overview of Dial Interfaces, Controllers, and Lines
- Configuring Asynchronous Lines and Interfaces
- Asynchronous Call Queueing by Role
- Configuring Asynchronous Serial Traffic Over UDP
- Configuring and Managing Integrated Modems
- 1- and 2-Port V.90 Modem WICs for Cisco 2600 and Cisco 3600 Series Multiservice Platforms
- Call Tracker show Commands Extensions
- Cisco NM-8AM-V2 and NM-16AM-V2 Analog Modem Network Modules with V.92
- MICA and NextPort Modem Tech-Support Command Additions
- PIAFS Wireless Data Protocol Version 2.1 for Cisco MICA Modems
- V.92 and V.44 Support for Digital Modems
- V.92 Modem on Hold for Cisco AS5300 and Cisco AS5800 Universal Access Servers
- V.92 Modem on Hold for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
- V.92 Quick Connect for Cisco AS5300 and Cisco AS5800 Universal Access Servers
- V.92 Quick Connect for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
- V.92 Reporting Using RADIUS Attribute v.92-info
- Configuring and Managing Cisco Access Servers and Dial Shelves
- Configuring and Managing External Modems
- Modem Signal and Line States
- Creating and Using Modem Chat Scripts
- Cisco Modem User Interface
- Modem Script and System Script Support in Large-Scale Dial-Out
- Leased and Switched BRI Interface for ETSI NET3
- ISDN BCAC and Round-Robin Channel Selection Enhancements
- Configuring Virtual Asynchronous Traffic over ISDN
- Configuring Modem Use over ISDN BRI
- Configuring X.25 on ISDN
- Configuring X.25 on ISDN Using AO/DI
- Configuring ISDN on Cisco 800 Series Routers
- Cisco IOS Software Feature Removal
- Configuring ISDN PRI
- Dialing Number Enhancement
- ISDN BCAC and Round-Robin Channel Selection Enhancements
- Configuring ISDN Special Signaling
- Configuring Network Side ISDN PRI Signaling, Trunking, and Switching
- Preparing to Configure DDR
- Configuring Legacy DDR Spokes
- Configuring Legacy DDR Hubs
- Configuring Peer-to-Peer DDR with Dialer Profiles
- Dialer Map VRF-Aware for an MPLS VPN
- Dialer Persistent
- PPPoE Client DDR Idle-Timer
- Redial Enhancements
- Rotating Through Dial Strings
- Configuring Dialer CEF
- CEF Support for Dialer Profiles on Cisco 7500 Routers
- Configuring Snapshot Routing
- Reliable Static Routing Backup Using Object Tracking
- Configuring Dial Backup for Serial Lines
- Configuring Dial Backup Using Dialer Watch
- Dialer Watch Connect Delay
- VRF Aware Dialer Watch
- Configuring Dial Backup with Dialer Profiles
- ISDN Backup in MPLS Core
- Configuring Cisco Easy IP ..
- Configuring Virtual Template Interfaces
- Multiclass Multilink PPP
- Configuring Asynchronous Callback
- Configuring PPP Callback
- Configuring ISDN Caller ID Callback
- Configuring BACP
- Configuring an IP Local Pools Holdback Timer
- Configuring per-User Configuration
- Configuring Resource Pool Management
- Configuring Wholesale Dial Performance Optimization
- Large-Scale Dial-Out
- Dial-Out DS0 Level Trunk Group
- L2TP Large-Scale Dial-Out
- L2TP Large-Scale Dial-Out per-User Attribute via AAA
- Modem Script and System Script Support in Large-Scale Dial-Out
- Large-Scale Dial-Out (LSDO) VRF Aware
- Peer Pool Backup
- Dial Networking Business Applications
- Enterprise Dial Scenarios and Configurations
- Telco and ISP Typical Dial Scenarios and Configurations
- Modem Initialization Strings
Redial Enhancements
|
|
|
This document describes the Redial Enhancements feature for Cisco IOS Release 12.2(4)T. It includes the following sections:
Feature Overview
The Redial Enhancements feature improves the performance of redial and provides greater control over redial behavior. The dialer will now cycle through all matching dialer strings or dialer maps before applying the redial interval, and may select a different physical dialer on each redial attempt. New dial-out attempts will not be initiated if a redial to the same destination is pending. The dialer can now be configured to apply a disable timer without performing any redial attempts, and a disable time can be applied to a dialer profile interface and to a serial dialer.
By default, the Cisco IOS software considers a call successful if it connects at the physical layer (Layer 1 of the OSI reference model). However, problems such as poor quality telco circuits or peer misconfiguration can cause dial-out failure even though a connection is made at the physical layer. The Redial Enhancements feature introduces a new command that allows the router to be configured to wait a specific amount of time for a line protocol to come up before considering a dial-out attempt successful. If the timer runs out or the call is dropped before the line protocol comes up, the call is considered unsuccessful. Unsuccessful dial-out attempts will trigger redial if the redial options have been configured.
Benefits
The Redial Enhancements feature will reduce dialer congestion by preventing additional dial-out attempts to any locations which have a redial attempt pending. This can reduce your telco bills by limiting unecessary dial-out attempts. In addition, the router may now be configured to wait for the line protocol to come up before considering a dial-out attempt successful.
Restrictions
The dialer wait-for-line-protocol command is supported only with the PPP encapsulation protocol.
Related Documents
Supported Platforms
- Cisco 800 series
- Cisco 1000 series
- Cisco 1600 series
- Cisco 2500 series
- Cisco 2600 series
- Cisco 3600 series
- Cisco 7200 series
- Cisco 7500 series
Platform Support Through Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Feature Navigator. Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image.
To access Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, e-mail the Contact Database Administration group at cdbadmin@cisco.com. If you want to establish an account on Cisco.com, go to http://www.cisco.com/register and follow the directions to establish an account.
Feature Navigator is updated when major Cisco IOS software releases and technology releases occur. As of May 2001, Feature Navigator supports M, T, E, S, and ST releases. You can access Feature Navigator at the following URL:
Supported Standards, MIBs, and RFCs
No new or modified standards are supported by this feature.
No new or modified MIBs are supported by this feature.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Configuration Tasks
See the following sections for configuration tasks for the Redial Enhancements feature. Each task in the list is identified as either required or optional:
- Configuring Redial Options (optional)
- Configuring the Dialer to Wait for a Line Protocol (optional)
- Verifying Redial Configuration (optional)
Configuring Redial Options
To configure redial options, use the following commands beginning in global configuration mode:
|
|
|
|
|---|---|---|
Router(config-if)# dialer redial interval time attempts number re-enable disable-time |
Configuring the Dialer to Wait for a Line Protocol
To configure the router to wait for a line protocol after connecting to the physical layer, use the following commands beginning in global configuration mode:
|
|
|
|
|---|---|---|
Configures the router to wait for a line protocol after connecting to the physical layer. |
Verifying Redial Configuration
To verify the configuration of redial options, perform the following steps:
Step 1
Initiate a dial-out attempt to a location that is likely to fail to connect on the first attempt.
Step 2 Enter the debug dialer events command. The following debug output results from a dial-out attempt that failed to connect on both the initial attempt and two redial attempts:
Target IP address:10.0.0.2
Repeat count [5]:1
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
*Mar 1 02:26:52.567:BR0/0 DDR:rotor dialout [priority]
*Mar 1 02:26:52.567:BR0/0 DDR:Dialing cause ip (s=10.0.0.1, d=10.0.0.2)
*Mar 1 02:26:52.567:BR0/0 DDR:Attempting to dial 6109
*Mar 1 02:26:52.739:BRI0/0:wait for isdn carrier timeout, call id=0x800B
*Mar 1 02:26:52.739:Di1 DDR:Redial:Created for ip (s=10.0.0.1, d=10.0.0.2).
!This is new debug output specific to redial configuration.
Success rate is 0 percent (0/1)
led#
*Mar 1 02:27:22.739:Di1 DDR:Redial:Timeout
!This is new debug output specific to redial configuration.
*Mar 1 02:27:22.739:BR0/0 DDR:rotor dialout [priority]
*Mar 1 02:27:22.739:Di1 DDR:Redialing on BR0/0 for ip (s=10.0.0.1, d=10.0.0.2) (attempt 1)
!This is new debug output specific to redial configuration.
*Mar 1 02:27:22.739:BR0/0 DDR:Dialing cause ip (s=10.0.0.1, d=10.0.0.2)
*Mar 1 02:27:22.739:BR0/0 DDR:Attempting to dial 6109
*Mar 1 02:27:22.939:BRI0/0:wait for isdn carrier timeout, call id=0x800C
led#
*Mar 1 02:27:52.939:Di1 DDR:Redial:Timeout
!This is new debug output specific to redial configuration.
*Mar 1 02:27:52.939:BR0/0 DDR:rotor dialout [priority]
*Mar 1 02:27:52.939:Di1 DDR:Redialing on BR0/0 for ip (s=10.0.0.1, d=10.0.0.2) (attempt 2)
!This is new debug output specific to redial configuration.
*Mar 1 02:27:52.939:BR0/0 DDR:Dialing cause ip (s=10.0.0.1, d=10.0.0.2)
*Mar 1 02:27:52.939:BR0/0 DDR:Attempting to dial 6109
*Mar 1 02:27:53.135:BRI0/0:wait for isdn carrier timeout, call id=0x800D
*Mar 1 02:27:53.139:Di1 DDR:Redial:Removed for ip (s=10.0.0.1, d=10.0.0.2) (2 attempts tried)
!This is new debug output specific to redial configuration.
led#
The following debug output results from a dial-out attempt that failed to connect initially, but succeeded on the first redial attempt:
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
The following debug output results from a call that failed to connect to a line protocol during either the initial dial-out attempt or the first redial attempt. The connection was successfully made on the second redial attempt. The router was configured with both the dialer wait-for-line-protocol and dialer redial commands. In this example, the dialer wait-for-line-protocol command was configured to wait 10 seconds for the line protocol to come up.
!This is new debug output specific to waiting for a line protocol to come up.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to waiting for a line protocol to come up.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
!This is new debug output specific to redial configuration.
Configuration Examples
This section provides the following configuration examples:
Dialer Redial Example
The following example configures redial options on the dialer:
Dialer Wait-for-Line-Protocol Example
The following example configures the dialer to wait for a line protocol after making a physical connection:
Command Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Dial Technologies Command Reference at http://www.cisco.com/en/US/docs/ios/dial/command/reference/dia_book.html . For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
Feedback