Cisco Cisco Packet Data Interworking Function (PDIF) Notas De La Versión
GTPP Changes in Release 15.0
▀ GTPP Enhancements for January 31, 2014
▄ Cisco ASR 5x00 Release Change Reference
222
gtpp egcdr { closure-reason admin-disconnect [ management-intervention | normal-
release ] }
release ] }
default gtpp egcdr closure-reason admin-disconnect
end
Notes:
The new keyword options specify to send either Management-Intervention or Normal Release as
causeForRecordClosing in PGW-CDRs. By default, Management-Intervention will be sent as the record
closure reason for PGW-CDRs.
closure reason for PGW-CDRs.
CSCui40165 - Charging in ‘servers unreachable’ state, special reporting in
CDRs
Applicable Products: P-GW
Feature Changes
Secure Charging Functionality During OCS Failure
This feature provides the functionality to generate interim PGW-CDRs with the following causeForRecordClosing
Reasons:
Reasons:
OCS_UNREACHABLE – when OCS becomes unreachable.
OCS_REACHABLE – when OCS becomes reachable.
OCS_STATUS_UNKNOWN – when a session is terminated and when there is a chance of double counting.
Scenario in which this will be used is when the configured interim-quota is exhausted and when the connection
to the server is retried by sending out a CCR-I/U and termination is initiated (before timeout).
to the server is retried by sending out a CCR-I/U and termination is initiated (before timeout).
The duplicate charging is solved by suppressing the MSCC’s in CCR-T. Since no MSCCs are encoded in the CCR-T, no
usage will be reported and at the same time a CCR-T will be generated to close the session on the OCS server.
usage will be reported and at the same time a CCR-T will be generated to close the session on the OCS server.
Important:
This behaviour is applicable only for custom45 GTPP dictionary (PGW-CDRs).
For this feature to work, custom45 should be configured as the GTPP dictionary under GTPP Group configuration and
the CLI command “
the CLI command “
servers-unreachable
” should also be configured under Credit-Control Group. With this feature
turned on, it is easy to identify the potentially unreported usage prior to the CCFH.
There will NO OCS_UNREACHABLE CDR generations on failed retries, when we are in unreachable state.
There will be no flag in the CDRs to indicate if the OCS is unreachable/reachable. So, the CDRs generated due to other
reasons like time-limit, volume-limit, triggers, etc., while the OCS is unreachable, will have no flag indicating the OCS-
unreachable status. If there are no specific service-condition changes to be reported, the LOSDVs that are cut by these
CDRs (Unreachable/Reachable/OCS_STATUS_UNKNOWN) will have record-closure as the serviceConditionChange.
reasons like time-limit, volume-limit, triggers, etc., while the OCS is unreachable, will have no flag indicating the OCS-
unreachable status. If there are no specific service-condition changes to be reported, the LOSDVs that are cut by these
CDRs (Unreachable/Reachable/OCS_STATUS_UNKNOWN) will have record-closure as the serviceConditionChange.
CSCuj99515 - Disabling the triggers for closing CDR service containers
Applicable Products: P-GW