On occasion, we will see an operator login session record twice (two records for the same operator, with the same login time/date and logout time/date). This started happening with Ace Operator V2.
This does not look like it is a problem. The problem may be with the Ace Communicator code which displays duplicate records because of a SQL join bug. Lowering the priority so that we can look at it later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks like the CDRs are getting generated properly and the bug is in the Ace Communicator report.
This does not look like it is a problem. The problem may be with the Ace Communicator code which displays duplicate records because of a SQL join bug. Lowering the priority so that we can look at it later.