-
Cisco IOS Dial Technologies Command Reference, Release 12.2
-
Using Cisco IOS Software
-
Commands A through CAS
-
Commands CHA through CPP
-
Commands D
-
Commands EN through IP
-
Commands IS through L2
-
Commands LCP through MOD
-
Commands MU through PPP
-
Commands PRI through SHE
-
Commands SHOW A through SHOW DI
-
Commands SHOW DS through SHOW LI
-
Commands SHOW M through SHOW N
-
Commands SHOW P through SHOW R
-
Commands SHOW S through SHOW V
-
Commands SHU through X
-
Index
-
Table Of Contents
resource-pool aaa accounting ppp
resource-pool call treatment discriminator
resource-pool profile customer
resource-pool profile discriminator
pri-group timeslots
To configure Non-Facility Associated Signaling (NFAS) and specify the channels to be controlled by the primary NFAS D channel, use the pri-group timeslots command in controller configuration mode.
pri-group timeslots range nfas_d [primary | backup | none] nfas_int number nfas_group group-id-number
pri-group timeslots range
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
NFAS allows a single D channel to control multiple PRI interfaces. Use of a single D channel to control multiple PRI interfaces frees one B channel on each interface to carry other traffic. A backup D channel can also be configured for use when the primary NFAS D channel fails. When a backup D channel is configured, any hard system failure causes a switch over to the backup D channel and currently connected calls remain connected.
NFAS is supported only with a channelized T1 controller and, as a result, must be ISDN PRI capable. Once the channelized T1 controllers are configured for ISDN PRI, only the NFAS primary D channel must be configured; its configuration is distributed to all members of the associated NFAS group. Any configuration changes made to the primary D channel will be propagated to all NFAS group members. The primary D channel interface is the only interface shown after the configuration is written to memory.
The channelized T1 controllers on the router must also be configured for ISDN. The router must connect to either an AT&T 4ESS, Northern Telecom DMS-100 or DMS-250, or National ISDN switch type.
The ISDN switch must be provisioned for NFAS. The primary and backup D channels should be configured on separate T1 controllers. The primary, backup, and B-channel members on the respective controllers should be the same configuration as that configured on the router and ISDN switch. The interface ID assigned to the controllers must match that of the ISDN switch.
You can disable a specified channel or an entire PRI interface, thereby taking it out of service or placing it into one of the other states that is passed in to the switch using the isdn service interface configuration command.
In the event that a controller belonging to an NFAS group is shut down, all active B-channel calls on the controller that is shut down will be cleared (regardless of whether the controller is set to primary, backup, or none), and one of the following events will occur:
•
If the controller that is shut down is configured as the primary and no backup is configured, all active calls on the group are cleared.
•
•
•
Note
Examples
The following example configures T1 controller 1/0 for PRI and for the NFAS primary D channel. This primary D channel controls all the B channels in NFAS group 1.
controller t1 1/0framing esflinecode b8zspri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 1Related Commands
profile incoming
To define a template formed by directives guiding the Call Service Module (CSM) to process the digit sequence for a signaling class, use the profile incoming signaling-class submode command.
Note
profile incoming template
Syntax Description
Defaults
No default behavior or values
Command Modes
Signaling-class submode
Command History
Usage Guidelines
Arrange the directive special characters in the order necessary to process the digit sequence for your signaling class.
Examples
The following example enables the profile incoming command:
service internalsignaling-class cas testprofile incoming S<*a<*d<*nRelated Commands
Activates the signaling-class cas command.
Defines a signalling class with a template formed by directives guiding the CSM to process the digit sequence.
protocol rlm port
To configure the RLM port number, use the protocol rlm port command in RLM configuration mode. To disable this function, use the no form of this command.
protocol rlm port port-number
no protocol rlm port port-number
Syntax Description
port-number
RLM port number. See Table 20 for the port number choices.
Defaults
3000
Command Modes
RLM configuration
Command History
Usage Guidelines
The port number for the basic RLM connection can be reconfigured for the entire RLM group. Table 20 lists the default RLM port numbers.
Related Commands
protocol (VPDN)
To specify the tunneling protocol that a virtual private dialup network (VPDN) subgroup will use, use the protocol command in VPDN subgroup configuration mode. To remove the protocol-specific configurations from a VPDN subgroup, use the no form of this command.
protocol {any | l2f | l2tp | pppoe | pptp}
no protocol
Syntax Description
Defaults
No protocol is specified.
Command Modes
VPDN subgroup
Command History
Usage Guidelines
This command is required for any VPDN subgroup configuration.
L2TP is the only protocol that can be used for dialout subgroup configurations.
Changing the protocol will remove all the commands from the VPDN subgroup configuration, and any protocol-specific commands from the VPDN group configuration.
Note
Examples
The following example configures VPDN group 1 to accept dial-in calls using L2F and to request dial-out calls using L2TP:
vpdn-group 1accept-dialinprotocol l2fvirtual-template 1request-dialoutprotocol l2tppool-member 1local name router1terminate-from hostname router2initiate-to ip 10.3.2.1l2f ignore-mid-sequencel2tp ip udp checksumIf you then use the no protocol command in request-dialout mode, the configuration will be changed to this:
vpdn-group 1accept-dialinprotocol l2fvirtual-template 1request-dialoutlocal name router1terminate-from hostname router2l2f ignore-mid-sequenceRelated Commands
range
To associate a range of modems or other physical resources with a resource group, use the range command in resource group configuration mode. To remove a range of modems or other physical resources, use the no form of this command.
range {limit number | limit slot/port | port slot [slot]}
no range {limit number | limit slot/port | port slot [slot]}
Cisco AS5200 and AS5300 Series Routers
range {limit number | limit slot/port | port slot/port [slot/port]}
no range {limit number | limit slot/port | port slot/port [slot/port]}
Syntax Description
Defaults
No range is configured.
Command Modes
Resource group configuration
Command History
Usage Guidelines
Use the range resource group configuration command to associate a range of modems or other physical resources with a resource group.
Specify the range for port-based resources by using the resource's physical location. Do not identify non-port-based resource ranges by using a location. Rather, specify the size of the resource group with a single integer limit.
Specify noncontiguous ranges by using multiple range port commands within the same resource group. Do not configure the same ports in more than one resource group and do not overlap multiple port ranges.
For resources that are not pooled and have a one-to-one correspondence between DS0s, B channels, and HDLC framers, use the range limit number command. Circuit-switched data calls and V.120 calls use these kinds of resources.
Note
Do not configure "port" and "limit" parameters in the same resource group.Examples
The following example shows the range limit set for 48 simultaneous connections being supported by the resource group:
Cisco AS5300
resource-pool group resource hdlc1range limit 48Cisco AS5400
resource-pool group resource hdlcrange limit 2:255 (where 2 is slot#)Cisco AS5800
resource-pool group resource hdlcrange limit 2/0:255 (where 2 is slot# & 0 is subslot#for the trunk card)The following example shows the ports set for modem 1 ranging from port 0 to port 47:
resource-pool group modem1 range port 1/0 1/47rcapi number
To enable the Cisco 800 series router to distinguish between incoming CAPI calls and incoming non-CAPI calls such as POTS, PPP, and X.25, use the rcapi number command in global configuration mode. To release the specified directory number from the RCAPI interface, use the no form of this command.
rcapi number directory-number[:subaddress]
no rcapi number
Syntax Description
directory-number
ISDN directory number. Default is none.
:subaddress
(Optional) Subaddress of the router preceded by a colon (:).
Defaults
The default is no directory number set for the RCAPI interface.
Command Modes
Global configuration
Command History
12.0(7)XV
The commands rcapi number and no rcapi number were introduced on the Cisco 800 series router.
Usage Guidelines
The rcapi number command allows the Cisco 800 series router to reserve directory numbers exclusively for incoming calls.
The directory-number argument is the number assigned by the ISDN provider for the PC on which RCAPI is configured. The directory number should not be set to any other interfaces such as POTS and DOV. This command works only with the Net3 switch type.
Examples
The following example sets the router to recognize an ISDN number rather than a subaddress:
rcapi number 12345Related Commands
rcapi server
To enable the RCAPI server on the 800 series router or to set the TCP port number, use the rcapi server command in global configuration mode. To disable the RCAPI server on the 800 series router, use the no form of this command.
rcapi server [port number]
no rcapi server
Syntax Description
Defaults
If the router is configured for basic Net3 IDSN switch type, by default RCAPI is enabled, and the port number is set to 2578.
Command Modes
Global configuration
Command History
Usage Guidelines
This command works only with the Net3 switch type. The same port number must be configured on both the router and client PC.
Examples
The following example set the TCP port number to 2000:
rcapi server port 2000Related Commands
reload components
To request that the DSC (or DSCs in a redundant configuration) be reloaded at the same time as a reload on the Router Shelf on the Cisco AS5800, use the reload components command in EXEC mode. To cancel a reload, use the reload components cancel command.
reload components {all | description-line | at hh:mm | in [hhh:]mmm}
reload components cancel
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
On the Cisco AS5800 only, to request that the DSC (or DSCs in a redundant configuration) be reloaded at the same time as a reload on the Router Shelf, use the reload components all command.
You cannot reload from a virtual terminal if the system is not set up for automatic booting. This prevents the system from dropping to the ROM monitor and thereby taking the system out of remote user control.
If you modify your configuration file, the system prompts you to save the configuration. During a save operation, the system asks you if you want to proceed with the save if the CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you say "yes" in this situation, the system goes to setup mode upon reload.
When you schedule a reload to occur at a later time, it must take place within approximately 24 days.
The at keyword can only be used if the system clock has be set on the router (either through NTP, the hardware calendar, or manually). The time is relative to the configured time zone on the router. To schedule reloads across several routers to occur simultaneously, the time on each router must be synchronized with NTP.
To display information about a scheduled reload, use the show reload command.
Examples
The following example reloads all components on a Cisco AS5800:
Router# reload components allRelated Commands
request-dialin
To create a request dial-in VPDN subgroup that configures a network access server (NAS) to request the establishment of a dial-in tunnel to a tunnel server, and to enter request dial-in VPDN subgroup configuration mode, use the request-dialin command in VPDN group configuration mode. To remove the request dial-in VPDN subgroup configuration from a virtual private dialup network (VPDN) group, use the no form of this command.
request-dialin
no request-dialin
Syntax Description
This command has no arguments or keywords.
Defaults
No request dial-in VPDN subgroups are configured.
Command Modes
VPDN group configuration
Command History
Usage Guidelines
Use the request-dialin command on a NAS to configure a VPDN group to request the establishment of dial-in VPDN tunnels to a tunnel server.
For a VPDN group to request dial-in calls, you must also configure the following commands:
•
•
•
The NAS can also be configured to accept requests for Layer 2 Tunnel Protocol (L2TP) dial-out VPDN tunnels from the tunnel server using the accept-dialout command. Dial-in and dial-out calls can use the same L2TP tunnel.
Examples
The following example requests an L2TP dial-in tunnel to a remote peer at IP address 172.17.33.125 for a user in the domain named cisco.com:
Router(config)# vpdn-group 1Router(config-vpdn)# request-dialinRouter(config-vpdn-req-in)# protocol l2tpRouter(config-vpdn-req-in)# domain cisco.com!Router(config-vpdn)# initiate-to ip 172.17.33.125Related Commands
request-dialout
To create a request dial-out VPDN subgroup that configures a tunnel server to request the establishment of dial-out Layer 2 Tunnel Protocol (L2TP) tunnels to a network access server (NAS), and to enter request dial-out VPDN subgroup configuration mode, use the request-dialout command in VPDN group configuration mode. To remove the request dial-out VPDN subgroup configuration from a virtual private dialup network (VPDN) group, use the no form of this command.
request-dialout
no request-dialout
Syntax Description
This command has no arguments or keywords.
Defaults
No request dial-out VPDN subgroups are configured.
Command Modes
VPDN group configuration
Command History
Usage Guidelines
Use the request-dialout command on a tunnel server to configure a VPDN group to request the establishment of dial-out VPDN tunnels to a NAS. L2TP is the only tunneling protocol that can be used for dial-out VPDN tunnels.
For a VPDN group to request dial-out calls, you must also configure the following commands:
•
•
•
•
If the dialer pool or dialer rotary group that the VPDN group is in contains physical interfaces, the physical interfaces will be used before the VPDN group configuration.
The tunnel server can also be configured to accept requests to establish dial-in VPDN tunnels from a NAS using the accept-dialin command. Dial-in and dial-out calls can use the same L2TP tunnel.
Examples
The following example configures VPDN group 1 to request an L2TP tunnel to the peer at IP address 10.3.2.1 for tunneling dial-out calls from dialer pool 1:
Router(config)# vpdn-group 1Router(config-vpdn)# request-dialoutRouter(config-vpdn-req-ou)# protocol l2tpRouter(config-vpdn-req-ou)# pool-member 1!Router(config-vpdn)# initiate-to ip 10.3.2.1!Router(config)# interface Dialer2Router(config-if)# ip address 172.16.2.3 255.255.128Router(config-if)# encapsulation pppRouter(config-if)# dialer remote-name reubenRouter(config-if)# dialer string 5551234Router(config-if)# dialer vpdnRouter(config-if)# dialer pool 1Router(config-if)# dialer-group 1Router(config-if)# ppp authentication chapRelated Commands
resource
To assign resources and supported call-types to a customer profile, use the resource command in customer profile configuration mode. To disable this function, use the no form of this command.
resource name {digital | speech | v110 | v120} [service name]
no resource name {digital | speech | v110 | v120} [service name]
Syntax Description
Defaults
No resources are assigned to the customer profile by default.
Command Modes
Customer profile configuration
Command History
Usage Guidelines
Use the resource customer profile configuration command to assign resources and supported call-types to a customer profile. This command specifies a group of physical resources to be used in answering an incoming call of a particular type for a particular customer profile. For example, calls started by analog modems are reciprocated with the speech keyword.
Examples
The following example shows a physical resource group called "modem1". Forty-eight integrated modems are then assigned to modem1, which is linked to the customer profile called "customer1_isp":
resource group resource modem1range port 1/0 1/47exitresource-pool profile customer customer1_ispresource modem1 speechRelated Commands
resource-pool
To enable or disable resource pool management, use the resource-pool command in global configuration mode.
resource-pool {enable | disable}
Syntax Description
Defaults
Resource management is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the resource-pool global configuration command to enable and disable the resource pool management feature.
Examples
The following example shows how to enable RPM:
resource-pool enableresource-pool aaa accounting ppp
To include enhanced start/stop resource manager records to authorization, authentication, and accounting (AAA) accounting, use the resource-pool aaa accounting ppp command in global configuration mode. To disable this feature, use the no form of this command.
resource-pool aaa accounting ppp
no resource-pool aaa accounting ppp
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled. The default of the resource-pool enable command is to not enable these new accounting records.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the resource-pool aaa accounting ppp global configuration command to include enhanced start/stop resource manager records to AAA accounting. The resource-pool aaa accounting ppp command adds new resource pool management fields to the AAA accounting start/stop records. The new attributes in the start records are also in the stop records—in addition to those new attributes added exclusively for the stop records.
If you have configured your regular AAA accounting, this command directs additional information from the resource manager into your accounting records.
Note
Table 21 shows the new fields that have been added to the start and stop records:
Caution
Note
Examples
The following example shows the new AAA accounting start/stop records inserted into an existing AAA accounting infrastructure:
resource-pool aaa accounting pppRelated Commands
show accounting
Allows display of the active accountable events on the network and helps collect information in the event of a data loss on the accounting server.
resource-pool aaa protocol
To specify which protocol to use for resource management, use the resource-pool aaa protocol command in global configuration mode. To disable this feature and go to local, use the no form of this command.
resource-pool aaa protocol {local | group name}
no resource-pool aaa protocol
Syntax Description
local
Local authorization.
group name
Use an external authorization, authentication, and accounting (AAA) server group. The Resource Pool Management Server (RPMS) is defined in a AAA server group.
Defaults
Default is set to local authorization.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the resource-pool aaa protocol global configuration command to specify which protocol to use for resource management. The AAA server group is most useful when you want to have multiple RPMSs configured as a fall-back mechanism.
Examples
The following example shows how to specify local authorization protocol:
resource-pool aaa protocol localresource-pool call treatment
To set up the signal sent back to the telco switch in response to incoming calls, use the resource-pool call treatment command in global configuration mode. To disable this function, use the no form of this command.
resource-pool call treatment {profile {busy | no-answer} | resource {busy | channel-not-available}}
no resource-pool call treatment {profile {busy | no-answer} | resource {busy | channel-not-available}}
Syntax Description
Defaults
No answer for a customer profile; CNA for a resource.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the resource-pool call treatment global configuration command to set up the signal sent back to the telco switch in response to incoming calls.
Examples
Router(config)# resource-pool call treatment profile ?busy Send busy code when profile authorization failsno-answer Don't answer when profile authorization failsresource-pool call treatment discriminator
To modify the signal (ISDN cause code) sent to the switch when a discriminator rejects a call, enter the resource-pool call treatment discriminator command in global configuration mode. To disable this function, use the no form of this command.
resource-pool call treatment discriminator {busy | no-answer | channel-not-available}
no resource-pool call treatment discriminator {busy | no-answer | channel-not-available}
Syntax Description
Defaults
No answer for a customer profile; CNA for a resource.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the resource-pool call treatment discriminator global configuration command to set up the signal sent back to the telco switch in response to incoming calls.
Examples
Use the following command to answer the call, but send a busy signal to the switch when profile authorization or resource allocation fails:
resource-pool call treatment discriminator busyUse the following command to prevent the call from being answered when profile authorization fails and the discriminator rejects a call:
resource-pool call treatment discriminator no-answerresource-pool group resource
To create a resource group for resource management, use the resource-pool group resource command in global configuration mode. To remove a resource group from the running configuration, use the no form of this command.
resource-pool group resource name
no resource-pool group resource name
Syntax Description
name
Name for the group of physical resources inside the access server. This name can have up to 23 characters.
Defaults
No resource groups are set up.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the resource-pool group resource global configuration command to create a resource group for resource management. When calls come into the access server, they are allocated physical resources as specified within resource groups and customer profiles.
See the range command for more information.
If some physical resources are not included in any resource groups, then these remaining resources are not used and are considered to be part of the default resource group. These resources can be used in certain cases to answer calls before profile allocation occurs, but the resources are not used other than in the connection phase.
Note
When enabling RPM for SS7 signalling, like resources in the network access server (NAS) must be in a single group:
•
•
•
•
All resource group types must have the same number of resources and that number must equal the number of interface channels available from the public network switch. This grouping scheme prevents the CNA signal from being sent to the signalling point. For SS7 signalling, Microcom and MICA technologies modems must be in the same group. If SS7 signalling is not used, Cisco recommends assigning Microcom and MICA modems to separate groups to avoid introducing errors in RPM statistics.
Examples
The following example shows the configuration options within a resource group:
Router(config)# resource-pool group resource modem1?Resource Group Configuration Commands:default Set a command to its defaultsexit Exit from resource-manager configuration modehelp Description of the interactive help systemno Negate a command or set its defaultsrange Configure range for resourceRouter(config-resource)# range ?limit Configure the maximum limitport Configure the resource portsRouter(config-resource)# range limit ?<1-192> Maximum number of connections allowedRouter(config-resource)# range port ?<0-246> First Modem TTY Numberx/y Slot/Port for Internal ModemsRelated Commands
resource-pool profile customer
To create a customer profile and to enter customer profile configuration mode, use the resource-pool profile customer command in global configuration mode. To delete a customer profile from the running configuration, use the no form of this comm
