| Field Name |
Description/Procedure |
| Date |
The starting date for which traffic data was collected for
the report. It is the date you entered on the command line or
the current date if you did not specify a date.
If you enter a date previous to the current date, each day's
record is presented as an additional page (screen). Press
F7 (Next Page) and F8 (Prev Page) to scroll through each daily
report record.
|
| Hour |
The starting hour for which traffic data was collected for
the report. It is the hour you entered on the command line or
the current hour if you did not specify an hour. |
| Ending Time |
The time at which data collecting ended. |
| Average IMAPI Sessions in Use |
The average number of IMAPI sessions that were in use simultaneously
during the hour of the day you selected. On small systems, if
this number is greater than half the total number of ports configured,
the messaging system is probably experiencing call blocking.
|
| SUBSCRIBERS |
| Local |
The total number of local subscribers on the messaging system
at the end of the hour being reported (or at the current time
if the current hour is being reported). |
| Remote |
The total number of remote subscribers on the messaging system
at the end of the hour being reported (or at the current time
if the current hour is being reported). |
| Non Administered Remote |
The total number of non-administered remote subscribers on
the messaging system at the end of the hour being reported (or
at the current time if the current hour is being reported). |
| VOICE MAIL |
|
Successful IMAPI Logins
|
The number of successful login attempts made during the hour
reported. Login attempts were made by subscribers calling
from an IMAPI client.
|
|
Failed IMAPI Logins
|
The number of unsuccessful login attempts made during the
hour reported. Login attempts were made by subscribers calling
from an IMAPI client.
Unsuccessful means that the messaging system did not
allow the caller access to messaging operations. Unsuccessful
access could have been due to an unrecognizable password, login
ID, or both, or because the caller hung up before completing
the call. |
| IMAPI Session Usage, (Seconds) |
The total number of seconds that IMAPI sessions were in use
for client voice mail sessions during the hour reported. |
| CALL ANSWER |
|
IMAPI Sessions
|
The number of completed call answer telephone calls made
to the system during the hour reported. Calls came from telephones
networked with IMAPI (network) sessions to the host switch
These numbers include the times the system answered calls
for subscribers, attendants, and bulletin boards.
|
|
Voice Components
|
The number of voice components that were included in call
answer telephone calls made to the system during the hour
reported. Calls came from telephones networked with IMAPI
sessions to the host switch
These numbers include the times the system answered calls
for subscribers, attendants, and bulletin boards.
|
|
Fax Components
|
The number of fax components that were included in call answer
telephone calls made to the system during the hour reported.
Calls came from telephones networked with IMAPI sessions to
the host switch
These numbers include the times the system answered calls
for subscribers, attendants, and bulletin boards.
|
| IMAPI Session Usage (Seconds) |
The number of seconds that IMAPI sessions were in use for
call answer sessions during the hour reported. |
