|
|
Cisco Resource Pool Manager Server (Cisco RPMS) can support many types of service on the same network access servers (NASes). Each time you add a new customer or service, use one of the following:
Standard wholesale DNIS service uses DNIS numbers to accept or reject a call based on the call type (bearer capability) and session limits before it is answered and to establish VPDN tunnels. For an example of a standard wholesale DNIS configuration, see Figure 2-1.
Standard wholesale DNIS service is useful for giving each customer or service type separate access numbers and for conserving NAS resources by not answering calls when session limits are reached.
Standard wholesale DNIS service uses the following:
Standard wholesale domain name service always answers the call and uses the domain name in the user ID field to build a VPDN tunnel (if the domain name belongs to a VPDN group and is within session limits). Although this service uses more resources by answering all calls, DNIS-based resource management can be difficult to manage and new DNISes will have to be ordered each time you add a customer. For an example of a standard wholesale domain name configuration, see Figure 2-2.
Some trunks do not pass DNIS information. If this is true for your configuration, you must use standard wholesale domain name service to build VPDN tunnels.
Standard wholesale domain name service uses the following management methods:
Standard retail service always answers the call and uses the local AAA for user authentication. For an example of a retail configuration, see Figure 2-3.
Standard retail service uses the following:
Default customer profile wholesale DNIS service always answers the call and only uses the DNIS number to build a VPDN tunnel (if the DNIS number belongs to a VPDN group and is within session limits). For an example of an default customer profile wholesale DNIS configuration, see Figure 2-4.
Although default customer profile wholesale DNIS service consumes more resources by always answering calls, you might want to place all of your NASes in a single pool and use VPDN groups for session control.
Default customer profile wholesale DNIS service uses the following:
DNIS-based wholesale domain name service uses the DNIS number to accept or reject a call based on the session limits and the domain name to establish VPDN tunnels. For an example of a DNIS-based wholesale domain name configuration, see Figure 2-5.
DNIS-based wholesale domain name service works well for sharing smaller resource pools among customers. For example, you could offer levels of service that offered different oversubscription ratios. Session control for each level of service is managed through DNIS numbers and the domain name is used to route each call to the appropriate VPDN tunnel.
DNIS-based wholesale domain name service uses the following:
DNIS-based retail service uses the DNIS number to accept or reject a call based on the call type and session limits before it is answered and uses the local AAA for user authentication. For an example of a DNIS-based retail configuration, see Figure 2-6 .
DNIS-based retail works well when you want to create smaller resource pools and ensure that retail customers do not take over the NAS resources.
Standard retail service uses the following:
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Aug 31 07:33:17 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.