Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

This is accomplished by setting the Write above Text to File? to “Yes” and entering details of the records function in the Text for File Output field.

0
Posted

This is accomplished by setting the Write above Text to File? to “Yes” and entering details of the records function in the Text for File Output field.

0

Run the routine, and then look at the CMCalls.TXT file. In this file you will see each record and where things went wrong. Watch the system carefully to see where this happens by observing the port’s activities. For more information about the label field, read the description of the field in the beginning of the “Audiotex” section. The CMCalls.TXT file is defined by the Logging Parameter Call Log File, and can be viewed while CALLMaster is running. It would be helpful to turn off the status screen first so you don’t get a jumble of data on the screen. Another way to debug is to make a recording in each record. An Audiotex key will play the message first. The last message you hear before the system freezes is the one you need to check for the problem.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123