This command allows configuring a token to be used for appending original URL to the redirect address.

Product

GGSN

HA

IPSG

PDSN

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter redirect-url-token string
default diameter redirect-url-token 

default

Configures this command with the default setting.

string

The redirect url token name must be an alphanumeric string of size 1 through 63 characters.

Usage Guidelines

The chassis should perform dynamic Advice of Charge (AoC) redirections (URL provided by Online Charging System (OCS)) for a particular Service ID/Rating Group combination without affecting the flows mapped to other Service ID/Rating Group combinations. Redirections can be removed by OCS for a particular MSCC (Service ID/Rating Group combination) using a RAR message containing a specific Service ID/Rating Group combination.

As part of redirection to an AoC or Top-UP server (302 Moved HTTP message) the PCEF should be able to append the original HTTP URL to the redirected session. This way, once the subscriber has successfully been redirected (and potentially topped up their prepaid account) they can be presented with an option to be redirected back to their original URL. The OCS can indicate to the PCEF if the original URL is to be appended to the redirection by specifying a special character to the end of the AoC redirection — for example, a "?" character.

Upon final unit indication a redirect server address will be returned together with the FUI.

On redirection, the redirect URL will be appended with the original URL information using the token name configured with the diameter redirect-url-token command so that on completion of AoC, the AoC server may redirect the client back to the original location.

For example:

When the original URL was http:/​/​homepage/​

OCS provided URL:

http:/​/​test.dev.mms.ag/​test/​aoc.htm?appName=Return&CODE=UPSELL&OCSCode=FWB&SessionID=4:0001-diamproxy.st40gy2;130020198;9243;1b02:12000:12000:H:AOC:1299597546:UPSELL:N&transID=AOCPurchasepage?

The text in bold in the following sample indicates the current configuration for implementing the dynamic AoC redirection.

http:/​/​test.dev.mms.ag/​test/​aoc.htm?appName=Return&CODE=UPSELL&OCSCode=FWB&SessionID=4:0001-diamproxy.st40gy2;130020198;9243;1b02:12000:12000:H:AOC:1299597546:UPSELL:N&transID=AOCPurchasepage&returnUrl=http:/​/​homepage/​

This command allows you to control the starting of validity timer for the FUI-redirect scenario.

Product

GGSN

HA

IPSG

PDSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter redirect-validity-timer { immediate | traffic-start }
default diameter redirect-validity-timer

default

Configures this command with the default setting. By default, the validity timer is started on receiving the first matching packet.

immediate

This keyword will make the redirect-validity-timer to get started immediately.

traffic-start

This keyword will make the redirect-validity-timer to get started only on receiving matchingtraffic. This is the default configuration.

Usage Guidelines

Use this CLI command to control the starting of validity timer on receipt of CCA in all cases. Based on the configuration value, DCCA decides when to start the redirect-validity-timer. By default, it is started on receiving the first matching packet.

This command enables sending a GTP Create-PDP-Context-Rsp message with cause code based on the DCCA result code.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter result-code { authorization-rejected | credit-limit-reached | end-user-service-denied | user-unknown } use-gtp-cause-code { apn-access-denied-no-subscription | authentication-failure | no-resource-available | system-failure }
default diameter result-code { authorization-rejected | credit-limit-reached | end-user-service-denied | user-unknown } use-gtp-cause-code

default

Configures this command with the default setting.

In 12.1 and earlier releases: no-resource-available

In 12.2 and later releases: system-failure

authorization-rejected

Result code received as DIAMETER_AUTHORIZATION_REJECTED(5003).

credit-limit-reached

Result code received as DIAMETER_CREDIT_LIMIT_REACHED(4012).

end-user-service-denied

Result code received as DIAMETER_END_USER_DENIED(4010).

user-unknown

Result code received as DIAMETER_USER_UNKNOWN(5030).

use-gtp-cause-code

Cause code to be sent in GTP response.

apn-access-denied-no-subscription

Sends the GTP cause code GTP_APN_ACCESS_DENIED_NO_SUBSCRIPTION in GTP response.

If this keyword is configured and if the CCR-U is received with auth-rejected(5003) or credit-limit-reached(4012) or user-unknown(5030) or end-user-service-denied(4010), then the GTP result-code is sent as "apn-access-denied-no-subscription".

authentication-failure

Sends the GTP cause code GTP_USER_AUTHENTICATION_FAILED in GTP response.

no-resource-available

Sends the GTP cause code GTP_NO_RESOURCES_AVAILABLE in GTP response.

system-failure

Sends the GTP cause code GTP_SYSTEM_FAILURE in GTP response.

Usage Guidelines

On receiving result-code as AUTHORIZATION-REJECTED, CREDIT_LIMIT_REACHED, END_USER_DENIED or USER_UNKNOWN from DCCA server, based on this CLI configuration, in GTP Create-PDP-Context Response message the cause code can either be sent as GTP_NO_RESOURCE_AVAILABLE or GTP_AUTHENTICATION_FAILED or GTP_SYSTEM_FAILURE or GTP_APN_ACCESS_DENIED_NO_SUBSCRIPTION.

This command configures when to send an initial Credit Control Request (CCR-I) for the subscriber session.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter send-ccri { session-start | traffic-start }
default diameter send-ccri

default

Configures this command with the default setting.

Default: session-start

session-start

Sends CCR-I when the PDP context is being established (on receiving Create-PDP-Context-Request).

traffic-start

Delays sending CCR-I until the first data packet is received from the subscriber.

Usage Guidelines

Use this command to configure when to send CCR-Initial for the subscriber session.

This command configures the value to be sent in the Service-Context-Id AVP, which identifies the context in which DCCA is used.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter service-context-id service_context_id
default diameter service-context-id

default

Configures this command with the default setting. Currently, the default value is encoded based on the dictionary wherever applicable; when not applicable, it is not encoded.

service_context_id

Specifies the service context as an alphanumeric string of 1 through 63 characters that can contain punctuation characters.

Usage Guidelines

If Service-Context-Id is applicable and configured using this command, it will be sent in the AVP Service-Context-Id in the Diameter CCR message.

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

GGSN

HA

IPSG

PDSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

[ default | no ] diameter session failover

default

Configures this command with 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 Guidelines

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.

This command specifies to suppress the AVPs like the MVNO-subclass-id and MVNO-Reseller-Id AVPs.

Product

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter suppress-avp reseller-id subclass-id
[no | default] diameter suppress-avp reseller-id subclass-id

no

Disables AVP suppression. Whenever PCRF sends the MVNO-subclassid and MVNO-Reseller-id AVPs in the Gx interface, the same is sent in the Gy message.

default

Sets the default configuration. AVPs are not suppressed by default. Whenever PCRF sends the MVNO-subclassid and MVNO-Reseller-id AVPs in the Gx interface, the same is sent in the Gy message.

uppress-avp

Suppresses both MVNO-subclassid and MVNO-Reseller-id AVPs.

reseller-id

Supresses the MVNO-Reseller-Id AVP.

subclass-id

Supresses the MVNO-Sub-Class-Id AVP.

Usage Guidelines

Use this command to suppress the AVPs like the MVNO-subclass-id and MVNO-Reseller-Id AVPs.

This command enables dictionary control of the AVPs that need to be added based on the version of the specification with which the Online Charging System (OCS) is compliant. This command is applicable to all products that use the dcca-custom8 dictionary for Gy interface implementation.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

diameter update-dictionary-avps { 3gpp-rel8 | 3gpp-rel9 | 3gpp-rel10 | 3gpp-rel11| 3gpp-rel13 }
[ default | no ] diameter update-dictionary-avps

default | no

Configures this command with the default setting.

Default: Compliant with the oldest release (Rel. 7) and send only Rel. 7 AVPs

3gpp-rel8

Select the 3GPP Rel. 8 AVPs for encoding.

3gpp-rel9

Selects the 3GPP Rel. 9 AVPs for encoding.

3gpp-rel10

Select the 3GPP Rel. 10 AVPs for encoding.

3gpp-rel11

Select the 3GPP Rel. 11 AVPs for encoding.

3gpp-rel13

Select the 3GPP Rel. 13 AVPs for encoding.

Usage Guidelines

Use this command to encode the AVPs in the dictionary based on the release version of the specification to which the OCS is compliant with.

Exits the current configuration mode and returns to the Exec mode.

Product

All

Privilege

Security Administrator, Administrator

Syntax

Syntax Description

end

Usage Guidelines

Use this command to return to the Exec mode.

This command configures the parameters for event-based Gy session.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

[ no ] event-based-session trigger type { location-any | mcc | mnc | timezone } +
default event-based-session trigger type

default

Configures this command with the default setting.

Default: No triggers.

no

Removes the previously configured trigger type.

location-any

Sets the trigger based on change in user location.

mcc

Sets the trigger based on change in Mobile Country Code (MCC) of the serving node (for e.g. SGSN, S-GW).

mnc

Sets the trigger based on change in Mobile Network Code (MNC) of the serving node (for e.g. SGSN, S-GW).

timezone

Sets the trigger based on change in the timezone of UE.

+

Indicates that more than one of the previous keywords can be entered within a single command.

Usage Guidelines

Use this command to enable the credit control reauthorization triggers for event-based-session in the credit-control group.

Exits the current mode and returns to the parent configuration mode.

Product

All

Privilege

Security Administrator, Administrator

Syntax

Syntax Description

exit

Usage Guidelines

Use this command to return to the parent configuration mode.

This command configures Diameter Credit Control Failure Handling (CCFH) behavior in the event of communication failure with the prepaid server or on reception of specific error codes from prepaid server.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

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 an 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. If 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

Starts offline charging after Tx expiry.

retry-after-tx-expiry

Retries after Tx expiry. Enables secondary-host, if up, to take over after Tx expiry.

Usage Guidelines

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.

This command enables the Gy event triggers for configuration of matching Rf ACR containers.

Product

GGSN

HA

IPSG

PDSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

gy-rf-trigger-type { final | forced-reauthorization | holding-time | quota-exhausted | rating-condition-change | threshold | validity-time }
{ default | no } gy-rf-trigger-type

default | no

The "default/no" variant of this command will not enable any of the Gy event-triggers which means the containers would not be closed for any of the event-triggers.

final

Enables Gy trigger "final" for Rf

forced-reauthorization

Enables Gy trigger "forced-reauthorization" for Rf.

holding-time

Enables Gy trigger "qht" for Rf. The trigger "qht" indicates Quota Holding Time.

quota-exhausted

Enables Gy trigger "quota-exhausted" for Rf.

rating-condition-change

Enables Gy trigger "rating-condition-change" for Rf.

threshold

Enables Gy trigger "threshold" for Rf.

validity-time

Enables Gy trigger "validity-time" for Rf.

Usage Guidelines

Use this command to enable the Gy reporting reasons/event triggers.

For all the Gy event triggers a container will be cached at Rf and will be sent based on other events at Rf (for example, max-charging-change-condition, RAT-Change, etc).

For example, when the CLI for QUOTA_EXHAUSTED event trigger is configured under credit-control group configuration, if there is quota_exhausted event then the container should be cached with appropriate change-condition value and ACR-I would be sent out based on other Rf event triggers. Similar behavior is applicable to other event triggers when configured.

This command configures the encoding format of IMSI/IMEISV in the User-Equipment-Info, 3GPP-IMSI and 3GPP-IMEISV AVPs.

Product

GGSN

HA

IPSG

PDSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

[ default | no ] imsi-imeisv-encode-format { ascii | tbcd }

ascii

Sends IMSI/IMEISV as an octet string in ASCII encoded format. By default, the IMSI/IMEISV will be encoded in ASCII format.

tbcd

Sends IMSI/IMEISV as an octet string in Telephony Binary Coded Decimal (TBCD) format, i.e. the nibbles in an octet are inter-changed.

Usage Guidelines

Use this command to configure the encoding format of IMSI/IMEISV in User-Equipment-Info, 3GPP-IMSI and 3GPP-IMEISV AVPs.

This command configures the Prepaid Credit Control mode to RADIUS or Diameter.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

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 Guidelines

Use this command to configure the prepaid charging application mode to Diameter or RADIUS credit control.

This command is configured to re-enable the offline Gy session after failure.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

[ no ] offline-session re-enable

no

Disables the feature. This is the default behavior.

The default configuration is no offline-session re-enable.

Usage Guidelines

Use this command to re-enable the Offline Gy session back to Online charging, based on indication from PCRF. When offline-session re-enable is configured and the PCRF installs/modifies a rule with "Online" AVP value set to 1, then the Offline DCCA will be marked Online.

This command controls the pass/drop treatment of traffic while waiting for definitive credit information from the server.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

pending-traffic-treatment { { { forced-reauth | trigger | validity-expired } drop | pass } | { noquota { buffer | drop | limited-pass volume | pass } } | { quota-exhausted { buffer | drop | pass } } }
default pending-traffic-treatment { forced-reauth | noquota | quota-exhausted | trigger | validity-expired }

default

Configures this command with 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 is passed.

drop

Drops any traffic when there is no quota present.

limited-pass volume

Enables limited access for subscribers when the OCS is unreachable.

volume specifies the Default Quota size (in bytes) and must be an integer from 1 through 4294967295.

This feature allows the subscriber to use the network when the OCS response is slow. This configuration enables to set a Default Quota size from which the subscriber can consume quota until response from the OCS arrives. The traffic consumed by the subscriber from the Default Quota at the beginning of the session is reported and counted against the quota assigned from the OCS.

If the Default Quota is NOT exhausted before the OCS responds with quota, traffic is allowed to pass. Initial Default Quota usage is counted against initial quota allocated. If quota allocated is less than the actual usage, the actual usage and request additional quota are reported. If no additional quota is available, the traffic is denied.

If the Default Quota is NOT exhausted before the OCS responds with denial of quota, traffic is blocked after the OCS response. The gateway will report usage on Default Quota even in for CCR-U (FINAL) or CCR-T until the OCS responds.

If the Default Quota is exhausted before the OCS responds, the session is dropped.

The default pending-traffic-treatment for noquota is drop. The default pending-traffic-treatment noquota command removes any Default Quota limit configured.

pass

Passes all traffic more or less regardless of quota state.

Usage Guidelines

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 command, which specifies behavior in the case of an actual timeout or error, as opposed to the behavior while waiting. See also the buffering-limit command in the Active Charging Service Configuration Mode.

This command sets various time-based quotas in the prepaid credit control service.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

quota holding_time | validity-time validity_time }
{ default | no } quota { holding-time | validity-time }

holding-time holding_time

Specifies the Quota Holding Time (QHT) in seconds. The value must be an integer from 1 through 4000000000.

validity-time validity_time

Specifies the validity lifetime of the quota, in seconds. The value must be an integer from 1 through 4000000.

Usage Guidelines

Use this command to set the prepaid credit control quotas.

This command configures the action on the packet that triggers the credit control application to request quota.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

quota request-trigger { exclude-packet-causing-trigger | include-packet-causing-trigger }
{ default | no } quota request-trigger
default quota request-trigger

default

Configures this command with the default setting. Default: include-packet-causing-trigger

no

Same as the default quota request-trigger command.

exclude-packet-causing-trigger

Excludes the packet causing threshold limit violation trigger.

include-packet-causing-trigger

Includes the packet causing the threshold limit violation trigger.

Usage Guidelines

Use this command to configure action on the packet that triggers the credit control application to request quota, whether the packet should be excluded/included in the utilization information within the quota request.

This command configures the time threshold limit for subscriber quota in the prepaid credit control service.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

quota time-threshold { abs_time_value | percent percent_value }
{ default | no } quota time-threshold

default

Configures this command with the default setting.

Default: Disabled

no

Disables time threshold for prepaid credit control quota.

abs_time_value

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. Default: 0 (Disabled)

percent_value

Specifies the time threshold value as a percentage of the configured time quota in DCCA. percent_value must be an integer from 1 through 100.

Usage Guidelines

Use this command to set the time threshold for prepaid credit control quotas.

This command sets the unit threshold limit for subscriber quota in the prepaid credit control service.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

quota unit-threshold { abs_unit_value | percent percent_value }
{ default | no } quota units-threshold

default

Configures this command with the default setting.

Default: Disabled

no

Disables unit threshold for DCCA quota.

abs_unit_value

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. Default: 0 (Disabled)

percent_value

Specifies the time threshold value as a percentage of the configured units quota in DCCA. percent_value must be an integer from 1 through 100.

Usage Guidelines

Use this command to set the units threshold for prepaid credit control quotas.

This command sets the volume threshold limit for subscriber quota in the prepaid credit control service.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

quota volume-threshold { abs_vol_value | percent percent_value }
{ default | no } quota volume-threshold

default

Configures this command with the default setting.

Default: Disabled

no

Disables volume threshold for prepaid credit control quota.

abs_vol_value

Specifies the absolute threshold volume (in bytes) to the configured volume quota in prepaid credit control. abs_vol_value must be an integer from 1 through 4000000000. To disable this assign 0. Default: 0 (Disabled)

If configured, the Credit Control client will seek re-authorization from the server for the quota when the quota contents fall below the specified threshold.

percent percent_value

Specifies the volume threshold value as a percentage of the configured volume quota in prepaid credit control. percent_value must be an integer from 1 through 100.

Usage Guidelines

Use this command to set the volume threshold for prepaid credit control quotas.

This command configures the usage reporting algorithm for RADIUS prepaid using the Diameter Credit-Control Application (DCCA).

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

radius usage-reporting-algorithm { cumulative | relative }
default radius usage-reporting-algorithm

default

Configures this command with the default setting.

Default: cumulative

cumulative

Reports the total accumulated usage of quota in every accounting interim.

relative

Reports the quota usage per accounting interim (since the previous usage report).

Usage Guidelines

Use this command to configure the usage reporting algorithm for RADIUS prepaid using DCCA.

This command configures the action on buffered packets when a redirect-indicator is received from the RADIUS server.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

redirect-indicator-received { discard-buffered-packet | reprocess-buffered-packet }
{ default | no } redirect-indicator-received

default

Configures this command with the default setting. Default: discard-buffered-packet

no

Disables the redirect-indicator-received configuration.

discard-buffered-packet

Discards the buffered packet.

reprocess-buffered-packet

Redirects the buffered packet on receiving a redirect-indicator from the RADIUS server.

Usage Guidelines

Use this command to configure the action taken on buffered packet when redirect-indicator is received.

Diameter can return a redirect URL but not a redirect indicator, however RADIUS can return a redirect indicator. In this situation, any subsequent subscriber traffic would match ruledefs configured with cca redirect-indicator, and charging actions that have flow action redirect-url should be configured. However, some handsets do not retransmit, so there will be no subsequent packets. On configuring reprocess-buffered-packet, the ruledefs are reexamined to find a new charging action, which may have flow action redirect-url configured.

This command conditionally verifies the presence of user-agents in the HTTP header, based on which HTTP URL redirection will be applied.

Product

GGSN

HA

IPSG

PDSN

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

[ no ] redirect-require-user-agent

no

Disables the "user-agent" check in the HTTP header.

Usage Guidelines

Use this command to conditionally verify the presence of configured user-agents in the HTTP header. The user agent is configured using the redirect user-agent command in the ACS Configuration Mode. The user agent could be, for example, Mozilla, Opera, Google Chrome, etc.

The default configuration is to enable the "user-agent" check, and compare it with the configured list of supported user-agents. The packet will be redirected only when the user-agent is matched with one of the configured user-agents.

If no redirect-require-user-agent is configured, the user-agent check is disabled. The packets will be redirected even if it does not contain a "user-agent" information in the HTTP header.

This command configures whether to continue or terminate calls when Diameter server or the OCS becomes unreachable.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

In 12.1 and earlier releases:

servers-unreachable { initial-request { continue | terminate [ after-timer-expiry timeout_period ] } | update-request { continue | terminate [ after-quota-expiry | after-timer-expiry timeout_period ] } }
no servers-unreachable { initial-request | update-request }

In 12.2 and later releases:

servers-unreachable { behavior-triggers { initial-request | update-request } result-code { any-error | result-code [ to end-result-code ] } | transport-failure [ response-timeout | tx-expiry ] | initial-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count | after-timer-expiry timeout_period ] } | update-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | after-quota-expiry | after-timer-expiry timeout_period ] } }
no servers-unreachable { initial-request | update-request }
default servers-unreachable behavior-triggers { initial-request | update-request }

no

Deletes the current servers-unreachable configuration.

In 15.0 and later releases, to remove the error result code configuration, the no command syntax is no servers-unreachable behavior-triggers { initial-request | update-request } result-code { any-error | result-code [ to end-result-code ] }.

behavior-triggers { initial-request | update-request } { result-code { any-error | result-code [ to end-result-code ] } | transport-failure [ response-timeout | tx-expiry ] }

This keyword is used to determine when to apply server-unreachable action. This supports three configurable options to apply server-unreachable action either at transport failure, Tx expiry or at response timeout. Out of these three options, the transport failure is the default option.

initial-request { continue | terminate [ after-timer-expiry timeout_period ] }

Specifies behavior when Diameter server(s)/OCS become unreachable during initial session establishment.

initial-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | after-timer-expiry timeout_period }

Specifies behavior when Diameter server(s)/OCS become unreachable during initial session establishment.

update-request { continue | terminate [ after-quota-expiry | after-timer-expiry timeout_period ] }

Specifies behavior when Diameter server(s)/OCS become unreachable during mid session.

update-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | after-quota-expiry | after-timer-expiry timeout_period ] }

Specifies behavior when Diameter server(s)/OCS become unreachable during mid session.

Usage Guidelines

Use this command to configure whether to continue/terminate calls when Diameter server(s)/OCS are unreachable. This command can be used to verify the functionality of the configurable action if the OCS becomes unreachable.

In 12.1 and earlier releases, the OCS is considered down/unreachable when all transport/TCP connections are down for that OCS.

In 12.2 and later releases, the OCS is declared unreachable when all transport connections are down OR message timeouts happen (for example, a Tx expiry or response timeout, for all available OCS servers) owing to slow response from the OCS (may be due to network congestion or other network related issues).

The following set of actions are performed if the servers become unreachable:

This command works on the same lines as the failure-handling command, which is very generic for each of the xxx-requests.

The servers-unreachable CLI command is specifically for TCP connection error. In the event of TCP connection failure, the failure-handling and/or servers-unreachable commands can be used. This way, the operator has the flexibility to configure CCFH independent of OCS-unreachable feature, that is having two different failure handlings for same request types.

This command can also be used to control the triggering of behavior based on transport failure, response message timeouts or Tx expiry when OCS becomes unreachable. The OCS could be unreachable due to no TCP connection and the message timeout could be due to network congestion or any other network related issues.

The following are the possible and permissible configurations with respect to behavior triggering:

Of these configurations, the first one is considered to be the default configuration and it will take care of backward compatibility with 12.0 implementation.

If the server returns the CC-Failure-Handling AVP, it would apply for transport-failure/response-timeout/tx-expiry when the CLI command servers-unreachable is not configured. If the servers-unreachable is configured for a set of behavior-triggers, then servers-unreachable configuration will be applied for them. For those behavior-triggers for which servers-unreachable is not configured, the CC-Failure-Handling value provided by the server will be applied.

By default, Result-Code such as 3002 (Unable-To-Deliver), 3004 (Too-Busy) and 3005 (Loop-Detected) falls under delivery failure category and will be treated similar to response-timeout configuration.

This command enables required Subscription-Ids for various service types.

Product

GGSN

HA

IPSG

PDSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

subscription-id service-type { closedrp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw } { e164 | imsi | nai }
[ no ] subscription-id service-type { closedrp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw }

default

Configures the default timestamp-rounding setting.

Default: floor

closedrp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw { e164 | imsi | nai }

Includes the Subscription-Id for the chosen service type. For example, if ipsg is configured as the keyword option, then the subscription-id is included for the IPSG service.

The following subscription-Id types are available:

Usage Guidelines

Currently, Subscription-Id AVP is encoded in the Gy CCRs based on dictionary and service-type checks. With the new CLI command, customers will have the provision of enabling required Subscription-Id types for various services.

Each service can have a maximum of three Subscription-Id types (e164, imsi & nai) that can be configured through this CLI command. The DCCA specific changes are made in such a way that, if the CLI command is configured for any particular service, then the CLI takes precedence. Else, it falls back to default (hard-coded) values configured for that service.

The advantage of this CLI command is that any further dictionary additions in DCCA can be minimized.

For an instance, if a customer wants IMSI value to be encoded in Gy CCRs (along with E164) for MIPv6HA service, then this CLI command subscription-id service-type mipv6ha e164 imsi should be configured in the Credit Control Configuration mode.

If only imsi is configured through the CLI, then Gy CCRs will only have imsi value.

This command configures how to convert exact time into the units that are used in quotas.

Product

ACS

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

timestamp-rounding { ceiling | floor | roundoff }
default timestamp-rounding

default

Configures the default timestamp-rounding setting.

Default: floor

timestamp-rounding ceiling

Round off to the smallest integer greater than the fraction.

If the fractional part of the seconds is greater than 0, add 1 to the number of seconds and discard the fraction.

timestamp-rounding floor

Discard the fractional part of the second.

timestamp-rounding roundoff

Set the fractional part of the seconds to the nearest integer value. If the fractional value is greater than or equal to 0.5, add 1 to the number of seconds and discard the fractional part of second.

Usage Guidelines

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).

This command enables/disables triggering a credit reauthorization when the named values in the subscriber session changes.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

[ no ] trigger type { cellid | lac | mcc | mnc | qos | rat | serving-node | sgsn | timezone } +
default trigger type

default

Configures this command with the default setting.

Default: No triggers.

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.

mcc

Sets the trigger based on change in Mobile Country Code (MCC).

mnc

Sets the trigger based on change in Mobile Network Code (MNC).

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).

serving-node

Sets the trigger based on change in serving node. The serving node change causes the credit control client to ask for a re-authorization of the associated quota.

Typically used as an extension to sgsn trigger in P-GW (SAEGW), however, may also be used alone.

sgsn

Sets the trigger based on change in the IP address of SGSN.

timezone

Sets the trigger based on change in the timezone of UE.

+

Indicates that more than one of the previous keywords can be entered within a single command.

Usage Guidelines

Use this command to set the credit control reauthorization trigger.

This command configures the ACS Credit Control usage reporting type.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > ACS Configuration > Credit Control Configuration

active-charging service service_name > credit-control

Entering the above command sequence results in the following prompt:

[local]host_name(config-dcca)#

Syntax

Syntax Description

usage-reporting quotas-to-report based-on-grant { report-only-granted-volume }
default usage-reporting quotas-to-report

default

Configures this command with the default setting.

Default: Disabled

report-only-granted-volume

Suppresses the input and output octets. If the Granted-Service-Unit (GSU) AVP comes with CC-Total-Octets, then the device will send total, input and output octets in Used-Service-Unit (USU) AVP. If it comes with Total-Octets, the device will send only Total-Octets in USU.

Usage Guidelines

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.