Configuring ISA Support for Prepaid Billing

Table Of Contents

Configuring ISA Support for Prepaid Billing

Contents

Prerequisites for ISA Prepaid Billing Support

Restrictions for ISA Prepaid Billing Support

Information About ISA Prepaid Billing Support

Overview of ISA Support for Prepaid Billing

ISA Prepaid Threshold

ISA Prepaid Idle Timeout

ISA Prepaid Tariff Switching

Benefits of ISA Prepaid Billing

How to Configure ISA Support for Prepaid Billing

Configuring RADIUS Attribute Support for ISA Prepaid Billing

Enabling ISA Prepaid Billing

Enabling ISA Prepaid Billing in a Service Policy Map

Enabling ISA Prepaid Billing in Service Profile on the AAA Server

Creating an ISA Prepaid Billing Configuration

Prerequisites

Redirecting Subscriber Traffic upon Exhaustion of Credit

Credit-Exhausted Event

Configuring L4 Redirection in a Service Policy Map

Applying a Service Policy Map to Subscriber Traffic Upon Exhaustion of Credit

What to Do Next

Forwarding Subscriber Traffic Upon Depletion of Quota

Quota-Depleted Event

Prerequisites

What to Do Next

Monitoring ISA Prepaid Billing Sessions

Troubleshooting ISA Prepaid Billing Support

Configuration Examples for ISA Prepaid Billing Support

ISA Prepaid Billing Support: Example

ISA Policies for Handling Credit-Exhausted and Quota-Depleted Prepaid Billing Events: Example

Additional References

Related Documents

Technical Assistance

Feature Information for ISA Support for Prepaid Billing

Configuring ISA Support for Prepaid Billing

---

The Intelligent Service Architecture (ISA) is a core set of Cisco IOS components that provide a structured framework in which edge access devices can deliver flexible and scalable services to subscribers. A Cisco device that is running a Cisco IOS image with ISA is called an Intelligent Service Gateway (ISG). ISA prepaid billing support allows an ISG to check a subscriber's available credit to determine whether to allow the subscriber access to a service and how long the access can last. ISA prepaid billing works on a repeated reauthorization model in which fragments of credit, called quotas, are allotted by a prepaid billing server. This model allows a subscriber to be connected to multiple simultaneous prepaid services, each with a different billing rate. ISA supports time- and volume-based prepaid billing.

This module provides information about how to configure ISA support for prepaid billing.

Module History

This module was first published on April 11, 2005, and was last updated April 11, 2005.

Finding Feature Information in This Module

Your Cisco IOS software release may not support all features. To find information about feature support and configuration, use the "Feature Information for ISA Support for Prepaid Billing" section.

Contents

•Prerequisites for ISA Prepaid Billing Support

•Restrictions for ISA Prepaid Billing Support

•Information About ISA Prepaid Billing Support

•How to Configure ISA Support for Prepaid Billing

•Configuration Examples for ISA Prepaid Billing Support

•Additional References

•Feature Information for ISA Support for Prepaid Billing

Prerequisites for ISA Prepaid Billing Support

The tasks in this document assume a subscriber session has been created a method of service activation is in place.

Restrictions for ISA Prepaid Billing Support

•ISA prepaid billing support can only be applied to traffic flows that have been defined by an ISA traffic class.

•Quotas are measured in seconds for time or bytes for volume. There is no way to change the unit of measure.

•The volume quota is for combined upstream and downstream traffic.

Information About ISA Prepaid Billing Support

Before you configure support for ISA prepaid billing, you should understand the following concepts:

•Overview of ISA Support for Prepaid Billing

•ISA Prepaid Threshold

•ISA Prepaid Idle Timeout

•ISA Prepaid Tariff Switching

•Benefits of ISA Prepaid Billing

Overview of ISA Support for Prepaid Billing

ISA prepaid billing support allows an ISG to check the available credit for a subscriber to determine whether to activate the service for the subscriber and how long the session can last. The subscriber's credit is administered by a prepaid billing server as a series of quotas representing either a duration of use (in seconds) or an allowable data volume (in bytes). A quota is an allotment, or fragment, of available credit. Allocating quota in fragments rather than providing all the credit at once enables ISA to support the use of credit for multiple simultaneous prepaid sessions.

ISA uses the RADIUS protocol to facilitate interaction between ISG and external authentication, authorization, and accounting (AAA) servers and prepaid billing servers. A single device can serve as the AAA server and the billing server.

To obtain the first quota for a session, ISG submits an authorization request to the AAA server. The AAA server contacts the prepaid billing server, which forwards the quota values to the ISG. ISG then monitors the session to track the quota usage. When the quota runs out or a specified limit is reached, ISG performs reauthorization. During reauthorization, the prepaid billing server may provide ISG with an additional quota if there is available credit. If no further quota is provided, ISG will log the user off from the service or perform some other specified action.

When a service is deactivated, the cumulative usage is provided to the prepaid billing server in an Accounting-Stop message.

ISA Prepaid Threshold

By default, the ISG sends reauthorization requests to the billing server when a subscriber's quota is exhausted. ISA prepaid thresholds allow the ISG to send reauthorization requests before a quota is used up. When a prepaid threshold is configured, the ISG sends a reauthorization request to the billing server when the amount of remaining quota is equal to the value of the threshold. Prepaid thresholds can be configured for both time and volume.

For example, if the prepaid threshold is configured for 10 seconds, and the prepaid billing server sends the ISG a quota of 30 seconds, the ISG will send a reauthorization request to the prepaid billing server when the subscriber has used up 20 seconds of the quota and has 10 seconds remaining.

ISA Prepaid Idle Timeout

The ISA prepaid idle timeout can be used to suspend a prepaid service session if no traffic is received for a specified period of time. The ISG keeps the session up during the suspension but releases all quota previously received for the prepaid session. Subsequent traffic on the session will cause the ISG to send a reauthorization request and download a new quota for the session.

ISA Prepaid Tariff Switching

Prepaid tariff switching allows changes in tariffs during the lifetime of a session. Typically, a service provider uses prepaid tariff switching to offer different tariffs to an end user during an active connection; for example, changing a user to a less expensive tariff during off-peak hours.

---

Note The ISG is not involved in computing the billing rate changes that occur at tariff switch points. Billing rate change computations are performed by the prepaid billing server.

---

ISA supports prepaid tariff switching by using two quotas that correspond to the pre-tariff switch time period and post-tariff switch time period. In the authorization response to the ISG, the prepaid billing server specifies the tariff change time and the quotas for pre-tariff switch and post-tariff switch periods.

The ISG uses the pre-tariff switch quota until the tariff switch occurs. If the pre-tariff switch quota is exhausted (or the threshold is reached) prior to the tariff switch, reathorization occurs as usual. Upon tariff switch, the ISG starts using the post-tariff switch quota for prepaid session monitoring. Reauthorization occurs only when either of these quotas is exhausted, not when a tariff change occurs.

This dual quota approach to accounting for prepaid tariff switching staggers reauthorization requests according to the usage of the subscriber and prevents the billing server from being overwhelmed with reauthorization requests at the time of a tariff switch.

Benefits of ISA Prepaid Billing

Concurrent Prepaid Service Access

The ISA Support for Prepaid Billing feature is capable of supporting concurrent prepaid service access while maintaining the same pool of quota at the prepaid billing server. ISA services can be configured for concurrent or sequential access. Concurrent access allows users to log on to a service while simultaneously connected to other services.

Real-Time Billing

The ISA Support for Prepaid Billing feature allows for real-time billing with maximum flexibility, regardless of the type of service and billing scheme. Users can be billed on a flat rate, air-time, or volume basis.

Redirection Upon Exhaustion of Quota

When a user runs out of quota, the ISG can redirect the user to a portal where the user can replenish the quota without being disconnected from the service.

Returning Residual Quota

The ISG can return residual quota to the billing server from services that a user is logged into but not actively using. The quota that is returned to the billing server can be applied to other services that the user is actively using.

Threshold Values

ISA enables you to configure threshold values that cause prepaid sessions to be reauthorized before the subscriber completely consumes the allotted quota for a service.

Traffic Status During Reauthorization

You can prevent revenue leaks by configuring the ISG to drop connected traffic during reauthorization of a service. The user remains connected to the service and does not need to log in to the service again, but no traffic is forwarded during the reauthorization process. This prevents a user from continuing to use a service for which they have run out of quota while the ISG sends a reauthorization request to the billing server.

Simultaneous Volume-Based and Time-Based Prepaid Billing

ISA supports rating on both time and volume simultaneously for prepaid services. The prepaid billing server may allocate quotas in both time and volume, and the ISG monitors the session on both these parameters. The ISG performs a reauthorization whenever either of these quota types is exhausted.

How to Configure ISA Support for Prepaid Billing

This section documents the following tasks:

•Configuring RADIUS Attribute Support for ISA Prepaid Billing (required)

•Enabling ISA Prepaid Billing (required)

•Creating an ISA Prepaid Billing Configuration (optional)

•Redirecting Subscriber Traffic upon Exhaustion of Credit (optional)

•Forwarding Subscriber Traffic Upon Depletion of Quota (optional)

•Monitoring ISA Prepaid Billing Sessions (optional)

•Troubleshooting ISA Prepaid Billing Support (optional)

Configuring RADIUS Attribute Support for ISA Prepaid Billing

Perform this task to enable the ISG to include RADIUS attribute 44 in Access-Request packets and attribute 55 in Accounting-Request packets.

SUMMARY STEPS

1. enable

2. configure terminal

3. radius-server attribute 44 include-in-access-req [vrf vrf-name]

4. radius-server attribute 55 include-in-acct-req

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	radius-server attribute 44 include-in-access-req [vrf vrf-name] Example: Router(config)# radius-server attribute 44 include-in-access-req	Sends RADIUS attribute 44 (Accounting Session ID) in Access-Request packets before user authentication.
Step 4	radius-server attribute 55 include-in-acct-req Example: Router(config)# radius-server attribute 55 include-in-acct-req	Sends the RADIUS attribute 55 (Event-Timestamp) in Accounting-Request packets.

Enabling ISA Prepaid Billing

Perform one of the following tasks to enable prepaid billing in a service policy map or a remote service profile:

•Enabling ISA Prepaid Billing in a Service Policy Map

•Enabling ISA Prepaid Billing in Service Profile on the AAA Server

Enabling ISA Prepaid Billing in a Service Policy Map

Perform this task to enable ISA prepaid billing support in a service policy map.

Prerequisites

ISA prepaid billing is enabled in a traffic class within a service policy map. This task assumes that you have defined the traffic class map and associated IP access lists. See the module "Configuring ISA Subscriber Services" for more information.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service policy-map-name

4. class type traffic class-map-name

5. prepaid config name-of-configuration

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type service policy-map-name Example: Router(config)# policy-map service mp3	Creates or defines a service policy map, which is used to define an ISA service.
Step 4	class type traffic class-map-name Example: Router(config-service-policymap)# class type traffic class-acl-101	Associates a previously configured traffic class to the policy map.
Step 5	prepaid config name-of-configuration Example: Router(config-control-policymap-class-traffic)# prepaid config conf-prepaid	Enables ISA support for prepaid billing and applies a configuration that defines the prepaid billing parameters. Note The presence of this command does not guarantee that prepaid billing will be applied to the flow. This command causes the first prepaid authorization request. Whether prepaid billing will be applied to the flow is determined by the billing server.

What to Do Next

You may want to configure a method of activating the service policy map or service profile; for example, control policies can be used to activate services. For more information about methods of service activation, see the module "Configuring ISA Subscriber Services."

Enabling ISA Prepaid Billing in Service Profile on the AAA Server

Perform this task to enable ISA support for prepaid billing in a service profile that is configured on a remote AAA server.

SUMMARY STEPS

1. Add the ISA Traffic Class attribute to the service profile.

2. Add the ISA Prepaid Billing VSA to the service profile.

DETAILED STEPS

	Command or Action	Purpose
Step 1	Add the ISA Traffic Class attribute to the service profile. Cisco-AVpair = "ip:traffic-class=in access-group [<acl_number> | name <acl_name>] [priority <n>]" or Cisco-AVpair = "ip:traffic-class=out access-group [<acl_number> | name <acl_name>] [priority <n>]"	Specifies input and output traffic to which the service will apply. •Both an input and output traffic classifier can be added to a service profile.
Step 1	Add the ISA Prepaid Billing VSA to the service profile. 26,9,1 = "prepaid-config={<name-of-config> | default"	Enables ISA support for prepaid billing and applies a configuration that defines the prepaid billing parameters.

What to Do Next

You may want to configure a method of activating the service policy map or service profile; for example, control policies can be used to activate services. For more information about methods of service activation, see the module "Configuring ISA Subscriber Services."

Creating an ISA Prepaid Billing Configuration

Perform this task to create or modify an ISA prepaid billing parameters configuration. This configuration can be referenced in service profiles or service policy maps in which ISA prepaid support has been enabled.

Note that a default prepaid configuration exists with the following parameters:

subscriber feature prepaid default

 threshold time 0 seconds

 threshold volume 0 bytes

 method-list authorization default

 method-list accounting default

 password cisco

The default configuration will not show up in the output of the show running-config command unless you change any one of the parameters.

The parameters of named prepaid configurations are inherited from the default configuration, so if you create a named prepaid configuration and want only one parameter to be different from the default configuration, you have to configure only that parameter.

Prerequisites

This task assumes that AAA method lists, server groups, and servers have been configured. See the Cisco IOS Security Configuration Guide for more information.

SUMMARY STEPS

1. enable

2. configure terminal

3. subscriber feature prepaid {name-of-config | default}

4. interim-interval number-of-minutes

5. method-list {accounting | authorization} name-of-method-list

6. password password

7. threshold {time number-of-seconds | volume number-of-bytes}

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	subscriber feature prepaid {name-of-config | default} Example: Router(config)# subscriber feature prepaid conf-prepaid	Creates a new ISA prepaid configuration or specifies an existing configuration so it can be modified.
Step 4	interim-interval number-of-minutes Example: Router(config-prepaid)# interim-interval 5	Configures the interval at which the ISG sends interim prepaid accounting records.
Step 5	method-list {accounting | authorization} name-of-method-list Example: Router(config-prepaid)# method-list accounting list1	Specifies the AAA method list to be used for ISA prepaid accounting or authorization.
Step 6	password password Example: Router(config-prepaid)# password cisco	Configures the password to be used for ISA prepaid authorization and reauthorization requests.
Step 7	threshold {time number-of-seconds | volume number-of-bytes} Example: Router(config-prepaid)# threshold time 20	Configures the threshold at which ISA will send a reauthorization request to the prepaid billing server. The quota provided by the billing server minus the configured threshold equals the value at which ISA will send a reauthorization request •This command can be entered twice to configure thresholds in both time and volume.

Redirecting Subscriber Traffic upon Exhaustion of Credit

Service providers often want to offer subscribers an opportunity to recharge their accounts when they have run out of credit for their prepaid services. The tasks in this section enable you to redirect a subscriber's Layer 4 traffic to a specified server when the subscriber has run out of credit.

Before you configure ISA Layer 4 Redirect for exhaustion of credit, you should understand the following concept:

•Credit-Exhausted Event

Perform the following tasks to redirect a subscriber's Layer 4 traffic upon exhaustion of credit:

•Configuring L4 Redirection in a Service Policy Map

•Applying a Service Policy Map to Subscriber Traffic Upon Exhaustion of Credit

Credit-Exhausted Event

The ISA credit-exhausted event occurs when the prepaid server responds with an Access-Accept packet with a quota value of zero (time or volume) and an idle timeout greater than zero. In this case, the prepaid server has determined for certain that the subscriber does not have enough credit, but the idle timeout provides a grace period in which the subscriber could recharge the account. Typically, a service provider would want to redirect the subscriber's traffic to a web portal where the subscriber could recharge the account. At the end of the idle-timeout interval, the ISG will send a reauthorization request.

The default ISA behavior is to drop subscriber packets when the credit-exhausted event occurs.

---

Note Layer 4 Redirection is one action that a service provider could take when a subscriber has run out of credit. Other actions can be configured instead of or in addition to Layer 4 Redirection.

---

Configuring L4 Redirection in a Service Policy Map

Perform this task to configure ISA Layer 4 redirection in a service policy map.

The ISA Layer 4 Redirect feature can also be configured in a service profile on a AAA server. For more information about redirecting Layer 4 subscriber traffic, see the module "Redirecting Subscriber Traffic Using ISA Layer 4 Redirect".

Prerequisites

The ISA Layer 4 Redirect feature is configured under a traffic class within the service policy map. This task assumes that you have defined the traffic class map. See the module "Configuring ISA Subscriber Services" for more information.

Traffic can be redirected to a server or server group. If you are redirecting traffic to a server group, this task assumes that the server group has been configured. See the module "Configuring ISA Subscriber Services" for more information about configuring server groups.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service policy-map-name

4. class type traffic class-name

5. redirect [list access-list-number] to {group server-group-name | ip ip-address [port port-number]} [duration seconds] [frequency seconds]

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type service policy-map-name Example: Router(config)# policy-map type service redirect-service	Creates or defines a service policy map, which is used to define an ISA service.
Step 4	class type traffic class-name Example: Router(config-service-policymap)# class type traffic class-all	(Optional) Associates a previously configured traffic class to the policy map.
Step 5	redirect [list access-list-number] to {group server-group-name | ip ip-address [port port-number]} [duration seconds] [frequency seconds] Example: Router(config-service-policymap-class-traffic)# redirect to group redirect-sg	Redirects traffic to a specified server or server group.

Applying a Service Policy Map to Subscriber Traffic Upon Exhaustion of Credit

Perform this task to configure a control policy that will apply a service to subscriber traffic upon exhaustion of credit.

Prerequisites

If you specify a named control class map, this task assumes that the class map has been configured. See the module "Configuring ISA Control Policies" for information about configuring control class maps.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type control policy-map-name

4. class type control {control-class-name | always} event credit-exhausted

5. action-number service-policy type service policy-map-name

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type control policy-map-name Example: Router(config)# policy-map type control policyA	Creates or modifies a policy map that defines a control policy.
Step 4	class type control {control-class-name | always} event credit-exhausted Example: Router(config-control-policymap)# class type control always event credit-exhausted	Specifies a control class and event for which actions may be configured.
Step 5	action-number service-policy type service policy-map-name Example: Router(config-control-policymap-class-control)# 1 service-policy type service redirect-profile	Applies the specified service policy map. •Applies the service policy map or service profile in which the ISA Layer 4 Redirect feature has been configured.

What to Do Next

Control policies must be applied to a context by using the service-policy type control command.

Forwarding Subscriber Traffic Upon Depletion of Quota

By default, ISA drops subscriber packets when a subscriber's quota has been depleted. This task enables you override the default and forward subscriber traffic when the quota-depleted event occurs.

Before you perform this task you should understand the concept described in the "Quota-Depleted Event" section.

Quota-Depleted Event

A quota-depleted event occurs when a subscriber's quota is exhausted and ISA has not yet received a reauthorization response from the billing server. This event can occur in two situations:

•When a prepaid threshold is not configured and the subscriber's quota is used up.

•When a prepaid threshold is configured but the quota is exhausted before the prepaid server responds to the reauthorization request that the ISG sent when the threshold was met.

The quota-depleted event is not necessarily an indication that a subscriber does not have any more credit. The ISG does not know for certain whether the subscriber has any more credit until a reauthorization response is returned from the billing server. For this reason, some service providers may choose to forward subscriber packets upon quota depletion until a reauthorization response is returned.

The default ISG behavior is to drop subscriber packets when a quota-depleted event occurs.

Prerequisites

If you specify a named control class map, this task assumes that the class map has been configured. See the module "Configuring ISA Control Policies" for information about configuring control class maps.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type control policy-map-name

4. class type control {control-class-name | always} event quota-depleted

5. action-number set-param drop-traffic false

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type control policy-map-name Example: Router(config)# policy-map type control policyB	Creates or modifies a policy map that can be applied globally, to an interface, or to an ATM VC to specify a control policy.
Step 4	class type control {control-class-name | always} event quota-depleted Example: Router(config-control-policymap)# class type control always event quota-depleted	Specifies a control class and event for which actions may be configured.
Step 5	action-number set-param drop-traffic false Example: Router(config-control-policymap-class-control)# 1 set-param drop-traffic false	Configures the ISG to drop traffic.

What to Do Next

Control policies must be applied to a context by using the service-policy type control command.

Monitoring ISA Prepaid Billing Sessions

Perform this task to monitor ISA prepaid sessions.

SUMMARY STEPS

1. enable

2. show subscriber session [detailed] [identifier identifier | uid session-id | username name]

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	show subscriber session [detailed] [identifier identifier | uid session-id | username name] Example: Router# show subscriber session detailed	Displays ISA subscriber session information.

Troubleshooting ISA Prepaid Billing Support

Perform these steps to troubleshoot ISA prepaid billing support.

SUMMARY STEPS

1. show subscriber session

2. Make sure service authentication was successful.

3. Make sure the AAA method list is valid and has been configured.

4. test aaa

5. debug subscriber policy prepaid

DETAILED STEPS

---

Step 1 Use the show subscriber session command to make sure the service in which prepaid billing support is configured has been activated.

Step 2 If the service requires service authentication, make sure the authentication succeeded.

Step 3 Make sure the AAA method list referred to in the prepaid billing configuration is valid and has been configured with the aaa accounting network command.

Step 4 Use the test aaa command to make sure the AAA server is reachable from the ISG.

Step 5 Use the debug subscriber policy prepaid command to display debug messages about prepaid operation.

---

Configuration Examples for ISA Prepaid Billing Support

This section contains the following examples:

•ISA Prepaid Billing Support: Example

•ISA Policies for Handling Credit-Exhausted and Quota-Depleted Prepaid Billing Events: Example

ISA Prepaid Billing Support: Example

The following example shows ISA prepaid billing support configured with the following parameters:

•The time threshold is 20 seconds.

•The volume threshold is 1000 bytes, which is derived from the default prepaid configuration.

•When the quota-depleted event occurs, ISA will drop subscriber packets until the billing server sends another quota.

•When the credit-exhausted event occurs, subscriber packets will be redirected to the server group "redirect-sg".

•The prepaid service is called "mp3" and is configured directly on the router in a service policy map.

•The AAA method list that will be used for this service to authenticate subscribers is called "cp-mlist". That is the same method list to which the service accounting records will be sent.

•Prepaid authorization, reauthorization and accounting messages will be sent to the AAA method list called "ap-mlist".

!

aaa authorization network default local

aaa authorization network ap-mlist group sg2

aaa authentication network cp-mlist group sg1

aaa accounting network cp-mlist group sg1

aaa accounting network ap-mlist group sg2

service-policy type control RULEA 

!

class-map type traffic CLASS-ALL

!

class-map type traffic CLASS-ACL-101

    match access-group input 101

!

policy-map type control RULEA

 class type control always event credit-exhausted

  1 service-policy type service redirectprofile

!

policy-map type service redirectprofile

 class type traffic CLASS-ALL

  redirect to group redirect-sg

policy-map type service mp3

 class type traffic CLASS-ACL-101

  authentication method-list cp-mlist

  accounting method-list cp-mlist

  prepaid conf-prepaid 

subscriber feature prepaid conf-prepaid

 threshold time 20

 threshold volume 0

 method-list accounting ap-mlist

 method-list authorization default

 password cisco

subscriber feature prepaid default

 threshold time 0

 threshold volume 1000

 method-list accounting default

 method-list authorization default

 password cisco

ISA Policies for Handling Credit-Exhausted and Quota-Depleted Prepaid Billing Events: Example

In the following example, a single control policy called "RULEA" has been defined to override the ISA prepaid default behavior by forwarding subscriber packets after a quota-depleted event and redirecting subscriber packets after a credit-exhausted event.

!class-map type traffic CLASS-ALL

!

policy-map type control RULEA

 class type control always event quota-depleted

  1 set-param drop-traffic false

 class type control always event credit-exhausted

  1 service-policy type service l4redirect

!

policy-map type service l4redirect

 class type traffic CLASS-ALL

  redirect to group SESM

!

subscriber feature prepaid conf-prepaid

 threshold time 100

 threshold volume 1000 

 method-list author prepaidlist

 method-list accounting default

 password cisco

subscriber feature prepaid default

 threshold time 0

 threshold volume 0

 method-list author default

 method-list accounting default

 password cisco

Additional References

The following sections provide references related to ISA support for prepaid billing.

Related Documents

Related Topic	Document Title
ISA commands	Intelligent Service Architecture Command Reference
AAA configuration tasks	The "Authentication, Authorization, and Accounting (AAA)" section in the Cisco IOS Security Configuration Guide, Release 12.2.
AAA commands	The "Authentication, Authorization, and Accounting (AAA) section in the Cisco IOS Security Command Reference, Release 12.2.

Technical Assistance

Description	Link
Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.	http://www.cisco.com/public/support/tac/home.shtml

Feature Information for ISA Support for Prepaid Billing

Table 13 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(27)SBA or later appear in the table.

Not all commands may be available in your Cisco IOS software release. For details on when support for specific commands was introduced, see the command reference documents.

If you are looking for information on a feature in this technology that is not documented here, see the "Intelligent Service Architecture Features Roadmap."

Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

---

Note Table 13 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

---

Table 13 Feature Information for ISA Support for Prepaid Billing

Feature Name	Releases	Feature Configuration Information
ISA:Accounting: Prepaid	12.2(27)SBA	ISA prepaid billing support allows an ISG to check a subscriber's available credit to determine whether to allow the subscriber access to a service and how long the access can last. ISA supports time- and volume-based prepaid billing. The following sections provide information about this feature: •Information About ISA Prepaid Billing Support •How to Configure ISA Support for Prepaid Billing
ISA: Accounting: Tariff Switching	12.(27)SBA	Prepaid tariff switching allows changes in tariffs during the lifetime of a session. ISA supports prepaid tariff switching by using two quotas that correspond to the pre-tariff switch time period and post-tariff switch time period.Tariff switching can also be used between accounting methods, such as switching from prepaid billing to post paid billing. •ISA Prepaid Tariff Switching •How to Configure ISA Support for Prepaid Billing

Copyright © 2005 Cisco Systems, Inc. All rights reserved.
This module first published April 11, 2005. Last updated April 11, 2005.