![]()
Mutare stayed with us every step of the way with their quick response to our questions and thorough training for those of us operating the system."
Eugene Conlogue
Millinocket, Maine
Mutare Software continually updates its technical FAQs for our customers and business partners.
Use the search tool below to find the answer to your question.
You may also want to check out our Technical Documents page, which contains installation checklists, technical product overviews, specifications, and Avaya Application Notes.
If you do not find the answer you are looking for, email the Mutare support staff.
Displaying the 5 most recent FAQs.
This error occurs only in CMM systems. Only one IMAP4 session can be enabled at a time. The mailbox is in use from the telephone user interface (TUI) and EVM cannot access the mailbox. The application will try again the next cycle.
Last Updated: 5/5/2010 12:30:00 PM Tags: CMM, EVM
This error can occur with EVM on Avaya CMM systems. This error occurs when the MsgCount drops on a mailbox. Messages are queued for deletion, but are cached. The MsgCount remains at the previous value, even though messages are in the process or have been deleted. EVM attempts to grab the message headers for messages that are not there.
This error in the muLog file looks like: CheckIMAP4:XXXX - 3:EVM:Object variable or With block variable not set.
Last Updated: 11/24/2009 4:09:31 PM Tags: EVM, CMM
This happens in Message Mirror. This means that the destination mailbox is not allowing messages to be added. Usually occurs when the destination mailbox is a bulletin board mailbox, as the COS does not allow messages to be appended. It is best to omit these mailboxes from Message Mirror.
Last Updated: 11/5/2009 3:06:00 PM Tags: Message Mirror
Occurs in Message Mirror. This happens on the backup when Message Mirror tries to delete (expunge) messages via IMAP4. In most cases, it simply means that the MSS took too long to report back the deletion of messages to the Message Mirror application. Things should be back to normal on the next cycle. If this recurs for multiple cycles, it could mean that a corrupt message has appeared on the backup Modular Messaging system. Deleting the offending message on the backup can resolve this issue.
Last Updated: 5/18/2009 3:33:52 PM Tags: Message Mirror
This can happen during the MMLDAPUpdate process in Message Mirror when a mailbox creation on the backup is being attempted. The attempt fails because the NumericAddress already exists in the voicemail network or domain. XXXXXXXX is the mailbox number. This can happen when Message Networking is installed at the site.
Last Updated: 3/4/2009 5:54:40 PM Tags: Message Mirror