Amethyst Voice Recorder Errors

Amethyst - Advance Call Recording Solution(Trunk,Extension, VoIP and clientside) with Agent Quality Management and 3rd party integration SDK

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

Amethyst Voice Recorder Errors

Postby QMetrix » Fri Oct 06, 2017 10:39 am

Hi

I've been getting these error messages from the Amethyst Recorder -

2017-06-09 12:05:37 Amethyst has no communication with the cardserver / CRE at (172.17.118.245)

This has happened:

9 June 12:05PM and 4:24PM
1 July 12:02AM
1 Aug 12:03AM
23 Aug 3:41AM
31 Aug 12:52AM and 1:09AM
1 Sep 12:03AM
11 Sep 11:29AM and 2:11PM
27 Sep 1:51PM and 9:00PM
28 Sep 9:42PM and 9:58PM
1 Oct 12:03AM and 9:47PM
3 Oct 11:04PM

Then we also get a different error message:

Recording /mnt/drive2/exclusive/20170927/a170927-0/mnt/drive2/exclusive/20170927/a170927-0004f2 specified in /opt/amethyst/bin/nfs/change.log-aaaa was not found

Recording /mnt/drive2/exclusive/20170927/a170927-0/mnt/drive2/exclusive/20170927/a170927-0004f2 specified in /opt/amethyst/bin/nfs/change.log-1 was not found

This has happened:

27 Sep 9:41PM
29 Sep 9:44PM
2 Oct 9:37PM
3 Oct 9:38PM
4 Oct 9:44PM
5 Oct 9:45PM

Is there an issue with our Recorder and if so, how do we fix it.

Regards
Thabo
QMetrix
 
Posts: 2
Joined: Fri Oct 06, 2017 10:06 am

Re: Amethyst Voice Recorder Errors

Postby QMetrix » Sat Oct 07, 2017 7:06 am

hi support

any feedback on this?
QMetrix
 
Posts: 2
Joined: Fri Oct 06, 2017 10:06 am

Re: Amethyst Voice Recorder Errors

Postby Belinda Frick » Thu Oct 12, 2017 2:01 pm

These are 2 different events:

  1. NO COMMUNICATION:

    AMETHYST will do a check from time to time to see if it can communicate with the recorders:

    If it cannot it will create the NO COMMUNICATION event and specify the IP for which it was created.

    The problem is either:
    • the recording server is down
    • the recording software is down
    • there is a network issue between AMETHYST and the recording server.

    It can also be at if at the time of the check the following happens:
    • network lost which recovered quickly, switch rebooted, etc.
    • software restarted

    The first critical e-mail sent is a warning.
    If it repeats at the same time each day, then it did not recover.
    If it stops sending, the specific incident was resolved.

    If the event starts again, but for a different time - then it is a new occurrence.

    The software that handles this check is the amtserver and on remote recorders the Remote AMETHYST Server. If this software restarts, it can also generate the event on startup.

    If you have a Windows recording server, check the network up time and/or if Windows update was done as it will restart the server. You can also check the Windows event logs around the time of the critical e-mails

    If recordings are taking place, then all are in order.

  2. ARCHIVE EVENTS:

    These errors are for recordings not found while archiving.

    Please load the attached file via AMETHYST Webadmin
    fix-archive-missing-recordings.rar
    NOTE: Unrar to extract .amt file
You do not have the required permissions to view the files attached to this post.
Belinda Frick
 
Posts: 3808
Joined: Fri Nov 12, 2010 4:25 pm


Return to Amethyst

Who is online

Users browsing this forum: No registered users and 1 guest

cron