Last Modified: Oct 01, 2018
See more info
Known Affected Versions:
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
Opened: Feb 09, 2016
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.
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.
This issues happens only for Gy interface and when initial set of CCR-I request doesn't get a CCA response.
Re-connect the subscriber once the CCA response is fixed in OCS
The solution is to resend CCR-I requests once the provisioning timeout happens