Cisco Bug: CSCul26374 - SGW receives DL pkt for dedicated bearer on default bearer if fragmented
Jan 30, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: The SGW CDR (SGWRECORD) generated for dedicated bearer (pDNConnectionID and chargingID will be different) will have 0 dataVolumeGSGPRSDownlink but dataVolumeGPRSUplink will be non-zero. It can also be observed that the expected bytes in SGWRECORD for dedicated bearer in dataVolumeGPRSDownlink must have been added to dataVolumeGPRSDownlink of SGWRECORD of default bearer Note:- It is very important to note that if the packet sent on dedicated bearer is such that before going out it gets fragmented then only this issue occurs Conditions: If a 4G call is setup and a dedicated bearer is setup either in CCAI,CCAU or RAR (with or without enabling monitoring key for the dynamic rule for dedicated bearer) and if TFT for dedicated bearer has remote address different than the one for default bearer, then if data is sent (a packet which gets fragmented before going out) on to remote address of dedicated bearer then downlink response packet goes onto default bearer. This causes SGWRECORD with dataVolumeGSGPRSDownlink 0.
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