Lucent Technologies Octel 100 Implementation And Service Manual

							Implementation and Service Manual  Establishing a Serial Integration10-1
CHAPTER 10
Establishing a Serial Integration
Some phone systems require you to establish a serial integration between the
messaging system and the phone switch. The Serial Integration utility takes proprietary
information sent from the phone system through the PC’s serial port, interprets it, and
passes it to the system. Because Serial Integration is an optional utility, the sentinel
controls access to it.
There are two types of Serial integrations:
·  Generic Simplified Message Desk Interface (SMDI), which works for any switch
that uses standard Bellcore serial information or for Centrex systems
·  Switch-specific integrations, which are software communications packages that
are produced for specific switches, such as MCI Link for the NEC 2400 and 2000
IVS
  The phone system dictates whether you must use SMDI or Switch-Specific Integrations
software. Consult the phone system’s Configuration Note before beginning Serial
Integration to v erify which serial integration you should use.
  Steps prov ided in this chapter will help you to:
·  Run the Serial Integration utility after messaging system installation
·  Configure the ICONFIG utility
·  Configure the Serial Integration to support multiple-prefix Centrex systems 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Running the Serial Integration Utility After Messaging System Installation10-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.
 
  You cannot run the Serial Integration utility while the UPS monitor is active, because
there is a common executable file (COMM.DLL) shared by the utilities. If you run the
UPS Integration utility and the messaging system is instructed to run UPS automatically
upon bootup, the UPS constantly runs in the background. Consequently, if you attempt
to run the Serial Integration utility after UPS integration, the necessary file is not
accessible to run the Serial Integration utility.
  There are two ways to av oid this file-sharing problem:
·  Run the Serial Integration utility before running the UPS Integration utility.
·  If you need to run the Serial Integration utility after the UPS integration has been
run, close the UPS Monitor before running the Serial Integration utility. To do this,
click the UPS icon once and select Close. After Serial Integration installation is
complete, perform a shutdown and restart the PC. The UPS automatically starts
upon bootup.
 Running the Serial Integration Utility After Messaging System
Installation
  Use the following procedure if you need to install the Serial integration software after the
messaging system has been installed.
  To install the serial integration software:
1.  Turn on the PC, if it is not already running. OS/2 boots and the OS/2 Program
Manager displays.
2.  If the messaging system is configured to launch automatically on bootup, select Exit
from the File menu to 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.”
3.  Insert the messaging system CD-ROM in the CD-ROM driv e.
4.  Open an OS/2 window.
5.  From the C: prompt, type F: 
and press .
6.  From the F: prompt, type CD VM 
and press .
7.  From the \VM directory prompt, type INSTALL 
and press . The message
“Setup is initializing, please wait” displays.
  Do not attempt installation from the full screen OS/2 window, because the
installation process will run in the background and the installation screens will not be
v isible to you. Consequently, you will not be able to follow the on-screen prompts for
entering information. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Running the Serial Integration Utility After Messaging System Installation10-3
8.  A window displays, which briefly describes the installation procedure. To continue
installing, click Continue or press . The installation program presents a list of
driv es from which you can select.
 
9.  Select the driv e to which the files should be installed. Use the down arrow key to
highlight the appropriate driv e, then click OK. (Driv es A and B are disk driv es.) The
system prompts whether you want to install the system to the \CVR directory on the
specified installation driv e.
 
10.  Click Yes to install the files to the \CVR directory and continue the installation
process. If you click No, you are prompted to select a destination directory.
  To facilitate system maintenance, it is recommended that you do 
not change the
default installation directory.
11.  W ait while the system prepares to load files. A dialog box with installation options
and space requirements displays. The Space Requirements section of the window
displays the disk space required, based on the selected options, the space
availability, and the installation and boot driv es.
 
12.  Under Installation Options, disable all of the options.
13.  Under Voice Files, disable all of the options.
14.  Under Voice Driv ers, select None. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Running the Serial Integration Utility After Messaging System Installation10-4
15.  Under Serial Integrations, select the appropriate option from the drop-down menu.
16.  Click Install to install the messaging system based on the selections.
  A small display appears to the left of the Disk Prompt window to show the
progression of the installation process. The graph represents the percent of hard
driv e space and memory being used, as well as the progression of each file as it is
copied to the hard driv e. If the Low icon comes on during installation, do not be
concerned.
17.  W hen the system prompts whether you want the Serial integration utility to launch
automatically upon bootup, select Yes. A dialog box displays when the installation is
complete.
18.  Click OK to continue.
19.  W hen the Installation Setup Utility displays, select ICONFIG from the list and click
the Run button. See the topic, “Configuring the Serial Integration Utility,” for
information on running the ICONFIG utility.
20.  After you run the ICONFIG utility, the Installation Setup Utility displays. Click Done
to exit the Installation Setup Utility dialog box. The system displays a message when
installation is complete and reminds you to restart the computer for any changes to
take effect.
21.  To close the dialog box and return to the OS/2 window, click OK. The OS/2 window
displays.
22. Type EXIT 
and press  to close the OS/2 window.
23.  Remov e the CD-ROM.
24.  Shut down the PC:
a.
  Click the right mouse button on an empty area of the OS/2 desktop and select
Shut down from the menu that displays.
b.
  W hen you are prompted whether you want to close all windows and activ e
programs, click OK.
c.
 When prompted to shut down or reboot, press  to reboot the
PC.
25.  If the messaging system is not configured to launch automatically on bootup, start
the system by double-clicking the messaging system icon in the program folder. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Configuring the Serial Integration Utility10-5
Configuring the Serial Integration Utility
Use the following procedure to configure the serial integration utility.
To configure the serial integration utility:
1.  During installation, select ICONFIG from the Installation Setup Utility. The values on
the ICONFIG dialog box depend on the system configuration and are strictly defined
if the messaging system connects directly to a Central Office (CO) or switch. Consult
the Configuration Note to determine the correct settings for the switch.
 
2.  In the Comm Port field, specify the serial port where the data link with the switch is
to be established.
3.  Select the Baud Rate, which is the speed at which the data is transferred.
4.  Under Parity, select the algorithm used to calculate the parity bit in a word.
5.  Under Data Bits, select the number of bits in each character (word).
6.  Under Stop Bits, select the number of bits used to signify the end of the word (byte).
7.  In the Data W ait field, enter the number of cycles the system is to hold data before
sending it to the messaging system. This parameter should be used on sites where
data arriv es before the call.
8.  In the Time Out field, enter the intercharacter timeout period, which determines the
amount of time the messaging system is to wait between characters before
assuming a bad or failed packet and aborting. If the system receiv es ring v oltage,
this parameter also determines the number of cycles the system is to wait for data
before answering anyway.
9. To identify the switch’s v oice ports, select Port IDs. The Port ID dialog box displays.
 
10.  In the Desk I.D. field, enter the number that identifies the messaging system. If you
are using Generic SMDI in a Centrex application, you must get the Desk ID from the 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Supporting Multiple-Prefix Centrex Systems10-6
CO. The messaging system does not use this field if you are using an RS-232
integration.
11. To complete the Port ID’s fields, see the Configuration Note for the switch connected
to the messaging system.
12.  To sav e the port assignments, click OK.
13.  Click OK to accept the settings and close the ICONFIG dialog box.
You can change the ICONFIG or Port ID settings at any time. To access the ICONFIG
dialog box, double-click the Integration Configuration icon in the program folder.
WARNING:If you re-run the ICONFIG program, manual modifications made to the
SI.CFG file will be overwritten.
Supporting Multiple-Prefix Centrex Systems
On multiple-prefix Centrex systems using the automatic station login (direct subscriber
login to their mailbox) or message indicator features, the messaging system must
determine whether an incoming call is from an internal or external extension.
To define the internal prefix/extension combinations for the messaging system, you must
create one or both of the following files:
·  SMDI.TPT–if you are activ ating the automatic station login feature
·  SMDI.PFX – if you are configuring the message indicators
You are not required to create these files if you are using a single-prefix Centrex
configuration or if you are using a multiple-prefix Centrex, but are not using the
automatic station login or message indicator features.
Creating the SMDI.TPT File
On Centrex systems with multiple prefixes, the system must determine whether a call is
from an internal extension to properly process the call as an automatic station login. If
the system cannot determine whether a call is internal or external, external callers could
mistakenly be placed at a mailbox login prompt instead of the main greeting. The
SMDI.TPT file allows the system to differentiate between calls from internal extensions
and external callers.
You must create the SMDI.TPT file manually using a standard OS/2 editor. The file must
consist of v ariable-length ASCII strings called Target Prefix Strings. Target Prefix Strings
represent the prefix information for internal extensions.
See Preinstallation Configuration Worksheets
Refer to the Call Flow Sheet for a list of prefixes.
W hen a call is receiv ed, the calling telephone field of the serial integration packet is
compared to the Target Prefix Strings defined in the file. The number of digits in each
Target Prefix String determines how many digits are compared. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Supporting Multiple-Prefix Centrex Systems10-7
If the messaging system finds a match to one of the Target Prefix Strings:
1.  The call is considered an internal call.
2.  The mailbox number is extracted by remov ing the Number of Digits in a Mailbox
Number, specified in System Setup, starting from the right.
3.  The extracted mailbox number is then passed to the messaging system with the
correct integration code—in this case, the Automatic Station Login code.
If the calling digits do not match any of the Target Prefix Strings, the call is treated as an
outside call and the caller hears the main greeting.
To create the SMDI.TPT file:
1.  If the messaging system is running, select Exit from the File menu to shut it down.
2.  Open an OS/2 window.
3.  From the \CVR directory prompt, type E SMDI.TPT 
and press . A blank
OS/2 Editor window displays.
4.  Enter the first Target Prefix String and press . Each string can be up to 10
characters, which is the maximum currently supported by Centrex. The minimum
length is 1 character. Each character must be a single digit (0-9). Characters other
than digits are considered inv alid and generate an error message, such as, “The
TPS on line #1 contains inv alid characters.”
It is important to set up SMDI.TPT specifically for the type of Centrex application. If
you use a 7-digit Centrex implementation, do not include the area code in the prefix
information.
5.  Repeat step 4 for each Target Prefix String. You can define up to 25 Target Prefix
Strings in the SMDI.TPT file. The strings do not hav e to be in any certain order or
the same length.
 
6.  To sav e the file, select Sav e from the File menu. The first time you sav e the
SMDI.TPT file, the Sav e Notification dialog box displays.
7.  Click Type. The Type dialog box displays.
8.  Select Plain Text, then click Set. The file is sav ed as a plain text file.
9.  To exit the editor, click the icon in the upper-left corner of the window and select
Close. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Supporting Multiple-Prefix Centrex Systems10-8
10.  To close the OS/2 window, type EXIT 
and press .
11.  To load the file, shut down OS/2 and restart the PC. W hen the Serial Integration
driv er is loaded during bootup, the SMDI.TPT file is loaded into memory and the
Target Prefix Strings are used to compare against the incoming strings to determine
if the dialing number is internal or external. If the file is not found, a warning is
logged and no comparisons are performed.
Example SMDI.TPT File
The following scenarios are prov ided as examples. The digits being compared in these
scenarios are enclosed in brackets.
For the first two examples, a 10-digit Centrex implementation is used, the number of
digits in a mailbox number is 4 digits, and the following SMDI.TPT file is used:
555111
555112
555113
In the third example, a 7-digit Centrex implementation is used, the Number of Digits in a
Mailbox is set to 4, and the following SMDI.TPT file is used:
111
112
113
Sample SMDI.TPT File 1
If the incoming string is 5551112323:
·  The system compares [555111]2323 to the first entry in SMDI.TPT [555111
]
and finds a match.
·  The 4 digits for the mailbox (2323) are extracted and passed to the system as an
automatic station login for mailbox 2323.
  Sample SMDI.TPT File 2
  If the incoming string is 5552224444:
·  The system compares [555222]4444 to the first entry in SMDI.TPT [555111
]
and does not find a match.
·  The system compares [555222]4444 to the second entry in SMDI.TPT [555112
]
and does not find a match.
·  The system compares [555222]4444 to the last entry in SMDI.TPT [555113
] and
does not find a match.
·  The call is determined to be an external call, and the caller is placed at the Main
greeting.
  Sample SMDI.TPT File 3
  If the incoming string is 1136789:
·  The system compares [113]6789 to the first entry in SMDI.TPT [111
] and does
not find a match.
·  The system compares [113]6789 to the second entry in SMDI.TPT [112
] and
does not find a match. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Supporting Multiple-Prefix Centrex Systems10-9
·  The system compares [113]6789 to the last entry in SMDI.TPT [113
] and finds a
match. The four digits for the mailbox (6789) are extracted and passed to the
system as an automatic station login for mailbox 6789.
  W hile there can be duplicate extension numbers on a single system (multiple prefixes
with the same extension number), mailbox numbers must be unique. For example, while
there can be an extension 1200 on prefixes 511 and 512, there cannot be two mailboxes
numbered 1200 on the same messaging system.
  You can edit the SMDI.TPT file at any time. The messaging system must be restarted,
howev er, for the changes you make to be recognized.
 
Creating the SMDI.PFX Table
  Some Centrex applications require prefix information when sending message indicator
Activ ation and Deactiv ation codes.
  In a single-prefix application, you can add the -p
xxx 
switch, where xxx represents the
prefix to the START /C /MIN SMDI.EXE 
statement in the RUNVM.CMD file. For
example, on a system where a single prefix of 301 is used, you can add -p301 to the line
so it reads START /C /MIN SMDI.EXE -P301
.
  In a multiple-prefix application, there must be a way to determine the correct prefix
information to insert in the outgoing Centrex message indicator packet. In this case, you
must create a SMDI.PFX file using an OS/2 editor to determine the correct prefix
information. You can use the -p
xxx 
switch in a multiple-prefix application to specify a
default prefix. If there is one prefix associated with the majority of Centrex extensions,
specify that prefix in the RUNVM.CMD file and include the other prefixes in SMDI.PFX.
  W hen using SMDI.PFX file information to create a message indicator packet, the digits
are sent as specified in the file; there is no error-checking or padding. For example, if
you are using 7-digit Centrex, make sure that the number of digits in the prefix and
extension combination is exactly 7; otherwise, the packet will be incorrect.
  The SMDI.PFX file should contain three columns:
·  The first two columns must identify a mailbox number, or a range of mailbox
numbers, that exist on the system. The Ending Mailbox Number is optional if you
are identifying a single mailbox number.
·  The third column must identify the corresponding prefix information for the
mailbox, or range of mailboxes, identified in the first two columns. If you are
using a 7-digit Centrex application, do not include the area code in the prefix.
  See Preinstallation Configuration Worksheets
 
Refer to the Call Flow Sheet for a list of prefixes. 
						

							10. Establishing a Serial Integration
Implementation and Service Manual  Supporting Multiple-Prefix Centrex Systems10-10
  W hen the system sends a message indicator request, the mailbox number portion of the
string is compared to the Starting and Ending Mailbox Numbers defined in the
SMDI.PFX file:
·  If a match is found, the mailbox number and prefix combination is placed in a
Centrex message indicator packet and sent across the serial port.
·  If no match is found, the current message indicator prefix is used.
·  If no prefix is defined, the system looks to the RUNVM.CMD file to determine if
the -p
xxx 
switch is present. If no prefix is specified, the Centrex request
packet is sent with the extension number only.
To create the SMDI.PFX file:
1.  If the messaging system is running, select Exit from the File menu to shut it down.
2.  Open an OS/2 window.
3.  At the \CVR directory prompt, type E SMDI.PFX 
and press . A blank
OS/2 Editor window displays.
4.  Enter the Starting Mailbox Number in the first column. Each entry in these fields can
be up to 10 characters (the maximum currently supported by Centrex). Each
character must be a digit from 0-9; characters other than digits are considered
inv alid and generate an error message.
5.  Insert a space or a tab to separate the first and second columns.
6.  If it is the first mailbox in a range of mailboxes, enter the Ending Mailbox Number in
the range in the second column. The Ending Mailbox Number is not required if you
are specifying an indiv idual mailbox. Entries can v ary in length, but must fit on a
single line. Duplicate or ov erlapping mailbox numbers are not permitted.
7.  Insert a tab or space to separate the second and third columns.
8.  Enter the corresponding prefix for the mailbox or range of mailboxes.
9.  Repeat steps 4-8 for each entry, using a carriage return between lines. The entries
do not hav e to be in any particular order. There is no limit to the number of entries
that can be included in the file. To minimize processing time, howev er, you should
use ranges of mailboxes rather than indiv idual mailbox entries whenev er possible.
 
10.  To sav e the file, select Sav e from the File menu. If OS/2 prompts you to select a file
type to associate with the new file, click Plain Text.