Bug ID 522934: Provide an option to encode subscription ID in CCR-U/CCR-T messages over Gx/Gy

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP PEM(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
11.6.0 HF6

Opened: May 13, 2015

Severity: 3-Major

Symptoms

Some PCRF's require subscription ID in all CCR messages over Gx/Gy for easier session management.

Impact

Some PCRF's will not work properly with PEM if subscription ID is not specified in CCR-u and CCR-T messages.

Conditions

PEM with Gx enabled and connected to a PCRF.

Workaround

Set the sys db variable to True to see Subscription ID in CCR-u and CCR-T messages as well: Tmm.diameter.application.encode.subscriber.id.in.all.ccr Note: By default it is set to True.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips