Symptoms

For Gy interface, if OCS doesn't respond to the initial set of CCR-I requests as per the diameter-endpoint profile (1+ msg-max-retransmits <n>), the new set of CCR-I requests are not being generated, even after provisioning pending timeout happens.

Impact

The subscriber will be left in Idle state till the default quota is breached and brought down or subscriber can reconnect once OCS CCA response is fixed.

Conditions

This issues happens only for Gy interface and when initial set of CCR-I request doesn't get a CCA response.

Workaround

Re-connect the subscriber once the CCA response is fixed in OCS

Fix Information

The solution is to resend CCR-I requests once the provisioning timeout happens

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips