The industry's first example of second-generation policy management tools, Cisco RPMS brings to voice solutions the level of control previously enjoyed by data network providers.
Cisco RPMS allows service providers to:
| Features and Benefits of Cisco RPMS |
| Feature |
Benefit |
| DNIS groups |
Cisco RPMS includes an easy way to manage services using multiple DNIS entries. This scenario is especially useful with distributed dial services or universal toll-free dial services. |
| Trunk groups |
Service providers can provide port guarantees per regions to their customers even when the same DNIS is used in different regions. |
| DNIS wildcards |
A wildcard character (*) can be used in place of any number of digits in a DNIS to provision retail customers easily. |
PAP/CHAP selection |
Service providers can support a customer's choice of either Password Authentication Protocol (PAP) or Challenge Handshake Authentication Protocol (CHAP) for user authentication. |
| Call session and overflow limits |
Predefined service levels can be supplemented with the ability for users to exceed service levels when necessary but be charged premium rates. |
| Shared overflow pools |
Shared overflow pools with defined ratios of voice/dial calls can be created for one or more customers. |
| Variety of call types supported |
Cisco RPMS provides the tools to manage the full complement of service types delivered to the gateway by the PSTN. |
| Call discrimination |
Service providers can disallow calls that infringe on published rates because of the service type. (For example, ISDN data calls can be rejected for a number specifically rated for modem calls.) |
| Resource services |
Modem resources can be dynamically configured on a per-call basis, depending on the customer profile and service-level agreement. |
| Server-based session counting |
Using Cisco RPMS, service providers can centrally administer group-based service policies. |
| VPDN session and overflow limits |
When managing sessions after a call is answered, sessions may be limited with predefined service levels for VPDN groups enabled by the customer domain name. |
| VPDN tunnel limits |
This feature allows service providers to manage the number of sessions in a tunnel to prevent network congestion because each tunnel spanning the wide area network may use media with varied bandwidths. |
| VPDN tunnel load balancing |
Service providers can take advantage of multiple VPDN paths for better bandwidth utilization and higher service quality. |
| Flexible accounting |
Accounting information can be parsed from flat files or sent on to authentication, authorization, and accounting (AAA) servers to integrate easily with existing billing and reporting systems. |
| Synchronized call counting |
Cisco IOS Software delivers call accounting records for calls immediately to Cisco RPMS for synchronous call counting. Calls are recorded and counted against customers' quotas instantaneously. |
| Call Detail Record generation at call start |
Cisco RPMS offers the choice to generate call detail records (CDRs) at the beginning of a call to ensure accounting of calls that might not complete. Start/stop CDRs include rich information elements to allow tiered billing. |
| Reporting monitoring |
Administrators have instant access to dial service activity across POPs for troubleshooting and monitoring. |
| MGCP support for dial |
Cisco RPMS operates in a Media Gateway Control Protocol (MGCP) dial network using the Cisco gateway MGCP network access server package |
| Flexible configuration |
Service providers can configure Cisco IOS Software port management only for chassis-based management or add Cisco RPMS for centralized management, depending on their specific network architecture requirements. |
| RADIUS interface |
Cisco RPMS uses the RADIUS protocol for support of pre-authentication with other network access servers conforming to the RADIUS RFC standards. |
| Scalable architecture |
Cisco RPMS distributed architecture offers the flexibility to scale as service providers' networks grow. |
| Multiuser HTML administrative interface |
The graphical user interface (GUI) simplifies training requirements for administrators and allows remote operators in multiple locations to view or configure system and service parameters. |
| Cisco RPMS CLI |
The Cisco RPMS can be easily integrated with existing billing and provisioning systems using the Cisco RPMS command-line interface (CLI). |
| Call rejection |
A call is rejected if call volume or CPU utilization exceeds defined thresholds. A busy signal is sent to the PSTN if a call is rejected. |
| Configurable call threshold settings |
Administrators, customers, or sales departments can be alerted when problems occur, new capacity is required, or customers need to purchase more services. |
| Fault tolerance |
RPMS employs a hot-standby server for stateful failover. If the primary Cisco RPMS fails, the gateway automatically switches to the secondary server, maintaining state with no dropped calls. |
| SNMP manageability |
Cisco RPMS supports Simple Network Management Protocol Version 2 (SNMPv2) for network management and monitoring. |