Symptoms

CCR-I was send first and then CCR-T was sent if same subscriber session is created with different IP. This could cause confusion to PCRF when it sees at period of time 2 active sessions for the same subscriber.

Impact

CCR-I generated first and then CCR-T which will cause confusion to PCRF who maintain subscriber ID as their key to subscriber session.

Conditions

A session is created with subscriber ID say S1 and IP1 and new radius start or session create request arrives with S1 and IP2.

Workaround

None

Fix Information

Upgrade to latest hotfix or version which has the fix for the issue.

Behavior Change