Skip to content
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.

Incorrect duration for conference call journal line #7

Open
UNIVAC-Colonel-Panic opened this issue Jun 23, 2016 · 1 comment
Open

Comments

@UNIVAC-Colonel-Panic
Copy link

TAPI plugin is enabled. I initiated an outgoing call into the PBX's conference center. At the end of the call, the duration shows as the time the call ended (e.g., "10:36") instead of the 90 minute duration. What info can I provide to help you troubleshoot this?

@Sonderstorch
Copy link
Owner

There ought to be *.log and *.00x files in %LOCALAPPDATA%\cmon (you can type that in the address bar of Windows Explorer). That may provide some more insight.

I know that connection tracking of c'mon is currently depending heavily on the sequence the TAPI messages are sent by the TAPI provider and not all cases are currently handled correctly.

I'm planning a pre-release having some tracing and logging capabilities to track those issues down.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants