I have error event monitoring setup on my Unity machine. Lately I've been receive four messages regularly, but I don't know how to fix them. Could someone point me in the right direction. The messages are
1."Event Type: Error
Event Source: CiscoUnity_AMISConv
Event Category: Network
Event ID: 130
Time: 12:30:16 PM
An incoming call transmitted the DTMF C tone, which signals the beginning of an AMIS call. However, Cisco Unity was not able to find the UAMIS_<Servername> mailbox, so the message could not be accepted. Recommended Action: If the system is not configured for AMIS and should not except AMIS calls, this message can be safely ignored. If the rogue AMIS calls continue, you can obtain caller ID and other information by enabling the micro traces Conv PhoneHandler 10 and MiuGeneral 14 in the Cisco Unity Diagnostic Tool, or you can work with your carrier to determine the source. If the system is configured for AMIS and should accept AMIS calls, make sure that you have created the UAMIS_<Servername> mailbox before sending and/or receiving any messages using AMIS Networking. Refer to your Networking in Cisco Unity Guide for more information on how to properly configure your Cisco Unity server to use AMIS Networking. Error code = 0x8000ffff 152"
2."Event Type: Error
Event Source: CiscoUnity_Miu
Event Category: Error
Event ID: 559
Time: 9:55:45 AM
Cisco Unity's telephony component has encountered a serious error.
A serious failure has occurred on port 4 while dropping a call. In some cases, further calls on this port will not be handled correctly.
Thread 0x000017A4 had a failure on port 4 in method CAvMiuLine::Drop()
DESCRIPTION: Drop() called lineDrop() 0 times with result E_MIU_TIMEOUT..
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...