rohanmaradia
IS-IT--Management
CDR data issue
In one of our systems, we are observing that avaya cdr is recording the transfer node call segment prior to the initial IVR node contact call segment.
e.g. when a customer calls a tollfree number, it lands on IVR welcome message at vdn 270 and when the caller selects option number 2, he is routed to vdn 150. Here the call segment for 150 (transfer node) is being reported before 270 (IVR node), causing a mismatch of call duration calculation in call accounting software. Please refer to snapshot attached.
Also, as noticed, the segment with node 150 does not have caller number (striked out in other segments) but only the trunk TAC code. Is there a way we can enable calling number in transferred node segment as well ? The field parameter for this column is set to calling-number in cdr form.
This maybe an issue with cdr buffer transmission causing a write delay or any particular config on the switch, but i am not sure and need advise..
Appreciate if anyone can share a feedback on the same.
Thank you.
In one of our systems, we are observing that avaya cdr is recording the transfer node call segment prior to the initial IVR node contact call segment.
e.g. when a customer calls a tollfree number, it lands on IVR welcome message at vdn 270 and when the caller selects option number 2, he is routed to vdn 150. Here the call segment for 150 (transfer node) is being reported before 270 (IVR node), causing a mismatch of call duration calculation in call accounting software. Please refer to snapshot attached.
Also, as noticed, the segment with node 150 does not have caller number (striked out in other segments) but only the trunk TAC code. Is there a way we can enable calling number in transferred node segment as well ? The field parameter for this column is set to calling-number in cdr form.
This maybe an issue with cdr buffer transmission causing a write delay or any particular config on the switch, but i am not sure and need advise..
Appreciate if anyone can share a feedback on the same.
Thank you.