Avaya CS700, CS780 Administration And Maintenance

Meeting Exchange ® 5.0
Administration and Maintenance

CS700/CS780 Conferencing Server

04-602166

Issue 1

August 2007

© 2007 Avaya Inc. All Right s Re served.
Notice

While reasonable efforts were made to ensure that the infor mation in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.

Documentation disclaimer

Avaya Inc. is not responsible for any modifications, addition s, or deletions to
the original published version of this Documentation unless such modifications,
additions, or deletions were performed by Avaya.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linked third
party Web sites referenced elsewhere within this Documentation and Avaya
does not necessarily endorse the products, services, or information descri bed
or offered within them. We cannot guarantee that these lin ks will work all of the
time and we have no control over the availability of the linked pages.

License

USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S
ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL
LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT

http://support.avaya.com/LicenseInfo/

YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST
RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN
(10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.

Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the Documentation or other
materials available to End User. "Designated Processor" means a single
stand-alone computing device. "Server" means a Desi gnated Processor that
hosts a software application to be accessed by multiple users. "Software"
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone Products or
pre-installed on Hardware. "Hardware" means the standard hardwa re
Products, originally sold by Avaya and ultimately utilized by End User.

License Type(s):
Concurrent User License (CU). End User may install and use the Software

on multiple Designated Processors or one or more Servers, so long as only the
licensed number of Units are accessing and using the Software at any given
time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the
pricing of its licenses and can be, without limitation, an agent, port or user, an
e-mail or voice mail account in the name of a person or corporate function
(e.g., webmaster or helpdesk), or a directory entry in the administrati ve
database utilized by the Product that permits one user to interface with the
Software. Units may be linked to a specific, identified Server.

Database License (DL). Customer may install and use each copy of the
Software on one Server or on multiple Servers provided that each of the
Servers on which the Software is installed communicate with no more than a
single instance of the same database.

Copyright

Except where expressly stated otherwise, the Product is protected by copyrigh t
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense un der the
applicable law.

Third-party Components

Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements ("Third Party
Components"), which may contain terms that expand or limit rights to use
certain portions of the Product ("Third Party Terms"). I nformation identifying the
copyright holders of the Third Party Components and the Third Party Terms
that apply is available on Avaya's web site at:

http://support.avaya.com/ThirdPartyLicense/

For full information, please see the complete document, Avaya Third Part y
Terms, Document number 04-601558. To locate this document on the web si te,
simply go to http://www.avaya.com/support
number in the search box.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warran ty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the following Web site:

http://www.avaya.com/support

("GENERAL LICENSE TERMS"). IF

and search for the document

.

Avaya fraud intervention

If you suspect that you are being victimized by toll fraud and yo u need technical
assistance or support, call Technical Service Center Toll Fraud Intervention
Hotline at [phone] for the United States and Canada. Suspected
security vulnerabilities with Avaya Products should be reported to Avaya by
sending mail to: [e-mail].

For additional support telephone numbers, see the Avaya Web site:

http://www.avaya.com/support

Trademarks

Avaya and the Avaya logo are registered trademarks of Avaya Inc. in the
United States of America and ot her j urisdictions. Unless other wise provided in
this Documentation, marks identified by "®," "™" and "SM" are registered
marks, trademarks and service marks, respectively, of Avaya Inc. All other
trademarks are the property of their respective owners.

Document ordering information:

Avaya Publications Center
Voice: [phone]

Fax: [phone]

Write: Globalware Solutions

E-mail: [e-mail]
Order: 04-602166 Issue 1

For the most current versions of documentation, go to the Avaya support Web
site: http://www.avaya.com/support

1-800-457-1764 (Toll-free, U.S. and Canada only)

1-800-457-1764 (Toll-free, U.S. and Canada only)

200 Ward Hill Avenue
Haverhill, MA 01835 USA
Attention: Avaya Account Manager

July 2007

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

How to Get Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 1: System Features . . . . . . . . . . . . . . . . . . . . . . . . 15

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Audioconferencing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Attended Conferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Unattended Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

On-Demand Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Flex Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Conference Overbooking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

External Passcode Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Call Routing Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Conference Record and Playback . . . . . . . . . . . . . . . . . . . . . . . . 20

Sub-Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

How Participants Access and Exit a Sub-Conference. . . . . . . . . . . . 22

Role of the Conference Moderator . . . . . . . . . . . . . . . . . . . . . . 22

Conference Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Auto Blast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Saved Roster Recordings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

SNMPv2 Management Support . . . . . . . . . . . . . . . . . . . . . . . . . . 24

System Component Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Conference Call Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

How a Conferee Is Placed in a Conference . . . . . . . . . . . . . . . . . . . 25

Dialing Out to Conferees . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Conferee Dial In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Hardware Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Standard System Components . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Network/DSP Card Configurations . . . . . . . . . . . . . . . . . . . . . . 33

Media Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

RAID System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Issue 1 August 2007 3

Contents

Chapter 2: Configuring System-Wide Settings . . . . . . . . . . . . . . 45

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

System Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Time-sensitive Operator Assistance Configuration . . . . . . . . . . . . . . . . . 66

System Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Blast Dial Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Voice Message Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Operator Audio Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Flex Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 3: Configuring Channels and Call Routing. . . . . . . . . . . . 79

Establishing Port Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Inbound Port Groups (IPG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Understanding the PortGroupsIB.txt file. . . . . . . . . . . . . . . . . . . 80

Outbound Port Groups (OPG) . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Call Routing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Branding Calls using cbutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Adding Call Branding Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Modifying Call Branding Entries . . . . . . . . . . . . . . . . . . . . . . . . . 90

Deleting Call Branding Entries . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Listing the Entries in the Call Branding Table. . . . . . . . . . . . . . . . . . 91

Displaying a single call branding entry . . . . . . . . . . . . . . . . . . . 91

Displaying all call entries in the call brand table . . . . . . . . . . . . . . 91

Setting the Maximum DNIS Length System Configuration . . . . . . . . . . . 92

Displaying Help for cbutil . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Using Reservation Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Adding Reservation Groups . . . . . . . . . . . . . . . . . . . . . . . . . 93

Setting up the Call Branding Table Using Reservation Groups . . . . . . 93

Setting Up Flex Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Chapter 4: Managing Annunciator Messages . . . . . . . . . . . . . . . 95

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Prompt Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Annunciator Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Recording Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

About Annunciator Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Message Assignment Considerations . . . . . . . . . . . . . . . . . . . . . . 110

4 Administration and Maintenance of the CS700/CS780 Audio Conferencing Server

Managing Annunciator Text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

About Annunciator Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter 5: Using the System Management Interface . . . . . . . . . . . 115

Working with the Management Interface. . . . . . . . . . . . . . . . . . . . . . . 115

Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Menus and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

System Maintenance Options. . . . . . . . . . . . . . . . . . . . . . . . . 118

System Administrator Options . . . . . . . . . . . . . . . . . . . . . . . . 119

Working with Menus and Screens . . . . . . . . . . . . . . . . . . . . . . 122

Managing User Sign-Ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Creating Sign-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Viewing and Deleting Sign-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Reservation Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Entry and Exit Announcements. . . . . . . . . . . . . . . . . . . . . . . . . . 126

Scheduler Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Contents

Chapter 6: System Maintenance Options . . . . . . . . . . . . . . . . . 129

Configuring Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Configuring Trunks on T1/E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Synchronization and Monitoring . . . . . . . . . . . . . . . . . . . . . . . 132

Layer 1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Signaling Details and Configuration . . . . . . . . . . . . . . . . . . . . . 137

Set Board Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Trunk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Status View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Configuration and Switches Views . . . . . . . . . . . . . . . . . . . . . . 143

Trunk Enable and Disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

T3 Loopback Enable/Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

T3 Trunk Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Load the Outbound Port Group Configuration . . . . . . . . . . . . . . . . . 146

Load the Inbound Port Group Configuration . . . . . . . . . . . . . . . . . . 147

Configuring T3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

T3 Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

T3 Configuration Text File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

T3 Status Utility, t3stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Configuring the FDAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Specifying Flex-DAPI Channels. . . . . . . . . . . . . . . . . . . . . . . . . . 160

About Configuring Link Channels . . . . . . . . . . . . . . . . . . . . . . 162

Issue 1 August 2007 5

Contents

Configuring the System Hosts File. . . . . . . . . . . . . . . . . . . . . . . . . . 163

Adjusting the Channel Transmission Level . . . . . . . . . . . . . . . . . . . . . 164

Clearing Network Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

System Re-Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

System Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Chapter 7: Configuring Conference Scheduler . . . . . . . . . . . . . . 169

Working with the Conference Scheduler. . . . . . . . . . . . . . . . . . . . . . . 169

Configuring Warning Tones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Using External Passcode Validation . . . . . . . . . . . . . . . . . . . . . . . . . 177

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Validation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

XML Data Source Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 179

Validation Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

HTTP GET Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Test Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Passcode Validation Response. . . . . . . . . . . . . . . . . . . . . . . . 183

Mandatory billing codes for systems configured with Flex. . . . . . . . . 185

Stranded Participant Disconnect with EPV . . . . . . . . . . . . . . . . . 186

Keep Alive Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

The xCalcli Test Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Validating PIN Codes via a web browser. . . . . . . . . . . . . . . . . . . 188

Chapter 8: Managing Files . . . . . . . . . . . . . . . . . . . . . . . . . 191

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

About System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

System File Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

System File Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Working with the File Management Menu . . . . . . . . . . . . . . . . . . . . . . 195

File Management Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Working with File Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Automatically by the System . . . . . . . . . . . . . . . . . . . . . . . . . 198

File Management Menu Delete . . . . . . . . . . . . . . . . . . . . . . . . 198

Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Hard Disk Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Working with the Printer Management Menu . . . . . . . . . . . . . . . . . . . . 202

Printer Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

6 Administration and Maintenance of the CS700/CS780 Audio Conferencing Server

Cancel Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Display Printer Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Disabling Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Enabling Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Working with the Backup/Restore Menu. . . . . . . . . . . . . . . . . . . . . . . 204

Back Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Restore Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Saved Roster Audio Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Dial Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

LAN Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

User Transaction Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Modify Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

External Passcode Validation Log . . . . . . . . . . . . . . . . . . . . . . . . 215

Contents

Operator Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Specifying Filtering for a Operator Transaction View. . . . . . . . . . . . 217

Operator commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Network Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Digital Record/Playback (DRP) Files . . . . . . . . . . . . . . . . . . . . . . . . . 224

DRP Information in CODRs and Conference Reports. . . . . . . . . . . . . . 225

Converting DRP Files to WAV Files . . . . . . . . . . . . . . . . . . . . . . . 226

Traffic Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Managing System Files from a Remote Host . . . . . . . . . . . . . . . . . . . . 229

Using the Guest Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

UNIX Commands Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Remote Login and File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . 231

Registering Hosts to Use rlogin and rcp . . . . . . . . . . . . . . . . . . . 231

Using rlogin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Using Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Using rcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Using ftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Installing zlib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Installing OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Installing SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Issue 1 August 2007 7

Contents

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Improving System Security . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Additional Information About File Transfers. . . . . . . . . . . . . . . . . . . . . 246

DOS and UNIX Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Creating Files Off-line for Downloading . . . . . . . . . . . . . . . . . . . . . 247

Creating Tag Files Off-Line . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Creating Dial Lists Off-Line . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Copying Voice Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

About mlcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Starting mlcp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Transferring Voice Files between Systems . . . . . . . . . . . . . . . . . 250

Managing the PIN Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Creating PIN Code Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Pre-33 PIN Code File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Pre-33 PIN List file format . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

PIN Code File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

PIN List File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Copying the files to the system. . . . . . . . . . . . . . . . . . . . . . . . . . 256

Loading PIN Codes and PIN Lists to into Bridgedb . . . . . . . . . . . . . . . . . 256

Unloading PIN Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Chapter 9: Managing Reports . . . . . . . . . . . . . . . . . . . . . . . 261

Working with CDRs and CODRs . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

How the System Manages Detail Records . . . . . . . . . . . . . . . . . . . . 262

About CDR and CODR Formats. . . . . . . . . . . . . . . . . . . . . . . . . . 262

Configuring CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Configuring CODRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Multiple CODRs for One Conference ID . . . . . . . . . . . . . . . . . . . 284

Printing and Viewing CDRs and CODRs . . . . . . . . . . . . . . . . . . . . . 284

Printing and Viewing CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Printing and Viewing CODRs . . . . . . . . . . . . . . . . . . . . . . . . . 286

Printing CDRs and CODRs with More than 80 Columns . . . . . . . . . . 287

Alarm Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Conference Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Printing and Viewing Conference Reports. . . . . . . . . . . . . . . . . . . . 289

LAN Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

DRP Information in CODRs and Conference Reports. . . . . . . . . . . . . . 292

Real-time CDRs and CODRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

The autocdr Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

8 Administration and Maintenance of the CS700/CS780 Audio Conferencing Server

Retrieving Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Checking a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Auto CDR Process Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Preparing for Real-Time Export. . . . . . . . . . . . . . . . . . . . . . . . . . 299

Appendix A: Moderator and Participant Touchtone Commands. . . . . 301

Managing Avaya conferences using touchtone commands . . . . . . . . . . . . 302

Moderator Touchtone Commands . . . . . . . . . . . . . . . . . . . . . . 302

Participant Touchtone Commands . . . . . . . . . . . . . . . . . . . . . . 307

Managing flex conferences using touchtone commands. . . . . . . . . . . . . . 308

Modifying flex conference settings. . . . . . . . . . . . . . . . . . . . . . . . 308

Managing conferences using flex touchtone commands. . . . . . . . . . . . 310

Appendix B: Site Requirements . . . . . . . . . . . . . . . . . . . . . . 319

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

LAN Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Network Connection Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

About Hunt Group Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Maintenance Modem Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Contents

Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Appendix C: System Maintenance . . . . . . . . . . . . . . . . . . . . . 323

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Hot Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Hot Swapping a DSP Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Extracting a DSP Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Inserting a DSP Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Hot Swapping a PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Extracting the PRI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Inserting the PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Monthly Maintenance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Physical Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Cleaning the Air Filter Assembly . . . . . . . . . . . . . . . . . . . . . . . 328

Cleaning System Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

File Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Check Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Issue 1 August 2007 9

Contents

Delete Unwanted Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Clear Network Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Amend Date and Time to Reliable Source . . . . . . . . . . . . . . . . . . . . 329

Powering Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Using the Power On/Off Switch and Reset Button . . . . . . . . . . . . . . . 331

Appendix D: SNMP Agent Configuration and MIB Object Definitions . . 333

Configuring the Master Agent Configuration File . . . . . . . . . . . . . . . . . . 333

Appendix E: System and Log Messages. . . . . . . . . . . . . . . . . . 351

System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Log Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

0000–0999: Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

1000–1999: User/Usage Messages . . . . . . . . . . . . . . . . . . . . . . . . 363

2000–2999: Process Interface Messages. . . . . . . . . . . . . . . . . . . . . 364

3000–3999: UNIX System Error Messages . . . . . . . . . . . . . . . . . . . . 367

4000–4999: Hardware and Device Messages . . . . . . . . . . . . . . . . . . 371

API Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Appendix F: Trunk Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 379

Trunk Alarm Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Responding to Trunk Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

10 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Preface

This guide describes CS700/CS780 Conferencing Server features and how to configure
audioconferencing and network settings for the CS700/CS780 Conferencing Server
audioconferencing system, which is referred to as the “system” throughout the remainder of th is
guide unless specified otherwise. Although this guide includes basic information about system
hardware, maintenance procedures, and tasks you can perform from the system’s UNIX shell
interface, it primarily describes configuration options available from the system’s text-based
management interface and how to configure those options for your particular aud ioconferencing
requirements.

Audience

This guide is intended for qualified personnel who manage the system. It describes procedures
that have a direct impact on system functions. System administrators should have a working
knowledge of teleconferencing concepts, customer requirements, and, under some
circumstances, telecommunication protocols and specifications, TCP/IP protocols, and UNIX
commands.

Contact a technical support representative if you require assistance with configuring system
and audio conference settings or require in-depth training on using the CS700/CS780
Conferencing Server or Avaya desktop products.

Conventions

This guide uses the following conventions

:

Convention Description

SMALL CAPS Used for keystrokes. For example: Press the ESC key.

Courier

Courier Bold Used for text you enter at the command line.

Bold Used for menu options. For example: Select Call

Used for text the system displays.
For example:

For example:

Branding.

ERROR: Digit collection in progress.

rlogin host [-ec] [-8]

Issue 1 August 2007 11

Preface

Convention Description

Italic Used for references to publications. For example:

See Meeting Exchange 5.0 Bridge Talk User’s Guide.

Menu > Option Used to indicate the path to management interface options.

For example: Select System Administrator Main >

Configurations.

Note:

Note: Provides information of special importance.

Tip:

Tip: Provides information about alternative procedures or shortcuts.

!

CAUTION:

CAUTION: Provides information about actions that may disrupt or damage

system resources.

Related Documents

The following documents may provide additional information:

l Meeting Exchange 5.0 CS700/CS780 Conferencing Server Release Notes
l Meeting Exchange 5.0 Installing the S700/780 Conferencing Server
l Meeting Exchange 5.0 Relational Database Guide
l Meeting Exchange 5.0 Bridge Talk User’s Guide
l MultiSite for Meeting Exchange 5.0 Installation and Configuration Guide

12 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

How to Get Help

Information
Telephone [phone]

Web site http://www.avaya.com/support
US and Canada Technical Support *1-800-242-2121

International Technical Support [phone] (CS700/CS780)

How to Get Help

[phone]

E-mail:

[e-mail]

Fax: [phone]

[phone] (CS7000)
E-mail: [e-mail]

International Meeting Exchange
Technical Support

E-mail: [e-mail]

Issue 1 August 2007 13

Preface

14 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Chapter 1: System Features

Includes system configuration, audioconferencing, and hardware features. This chapter also
describes client applications supported by the system and provides an overview of the different
ways conferees gain access to conferences.

Introduction

The CS700/CS780 Conferencing Server is a scalable, multi-featured audioconferencing system
designed to support a variety of audioconferencing requirements including:

l Control of large conferences from a single user interface.
l Dynamic allocation of unused ports to form new conferences.
l Conference support (up to 100,000 ports) across geographically distributed CS700/

CS780.

l Web-based conference scheduling and management and data conferencing support.
l Specified-interval and ad hoc conference scheduling options.
l T1, E1, T1-ISDN, T3 CAS, and T3-ISDN network interface support.
l Operator assisted conferences and security code
l Flex conferencing allows service providers to set up and implement a mixture of

predefined call flows.

This chapter is organized as follows:

l System Configuration Overview on page 16 illustrates representative system feature

configurations.

l Audioconferencing Features on page 16 describes audioconference features and services

supported by the system.

l SNMPv2 Management Support on page 24 describes the system’s SNMP management

components.

l Conference Call Modes on page 25 describes the different ways in which conferees gain

access to conferences and introduces terminology used and concepts referred to
throughout this manual.

l Hardware Features on page 27 describes standard and optional system hardware

components.

Issue 1 August 2007 15

System Features

System Configuration Overview

The CS700/CS780 can be configured to conduct audio conferences using Public Switched
Telephone (PSTN) lines. Operator audio paths and links can be set up as conventional lines.

Figure 1

depicts various system components and features in a PSTN environment.

Figure 1: System Feature Configuration

Audioconference System

Console Port

Monitor Port

Keyboard Port

Analog Music Source

Revenue lines
Operator lines
Music (FDAPI)
Play/Record
Link lines

Digital Music Source

Analog Record/Playback

Linked Bridge

NICs/DSPs

Digital Record/Playback

LAN Ports

Ethernet

LAN Hub

Reserver
Enterprise

Billing

Web Conferencing
Server

PIN Code
Administration

External

Passcode Server

MultiSite

Web Portal
SNMPClient

RCA Jack

Modem Port

External

Modem

Operator
Data & Control

Operator
Audio

Network

Conferees

Audioconferencing Features

This section provides an overview of the system’s audioconference feature set. It also
introduces concepts and terminology used throughout the remainder of this manual.

16 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Attended Conferences

An attended conference is a conference in which an operator, using the Bridge Talk application
for managing and scheduling conferences, places callers into the conference and remains
available to assist conferees and moderators throughout its duration. The CS700/CS780 can be
configured for support operators, who can manage and monitor conferences alone or as part of
a team. They can also record annunciator messages, create and edit dial lists, dial out to
conference participants, record and playback recorded conference dialog, run question and
answer and polling sessions, and print conference reports directly from their workstations.

Attended conferences are scheduled and configured with the Conference Scheduler
application. To join an attended conference, conferees either dial in at a designated time or an
operator dials out to conferees. When dialing out, an operator can either dial a phone number
directly from the keyboard or launch an automated dialing function that dials numbers from a list
stored on the system (blast dialing).

See the Bridge Talk User’s Guide for details on the Conference Scheduler.

Audioconferencing Features

Unattended Conferences

An unattended conference is a conference in which conferees g ain access to and participate in
a conference without operator assistance. (Operator assistance, however, can be provided as
necessary .) When callers dial in to the unattended conference they are prompted to provide one
or more security codes to enter the conference. Once the system validates the code(s), the
caller is routed directly to the conference, but the system can also be configured to rou te callers
to a waiting queue to receive operator assistance.

Like attended conferences, specific conference features are set up using the Conference
Scheduler application from Bridge Talk. For instance, Auto Blast, a feature that enables
moderators to initiate a blast dial or enables the system to initiate a blast dial when the
moderator enters a conference is a conference-specific feature. System-wide operational
parameters for unattended conferences are specified by the Conference Scheduler
Configuration set up by a system administrator. See Chapter 7:

Scheduler on page 169 for details on configuring the Conference Scheduler and other

unattended conference features.
Other features that can be configured for unattended conferences on a system-wide basis

include:

l Auto Extend Duration — The system attempts to extend a conference beyond its

scheduled end time.

l Auto Extend Ports — The system attempts to allocate additional ports to conference to

accommodate additional conferees.

Configuring Conference

l Early Start Minutes — Conferees can enter a conference 1 to 30 minutes earlier than the

scheduled start time if ports are available.

Issue 1 August 2007 17

System Features

l External Passcode Validation — An external database validates the first access code

submitted for entry to a conference and then uploads conference parameters to the
system.

l PIN Mode — Specifies whether PIN code implementation is optional, whether non-unique

PIN codes are required (all conferees enter same PIN code), or whether unique PIN codes
are required (all conferee enter a different PIN code).

On-Demand Conferences

The system enables you to designate a percentage of system lines for On-Demand
conferences — ad hoc, unattended conferences that can be convened on a first-come,
first-served basis during a pre-scheduled time period. On-Demand conferences are configured
using the Conference Scheduler application. Schedulers can schedule one-time conferences or
a reoccurring conferences. An On-Demand conference can, for example, extend continuously
(24 hours a day, seven days a week), 9 AM to 5 PM Monday through Friday, 1 AM to 6 AM
every Saturday, 9 AM to 5 PM on 10th of each month, 12 AM to 12 PM on August 31, 2007, or
over any other span during which conferees want to insure lines are available for a conference
at a moment’s notice. See Meeting Exchange 5.0 Bridge Talk User’s Guide for details on
scheduling On-Demand conferences.

Like other unattended conferences, an On-Demand conference begins when the first conferee
calls in and provides a valid access code, and an On-Demand conference customer can
convene as many consecutive conferences as they want within the specified time period.
However, lines for On-Demand conferences are available on a first-come, first-served basis;
that is, successful convocation of On-Demand conferences is dependent on the availability of
lines for On-Demand conferences. See Configuring Conference Scheduler
details on apportioning a percentage of syste m lin es for On-de mand co nferen ces tha t will meet
your requirements.

Flex Conferences

Flex is a type of unattended, on-demand conference in which participants can join a conference
directly. This “reservationless” conference uses a profile to keep track of all the selected
conference features, such as Hang up or Name Record/Playback.

Once the system administrator has defined the settings in a profile, participants can join Flex
conferences on a first-come, first-served basis. However, there can be only one moderator
(leader). Leaders can change profile settings before a conference begins, and create, control,
and end a conference call using DTMF telephone commands. For example, moderators can:

l SPECIFY A CONFERENCE PASSWORD. Leaders can optionally add another layer of

security by specifying a passcode that participants must enter before they can join the
conference.This password is valid only for the duration of the conference and is not stored
on the system.

on page 169 for

18 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Audioconferencing Features

Note:

Note: If Music is turned on for the conference, participants who arrive early wait on

standby. If the moderator specifies a passcode upon arrival, the waiting
participants must enter the passcode before they are allowed into the
conference. However, if Music is turned off, participants who arrive before the
moderator can enter the conference without the passcode.

l CHANGE CONFERENCE OPTIONS. When a participant enters a leader PIN code and

assumes leader (moderator) status, the system immediately prompts the lead er to press 1
to start the conference. However, the leader can press 2 to change several conference
options before the conference starts. After changing options, the leader can press 1 to
start the conference.

l USE SPECIAL STAR COMMANDS. Flex conferences require that leaders and

participants use special DTMF commands during the conference. A leader can create,
control, and end a conference call using keypad star commands, which toggle on and off.

For more information on the default call flow and Flex options, see Reservation Features
page 125. For instructions on configuring bridge settings for Flex conferences, see Flex

Configuration Settings on page 76.

For more information on scheduling Flex conferences, refer to the Bridge Talk User’s Guide.

Note:

Note: Flex does not support Polling or Q&A.

Conference Overbooking

The system’s overbooking feature enables you to specify the percentage of system lines you
want available for Conference Overbooking. Overbooking enables you to schedule more
conference lines than the system supports. In light of the fact that some conference p articip ants
do not attend conferences as scheduled, this feature ensures that those scheduled yet unused
lines are immediately available for other conferences.

Refer to Chapter 7:
a percentage of system lines for Conference Overbooking that will meet your requirements.

Configuring Conference Scheduler on page 169 for details on apportioning

on

External Passcode Validation

External Passcode Validation (EPV) is an optional feature that enables the system to validate
conference security passcodes (conferee and moderator codes) for unattended conferences
from an external database (e.g., Oracle database) instead of from the system database.
Basically, the system submits to an external database the passcode entered by the first caller
(moderator or conferee) who attempts to enter a conference. Upon determining the code is

Issue 1 August 2007 19

System Features

valid, the database provides the system the conference information required to convene the
conference and validate passcodes entered by subsequent callers.

See Using External Passcode Validation

on page 177 for details.

Call Routing Service

The Call Routing Service provides automated processing of incoming calls based on either
DNIS or DDI digits. Services include:

l Call branding — Lets you assign conference-specific greeting and instructional messages

to callers.

l Call routing — Lets you specify the method used to process a call.

Conference Record and Playback

The system supports two modes of conference record and playback:

l Digital Record/Playback (DRP) — DRP enables conference operators and moderators to

digitally record up to 12 hours of dialog per conference and play it back. Up to 1,000
simultaneous recordings and playbacks can be running on a system. 770 hours of digit ally
recorded conference dialog can be stored on either the system’s removable hard drive or
the RAID system, depending on how the system is configured.

l Analog Record/Playback — Using FDAPI, the system can support up to 48 analog record/

playback channels. Conferences are recorded on and played back from an external
audio-recording device. The audio recording device is accessed over a dedicated phone
line that has been set up for that purpose in the FDAPI configuration (see C

FDAPI on page 159).

l Off-Bridge Recording — This mode allows the system to connect to an external recording

device. The time limit is determined by the recording device.

See the Bridge Talk User’s Guide for details on recording and playing back conference dialog.

Sub-Conferences

Sub-conferencing enables a group of participants to leave a main conference to discuss topics
of a confidential nature or that are unrelated to the topic of discussion in the main conference.
The CS700/CS780 can be configured to allow a conferee, a moderator, or both to convene a
sub-conference from a main conference. Both conferees and moderators, however, can join a
sub-conference regardless of which type of conference participant started the conference.

onfiguring the

20 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Audioconferencing Features

The system allows up to nine concurrent sub-conferences to be created from a main
conference, but it does not impose any limits on the number of successive sub-conferences that
can be created. The system does not permit creation of a sub-conference from another.

See System Configuration

on page 45 for details on enabling the sub-conference feature o n the

system.
Although it inherits most of the configuration settings of the main conference from which it is

created, a sub-conference is essentially a distinct conference:

l A sub-conference can be secured (no one allowed entry into the conference) by a

moderator in the sub-conference. Whether or not a main conference is secured has no
effect on the sub-conference.

l Once a moderator secures a main conference, participants in a sub-conference may not

rejoin the main conference until the moderator unsecures it. When the participant attempts
to rejoin a secured main conference:

l the system plays the moderator a notification message such as, “Your conference is

currently secured. A participant of the Sub Conference is requesting re-e ntry. Please turn
off security to unlock the conference.”

l the participant hears a message such as, “The main conference has been secured and

entry is not allowed at this time. The moderator has been notified of your request, please
stand by...” Once the moderator removes the security, the system plays a message such
as, “Re-entry to the main conference is now allowed.

l A sub-conference’s roster is played independently of its main conference roster.
l The system generates a Conference Detail Record (CODR) for each sub-conference

”

created from a main conference. (A CODR is a daily report that contains data from all
conferences that occurred for the day. See CODR Configuration, screen 1

on page 274 for

details.)
Important information about main and sub-conference CODRs:

l The values for the Cross Ref fields and the values for the Conference ID fields for main

and sub-conference CODRs are identical. This enables billing or auditing personnel to
correctly associate sub-conferences with main conferences.

l The User Conf Type field in a sub-conference CODR identifies the conference as a

sub-conference.

l Sub-conferences are recorded separately from the main conference.

The following system-wide conference features applicable to a main conference are not
applicable to a sub-conference:

l Auto-Extend-Ports — The system does not extend ports for a sub-conference. Ports

added to a main conference are also available for any new or existing sub-conference
created from the main conference. Any additional participants who wish to join a
sub-conference can enter the main conference and then transfer to the sub-conference.

Issue 1 August 2007 21

System Features

l Auto-Extend-Duration — The system does not allow individual extension of a

sub-conference. The duration of an existing sub-conference extends as long as the main
conference duration extends.

How Participants Access and Exit a Sub-Conference

A conference participant (moderator or confer ee) uses the keypad command, *93, to create and
transfer to and from a sub-conference:

l When a participant in a default call flow main conference presses *93 plus a digit 1- 9,

where the digit corresponds to the subconference, the system creates a sub-conference
or, if sub-conference has already been created, the system routes the participant to that
sub-conference.

l Participant lines are transferred to the sub-conference and thus subtracted from the main

conference. The Call Detail Record (CDR) the system generates for each line in a
conference indicates that the line was transferred.

l When a participant presses *930 while in the sub-conference, the system returns the

participant line to the main conference.

A sub-conference ends when all participants have left the sub-conference.

Tip:

Tip: For a Flex conference, one sub-conference only is supported. Press *93 to

access a Flex sub-conference.

Role of the Conference Moderator

A sub-conference “shares” the moderator(s) from the main conference. That is, no additional
moderators are required to manage a sub-conference; moderators can enter and exit a
sub-conference at will.

Questions and answers about the role of a moderator in a main conference and a
sub-conference:

l What happens when the only or last moderator in the main conference joins a

sub-conference and the system is configured to automatically end a conference (Auto
Hang-up feature enabled) when the last moderator in the conference disconnects?

l The system does not end the main conference. The feature is applicable only when the

last moderator leaves the main conference.

l What happens when the only or last moderator in the main conference disconnects from a

sub-conference and the system is configured to automatically end a conference (Auto
Hang-up feature) when the last moderator in the conference disconnects?

l The system ends both the main conference and the sub-conference.
l When a moderator secures a main conference (disallows entry to any additional

participants) is the sub-conference secured as well?

22 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

l No. A moderator can secure a sub-conference only while in the sub-conference.
l Can participants become stranded in a sub-conference (unable to transfer back to the

main conference) if the only moderator transfers from a secured main conference to
sub-conference?

l No. An annunciator message notifies the moderator to unsecure the main conference

before transferring to the sub-conference. The moderator cannot transfer to the
sub-conference until the main conference is unsecured.

l Can participants become stranded in a sub-conference (unable to transfer back to the

main conference) if the only moderator disconnects from a secured main conference and
the Auto Hang-up feature is not in effect (the conference continues as scheduled)?

This scenario is possible. If a conference requirement is that all particip ants must b e able to
re-join a main conference before it ends, the moderator must ensure that all participants can
re-join the conference by not securing the conference prior to hanging up.

Conference Scheduler

Audioconferencing Features

The Conference Scheduler, which can be accessed from the Bridge Talk application, enables
you to schedule every type of conference supported by the system — attended, unattended,
and on-demand conferences. The system stores and automatically activates schedules.
Reservations that do not include an end date are considered to be valid for as long as the sytem
is active.

The Scheduler lets you specify conference setup information such as, but not limited to, start
time, end time, and number of lines. Also, the Scheduler notifies you if it detects scheduling
conflicts such as those related to the availability of lines or security codes, and it allows you to
modify the schedule as required. You can use the Scheduler to modify scheduled conference
settings at any time prior to a conference, and you can also modify the number of lines and the
duration of the conference and its security code while a conference is in progress. The
Scheduler also enables you to view and print scheduling reports and purge expired conference
information.

See the Bridge Talk User’s Guide for Conference Scheduler details.

Auto Blast

The optional Auto Blast feature provides blast-dial capability for moderators in unattended
conferences. From the Conference Scheduler application, Auto Blast can be disabled, set for
manual implementation, or set for automatic implementation.

l Manual implementation — The conference moderator enters *92 on the telephone keypad

to initiate the blast dial.

Issue 1 August 2007 23

System Features

l Automatic implementation — The system initiates the blast dial when the first moderator

enters the conference via a moderator code.

The total number of blast dial recipients called from the blast dial list is dependent on the
maximum number of lines available for the conference. A system message announces to the
conference how many numbers from the dial list are dialed.

See Blast Dial Parameters

on page 69 for information about blast dial settings, including
important details on setting the CLPG (call in progress) timeout period for Auto Blast used in
unattended conferences.

Saved Roster Recordings

The system can be configured to generate and save an audio recording of information provided
by conference participants (name, af filiation, and so on). For conferences that include the r oster
recording feature, participants provide the information in response to an audio prompt when
they attempt to enter a conference.

A raw audio file is created and saved on the system as soon as a participant records his name.
Each time a participant records his name, the information is appended to the raw audio file—so
the file grows as conference participation grows. The audio files are saved in pcm format.

See System Configuration

on page 45 for details on enabling roster recordings. See Saved

Roster Audio Files on page 206 for more information on roster recording files.

SNMPv2 Management Support

The system’s SNMPv2 management agent provides the interface betwe en the system MIB and
SNMP-compliant network management applications that connect to the system to monitor
system, runtime, telecom trunk, and LAN resources. Comprising a combination of select MIB-II
objects and platform-specific object, the MIB provides remote monitoring support for crucial
system components.

Unsolicited data from SNMP trap objects notify network management stations of actual and
potential problems with system, processor, memory, and network components (see System

Component Alerts on page 25. Current, average, and accumulated data from the MIB’s

read-only objects derived and monitored by management applications can be used by system
and network administrators to evaluate system performance. Most importantly, both unsolicited
and solicited data from the MIB can serve as input for automated alarm notification or
trouble-ticket applications used in conjunction with or part of the network management platform.

See SNMP Agent Configuration and MIB Object Definitions

on page 333 for agent configuration

guidelines and a list of MIB object definitions.
Contact Customer Support for assistance with enabling and configuring SNMP support on your

system.

24 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

System Component Alerts

The system MIB’s trap objects alert network managers about potential and actual problems with
system elements and processes:

l Core system resources — Fan, temperature, power supply.
l Runtime resources — Disk space (90% threshold), memory (75% threshold), host and

DSP processor, NICs.

l Telco resources — Signaling and frames.
l LAN resources — Link down and transmit and receive errors.

Conference Call Modes

A call mode is the method by which a conferee gains access to a conference. The system
supports several call modes to accommodate various customer requirements. A conference
can be conducted several ways. The system accommodates attended and unattended
conferences simultaneously, and even allows semi-attended calls, depending upon system
configuration.

Conference Call Modes

In an attended conference, the operator greets the participant and places them directly into a
conference. No passcode is required. In an unattended conference the participant enters a
passcode to be placed directly into a conference. No operator is required. Operators can
manage participants in both attended and unattended conferences.

For example, if you have an operator, you can arrange unattended coded conferences, which
allow conferees, who forget their conference codes, to reach an operator, rather than being
automatically disconnected. In addition, you can run a conference that is unattended except for
an operator initiated blast dial.

The system also permits combinations of certain modes. For example, the moderator of an
attended dial-in conference can ask an operator to dial out to a conferee who has not dialed in.

How a Conferee Is Placed in a Conference

Conferees gain access to conferences in eight different ways.

l Five ways involve dial-outs from the system to the conferee.
l Three ways involve dial-ins from conferees to the system.

Issue 1 August 2007 25

System Features

Dialing Out to Conferees

There are different ways for operators and moderators to di al out to a participant:

Operator Dial Out

l Immediate — An operator manually dials a phone number directly from the keyboard.
l Fastdial — An operator dials participants from a list stored on the system.
l Blast Direct — An operator has the system simultaneously dial an entire list of numbers.

Conferees are automatically placed in the conference after they answer the call and enter
a “1.”

l Blast Direct to Conference—An operator invokes the system’s blast dial feature to

simultaneously dial an entire list of numbers. The system places answered lines directly
into a conference.

l Blast Coded — An operator invokes the system’s blast dial feature to simultaneously dial

an entire list of numbers. The system prompts conferees for a conference code, befo re the
system places them in the conference.

Moderator Dial Out

l Originator Dial Out (ODO) — A moderator dials out to a conferee during the conference.
l Automatic Blast—As soon as the moderator joins the conference, the system dials a pre-

configured blast list.

l Manual Blast—A moderator initiates dialout to a preconfigured list using DTMF

commands.

Conferee Dial In

The system provides three methods of processing conferee calls to the system:

l Direct — The system automatically routes incoming callers directly to a specified

conference. No access code is required.

l Coded (Unattended) — The system requests that a caller enter a pre-specified access

code to enter the conference. The system automatically routes the caller to the specified
conference. An additional security layer is available by using PIN codes.

l Attended — Operator places callers into the conference.

While not all calls require an operator to respond to incoming calls, there is often the need to
have one or more operators available to initiate and/or process calls, and to be availa ble to help
moderators or conferees needing assistance.

26 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Hardware Features

Table 1 summarizes the operator involvement in the various conference call modes.

.

Table 1: Operator Involvement in Various Conference Call Modes

Conference
Call Mode

Direct No No No No

Coded No No No Yes

Dial In

Attended No Yes Yes No

Immediate Yes Yes Yes No

Fastdial Yes Yes Yes No

Blast Direct Yes No Yes No

Blast Coded Yes No Yes Yes

Dial Out

Hardware Features

The foundation of the CS700/CS780 is the scalable, modular chassis, which can be rack
mounted or simply placed on a suitably sturdy structure. (See Site Requirements
for details.) It accommodates all hardware, software, and environment al components necessary
to support the system’s audioconferencing features and basic data storage requirements.

Operator
Initiated?

Operator
Processed?

Operator
Attended?

Code
Required?

on page 319

CS700/CS780 Conferencing Server hardware components:

l Te lecommunication Network Interface Cards (NICs), each with eight RJ-45 ports that

support scalable T1, T1-ISDN, or E1 channel configurations.

l The CS700 supports up to six NICs (1152 T1, 1104 T1-ISDN PRI, and 1200 E1

channels).

l The CS780 supports up to 3 NICs (576 TI, 552 T1-ISDN PRI, and 600 E1 channels).

l Up to three (3) hot-swappable Digital Signal Processing (DSP) cards in the CS780, and six

(6) in the CS700. DSP cards process audioconference operations. Use these equations to
calculate the number of DSP resources:

l T1 systems require T1 = 1 DSP board.
l T3 systems require T3 = 3n DSP +1, where n is the number of T3 cards.

Issue 1 August 2007 27

System Features

l CPU host processor card with a minimum processing power and RAM to support the

installed system features. Table 2
various system features and Table 3

.

Table 2: Supported T1/E1 Configurations

identifies the supported T1/E1 that are required for

the supported T3 system configurations

CS CPU MHz MEM

Meg

Max #
Ports

700 5550 700 512 1152

700 5550 700 512 1152
700 5550 700 512 1152
780 5550 700 512 576
780 5550 700 512 576
700 5551 1000 1024 1152

700 5551 1000 1024 1152
700 5551 1000 1024 1152
700 5551 1000 1024 2016

700 5551 1000 1024 2016

700 5551 1000 1024 2016
700 5551 1000 1024 2016
780 5551 1000 1024 576

780 5551 1000 1024 576
780 5551 1000 1024 576

NRP Calls/

Call Flow

second

1

5 cps,

5Flex

15 sec rec

1

1
2
2

1

NO 6 Flex
NO 8 Default
NO 8 Default
NO 6 Flex

5 cps,

5Flex

15 sec rec

1

1

3

NO 6 Flex
NO 8 Default

5 cps,

5 Default

15 sec rec

3

5 cps,

5Flex

15 sec rec

3

3
2

NO 6 Flex
NO 8 Default

5 cps,

5 Default

15 sec rec

2
2

NO 8 Default
NO 6 Flext

1. 1200 ports for an E1 configuration.

2. <=600 ports for E1 configuration.

3. 1932 ports for T3 ISDN configuration.

The CPU card can be configured to include a hard drive and 3.5” disk drive if a RAID
system is not used. It also includes two DB9 serial ports, a keyboard /mouse port, a SVGA
port, a USB port, and two RJ-45 LAN ports that are each configurable for 10 or 100 Mbps
Ethernet connections.

28 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server

Hardware Features

.

Table 3: Supported T3 Configurations

Mixed Configuration

Total

System CPU

PortsT1 T3 ISDN T3 CAS

CS700 5551 0 1932 0 1932
CS700 5551 0 1932 0 1932
CS700 5551 0 1932 0 1932
CS700 5551 0 1932 0 1932
CS700 5551 0 644 1344 1988
CS700 5551 0 1288 672 1960
CS700 5551 0 0 2016 2016
CS700 5551 768 0 672 1440
CS700 5551 768 644 0 1412
CS700 5551 384 0 1344 1728
CS700 5551 384 1288 0 1672
CS700 5551 0 0 2016 2016
CS780 5551 0 0 672 672
CS780 5551 0 644 0 644

Redundant, hot-swappable power supplies: up to four for the CS700; up to two for the

l

CS780.

l RCA Jack (on a DSP card) for connection to analog music source (CD player for

example).

l Removable hard drive (for storing digitally recorded conferences and system file backups).

Note:

Note: Your system might be configured with a RAID drive instead of a removable hard

drive. See RAID System

on page 38 for more information.

Standard System Components

Figure 2 shows CS700 components for a non-RAID configuration and Figure 3 shows CS780

components for a non-RAID drive configuration. See RAID System
on a RAID configurations.

on page 38 for information

Issue 1 August 2007 29

System Features

Note:

Note: The system has video and keyboard connections on the host CPU and on the

Serial ports are available on the front and the back of the system, but only one of the two ports
can be functional. If the front port is in use, the rear port is disabled, and if the rear port is used ,
the front port is disabled. LAN ports are available on the front and the back of the system.
When the front port is in use, the rear port is disabled, and if the rear port is u sed, the fro nt po rt
is disabled.

optional embedded CPU (eCPU). These connections are used only for initial
startup of the system during installation and for local system diagnostics and
troubleshooting. The serial and ethernet ports on the NIC card and the serial port
on the DSP card are only used by the CS700/CS780 developers for application
development.

30 Administration and Maintenance of the CS700/CS780 Audio Conferenc ing Server