tdaugirdas
Technical User
I recently upgraded a Magix Messaging R2.5 module to Release 4.0 -
and I have several questions.
#1. After the upgrade, in reviewing the "Critical Event" report - I saw a whole bunch of "Error Bad Mailbox Data 8388608 -1 0" (When the firmware upgrade is in process, the display indicates that 204 mailboxes are being converted from type "0" to type "1"). Does anyone know what these errors mean? Is there a way to reset the "Critical Event" report to erase meaningless and/or outdated errors?
#2. Is there a way to reset the Messaging mopdule to factory specs - after the upgrade? 989-clear and 989-reset no longer appear to default the module completely (changing admin password, resetting LAN connections, etc.). Does this have to be done manually? Is there an equivalent command to the "init" command on older voice mails that reinitializes and defaults all parameters? Is there a different command for Release 4.0?
I would appreciate hearing from anyone who has upgraded their Messging module to Release 4.0 - and maybe experienced similar issues. Thanks...Tom
and I have several questions.
#1. After the upgrade, in reviewing the "Critical Event" report - I saw a whole bunch of "Error Bad Mailbox Data 8388608 -1 0" (When the firmware upgrade is in process, the display indicates that 204 mailboxes are being converted from type "0" to type "1"). Does anyone know what these errors mean? Is there a way to reset the "Critical Event" report to erase meaningless and/or outdated errors?
#2. Is there a way to reset the Messaging mopdule to factory specs - after the upgrade? 989-clear and 989-reset no longer appear to default the module completely (changing admin password, resetting LAN connections, etc.). Does this have to be done manually? Is there an equivalent command to the "init" command on older voice mails that reinitializes and defaults all parameters? Is there a different command for Release 4.0?
I would appreciate hearing from anyone who has upgraded their Messging module to Release 4.0 - and maybe experienced similar issues. Thanks...Tom