Avaya Meeting Exchange CS7000 9.5 Suite

Avaya Meeting Exchange CS7000 9.5 Suite
Avaya Meeting Exchange
CS7000 9.5 Suite Release
System Administrator Guide
04-601478
Issue 1
September 2006
© 2006 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
LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE 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 http://www.avaya.com/support and search for the document
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 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.
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: [email protected]
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 ordering information:
Avaya Publications Center
Voice:
+1-207-866-6701
1-800-457-1764 (Toll-free, U.S. and Canada only)
Fax:
+1-207-626-7269
1-800-457-1764 (Toll-free, U.S. and Canada only)
Write:
Globalware Solutions
200 Ward Hill Avenue
Haverhill, MA 01835 USA
Attention: Avaya Account Manager
E-mail:
[email protected]
Order:
04-601478 Issue 1
September 2006
For the most current versions of documentation, go to the Avaya support Web
site: http://www.avaya.com/support
Contents
Chapter 1: Introducing this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents of this guide . . . . . . . . . . . . . . . . . . . . . .
Avaya Conference Management Server (CMS) . . . . . .
Avaya Client Registration Server (CRS) . . . . . . . . . .
Avaya Notifications Subsystem . . . . . . . . . . . . . .
Avaya Template Editor . . . . . . . . . . . . . . . . . . .
Avaya Short Message Server Controller (SMS Controller)
Avaya Data Services Client Application (DSCA). . . . . .
Avaya Operator Console . . . . . . . . . . . . . . . . . .
Avaya Demand PIN Master . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
11
11
12
13
13
13
14
14
14
New features in the Avaya CS7000 Conferencing Server . . . . . . . . . . . . . .
15
Additional reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
Chapter 2: Introducing the Avaya Conference Management Server (CMS) . . . . . .
19
Introducing the CMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
Finding CMS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
Starting CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CMS applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
22
22
Chapter 3: Administering the Avaya Conference Management Server (CMS). . . . .
25
Managing the CMS. . . . . . . . . . . . . . . . . . .
Viewing CMS version details . . . . . . . . . . .
Viewing system status . . . . . . . . . . . . . .
System status fields . . . . . . . . . . . . . .
Viewing details of a shelf, slot, or line . . . . . .
Updating details of a shelf, slot, trunk, or line . .
Viewing the database . . . . . . . . . . . . . . .
Viewing conference configurations . . . . .
Viewing audio conferencing configurations .
Viewing Operator Console applications . . .
Vewing telephone configurations. . . . . . .
Viewing map configurations . . . . . . . . .
Updating recording settings . . . . . . . . . . .
Managing outgoing routing . . . . . . . . . . . .
Outgoing routing. . . . . . . . . . . . . . . .
Viewing outgoing routing settings . . . . . .
Editing outgoing routing settings . . . . . .
Managing DDI Tables . . . . . . . . . . . . . . .
Viewing DDI tables . . . . . . . . . . . . . . .
CS7000 System Administrator Guide for Release 9.5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
25
26
27
27
28
30
32
32
32
33
34
34
35
35
36
38
39
39
39
September 2006
3
Contents
Editing DDI tables . .
Viewing ISF Settings. . .
Managing IPDDI Tables .
Viewing IPDDI tables.
Editing IPDDI tables .
.
.
.
.
.
40
40
41
41
42
Viewing Application Recordings . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
Viewing Application Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
Viewing LCOMMS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
Viewing the Number of Connected Consoles . . . . . . . . . . . . . . . . . . . .
46
Viewing the Audio Conferencing Status . . . . . . . . . . . . . . . . . . . . . . .
47
Shutting down Avaya CS7000 Conferencing Server . . . . . . . . . . . . . . . .
47
Chapter 4: Configuring the Avaya Conference Management Server (CMS) . . . . . .
49
Introducing CMS system configuration files. . . . . . . . . . . . . . . . . . . . .
50
Shelf configuration file (Acs.fil). . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
Primary rate interface configuration file (Pri.fil) . . . . . . . . . . . . . . . . . . .
51
Cnf configuration file (Cnf.fil) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
LI3 configuration file (Li3.fil) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
Intershelf links configuration file (Isl.fil) and Intershelf Framers file (Isf.fil) . . . .
52
Routing configuration file (Routing.fil) . . . . . . . . . . . . . . . . . . . . . . . .
52
Outgoing routing configuration file (Ogrouting.fil) . . . . . . . . . . . . . . . . .
52
Incoming DDI configuration file (Icddi.fil) . . . . . . . . . . . . . . . . . . . . . .
52
Conference configuration file (Conf.fil) . . . . . . . . . . . . . . . . . . . . . . .
53
Runtime options configuration file (Sysparm.fil) . . . . . . . . . . . . . . . . . .
53
Console configuration file (Cons.fil) . . . . . . . . . . . . . . . . . . . . . . . . .
57
EMS configuration file (Emi.fil) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
Application recording configuration file (Aprec.fil) . . . . . . . . . . . . . . . . .
58
Call detail record configuration file (Cdr_ctrl.fil) . . . . . . . . . . . . . . . . . .
58
Hoot and holler configuration file (Hh.fil) . . . . . . . . . . . . . . . . . . . . . .
58
Hoot and holler conferee configuration file (Hhconferee.fil) . . . . . . . . . . . .
58
Mf.fil. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
Numbers configuration file (Numbers.fil) . . . . . . . . . . . . . . . . . . . . . .
59
Serial configuration file (Serial.fil) . . . . . . . . . . . . . . . . . . . . . . . . . .
59
Synchronization configuration file (Sync.fil). . . . . . . . . . . . . . . . . . . . .
59
Internet protocol direct dial inward configuration file
(IPDDI.fil) and Voice Over Internet Protocol (VoIP) . . . . . . . . . . . . . . . . .
60
4
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CS7000 System Administrator Guide for Release 9.5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
September 2006
Contents
Chapter 5: Introducing the Avaya Client Registration Server (CRS) Front End . . . .
61
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End . .
63
Starting the CRS Front End . . .
Starting the CRS Front End .
Optional Extras . . . . . . .
Reference Numbers . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
64
64
66
66
Managing User Logins . . . . . . . . . . . . . . .
Login Levels . . . . . . . . . . . . . . . . . . .
Operator . . . . . . . . . . . . . . . . . . .
Supervisor . . . . . . . . . . . . . . . . . .
Administrator. . . . . . . . . . . . . . . . .
Login Fields . . . . . . . . . . . . . . . . . . .
Creating a New User Login . . . . . . . . . . .
Searching for an Owner Name/Wholesaler.
Editing an Existing User Login . . . . . . . . .
Deleting an Existing User Login . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
67
67
67
68
68
68
69
70
72
72
Managing System Component Logins .
Types of System Component . . . .
System Fields . . . . . . . . . . . .
Creating a new system component.
Editing an existing system login . .
Deleting an existing system login .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
73
73
74
74
76
76
Managing Wholesalers . . . .
Wholesaler Fields . . . . .
Creating New Wholesalers
Editing Wholesalers . . . .
Deleting Wholesalers . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
77
78
79
80
81
Managing Resellers . . . .
Reseller Fields . . . . .
Creating New Resellers
Editing Resellers. . . .
Deleting Resellers . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
81
82
83
85
85
Managing Sales People . . . . . . . . .
Creating a New Sales Contact . . .
Editing an Existing Sales Contact .
Deleting an Existing Sales Contact.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
86
87
88
88
Managing Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Any Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
89
90
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CS7000 System Administrator Guide for Release 9.5
.
.
.
.
.
.
.
.
September 2006
5
Contents
Editing a Cabinet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing System Cards . . . . .
Resource Fields . . . . . . . .
Creating a New Resource . . .
Editing an Existing Resource .
Deleting an Existing Resource
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
92
93
94
95
96
Managing DDIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a DDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DDI Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a new DDI . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a DDI for a Crisis Alert Conference. . . . . . . . . . . . .
Creating a DDI for a Meet Me Secure (CLI Validation) Conference .
Editing an existing DDI . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an existing DDI. . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
96
97
98
100
100
101
102
103
Managing Telephones . . . . . . . . . .
Creating a New Telephone Number
Editing a Telephone Number . . . .
Deleting a Telephone Number . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
103
104
106
106
Managing Time Zones . . . . . . . .
Time Zone Fields. . . . . . . . .
Creating a New Time Zone . . .
Editing an Existing Time Zone .
Deleting an Existing Time Zone.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
107
108
108
110
110
Managing MultiSite Servers . . . . . . . .
Multisite Server Fields. . . . . . . . .
Configuring a new multisite server . .
Deleting an existing multisite server .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
111
111
112
113
Chapter 7: Configuring System Parameters . . . . . . . . . . . . . . . . . . . . . . .
115
Redistributing System Resources Across Multiple Shelves . . . . . . . . . . . .
116
Sending Reminder Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
116
Charging for a Cancelled Conference . . . . . . . . . . . . . . . . . . . . . . . .
116
Previewing Conference Details Before it Starts . . . . . . . . . . . . . . . . . . .
117
Retaining a Conference After Completion . . . . . . . . . . . . . . . . . . . . . .
117
Setting the Maximum Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
Setting the Maximum Participant/Port Availability . . . . . . . . . . . . . . . . .
118
Setting the Maximum Number of Extension Periods . . . . . . . . . . . . . . . .
118
Reusing the Same DDI for Scheduled Conferences. . . . . . . . . . . . . . . . .
118
6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CS7000 System Administrator Guide for Release 9.5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
91
92
September 2006
Contents
Setting the Minimum Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
Setting the Minimum Number of Participants . . . . . . . . . . . . . . . . . . . .
119
Setting the Second Conference Ending Time Warning . . . . . . . . . . . . . . .
119
Opening a Conference Before it is Due to Begin . . . . . . . . . . . . . . . . . .
120
Setting the ‘Conference Yet to Begin’ Message Warning . . . . . . . . . . . . . .
120
Extending Conference Duration . . . . . . . . . . . . . . . . . . . . . . . . . . .
120
Setting the First ‘Conference Ending’ Time Warning . . . . . . . . . . . . . . . .
121
Setting the Maximum Number of Conferences . . . . . . . . . . . . . . . . . . .
Booking Perpetual Conferences . . . . . . . . . . . . . . . . . . . . . . . . .
121
121
Setting Conference Reception ID . . . . . . . . . . . . . . . . . . . . . . . . . . .
123
Setting Account Number Length . . . . . . . . . . . . . . . . . . . . . . . . . . .
124
Setting AdHoc Account Number Length . . . . . . . . . . . . . . . . . . . . . . .
124
Setting PIN Code Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
124
Enabling PIN Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
Setting Up Sales Person as a Mandatory Field . . . . . . . . . . . . . . . . . . .
125
Configuring Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
Chapter 8: Configuring the Bands Initialization File . . . . . . . . . . . . . . . . . .
127
Chapter 9: Introducing the Avaya Notification Subsystem . . . . . . . . . . . . . . .
151
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
152
Operating the Notifications Subsystem . .
vCalender Support. . . . . . . . . . . .
Internal Fax Resources . . . . . . . . .
E-mail Transport . . . . . . . . . . . . .
E-mail Attachments . . . . . . . . .
Attachment settings . . . . . . . . .
Notification States . . . . . . . . . . . .
Setting the Application Font . . . . . .
Setting the Application Font . . . .
Deleting Faxes and E-mails . . . . . . .
Deleting Items By State . . . . . . .
Adding and Testing Faxes and E-mails
Setting the Information Logs . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
153
153
154
154
155
156
156
158
159
159
159
160
163
Testing the Notifications Subsystem .
Setting the Process Flags . . . . .
Logging Details . . . . . . . .
Viewing Logging Details. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
165
165
166
166
.
.
.
.
.
.
.
.
.
.
.
.
CS7000 System Administrator Guide for Release 9.5
September 2006
7
Contents
Playback Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Streaming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
167
167
Notifications Subsystem Alerts . . . . . . . . .
Notification Alert Message . . . . . . . . .
Excerpt from Broadcast.ini Alerts Settings
Alerts Section . . . . . . . . . . . . . . . .
.
.
.
.
168
170
170
170
Chapter 10: Configuring the Avaya Notifications Subsystem . . . . . . . . . . . . .
171
Configuration Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example SMS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172
178
File Templates . . . . . . . . . . . . . . .
File Template Naming Conventions .
Template Name Examples. . . . . . .
Alias Controls . . . . . . . . . . . . .
File Template Example . . . . . .
Alias Control Character * and + . . . .
Attendance Reports . . . . . . . . . .
Fax Command Controls . . . . . . . .
Character Attribute Commands. . . .
Character Code Commands. . . . . .
E-mail Command Controls . . . . . .
Example confirm1aa.txt template .
.
.
.
.
.
.
.
.
.
.
.
.
180
181
183
183
186
186
186
188
190
190
190
193
Configuring Multilingual Notifications . . . . . . . . . . . . . . . . . . . . . . . .
Language Template Locations . . . . . . . . . . . . . . . . . . . . . . . . . .
194
195
Customizing Fax Logos . . . . . . . . . . . .
Hardware Requirements. . . . . . . . . .
Fax Templates . . . . . . . . . . . . . . .
TIFF Files . . . . . . . . . . . . . . . . . .
Customizing Fax Logos . . . . . . . . . .
Converting to a TIFF Image . . . . . . . .
Converting BMP to TIFF/F using TIFFKIT
Applying TIFF/F to Fax Template . . . . .
.
.
.
.
.
.
.
.
198
198
198
200
200
201
201
202
Chapter 11: Troubleshooting the Avaya Notifications Subsystem . . . . . . . . . . .
203
Fax Functionality Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
203
Import Utility Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
203
Chapter 12: Administering the Avaya Template Editor . . . . . . . . . . . . . . . . .
205
Notification Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205
Installing Avaya Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . .
206
8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CS7000 System Administrator Guide for Release 9.5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
September 2006
Contents
Editing an Existing Set of Templates . . . . . . . . . . . . . . . . . . . . . . . . .
208
Editing a Single Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212
Chapter 13: Administering the Avaya SMS Controller . . . . . . . . . . . . . . . . .
215
The Short Message Service Controller . . . . . . . . . . . . . . . . . . . . . . . .
215
Installing the SMS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running SMS Test Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
218
Configuring the SMS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . .
An Example of a Logging File. . . . . . . . . . . . . . . . . . . . . . . . . . .
219
223
Chapter 14: Administering the Avaya Data Services Client Application (DSCA) . . .
225
Directory Services Client Application . . . . . . . . . . . . . . . . . . . . . . . .
225
How it Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
226
Installing DSCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
227
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Non-Cached Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cached Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
231
232
232
User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233
Demand Profile Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
234
Chapter 15: Administering the Avaya Operator Console . . . . . . . . . . . . . . . .
235
Configuring Log on Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
235
Disconnecting a Remote Operator Line . . . . . . . . . . . . . . . . . . . . . . .
236
Enabling the Display of a Substitute CLI for Operator Originated Calls . . . . . .
237
Hiding the Display of Conferees’ CLI on the Operator Console . . . . . . . . . .
238
Configuring Multiple Operator Consoles on one Workstation . . . . . . . . . . .
238
Customizing the Operator Console Title Bar . . . . . . . . . . . . . . . . . . . .
240
Configuring Hoot and Holler Groups .
Defining Hoot and Holler Groups .
Configuring the Operator ini File .
Operator Options . . . . . . .
New Fields . . . . . . . . . . .
.
.
.
.
.
241
241
242
243
246
Customizing Operator Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
247
Chapter 16: Administering the Avaya Client Registration Server (CRS)
server interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Introducing the Client Registration Server.
Server Menu . . . . . . . . . . . . . . .
Trace menu. . . . . . . . . . . . . . . .
Help Menu . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
CS7000 System Administrator Guide for Release 9.5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
249
250
251
251
September 2006
9
Contents
Editing Trace Settings . . . . . . . .
General Group . . . . . . . . . . . .
Applications Group . . . . . . . . .
Viewing Logging Details . . . . . .
Viewing Registration Server Details
Shutting Down the Application . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
251
252
253
254
254
255
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
255
256
256
257
257
258
Chapter 17: Administering the Avaya Demand PIN Master . . . . . . . . . . . . . . .
259
Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
259
Client PIN Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
260
CLI Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
260
CLI Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
261
Branded DDIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
261
Locked and Full Conferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
262
Extending Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263
Toll-free Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263
Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
265
Demand.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
265
Configuration .
General . . .
Database . .
Comms . . .
Protocol . .
LogSettings
Index
10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CS7000 System Administrator Guide for Release 9.5
273
September 2006
Chapter 1: Introducing this Guide
This chapter introduces the Avaya CS7000 Conferencing Server Administrator Guide. It
contains the following sections:
●
Contents of this guide
●
New features in the Avaya CS7000 Conferencing Server
●
Additional reading
Contents of this guide
The Avaya CS7000 Conferencing Server Administrator Guide is aimed at Avaya System
Administrators. Users or Operators of the Avaya CS7000 Conferencing Server can consult the
Avaya CS7000 Operator Guide for information on how to use the system.
The Avaya CS7000 Conferencing Server Administrator Guide describes how to manage key
components of the Avaya CS7000 Conferencing Server. The guide describes the functions of
each component, the main administrative tasks associated with each component, and the
configuration tasks necessary for customized operation. Key components of the Avaya CS7000
Conferencing Server include:
●
Avaya Conference Management Server (CMS)
●
Avaya Client Registration Server (CRS)
●
Avaya Notifications Subsystem
●
Avaya Template Editor
●
Avaya Short Message Server Controller (SMS Controller)
●
Avaya Data Services Client Application (DSCA)
●
Avaya Operator Console
●
Avaya Demand PIN Master
Avaya Conference Management Server (CMS)
Use the CMS to access information about hardware configuration and status.
Use it also to monitor information messages, alarms, and server communications.
CS7000 System Administrator Guide for Release 9.5
September 2006
11
Chapter 1: Introducing this Guide
For more information, see:
●
Introducing the Avaya Conference Management Server (CMS)
●
Administering the Avaya Conference Management Server (CMS)
●
Configuring the Avaya Conference Management Server (CMS)
Avaya Client Registration Server (CRS)
There are two aspects to the CRS. These aspects are the front end interface and the server
interface.
Use the Avaya CRS Front End to manage:
●
Users
●
Bridges
●
Cabinets
●
Card Profiles
●
DDIs
●
Telephones
●
System Parameters
●
Timezones
Use the server interface to monitor communication logs. These communication logs contain
information about the communication between the CRS and other applications. These other
applications include the Avaya Operator Console and the CMS.
Operators use the Avaya CRS Front End to create scheduled and demand conferences.
Operators also use the Avaya CRS Front End to create and maintain company and client
accounts.
For more information, see:
12
●
Introducing the Avaya Client Registration Server (CRS) Front End
●
Administering the Avaya Client Registration Server (CRS) Front End
●
Configuring System Parameters
●
Configuring the Bands Initialization File
●
Administering the Avaya Client Registration Server (CRS) server interface
CS7000 System Administrator Guide for Release 9.5
September 2006
Contents of this guide
Avaya Notifications Subsystem
Use the Avaya Notifications Subsystem to configure fax, e-mail, and SMS notifications. Fax,
e-mail, and SMS notifications are sent to invite participants to a booked conference, to remind
participants of conference details, and so on. You can also use the Avaya Notifications
Subsystem to customize fax, e-mail, and SMS templates.
For more information, see:
●
Introducing the Avaya Notification Subsystem
●
Configuring the Avaya Notifications Subsystem
●
Troubleshooting the Avaya Notifications Subsystem
Avaya Template Editor
Use the Avaya Template Editor to create and edit a set of fax and e-mail templates. The Avaya
Notifications Subsystem uses these templates.
The Avaya Template Editor automates an otherwise manual task. Before the release of the
Avaya Template Editor, users had to create and edit individual templates. For this task, they had
to use an ASCII editor, such as Notepad.
For more information, see:
●
Chapter 12: Administering the Avaya Template Editor
Avaya Short Message Server Controller (SMS Controller)
Use the Avaya SMS Controller to configure the settings involved in the transmission of SMS
messages.
The Avaya SMS Controller provides connectivity between client applications and a mechanism
to transmit an SMS message. The customer provides the mechanism to transmit the message.
This mechanism can be either an SMS gateway or an Short Message Service Centre (SMSC).
Alternatively, a connection can be made to an SMS service provider. Templates provide the
content of the SMS message. This template set is included as part of the Avaya Notifications
Subsystem installation.
For more information, see:
●
Administering the Avaya SMS Controller
CS7000 System Administrator Guide for Release 9.5
September 2006
13
Chapter 1: Introducing this Guide
Avaya Data Services Client Application (DSCA)
Use the Avaya DSCA to ensure that registration details stored on the CRS are synchronized
with registration details stored on the directory server.
For more information, see:
●
Administering the Avaya Data Services Client Application (DSCA)
Avaya Operator Console
Use the Avaya Operator Console initialization (ini) file to manage settings on the Avaya
Operator Console. The console ini file contains parameters that control the functionality of the
Avaya Operator Console.
System Administrator tasks include enabling the display of a substitute CLI for
Operator-originated calls and configuring multiple Avaya Operator Consoles on a single
workstation. Additional tasks can include configuring hoot and holler groups.
Operators use the Avaya Operator Console to manage live conferences.
For more information, see:
●
Administering the Avaya Operator Console
In addition, see the Avaya CS7000 9.5 Console Parameter Description Document, which is
accessible from the www.avaya.com web site.
Avaya Demand PIN Master
Use the Avaya Demand PIN Master to configure parameters associated with the validation of
PINs and the subsequent opening of conferences. Use it also to set parameters associated with
the closing of conferences.
For more information, see:
●
14
Administering the Avaya Demand PIN Master
CS7000 System Administrator Guide for Release 9.5
September 2006
New features in the Avaya CS7000 Conferencing Server
New features in the Avaya CS7000 Conferencing Server
There are a number of new features in the CS7000 9.5 suite release:
●
Wholesalers and conference codes
Conference codes are unique within a Wholesaler. For example: The conference codes
associated with Wholesaler A are all distinct and different. Similarly, the conference codes
associated with Wholesaler B are all distinct and different. However, Wholesaler A and
Wholesaler B can have duplicate conference codes. This flexibility means that
Wholesalers can keep their existing conference codes if they import their conference
codes from another conferencing application. When Wholesaler Operators log in to the
CRS Front End, the CRS ensures that they can only view the details and conferences
associated with their Wholesaler. For more information, see Managing Wholesalers on
page 77.
●
Searching for records
When Wholesaler Operators search CRS or Operator Console records, using either the
internal or external search functionality, the system only returns records associated with
their Wholesaler. In this way, searches are confined to within a Wholesaler. The CRS does
not apply these restrictions to System Operators, who are not associated with a
Wholesaler. For more information, see Managing Wholesalers on page 77.
●
Single conferee alert
There is a new field in the Demand PIN Master, called LastConfereeSecs. If a single
participant is alone in a conference for a configurable number of seconds, the system
alerts the Operator. This feature operates for demand or scheduled, non-global
conferences. If LastConfereeSecs is greater than zero, the system enables the timer.
For more information, see Table 85.
●
Toll-free conferencing
Avaya has added new parameters to the Demand.ini file to enable the effective operation
of toll-free conferencing. This new functionality plays an explanatory message to callers
who try to access a non-toll-free conference using a toll-free DDI. You can also configure a
new setting to disconnect callers who try to access non-toll-free conferences using toll-free
DDIs. For more information, see Toll-free Conferences on page 263.
●
Management alert conferences
Avaya has added new parameters to the Demand.ini to enhance the functionality of
management alerts. The CS7000 now plays a message to the Moderator who initiates a
management alert caller dial out. When the CS7000 finishes dialing the last participant on
the management alert dial list, it plays a notification message to the Moderator. The new
parameters are called ModDialNotifyMsg and ModDialSecs. For more information,
see Table 85.
CS7000 System Administrator Guide for Release 9.5
September 2006
15
Chapter 1: Introducing this Guide
●
Language support in notifications subsystem
You can configure the Notifications Subsystem to send conference notifications in a
number of different languages. This feature is an especially efficient and powerful feature if
participants with different languages regularly attend the same conference. For more
information, see Configuring Multilingual Notifications on page 194.
●
Hiding the display of callers’ CLI
You can now configure the Operator Console to hide the display of conferees’ CLI. This
way, Operators cannot view the CLI of callers when they dial the conferencing system. A
parameter in the Operator ini file controls this functionality. For more information, see
Hiding the Display of Conferees’ CLI on the Operator Console on page 238.
●
Limit on the number of calls in PIN reception
Avaya has changed the default value of the parameter that limits the number of calls that
the system processes in PIN reception at the same time. In previous releases, the default
value of PMLimit=0. This value means that there is no limit on the number of calls. Avaya
has changed the default value to PMLimit=200. This value means that the system can
process 200 calls in PIN reception at the same time. For more information, see Table 85.
●
Notification Subsystem VCalendar support
The Notification Subsystem now supports vCalender. vCalender defines a transport and
platform-independent format for exchanging calendering and scheduling information. For
more information see Table 49 and vCalender Support on page 153.
●
Notification Subsystem SMTP support
The Notification Subsystem now supports Simple Mail Transport Protocol (SMTP). In
previous releases, the Notifications Subsystem used Messaging Application Programming
Interface (MAPI) but in the current release, Avaya includes the configurable
non-proprietary option, SMTP. MAPI is dependent on Microsoft Outlook, but SMTP is not
dependent on a particular transport provider. SMTP also supports mails in HTML format,
as well as plain text format. MAPI is still available in this release. For more information, see
Table 50 and E-mail Transport on page 154.
16
CS7000 System Administrator Guide for Release 9.5
September 2006
Additional reading
Additional reading
There are several guides that cover topics that are referenced, but not fully described in the
current manual. These guides are available from the Avaya web site.
●
Avaya CS7000 9.5 Conferencing Server Operator Guide
●
Avaya CS7000 9.5 Import Utility Guide
●
Avaya CS7000 9.5 Extended Message Server (XMS) Guide
●
Avaya CS7000 9.5 Billing Guide
●
Avaya CS7000 9.5 Reports Guide
●
Avaya CS7000 9.5 Console Parameter Description Document
●
Avaya CS7000 9.5 Hardware Guide
●
Avaya CS7000 9.5 Stored Procedure Interface Guide
●
Avaya CS7000 9.5 Conference Management Server (CMS) Configuration Guide
●
Avaya CS7000 9.5 Release Notes
●
Avaya CS7000 9.5 Conferencing Server Alerts Conferencing Guide
CS7000 System Administrator Guide for Release 9.5
September 2006
17
Chapter 1: Introducing this Guide
18
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 2: Introducing the Avaya
Conference Management
Server (CMS)
This chapter introduces the Avaya Conference Management Server (CMS). It contains the
following sections:
●
Introducing the CMS
●
Finding CMS files
●
Starting CMS
Introducing the CMS
The CMS is the nerve center of the Avaya CS7000 Conferencing Server. It performs all the
basic housekeeping tasks required by the system. These tasks are performed automatically
without manual intervention.
Using the CMS manager, you can:
●
View the entire system configuration from system wide view to card level.
●
Access the status of each line.
●
Determine whether...
- A line
- A card
- A shelf
- The whole system
...is in or out of service.
●
Determine whether a line is on hold, in conference, receiving a message and so on.
●
Identify which card is in which slot and, in the case of a multi shelf system, in which shelf.
This information gives a clear indication of where each conference, message, or line is
located in the hardware.
CS7000 System Administrator Guide for Release 9.5
September 2006
19
Chapter 2: Introducing the Avaya Conference Management Server (CMS)
●
Change the status of individual...
- shelves
- cards
- lines
- The entire system
...from in-service to out-of-service, and back again.
Usually, you monitor the system through the various CMS applications and intervene only if a
problem occurs. If you intervene, ensure that you have a complete knowledge of the
conferencing system. The implications of changes in the CMS configuration settings can be
extensive.
To view the current version of CMS:
●
Click the Help About of the CMS Management – man program.
Finding CMS files
The program files for the CMS are stored in the c:\C2001\bin directory and the data and
configuration files are stored in the c:\C2001\data directory. Table 1 shows a sample listing of
the relevant directories, actual listings vary.
Table 1: CMS Files
c:\C2001\bin
c:\C2001\data
C:\WINDOWS
AC.EXE
Acs.fil
LCOMMS.INI
AcPc.EXE
Aennn.fil
SCOMMS.INI
Note: SCOMMS is not
supported in the 9.5
release.
AE.EXE
Aprec.fil
AR.EXE
Arnnnn.fil
LANUP.LOG
Caltmp.fil
LCOMMS.EXE
Cdr_ctrl.fil
MAN.EXE
Cnf.fil
1 of 2
20
CS7000 System Administrator Guide for Release 9.5
September 2006
Finding CMS files
Table 1: CMS Files (continued)
c:\C2001\bin
c:\C2001\data
SCOMMS.EXE
Conf.fil
SIF.EXE
Cons.fil
STATS.EXE
Emi.Fil
SSIF.EXE
IPDDI.FIL
C:\WINDOWS
hh.fil
hhconferee.fil
icddi.fil
isf.fil
Isl.fil
L13.fil
Mf.fil
Ogrouting.fil
Pri.fil
Routing.fil
Serial.fil
Sync.fil
Sysparm.fil
Timer.fil
Numbers.fil
2 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
21
Chapter 2: Introducing the Avaya Conference Management Server (CMS)
Starting CMS
This section describes how to start the CMS. It also describes the linked applications that make
up the CMS. It contains the following sections:
●
Starting CMS
●
CMS applications
Starting CMS
To start the CMS:
●
Double-click the Do Start icon on the desktop.
Figure 1: Do Start Icon
The Do Start icon starts each application, using the BSMon tool. The BSMon tool
manages the opening and closing of CMS applications.
The system also displays the AcPc dialog.
You can use the AcPc dialog to close the applications that you have just opened. On the
AcPc dialog, the CMS selects each checkbox by default. The CMS also displays the
windows of all the applications, by default.
CMS applications
There are several CMS applications. They are:
Table 2: CMS Applications
Abbreviation
Meaning
Description
AE
Alarms and Errors
AE displays CMS alarms and errors.
AR
Application Recording
AR displays CMS application recording
messages.
1 of 2
22
CS7000 System Administrator Guide for Release 9.5
September 2006
Starting CMS
Table 2: CMS Applications (continued)
Abbreviation
Meaning
Description
SSIF
Socket Interface
SIF implements a socket server that
enables CMS to communicate with other
applications, such as the Operator
Console.
AC
Audio Conferencing
AC performs the conferencing functions
of the CMS. It also displays its in-service
time.
MAN
AcPc Manager
MAN retrieves and displays information
about hardware configuration and
status. You can also use MAN to change
the status of individual shelves, cards,
and lines.
STATS
Statistics
STATS accepts statistic records from the
AC and puts them into *.cdr files.
SCOMMS
Serial
Communications
SCOMMS implements serial
communications between the shelves
and the CMS. It also displays serial
communications statistics.
ACPC Start up
LCOMMS
2 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
23
Chapter 2: Introducing the Avaya Conference Management Server (CMS)
24
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 3: Administering the Avaya
Conference Management
Server (CMS)
This chapter describes each of the linked applications that form the CMS. It also describes the
tasks involved in the administration of the CMS. It contains the following sections:
●
Managing the CMS
●
Viewing Application Recordings
●
Viewing Application Errors
●
Viewing Statistics
●
Viewing LCOMMS Information
●
Viewing the Number of Connected Consoles
●
Viewing the Audio Conferencing Status
●
Shutting down Avaya CS7000 Conferencing Server
Managing the CMS
The application that you use to manage the CMS is called Acpc Management - man
application. Mangement tasks include:
●
Viewing CMS version details
●
Viewing system status
●
Viewing details of a shelf, slot, or line
●
Updating details of a shelf, slot, trunk, or line
●
Viewing the database
●
Updating recording settings
●
Managing outgoing routing
●
Managing DDI Tables
●
Viewing ISF Settings
●
Managing IPDDI Tables
CS7000 System Administrator Guide for Release 9.5
September 2006
25
Chapter 3: Administering the Avaya Conference Management Server (CMS)
To view the Acpc Management - man application:
●
Select the Acpc Management - man application shortcut from the taskbar.
The system displays the Acpc Management - man application.
Figure 2: Acpc Management - man
The Acpc Management - man application displays the status of shelves, cards, and lines. For
more information, see Viewing system status on page 27.
Viewing CMS version details
To view CMS version details:
●
From the Help menu, select About man.
The system displays the About man dialog.
Figure 3: About man Dialog
Click OK to return to the Acpc Management - man application main screen.
26
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
Viewing system status
To view the system status:
●
From the System menu, select Display.
The system displays the system status screen.
Figure 4: System Status
System status fields
Table 3: System Status Fields
Item
Description
System status
Displays the system status, in the following format: INS (INS). The
status in brackers refers to the expected status. The status outside
the brackets refers to the actual status.
AC Shelf
Displays the CMS shelf number, in the case of a multi-shelf system.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
27
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Table 3: System Status Fields (continued)
Item
Description
Equipped
Indicates whether the serial LAN communications link between the
shelf and the CMS is up or down.
Link
Indicates whether the serial communications link between the shelf
and the CMS is up or down.
Status
Displays the shelf status, which is given in the following format:
INS(OOS). The status in brackets refers to the expected status,
outside to the actual status.
Slot
Displays the slot status, which is given in the following format: INS
(INS). The status in brackets refers to the expected status, outside to
the actual status.
2 of 2
Viewing details of a shelf, slot, or line
To view the details of a shelf, slot, or line:
●
From the Configuration menu, select Display.
The system displays the Display Configuration dialog.
Figure 5: Display Configuration Dialog
To view a shelf:
1. Enter the shelf number in the Shelf field.
2. Click Shelf.
The system displays the shelf details.
28
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
Figure 6: Shelf Details
To view a slot:
1. Enter the slot number in the Slot field.
2. Click Slot.
The system displays the slot details.
Figure 7: Slot Details
CS7000 System Administrator Guide for Release 9.5
September 2006
29
Chapter 3: Administering the Avaya Conference Management Server (CMS)
To view a line:
1. Enter the shelf number in the Line field.
2. Click Line.
The system displays the line details.
Figure 8: Line Details
Updating details of a shelf, slot, trunk, or line
To edit the status of a shelf, slot, trunk, or line:
●
From the Configuration menu, select INS/OOS.
The system displays the Service State dialog.
Figure 9: Service State
Serv
30
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
To edit a shelf:
1. Enter the shelf number in the Shelf field.
2. Ensure that Shelf is selected in the Scope panel.
3. Click OOS Hard to put the shelf out of service.
or
Click INS to put the shelf in service.
To edit a slot:
1. Enter the slot number in the Slot field.
2. Ensure that Slot is selected in the Scope panel.
3. Click OOS Hard to put the slot out of service.
or
Click INS to put the slot in service.
To edit a trunk:
1. Enter the trunk number in the Trunk field.
2. Ensure that Trunk is selected in the Scope panel.
3. Click OOS Hard to put the trunk out of service.
or
Click INS to put the trunk in service.
To edit a line:
1. Enter the line number in the Line field.
2. Ensure that Line is selected in the Scope panel.
3. Click OOS Hard to put the line out of service.
or
Click INS to put the line in service.
CS7000 System Administrator Guide for Release 9.5
September 2006
31
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Viewing the database
This section describes how to view information associated with the various applications that
compose the CMS. It contains the following sections:
●
Viewing conference configurations
●
Viewing audio conferencing configurations
●
Viewing Operator Console applications
●
Vewing telephone configurations
●
Viewing map configurations
Viewing conference configurations
To view conference configurations:
1. From the Database menu, select Conference.
The system displays the Conference dialog.
Figure 10: Conference Dialog
The conference ID number is 1 by default.
2. Enter the required Conference ID.
3. Click OK.
The Conference Configuration on the Acpc Management – man screen displays the
conference configuration.
Viewing audio conferencing configurations
To view audio conferencing configurations:
●
From the Database menu, select ACS.
The system displays the audio conferencing system (ACS) data.
32
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
Figure 11: Audio Conferencing Configuration Data
Viewing Operator Console applications
To view Operator Console configurations:
1. From the Database menu, select Consoles.
The system displays the Console Display screen.
Figure 12: Console Display
2. Click Console Config.
The Console Display screen displays the console configuration.
CS7000 System Administrator Guide for Release 9.5
September 2006
33
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Vewing telephone configurations
To view telephone configurations:
●
From the Database menu, select Telephones.
The Acpc Management – man screen displays the telephone configuration.
Figure 13: Telephone Configuration Data
Viewing map configurations
To view map configurations:
1. From the Database menu, select Map.
The system displays the Map Display dialog.
34
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
Figure 14: Map Configuration Data
2. Enter a digit in the Display Map field.
3. Click Display Map.
The system displays the individual map configuration information.
Updating recording settings
To update recording settings:
1. From the AppRecording menu, select Logging.
The system displays the Application Recording Settings dialog.
2. Update the recording settings.
3. Click OK.
The updates are saved.
Managing outgoing routing
This section describes how to manage outgoing routing functionality. It contains the following
sections:
●
Outgoing routing
●
Viewing outgoing routing settings
●
Editing outgoing routing settings
CS7000 System Administrator Guide for Release 9.5
September 2006
35
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Outgoing routing
The outgoing routing file c:\C2001\data\ogrouting.fil instructs the CMS which hunt groups to use
to dial out a particular number prefix. Dial-outs occur from the PRI hunt group to the exchange.
Outgoing routing functionality helps customers to configure their Avaya CS7000 Conferencing
system so that calls to particular destinations route through a preselected trunk. For example, a
trunk can be dedicated to international calls and another trunk can be dedicated to mobile calls.
The PRI.fil file assigns hunt groups to particular trunks. In this way, hunt groups are associated
with specific slots and shelves.
The ogrouting.fil file and the PRI.fil file work together to determine which telephone numbers are
routed from each trunk. This mutual relationship is especially important where different carriers
provision individual shelves. For example, one carrier can offer economical international calls
and another carrier can offer economical domestic or mobile calls. Hunt groups can be created
and configured to optimize carrier offerings, using the combination of the ogrouting.fil and PRI.fil
files.
When a dial out is required in the Avaya CS7000 Conferencing Server, the system looks at the
ogrouting.fil file. The system checks this file to see if the number or prefix has an associated
hunt group. This hunt group and its associated trunk are then used for the outgoing call. A
typical ogrouting. fil file contains the following syntax:
OUTGOING ROUTING TABLE
ROUTING DIGITS
GROUP
"86"
001
"76"
002
"5659"
003
END ROUTING
Using this sample ogrouting.fil file, telephone numbers starting with “86”, for example, 8647432,
are routed through the trunk associated with hunt group 001. Similarly, telephone numbers
starting with “76” are routed through the trunk associated with hunt group 002.
The PRI.fil file associates hunt groups and trunks. Here is some sample text from a pri.fil file:
SHELF 3 SLOT 04
STATUS INS ACCESS BOTHWAYS TYPE GIC
CHANNEL
36
HUNT GROUP
IN SERVICE
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
SHELF 3 SLOT 04
01
-
N
NOT AVAILABLE
02
001
Y
;1
03
001
Y
;2
04
001
Y
;3
05
001
Y
;4
06
001
Y
;5
07
001
Y
;6
08
001
Y
;7
09
001
Y
;8
10
001
Y
;9
11
001
Y
;10
12
001
Y
;11
13
001
Y
;12
14
001
Y
;13
15
001
Y
;14
16
001
Y
;15
According to this sample pri.fil file, all channels in shelf 3, slot 4, are associated with hunt group
001. In other words, if you dial a telephone number that is associated with hunt group 001 in the
ogrouting.fil file, the call goes out on a trunk in shelf 3, slot 4. This calls goes out on a trunk in
shelf 3, slot 4 in accordance with the settings in the pri.fil file. The pri.fil file is set to use 003 by
default.
Customers can also specify a descending list of preferred trunks to be used when their first
preference reaches capacity. This functionality diverts calls through alternative trunks during
times of heavy load. In the ogrouting.fil file, trunks are separated by commas. The sample
ogrouting.fil file below shows a descending list of preferred trunks:
OUTGOING ROUTING TABLE
ROUTING DIGITS
GROUP
"86"
001,009
CS7000 System Administrator Guide for Release 9.5
September 2006
37
Chapter 3: Administering the Avaya Conference Management Server (CMS)
OUTGOING ROUTING TABLE
"76"
002,005
"5659"
003,007
END ROUTING
The Demand.ini file is checked if a client request for a particular hunt group is nonexistent. The
Demand.ini file is also checked if the number or prefix is not referenced in the ogrouting.fil.
Demand.ini contains a parameter called DialGroups. DialGroups specifies a series of hunt
groups to be used. If the related trunk resources are available, the first hunt group is used. If
resources is unavailable, the second hunt group is used, and so on. If ogrouting.fil is configured,
the values in ogrouting.fil overwrite the values contained in the DialGroups parameter.
Viewing outgoing routing settings
To view current outgoing routing settings:
1. From the OgRouting menu, select Display Routing Table.
The system displays the Outgoing Routing dialog.
Figure 15: Outgoing Routing Dialog
2. On the Outgoing Routing dialog, click Routing to display the current outgoing routing
settings.
Avaya CS7000 Conferencing Server displays the outgoing routing table.
The Digits column displays the digits that are common through all the numbers of a
particular hunt group.
The Hunt Group column displays the digits that are common through all the numbers of a
particular hunt group.
38
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
Editing outgoing routing settings
The settings for outgoing routing are uploaded from the ogrouting.fil file in C:\C2001\data. To
edit outgoing routing settings, you must update this fil file. Avaya recommends that you save a
copy of the original file before you make any changes.
1. Open ogrouting.fil, located in C:\C2001\data.
2. Change the ogrouting settings.
3. Save ogrouting.fil.
4. Close ogrouting.fil.
5. From the OgRouting menu, select Load Routing Table.
The new outgoing routing settings are uploaded.Managing System Configuration
Managing DDI Tables
The incoming DDI table associates channels with digit strings (telephone numbers) so that DDI
on incoming calls is simulated. This section contains the following sections:
●
Viewing DDI tables
●
Editing DDI tables
Viewing DDI tables
To view DDI tables:
1. From the IcDdi (Incoming DDI) menu, select Read DDI Table.
The system displays the DDI table.
Figure 16: DDI Table
CS7000 System Administrator Guide for Release 9.5
September 2006
39
Chapter 3: Administering the Avaya Conference Management Server (CMS)
2. Click Read Ic Ddi.
The Ic Ddi dialog displays the Ic Ddi configuration.
The PRI address column displays the line on which the associated digit string is routed.
The Digits column displays the digit string, the direct dial inward number, which is
associated with a particular line.
Editing DDI tables
The DDI settings are uploaded from the icddi.fil file in C:\C2001\data. To edit DDI settings, you
must update this fil file.
To edit DDI tables:
1. Open icddi.fil (located in C:\C2001\data).
2. Change the DDI settings.
3. Save icddi.fil.
4. Close icddi.fil.
5. From the IcDdi menu, select Load DDI Table.
The new DDI settings are uploaded.
Viewing ISF Settings
You can view the settings in the current ISF.fil file if you access the ISF menu on the CMS
Management screen. The system displays sixty four channels at any one time.
To view ISF Settings:
1. From the ISF menu, select Read ISF.
The system displays the ISF Dialog.
Figure 17: ISF Dialog
2. Enter a channel number in the ISF channel field.
The system displays 64 consecutive channels starting with the channel number entered in
the ISF channel field.
The Acpc Management - man screen displays the ISF status.
40
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing the CMS
Figure 18: ISF Information in the Acpc Management - man Screen
Managing IPDDI Tables
In the IPDDI.fil, you can map SIP addresses and IP addresses to DDIs. This mapping ensures
that whether users use VoIP or more traditional telephony technology, the experience is the
same. You can view the mappings and also upload a new mapping file, in realtime. This section
contains the following sections:
●
Viewing IPDDI tables
●
Editing IPDDI tables
Viewing IPDDI tables
To view IPDDI tables:
1. From the IPDdi menu, select Read DDI Table.
The system displays the IPDDI table.
2. Click Read IP Ddi.
The system displays the current IPDdi configuration in the Ic Ddi dialog.
CS7000 System Administrator Guide for Release 9.5
September 2006
41
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Editing IPDDI tables
You can upload the IPDDI settings from the Ipddi.fil file in C:\C2001\data. To edit IPDDI settings,
you must update this fil file.
To edit IPDDI tables:
1. Open IPddi.fil, which is located in C:\C2001\data.
2. Change the DDI settings.
3. Save ipddi.fil.
4. Close ipddi.fil.
5. From the IPDdi menu, select Load IPDDI Table.
The system displays the new IPDDI settings.
Viewing Application Recordings
To view an application recording:
●
Select the Acpc Recording - AR application from the startup menu.
Figure 19: AR Application
42
CS7000 System Administrator Guide for Release 9.5
September 2006
Viewing Application Recordings
You can use this screen to review the operations of the Avaya CS7000 Conferencing
Server and help the troubleshooting of problems.
Application Recording produces messages in the following format:
{Date & Time} {Source task I/D} {System message type} {Message}.
If the message constitutes an error, a message is sent to Alarms and Errors, where it is
stored in a disk file (c:\C2001\data\aemess.log). For more information, see Viewing
Application Errors on page 44.
{Date & Time} is the date and time the message was received.
{Source task I/D} is an identification tag that corresponds to the task that prompted the
message.
{System message type} is the classification of the message.
{Message} is the first ten bytes of the message.
Note:
Note:
Because real time events occur at a rate capable of swamping any system, try to
limit the number of items being recorded at any one time. Take this into account
whenever changing recording settings.
CS7000 System Administrator Guide for Release 9.5
September 2006
43
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Viewing Application Errors
To review alarms and errors:
●
Select the Acpc Errors – ae application.
Figure 20: AE Application
The system displays the errors in real time, so it only displays recent events.
Application Errors produces messages in the following format:
{Date & Time} {Severity} {Message ID and message text} {Source task}.
If the message constitutes an error, a message is sent to Alarms and Errors, where it is
stored in a disk file (c:\C2001\data\aemess.log). For more information, see Viewing
Application Errors on page 44.
{Date & Time} is the date and time the error was noted. This time is based on your
computer clock. Set the computer clock to local time in Month/ Year/ Time format.
{Severity} is a numeric representation of the seriousness of the alarm. There are four
severity levels numbered 0 – 3. Level 0 provides information only and does not affect the
system. Levels 1 to 3 correspond to the Minor, Major & Critical buttons.
{Message ID and message text} is the classification of the message. There are 56 alarm
messages numbered from 0 to 55. These messages contain variables "%.10s,%d " which
are replaced with the name or line that has the fault.
{Source task} is a reference to the function in the source code, which reported the alarm.
This reference is only of interest to a system programmer during system design and
remains for use in future system development.
44
CS7000 System Administrator Guide for Release 9.5
September 2006
Viewing Statistics
Viewing Statistics
This application accepts statistic records from the AC task and generates *.cdr files. The Stats
dialog provides information only. To view these statistics:
●
Select the Stats application.
The system displays the Stats dialog.
Figure 21: Stats Dialog
Viewing LCOMMS Information
You can view LCOMMS information using the LCOMMS application dialog.
Figure 22: LCOMMS Dialog
There are a number of columns in the LCOMMS dialog. Table 4 describes the columns.
CS7000 System Administrator Guide for Release 9.5
September 2006
45
Chapter 3: Administering the Avaya Conference Management Server (CMS)
Table 4: LCOMMS Columns
Column
Description
Shelf
Identifies shelf number
Link ups
If there is an established link with the CMS, the value is 1.
If there is no established link to the CMS, the value is 0.
CPU 1
The IP address of the CPU in the primary slot.
State
Can be active or standby
TXMSG1
Number of Transmit Messages for CPU 1
RXMSG1
Number of Receive Messages for CPU 1
TXHBMSG1
Number of Transmit Heartbeat Messages for CPU 1
RXHBMSG1
Number of Receive Heartbeat Messages for CPU 1
LOSTHBMSG1
Number of Lost Heartbeat Messages for CPU 1
Note:
Note:
This information is repeated for CPU 2 in the secondary slot.
Viewing the Number of Connected Consoles
To view the number of connected consoles:
●
Select the Secure SIF (Socket Interface) application.
Figure 23: Secure SIF
Secure SIF is a noninteractive application, which displays the number of applications connected
to the CMS.
When an Operator Console connects, the socket number increases. When an Operator
Console disconnects, the socket number decreases.
46
CS7000 System Administrator Guide for Release 9.5
September 2006
Viewing the Audio Conferencing Status
Viewing the Audio Conferencing Status
●
Select the AC (audio conferencing) application.
Figure 24: AC Application
This noninteractive application displays shelf details.
The system diaplays the Status field if a system is in service (INS) or out of service (OOS).
The Total Seconds field displays how long the system is running, in seconds.
Shutting down Avaya CS7000 Conferencing Server
●
Double-click the Do Stop icon on the desktop.
Figure 25: Do Stop
The CMS must be started using BSMon tool.
CS7000 System Administrator Guide for Release 9.5
September 2006
47
Chapter 3: Administering the Avaya Conference Management Server (CMS)
48
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 4: Configuring the Avaya
Conference Management
Server (CMS)
This chapter describes CMS system configuration files. It contains the following sections:
●
Introducing CMS system configuration files
●
Shelf configuration file (Acs.fil)
●
Primary rate interface configuration file (Pri.fil)
●
Cnf configuration file (Cnf.fil)
●
LI3 configuration file (Li3.fil)
●
Intershelf links configuration file (Isl.fil) and Intershelf Framers file (Isf.fil)
●
Routing configuration file (Routing.fil)
●
Outgoing routing configuration file (Ogrouting.fil)
●
Incoming DDI configuration file (Icddi.fil)
●
Conference configuration file (Conf.fil)
●
Runtime options configuration file (Sysparm.fil)
●
Console configuration file (Cons.fil)
●
EMS configuration file (Emi.fil)
●
Application recording configuration file (Aprec.fil)
●
Call detail record configuration file (Cdr_ctrl.fil)
●
Hoot and holler configuration file (Hh.fil)
●
Hoot and holler conferee configuration file (Hhconferee.fil)
●
Mf.fil
●
Numbers configuration file (Numbers.fil)
●
Serial configuration file (Serial.fil)
●
Synchronization configuration file (Sync.fil)
●
Internet protocol direct dial inward configuration file (IPDDI.fil) and Voice Over Internet
Protocol (VoIP)
CS7000 System Administrator Guide for Release 9.5
September 2006
49
Chapter 4: Configuring the Avaya Conference Management Server (CMS)
Introducing CMS system configuration files
CMS system configuration files are customized to suit the requirements of each customer.
These files tell the CMS where to find hardware resources and how they are configured. These
files are read-only on system start up. If any of these files changed, the CMS addresses the
hardware in a totally different way. Under normal circumstances, there is no reason for anyone
other than the Installation Engineer to make changes to these files. The information in the
following subsections describes the contents of these configuration files for the following
reasons:
●
For a clear understanding of how the system is configured.
●
To optimize communications with the Avaya Support Helpdesk in the unlikely event of the
deletion, corruption, or incorrect alteration or any of the files.
With a small number of exceptions, all configuration files have a header line, and a trailer line.
Header lines all end with the text CONFIGURATION.All trailer lines are identical to the header
line in the same file, with the addition of the word END. Files might contain comments and blank
lines, which are ignored in processing. Comment lines have a semicolon (;) or period (.) as their
first nonblank character.
Where a file obviously contains no header and trailer, the addition of one is invalid.
Parameter lines in the file are frequently of the form PARAMETER_NAME=value.
PARAMETER_NAME is a capitalized key word. Value is one of the following types:
●
Y or N
●
A number
●
A number range, specified as number-number
●
A string, which cannot contain blanks
For more information about each of the CMS configuration files, see the Avaya 9.5 Conference
Management Server Configuration File Guide.
Shelf configuration file (Acs.fil)
The file c:\C2001\data\acs.fil defines shelf configuration. This file tells the CMS the
position of all cards used in its shelf or shelves. It also tells the CMS whether a shelf is
equipped, the status of the shelf, and any additional information relating to the particular
installation.
50
CS7000 System Administrator Guide for Release 9.5
September 2006
Primary rate interface configuration file (Pri.fil)
Primary rate interface configuration file (Pri.fil)
The file C:\C2001\data\pri.fil defines the configuration of the primary rate interface
(PRI) cards fitted in the system. It defines the location of the PRIs used in the shelf or shelves,
the individual card status, and the channel number. It also tells the CMS whether a hunt group
services the CMS and if so which one.
Note:
Channels 1 and 17 are unavailable on any PRI. This situation is always the case,
as these channels are required for signaling purposes.
Note:
Cnf configuration file (Cnf.fil)
The file c:\C2001\data\cnf.fil defines the configuration details of the CNF (DACC) cards
used in the system. It specifies the location and status of each card. It also specifies the bridge
configuration and the bridge hunt group assignment for each bridge. It also lists the CNF
channel configuration and their assigned CNF hunt groups. Shelves...
●
16
●
17
●
18
●
19
●
20
...are virtual CNF resources. These virtual resources are the CNF resources used for reception
conferences.
LI3 configuration file (Li3.fil)
The file c:\C2001\data\LI3.fil defines the configuration details of the LI3 (OI16) cards
used in the system. It specifies the location and status of each card and the LI3 channel
configuration. The LI3 card and the OI16 card are set up similarly.
CS7000 System Administrator Guide for Release 9.5
September 2006
51
Chapter 4: Configuring the Avaya Conference Management Server (CMS)
Intershelf links configuration file (Isl.fil) and Intershelf
Framers file (Isf.fil)
The ISL file sets the parameters for intershelf linking. The ISL personality module links the
switching matrix of one shelf to another. The system provides for the linking of 32 digital
channels between the central processing units (CPUs) on two different shelves. The linking is
accomplished with two cables for each intershelf link.
isl.fil is an older technology. isf.fil is used if the multichassis 3 (MC3) card is
implemented. In conferencing systems, which were released prior to the deployment of MC3,
isl.fil is used in place of isf.fil.
Routing configuration file (Routing.fil)
Routing.fil is the configuration map for calls coming into the system. The system routes
these calls by DDI or by PIN.
Outgoing routing configuration file (Ogrouting.fil)
Note:
Note:
For more information about the outgoing routing configuration file, see Managing
outgoing routing on page 35.
Incoming DDI configuration file (Icddi.fil)
The incoming routing file associates channels with digit strings (telephone numbers) so that
incoming calls are simulated. The incoming routing file is located here: c:\C2001\data\
icddi.fil
INCOMING DDI TABLE
PRI ADDRESS
DDI
1,4,2
"4973931"
1,4,3
"4973931"
END ROUTING
52
CS7000 System Administrator Guide for Release 9.5
September 2006
Conference configuration file (Conf.fil)
Conference configuration file (Conf.fil)
The conference configuration file c:\C2001\data\conf.fil tells the CMS the settings to
use when dealing with the default conference. The default conference is set up by the system
automatically in response to this configuration file. conf.fil specifies:
●
Name
●
ID
●
Number
●
Resource groups
●
Messages
●
Configuration settings
All other conferences are set up by the Operator Console. For more information, see
Administering the Avaya Operator Console on page 235.
Runtime options configuration file (Sysparm.fil)
Some of the parameters from sysparm.fil are described in Table 5:
Table 5: Sysparm.fil
Parameter
Description
MCDAP = Y
Y means that the McDAP is connected.
NO_DAP = N
Y means that there is no DAP, cards and lines are not
initialized.
UDMOFF = N
Y means that undefined messages are not alarmed,
useful if stallion looped to simulate DAP.
ARSIZE = 10000
MAX size of ARMESS.LOG in units of Kilobytes before
automatic reset.
AESIZE = 10000
MAX size of AEMESS.LOG in units of Kilobytes before
automatic reset.
ARTOTAL = 100000
MAX size of all ARnnnn.BAK files in units of Kilobytes
before oldest deleted.
1 of 5
CS7000 System Administrator Guide for Release 9.5
September 2006
53
Chapter 4: Configuring the Avaya Conference Management Server (CMS)
Table 5: Sysparm.fil (continued)
Parameter
Description
AETOTAL = 100000
MAX size of all AEnnnn.BAK files in units of Kilobytes
before oldest deleted.
AUTO_CONFIG_OFF = N
Y means that if an exception occurs, it is not
automatically handled.
ALARM_SOUND_OFF = Y
Y means that the alarm on the AC-PC is not sounded
when an error is logged, required during testing to
keep noise down.
SYNC1 = 1
Specifies the card on shelf 1 that is to be used for
SELECT_SYNC_SOURCE. SYNC1 = 1 is card as per
operator view. In other words, it refers to HW card 0 on
HW shelf 0.
SYNC2 = 1
Specifies the card on shelf 2 that is to be used for
SELECT_SYNC_SOURCE. SYNC2 = 11 is card as
per operator view. In other words, it refers to HW card
10 on HW shelf 1.
SYNC3 = 1
Specifies the card on shelf 3 that is to be used for
SELECT_SYNC_SOURCE. SYNC3 = 12 is card as
per operator view. In other words, it refers to HW card
11 on HW shelf 2.
AUTOCLEAR = N
Y turns on the auto disconnect facility. N turns off the
auto disconnect facility. You must set up a valid
TIMER.FIL file before using this option.
CLEARTIME = 900
When the auto disconnect facility is turned on this is
the default value in seconds for the auto disconnect
timer. If not set, or if set to zero, the system defaults to
300 secs. In other words, after 5 minutes, I/C calls are
cleared.
MESSDELAY = N
Y turns on the message delay facility, used to
increase efficiency of usage of limited replay
channels under high loads. N turns off the message
delay facility.
DELAYTIME = 1
when the message delay facility is turned on this is
the value in seconds for the message delay timer. If
not set, or if set to zero and MESSDELAY = Y, the
system defaults to 2 secs.
2 of 5
54
CS7000 System Administrator Guide for Release 9.5
September 2006
Runtime options configuration file (Sysparm.fil)
Table 5: Sysparm.fil (continued)
Parameter
Description
RINGTONE = Y
Y turns on the secondary ring tone facility, used to
mask possible message delays caused by limited
replay channels. N turns off the secondary ring tone
facility.
NETDRIVE = c
Sets the network drive used for logging of AE and AR
logs. If not specified, defaults to c.
MOVEMESS = N
If MOVEMESS = Y, following a "move" to a new
conference, the moved conferee is played the
conference entry (welcome) message.
If MOVEMESS = Y, following a "move" to a new
conference, the moved conferee is played the
conference entry (welcome) message.
AUTOROUTE = N
If AUTOROUTE = Y, the AC_PC moves a conferee
from conference ROUTECONF to a conference in the
range ROUTESTART to ROUTEEND every second.
This movement occurs provided that the conference is
OPEN, has less than MAXCONF conferees, and at
least one 'consultant'. A consultant is a special
conferee with disabled AUTO DISCONNECT TIMER.
If AUTOROUTE = Y, auto routing is ON.
ROUTESTART = 2
Start of range of conferences fed by AUTOROUTE.
ROUTEEND = 28
End of range of conferences fed by AUTOROUTE.
ROUTECONF = 1
Feeder conference for AUTOROUTE.
MAXCONF = 1
Maximum number of conferees, not including the
'consultant', for each AUTOROUTE target conference.
ROUTE# = 1
If ROUTE# != 0, # routing is enabled. When a
conferee hits '#', the system attempts to route him to
the next OPEN conference according to the
AUTOROUTE option.
ROUTE* = 1
If ROUTE* != 0, * routing is enabled. When a
conferee hits the '*', followed by up to three digits, the
system attempts to route him to the corresponding
conference as per the AUTOROUTE option.
3 of 5
CS7000 System Administrator Guide for Release 9.5
September 2006
55
Chapter 4: Configuring the Avaya Conference Management Server (CMS)
Table 5: Sysparm.fil (continued)
Parameter
Description
DCHAIR = Y
If DCHAIR = Y, resource control does not guarantee a
CHAIRMAN position and reserves conference CNF
lines as per the OPEN size. Dynamic CHAIRMEN
use the CNF group 3.
If DCHAIR = N, resource control permanently
allocates a CHAIRMAN position and reserves
conference CNF lines. The system reserves
conference lines as per OPEN size, + 1 chairman,
and a minimum of 2 conferees. Dynamic CHAIRMEN
come from the conference CNFs. This option = N is
used in ACT.
PRICHECK = N
If PRI CHECK = Y, loop thru TELSPEC FREE PRI
lines, one a second, and do a
REQUEST_LINE_STATE.
EMSNET = Y
If EMSNET = Y, the EMS is accessed by way of the
network. If EMSNET = N, the EMS is accessed by
way of a stallion port.
PIN_TIME = 4
Timeout for 1st digit of 1st attempt at PIN. Used to
allow non-DTMF telephones a quick out. If = 0 or not
set defaults to 2 secs.
PerpCPreBookPeriod
PerpCPreBookPeriod specifies how often the
rebooking script must run. If
PerpCPreBookPeriod=30, the rebooking script
checks for perpetual conferences every 30 days.
QA_STATE_CHECK=Y
If QA_STATE_CHECK=Y, the system determines
whether a call is in a CONF state before performing Q
and A commands. The default is N.
DEDICATED_OP_CNFS=N
If DEDICATED_OP_CNFS=Y, remote Operators use
the dedicated CNF line pool. The default is N.
DEFAULT_CLI="123456"
This CLI is the default CLI applied to outgoing calls.
DIAL_HOLD_MSG=313
This message is the default message played to callers
on dial hold. The default is 0.
4 of 5
56
CS7000 System Administrator Guide for Release 9.5
September 2006
Console configuration file (Cons.fil)
Table 5: Sysparm.fil (continued)
Parameter
Description
CONFERENCE_STATS_
TIMER=5
Conference statistics, such as the number of
participants, are sent to clients at the timed interval if
they have changed during that interval. The default
value is 0.
WELCOME_RECORDING_
MESSAGE=Y
If recording is switched on and if
WELCOME_RECORDING_MESSAGE=Y, the CMS
instructs XMS to play a welcome message to indicate
that recording is active.
POLLING_TIMER=30
Times out the polling operation if the client who started
the poll exits. The default value is 30.
SSIF=Y
If SSIF=Y, CMS uses the new SSIF task as a socket
server for CCL clients instead of the older SIF task.
ALLOW_MODERATOR_
DIAL=N
If ALLOW_MODERATOR_DIAL=Y, XMS dial out is
permitted. The default value is N.
CARD_STATUS_DELAY=10
CARD_STATUS_DELAY is a timer that specifies the
time to wait for a status to be polled after a trunk is put
OOS or INS. This timer prevents out of service
(OOS) and then in service (INS) from being done
too quickly. A dialog displays when the trunk is put
OOS and INS until the timer is timed out. The text on
the dialog is "Waiting.....".
PLAY_MESS_TO_CONF
If PLAY_MESS_TO_CONF=Y, messages are played
into conferences rather than directly to callers. If
PLAY_MESS_TO_CONF=N, messages are played to
all callers.
5 of 5
Console configuration file (Cons.fil)
Console configuration is specified in the file c:\C2001\data\cons.fil. This file tells the
CMS which consoles are in service.
CS7000 System Administrator Guide for Release 9.5
September 2006
57
Chapter 4: Configuring the Avaya Conference Management Server (CMS)
EMS configuration file (Emi.fil)
This file sets the parameters for communications between the CMS and the EMI card and the
dialogic cards.
Application recording configuration file (Aprec.fil)
This file is read by the CMS at start up and sets the defaults for the application recording
functionality. For example, if a command, such as, ccl_trace, is set to "0", its output is not
recorded. If a command is set to "1", its output is recorded. While the CMS is running, changes
to application recording functionality can be made. When the CMS is reset, this file is read and
the defaults are reset in accordance with this file.
Call detail record configuration file (Cdr_ctrl.fil)
Cdr_ctrl.fil contains the sequence number of the next CDR file that the system opens
when the system fills the current CDR file. It is similar to numbers.fil as it holds sequence
numbers. However, numbers.fil represents a finer level of detail as it holds the statistics
record numbers that comprise the CDR files.
Hoot and holler configuration file (Hh.fil)
Hh.fil contains the names of hoot n' holler circuits. Each hoot n' holler circuit has a numeric
identifier. This identifier is stored in hh.fil.
Hoot and holler conferee configuration file (Hhconferee.fil)
At system start up, Hhconferee.fil directs particular hoot n' holler circuits to conferences.
Conferences are opened at system start up, based on the contents of conf.fil.
58
CS7000 System Administrator Guide for Release 9.5
September 2006
Mf.fil
Mf.fil
At system start up, CMS reads Mf.fil. It is a legacy file and its functionality is disregarded in
the current system. However, the code has not been deactivated as it might be required for
future systems. In older systems, an MF card performed some of the functionality performed by
the PRI card in the current systems.
Numbers configuration file (Numbers.fil)
Numbers.fil contains sequencing numbers of CDR billing records. Whenever a call is made,
a number is incremented so that each call is associated with a unique number. These statistic
record numbers are used in CDR files. Numbers.fil ensures that in the event of a system
restart, existing statistics are not overwritten. A sample Numbers.fil file is shown below here;
stats_num 3493406 call_num 1910322 conf_num -2094619975
Serial configuration file (Serial.fil)
Serial.fil is a legacy file as its functionality is disregarded in the current system. However,
the code has not been deactivated as it might be required for future systems. In older systems,
consoles were connected using serial ports rather than using TCP-IP. This file contained serial
port details.
Synchronization configuration file (Sync.fil)
Sync.fil determines the order of PRIs used in failover situations. For example, in a failover
situation, slot one might be the initial point, followed by slot two as a backup, and so on.
Note:
Note:
This is a legacy file for MC3 systems.
CS7000 System Administrator Guide for Release 9.5
September 2006
59
Chapter 4: Configuring the Avaya Conference Management Server (CMS)
Internet protocol direct dial inward configuration file
(IPDDI.fil) and Voice Over Internet Protocol (VoIP)
Avaya have added a voice over Internet Protocol (VoIP) interface to the CS7000 conferencing
platform. The CS7000 supports mixed public switched telephone network (PSTN) and VoIP
callers in conferences. The CS7000 ensures that the user experience is transparent,
irrespective of the transport method.
The principle is that all traffic occurs within the same CS7000 conferencing infrastructure as the
PSTN traffic. The user experience, the Operator experience, and elements such as billing and
reporting remain essentially unchanged.
For more information on VoIP, see the Avaya CS7000 Conferencing Server Hardware Guide.
On the VoIP card, Data Connections Ltd (DCL) supply a serial interface protocol (SIP) stack,
version 2.04. It is responsible for call setup. The SIP communications take place over user
datagram protocol (UDP). Once call setup is established, the actual voice traffic is transported
using real time transport protocol (RTP) over UDP. SIP uses UDP port 5060 for call setup.
At the core of the system, routing decisions are made based on direct dial inward (DDI).
Accordingly, SIP and IP addresses for inbound traffic are mapped to DDIs to provide the correct
user experience based on the conference booking. The configuration file is called Ipddi.fil.
The IPDDI menu option helps you to view the IPDDI table on the CMS Management interface.
60
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 5: Introducing the Avaya Client
Registration Server (CRS)
Front End
As a System Administrator, you use the Avaya Client Registration Server (CRS) to manage
several different aspects of the conferencing experience. You can manage users, conferencing
components, wholesalers, telephones, timezones, and system parameters through the CRS
Front End. Operator use the CRS Front End to manage companies, clients, and conferences.
The Operator view of the CRS Front End is more limited than the System Administrator view.
Note:
For more information about installing the CRS Front End, see the Avaya CS7000
Operator Guide for 9.5.
Note:
In this manual, the following chapters relate to the CRS:
●
Administering the Avaya Client Registration Server (CRS) Front End
●
Configuring System Parameters
●
Configuring the Bands Initialization File
CS7000 System Administrator Guide for Release 9.5
September 2006
61
Chapter 5: Introducing the Avaya Client Registration Server (CRS) Front End
62
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 6: Administering the Avaya Client
Registration Server (CRS)
Front End
As an Administrator of the Avaya CS7000 Conferencing Server, you have responsibility for
managing several booking and scheduling resources. Operators require these booking and
scheduling resources to arrange and supervise the Avaya conferencing system on behalf of
their clients.
As an Administrator of the Avaya CS7000 Conferencing Server, you are responsible for:
●
Managing User Logins
●
Managing System Component Logins
●
Managing Wholesalers
●
Managing Resellers
●
Managing Sales People
●
Managing Cabinets
●
Managing System Cards
●
Managing DDIs
●
Managing Telephones
●
Managing Time Zones
●
Managing MultiSite Servers
You can manage all resources using the Client Registration Server (CRS) Front End. Once you
intall the CRS Front End, you can open it from your desktop.
CS7000 System Administrator Guide for Release 9.5
September 2006
63
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Starting the CRS Front End
This section describes how to start up the CRS Front End, once you have installed it. This
section also describes some optional features. It also contains a short note that describes how
the CRS server assigns a reference number to each new database item. This section contains
the following sections:
●
Starting the CRS Front End
●
Optional Extras
●
Reference Numbers
Starting the CRS Front End
If your environment has several operating CRS servers, Operators can choose which server
they want to use. Each CRS server has an associated initialization file. Initialization files have
an .ini file extension. If you select a server, the system uses the corresponding ini file to achieve
the client-server connection.
To start the CRS Front End:
1. Double-click the CRS Front End icon on the desktop.
The system displays the Select CRS dialog1.
Figure 26: The Select CRS Dialog
1. The system might not display this dialog. If there is only one ini file present, the system does not display this
dialog. Also the system does not display this dialog if the System Administrator has specified a specific ini file in
the Properties dialog.
64
CS7000 System Administrator Guide for Release 9.5
September 2006
Starting the CRS Front End
2. Select an ini file from the File Name list.
The system displays the corresponding server in the server fields.
3. Click OK.
The CRS validates your Windows NT user name against a predefined list of user logins
already established in the CRS database.
If you have configured an additional level of security, the system requests a password. For
more information on passwords, see Table 6.
The system displays the Enter Password dialog.
Figure 27: Enter Password Dialog
4. Enter a password in the Password field.
5. Click OK.
The system displays the CRS Front End.
Note:
Note:
If the system displays an error message to indicate that you are not registered as
an user, contact Avaya support.
6. From the CRS Front End, click System Administration.
The system displays the System Administration section of the CRS Front End.
CS7000 System Administrator Guide for Release 9.5
September 2006
65
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Figure 28: System Administration Section
Optional Extras
The Avaya CS7000 Conferencing Server contains several optional features. The optional
features include Managing Wholesalers functionality and Managing Resellers functionality. Your
configuration might not contain this functionality.
Reference Numbers
When you create...
66
●
A login
●
A sales person
●
A resource profile
●
A resource DDI
●
A time zone
●
A server
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing User Logins
...as a system resource, the system assigns a reference number to the new item. This number
is unique. The system uses this unique reference number to map information and associate
resources when Operators reserver conferences.
Managing User Logins
To access the CRS Front End application, users must have appropriate login privileges. As a
CRS System Administrator, you can configure login privileges for CRS Operators in the Login
tab.
This section describes how to add, edit, and delete logins. It also describes the various levels of
privilege and the fields that the system displays on the Add, Edit, and Delete dialogs. It contains
the following sections:
●
Login Levels
●
Login Fields
●
Creating a New User Login
●
Editing an Existing User Login
●
Deleting an Existing User Login
Login Levels
There are three login levels. They are as follows:
●
Operator
●
Supervisor
●
Administrator
Operator
With Operator privileges, Operators can:
●
View the existing conferencing schedule
●
Print conference details
●
Create company and client details
●
Schedule new conferences
●
Manage existing conference reservations
CS7000 System Administrator Guide for Release 9.5
September 2006
67
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
An Operator also manages and monitors conference activity with the Avaya Operator Console.
For more information on the Avaya Operator Console, see the Avaya CS7000 Operator Guide
for Version 9.5.
Supervisor
Supervisor privileges include all Operator and certain Administrator privileges.
Administrator
Administrator privileges provide complete control over functionality in the CRS Front End.
Usually, System Administrators concentrate on system administration tasks only.
Login Fields
As a System Administrator, you allocate a privilege level to users. You can include additional
details for each user.
Table 6: User Logins
Field
Description
Example
Ref
The system automatically generates a unique number
when you create a new user login. For more
information, see Reference Numbers on page 66.
4
Owner Type
A login can be either a System login or a Wholesaler
login. System Users are not associated with a
Wholesaler. Wholesaler Users are associated with a
Wholesaler. You must enter the Wholesaler name in
the Owner field. For more information, see Searching
for an Owner Name/Wholesaler on page 70.
Owner
If the login is associated with a Wholesaler, you must
enter the the Wholesaler name in the Owner field. For
more information, see Searching for an Owner Name/
Wholesaler on page 70.
Name
This name is the Microsoft Windows™ login name of
the user.
jbloggs
Level
The level reflects the users system privilege level. For
more information, see Login Levels on page 67.
Operator
1 of 2
68
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing User Logins
Table 6: User Logins (continued)
Field
Description
Example
Description
This field is a free text field. Use it to enter a comment
about the user.
Engineer
Password
The password is a second level of security.
You can choose to enable or disable this feature.
If you enable it, Operators must enter a password
when they log in.
If you disable the feature, Operators do not need to
enter a password to log in.
To enable this feature, ensure that
ValidationRequired=1 in the bands.ini file.
To disable this feature, ensure that
ValidationRequired=0.
****
2 of 2
Creating a New User Login
This section describes how to create a new user login. It also contains a sub section which
describes how to search for an owner name or a wholesaler. This search functionality is useful if
you want to associate a new user with an existing owner or wholesaler.
●
Searching for an Owner Name/Wholesaler
1. From the Login tab, select User from the View panel.
The system displays all user logins.
2. Click New.
The system displays New User Login dialog.
CS7000 System Administrator Guide for Release 9.5
September 2006
69
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Figure 29: New User Login Dialog
Browse Symbol
3. Enter the appropriate details in the editable text fields.
4. From the Level drop down list, select the user type.
5. From the Owner Type drop down list, select the owner type.
6. Enter the name of the owner in the Owner field.
For more information on searching for the owner name, see Searching for an Owner
Name/Wholesaler on page 70.
7. Click Save.
The system stores the new details in the CRS database.
Searching for an Owner Name/Wholesaler
When you select Wholesaler as an Owner Type, they can search for a particular Wholesaler
from the list of available Wholesalers.
To search for a Wholesaler:
1. Click the Browse symbol at the side of the Owner field.
The system displays the Wholesaler Search dialog.
70
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing User Logins
Figure 30: Wholesaler Search Dialog
2. To search for Wholesalers, enter search criteria in the Filter Details area, such as:
●
Wholesaler Reference Number
●
Wholesaler Name
●
Wholesaler Identification String
●
Wholesaler Identification ID
3. Click Search Now.
Alternatively, you can display all Wholesalers by leaving the search fields blank and
clicking Search Now.
The system displays the matching Wholesalers.
4. Select a Wholesaler by double-clicking on the Wholesaker row.
Alternatively, select a Wholesaler and click SELECT.
The system displays a CRS Information dialog.
Figure 31: CRS Information Dialog
5. Click Yes.
The system closes the Wholesaler Search dialog and displays the New Login dialog.
CS7000 System Administrator Guide for Release 9.5
September 2006
71
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Editing an Existing User Login
1. From the Login tab, select a user and click Edit.
The system displays the Edit Login dialog.
Figure 32: Edit Login Dialog
2. Edit the appropriate details and click Update.
The system updates the login.
Deleting an Existing User Login
1. From the Login tab, select a user and click Delete.
The system displays the Delete Login dialog.
Figure 33: Delete Login Dialog
2. Click Delete.
The system delete the login.
72
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing System Component Logins
Managing System Component Logins
The CRS Front End is one of many components used by the conferencing system. Other
system components must communicate with the Client Registration Server (CRS). The various
components communicate using system component logins. System component logins establish
communication between each system component and the CRS. Usually, the system installer
creates these component logins.
This section describes how to add, edit, and delete system component logins. It also describes
the fields that the system displays on the Add, Edit, and Delete dialogs. It contains the following
sections:
●
Types of System Component
●
System Fields
●
Creating a new system component
●
Editing an existing system login
●
Deleting an existing system login
Types of System Component
The types of system component that communicate with the CRS Reserver are:
●
Consoles
The Operator Console is an application. It enables Operators to manage live conferences.
●
XMS
The eXtended Message Server is a Character User Interface (CUI) application. It stores all
conference and system messages. It also stores conference recordings.
●
Email
The email system that operates with the CRS is called the Notifications Subsystem. The
Notifications Subsystem gathers notification information from the CRS for delivery to
conference participants by way of several different media. These media include fax,
e-mail, and short message service.
●
Data
The Data Conferencing application is an application that provides data sharing over the
Internet. When a participant logs in to a data conferencing session, the Data Conferencing
application communicates with the CRS to validate the participant details. The CRS
checks the system database to ensure that log in details are correct and that the data
feature is selected for this conference.
CS7000 System Administrator Guide for Release 9.5
September 2006
73
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
●
Web
The Web Portal also communicates with the CRS. Users can use the Web Portal suite of
applications to reserve conferences and manage accounts. System Administrators can
use the Web Portal suite to configure a company look and feel for the Web interface.
System Fields
The fields available to system component logins are the same as those attributed to user logins
with one exception:
Table 7: System Login Field
Field
Explanation
Example
Level
On the User Login dialog, there are three levels of users. The
three levels are Operator, Supervisor, and Administrator. On
the System Login dialog, there is one level. This level is the
System level.
System
For more information on the other fields, see Login Fields on page 68.
Creating a new system component
1. From the Login tab, select System from the View panel.
The system displays the System Logins tab.
74
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing System Component Logins
Figure 34: System Logins Tab
The system displays all system logins.
2. Click New.
The system displays the New Login dialog.
Figure 35: New System Login Dialog
3. Enter the appropriate details in the editable text fields.
4. From the Level drop down list, select System and click Save.
The system stores the new details in the CRS database. You can view the new details
from the System Logins tab.
CS7000 System Administrator Guide for Release 9.5
September 2006
75
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Editing an existing system login
1. From the Login tab, select a system component and click Edit.
The system displays the Edit Login dialog.
Figure 36: Edit System Login Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
Deleting an existing system login
1. From the Login tab, select a system component and click Delete.
The system displays the Delete Login dialog.
Figure 37: Delete System Login Dialog
2. Click Delete.
The system deletes the system login.
76
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Wholesalers
Managing Wholesalers
Note:
This feature is an optional feature in the Avaya CS7000 Conferencing Server.
Note:
A Wholesaler is the owner of a company or companies. Wholesalers can create...
●
Companies
●
Clients
●
Resellers
●
Conferences
...on the Web and the CRS Front End. Wholesalers cannot access data related to companies or
clients owned by other wholesalers.
Conference codes are unique within a Wholesaler. For example: The conference codes
associated with Wholesaler A are all distinct and different. Similarly, the conference codes
associated with Wholesaler B are all distinct and different. However, Wholesaler A and
Wholesaler B can have duplicate conference codes. This flexibility means that Wholesalers can
keep their existing conference codes if they import their conference codes from another
conferencing application.
When Wholesaler Operators log in to the CRS Front End, the CRS ensures that they can only
view the details and conferences associated with their Wholesaler. Similarly, when Wholesaler
Operators search CRS or Operator Console records, using either the internal or external search
functionality, the CRS only returns records associated with their Wholesaler. The CRS does not
apply these restrictions to System Operators, who are not associated with a Wholesaler.
For more information on adding Operators, see Managing User Logins on page 67.
For more information on searching, see the Avaya Meeting Exchange CS7000 9.5 Suite
Release Operator Guide.
CRS System Administrators manage Wholesalers through the CRS Front End. Managing
Wholesalers consists of three tasks. These tasks are adding, editing, and deleting. This section
describes how to add, edit, and delete wholesalers. It also describes the fields that the system
displays on the Add, Edit, and Delete dialogs. It contains the following sections:
●
Wholesaler Fields
●
Creating New Wholesalers
●
Editing Wholesalers
●
Deleting Wholesalers
CS7000 System Administrator Guide for Release 9.5
September 2006
77
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Wholesaler Fields
Table 8 lists the Wholesaler fields
Table 8: Wholesaler Fields
Field
Description
Sample
Reference
The system automatically generates this unique
number when you create a new Wholesaler.
1234
Name
The name of the Wholesaler.
Teleconference
Company
Bill Code
Users can enter an alphanumeric sequence for
display on the billing output. Clients can use it to
reconcile billing records.
654321
Note
You can enter free text in this field to provide
additional information about the Wholesaler.
A subdivision of
Company A.
Description
Similarly, you can enter free text in this field to
describe the Wholesaler.
Based in
London
ID
You can enter a code in this field to associate the
Wholesaler with an external database.
12ab
String
You can enter free text in this field to reconcile the
Wholesaler with an external database.
TeleCon
Contact Details
Enter the contact details of the Wholesaler in this
field. Contact details include:
Teleconference
Company,
123456,
789123,
[email protected]
com
Disabled Option
78
●
Name
●
Telephone
●
Fax
●
E-mail.
You can disable Wholesalers. When you disable
Wholesalers, their associated companies and
clients cannot book conferences.
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Wholesalers
Creating New Wholesalers
To create a new wholesaler:
1. Select the Wholesalers tab.
The system displays the Wholesaler tab.
Figure 38: Wholesaler Tab
2. Click New.
The system displays the New Wholesaler dialog.
Figure 39: New Wholesaler Dialog
3. Enter the appropriate details in the editable text fields.
CS7000 System Administrator Guide for Release 9.5
September 2006
79
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
4. Click Contact to enter the contact details.
The system displays the Contact Details dialog.
Figure 40: Contact Details Dialog
5. Enter the contact details as appropriate.
6. Click OK.
The system displays New Wholesaler dialog.
7. Click Save.
The system stores the new details in the CRS database. You can view the details from the
Wholesaler tab.
Editing Wholesalers
To edit a wholesaler:
1. From the Wholesaler tab, select a Wholesaler and click Edit.
The system displays the Edit Wholesaler dialog.
Figure 41: Edit Wholesaler Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
80
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Resellers
Deleting Wholesalers
Note:
If you delete Wholesalers who have associated Resellers, the Resellers revert to
the System Owner Type.
Note:
1. From the Wholesaler tab, select a Wholesaler and click Delete.
The system displays the Delete Wholesaler dialog.
Figure 42: Delete Wholesaler Dialog
2. Click Delete.
The system deletes the Wholesaler.
Managing Resellers
Note:
This feature is an optional feature in the Avaya CS7000 Conferencing Server.
Note:
The system owner or a Wholesaler can have a network of Resellers. The Resellers are
responsible for finding conferencing customers for the Wholesaler. Accordingly, the Wholesaler
can create, edit, and delete Resellers. Also, Wholesalers can identify each Reseller so that they
can credit Resellers for conferencing revenue. Reseller is an optional attribute of a company.
CRS System Administrators manage Resellers through the CRS Front End. Managing
Resellers consists of three tasks. These tasks are adding, editing, and deleting. This section
describes how to add, edit, and delete Resellers. It also describes the fields that the system
displays on the Add, Edit, and Delete dialogs. It contains the following sections:
●
Reseller Fields
●
Creating New Resellers
CS7000 System Administrator Guide for Release 9.5
September 2006
81
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Note:
●
Editing Resellers
●
Deleting Resellers
Note:
If users update Reseller details through the Web Portal application, the system
does not display the changes on the CRS Front End immediately. You must
restart the CRS Front End.
Reseller Fields
Table 9 describes the Reseller fields.
Table 9: Reseller Fields
Field
Description
Sample
Reference
The system automatically generates a unique
number when you create a Reseller.
123456789
Name
The name of the Reseller.
Phone-a-Conference
Note
You can enter free text in this field to provide
additional information about the Reseller.
Web Conferencing
specialists
Description
Similarly, you can enter free text in this field to
describe the Reseller.
Based in London
ID
You can enter a code in this field to link the
Reseller with an external database.
123abc
String
You can enter free text in this field to reconcile
the Reseller with an external database.
TeleCon
Owner Type
Resellers are System Resellers or Wholesaler
Resellers. System Resellers are not associated
with a Wholesaler. Wholesaler Resellers are
associated with a Wholesaler. You must enter
the Wholesaler in the Owner field.
Wholesaler
1 of 2
82
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Resellers
Table 9: Reseller Fields (continued)
Field
Description
Sample
Owner
If you associate the Reseller with a Wholesaler,
you must enter the Wholesaler in this field.
Teleconference
Technologies
Contact
Details
The contact details of the Wholesaler. Contact
details include:
Phone-a-Conference
, 123456, 789123,
[email protected]
●
Name
●
Telephone
●
Fax
●
E-mail
2 of 2
Creating New Resellers
To create a new Reseller:
1. Select the Resellers tab.
The system displays the Resellers tab.
Figure 43: Resellers Tab
CS7000 System Administrator Guide for Release 9.5
September 2006
83
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
2. Click New.
The system displays the New Reseller dialog.
Figure 44: New Reseller Dialog
3. Enter the appropriate details in the editable text fields.
For more information on selecting a Wholesaler owner, see Searching for an Owner
Name/Wholesaler on page 70.
4. Click Contact to enter the contact details.
The system displays the Contact Details dialog.
Figure 45: Contact Details Dialog
5. Enter the contact details as appropriate.
6. Click OK.
The system displays the New Reseller dialog.
7. Click Save.
The system stores the new details in the CRS database. You can view the details from the
Reseller tab.
84
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Resellers
Editing Resellers
To edit a Reseller:
1. From the Resellers tab, select a Reseller and click Edit.
The system displays the Edit Reseller dialog.
Figure 46: Edit Reseller Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
Deleting Resellers
To delete a Reseller:
1. From the Reseller tab, select a Reseller and click Delete.
The system displays the Delete Reseller dialog
CS7000 System Administrator Guide for Release 9.5
September 2006
85
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Figure 47: Delete Reseller Dialog
2. Click Delete.
The system deletes the Reseller.
Managing Sales People
Service providers who sell conferencing services can track sales personnel involved in the sale.
Tracking sales personnel is especially useful for sales managers. Sales managers can use the
data to assess job performance to determine a pay rise or exercise bonus schemes. On the
CRS Front End, sales personnel are associated with conference reservations when each
conference is confirmed.
As a CRS System Administrator, you can use the Sales People feature in conjunction with the
system parameter IsSalesPersonMandatory. For more information, see Setting Up Sales
Person as a Mandatory Field on page 125.
The fields on the Sales People dialogs have the same value as the fields on the Login dialogs.
For more information, see Login Fields on page 68.
Managing sales personnel consists of three tasks. These tasks are adding, editing, and
deleting. This section describes how to add, edit, and delete sales personnel. It contains the
following sections:
86
●
Creating a New Sales Contact
●
Editing an Existing Sales Contact
●
Deleting an Existing Sales Contact
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Sales People
Creating a New Sales Contact
To create a new sales contact:
1. From the System Administration screen, click Sales People.
The system displays the Sales People tab.
Figure 48: Sales People Tab
2. Click New.
The system displays the New Sales Person dialog.
Figure 49: New Sales Person Dialog
3. Enter the appropriate details in the editable text fields and click Save.
The system saves the details.
CS7000 System Administrator Guide for Release 9.5
September 2006
87
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Editing an Existing Sales Contact
To edit a sales contact:
1. From the Sales Person tab, select a sales person and click Edit.
The system displays the Edit Sales Person dialog.
Figure 50: Edit Sales Person Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
Deleting an Existing Sales Contact
To delete a sales contact:
1. From the Sales Person property sheet, select a sales person and click Delete.
The system displays the Delete Sales Person dialog.
Figure 51: Delete Sales Person Dialog
2. Click Delete.
The system deletes the sales person details.
88
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Cabinets
Managing Cabinets
Operators might want to book conferences on several different cabinets. In addition, Operators
might want to book conferences on an Avaya CS7000 or an Avaya CS700 or an Avaya CS780
Conferencing Server. Currently, Operators can book conferences on several difference
cabinets, as long as they are of the same server type. Eventually, Operators will use a single
scheduling application for all conferencing server types. This scheduling application will be the
CRS front end. At the moment, the system centrally processes CDRs and CoDRs from all
cabinets of the same server type in the CDR database. The system forwards the data to a
single billing application. The Notifications Subsystem sends conference notifications relating to
all cabinets. As the CRS System Administrator, you must locate the cabinets on the same LAN,
WAN, or VPN and within the same timezone. The CRS communicates with the multiple bridges
using TCP/IP.
Note:
At present, Operators can book conferences through multiple Avaya CS700 and
CS780 Conferencing Servers, or multiple Avaya CS7000 Conferencing Servers.
In future releases, a single CRS will support multiple bridge types, for example,
Avaya CS7000 and Avaya CS780.
Note:
You can add, edit, and delete cabinets through the CRS front end. This section describes how
to manage cabinets in the system. It also describes the Any cabinet configuration option. It
contains the following sections:
●
Any Cabinet
●
Adding a Cabinet
●
Editing a Cabinet
●
Deleting a Cabinet
Any Cabinet
When Operators book a conference, they can select a particular cabinet for their reservation.
Alternatively, Operators can select the Any (cabinet) option. When Operators select the Any
option, the CRS checks which cabinets have available resources. The system selects the first
available cabinet. Operators must specify the conference type. The system only considers
cabinets with matching conference types. Operators do not specify a DDI when they select the
Any option. For more information on the Any option, see the Avaya CS7000 Operator Guide for
Version 9.5.
Note:
Note:
The system does not support Best fit functionality when Operators select the Any
option.
CS7000 System Administrator Guide for Release 9.5
September 2006
89
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
The bands.ini file contains a new parameter called AnyCabinetFlag. AnyCabinetFlag is
located in the [Make Reservation] section. The possible values for this parameter are as
follows:
●
AnyCabinetFlag=0
If AnyCabinetFlag=0, the Any Cabinet feature is disabled. The feature is unavailable to
the user on the Make Reservation dialog.
●
AnyCabinetFlag=1
If AnyCabinetFlag=1, the Any Cabinet option displays at the top of the Cabinet list on
the Make Reservation dialog.
●
AnyCabinetFlag=2
If AnyCabinetFlag=2, the Any Cabinet option displays at the bottom of the Cabinet list
on the Make Reservation dialog.
Adding a Cabinet
To add a cabinet:
1. Select Cabinets from the System Administration screen.
The system displays the Cabinets tab.
Figure 52: Cabinets Tab
2. Click New.
The system displays the New Cabinet dialog.
90
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Cabinets
Figure 53: New Cabinet Dialog
These fields apply to the Avaya CS700/780
3. Enter the cabinet name in the Name field.
4. Select a cabinet type from the Type drop-down list.
5. Click Save.
The system creates a new cabinet.
Editing a Cabinet
To edit a cabinet:
1. Select a cabinet from the Cabinet tab.
2. Click Edit.
The system displays the Edit Cabinet dialog.
Figure 54: Edit Cabinet Dialog
These fields apply to the Avaya CS700/780
3. Edit the appropriate details and click Update.
The system updates the cabinet.
CS7000 System Administrator Guide for Release 9.5
September 2006
91
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Deleting a Cabinet
To delete a cabinet:
1. Select a cabinet from the Cabinet tab.
2. Click Delete.
The system displays the Delete Cabinet dialog.
Figure 55: Delete Cabinet Dialog
3. Click Delete.
The system deletes the cabinet.
Managing System Cards
The Avaya CS7000 Conferencing Server contains many resources that combine to provide the
conferencing experience. A typical cabinet shelf includes the following hardware cards:
●
PSU
●
CPU
●
O.I.16
●
DACC
●
CNF
●
PRI
●
EMI
For more information on system cards, see the Avaya CS7000 Hardware Guide for Version 9.5.
92
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing System Cards
This section describes how to manage system cards on the CRS Front End. It contains the
following sections:
●
Resource Fields
●
Creating a New Resource
●
Editing an Existing Resource
●
Deleting an Existing Resource
Resource Fields
As the CRS System Administrator, you create each resource profile. You can associate
attributes with each resource. Table 10 describes the fields associated with system cards.
Table 10: Resource Profile
Field
Description
Example
Resource
This value is a numeric value. Use it to associate the system
resource with specific DDIs. For more information on DDIs,
see Managing DDIs on page 96. Once you configure the
resource number, you cannot edit it.
If the traffic light is green the resource is active.
If the traffic light is red the resource is inactive.
1
Cabinet
In a multicabinet environment, the system lists the available
cabinets here.
Cabinet 1
Type
This type is the type of resource selected for profiling. You can
select from three types:
PRI
●
PRI
●
CNF
●
EMI
Bookable
You can establish the maximum ports available for booking
per conference reservation.
For example, if you enter 240, the system makes 240 ports
available for a single conference reservation.
230
Extension
You can use system ports to increase conferences in size
after booking.
5
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
93
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Table 10: Resource Profile (continued)
Field
Description
Example
Operator
You can reserve a certain number of ports for Operator use
only.
5
Toll Free
When you select Toll Free, conferences completed using this
resource are charged to the conferencing service provider
and not the participant.
No
2 of 2
Creating a New Resource
To create a new resource:
1. From the System Administration screen, click Resources.
The system displays the Resource Profile tab.
Figure 56: Resource Profile Tab
2. Click New.
The system displays the New Resource dialog.
94
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing System Cards
Figure 57: New Resource Dialog
3. Enter the appropriate details in the editable text fields.
4. From the Type drop down list, select the resource card required and click Save.
The system stores the new details in the CRS database. You can view the details from the
Resource tab.
Editing an Existing Resource
To edit a resource:
1. From the Resource Profile tab, select a resource and click Edit.
The system displays the Edit Resource dialog.
Figure 58: Edit Resource Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
CS7000 System Administrator Guide for Release 9.5
September 2006
95
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Deleting an Existing Resource
To delete a resource:
1. From the Resource Profile tab, select a resource and click Delete.
The system displays the Delete Resource dialog.
Figure 59: Delete Resource Dialog
2. Click Delete.
If the resource has associated DDIs, the system displays a Confirmation dialog.
Figure 60: Confirmation Dialog
3. Click Yes to delete the resource profile.
The system deletes the resource profile.
Managing DDIs
Direct Dial Inward (DDI) numbers provide a block of telephone numbers for calling into the
private branch exchange (PBX) system of a company. Using DDIs, a company can offer its
customers individual numbers for each person or workstation within the company. DDIs do not
require a physical line into the PBX for each possible connection.
You can buy DDIs from your Communications Service Provider.
96
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing DDIs
As a CRS System Administrator, you must set up separate DDIs for each conference type. DDIs
are limited to 10 digits.
When you set up DDIs, you can associate them with telephone numbers. For example, you can
associate a DDI with multiple telephone numbers, such as, an internal number, an external
number, and a toll free number. Similarly, you can associate a single telephone number with
multiple DDIs. In this way, a single telephone number can access several conferences.
When you create a new DDI, you enter a description for the DDI. Operators can view this textual
description on the Avaya Operator Console, using the View Format menu.
When the system sends conference details to conferees, the system displays the telephone
number, rather than the DDI. The system displays the DDI if there is no associate telephone
number. For more information, see Managing Telephones on page 103.
This section describes how to manage DDIs. Managing DDIs consists of adding, editing, and
deleting DDIs. This section also describes some questions to help you decide which DDI to
associate with a particular conference. It also describes the DDI fields on the Add, Edit, and
Delete dialogs. It contains the following sections:
●
Configuring a DDI
●
DDI Fields
●
Creating a new DDI
●
Editing an existing DDI
●
Deleting an existing DDI
Configuring a DDI
When you associate a DDI with a conference, consider the following questions:
●
What type of conference service are you providing?
●
What is the primary language of your conferencing audience?
●
Does the conference require a moderator?
●
Are you creating a demand conference?
●
Do you want the participant to bypass second level security and enter the conference
directly?
CS7000 System Administrator Guide for Release 9.5
September 2006
97
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
DDI Fields
Table 11: DDI
Field
Description
Example
Reference
The system automatically generates this number once the
DDI is configured for use with the system. For more
information, see Reference Numbers on page 66.
5
Cabinet
This field refers to the cabinet to which the system directs
the DDI. You can configure the system to operate in a
multicabinet environment. Usually, the system uses the
default cabinet.
Resource
This field refers to resource profiles currently available to
the system.
2
DDI
The field refers to the DDI that your network provider
assigns. The DDI is associated with conference
reservations.
7910004
Conference
Type
When you create new DDIs, you associate them with a
specific conference type. When Operators reserve a
conference and select a conference type, the system
displays appropriate DDIs in the DDI dialog. Once you
associate a conference type with a DDI, you cannot edit it.
Meet Me
Language
Type
When you create new DDIs, you associate them with a
language type to suit the primary conferencing audience.
Once you associate a language type with a DDI, you
cannot edit it.
English
Welcome
Msg
You can record alternative messages. You can associate
new messages with a new DDI. To make custom
messages available, select
AllLanguagesSupported=1 in the bands.ini file.
000 - <no
message
selected>
Alias
Alias functionality is optional. Alias functionality helps you
to associate an alternative telephone number with the
DDI. Callers can access the original DDI through this
alternative number. For example, you might want callers
to use a free or easy-to-remember number.
+ 353 1
7910004
Group
Name
The group name is a field of up to four characters. It is
often used to correspond with existing identification codes
for company departments or project teams. You can apply
this field in a variety of ways, depending on your company
needs. This field is an optional field.
4
1 of 2
98
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing DDIs
Table 11: DDI (continued)
Field
Description
Example
Description
This field provides a description for the DDI. It is an
optional field. Operators can view the text that you enter in
this field. They can chose to display the text on the Avaya
Operator Console, using the View Format feature.
Crisis Alert
DDI
Owner Type
DDIs are System DDIs or Wholesaler DDIs. System DDIs
are not associated with a Wholesaler. Wholesaler DDIs
are associated with a Wholesaler. You must enter the
Wholesaler in the Owner field.
Wholesaler
Owner
If the DDI is associated with a Wholesaler, specify the
Wholesaler here.
TeleCon
Moderator
When Operators complete a conference reservation and
select a Moderator in the Check Reservation dialog, the
system only displays certain DDIs. The system only
displays DDIs that you have configured with the
moderator option.
Yes
Demand
When Operators complete a demand conference
reservation, the system only displays certain DDIs. The
system only displays DDIs that you have configured with
the demand option.
No
Direct
Select Direct if you want the conference participant to
enter the conference directly. If you do not select Direct,
the system prompts the participant to enter a
conference-specific PIN.
Yes
Validation
Select validation if you want an additional level of security.
The system prompts the participant to enter their own
specific user PIN along with other conference details.
No
Hunt Group
Hunt groups refer to groupings of telephone numbers
(DDIs). If a DDI is unavailable at a certain time, the
system checks the availability of the next DDI in the hunt
group.
1
2 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
99
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Creating a new DDI
Note:
Each conference type must have an associated dedicated DDI.
Note:
DDIs must be associated with conference types. This section describes the basic steps to
create a new DDI. It also contains two examples:
●
Creating a DDI for a Crisis Alert Conference
●
Creating a DDI for a Meet Me Secure (CLI Validation) Conference
To create a new DDI:
1. From the System Administration screen, click DDIs.
The system displays the Resource DDIs tab.
2. Click New.
The system displays the New DDI dialog.
Figure 61: New DDI Dialog
Creating a DDI for a Crisis Alert Conference
A crisis alert conference is a demand conference that autostarts in an emergency situation.
Crisis alert conferences enable different groups to coordinate their response to the emergency.
A caller starts a crisis alert conference by dialing a pre-configured emergency number, such as
110. At this prompt, the system dials a preselected list of conferees and transfers them to the
crisis alert conference as soon as they answer. One of the conferees must be a Moderator. The
crisis alert initiator, the conferees, and the Moderator can communicate together to respond to
the emergency. The conference ends when the Moderator leaves.
100
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing DDIs
1. Select Default from the Cabinet drop-down list.
2. Select 1 from the Resource drop-down list.
Resource 1 refers to shelf 1.
3. Enter a DDI in the DDI field.
4. Select Crisis Alert from the Conference Type drop-down list.
The system automatically selects the Demand check box.
5. Select a language from the Language Type drop-down list.
English is the default language.
6. Enter details in the remaining fields as appropriate.
If you have associated the DDI with a Wholesaler, select the Wholesaler owner type and
enter the Wholesaler name in the Owner field. For more information on selecting a
Wholesaler, see Searching for an Owner Name/Wholesaler on page 70.
7. Ensure that the Hunt Group is 0.
8. Click Save.
The system creates a new crisis alert resource DDI.
Creating a DDI for a Meet Me Secure (CLI Validation) Conference
A Meet-Me Secure CLI Validation conference is a Meet-Me Secure conference with an extra
level of security. In a Meet-Me Secure CLI Validation conference, the server uses the telephone
number from which the conferee dials to identify the caller. Calling Line Identification (CLI)
validation determines whether to grant conference access to the caller. The system constrains
conference access using the number from which the client dials.
CLI Validation ensures fast access as the participant does not have to enter their PIN. CLI
Validation also provides an extra security function that blocks callers who are dialing from an
unrecognised extension.
As an alternative entry methods, the server also supports conference access on CLI failure. In
this situation, the system prompts the for a PIN if they call from an unauthorised extension. If
they enter the correct PIN, the system allows conference access. Operators enable this
alternative entry method on a per conference basis, by the Operator.
1. Select Default from the Cabinet drop-down list.
2. Select the appropriate resource number from the Resource drop-down list.
3. Enter a DDI number in the DDI text field.
4. Select Meet Me Secure from the Conference Type drop-down list.
5. Select a language from the Language Type drop-down list,
6. Select a welcome message from the Welcome Msg drop-down list.
CS7000 System Administrator Guide for Release 9.5
September 2006
101
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
7. Enter details in the remaining fields as appropriate.
If you have associated the DDI with a Wholesaler, select the Wholesaler owner type and
enter the Wholesaler name in the Owner field. For more information on selecting a
Wholesaler, see Searching for an Owner Name/Wholesaler on page 70.
8. Select the following option:
Direct - To bypass any second level of security.
9. Click Save.
The system stores the new details in the CRS database. You can view the details from the
Resource DDIs tab.
You can also enter additional details for the DDI such as an alias or a group name.
Note:
Note:
Avaya recommends that you restart the CRS Front End when you add a new
resource, such as a DDI. Restarting the system ensures that the displayed details
are up-to-date.
Editing an existing DDI
To edit a DDI:
1. From the Resource DDIs tab, select a resource and click Edit.
The system displays the Edit DDI dialog.
Figure 62: Edit DDI Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
102
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Telephones
Deleting an existing DDI
To delete a DDI:
1. From the Resource DDIs tab, select a resource and click Delete.
The system displays the Delete DDI dialog.
Figure 63: Delete DDI Dialog
2. Click Delete.
The system deletes the DDI.
Managing Telephones
The Phones tab enables you to associate DDIs and telephone numbers. Telephone numbers
are presented to the user on:
●
E-mail notification
●
Fax notification
●
SMS notification
●
The Web
DDIs are limited to 10 digits. As a result, DDIs might not contain enough information for the user
to access a conference. For more information on DDIs, see Managing DDIs on page 96.
CS7000 System Administrator Guide for Release 9.5
September 2006
103
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
You can associate DDIs with telephone numbers in the following ways:
●
You can associate a single DDI with multiple telephone numbers.
For example, you can associate a single DDI with an internal number, an external number,
and a toll free number.
●
You can associate a single telephone number with multiple DDIs.
For example, you can configure a single telephone number so that Operators can use it to
access several conference types, such as, demand and scheduled.
When you create a new telephone number, you must associate several attributes with
telephone numbers. These attributes include:
●
Location
You can configure telephone numbers to be location-specific to ensure more economical
rates.
●
Description
This field is a free text field. You can use it to enter additional information in relation to the
number.
●
Toll Free
If you select the Toll Free check box, the system displays the telephone number in
notification e-mails. This occurs only if the Operator books the conference as toll free.
This section describes how to manage telephones in the CRS Front End. Managing telephones
consists of adding, editing, and deleting telephones. This section describes the following tasks:
●
Creating a New Telephone Number
●
Editing a Telephone Number
●
Deleting a Telephone Number
Creating a New Telephone Number
To create a new telephone number:
1. From the System Administration screen, click Phones.
The system displays the Phones tab.
104
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Telephones
Figure 64: Phones Tab
2. Click New.
The system displays the New DDIPhone dialog.
Figure 65: New DDIPhone Dialog
3. Select a DDI from the DDI drop down list.
4. Enter the telephone number in the Phone Number field.
5. Enter a location for the telephone number in the Location field.
6. Enter any additional information related to the telephone number in the Description field.
CS7000 System Administrator Guide for Release 9.5
September 2006
105
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
7. Select the Toll Free check box to save this telephone number as a toll free number.
8. Click Save to save the new telephone number.
The system displays the System Administration screen and saves the new telephone
number.
Editing a Telephone Number
To edit a telephone number:
1. From the Phones tab, select a telephone number and click Edit.
The system displays Edit DDIPhone dialog.
Figure 66: Edit DDIPhone Dialog
2. Update the telephone number as required.
3. Click Update to save the details.
The system updates the details and displays the System Administration screen.
Deleting a Telephone Number
To delete a telephone number:
1. From the Phones tab, select a telephone number and click Delete.
The system displays the Delete DDIPhone dialog.
106
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Time Zones
Figure 67: Delete DDIPhone Dialog
2. Click Delete to delete the telephone number.
The system deletes the telephone number and displays the System Administration
screen.
Managing Time Zones
As a System Administrator, you control the number of time zones in the conferencing system.
Avaya recommends that you focus on the time zones that the users are likely to require. For
more information about time zones, see the Avaya CS7000 Operator Guide for Version 9.5.
This section describes how to manage time zones on the CRS Front End. Managing time zones
consists of adding, editing, and deleting time zones. This section also describes the time zone
fields. It contains the following sections:
●
Time Zone Fields
●
Creating a New Time Zone
●
Editing an Existing Time Zone
●
Deleting an Existing Time Zone
CS7000 System Administrator Guide for Release 9.5
September 2006
107
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Time Zone Fields
Table 12: Time Zones
Field
Description
Example
TimeZone
Type
The system automatically generates a time zone reference
number when you create a new time zone entry. The
system assigns numbers in an incremental numeric
sequence.
If you delete a time zone entry, you cannot use the
reference number again.
4
TimeZone
Name
This field refers to the name of the time zone. It mentions
the city or cities associated with the time zone.
GMT (NO
DST)
DST Start
The date and time when daylight saving time starts.
2001/04/01
02:00
DST End
The date and time when daylight saving time ends.
2001/04/01
02:00
DST
Offset
This field shows the time in minutes that you must account
for when accommodating annual daylight saving time.
Usually, this figure is 60 minutes.
60
STD
Offset
The standard time difference between each time zone. The
offset is calculated against GMT (0). For example, the STD
Offset for New York is -300. Therefore, this time is 300
minutes (5 hours) behind GMT.
300
Creating a New Time Zone
To create a new time zone:
1. From the System Administration screen, click Time Zones.
The system displays the Time Zone tab.
108
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing Time Zones
Figure 68: Time Zones Tab
2. Click New.
The system displays the New Time Zone dialog.
Figure 69: New Time Zone Dialog
3. From the Resource drop down list, select the appropriate resource number.
4. Enter the following details:
●
An appropriate time zone name. For example, EST + Daylight Savings Time (DST)
●
The DST Start and End times in the following format: dd/mm/yyyy hh:mm
●
The DST Offset time in minutes
●
The STD Offset time in minutes
5. Click OK.
The system stores the new time zone in the CRS database. You can view the details from
the Time Zones tab.
CS7000 System Administrator Guide for Release 9.5
September 2006
109
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Editing an Existing Time Zone
To edit a time zone:
1. From the Time Zones tab, select an existing time zone and click Edit.
The system displays the Edit TimeZone dialog.
Figure 70: Edit TimeZone Dialog
2. Edit the appropriate details and click Update.
The system updates the details.
Deleting an Existing Time Zone
To delete a time zone:
1. From the Time Zones tab, select an existing time zone and click Delete.
The system displays the Delete TimeZone dialog.
Figure 71: Delete TimeZone
2. Click Delete.
The system deletes the time zone.
110
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing MultiSite Servers
Managing MultiSite Servers
A conferencing client often has systems in multiple locations worldwide. If the systems are all
connected on a WAN or a LAN, the systems can communicate together. As a System
Administrator, you can create a server login for each available CRS on the network. Once you
set up the various systems, each system communicates by recognizing the server name that
you have entered in the ServerName field.
This section describes how to manage multisite servers. Managing multisite servers consists of
adding and deleting multisite servers. This section describes how to add and delete multisite
servers. It also describes the multisite fields. It contains the following sections:
●
Multisite Server Fields
●
Configuring a new multisite server
●
Deleting an existing multisite server
Multisite Server Fields
Table 13: Servers
Field
Description
Example
Client Ref
The system automatically generates a reference
number when you create a new server entry.
6
Server
Name
The recognized computer name that the system uses
to identify the server on the network.
My Server
CS7000 System Administrator Guide for Release 9.5
September 2006
111
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
Configuring a new multisite server
To configure a new multisite server:
1. From the System Administration screen, click Servers.
The system displays the Servers tab.
Figure 72: Servers Tab
2. Click New.
The system displays the New Server dialog.
Figure 73: New Server Dialog
3. Enter the server name in the ServerName text field.
4. Click Save.
The system stores the new server details. You can view the new details on from the
Servers tab.
112
CS7000 System Administrator Guide for Release 9.5
September 2006
Managing MultiSite Servers
Deleting an existing multisite server
To delete a multisite server:
1. From the Servers property sheet, select an existing server and click Delete.
The system displays the Delete Server dialog.
Figure 74: Delete Server Dialog
2. Click Delete.
The system deletes the server.
CS7000 System Administrator Guide for Release 9.5
September 2006
113
Chapter 6: Administering the Avaya Client Registration Server (CRS) Front End
114
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 7: Configuring System
Parameters
You can configure several aspects of CRS functionality using the CRS system parameters. You
can make changes to the CRS system parameters on the CRS Front End. For more
information, see Configuring the Bands Initialization File on page 127.
Note:
You can configure bands.ini to display certain parameters on the CRS Front End
and to hide other parameters.
Note:
This chapter describes how to configure certain aspects of CRS functionality to suit your
conferencing requirements. It contains the following sections:
●
Redistributing System Resources Across Multiple Shelves
●
Sending Reminder Details
●
Charging for a Cancelled Conference
●
Previewing Conference Details Before it Starts
●
Retaining a Conference After Completion
●
Setting the Maximum Duration
●
Setting the Maximum Participant/Port Availability
●
Setting the Maximum Number of Extension Periods
●
Reusing the Same DDI for Scheduled Conferences
●
Setting the Minimum Duration
●
Setting the Minimum Number of Participants
●
Setting the Second Conference Ending Time Warning
●
Opening a Conference Before it is Due to Begin
●
Setting the ‘Conference Yet to Begin’ Message Warning
●
Extending Conference Duration
●
Setting the First ‘Conference Ending’ Time Warning
●
Setting the Maximum Number of Conferences
●
Setting Conference Reception ID
●
Setting Account Number Length
●
Setting AdHoc Account Number Length
CS7000 System Administrator Guide for Release 9.5
September 2006
115
Chapter 7: Configuring System Parameters
●
Setting PIN Code Length
●
Enabling PIN Entry
●
Setting Up Sales Person as a Mandatory Field
●
Configuring Field Names
Redistributing System Resources Across Multiple Shelves
If your conferencing system includes more than one shelf, you can redistribute participants
across available shelves to avail of other ports. This can be the most effective use of resources.
If a conference exceeds the size of BigConferenceSize, the system allocates ports on
another shelf to any additional participants.
For example, if the BigConferenceSize=90, and a conference has 100 attendees, the
system makes other resources available across other shelves.
Sending Reminder Details
When Operators schedule a conference, they can select notification options, including the
reminder option. When Operators select any of these options, the Notifications Subsystem
sends each participant details of the scheduled conference.
The ConferenceReminderXMinutesBefore parameter controls the actual time the system
sends a reminder.
For example, if ConferenceReminderXMinutesBefore=180, the system sends each
participant a reminder 180 minutes before the scheduled start time.
Charging for a Cancelled Conference
The system bills for cancelled conferences if conference organizers cancel too late. If
conference organizers cancel before the time frame stated in the
FreeIfCancelledXminutesBefore parameter, the system does not bill them.
For example, if FreeIfCancelledXMinutesBefore=180, conference organizers who cancel a
conference 180 minutes before its scheduled start time are not billed. If conference organizers
cancel within the 180 minute time frame, the system bills for the conference.
116
CS7000 System Administrator Guide for Release 9.5
September 2006
Previewing Conference Details Before it Starts
Previewing Conference Details Before it Starts
As the System Administrator, you set the preview time for each conference. The preview time is
the point before a conference starts, that the system previews the conference details. The
ListConferenceActivityXMinutesBefore parameter controls the preview time. The
Avaya Operator Console uses this parameter to operate the Schedule Open functionality.
Note:
Note:
ListConferenceActivityXMinutesBefore must be equal to or greater
than OpenConferenceXMinutesBefore.
Retaining a Conference After Completion
After conference completion, the system retain the conference details for a configurable period
of time. Only you, the System Administrator can view these details. The
ListConferenceActivityXMinutesBefore parameter controls the retention of
conference details.
Note:
Note:
This parameter is now obsolete.
Setting the Maximum Duration
When Operators schedule a conference, they set its duration in minutes. The
MaxConferenceDurationMinutes parameter controls the maximum duration of
conferences. If Operators attempt to schedule a conference that has a duration greater than
that stated in MaxConferenceDurationMinutes, the system prompts them to enter a
reduced number.
For example, if MaxConferenceDurationMinutes=1440, Operators must not schedule
conference durations greater than 24 hours.
CS7000 System Administrator Guide for Release 9.5
September 2006
117
Chapter 7: Configuring System Parameters
Setting the Maximum Participant/Port Availability
You can restrict the number of participants in conferences to ensure that the conference load
does not overstretch system resources.
If a system has 240 ports, Avaya recommends that you set the MaxConferenceSize
parameter to a percentage of the overall ports available.
For example, if MaxConferenceSize=80, you can schedule three conferences using 80 ports
each, occurring at the same time.
Setting the Maximum Number of Extension Periods
When a conference is nearly complete, ths system can extend the conference duration if
resources are available.
The MaxNumberExtensionPeriods parameter controls the number of extensions that the
system can add to the conference duration. MaxNumberExtensionPeriods works with
another parameter called SizeExtensionPeriodMinutes. For more information, see
Extending Conference Duration on page 120.
For example, if MaxNumberExtensionPeriods=4, the system can extend a conference a
maximum of four times.
Reusing the Same DDI for Scheduled Conferences
Usually, you use DDI numbers for dialing into scheduled conferences. Before you can use a
DDI, you must create it as a resource. For more information, see Managing DDIs on page 96.
Usually, the system has a limited number of DDIs available for use. The system can reuse DDIs
to counter the shortage. The system does not allow conferences with the same DDI and PIN
combination to occur simultaneously. The MinutesBetweenDDIReuse parameter establishes
the minimum duration that must lapse between two conferences before the system can reuse
the same DDI and PIN combination.
For example, if MinutesBetweenDDIReuse=40, 40 minutes must lapse between scheduled
conferences before the system can reuse the DDI and PIN combination.
118
CS7000 System Administrator Guide for Release 9.5
September 2006
Setting the Minimum Duration
Setting the Minimum Duration
When Operators schedule a conference, they set its duration in minutes. However, if the
duration they enter is less than the minimum duration allowed, the system prompts the Operator
to enter a greater duration. MinConferenceDurationMinutes controls the minimum
conference duration.
For example, if MinConferenceDurationMinutes=10, Operators must set the duration to
be greater or equal to 10 minutes.
Setting the Minimum Number of Participants
When Operators schedule a conference, they enter the number of participants. If they enter a
participant number that is less than the minimum number allowed, the system prompts the
Operator to enter a greater number of participants.
For example, if MinConferenceSize=3, Operators must enter three or more participants in
the Participants field.
Setting the Second Conference Ending Time Warning
Just before a conference is due to end, the system automatically sends two system messages
to participants, if this parameter is enabled. The XMS sends these messages. The system
messages remind the participants that the conference is about to end. These messages help
participants to decide whether they should add an extension period. For more information on
extension periods, see Setting the Maximum Number of Extension Periods on page 118
For information about the first system message, see Setting the First ‘Conference Ending’ Time
Warning on page 121.
The OneMinuteWarningXMinutesBefore parameter controls the timing of the second
warning message.
CS7000 System Administrator Guide for Release 9.5
September 2006
119
Chapter 7: Configuring System Parameters
Opening a Conference Before it is Due to Begin
The system can open a conference before it is due to begin to facilitate participants that arrive
into conference early. The OpenConferenceXMinutesBefore parameter controls the
amount of time, before the conference start time, that the conference opens.
Setting the ‘Conference Yet to Begin’ Message Warning
Participants who dial in to a conference before it is due to begin are greeted by a system
message. The system message informs the participants that the conference is yet to begin. The
PlayStartingUpToXMinutesBefore parameter controls the timing of this system message.
If a participant enters the conference before a specified time, the system does not play a system
message.
For example, if PlayStartingUpToXMinutesBefore=10, any participant who dials into the
conference within ten minutes of its starting time, hears the system message. If the participant
dials into conference twelve minutes before the conference, they hear no message.
Extending Conference Duration
When a conference is close to completion, the system sends an informational message to the
CRS. The system automatically checks to see if any of the following are true:
●
The conference is still in progress
●
No conflict exists with the allocation of system resources
If these conditions exist, the system automatically extends the conference. However, if the
conference is over or a conflict exists with system resources, the system does not extend the
conference. The SizeExtensionPeriodMinutes parameter controls the conference
extension period..
For example, if SizeExtensionPeriodMinutes=30, the system extends the conference by
30 minutes.
This parameter is used in association with MaxNumberExtensionPeriods. For more
information, see Setting the Maximum Number of Extension Periods on page 118.
The warning message plays before the end of the conference. For more information, see
Setting the First ‘Conference Ending’ Time Warning on page 121.
120
CS7000 System Administrator Guide for Release 9.5
September 2006
Setting the First ‘Conference Ending’ Time Warning
Setting the First ‘Conference Ending’ Time Warning
Just before a conference is due to end, the system automatically sends two system messages
to participants, if this parameter is enabled. The XMS sends these messages. The system
messages remind the participants that the conference is about to end. These messages help
participants to decide whether they should add an extension period.
The TenMinuteWarningXMinutesBefore parameter controls the timing of the first
message.
The system follows the first message with a second message. For more information on the
second message, see Setting the Second Conference Ending Time Warning on page 119.
Setting the Maximum Number of Conferences
When Operators create a reservation, they schedule a conference. A reservation can contain
multiple conferences in a variety of states. A reservation contains multiple conferences if:
●
An existing conference is cloned
●
A conference is a repeating conference
The MaxConferencePerBooking parameter controls the number of conferences per
reservation.
For example, if MaxConferencePerBooking=100, Operators can only associate 100
conferences with a reservation.
Booking Perpetual Conferences
To book a perpetual conference, an Operator must schedule a repeat booking in which the
number of conferences equals the maximum possible conferences in
MaxConferencesPerBooking parameter.
A perpetual conference is a repeat conference that the system automatically extends.
Extension occurs without any Operator or System Administrator intervention. The system sends
an optional e-mail to confirm that it has successfully extended the conferences. In the mail, the
system indicates if it has been unable to rebook any conferences. It also indicates the cause of
the rebooking failure. The system sends the e-mail using SMTP protocols. A possible cause for
a rebooking failure is if the PIN is allocated to another conference. The system also displays
rebooking failures on the CRS Front End. See the Avaya CS7000 Operator Guide for Version
9.5 for an example e-mail.
CS7000 System Administrator Guide for Release 9.5
September 2006
121
Chapter 7: Configuring System Parameters
A parameter called PerpCPreBookPeriod specifies the number of days by which the system
should extend a conference booking. If PerpCPreBookPeriod=30, the system extends all
perpetual conferences to 30 days from the current date. PerpCPreBookPeriod is located in
the BSRes 2 database:
BSRes2/Stored Procedures/Get System Parameters/PerpCPreBookPeriod
The parameter, MaxConferencesPerBooking, determines the maximum number of
conferences that can be booked in a single reservation. For example, if
MaxConferencesPerBooking=100, Operators can book conferences that repeat up to 100
times. If an Operator attempts to book a conference that repeats 101 times, the system displays
an error message. The MaxConferencesPerBooking parameter is configured using System
Parameters tab on the CRS Front End. For more information on this parameter, see Setting the
Maximum Number of Conferences on page 121
To reserve a perpetual conference, an Operator must book a conference that repeats for the
exact number of times specified in MaxConferencesPerBooking. If they book fewer
conferences, the system does not interpret the repeating conference as a perpetual conference.
The system checks for conferences that it might need extend using a scheduled job called,
ExtendPerpetualConferencesJob. By default, ExtendPerpetualConferencesJob
runs on a weekly basis. The ExtendPerpetualConferencesJob:
●
Checks for reservations that might require extending.
●
Extends reservations that meet the criteria for extension.
●
Checks for e-mails in the EMailMessage table and sends them.
Table 14 describes the main system parameters involved in perpetual conference support.
Table 14: Main System Parameters
Name
Default Value
Description
PerpCPreBookPeriod
30
Specifies the number of days by which
the system should extend a perpetual
conference.
PerpCDebugLogging
0
Specifies whether the system should
compile debug logs for perpetual
conference extensions. Set this
parameter to 0 on a customer site.
PerpCSendEmails
1
Specifies whether the system should
send e-mails for perpetual conference
extensions. The system does not use
the remaining parameters if you set
this parameter to 0.
1 of 2
122
CS7000 System Administrator Guide for Release 9.5
September 2006
Setting Conference Reception ID
Table 14: Main System Parameters (continued)
Name
Default Value
Description
PerpCEmailToAddress
[email protected]
com
Specifies the e-mail address to which
p_CheckMailAndSend sends e-mails.
Enter a valid e-mail address here.
PerpCEmailCcAddress
[email protected]
com
Specifies another e-mail address to
which p_CheckMailAndSend sends
e-mails. Enter a valid e-mail address
here or leave it blank.
SMTPServerAddress
yourmailserver.yourdoma
in.com
Specifies the SMTP server address
that p_CheckMailAndSend uses.
SMTPServerPort
25
Specifies the SMTP server port that
p_CheckMailAndSend uses.
EMailTemplateRef
1
Specifies the e-mail template that the
system uses to generate perpetual
conference e-mail reports. Set this
value to 1.
2 of 2
Table 15 describes the stored procedures that the system uses to support perpetual
conferences.
Table 15: New Stored Procedures
Name
Description
p_CheckMailAndSend
Checks for e-mails in the EMailMessage table and sends them.
p_ExtendPerpetualConf
Extends a perpetual reservation using the conference as a
template.
p_ExtendPerpetualConfs
Checks for reservations that need to be extended and calls
p_ExtendPerpetualConf for each one that requires an
extension.
Setting Conference Reception ID
You can set the ID of conference reception. The parameter MaxReceptionConferenceId
controls the idenfitication number of conference reception. If
MaxReceptionConferenceId=120, the reception ID is 120.
CS7000 System Administrator Guide for Release 9.5
September 2006
123
Chapter 7: Configuring System Parameters
Setting Account Number Length
Each client has an account number in the BSRes 2 database. The system generates the
account number when Operators add a new client. For more information, see the Avaya
CS7000 Operator Guide for Version 9.5.
The AccountNumberLength parameter controls the length of the account number.
For example, if the AccountNumberLength=10, the system generates an account number
that is 10 digits long.
If you modify the AccountNumberLength parameter, the system displays an error message
when the Operator views the account details of an existing client. The error message states that
the old account number length is not consistent with the current system parameter. Operators
must manually modify the account number to update the record.
Setting AdHoc Account Number Length
All clients have a regular account number. Clients who use the AdHoc feature also have an
AdHoc account number. The AdHocAccountNumberLength parameter controls the length of
the AdHoc account number.
For example, if AdHocAccountNumberLength=10, the system generates an AdHoc account
number that is 10 digits long.
Setting PIN Code Length
Operators can enter Participant and Moderator PIN codes when they book a conference.
Alternatively, they can choose system-generated PIN codes. If Operators select the Auto PIN
feature, the system generates PIN codes. The parameter PinCodeLength controls the length
of the system-generated PIN code. For example, if PinCodeLength=6, the system generates
PIN codes that are 6 digits long. PinCodeLength and IsPinCodeMandatory both
determine the operation of PINs. For more information on IsPinCodeMandatory, see
Enabling PIN Entry on page 125.
124
CS7000 System Administrator Guide for Release 9.5
September 2006
Enabling PIN Entry
Enabling PIN Entry
The parameter IsPinCodeMandatory relates to the necessity of having a PIN. If you enable
this feature, Operators cannot book a conference unless they include a PIN. All conferences
must have a PIN.
Setting Up Sales Person as a Mandatory Field
Operators can associate a sales person with a conference. The system displays a drop down
menu containing the names of the all the sales people. For more information, see Managing
Sales People on page 86.
If you enable the IsSalesPersonMandatory parameter, Operators must always associate a
sales person with each conference reservation.
Configuring Field Names
As a System Administrator, you can configure some field names on the the CRS front end. You
can configure the following aspects of the fields names:
●
Caption
●
Position
●
Appearance (enabled or disabled)
You can update field names using the Ctrlpos.ini file. Ctrlpos.ini is a comma separated file
located in C:\WINDOWS.
Each field listed in Ctrlpos.ini has the following attributes:
Table 16: Field Syntax
Field
Attribute
Description
CID
A unique field identification number.
nChecked
A reference to the field identification number.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
125
Chapter 7: Configuring System Parameters
Table 16: Field Syntax (continued)
Field
Attribute
Description
Left
The left coordinates of the field position.
Top
The extent to which the field is offset from the top of the
dialog.
Right
The right coordinates of the field position.
Bottom
The extent to which the field is offset from the bottom of
the dialog.
bEnabled
Indicates whether the field is enabled or disabled
(greyed-out).
bVisible
Indicates whether the field is visible or hidden.
strDefault
The field caption.
2 of 2
To configure field names:
1. Close the CRS front end.
2. Open Ctrlpos.ini.
Ctrlpos.ini is located in C:\WINDOWS.
The configurable field names are listed.
Note:
Note:
The system sets fields that are specific to Avaya CS700/CS780 to invisible, using
the bVisible attribute.
3. Update field names as required.
For example, change the caption Auto Code to Auto PIN.
4. Save Ctrlpos.ini.
5. Open the CRS front end to view the changes.
126
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 8: Configuring the Bands
Initialization File
The Bands.ini file is a CRS configuration file. The file contains a series of parameters which
manage many aspects of how the CRS Front End operates.
The Bands.ini file is usually located on the C:\WINDOWS drive of computers running the CRS
Front End application. The Bands.ini file is a local, client-side file. As a System Administrator,
you can configure individual Bands.ini files to optimize functionality for specialized Operators.
Note:
Note:
As an aside, the parameters listed in the System Parameters section of the CRS
Front End are server-side settings. These parameters are entirely separate from
the Bands.ini parameters. If you change the System Parameters section settings
on any client computer, the system implements the new settings on all client
computers. You require System Administrator access to access the System
Parameters section of the CRS Front End. For more information on the System
Parameters section of the CRS Front End, see Configuring System
Parameters on page 111.
Figure 77 shows the System Parameters dialog and several Bands.ini files.
Figure 75: System Parameters Dialog and a Number of Bands.ini Files
Settings
apply to all
clients
Settings
apply to
individual
Operator
Bands.ini
Bands.ini
Bands.ini
CRS Front End Parameters
CS7000 System Administrator Guide for Release 9.5
September 2006
127
Chapter 8: Configuring the Bands Initialization File
The Bands.ini file is divided into the following sections:
Note:
●
Table 17 describes login parameters and custom settings
●
Table 18 describes reservation settings
●
Table 19 describes conference messages settings
●
Table 20 conference options settings
●
Table 21 print parameter settings
Note:
The asterisk symbol indicates the default setting.
Table 17: Login Parameters and Custom Settings
Parameter
Description
7000/7X0
IPAddress
The IP address of the CRS server.
7000/7X0
IPDisplayName
The displayed name of the CRS server.
7000/7X0
ValidationRequired
A password can act as a second level of security when
the Operator logs in to the CRS Front End.
As a System Administrator, you can choose to enable
or disable this feature.
If it is enabled, Operators must enter a password when
they log on.
If it is disabled, Operators do not need to enter a
password when they log on.
To enable this feature, ensure that
ValidationRequired=1
To disable this feature, ensure that
ValidationRequired=0
7000/7X0
Graph
The chart display type. You can select from several
different display formats, as follows:
7000/7X0
●
Graph=0
●
Graph=1
●
Graph=2
The Bands.ini file retains the last graph type viewed by
an Operator. For example, if an Operator views a
barchart, the system displays this graph type the next
time the Operator accesses graph functionality. The
default value is 7*.
1 of 10
128
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
DateFormat
The layout of the displayed date on the CRS Front
End. The possible values are as follows:
7000/7X0
●
DateFormat=0*
This format is the European display format:
DDMMYY
●
DateFormat=1
This format is the American display format:
MMDDYY
CalenderFirstDay
A calender control that determines the day on which
the week starts. For example:
●
7000/7X0
CalenderFirstDay=0
The week starts on a Sunday.
●
CalenderFirstDay=1
The week starts on a Monday.
MinimumFilter
If Minimum Filter is enabled, the system restricts the
amount of information retrieved from the customer
database when an Operator enters a number of
characters in the Company List field. This filter is
normally enabled on systems with a large amount of
data.
7000/7X0
2 of 10
CS7000 System Administrator Guide for Release 9.5
September 2006
129
Chapter 8: Configuring the Bands Initialization File
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
CacheConfig,
CacheData
CRS Front End distinguishes between two types of
data. These two types of data are Configuration Data
and Normal Data. Configuration data rarely changes
because it is primarily installation setup data, such as
DDIs and timezones. Normal data frequently changes.
CacheConfig detemines whether configuration data
is always refreshed or cached.
CacheData detemines whether normal data is
always refreshed or cached.
For example:
7000/7X0
●
If CacheConfig=1, the system reads data at
CRS Front End start up. If you make changes
on other CRS Front End instances, the system
does not display these changes until you restart
the CRS Front End.
●
If CacheConfig=0, the system reads data at
CRS Front End start up. The system also reads
data when, for example, you enter the System
Administration section.
Note: The CRS does not re-read data when you
simple change tabs on the System Administration
screen.
Synchronize
If you enable Synchronize, time is synchronized on all
client CRS Front Ends. By default, Synchronize is
enabled. Synchronize=1* is the default value. You
can disable Synchronize to perform administrative
tasks.
7000/7X0
LargeIcons
You can display CRS Front End icons in two different
sizes. The possible values are as follows:
7000/7X0
●
LargeIcons=0*
The system displays small icons.
●
LargeIcons=1
The system displays large icons.
3 of 10
130
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
AutoRefresh
The system automatically refreshes CRS on-screen
data if you enable the AutoRefresh parameter. The
AutoRefresh parameter applies to dialogs such as
the Schedule and Recording dialogs. You can disable
AutoRefresh to reduce network traffic.
AutoRefresh=0*
Automatic refresh is disabled.
AutoRefresh=1
Automatic refresh is enabled.
7000/7X0
ZeroStartPIN
If you enable ZeroStartPIN , the system allows PIN
codes that start with the digit “0”. If you disable
ZeroStartPIN , the system does not allow PIN
codes that start with the digit “0”. The possible values
are as follows:
7000/7X0
●
ZeroStartPIN=0*
ZeroStartPIN is disabled.
●
ZeroStartPIN=1
ZeroStartPIN is enabled.
CheckPINSize
CheckPINSize controls whether PINs are a
predetermined length or can be any length. If you
disable CheckPINSize, you can vary PIN digit
length. If you enable CheckPINSize, PINs must be a
set size. The possible values are as follows:
●
7000/7X0
CheckPINSize=0
CheckPINSize is disabled.
●
CheckPINSize=1*
CheckPINSize is enabled.
You can configure PIN length on the System
Parameters section in the CRS Front End.
4 of 10
CS7000 System Administrator Guide for Release 9.5
September 2006
131
Chapter 8: Configuring the Bands Initialization File
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
CheckAccountSize
CheckAccountSize controls whether account
numbers are a pre-determined length or can be any
length. If you disable CheckAccountSize, you can
vary account number length. If you enable
CheckAccountSize, you must ensure that account
numbers are a set size. The possible values are as
follows:
7000/7X0
●
CheckAccountSize=0
CheckAccountSize is disabled.
●
CheckAccountSize=1*
CheckAccountSize is enabled.
You can configure account size on the System
Parameters section in the CRS Front End.
CheckResourceSize
Resources in the CRS Front End are cards, such as
DPRI cards and CNF cards. If you enable
CheckResourceSize, the system checks the size of
resources that you enter. For example, DPRI cards
can be 30 or 60 ports in size. This parameter is an
historical parameter and is usually no longer used. By
default, CheckResourceSize=0*.
7000/7X0
ReadOnlyCompanies
The ReadOnlyCompanies parameters restricts
access to company data on the CRS database, which
is called BSRes2. If you enable
ReadOnlyCompanies, Operators cannot edit
company data. If you disable ReadOnlyCompanies,
Operators can add new companies, update existing
companies, and delete companies. The possible
values are as follows:
7000/7X0
●
ReadOnlyCompanies=0*
ReadOnlyCompanies is disabled.
●
ReadOnlyCompanies=1
ReadOnlyCompanies is enabled.
5 of 10
132
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
ReadOnlyClients
Similarly, ReadOnlyClients restricts access to client
data on the CRS database, which is called BSRes2. If
you enable ReadOnlyClients, Operators cannot
edit client data. If you disable ReadOnlyClients,
Operators can add new clients, update existing clients,
and delete clients. The possible values are as follows:
7000/7X0
●
ReadOnlyClients=0*
ReadOnlyClients is disabled.
●
ReadOnlyClients=1
ReadOnlyClients is enabled.
ReadOnlyBooking
Similarly, ReadOnlyBooking restricts access to
reservation data on the CRS database, which is
called, BSRes2. If you enable ReadOnlyBooking,
Operators cannot edit reservation data. If you disable
ReadOnlyBooking, Operators can add new
reservations, update existing reservations, and delete
reservations. The possible values are as follows:
●
7000/7X0
ReadOnlyBooking=0*
ReadOnlyBooking is disabled.
●
ReadOnlyBooking=1
ReadOnlyBooking is enabled.
RoewelD
For most customers, RoeweID is disabled and the
Main ICC field is displayed as the Main ICC field. This
field refers to credit card payments for conferences. If
RoeweID is enabled, this field accepts a numeric
value, such as employee number. This was a
customer request.
7000/7X0
ExpandRepeats
ExpandRepeats determines whether the CRS Front
End automatically expands a repeat conference
request. In other words, ExpandRepeats determines
if the CRS sends a request for four conference times.
If this is not the case, ExpandRepeats determines if
the CRS asks the server to extrapolate the conference
times. If the CRS asks the server to extrapolate, it
does so based on the repeat frequency and
exclusions. You can view the functioning of
ExpandRepeats in the trace log. Avaya added the
ExpandRepeats parameter to enable the CRS Front
End to successfully work in multiple time zones.
7000/7X0
6 of 10
CS7000 System Administrator Guide for Release 9.5
September 2006
133
Chapter 8: Configuring the Bands Initialization File
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
AutoSetFilter
AutoSetFilter is now an obsolete parameter.
Originally, AutoSetFilter set the Company and
Client filters. By default, AutoSetFilter=1*.
7000/7X0
Tooltips
Tooltips are explanatory phrases that users can
view when they highlight a toolbar icon with the mouse
arrow. If you enable the Tooltips parameter, the
system displays explanatory phrases when users pass
their mouse arrow over a toolbar icon. If you disable
the Tooltips parameter is disabled, the system does
not display explanatory phrases. The possible values
are as follows:
7000/7X0
●
Tooltips=0
Tooltips are disabled.
●
Tooltips=1*
Tooltips are enabled.
GetAttempts
GetAttempts represents the amount of time, in
miliseconds, that an Operator is willing to wait for a
response from the CRS server. At the end of the
period that the GetAttempts parameter specifies,
the system displays an information message. The
information message enables an Operator to cancel a
request or wait for a further period. The further period
isequivalent to the length specified in GetAttempts.
By default, GetAttempts=1000*.
7000/7X0
ReportProgram
ReportProgram represents the folder location of the
Avaya Reports executable. If you configure
ReportProgram, you can start the Avaya Reports
application from the Reports button on the CRS Front
End. For example: C:\Avaya\CRSReports.exe.
Note: This is an optional entry.
7000/7X0
BookingRect
The X and Y coordinates of the Reservation dialog.
For example: 0,0,480,640*
7000/7X0
RecordingRect
The X and Y coordinates of the Recording dialog. For
example: 0,0,480,640*
7000/7X0
ScheduleRect
The X and Y coordinates of the Schedule dialog. For
example: 0,0,480,640*
7000/7X0
ConfereeRect
The X and Y coordinates of the Conferee Selection
dialog. For example: 0,0,480,640*
7000/7X0
7 of 10
134
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
CallerRect
The X and Y coordinates of the Caller dialog. For
example: 0,0,480,640*
7000/7X0
Backdoor
Backdoor is now an obsolete parameter. Originally,
Backdoor played a role in Avaya administration.
7000/7X0
AutoAccount
The AutoAccount parameter determines whether
the AutoAccount flag is set when you create and edit a
client. There is a corresponding AutoAccountInd on
the CRS server side, which you can apply to all clients.
If you use the AutoAccount parameter in bands.ini,
you can set this feature on a per CRS Front End basis.
7000/7X0
ScheduleColumns
ScheduleColumns determines the columns that
display in the Schedule section of the CRS Front End.
Each column has a unique numeric identifier. For
example:
0,100:1,100:2,100:3,100:4,100:8,100:9,10
0:10,100:11,100:28,100:21,100:36,100:37,
100:38,100:34,100:35,100:16,100:17,100:2
9,100:
You can configure column display on the CRS Front
End. The system saves column display to the
Bands.ini file when users exit the CRS Front End.
7000
GCDUTimer
The system automatically refreshes global conference
data (GCD) if you enable the GCDUTimer parameter.
You can disable GCDUTimer to reduce network traffic.
GCDUTimer=0
GCDUTimer is disabled.
GCDUTimer=1
GCDUTimer is enabled.
7000/7X0
8 of 10
CS7000 System Administrator Guide for Release 9.5
September 2006
135
Chapter 8: Configuring the Bands Initialization File
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
AllLanguageSupported
XMS messages have two significant features:
7000
●
Message Type . Message types include
welcome, bell, hold, conference, and so on.
●
Language Type. Language types include All,
English, and so on.
●
AllLanguageSupported determines whether
the system displays Language Type=All
messages when you select Welcome, Bell,
Hold, for a particular language.
For example, if you enable
AllLanguageSupported, the system displays XMS
messages marked LanguageType=All when you
choose a DDI branding message for an English
language DDI.
StrictValidation
StrictValidation relates to backward
compatibility. If you disable StrictValidation, the
CRS is backward compatible and CRS clients ignore
fields that they do not recognise. For example, if a
CRS client receives information from a CRS server
and does not recognize some of the fields, the client
does not display an error message. The CRS client
can process the information that it recognises. This
situation is likely to occur if a CRS server is running a
newer version of the CRS, with additional fields than
the CRS client.
If you enable StrictValidation, CRS clients do
not ignore fields that they do not recognize. The
system displays an error message if it encounters
such a field.
The possible values are:
●
7000/7X0
StrictValidation=0
StrictValidation is disabled.
●
StrictValidation=1
StrictValidation is enabled.
9 of 10
136
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 17: Login Parameters and Custom Settings (continued)
Parameter
Description
7000/7X0
SearchRect
The X and Y coordinates of the Search dialog. For
example: 0,0,480,640*.
7000/7X0
ScheduleColumns700
ScheduleColumns700 determines which columns
that the system displays in the Schedule section of the
Avaya CS700 CRS Front End. Each column has a
unique numeric identifier. For example:
0,100:1,100:2,100:3,100:4,100:8,100:9,10
0:10,100:11,100:28,100:21,100:36,100:37,
100:38,100:34,100:35,100:16,100:17,100:2
9,100:
This parameter has no value in a Avaya CS7000
environment. You can configure column display on the
CRS Front End. The system saves column display
settings in the Bands.ini file when users exit the CRS
Front End.
7X0
10 of 10
Table 18: Make Reservation Settings
Parameter
Description
7000/
7X0
Duration
Duration specifies the default duration for new
conferences. For example, if Duration=45, the
system enters 45 minutes in the Duration field on
the Reservation dialog for new conferences. By
default, Duration=0*.
7000/
7X0
TimeZone
TimeZone specifies a default timezone for new
conferences. Each timzone has a numeric identifier,
which you can configure on the System
Administration section of the CRS Front End. By
default, TimeZone=0*.
7000/
7X0
Size
Size specifies a default size for new conferences.
For example, if Size=10, the system enters 10
participants in the Size field on the Reservation
dialog for new conferences. By default, Size=0*.
7000/
7X0
1 of 5
CS7000 System Administrator Guide for Release 9.5
September 2006
137
Chapter 8: Configuring the Bands Initialization File
Table 18: Make Reservation Settings (continued)
Parameter
Description
7000/
7X0
Type
Type specifies a default type for new conferences.
Each conference type has a numeric identifier. For
example,
1=Meet Me Direct
2=Meet Me Operator Assisted
3=Management Alert
And so on. Not all customers have the full range of
conference types. Certain conference types are
specific to the Avaya CS7X0 or the CS7000.
Example values for Type are as follows:
Type=1*
Type=2
Type=3
And so on.
7000/
7X0
Language
Language specifies a default language for new
conferences. Each available language has a
numeric identifier. For example,
1=English
2=Mandarin
3=Japanese
4=Malaysian
And so on. As a System Administrator, you can
configure languages.
Example values for Language are as follows:
7000
DDI
●
Language=1*
●
Language=2
●
Language=3
●
And so on.
DDI specifies a default DDI for new conferences.
Avaya recommends that you do not set this
parameter. By default, this field is blank.
2 of 5
138
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 18: Make Reservation Settings (continued)
Parameter
Description
7000/
7X0
Priority
Priority specifies a default priority for new
conferences, as follows:
7000
●
Low priority=0
●
Normal priority=1
●
High priority=2
Based on this classification, the possible values for
Priority are as follows:
Operator
●
Priority=0
●
Priority=1*
●
Priority=2
Operator specifies a default Operator type for new
conferences, as follows:
●
None= 0
●
Assisted= 1
●
Dedicated= 2
7000
Based on this classification, the possible values for
Operator are as follows:
Recording
●
Operator=0*
●
Operator=1
●
Operator=2
If you enable the Recording parameter, the system
selects the Recording check box on the
Reservation dialog, by default. If you disable the
Recording parameter, the system does not select
the Recording check box, by default. The possible
values are:
●
7000
Recording=0*
Recording is disabled.
●
Recording=1
Recording is enabled.
3 of 5
CS7000 System Administrator Guide for Release 9.5
September 2006
139
Chapter 8: Configuring the Bands Initialization File
Table 18: Make Reservation Settings (continued)
Parameter
Description
7000/
7X0
Moderator
If you enable Moderator, the system selects the
Moderator check box on the Reservation dialog, by
default. If you disable the Moderator parameter,
the system does not select the Moderator check
box, by default. The possible values are:
7000/
7X0
●
Moderator=0*
Moderator is disabled.
●
Moderator=1
Moderator is enabled.
Demand
If you enable Demand, the system selects the
Demand check box on the Reservation dialog, by
default. If you disable the Demand parameter, the
system does not select the Demand check box, by
default. The possible values are:
Demand=0*
Demand is disabled.
Demand=1
Demand is enabled.
7000/
7X0
Data
If you enable Data, the system selects the Data
check box on the Reservation dialog, by default. If
you disable the Data parameter, the system does
not select the Data check box, by default. The
possible values are:
Data=0*
Data is disabled.
Data=1
Data is enabled.
7000/
7X0
TollFree
If you enable TollFree, the system selects the
TollFree check box on the Reservation dialog, by
default. If you disable the TollFree parameter, the
system does not select the TollFree check box, by
default. The possible values are:
TollFree=0*
TollFree is disabled.
TollFree=1
TollFree is enabled.
7000/
7X0
4 of 5
140
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 18: Make Reservation Settings (continued)
Parameter
Description
7000/
7X0
AutoPIN
If you enable AutoPIN, the system selects the
AutoPIN check box on the Reservation dialog, by
default. If you disable the AutoPIN parameter, the
system does not select the AutoPIN check box, by
default. The possible values are:
7000/
7X0
●
AutoPIN=0
AutoPIN is disabled.
●
AutoPIN=1*
AutoPIN is enabled.
SubConfSize
SubConfSize specifies a default size for new sub
conferences. For example,
SubConfSize=5.
By default, SubConfSize=0*.
CabinetRef
CabinetRef specifies a default cabinet for new
conferences. For example,
CabinetRef=3
You must base the value of CabinetRef on the
order of new cabinets in the System Administration
section of the CRS Front End.
7000/
7X0
AnyCabinetFlag
The possible values for this parameter are as
follows:
7000/
7X0
●
AnyCabinetFlag=0
If AnyCabinetFlag=0, the system disables
the Any Cabinet feature. It is unavailable to
the user on the Make Reservation dialog.
●
AnyCabinetFlag=1
If AnyCabinetFlag=1, the system displays
the Any Cabinet option at the top of the
Cabinet list on the Make Reservation dialog.
●
AnyCabinetFlag=2
If AnyCabinetFlag=2, the system displays
the Any Cabinet option at the bottom of the
Cabinet list on the Make Reservation dialog.
5 of 5
CS7000 System Administrator Guide for Release 9.5
September 2006
141
Chapter 8: Configuring the Bands Initialization File
Table 19: Conference Messages Settings
Parameter
Description
7000/
7X0
Welcome
Welcome specifies a default Welcome message on
the Messages dialog. Each message has a
numeric identifier. For example:
Welcome=200*
7000
Bell
Bell specifies a default Bell message on the
Messages dialog. Each message has a numeric
identifier. For example:
Bell=230*
7000
Hold
Hold specifies a default Hold message on the
Messages dialog. Each message has a numeric
identifier. For example:
Hold=260*
7000
EnterPinCode
EnterPinCode specifies a default message for
requesting PINs on the Messages dialog. Each
message has a numeric identifier. For example:
EnterPinCode=290*
7000
ConferenceFull
ConferenceFull specifies a default conference
full message on the Messages dialog. Each
message has a numeric identifier. For example:
ConferenceFull=294*
7000
StartLater
Startlater specifies a default conference delay
message on the Messages dialog. Each message
has a numeric identifier. For example:
Startlater=310*
7000
FirstConferee
FirstConferee specifies a default message that
the system plays to the first participant. Each
message has a numeric identifier. For example:
FirstConferee=295*
7000
PlacedInConference
PlacedInConference specifies a default
message that the system plays while the system
places each participant into their conference. Each
message has a numeric identifier. For example:
PlacedInConference=293*
7000
1 of 2
142
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 19: Conference Messages Settings (continued)
Parameter
Description
7000/
7X0
FirstHold
FirstHold specifies a default message that the
system plays to first callers, as the system places
each participant on hold. Each message has a
numeric identifier. For example:
FirstHold=299*
7000
TenMinuteWarning
TenMinuteWarning specifies a default warning
message that the system plays at a configurable
period before the end of the conference. This
warning message is the first of two. For example:
TenMinuteWarning=297*
7000
OneMinuteWarning
OneMinuteWarning specifies a default warning
message that the system plays at a configurable
period before the end of the conference. This
warning message is the second of two.
OneMinuteWarning=296*
7000
WaitForModerator
WaitForModerator specifies a default Wait For
Moderator message. Each message has a
numeric identifier. For example:
7000
WaitForModerator=298*
MultiLanguage
By default, the Avaya CS7000 contains many
messages. You can record alternative custom
messages. You can associate alternative
messages with the new DDI. If you select
MultiLanguage=1, the system makes additional
messages available for selection.
7000
2 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
143
Chapter 8: Configuring the Bands Initialization File
Table 20: Conference Options Settings
Parameter
Description
7000/
7X0
Broadcast
If you enable Broadcast, the system selects the
Broadcast check box on the Options dialog, by
default. If you disable the Broadcast parameter, the
system does not select the Broadcast check box, by
default. The possible values are:
7000/
7X0
●
Broadcast=0*
Broadcast is disabled.
●
Broadcast=1
Broadcast is enabled.
EnterTone
If you enable EnterTone, the system selects the
EnterTone check box on the Options dialog, by
default. If you disable the EnterTone parameter, the
system does not select the EnterTone check box, by
default. The possible values are:
●
7000/
7X0
EnterTone=0*
EnterTone is disabled.
●
EnterTone=1
EnterTone is enabled.
LeavingTone
If you enable LeavingTone, the system selects the
LeavingTone check box on the Options dialog, by
default. If you disable the LeavingTone parameter,
the system does not select the LeavingTone check
boxcheck box, by default. The possible values are:
●
7000/
7X0
LeavingTone=0*
LeavingTone is disabled.
●
LeavingTone=1
LeavingTone is enabled.
1 of 6
144
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 20: Conference Options Settings (continued)
Parameter
Description
7000/
7X0
Polling
If you enable Polling, the system selects the Polling
check box on the Options dialog, by default. If you
disable the Polling parameter, the system does not
select the Polling check box, by default. The possible
values are:
Polling=0*
Polling is disabled.
Polling=1
Polling is enabled.
7000/
7X0
QandA
If you enable QandA, the system selects the QandA
check box on the Options dialog, by default. If you
disable the QandA parameter, the system does not
select the QandA check box, by default. The possible
values are:
QandA=0*
QandA is disabled.
QandA=1
QandA is enabled.
7000/
7X0
RollCall
If you enable RollCall, the system selects the
RollCall check box on the Options dialog, by default.
If you disable the RollCall parameter, the system
does not select the RollCall check box, by default. The
possible values are:
RollCall=0*
RollCall is disabled.
RollCall=1
RollCall is enabled.
7000/
7X0
WaitForModerator
If you enable WaitForModerator, the system
selects the WaitForModerator check box on the
Options dialog, by default. If you disable the
WaitForModerator parameter, the system does not
select the WaitForModerator check box, by default.
The possible values are:
7000/
7X0
●
WaitForModerator=0
WaitForModerator is disabled.
●
WaitForModerator=1*
WaitForModerator is enabled.
2 of 6
CS7000 System Administrator Guide for Release 9.5
September 2006
145
Chapter 8: Configuring the Bands Initialization File
Table 20: Conference Options Settings (continued)
Parameter
Description
StreamLive
This parameter is for future use. It is an optional
setting.
StreamPlayback
If you enable StreamPlayback, the system selects
the StreamPlayback check box on the Options
dialog, by default. If you disable the
StreamPlayback parameter, the system does not
select the StreamPlayback check box, by default. The
possible values are:
●
7000/
7X0
7000
StreamPlayback=0*
StreamPlayback is disabled.
●
StreamPlayback=1
StreamPlayback is enabled.
StreamPlayback is an optional setting.
Locked
This parameter is for future use.
3 of 6
146
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 20: Conference Options Settings (continued)
Parameter
Description
7000/
7X0
NameOnEntry
The NameOnEntry parameter is related to the
RollCall parameter. The RollCall feature has
several options:
7000/
7X0
1. The system announces the name of the participant
when they enter the conference. To enable this option,
Operators select the Name On Entry check box on the
Options dialog.
2. The system announces the name of the participant
when they leave the conference. To enable this option,
Operators select the Name On Exit check box on the
Options dialog.
3. The system announces the name of the participant
both when they enter and leave the conference. To
enable this option, Operators select the Name On
Entry and Name on Exit check boxes on the Options
dialog.
If you enable the NameOnEntry parameter, the
system selects the Name On Entry check box on the
Options dialog, by default. If you do not enable the
Name On Entry parameter, the system does not
select the NameOnEntry check box, by default. The
possible values are:
●
NameOnEntry=0*
NameOnEntry is disabled.
●
NameOnEntry=1
NameOnEntry is enabled.
4 of 6
CS7000 System Administrator Guide for Release 9.5
September 2006
147
Chapter 8: Configuring the Bands Initialization File
Table 20: Conference Options Settings (continued)
Parameter
Description
7000/
7X0
NameOnExit
The NameOnExit parameter is related to the
RollCall parameter. The RollCall feature has
several options:
7000/
7X0
1. The system announces the name of the participant
when they enter the conference. To enable this option,
Operators select the Name On Entry check box on the
Options dialog.
2. The system announces the name of the participant
when they leave the conference. To enable this option,
Operators select the Name On Exit check box on the
Options dialog.
3. The system announces the name of the participant
both when they enter and leave the conference. To
enable this option, Operators select the Name On
Entry and Name on Exit check boxes on the Options
dialog.
If you enable NameOnExit, the system selects the
Name On Exit check box on the Options dialog, by
default. If you do not enable the NameOnExit
parameter, the system does not select the Name On
Exit check box, by default. The possible values are:
●
NameOnExit=0*
NameOnExit is disabled.
●
NameOnExit=1
NameOnExit is enabled.
MusicSrc
MusicSrc specifies the hold music that the system
plays prior to the arrival of the Moderator. For example:
MusicSrc=1
By default, MusicSrc=0*.
7X0
5 of 6
148
CS7000 System Administrator Guide for Release 9.5
September 2006
Table 20: Conference Options Settings (continued)
Parameter
Description
7000/
7X0
ModeratorHangup
If you enable ModeratorHangup, the conference
ends when the Moderator disconnects. The possible
values are:
7X0
●
ModeratorHangup=0*
ModeratorHangup is disabled.
●
ModeratorHangup=1
ModeratorHangup is enabled.
Security
If you enable Security, the Moderator can lock the
conference. The possible values are:
●
7X0
Security=0*
Security is disabled.
●
Security=1
Security is enabled.
NRP
NRP specifies whether the system prompts callers for
their name when they enter the conference. The
possible values are:
●
7X0
NRP=0
NRP is disabled.
●
NRP=1*
NRP is enabled.
PinMode
PinMode adds extra security to the conference. By
default, PinMode=1*.
7X0
6 of 6
CS7000 System Administrator Guide for Release 9.5
September 2006
149
Chapter 8: Configuring the Bands Initialization File
Table 21: Print Parameter Settings
Parameter
Description
7000/
7X0
DSN=DSN=Wiz1_DSN
The Data Source Name: As an Avaya
System Administrator, you must set up a
DNS using the Administrative Tools in
the Control Panel.
7000/7X0
WorkingDir=C:\AVAYA\BSFRONT\printing
The working directory for printing
reports: As an Avaya System
Administrator, you configure this
directory through the ODBC Text Setup
dialog.
7000/7X0
ConfFullRptFile=ConfDataFullReport.rpt
These files are report templates.
ConfShortRptFile=ConfDataShortReport.rpt
ConfDataFile=ConfData.csv
ReservFullRptFile=ReservDataFullReport.r
pt
Avaya recommends that you do no edit these
parameters.
These files operate on both the Avaya CS7000 and
CS7X0.
ReservShortRptFile=ReservDataShortRep
ort.rpt
ReservDataFile=ReservData.csv
CompanyRptFile=CompanyReport.rpt
ClientShortRptFile=ClientShortReport.rpt
ClientFullRptFile=ClientFullReport.rpt
CompanyDataFile=CompanyData.csv
ClientDataFile=ClientData.csv
ClientPartDataFile=ClientPartData.csv
150
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 9: Introducing the Avaya
Notification Subsystem
The Avaya Notifications Subsystem program is a fax, e-mail, and optionally, SMS broadcast
provider for the Avaya CS7000 conferencing system. This chapter describes the Notifications
Subsystem. It contains the following sections:
●
Introduction
●
Operating the Notifications Subsystem
●
Testing the Notifications Subsystem
●
Playback Streaming
Introduction
The Notifications Subsystem sends the following types of fax, e-mail, or SMS broadcasts:
●
Invitations to a booked conference
●
Confirmations of a conference booking
The system only sends confirmations to Moderators.
●
Reminders to participants of conference details
The system sends reminders at a configurable time before the conference start.
●
Notifications to make conference Moderators and participants aware of any changes or
cancellations to bookings
●
Lists of conference attendees after the conference has taken place
The system only sends attendee lists to Moderators.
The Notifications Subsystem also prepares conference recordings for streamed playback on the
Web. Users need access to RealServer™ for streamed conferences.
The Notifications Subsystem communicates with the Reservation Server and retrieves details of
notifications that it must send. It queues the requests until the conferencing system makes a
resource line available. The Notifications Subsystem is a back-end application. Once you install
and configure it, you should not need to make any changes to it.
CS7000 System Administrator Guide for Release 9.5
September 2006
151
Chapter 9: Introducing the Avaya Notification Subsystem
The system bases notifications on template text files. The system uses these templates and
populates them with the current booking information. You can update these templates
individually or all together using the Avaya Template Editor. For more information, see
Administering the Avaya Template Editor on page 205.
When the system sends a fax request, it sends a report to the Reservation Server. The report
gives details of whether the fax transmission was successful. In the case of e-mail requests, the
system does not produce this report. The Avaya Billing System can then process this
information. Invitation notifications are optionally sent to participants when a conference is
booked.
Starting the application
●
Double-click the Notifications Subsystem icon on the Windows desktop.
Figure 76: Notifications Subsystem Icon
The system displays the Notifications Subsystem screen.
Table 22 describes each field in the Notifications Subsystem screen.
Table 22: Notifications Subsystem Fields
152
Field
Description
Status
Displays the current state of the broadcast request.
Destination
Displays the destination of the broadcast.
Name
Displays the name of the broadcast receiver.
Template
Displays the templates that the broadcast is sent in.
Conf Name
Displays the conference name.
Conf Date
Displays the date that the conference took place.
Conf Time
Displays the time that the conference started.
CS7000 System Administrator Guide for Release 9.5
September 2006
Operating the Notifications Subsystem
Operating the Notifications Subsystem
Notifications Subsystem is a background application. You should not need to reconfigure it after
installation. If you make any changes to it after installation, ensure that you have a complete
knowledge of the full implications of any change.
This section describes some aspects of the Notifications Subsystem. It contains the following
sections:
●
vCalender Support
●
Internal Fax Resources
●
E-mail Transport
●
Notification States
●
Setting the Application Font
●
Deleting Faxes and E-mails
●
Adding and Testing Faxes and E-mails
●
Setting the Information Logs
vCalender Support
vCalender defines a transport and platform-independent format for exchanging calendering and
scheduling information. You can configure the Notifications Subsystem to send vCalender files
with confirmation and invitation e-mail notifications. When e-mail notification recipients open the
vCalender file, compatible applications store the details as appointments. Compatible
applications include Microsoft Outlook. The compatible applications display reminder alerts for
the conference call as they would any other appointment.
To enable vCalender support, you must configure two parameters in the Broadcast.ini file.
Table 49 describes the parameters. Here is a sample configuration:
[vCalender]
Attach=Y
WorkingDir=booking\VCal
CS7000 System Administrator Guide for Release 9.5
September 2006
153
Chapter 9: Introducing the Avaya Notification Subsystem
The Notifications Subsystem uses a configurable template file to enable customization of
vCalender content. Here is a sample template:
BEGIN:VCALENDER
VERSION:1.0
BEGIN:VEVENT
DTSTART:[STIME]
DTEND:[ETIME]
LOCATION:ENCODING=QUOTED-PRINTABLE:DDI:[DDI] PIN:[PIN]
LOCATION:ENCODING=QUOTED-PRINTABLE:DDI:[DDI] ON [LOCALDATE] AT
[LOCALTIME] & ENTER [PIN]#
SUMMARY:ENCODING=QUOTED-PRINTABLE:Conference - [CNAME]
PRIORITY:3
END:VEVENT
END:VCALENDER
Internal Fax Resources
You can configure the Notifications Subsystem to send faxes internally using the Dialogic
VFX40 solution for Windows NT.
The Notifications Subsystem requires the presence of at least one VFX40 card. A VFX40 card
is Dialogic D41ESC with a FAX40 daughter board.
E-mail Transport
The Notifications Subsystem uses Simple Mail Transport Protocol (SMTP) for e-mail transport.
In previous releases, the Notifications Subsystem used Messaging Application Programming
Interface (MAPI) but the current release also supports SMTP. MAPI is dependent on Microsoft
Outlook, but SMTP is not dependent on a particular transport provider.
As a System Administrator, you must configure the SMTP server for the connectivity and
relaying of messages. You must also configure the Broadcast.ini file to enable SMTP. The
Broadcast.ini configuration settings are listed in Table 50. Here is a sample configuration:
[SMTP]
154
CS7000 System Administrator Guide for Release 9.5
September 2006
Operating the Notifications Subsystem
Active=Y
Server=123.45.67.89
Port=25
Username=testuser5r
Password=testuser5r
Sender=<[email protected]>
Auth=N
HTML=Y
SingleTemplate=Email
Unlike MAPI, SMTP supports HTML e-mails, as well as plain text e-mails.
The Notifications Subsystem now supports single e-mail templates, on a per language basis. In
previous releases, there were as many as 100 templates per language. The Notifications
Subsystem now parses the single template and extracts the sections required for processing.
When you install the Notifications Subsystem, a sample single template, called Email1.html
is included in the installation.
The speed with which the Notifications Subsystem processes and delivers e-mails is dependent
on the e-mail transport provider. However, the Notifications Subsystem is highly efficient at
preparing e-mails for the e-mail transport provider.
Note:
The Avaya Web Portal application supports attachment functionality. Similar
applications might not have an attachment feature.
Note:
Note:
SMS transmission and e-mail transmission must be independent. However, in the
current release, if the e-mail transmission is disabled, the SMS transmission is
also disabled. To resolve this issue, ensure that you enable e-mail transmission.
Note:
This section describes the attachment settings for e-mails. It contains the following sections:
●
E-mail Attachments
●
Attachment settings
E-mail Attachments
The Notifications Subsystem attaches files to reminder type notifications when conference
users make bookings on the Web. For more information, see the Avaya Web Portal
documentation.
CS7000 System Administrator Guide for Release 9.5
September 2006
155
Chapter 9: Introducing the Avaya Notification Subsystem
Attachment settings
The system has two specific settings for attachments. These settings are in the Configuration
menu.
●
SendAttachments
If you set this parameter to Y, the scheduler sends attachments with e-mails.
SendAttachments=Y
●
AttachmentsDir
The scheduler program searches for attachments in this folder. Ensure that it matches the
Web Portal configuration.
AttachmentsDir=G:\Attachments
Notification States
When the Notifications Subsystem takes a notification request from the Reservation Server, the
request must progress through various states before completion. The Notifications Subsystem
screen displays the current request state and some additional details. There are two state
types:
●
Fax item states
Table 23 describes fax states.
●
E-mail item states
Table 24 describes fax states.
156
CS7000 System Administrator Guide for Release 9.5
September 2006
Operating the Notifications Subsystem
Table 23: Fax Item States
Icon
Item
Description
Waiting
The system has no fax resources available yet.
Requesting
The Notifications Subsystem is waiting for
acknowledgement from the DOS server of the fax
request.
Sending
The system has assigned a fax resource and is
processing the request.
SENDOK
The actual fax transmission is successful.
SENDFAIL
The actual fax transmission failed.
REPORTOK
The system has successfully sent the final details of a
fax request to the Reservation Server.
REPORTFAIL
The Reservation Server has rejected the final details of
a fax request.
TRASH
The system has tagged a fax request for deletion.
SUSPEND
The system could not send a fax and is waiting to send
the fax again. This state relates to Windows NT
internal Fax resources only.
Table 24: E-mail Item States
Icon
Item
Description
WAITING
The system has no broadcast resources available.
REQUESTING
The Notifications Subsystem is building and verifying
the e-mail item.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
157
Chapter 9: Introducing the Avaya Notification Subsystem
Table 24: E-mail Item States (continued)
Icon
Item
Description
SENDING
The system has assigned an e-mail resource and is
processing the request.
SENDOK
The actual e-mail transmission is successful.
SENDFAIL
The actual e-mail transmission failed.
2 of 2
The system removes fax and e-mail requests from the main display after the requests progress
through the various states. The system deletes requests with SENDOK, SENDFAIL, and TRASH
states when it detects them.
Setting the Application Font
Use the Application Font dialog to configure the font type on the Notifications Subsystem
front-end. You can access it from the Data menu.
Table 25: The Application Font Dialog
158
Item
Description
Font
Choose a font from the drop-down list or enter the first few
characters of the name in the field until the name is
recognized.
Font style
Check Regular or combinations of other styles.
Size
Choose a size form the drop-down list or enter a value in the
field.
Sample
This field displays a sample of the selected font style.
Script
Select the type of script from the Script drop down list.
Effects Group
Strikeout
Underline
Color
Click to put a line through the text.
Click to underline the text.
Choose a color from the drop-down list.
CS7000 System Administrator Guide for Release 9.5
September 2006
Operating the Notifications Subsystem
Setting the Application Font
1. At the Data menu, select Set Font.
2. Choose the required font, style and color.
3. Click OK.
The system implements the new settings.
Deleting Faxes and E-mails
To delete a fax or e-mail, select the item that you want to delete.
●
At the Edit menu, select Delete Highlighted items.
or
●
Press Delete.
Use the Delete dialog to delete groups of fax or e-mail broadcasts by their state.
Table 26: Deleting Selected Items
Item
Description
Status Group
WAITING
REQUEST
SENDING
SENDOK
SENDFAIL
REPORTOK
REPORTFAIL
Select to delete fax and e-mail in Waiting mode.
Select to delete fax and e-mail in Request mode.
Select to delete fax and e-mail in Sending mode.
Select to delete fax and e-mail in Send OK mode.
Select to delete fax and e-mail in Send fail mode.
Select to delete fax and e-mail in Report OK mode.
Select to delete fax and e-mail in Report Fail mode.
Buttons
Select All
OK
Cancel
Click to select all status types.
Click to delete selected types of fax and e-mail.
Click to exit the Delete Items dialog.
Deleting Items By State
1. At the Edit menu, select Delete items by State.
The system displays the Delete Items dialog.
CS7000 System Administrator Guide for Release 9.5
September 2006
159
Chapter 9: Introducing the Avaya Notification Subsystem
Figure 77: Delete Items Dialog
2. Select or deselect the items as necessary.
3. Click OK.
The system deletes the selected items.
Adding and Testing Faxes and E-mails
●
At the Insert menu, click Booking Fax/Email.
The system displays the Add Item dialog.
Figure 78: Add New Item Dialog
Use the Add New Item dialog to configure:
160
●
The type of notification. E-mail or Fax
●
What is being broadcast
●
The booking details of the conference
CS7000 System Administrator Guide for Release 9.5
September 2006
Operating the Notifications Subsystem
●
The participant details of the receiver of the notification
●
The conference details
Table 27: The Add New Item Dialog
Item
Description
E-mail
Select to send an e-mail.
Fax
Select to send a fax.
Table 28: Type Group
Item
Description
Confirm
Select to send confirmation of a conference
booking. The system uses a confirm template.
Remind
Select to send a reminder of a conference
booking. The system uses a reminder template.
Change
Select to send details of a conference booking
change. The system uses a change template.
Cancel
Select to send details of a conference booking
cancellation. The system uses a cancellation
template.
Invitation
Select to send to all participants at time of
booking. The system sends this type if you
select confirmation.
Attendance
Select to send attendance details of conference
chairman on termination of conference.
CS7000 System Administrator Guide for Release 9.5
September 2006
161
Chapter 9: Introducing the Avaya Notification Subsystem
Table 29: Conference Type Group
Item
Description
Meet Me Direct
Select a Meet Me Direct conference type. A
Meet Me Direct conference is a conference in
which callers dial into the conference using DDI
and optional PIN. A conference welcome
message is played and they are directly
transferred into conference.
Meet me (Op Asst)
Select a Meet Me Operator Assisted conference
type. A Meet Me Operator Assisted conference is a
conference in which callers dial into the system
and go into the conference where they remain
until intercepted. The caller is played a
message in bell mode. (Operator Assisted).
Dial out (Op Asst)
Select a Dial Out Operator Assisted conference
type. In this conference type, the operator sets up
the conference and dials each caller in turn,
intercepts him/her and releases him/her into
conference. (Operator Assisted).
Self dial
Select a Self Dial conference type. In this type of
conference the first person to dial in becomes
the Moderator. They can then dial each caller in
turn, intercept him/her and release him/her into
conference.
Table 30: Booking Details Group
162
Item
Description
Reference no.
Enter the Booking Reference Number.
Operator
Enter the name of the Operator.
Company
Enter the name of the company that made the booking.
Client
Enter the name of the client that made the booking.
CS7000 System Administrator Guide for Release 9.5
September 2006
Operating the Notifications Subsystem
Table 31: Participant Details Group
Item
Description
Fax
Enter the destination fax number.
E-mail
Enter the destination e-mail address.
Name
Enter the destination name.
Table 32: Conference Details Group
Item
Description
Name
Enter the Conference name.
Reference
Enter the Conference reference number.
DDI
Enter the DDI number of the conference.
PIN
Enter the PIN number for the conference.
Start Time
Enter the conference Start Time.
Start Date
Enter the conference Start Date.
Size
Enter the number of participants in the conference.
Free Text
Enter any extra information that you want to add.
Setting the Information Logs
Information logs record and display events associated with the various servers.
1. At the Logging menu, select Filter.
The system displays the Filter Logging dialog.
CS7000 System Administrator Guide for Release 9.5
September 2006
163
Chapter 9: Introducing the Avaya Notification Subsystem
Figure 79: Filter Logging Dialog
2. Select or deselect the items. All items are optional.
Table 33: Source Group
Item
Description
Reservation Server
Select to log information from the Reservation Server.
MS DOS Fax Server
Select to receive logging information from the MS DOS Fax
Server.
Internal Fax Resources
Select to receive logging information from the Internal Fax
server.
E-mail Resource
Select to receive logging information from the e-mail server.
Other
Select to log miscellaneous events.
Table 34: Level Group
164
Item
Description
Debug
Select to receive debug messages for the fax and e-mail
transmissions.
Notice
Select to receive notice messages for the fax and e-mail
transmissions.
Warning
Select to receive warning messages for the fax and e-mail
transmissions.
Error
Select to receive error messages for the fax and e-mail
transmissions.
Serious (MsgBox)
Select to log and display critical errors only.
CS7000 System Administrator Guide for Release 9.5
September 2006
Testing the Notifications Subsystem
Testing the Notifications Subsystem
Use the Process Flags dialog to suspend items at different stages by disabling the process
states. You can use this dialog for testing or debugging sessions. The different process states
are described in Table 35.
Table 35: Process Flags Dialog Box
Item
Description
WAITING
Processes fax transmissions and e-mails that are queued in the system.
SENDOK
Process fax transmissions and e-mails that are successfully sent.
SENDFAIL
Process unsuccessful fax transmissions and e-mails.
REPORTOK
Process fax transmissions to the Reservation Server.
REPORTFAIL
Process fax transmissions to the Reservation Server.
Enable All
Process all faxes and e-mails.
Setting the Process Flags
1. At the Settings menu, select Process Flags.
The system displays the Process dialog.
Figure 80: Process Selected Item States Dialog
2. Select or deselect the items as necessary.
3. Click OK.
The system sets the process flags.
CS7000 System Administrator Guide for Release 9.5
September 2006
165
Chapter 9: Introducing the Avaya Notification Subsystem
Logging Details
This dialog is a notepad. Use it to view the logging details of the Notifications Subsystem.
Table 36 describes the fields.
Table 36: Logging Details Dialog
Field
Explanation
Level
DEBUG
NOTICE
WARNING
ERROR
SERIOUS
Date
Displays the Log date.
Time
Displays the Log time.
Source
RS
FS
FX
OT
FREE TEXT
Displays Log details.
Log all events plus communications packets.
Log all events.
Log serious events.
Log errors only.
Log critical errors only.
This is the default setting.
Reservation Server.
DOS Fax Server.
Windows NT Fax Resource.
Other.
Viewing Logging Details
1. At the Logging menu, select Launch NotePad.
The system displays the FaxSched.txt Notepad screen.
166
CS7000 System Administrator Guide for Release 9.5
September 2006
Playback Streaming
Figure 81: FaxSched.txt - Notepad Screen
Note:
The faxsched2.ini file describes the full path of this file. The setting is called
FileName in the e: [Logging] section of the file.
Note:
2. Review the active window as necessary.
Playback Streaming
The Notifications Subsystem provides conference recordings that users can access and play
over an Intranet with Real Player applications. The Notifications Subsystem is responsible for
providing the audio file. The Notifications Subsystem does not set up the Web interface. The
application CWList uses a Java servlet to set up the Web access.
When you listen to recordings over the Intranet, the audio is streamed. Streaming means that
the data is downloaded and played at the same time. You do not have to wait for the entire
recording to be downloaded.
The Notifications Subsystem polls the CRS for recordings. When it locates recordings, it
converts them from wave format to the RealNetworks format.
Streaming Requirements
●
The Notifications Subsystem requires access to the conference recordings directory of the
XMS application.
●
Set the XMS to use the following recording formats: 8-bit, wave, 8kHz linear PCM.
CS7000 System Administrator Guide for Release 9.5
September 2006
167
Chapter 9: Introducing the Avaya Notification Subsystem
●
RealServer™ must be installed and set up correctly on the LAN.
●
CWList must be set up and configured.
Note:
CWList is a Avaya application. It is a Java servlet that runs on a Web server. It
enables Internet users to listen to conference recordings over the Web.
Note:
●
Web users must have a version of Real Player installed.
●
Web users require a sound card
Notifications Subsystem Alerts
The Notifications Subsystem alerts notify Operators when conferences are about to open. With
the help of alerts, Operators can prepare for, or manually open scheduled conferences.
Examples of conferences that require attention are Dial-out conferences & Meet Me Operator
Assisted conferences. In these cases, Operators monitor the conference to dial in or greet
participants.
The Notifications Subsystem polls the CRS and requests specific conference types that are
about to open. If conferences are about to open, the system sends alerts to the Operator
Console. It might also send alerts to the CRS Front End. On the CRS Front End, alerts display
as dialogs, describing conference details such as name, reference numbers, and scheduled
start times. Figure 82 shows an example.
Figure 82: Example of an Alert Dialog
The Notifications Subsystem interface has icons for three alert states.
Alert waiting to be sent
Alert processed
Alert failed
Figure 83 shows an example.
168
CS7000 System Administrator Guide for Release 9.5
September 2006
Notifications Subsystem Alerts
Figure 83: Notifications Subsystem Interface
You can configure the format of Alerts with the template, alerts.txt. Table 37 lists he
available ALIAS items.
Table 37: Alert Display
Alias
Description
RNUM
Booking reference number
CNUM
Conference reference number
CSNAME
Conference name
CSTIME
Start time
CSDATE
Start date
SECSDUE
Number of seconds before start time
MINSDUE
Number of minutes before start time
TIMEDUE
Number of seconds and minutes before start time
This section shows the alert message template. It also contains a description of the Alerts
section in Broadcast.ini. This section contains the following sections:
●
Notification Alert Message
●
Excerpt from Broadcast.ini Alerts Settings
●
Alerts Section
CS7000 System Administrator Guide for Release 9.5
September 2006
169
Chapter 9: Introducing the Avaya Notification Subsystem
Notification Alert Message
*** Attention ***
The following conference is about to open: * Conference name: [CNAME]
* Reference No : [RNUM]
* Scheduled Conf Date: [CSDATE]
* Scheduled Conf Time: [CSTIME]
Excerpt from Broadcast.ini Alerts Settings
Table 38 contains a section of the Broadcast initialization file.
Table 38: [Alerts]
Alias
Description
Active
Turn on & off alerts
TimeWindow
Time in minutes to alert before conference starts
ConfTypes
Alert conference types. Numbers are divided by comma
QandA
Alert conferences flagged for Q and A
Broadcast
Alert conferences flagged for broadcast
Console
Send alerts to Operator Consoles
FrontEnd
Send alerts to Front Ends, such as the CRS Front End
WorkingDir
Path where alerts.txt template is stored
Alerts Section
Active=N
TimeWindow=10
ConfTypes=2,4
QandA=N
Broadcast=N
Console=Y
FrontEnd=N
WorkingDir=\Avaya\broadcast\Booking
170
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 10: Configuring the Avaya
Notifications Subsystem
This chapter outlines the different fields that are available in the configuration section of the
Notifications Subsystem. You can configure the application settings in the initialization file
Broadsys.ini in the WINDOWS directory.
This chapter contains the following sections:
●
Configuration Fields
●
File Templates
●
Configuring Multilingual Notifications
●
Customizing Fax Logos
CS7000 System Administrator Guide for Release 9.5
September 2006
171
Chapter 10: Configuring the Avaya Notifications Subsystem
Configuration Fields
Table 39: Communication
Field
Description
ResServerIP
TCP IP address of reservation server PC i.e.
192.168.1.5. If this entry is blank the thread that
communicates to the server will not be started.
ResServerPortID
Port ID of reservation server PC i.e. 5050
FaxServerIP
TCP IP address of MS DOS fax server PC i.e.
192.168.1.17. If this entry is blank the thread that
talks to the fax server will not be started.
FaxServerPortID
Port ID of fax server i.e. 9090
Table 40: Logging
Field
Description
Status
On/off state of event logging. This should be set
through the front end logging menu items.
Source
This item dictates what types of events are required.
This should be set through the front-end logging filter
dialog.
Level
This item dictates the levels of events required. This
should be set through the front-end logging filter
dialog.
FileName
Name of logging text file.
MaxFileKSize
The maximum size in kilobytes of the logging file.
Table 41: Fax Resources
Field
Description
Active
If ‘Active’ is not set to ‘Y’ no faxes will be sent.
NumResources
The number of internal Dialogic fax channels available.
StartResource
The start fax channel number (1 based).
1 of 2
172
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuration Fields
Table 41: Fax Resources (continued)
Field
Description
NumSendAttempts
Maximum number of times to attempt to send a fax in
case of failure.
SuspendTime
Time in seconds to wait before re-sending an
unsuccessful fax.
WorkingDir
Internal working directory and position of fax template
files.
2 of 2
Table 42: E-mail
Field
Description
Active
If ‘Active’ is not set to ‘Y’ no e-mails will be sent.
Profile
Name of e-mail transport provider i.e. MS Outlook.
Password
Password to get access to e-mail transport provider.
WorkingDir
Internal working directory and position of e-mail
template files.
CS7000 System Administrator Guide for Release 9.5
September 2006
173
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 43: Settings
Field
Description
ProcessFlags
This item describes what states to process. It is
useful for testing purposes. This should be set using
the front-end Settings/Process Flags dialog.
InternalGMT
If this item is set to Y all communication with the
reservation server is in GMT. If this is not set to T
communication is in local time.
RecordingTemplate
If RecordingTemplate is set to Y template file names
are composed based on the recording status of a
conference. If a conference is tagged for recording
‘b’ is tagged to the name. If recording is off ‘a’ is
tagged
E.g. ‘Meet me direct’ conference with recording on
will use the template CONFIRM1B.TXT template.
RepeatBookingTemplate
If RepeatBookingTemplate is set to Y template file
names are composed based if the reservation for a
single conference or repeat conferences. If it is a
repeat booking ‘b’ is tagged to the name. If it is a
single conference booking ‘a’ is tagged.
E.g. ‘Meet me direct’ repeat booking would produce
the template: CONFIRM1AB.TXT template.
ResServerRequestInterval
This item sets the interval in minutes for fax data
requests from the reservation server.
DateFormat
Sets the mask for all dates in e-mail or fax output.
TimeFormat
Sets the mask for all times in e-mail or fax output.
LanguageTemplate
Sets multilingual support. For more information, see
Configuring Multilingual Notifications on page 194.
The date and time formats follow the same rules, except that with dates, the character M refers
to months and with times the character M refers to minutes.
Table 44: Date and Time Formats
Format
Description
YY
2-character year i.e. 04.
YYYY
4-character year i.e. 2004.
1 of 2
174
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuration Fields
Table 44: Date and Time Formats (continued)
Format
Description
M
Numeric month with no leading zeros i.e. 11 or 4.
MM
Numeric month with leading zeros i.e. 11 or 04.
Mmm
English text month with 3 characters i.e. Jan.
MMM
English text month with 3 capital characters i.e. JAN.
Mmmm
English text month with all characters i.e. January.
MMMM
English text month with all capital characters i.e. JANUARY.
D
Numeric date with no leading zeros i.e. 11 or 4.
DD
Numeric date with leading zeros i.e. 11 or 04.
Ddd
English text day with 3 characters i.e. Mon.
DDD
English text day with 3 capital characters i.e. MON.
Dddd
English text day with all characters i.e. Monday.
DDDD
English text day with all capital characters i.e. MONDAY.
H
Numeric hour with no leading zeros i.e. 11 or 4.
HH
Numeric hour with leading zeros i.e. 11 or 04.
M
Numeric minute with no leading zeros i.e. 11 or 4.
MM
Numeric minute with leading zeros i.e. 11 or 04.
S
Numeric second with no leading zeros i.e. 11 or 4.
SS
Numeric second with leading zeros i.e. 11 or 04.
TTT
AM/PM clock i.e. 10:30pm 1:00am.
Ttt
AM/PM clock i.e. 10:30p 1:00a.
TTTT
Standard 24-hour clock with colon separators and no seconds.
TTTTTT
Standard 24-hour clock with colon separators and seconds.
2 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
175
Chapter 10: Configuring the Avaya Notifications Subsystem
You can use literals, such as, i.e. / or :
Table 45: Literals
Format
Description
DD/MM/YYYY
18/07/1969.
MM-DD-YY
07-18-69.
Dddd Mmmm D
Friday July 2.
TTT
9:30pm.
Ttt
09:30p.
TTTT (DDDD)
10:10 (Friday.)
TTTTTT
10:08:10.
Table 46: Reports
Format
Description
Active
Turn on/off attendance reports (=N)
PollingDir
Directory of raw report files (by PC Reports) (C:\
Avaya\Broadcast\PCReport\Output)
PolllingPeriodMins
How often to search for report files (3)
WorkingDir
Path for report template (C:\Avaya\Broadcast\
REPORT)
DestinationDir
Directory to build raw reports (for testing only)
(C:\Avaya\Broadcast\PCReport\Output)
Table 47: Templates
176
Format
Description
SysOwner1
Generic Alias used on all templates
(SAMPLE NOTIFICATION)
SysOwner2
Generic Alias used on all templates
(Sample Company)
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuration Fields
Table 48: SMS Template Settings
Parameter
Description
Active
Turn on/off SMS resource
WorkingDir
Path of SMS templates
IP
IP address of SMS Controller (Server)
PORT
Port of SMS Controller (Server)
ClientTemplates
Use client template set
CompanyTemplates
Use company template set
WholesalerTemplates
Use wholesaler template set
Table 49: VCalendar
Parameter
Description
Attach
Enables the vCalender feature. Attach=Y
enables the feature and Attach=N disables
the feature.
WorkingDir
The system uses the vCalender working
directory to locate the template file
vCalender1.txt. In this case, 1 refers to
language ID 1. For more information on
languages, see Configuring Multilingual
Notifications on page 194.
Table 50: SMTP
Parameter
Description
Active
Enables the SMTP server. Active=Y enables
the server and Active=N disables the server.
Server
Identifies the SMTP server IP or name.
Port
Identifies the SMTP server port number. The
default value is Port=25.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
177
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 50: SMTP (continued)
Parameter
Description
Username
User account name. You must configure this
setting if you set Auth=Y. Auth=Y adds a level
of security and means that the user must
undergo an authentication process. The
authentication process involves entering a
username and a password.
Password
User password. You must configure this setting
if you set Auth=Y. Auth=Y adds a level of
security and means that the user must undergo
an authentication process. The authentication
process involves entering a username and a
password.
Sender
Enter the e-mail address that you would like the
system to display in the receivers’ From field in
their e-mail Inbox. Enter the e-mail address in
the following format:
Sender=<[email protected]>
Auth
If you set Auth=Y, the user must enter a
username and a password. If you set Auth=N,
the user does not have to enter a username
and a password.
HTML
To send the e-mail as a HTML e-mail, set
HTML=Y. To send the e-mail as a plain text
e-mail, set HTML=N.
SingleTemplate
If you set SingleTemplate=Email, the
system uses a single e-mail template.
2 of 2
Example SMS Settings
[SMS]
Active=N
WorkingDir=Booking\SMS
IP=127.0.0.1
PORT=4500
ClientTemplates=N
CompanyTemplates=N
WholesalerTemplates=N
178
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuration Fields
All streaming configurations are in the section Streaming in the broadcast.ini file in the
Windows directory. Table 51 describes the streaming settings.
Table 51: Streaming Configuration
Parameter
Description
Active
If set to Y, the Notifications Subsystem converts required
recordings to the correct streaming format.
XMSDir
This is the folder used by the XMS application to store
conference recordings. The computer containing the
scheduler must have visibility of the XMS computer.
DestinationDir
This is the folder used by RealServer™ to hold the
streaming files. This is typically in the content folder of the
installed RealServer™ package.
SourceEXT
This is the extension of the XMS conference recordings
and is usually set to wav.
EMSVerPost7_52
The format of storing recordings has changed with EMS
upgrades. The scheduler uses this configuration setting
for backward compatibility. If the installed version of EMS
is greater than 7.52, this item should be set to Y.
EMSVerPost8_00
If the installed version of EMS is greater than 8.00 set this
item to Y.
ServerIP
The IP address of the machine on which you install
RealServer™.
ServerPort
This is the port number of the streaming protocol. It is
usually 7070. Consult the RealServer™ settings for more
information.
ServerProtocol
This is the mnemonic protocol. It is usually pnm. Consult
the RealServer™ settings for more information.
RAMDestinationDir
This is the destination of RAM files used by the CWList.
InfoFileActive
Info files are text files containing extra information about
the audio streams, such as company, client, conference
name, reference, and so on. This information enables third
party Web applications to provide access to the streams. It
was developed for a particular customer and is not usually
active. To activate it, set it to Y.
InfoFileDir
This is the directory on the local area network in which to
store info files.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
179
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 51: Streaming Configuration (continued)
Parameter
Description
InfoFileExt
This is the file extension of the info files. For example,
InfoFileExt=Info
CopyFileOnly
When set to Y, the Notifications Subsystem copies the
wave file into the web directory without conversion to the
RealNetworks format. Microsoft Media-Player may be
used as an alternative to stream the audio files.
2 of 2
File Templates
File templates describe the layout and content of a notification. These files are American
StandardCode for Information Interchange (ASCII), text based, and contain a mixture of text
and control keywords. Before a notification is sent, a temporary file is built based on a file
template and the individual data associated with a booking. There are two types of control
keywords that may be included in a file templates; Alias controls and Command controls.
File templates are based on notification type, conference type, recording state and booking
types; single and repeat. There are six types; confirm, remind, cancel, change, attendance, and
invitation. There are several conference types; Meet Me Direct, Meet Me Operator Assisted,
Meet Me Toll Free, Dial Out Operator Assisted, Self-Dial, Marketeer, and Self Registration
(recognized by the bridge as Meet Me Secure). Fax templates are stored in the directory
described by the INI setting [Fax Resource] WorkingDir=, e-mail templates by the configuration
[E-mail] WorkingDir.
Each release of Notifications Subsystem builds on the number of templates shipped with the
application. This release contains extra invitation templates.
Any editor may be used as long as the file is saved in an ASCII format. An editor that uses
non-proportional fonts is recommended to get a better sense of the resulting fax output i.e.
NOTEPAD.EXE.
This section describes file templates. It contains the following sections:
180
●
File Template Naming Conventions
●
Template Name Examples
●
Alias Controls
●
Alias Control Character * and +
●
Attendance Reports
●
Fax Command Controls
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
●
Character Attribute Commands
●
Character Code Commands
●
E-mail Command Controls
File Template Naming Conventions
File templates are based on fax type, conference type, recording state and booking types. The
system chooses a template, based on these items.
Table 52: Fax Type
Fax Types
Meaning
Start of Template
Name
Confirm
Sent to chairperson to confirm a
conference has been booked
and verify all booking details.
CONFIRM???
Remind
Sent to all conference
participants before conference
to remind of DDI times etc.
REMIND???
Cancel
Sent to chairperson to confirm a
conference booking has been
cancelled.
CANCEL???
Change
Sent to all conference
participants to make aware of
new times, DDI etc.
CHANGE???
Attendance
Sent to Moderator after the
conference closes if PCReports
is installed.
ATTEND???
Invitation
Sent to send attendance details
of conference chairman on
termination of conference.
INVITE???
CS7000 System Administrator Guide for Release 9.5
September 2006
181
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 53: Conference Type
Fax Types
Meaning
Start of Template
Name
Meet Me Direct
Dial in conference.
1
Meet Me Operator
Assisted
Dial in handled by the Operator.
2
Meet Me Toll Free
Dial in for free.
3
Dial Out Operator
Assisted
Operator dials participants.
4
Self dial
Chairperson dials in
participants.
5
Marketeer
Special conference type.
10
Meet Me Secure/Self
Registration
Participants pre-register using
an online form.
13
If the configuration item RepeatBookingTemplate is set to Y in the Broadcast.ini file,
the letter ‘A’ is attached to the template name if the booking is a single booking. The letter ‘B’ is
attached to the template name if the booking is a repeat booking. In other words, if the
configuration item RecordingTemplate is set to Y in the Broadcast.ini file, the letter ‘A’ or
‘B’ is attached the template name depending on the conference recording state. If recording is
on, ‘B’ is added. If not, ‘A’ is added.
Table 54: Repeat and Recording Flags
182
On/Off
Recording
Repeat Booking
On
B
B
Off
A
A
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
Template Name Examples
Table 55: Template Example
Action
Conference
Type
Repeat
Bookin
g
Recordin
g
Template Used
Confirmation
Meet Me Direct
No
Off
CONFIRM1AA.TXT
Remind
Meet Me Direct
Yes
Off
REMIND1BA.TXT
Cancel
Dial Out Op
Assist
No
Off
CANCEL4AA.TXT
Change
Self Dial
No
Yes
CHANGE5AB.TXT
Alias Controls
Alias controls are keywords that correspond to individual pieces of data associated with a
conference booking. Alias controls are removed and are replaced by the actual piece of booking
data required. The Alias keyword is enclosed by the bracket characters ‘[‘ and ‘]’. An Alias
keyword such as [CSDATE] meaning ‘conference start date’ is replaced by something like ‘18
July 2004’. The following is a list of all available Alias keywords:
Table 56: Alias Controls
Alias Name
Meaning
Example
RNUM
Booking reservation number.
55231122.
CNUM
Conference reference number.
221133.
CNAME
Conference name.
End of quarter sales.
CSTIME
Conference start time.
18:30.
CETIME
Conference end time.
CSDATE
Conference start date.
CEDATE
Conference end date.
18 July 2004.
1 of 3
CS7000 System Administrator Guide for Release 9.5
September 2006
183
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 56: Alias Controls (continued)
Alias Name
Meaning
Example
CMTIME
Conference booking modified
time.
23:50.
CMDATE
Conference booking modified
time.
21 August 2004.
FTEXT
Comment box/Free text.
Visit us at inventus
www.inventus.com.
NAME
Participant name.
John Smith.
FAXNUMBER
Receiver’s fax number.
5552288.
EMAILADR
Receiver’s e-mail address.
[email protected]
company.com.
DDI
Conference direct dial in.
668822.
PIN
Conference PIN entry number.
113254.
CPIN
Conference conferee PIN
321321.
MPIN
Conference moderator PIN
987654.
UNAME
Operator name.
Ms Jones.
CMNAME
Company name.
IBI Ltd.
CLNAME
Client name.
Mr. John Smith.
CFREES
Conference participant size.
8.
DATE
Current date (see
DateFormat.)
Friday January 2004.
TIME
Current time (see
TimeFormat.)
9:10pm.
CHAIRNAME
Name of chairperson.
Mr Davids.
CHAIREMAIL
E-mail of chairperson.
[email protected]
company.com
TZONE
Conference time zone.
DST
LOCALTIME
Conference local time.
12.00.
LOCALDATE
Conference local date.
18 July 2004.
PPIN
Participant PIN.
654654.
2 of 3
184
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
Table 56: Alias Controls (continued)
Alias Name
Meaning
Example
CLNUM
Client reference.
665544.
CMNUM
Company reference.
998877.
CLACC
Client a/c.
9955112233.
DDIS1
Number of DDIs associated
with conference
2
DPIN
PIN associated with multiple
DDIs.
554400.
DDILOCAL2
Location associated with DDI.
Dublin.
DDIPHONE
Phone no. associated with DDI.
951951.
SysOwner13
The owner of the system. Free
text field.
Avaya Inc.
SysOwner2
Second line of the system
owner name. Free text field.
Limited
SysAdr1
First line of the address of the
system owner. Free text field.
21 Stillorgan Industrial
Park,
SysAdr2
Second line of the address of
the system owner. Free text
field.
Stillorgan,
SysAdr3
Third line of the address of the
system owner. Free text field.
County Dublin.
SysURL1
Typically used for Self
Registration or Data Xchange
links.
www.Avaya.com
SysURL2
Typically used for Self
Registration or Data Xchange
links.
www.selfreg.com
SysURL3
Typically used for Self
Registration or Data Xchange
links.
www.dataxchange.com
3 of 3
1. DDIs and DPIN are optional if Multiple DDIs=Y in Broadcast.ini.
2. DDILOCAL and DDIPHONE are optional if multiple DDIPhones=Y in Broadcast.ini.
3. The following fields are declared in the Broadcast.ini. They are system-wide and
do not varying per booking.
CS7000 System Administrator Guide for Release 9.5
September 2006
185
Chapter 10: Configuring the Avaya Notifications Subsystem
File Template Example
WORLD CONFERENCE for [CMNAME]
Reservation No:
Company:
[RNUM]
[CMNAME]
Appears as:
WORLD CONFERENCE for IBI Ltd
Reservation No:
Company:
55231122
IBI Ltd
Alias Control Character * and +
Using an asterisk character after the Alias name i.e. [CNUM*] gives the Alias control a special
meaning. It implies that there are multiple conference reference numbers in a reservation. This
happens for a repeat booking and the configuration setting RepeatBookingTemplate is set to ‘Y’.
The first conference reference number replaces the keyword [CNUM*]. Use + when the variable
is value is needed again. All following conference reference number will appear on the same
column of the following lines. An example from a file template:
Conference number
[CNUM*]
Date
Time
DDI
PIN
[CSDATE*][CSTIME*][DDI*][PIN*]
May appear as:
Conference number
Date
Time
DDI
PIN
600112
600113
600114
21July 2004
22July 2004
23July 2004
09:00
09:00
09:00
6699
6699
6699
221423
221423
221423
Attendance Reports
Table 57: Alias Controls
Alias Name
Meaning
Example
PSDATE
Participant entry date.
18 November 2004.
PSTIME
Participant entry time.
9:10pm.
PEDATE
Participant exit date.
18 November 2004.
PETIME
Participant exit time.
9:10pm.
CLI
Participant CLI/ANI
1234564.
1 of 2
186
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
Table 57: Alias Controls (continued)
Alias Name
Meaning
Example
NAME
Participant name.
Mr. Thomas.
RNUM
Booking reference number.
654321.
CNUM
Conference reference number.
654987654.
CNAME
Conference name.
Sales Meeting.
CSTIME
Conference start time.
3.15pm.
CSDATE
Conference start date.
21 November 2004.
CETIME
Conference end time.
3.45pm.
CEDATE
Conference end date.
21 November 2004.
FAXNUMBER
Participant’s fax number
6546544.
EMAILER
E-mail address
[email protected]
UNAME
Booking operator name.
Mary White.
CMNAME
Company name.
Company.com.
CLINAME
Client name.
Sales Dept.
CFREES
Number of participants.
20.
DATE
Current date.
21 November 2004.
TIME
Current time.
10.58.
2 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
187
Chapter 10: Configuring the Avaya Notifications Subsystem
Fax Command Controls
A fax’s appearance is controlled by eleven fields. The command keywords are enclosed by the
brace characters ‘{‘ and ‘}’ i.e. {PAGE}. Some command keyword take arguments separated by
the forward slash ‘/‘ character i.e. {IMPORT/LOGO.TIFF}. Some command keywords also have
sub-arguments separated by the comma ‘,’ i.e. {BOX/1/1,2,3}.
Table 58: Import Fax Command
Import
Description
Usage
{IMPORT/Filename.}
Meaning
Embed file in fax.
Argument
Filename.
Description
The command inserts a file at this point in the
file. Files may be of type ASCII or TIFF/F. If the
file extension is ‘tif’ the file is assumed to be of
type TIFF/F. Any other extension is assumed to
be ASCII.
Example
{IMPORT/LOGO.TIF.}
Table 59: Page Fax Command
Page
Description
Usage
{PAGE.}
Meaning
Starts new page.
Description
This commands specifies that the text following
will start on a new page.
Table 60: Box Fax Command
Box
Description
Usage
{BOX/Box type/ID1 [, ID2][, ID3].}
Meaning
Draw box on fax document.
1 of 2
188
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
Table 60: Box Fax Command (continued)
Box
Description
Argument
Box type
Box ID 1
Box ID N (Optional.)
Description
This command specifies that a text box should be drawn
starting with the top left corner at the character ‘{‘ before
the BOX text. The first argument defines the type of text
box to draw. The four types are:
●
Single line box
●
Double line box
●
Single horizontal and double vertical lines
●
Single vertical and double horizontal lines
The next argument is the box ID. This is used with the
BEND (box end) command. There can be any number of
Ids separated with commas.
2 of 2
Table 61: Bend Fax Command
Bend
Description
Usage
{BEND/ID1[,IDn].}
Meaning
Box end.
Argument
Box ID 1
Box ID N (Optional.)
Desc
This command specifies the end of a text box.
The bottom right corner is at the character ‘}‘ at
the end of the BEND command.
Example
See the above BOX example.
Table 62: Abox Fax Command
Abox
Description
Usage
{ABOX/Box type/ ID/ Alias control.}
Meaning
Alias box.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
189
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 62: Abox Fax Command (continued)
Abox
Description
Argument
Box type
Box ID
Alias control name.
Desc
An Alias Box acts as a BOX command with an
ALIAS control text formatted inside the box
area. Only one ID is allowed and the box is
terminated with a BEND command.
2 of 2
Character Attribute Commands
The character attribute commands are: B, b, U, u, F, f
●
{B} Turn bold on. The text following will be bold.
●
{b} Turn bold off. The text following will not be bold.
●
{U} Underline on. The text following will be underlined.
●
{u} Underline off. The text following will not be underlined.
●
{F} Use large fonts. The text following will use large fonts.
●
{f} Use small fonts. The text following will use small fonts.
Character Code Commands
A numeric value representing the Modified ASCII 437 character set may be placed between
square brackets i.e. [204] etc the numbers are taken to be values over 200 and values below
200 will have 200 added to them.
E-mail Command Controls
Note:
190
Note:
The maximum e-mail address size, used within notifications, is 64 characters.
Any additional characters are truncated.
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
Currently there are a number of control commands for e-mail broadcast.
Table 63: Attach E-mail Command
Attach
Description
Usage
{ATTACH/Filename[*].}
Meaning
Attach file to e-mail.
Argument
Name of file to attach.
Description
This command attaches a file to an e-mail
broadcast. If the * character is specified the
filename is an absolute path otherwise the
filename is appended to the e-mail working
directory before being attached.
Example
{ATTACH*/C:\ART\BITMAP.BMP.}
Table 64: Repeat E-mail Command
Attach
Description
Usage
{REPEAT/ number of times/ content}
Meaning
Includes multiple rows of conference related
data
Argument
Times to repeat data
Description of ASCII data to repeat
Description
This command is used to display multiple lines
of data. The first arguement describes the
number of times to display the content. This
numeric value is generally an ALIAS value,
such as CONFS or DDIS. ALIAS values may
also be included in the content arguement. Use
the asterisk character to take the ALIAS values
from the related list rather than taking one static
value.
Example
{REPEAT/DDIS/*Dial-in
Number:[DDI*][DDILOCAL*][DDIPHONE*]}
CS7000 System Administrator Guide for Release 9.5
September 2006
191
Chapter 10: Configuring the Avaya Notifications Subsystem
Table 65: IFIS E-mail Command
Attach
Description
Usage
{IFIS/ check value 1/ check value 2/ content}
Meaning
Includes data text only on condition
Argument
Check value one. Usually an ALIAS item.
Check value two. Usually a constant value.
Content.
Description
This command compares the check arguments
1 and 2. If they are the same, the content text is
inserted into the e-mail.
Example
{IFIS/DATAIND/1/* Data conference:
[SYSURL2]\[CNUM].html}
Table 66: IFNOT E-mail Command
Note:
192
Attach
Description
Usage
{IFNOT/ check value 1/ check value 2 / content}
Meaning
Includes data text only on condition
Argument
Check value one. Usually an ALIAS item.
Check value two. Usually a constant value.
Content.
Description
This command is opposite to IFIS. It compares
the check arguments 1 and 2. If they are not the
same, the content text is inserted into the
e-mail.
Example
{IFNOT/DATAIND/1/* Data conference:
[SYSURL2]\[CNUM].html}
Note:
The forward slash character should not be included in any of the above content
arguments. If URLs are required, they should be configured in Broadcast.ini and
the ALIAS items SysURL1 or SysURL2 should be used to reference them.
CS7000 System Administrator Guide for Release 9.5
September 2006
File Templates
Example confirm1aa.txt template
INVENTUS WORLDCONFERENCE
Date:
[DATE]
Time:
[TIME]
Reference No:
[RNUM]
Company Name:
[CMNAME]
E-mail Address
: [EMAILADR]
For Attention:
[NAME]
-----------------------------------------DIAL-IN CONFERENCE CONFIRMATION
Your conference has been confirmed for [CSDATE] at [CSTIME].
Here are the calling instructions for your DIAL-IN conference.
1. Dial [DDI] from the country you are in. Or dial the Irish Direct toll-free
number and follow the voice prompt for a Home EasyDial call.
2. At the voice prompt, press the 6-digit Conference Code [CNUM] and the # key.
3. You are connected to the conference if your Conference Code is correct.
Otherwise, you are transferred to an EireTelly Conference Co-ordinator for
assistance.
4. Press * and 0 for the assistance of a Conference Co-ordinator during the
conference.
5. If you are disconnected for any reason, you can dial [DDI] and Conference Code
[CNUM] to continue with your Conference or call the Conference Center at
1800-555-3312 (local toll-free) or +(322) 234 2222 (overseas) for further
assistance.
-----------------------------------------Your conference call is booked as follows:
* Start Conf Date:
[CSDATE]
* Start Conf Time:
[CSTIME]
* Conference Ref:
[CNUM]
* Participants:
[CFREES]
* Dial in code:
[DDI]
* Pin access code:
[PIN]
* Web console:
www.avaya.com
-----------------------------------------Thank you for choosing Avaya WorldConference.
[UNAME]
Asst Telecom Service Executive
[FTEXT]
CS7000 System Administrator Guide for Release 9.5
September 2006
193
Chapter 10: Configuring the Avaya Notifications Subsystem
Configuring Multilingual Notifications
You can configure the Notifications Subsystem to send conference notifications in a number of
different languages. This feature is an especially efficient and powerful feature if participants
with different languages regularly attend the same conference. For example, if you configure
the Notifications Subsystem to send notifications in French, German, and Spanish, the French
participants receive notifications in French, the German participants receive notifications in
German, and the Spanish participants receive notifications in Spanish.
For the majority of notifications, the participant language determines the notification language
choice. If a participant is associated with the Italian language, you can configure the
Notifications Subsystem to send them Italian notifications. Operators set the participant
language when they create new participants in the CRS Front End. Figure 84 displays the New
Participant dialog.
Figure 84: New Participant Dialog
The participant language determines the notification language choice for the following
notification types:
●
Confirmation
●
Invitation
●
Change
●
Reminder
●
Cancellation
However, the attendance notifications operate differently. The Notifications Subsystem sends
attendance notifications to the conference Moderator once the conference has taken place.
Attendance notifications are multilingual, however, the notification language choice is based on
the conference language and not the participant language. Operators set the conference
language when they create new reservations in the CRS Front End. Figure 85 displays the
Check Reservation dialog.
194
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring Multilingual Notifications
Figure 85: Check Reservation Dialog
To configure multilingual language support, you must configure a parameters in
Broadsys.ini in the WINNT directory. The parameter is
LanguageTemplate=Y
Set LanguageTemplate to Y to support multilingual notifications. If you set
LanguageTemplate to N, the system sends notifications in a single language.
Language Template Locations
The notifcations that are based on participant language are stored here:
C:\Avaya\BROADCAST\Booking\Email\Lang1
C:\Avaya\BROADCAST\Booking\Fax\Lang1
C:\Avaya\BROADCAST\Booking\SMS\Lang1
For each new language, you must create folders called Lang2, Lang3, and Lang4 under the \
Email, \Fax and \SMS directories. It is important to note that Avaya has not translated each of
the notification templates. Customers must copy the directories and translate the notification
template text. Figure 86 displays the directory structure.
CS7000 System Administrator Guide for Release 9.5
September 2006
195
Chapter 10: Configuring the Avaya Notifications Subsystem
Figure 86: Directory Structure for Multiple Languages
C:\
Avaya
BROADCAST
Booking
Email
Lang1
Lang2
Lang3
Lang4
Fax
Lang1
Lang2
Lang3
Lang4
SMS
Lang1
Lang2
Lang3
Lang4
Directory Structure for Multiple Languages
The attendance notification template is stored in a different location. The attendance template is
stored here:
C:\Avaya\BROADCAST\Report\Booking\Email\Lang1
C:\Avaya\BROADCAST\Report\Booking\Fax\Lang1
C:\Avaya\BROADCAST\Report\Booking\SMS\Lang1
196
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring Multilingual Notifications
Figure 87 displays the directory structure.
Figure 87: Directory Structure for Attendance Notifications
C:\
Avaya
BROADCAST
Report
Booking
Email
Lang1
Lang2
Lang3
Lang4
Fax
Lang1
Lang2
Lang3
Lang4
SMS
Lang1
Lang2
Lang3
Lang4
Directory Structure for Attendance Notifications
CS7000 System Administrator Guide for Release 9.5
September 2006
197
Chapter 10: Configuring the Avaya Notifications Subsystem
Customizing Fax Logos
This section describes how to customize fax logos. It consists of the following sections:
●
Hardware Requirements
●
Fax Templates
●
TIFF Files
●
Customizing Fax Logos
●
Converting to a TIFF Image
●
Converting BMP to TIFF/F using TIFFKIT
●
Applying TIFF/F to Fax Template
Hardware Requirements
In order to send faxes, a dialogic VFX40 is required. This card requires a full length PCI slot and
has resource of 4 analogue voice/fax channels. The Notifications Subsystem application should
be configured to use one or more of these fax channels. The remaining channels may be left for
use with the XMS configuration.
Fax Templates
Fax notifications are built based on a set of supplied templates with the Notifications Subsystem
application. Templates are text based that describe the format of final delivered fax. The
Scheduler loads in the appropriate template and embeds run-time conference data before
dialling the given fax number. Monochrome graphics may also embedded using the IMPORT
keyword in a fax template.
For example:
Template: CONFIRM1AA.TXT
{IMPORT/HeadingLogo.tif}
{BOX/1/1,2}
To:[NAME]
Scheduled by Inventus
[CMNAME]
On: [DATE]
At: [TIME]
Modified by Inventus
198
CS7000 System Administrator Guide for Release 9.5
September 2006
Customizing Fax Logos
To:[NAME]
Scheduled by Inventus
Fax: [FAXNUMBER]
On: [CMDATE]
Date: [DATE]
At: [CMTIME]
{BEND/1}
{BEND/2}
Your TeleConference is now scheduled
Please advise your TeleConference participants of the following:
{BOX/1/3,4}
{ABOX/1/5/FTEXT}
Conference date: [CSDATE]
Conference time: [CSTIME]
End time: [CETIME]
Toll-Free Number: [(800)[DDI]
Backup Number: (800)955-5560
Chairman PIN: [MPIN]
Participant PIN: [CPIN]
Conference ID: [CNUM]
{BEND/3/5}
Should you experience difficulties between 8am-8pm EST, Monday-Friday,
call 1800-937-7726. For emergencies at other times, call 1800-236-9935.
Advise the operator of your organization of your teleconference code.
Per-minute rates are based upon the use of either toll-free 800 or tolled
telephone numbers.
{BEND/4}
{IMPORT/Advertisment.tif}
The above fax template contains two tiff graphics HeadingLogo.tif &
advertisment.tif.
Figure 88: Sample Logo
CS7000 System Administrator Guide for Release 9.5
September 2006
199
Chapter 10: Configuring the Avaya Notifications Subsystem
TIFF Files
Dialogic supports the TIFF format (class F). Class F tiff files is a limited version of the TIFF
design for use with fax transport. TIFF files are simple monochrome images. Note: Dialogic will
not support TIFF files that anything other than class F. For more information on the TIFF/F
format see the link http://www.faqs.org/rfcs/rfc2306.html
Customizing Fax Logos
The goal is to create a TIFF/F image with dimensions of approximately 1150x110 pixels. Image
applications such as MS-Paint & Informatik TiffKit may have to be used to create the final
required TIFF/F image.
Note:
200
●
If the customer has supplied a TIFF/F with the above dimensions of 1150x110 pixels, skip
to next section.
●
If the customer supplies a monochrome bitmap adjust the dimensions (Image / attributes
in MS-Paint) to 1150x110. If the original image is smaller than these dimensions, white will
be appended on to height and/or width of image. Skip to next section.
●
If the image is larger, it may have to be recreated to fit into these dimensions although the
width is the important factor. Heights of 220 pixel is expectable but may not be in
proportion to the remainder of the fax in which case it will have to be recreated.
●
If the customer supplies a normal (colour) TIFF file, the image will have to be converted to
a monochrome bitmap before becoming a TIFF/F file. The MS imaging application may be
used to open and scale the image to required size. In which case the image may be pasted
into MS paint using ALT-Print screen (MS imaging active) and Ctrl-V (MS-Paint active).
●
More than not, the required TIFF logo will have to be created from scratch using MS-Paint.
The images will usually have relatively simple text & shapes.
●
Bare in mind that after conversion the TIFF/F images will look slightly different to the
original bitmap images and, in some case, it is trial and error until the desired image is
created.
Note:
It is important to note that fax logos are not multilingual. The multilingual
notifications feature does not extend to fax logos. A single fax logo is used for all
languages. For more information on multilingual notifications, see Configuring
Multilingual Notifications on page 194.
CS7000 System Administrator Guide for Release 9.5
September 2006
Customizing Fax Logos
Converting to a TIFF Image
At this stage there should be a monochrome bitmap image of width 1150 (approx) that has to be
converted to the tiff/f format. A conversion tool needs to be used to create the TIFF file. The
Tiffkit package from Informatik supplies a conversion application (reformat) to do this. There
may be other applications that do similar but this was recommended by Dialogic.
Converting BMP to TIFF/F using TIFFKIT
1. Run TIFFKIT application.
2. The system displays the Infothek Tiffkiet dialog.
Figure 89: Infothek Tiffkit v6.53 Dialog
3. Choose reformat.exe from Interactive drop down box.
The system displays the Informatik Reformatting dialog.
Figure 90: Informatik Reformatting v6.51 Dialog
CS7000 System Administrator Guide for Release 9.5
September 2006
201
Chapter 10: Configuring the Avaya Notifications Subsystem
4. Select Source directory of bitmap file.
5. Select Destination directory of TIFF file.
6. Set Graphics format to TIF.
7. Set Tiff compression to TIFF/F (Dialogic).
8. Select bitmap file from Files.
9. Click OK.
Applying TIFF/F to Fax Template
1. Copy tiff logo to same folder as fax templates.
2. Add or amend IMPORT command in each template to use your file name i.e. {IMPORT/
MYLOGO.TIF}
Note:
Note:
202
Note:
Test Faxes by using the Insert option in the Notifications Subsystem application.
Note:
Tifkit and other tools can be downloaded from http://www.informatik.com
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 11: Troubleshooting the Avaya
Notifications Subsystem
This chapter describes some steps that can be taken in the unlikely event of problems with the
Notifications Subsystem. It contains several tests that a user can undertake before contacting
Avaya Support.
Fax Functionality Problems
●
Enter the test fax machine number and click Insert.
●
Ensure that the tiff file on the template exists in the fax folder.
●
Use the Import command to retrieve the name of the tiff file. Check the fax folder, for
example, C:\Avaya\broadcast\booking\fax, to determine if the tiff file is present.
●
Ensure that the telephone system is operating normally.
●
Connect the analog handset to the line and check for a dial tone. If no dial can be heard,
check with internal technical support or find another analog telephone line.
●
Ensure that the fax machine is operating normally.
●
Dial the test fax number from the analog handset and listen. If fax beeps are not heard,
check fax machine and number.
●
If you do not hear any tones on the handset when you send the fax, check the
configuration. Fax channels are one-based. The first channel on the dialogic is the port at
the top.
Import Utility Problems
●
Notification items can be lost when running the Client Import Utility and the CRS/
Notifications Subsystem. If the Import Utility is writing data to the database while the CRS
is requesting data, items are lost.
●
Increase the Broadcast.ini setting “ResServerRequestInterval” and restart the Notifications
Subsystem before doing a client import.
●
Import a maximum of 1000 records on any single occasion.
CS7000 System Administrator Guide for Release 9.5
September 2006
203
Chapter 11: Troubleshooting the Avaya Notifications Subsystem
204
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 12: Administering the Avaya
Template Editor
This chapter describes how to operate the Avaya Template Editor application. You can use the
Avaya Template Editor to create and edit a set of fax and e-mail templates. The Avaya
Notifications Subsystem uses these templates for conference notifications. The Avaya Template
Editor automates an otherwise manual task. Before the release of the Avaya Template Editor,
users had to create and edit individual templates with an ASCII editor, such as Notepad.
This chapter contains the following sections:
●
Notification Templates
●
Installing Avaya Template Editor
●
Editing an Existing Set of Templates
●
Editing a Single Template
Notification Templates
The Avaya Notifications Subsystem uses over 200 templates.
Templates depend on the following variables:
●
Media type: Fax or e-mail
●
Notification type: Confirmation, Invitation, Reminder, Cancel, or Change
●
Conference type: Meet me direct, Meet me, and so on
●
Repeat conference booking: This setting is represented as, a or b
●
Recording status: Recording can be on or off. This is represented as a or b
For example:
CONFIRM1AB.TXT
This template is sent to a chairman at the time of booking conference type 1, which is
“Meet me direct”. Recording is switched on. It is not a repeat conference.
CS7000 System Administrator Guide for Release 9.5
September 2006
205
Chapter 12: Administering the Avaya Template Editor
Installing Avaya Template Editor
1. Double-click setup.exe.
The system displays the Welcome dialog.
Figure 91: Welcome Dialog
2. Click Next.
The system displays the User Information dialog.
Figure 92: User Information Dialog
3. Enter user information.
This step is an optional step.
4. Click Next.
The system displays the Choose Destination Loction dialog.
206
CS7000 System Administrator Guide for Release 9.5
September 2006
Installing Avaya Template Editor
Figure 93: Choose Destination Location Dialog
5. Click Next or Browse to change the location of the destination folder.
The system displays the Select Program Folder dialog.
Figure 94: Select Program Folder Dialog
6. Click Next.
The system displays the Setup Complete dialog.
Figure 95: Setup Complete Dialog
7. Click Finish to complete the installation.
CS7000 System Administrator Guide for Release 9.5
September 2006
207
Chapter 12: Administering the Avaya Template Editor
Editing an Existing Set of Templates
1. Open Avaya Template Editor.
The system displays the New Templates Project dialog.
Figure 96: New Templates Project Dialog
2. Click Next.
The system displays the Open dialog.
Figure 97: Open Dialog
3. Browse for an existing template file.
4. Click Open.
The system displays the Project Settings dialog.
208
CS7000 System Administrator Guide for Release 9.5
September 2006
Editing an Existing Set of Templates
Figure 98: Project Settings Dialog
5. Click Next.
The system displays the Units Editor dialog.
Figure 99: Units Editor Dialog
CS7000 System Administrator Guide for Release 9.5
September 2006
209
Chapter 12: Administering the Avaya Template Editor
A unit is a component that is used in the generation of a template. For example, the
Confirmation unit is used in each Confirmation type template. The Recording unit is used in
each template that requires recording or playback information, regardless of conference type.
The Confirmation unit contains the following information, by default:
Conference Confirmation
Your conference booking is confirmed for [CSDATE] at [CSTIME].
Your conference call is booked as follows:
* Conference name: [CNAME]
* Scheduled Conf Date: [CSDATE]
* Scheduled Conf Time: [CSTIME]
* Conference Reference: [CNUM]
* Number or participants: [CFREES]
* Dial-in Number: [DDI]
* Moderator Pin access code: [MPIN]
* Particapant Pin access code: [CPIN]
The Recording unit contains the following information, by default:
Playback Instructions
Your conference will be recorded. To listen to the recording:
1. Dial 2075683 one hour after the conference ends.
2. At the voice prompt, key in the 6-digit reference no. [CNUM] and
end with the # key.
3. Your conference is then played back to you over the telephone.
The nine digits on your keypad helps you to control the playback:
1. Slow Rewind
2. Increase volume
3. Slow Forward
4. Medium Rewind
5. Pause On/Off
6. Medium Forward
7. Fast Rewind
8. Increase Volume
9. Fast Forward
210
CS7000 System Administrator Guide for Release 9.5
September 2006
Editing an Existing Set of Templates
6. Edit the templates as follows:
1. Click in the text window and edit using the keyboard.
2. Double-click on keywords from the Keywords dialog to position keywords in the
template text. Keywords are variables, or alias items. Real conference data replaces
keywords when a notification is sent.
Figure 100: Keywords Dialog
7. Once editing is complete, click Next.
The system displays the Files Selector dialog.
Figure 101: Files Selector Dialog
8. Click Finish.
The system displays the Confirmation dialog. The Confirmation dialog confirms the
number of generated templates.
CS7000 System Administrator Guide for Release 9.5
September 2006
211
Chapter 12: Administering the Avaya Template Editor
Figure 102: Confirmation Dialog
9. Click OK to close Avaya Template Editor.
Editing a Single Template
In addition to editing a set of templates, single templates can also be modified using Avaya
Template Editor.
1. Display the File Selector dialog. For more information, see Editing an Existing Set of
Templates on page 208.
Figure 103: Files Selector Dialog
2. Select the file you want to modify.
3. Double-click this file.
The system displays the template file.
212
CS7000 System Administrator Guide for Release 9.5
September 2006
Editing a Single Template
Figure 104: Template File Dialog
Panel A
Panel B
Panel C
Panel A lists the units that are contained in the template. To remove a unit, select it and hit
Delete.
Panel B lists all available units. To add a unit to the template, double-click on the item.
Panel C displays a preview of the template.
4. Update the template as required.
5. Click OK.
6. Click Finish.
The system displays the Confirmation dialog. The Confirmation dialog confirms the
number of generated templates.
Figure 105: Confirmation Dialog
7. Click OK to close Avaya Template Editor.
CS7000 System Administrator Guide for Release 9.5
September 2006
213
Chapter 12: Administering the Avaya Template Editor
214
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 13: Administering the Avaya SMS
Controller
This chapter describes the Short Message Service Controller. It also describes how to install
and configure the controller. It is divided into the following sections:
●
The Short Message Service Controller
●
Installing the SMS Controller
●
Configuring the SMS Controller
The Short Message Service Controller
The Short Message Service (SMS) Controller is an application providing connectivity between
client applications and a mechanism to transmit an SMS message. The customer provides the
mechanism to transmit the message. It can be either an SMS gateway or an Short Message
Service Centre (SMSC). Alternatively, a connection can be made to an SMS service provider.
The system uses templates to provide the content of the SMS message. This template set is
included as part of the Notifications Subsystem installation. For more information on the
Notifications Subsystem, see Configuring the Avaya Notifications Subsystem on page 171.
Figure 106 displays the relationship between client applications and the SMSC/modem.
CS7000 System Administrator Guide for Release 9.5
September 2006
215
Chapter 13: Administering the Avaya SMS Controller
Figure 106: SMS Architecture
XMS
*
SMS Test Client
Notifications Subsystem
Client Applications
test application
* Aincluded
to test
connectivity between
clients, SMS
Controller, and
SMSC.
SMS Controller
Option 1
Option 2
SMS Gateway
SMSC
GSM Modem
Relationship between client applications and SMSC/modem
The SMS Controller GUI consists of separate windows, each of which represents a connected
client application. Each window contains two columns. The Destination column displays the
destination mobile number. The Message column displays the text message contents. In
addition, the system uses icons to represent the progress of the SMS.
Figure 107 displays the SMS Controller GUI.
Table 67 displays the SMS progress icons.
216
CS7000 System Administrator Guide for Release 9.5
September 2006
The Short Message Service Controller
Figure 107: SMS Controller GUI
Table 67: SMS Progress Icons
Icon
Description
An incoming SMS request that is waiting to be
processed.
The SMS is being processed and the SMSC is notified.
The SMS is successfully sent.
The SMS has failed to reach its destination.
Completed SMS requests are cleared from the SMS Controller GUI every 30 seconds.
CS7000 System Administrator Guide for Release 9.5
September 2006
217
Chapter 13: Administering the Avaya SMS Controller
Installing the SMS Controller
1. Run setup.exe.
Setup.exe is on disk 1.
2. Choose a destination folder.
The default path is C:\Avaya\SMS.
The Installer loads the following files:
Table 68: SMS Controller Files
Files
Description
SMSController.exe
The main program.
SMSTestClient.exe
A test application.
SMSControl.ini
The configuration file.
SmppLib.dll
A required DLL.
SMSClient.dll
A required DLL.
Running SMS Test Client
The SMS Test Client is a test application. It helps users to quickly test connectivity between
client applications, the SMS Controller, and the SMSC/GSM modem.
To test:
1. Run the SMS Controller.
2. Run the SMS Test Client.
3. On the SMS Test Client GUI, enter the SMS Controller details.
The system displays the SMSTestClient dialog.
218
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring the SMS Controller
Figure 108: SMS Test Client GUI
The required details are:
- IP address
- Port number
- Name
4. Click Connect.
5. On the SMS Test Client, enter some text in the SMS field.
6. Enter a destination mobile telephone number.
Usually, the SMSC requires an international code prefix.
7. Click Send SMS.
Configuring the SMS Controller
You can configure the SMS Controller application with the SMSController.ini file. The
SMSController.ini file is located in the Windows directory.
CS7000 System Administrator Guide for Release 9.5
September 2006
219
Chapter 13: Administering the Avaya SMS Controller
This code is from a sample SMSController.ini file:
[Server]
Port=4500
Client=8
;Protocol=SMPP
Protocol=HTTP
[SMPP]
Logon=user1
Password=password
Sender=35312073616
IP=10.121.10.125
Port=8901
ton=1
npi=1
[HTTP]
URLA=http://213.190.141.35/bulksms/SendSMSClient.asp?UID=avaya&
URLB=Pswd=spect2003&Phone=[DEST]&OperatorID=2&SMS=[MESG]
[Logging]
Path=Logs
Level=2
Alert=4
Size=10
Days=3
Flush=1
220
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring the SMS Controller
Table 69describes the parameters.
Table 69: Configuration Parameters
Parameter
Description
Port
The port of the listening socket opened by the
SMS Controller. The connected client
applications must be configured to use the
same port number.
Clients
Specifies the maximum number of clients that
can connect to the SMS Controller.
Protocol
This can be configured for SMPP or HTTP. It
describes the protocol used to communicate
with the SMSC. If the SMPP protocol is
selected here, the HTTP configuration settings
(URLA, URLB) are ignored. If the HTTP
protocol is selected here, the SMPP
configuration settings, Logon, Password,
Sender, IP, Port, Ton, NPI, are ignored.
[SMPP]
The Short Message Peer to Peer (SMPP)
protocol is an open industry standard
messaging protocol. SMPP simplifies the
integration of data applications with wireless
mobile networks. These mobile networks
include, GSM, Time Division Multiple Access
(TDMA), and Code Division Multiple Access
(CDMA). This protocol is widely deployed in the
mobile telecommunications industry.
The SMPP configuration items depend on the
SMSC or GSM modem software that is being
used. When an account is set up with an
SMSC, some or all of the SMPP configuration
settings are provided. In the case of a GSM
modem, consult the third party modem software
to configure the SMPP settings.
Logon
SMSC account name
Password
SMSC security password
IP
IP server address of SMSC
Port
Listening port of SMSC
TON
Set to 0
NPI
Set to 0
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
221
Chapter 13: Administering the Avaya SMS Controller
Table 69: Configuration Parameters (continued)
Parameter
Description
[HTTP]
SMS requests can be processed using the
HTTP protocol. The destination mobile
telephone number and message must be
included as part of the URL. There are four
configuration items available to configure the
URL, which are concatenated. The literal token
[DEST] represents where the destination
mobile number is embedded. The [MESG]
represents the actual text content. This
technique is used because different SMSC
servers use different formats. For example:
URLA=http://213.190.141.35/bulksms/
SendSMSClient.asp?UID=avaya&
Note: SMS requests using HTTP do not receive
a response and are assumed to be successful.
[Logging]
Logs are stored based on events from SMSC or
client applications. Log files are stored in the
format:
LogMM_DD_Ddd_HHMMSS.txt
For example:
Log07_14_Wed_153954.txt
Path
Folder to store logs
Level
Logging level 1-5. The lower the number, the
more detailed the events that are logged.
Alert
Alert level to display warning message dialog
4-5
Size
This setting is the maximum size in kilobytes of
a single log file. When the log file reaches this
specified size, a new file is created.
Days
The number of days for which logs are stored.
When this number is reached, the log files are
automatically deleted.
Flush
If Flush is set to 1, the logging data is not
buffered.
2 of 2
222
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring the SMS Controller
An Example of a Logging File
------------------------------------------PRODUCT : 0150A001.01.00
------------------------------------------Date
Time
ClntLevelDetails
------------------------------------------14/07/04 15:39:54 N/ANoticeSMPP:TRANSSCEIVER Bind(user1,password)
- success
14/07/04 15:39:54 N/ADebugSMPP_BIND_RECEIVER_RESP - SYSID 3233796
14/07/04 15:39:54 N/ANoticeSMPP - INS with SMSC
14/07/04 15:39:54 1NoticeNew client connected Notifications
Subsystem ID = 1
14/07/04 15:39:54 1NoticeNew client logged on - client name
[Notifications Subsystem]
14/07/04 15:39:54 N/ANoticeSMPP:TRANSSCEIVER Bind(user1,password)
- success
14/07/04 15:39:54 N/ADebugSMPP_BIND_RECEIVER_RESP - SYSID 3248652
14/07/04 15:39:54 N/ANoticeSMPP - INS with SMSC
14/07/04 15:39:54 1NoticeReceived SMS request to send to
353876712603
14/07/04 15:39:54 1DebugConference confirmation: MPIN-771539
CPIN-878014.Calling instructions: On 14 July 2004 at 3:53pm dial
7700001 and enter 771539# - Avaya
14/07/04 15:39:54 1NoticeSending message by SMPP to 353876712603
14/07/04 15:39:54 N/ADebugSMPP_SUBMIT_SM_RESP Message ID - 84
14/07/04 15:39:54 1NoticeClient [0] disconneted
Note:
Note:
If a previous application crash is detected on start up, the last logging file is stored
in a subfolder called fatal.
CS7000 System Administrator Guide for Release 9.5
September 2006
223
Chapter 13: Administering the Avaya SMS Controller
224
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 14: Administering the Avaya Data
Services Client Application
(DSCA)
This chapter describes how the Avaya Client Registration Server (CRS) is integrated with an
enterprise directory server. It contains the following sections:
●
Directory Services Client Application
●
How it Works
●
Installing DSCA
●
Modes of Operation
●
User Data
●
Demand Profile Creation
Directory Services Client Application
The Directory Services Client Application (DSCA) ensures that registration details on the Client
Registration Server (CRS) are synchronized with registration details on the directory server.
Registration data on the CRS is updated using the directory server registration data. The basic
sequence is as follows:
The user logs on the directory server using their account details as specified in the bands.ini
configuration file. A query is sent to the directory server and the account details in the bands.ini
are updated accordingly. Table 109 displays the DSCA main screen.
CS7000 System Administrator Guide for Release 9.5
September 2006
225
Chapter 14: Administering the Avaya Data Services Client Application (DSCA)
Figure 109: DSCA Main Interface
The Configuration dialog can be
accessed via the Edit menu.
Next Process Time
Last Process Time
Some Historical Status Details
How it Works
The Lightweight Directory Access Protocol (LDAP) is the standard for accessing directory
servers. LDAP has evolved to become the Internet standard way of accessing online directory
systems. Over 40 organisations, including Microsoft, Novel, Netscape, IBM, Lotus have pledged
support for LDAP.
The CRS uses LDAP to:
●
Authenticate users
●
Query user data
Most directory servers use a standard schema to store typical user information. These schemas
can be extended as required. Any directory server can be integrated with the CRS, provided the
it contains the following items of user information:
226
●
Name
●
E-mail address (optional)
●
Telephone
CS7000 System Administrator Guide for Release 9.5
September 2006
Installing DSCA
Figure 110: Client LDAP Interface Architecture
Directory Server Client Application
(LDAP Client)
ODBC Interface
LDAP Interface
CRS Database
LDAP API
Enterprise Directory Server
Schema
LDAP Architecture
Installing DSCA
1. Run setup.exe.
2. Locate and run the SQL script, DSCA.sql.
The DSCA.sql script is stored in the SQL folder in, C:\avaya\dsca.
Ensure that you choose the correct databse (BSRes2).
Note:
Note:
The Auto-Demand profile is now part of the standard BSRes2 database setup.
There is no need to run any Auto Demand Profile (DProf) script when installing
DSCA.
3. Set AutoAccountInd in system parameters to 1.
4. Create an account in the directory server for the DSCA login account.
For example, CRSAdmin.
5. Create a new company in the CRS Front End.
All directory server users and demand profiles are created using this new company.
6. Edit one of the sample profiles with the Configuration option on the Edit menu.
CS7000 System Administrator Guide for Release 9.5
September 2006
227
Chapter 14: Administering the Avaya Data Services Client Application (DSCA)
Figure 111: Configuration Dialog
The following parameters need to be configured:
Table 70: Configuration Parameters
Parameter
Description
Host Value
The IP address of the directory server
Port
The port number. The default value is 389.
Login DN
The login DN is the user name. In other words, it is the
account in the directory server for the DSCA login
account. For example, cn=CRSAdmin, cn=users,
dc=DSServer1, dc=com.
Password
The password associated with the user name
SearchBase
The search base, based on the customer directory server
structure. For example, ou=department,
dc=DSServer1, dc=com. cn=users,
dc=DSServer1, dc=com.
SearchPath
The search path through which directory server users are
retrieved. For example,
(objectClass=user)
(&(objectClass=user)(cn=Smith*)
D.S. N/W Timeout
Directory server timeout in seconds. Default value is 15.
This timeout means that if the directory server does not
respond within 15 seconds, it fails.
1 of 4
228
CS7000 System Administrator Guide for Release 9.5
September 2006
Installing DSCA
Table 70: Configuration Parameters (continued)
Parameter
Description
SPCondition1
Optional condition to restrict the entries returned by the
search. For example:
(modifyTimeStamp>=%LASTPROCESSTIME%)
%LASTPROCESSTIME% indicates the last process date
and time. This setting means that only records that have
a modifyTimeStamp that us more recent than
%LASTPROCESSTIME% are returned.
--(modifyTimeStamp>=%LASTPROCESSTIME%)
The double dash before this line disables the feature
without having to remove the text.
Comment
Free text that identifies the profile
Common Name
The actual attribute name that refers to the Common
Name in the specific directory server. It varies from one
directory server to another. For example, the Windows
directory server uses cn. The parameters are as follows:
●
homePhone
●
telephoneNumber
●
mobile
●
facsimileTelephoneNumber
●
mail
These attribute names vary from one directory server to
another.
UserAccountControl
The actual attribute name that identifies the user account
control details for this specific directory server. This
attribute might not be supported on all types of directory
server.
DisabledMask
When masked with the UserAccountControl attribute,
DisabledMask results in the disabled status of the
account.
LDapCompanyRef
Specifies the company reference number.
2 of 4
CS7000 System Administrator Guide for Release 9.5
September 2006
229
Chapter 14: Administering the Avaya Data Services Client Application (DSCA)
Table 70: Configuration Parameters (continued)
Parameter
Description
Setting for Demand
Profile
Conference Size: Specifies the conference size
Recording On: Indicates whether recording is on or off.
The possible values are 1/0.
Data On: Indicates the date. The possible values are 1/0.
Entry Tone On: Indicates whether the entry tone is on or
off. The possible values are 1/0.
Leaving Tone On: Indicates whether the leaving tone is
on or off. The possible values are 1/0.
Wait for Moderator On: Indicates whether the wait for
Moderator indicator is on or off. The possible values are
1/0.
Notification Type: The possible values are:
●
0 (None)
●
1 (Fax)
●
2 (Email)
●
3 (Email and fax)
●
4 (SMS)
●
5 (Fax and SMS)
●
6 (Email and SMS)
●
7 (Email and fax and SMS)
Confirmation Ntf: Indicates whether the Confirmation
Notification is on or off. The possible values are 1/0.
Attendance Ntf: Indicates whether the Attendance
Notificiation is on or off. The possible values are 1/0.
Disable Non DS
Clients
When this parameter is set to 1, the DSCA disables all
CRS clients that the directory server does not return by
the directory server search. If the search path returns
partial results, based on %LASTPROCESSTIME%, the
<Disable Non DS Clients> feature is deactivated for the
search process.
Last Process Data
Time
Stores the date and time of the last process. The values
are automatically generated after each process if the
SPCondition1 is enabled.
3 of 4
230
CS7000 System Administrator Guide for Release 9.5
September 2006
Modes of Operation
Table 70: Configuration Parameters (continued)
Parameter
Description
ProcessIntervalType
Detemines, along with ProcessInternalValue, how often
the process runs. Process interval types:
ProcessIntervalValue
●
0 Seconds
●
1 Minutes
●
2 Hours
●
3 Days
Detemines, along with ProcessInternalType, how often
the process runs. For example:
●
To run the process every 30 minutes:
ProcessIntervaltype:1
ProcessIntervalValue:30
●
To run the process each day:
ProcessIntervaltype:3
ProcessIntervalValue:1
4 of 4
The configuration dialog does not show the RunOnStartup setting. When RunOnStartup is
set to 1, the process is started on computer start up. If using BSMon to start this
application, RunOnStartup must be set to 1.
7. Save this file with a different file name.
8. Add DDIs for the demand conference with the CRS Front End.
Ensure that the DDI has the same properties as the demand profile configurations in the
DSCA. Ensure that the language and Moderator settings are consistent.
Modes of Operation
There are two modes of operation:
●
Non-Cached
●
Cached
Cached mode is described here for illustrative purposes. Cached mode is supported in
future releases only.
CS7000 System Administrator Guide for Release 9.5
September 2006
231
Chapter 14: Administering the Avaya Data Services Client Application (DSCA)
Non-Cached Mode
The steps involved in this mode of operation are:
●
Retrieval of registration details from the directory server
●
Synchronization of CRS registration details
Using the search criteria configured in the current profile, the DSCA queries the directory server
for entries that meet the specified criteria. These records are stored in a temporary table in the
CRS database. Entries that are disabled on the directory server are added (or updated) on the
CRS as disabled clients.
Each of the entries retrieved from the directory server is checked to ensure that it meets certain
requirements. The current requirements are that the entry has a distinguished name, common
name (client name), and an e-mail address. Records that meet this criteria are added or
updated on the live CRS database. The disabled status is also updated. Demand profiles and
additional details are generated for new clients.
Confirmation and attendance notifications are configurable. They can be enabled or disabled. If
they are enabled, new clients receive an e-mail to inform them that they are active on the CRS
system.
Cached Mode
The steps involved in this mode of operation are:
●
Caching of existing data
●
Retrieval of registration details from the directory server
●
Synchronization of CRS registration details
The DSCA queries the CRS for the client details associated with the directory server company.
The client details are cached locally. These details are a subset of the client details that are
available on the CRS database. These details contain the common fields that exist on both the
CRS database and the directory server. The cached details also indicate if the entry is disabled
or enabled. When the cache is created, the system disables all entries by default. The cache
also contains fields to indicate if the entry is a new or existing entry.
Using the search criteria configured in the current profile, the DSCA queries the directory server
for entries that meet the specified criteria. Entries that are disabled on the directory server are
added (or updated) on the CRS as disabled clients.
Each of the entries retrieved from the directory server is checked to ensure that it meets certain
requirements. The current requirements are that the entry has a distinguished name, common
name (client name), and an e-mail address. Records that meet this criteria are added or
updated on the cache.
232
CS7000 System Administrator Guide for Release 9.5
September 2006
User Data
The disabled status is also updated. Demand profiles and additional details are generated for
new clients.
Confirmation and attendance notifications are configurable. They can be enabled or disabled. If
they are enabled, new clients receive an e-mail to inform them that they are active on the CRS
system.
User Data
The following data can be retrieved from the directory server.
Table 71: User Data
Note:
User Data
LDAP Attribute Names
CRS Field Names
Distinguished
Name
Dn
CLIENT_DISTINGUISHEDNAME
Name
Cn
CLIENT_NAME
Telephone Number
HomeNumber
TelephoneNumber
FacsimileTelephoneNum
ber
Mobile
CLIENT_MAIN_PHONE
CLIENT_MAIN_FAX
CLIENT_CONTACT_MOBILE
E-mail
Mail
CLIENT_EMAIL
User Account
Control
User AccountControl
N/A
Disabled Mask
N/A
CLIENT_DISABLEDIND
Note:
To permit brackets as acceptable characters in the Telephone Number field,
update the Phone Number Format Type parameter to 1. The default value of the
Phone Number Format Type parameter is 0. When Phone Number Format
Type=0, brackets are rejected. The Phone Number Format Type parameter is
one of the system parameters in the BSRes 2 database.
An example of a telephone number with brackets: (353) 895623
An example of a telephone number without brackets: 353 8598623
The DSCA has configurable mappings for CRS fields to LDAP attributes, as attributes are not
standard across LDAP schemas.
CS7000 System Administrator Guide for Release 9.5
September 2006
233
Chapter 14: Administering the Avaya Data Services Client Application (DSCA)
LDAP attributes to query for name, telephone number, and e-mail searches are set in the DSCP
properties file. This file is in the same format as the Web Portal LDAP. It might possibly be
shared out to the Web Portal LDAP, to minimize configuration.
The LDAP search filter used to retrieve user data is “objectclass=<user account schema>”. For
example, the default schema for active directory is ‘user’, so that the LDAP search filter is
“objectclass=user”. The user account schema name is a configurable option for DSCA.
Communication with the LDAP server is done using an LDAP Client API. Communication to the
CRS database is done using the ODBC API, callling the standard Booking and Scheduling
database stored procedures.
Demand Profile Creation
Demand (conference) profiles are generated for each new Client added to the CRS database if
configured to do so.
Some of the details used to create this demand profile are taken from the DSCA configuration.
Other details are taken from the BSDefaults table found in the BSRes2 database.
Note:
234
Note:
Setting the DefaultEnabledInd to 0 on the BSDefaults table disables the creation
of demand profiles.
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 15: Administering the Avaya
Operator Console
Operators use the Avaya Operator Console to manage conferences. The Avaya Operator
Console consists of an intuitive graphic user interface which displays the real time status of
conferences and conferees. Using the Operator Console, Operators can manipulate conferees
and control conferences by performing actions such as intercepting, muting, roaming, and so
on. The features and functions of the Operator Console are described in the Avaya Meeting
Exchange CS7000 9.5 Suite Release Operator Guide.
There are several administrative tasks associated with the Operator Console. Among them are:
●
Configuring Log on Types
●
Disconnecting a Remote Operator Line
●
Enabling the Display of a Substitute CLI for Operator Originated Calls
●
Hiding the Display of Conferees’ CLI on the Operator Console
●
Configuring Multiple Operator Consoles on one Workstation
●
Customizing the Operator Console Title Bar
●
Configuring Hoot and Holler Groups
●
Customizing Operator Icons
Configuring Log on Types
In the Avaya CS7000 Operator Console, there are two log on types. Operators can log on as
System Owners or as Wholesalers.
A CRS Wholesaler is the owner of a company or companies. Wholesalers can create...
●
Companies
●
Clients
●
Resellers
●
Conferences
...on the Web, but cannot access data related to companies or clients owned by other
wholesalers.
For more information on Wholesalers, see Managing Wholesalers on page 77.
CS7000 System Administrator Guide for Release 9.5
September 2006
235
Chapter 15: Administering the Avaya Operator Console
System Owners can view all conferences. Wholesalers can view their own conferences.
In the Operator.ini file, the GroupFilter parameter controls the log on type.
For Wholesaler users, System Administrators must set the GroupFilter parameter to match
the Wholesaler reference number. The Wholesaler reference number is generated when new
Wholesalers are created. For more information, see Managing Wholesalers on page 77.
For System Owners, System Administrators must set the GroupFilter parameter to 0.
System Owners can view all conferences. System Owners cannot move conferees from one
conference to another unless both conferences are associated with the same Wholesaler
grouping. You can view the Wholesaler Grouping in the Conference List and Conference Title.
The column title is Group.
If the GroupFilter parameter has an invalid value, access is denied and a fatal error results.
Disconnecting a Remote Operator Line
As an Operator Console System Administrator, you can disconnect remote PRI Operators.
Operators cannot disconnect other remote PRI Operators. When you log on to the Operator
Console, a disconnect option activates. This option is unavailable to regular Operators.
USER_LEVEL _TYPE in the CRS User Table determines System Administrator access. If
USER_LEVEL_TYPE is UL_ADMINISTRATOR, users are granted System Administrator access
to the Operator Console. Regular Operators and Supervisors cannot disconnect remote
Operators.
To disconnect a remote Operator:
1. Select a remote Operator.
Figure 112: Selection of Operator
2. Select the Delete icon.
236
CS7000 System Administrator Guide for Release 9.5
September 2006
Enabling the Display of a Substitute CLI for Operator Originated Calls
Figure 113: Delete Icon
The Operator Console displays an Avaya Console information dialog.
Figure 114: Avaya Console Information Dialog
3. Click Yes.
The Operator Console disconnects the Operator.
Enabling the Display of a Substitute CLI for Operator
Originated Calls
When Operators make outgoing calls, they can enable a substitute calling line identifier (CLI).
The display field on the handset of the conferee displays the substitute CLI. The substitute CLI
must first be entered in the Operator ini file by a System Administrator. The parameter
associated with substitute CLIs is CLI=. The new CLI must be entered on this line as a string
value.
When Operators make outgoing calls and want to use this feature, they must ensure that Auto
Intercept and Monitor are not enabled.
CS7000 System Administrator Guide for Release 9.5
September 2006
237
Chapter 15: Administering the Avaya Operator Console
Hiding the Display of Conferees’ CLI on the Operator
Console
You can configure the Operator Console to hide the CLI of calls made to the conferencing
system. If you configure this setting, Operators using the Operators Console cannot view the
CLI of conferees when conferees dial the conferencing server. The CLI information is not
displayed on the Operator Console. To activate this setting, you must configure a parameter in
the Operator ini file, called, HideCli.
When HideCli=1, the system prevents the CLI from being displayed on the Operator Console.
When HideCli=0, the system displays the CLI on the Operator Console.
Configuring Multiple Operator Consoles on one
Workstation
You can configure multiple Operator Consoles on one workstation. Using this functionality,
Operators can access several bridges from their workstation.
If the bridges have the same version number, a single Operator executable can be used. The
executable is located in the C2000con folder. An Operator ini file is required for each bridge. For
example, if three bridges are running, three Operator ini files are required. Folders must be
created within the C2000con folder for each separate Operator ini file. In addition, shortcuts
must be created on the workstation desktop for each separate bridge. Figure 115 shows a
sample directory structure.
238
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring Multiple Operator Consoles on one Workstation
Figure 115: Directory Structure for Multiple Operator Consoles
C:\
C2000con
Operator.exe
Operator1.ini
Operator2.ini
Operator3.ini
Directory Structure for Multiple Operator Consoles
The desktop shortcuts must contain the full path of the Operator exe and the appropriate
Operator ini file. The paths must be separated by a single space. For example:
C:\C2000con\Operator.exe C:\C2000con\bridge 1\Operator.ini
Figure 116 shows an example shortcut properties dialog.
Figure 116: Desktop Shortcut
CS7000 System Administrator Guide for Release 9.5
September 2006
239
Chapter 15: Administering the Avaya Operator Console
If the bridges have a different version number, several Operator executables are required. In
this situation, where different versions of the bridge are running, each Operator executable must
be located in a separate folder. The Operator ini file associated with each Operator Console
must be located in the same directory. Figure 117 shows a sample directory structure.
Figure 117: Directory Structure for Multiple Operator Consoles with Different Bridge
Versions
C:\
C2000con
Version 1
Operator.exe
Operator.ini
Version 2
Operator.exe
Operator.ini
Version 3
Operator.exe
Operator.ini
Directory Structure for Multiple Operator Consoles
As before, a separate desktop shortcut must be created for each Operator Console. The
shortcut target must point to the Operator.exe and Operator.ini files.
Operator OI16 handsets are directly configured using the Comport setting in the Operator ini
file. This setting must be unique to each operator.
Operators can also choose from multiple CRS servers. Choosing a particular server causes the
corresponding ini file to be used for the connection. All ini files must reside in the Windows
directory.
Customizing the Operator Console Title Bar
System Administrators can customize the Operator Console title bar by entering the required
title in the Operator.ini file. This feature enables operators to quickly identify individual consoles
when multiple consoles are running on a single workstation. The parameter that must be
updated is:
ConsoleLabel=”A New Label”
240
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring Hoot and Holler Groups
If no value is entered, the system displays one of the following default values:
●
Avaya Console
●
DTMF Master
●
Demand PIN/V Master
●
PIN Master
●
Demand PIN Master
●
PIN/V Master
This feature only applies if separate Operator ini files are used. For more information, see
Configuring Multiple Operator Consoles on one Workstation on page 238.
Configuring Hoot and Holler Groups
The Hoot and Holler Conferencing feature enables Operators to set up a conference between a
conference room, individual users and a trading floor.
Hoot and Holler circuits can be grouped together for convenience. Operators can connect Hoot
and Holler groups to a conference, rather than manually connecting individual circuits.
There are two main steps involved in the configuration of Hoot and Holler groups:
●
Defining Hoot and Holler Groups
●
Configuring the Operator ini File
Defining Hoot and Holler Groups
To define Hoot and Holler groups, System Administrators create a simple text file using
Notepad.exe. The text file must contain a section called Presets. The Presets section must
contain an entry for each group, in the following format:
<ID>=<list>
●
<ID> is a group identifier
●
<list> is a comma separated values list of Hoot and Holler circuits IDs
For example:
[Presets]
2=1,4,9
3=7,8,9,10
15=18,17,3,4,5,6
CS7000 System Administrator Guide for Release 9.5
September 2006
241
Chapter 15: Administering the Avaya Operator Console
System Administrators must save this text file to a centralized location. Alternatively, the file can
be saved locally to the same directory as the Operator ini file. If the file is saved locally, System
Administrators must ensure that the exact same file is on all Operator workstations. For this
reason, Avaya recommend the centralized option. Figure 118 displays a sample Hoot and
Holler definition file.
Figure 118: Hoot and Holler Groups
Configuring the Operator ini File
This section describes how to configure the Operator ini file. This section also describes some
new fields and Operator options that arise as a result of new features:
●
Operator Options
●
New Fields
To configure the Operator ini file, System Administrators set the HHGroups and HHParkID
parameters.
The HHGroups parameter specifies a path to the file that defines the Hoot and Holler groups.
For more information, see Defining Hoot and Holler Groups on page 241.
The HHParkID parameter specifies a conference for unconnected Hoot and Holler groups. The
system uses this conference hold Hoot and Holler groups when they are not connected to their
group conference. Usually, the holding conference has a conference ID of 1. A conference ID of
1 ensures consistency with an existing configuration of a customer. It might be necessary to
reconfigure other elements in the Avaya CS7000 system.
Figure 119 displays a section from a sample Operator ini file.
242
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring Hoot and Holler Groups
Figure 119: Operator ini File
When the Hoot and Holler groups are defined and the Operator ini file is configured, a
conference must be opened for each Hoot and Holler group. The conference ID must be the
same as the group ID for the associated group.
When these administrative tasks are complete, several new options are made available to the
Operator on the Operator Console. For more information, see “Operator Options” on page 263.
In addition, new fields are made available in the Conference title bar and the Conference List
title bar.
Operator Options
If HHGroups is not blank, two new options are added to the Conference menu. These options
are Connect Preset and Disconnect Preset. These options are also accessible from the
Conference List context menu. To access the context menu, use the right click mouse button.
If an Operator selects a conference and selects the Connect Preset option, the group of circuits
associated with that conference is connected to the conference. A group is associated with a
conference if the group ID is the same as the conference ID.
Figure 120 displays the Connect Preset menu option.
CS7000 System Administrator Guide for Release 9.5
September 2006
243
Chapter 15: Administering the Avaya Operator Console
Figure 120: Connect Preset
If an Operator selects a conference and selects the Disconnect Preset option, the group of
circuits in that conference is disconnected. The group of circuits is moved to the conference that
is holding unconnected Hoot and Holler groups. This conference is the conference defined in
HHParkID.
Figure 121 displays the Disconnect Preset menu option.
244
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuring Hoot and Holler Groups
Figure 121: Disconnect Preset
For more information on the operation of the Connect Preset and Disconnect Preset options,
see the Avaya CS7000 Operator Guide for Version 9.5.
Other parameters relating to Hoot and Holler functionality include:
●
HHSuper
●
HHEnabled
HHSuper allows non-Supervisor control of the Hoot and Holler functions of Hoot, Holler, and
Remove. If HHSuper=1, non-Supervisors can use these functions. If HHSuper=0,
non-Supervisors cannot use these functions.
HHEnabled controls Hoot and Holler availability on the Operator Console. If HHEnabled=0,
Hoot and Holler functionality is disabled. If HHEnabled=1, Hoot and Holler functionality is
enabled but only Supervisors can add more than a single hoot to a conference. If
HHEnabled=2, there is no Supervisor restriction and there can be multiple hoots per
conference. The default is HHEnabled=1.
CS7000 System Administrator Guide for Release 9.5
September 2006
245
Chapter 15: Administering the Avaya Operator Console
New Fields
When an Operator connects a group of circuits to a conference, a message is sent from the
Operator Console to the Conference Management Server (CMS). This message is sent using
the Avaya protocol, CCL. When an Operator disconnects a group of circuits, a CCL message is
also sent from the Operator Console to the CMS. When a group of circuits is connected to a
conference, the Operator Console displays the letter P in the Conference title bar. The letter P
represents preset groups, The Operator Console does not display this letter if no circuits are
connected to that particular conference. Figure 122 displays the P symbol.
Figure 122: Conference Title Field
The conference list also contains new information in relation to Hoot and Holler groups. The
conference list displays the individual circuits that make up each group. In addition, the
Operator Console displays a connection indicator, the P symbol. Figure 123 displays a
conference list.
Figure 123: Conference List Fields
To view the Hoot and Holler Group information fields in the conference list and in the conference
title bar, the view formats must be configured. For more information, see the Avaya CS7000
Operator Guide for Version 9.5.
In addition to these Hoot and Holler configuration tasks, System Administrators must configure
Hoot and Holler on the CMS. The Hoot and Holler feature uses two CMS fil configuration files.
For more information, see Hoot and holler configuration file (Hh.fil) on page 58 and Hoot and
holler conferee configuration file (Hhconferee.fil) on page 58. The Avaya CS7000 CMS
Configuration Guide for Version 9.5 also contains further information on the configuration of
these files.
246
CS7000 System Administrator Guide for Release 9.5
September 2006
Customizing Operator Icons
Customizing Operator Icons
Operator icons can now be customized. Using this functionality, distinctive icons can be
assigned to individual Operators. This functionality simplifies the task of distinguishing between
Operators.
The icons must be bitmap files that are 24 pixels wide and 16 pixels high, with 16 colors.
A parameter in C2000con.ini, called OpUserPath, specifies a network folder, such as Icons in
Figure 124 . Within the specified folder, the Avaya CS7000 System Administrator must create
several folders. The name of each of these folders must correspond with an Operator name.
One or more bitmap files must exist within each of these folders, which conform to the specified
naming and sizing criteria. They are used in place of the corresponding standard Operator icons
for that Operator.
Note:
Note:
The customer or client is responsible for creating icons.
To set up customized icons:
1. Create a base folder on the network.
2. Create another folder within this base folder.
This second folder should have the same name as the Operator.
Figure 124: Directory Structure for Customized Operator Icons
C2000con
Operator.exe
C2000con.ini
Mary
Icons
John
conf.bmp
mute.bmp
open.bmp
close.bmp
int.bmp
conf.bmp
mute.bmp
open.bmp
close.bmp
int.bmp
Directory Structure for Customized Operator Icons
CS7000 System Administrator Guide for Release 9.5
September 2006
247
Chapter 15: Administering the Avaya Operator Console
3. Create a series of bitmap files to represent the various Operator states, using the following
naming conventions:
The conference state bitmap should be called, conf.bmp
(For example:
)
The mute state bitmap should be called, mute.bmp
(For example:
)
The talking state, with the mouth open, should be called, open.bmp
(For example:
)
The talking state, with the mouth closed, should be called, close.bmp
(For example:
)
The intercept state, with the interception icon, should be called, int.bmp
(For example:
)
4. Save these files to the newly created Operator folder.
5. In the C2000con.ini file, configure the new parameter, OpUserPath.
OpUserPath must specify the base folder. For more information, see Figure 124.
6. Save and close the C2000con.ini file.
Figure 125 displays customized icons.
Figure 125: Conference Dialog with Customized Icon
248
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 16: Administering the Avaya Client
Registration Server (CRS)
server interface
The Client Registration Server handles all reservation requests and information requests
relating to the CRS system. All CRS front ends and operator consoles log on to this server. The
service resides on the CRS and the application is continuously running. This chapter describes
the server side of the CRS. It contains the following sections:
●
Introducing the Client Registration Server
●
Configuration
Introducing the Client Registration Server
To access the Client Registration Server, either double-click the icon for the Client Registration
Server on the Windows desktop. Alternatively, select Registration Server from the Program
Start Up menu.
Note:
Note:
The Client Registration Server application is auto-started and should only be
stopped after the BSMon Program has stopped.
CS7000 System Administrator Guide for Release 9.5
September 2006
249
Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface
Figure 126: Client Registration Server
This section introduces the CRS, server side. It contains the following sections:
●
Server Menu
●
Trace menu
●
Help Menu
●
Editing Trace Settings
●
General Group
●
Applications Group
●
Viewing Logging Details
●
Viewing Registration Server Details
●
Shutting Down the Application
Server Menu
Table 72: Server Menu
250
Item
Description
Exit
Exits the application. For more information, see Shutting Down
the Application on page 255.
CS7000 System Administrator Guide for Release 9.5
September 2006
Introducing the Client Registration Server
Trace menu
Table 73: Trace Menu
Item
Description
Reset
Empties the log file.
Start
Starts logging.
Stop
Stops logging.
Settings
Enables the operator to specify what events can be
logged. For more information, see Viewing Logging
Details on page 254.
View
Views log file in notepad.
Help Menu
Table 74: Help Menu
Item
Description
About
ResServer
Displays details about the Client Registration Server.
Editing Trace Settings
This feature helps the user to specify what events to log to the log file.
1. At the Trace menu, select Settings to display the Trace Settings dialog.
CS7000 System Administrator Guide for Release 9.5
September 2006
251
Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface
Figure 127: Trace Setting Dialog
General Group
Table 75: General Group
Item
Description
Timing
Shows the time of incoming and outgoing
messages.
Channel Header
Information about the sender of the
message. The channel header precedes
the message data.
Message Header
Information about the message type. The
message header precedes the message
data.
Incoming Contents
The data within an incoming message.
Outgoing Contents
(SUCCESS)
The data within an outgoing success
message. SUCCESS is a message type. It
represents a positive response to an
incoming message. Typically, this is set to
OFF and is only activated for debugging
purposes.
1 of 2
252
CS7000 System Administrator Guide for Release 9.5
September 2006
Introducing the Client Registration Server
Table 75: General Group (continued)
Item
Description
Outgoing Contents
(FAILURE)
The data within an outgoing failure
message. FAILURE is a message type. It
represents a negative response to an
incoming message.
Outgoing Contents
(EVENT)
The data within an outgoing event
message. EVENT is a message type. It
represents a response to a change in the
system.
2 of 2
Applications Group
Table 76: Applications Group
Item
Description
API Client
Monitors communication between the Client
Registration Server and the API Client.
Notifications
Subsystem
(Broadcast Scheduler)
Monitors communication between the Client
Registration Server and the Notifications
Subsystem.
Conference Manager
(Obsolete)
Monitors communication between the Client
Registration Server and the Conference
Manager.
Console
Monitors communication between the Client
Registration Server and the Operator
Console.
Demand Master
Monitors communication between the Client
Registration Server and the Demand Master
console.
EMS/XMS
Monitors communication between the Client
Registration Server and EMS/XMS.
Front End
Monitors communication between the Client
Registration Server and the CRS Front End.
Reservation Server
CRS generated messages are monitored.
1 of 2
CS7000 System Administrator Guide for Release 9.5
September 2006
253
Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface
Table 76: Applications Group (continued)
Item
Description
Web Booking
Monitors communication between the Client
Registration Server and Web Booking.
Unknown
Monitors communications between the Client
Registration Server and an, as of yet,
unidentified application.
2 of 2
Viewing Logging Details
1. At the Trace menu, select View. Displays the ResServer - Notepad screen.
2. Review the active window as necessary:
Table 77: Logging Details
Item
Description
TIME
Displays the Log time in hour, minutes, and
seconds.
FREE TEXT
Displays Log details
Viewing Registration Server Details
1. At the Help menu, select About CRS server. Avaya CS7000 displays the About CRS
server screen.
2. Click OK to return to the Client Registration Server screen.
254
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuration
Shutting Down the Application
At the Server menu, select Exit. Avaya CS7000 displays the CRS server screen
Figure 128: CRS server Dialog
Table 78: ReServer Dialog
To
Do this
Exit the application
Click Yes.
Return to the Client Registration Server Screen
Click No.
Configuration
This section describes the INI file settings for ResServer.ini. It contains the following sections:
Note:
●
General
●
Database
●
Comms
●
Protocol
Note:
Changes are only saved if the programme is not running when the changes are
made.
CS7000 System Administrator Guide for Release 9.5
September 2006
255
Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface
General
Table 79: General Configuration
Item
Description
ContinueOnRepeatFailure=1
Specifies if repeat bookings are to stop on
first conference failure
SaveSettings=1
Specifies if changes are to be saved on
exiting
ValidateResults=0
Specifies if all messages received be error
checked
CMSAddress=
The IP address of the CMS server.
AllowDuplicateLogons=1
Specifies if duplicate CRS logons are
allowed
GenerateMIS= 0
Store all MIS details for CRS report
CloseOnBusy=1
Specifies whether the server is shut down
when it encounters an Sql cursor error.
Database
Table 80: Database Configuration
256
Item
Description
LoginTimeout=15
Specifies the number of seconds to wait on
trying to log on to database
QueryTimeout=180
Specifies the number seconds to wait on
trying to retrieve query result
Row Count
Specifies the maximum number of rows
allowed to be returned. E.G. 1000 Companies
CS7000 System Administrator Guide for Release 9.5
September 2006
Configuration
Comms
Table 81: Comms Configuration
Item
Description
MaxClients=100
Specifies the maximum number of clients to be
connected
RXBufferSize=2048
Specifies the receive buffer size for normal
clients
TXBufferSize=2048
Specifies the transmit buffer size for normal
clients
CMRXMaxMsgs=1000
Specifies the number of messages buffered from
the ConfManager
CMTXMaxMsgs=1000
Specifies the number of messages buffered to
the ConfManager
HBSend=120
Send a heart beat to all connected clients each
n seconds
HBTimeout=60
When heart beat is sent, give the client n
seconds to respond
Protocol
Table 82: Protocol Configuration
Item
Description
ConsoleMajor=-1
Specifies the major version number of the console
with which the server communicates.
ConsoleMinor=-1
Specifies the minor version number of the console
with which the server communicates.
CS7000 System Administrator Guide for Release 9.5
September 2006
257
Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface
LogSettings
Table 83: LogSettings Configuration
258
Item
Description
Archives=50
The number of log files that are written before a
process of overwriting occurs.
GenFlags=127
Retains the general trace settings.
AppFlags=1023
Retains the application trace settings.
Buffered=1
Specifies whether the logging cache is activated.
Activation of the cache ensures a more efficient
service.
CS7000 System Administrator Guide for Release 9.5
September 2006
Chapter 17: Administering the Avaya
Demand PIN Master
The Demand PIN Master is a program that deals with the validation of personal identification
numbers (PINs) and the opening and closing of conferences. The PIN engine routes callers to
conferences according to the PIN they enter. The Demand engine opens conferences
according to start times stored in the Client Registration Server (CRS) and according to current
demand. The Demand PIN Master resides on the same computer as the Conference
Management Server (CMS).
This chapter describes the administrative tasks associated with the Demand PIN Master
program. It contains the following sections:
●
Resource Management
●
Client PIN Validation
●
CLI Validation
●
CLI Identification
●
Branded DDIs
●
Locked and Full Conferences
●
Extending Conferences
●
Toll-free Conferences
●
Time Synchronization
●
Demand.ini
Resource Management
The Demand PIN Master opens demand conferences as soon as the first participant arrives.
Participants access conferences by entering a valid PIN or by dialing in using a DDI tagged as
direct. All subsequent participants are routed to the conference as they arrive.
In the case of scheduled conferences, the arrival of the first participant might not coincide with
the scheduled start time. The booking period is the span between the scheduled start time and
the scheduled end time. The first participant can activate their conference at any point during
the booking period. The Demand PIN Master manages resources efficiently by ensuring that
conferences are not opened unneccessarily. Conferences do not open automatically at the
scheduled start time. They open only if the first participant enters a valid PIN.
CS7000 System Administrator Guide for Release 9.5
September 2006
259
Chapter 17: Administering the Avaya Demand PIN Master
In the case of demand conferences, the Demand PIN Master opens conferences as the
requirement arises. Demand conferences are closed as soon as they become empty or as soon
as the moderator leaves. A system-wide setting, called the keep flag, controls this functionality.
If the keep flag is on, the conference closes as soon as it becomes empty. If the keep flag is off,
the conference closes when the moderator leaves. Keep flag functionality can be controlled at
run time by pressing preconfigured DTMF commands, which are available to the Moderator.
Client PIN Validation
The Demand PIN Master supports both internal and external client PIN validation.
Internal client PIN validation involves sending a query to a PIN database located in the CRS.
The CRS Operator manages PINs.
External client PIN validation involves sending a query to an external database located outside
the Avaya CS7000 system, for example, a credit card number database. There are several
plug-in products, which can extend the Demand PIN Master to incorporate client data in the
client PIN validation process. These plug-ins use customer.dll.
CLI Validation
Calling Line Identification (CLI) validation involves using the telephone number from which a
potential conferee dials to determine conference access.
The Demand PIN Master checks the telephone number of potential conferees and grants
conference access if the digits match those in the participant list. If a match is found, the call is
routed in the normal way. If no match is found, a dedicated fail message is played.
If, at time of booking, the Operator selects the Validate on CLI Failure check box, the system
plays an additional message. The system plays this additional message after the dedicated fail
message to prompt the caller for their client PIN. The caller is granted conference access if their
PIN matches the PIN in the participant list. If, at time of booking, the Operator does not select
the Validate on CLI Failure check box, the call is routed to reception. For more information,
see the PMCLIFailMsg parameter in Settings on page 265.
Validation on CLI failure ensures that potential conferees are granted conference access in the
event that they call from an unauthorised telephone number.
260
CS7000 System Administrator Guide for Release 9.5
September 2006
CLI Identification
CLI Identification
Prior to this release, Avaya distributed two versions of the Demand PIN Master. One version
contained the standard DPM settings. The second version controlled the functionality of alert
conferences. In this release, Avaya has merged the standard DPM with the Alerts DPM.
As a result of merging the two versions, all customers must now install a Customer.dll file.
Customer.dll enables external CLI identification of the alert initiator. External CLI means that if
the alert initiator calls from a listed telephone number, the system retains their details. These
details can be name and location. This feature is especially useful if, for example, the caller
cannot communicate or the call is abruptly disconnected. You must install Customer.dll even if
you do not intend to use the CLI feature. The CLI feature only operates on crisis or volunteer
conferences. You can switch off the CLI feature if you disable CustomerDataSource.
CustomerDataSource is a new setting in the Demand PIN Master. For more information, see
Settings on page 265.
Branded DDIs
Direct dial inward (DDI) functionality can be used to:
●
Determine the greeting message played to the caller.
●
Determine how the call is subsequently processed.
CS7000 System Administrator Guide for Release 9.5
September 2006
261
Chapter 17: Administering the Avaya Demand PIN Master
Branding means that the number you use to dial the conferencing system determines the
greeting message that is played. Greeting messages can be customized to specific customer
requirements. The system also uses DDIs to determine how your call is processed. DDI is
known as Dialed Number Identification Service (DNIS) in the United States of America. The
Resource DDI table is stored in the CRS. The CRS Operator manages DDIs through the CRS
front end. DDI attributes determine the range of conference functionality to which the DDI
applies, the type of conference access the DDI provides, and so on. DDI attributes are as
follows:
Table 84: DDI Attributes
Attribute
Description
Type
The features that support DDI branding, such as conferencing and
conferencing playback.
CONF
PLAYBACK
CRISIS_ALERT
VOLUNTEER _ALERT
Validation
The PIN used to identify the caller. If validation is set to true, the client
PIN is processed before the conference PIN.
Language
The language used in system messages.
Message
The type of branded message played to callers. Branded messages are
also called greeting messages.
Reception ID
The group identifier. If users are grouped, this attribute is used to
identify their group.
Direct
The type of user access. If Direct is true (Y), users are not prompted for
a PIN and the DDI identifies the conference. If Direct is false (N), users
are prompted for a PIN.
Locked and Full Conferences
Before the Demand PIN Master routes a call to a conference, the master determines if the
conference is locked or full. If the conference is locked or full, the system plays an explanatory
message and routes the call to reception
262
CS7000 System Administrator Guide for Release 9.5
September 2006
Extending Conferences
Extending Conferences
Scheduled conferences have a scheduled start time and a scheduled end time. Conferences
can be automatically extended by the system if there are available resources.
CRS accepts or rejects extension requests, based on several CRS rules, such as the number of
extensions parameter. By default, the number of extensions parameter is set to four.
If negotiation is successful, the conference is extended. No message is played to the conferees
at this point.
If negotiation is unsuccessful, the conference is not extended. A message is played to
conferees to inform them that the conference is about to close. A second warning message is
played immediately prior to the scheduled end time. The period between the messages and the
scheduled end time is configurable.
The CRS Front End parameters that store the timing configurations are called
TenMinuteWarningXMinutesBefore and OneMinuteWarningXMinutesBefore.
If a conference becomes empty at any point during an extension period, it is automatically
closed to efficiently manage resources.
The Demand PIN Master informs CRS of each conference closure so that the conferences can
be removed from the CRS front end.
Toll-free Conferences
From the viewpoint of a conference participant, toll-free conferences use a free telephone
number. Toll-free conferences are charged to the conferencing service provider and not the
participant. Operators can select the Toll-free option when they book a conference on the CRS
Front End.
As the CS7000 System Administrator, there are a number of settings which you must configure
in order to enable the effective operation of toll-free conferencing.
On the System Administration section of the CRS Front End, you must set up a PRI resource for
toll-free conferencing. This PRI resource will be dedicated to toll-free conferencing. For more
information on setting up PRI resources, see Managing System Cards on page 92.
On the System Administration section of the CRS Front End, you must set up a DDI and
associate it with the PRI resource that you have dedicated to toll-free conferencing. This DDI
will be the toll-free DDI for your toll-free conferences. You can set up a number of toll-free DDIs.
For more information on setting up DDIs, see Managing DDIs on page 96. As an optional step,
you can also associate a telephone number with your DDI. For more information on how to
associate telephone numbers and DDIs, see Managing Telephones on page 103.
CS7000 System Administrator Guide for Release 9.5
September 2006
263
Chapter 17: Administering the Avaya Demand PIN Master
In the Demand.ini, you must associate a parameter called Tollfree with the PRI resource that
you have set up for toll-free conferencing. For more information on the Tollfree parameter,
see Table 85.
When you configure the Tollfree parameter in Demand.ini, the CS7000 only allows callers to
use toll-free DDIs to access toll-free conferences. If callers try to use toll-free DDIs to access
non-toll-free conferences, the CS7000 does not permit access and plays an explanatory
message. To enable the message, you must set the message number in Demand.ini. A
parameter called PMTollFreeFailMsg holds the message number. For more information on
the PMTollFreeFailMsg parameter, see Table 85.
Together, the Tollfree and PMTollFreeFailMsg parameters prevent callers accessing
"paying" conferences using a free telephone number. You can also configure the CS7000 to
disconnect these callers once they hear the explanatory message.
If you want to disconnect callers who try to use toll-free DDIs to access non-toll-free
conferences, you must set the parameter, PMDO_TF in Demand.ini. For more information on the
PMDO_TF parameter, see Table 85.
It is important to note that PMDisconnect controls all disconnect functionality. To disconnect
callers, you must set PMDisconnect to 1. If you set PMDisconnect to 1, ensure that you
configure each PMDO setting to reflect the your system behaviour preferences.
●
PMDO_TF manages the outcome for callers who try to use a toll-free DDI to access a
non-toll-free conference.
●
PMDO_L manages the outcome for callers who are locked out of conferences.
●
PMDO_F manages the outcome for callers who try to access conferences that are full.
●
PMDO_P manages the outcome for callers who exceed the maximum number of PIN
attempts.
Table 85 describes each of these parameters.
If you want Toll-free to be selected by default on the CRS Front End Booking dialog, you can
configure a setting called Tollfree in bands.ini. For more information, see Table 18 and
Configuring the Bands Initialization File on page 127.
The Avaya Operator Console displays an indicator in the Toll Free conference heading column
if a conference is a toll-free conference. This indicator enables Operators to easily identify a
toll-free conference. For more information, see the Avaya CS7000 Suite Release 9.5 Operator
Guide.
264
CS7000 System Administrator Guide for Release 9.5
September 2006
Time Synchronization
Time Synchronization
The Demand PIN Master ensures that its system clock is synchronized with the CRS system
clock by regularly polling the CRS computer. Time synchronization between the Demand PIN
Master and the CMS ensures that conference start and end times are the same in both
systems.
Demand.ini
The demand.ini file contains the parameters used in the Demand PIN Master. It includes the
following parameters:
Table 85: Settings
Parameter
Example Value
PMPromptMsg
The PIN Master prompt message is the message that is played
to a caller to elicit their conference PIN. Avaya CS7000 contains
several prerecorded messages. New messages can also be
recorded. All messages are associated with a numeric identifier.
PIN Master prompt message holds the message identifier.
PMRetryMsg
The PIN Master retry message is the message that is played to a
caller to elicit a further conference PIN entry. The PIN Master
retry message holds the message identifier.
PMCLIFailMsg
The PIN Master CLI fail message plays when the telephone
number that the caller uses to dial into the conference, is not
recognised. In a Meet Me Secure CLI Validation conference, the
telephone number used to dial into the conference must match
the number in the participant list.
PMCLILenMax
In a CLI Validation conference, this parameter is the number of
CLI digits used when matching against the telephone number for
CLI validation. When PMCLILenMax is set to zero, the feature is
disabled.
PMPINSecs
PIN Master PIN seconds is the maximum amount of time that
can elapse during complete conference PIN entry. The default
value is ten seconds.
PMPINLenMin
The PIN Master minimum PIN length parameter is the minimum
conference PIN length that can be accepted without hash
termination. The default value is four.
1 of 7
CS7000 System Administrator Guide for Release 9.5
September 2006
265
Chapter 17: Administering the Avaya Demand PIN Master
Table 85: Settings (continued)
Parameter
Example Value
PMRetries
The PIN Master retries parameter is the number of retry attempts
a caller can make to enter their correct conference PIN. The
default value is two.
PMDisconnect
If PIN Master Disconnect is set to zero, the Demand PIN Master
routes the call to reception if...
●
The number of retries is exhausted
●
The conference is locked
●
The conference is full
If PIN Master Disconnect is set to non zero, the Demand PIN
Master can disconnect the call if...
●
The number of retries is exhausted
●
The conference is locked
●
The conference is full
If PIN Master Disconnect is set to non zero, four additional
parameters modify the behaviour of PIN Master Disconnect:
PMDO_L
PMDO_F
PMDO_P
PMDO_TF
If PIN Master Disconnect is set to non zero, these three
parameters override the setting in PIN Master Disconnect. If PIN
Master Disconnect is set to zero, the PIN Master Disconnect
setting is used and the three additional parameters are ignored.
PMDO_L
PMDO_L is ignored if PIN Master Disconnect (PMDisconnect) is
set to zero. If PIN Master Disconnect is set to non zero, PMDO_L
is used.
If PMDO_L=0, all calls to locked conferences are disconnected.
If PMDO_L=1, moderator calls to locked conferences are routed
to reception, but all other calls to locked conferences are
disconnected.
If PMDO_L=2, all calls to locked conferences are routed to
reception. Disable PMDisconnect for this condition. It defaults to
0.
2 of 7
266
CS7000 System Administrator Guide for Release 9.5
September 2006
Demand.ini
Table 85: Settings (continued)
Parameter
Example Value
PMDO_F
PMDO_F is ignored if PIN Master Disconnect (PMDisconnect) is
set to zero. If PIN Master Disconnect is set to non zero, PMDO_F
is used.
If PMDO_F=0, all calls to full conferences are disconnected.
If PMDO_F=1, moderator calls to full conferences are routed to
reception, but all other calls to full conferences are disconnected.
If PMDO_F=2, all calls to full conferences are routed to
reception. Disable PMDisconnect for this condition. It defaults to
0.
PMDO_P
PMDO_P is ignored if PIN Master Disconnect (PMDisconnect) is
set to zero. If PIN Master Disconnect is set to non zero, PMDO_P
is used.
If PMDO_P=0, all calls in which the maximum number of PIN
retries are exhausted, are disconnected.
If PMDO_P=1, moderator calls in which the maximum number of
PIN retries are exhausted are routed to reception. However, all
other calls in which the maximum number of PIN retries are
exhausted, are disconnected.
If PMDO_P=2, all calls in which the number of retries are
exhausted, are routed to reception. Disable PMDisconnect for
this condition. It defaults to 0.
PMDO_TF
PMDO_TF is ignored if PIN Master Disconnect (PMDisconnect)
is set to zero. If PIN Master Disconnect is set to non zero,
PMDO_TF is used.
If PMDO_TF=0, all callers who attempt to access a non-toll-free
conference using a toll-free DDI are disconnected.
If PMDO_TF=1, moderators who attempt to access a
non-toll-free conference using a toll-free DDI, are routed to
reception. However, all other callers who attempt to access a
non-toll-free conference using a toll-free DDI, are disconnected.
If PMDO_TF=2, all callers who attempt to access a non-toll-free
conference using a toll-free DDI, are routed to reception. Disable
PMDisconnect for this condition. It defaults to 0.
PMLimit
PMLimit limits the number of calls that the system processes in
PIN reception at the same time. When the limit is exceeded, no
new calls are processed. Link lines for global conferences are
exempt from this limit. The default value for PMLimit=200. This
means that the system can process 200 calls at the same time.
If PMLimit=0, there is no limit. PMLimit is disabled. Avaya does
not recommend this option.
3 of 7
CS7000 System Administrator Guide for Release 9.5
September 2006
267
Chapter 17: Administering the Avaya Demand PIN Master
Table 85: Settings (continued)
Parameter
Example Value
DirectMod
DirectMod applies to DDIs that are flagged as direct. DirectMod
specifies a sequence, which, if detected on a DDI during the
greeting message, prompts for the conference PIN. If this
sequence is not detected, the caller is routed to the conference in
the normal way, as a non moderator.
PMClientPromptMsg
The PIN Master client prompt message is the message that is
played to a caller to elicit their client PIN.
PMClientRetryMsg
The PIN Master client retry message is the message that is
played to a caller to elicit a further client PIN entry.
PMClientPINSecs
The PIN Master client PIN seconds parameter is the maximum
amount of time that can elapse during complete client PIN entry.
PMClientPINLenMin
The PIN Master client minimum PIN length parameter is the
minimum client PIN length that can be accepted without hash (#)
termination. If using Meet Me Secure with variable PIN length,
this number must be set high, for example, 10, to force #
termination.
PMClientRetries
The PIN Master client retries parameter is the number of retry
attempts a caller can make to enter their correct client PIN.
ModOpenModConf
The Moderator Open, Moderator Conference parameter
determines whether a non moderator can open a moderator
conference. The default value is 1. This value means that only a
moderator can open a moderator conference. Set the value to 0
to enable all participants to open conferences.
DemandCNFGroups
DemandCNFGroups specifies a CNF group. It overrides the
value in CNFGroups.
DemandBridgeGroups
DemandBridgeGroups specifies a bridge group. It overrides the
value in BridgeGroups. It is similar to DemandCNFGroups.
BSTimeSyncMins
If BSTimeSyncMins is set to zero, time synchronization is
disabled.
If BSTimeSyncMins is set to non zero, it specifies the interval
time between Demand PIN Master and CRS synchronization.
The default value is 0.
4 of 7
268
CS7000 System Administrator Guide for Release 9.5
September 2006
Demand.ini
Table 85: Settings (continued)
Parameter
Example Value
CrisisHold
The CrisisHold parameter ensures that the initiating call of a
crisis alert is placed on hold until one of the dialed calls is
answered. The CrisisHold parameter has four possible values:
0 = This feature is disabled.
The following values determine what happens to the call if the
conference closes:
1 = The call is left on hold.
2 = The call is routed to reception.
3 = The call is disconnected.
The default value is zero.
DialHold
The DialHold parameter enables the Dial Hold Release feature
on any calls dialed from a participant list. The Dial Hold Release
feature is a voicemail filter.
EmptyAtOneSecs
If you set the EmptyAtOneSecs parameter to non zero, demand
conferences close if only one conferee remains for that number
of seconds. For example, if you set EmptyAtOneSecs to 180, the
demand conference closes if only a single conferee remains for a
period of three minutes.
By default, the EmptyAtOneSecs parameter is disabled:
EmptyAtOneSecs=0
DialTimeoutSecs
The parameter, DialTimeoutSecs, was active in previous
releases but in recent times, Avaya made it obsolete. Avaya has
now reinstated DialTimeoutSecs. It now ensures that if users do
not answer calls that the system starts, the system disconnects
these calls. DialTimeoutSecs specifies a timeout, in seconds,
after which the system disconnects these unanswered calls. The
default value is zero. Any value, greater than zero equates to the
timeout period.
DialTimeoutSecs enables the system to make several attempts
to contact a participant for alert conferencing. For example, if the
caller does not respond to a call to their main telephone number,
the system dials a secondary contact number. If they do not
respond to this call, the system dials a third contact number. For
more information, see the Avaya CS7000 Alerts Conferencing
Guide for Release 9.5.
CustomerDataSource
The parameter, CustomerDataSource, controls whether the
system starts the Customer.dll file. If you ensure that
CustomerDataSource is blank, the system does not start the
Customer.dll file. The system uses the Customer.dll file to look
up a linked database for external CLI identification. If
CustomerDataSource is blank, CLI identification is disabled.
5 of 7
CS7000 System Administrator Guide for Release 9.5
September 2006
269
Chapter 17: Administering the Avaya Demand PIN Master
Table 85: Settings (continued)
Parameter
Example Value
LastConfereeSecs
If a single participant is alone in a conference for a configurable
number of seconds, the system alerts the Operator. This feature
operates for demand or scheduled, non-global conferences. If
LastConfereeSecs is greater than zero, the system enables
the timer. The value of LastConfereeSecs specifies the
timeout period in seconds. When the timer expires, the system
generates an alert for the Operator. The timer then resets and
repeats after the same timeout.
Tollfree
The parameter, Tollfree, holds the identity of the PRI card that
is used for toll-free conferencing. When you set up a PRI system
card in the System Administration section of the CRS Front End,
you associate it with a resource reference number. To enable the
effective operation of toll-free conferencing, you must enter the
resource reference number of the toll-free PRI card in this
parameter. For example, if the resource reference number of the
toll-free PRI card is 2, Tollfree=2.
The effective operation of toll-free conferencing prohibits the use
of toll-free DDIs to gain access to non-toll-free conferences.
The parameter, Tollfree operates in conjunction with the
parameter, PMTollFreeFailMsg.
PMTollFreeFailMsg
The parameter, PMTollFreeFailMsg, holds the message number
of the message that the CS7000 plays to callers who attempt to
access a non-toll-free conference using a toll-free DDI.
The parameter, PMTollFreeFailMsg operates in conjunction
with the parameter, Tollfree. Together, these parameters
prevent callers accessing "paying" conferences using a free
telephone number.
ModDialNotifyMsg
The parameter, ModDialNotifyMsg, holds the message
number of the message that the CS7000 plays to Moderators
who dial into a management alert conference and start the
dialing of callers. The CS7000 does not take account of whether
the calls are answered. The message is played when the
CS7000 finishes dialing the last person in the dial list.
The parameter ModDialNotifyMsg operates in conjunction
with the parameter ModDialSecs.
6 of 7
270
CS7000 System Administrator Guide for Release 9.5
September 2006
Demand.ini
Table 85: Settings (continued)
Parameter
Example Value
ModDialSecs
The parameter ModDialSecs controls the delay, in seconds,
between the completion of a management alert dial out and the
playing of the message that indicates to the Moderator that the
dial out is complete. Moderators, who dial into a management
alert conference and start the dialing of callers, hear a notification
message when the dial out is complete. ModDialSecs controls
the time between the completion of the dial out and the playing of
the message. However, if the time it takes to dial out to all the
callers exceeds the value of ModDialSecs, the CS7000 plays
the notification message immediately after the final caller is
dialed.
DialTXtimer
The parameter, DialTXTimer controls the time, in milliseconds,
that the CS7000 waits between dialing callers in a blast dial. If
DialTXtimer=500, the CS7000 waits for .5 seconds between
each call in the dial list. This delay ensures that the PBX system
does not overload with simultaneous calls. Operators can also
set a value for DialTXtimer on the Avaya Operator Console.
The CS7000 uses the Avaya Operator Console DialTXtimer
value for blast dials that the Operator initiates from the console.
The CS7000 uses the Demand.ini DialTXtimer value for blast
dials that the Moderator initiates using a DMTF key sequence.
For more information on configuring DialTXtimer on the Avaya
Audio Console, see the Avaya CS7000 9.5 Suite Release
Operator Guide.
7 of 7
CS7000 System Administrator Guide for Release 9.5
September 2006
271
Chapter 17: Administering the Avaya Demand PIN Master
272
CS7000 System Administrator Guide for Release 9.5
September 2006
Index
Index
A
AC . . . . . . . . . . . . .
AccountNumberLength . . . .
acs.fil . . . . . . . . . . . .
AdHocAccountNumberLength
administrator . . . . . . . .
alarms and errors . . . . . .
AllLanguageSupported . . . .
Any cabinet . . . . . . . . .
AnyCabinetFlag . . . . . . .
application recordings . . . .
aprec.fil . . . . . . . . . . .
AttachmentsDir . . . . . . .
audio conferencing . . . . . .
AutoPIN . . . . . . . . . . .
D
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 47
. 124
. 50
. 124
. 68
. 44
. 136
. 89
90, 141
. . 42
. . 58
. . 156
. . 47
. . 141
Data Connections Ltd .
database . . . . . . .
DCL . . . . . . . . .
DDI . . . . . . . . .
DDI fields . . . . . .
DDI table. . . . . . .
Demand.ini file . . . .
DialGroups . . . . . .
Do Stop . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
60
32
60
96
98
39
38
38
47
E
emi.fil . . . . . . . . . . . . . . . . . . . . . . . 58
EnterPinCode . . . . . . . . . . . . . . . . . . 142
B
F
bands.ini . . . . . . . . . . . . . . . . . . . . . 127
bands.ini parameters . . . . . . . . . . . . . . . . 128
BSMon . . . . . . . . . . . . . . . . . . . . . . 47
faxes . . . . . . . . . . . . . . . . . . . . . . 154
field names. . . . . . . . . . . . . . . . . . . . 125
G
C
CabinetRef . . . . . . . . . . . . .
ccl_trace . . . . . . . . . . . . . .
cdr_ctrl.fil . . . . . . . . . . . . . .
CheckAccountSize . . . . . . . . . .
CheckPINSize . . . . . . . . . . . .
CLI validation . . . . . . . . . . . .
CMS . . . . . . . . . . . . . . . .
applications . . . . . . . . . . .
starting . . . . . . . . . . . . . .
version details . . . . . . . . . .
CMS files . . . . . . . . . . . . . .
cnf.fil . . . . . . . . . . . . . . . .
conf.fil . . . . . . . . . . . . . . . .
conference configurations . . . . . .
ConferenceReminderXMinutesBefore .
configuring field names . . . . . . . .
cons.fil . . . . . . . . . . . . . . .
CRS . . . . . . . . . . . . . . . .
Ctrlpos.ini . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . 141
. . 58
. . 58
. . 132
. . 131
. . 101
. . 19
. . 22
. . 22
. . 26
. . 20
. . 51
. 53, 58
. . 32
. . 116
. . 125
. . 57
. . 61
. . 125
CS7000 System Administrator Guide for Release 9.5
GCDUTimer . . . . . . . . . . . . . . . . . . . 135
H
hh.fil . . . . . . . . . . . . . . . . . . . . . . . . 58
Hhconferee.fil . . . . . . . . . . . . . . . . . . . 58
hunt group . . . . . . . . . . . . . . . . . . . . 101
I
IcDdi . . . . . . . . . .
icddi.fil . . . . . . . . .
information logs . . . .
initialization . . . . . .
IP addresses . . . . . .
ISF . . . . . . . . . .
isf.fil . . . . . . . . . .
IsSalesPersonMandatory
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . 39
. . . 52
. . 163
. . . 64
. . . 41
. . . 40
. . . 52
. 86, 125
September 2006
273
Index
L
R
LI3.fil . . . . . . . . . . . . . . . . . . . . . . . 51
ListConferenceActivity . . . . . . . . . . . . . . . 117
logins . . . . . . . . . . . . . . . . . . . . . . . 67
ReadOnlyClients . . .
ReadOnlyCompanies .
RealNetworks . . . .
recording settings. . .
reference numbers . .
resellers . . . . . . .
resources . . . . . .
RollCall . . . . . . .
routing.fil . . . . . . .
RTP . . . . . . . . .
M
MaxConferencePerBooking.
MaxConferenceSize . . . .
MaxNumberExtension . . .
MaxReceptionConferenceId
mf.fil . . . . . . . . . . .
MinConferenceDuration . .
MinConferenceSize . . . .
MinutesBetweenDDIReuse .
multisite . . . . . . . . . .
multisite servers . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 121
. 118
. 118
. 123
. 59
. 119
. 119
. 118
. 111
. 111
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 147
. 148
. 103
. 151
. 58
ogrouting.fil . . . . . . . . . .
OneMinuteWarning . . . . . .
Operator Console configurations
operators . . . . . . . . . . .
optional features . . . . . . . .
outgoing routing . . . . . . . .
Overbooking
System Parameters . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
N
NameOnEntry . . . . .
NameOnExit . . . . . .
notifications . . . . . .
notifications subsystem .
numbers.fil . . . . . .
.
.
.
.
.
.
.
.
.
.
O
36
119
33
67
66
36
. . . . . . . . . . 116
P
PBX. . . . . . . . . . . . . . .
perpetual conferences . . . . . .
PerpCPreBookPeriod . . . . .
PinCodeLength . . . . . . . . .
PlayStartingUpToXMinutesBefore .
pri.fil . . . . . . . . . . . . . .
process flags . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 96
. 121
. 122
. 124
. 120
. 51
. 165
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
133
132
167
. 35
. 67
. 81
. 94
145
. 52
. 60
sales contact . . . . . . . .
sales people . . . . . . . .
ScheduleColumns700 . . .
SendAttachments. . . . . .
serial.fil . . . . . . . . . .
SIP addresses . . . . . . .
SizeExtensionPeriodMinutes
socket interface . . . . . .
statistics . . . . . . . . . .
StrictValidation . . . . . . .
SubConfSize . . . . . . . .
supervisor . . . . . . . . .
sync.fil . . . . . . . . . . .
sysparm.fil . . . . . . . . .
system cards . . . . . . . .
system components . . . .
system configuration files . .
aprec.fil . . . . . . . . .
cdr_ctrl.fil . . . . . . . .
cnf.fil . . . . . . . . . .
conf.fil . . . . . . . . .
cons.fil . . . . . . . . .
emi.fil . . . . . . . . . .
hh.fil . . . . . . . . . .
hhconferee.fil . . . . . .
icddi.fil . . . . . . . . .
isl.fil . . . . . . . . . .
LI3.fil . . . . . . . . . .
mf.fil . . . . . . . . . .
pri.fil . . . . . . . . . .
routing.fil . . . . . . . .
serial.fil . . . . . . . . .
sync.fil . . . . . . . . .
sysparm.fil . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 87
. 86
S
137
156
. 59
. 41
120
. 46
. 45
136
141
. 68
. 59
. 53
. 92
. 73
. 50
. 58
. 58
. 51
53, 58
. . 57
. . 58
. . 58
. . 58
. . 52
. . 52
. . 51
. . 59
. . 51
. . 52
. . 59
. . 59
. . 53
Q
QandA . . . . . . . . . . . . . . . . . . . . . . 145
274
CS7000 System Administrator Guide for Release 9.5
September 2006
Index
System Parameters
AccountNumberLength . . . . . . .
AdHocAccountNumberLength . . . .
ConferenceReminderXMinutesBefore
FreeIfCancelledXMinutesBefore . . .
IsPinCodeMandatory . . . . . . . .
IsSalesPersonMandatory . . . . . .
ListConferenceActivity . . . . . . .
MaxConferencePerBooking . . . . .
MaxConferenceSize . . . . . . . .
MaxNumberExtension . . . . . . .
MaxReceptionConferenceId . . . . .
MinConferenceDuration . . . . . . .
MinConferenceSize . . . . . . . . .
MinutesBetweenDDIReuse . . . . .
OneMinuteWarning . . . . . . . . .
Overbooking . . . . . . . . . . . .
PerpCPreBookPeriod . . . . . . . .
PinCodeLength . . . . . . . . . . .
PlayStartingUpToXMinutesBefore . .
SizeExtensionPeriodMinutes . . . .
TenMinuteWarning . . . . . . . . .
system status . . . . . . . . . . . . .
system status fields . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . 124
. . . 124
. . . 116
.116, 117
. . . 125
. . . 125
. . . 117
. . . 121
. . . 118
. . . 118
. . . 123
. . . 119
. . . 119
. . . 118
. . . 119
. . . 116
. . . 122
. . . 124
. . . 120
. . . 120
. . . 121
. . . 27
. . . 27
T
telephones . . . .
TenMinuteWarning
time zones . . . .
toll free . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
103
121
107
104
U
UDP . . . . . . . . . . . . . . . . . . . . . . . . 60
V
VoIP . . . . . . . . . . . . . . . . . . . . . . . . 60
W
WaitForModerator . . . . . . . . . . . . . . . . 145
wholesalers . . . . . . . . . . . . . . . . . . 70, 77
Z
ZeroStartPIN . . . . . . . . . . . . . . . . . . . 131
CS7000 System Administrator Guide for Release 9.5
September 2006
275
Index
276
CS7000 System Administrator Guide for Release 9.5
September 2006
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement