Cisco Bug: CSCuq22382 - PGw: UBReq not propagated to sessmgr after DBReq/Resp
Feb 08, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: When Update bearer (UBReq) for a dedicated bearer is in progress, the bearer getting initiated for a delete (DBReq). Now when we get the Delete (DBReq), we abort the procedure of the update. But this abortion of the UBReq never Propagated to Sessmgr and the bearer still assume Update is in progress. Any further update will never be sent... Conditions: It doesn't depend on the RAR from PCRF, if the same bearer id is allocated after the DBReq sequence you have mentioned followed by any type of UBReq on the freshly created bearer, you would hit the problem.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases