Mitel Voice Processing Solutions Instructions Manual

							Cl?5729 
Page 2 of 5 
Release 6.OA and later 
Step 
7. Set the maximum number of message minutes that can accumulate in a queue 
before the queue is sent. 
Select: (T) Total Message Minutes 
Prompt: 
Total Message Minutes [5J: 
Response: The number of minutes that the total messages add up to before the 
queue is sent.. 
8. Select X to exit. 
9. Repeat steps 3 through 8 for the other queue (batch or urgent). 
ED Set Network Queue Time 
10. Reach the Network Queue Start/Stop Times menu. 
11. Select to modify either the batch queue (B) or the urgent queue (U). 
12. If you do not want any time limits on when the local node can originate 
MESA-Net connections during the week, set the weekday window to always open. 
Select: (U) Always Open Weekday Window 
P7-0~7pt W-ins7 : This will reset the WEEKDAY BATCH start 
and stop times so that the window will always be 
open to transmit messages: 
Start time = 12:00 am, 
Stop Gme = Never 
To define specific times wh-messages can be 
transmitted and when 
messages will only be queued, 
set up desired start and stop times using the menu 
choices. 
Reset times to always open? (Y/N): 
Response: Y to set the window to always open; N to leave the times unchanged. Reference  
						

							Cl? 5729 
Page 3 of 5 
Release 6.OA and later 
13. If you do not want any time limits on when the local node can originate 
MESA-Net connections on the weekends, set the weekend window to always 
open. 
Select: 
or) Always Open Weekend 
Window 
Pr0mpt: Warning : This will reset the WEEKEND BATCH start 
and stop times so that the window will always be 
open to transmit messages: 
Start time = 12:oo am, 
Stop time = Never 
To define specific times when messages can be 
transmitted and when 
messages will only be queued, 
set up desired start and stop times using the menu 
choices. 
Reset times to always open? (Y/N): 
Response: Y to set the window to always open; N to leave the times unchanged. 
14. Set the weekday start time. 
Select: 
(A) Weekday Start Time [12:00 am] 
Prompt: 
Weekday Start Time [12:00 am]:? 
Response: The time that MESA-Net starts sending the network queue on 
weekdays. The time must between 01 00 am or pm and 
12 00 am-or 
pm in the format hh mm am or hh mm pm. 
5. Set the weekday stop time. 
Select: (D) Weekday Stop Time [Never] 
Prompt: 
Weekday Stop Time [Never]:? T 
Response: The time that MESA-Net stops sending the network queue on 
weekdays. The time must between 
01 00 am or pm and 12 00 am or 
pm in the format hh mm am or hh mm pm. 
6. Set the weekend start time. 
Select: 
(E) Weekend Start Time [ l2:OO am] 
Prompt: 
Weekend Start Time [12:00 am]:? 
Response: The time that MESA-Net starts sending the network queue on 
weekends. The time must between 
01 00 am or pm and 12 00 am or 
pm in the format hh mm am or hh mm pm. Reference  
						

							Cl? 5729 
Page 4 of 5 
Release G.OA and later 
Step 
17. Set the weekend stop time. 
Select: (I) Weekend Stop Time [Never] 
prompt: Weekend Stop Time [Never]:? 
Response: The time that MESA-Net stops sending the network queue on 
weekends. The time must between 
01 00 am or pm and 12 00 am or 
pm in the format hh mm am or hh mm pm. 
18. Select X to exit. 
19. Repeat steps 11 through 
18 for the other queue (batch or urgent). 
CD Set Network Limits 
20. Reach the Network Queue Limits menu. 
21. If desired, set the parameters to their default values. Otherwise, proceed to step 
22. 
Select: (W) Set to Default Values 
Prompt: W==ning : 
This command will set the following 
default values: 
Message Block Use threshold: 80 percent 
Maximum Call Setup Tries: 50 
Call Setup Retry Interval to 10 minutes 
Maximum Session Length to No Limit. 
Reset jlimits to default values (Y/N)? 
Response: Y to set the limits to the defaults; N to leave them unchanged. 
22. Set the message block use threshold 
Select: (T) Message Block Use Threshold (percent) 
prompt: Message Block Use Threshold (percent)?: 
Response: The number that indicates a percentage of buffers used for messages. 
When this percentage is reached, MESA-Net will send the queue with 
the greatest number of message. MESA-Net continues to send queues 
until the message storage falls below the threshold. This number can 
be from 80 to 
100. ., 
Reference  
						

							CJ? 5729 
Page 5 of 5 
Release 6.OA and later 
Step 
23. Set the maximum of times that MESA-Net will try to set up a connection. 
Select: 
(U) Maximum Call Setup Tries 
Prompt 
Maximum Call Setup Tries? 
Response: 
The number that indicates the number of times MESA-Net will try to 
send a network queue. Each try consists of three call setup attempts. 
24. Set the number of seconds that MESA-Net waits before trying to set up a 
connection after an attempt has failed. 
Select: (V) Call Setup Retry Interval (minutes) 
.I)rompt: Call Setup Retry Interval (minutes)?: 
Response: 
The number of minutes  between attempts to set up a 
connection to a remote node.  
						

							rii 
The VoiceMemo software allows you to customize your system to meet the specific 
needs of your site. You do this through Classes of Service (COS), which is a way of 
differentiating what privileges and abilities different mailbox owners have. 
MESA-Net messaging uses the Network Class of Service (NCOS) to control network 
privileges. NCOS settings control whether a mailbox owner can send, give, or 
answer messages over the network. This chapter describes the NCOS features. 
e res 
MESA-Net provides twelve different NCOS features. You can combine these 
features in any way to create an NCOS that provides network privileges for a specific 
user group. You can configure up to 64 NCOS’s. This section explains each NCOS 
feature and provides you with a worksheet to use for NCOS planning. 
S check across network 
A Group Class of Service (GCOS) must be assigned to every VoiceMemo mailbox. 
A mailbox cannot make, give, or answer messages to a mailbox outside of its group. 
If a mailbox’s NCOS includes feature bit 001, the sending node transmits the 
mailbox’s GCOS number with any message that the mailbox sends to a remote 
mailbox. The receiving node delivers the message if either of two conditions is met: 
& 
The GCOS numbers of the sending and receiving mailboxes are the 
IL 
same. 
e 
The GCOS on the receiving node that has the same number as the 
GCOS of the sending mailbox allows communication with the recipient 
mailbox. 
If neither condition is true, the remote node rejects the message. The sender receives 
a receipt saying that “remote mailbox XXX cannot receive messages from your 
group.” (Also see NCOS Feature bit 008 for the circumstances under which receipts 
are generated.) 
ote: The remote node does not receive any information about the 
sender’s Group Class of Service other than the GCOS number. 
For the GCOS check to work consistently, all GCOS’s that are 
S-1  
						

							Configuring Classes of Service for Networking 
assigned to mailboxes that have network message privileges must 
have exactly the same group definitions on all nodes. 
If the Network Class of Service does not include feature 
001, no GCOS checking 
will be done, that is. a user can send messages to any remote user, regardless of the 
recipient’s Group Class of Service. (Local node interactions are still controlled by 
the GCOS.) 
02 Allow user to make network messages 
This feature allows users, while logged into their mailboxes, to press “M” to Make a 
message for a mailbox on another MESA-Net node. This feature is required to make 
both batch and urgent messages for remote mailboxes. 
ser to e urgent ne 
Feature 003 allows a user to request urgent delivery for messages that are made to 
remote mailboxes. Feature 002 is required for this feature to work. 
004 Allow user to give network messages 
This feature allows users to press G to Give a message to a mailbox on another 
MESA-Net node. This feature is required to give both batch and urgent messages to 
remote mailboxes. 
llow user to give urgent network messages 
Feature 005 allows a user to request urgent delivery for messages that are given to 
remote mailboxes. Feature 004 is required for this feature to work. 
06 Allow user ty answer network messages 
This feature allows a user, after playi%g a message from a mailbox on another MESA- 
Net node, to press A to answer that message. This feature is required to answer both 
batch and urgent messages from remote mailboxes. 
007 Allow user to answer urgent network messages 
This feature allows a user to press A to answer urgent messages from users on remote 
nodes. Feature 006 is required for this feature to work. 
8 Automatic receipts on network messages 
This feature causes MESA-Net to generate a receipt every time a remote message is 
made, given, or answered. 
Receipts are generated under most conditions when a message to a remote node 
cannot be delivered. The only time a user will not be notified that a message to a 
8-2  
						

							Configuring Cla.sses of Service for Networking 
remote mailbox was not delivered is if the message was made for more than one 
mailbox (either through a distribution list or through the “make multiple” feature), 
and at least one other mailbox on the same node got the message. 
Automatic receipts ensure that the sender is always notified of an undeliverable 
message; however, system users who make many messages often find that the 
automatic receipts feature is more annoying than helpful. An alternative is to give 
mailboxes an FCOS that allows the user to request receipts, then instruct the users to 
request receipts any time messages are made to multiple mailboxes on the same 
remote node. 
emote mailb rk messages 
The feature adds the words “remote message” when the message header is played by 
the recipient. In other words, network messages are announced in the form of “8:45 
am, remote message from Jane Jones.” 
This feature eliminates potential confusion when received messages seem to be out of 
order. When a user plays a remote message, the system announces the time that the 
remote message was recorded, converted to the local time of the recipient, but the 
message appears in the user’s unplayed queue in the order in which it was received. 
When a remote message is delayed in a queue on the sending node, the time stamp 
will be out of order with other messages in the unplayed queue, and users may 
become confused because they do not realize that the message was sent from a 
remote node. Adding this NCOS feature distinguishes network messages, which 
may be delayed due to queue thresholds, from local messages. - 
If senders do not record a name in their mailboxes, remote message introductions 
announce the sending mailbox number. 
llow user to make fax message ove the network 
This feature allows a user to make a fax message over the network. 
11 llow user to give fax message over the network 
This feature allows a user to give a fax message to a mailbox on a remote network. 
user to answer fax message over the ne ork 
This feature allows a user to answer a fax message to a mailbox on a remote network. 
in 
VoiceMemo release 6.0 introduced new hardware and the ability to provide different 
levels of speech quality by using different compression rates for message storage. 
8-3  
						

							Configuring Classes of Service for Networking 
Pre-6.0 hardware and software only support a single compression rate - 18.3 Kbps - 
and cannot accept messages that were recorded with a different compression rate. 
If your MESA-Net network includes AIP systems that have pre-6.0 hardware and 
software and you want all nodes to be able to exchange messages, you must set the 
compression rate on all 6.0 systems to 18.3 Kbps. You must use this setting for all 
messages, names, and greetings. You use feature bits in FCOSs to set the 
compression rates for each type of recording. See the FCOS chapter in the 
VoiceMemo 
Reference and Configuration Mand for more information. 
uring Networ ervice 
The VoiceMemo software has a single default Network Class of Service, NCOS 1 
NCOS 1 has all NCOS features except 00 1, Enable GCOS check across network 
and 008, Automatic receipts on network messages. 
You can create up to 64 NCOSs, each with a different combination of features, to 
meet the needs of users on the local node. To create a new NCOS, you simply 
identify an NCOS number, give it a name, and add or delete NCOS features. You 
must then assign the NCOS to those mailboxes that you want to have that set of 
network privileges. 
Use the Network Class of Service Worksheet to help plan your NCOSs. 
8-4  
						

							Configuring Classes of Service for Networking 
I 
I 
1 NCOS Number 3 
II NCOS Name Basic Network Service 
; Assign to Mailboxes: 
’ 342 345 346 350 
--------- 
+iEL-___------- 416 
I 
ppp_______________---- 
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 
I 
I 
I 
I 
I 
q 001 Enable GCOS check across network 
r-l X 002 Allow user to make network messages 
r-l X 003 Allow user to make urgent network messages - 
q X 004 Allow user to give network messages 
q X 005 Allow user to give urgent network messages - 
q X 006 Allow user to answer network messages 
I-’ X bO7 Allow user to answer ursnt network messages 
r-l 008 Automatic receipts on network messages 
cl 009 Say “Remote message” when playing network messages 
q 010 Allow user to make fax message over the network 
13 011 Allow user to give fax message over the network 
i-l 012 Allow user to answer fax message over the network 
8-5