Specifications

Chapter 6: Programming
Database Conversion Process
Mitel
®
5000 Installation Manual – Issue 3.0, October 2008 Page 6-33
• Voice Mail: If the Voice Mail type was EVMC, it will be translated to BVM. This requires no
database changes. The following checks and changes occur only when the Voice Mail
type was EVMC.
o If the E-mail system type is anything other than None, it is automatically changed to
None. This is necessary because MAPI and VIM are not supported with BVM, and
SMTP is supported only when a hostname is defined—since the conversion is
defaulting the IP Settings, a hostname will not be defined. These settings are unlikely,
because they are not supported with EVMC. However, since they can be programmed
in the Inter-Tel Axxess database, they will be cleared if detected.
o The Voice Mail Alternate Tone Detection Flag is checked. If set, it is cleared, as it is not
supported for BVM in the Mitel 5000.
o All local mailboxes are checked to see if any have Unified Messaging set as the E-mail
Gateway type. If so, this is cleared (set to None) because this is also not supported for
BVM in the Mitel 5000.
If any of the changes just described are made to the database, each is recorded in the log
file, with indication of the old value and the new value. For each local mailbox changed,
the mailbox extension is included on the logged record.
All local mailboxes are set to uninitialized, and a warning is recorded in the log file
indicating that all mailboxes will need to be reinitialized and all custom prompts re-
recorded.
• Meta Database: The meta database needs to be adjusted for the destination Mitel 5000
platform. Default values for the destination Mitel 5000 platform are compared to the
current values in the meta database, from the original Inter-Tel Axxess system. If any
value is lower than the default limit, it is set to the default limit. If any value is higher, the
value is not changed, but a warning is added to the log file showing the name of the value,
the current value, and the default limit for the destination system.
After all meta database values have been examined and updated as needed, and any
default limits were found to be exceeded, a message appears alerting you that one or
more meta database limits are exceeded. Review these numbers and the associated
programming. These warnings are recorded in the log file.
NOTICE
Do not change any Meta Database values unless instructed to do so by Mitel Technical
Support. These values should not be changed beyond any necessary changes made by
the conversion utility.