Table Of Contents
Resource Pool Management with Direct Remote Services
Feature Overview
Standalone Network Access Server (NAS)
Components of Incoming and Outgoing Call Management
Customer Profiles
DNIS Groups
Call Types
Resource Groups
Resource Services
VPDN Groups
VPDN Profiles
Direct Remote Services
Processes of Incoming and Outgoing Call Management
Call Treatment
Call Discrimination
Base Session and Overflow Session Limits
VPDN Session and Overflow Session Limits
VPDN MLP Bundles and Links-Per-Bundle Limits
VPDN Tunnel Limits
Call Management Functional Descriptions
Accounting Data
Data over Voice Bearer Services
Benefits
Restrictions
Related Features and Technologies
Related Documents
Supported Platforms
Supported MIBs and RFCs
Prerequisites
Configuration Tasks
Enabling Resource Pool Management
Configuring DNIS Groups
Configuring Discriminator Profiles
Configuring Resource Groups
Configuring Service Profiles
Configuring Customer Profiles
Configuring Customer Profile Templates
Configuring AAA Server Groups
Configuring VPDN Profiles
Configuring VPDN Groups
Configuration Examples
Sample Configuration for Resource Pool Management
Sample Direct Remote Services Configuration
Sample Customer Profile Configuration for Data Over Voice Bearer Service
Sample VPDN Configuration
Sample VPDN Load Sharing and Backup Configuration
Verifying Call-Counter and Call-Detail Output
show resource-pool call
show resource-pool customer
show resource-pool discriminator
show resource-pool resource
show dialer dnis
show resource-pool vpdn
clear resource-pool
Troubleshooting Resource Pool Management
Checking the Resource Pool Connection
Troubleshooting DNIS Group Problems
Troubleshooting Call Discriminator Problems
Troubleshooting Customer Profile Counts
Troubleshooting Resource Group Counts
Checking the RPM/VPDN Connection
Troubleshooting Customer/VPDN Profile
Troubleshooting VPDN Profile Limits
Troubleshooting VPDN Group Limits
Troubleshooting VPDN Endpoint Problems
Using the debug aaa authorization Command
Command Reference
aaa group-configuration
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Example
Related Commands
backup
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
call progress tone
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
call-type
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
call-type cas
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Examples
Related Commands
clear dialer dnis
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
clear resource-pool
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
dialer dnis group
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
dnis
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Examples
Related Commands
dnis group
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
domain
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
limit base-size
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
limit overflow-size
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
loadsharing
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
modem min-speed max-speed
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
multilink
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
number
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
ppp ipcp
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
range
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
request dialin
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool aaa accounting ppp
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool aaa protocol
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool call treatment
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool group resource
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool profile customer
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool profile discriminator
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool profile service
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
resource-pool profile vpdn
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show call progress tone
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show dialer dnis
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show resource-pool call
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show resource-pool customer
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show resource-pool discriminator
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show resource-pool resource
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show resource-pool vpdn
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show vpdn domain
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show vpdn group
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show vpdn multilink
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
source template
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
template
Syntax Description
Defaults
Command Modes
Usage Guidelines
Examples
Related Commands
vpdn group
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
vpdn profile
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
Debug Commands
debug resource-pool
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
Glossary
Resource Pool Management with Direct Remote Services
This document contains the following sections:
•
Feature Overview
•Benefits
•Restrictions
•Related Features and Technologies
•Related Documents
•Supported Platforms
•Supported MIBs and RFCs
•Prerequisites
•Configuration Tasks
•Configuration Examples
•Command Reference
Feature Overview
Cisco Resource Pool Manager (RPM) enables telephone companies and Internet service providers (ISPs) to share dial resources for wholesale and retail dial network services in a single network access server (NAS) or across multiple NAS stacks. With Cisco RPM, service providers can count, control, and manage dial resources and provide accounting for shared resources when implementing different service-level agreements.
This document presents the single, standalone NAS version of Cisco RPM. For information on the Cisco Resource Pool Manager Server (RPMS) solution, see the Cisco Connection Online location at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_1-0/index.htm.
Cisco RPM is ideal for combining retail and wholesale dial services using Cisco AS5200, AS5300, and AS5800 network access servers. The Cisco RPM can be configured in one or more standalone Cisco NASs, or, optionally, across multiple NAS stacks by using one or more external Cisco Resource Pool Manager Servers (RPMSs). Call management and call discrimination can be configured to occur before the call is answered.
For call management, dial customers are differentiated by the use of configurable customer profiles. Each profile is based on the Dialed Number Information Service (DNIS) and the call type determined at the time of an incoming call.
When using call discrimination, the DNIS and call type are matched against a table of disallowed calls. When a call arrives at the NAS, if the DNIS and call type match an entry in this table, the call is rejected. Call discrimination can be used to manage the billing of calls to different types of resources.
When management by virtual private dialup network (VPDN) is configured, a VPDN group includes the information needed to set up or reject a VPDN session. VPDN setup can be based on the DNIS received during call setup, or on the domain name after the call is answered. Load balancing is used to achieve full usage of VPDN tunnels. The VPDN group can also serve as the "customer profile" when all calls are answered and sessions are identified and limited by domain name instead of DNIS.
To support data over voice bearer service (DoVBS), service providers use DNIS to direct calls to the appropriate resource. When a digital call arrives at the NAS through the voice network, it terminates on a High-Level Data Link Control (HDLC) controller rather than on a modem. In this application, the customer profile that the DNIS group is assigned has the associated call type of speech and the resource group directs the call to the HDLC controller.
Standalone Network Access Server (NAS)
A single NAS using Cisco RPM can provide:
•wholesale virtual private dialup network (VPDN) dial service to corporate customers
•direct remote services
•retail dial service to end users
and show multiple connections to a Cisco AS5300 NAS. Incoming calls to the NAS can use ISDN Private Rate Interface (PRI) signaling, channel associated signaling (CAS), or SS7 signaling protocol. shows incoming calls that are authenticated locally for retail dial services, or forwarded through VPDN tunnels for wholesale dial services.
Note This implementation does not use Cisco RPMS. If you are not using Cisco RPMS and you have more than one Cisco NAS, you must manually configure each NAS by using Cisco IOS commands. Resource usage information is not shared between NASs.
Figure 1 Retail Dial Service Using Resource Pool Management
shows a method of implementing wholesale dial services without using VPDN tunnels. This is done by creating individual customer profiles consisting of authentication, authorization, and accounting (AAA) groups and Point-to-Point Protocol (PPP) configurations. The AAA groups provide IP addresses of AAA servers for authentication and accounting. The PPP configurations enable you to set different PPP parameter values on each customer profile. A customer profile typically includes the following PPP parameters:
•Applicable IP address pools or a default local list of IP addresses
•Primary and secondary domain name server (DNS) or Windows internet naming service (WINS)
•Authentication method (PAP, CHAP, MSCHAP)
•Number of links allowed for each call using Multilink PPP
Note The AAA and PPP integration applies to a single NAS environment; the external RPMS solution is not supported.
Figure 2 Resource Pool Management with Direct Remote Services
Components of Incoming and Outgoing Call Management
Cisco RPM manages both incoming calls and outgoing sessions. Cisco RPM differentiates dial customers through configured customer profiles based on the Dialed Number Information Service (DNIS) and call type determined when an incoming call comes in.
The components of incoming call management in the Cisco RPM are:
•Customer profiles
•DNIS groups
•Call types
•Resource groups
•Resource services
The components of outgoing session management in the Cisco RPM are:
•VPDN groups
•VPDN profiles
•Direct remote services
Customer Profiles
A customer profile defines how and when a call is answered. Customer profiles include the following components (see ):
•Customer profile name
•Session limits—Maximum number of standard sessions
•Overflow limits—Maximum number of overflow sessions
•DNIS groups
•Resource groups
•Resource services
•VPDN profiles or groups
•Direct remote services source template
Figure 3 Components of a Customer Profile
The following types of customer profiles can be used on a NAS:
•DNIS-based customer profile—Associated with a specific DNIS group and used for a single NAS solution.
•Default customer profile—Associated with the default DNIS group and also used for a single NAS solution. This is most useful with domain-based VPDN services and for combining retail dial services with VPDN services. You can use up to four default customer profiles, each differentiated by the call type (speech, digital, V.110, V.120).
•Backup customer profile—Functionally the same as the two profiles above, except that the backup customer profile is applicable with an RPMS solution and is used only when connectivity between a NAS and the RPMS is lost. When the connection is restored, the call counters may not be synchronized.
See the RPMS documentation for a review of the RPMS fault tolerance and recovery mechanisms.
DNIS Groups
A DNIS group is a configured list of DNIS numbers that correspond to the numbers dialed to access particular customers, service offerings, or both. The Cisco RPM checks the DNIS number of inbound calls against the configured DNIS groups and selects a customer profile based on the following criteria:
•If Cisco RPM finds a match, it uses the configured information in the customer profile to which the DNIS group is assigned.
•If Cisco RPM does not find a match, it uses the configured information in the customer profile to which the default DNIS group is assigned.
The DNIS/call type sequence can only be associated with one customer profile.
Call Types
The following call types are supported in the Cisco RPM:
•Speech
•Digital
•V.110
•V.120
Note Voice over IP, Fax over IP, and dial-out calls are not currently supported.
Call types are used within a customer profile to assign calls to the appropriate resource based on:
•Q.931 bearer capability for ISDN PRI and SS7 calls
•Static DNIS group configuration for CAS (CT1, CT3, and CE1) calls
Note For information on SS7 implementation for RPM, see Cisco Resource Pool Manager Server 1.0 SS7 Implementation on Cisco Connection Online (CCO) at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_1-0/rpmsnote.htm.
Resource Groups
Resource groups represent groupings of similar hardware and/or firmware that are static and do not change on a per-call basis. Resource groups can be used to define resources that are port-based or non-port-based.
•Port-based resources are identified by physical location, such as a range of port/slot numbers (for example, modems or terminal adapters).
•Non-port-based resources are identified by a single size parameter (for example, HDLC framers or V.120 terminal adapters). Note that V.120 terminal adapters are currently implemented as part of the Cisco IOS software.
The Cisco RPM:
•Enables you to configure resource groups on a Cisco NAS and apply them to a customer profile to maximize the use of available shared resources and thus support service-level agreements for various resource allocation schemes.
•Allows you to combine your Cisco NAS resource groups with call types (speech, digital, V.110, and V.120) and optional resource modem services. Resource groups and services are assigned to incoming calls through DNIS groups and call types.
Note Resources not configured in the NAS as part of a resource group and not assigned to a customer profile cannot be used by Cisco RPM or Cisco RPMS.
Note To support ISDN Data over Voice Bearer Service (DoVBS), use a DNIS group and a configured customer profile to direct the speech call to the appropriate digital resource. The resource group assigned to this customer profile is digital resources with a call type of speech, so the call will terminate on an HDLC controller rather than on a modem.
Resource Services
A resource service contains a finite series of resource command strings that can be used to dynamically configure an incoming connection.
Services supported by a resource group are determined by the combination of hardware and firmware installed. Currently, resource services:
•Can be configured and applied to resource groups containing only MICA modems.
•Can be configured to affect minimum and maximum speed, modulation, error correction, and compression as shown in .
Table 1 Resource Services for Resource Groups Containing MICA Modems
Service
|
Options
|
Comments
|
min-speed
|
<300—56000>, any
|
Must be a V.90 increment
|
max-speed
|
<300—56000>, any
|
Must be a V.90 increment
|
modulation
|
k56flex, v22bis, v32bis, v34, v90, any
|
|
error-correction
|
1apm, mn14
|
Hidden command
|
compression
|
mnps, v42bis
|
Hidden command
|
VPDN Groups
A VPDN group contains the data required to build a VPDN tunnel from the Cisco RPM NAS L2TP Access Concentrator (LAC) to the L2TP Network Server (LNS). In the context of RPM, VPDN is authorized by first associating a customer profile with a VPDN group, and second by associating the VPDN group to the DNIS group used for that customer profile. VPDN groups are assigned to customer profiles as follows:
•For DNIS-based VPDN dial services, VPDN groups are assigned to customer profiles based on the configured DNIS groups.
•For domain-based VPDN dial services, VPDN groups are assigned to customer profiles with the default DNIS group and matching call-type assignment.
VPDN group data includes the endpoint IP addressses. Cisco RPM enables you to specify multiple IP endpoints for a VPDN group. If two or more IP endpoints are specified, Cisco RPM uses a load-balancing method to ensure traffic is distributed across the IP endpoints.
The VPDN group provides call management by allowing limits to be applied to both the number of multilink PPP bundles per tunnel and the number of links per multilink PPP bundle. Limits can also restrict the number of sessions per IP endpoint. If you require more granular control of VPDN counters, use VPDN profiles.
VPDN Profiles
VPDN profiles allow for session and overflow limits to be imposed for a particular customer profile. These limits are unrelated to the limits imposed by the customer profile. A customer profile is associated with a VPDN profile. A VPDN profile is associated with a VPDN group. VPDN profiles are required only when these additional counters are required for VPDN usage per customer profile.
Direct Remote Services
Direct remote services is an enhancement to Cisco resource pool management (RPM) implemented in Cisco IOS Release 12.0(7)T that enables service providers to implement wholesale dial services without using VPDN tunnels. A customer profile that has been preconfigured with a PPP template to define the unique PPP services for the wholesale dial customer is selected by the incoming DNIS and call type. At the same time, the DNIS is used to select AAA server groups for authentication/authorization and for accounting for the customer.
PPP Common Configuration Architecture (CCA) is the new component of the RPM customer profile that enables direct remote services. The full PPP command set available in Cisco IOS software is configurable per customer profile for wholesale dial applications. A customer profile typically includes the following PPP parameters:
•Local or named IP address pools
•Primary and secondary domain name server (DNS) or Windows internet naming service (WINS) addresses
•Authentication method (PAP, CHAP, MS-CHAP)
•Multilink PPP links per bundle limits
The AAA session information is selected by the incoming DNIS. AAA server lists provide the IP addresses of AAA servers for authentication, authorization, and accounting in the wholesale customer's local network. The server lists for both authentication and authorization and for accounting contain the server addresses, AAA server type, timeout, retransmission, and keys per server.
When direct remote services is implemented on a Cisco NAS, the following events occur:
1 The NAS sends an authorization request packet to the AAA server by using the authentication method (PAP, CHAP, MSCHAP) that has been configured through PPP.
2 The AAA server accepts the authorization request and returns one of the following items to the NAS:
(a) a specific IP address
(b) an IP address pool name
(c) nothing
3 Depending on the response from the AAA server, the NAS assigns one of the following items to the user through the DNS/WINS:
(a) the IP address returned by the AAA server
(b) an IP address randomly assigned from the named IP address pool
(c) an IP address from a pool specified in the customer profile template
Note If the AAA server sends back to the NAS a named IP address pool and that name does not exist on the NAS, the request for service is denied. If the AAA server does not send anything back to the NAS and there is an IP address pool name configured in the customer profile template, an address from that pool is used for the session.
Processes of Incoming and Outgoing Call Management
This section describes the following topics:
•Call Treatment
•Call Discrimination
•Base Session and Overflow Session Limits
•VPDN Session and Overflow Session Limits
•VPDN MLP Bundles and Links-Per-Bundle Limits
•VPDN Tunnel Limits
•Call Management Functional Descriptions
Call Treatment
Call treatment determines how calls are handled when certain events require the call to be rejected. For example, if the session and overflow limits for one of your customers has been exceeded, any additional calls receive a busy signal. summarizes the various call treatment options.
Table 2 Call Treatment Events and Options
Event
|
Call Treatment Option
|
Results
|
Customer profile not found
|
No answer (default)
|
The caller receives rings until the switch eventually times out. Implies that the NAS was appropriate, but resources were unavailable. The caller should try later.
|
Busy
|
The switch drops the call from the NAS and sends a busy signal back to the caller. The call is rejected based on not matching a DNIS group/call type and customer profile. Can be used to immediately reject the call and free up the circuit.
|
Customer profile limits exceeded
|
Busy
|
The switch drops the call from the NAS and sends a busy signal back to the caller.
|
NAS resource not available
|
Channel not available (default)
|
The switch sends the call to the next channel in the trunk group. The call can be answered, but the NAS does not have any available resources in the resource groups. Allows the switch to try additional channels until it gets to a different NAS in the same trunk group that has the available resources.
|
Busy
|
The switch drops the call from the NAS and sends a busy signal back to the caller. Can be used when the trunk group does not span additional NASs.
|
Call discriminator match
|
No answer
|
The caller receives rings until the switch eventually times out.
|
Call Discrimination
Resource pool management offers a call discrimination feature that rejects calls based on a DNIS group and a call type filter. When a call arrives at the NAS, the DNIS and the call type are matched against a table of disallowed calls. If the DNIS and call type match entries in this table, the call is rejected before it is assigned Cisco NAS resources, or before any other Cisco RPM processing occurs.
and show the sequence of call discrimination/call processing events which take place when an incoming call arrives at the Cisco NAS. shows the sequence for a Cisco NAS that is not using direct remote services. shows the sequence that occurs when direct remote services is being used.
Figure 4 RPM Call-Processing Flowchart for a Standalone NAS
Figure 5
RPM Call-Processing Flowchart for a Standalone NAS with Direct Remote Services
You can use call discrimination to manage billing of calls to different types of resources. If you have a different billing structure for modem calls and for digital calls, each call type is assigned a different DNIS. When a user calls the DNIS, the call type must be of the allowed call type or the call is rejected.
For example, to restrict a specific DNIS group to modem calls only, create call discrimination settings for the DNIS group and the other call types (digital, V.110, and V.120) as shown in .
Note Supported call types are speech, digital, V.110, and V.120.
Figure 6 Call Discrimination
Base Session and Overflow Session Limits
The Cisco RPM enables you to set base and overflow session limits in each customer profile.
The base session limit determines the maximum number of non-overflow sessions supported for a customer profile. When the base session limit is reached, any new calls are rejected unless overflow sessions are enabled. If overflow sessions are enabled, new sessions up to the session overflow limit are processed and marked as overflow for call handling and accounting. The RPM call counters and AAA accounting records indicate whether a call is considered overflow for tracking and billing.
The overflow session limit determines the allowable number of sessions above the session limit. If the overflow session limit is greater than zero, overflow sessions are enabled. The maximum number of allowed sessions is the base session limit plus the overflow session limit. When the overflow session limit is reached, any new calls are rejected.
Enabling overflow sessions is useful for allocating extra sessions for preferred customers at premium rates. Overflow sessions can also be useful for encouraging customers to adequately forecast bandwidth usage or for special events when normal session usage is exceeded. For example, if a customer has a corporate-wide program and many people are expected to request remote access, you can enable many overflow sessions and charge a premium rate for the extra bandwidth used.
Note An overflow call is a call received when the base session limit is exceeded and is in an overflow state. When a call is identified as an overflow call, the call maintains the overflow status throughout its duration—even if the number of current sessions returns below the base session limit.
.
Table 3 Effects of Session Limit and Session Overflow Limit Settings Combinations
Base Session Limit
|
Session Overflow Limit
|
Call Handling
|
0
|
0
|
Reject all calls.
|
10
|
0
|
Accept up to 10 sessions.
|
10
|
10
|
Accept up to 20 sessions and mark sessions 11 to 20 as overflow sessions.
|
0
|
10
|
Accept up to 10 sessions and mark session 1 to 10 overflow sessions.
|
All
|
0
|
Accept all calls.
|
0
|
All
|
Accept all calls and mark all calls as overflow.
|
VPDN Session and Overflow Session Limits
The Cisco RPM enables you to configure base and overflow session limits per VPDN profile for managing VPDN sessions.
Note The VDPN session and overflow session limits are independent of the limits set in the customer profiles.
The base VPDN session limit determines the maximum number of non-overflow sessions supported for a VPDN profile. When the base VPDN session limit is reached, any new VPDN calls using the VPDN profile sessions are disconnected unless overflow sessions are enabled. If overflow sessions are enabled, new sessions up to the overflow session limit are processed and marked as overflow for VPDN accounting.
The VPDN overflow session limit determines the number of sessions above the base session limit allowed in the VPDN group. If the overflow session limit is greater than zero, overflow sessions are enabled. The maximum number of allowed sessions is the base session limit plus the overflow session limit. When the overflow session limit is reached, any new calls are disconnected.
VPDN MLP Bundles and Links-Per-Bundle Limits
To ensure resources are not consumed by a few users with multilink PPP (MLP) connections, the Cisco RPM also enables you to specify the maximum number of MLP bundles that can be opened in a VPDN group. In addition, you can specify the maximum number of links for each MLP bundle.
For example, if standard ISDN users access the VPDN profile, limit this setting to two links per bundle. If video conferencing is used, increase this setting to accommodate the necessary bandwidth (usually six links). These limits have no overflow options and are configured under the VPDN group component.
VPDN Tunnel Limits
For increased VPDN tunnel management, the Cisco RPM enables you to set an IP endpoint session limit for each IP endpoint. IP endpoints are configured for VPDN groups.
Call Management Functional Descriptions
and depict the processes of incoming and outgoing call management that have been described in the previous sections.
Figure 7 RPM Functional Description for Incoming Call Management
When a DNIS call comes in, the Cicco NAS chooses an authentication/authorization server and an accounting server.
For information on RADIUS multiple UDP ports support for RPM, see Configuring RADIUS for Multiple UDP Ports Support. For information on AAA server groups based on DNIS implementation for RPM, see Selecting AAA Server Groups Based on DNIS.
Incoming call management includes the following processes:
•The incoming DNIS is mapped to a DNIS group; if there is no incoming DNIS number, or the DNIS number provided does not match any configured DNIS group, the DNIS group default is used.
•The mapped DNIS group is checked against configured call discriminator profiles to confirm if this DNIS group/call type combination is disallowed. If there is a match, the call is immediately rejected.
•Once a DNIS group or a default DNIS group is identified, the customer profile associated with that DNIS group and call type (from the bearer capability for ISDN calls; statically configured for CAS calls) is selected. If there is no corresponding customer profile, the call is rejected.
•The customer profile includes a base session limit value and an overflow session limit value. If these thresholds have not already been met, the call is assigned the appropriate resource defined in the customer profile. If the thresholds have been met, the call is rejected.
•If resources are available from the resource group defined in the customer profile, the call is answered. Otherwise, the call is rejected.
•As sessions start and end, the session counters increase and decrease, so the customer profile call counters are kept current.
Outgoing call management is depicted in .
Figure 8 RPM Functional Description for Outgoing Call Management
Outgoing call management includes the following processes:
•After the call is answered and if VPDN is enabled, the Cisco RPM checks the customer profile for an assigned VPDN group or profile.
•If a VPDN profile is found, the limits for number of multilink bundles and number of links per bundle are checked:
•If the limits have not been exceeded, the VPDN group data associated with that VPDN profile is used to build a VPDN tunnel.
•If the VPDN limits have been exceeded, the call is disconnected.
•If a VPDN group is found within the customer profile, the VPDN group data is used to build a VPDN tunnel:
•If the VPDN group limits for number of multilink bundles and number of links per bundle have not been exceeded, a VPDN tunnel is built.
•If the limits have been reached, the call is disconnected.
•The outgoing session management of the customer profile directs the answered call to the appropriate destination:
•To a PPP command set/feature set and AAA server group for direct remote services.
•To a tunnel that is established between the NAS or L2TP Access Concentrator (LAC) and a wholesale (VPDN) dial customer's home gateway (HGW) or L2TP Network Server (LNS) using L2F or L2TP tunneling technology.
•To a local AAA server of retail dial applications and Internet and intranet access.
•If no VPDN profile is assigned to the customer profile and VPDN is enabled, non-RPM VPDN service is attempted. If this non-RPM VPDN service fails, the call is processed as a retail dial service call if local AAA service is available.
Accounting Data
You can generate accounting data for network dial service usage in NAS AAA attribute format. You can configure the Cisco NAS to generate AAA accounting records for access to an external AAA server. The accounting start and stop records in AAA attribute format are sent to the external AAA server by using either RADIUS or TACACS+ protocols for accounting data storage. lists the new fields in the AAA accounting packets.
Table 4 AAA Accounting Records
Accounting Start Record
|
Accounting Stop Record
|
Call-Type
CAS-Group-Name
Customer-Profile-Name
Customer-Profile-Active-Sessions
DNIS-Group-Name
Overflow
MLP-Session_ID
Modem-Speed-Receive
Modem-Speed-Transmit
VPDN-Domain-Name
VPDN-Tunnel-ID
VPDN-HomeGateway
VPDN-Group-Active-Sessions
|
Disconnect-Cause
Modem-Speed-Receive
Modem-Speed-Transmit
MLP-Session-ID
|
Data over Voice Bearer Services
Data over Voice Bearer Services (DoVBS) is a dial service that uses a customer profile and an associated resource group of digital resources to direct data calls with a speech call type to HDLC controllers.
To support ISDN DoVBS, use a DNIS group and a configured customer profile to direct the speech call to the appropriate digital resource.
The resource group assigned to this customer profile is digital resources; the call type is speech. The call terminates on an HDLC controller rather than on a modem.
Benefits
Cisco Resource Pool Manager with direct remote services gives data network service providers the capability to:
•Manage customer use of shared resources, such as modems or HDLC controllers for data calls.
•Offer advanced wholesale dial-up services directly to customers. Because the PPP and AAA feature sets are selected by the incoming DNIS, the service provider no longer needs tunneling technology to provide unique service-level agreements to wholesale dial customers.
•Efficiently use resource groups, such as modems to offer differing over-subscription rates and dial service-level agreements.
•Deploy Data over Voice Bearer Service (DoVBS).
•Accept or reject a call based on the incoming DNIS number before answering the call.
•Include local retail dial services in the same NAS with the wholesale dial customers.
The Cisco RPM customer profile template provides a strong, single NAS solution with the following benefits for providers of wholesale dial services:
•Call acceptance is determined by the Cisco RPM before call answering by using the configured size limits and resource availability.
•The answered call uses the PPP configuration defined in the template to initiate authentication, obtain an IP address, and select a DNS or WINS that is located at the customer's site.
•The same DNIS that was used to choose the customer profile selects the servers for authentication/authorization and accounting that are located at the wholesale customer's site.
Restrictions
•Ear and Mouth Feature Group B (E&M-FGB) is the only signaling type supported for channel associated signaling (CAS) on T1 and T3 facilities; R2 is supported for E1 facilities. Feature Group (FG) D is not currently supported.
•The Cisco IOS software collects DNIS digits for E&M-FGB CAS signaling. For all other CAS signaling types, use the default DNIS group customer profiles.
•The Resource Pool Manager application requires the NPE 300 processor when implemented on the Cisco AS5800.
•Use resource pool management services with MICA modems only.
•Modem pooling and resource pool management are not compatible.
Related Features and Technologies
•Authentication, Authorization, and Accounting (AAA)
•Point-to-Point Protocol (PPP)
•Virtual Private Dial-up Network (VPDN)
•SS7 Signaling
Related Documents
•Cisco AS5200 Universal Access Server Software Configuration Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5200/52swcfg2/index.htm
•Cisco AS5300 Software Configuration Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/53swcf2/index.htm
•Cisco AS5800 Access Server Software ICG
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/58sw_icg/index.htm
•Cisco Access VPN Solutions Using Tunneling Technology
http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/vpn_soln/index.htm
•Cisco Resource Pool Manager Server Configuration Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_1-0/rpmsconf/index.htm
•Cisco Resource Pool Manager Server Installation Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_1-0/rpms_ins/index.htm
•Cisco Resource Pool Manager Server Solutions Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_1-0/rpms_sol/index.htm
•Dial Solutions Quick Configuration Guide (Cisco IOS Release 12.0)
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12supdoc/dsqcg3/index.htm
•Redundant Link Manager
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113aa/113aa_7/rlm_rel2.htm
•Release Notes for Cisco Resource Pool Manager Server Release 1.0
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_1-0/rpmsnote.htm
•SS7 Continuity Testing for Network Access Servers
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113aa/113aa_5/cot.htm
•SS7 Dial Solution System Integration
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/iosinfo/ios_mods/5420.htm
•Configuring RADIUS for Multiple User Datagram Protocol Ports
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/rad_udp6.htm
•Selecting AAA Server Groups Based on DNIS
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/serdnis6.htm
Supported Platforms
The following platforms support resource pool management in NAS standalone and external server scenarios for this Cisco IOS release:
•Cisco AS5200
•Cisco AS5300
•Cisco AS5800
Supported MIBs and RFCs
MIBs
•CALL-RESOURCE-POOL-MIB
•CISCO-VPDN-MANAGEMENT-MIB
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Prerequisites
•For the Cisco AS5200 and Cisco AS5300, Cisco IOS Release 12.0(4)XI1 or later releases must be running on the NAS.
•For the Cisco AS5800, Cisco IOS Release 12.0(5)T or later releases must be running on the NAS.
•A minimum of 64 MB must be available on the DMM cards.
•Before configuring resource pool management, verify the operation of the following features as described in the appropriate documentation listed in "Related Documents":
•Ensure AAA operation (if enabled)
•Ensure PPP operation
•Ensure VPDN operation (if enabled)
See Configuring the NAS for Basic Dial Access for more information: http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/vpn_soln/l2fcase/l2ftask1.htm
Configuration Tasks
The following configuration tasks are used to configure a Cisco NAS for resource pool management:
•Enabling Resource Pool Management
•Configuring DNIS Groups
•Configuring Discriminator Profiles
•Configuring Resource Groups
•Configuring Service Profiles
•Configuring Customer Profiles
•Configuring Customer Profile Templates
•Configuring AAA Server Groups
•Configuring VPDN Profiles
•Configuring VPDN Groups
These tasks are described in the following sections:
Enabling Resource Pool Management
To enable resource pool management on a Cisco NAS, perform the following steps, beginning from global configuration mode.
Step
|
Command
|
Purpose
|
1
|
Router(config)# resource-pool {enable | disable}
|
Enable resource pool management (RPM).
|
2
|
Router(config)# resource-pool call treatment
resource {busy | channel-not-available}
|
Specify the desired call treatment when resource allocation fails to connect an incoming call.
|
3
|
Router(config)# resource-pool call treatment
profile {busy | no-answer }
|
Specify the desired call treatment when profile authorization fails for an incoming call.
|
4
|
Router(config)# resource-pool aaa protocol (local | group name}
|
Specify the authentication/authorization and accounting protocol for RPM. Group name specifies an authorization method that is not local; for example, an external AAA server group.
|
Example
The following example shows the commands used to enable resource pool management and establish the call treatments for incoming calls when resource allocation fails to connect (channel-not-available) and when profile authorization fails (no-answer). It also shows that local AAA has been chosen for the RPM configuration:
Router(config)# resource-pool enable
Router(config)# resource-pool call treatment resource channel-not-available
Router(config)# resource-pool call treatment profile no-answer
Router(config)# resource-pool aaa protocol local
Note that with RPM disabled, the resource groups will still take effect (that is, modem pooling will not be possible).
Note If you have an RPMS, you do not need to define VPDN groups and profiles, customer profiles, or DNIS groups on the NAS—you only need to define resource groups. Configure the remaining items by using the RPMS system.
Configuring DNIS Groups
This configuration task is optional. For default DNIS service, no DNIS group configuration is required. The following characteristics and restrictions apply to DNIS group configuration:
•Each DNIS group/call type combination can apply to only one customer profile.
•You can use up to four default DNIS groups (one for each call type).
•You must statically configure CAS call types.
•You can use x, X or . as wildcards within each DNIS number.
To configure DNIS groups for RPM implementations, perform the following steps, beginning from global configuration mode.
Step
|
Command
|
Purpose
|
1
|
Router(config)# dialer dnis group {dnis-group-name}
|
Create a DNIS group with a name of your choice. The name you specify in this step must be used when configuring the customer profile (see "Configuring Customer Profiles" on page 23).
|
2
|
Router(config-dnis-group)# call-type cas {digital | speech}
|
Statically set the call-type override for incoming CAS calls to either digital or speech.
|
3
|
Router(config-dnis-group)# number number
|
Add a DNIS number to the dialer DNIS group to be used in the customer profile. The DNIS number may have up to 65 characters; wildcards may be used.
|
Example
The following example shows the commands used to configure a DNIS group named cisco with a call type override for incoming CAS calls of speech and the DNIS numbers of 5552221210 through 5552221219:
Router(config)# dialer dnis group cisco
Router(config-dnis-group)# call-type cas speech
Router(config-dnis-group)# number 555222121x
Configuring Discriminator Profiles
Discriminator profiles enable you to process calls differently based on the call type and DNIS combination. To configure discriminator profiles for RPM implementation, perform the following steps, beginning from global configuration mode.
Step
|
Command
|
Purpose
|
1
|
Router(config)# resource-pool profile discriminator name
|
Create a call discriminator profile and assign it a name of up to 23 characters.
|
2
|
Router(config-call-discrimin)# call-type {all | digital | speech | v110 | v120}
|
Specify the type of calls you want to block. The NAS will not answer the call-type you specify.
|
3
|
Router(config-call-discrimin)# dnis group {dnis-group-name | default}
|
Enter the name of the DNIS group to be rejected by this call discriminator profile.
|
Note To create a call discriminator profile, you must specify both a call-type and a DNIS group. Once a DNIS group is associated with a call type in a discriminator, it cannot be used in any other discriminator.
Example
The following example shows a call discriminator named blocked1 being created and configured to block speech calls from the DNIS group named remotephone:
Router(config)# resource-pool profile discriminator blocked1
Router(config-call-discrimin)# call-type speech
Router(config-call-discrimin)# dnis group remotephone
Configuring Resource Groups
Note For external Cisco RPMS environments, configure resource groups on the NAS before defining them on external RPMS servers. For standalone NAS environments, first configure resource groups before using them in customer profiles.
•Resource groups can apply to multiple customer profiles.
•You can separate the physical resources into different resource groups.
