This command configures whether the virtual or real Access Point Name (APN) is sent in Credit Control Application (CCA) messaging.

default

Configures this command with the default setting.

Default: gn

gn

Sends the Gn APN name in the CCA messages.

virtual

Sends the virtual APN name, if configured in the APN Configuration Mode, in the CCA messages.

This command enables/disables application-level retransmissions with the "T" bit set.

default

Configures this command with the default setting.

Default: unset-retransmission-bit

set-retransmission-bit

Sets the retransmission bit.

unset-retransmission-bit

Unsets the retransmission bit.

This command associates/disassociates a failure handling template with the Diameter Credit Control Application (DCCA) service.

no

Disassociates a failure handling template with the DCCA service.

failure-handling-template template_name

Associates a previously created failure handling template with the DCCA service. template_name specifies the name for a pre-configured failure handling template. template_name must be an alphanumeric string of 1 through 63 characters.

For more information on failure handling templates, refer to the failure-handling-template command in the Global Configuration Mode Commands chapter.

This command allows static configuration of charging rulebase name to be sent to OCS through the CCR message.

no

The no variant, when configured, sends the rulebase that was configured in APN/subscriber template to the OCS.

rulebase_name

Specifies the name for a charging rulebase to be sent to OCS via CCR message. rulebase_name must be an alphanumeric string of 1 through 63 characters.

This command configures the Diameter Credit Control dictionary for the Active Charging Service (ACS).

default

Configures this command with the default setting.

Default: standard dictionary

dcca-custom1 ... dcca-custom30

Configures a custom Diameter dictionary.

dynamic-load

Configures the dynamically loaded Diameter dictionary. The dictionary name must be an alphanumeric string of 1 through 15 characters.

For more information on dynamic loading of Diameter dictionaries, see the diameter dynamic-dictionary in the Global Configuration Mode Commands chapter of this guide.

standard

Configures the standard Diameter dictionary.

Default: Enabled

This command controls sending of CCR-U with reporting reason as FINAL immediately on receiving a 4012 or 4010 result-code at MSCC level.

default | no

Configures this command with the default setting. Default behavior is to send CCR-U with reporting reason as FINAL immediately on receiving 4010/4012 result-code.

This command specifies to request quota immediately in the CCR sent to the Gy interface when the traffic matches the dynamic rules with Online AVP enabled and received over Gx interface.

default

Configures this command with the default setting.

Default: on-receiving-rule

on-traffic-match

Requests quota only when there is traffic matching the dynamic rules with Online AVP enabled.

on-receiving-rule

Requests quota on receiving a dynamic rule with Online AVP enabled.

This command enables/disables Quota Retry Timer for blacklisted content.

no

Configures this command with the default setting.

This command enables to exclude Multiple-Services-Credit-Control (MSCC) AVP in CCR-T message.

default

Includes MSCC AVP in CCR-T.

no

Includes MSCC AVP in CCR-T.

This command enables to control the behavior of marking redirected HTTP flow as free-of-charge.

no

Disables the behavior of marking redirected HTTP flow as free-of-charge.

Default: diameter fui-redirected-flow allow

This command configures whether to accept/reject CCA messages that contain Granted-Service-Unit AVP with only infinite quota grants from the server.

default

Configures this command with the default setting.

Default: reject-credit-control-answer

accept-credit-control-answer

Accepts the Credit-Control-Answer message.

reject-credit-control-answer

Rejects the Credit-Control-Answer message.

This command enables/disables the Hard Disk Drive (HDD) to store the failed CCR-T messages for the corresponding credit control group.

no

Disables the HDD from storing the failed CCR-T messages for the corresponding credit control group.

This command configures to accept/ignore the rulebase ID in the Rulebase-Id AVP returned by the Diameter server in CCA messages.

default

Configures this command with the default setting.

Default: Accept

no

Accepts the rulebase ID received from Diameter server in CCA.

This command enables to accept/ignore service ID in the Service-Identifier AVP defined in the Diameter dictionaries. This command is applicable to all products that use the Gy interface.

default

Configures this command with the default setting.

Default: Accept

no

Specifies to accepts the service ID.

This command enables either to terminate a PDP session immediately when the Final-Unit-Action (FUA) in a particular Multiple Service Credit Control (MSCC) is set as TERMINATE and the quota is exhausted for that service, or to terminate the session after all other MSCCs (categories) have used up their available quota.

default

Configures this command with the default setting.

Default: Same as diameter mscc-final-unit-action terminate category

category

This is the standard behavior wherein the category is terminated if the Final-Unit-Indication AVP comes with TERMINATE for a given MSCC.

session { on-per-mscc-exhaustion | on-all-mscc-exhaustion }

Terminates the session depending on the quota usage of one MSCC or all the MSCCs.

on-per-mscc-exhaustion : When the FUA in a particular MSCC is set as TERMINATE and the quota is exhausted for that service, the session will be terminated immediately regardless of the state of the other MSCCs.

on-all-mscc-exhaustion : When the FUA in a particular MSCC is set as TERMINATE and the quota is exhausted for that service, the session termination will be initiated after all the other MSCCs (categories) have used up their available quota. There will no more CCR(U) messages sent requesting quota after receiving the FUA as TERMINATE in the MSCC level.

This command configures sending single/multiple Multiple-Services-Credit-Control (MSCC) AVP in CCR-U messages.

default

Configures this command with the default setting.

Default: multiple

multiple

Sends multiple Multiple-Services-Credit-Control AVP in a single CCR-U message.

single

Sends only one Multiple-Services-Credit-Control AVP in a CCR-U message.

This command controls sending of CCR-U/CCR-T with reporting reason as FINAL immediately on receiving a 4012 or 4010 result-code at MSCC level or when the MSCC is in FUI Redirect/Restrict-access state.

no

Depending on the configuration, this keyword will selectively send FINAL either in CCR-U or CCR-T even if MSCC is in FUI Redirect/Restrict-access state and USU is zero.

The default behavior is to not send CCR-T with reporting reason as FINAL even when MSCC is in FUI Redirect/Restrict-access state and USU is zero.

Important

This default behavior is applicable to all dictionaries except for dcca-custom12 and dcca-custom13 dictionaries. In the case of dcca-custom12 and dcaa-custom13, the FINAL reporting will always be sent in CCR-T even if MSCC is in FUI Redirect/Restrict-access and USU is zero.

ccru

This keyword disables Immediate FINAL reporting for result code 4010/4012 in CCR-U message.

ccrt

This keyword disables FINAL reporting for MSCC which are in no-quota and FUI Redirect/Restrict-access state.

suppress-final-reporting

Important

This keyword is available only in 18.3, 19.2 and later releases.

When used with the diameter msg-type ccru command, this keyword disables immediate FINAL reporting for result code 4010/4012. When used with the diameter msg-type ccrt command, this keyword disables FINAL reporting for no-quota FUA Redirect/Restrict-access.

suppress-blacklist-reporting

Important

This keyword is available only in 18.3, 19.2 and later releases.

Disables FINAL reporting for blacklisted (4010/4012) content in CCR-T.

This command is obsolete. See the diameter origin endpoint command.

This command configures the Diameter Credit Control Origin Endpoint.

no

Removes the Diameter Credit Control Origin Endpoint configuration.

endpoint endpoint_name

Specifies the Diameter Credit Control Origin Endpoint name as an alphanumeric string of 1 through 63 characters.

realm realm_name

Specifies the Diameter Credit Control Realm ID as an alphanumeric string of 1 through 127 characters.

This command configures the Diameter credit control primary and secondary hosts for DCCA.

no

Removes previously configured Diameter credit control peer selection setting.

peer peer_name

Specifies the primary host name. as an alphanumeric string of 1 through 63 characters that can contain punctuation characters.

imsi-based start-value imsi_start_value end-value imsi_end_value

Important

This section applies only to 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 ]

Important

This section applies only to 9.0 and later releases for UMTS deployments.

Selects peer 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 an IMSI prefix/suffix, and must be an integer from 1 through 15 characters.

imsi/prefix/suffix_end_value : Specifies the IMSI/prefix/suffix end value. prefix/suffix must be an IMSI prefix/suffix, and must be an integer from 1 through 15 characters that 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.

msisdn-based { { prefix | suffix } msisdn/prefix/suffix_start_value } [ to msisdn/prefix/suffix_end_value ]

Specifies peer selection based on MSISDN prefix or suffix or MSISDN range.

prefix : Specifies the prefix range

suffix : Specifies the suffix range

msisdn/prefix/suffix_start_value : Specifies the MSISDN/prefix/suffix start value. prefix/suffix must be an MSISDN prefix/suffix, and must be an integer from 1 through 15 characters.

msisdn/prefix/suffix_end_value : Specifies the MSISDN/prefix/suffix end value. prefix/suffix must be an MSISDN prefix/suffix, and must be an integer from 1 through 15 characters that must be greater than the start value.

realm realm_name

The realm_name must be an alphanumeric string of 1 through 127 characters, and can contain punctuation characters. The realm may typically be a company or service name.

secondary-peer secondary_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.

secondary_peer_name must be an alphanumeric string of 1 through 63 characters, and can contain punctuation characters.

This command configures the maximum time period to wait for response from a Diameter peer.

default

Disables DCCA resending message at pending-timeout.

duration

Specifies the timeout duration (in deciseconds). The value must be an integer from 1 through 3000.

deciseconds msg-type { any | ccr-event | ccr-initial | ccr-terminate | ccr-update }

Specifies independent timers (in deciseconds) for all message types like CCR-I, CCR-U, CCR-T and CCR-E. The default time will be 100 deciseconds (10 seconds).

This keyword option provides additional flexibility for operator to configure independent timers with reduced granularity.

This feature implementation ensures that the timer configuration is backward compatible. If the CLI command is configured without "desiseconds " and "msg-type ", the configured time will be taken as seconds and while displaying the CLI it will be converted to deciseconds and msg-type will be "any ".

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.

This command allows reauthorization of blacklisted content (blacklisted with Result-Code like 4012, 4010, etc) when a Rating Group (RG) based Re-Authorization Request (RAR) or generic RAR is received.

no

Configures this command with the default setting. That means, the reauthorization of blacklisted RG will not happen.

content-based-rar

Reauthorizes blacklisted RG only when RG specific RAR is received.

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

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.

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

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.

This command enables sending a GTP Create-PDP-Context-Rsp message with cause code based on the DCCA result 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.

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

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.

Important

Please note that the CCR-I will be sent only with the default rulebase and not with Rulebase list even if the rulebase-list configuration is enabled. When the rulebase-list command is used in conjunction with diameter send-ccri traffic-start command, the former one's function is invalidated. The rulebase-list is used to allow the OCS to select one of the rulebases from the list configured during the session setup. But in case of send-ccri traffic-start the CLI causes the session setup to complete without OCS interaction. For more information on rulebase-list command, please see the ACS Configuration Mode Commands chapter of the Command Line Interface Reference.

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

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.

This command enables or disables Diameter Credit Control Session Failover. When enabled, the secondary peer is used in the event the main peer is unreachable.

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.

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

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.

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.

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.

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

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

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.

Exits the current mode and returns 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.

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.

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

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.

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

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.

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

default

Configures the default prepaid credit control mode.

Default: diameter

diameter

Enables Diameter Credit Control Application (DCCA) for prepaid charging.

Important

After you configure this keyword, you must save the configuration and then reload the chassis for the command to take effect. For information on saving the configuration file and reloading the chassis, refer to the System Administration Guide for your deployment.

radius

Enables RADIUS Credit Control for prepaid charging.

Important

After you configure this keyword, you must save the configuration and then reload the chassis for the command to take effect. For information on saving the configuration file and reloading the chassis, refer to the System Administration Guide for your deployment.

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

no

Disables the feature. This is the default behavior.

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

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

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.

Important

Default Quota is used only for noquota case (Rating Group (RG) seeking quota for the first time) and not for quota-exhauste d. Default Quota is not used for subsequent credit requests.

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.

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

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.

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

default

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

no

Same as the default quota request-trigger command.

Important

In 10.0 and later releases, this keyword is deprecated.

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.

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

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.

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

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.

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

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.

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

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

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

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.

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

no

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

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

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 : Specifies the behavior when Diameter server(s)/OCS become unreachable during initial session establishment.

• update-request : Specifies the behavior when Diameter server(s)/OCS become unreachable during mid-session.

• result-code { any-error | result-code [ to end-result-code ] } : Specifies to configure any Diameter error result code or a range of result codes to trigger entering server unreachable mode.

  result-code must be an integer ranging from 3000 to 5999.

• transport-failure [ response-timeout | tx-expiry ] : This keyword specifies to trigger the behavior either at transport failure or response timeout OR at Transport failure or Tx expiry.

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

Important

This section applies only to 12.1 and earlier releases.

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

• continue : Specifies to continue call if Diameter server(s) becomes unreachable.

• terminate : Specifies to terminate call if Diameter server(s) becomes unreachable.

  after-timer-expiry timeout_period : On detecting transport failure, this keyword variable specifies the time limit for which the subscriber session will remain in offline state before the call is terminated.

  timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.

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 }

Important

This section applies only to 12.2 and later releases.

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

• continue : Specifies to continue call if Diameter server(s) becomes unreachable.

• terminate : Specifies to terminate call if Diameter server(s) becomes unreachable.

  • after-interim-time timeout_period : Specifies to continue or terminate call after the interim timeout period expires.

    timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.

  • after-interim-volume quota_value : Specifies to continue or terminate call on exhaustion of the assigned quota.

    quota_value specifies the volume-based quota value, in bytes, and must be an integer from 1 through 4294967295.

    The after-interim-volume and after-interim-time can be configured in one of the following ways:

    • after-interim-volume quota_value server-retries retry_count

    • after-interim-time timeout_period server-retries retry_count

    • after-interim-volume quota_value after-interim-time timeout_period server-retries retry_count

  • after-timer-expiry timeout_period : On detecting transport failure, this keyword variable specifies the time limit for which the subscriber session will remain in offline state before the call is terminated.

    timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.

  • server-retries retry_count : Specifies the number of retries that should happen to OCS before allowing the session to terminate/offline.

    retry_count specifies the retries to OCS, and must be an integer from 0 through 65535. If the value 0 is defined for this keyword, the retry to OCS will not happen instead the configured action will be immediately applied.

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

Important

This section applies only to 12.1 and earlier releases.

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

• continue : Specifies to continue call if Diameter server(s) becomes unreachable.

• terminate : Specifies to terminate call if Diameter server(s) becomes unreachable.

  • after-quota-expiry : Specifies to terminate call on exhaustion of all available quota.

  • after-timer-expiry timeout_period : On detecting transport failure, this keyword variable specifies the time limit for which the subscriber session will remain in offline state before the call is terminated.

    timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.

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 ] }

Important

This section applies only to 12.2 and later releases.

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

• continue : Specifies to continue call if Diameter server(s) becomes unreachable.

• terminate : Specifies to terminate call if Diameter server(s) becomes unreachable.

  • after-interim-time timeout_period : Specifies to continue or terminate call after the interim timeout period expires.

    timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.

  • after-interim-volume quota_value : Specifies to continue or terminate call on exhaustion of the assigned quota.

    quota_value specifies the volume-based quota value, in bytes, and must be an integer from 1 through 4294967295.

    The after-interim-volume and after-interim-time can be configured in one of the following ways:

    • after-interim-volume quota_value server-retries retry_count

    • after-interim-time timeout_period server-retries retry_count

    • after-interim-volume quota_value after-interim-time timeout_period server-retries retry_count

  • after-quota-expiry : Specifies to terminate call on exhaustion of all available quota.

  • after-timer-expiry timeout_period : On detecting transport failure, this keyword variable specifies the time limit for which the subscriber session will remain in offline state before the call is terminated.

    timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.

  • server-retries retry_count : Specifies the number of retries that should happen to OCS before allowing the session to terminate/offline.

    retry_count specifies the retries to OCS, and must be an integer from 0 through 65535. If the value 0 is defined for this keyword, the retry to OCS will not happen instead the configured action will be immediately applied.

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

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:

• e164 - Include E164 information in the Subscription-Id AVP

• imsi - Include IMSI information in the Subscription-Id AVP

• nai - Include NAI information in the Subscription-Id AVP

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

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.

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

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.

This command configures the ACS Credit Control usage reporting type.

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.