Hello community,
CM: 10.1
AES: 10.1
We have been running a recording application (formerly known as CallCopy) that utilizes DMCC for its recording channels and TSAPI to monitor the recorded stations for call events. We recently have stopped recording calls and, through our investigation, have determined that calls are not recording because the recorder is not receiving the TSAPI messages regarding call establish, call complete, call held, etc. The recorder is able to see specific TSAPI messages for Do Not Disturb and MWI and is able to register the monitors via TSAPI and the recording channels via DMCC.
I enabled TSAPI trace in the AES and the tsapi_trace.out logs indicate the same failure. AES is only sending heartbeats, do not disturb, and MWI messaging. To top the situation's oddity off, we interchanged our CM to a standby server and we properly recorded 10 calls over the course of the next hour, but nothing beyond that. During the 'working' time interval, still not all calls were recorded, but logs do verify that the appropriate TSAPI messages were being sent/received for the calls that did record.
With the background info stated, the main crux of my question is 'is it possible to see what CM is sending out regarding CTI messages to AES?' I am not yet able to determine if CM is not sending the messages or if AES is failing to process them and send them on. I appreciate any insight anyone may have, and thank you.
CM: 10.1
AES: 10.1
We have been running a recording application (formerly known as CallCopy) that utilizes DMCC for its recording channels and TSAPI to monitor the recorded stations for call events. We recently have stopped recording calls and, through our investigation, have determined that calls are not recording because the recorder is not receiving the TSAPI messages regarding call establish, call complete, call held, etc. The recorder is able to see specific TSAPI messages for Do Not Disturb and MWI and is able to register the monitors via TSAPI and the recording channels via DMCC.
I enabled TSAPI trace in the AES and the tsapi_trace.out logs indicate the same failure. AES is only sending heartbeats, do not disturb, and MWI messaging. To top the situation's oddity off, we interchanged our CM to a standby server and we properly recorded 10 calls over the course of the next hour, but nothing beyond that. During the 'working' time interval, still not all calls were recorded, but logs do verify that the appropriate TSAPI messages were being sent/received for the calls that did record.
With the background info stated, the main crux of my question is 'is it possible to see what CM is sending out regarding CTI messages to AES?' I am not yet able to determine if CM is not sending the messages or if AES is failing to process them and send them on. I appreciate any insight anyone may have, and thank you.