Avaya CMS 16.2 External Call History Stops Generating CHR Report

[lmdelacruz]

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?

 

[BIS]

As always, step 1 would be "What do the logs tell you?"
/export/home/pserv/ech/echlog

 

[lmdelacruz]

Did we get the directory correct? As checked, there was no ech/echlog under the path /export/home/pserv/. Hoping to get the right path to check the logs.
We already checked other locations to get any logs that may guide us in troubleshooting this issue. However, we only found chr_logs under /cms/dc/chr/ kindly check the attached screenshot.

We are running uucp_check and uucp_copy for the generation of chr files. We can see that CMS is still trying to generate a CHR file because we noticed that chr_log is still populating.
You may also refer to these instructions that we have followed on our prior (working) configuration.

http://avaya.dwalin.ru/call-center/using-cms-external-call-history-interface-part-1-data-extraction/