Specifications

Configuring Resource Pool Management
RPM Overview
DC-702
Cisco IOS Dial Technologies Configuration Guide
• Manage call sessions by differentiating dial customers through customer profiles. The customer
profile determines where resources are allocated and is based on the incoming Dialed Number
Information Service (DNIS) number or Calling Line Identification (CLID).
• Efficiently use resource groups such as modems to offer differing over subscription rates and dial
service-level agreements.
Note 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. FG D
is not supported. Cisco IOS software collects DNIS digits for the signaling types FGB, PRI, and SS7
and only E&M-FGB and R2 CAS customer profiles are supported. For all other CAS signaling types,
use the default DNIS group customer profiles.
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 DNIS and call type determined at the time
of an incoming call.
The components of incoming call management in the Cisco RPM are described in the following sections:
• Customer Profile Types
• DNIS Groups
• Call Types
• Resource Groups
• Resource Services
You can use Cisco RPM to answer all calls and differentiate customers by using VPDN profiles and
groups. The components of outgoing session management in the Cisco RPM are described in the
following sections:
• VPDN Groups
• VPDN Profiles
Note These components of Cisco RPM are enabled after the NAS and other equipment has been initially
set up, configured, and verified for proper operation of the dial, PPP, VPDN, and authentication,
authorization, and accounting (AAA) segments. Refer to the Cisco IOS documentation for these
other segments for installation, configuration, and troubleshooting information before attempting to
use RPM.
Configured DNIS groups and resource data can be associated to customer profiles. These customer
profiles are selected by the incoming call DNIS number and call type and then used to identify resource
allocations based on the associated resource groups and defined resource services.
After the call is answered, customer profiles can also be associated with VPDN groups so the configured
VPDN sessions and other data necessary to set up or reject a VPDN session are applied to the answered
calls. VPDN group data includes associated domain name or DNIS, IP addresses of endpoints, maximum
sessions per endpoint, maximum Multilink PPP (MLP) bundles per VPDN group, maximum links per
MLP bundle, and other tunnel information.