Lucent Technologies Octel 100 Implementation And Service Manual

							18. Using Network Messaging
Implementation and Service Manual  Managing NameNet Directories18-19
2.  In the Enter Node Number field, enter the number of the node you want to edit, then
click Edit. The Network Node Maintenance dialog box displays. If you do not know
the node number, use the search feature to help locate the appropriate node. For
additional information, see the topic, Searching for a Node, earlier in this chapter.
 
3.  Click NameNet Entries. The NameNet Maintenance dialog box displays the current
NameNet entries for the node.
 
4.  Highlight the NameNet entry you want to mark as permanent, then click Permanent.
The letter P displays before the subscriber name.
5.  To mark a permanent NameNet entry as usage-based, select the entry, then click
Permanent. The letter U displays next to the subscriber’s name.
6.  To close the NameNet Maintenance dialog box, click OK. The Network Node
Maintenance dialog box displays.
7.  To close the Network Node Maintenance dialog box, click OK. The main system
window displays. 
						

							18. Using Network Messaging
Implementation and Service Manual  Managing NameNet Directories18-20
To delete a NameNet entry:
1.  From the Options menu, click Network Maintenance. The Select Node dialog box
displays.
 
2.  In the Enter Node Number field, enter the number of the node you want to edit, then
click Edit. The Network Node Maintenance dialog box displays. If you do not know
the node number, use the search feature to help locate the appropriate node. For
additional information, see the topic, Searching for a Node, earlier in this chapter.
 
3.  Click NameNet Entries. The NameNet Maintenance dialog box displays the current
NameNet entries for the node.
 
4.  Highlight the NameNet entry you want to delete, then click Delete. The entry is
deleted.
5.  To close the NameNet Maintenance dialog box, click OK. The Network Node
Maintenance dialog box displays.
6.  To close the Network Node Maintenance dialog box, click OK. The main system
window displays. 
						

							Implementation and Service ManualInstalling and Configuring Visual Mailbox19-1
CHAPTER 19
Installing and Configuring Visual Mailbox
Visual Mailbox is an optional add-on module that prov ides messaging system
subscribers with a v isual interface to their v oice mailboxes ov er an installed network.
W ith Visual Mailbox, subscribers can control many of the features av ailable in their v oice
mailbox, such as listening to and sending messages, with the point-and-click abilities of
their PC’s mouse.
Visual Mailbox may not be av ailable on all messaging systems. Contact your authorized
representativ e for more information.
This chapter prov ides steps for installing and implementing Visual Mailbox. In some
cases, Visual Mailbox is preinstalled on the messaging system. If so, you do not hav e to
complete all of the procedures prov ided in this chapter.
This chapter will help you to:
·  Understand the Visual Mailbox components
·  Understand the Visual Mailbox requirements
·  Plan for Visual Mailbox implementation
·  W ork with the LAN Administrator to configure the LAN
·  Install the network interface card
·  Install Networking Support for OS/2
·  Install the Voice Fax Serv er
·  Configure the messaging system software
·  Perform Visual Mailbox maintenance
·  Install the client software on the LAN serv er
·  Install Visual Mailbox on client (subscriber) PCs 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualUnderstanding the Visual Mailbox Components19-2
  Procedures in this chapter assume that the hard driv e on which the system is installed is
driv e C, that an additional hard driv e that may be installed is D, that the disk driv e is A,
and that the CD-ROM driv e, if installed, is F. Driv e designations on the specific PC on
which you are working may v ary. Confirm the appropriate driv e letters, when necessary,
in procedures prov ided in this chapter.
Understanding the Visual Mailbox Components
Visual Mailbox software depends on sev eral components to perform the necessary
communication functions:
· LAN
· LAN Serv er
·  Messaging System and the Voice Fax Serv er
·  Priv ate Branch Exchange (PBX)
·  Client (subscriber) PC
·  Client sof tware setup
Component Function
Local Area Network The LAN is the communication vehicle from each
subscriber’s desktop to the Voice Fax Server on the
messaging system. Physically, the LAN is represented by a
LAN server and a network of PCs connected by cables to
Network Interface Cards (NICs) at each PC or workstation.
LAN Server A LAN server is the PC through which all network
communications are controlled. The messaging system PC,
which contains the Voice Fax Server, and all PCs attached to
the LAN communicate with the LAN server via a network
interface card in each PC.
Messaging System Voice Fax
ServerThe messaging system and the Visual Mailbox Voice Fax
Server reside on the same PC. The Voice Fax Server is the
portion of Visual Mailbox that sends and receives commands
to subscriber PCs. The messaging system and Voice Fax
Server communicate with each other to perform functions for
subscribers who access their mailboxes visually on their
desktops.
The Voice Fax Server sends and receives commands for the
subscriber across the LAN via the network card. The Voice
Fax Server interprets requests received from subscribers
across the LAN and passes information back and forth to the
messaging system.
PBX The PBX establishes a voice path between the subscriber’s
workstation and the Voice Fax Server to allow subscribers to
listen to and send messages to other subscribers or to record
greetings for their mailboxes. W hen a subscriber wants to
perform one of these functions, the Voice Fax Server
requests an available line from the messaging system. The
Voice Fax Server then calls the subscriber to establish a
voice path. 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualUnderstanding the Visual Mailbox Components19-3
Client PC In networking terms, a client is an entity that is connected to
a LAN and requests or receives information from a server.
W ith Visual Mailbox, the requests made on a client PC are
passed to the Voice Fax Server via the LAN server.
Client Software In addition to the files that must be installed on the computer
housing the messaging system, Visual Mailbox includes files
that must be installed on each client PC that will be running
Visual Mailbox. These files, collectively referred to as 
client
software
, allow individual subscribers to access and operate
Visual Mailbox from their desktops.
Understanding Visual Mailbox Requirements
The following list represents the minimum hardware and software requirements
necessary to configure Visual Mailbox.
LAN
Visual Mailbox currently supports:
· Novell NetWare versions 3.x and 4.x – Verify with the LAN Administrator that
all the latest updates are installed on the NetW are LAN. Sev eral LAN software
rev isions hav e been released to correct problems.
· Windows NT Server
  The Shared Files network protocol is the protocol supported for Visual Mailbox. W hen
using the Shared Files protocol, the Voice Fax Serv er creates two files on the LAN
serv er:
·  W 2S.DAT – Records requests from the client PC to the serv er
·  S2W .DAT – Stores serv er to client PC responses
Both files are created in the directory specified in the Path to Serv er listbox, which you
complete when installing the VFS.
Under the Shared Files protocol, the VFS periodically scans the W 2S.DAT file, looking
for client PC requests. Each indiv idual client PC is identified by its mailbox and
application ID. W hen the VFS finds a request, it processes the request and places a
response in the S2W .DAT file, which is systematically scanned by each client PC.
LAN Server
The LAN serv er is the PC that processes requests and supplies connectiv ity to users on
the LAN who are attached to it. The LAN serv er controls client PC access to other LAN
applications, such as word processing, database, or accounting programs. Visual
Mailbox requires that the LAN serv er has a directory av ailable to all users of the Voice
Fax Serv er, so that files and requests can be transferred between the Voice Fax Serv er
and the client PCs. Details on configuring the LAN serv er are prov ided in this chapter.
Many LANs use sev eral serv ers to accommodate users’ needs. Be aware that the Visual
Mailbox software will access only one LAN serv er. Any potential Visual Mailbox users
must be attached and mapped to this serv er. 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualUnderstanding the Visual Mailbox Components19-4
It is recommended that there be sufficient hard driv e space on the LAN to accommodate
the necessary data files and client software files. W hile the amount of disk space will
v ary based on the number of users and the v olume of call traffic on Visual Mailbox, a
minimum of 10 MB is recommended for small, low-traffic systems.
Messaging System/Voice Fax Server
To use Visual Mailbox with the messaging system, there are sev eral hardware and
software requirements that must be met.
Hardware
Although there are hardware requirements defined for the messaging system, there are
additional requirements for using Visual Mailbox. The Voice Fax Serv er will, in many
cases, require a higher performance PC than that required by the system alone. All
turnkey systems meet the respectiv e requirements:
· CPU and Memory – For CPU and memory requirements for systems using
Visual Mailbox, see Chapter 2, “Determining the Customer’s System Needs.”
· Network Interface Card and LAN Connection – The messaging system PC
must hav e a network interface card (NIC). The Voice Fax Serv er must be
physically connected to the LAN by attaching a LAN cable to the NIC.
Some PCs do not require a NIC. See the 
PC Specification Sheet you received
with your system for information on whether it uses a NIC.
· Expansion Slots – An expansion slot is required for the NIC. The NIC is
preinstalled on systems ordered with Visual Mailbox.
· Hard Drive – Chapter 2, “Determining the Customer’s System Needs,” describes
the method used to calculate the size of the hard driv e required to support the
user’s application. In addition to the size needed for the messaging system, the
PC’s hard driv e should be large enough to accommodate the Visual Mailbox
software and its associated databases. Contact a technical support
representativ e for details.
· Sentinel – Like other optional messaging system utilities, Visual Mailbox access
is controlled by the sentinel, which must be programmed to allow the system to
use it. The sentinel also controls the maximum number of licensed users who
can be logged into the Voice Fax Serv er at one time.
· Fax Board – A fax board is required 
only if you want to utilize the Fax Viewer
feature of Voice Mailbox. The Fax Viewer allows subscribers to v iew faxes sent
to their mailboxes on their PCs, rather than retriev ing them at a fax machine, as
in the v oice-only system. Note that the Fax Viewer icon displays in the Visual
Mailbox folder on client PCs whether the system supports it or not.
  Software
  In addition to the required hardware, different software utilities may be required:
· Visual Mailbox – Contains the files necessary to run Visual Mailbox.
· Optional Utilities – Optional utilities permit subscribers to use additional
features in Visual Mailbox, including sending messages to subscribers of remote
messaging systems and sending fax messages to subscriber mailboxes. 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualUnderstanding the Visual Mailbox Components19-5
Private Branch Exchange
There should be no changes required to PBX programming when adding Visual Mailbox
to an existing messaging system. As always, be sure that the switch is configured as
described in the appropriate Configuration Note. In most cases, the features supported
by the switch are av ailable with Visual Mailbox.
The PBX must support third-party transfer capabilities for the Dialer and Immediate Call
features to be available. If the Integrator utility supports the customer’s switch, the
required codes are automatically configured when you run the Integrator utility during
messaging system installation. Again, be sure to consult the switch’s Configuration Note.
Client PC
The client PCs must also meet minimum hardware and software requirements to use
Visual Mailbox.
Hardware
· CPU and Memory – All client systems must be a minimum 386-SX/16 MHz
millennium-compliant PC with 4 MB RAM. See the manufacturer’s
documentation if necessary to determine whether the PC meets the minimum
requirements.
· NIC – The Visual Mailbox client PCs must hav e a NIC. The clients must be
physically connected to the LAN by attaching a LAN cable to the NIC.
· Hard drive – The hard driv e in the client PC must hav e space av ailable for
loading fax files and adding the files necessary for Visual Mailbox installation.
Space requirements are still under consideration. Contact a technical support
representativ e for more information.
· Mouse – A mouse is required on each client PC for point-and-click control of a
v isual mailbox. Some functionality of the desktop interface is av ailable only with
a mouse.
Software
· Windows 3.x, Windows 95, or Windows NT 4.0 with Serv ice Pack 3 or higher.
– Access to Microsoft W indows v ersion 3.x , W indows 95, or W indows NT 4.0
with Serv ice Pack 3 or higher is required for each client PC to access the Visual
Mailbox interface. W indows can be accessed from the local hard driv e or from a
network driv e.
Additional Client Requirements for PC Audio Features
If a client (subscriber) PC is equipped with a sound card and all the necessary dev ice
driv ers for the sound card are correctly installed, Visual Mailbox’s PC audio features
allow the subscriber to use speakers or headphones attached to the PC to play
messages and greetings—instead of using the telephone. If the subscriber plugs a
microphone into the sound card or the PC has a built-in microphone, it can be used to
record new messages and greetings.
If a client PC is not equipped with a sound card, Visual Mailbox detects this and disables
all of the PC audio features of Visual Mailbox. 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualPlanning for Visual Mailbox Implementation19-6
Be adv ised of the following additional considerations:
·  The sound card installed in any PC using PC audio features must be Sound
Blaster-compatible (MPC-compliant).
·  Each PC using the PC audio features must hav e hard driv e space av ailable to
temporarily store W AV files. A W AV file is downloaded to the client PC hard
driv e each time a subscriber plays a message using PC audio features. A
downloaded W AV file is automatically deleted when the subscriber deletes the
associated message or logs out of Visual Mailbox.
  The amount of hard driv e space required for W AV files depends on the length of
messages downloaded (played) by subscribers. A subscriber running PC audio
features in 8-bit mode requires 8,000 bytes of space to play one second of a
recorded message (or .5 MB for ev ery minute of play). A subscriber running PC
audio in 16-bit mode requires 16,000 bytes of space to play one second of a
recorded message (or 1 MB for ev ery minute of play).
·  Subscribers using a microphone to record messages and greetings should
activ ate the multimedia Automatic Gain Control option, if it is av ailable on the
PC. Consult the PC’s documentation for instructions on activ ating this option.
·  PC audio users must be assigned all network rights (read, write, create, erase,
modify, and scan) to the ...\DATA\BIN directory on the LAN server.
The playback sound quality of greetings and messages may v ary, depending on factors
including the quality of the sound card and microphone, a subscriber’s recording
techniques, and the lev el of background noise. Also, certain hardware setups (including
some laptops), sound card setups, and operating system anomalies may impair the
ability of the PC audio features to function as they should. If you encounter issues or
problems, report them immediately to a technical support representativ e.
Planning for Visual Mailbox Implementation
To effectiv ely install Visual Mailbox, it is important that you know the customer’s
expectation of the application before you begin. To accomplish this, work closely with the
customer’s Information Serv ices (IS) and telecommunications representativ es. In
addition, carefully assess the existing system to determine whether additional hardware
(such as NICs, cabling, and memory) and software (such as Microsoft W indows and
optional system utilities) must be installed before you attempt to install Visual Mailbox. A
Visual Mailbox Implementations Considerations W orksheet is prov ided behind the
W orksheets tab. Make sure it is completed by the site’s LAN Administrator before you
attempt Visual Mailbox installation.
W hen including installation of Visual Mailbox as part of an initial messaging system
installation, ensure that the Automated Attendant and messaging software is functioning
properly before installing the Visual Mailbox software. This includes all integration
features, such as message indicators, call forward to a personal greeting, and automatic
station login, as well as other utilities, such as network messaging and fax. Also, be sure
that the desired outside caller call flow has been established for the integration type.
It is also assumed that the LAN is installed and functioning properly and that all potential
client PCs are attached and functioning before the Visual Mailbox installation is started.
It is important that you and the customer’s IS representativ e address the following
considerations before you begin installation. 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualW orking with the LAN Administrator to Configure the LAN19-7
LAN Considerations
W ith the assistance of the customer’s IS representativ e, sketch a diagram of the
customer’s existing network, displaying the configuration topology and the number of
serv ers. At this time, you should also gather a list of all subscribers who will be attached
to the Voice Fax Serv er.
Because a LAN contains information of a v ital and sensitiv e nature, you must be certain
that the LAN serv er is av ailable and ready for the installation.
It is recommended that the site’s authorized LAN administrator prepare the LAN for the
installation of Visual Mailbox and be present for Visual Mailbox installation and
configuration. If you are using IBM Peer for OS/2 to communicate with a non-Nov ell
LAN, such as W indows NT, make sure that the LAN has been installed and configured
before you begin Visual Mailbox installation. Be sure that the LAN administrator
completes the listed actions before you install Visual Mailbox.
Messaging System Considerations
Because the Voice Fax Serv er resides on the same PC as the messaging system, the
messaging software must be shut down to install Visual Mailbox. It is recommended,
therefore, that you install Visual Mailbox during off-peak hours. Also, be sure that all
users who will access Visual Mailbox have existing messaging system voice mailboxes.
System Security Considerations
It is important to discuss security issues with the customer. First, is the LAN serv er in a
secure env ironment? Next, is the PC in a secure env ironment? This is important, since
an unsecure env ironment allows unauthorized indiv iduals to alter settings or turn off
power to both the LAN serv er and the messaging system.
If the LAN serv er is configured to automatically log out all users at a defined time to
perform a network backup, it is recommended that you ensure it does not log out the
Voice Fax Serv er. Instead, back up Visual Mailbox software on a regular basis using a
third-party utility that is initiated in the RUNVM.CMD file.
Also, recommend to the customer that subscribers use a password-protected screen
sav er on their PCs, since anyone with access to a client PC keyboard can access a
user’s v oice and fax messages if Visual Mailbox is running on the PC.
Client Software Setup Considerations
If indiv idual subscribers are responsible for installing the client software portion of Visual
Mailbox on their PCs, be sure to prov ide them with instructions. These instructions must
include the driv e and directory path to the serv er containing Visual Mailbox, which will
v ary from site to site. A Client Software Installation Template is prov ided at the end of
this chapter. This template should be completed and distributed to all subscribers who
are installing the client software on their PCs.
Working with the LAN Administrator to Configure the LAN
Before you install Visual Mailbox, the LAN serv er must be properly configured. It is
strongly recommended that the LAN administrator at the customer site or the LAN
serv ice prov ider make the necessary changes. All LAN configuration should be
completed before installing Visual Mailbox. If you do not prov ide LAN support for the
site, contact an authorized LAN representativ e to assist you. 
						

							19. Installing and Configuring Visual Mailbox
Implementation and Service ManualInstalling the Network Interface Card19-8
The tasks inv olv ed in configuring the LAN depend on the type of network installed at the
customer site. Two worksheets are prov ided behind the W orksheets tab that list the
requirements for Nov ell NetW are and W indows NT implementations. Make sure the LAN
Administrator completes the appropriate worksheet before you attempt to install
networking support for OS/2 or Visual Mailbox.
Installing the Network Interface Card
The Network Interface Card must be installed in the messaging system PC to prov ide a
communications path with the network.
Some PCs do not require a NIC. See the 
PC Specification Sheet you received with your
system for information on whether it uses a NIC.
If Visual Mailbox was preinstalled on the messaging system PC, the network interface
card is already installed.
You will need the following materials to complete the ethernet card installation:
· NIC
·  Appropriate hand tools
· DOS-bootable disk
·  RJ-45 network cable
W hen handling the NIC, be sure to wear a grounding wrist strap to control static
electricity. If you do not wear a grounding strap, you may damage the card.
To install the NIC into the messaging system PC:
1.  If the messaging system is running, shut it down. For information on logging into the
system and shutting it down, see Chapter 20, “Starting, Logging Into, and Shutting
Down the System.”
2.  Shut down any open applications (for example, UPS, SMDI) and windows except the
OS/2 desktop:
a.
  Press  to open the W indow menu.
b.
  Highlight any application you see with the exception of the OS/2 desktop.
c.
  Click the right mouse button once on the highlighted application.
d.
 Select Close.
e.
  Repeat steps 2a – d for each open application.