Jump to content

Wait duration in cdr packages are not coherent with duration in acd packages


Recommended Posts

  • 3 weeks later...

There are a couple of different time durations here. First of all, the trunk have a different view on the CDR, as it does not care if the call is in the ACD or AA or IVR node or whatever. Then from the account perspective, there is the time when the call is in the "ringing/unconnected" state (technically it can be already connected, but in the ACD the callers are considered unconnected until the agent picks up) and then there is the time how long the call is on hold, e.g. when the agent puts the call on hold. Maybe this is causing the confusion.

Link to comment
Share on other sites

  • 4 months later...

I have another question.


In call's acd packet sent to TCP port, wait duration is 1271309918. Also, sometimes it can be minus values. Because of these problems, the reports that i get according to these values are wrong.


What is the solution for this problem. Version :

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...