Bug ID 627616: CCR-U missing upon VALIDITY TIMER expiry when quota is zero

Last Modified: Jan 16, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP PEM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1

Fixed In:
13.0.0, 12.1.3.2

Opened: Nov 09, 2016
Severity: 3-Major

Symptoms

CCR-U is not sent upon VALIDITY TIMER experts.

Impact

OCS does not get the CCR-U message and misses the information about quota.

Conditions

If PCRF does not grant any GSU (no quota), but only specifies the VALIDITY timer.

Workaround

Work around is to set the following timers using sysdb to non-zero value. Here is an example: sys db tmm.pem.session.quota.bucket.denied.timeout { value "1" } sys db tmm.pem.session.quota.bucket.depleted.timeout { value "2" } sys db tmm.pem.session.quota.bucket.idle.timeout { value "3" }

Fix Information

CCR-U is now sent upon VALIDITY TIMER experts.

Behavior Change