Mitel Voice Processing Solutions Instructions Manual

							I 
I 
) NCOS Number 
Cl 
/ Assign to Mailboxes: 
NCOS Name 
l 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
I 
cl 001 Enable GCOS check across network 
r-l 002 Allow user to make network messages 
cl 003 Allow user to make urgent network messages 
q 004 Allow user to give network messages - 
G 005 Allow user to give urgent network messages 
G ‘006 Allow user to answer ne&ork messages 
cl 007 Allow user to answer urgent network messages 
El 008 Automatic receipts on network messages 
c! 009 Say “Remote message” when playing network messages 
G 010 Allow user to make fax message over the network 
G 011 Allow user to give fax message over the network 
q 012 Allow user to answer fax message over the network  
						

							Page 1 of 1 
Release 6.OA 
Task 
Procedure 
Configure a Network Class of Service 
. . . . . . . . . . . . . ..*................................. 
cl? 5730  
						

							Configure a Network Class of Service (NCOS) 
Page 1 of 2 
VoiceMemo Release 6OA and later 
Use this procedure to create or modify an NCOS by adding and deleting network 
messaging features. 
Reference 
1. Reach the Network Class of Service Menu. (This choice is not illustrated on this 
menu map, but it is in the same location as the other Classes of Service.) 
2. Select the NCOS that you want to create or modify. 
SeLkt: (C) Current NCOS 
Prompt: NCOS to modify: 
Response: The number (l-64) of the NCOS that you want to create or modify. 
3. Name the NCOS. 
Select: (N) Name NCOS 
Prompt: Enter NCOS name (O-15 characters): 
Response: A descriptive name for the NCOS, possibly one that describes the 
NCOS user group. 
4. If desired, view the network messaging features that you can add to an NCOS. 
Select: (H) Help NCOS 
Prompt: :Eys DESCRIPTION 
Enable GCOS check across network. 
002 Allow user to make network messages. 003 Allow user to make urgent network msgs. 004 Allow user to give network messages. 
005 Allow user to give urgent network msgs. 
006 Allow user to answer network messages. 007 Allow user to answer network msgs (urg) 008 Automatic receipts on network msgs. 
009 
Say Remote message when playing network msgs. 
010 Alllow user to make fax message over the network. 
011 Allow user to give fax messa- over the network. 
012 Allow user to answer fax msg bver the network. 
5. Add features to the NCOS. 
Select: (A) Add Features 
Prompt: Feature to add = 
Response: The numbers (1-12) of the NCOS features that you want to add. You 
can enter an individual feature number, a comma-separated list, or a 
range, such as 2-4. 
6. If desired, delete features from the NCOS. 
Sekct: (D) Delete Features 
Prompt: 
Feature to delete = 
Response: The numbers (1-12) of the NCOS features that you want to delete. 
You can enter an individual feature number, a comma-separated list, or 
a range, such as 2-4. Menu Map 
11 
Doe. Rev. A  
						

							a? 5730 
Page 2 of 2 
VoiceMemo Release 6.OA and later 
steb 
7. View the NCOS to verify your work. 
Select: (R) Report NCOS 
prompt: NCOS to report = 
Response: The number (l-64) of the NCOS that you just created or modified. 
The system displays the NCOS number and name, and the features enabled for the 
NCOS users. 
8. If necessary, make further changes to the NCOS by adding or deleting features. 
When finished, exit to the System Configuration Menu to save your work. 
Dot. Rev. A 
Reference  
						

							This chapter describes MESA-Net mailbox maintenance: creating network 
mailboxes, adding network mailboxes to distribution lists, and working with 
broadcast mailboxes over the network. The information here is an addition to the 
mailbox information in the VoiceMemo Reference and Conj@ration Manual. 
There is very little difference between a regular mailbox and a network mailbox. A 
regular mailbox becomes a network mailbox when you associate it with a network 
class of service (NCOS) that allows messaging across the network. Network Class of 
Service is described in Chapter 8 of this manual. Follow the “Create a Mailbox” 
procedure in the VGceMemo Reference and Conjgurazion Manual to create network 
mailboxes. 
Unless you specify otherwise, all mailboxes are assigned NCOS 1. To make 
administration easier, you should configure NCOS 1 to match the needs of the 
largest group of network users. 
If you enabled GCOS checking across the network (NCOS feature OOl), you must 
pay special attention to the GCOS that you assign to each mailbox so that the 
mailbox owner can communicate with the appropriate people. 
in xisying ailboxes for 
When you add MESA-Net software toTSeries 6 server that is already processing 
calls, the default NCOS that was assigned to all mailboxes becomes effective. If you 
want to change mailbox NCOS assignments, follow the “Modify a Mailbox” 
procedure in the VoiceMemo Reference and Con.guration Manual to change the 
NCOS on one mailbox, or a range of mailboxes, if necessary. 
If you maintain any distribution lists from the console, such as system-level 
distribution lists, you can add remote mailboxes to those lists. You add remote 
mailboxes from the console using the same letters as the dialing plan: N and I?. 
When adding members to a distribution list, enter N and a remote mailbox number 
(just like a user would enter the number when addressing a message), or I? and a 
prefer and mailbox number. 
T-1  
						

							Configuring Network Mailboxes 
Any remote mailbox entries that you put in distrubution lists must match the dialing 
plan and Node Access Table configuration. 
adcasting ork 
A Broadcast mailbox (mailboxes with FCOS bit 122) functions differently when 
broadcasting to remote mailboxes: 
e FCOS bit 123, which directs the system to announce the broadcast mailbox 
number/name to the recipient, rather than the sender’s mailbox number/name, 
does not work when the message is sent to a remote node. 
Messages made for a broadcast mailbox are automatically sent to every member 
of distribution list 01 of that mailbox. Local and remote mailboxes can be 
included in this distribution list. Distribution lists are limited to 200 members, 
and each local or remote mailbox in the list counts toward that limit. 
The same system will not perform a “double broadcast,” that is, if one of the 
child mailboxes is also a broadcast mailbox, the message will not be sent to the 
mailboxes in its distribution list 0 1. 
If a remote broadcast mailbox is included in distribution list 01 of the local 
broadcast mailbox, the message will be broadcast to the remote mailbox’s 
distribution list 01, since each broadcast is done by a different system. 
essage ueues and the Mailbox 
The mailbox Limits Class of Service limits the number of messages that can be stored 
in a mailbox. The absolute maximum-number of messages allowed is 73 (note that 
attachments to a message count toward this total). Network messages that are 
queued but have not been sent count toward this limit, and so do message receipts. 
You must take these additional demands on mailbox message storage into account 
when programming network queue configurations and when assigning Limits 
Classes of Service to network mailboxes. 
Y-2  
						

							This chapter describes two similar areas of MESA-Net administration: mailbox 
billing for network messaging and system reports on MESA-Net programming and 
activity. 
illi 
This section describes the mailbox billing counters and the parts of the standard 
billing report that reflect MESA-Net usage. Refer to the VoiceMemo Reference 
md 
Coq’?g~ration Man&for instruction on adjusting billing rates and running the 
billing report. 
essage Counters 
Network message counters tally the number of messages sent by a mailbox to remote 
nodes. Different counters measure the total number of network messages sent, the 
number of nodes to which a message is sent, number of remote recipients to which a 
message is sent, and the number of network messages received by the mailbox during 
the billing period. Separate totals are kept for urgent and batch messages that meet 
each of these criteria. 
messages sent 
This counter keeps track of the total number of batch messages recorded for remote 
mailboxes during the billing period. A “Give + comments” message is counted as 
one mfssage, as is an original message that has an answer or answers attached. 
Messages are billed on a “per message”lbasis, not a “per recipient” basis; when a batch 
message is made to a distribution list, or by using the “make multiple” feature, it 
counts as one network message sent. 
rk urgent messuges sent 
This counter keeps track of the total number of urgent messages sent to remote 
nodes by the mailbox during the billing period. A “Give + comments” message is 
counted as one message, as is an original message that has an answer or answers 
attached. 
Messages are billed on a “per message” basis, not a “per recipient” basis; when an 
urgent message is made to a distribution list, or by using the “make multiple” 
feature, it counts as one urgent network message sent. 
10-l