Mitel Voice Processing Solutions Instructions Manual

							Network Billing and Reports 
umber of network nodes sent to 
The Make Multiple and Broadcast features permit users to send a single message to 
more than one node. This counter allows the administrator to charge separately for 
each node to which a batch message is sent, since each destination node requires a 
separate transmission. The number of recipient mailboxes on each node does not 
matter. For example, a single message that is broadcast to five mailboxes on three 
different nodes increments this counter by 3. 
A “Give + comments” message is equivalent to the single message in the previous 
paragraph, as is a “Give + message with an answer or answers attached.” 
umber of network nodes sent urgent to 
The Make Multiple and Broadcast features enable users to send a single message to 
more than one node. This counter allows the administrator to charge separately for 
each node to which an urgent message is sent, since each destination node requires a 
separate transmission. Th e number of recipient mailboxes on each node does not 
matter. For example, a single message that is marked urgent, then sent to five 
mailboxes on three different nodes increments this counter by three. 
Number of network recipients sent to 
The Make Multiple and Broadcast features permit users to send a single message to 
more than one remote mailbox. This counter allows the administrator to charge 
separately for each remote mailbox to which a batch message is sent. The number of 
nodes is irrelevant. For example, if a single batch message is sent to five mailboxes 
- 
on three different nodes, this counter is incremented by 5. 
Number of network recipients sent urgent to 
The Make Multiple and Broadcast features enable users to send a single message to 
mork than one remote mailbox. This counter allows the administrator to charge 
separately for each For example, a sin;le message that is marked urgent, then sent to 
five mailboxes on three different nodes increments this counter by 5. 
Network messages received 
This counter keeps track of the number of batch messages received from 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. 
Ne rk urgent messages received 
This counter keeps track of the number of urgent messages received from remote 
nodes by the mailbox during the billing period. A “Give + comments” message is 
counted as one message, as is a original message that has an answer or answers 
attached. 
1 o-2  
						

							Network Billing and Reports 
Message length counters keep track of the total amount of recorded speech that fits 
certain criteria. Every mailbox has these counters, and all counters are incremented 
in tenths of a minute. 
Among the reasons why an administrator would set rates based on message lengths 
are (1) messages use up disk storage when they wait in the queue, and (2) the longer 
the message, the longer the transmit time. While the cost of transmitting a single two 
minute message may not be significantly higher than the cost of transmitting a single 
one minute message, the cost differences can be substantial when they are multiplied 
over many messages. 
There are separate message length counters for Batch and Urgent messages. Batch 
messages usually stay in the queue longer than urgent messages, but urgent messages 
may be transmitted during time periods when transmission charges are highest. 
Take these factors into account when setting rates. 
essage length #or network messages sent 
The counter tallies the total amount of recorded speech in all batch messages sent to 
remote nodes by the mailbox during the current billing period. 
th for network messages sent urgent 
The counter tallies the total amount of recorded speech in all urgent messages sent to 
remote nodes by the mailbox during the current billing period- 
essage length for net-work messages received 
This counter totals the amount of recorded speech in all batch messages received 
from rfmote nodes during the current billing period. 
-0t 
Message length for urgent network messages received 
This counter totals the amount of recorded speech in all urgent messages received 
from remote nodes during the current billing period. 
essage length for number of network nodes sent 
MESA-Net multiplies the amount of recorded speech in each batch message by the 
number of remote nodes to which the mailbox sends the message. The results are 
recorded by this counter. 
ork nodes sent urgent 
MESA-Net multiplies the amount of recorded speech in each urgent message by the 
number of remote nodes to which the mailbox sends the message. The results are 
recorded by this counter. The number of recipients on each node does not count 
here. 
10-3  
						

							NetworkBillingand Reports 
essage length for number of remote recipients sent 
MESA-Net multiplies the amount of recorded speech in each batch message by the 
number of remote mailboxes to which the mailbox sends the message. The results 
are recorded by this counter. The number of different remote nodes is irrelevant 
here; two messages for the same remote node are equivalent to one message for two 
different remote nodes. 
Message length for number of remote recipients sent urgent 
MESA-Net multiplies the amount of recorded speech in each urgent message by the 
number of remote mailboxes to which the mailbox sends the message. The results 
are recorded by this counter. The number of different remote nodes is irrelevant 
here; two messages for the same remote node are equivalent to one message for two 
different remote nodes. 
Network Billing Report Entries 
The billing report includes the charges accrued by network messaging. Some of the 
network charges are shown in boldface in the this billing report for mailbox 402. 
When no charges have accumulated for a counter, the entry does not appear on the 
billing report. 
MAILBOX: 402 ID: A.G. Bell 
GCOS 1  GROUP: 
$ 5.00 
$ -40 
$ 2.30 
$ -00 
$ -00 
$ 2.60 
$ .oo 
$ 1.20 
$ 4.10 
$ 3.50 
$ 9.60 
$ 1.70 
$ -00 
$ 1.80 
$ 5.40 
$ 6.00 
$ 3.21 
$ 5.84 
$ 1.40 
$ 50 
$ 2:36 
$ 1.26 FCOS 1: UNLIMITED base rate 
40 
23 
0 
0 
13 
0 
24 
41 
72 
9.6 
3.4 
0 
.09 
18 
6 
32.1 
116.8 
14 user messages received 
caller messages receiked 
call placements sent 
future deliveries sent 
urgent messages sent 
tas messages received 
number of receipts requested 
g;getings played 
times logged in 
user connect time 
caller connect time 
call placement time 
disk usage 
1 
9l.5 
6.3 messages sent to nodes 
urgent messages sent to nodes 
-1 minutes sent network urgent 
.l minutes sent over network 
messages received from nodes 
urgent messages received 
.l minutes rcvd over network 
.1 minutes rcvd network urgent 
1 o-4 Total Charges = $ 58.17  
						

							Network Billing and Reports 
ti rts 
Centigram Series 6 servers can provide reports on all aspects of MESA-Net 
configuration, both for MESA-Net Async and MESA-Net TCP/IP. 
When you complete MESA-Net programming for the first time, or when you update 
the configuration, print the reports showing the configuration. Confirm the changes 
and communicate them to the customer, then leave a copy on site for technicians 
servicing MESA-Net in the future. 
The available reports are: 
Digits Translation Report 
Node Table Report 
Network Queues 
Link Report 
Hardware Report 
Network Transport Query 
Network Link Query 
TCP Network Status 
Every time that you request one of these reports you are given the option to view 
these reports on the system console or your terminal connection, send them to a 
specific serial port, or put the information in a file. 
The Digits nslation Report 
This report displays each node prefer and associated node number that has been 
programmed into the Digits Translation Table. The Digits Translation report has 
the folfowing format: 
a 
>>> Denver VoiceMemo 
						

							Network Billing and Reports 
ode Access Table Report 
The Network Node Table stores the access string and hardware type of each remote 
node on the system. This information enables the originate link of the local node to 
establish communications with the other nodes on the system. 
The Node Table Report shows the node number, node name, access code (string), 
hardware type and access status (enabled or disabled) for every node that was entered 
into the Network Node Table. 
>>> Denver VoiceMemo >> Denver VoiceMemo cc< 
NEXWORK LINK DATA 
Mon Dee 4, 1995 6:12 pm 
LINI: MODE NETWORK TIMERS FAILCNTS 
HARDWARE RCV, RSND, INACT RCV, SND 
1 orig 1 = TELLABS? 60 60 60 7 7 
2 ans 1 = TELLABS 60 60 60 7 7 
Reading the Network Data Link Report 
The heading shows the site name, the report name, and the date and time that the 
report was run. 
LINK - the link number 
MODE - the link is either answer (ans) or originate (orig) 
NETWORK HARDWARE - This column shows the hardware type associated with 
the link. 
10-6  
						

							Nerwork Billing and Reports 
TIMERS - The three columns listed under Timers show the settings for the timeout 
parameters: 
RCV - the Data receive timeout, expressed in seconds 
RSND - the Resend timeout, in seconds 
INACT - the Node inactivity timeout, in seconds 
FAILCNTS - The two columns listed under FAILCNTS show the fail count 
settings: 
RCV - the Receive fail count 
SND - the Send fail count 
in erial 
=I= 
The Network Link Serial Port report is the second link report. The report is given in 
the following form: 
>>> Denver VoiceMemo -s< 
NETWORK LINK SERIAL PORTS 
Mon Dee 4, 1995 6:18 pm 
LINK PORT BAUD PARITY STOPBITS DATABITS FLOWCONTROL 
1 ctil 19200 none 1 8 enabled 
2 cti2 19200 none 1 8 - enabled 
Reading the ata Link Serial 
The heading shows the site name, the report name, and the date and time that the 
repordwas run. 
-ir 
LINK - the link number 
PORT - the port assigned to each link. “ctil ” and “cti2” are ports on the expansion 
serial card. 
BAUD, PARITY, STOPBITS, DATABITS - the communications setup for each 
port. 
IO-7  
						

							Q 
Network Billing and Reports 
ueue Parameters Report 
The Network Queue Menu, accessed from the reports menu, has two entries, Report 
Queue Parameters and Dump. “Dump” is a utility that is used only by service 
personnel. The Queue Parameters report shows the current network queue 
configuration. The report for the default configuration is as follows: 
Batch Urgent 
Weekday start time (hh:mm) 12:oo am 12:oo am 
Weekday stop time (hh:mm) Never Never 
Weekend start time (hh:mm) 12:oo am 12:00 am 
Weekend stop time (hh:mm) Never Never 
Message count threshold 1 1 
Waiting time threshold (minutes) 0 0 
Total message minutes threshold 0 0 
Limits 
Message blk use threshold (percent) 80 
Max call setup tries 
6 
Call retry interval (minutes)  1 
The Hardware Report 
The Hardware Report shows all currently configured hardware types, and their 
associated originate, answer, and disconnect actions, and line drop signals. Default 
hardware types do not appear in this report unless they have been assigned a 
hardware type number. 
This report is useful to leave on site to help debug communication device problems, 
or in the site log. 
>>> Denver VoiceMemo K-X 
i NETWORK LINKHARDWxm 
son Dee 4, 1995 6:42 pm 
DEVICE 1 TELLABS ORIGINATE ACTIONS 
ACTION PARAMETER 
1) Send string 

 
2) Sleep 
3) Flush device 
4) Sleep 
5) Send access code 
6) Sleep 
7) Read string 
connected TIMEOUT 
3 seconds 
2 seconds 
2 seconds 
20 seconds 
DEVICE 1 TELLABS ANSWER ACTIONS 
ACTION 
PARAMETER 
1) Send string 

 
2) Sleep 
3) Flush device 
4) Read string connected TIMEOUT 
3 seconds 
0 seconds 
10-8  
						

							‘I 
Nenvork Billing and Reports 
DEVICE 1 TELLABS DISCONNECT ACTIONS 
ACTION 
PARAMETER 
TIMEOUT 
1) Set signal lo 
DTR 
2) Set signal lo 
RTS 
3) Sleep 
5 seconds 
4) Set signal hi 
RTS 
5) Set signal hi DTR 
6) Sleep 
2 seconds 
DEVICE 1 TELLABS 
LINE DROP SIGNAL = CD 
DEVICE 1 TELLABS 
DIRECT LINK HARDWARE TYPE = 1 TELLABS 
eports 
It is always a good idea to print out a few other system reports, such as the NCOS 
table and the Smartcard Table. 
Several reports are invaluable when debugging MESA-Net delivery problems. 
ueue Report 
The Network Queue Report is an essential MESA-Net report. It lists all current 
messages in the network queue. Each remote node is displayed separately, and batch 
and urgent deliveries are separated. 
BATCH QUEUE: 
URGENT QUEUE: 
>>> Denver VoiceMemo >> Denver VoiceMemo 
						

							Nenvork Billing and Reports 
Two statistics reports give comprehensive pictures of network usage. These reports 
are available from the Network Usage Report Menu, which is a sub-menu of the 
Statistics Menu (not the Network Reports menu). 
The Network sage Report 
The Network Usage Report gives 15 minute “snapshots” of network message activity 
for a specified reporting period. This reporting period can be any hour, or range of 
hours, from the current day or the previous 6 days. 
12/04/95 8hr-17hr 
MESSAGE DAY=01 HOUR=08 
BATCH IN QUEUE 
URG IN QUEUE 
BATCH MAX LENGTH 
URG MAX LENGTH 
BATCH LATENCY H:M:S 
URG LATENCY 
BATCH DELIVERED 
URG DELIVERED 
TOTAL UNDELIVERED 
BATCH RECEIVED 
URG RECEIVED >>> Denver VoiceMemo 
						

							Network Billing and R< 
example, if the report is run at 3:30 pm, and the report interval is for hours 12-I 
(noon to 3 pm) of the same day, the entries for hour 
15 (3 to 4 pm) will all be 
hyphens. 
:ports 
5 
BATCH IN QUEUE is the total number of batch (non-urgent) messages and receipt 
updates present in the network queue during the time period. 
URG IN QUEUE is the total number of urgent messages in the network queue 
during the time period. 
BATCH MAX LENGTH is the total number of minutes of recorded speech in the 
network batch queue during the time period. 
URG MAX LENGTH is the total number of minutes of recorded speech in the 
urgent network queue during the time period. 
BATCH LATENCY is the maximum number of seconds that a message remained in 
the batch network queue during the time period. 
URG LATENCY is the maximum number of seconds that a message remained in 
the urgent network queue during the time period. 
BATCH DELIVERED is the total number of batch messages that were delivered to 
their destination nodes during the time period. (Receipt updates do not count here.) 
URG DELIVERED is the total number of urgent messages that were delivered to 
their destination nodes during the time period. 
TOTAL UNDELIVERED is the total number of messages (batch and urgent) that 
were rejected by their destination nodes during the time period. (Receipt updates do 
not count here.) -WC* 
sage Summa eport 
The Network Usage Summary Report gives peak (maximum) and total statistics for 
network message activity during a specified reporting period. This reporting period 
can be any hour, or range of hours, from the current day or from the previous 6 days. 
>>> Denver VoiceMemo