Cisco Cisco ASR 5000
Context Configuration Mode Commands E-H
gtpp attribute ▀
Command Line Interface Reference, StarOS Release 18 ▄
2459
Important:
The Abnormal Bearer Termination feature is currently applicable only to custom34 and custom35
GTPP dictionaries. That is, the bearer termination cause is populated in SGW-CDR for custom34 and custom35
dictionaries, and PGW-CDRs for custom35 GTPP dictionary when the cause for record closing is “Abnormal Release”.
dictionaries, and PGW-CDRs for custom35 GTPP dictionary when the cause for record closing is “Abnormal Release”.
direct-tunnel
Default: Disabled
Includes the Direct Tunnel field in PGW-CDR/eG-CDRs.
This keyword is applicable for GGSN, P-GW and S-GW only.
Includes the Direct Tunnel field in PGW-CDR/eG-CDRs.
This keyword is applicable for GGSN, P-GW and S-GW only.
duration-ms
Specifies that the information contained in the mandatory Duration field be reported in milliseconds instead
of seconds (as the standards require). Default: Disabled
of seconds (as the standards require). Default: Disabled
dynamic-flag
Default: Enabled
This keyword controls the inclusion of the optional field “Dynamic Flag” in the x-CDRs.
This keyword controls the inclusion of the optional field “Dynamic Flag” in the x-CDRs.
dynamic-flag-extension
Default: Enabled
This keyword controls the inclusion of the optional field “Dynamic Address Flag Extension” in the x-CDRs.
This field is seen in the CDR when the IPv4 address is dynamically assigned for a dual PDP context. This
extension field is required in the 3GPP Release 10 compliant CDRs so that the Dual Stack Bearer support is
available.
This keyword controls the inclusion of the optional field “Dynamic Address Flag Extension” in the x-CDRs.
This field is seen in the CDR when the IPv4 address is dynamically assigned for a dual PDP context. This
extension field is required in the 3GPP Release 10 compliant CDRs so that the Dual Stack Bearer support is
available.
furnish-charging-information
Default: Disabled
This keyword controls the inclusion of the optional field “pSFurnishChargingInformation” in the eG-CDRs
and PGW-CDRs.
This keyword controls the inclusion of the optional field “pSFurnishChargingInformation” in the eG-CDRs
and PGW-CDRs.
Important:
The Furnish Charging Information (FCI) feature is applicable to all GTPP dictionaries compliant to
3GPP Rel.7 and 3GPP Rel.8 except custom43 dictionary. This keyword option will be available only if a valid license is
installed. For more information, contact your Cisco account representative.
installed. For more information, contact your Cisco account representative.
PGW-CDR and eG-CDR will contain FCI only if it is enabled at command level, i.e. using the
gtpp
attribute furnish-charging-information
command in GTPP Server Group Configuration mode.
Whenever FCI changes, a new Free-Format-Data (FFD) value is either appended to existing FFD or
overwritten on the existing FDD depending on Append-Free-Format-Data (AFFD) flag. CDR is not generated
upon FCI change.
FCI is supported in main CDR as well as in LOSDV. Whenever a trigger (volume, time, RAT, etc.) happens
current available FFD at command level is added to the main body of the CDR. The same FFD at command
level is added to the main body of the next CDRs until it is not appended or overwritten by next Credit-
Control-Answer message at command level.
In the case of custom43 dictionary, the FCI implementation will be as follows:
overwritten on the existing FDD depending on Append-Free-Format-Data (AFFD) flag. CDR is not generated
upon FCI change.
FCI is supported in main CDR as well as in LOSDV. Whenever a trigger (volume, time, RAT, etc.) happens
current available FFD at command level is added to the main body of the CDR. The same FFD at command
level is added to the main body of the next CDRs until it is not appended or overwritten by next Credit-
Control-Answer message at command level.
In the case of custom43 dictionary, the FCI implementation will be as follows:
Whenever FCI changes PGW-CDR will generate CDR i.e close old bucket and will have old FCI
details in the generated CDR.