Meeting Exchange ® 5.1 Administration and Maintenance Guide CS700/CS780 Conferencing Server
November 2008
04-602673
Issue 1
© 2008 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information 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, additions, 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 described
or offered within them. We cannot guarantee that these links 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
LI CE NS E T ER MS AVAI LA BL E O N T HE AVAYA W EB SI TE AT
http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF
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 Designated 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 hardware
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 administrative
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 copyright
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense under 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"). Information 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 Party
Terms, Document number 04-601558. To locate this document on the website,
simply go to
number in the search box.
Warr anty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. 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.
http://www.avaya.com/support and search for the document
Avaya fraud intervention
If you suspect that you are being victimized by toll fraud and you need technical
assistance or support, call Technical Service Center Toll Fraud Intervention
Hotline at +1-800-643-2353 for the United States and Canada. Suspected
security vulnerabilities with Avaya Products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
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 other jurisdictions. Unless otherwise 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 Information
For the most current versions of documentation, go to the Avaya support Web
http://www.avaya.com/support
site:
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Attended Conferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Unattended Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
On-Demand Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Flex Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Conference Overbooking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
External Passcode Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Call Routing Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Conference Record and Playback . . . . . . . . . . . . . . . . . . . . . . . . 20
Sub-Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
How Participants Access and Exit a Sub-Conference. . . . . . . . . . . . 22
Role of the Conference Moderator . . . . . . . . . . . . . . . . . . . . . . 22
Conference Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Auto Blast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Saved Roster Recordings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
SNMPv2 Management Support . . . . . . . . . . . . . . . . . . . . . . . . . . 24
System Component Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Conference Call Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
How a Conferee Is Placed in a Conference . . . . . . . . . . . . . . . . . . . 26
Dialing Out to Conferees . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Conferee Dial In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Hardware Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Standard System Components . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Network/DSP Card Configurations . . . . . . . . . . . . . . . . . . . . . . 34
Media Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
RAID System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Issue 1 November 2008 3
Contents
Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
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
Accessing cbutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Adding Call Branding Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Modifying Call Branding Entries . . . . . . . . . . . . . . . . . . . . . . . . . 91
Deleting Call Branding Entries . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Listing the Entries in the Call Branding Table . . . . . . . . . . . . . . . . . . 91
Displaying a single call branding entry . . . . . . . . . . . . . . . . . . . 92
Displaying all call entries in the call brand table . . . . . . . . . . . . . . 92
Setting the Maximum DNIS Length System Configuration . . . . . . . . . . . 93
Displaying Help for cbutil . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Using Reservation Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Adding Reservation Groups . . . . . . . . . . . . . . . . . . . . . . . . . 94
Setting up the Call Branding Table Using Reservation Groups . . . . . . 94
Setting Up Flex Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 4: Managing Annunciator Messages . . . . . . . . . . . . . . . 97
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Prompt Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Installing non-default prompt sets . . . . . . . . . . . . . . . . . . . . . . . . 99
4 Administration and Maintenance of the S700/780 Audio Conferencing Server
Annunciator Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Recording Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
About Annunciator Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Message Assignment Considerations . . . . . . . . . . . . . . . . . . . . . . 114
Managing Annunciator Text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
About Annunciator Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Chapter 5: Using the System Management Interface . . . . . . . . . . . 119
Working with the Management Interface. . . . . . . . . . . . . . . . . . . . . . . 119
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Menus and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
System Maintenance Options. . . . . . . . . . . . . . . . . . . . . . . . . 122
System Administrator Options . . . . . . . . . . . . . . . . . . . . . . . . 123
Working with Menus and Screens . . . . . . . . . . . . . . . . . . . . . . 126
Managing User Sign-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating Sign-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Viewing and Deleting Sign-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Reservation Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Entry and Exit Announcements. . . . . . . . . . . . . . . . . . . . . . . . . . 130
Scheduler Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Contents
Chapter 6: System Maintenance Options . . . . . . . . . . . . . . . . . 133
Configuring Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Configuring Trunks on T1/E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Synchronization and Monitoring . . . . . . . . . . . . . . . . . . . . . . . 136
Layer 1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Signaling Details and Configuration . . . . . . . . . . . . . . . . . . . . . 141
Set Board Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Trunk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Configuration and Switches Views . . . . . . . . . . . . . . . . . . . . . . 147
Trunk Enable and Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
T3 Loopback Enable/Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
T3 Trunk Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Load the Outbound Port Group Configuration . . . . . . . . . . . . . . . . . 150
Load the Inbound Port Group Configuration . . . . . . . . . . . . . . . . . . 151
Configuring T3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
T3 Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
T3 Configuration Text File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Issue 1 November 2008 5
Contents
T3 Status Utility, t3stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Configuring the FDAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Specifying Flex-DAPI Channels. . . . . . . . . . . . . . . . . . . . . . . . . . 164
About Configuring Link Channels . . . . . . . . . . . . . . . . . . . . . . 166
Configuring the System Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Adjusting the Channel Transmission Level . . . . . . . . . . . . . . . . . . . . . 168
System Re-Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
System Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Chapter 7: Configuring Conference Scheduler . . . . . . . . . . . . . . 173
Working with the Conference Scheduler. . . . . . . . . . . . . . . . . . . . . . . 173
Configuring Warning Tones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Using External Passcode Validation . . . . . . . . . . . . . . . . . . . . . . . . . 181
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Validation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
XML Data Source Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 183
Validation Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
HTTP GET Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Test Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Passcode Validation Response. . . . . . . . . . . . . . . . . . . . . . . . 186
Billing code values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Mandatory billing codes for systems configured with Flex. . . . . . . . . 190
Stranded Participant Disconnect with EPV . . . . . . . . . . . . . . . . . 190
Keep Alive Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
The xCalcli Test Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Validating PIN Codes via a web browser . . . . . . . . . . . . . . . . . . . 192
Chapter 8: Managing Files . . . . . . . . . . . . . . . . . . . . . . . . . 195
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
About System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
System File Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
System File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Working with the File Management Menu . . . . . . . . . . . . . . . . . . . . . . 199
File Management Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Working with File Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Automatically by the System . . . . . . . . . . . . . . . . . . . . . . . . . 202
File Management Menu Delete . . . . . . . . . . . . . . . . . . . . . . . . 202
Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6 Administration and Maintenance of the S700/780 Audio Conferencing Server
View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Hard Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Working with the Printer Management Menu . . . . . . . . . . . . . . . . . . . . 206
Printer Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Cancel Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Display Printer Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Disabling Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Enabling Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Working with the Backup/Restore Menu . . . . . . . . . . . . . . . . . . . . . . . 208
Back Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Restore Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Saved Roster Audio Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Dial Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
LAN Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
User Transaction Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Modify Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
External Passcode Validation Log . . . . . . . . . . . . . . . . . . . . . . . . 219
Operator Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Specifying Filtering for a Operator Transaction View . . . . . . . . . . . . 221
Operator commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Digital Record/Playback (DRP) Files . . . . . . . . . . . . . . . . . . . . . . . . . 227
DRP Information in CODRs and Conference Reports . . . . . . . . . . . . . . 228
Converting DRP Files to WAV Files . . . . . . . . . . . . . . . . . . . . . . . 229
Contents
Traffic Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Managing System Files from a Remote Host . . . . . . . . . . . . . . . . . . . . 232
Using the Guest Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
UNIX Commands Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Remote Login and File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . 234
Registering Hosts to Use rlogin and rcp . . . . . . . . . . . . . . . . . . . 234
Using rlogin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Using Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Using rcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Using ftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Installing zlib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Issue 1 November 2008 7
Contents
Installing OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Installing SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Improving System Security . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Additional Information About File Transfers. . . . . . . . . . . . . . . . . . . . . 249
DOS and UNIX Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Creating Files Off-line for Downloading . . . . . . . . . . . . . . . . . . . . . 250
Creating Tag Files Off-Line . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Creating Dial Lists Off-Line . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Copying Voice Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
About mlcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Starting mlcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Transferring Voice Files between Systems . . . . . . . . . . . . . . . . . 253
Managing the PIN Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Creating PIN Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Pre-33 PIN Code File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Pre-33 PIN List file format . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
PIN Code File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
PIN List File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Copying the files to the system. . . . . . . . . . . . . . . . . . . . . . . . . . 259
Loading PIN Codes and PIN Lists to into Bridgedb . . . . . . . . . . . . . . . . . 259
Unloading PIN Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Chapter 9: Managing Reports . . . . . . . . . . . . . . . . . . . . . . . 263
Working with CDRs and CODRs . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
How the System Manages Detail Records . . . . . . . . . . . . . . . . . . . . 264
About CDR and CODR Formats. . . . . . . . . . . . . . . . . . . . . . . . . . 264
Configuring CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Configuring CODRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Multiple CODRs for One Conference ID . . . . . . . . . . . . . . . . . . . 287
Printing and Viewing CDRs and CODRs . . . . . . . . . . . . . . . . . . . . . 288
Printing and Viewing CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Printing and Viewing CODRs . . . . . . . . . . . . . . . . . . . . . . . . . 289
Printing CDRs and CODRs with More than 80 Columns . . . . . . . . . . 290
Alarm Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Conference Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Printing and Viewing Conference Reports . . . . . . . . . . . . . . . . . . . . 292
LAN Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
DRP Information in CODRs and Conference Reports . . . . . . . . . . . . . . 295
8 Administration and Maintenance of the S700/780 Audio Conferencing Server
Real-time CDRs and CODRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
The autocdr Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Retrieving Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Checking a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Auto CDR Process Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Preparing for Real-Time Export. . . . . . . . . . . . . . . . . . . . . . . . . . 302
Appendix A: Moderator and Participant Touchtone Commands . . . . . 301
Managing 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
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
LAN Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Network Connection Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
About Hunt Group Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Maintenance Modem Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
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
Issue 1 November 2008 9
Contents
Cleaning System Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
File Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Check Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Delete Unwanted Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Amend Date and Time to Reliable Source . . . . . . . . . . . . . . . . . . . . 329
Powering Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Appendix F: Trunk Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 379
Trunk Alarm Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Responding to Trunk Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
10 Administration and Maintenance of the S700/780 Audio Conferencing 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 this
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 audioconferencing
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: ERROR: Digit collection in progress.
For example: rlogin host [-ec] [-8]
Branding.
Issue 1 November 2008 11
Preface
Convention Description
Italic Used for references to publications. For example:
See Meeting Exchange 5.1 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:
● Meeting Exchange 5.1 CS700/CS780 Conferencing Server Release Notes
● Meeting Exchange 5.1 Installing the S700/780 Conferencing Server
● Meeting Exchange 5.1 Relational Database Guide
● Meeting Exchange 5.1 Bridge Talk User’s Guide
● MultiSite for Meeting Exchange 5.1 Installation and Configuration Guide
12 Administration and Maintenance of the S700/780 Audio Conferencing Server
How to Get Help
Information
Telephone +1-877-742-8351
Web site http://www.avaya.com/support
US and Canada Technical Support *1-800-242-2121
International Technical Support +353-1-207-5667 (CS700/CS780)
How to Get Help
+1-877-742-8352
E-mail:
MXCustomerSupp@avaya.com
Fax: +1-978-677-5134
+353-1-207-5666 (CS7000)
E-mail: MXdubsupp@avaya.com
International Meeting Exchange
Technical Support
E-mail: MXSupport@avaya.com
Issue 1 November 2008 13
Preface
14 Administration and Maintenance of the S700/780 Audio Conferencing 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:
● Control of large conferences from a single user interface.
● Dynamic allocation of unused ports to form new conferences.
● Conference support (up to 100,000 ports) across geographically distributed CS700/
CS780.
● Interoperable with Audiocodes Mediant 2000
● Third Party Support for Outlook 2003 & 2007
● Web-based conference scheduling and management and data conferencing support.
● Specified-interval and ad hoc conference scheduling options.
● T1, E1, T1-ISDN, T3 CAS, and T3-ISDN network interface support.
● Operator assisted conferences and security code
● Flex conferencing allows service providers to set up and implement a mixture of
predefined call flows.
This chapter is organized as follows:
● System Configuration Overview on page 16 illustrates representative system feature
configurations.
● Audioconferencing Features on page 17 describes audioconference features and services
supported by the system.
● SNMPv2 Management Support on page 24 describes the system’s SNMP management
components.
● 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.
Issue 1 November 2008 15
System Features
● Hardware Features on page 27 describes standard and optional system hardware
components.
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
16 Administration and Maintenance of the S700/780 Audio Conferencing Server
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.
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).
Audioconferencing Features
See the ACS Managing and Scheduling Conferences Guide for details on the Conference
Scheduler.
Unattended Conferences
An unattended conference is a conference in which conferees gain 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 route 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 173 for details on configuring the Conference Scheduler and other
unattended conference features.
Configuring Conference
Issue 1 November 2008 17
System Features
Other features that can be configured for unattended conferences on a system-wide basis
include:
● Auto Extend Duration — The system attempts to extend a conference beyond its
scheduled end time.
● Auto Extend Ports — The system attempts to allocate additional ports to conference to
accommodate additional conferees.
● Early Start Minutes — Conferees can enter a conference 1 to 30 minutes earlier than the
scheduled start time if ports are available.
● 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.
● 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.1 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
on page 173 for
details on apportioning a percentage of system lines for On-demand conferences that will meet
your requirements.
18 Administration and Maintenance of the S700/780 Audio Conferencing Server
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.
Audioconferencing Features
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:
● 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.
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.
● CHANGE CONFERENCE OPTIONS. When a participant enters a leader PIN code and
assumes leader (moderator) status, the system immediately prompts the leader 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.
● 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 on
page 129. 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 ACS Managing and
Scheduling Conferences 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
Issue 1 November 2008 19
System Features
conference lines than the system supports. In light of the fact that some conference participants
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:
Configuring Conference Scheduler on page 173 for details on apportioning
a percentage of system lines for Conference Overbooking that will meet your requirements.
External Passcode Validation
External Passcode Validation (EPV) is an optional feature that enables the system to validate
conference security passcodes (conferee and moderator passcodes) 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 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
Call Routing Service
The Call Routing Service provides automated processing of incoming calls based on either
DNIS or DDI digits. Services include:
on page 181 for details.
● Call branding — Lets you assign conference-specific greeting and instructional messages
to callers.
● 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:
● 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 digitally
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.
● 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
FDAPI on page 163).
Configuring the
20 Administration and Maintenance of the S700/780 Audio Conferencing Server
● 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 ACS Managing and Scheduling Conferences 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.
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.
Audioconferencing Features
See System Configuration
on page 45 for details on enabling the sub-conference feature on 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:
● 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.
● 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:
● the system plays the moderator a notification message such as, “Your conference is
currently secured. A participant of the Sub Conference is requesting re-entry. Please turn
off security to unlock the conference.”
● 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.
● A sub-conference’s roster is played independently of its main conference roster.
● 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 277 for
details.)
Important information about main and sub-conference CODRs:
Issue 1 November 2008 21
System Features
● 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.
● The User Conf Type field in a sub-conference CODR identifies the conference as a
sub-conference.
● 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:
● 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.
● 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 conferee) uses the keypad command, *93, to create and
transfer to and from a sub-conference:
● 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.
● 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.
● 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.
22 Administration and Maintenance of the S700/780 Audio Conferencing Server
Audioconferencing Features
Questions and answers about the role of a moderator in a main conference and a
sub-conference:
● 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?
● The system does not end the main conference. The feature is applicable only when the
last moderator leaves the main conference.
● 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?
● The system ends both the main conference and the sub-conference.
● When a moderator secures a main conference (disallows entry to any additional
participants) is the sub-conference secured as well?
● No. A moderator can secure a sub-conference only while in the sub-conference.
● 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?
● 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.
● 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 participants must be 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
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
system 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
Issue 1 November 2008 23
System Features
Scheduler also enables you to view and print scheduling reports and purge expired conference
information.
See the ACS Managing and Scheduling Conferences 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.
● Manual implementation — The conference moderator enters *92 on the telephone keypad
to initiate the blast dial.
● Automatic implementation — The system initiates the blast dial when the first moderator
enters the conference via a moderator passcode.
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
important details on setting the CLPG (call in progress) timeout period for Auto Blast used in
unattended conferences.
on page 69 for information about blast dial settings, including
Saved Roster Recordings
The system can be configured to generate and save an audio recording of information provided
by conference participants (name, affiliation, and so on). For conferences that include the roster
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
Roster Audio Files on page 210 for more information on roster recording files.
on page 45 for details on enabling roster recordings. See Saved
SNMPv2 Management Support
The system’s SNMPv2 management agent provides the interface between 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
24 Administration and Maintenance of the S700/780 Audio Conferencing Server
Conference Call Modes
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
guidelines and a list of MIB object definitions.
Contact Customer Support for assistance with enabling and configuring SNMP support on your
system.
System Component Alerts
The system MIB’s trap objects alert network managers about potential and actual problems with
system elements and processes:
● Core system resources — Fan, temperature, power supply.
● Runtime resources — Disk space (90% threshold), memory (75% threshold), host and
DSP processor, NICs.
● Telco resources — Signaling and frames.
● LAN resources — Link down and transmit and receive errors.
on page 333 for agent configuration
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.
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 passcodes, to reach an operator, rather than being
Issue 1 November 2008 25
System Features
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.
● Five ways involve dial-outs from the system to the conferee.
● Three ways involve dial-ins from conferees to the system.
Dialing Out to Conferees
There are different ways for operators and moderators to dial out to a participant:
Operator Dial Out
● Immediate — An operator manually dials a phone number directly from the keyboard.
● Fastdial — An operator dials participants from a list stored on the system.
● 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.”
● 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.
● 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 passcode,
before the system places them in the conference.
Moderator Dial Out
● Originator Dial Out (ODO) — A moderator dials out to a conferee during the conference.
● Automatic Blast—As soon as the moderator joins the conference, the system dials a pre-
configured blast list.
● 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:
26 Administration and Maintenance of the S700/780 Audio Conferencing Server
Hardware Features
● Direct — The system automatically routes incoming callers directly to a specified
conference. No access code is required.
● 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.
● 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 available to help
moderators or conferees needing assistance.
Table 1
.
summarizes the operator involvement in the various conference call modes.
Table 1: Operator Involvement in Various Conference Call Modes
Conference
Call Mode
Operator
Initiated?
Operator
Processed?
Operator
Attended?
Code
Required?
Direct No No No No
Coded No No No Yes
Dial In
Attended No Yes Yes No
Immediate Ye s Yes Ye s 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 environmental components necessary
to support the system’s audioconferencing features and basic data storage requirements.
CS700/CS780 Conferencing Server hardware components:
● Telecommunication Network Interface Cards (NICs), each with eight RJ-45 ports that
support scalable T1, T1-ISDN, or E1 channel configurations.
● The CS700 supports up to six NICs (1152 T1, 1104 T1-ISDN PRI, and 1200 E1
channels).
on page 319
Issue 1 November 2008 27
System Features
● The CS780 supports up to 3 NICs (576 TI, 552 T1-ISDN PRI, and 600 E1 channels).
● 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:
● T1 systems require T1 = 1 DSP board.
● T3 systems require T3 = 3n DSP +1, where n is the number of T3 cards.
28 Administration and Maintenance of the S700/780 Audio Conferencing Server
Hardware Features
● CPU host processor card with a minimum processing power and RAM to support the
installed system features.
Tab le 2 identifies the supported T1/E1 that are required for
various system features and Table 3 the supported T3 system configurations.
.
Table 2: Supported T1/E1 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,
5 Flex
15 sec rec
1
1
2
2
1
NO 6 Flex
NO 8 Default
NO 8 Default
NO 6 Flex
5 cps,
5 Flex
15 sec rec
1
1
3
NO 6 Flex
NO 8 Default
5 cps,
5 Default
15 sec rec
3
5 cps,
5 Flex
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.
Issue 1 November 2008 29
System Features
.
Table 3: Supported T3 Configurations
Mixed Configuration
Total
System CPU
T1 T3 ISDN T3 CAS
Ports
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
CS780.
● RCA Jack (on a DSP card) for connection to analog music source (CD player for
example).
● 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 39 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 39 for information
30 Administration and Maintenance of the S700/780 Audio Conferencing Server
Loading...