Cisco Bug: CSCte60624 - SBC does not include coded information in billing records with 302 redir
Feb 16, 2011
- Cisco ASR 1000 Series Aggregation Services Routers
Known Affected Releases
Symptom: When a 302 message is received for a call that was routed via SBC, SBC does not include proper billing (PacketCable attributes when PacketCable billing is configure) attributes on the egress leg of the call. This results in billing systems not being able to co-relate both call legs and bill the call. Conditions: This occurs when a 302 is received for a call that was routed via SBC.
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