Lucent Technologies CRCS User Manual

Conference Reservation and Control System

(CRCS) Release 6.0

Installation

555-027-109
Comcode 108382085
Issue 1
April 1999

Copyright© 1999 Lucent Technologies Inc.
All Rights Reserved
Printed in U.S.A.

Notice

While reasonable effort was made to ensure that the information
in this document was complete and accurate at the time of
printing, Lucent Technologies Inc. and its authorized agents
cannot assume responsibility for errors. Changes and/or
corrections to the information contained in this document may be
incorporated in future issues. Names and addresses used for
examples throughout this guide are fictitious.

Your Responsibility for Your System’s Security

You are responsible for the security of your system. Lucent
Technologies Inc. does not warrant that this product is immune
from or will prevent unauthorized use of common-carrier
telecommunications services or facilities accessed through or
connected to it. Lucent T echnologies Inc. will be not responsible
for any charges that result from such unauthorized use. Product
administration to prevent unauthorized use is your responsibility
and your system administrator should read all documents
provided with this product to fully understand the features
available that may reduce your risk of incurring charges.

Trademarks and Copyright Acknowledgments

Concorde is a trademark of PictureTel Corp.
DEFINITY is a registered trademark of Lucent Technologies Inc.
in the United States and throughout the world
Lotus 1-2-3 is a registered trademark of IBM
Microsoft Windows 95 and Windows NT are registered
trademarks of Microsoft Corporation
SatisFAXtion is a registered trademark of PureData
Sportster is a registered trademark of U.S. Robotics
WinFax is a registered trademark of Delrina Technology Inc.
Zetafax is a registered trademark of Equisys Limited

Users outside of the US and Canada should contact their local
authorized Lucent Technologies distributor if they want to order
additional copies of this document. Also, users in these countries
should send any comments on the document to their local
authorized Lucent Technologies distributor.

Lucent T e chn ologi es Inc. Fraud Interventi on

If you suspect you are being victimized by toll fraud and you need
technical support or assistance, call the BCS Technical Service
Center Toll Fraud Intervention hotline at 800 643-2353.

Comments

To comment on this document, complete and fax in the comment
card at the end of the document.

Technical Support

Call: Video Technical Center (VTC)

800 242-2121 then follow the prompts for video
conferencing

International Technical Assistance Center (ITAC)
303 804-3777

Screen shots of Microsoft Windows 95/NT 4.0 reprinted with
written permission from Microsoft Corporation.

Ordering Information

Call: Lucent Technologies BCS Publications Center

Voice: 800 457-1235 International Voice: 317 322-6416
Fax: [phone] International Fax: [phone]

Write: Lucent Technologies BCS Publications Center

2855 N. Franklin Road
Indianapolis, IN 46219

Order: Document No. 555-027-109

Comcode No.108392085
Issue 1, April 1999

You can be placed on a standing order list for this and other
related documents you may need. Standing order will enable you
to automatically receive updated versions of individual documents
or document sets, billed to account information that you provide.
For more information on standing orders, or to be put on a list to
receive future issues of this document, contact the Lucent
Technologies BCS Publications Center.

Contents

n

Installation Overview 1

n

Upgrading from a Previous Release 2

Upgrading a Single-User System 2

n

Pre-Installation Requ ir em ents 5

CRCS/OpCenter and OpCenterSP Checklist 5
Fax Option 6

n

Configuring the PC 7

n

Connecting the PC to the MCU 9

Local Connection to MCU 9
Remote Connection to MCU 10
Connection Procedure 10
Checking the Modem Settings 12

n

CRCS/OpCenter Software Installation 15

n

Testing CRCS 19

Logging In to CRCS 19
Setting the Time Zone 20
Adding the M CU 21
Establishing the Communications Link 22
Uploading MCU Options 24
Running the MCU Extension Utility Program 24
Adding an Endpoint 24
Adding a Conference Template 26
Adding a Company 27
Adding a Person 27
Adding a Site 28
Editing Defaults 30
Adding a Test Conference 30

n

Testing OpCenter 31

n

Faxmodem Installation 32

Windows 95 32
Windows NT 4.0 32
Installing WinFax PRO 8.0 33
Saving Faxes with WinFax Log Files 37
Setting Up Reminder Faxes 37

Issue 1 CRCS R6.0 April 1999 iii

Contents

n

OpCenterSP Installation 38

n

Testing OpCenterSP 42

n

Appendix A: Modem Pooling 44

Administering Modem Pool Groups 44
3800 Series Modem Installation 48

3810 48
3820 53
3830 53

7400A Data Module Installation 54

iv Issue 1 CRCS R6.0 April 1999

Single-User
CRCS/OpCenter and
OpCenterSP Installation

Installation Overview

CRCS/OpCenter and OpCenterSP can be set up as a single-user system on a
dedicated PC connected to up to 2 Lucent Technologies MultiPoint Conferencing

Units (MCU). The CRCS/OpCenter PC can run either Microsoft® Windows NT

4.0 or Microsoft Windows 95.
The connection between the CRCS/OpCenter or the OpCenterSP PC and the

MCU can be local if the distance between the two is less than 5000 feet. The con­nection is considered remote if the distance is greater than 5000 feet. Also, if the
CRCS/OpCenter or OpCenterSP PC is not connected to the TN754B or TN2224
on the MCU side, the connection is considered remote.

Follow the installation procedures outlined in this guide to set up and connect the
CRCS/OpCenter or the OpCenterSP PC to the MCU. This manual also includes
installation procedures for the fax option available with CRCS.

Issue 1 CRCS R6.0 April 1999 1

Upgrading from a Previous Release

Upgrading from a Previous Release

Each new release of the CRCS/OpCenter program and the MCU offers additional
features. If any endpoint already included in your previous release supports some
or all of the new enhancements, you may need to update the bandwidth, proto­cols, and feature entries in the Conference Template, Endpoint, Site, and MCU
databases.

Beginning with release 6.0, CRCS is backward compatible with the previous
release MCU. The two MCUs controlled by CRCS do not need to be the same
release. For example, MCU1 could be release 6.0 and MCU2 could be release

5.0.47.

NOTE:

If upgrading from a release earlier than CRCS 4.2, remove all reservation
system items including link manager and command manager from the
StartUp group prior to installation.

Upgrading a Single-User System

The first consideration before upgrading from an earlier release is to make sure
your hardware and operating system meets the higher minimum requirements of
the release of CRCS/OpCenter. See "Pre-Installation Requirements" for a list of
the required hardware components, software, and operating system. Also make
sure you have the list of logins and passwords as defined.

With the proper hardware installed, use the following upgrade procedure to load
the new release of CRCS:

1. Before upgrading, you need to run the database repair program. To do so,
click Start—Programs—Lucent Technologies CRCS—Run Dat abase

Repair. If there are any errors reported, click Start—Programs—Acces-
sories—System Tools—Scan Disk.

2. Backup the database to external media such as floppy disk, zip disk, or
tape. This database file named
tory (where CRCS was previously installed). You can perform a Start—
Find to locate the file or look in your CRCS directory under the dbase
folder. It may be located on your main boot drive.

crs.mdb

is located in the

dbase

subdirec-

NOTE:

If you changed the name of the default directory or destination drive when
you previously installed CRCS, copy the
rectory of the new directory before installing CRCS and readministering the
link. For example, if you name the directory

crs.mdb

c:\crcs6x

file to the dbase subdi-

, you would need to

2 Issue 1 CRCS R6.0 April 1999

Upgrading a Single-User System

create a subdirectory named

c:\crcs6x\dbase

and copy the

crs.mdb

file into

it before installing CRCS.

3. From the MCU MT, perform an add login and change permissions to create
the crcs login, password, and permissions (see

MCU Administration

for

details).

4. Insert the CRCS CD-ROM and click Start on the Windows Taskbar.

NOTE:

Make sure no other applications are running, including fax programs.

5. Click Run and use the Browse button to locate the
CD-ROM. Click OK.

6. Follow the program prompts (see "CRCS/OpCenter Software Installation"
on page 15 for details) and when the installation is complete, choose to exit
without the automatic reboot (the No option) and shutdown your PC.

7. Power off your PC.

8. Wait a few seconds and power on the PC.

9. Login to CRCS as an administrator.

10. From the A

dmin menu on the Main window, select Query MCU Parame-

ters for each MCU (1 and/or 2).

1 1. Schedule a test conference to begin immediately, verify that the conference

downloads to the MCU and record the CRCS ID #.

setup.exe

file on the

12. From the MCU MT, perform a list conference to verify the conference
downloaded to the MCU. If the connection is established, the upgrade is
complete. For remote connections only, continue to step 13.

13. For remote connections, you can administer when the link between CRCS
and the MCU is connected. It can be connected full time (permanent), only
when a conference data is being downloaded (on-demand), or during a
specified hours in a day (between). From the CRCS PC, administer a con­nect time from the A

dmin menu on the Main window, select Run Link

Admin.

14. From the MCU Link Administration window, click the Connect Parameters
tab.

n

for the on-demand option, specify the time (in minutes) that the link
should remain connected.

n

for the between option, specify the time range when the link will be
connected. Also, for off-hours (those hours that fall outside the time
range) specify the time (in minutes) that the link should remain con­nected when requested.

Issue 1 CRCS R6.0 April 1999 3

Upgrading from a Previous Release

Figure 1. MCU Link Administration window

15. The upgrade process is complete and you can begin using CRCS/
OpCenter.

4 Issue 1 CRCS R6.0 April 1999

CRCS/OpCenter and OpCenterSP Checklist

Pre-Installation Requirements

As a single-user dedicated system on a PC connected to one or two Lucent Tech­nologies MultiPoint Conferencing Units (MCU), CRCS/OpCenter or OpCenterSP
can be set up as either local or remote.

For a local connection, the distance between the PC and MCU must be less than
5000 feet. Distances beyond 5000 feet are considered remote. Also, if the PC is
not connected to the TN754B or TN2223 on the MCU side, the connection is
remote.

CRCS/OpCenter and OpCenterSP Checklist

Hardware Requirements

The system installed for single-user CRCS/OpCenter must be dedicated for
CRCS/OpCenter use only. The following hardware components are required:

n

266 MHz Pentium II CPU with 64 MB RAM or greater recommended (mini­mum 100 MHz Pentium with 32 MB RAM)

n

1024 by 768 pixel

n

One 17-inch monitor (minimum 15 inch)

n

2.5 GB hard disk with a high-speed drive and local bus controller (minimum

1.2 GB)

n

One 1.44 MB 3.5 inch floppy disk drive

n

One 6X CD-ROM drive (minimum 4X)

n

A COM1 serial port with a 25-pin connector or a 9-to-25 pin adapter, if the
COM1 port is 9 pin

n

A bus mouse or a serial mouse connected to a COM serial port

n

Optional laser or laser-quality printer connected to the LPT1 parallel port
and installed as the default printer

n

Optional (highly recommended) backup tape or high capacity removable
disk device and appropriate software for the backup

n

Slot for the fax hardware (optional)

Software Requirements

n

Microsoft Windows 95 or Windows NT 4.0 workstation with Service Pack 4

resolution,

256 color

, and

small fonts

Issue 1 CRCS R6.0 April 1999 5

Pre-Installation Requirements

Remote Configurations

For remote configurations where the MCU and CRCS/OpCenter or OpCenter SP
are not collocated, modem pooling is used (see "Appendix A: Modem Pooling" on
page 44). The modems must support a minimum of 9600 baud. Additional serial
ports may be required which must support non-shared interrupts.

Login and Passwords

Be sure you know the following information:

n

Login, password, dialed number and COM port for each MCU

n

CRCS or OpCenterSP Serial Number

n

Default administrator password and agent password

n

PC login and password, if applicable

Fax Option

Refer to "Faxmodem Installation" on page 32 for hardware and software require­ments for the optional fax feature.

6 Issue 1 CRCS R6.0 April 1999

Fax Option

Configuring the PC

Regardless of whether the connection between the PC and the MCU is local or
remote, you must supply the proper adapter to connect the COM1 port to the
RS232 cable.

Configure your CRCS/OpCenter or OpCenterSP PC as follows:

Figure 2. Microsoft Windows Control Panel Settings

1. With your PC powered on, select Start—Settings—Control Panel.

2. Perform each of the following steps:

n

select the Regional Setting and Keyboard to set both to English
(United States)

n

set the Display by selecting Settings to 1024 by 768 pixels, 256
color, and small fonts

Issue 1 CRCS R6.0 April 1999 7

Configuring the PC

.

Figure 3. Display Properties Window

n

select Modem and use the Modem Installation wizard to set the
modem COM ports. Click Add then Don’t detect my modem.
Under Manufacturers, choose Standard Modem Types. Under
Models, select Standard 9600 bps Modem. Choose the appropri­ate COM port: Communications Port (COM 1) for the MCU 1 con­nection and COM2 for the MCU 2 connection.

Figure 4. Install New Modem Wizard—Selecting the COM Port

8 Issue 1 CRCS R6.0 April 1999

Local Connection to MCU

Connecting the PC to the MCU

This procedure establishes the connection between the CRCS/OpCenter PC and
the data module or modem. For information about connecting the data module or
modem to the MCU, see the
PC using the standard serial ports to the modem or data module, follow these
steps:

Local Connection to MCU

The following hardware is required for a local MCU connection:

n

8400B data module (supplied)

NOTE:

7400B data module is supported from previous releases

n

M25B cable (not supplied)

n

9-pin-to-25 pin RS232 adapter (not supplied)

MCU Installation and Test

manual. To connect the

MCU

PBX
Wall
Jack

Phone Line
D8W Cord

Figure 5. Local Connection to the MCU

To
MCU

8400B/7400B

PC

COM 1

RS232
Cable

Port 1

Issue 1 CRCS R6.0 April 1999 9

Connecting the PC to the MCU

Remote Connection to MCU

When the PC is located remotely from the MCU, the MCU’s modem pooling capa­bility is ideal for connecting the data link needed to support CRCS/OpCenter. With
modem pooling, Hayes-compatible analog modems are used at the PC to connect
over the PTSN to the MCU. The MCU implements an external 7400A data module
combined with a 3800 modem running 9600 bps to provide conversion resources
needed to route the analog voice calls from the CRCS to the digital Netcon chan­nels in the MCU.

There are two types of conversion resources for modem pooling. The first type, an
integrated conversion resource, is a circuit pack which emulates a Trunk Data
Module connected to a 212A-type modem. The MCU does not support the inte­grated modem solution.

The second type, a combined conversion resource, is a separate Trunk Data
Module and modem administered as a unit. The Trunk Data Module component of
the conversion resource may be either a Modular Trunk Data Module (MTDM) or
a 7400A data module. The module connects to a digital port using Digital Commu­nications Protocol (DCP); the 3800 modem connects to an analog port on the
TN746B.

The MCU supports the Combined Modem Pooling Solution for use in remote con­nectivity between the MCU and the CRCS module whenever these components
are not collocated. See "Appendix A: Modem Pooling" for further installation
details.

Connection Procedure

1. Connect the COM1 port to the 8400B/7400B data module with an appropri­ate adapter, if necessary, and an M25B (EIA-232-D) cord or equivalent. If
using modem pooling, use an analog modem instead.

2. Use an RS232 cable (M25B) with a 25-pin female connector for the CRCS
PC or server and a 25-pin male connector for the analog modem (remote
connection) or data module (local connection).

3. If your supplied cable does not have the appropriate gender connectors,
use a gender changer to make the adjustments.

4. PC ports are usually labeled with the port number and type (serial or paral­lel), if not see your PC user manual for proper labeling. If the first serial port
is a 9-pin connector, connect a 9-pin-to-25-pin RS232 adapter (you sup­ply).

10 Issue 1 CRCS R6.0 April 1999

Connection Procedure

TDM Bus

TN746B

TN754B

DS1

Voice Grade
Data Call

Public/Private

Network

Analog

Analog

DCP

DCP

3800

3800
7400A
7400A

Modem

RS232Analog

Figure 6. Remote CRCS Connection to MCU (Modem Pooling)

5. Connect the female end of the RS232 cable to the male end of either an
adapter or the CRCS PC first serial port.

6. Connect the male end of the RS232 cable to the female 25-pin RS232 con­nector on the analog modem (remote connection) or data module (local
connection).

RS232

PC

5000 Feet

MCU

TN754B/

TN2224

B25A

Cross-Connect

at MDF

or Wall

Figure 7. Connecting the MCU to the CRCS PC

7. If you are using the 8400B data module (TN2224 required), go to step 8. If
you are using the 7400B data module, verify or change the following dip
switch settings:

n

For a standalone data-only 7400B data module, set dip switch #1 to
ON (UP), if no phone is connected. All other dip switches should be
set to the OFF position (DOWN);

n

If you are using a phone on a 7400B data module, set all dip
switches to the OFF position (DOWN).

8. Continue with "Checking the Modem Settings" on page 12.

103A

Jack

D8W M25B

7400B/8400B

PC

Issue 1 CRCS R6.0 April 1999 11

Connecting the PC to the MCU

Checking the Modem Settings

The last step before loading the CRCS program requires that you configure and
check the modem connection to the MCU.

1. From Microsoft Windows, select Start—Programs—Accessories—

HyperTerminal.

2. From the HyperTerminal window, click the Hypertrm.exe icon.

Figure 8. HyperTerminal Window Setting

3. Enter Test in the
select the first icon as shown. Click the OK button.

4. Click on Connect Using and select Direct to COM1.

12 Issue 1 CRCS R6.0 April 1999

Name

field of the Connection Description window and

Checking the Modem Settings

5. Choose the following settin gs:

n

Connector=Com1

n

Baud Rate=9600

n

Data Bits =8

n

Stop Bits=1

n

Parity=None

n

Flow Control=None

6. Click the OK button to save the changes. If you are using the 8400B data
module, continue to step 7. For the 7400B data module, skip to step 10.

7. Type ats24=001 to set the data module for standalone operation without a
telephone.

8. Remove power from the 8400B data module for 5 seconds.

9. Reconnect power to the 8400B data module. The red LED comes on
steady.

10. Type at and press Enter. The OK prompt appears. Type atdt and the dial
number you recorded earlier. Press Enter. The login prompt appears.

Figure 9. Connection Description Window

Issue 1 CRCS R6.0 April 1999 13

Connecting the PC to the MCU

11. When the login for the MCU displays, enter the login and password
assigned by the technical center during installation to verify that you have a
working CRCS to MCU link.

12. Type logoff and exit hyperterminal. Repeat this procedure to test COM2 if
you are controlling a second MCU.

NOTE:

If the MCU login does not display, verify that the MCU recognizes that
CRCS is active (from the MT check the
tomer-options form. It must be set to y).

13. Continue to "CRCS/OpCenter Software Installation" on page 15 to load the
CRCS/OpCenter program.

Scheduler Adjunct

field on the cus-

14 Issue 1 CRCS R6.0 April 1999