APPLICATION_START and APPLICATION_STOP triggers unconditionally in CCR-A by PCRF
(Doc ID 2575071.1)
Last updated on FEBRUARY 13, 2020
Applies to:Oracle Communications Policy Management - Version POLICY 11.0.0 to POLICY 12.5.2 [Release POLICY 11.0 to POLICY 12.0]
Information in this document applies to any platform.
Customer have below concern after enabled ADC functionality on our PGW and bit 6 in the Support Features AVP is now set for ADC.
CCR-I from PGW to PCRF
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] Feature-List-ID: 1
[V] Feature-List: 66
In the CCR-A the PCRF appears to set the APPLICATION_START and APPLICATION_STOP triggers unconditionally i.e. even if customer have NOT specified this in a policy. For example, the simple policy below results in the event triggers below.
where the user E.164 phone number matches one of 6421123456 (TEST MSISDN)
Advanced: set values for QoS and Charging parameters to
Diameter Enforcement Session Event Triggers NO_EVENT_TRIGGERS
CCA-I from PCRF to PGW
[V] [M] Event-Trigger: NO_EVENT_TRIGGERS (14)
[V] [M] Event-Trigger: APPLICATION_START (39)
[V] [M] Event-Trigger: APPLICATION_STOP (40)
1) Does the PCRF unconditionally set the APPLICATION_START and APPLICATION_STOP triggers even if there is no policy defining this?
2) In the case where a policy defines "NO_EVENT_TRIGGERS" (like in the example above), the PCRF seems to incorrectly send back this and the APPLICATION_START/STOP triggers? This does make sense and generates an error message on our PGW.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document