HTML format Reports

[eortizn85]

Hello guys,

We recently upgraded our Vicidial server to Vicibox 7.
VERSION: 2.12-563a
BUILD: 160801-2119

We are using this installation:
- 1 DB Server: HP Proliant DL160 G9, 2 CPUs E5-2603v3, 24 Gb RAM, 300Gb HD SAS 15Krpm/6G/s
- 1 Web Server: HP Proliant ML150 G6, 2 CPUs Xeon Quad Core E5520, 10 Gb RAM, 300 Gb HD SAS 15 Krpm
- 4 PBX: HP Proliant DL360 G5, 2 CPU Xeon Quad Core E5345, 10 Gb RAM, 146 Gb HD SAS 10 Krpm

60 agents simultaneously (for now, we expect this will increase in the near future).

Since we are having a couple of issues, I'm going to post them here:

First Issue:

The Asterisk server didn't start automatically on boot, we had to start it manually in pbx1 and pbx2. And also we had to reinstall the DAHDI module, because its service wouldn't start at all.
Everything was working fine until, suddenly pbx1 stopped sending calls through the trunk to our gateway, instead the calls were going out through pbx2.
We are considering a full reinstall of pbx1 and pbx2 due to the little time we have to fix this. By the way, pbx3 and pbx4 are working fine and we are using them instead of the other two.

Second Issue:

The new graphic interface is really cool, and our operators are happy with the new graph options on the reports tool. However, we just noticed when we run a report (i.e. Team Performance Detail) and we pick several groups at once using HTML format, it changes randomly the group members name.
Testing a simple work around for our operators, found that if you run the report for each group individually it wouldn't change the group member names. I'm not sure if this is a bug or if we have to patch something in our web server.

Hopefully tomorrow we will dig more into this, but in the meantime I wanted to know what you guys think about this, maybe the answer is simplet than it seems.

Thank you very much in advance.
- Enmanuel Ortiz

[mflorell]

As for issue 1, there could be several causes of that. What VICIbox version did you install?

As for issue 2, this should be fixed in svn/trunk. Just upgrade and let us know if you continue to have any issues.