Credit Control Configuration Mode Commands


Credit Control Configuration Mode Commands
 
 
The Credit Control Configuration Mode is used to configure prepaid services for Diameter/RADIUS applications.
 
 
apn-name-to-be-included
This command configures whether the virtual or real APN name is sent in Credit Control Application messaging.
Product
All
Privilege
Security Administrator, Administrator
Syntax
apn-name-to-be-included { gn | virtual }
default apn-name-to-be-included
default
Configures the default option for this command.
Default: gn
gn
Sends Gn APN name in the CCA messages.
virtual
Sends virtual APN name, if configured in the APN Configuration Mode, in the CCA messages.
Usage
Use this command to configure the APN information in CCA messages. Virtual APN name can be set to be sent in CCA messages if it is configured in the APN Configuration Mode.
Example
The following command sets the virtual APN name to be sent in CCA message:
apn-name-to-be-included virtual
 
diameter dictionary
This command configures the Diameter Credit Control dictionary for the Active Charging Service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter dictionary { dcca-custom1 | dcca-custom10 | dcca-custom11 | dcca-custom12 | dcca-custom13 | dcca-custom14 | dcca-custom15 | dcca-custom16 | dcca-custom17 | dcca-custom18 | dcca-custom19 | dcca-custom2 | dcca-custom20 | dcca-custom3 | dcca-custom4 | dcca-custom5 | dcca-custom6 | dcca-custom7 | dcca-custom8 | dcca-custom9 | standard }
default diameter dictionary
default
Configures the default setting.
Default: standard dictionary
dcca-custom1 ... dcca-custom20
Specifies a custom Diameter dictionary.
standard
Specifies the standard Diameter dictionary.
Default: Enabled
Usage
Use this command to select the Diameter dictionary for Active Charging Service.
Example
The following command selects the standard Diameter dictionary:
diameter dictionary standard
 
diameter gsu-with-only-infinite-quota
This command configures whether to accept/reject CCA messages that contain Granted-Service-Unit AVP with only infinite quota grants from the server.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter gsu-with-only-infinite-quota { accept-credit-control-answer | reject-credit-control-answer }
default diameter gsu-with-only-infinite-quota
default
Configures the default setting.
Default: reject-credit-control-answer
accept-credit-control-answer
Specifies to accept the Credit-Control-Answer message.
reject-credit-control-answer
Specifies to reject the Credit-Control-Answer message.
Usage
Use this command to accept/reject CCA messages that contain Granted-Service-Unit AVP with only infinite quota grants from the server.
Example
The following command specifies to accept CCA with Granted-Service-Unit AVP containing only Infinite quota:
diameter gsu-with-only-infinite-quota accept-credit-control- answer
The following command configures to reject Granted-Service-Unit that contains only Infinite quota:
diameter gsu-with-only-infinite-quota reject-credit-control- answer
 
diameter ignore-returned-rulebase-id
This command configures to accept/ignore rulebase ID in Rulebase-Id AVP returned by the Diameter server in CCA message.
Product
All
Privilege
Security Administrator, Administrator
Syntax
[ default | no ] diameter ignore-returned-rulebase-id
default
Configures the default setting.
Default: accept
no
Specifies to accept the rulebase ID received from Diameter server in CCA.
Usage
Use this command to ignore/accept rulebase ID returned from the Diameter server in CCA.
Example
This following command specifies to ignore rulebase ID returned from Diameter server in CCA:
diameter ignore-returned-rulebase-id
 
diameter mscc-per-ccr-update
This command configures sending single/multiple Multiple-Services-Credit-Control (MSCC) AVP in CCR-U messages.
Important: This command is only available in StarOS 8.3 and later.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter mscc-per-ccr-update { multiple | single }
default diameter mscc-per-ccr-update
default
Configures the default setting.
Default: multiple
multiple
Specifies sending multiple Multiple-Services-Credit-Control AVP in a single CCR-U message.
single
Specifies sending only one Multiple-Services-Credit-Control AVP in a CCR-U message.
Usage
Use this command to configure sending single/multiple Multiple-Services-Credit-Control AVP in CCR-U messages.
Example
The following command configures sending a single MSCC AVP in CCR-U messages:
diameter mscc-per-ccr-update single
 
diameter origin host
 
This command is obsolete. See the diameter origin endpoint command.
 
diameter origin endpoint
This command configures the Diameter Credit Control Origin Endpoint.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter origin endpoint endpoint_name [ realm realm_name ]
no diameter origin endpoint
no
Removes the Diameter Credit Control Origin Endpoint configuration.
endpoint_name
Specifies the Diameter Credit Control Origin Endpoint.
endpoint_name must be the endpoint’s name, and an alpha and/or numeric string of 1 through 63 characters in length.
realm realm_name
Specifies the Diameter Credit Control Realm ID.
realm_name must be a string of 1 through 127 characters in length.
Usage
Use this command to configure the Diameter Credit Control Origin Endpoint.
The endpoint to configure should be pre-configured. For information on creating and configuring a Diameter endpoint, in the Context Configuration Mode, see the diameter endpoint command.
Example
The following command configures a Diameter Credit Control Origin Endpoint named test:
diameter origin endpoint test
 
diameter peer-select
This command configures the Diameter credit control primary and secondary hosts for DCCA.
Product
All
Privilege
Security Administrator, Administrator
Syntax
In StarOS 8.x:
diameter peer-select peer peer_name [ realm realm_name ] [ secondary-peer sec_peer_name [ realm realm_name ] ] [ imsi-based start-value imsi_start_value end-value imsi_end_value ]
no diameter peer-select [ imsi-based start-value imsi_start_value end-value imsi_end_value ]
In StarOS 9.0 and later for UMTS deployments:
diameter peer-select peer peer_name [ realm realm_name ] [ secondary-peer sec_peer_name [ realm realm_name ] ] [ imsi-based { [ prefix | suffix ] imsi/prefix/suffix_start_value } [ to imsi/prefix/suffix_end_value ] ]
no diameter peer-select [ imsi-based { [ prefix | suffix ] imsi/prefix/suffix_start_value } [ to imsi/prefix/suffix_end_value ]
no
Removes previously configured Diameter credit control peer selection setting.
peer peer_name
Specifies the primary host name.
peer_name must be an alpha and/or numeric string of 1 through 63 characters in length, and can contain punctuation characters.
imsi-based start-value imsi_start_value end-value imsi_end_value
Available only in StarOS 8.3 and earlier releases.
Specifies peer selection based on International Mobile Subscriber Identification (IMSI) range.
start-value imsi_start_value specifies the start of range in integer value of IMSI, and end-value imsi_end_value specifies the end of range in integer value of IMSI.
imsi-based { [ prefix | suffix ] imsi/prefix/suffix_start_value } [ to imsi/prefix/suffix_end_value ]
In this release, available only for UMTS deployments.
Specifies peer selection based on IMSI prefix or suffix or IMSI range.
prefix: Specifies the prefix range
suffix: Specifies the suffix range
imsi/prefix/suffix_start_value: Specifies the IMSI/prefix/suffix start value. prefix/suffix must be IMSI prefix/suffix, and must be an integer from 1 through 15 characters in length.
imsi/prefix/suffix_end_value: Specifies the IMSI/prefix/suffix end value. prefix/suffix must be IMSI prefix/suffix, and must be an integer from 1 through 15 characters in length, and must be greater than the start value.
Important: If prefix/suffix is used, the lengths of both start and end prefix/suffix must be equal. If the prefix or suffix keyword is not specified, it will be considered as suffix.
realm realm_name
The realm_name must be an alpha and/or numeric string of 1 through 127 characters in length, and can contain punctuation characters. The realm may typically be a company or service name.
secondary-peer sec_peer_name
Specifies a name for the secondary host to be used for failover processing. When the route-table does not find an AVAILABLE route, the secondary host performs a failover processing if the diameter session failover command is set.
sec_peer_name must be an alpha and/or numeric string of 1 through 63 characters in length, and can contain punctuation characters.
Usage
Use this command to configure Diameter credit control host selection.
If the diameter peer-select command is not configured, and if multiple peers are configured in the endpoint, the available peers configured in the endpoint are automatically chosen in a load-balanced round-robin manner.
In StarOS 9.0 and later, a prefix or suffix of IMSI or IMSI range can be configured. If prefix or suffix keyword is not specified, it will be considered as suffix. Up to 64 peer selects can be configured. At any time either prefix or suffix mode can be used in one DCCA config. If the prefix/suffix mode is used, the start and end prefix/suffix lengths must be equal.
StarOS 9.0 and later supports peer selection using prefix or suffix of IMSI or IMSI range. Subscribers are now assigned to a primary OCS instance based on the value of the IMSI prefix or suffix of a length of 1 to 15 digits. If the prefix or suffix keyword is not specified, it will be considered as suffix. Up to 64 peer selects can be configured. At a time either prefix or suffix mode can be used in one DCCA config. If prefix or suffix mode is used, the lengths of all prefix/suffix must be equal.
Each primary OCS may have a designated secondary OCS in case of failure of the primary. It will be the responsibility of the GGSN to use the appropriate secondary OCS in case of primary failure. The secondary OCS for each primary OCS will be one of the existing set of OCSs.
Example
The following command configures a Diameter credit control peer named test and the realm companyx:
diameter peer-select peer test realm companyx
The following command configures IMSI-based Diameter credit control peer selection in the IMSI range of 1234567890 to 1234567899:
diameter peer-select peer star imsi-based start-value 1234567890 end-value 1234567899
The following command configures IMSI-based DCCA peer selection with IMSI suffix of 100 through 200:
diameter peer-select peer test_peer realm test_realm secondary-peer test_sec_realm realm test_realm2 imsi-based suffix 100 to 200
 
diameter pending-timeout
This command configures the maximum time period to wait for response from a Diameter peer.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter pending-timeout duration
default diameter pending-timeout
default
Disables DCCA resending message at pending-timeout.
duration
Specifies the timeout duration in seconds.
duration must be an integer from 1 through 300.
after-expiry-try-secondary-host
This keyword is deprecated. This can now be managed using the retry-after-tx-expiry and go-offline-after-tx-expiry keywords in the failure-handling command.
Usage
Use this command to set the maximum time for Diameter credit control to receive a response from its peer.
DCCA refers to this as the Tx Timer. Typically, this should be configured to a value smaller than the response-timeout value of Diameter Endpoint Configuration Mode. That value is typically too large for DCCA's purposes.
If DCCA gets a “no available routes” error before pending-timeout expires, then DCCA tries to send to the secondary host (if one has been configured). If DCCA gets no response and pending-timeout expires, then DCCA either tries the secondary host or gives up. This can now be managed using the failure-handling command.
If routing has failed, i.e., the attempt to the primary host, as well as, the attempt to the secondary host (if that has been configured), then the processing configured by the failure-handling CLI command is performed.
The routing (i.e., returning a good response, no response or an error response such as "no available routes") is controlled by Diameter Endpoint Configuration Mode. That uses a watchdog timer (called Tw Timer) to attempt a different route to a host. Multiple routes could be attempted. If there's no response before the endpoint's configured response-timeout expires, then "no available routes" is the routing result. The routing logic remembers the status of routes, so it can return "no available routes" immediately, without using any timers.
The default case will disable DCCA resending message at Tx (pending-timeout). So messages are retried only at Tw (device watchdog timeout) by diabase or at response-timeout by DCCA.
Example
The following command configures a Diameter Credit Control Pending Timeout of 20:
diameter pending-timeout 20
 
diameter result-code
This command enables sending GTP Create-PDP-Context-Rsp message with cause code based on the DCCA result code.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter result-code { authorization-rejected | user-unknown } use-gtp-cause-code { authentication-failure | no-resource-available }
default diameter result-code { authorization-rejected | user-unknown } use-gtp-cause-code
authorization-rejected
Result code received as DIAMETER_AUTHORIZATION_REJECTED(5003).
user-unknown
Result code received as DIAMETER_USER_UNKNOWN(5030).
use-gtp-cause-code
Cause code to be sent in GTP response.
authentication-failure
To send GTP cause code GTP_USER_AUTHENTICATION_FAILED in GTP response.
no-resource-available
To send GTP cause code GTP_NO_RESOURCES_AVAILABLE in GTP response (default cause code).
Usage
On receiving result-code as AUTHORIZATION-REJECTED or DIAMETER_USER_UNKNOWN from DCCA server, the cause code can either be sent as GTP_NO_RESOURCE_AVAILABLE or GTP_AUTHENTICATION_FAILED in GTP create-PDP-Context response message, based on this CLI configuration. By default, GTP_NO_RESOURCE_AVAILABLE is sent.
Example
The following command sets the deny cause as user authentication failure when the CCA-Initial has the result code DIAMETER_AUTHORIZATION_REJECTED(5003):
diameter result-code authorization-rejected use-gtp-cause-code authentication-failure
 
diameter send-ccri
This command configures when to send CCR-Initial for the subscriber session.
Product
All
Privilege
Security Administrator, Administrator
Syntax
diameter send-ccri { session-start | traffic-start }
default diameter send-ccri
default
Configures the default setting.
Default: session-start
session-start
Specifies to send CCR-I when the PDP context is being established (on receiving Create-PDP-Context-Request).
traffic-start
Specifies to delay sending CCR-I until the first data packet received from the subscriber.
Usage
Use this command to configure when to send CCR-Initial for the subscriber session.
Example
The following command configures to send CCR-I on traffic detection and not on context creation:
diameter send-ccri traffic-start
 
diameter session failover
This command enables/disables Diameter Credit Control Session Failover. When enabled, the secondary peer is used in the event the main peer is unreachable.
Product
All
Privilege
Security Administrator, Administrator
Syntax
[ default | no ] diameter session failover
default
Configures the default setting.
Default: Depends on the failure-handling configuration
no
If the primary server is not reachable, failover is not triggered and the session is torn down. No failover action is taken.
Usage
Use this command to enable/disable Diameter Credit Control Session Failover.
The failure-handling configuration comes into effect only if diameter session failover is present in the configuration. The failover can be overridden by the server in the response message, and it takes precedence.
Example
The following command enables Diameter Credit Control Session Failover:
diameter session failover
 
end
Returns the CLI prompt to the Exec mode.
Product
All
Privilege
Security Administrator, Administrator
Syntax
end
Usage
Use this command to change to the Exec mode.
 
exit
Exits the current mode and returns to the Active Charging Service Configuration mode.
Product
All
Privilege
Security Administrator, Administrator
Syntax
exit
Usage
Use this command to return to the Active Charging Service Configuration mode.
 
failure-handling
This command configures the Diameter Credit Control Failure Handling (CCFH) behavior in the event of communication failure with the prepaid server.
Product
All
Privilege
Security Administrator, Administrator
Syntax
failure-handling { initial-request | terminate-request | update-request } { continue [ go-offline-after-tx-expiry | retry-after-tx-expiry ] | retry-and-terminate [ retry-after-tx-expiry ] | terminate }
default failure-handling [ initial-request | terminate-request | update-request ]
default failure-handling [ initial-request | terminate-request | update-request ]
Configures the default CCFH setting:
initial-request: The default setting is terminate.
update-request: The default setting is retry-and-terminate.
terminate-request: The default setting is retry-and-terminate.
initial-request
Specifies the message type as CCR-Initial.
terminate-request
Specifies the message type as CCR-Terminate.
update-request
Specifies the message type as CCR-Update.
continue
Specifies the CCFH setting as continue. The online session is converted into offline session. The associated PDP Context is established (new sessions) or not released (ongoing sessions).
retry-and-terminate
Specifies the CCFH setting as retry-and-terminate. The user session will continue for the duration of one retry attempt with the prepaid server. In case there is no response from both primary and secondary servers the session is torn down.
terminate
Specifies the CCFH setting as terminate. All type of sessions (initial or update) are terminated in case of failure.
go-offline-after-tx-expiry
Specifies to start offline charging after Tx expiry.
retry-after-tx-expiry
Specifies to retry after Tx expiry. Enables secondary-host, if up, to take over after Tx expiry.
Usage
Use this command to select the CCFH behavior. The specified behavior is used for sessions when no behavior is specified by the prepaid server. By default, the CCFH is taken care at response-timeout except for terminate setting.
If the Credit-Control-Failure-Handling AVP is received from the server, the received setting will be applied to all the message types.
The following table indicates the CCFH behavior for the combination of different CCFH settings, and the corresponding CLI commands.
Example
The following command sets the Credit Control Failure Handling behavior for initial request message type to retry-and-terminate:
failure-handling initial-request retry-and-terminate
 
mode
This command configures the Prepaid Credit Control mode to RADIUS or Diameter.
Product
All
Privilege
Security Administrator, Administrator
Syntax
mode { diameter | radius }
default mode
default
Configures the default prepaid credit control mode.
Default: Diameter
diameter
Enables Diameter Credit Control Application (DCCA) for prepaid charging.
radius
Enables RADIUS Credit Control for prepaid charging.
Usage
Use this command to configure the prepaid charging application mode between Diameter or RADIUS credit control.
Example
The following command specifies to use RADIUS prepaid credit control application:
mode radius
 
pending-traffic-treatment
This command controls the pass/drop treatment of traffic while waiting for definitive credit information from the server.
Product
All
Privilege
Security Administrator, Administrator
Syntax
pending-traffic-treatment { { { forced-reauth | trigger | validity-expired } drop | pass } | { { noquota | quota-exhausted } buffer | drop | pass } }
default pending-traffic-treatment { forced-reauth | noquota | quota-exhausted | trigger | validity-expired }
default
Configures the default setting.
Default: drop
forced-reauth
Sets the Diameter credit control pending traffic treatment to forced reauthorization.
trigger
Sets the Diameter credit control pending traffic treatment to trigger.
validity-expired
Sets the Diameter credit control pending traffic treatment to validity expired.
noquota
Sets the Diameter credit control pending traffic treatment to no quota.
quota-exhausted
Sets the Diameter credit control pending traffic treatment to quota exhausted.
buffer
Specifies to tentatively count/time traffic, and then buffer traffic pending arrival of quota. Buffered traffic will be forwarded and fully charged against the quota when the quota is eventually obtained and the traffic passed.
drop
Specifies to drop any traffic when there is no quota present.
pass
Specifies to pass all traffic more or less regardless of quota state.
Usage
Use this command to set the Diameter credit control pending traffic treatment while waiting for definitive credit information from the server.
This CLI command is different than the failure-handling CLI command, which specifies behavior in the face of an actual timeout or error, as opposed to the behavior while waiting. See also the buffering-limit CLI command in Active Charging Service Configuration Mode.
Example
The following command sets the Diameter credit control pending traffic treatment to drop any traffic when there is no quota present:
pending-traffic-treatment noquota drop
 
quota
This command is used to set various time-based quotas in the prepaid credit control service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
{ default | no } quota { holding-time | validity-time }
holding-time holding_time
Specifies the Quota Holding Time (QHT).
holding_time must be an integer from 1 through 4000000000.
validity-time validity_time
Specifies the validity lifetime of the quota.
validity_time must be an integer from 1 through 65535.
Usage
Use this command to set the prepaid credit control quotas.
Example
The following command sets the prepaid credit control request holding time to 30000 seconds:
quota holding-time 30000
 
quota request-trigger
This command is used to set the action on packets used from request trigger on crossing threshold limit of subscriber quota in the prepaid credit control service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
quota request-trigger { exclude-packet-causing-trigger | include-packet-causing-trigger }
{ default | no } quota request-trigger
default
Configures the default setting.
Default: Disabled
no
Disables time threshold for prepaid credit control quota.
exclude-packet-causing-trigger
Default: Disabled
This option excludes the packets causing threshold limit violation trigger in accounting.
include-packet-causing-trigger
Default: Disabled
This option includes the packets causing threshold limit violation trigger in accounting.
Usage
Use this command to set the action of packets causing threshold limit violation for prepaid credit control quotas.
Example
The following command sets the system to exclude the packets causing threshold limit triggers from accounting of prepaid credit of a subscriber:
quota request-trigger exclude-packet-causing-trigger
 
quota time-threshold
This command configures the time threshold limit for subscriber quota in the prepaid credit control service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
quota time-threshold { abs_time_value | percent percent_value }
{ default | no } quota time-threshold
default
Configures the default setting.
Default: Disabled
no
Disables time threshold for prepaid credit control quota.
abs_time_value
Default: 0 (Disabled)
Specifies the absolute threshold time in seconds for configured time quota in prepaid credit control charging.
abs_time_value must be an integer from 1 through 86400. To disable this assign 0.
percent percent_value
Specifies the time threshold value in percentage of configured time quota in DCCA.
percent_value must be an integer from 1 through 100.
Usage
Use this command to set the time threshold for prepaid credit control quotas.
Example
The following command sets the prepaid credit control time threshold to 400 seconds:
quota time-threshold 400
 
quota units-threshold
This command is used to set the unit threshold limit for subscriber quota in the prepaid credit control service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
quota unit-threshold { abs_unit_value | percent percent_value }
{ default | no } quota units-threshold
default
Configures the default setting.
Default: Disabled
no
Disables unit threshold for DCCA quota.
abs_unit_value
Default: 0 (Disabled)
Specifies the absolute threshold value in units for the configured units quota in prepaid credit control application.
abs_unit_value must be an integer from 1 through 4000000000. To disable this assign 0.
percent percent_value
Specifies the time threshold value in percentage of configured units quota in DCCA.
percent_value must be an integer from 1 through 100.
Usage
Use this command to set the units threshold for prepaid credit control quotas.
Example
The following command sets the prepaid credit control time threshold to 160400 units:
quota units-threshold 160400
 
quota volume-threshold
This command is used to set the volume threshold limit for subscriber quota in the prepaid credit control service.
Product
All
Privilege
Security Administrator, Administrator
Syntax
quota volume-threshold { abs_vol_value | percent percent_value }
{ default | no } quota volume-threshold
default
Configures the default setting.
Default: Disabled
no
Disables volume threshold for prepaid credit control quota.
abs_vol_value
Default: 0 (Disabled)
Specifies the absolute threshold volume in bytes to configured volume quota in prepaid credit control.
abs_vol_value must be an integer from 1 through 4000000000. To disable this assign 0.
percent percent_value
Specifies the volume threshold value in percentage of configured volume quota in prepaid credit control.
percent_value must be an integer from 1 through 100.
Usage
Use this command to set the volume threshold for prepaid credit control quotas.
Example
The following command sets the prepaid credit control volume threshold to 160400 bytes:
quota volume-threshold 160400
 
radius usage-reporting-algorithm
This command configures the usage reporting algorithm for RADIUS prepaid using DCCA.
Product
All
Privilege
Security Administrator, Administrator
Syntax
radius usage-reporting-algorithm { cumulative | relative }
default radius usage-reporting-algorithm
default
Configures the default setting.
Default: Cumulative
cumulative
Specifies that the total accumulated usage of quota be reported in every accounting interim.
relative
Specifies that the quota usage be reported per accounting interim. I.e., since the previous usage report.
Usage
Use this command to configure the usage reporting algorithm for RADIUS prepaid using DCCA.
Example
The following command configures the usage reporting algorithm for RADIUS prepaid using DCCA to relative:
radius usage-reporting-algorithm relative
 
timestamp-rounding
This command configures how to convert exact time into the units that are used in quotas.
Product
ECS
Privilege
Security Administrator, Administrator
Syntax
timestamp-rounding { ceiling | floor | roundoff }
default timestamp-rounding
default
Sets the default timestamp-rounding setting.
Default: roundoff
ceiling
This keyword round-off to the smallest integer greater than the fraction.
If the fractional part of the seconds is greater than 0, then this keyword adds 1 to the number of seconds and discard the fraction.
floor
This keyword always discards the fractional part of the second.
roundoff
This keyword sets the fractional part of the seconds to nearest integer value. If fractional value is greater than or equal to 0.5 it adds 1 to the number of seconds and discards the fractional part of second.
Usage
Use this command to configure how to convert exact time into the units that are used in quotas for CCA charging.
The specified rounding will be performed before system attempts any calculation. For example using round-off, if the start time is 1.4, and the end time is 1.6, then the calculated duration will be 1 (i.e., 2 – 1 = 1).
Example
The following command sets the CCA timestamp to nearest integer value second; i.e. 34:12.23 to 34:12.00:
timestamp-rounding roundoff
 
trigger type
This command enables or disables triggering a credit reauthorization when the named values in the subscriber session changes.
Product
All
Privilege
Security Administrator, Administrator
Syntax
[ no ] trigger type { cellid | lac | qos | rat | sgsn } +
default trigger type
default
Sets the default trigger type setting.
no
Removes the previously configured trigger type.
cellid
Sets the trigger based on change in cell identity or service area code (SAC)
lac
Sets the trigger based on change in Location Area Code.
qos
Sets the trigger based on change in the Quality of Service (QoS).
rat
Sets the trigger based on change in the Radio Access Technology (RAT).
sgsn
Sets the trigger based on change in the IP address of SGSN.
+
Indicates that more than one of the previous keywords can be entered within a single command.
Usage
Use this command to set the credit control reauthorization trigger.
Example
The following command selects a credit control trigger as lac:
trigger type lac
 
usage-reporting
This command configures the ACS Credit Control usage reporting type.
Product
All
Privilege
Security Administrator, Administrator
Syntax
usage-reporting quotas-to-report based-on-grant
default usage-reporting quotas-to-report
default
Configures the default setting.
Default: Disabled
Usage
Use this command to configure reporting usage only for granted quota. On issuing this command, the Used-Service-Unit AVP will report quotas based on grant i.e, only the quotas present in the Granted-Service-Unit AVP.
With this command only the units for which the quota was granted by the DCCA server will be reported irrespective of the reporting reason.
Example
The following command configures to report usage based only on granted quota:
usage-reporting quotas-to-report based-on-grant
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883