Installation Standards for
Meridian Mail Enhanced Card Option
The purpose of this document is to put forth standards for use by the technician installing
Nortel Option 11 PBXs with Meridian Mail Enhanced Card Option voice mail systems. This document should serve as a guide to assist installers and database personal. It is not intended as a replacement for the installation
manuals shipped with the systems. In cases of conflict with the published installation
manual, the published manual takes precedent. It is the responsibility of the installer at
site to read all provided Technical Service Bulletins and/or other documentations that
Nortel provides to show updated installation information with each shipped system, in
other words RTFM.
The enhanced card option Meridian Mail (hereafter referred to as MM) is comprised of a full sized printed circuit board (PCB) to which a hard drive, and up to two daughter boards, are attached. A tape drive unit, used for initial program load and database backup is connected to the PCB by a provided cable.
Refer to this Installation Guide to install MM software from tape.
The main PCB provides for four (4) ports of MM service. Each additional daughter board provides an additional four (4) ports of MM service. The normal configuration for the Janus program will include twelve (12) ports. This is the maximum number of ports that can be installed on a card option MM. Additional cards cannot be installed in the PBX expansion cabinets.
MM ports are of two types:
- Full Service, which can be used for voice mail and auto attendant functions, and
- Basic Service, which can be used only for auto attendant service only.
The amount of storage provided will be between ten (10) and twenty four (24) hours.
The number and type of ports and the amount of storage time is determined at the time of install by the KeyCode. All installers should verify the KeyCode matches the configuration shown on the site LOM at the time of the switch inventory. Do Not wait until it is time to install the MM software to verify that a valid KeyCode exists.
MM Port Configurations
MM ports are programmed in the Option 11 PBX database as M2008 sets. The default TNs
for these ports should not be changed. The following table shows the relationship between
the physical MM ports and the TNs assigned in the PBX database.
|MM Port||Port Location||Option 11 TN|
|1||Main PCB||10 04|
|2||Main PCB||10 12|
|3||Main PCB||10 05|
|4||Main PCB||10 13|
|5||Top Daughter Board||10 00|
|6||Top Daughter Board||10 08|
|7||Top Daughter Board||10 01|
|8||Top Daughter Board||10 09|
|9||Bottom Daughter Board||10 02|
|10||Bottom Daughter Board||10 10|
|11||Bottom Daughter Board||10 03|
|12||Bottom Daughter Board||10 - 11|
The correct programming of the M2008 sets in the PBX database is shown in the Enhanced Card Option Installation and Maintenance Guide, and at the bottom of this document. Note: the number zero (0) should be used for the CLID entry on key 0.
Card option Meridian Mails will be equipped with both basic and full service ports (depending on Keycode). Basic and full service ports should not be programmed in consecutive MM port order. The main PCB and each of the daughter boards should have a mix of both full and basic ports to provide for maximum redundancy.
At least two ACD groups need to be programmed for voice mail and auto-attendant functions on the Option 11. It is recommended that the following numbering plan be used on all sites except where it causes conflicts with existing or new DID DN assignments. Both ACD groups are programmed as MCDNs according to Enhanced Card Option Installation and Maintenance Guide.
An example TN is shown here: ACD Programming
Full Service Ports - Voice Messaging: 5555
Full Service Ports - Express Messaging: 5590
Basic Service Ports - Auto Attendant: 5100
Basic Service Ports Prompt Maintenance 5199
For simplicitys sake the agent position id and SCN required for each M2008 should be
numbered consecutively according to the physical MM port. The following table should make
|MM Port||TN||Type*||ACD||Position ID||SCN (key 1)|
|12||10 - 11||Basic||5100||5012||5032|
*The number of basic vs. full service ports will be determined by the KeyCode and will
change from site to site.
Basic = Auto Attendant, Full = Voice Messaging
- Voice Service DNs (VSDN) associated with auto attendant services should use numbers in the range of 5101 to 5198 first.
- Voice Service Ids in Meridian Mail should be at least five digits long and begin with the VSDN primarily associated with the service.
Security and Voice Messaging Defaults
Recommended Meridian Mail caller security prohibitions are; NO outcalling, and NO direct inward access to system or mailbox programming. To achieve the first prohibition is realitively easy, set the on-switch permission list to only allow calls to exiting extensions and the attendant while denying calls to trunk and BARS/NARS access codes. Then make sure anywhere in the database where a permission list is requested, ONLY the On-Switch list is used. To insure that no direct access to system or mailbox programming is not allowed, do not use a DID extension number for any of the messaging services listed above.
Voice Security Menu Recommended defaults
|Function||MM Default||Pref. Default||Comments|
|Password Prefix||0||None||Make sure the 0 is deleted|
|Maximum invalid logon attempts per session||3||3|
|Maximum invalid logons attempts per mail box||9||9|
|Maximum Number of Days permitted between Password Changes||90||0||Setting at 0 allows passwords to last for life of mailbox|
|Minimum password length||4||4|
|External Logon||Enabled, Cannot Change|
Class of Service Defaults
Generally three different class of services are built; Basic, Exec, and Admin. Meridian
Mail has a default class of service named personal that a mailbox will be assigned to if
no other COS is chosen. It is very important that this class of service not be used as it
allows for off-site notification of messages and other features that may be a violation of
|Personal Verification Changeable by User||Yes||Yes||Yes|
|Voice Storage Limit (Minutes)||5||10||15|
|Maximum Message Length (MM:SS)||:30||:30||:30||*See Note Below|
|Dual Language Prompting||No||No||No|
|Network Broadcast Capability||No||No||Yes|
|Auto Deletion of Invalid PDL||Yes||Yes||Yes|
|Callers Notify of Busy Line||Yes||Yes||Yes|
|Prompt Played During Call Answering||Name||Name||Name||**See Note Below|
|Maximum Call Answering Message Length||:30||:30||:30||*See Note Below|
|Received Composed Messages||Yes||Yes||Yes|
|Receive External Messages||Yes||Yes||Yes|
|Message Waiting Indicating Options||Any||Any||Any|
|External Call-Sender Restrictions/Permission Codes||1(On Switch)||1(On Switch)||1(On Switch)|
|Maximum Read Message Retention (Days)||7||7||7|
|Retain Copy of Sent Messages||No||No||No|
|Delivery to non Users||No||No||No|
|Remote Notification Capability||No||No||No|
|Receive AMIS Messages||No||No||No|
|AMIS Open Network Restriction||1(On Switch)||1(On Switch)||1(On Switch)||Feature Not Used|
|External Dialing/Permission Codes||1(On Switch)||1(On Switch)||1(On Switch)||Feature Not Used|
|Custom Revert Restriction/Permission Codes||On Switch||On Switch||On Switch|
*Note: The time allotted for greetings and message length are multiplied by the number of mailboxes in the system, and can significantly impact the time available for other services. On a more common sense issue, greetings should consist of the mailbox owners name, a brief statement explaining that the call is being answered by voicemail and a request for the caller to leave their name, phone number and a brief reason for the call. In no case should greetings be longer than 30 seconds, even if the mailbox user is giving the greeting in two languages. Anyone who requests a longer time should be using an announcement service.
**Note: The Meridian Mail will only play the name if the personal verification is recorded by the user.
Meridian Mail systems from Release 13 have some added options not available before. These are shown in the table below:
|Service||Basic COS||Extended Storage||Admin||Comment|
|Unread Message Retention (Days)||35||35||35||Any message this old is not worth listening to!|
|Disable Message Reception||?||?||?||See Note Below|
Note: Release 13 gives the administrator the ability to disable a mailbox from recording messages if the mailbox storage is full, or if the user records a temporary access greeting. The user or administrator can also determine if the caller is transferred to a custom revert DN or an operator if a mailbox is not recording mailboxes. As these features are relatively new, a consensus on the implementation of them has not yet been formed and installers should their own best judgment, as dubious as it may be, when using these features.
Refer to MerMail ACD Programming for PBX programming examples.