Cisco Bug: CSCvi58213 - PGW - Gy - After Final Interrogation we see that PGW doesn apply validity time expires
Jun 12, 2018
- Cisco ASR 5000 Series
- Cisco ASR 5500
Known Affected Releases
Symptom: Currently StarOs doesn't support this mechanism: RFC 4006 specifies that Validity timer should be applied and respected after Final Interrogation is finished. ------- 5.6. Graceful Service Termination When "Final Interrogation End's" and "Action and Restrictions Start" we expect that subscriber is redirected and with validity timer we periodically check if subscriber replenished account. https://tools.ietf.org/html/rfc4006#appendix-A 5.6.2. Redirect Action When the final granted units have been consumed, the credit-control client MUST perform an intermediate interrogation. The purpose of this interrogation is to indicate to the credit-control server that the specified action started and to report the used units. The credit-control server MUST deduct the used amount from the end user's account but MUST NOT make a new credit reservation. The creditcontrol client, however, may send intermediate interrogations before all the final granted units have been consumed for which rating and money reservation may be needed; for instance, upon Validity-Time expires or upon mid-session service events that affect the rating of the current service. Therefore, the credit-control client MUST NOT include any rating related AVP in the request sent once all the final granted units have been consumed as an indication to the server that the requested final unit action started, rating and money reservation are not required (when the Multiple-Services-Credit-Control AVP is used, the Service-Identifier or Rating-Group AVPs is included to indicate the concerned services). Naturally, the Credit-Control- Answer message does not contain any granted service unit and MUST include the Validity-Time AVP to indicate to the credit-control client how long the subscriber is allowed to use network resources before a new intermediate interrogation is sent to the server. Conditions: Current behavior Validity-timer will get started only when session has valid Quota/redirected-behavior. If validity-time is received with 4012 result-code without GSU or FUI (with redirect) information PGW doesn't apply Validity-timer.
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