Skip to end of metadata
Go to start of metadata

Media Recorder Down Alert

Content

Alert: <ALERT_ERROR>
Service: <SERVICE_NAME>
Computer name: <COMPUTER_NAME>
Alert id: <ID>
Time: <TIME> (UTC)
Severity: <SEVERITY>

Description:
#DESCRIPTION#

Alert attributes:
#CUSTOM_ATTRIBUTES#

Cause

This alert is sent if the Verba Avaya DMCC/JTAPI Service can not connect to one of the Verba Media Recorder(s). The not reachable Media Recorder's IP address is mentioned in the alert email.

Resolution

Please note, that you need to restart the Avaya DMCC/JTAPI Service after this alert.

Before that, please check if the server machine (running the Verba Media Recorder role - which is provided by Verba Unified Call Recorder Service) is reachable. If not, contact your IT team.

If the server is reachable, please check if the Unified Call Recorder Service is running on that Server. If not, start that service and restart the Avaya DMCC/JTAPI Service as well.

If MediaRecUp alert is still not received, contact the support service and send the following log files from each Verba Server: Unified Call Recorder Service - unifiedrec.log. Verba Avaya DMCC/JTAPI Service - avaya_recorder.log.
Log files are available under "APPLICATION_FOLDER\log" (by default C:\Program Files (x86)\Verba\log) folder on each server.
 

  • No labels