Quote:
|
Originally Posted by Cephas
Are you sure you're not confusing that with the known fact that it will ALWAYS count the call against the highest numbered group the agent belongs to?
|
Known fact... after a colleague told me, because I don't think that's documented anywhere (I admit I haven't read the whole doc CD, however). Anyway, I've elliminated some groups so that agents belong to one and only one, and this problem disappeared, but some reports still show very strange data, even when before the upgrade they worked OK. For example, tabular agent group reports show all calls recorded to one line which is not an agent, but the group itself.
Quote:
|
Originally Posted by Cephas
If you are getting random logging (and even if you're not since you're using huntgroups), then DOWNGRADE to R2.0.18, the last stable build for IPO. R2.1 has a list of bugs that would make an exterminator shudder. Many many many huntgroup problems.
Peter
|
Hopefully, release 3.0 will be a decent one - it's said to be a complete rewriting from scratch. I've been told about the origins of 1.x and 2.x and it doesn't look like a quality design. In fact, it's a marvel that it works at all. If I had to count all the working hours spent trying to fix or workaround things that should work as explained in the manual, I'm quite sure that my company is losing money (and a lot) with IP Office, not counting intangibles as customer satisfaction.