This command configures the APN name to be included in CCR Gx messages.

gn | virtual

Specifies which APN name must be sent in the Gx messages.

gn : Specifies to send the real APN name.

virtual : Specifies to send the virtual APN name if present, else to send the real APN name.

default

Applies the default setting for this command.

Default: gn

This command enables mapping of the ARP priority-level value received from PCRF to inter-user-priority value and be sent in A11 session update.

default

Configures the default setting for this command.

Default: arp-priority-level to inter-user-priority mapping not applicable

no

Disables arp-priority-level to inter-user-priority mapping.

This command associates/disassociates a failure handling templateor a local policy template with the IMS authorization service.

no

Disassociates a failure handling templateor local policy template with the IMS authorization service.

failure-handling-template template_name

Associates a previously created failure handling template with the IMS authorization 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.

local-policy-service service_name [ dual-mode ]

Associates a previously created local policy service with the IMS authorization service. service_name specifies the name for a pre-configured local policy service. service_name must be an alphanumeric string of 1 through 63 characters.

dual-mode : This keyword enables both PCRF and local-policy to work together. When this CLI command is enabled, for a few set of events, PCRF will be contacted and for a few local-policy will be contacted.

This keyword is configured to provide load balancing support for PCRF, and failure-handling support when PCRF is down or any failure is detected.

By default, the dual-mode keyword will not enabled and only on PCRF failure the local-policy will be contacted.

For more information on local policy service configuration, refer to the local-policy-service command in the Global Configuration Mode Commands chapter.

This command configures the value of the Offline AVP sent to the PCRF based on the Charging Characteristics (CC) profile received from the SGSN.

default

Configures the default setting for this command.

Default: Deletes all previously configured mappings.

no

Deletes all previously configured mappings.

cc_profile_number

Specifies the CC profile number to map.

For example, 1 for Hot Billing.

cc_profile_number must be an integer from 0 through 15.

cc_profile_number_range_end

Specifies, for a range of CC profile numbers to map, the end number. That is, from cc_profile_number through cc_profile_number_range_end .

cc_profile_number_range_end must be an integer from 1 through 15.

map-to offline-avp { 0 | 1 }

Specifies to map the CC profile number(s) to the Offline AVP value sent to the PCRF.

This command enables custom reauthorization event triggers.

default

Configures the default setting for this command. The default setting is to enable all the event triggers.

none

Disables all custom event triggers.

apn-ambr-mod-failure

Enables APN AMBR Modification Failure event trigger.

default-bearer-qos-change

Enables Default EPS bearer QoS change event trigger.

default-bearer-qos-mod-failure

Enables Default EPS Bearer QOS Modification Failure event trigger.

qos-change

Enables QoS change trigger.

resource-modification-request

Enables Resource modification trigger.

ue-ip-addr-allocate

Enables UE IP address allocate trigger.

ue-ip-addr-release

Enables UE IP address release trigger.

preservation-changed

Enables preservation-changed event trigger.

Important

This keyword is for use with a customer-specific implementation, and will be available only if a valid license is installed.

reactivation-changed

Enables reactivation-changed event trigger.

Important

This keyword is for use with a customer-specific implementation, and will be available only if a valid license is installed.

This command controls PCEF from sending Flow-Description, TFT-Filter, andPacket-Filter-Content AVPs in Rel. 9 format.

3gpp-r9-flow-direction

Encodes Flow-Direction, Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs based on 3GPP Rel. 9 specification.

no

Encodes Flow-Direction, Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs in Rel. 8 format. This is the default configuration.

This command enables the system to clear the subscriber sessions which are affected by session ID mapping mismatch.

sessid-mismatch

Clears the session with mismatched session ID. This CLI configuration is optional.

no

This keyword does not delete the subscriber sessions. This is the default configuration.

This command specifies the Diameter Policy Control Application dictionary to be used by the IMS Authorization Service for the policy control application.

dpca-custom1

Custom-defined Diameter dictionary for the Gx interface.

dpca-custom2

Custom-defined Diameter dictionary for Rel. 7 Gx interface.

dpca-custom3

Custom-defined Diameter dictionary for the Gx interface in conjunction with IP Services Gateway (IPSG).

dpca-custom4

Standard Diameter dictionary for 3GPP Rel. 7 Gx interface.

dpca-custom5

Custom-defined Diameter dictionary for Rel. 7 Gx interface.

dpca-custom6 ... dpca-custom30

Custom-defined Diameter dictionaries.

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.

gx-wimax-standard

Gx WiMAX standard dictionary.

gxa-3gpp2-standard

Gxa 3GPP2 standard dictionary.

gxc-standard

Gxc standard dictionary.

pdsn-ty

This keyword is restricted.

r8-gx-standard

R8 Gx standard dictionary.

Standard

Standard Diameter dictionary for the 3GPP Rel. 6 Gx interface.

Default: Enabled for Gx support in 3GPP networks.

std-pdsn-ty

This keyword is restricted.

ty-plus

This keyword is restricted.

ty-standard

This keyword is restricted.

default

Sets the default Diameter dictionary.

Default: Standard

This command enables encoding of all the event-related information AVPs in CCR-U messages.

default

Applies the default setting for this command.

Default: Sends AVPs relevant to the Event-Trigger subscribed by the PCRF.

always

This keyword option always sends the event-related AVPs in all CCR messages.

local-fallback

This keyword option sends the event-related AVPs in CCR-U messages in the event of local fallback scenario.

This command enables/disables encoding and sending of Supported-Features AVP.

adc-rules

This keyword enables configuration of Application Detection and Control (ADC) rules over Gx interface. For ADC 6th bit of supported feature will be set. By default, this supported feature will be disabled.

Important

ADC Rule support is a licensed-controlled feature. Contact your Cisco account representative for detailed information on specific licensing requirements.

This keyword "adc-rules " will be available only when the feature-specific license is configured.

In release 18, the gateway node will use ADC functionality over Gx as defined in the Release 11 specification of 3GPP standard. ADC extension over Gx provides the functionality to notify PCRF about the start and stop of a specific protocol or a group of protocols, and provide the possibility to PCRF that with the knowledge of this information, change the QoS of the user when the usage of application is started and until it is finished.

The provision of ADC information is done through the ADC rule, the action initiated by PCRF is done through the PCC rule.

ADC rules are certain extensions to dynamic and predefined PCC rules in order to support specification, detection and reporting of an application flow. These rules are installed (modified/removed) by PCRF via CCA-I/CCA-U/RAR events. ADC rules can be either dynamic PCC or predefined PCC rules, and the existing attributes of dynamic and predefined rules will be applicable.

Dynamic PCC rule contains either traffic flow filters or Application ID. When Application ID is present, the rule is treated as ADC rule. Application ID is the name of the ruledef which is pre-defined in the boxer configuration. This ruledef contains application filters that define the application supported by P2P protocols.

PCEF will process and install ADC rules that are received from PCRF interface, and will detect the specified applications and report detection of application traffic to the PCRF. PCRF in turn controls the reporting of application traffic.

PCEF monitors the specified applications that are enabled by PCRF and generates Start/Stop events along with the Application ID. Such application detection is performed independent of the bearer on which the ADC PCC rule is bound to. For instance, if ADC rule is installed on a dedicated bearer whereas the ADC traffic is received on default bearer, application detection unit still reports the start event to PCRF.

cno-uli

This keyword enables the Presence Reporting Area (PRA) feature. Configuring cno-uli keyword enables feature bit in supported feature AVP and helps in negotiating with PCRF.

The Presence Reporting Area is an area defined within the 3GPP packet domain for the purpose of reporting of UE presence within that area. This is required for policy control and in charging scenarios.

During an IP-CAN session, the PCRF determines whether the reports for change of the UE presence in the PRA are required for an IP-CAN session. This determination is made based on the subscriber's profile configuration and the supported AVP features.

conditional-apn-policy-info

This keyword enables the Conditional APN Policy Information feature. This feature bit support is added to enable this feature for negotiation with PCRF. By default, this supported feature is disabled.

Use all three keywords—conditional-apn-policy-info, conditional-policy-info, conditional-policy-info-default-qos—to enable conditional Policy information feature on the P-GW. Using the no form of the command for all the three keywords, disables this feature.

Using only one of the keywords enables the feature bit in supported feature AVP.

Using no form of this command with only one of the keywords disables a specific feature bit in negotiation of this feature.

Important

This keyword is customer-specific. For more information, contact your Cisco account representative.

conditional-policy-info

This keyword enables the Conditional Policy Information feature. This feature bit support is added to enable this feature for negotiation with PCRF. By default, this supported feature is disabled.

Use all three keywords—conditional-apn-policy-info, conditional-policy-info, conditional-policy-info-default-qos—to enable conditional Policy information feature on the P-GW. Using the no form of the command for all the three keywords, disables this feature.

Using only one of the keywords enables the feature bit in supported feature AVP.

Using no form of this command with only one of the keywords disables a specific feature bit in negotiation of this feature.

Important

This keyword is customer-specific. For more information, contact your Cisco account representative.

conditional-policy-info-default-qos

This keyword enables the Conditional Policy Information Default QoS feature. This feature bit support is added to enable this feature for negotiation with PCRF. By default, this supported feature is disabled.

Use all three keywords—conditional-apn-policy-info, conditional-policy-info, conditional-policy-info-default-qos—to enable conditional Policy information feature on the P-GW. Using the no form of the command for all the three keywords, disables this feature.

Using only one of the keywords enables the feature bit in supported feature AVP.

Using no form of this command with only one of the keywords disables a specific feature bit in negotiation of this feature.

Important

This keyword is customer-specific. For more information, contact your Cisco account representative.

extended-bw-newradio

This keyword enables Extended Bandwidth with New-Radio feature.

mission-critical-qcis

This keyword enables Mission Critical (MC)-Push to Talk (PTT) (MC-PTT) QCI feature. By default, this feature will not be enabled.

Important

This keyword can be enabled only if the Wireless Priority Feature Set (WPS) license is configured. For licensing information, contact your Cisco account or support representative.

To support the MC-PTT services, a new set of standardized QoS Class Identifiers (QCIs) (65, 66, 69, 70) have been introduced. These are 65-66 (GBR) and 69-70 (non-GBR) network-initiated QCIs defined in 3GPP TS 23.203 v13.6.0 and 3GPP TS 23.401 v13.5.0 specifications. These QCIs are used for Premium Mobile Broadband (PMB)/Public Safety solutions.

In releases prior to 21, the gateway accepted only standard QCIs (1-9) and operator defined QCIs (128-254). If the PCRF sends QCIs with values between 10 and 127, then the gateway rejected the request. The MC QCI support was not negotiated with PCRF. In 21 and later releases, PCRF accepts the new standardized QCI values 69 and 70 for Default Bearer creation and 65, 66, 69 and 70 for Dedicated Bearer creation.

When mission-critical-qcis option is enabled, the gateway allows configuring MC QCIs as a supported feature and then negotiates the MC-PTT QCI feature with PCRF through Supported-Features AVP.

The gateway rejects the session create request with MC-PTT QCIs when the WPS license is not enabled and Diameter is not configured to negotiate MC-PTT QCI feature, which is part of Supported Feature bit.

To disable the negotiation of this feature, the existing no diameter encode-supported-features command needs to be configured. On executing this command, none of the configured supported features will be negotiated with the PCRF.

For more information on this feature, see the Gx Interface Support chapter in the administration guide of the product you are deploying.

multiple-pra

Enables the Multiple Presence Reporting Area Information Reporting.

netloc

Enables the NetLoc feature. The NetLoc feature indicates the support for reporting of the Access Network Information.

Important

Network Provided Location Information (NPLI) feature is a license-controlled feature. A valid feature license must be installed prior to configuring this feature. Contact your Cisco account representative for more information.

A new feature "netloc" (feature bit 10) has been added as part of the Supported-Features AVP to implement the Network provided Location Info (NPLI) feature for IMS. NPLI is used to support variety of applications like emergency call, Lawful intercept, charging, etc.

Important

This feature works only if PCRF too supports netloc.

The netloc feature bit will be sent to PCRF on demand via CCR-I message. A new event trigger "ACCESS_NETWORK_INFO_REPORT (45)" and a new Diameter AVP "Required-Access-Info" have been added to support the NPLI enhancement.

The gateway node provides the required access network information (e.g. user location and/or user time zone information) to the PCRF within the 3GPP-User-Location-Info AVP, User-Location-Info-Time AVP (if available), and/or 3GPP-MS-TimeZone AVP as requested by the PCRF. The gateway also provides the ACCESS_NETWORK_INFO_REPORT event trigger within Event-Trigger AVP.

netloc-ran-nas-cause

Enables the Netloc-RAN-NAS-Cause feature. By default, this supported feature will be disabled.

This feature is used to send detailed RAN and/or NAS release cause code information from the access network to PCRF. This feature is added to be in compliance with Release 12 specification of 3GPP TS 29.212. It requires that the NetLoc feature is also supported.

A new feature "netloc-ran-nas-cause" (feature bit 22) has been added as part of the Supported-Features AVP to support the 3GPP RAN/NAS Release Cause Code Information Element (IE) on Gx interface. Starting from Release 21.2, this feature is supported on S5/S8, and S2b interfaces.

Important

This feature can be enabled only when the NetLoc feature license is installed. However, from StarOS Release 21.1, you can enable the RAN/NAS feature without configuring the NetLoc feature. It is not mandatory to configure the "netloc" keyword to configure the "netloc-ran-nas-code" keyword.

If the supported features "netloc-ran-nas-code" and "netloc" are enabled, then netloc-ran-nas-cause code will be sent to PCRF via CCR-T message. A new Diameter AVP "RAN-NAS-Release-Cause" has been added to support this feature. This AVP will be included in the Charging-Rule-Report AVP and in CCR-T for bearer and session deletion events respectively.

pcscf-restoration-ind

Enables the P-CSCF Restoration Indication feature. By default, this feature is disabled.

Important

This keyword is license dependent. For more information, contact your Cisco account representative.

This keyword, when enabled, allows the negotiation of P-CSCF Restoration feature support with PCRF. A new Diameter AVP “PCSCF-Restoration-Indication” is introduced to indicate to PCEF that a P-CSCF Restoration is requested. This is achieved by setting AVP value to 0.

For more information on this feature, see the Gx Interface Support chapter in the administration guide of the product you are deploying.

pending-transactions

Configures the Pending Transactions feature as part of supported features. This keyword addition is to handle race conditions on Gx i.e. process the Diameter messages in the order they are received.

Gx-based applications are vulnerable to certain race conditions (e.g. concurrent RAR/CCR). Enhancements are done on the Diameter protocol to deterministically handle the race conditions on Gx.

In a scenario wherein RAR is received while waiting for CCA-U, Gx application rejects RAR with Experimental-Result-Code AVP set to DIAMETER_PENDING_TRANSACTION. This should be done only if PCRF supports this functionality otherwise Gx client should continue with the current implementation.

If race conditions are not processed properly, it can lead to unpredictable behavior from each node, resulting in subscriber disconnection. With this feature, the outcome in such situation is deterministic and operator has the ability to influence the node behavior aligned with their policy.

Important

Currently only one pending transaction is supported. So, all other transactions (like handoffs, etc) while one is pending will be rejected.

• Support for Negotiation of PT in initial session establishment.

• Support for receiving/sending 4144 with 3GPP Vendor ID in CCA/RAA.

• Retry of CCR-U when 4144 is received from PCRF.

• No Support for 4198 with Proprietary Vendor ID.

• Recovery of negotiated Supported features.

session-recovery

Enables the Session Recovery feature. This functionality helps ensure that the PCRF and P-GW can be in sync on session information and recover any lost Gx sessions. By default, session recovery and session sync features are not enabled.

Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers, etc. In this release, the Gx interface between P-GW and PCRF has been enhanced to allow the PCRF and P-GW to sync-up. This is currently not part of 3GPP 29.212.

Important

In this release, the Session Recovery and Sync will be supported only for the IMS APN.

This keyword is used to achieve the session recovery. When this feature is enabled, P-GW and PCRF will exchange session information and P-GW provides the complete subscriber session information to enable PCRF to build the session state.

session-sync

Enables the Session Synchronization feature. This functionality helps ensure that the PCRF and P-GW can be in sync on session information and recover any lost Gx sessions. By default, Session Recovery and Session Sync features will not be enabled.

Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers, etc. The Gx interface between P-GW and PCRF is enhanced to allow the PCRF and P-GW to sync-up. This is currently not part of 3GPP 29.212.

Important

In this release, the Session Recovery and Sync will be supported only for the IMS APN.

This keyword is used to achieve the session sync-up. When this feature is enabled, P-GW and PCRF will exchange session information and P-GW provides the complete subscriber session information to enable PCRF to build the session state.

sgw-restoration

This keyword enables configuration of S-GW Restoration feature.

P-GW is configured to support S-GW Restoration feature. P-GW sends S-GW Restoration feature in Supported-Features AVP through the CCR-I message during session creation. If P-GW receives S-GW Restoration feature in Supported-Features AVP in CCA-I message, then P-GW enables S-GW Restoration feature.

If P-GW and PCRF support S-GW Restoration feature, then the P-GW accepts CCA and RAR during S-GW restoration. Only Rule removal or RAR with session release cause is processed. Any rule install or modify is dropped. P-GW triggers CCR-U with PCC rule failure report and AN_GW_STATUS AVP to inform PCRF that S-GW is down. After receiving the SGW_Restoration indication, PCRF does not initiate any rule install or modification towards the P-GW. The P-GW informs the PCRF when the S-GW has recovered using the Event-Trigger AVP set to AN_GW_CHANGE and including the AN-GW-Address AVP related to the restored or new S-GW. If S-GW restoration is reported to PCRF, then the P-GW sends CCR-U with AN_GW_CHANGE trigger.

If S-GW Restoration feature is not negotiated through the Supported-Features AVP, then P-GW falls back to the old behavior as follows:

• Drops all internal updates towards PCRF

• Rejects CCA and RAR during S-GW Restoration

• Does not include AN_GW_STATUS as AN_GW_FAILED (0) AVP in CCR-U

• Sends an RAA command with the Experimental-Result-Code set to UNABLE_TO_COMPLY (5012) upon receiving RAR command

After configuring the S-GW Restoration feature on Gx interface, the failure is sent to PCRF with Rule-Failure-Code as AN_GW_FAILED in both failure and restoration scenarios.

sponsored-connectivity

Enables the Sponsored (data) Connectivity feature.

With sponsored data connectivity, the sponsor has a business relationship with the operator and the sponsor reimburses the operator for the user's data connectivity in order to allow the user access to an associated Application Service Provider's (ASP) services. Alternatively, the user pays for the connectivity with a transaction which is separate from the subscriber's charging. It is assumed the user already has a subscription with the operator.

The purpose of this feature is to identify the data consumption for a certain set of flows differently and charge it to sponsor. To support this, a new reporting level "SPONSORED_CONNECTIVITY_LEVEL" is added for reporting at Sponsor Connection level and two new AVPs "Sponsor-Identity" and "Application-Service-Provider-Identity" have been introduced at the rule level.

This CLI command "diameter encode-supported-features " has been added in Policy Control Configuration mode to send Supported-Features AVP with Sponsor Identity.

Sponsored Connectivity feature will be supported only when both P-GW and PCRF support 3GPP Rel. 10. P-GW advertises release as a part of supported features in CCR-I to PCRF. If P-GW supports Release 10 and also Sponsored Connectivity but PCRF does not support it (as a part of supported features in CCA-I), this feature is turned off.

This feature implementation impacts only the Gx dictionary "dpca-custom15".

trusted-wlan

Enables the Trusted WLAN feature.

netloc-trusted-wlan

Enables the NetLoc trusted WLAN feature over Gx interface.

This command takes effect when Gx is enabled on S2b call. By default, the feature is disabled and TWAN information will not be sent over Gx.

netloc-untrusted-wlan

Enables the NetLoc untrusted WLAN feature over Gx interface.

This command takes effect when Gx is enabled on S2b call. By default, the feature is disabled and UWAN information will not be sent over Gx.

virtual-apn

This keyword enables configuration of Gx-based Virtual APN (VAPN) feature. For VAPN 4th bit of supported feature will be set. By default, this supported feature will be disabled.

Important

Gx-based VAPN is a licensed-controlled feature. Contact your Cisco account representative for detailed information on specific licensing requirements.

This keyword "virtual-apn " will be available only when the feature-specific license is configured.

In releases prior to 19, VAPN selection was possible through RADIUS or local configuration. In Release 19, ASR5K uses PCRF and Gx interface for Virtual APN selection to achieve signaling reduction.

This keyword enables Gx based Virtual APN Selection feature for a given IMS authorization service. When this configuration is enabled at P-GW/GGSN, then P-GW/GGSN advertises this feature to PCRF through the Supported-Features AVP in CCR-I. When the VAPN is selected, then the PCRF rejects the CCR-I message with the Experimental-Result-Code AVP set to 5999 (DIAMETER_GX_APN_CHANGE), and sends a new APN through the Called-Station-Id AVP in CCA-I message. The existing call is then disconnected and established with the new virtual APN. Note that the Experimental Result Code 5999 will have the Cisco Vendor ID.

Important

Enabling this feature might have CPU impact (depending on the number of calls using this feature).

Limitations:

• Virtual APN supported feature negotiation, Experimental Result Code (5999), Called-Station-Id AVP should be received to establish the call with new virtual APN. When any one of conditions is not met then the call will be terminated.

• Failure-handling will not be taken into account for 5999 result-code when received in the CCA-I message.

• When the Experimental Result Code 5999 is received in the CCA-U then failure-handling action will be taken.

• If the Called-Station-Id AVP is received in CCA-U or CCA-T, then the AVP will be ignored.

• If virtual-apn is received in local-policy initiated initial message then the call will be terminated.

• When PCRF repeatedly sends the same virtual-apn, then the call will be terminated.

default | no

This keyword removes the previously configured supported features.

This command controls pacing of the reselection or switching of the PCRF after a change occurs in the table configuration for an IMS Authorization Service.

subscriber-limit subs_limit

Specifies the limit of subscribers to switch or reselect the PCRF for subscribers not more than subs_limit in time duration of duration second(s).

subs_limit must be an integer from 1 through 10000000.

time-interval duration

Specifies the time duration, in seconds, to reselect PCRF for subscribers not more than subs_limit in time duration of duration second(s).

duration must be an integer from 1 through 3600.

default

Applies the default setting for this command.

Sets the PCRF reselection or switching to default state.

no

Removes the configured PCRF reselection method and disables the reselection or switching of PCRF.

This command adds/appends rows with precedence to a Diameter host table or MSISDN prefix range table.

diameter host-select row-precedence precedence_value table { 1 | 2 } host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] ]

This command adds/appends a row in the specified Diameter host table.

In 8.0, a maximum of 16 rows can be added to a table. In 8.1 and later releases, a maximum of 128 rows can be added per table.

row-precedence precedence_value : Specifies precedence of the row in the Diameter host table.

Important

In 8.1 and later releases, precedence_value must be an integer from 1 through 128. In 8.0 and previous releases, precedence_value must be an integer from 1 through 100.

table { 1 | 2 } : Specifies the Diameter host table to add/append the primary and secondary Diameter host addresses.

host host_name : Specifies the primary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.

realm realm_id : Specifies the primary realm ID. realm_id must be an alphanumeric string of 1 through 127 characters in length.

secondary host sec_host_name [ realm sec_realm_id ] : Specifies the secondary host name and realm ID:

host sec_host_name : Specifies the secondary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.

realm sec_realm_id : Specifies the secondary realm ID. realm_name must be an alphanumeric string of 1 through 127 characters in length.

no diameter host-select row-precedence precedence_value table prefix-table { 1 | 2 } }

Removes the row with the specified precedence from the specified MSISDN prefix range table.

diameter host-select row-precedence precedence_value table prefix-table { 1 | 2 } msisdn-prefix-from msisdn_prefix_from msisdn-prefix-to msisdn_prefix_to host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] algorithm { active-standby | round-robin } ] [ -noconfirm ]

Use this command to configure the MSISDN prefix range based PCRF selection mechanism for Rel. 7 Gx interface support, wherein the PCEF is required to discover and select an appropriate PCRF to establish control relationship at primary PDP context activation.

This command adds a row in the specified MSISDN prefix range table. A maximum of 128 rows can be added per prefix range table.

row-precedence precedence_value : Specifies precedence of the row in the table.

Important

In 8.1 and later releases, precedence_value must be an integer from 1 through 128. In 8.0 and previous releases, precedence_value must be an integer from 1 through 100.

prefix-table { 1 | 2 } : Specifies the MSISDN prefix range table to add the primary and/or secondary Diameter host addresses.

msisdn-prefix-from msisdn_prefix_from : For a range of MSISDNs, specifies the starting MSISDN.

msisdn-prefix-to msisdn_prefix_to : For a range of MSISDNs, specifies the ending MSISDN.

Important

To enable the Gx interface to connect to a specific PCRF for a range of MSISDNs/subscribers configure msisdn_prefix_from and msisdn_prefix_to with the starting and ending MSISDNs respectively. The MSISDN ranges must not overlap between rows. To enable the Gx interface to connect to a specific PCRF for a specific MSISDN/subscriber, configure both msisdn_prefix_from and msisdn_prefix_to with the same MSISDN.

host host_name : Specifies the primary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.

realm realm_id : Specifies the primary realm ID. realm_id must be an alphanumeric string of 1 through 127 characters in length.

secondary host sec_host_name [ realm sec_realm_id ] : Specifies the secondary host name and realm ID: host sec_host_name : Specifies the secondary host name. sec_host_name must be an alphanumeric string of 1 through 127 characters in length.

realm sec_realm_id : Specifies the secondary realm ID. sec_realm_id must be an alphanumeric string of 1 through 127 characters in length.

algorithm { active-standby | round-robin } : Specifies the algorithm for selection between primary and secondary servers in the MSISDN prefix range table.

Default: active-standby

active-standby : Specifies selection of servers in the Active-Standby fashion.

round-robin : Specifies selection of servers in the Round-Robin fashion.

Important

The Round Robin algorithm for PCRF selection is effective only over a large number of PCRF selections, and not at a granular level.

[-noconfirm]

Specifies that the command is to execute without any additional prompt and confirmation from the user.

no diameter host-select row-precedence precedence_value table { 1 | 2 }

Removes the row with the specified precedence from the specified Diameter host table.

This command selects the Diameter host table or the MSISDN prefix range table, and the algorithm to select rows from the Diameter host table.

diameter host-select table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }

table { 1 | 2 } : Specifies the Diameter host table to obtain the primary and secondary host names for PCRF.

algorithm { ip-address-modulus [ prefer-ipv4 | prefer-ipv6 ] | msisdn-modulus | round-robin } : Specifies the algorithm to select row from the Diameter host table.

Important

The Round Robin algorithm is effective only over a large number of selections, and not at a granular level.

diameter host-select table prefix-table { 1 | 2 }

Specifies the MSISDN Prefix Range table to be used in case of MSISDN prefix range based PCRF discovery mechanism.

default

Applies the default setting for this command.

no

Removes previous configuration.

When no table is selected, the system will not communicate with any PCRF for new sessions.

This command specifies the Diameter host server template to be associated with this IMS Authorization service. The service uses the specified template (and associated host-select table) to select a Diameter peer server. It then uses the returned host name(s) to contact the PCRF and establish the call.

no

Removes the binding of the Diameter host select template with the IMS Authorization service.

tmplt_name

Specifies the name of an existing Diameter host server template (configured in Global Configuration mode) to bind with the IMS Authorization service. It is an alphanumeric string of 1 through 255 characters.

This command enables selecting the value to which the USAGE_REPORT and APN_AMBR_MOD_FAILURE Event-Trigger should be mapped to.

usage-report { 29 | [ 26 | 33 ] [ 26 | 33 ] }

Maps the USAGE_REPORT of Event-Trigger AVP to one or a combination of these values.

default

The default behavior is to configure the Event-Trigger USAGE_REPORT to be mapped to 26.

This command binds the origin endpoint configured in Context Configuration mode to the IMS Authorization service for Diameter Policy Control Application (DPCA).

endpoint endpoint_name

endpoint_name is the Diameter endpoint configured in Context Configuration Mode to bind with IMS authorization service, and must be an alpha/numeric string of 1 through 63 characters in length.

no

Removes the binding of Diameter origin endpoint with IMS Authorization service.

This command configures the request-timeout setting for Diameter-IMSA Gx interface.

timeout

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

Default: 10 seconds

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

Specifies independent timers (in deciseconds) for all message types like CCR-I, CCR-U and CCR-T. 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 ".

default

Applies the default setting for this command.

This command enables prioritization of Gx messages based on eMPS state of the session. From Release 21.4, it also supports DRMP AVP with value 0 to be sent in Credit Control Request (Initial, Update and Terminate) messages over the Gx interface for P-GW eMPS sessions and for eMPS upgrade and downgrade transactions. Also the help string for “session prioritization” keyword is updated accordingly.

no

Disables the command and has the following implications:

• Disables prioritization of Gx messages for eMPS sessions and eMPS upgrade and downgrade.

• Disables encoding of DRMP AVP (value 0) in Credit Control Request (Initial, Update, and Terminate) messages for eMPS sessions and eMPS upgrade and downgrade.

By default, the CLI is disabled and Gx messages will not be prioritized based on eMPS value.

This command enables reporting of SGSN_CHANGE event trigger and SGSN-Address AVP for 2G and 3G calls on GnGp P-GW.

sgsn-change-reporting

This keyword specifies to detect SGSN change and send SGSN-Address AVP and SGSN_CHANGE event trigger for a subscriber in 2G/3G on Gx interface during GnGp scenario.

no

This variant specifies to send AN-GW-Address AVP during the call setup, when SGSN change happens, or during the handoff from 4G to 3G. This is the default setting.

This command enables dictionary control of the AVPs that need to be added based on the version of the specification to which the PCEF is compliant with.

default | no

Configures this command with the default setting.

The default behavior is that R9 support will not be indicated as part of Supported-Features AVP in a R7/R8 dictionary and R8 support will not be indicated as part of Supported-Features AVP in a R7 dictionary.

3gpp-r8

Specifies to select the 3GPP Rel. 8 AVPs for encoding.

3gpp-r9

Specifies to select the 3GPP Rel. 9 AVPs for encoding.

3gpp-r10

Specifies to select the 3GPP Rel. 10 AVPs for encoding.

This command enables Diabase to select the Diameter peers in all failure scenarios.

on-host-select-failure

Specifies to perform server selection at Diabase when the hosts could not be selected by IMS Authorization application.

on-inactive-host

Specifies to perform server selection at diabase when the hosts selected by application are inactive.

default | no

Default/no behavior is to terminate the call when the hosts could not be selected by application or when the hosts selected by application are inactive.

This command enables event report indication.

all | pgw-trace-control | qos-change | rai-change | rat-change | sgsn-change | ue-timezone-change | user-loc-change

default | no

Disables event report indication.

This command configures sending usage monitoring information in event updates either for all event triggers or for a specific event trigger.

default

Configures the default setting for this command.

Default: Usage report is not sent in event update.

no

Disables sending usage report in event update.

reset-usage

Resets the usage at PCEF after reporting in event update.

events { an-gw-change | apn-ambr-mod-failure | bearer-loss | bearer-rcvry | charging-correlation-exchange | default-bearer-qos-change | default-bearer-qos-mod-failure | | ip-can-change | out-of-credit | pgw-trace-control | plmn-change | qos-change | qos-excess-change | rai-change | rat-change | reallocation-of-credit | resource-modification-request | revalidation-timeout | sgsn-change | successful-resource-alloc | tft-change | ue-ip-addr-allocate | ue-ip-addr-release | ue-timezone-change| user-loc-change }+

This command configures Diameter failure handling behavior.

no

Disables previous failure-handling configuration.

retry-and-terminate

Specifies that in the event of a failure the user session continues for the duration of one retry attempt with the server. If this retry attempt also fails, the session is terminated.

terminate

Specifies that in the event of a failure the user session be terminated.

diameter-result-code { any-error | result_code [ to end_result_code ] }

Specifies failure handling behavior for any/specific result-code(s) to identify the type of failure and failure handling action for specific credit control request type.

any-error : Specifies failure handling behavior for those result-codes for which failure-handling behavior has not been specified.

result_code : Specifies a Diameter failure result code. result_code is the code returned for a failure handling action and must be an integer from 3000 through 4999.

to end_result_code : Use to specify a range of Diameter failure result codes. end_result_code must be an integer from 3000 through 4999, and must be greater than result_code .

continue [ retry-server-on-event | send-ccrt-on-call-termination ] | retry-and-terminate | terminate

As in 8.1 and later releases:

ccfh { continue | retry-and-terminate | terminate }

As in 8.0 release:

cc-request-type

As in 8.0 release:

Refer to the Cisco ASR 5000 Lawful Intercept Configuration Guide for a description of this command.

This command enables or disables the gateway to send multiple back-to-back CCR-Us to PCRF.

default

This keyword sets the default value as 1 for the maximum number of outstanding CCR-U messages to be sent to PCRF.

value

This keyword configures a value for the maximum number of outstanding CCR-U messages to be sent to PCRF.

value must be an integer value from 1 through 12.

This command enables required subscription-id types for various services. The Subscription-ID AVP will be encoded based on the configured subscription-ID type.

default | no

Configures this command with the default setting.

The default behavior is that Subscription-ID AVP will be encoded based on service-type and Diameter dictionary.

{ closed_rp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw | samog-epdg } { e164 | imsi | nai }

Controls the encoding of Subscription-ID AVP based on the following service-types associated with services such as GGSN, HA, IPSG, PDSN, SaMOG, ePDG,etc.

In Release 21, samog-epdg service type is added to allow encoding of Subscription-ID with a combination of MSISDN, NAI or IMSI in CCR for SaMOG (S2a) or ePDG (S2b) service for WLAN access types (trusted and untrusted 3GPP access types). This keyword is supported to send the Subscription-ID AVP with MSISDN in CCR-I or CCR-U towards PCRF. For more information on the functionality, see the Gx Interface Support chapter in the administration guide of the product you are deploying.

+

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