Acme Packet 6300
 

PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-12915932061>

Applies to:

Symptoms

When a call contains multiple Diversion headers embedded in one Diversion header. This causes an issue on their CDR reports.

Changes

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?

Cause

RFC 6044 is not supported.

Solution

The root cause for this issue is the client has multiple diversion headers embedded within a single diversion header in the INVITE request, which is against the behavior specified in RFC 5806 (sec 6.5 - multiple diversions).

Going by the RFC, the client should have generated individual diversion header for each diversion. Since, the diversion values have been just separated by a comma(,) and with the CDR format type being CSV, this gives the illusion that the SD is adding an additional field, whereas the SD has only copied the value provided to it.

The delimiter value - comma is hard coded in the software and we cannot change it.

References

This solution has no attachment