Multiple Diversion Headers Causing the CDR CSV Field Placement To Change
Last updated on MAY 23, 2017
Applies to:Acme Packet 6300 - Version S-Cz7.2.0 to S-Cz7.4.0 [Release S-Cz7.0]
Information in this document applies to any platform.
When a call contains multiple Diversion headers embedded in one Diversion header. This causes an issue on their CDR reports.
Customer is using an internally developed CDR tool. The calls with multiple diversion headers are comma separated and the cdr mediation is parsing the file based on CSV format.
So the extra diversion headers which are added in the CDR is causing errors in our parsing.
Suppose the calls have 4 incoming diversion headers in an Invite. They are being written in the CDR, and it is resulting in 4 fields. Due to a comma in the field, it is making the field read as 4, even though the completed field is within a double quote.
The amount of fields does not match any more, thus creating an issue with the ORG header field and the request URI seen in the raw CDR's is sent to billing team.
Customer wants to know if we can change the default delimiter value - comma?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms