lmdelacruz
IS-IT--Management
Hi everyone,
We have an Avaya CMS 16.2 Server that collects call logs for our Avaya CM5 PABX Server (ACD1). It was generating CHR reports regularly for our external servers to be collected and used for an external ECHI Reports engine. Then, a couple of months ago, we tried to add ACD2 for our new Avaya CM7 PABX Server. We would also like to generate the CHR reports for this new CM7 PABX. So that our external ECHI Reports engine can display the two ACDs (both CM5 and CM7 Server). After our activity, it only generates CHR reports of the two ACDs for 8~9 hours duration and will stop. The only workaround we do is to restart both the CMS and External Call History service of the CMS server, then it will be ok again for 8~9 hours. Which is kind of tedious for us since we operate 24/7. Can someone help us with this one?
We have an Avaya CMS 16.2 Server that collects call logs for our Avaya CM5 PABX Server (ACD1). It was generating CHR reports regularly for our external servers to be collected and used for an external ECHI Reports engine. Then, a couple of months ago, we tried to add ACD2 for our new Avaya CM7 PABX Server. We would also like to generate the CHR reports for this new CM7 PABX. So that our external ECHI Reports engine can display the two ACDs (both CM5 and CM7 Server). After our activity, it only generates CHR reports of the two ACDs for 8~9 hours duration and will stop. The only workaround we do is to restart both the CMS and External Call History service of the CMS server, then it will be ok again for 8~9 hours. Which is kind of tedious for us since we operate 24/7. Can someone help us with this one?