Cisco Bug: CSCur23237 - Gx: event-trigger 33 displayed wrong for PDSN-SIP call in monitor msgs
May 21, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: event-trigger 33 is displayed wrong for PDSN-SIP call in Gx monitor messages Conditions: When event-trigger 33 is used for USAGE REPORTING and diameter map usage-report 33 is configured on the box, in Gx monitor messages the event-trigger goes with name USAGE_THRESHOLD_REACHED (33) instead of USAGE_REPORT (33).
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