Table Of Contents

pri-group timeslots

profile incoming

protocol (VPDN)

range

rcapi number

rcapi server

redirect identifier

redundancy

reload components

request-dialin

request-dialout

resource

resource-pool

resource-pool aaa accounting ppp

resource-pool aaa protocol

resource-pool call treatment

resource-pool call treatment discriminator

resource-pool group resource

resource-pool profile customer

resource-pool profile discriminator

resource-pool profile service

resource-pool profile vpdn

retry keepalive

rotary

rotary-group

pri-group timeslots

To specify an ISDN PRI group on a channelized T1 or E1 controller, and to release the ISDN PRI signaling time slot, use the pri-group timeslots command in controller configuration mode. To remove or change the ISDN PRI configuration, use the no form of this command.

pri-group timeslots timeslot-range [nfas_d {backup | none | primary {nfas_int number | nfas_group number | rlm-group number}} | service]

no pri-group timeslots timeslot-range [nfas_d {backup | none | primary {nfas_int number | nfas_group number | rlm-group number}} | service]

Syntax Description

timeslot-range	A value or range of values for time slots on a T1 or E1 controller that consists of an ISDN PRI group. Use a hyphen to indicate a range. Note Groups of time slot ranges separated by commas (1-4,8-23 for example) are also accepted.
nfas_d {backup | none | primary}	(Optional) Configures the operation of the ISDN PRI D channel. •backup—The D-channel time slot is used as the Non-Facility Associated Signaling (NFAS) D backup. •none—The D-channel time slot is used as an additional B channel. •primary—The D-channel time slot is used as the NFAS D primary. The primary keyword requires further interface and group configuration:
primary {nfas_int number | nfas_group number | rlm-group number}	–nfas_int number—Specifies the provisioned NFAS interface as a value; value is a number from 0 to 8. –nfas_group number—Specifies the NFAS group. –rlm-group number—Specifies the Redundant Link Manager (RLM) group and release the ISDN PRI signaling channel.
service	(Optional) Configures service type mgcp for Media Gateway Control Protocol service.

Defaults

No ISDN PRI group is configured. The switch type is automatically set to the National ISDN switch type (primary-ni keyword) when the pri-group timeslots command is configured with the rlm-group subkeyword.

Command Modes

Controller configuration

Command History

Release	Modification
11.0	This command was introduced.
11.3	This command was enhanced to support NFAS.
12.0(2)T	This command was implemented on the Cisco MC3810 multiservice concentrator.
12.0(7)XK	This command was implemented on the Cisco 2600 and Cisco 3600 series routers.
12.1(2)T	The modifications in Cisco IOS Release 12.0(7)XK were integrated into Cisco IOS Release 12.1(2)T.
12.2(8)B	This command was modified with the rlm-group subkeyword to support release of the ISDN PRI signaling channels.
12.2(15)T	The modifications in Cisco IOS Release 12.2(8)B were integrated into Cisco IOS Release 12.2(15)T.

Usage Guidelines

The pri-group command supports the use of DS0 time slots for Signaling System 7 (SS7) links, and therefore the coexistence of SS7 links and PRI voice and data bearer channels on the same T1 or E1 span. In these configurations, the command applies to voice applications.

In SS7-enabled Voice over IP (VoIP) configurations when an RLM group is configured, High-Level Data Link Control (HDLC) resources allocated for ISDN signaling on a digital subscriber line (DSL) interface are released and the signaling slot is converted to a bearer channel (B24). The D channel will be running on IP. The chosen D-channel time slot can still be used as a B channel by using the isdn rlm-group interface configuration command to configure the NFAS groups.

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 switchover 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 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.

•If the controller that is shut down is configured as the primary, and the active (In service) D channel is the primary and a backup is configured, then the active D channel changes to the backup controller.

•If the controller that is shut down is configured as the primary, and the active D channel is the backup, then the active D channel remains as backup controller.

•If the controller that is shut down is configured as the backup, and the active D channel is the backup, then the active D channel changes to the primary controller.

The expected behavior in NFAS when an ISDN D channel (serial interface) is shut down is that ISDN Layer 2 should go down but keep ISDN Layer 1 up, and that the entire interface will go down after the amount of seconds specified for timer T309.

---

Note The active D channel changeover between primary and backup controllers happens only when one of the link fails and not when the link comes up. The T309 timer is triggered when the changeover takes place.

---

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/0

 framing esf

 linecode b8zs

 pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 1 

The following example specifies ISDN PRI on T1 slot 1, port 0, and configures voice and data bearer capability on time slots 2 through 6:

isdn switch-type primary-4ess

controller t1 1/0

 framing esf

 linecode b8zs

 pri-group timeslots 2-6

The following example configures a standard ISDN PRI interface:

! Standard PRI configuration:

controller t1 1

 pri-group timeslots 1-23 nfas_d primary nfas_int 0 nfas_group 0

 exit

! Standard ISDN serial configuration:

interface serial1:23

! Set ISDN parameters:

 isdn T309 4000

 exit

The following example configures a dedicated T1 link for SS7-enabled VoIP:

controller T1 1

 pri-group timeslots 1-23 nfas_d primary nfas_int 0 nfas_group 0 

 exit

! In a dedicated configuration, we assume the 24th timeslot will be used by ISDN.

! Serial interface 0:23 is created for configuring ISDN parameters.

interface Serial:24

! The D channel is on the RLM.

 isdn rlm 0

 isdn  T309 4000

 exit

The following example configures a shared T1 link for SS7-enabled VoIP. The rlm-group 0 portion of the pri-group timeslots command releases the ISDN PRI signaling channel.

controller T1 1

 pri-group timeslots 1-3 nfas_d primary nfas_int 0 nfas_group 0 rlm-group 0 

 channel group 23 timeslot 24

 end

! D-channel interface is created for configuration of ISDN parameters:

interface Dchannel1

 isdn T309 4000

 end

Related Commands

Command	Description
controller	Configures a T1 or E1 controller and enters controller configuration mode.
interface Dchannel	Specifies an ISDN D-channel interface for VoIP applications that require release of the ISDN PRI signaling time slot for RLM configurations.
interface serial	Specifies a serial interface created on a channelized E1 or channelized T1 controller for ISDN PRI signaling.
isdn rlm-group	Specifies the RLM group number that ISDN will start using.
isdn switch-type	Specifies the central office switch type on the ISDN PRI interface.
isdn timer t309	Changes the value of the T309 timer to clear network connections and release the B channels when there is no signaling channel active, that is, when the D channel has failed and cannot recover by switching to an alternate D channel. Calls remain active and able to transfer data when the D channel fails until the T309 timer expires. The T309 timer is canceled when D-channel failover succeeds.
show isdn nfas group	Displays all the members of a specified NFAS group or all NFAS groups.

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 command in global configuration mode.

profile incoming template

Syntax Description

template

String of special characters that are arranged in a certain order to process the digit sequence for the signaling class. Choose from the following list: •S—Starts the state machine. •<*—Waits for the digit * to be detected. The digit to be detected is the next character in the template. If any other digit is detected, then that is a failure. If the digit is detected, then go to the next directive. •a—Digits are collected as the ANI until the first nondigit or a timeout occurs. •d—Digits are collected as the DNIS until the first nondigit or a timeout occurs. •n—Notifies the CSM of the collected ANI and DNIS.

Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Release	Modification
12.1(1)T	This command was introduced.

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:

signaling-class cas test

 profile incoming S<*a<*d<*n

Related Commands

Command	Description
class (controller)	Activates the signaling-class cas command.
signaling-class cas	Defines a signaling class with a template formed by directives guiding the CSM to process the digit sequence.

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

any	Specifies either the Layer 2 Forwarding (L2F) protocol or the Layer 2 Tunneling Protocol (L2TP).
l2f	Specifies the L2F protocol.
l2tp	Specifies L2TP.
pppoe	Specifies the PPP over Ethernet (PPPoE) protocol.
pptp	Specifies the Point-to-Point Tunneling Protocol (PPTP).

Defaults

No protocol is specified.

Command Modes

VPDN subgroup

Command History

Release	Modification
12.0(5)T	This command was introduced.
12.1(1)T	The pppoe keyword was added.

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 Users must first enter the vpdn enable command to set up the PPP over Ethernet discovery daemon.

---

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 1

 accept-dialin 

  protocol l2f 

  virtual-template 1 

 request-dialout 

  protocol l2tp

  pool-member 1

 local name router1

 terminate-from hostname router2

 initiate-to ip 10.3.2.1

 l2f ignore-mid-sequence

 l2tp ip udp checksum

If you then use the no protocol command in request-dialout mode, the configuration will be changed to this:

vpdn-group 1

 accept-dialin 

  protocol l2f 

  virtual-template 1 

 request-dialout 

 local name router1

 terminate-from hostname router2

 l2f ignore-mid-sequence

Related Commands

Command	Description
accept-dialin	Creates an accept dial-in VPDN subgroup that configures a tunnel server to accept requests from a NAS to tunnel dial-in calls, and enters accept dial-in VPDN subgroup configuration mode.
accept-dialout	Creates an accept dial-out VPDN subgroup that configures a NAS to accept requests from a tunnel server to tunnel L2TP dial-out calls, and enters accept dial-out VPDN subgroup configuration mode.
request-dialin	Creates a request dial-in VPDN subgroup that configures a NAS to request the establishment of a dial-in tunnel to a tunnel server, and enters request dial-in VPDN subgroup configuration mode.
request-dialout	Creates a request dial-out VPDN subgroup that configures a tunnel server to request the establishment of dial-out L2TP tunnels to a NAS, and enters request dial-out VPDN subgroup configuration mode.

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

limit number	Maximum number of simultaneous connections supported by the resource group. Replace the number argument with the session limit you want to assign. Your access server hardware configuration determines the maximum value of this limit. Applicable to ISDN B channels or HDLC controllers.
limit slot/port	Replace the slot argument with the slot number of the card and the port argument with the port range. Applicable to ISDN B-channels or HDLC controllers
port range	Range of resource ports to use in the resource group.
port slot/port	Specific ports to use in the resource group. A forward slash must be used to separate the slot and port numbers.

Defaults

No range is configured.

Command Modes

Resource group configuration

Command History

Release	Modification
12.0(4)XI	This command was introduced.

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 put heterogeneous resources in the same group. Do not put MICA modems in the same group as Microcom modems. Do not put modems and HDLC controllers in the same resource group.

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 hdlc1 

 range limit 48

Cisco AS5400

resource-pool group resource hdlc

         range limit 2:255 (where 2 is slot#)

Cisco AS5800

resource-pool group resource hdlc

         range 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/47

rcapi 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.
:subaddress	(Optional) Subaddress of the router preceded by a colon (:).

Defaults

No directory number is set for the RCAPI interface.

Command Modes

Global configuration

Command History

Release	Modification
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 12345

Related Commands

Command	Description
debug rcapi events	Displays diagnostic DCP and driver messages.
rcapi server	Enables the RCAPI server on the 800 series router and, optionally, sets the TCP port number.
show rcapi status	Display statistics and details about RCAPI server operation.

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

port number

(Optional) TCP port number.

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

Release	Modification
12.0(7)XV	This command was introduced on the Cisco 800 series router.

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 2000

Related Commands

Command	Description
debug rcapi events	Displays diagnostic DCP and driver messages.
rcapi number	Enables the Cisco 800 series router to distinguish between incoming CAPI calls and incoming non-CAPI calls such as POTS, PPP, and X.25.
show rcapi status	Display statistics and details about RCAPI server operation.

redirect identifier

To configure a virtual private dialup network (VPDN) redirect identifier to use for Layer 2 Tunneling Protocol (L2TP) call redirection on a network access server (NAS), use the redirect identifier command in VPDN group or VPDN template configuration mode. To remove the name of the redirect identifier from the NAS, use the no form of this command.

redirect identifier identifier-name

no redirect identifier identifier-name

Syntax Description

identifier-name

Name of the redirect identifier to use for call redirection.

Command Default

No redirect identifier is configured.

Command Modes

VPDN group configuration
VPDN template configuration

Command History

Release	Modification
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

The redirect identifier command is used only on the NAS. To configure the name of the redirect identifier on the stack group tunnel server, use the vpdn redirect identifier command in global configuration mode.

The NAS compares the redirect identifier with the one received from the stack group tunnel server to determine authorization information to redirect the call.

Configuring the redirect identifier is not necessary to perform redirects. If the redirect identifier is not configured, the NAS uses the redirect IP address in order to get authorization information to redirect the call. In that case, the IP address of the new redirected tunnel server must be present in the initiate-to command configuration of the VPDN group on the NAS.

The redirect identifier allows new stack group members to be added without the need to update the NAS configuration with their IP addresses. With the redirect identifier configured, a new stack group member can be added and given the same redirect identifier as the rest of the stack group.

If the authorization information for getting to the new redirected tunnel server is different, then you will need to configure the authorization information via RADIUS using tagged attributes:

Cisco:Cisco-Avpair = :0:"vpdn:vpdn-redirect-id=identifier name"

The NAS will choose the correct tagged parameters to get authorization information for the new redirected tunnel server by first trying to match the redirect identifier (if present) or else by matching the Tunnel-Server-Endpoint IP address.

Examples

The following example configures the redirect identifier named lns1 on the NAS for the VPDN group named group1:

vpdn-group group1

 redirect identifier lns1

Related Commands

Command	Description
clear vpdn redirect	Clears the L2TP redirect counters shown in the output from the show vpdn redirect command.
show vpdn redirect	Displays statistics for L2TP call redirects and forwards.
vpdn redirect	Enables L2TP redirect functionality.
vpdn redirect attempts	Restricts the number of redirect attempts possible for an L2TP call on the LAC.
vpdn redirect identifier	Configures a VPDN redirect identifier to use for L2TP call redirection on a stack group tunnel server.
vpdn redirect source	Configures the public redirect IP address of an LNS.
vpdn-group	Creates a VPDN group and enters VPDN group configuration mode.
vpdn-template	Creates a VPDN template and enters VPDN template configuration mode.

redundancy

To configure shelf redundancy for Cisco AS5800 universal access servers, use the redundancy command in global configuration mode. To disable, use the no form of this command.

redundancy

no redundancy

Syntax Description

This command has no arguments or keywords.

Defaults

Redundancy is disabled.

Command Modes

Global configuration

Command History

Release	Modification
12.2(2)T	This command was introduced.
12.2(11)T	This command was integrated into Cisco IOS Release 12.2(11)T.

Usage Guidelines

Use the redundancy global configuration command to enter redundancy-configuration mode.

Examples

The following example assigns the configured router shelf to the redundancy pair designated as 25. This command must be issued on both router shelves in the redundant router-shelf pair:

Router(config)# redundancy

Router(config-red)# failover group-number 25

Related Commands

Command	Description
failover group-number	Assigns a router-shelf pair to a redundancy router-shelf pair code.
show redundancy	Displays current or historical status and related information and displays the router-shelf redundancy status.

reload components

To request that the dial shelf controller (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

all	Reloads all attached components.
description-line	Displays reason for the reload, 1 to 255 characters in length.
at hh:mm	Schedules when the software reload takes place using a 24-hour clock. If you specify the month and day, the reload is scheduled to take place at the specified time and date. If you do not specify the month and day, the reload takes place at the specified time on the current day (if the specified time is later than the current time), or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. The reload must take place within approximately 24 days.
in [hhh:]mmm	Schedule a reload of the software to take effect in the specified minutes or (optionally) hours and minutes. The reload must take place within approximately 24 days.
cancel	Cancels a scheduled reload.

Command History

Release	Modification
12.1(3)T	This command was introduced.

Command Modes

EXEC

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 Network Time Protocol (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 all

Related Commands

Command	Description
show reload	Displays the reload status on the router.

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

Release	Modification
11.3(5)AA	This command was introduced.
12.0(5)T	This command was introduced.
12.0(5)T	The original keywords and arguments were removed and made into separate request-dialin subgroup commands.

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 initiate-to command in VPDN group configuration mode

•The protocol command in request dial-in VPDN subgroup configuration mode

•At least one dnis or domain command in request dial-in VPDN subgroup configuration mode

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 1

Router(config-vpdn)# request-dialin

Router(config-vpdn-req-in)# protocol l2tp

Router(config-vpdn-req-in)# domain cisco.com

!

Router(config-vpdn)# initiate-to ip 172.17.33.125

Related Commands

Command	Description
accept-dialin	Creates an accept dial-in VPDN subgroup that configures a tunnel server to accept requests from a NAS to tunnel dial-in calls, and enters accept dial-in VPDN subgroup configuration mode.
accept-dialout	Creates an accept dial-out VPDN subgroup that configures a NAS to accept requests from a tunnel server to tunnel L2TP dial-out calls, and enters accept dial-out VPDN subgroup configuration mode.
authen before-forward	Specifies that VPDN send the entire structured username to the AAA server the first time the router contacts the AAA server.
dnis	Specifies the DNIS group name or DNIS number of users that are to be forwarded to a tunnel server using VPDN.
domain	Specifies the domain name of users that are to be forwarded to a tunnel server using VPDN.
initiate-to	Specifies the IP address that calls are tunneled to.
protocol (VPDN)	Specifies the tunneling protocol that a VPDN subgroup will use.

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

Release	Modification
12.0(5)T	This command was introduced.

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:

•The initiate-to command in VPDN group configuration mode

•The protocol l2tp command in request dial-out VPDN subgroup configuration mode

•Either the pool-member or rotary-group command in request dial-out VPDN subgroup configuration mode, depending on the type of dialer resource to be used by the VPDN subgroup

•The dialer vpdn command in dialer interface configuration mode

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 1

Router(config-vpdn)# request-dialout

Router(config-vpdn-req-ou)# protocol l2tp

Router(config-vpdn-req-ou)# pool-member 1

!

Router(config-vpdn)# initiate-to ip 10.3.2.1

!

Router(config)# interface Dialer2

Router(config-if)# ip address 172.16.2.3 255.255.128

Router(config-if)# encapsulation ppp

Router(config-if)# dialer remote-name reuben

Router(config-if)# dialer string 5551234

Router(config-if)# dialer vpdn

Router(config-if)# dialer pool 1

Router(config-if)# dialer-group 1

Router(config-if)# ppp authentication chap

Related Commands

Command	Description
accept-dialin	Creates an accept dial-in VPDN subgroup that configures a tunnel server to accept requests from a NAS to tunnel dial-in calls, and enters accept dial-in VPDN subgroup configuration mode.
accept-dialout	Creates an accept dial-out VPDN subgroup that configures a NAS to accept requests from a tunnel server to tunnel L2TP dial-out calls, and enters accept dial-out VPDN subgroup configuration mode.
dialer vpdn	Enables a dialer profile or DDR dialer to use L2TP dial-out.
initiate-to	Specifies the IP address that will be tunneled to.
pool-member	Assigns a request-dialout VPDN subgroup to a dialer pool.
protocol (VPDN)	Specifies the tunneling protocol that a VPDN subgroup will use.
rotary-group	Assigns a request-dialout VPDN subgroup to a dialer rotary group.

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

name	Name for a group of physical resources inside the access server. This name can have up to 23 characters.
digital	Accepts digital calls. Specifies circuit-switched data calls that terminate on a HDLC framers (unlike asynchronous analog modem call that use start and stop bits).
speech	Accepts speech calls. Specifies normal voice calls, such as calls started by analog modems and standard telephones.
v110	Accepts V.110 calls.
v120	Accepts V.120 calls. By specifying this keyword, the access server begins counting the number of v120 software encapsulations occurring in the system.
service name	(Optional) Name for a service profile. This option is not supported for digital or V.120 calls.

Defaults

No resources are assigned to the customer profile by default.

Command Modes

Customer profile configuration

Command History

Release	Modification
12.0(4)XI	This command was introduced.

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 modem1

 range port 1/0 1/47

 exit 

resource-pool profile customer customer1_isp 

resource modem1 speech

Related Commands

Command	Description
resource-pool profile customer	Creates a customer profile.

resource-pool

To enable or disable resource pool management, use the resource-pool command in global configuration mode.

resource-pool {enable | disable}

Syntax Description

enable	Enables resource pool management.
disable	Disables resource pool management.

Defaults

Resource management is disabled.

Command Modes

Global configuration

Command History

Release	Modification
12.0(4)XI	This command was introduced.

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 enable

resource-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

Release	Modification
12.0(4)XI	This command was introduced.

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 If you configure only this command and do not configure AAA accounting, nothing happens. The default functionality for the resource-pool enable command does not include this functionality.

---

Table 20 shows the new fields that have been added to the start and stop records.

Table 20 Start and Stop Resource Manager Records

New Start Record Fields	New Stop Record Fields
Call-type Customer-profile-name Customer-profile-active-sessions MLP-session-ID (multilink users) Resource-group-name Overflow-flag VPDN-tunnel-ID (VPDN users) VPDN-homegateway (VPDN users) VPDN-domain-name (VPDN users) VPDN-group-active-session (VPDN users)	ModemSpeed-receive ModemSpeed-transmit MLP-session-ID (multilink users)

---

Caution This list of newly supported start and stop fields is not exhaustive. Cisco reserves the right to enhance this list of records at any time. Use the show accounting command to see the contents of each active session.

---

---

Note Cisco recommends that you thoroughly understand how these new start/stop records affect your current accounting structure before you enter this command.

---

Examples

The following example shows the new AAA accounting start/stop records inserted into an existing AAA accounting infrastructure:

resource-pool aaa accounting ppp

Related Commands

Command	Description
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