The chapters in this section describe how to configure the base NuPoint Unified Messaging software after it has been installed on a server. The definitions on this page describe terms and concepts that are used in this guide:
The following applications are provided with your basic NuPoint UM server. You can configure these applications to provide custom message-taking, outdialing, and Message Waiting Indication. Each application requires its own line group. (Note: NP Call Director and NP Receptionist are the exception - these two applications can share a line group with the NuPoint Voice application.)
NuPoint UM Voice Application: the basic business application, used for message-taking and retrieval.
Pager Application: used for paging, but also for a number of other functions that require outdialing.
Message Waiting Application: used when an integration does not handle message waiting indicators itself.
Modifiers are characteristics that are common to all applications. You control the behavior of the application by configuring its modifiers. The most common modifiers are listed here:
Line Groups: A line group is a set of one or more incoming telephone lines, which come into line ports on the server hardware. Each application you use must be assigned its own line group (except for NuPoint Receptionist and Call Director, which can both work in the same line group as the NuPoint Voice application. Also, any operations involving outdialing can use the same line group assigned to the Pager application.) Most of the modifications you make to an application are made to its line group. See About Line Groups for more information.
Dialing Plan: To configure each application, you must define its dialing plan, which is the structure of how the mailboxes are numbered. Related features include which key a user presses to speak to a system attendant, or to use call placement. See About Dialing Plans for more information.
Day/Night Hours: This feature of the NuPoint Voice application lets you set the work schedule: both office hours and which days are handled as weekends. This also handles certain situations such as a user wishing to speak to a system attendant.
Mailboxes: Every user of the server needs a mailbox, and all applications require mailboxes. The administrator’s mailbox and attendant’s mailbox are special mailboxes that interact with applications; along with other special mailboxes like tree, rotational, and broadcast, they are discussed in the Mailboxes section. Mailbox features, such as Distribution Lists, receipts, and greetings are also discussed in that section.
Class of Service:
Features Class of Service (FCOS): a group of features applied to each mailbox that allow users to perform functions or control how the server can be used. See Features Class of Service.
Limits Class of Service (LCOS): a group of limitations on each user, such as length and number of messages. LCOSs also affect how some optional features work. One LCOS is assigned to each mailbox. These are explained in Other Classes of Service.
Group Class of Service (GCOS): determines which users can send messages or respond to messages from other users. There are two kinds of GCOSs, affinity and bit-mapped. One GCOS is assigned to each mailbox. These are explained in the Other Classes of Service.
Network Class of Service (NCOS): controls users’ network access and is a part of the NP Net Digital Network optional feature. More NCOS information is contained in the NP Net chapter of the Optional Features section.
Restriction Class of Service (RCOS): is an element of NPA/NXX call screening that restricts mailbox outdials to certain area codes or to certain prefixes within an area code. One RCOS is assigned to each mailbox. These are explained in the Other Classes of Service.
Tenant Class of Service (TCOS): used with the ESMDI “Multi-Tenant” application, to govern mailbox interaction between user communities. For more information about ESMDI integrations, see the Optional Integrations Guide available at Mitel OnLine.