Avaya Aura

Implementing Avaya Aura™ Conferencing
04-603508
Issue 1
June 2010
Contents
Chapter 1: Choosing Conferencing™ 6.0..............................................................................15

Avaya Aura™ Conferencing 6.0......................................................................................................................15
Conferencing comparison tables.....................................................................................................................15
What you get...................................................................................................................................................18
Chapter 2: Updating network information.............................................................................19

Introduction to network information.................................................................................................................19
A series of short tasks.....................................................................................................................................20
Updating network information on System Platform................................................................................21
Verifying network information on System Platform.................................................................................24
Verifying connectivity..............................................................................................................................25
Manually restarting the Avaya Management Service on AWC...............................................................26
Updating network information on Conferencing Manager......................................................................27
Updating information on the CRS virtual machine..................................................................................29
Making changes to date and time...................................................................................................................30
Chapter 3: Preinstalling Conferencing..................................................................................31

Preinstallation steps........................................................................................................................................31
Registering for PLDS......................................................................................................................................32
Downloading software in PLDS.......................................................................................................................33
Verifying the downloaded ISO image..............................................................................................................33
Verifying the ISO image on a Linux-based computer.............................................................................33
Verifying the ISO image on a Windows-based computer.......................................................................34
Writing the downloaded software to DVD........................................................................................................35
DVD recommendations..........................................................................................................................35
Writing the ISO image to DVD................................................................................................................35
Extracting the content of the ISO images........................................................................................................36
Extracting the files to a Linux machine...................................................................................................36
Extracting the files to a Windows machine.............................................................................................38
Chapter 4: Installing Conferencing........................................................................................39

Conferencing installation.................................................................................................................................39
Installing Conferencing using DVDs.......................................................................................................41
Installing Conferencing using HTTP.......................................................................................................44
Windows licensing...........................................................................................................................................45
Entering Windows keys using Xming and PuTTY..................................................................................46
Setting the time after entering Windows keys........................................................................................48
Patch management.........................................................................................................................................49
Installing and activating Conferencing Manager patches.......................................................................50
Installing and activating regular patches................................................................................................52
System Manager/Conferencing Manager and virtual machines.....................................................................54
Adding virtual machines to Conferencing Manager................................................................................55
CRS virtual machine connectivity....................................................................................................................55
Assigning virtual machines to the CRS..................................................................................................56
A license for Conferencing..............................................................................................................................57
Applying a Conferencing license............................................................................................................57
Troubleshooting installation.............................................................................................................................58
Chapter 5: Connecting Conferencing to your network........................................................61
Implementing Avaya Aura™ Conferencing June 2010 3

Overview of supported deployments...............................................................................................................61
Conferencing and Communication Manager..........................................................................................62
Conferencing and Session Manager......................................................................................................63
Conferencing and Audiocodes...............................................................................................................63
Conferencing and Communications Server 1000E (CS1K)....................................................................64
SIP settings.....................................................................................................................................................64
SIP listener URI......................................................................................................................................64
Response contact...................................................................................................................................65
Session refresh timer..............................................................................................................................65
Min session refresh timer allowed..........................................................................................................66
Configuring SIP...............................................................................................................................................66
Chapter 6: Configuring telephone numbers.........................................................................67

Call routing......................................................................................................................................................67
Obtaining conference telephone numbers......................................................................................................67
Number of digits to match...............................................................................................................................68
Configuring the number of digits to match..............................................................................................68
Call branding...................................................................................................................................................69
Adding a call branding entry...................................................................................................................73
Editing a call branding entry...................................................................................................................75
Deleting a call branding entry.................................................................................................................75
DDI phones.....................................................................................................................................................76
Adding DDI phones................................................................................................................................76
Deleting DDI phones..............................................................................................................................77
Configuration of Conferencing to handle a number it does not recognize......................................................77
Adding a wildcard...................................................................................................................................78
Pattern matching.............................................................................................................................................79
Tel num to URI........................................................................................................................................80
URI to tel num.........................................................................................................................................81
Configuring patterns for dialing in...........................................................................................................83
Configuring patterns for dialing out.........................................................................................................83
Chapter 7: Verifying your installation....................................................................................85

Verification.......................................................................................................................................................85
Application server............................................................................................................................................85
Key features...........................................................................................................................................85
Placing a call..........................................................................................................................................87
Client Registration Server...............................................................................................................................88
Installing CRS Front End on the CRS server.........................................................................................88
Creating a test conference.....................................................................................................................90
Distributing CRS Front End to the operators..........................................................................................91
Web Portal.......................................................................................................................................................91
Accessing Web Portal............................................................................................................................92
Accessing Web Portal using PuTTY.......................................................................................................93
Avaya Web Conferencing................................................................................................................................94
Accessing AWC......................................................................................................................................95
Chapter 8: Configuring logs and alarms...............................................................................97

Logs and alarms..............................................................................................................................................97
Three pieces of information...........................................................................................................................104
Enrollment password............................................................................................................................104
Avaya Aura™Conferencing 6.0 Managed Element ID..........................................................................104
4 Implementing Avaya Aura™ Conferencing June 2010

Avaya Aura™ Alarming ID....................................................................................................................104
Obtaining the three pieces of information.....................................................................................................105
Configuring logs and alarms.........................................................................................................................106
Sending the logs and alarms to a network management system..................................................................107
Viewing logs and alarms...............................................................................................................................108
Troubleshooting logs and alarms..................................................................................................................108
Location of additional logs of interest............................................................................................................109
Chapter 9: Configuring the application server....................................................................111

Bridge features..............................................................................................................................................112
Media servers.......................................................................................................................................112
Prompt set management......................................................................................................................112
Bridge features.....................................................................................................................................113
Scheduling............................................................................................................................................116
Sign in users.........................................................................................................................................118
Configuring bridge features..................................................................................................................120
Conference features......................................................................................................................................121
Conference defaults.............................................................................................................................122
Conference settings..............................................................................................................................125
Conference error behavior....................................................................................................................131
Conference features.............................................................................................................................133
Adhoc conferencing..............................................................................................................................134
Configuring conference features..........................................................................................................135
Call routing....................................................................................................................................................136
Dial out.................................................................................................................................................137
Blast dial settings..................................................................................................................................138
System configuration.....................................................................................................................................141
Networking............................................................................................................................................141
NFS mounts..........................................................................................................................................145
SAL connectivity settings......................................................................................................................147
Miscellaneous.......................................................................................................................................148
Configuring system configuration.........................................................................................................149
General configuration....................................................................................................................................150
General.................................................................................................................................................151
DTMF controls......................................................................................................................................157
Recording and playback.......................................................................................................................168
Logging.................................................................................................................................................170
Flex settings.........................................................................................................................................172
Billing....................................................................................................................................................174
RAI configuration..................................................................................................................................175
Port pool usage thresholds...................................................................................................................176
Configuring general configuration settings...........................................................................................178
Chapter 10: Configuring media settings.............................................................................181

Media server settings....................................................................................................................................181
Media server features settings......................................................................................................................181
Audio quality.........................................................................................................................................181
Video quality.........................................................................................................................................183
TTY.......................................................................................................................................................183
SRTP....................................................................................................................................................184
Network performance...........................................................................................................................185
Media server configuration settings..............................................................................................................186

General.................................................................................................................................................186
Media codecs.......................................................................................................................................187
SIP settings..........................................................................................................................................189
Chapter 11: Configuring the CRS.........................................................................................191

Client Registration Server.............................................................................................................................191
CRS configuration.........................................................................................................................................191
General settings...................................................................................................................................192
Reseller settings...................................................................................................................................223
Timezone settings.................................................................................................................................223
User settings.........................................................................................................................................224
Wholesaler settings..............................................................................................................................229
Chapter 12: Configuring the AWC........................................................................................231

Avaya Web Conferencing..............................................................................................................................231
Configuration of AWC using Conferencing Manager....................................................................................231
Login type.............................................................................................................................................232
Configuration of your network in preparation for AWC..................................................................................233
Configuration of the AWC virtual machine....................................................................................................235
Licensing AWC.....................................................................................................................................236
Configuring the AWC Windows password............................................................................................237
Administration of AWC..................................................................................................................................238
Verifying the license..............................................................................................................................239
Creating new administrator logins........................................................................................................240
Configuring AWC password settings....................................................................................................240
Deleting duplicate servers....................................................................................................................241
Installing AWC in a DMZ...............................................................................................................................242
Manually starting AWC..................................................................................................................................244
Disabling the AWC permanently...................................................................................................................245
Chapter 13: Configuring the Web Portal.............................................................................247

Web Portal virtual machine...........................................................................................................................247
Audio Console...............................................................................................................................................247
Client registration server.......................................................................................................................247
Login type.............................................................................................................................................248
Web Portal.....................................................................................................................................................248
Client registration server.......................................................................................................................249
Login type.............................................................................................................................................249
Mail server............................................................................................................................................250
Mail from...............................................................................................................................................250
SSL enabled.........................................................................................................................................251
SSL certificate......................................................................................................................................251
SSL private key....................................................................................................................................251
HTTPS..................................................................................................................................................252
Brand prefix..........................................................................................................................................252
Chapter 14: Configuring the Conferencing watchdog.......................................................253

Booking and scheduling monitor...................................................................................................................253
Configuring BSMon to monitor an application...............................................................................................253
Chapter 15: Activating and deactivating virtual machines................................................255

Virtual machines and services.......................................................................................................................255

Activating virtual machines and services......................................................................................................256
Deactivating virtual machines and services..................................................................................................256
Chapter 16: Backing up and restoring settings..................................................................259

Backing up and restoring..............................................................................................................................259
Two stages in the backup process, three stages in the restore process..............................................260
What is included?.................................................................................................................................261
What is not included?...........................................................................................................................263
System Platform backup...............................................................................................................................265
Backing up the system by using the System Platform Web Console...................................................266
Scheduling a backup............................................................................................................................266
Transferring the Backup Archives to a remote destination...................................................................267
Viewing backup history.........................................................................................................................267
Backup field descriptions......................................................................................................................268
Additional backup..........................................................................................................................................269
Backing up using PuTTY......................................................................................................................269
Stop AWC restore.........................................................................................................................................271
Disabling AWC restore.........................................................................................................................272
System Platform restore................................................................................................................................273
Restoring backed up configuration information....................................................................................274
Additional restore..........................................................................................................................................276
Restoring using PuTTY........................................................................................................................276
Chapter 17: Configuring languages.....................................................................................281

Introduction to languages..............................................................................................................................281
A point of clarification regarding languages..................................................................................................283
System language..................................................................................................................................283
Conference language...........................................................................................................................283
Participant experience..........................................................................................................................284
Scope of localization.....................................................................................................................................284
Internationalization...............................................................................................................................285
Localization...........................................................................................................................................285
Plug-in components..............................................................................................................................285
Web components..................................................................................................................................287
CRS components.................................................................................................................................287
APIs......................................................................................................................................................288
Application server components............................................................................................................288
Operator components...........................................................................................................................289
Chapter 18: Configuring audio messages..........................................................................291

Audio messages and prompt sets.................................................................................................................291
Per conference messages....................................................................................................................292
System wide messages........................................................................................................................293
Message rules......................................................................................................................................293
Audio transcript.....................................................................................................................................295
Linked files and linking.........................................................................................................................295
Configuring audio messages for your system...............................................................................................296
Configuring audio messages at conference-level.........................................................................................297
Viewing prompt sets......................................................................................................................................298
Chapter 19: Configuring recording......................................................................................301

Introduction to recording...............................................................................................................................301

Some important parameters relating to recording.........................................................................................301
Digital conference record playback......................................................................................................302
Bridge record........................................................................................................................................302
Phone number......................................................................................................................................303
Dial string..............................................................................................................................................303
Pre dial delay period.............................................................................................................................303
DRP auto gen fname............................................................................................................................304
Playback small jump.............................................................................................................................304
Playback medium jump........................................................................................................................304
Playback long jump..............................................................................................................................304
Automatic record all..............................................................................................................................305
Secure blocks record............................................................................................................................305
Bridge ID number.................................................................................................................................306
Number of annunciator channels..........................................................................................................306
Enabling the recording feature......................................................................................................................307
Configuring the recording feature..................................................................................................................308
Configuring the playback call flow.................................................................................................................309
Managing files...............................................................................................................................................309
User access..........................................................................................................................................310
File sizes and file names......................................................................................................................310
Legacy Web Portal feature...................................................................................................................312
Chapter 20: Producing bills for conferences......................................................................313

Introducing billing..........................................................................................................................................313
Layout of bills................................................................................................................................................313
Billing configuration.......................................................................................................................................314
Primary bill file location.........................................................................................................................315
Secondary bill file location....................................................................................................................315
Bill file extension...................................................................................................................................315
Bill file prefix.........................................................................................................................................315
Bill frequency........................................................................................................................................316
Bill start offset (mins)............................................................................................................................316
Bill at time.............................................................................................................................................316
Bill file header.......................................................................................................................................317
Bill file trailer.........................................................................................................................................317
Period to retain CDR files.....................................................................................................................317
Free if cancelled X minutes before.......................................................................................................317
Configuring billing.................................................................................................................................317
Billing application graphic user interface (GUI).............................................................................................318
Creating a bill for a specific date...................................................................................................................320
Creating a bill for a specific date range.........................................................................................................321
Clarification on billing scenarios....................................................................................................................321
Rebilling........................................................................................................................................................322
Chapter 21: Configuring e-mail notifications......................................................................323

Introduction to notifications...........................................................................................................................323
Notification settings.......................................................................................................................................324
Conference reminder X minutes before................................................................................................325
Activate e-mail notifications..................................................................................................................325
Activate attachments............................................................................................................................326
Attachments directory...........................................................................................................................326
Activate SMS notifications....................................................................................................................327

Activate attendance notifications..........................................................................................................327
Web conferencing URL........................................................................................................................327
Self registration URL............................................................................................................................327
Activate vcalendar................................................................................................................................328
Activate SMTP......................................................................................................................................328
SMTP server address...........................................................................................................................328
SMTP server port.................................................................................................................................328
SMTP username...................................................................................................................................329
SMTP password...................................................................................................................................329
E-mail sender.......................................................................................................................................329
Authenticate..........................................................................................................................................329
HTML format.........................................................................................................................................330
Attendance record processing delay....................................................................................................330
Configuring notification settings....................................................................................................................330
Advanced settings.........................................................................................................................................331
The variables in the template........................................................................................................................332
Customizing e-mail templates.......................................................................................................................334
Viewing logs..................................................................................................................................................335
Chapter 22: Understanding PINs, passcodes, and security..............................................337

Understanding some terms...........................................................................................................................337
PIN functionality............................................................................................................................................338
PINs in use...........................................................................................................................................339
Secret PIN functionality.................................................................................................................................340
Secret PINs in use................................................................................................................................341
Secret PIN administration.....................................................................................................................342
Passcode functionality..................................................................................................................................347
Auto generated passcode length..........................................................................................................348
Period to conference passcode renewal..............................................................................................348
Period of passcode overlap..................................................................................................................350
Maximum passcode length...................................................................................................................351
Minimum passcode length....................................................................................................................351
Passcodes in use in the Web applications...........................................................................................351
Summary.......................................................................................................................................................352
Chapter 23: Configuring LDAP for Conferencing...............................................................355

The Directory Services Client Application (DSCA)........................................................................................355
DSCA parameters................................................................................................................................356
User data retrieved...............................................................................................................................363
DSCA demand profile creation.............................................................................................................364
DSCA and secure sockets layer...........................................................................................................364
DSCA and Web Portal..........................................................................................................................365
Exporting the certificate for CRS...................................................................................................................366
Installing the certificate and keystore for CRS..............................................................................................368
Exporting the certificate for Web Portal.........................................................................................................368
Installing the certificate for Web Portal..........................................................................................................369
Chapter 24: Understanding blast dial..................................................................................371

Introduction to blast dial................................................................................................................................371
Configuring blast dial settings.......................................................................................................................372
LDAP dial lists...............................................................................................................................................373
Configuration of CRS for LDAP............................................................................................................373

Dial lists saved on the application server......................................................................................................376
Configuring the CRS for application server dial lists............................................................................376
Linking a blast dial list to a conference.........................................................................................................377
Chapter 25: Importing companies, clients, and conferences...........................................379

Introduction to the Import Utility....................................................................................................................379
Import Utility main features...........................................................................................................................380
Preparation of data........................................................................................................................................381
Database compatibility.........................................................................................................................381
Input files..............................................................................................................................................381
Orphan clients......................................................................................................................................382
The logging file.....................................................................................................................................382
Attribute fields.......................................................................................................................................383
Field types............................................................................................................................................384
Existing records....................................................................................................................................385
Significant fields....................................................................................................................................385
The CRS Front End and duplication of content....................................................................................386
Demand conference profiles.................................................................................................................388
The Import Utility interface............................................................................................................................390
Import Utility fields................................................................................................................................392
Using Import Utility........................................................................................................................................394
Selecting fields.....................................................................................................................................394
Configuring on demand profiles............................................................................................................395
Finishing the import..............................................................................................................................398
Chapter 26: Importing and exporting configurations........................................................401

Introduction to the import and export process...............................................................................................401
Exporting the customer model..............................................................................................................402
Importing the customer model at the customer site..............................................................................403
Using Solution Modeller................................................................................................................................404
Creating your model in Solution Modeller.....................................................................................................405
Customizing/Configuring your model............................................................................................................406
Saving the model..........................................................................................................................................407
Loading the model.........................................................................................................................................408
Discarding the model....................................................................................................................................409
Chapter 27: Customizing the Web Portal application........................................................411

Web Portal administrator interface................................................................................................................411
Configuring the Web Portal display...............................................................................................................412
Legal disclaimer............................................................................................................................................413
Configuring a legal disclaimer..............................................................................................................413
Passcodes.....................................................................................................................................................414
Configuring Web Portal passcodes......................................................................................................415
Configuring participant ID identify and validate conferencing.......................................................................416
Time and date formats..................................................................................................................................417
Setting time and date............................................................................................................................418
Configuring booking options..........................................................................................................................419
Setting the navigation pane...........................................................................................................................420
Configuration of access to functionality.........................................................................................................421
Disabling/enabling conference booking options...................................................................................421
Disabling/enabling notification options.................................................................................................427
Disabling/enabling recurring conference options..................................................................................429

Recording......................................................................................................................................................430
Hiding functionality........................................................................................................................................432
Web Portal look and feel...............................................................................................................................433
Uploading files......................................................................................................................................434
Uploading graphics...............................................................................................................................435
Deleting customizations........................................................................................................................437
Searching for customizations............................................................................................................... 437
Localizing Web Portal....................................................................................................................................438
Chapter 28: Administering the Web Portal application......................................................441

Web Portal user authentication.....................................................................................................................441
Web Portal password expiry..........................................................................................................................443
Single sign on................................................................................................................................................445
Implementing single sign on.................................................................................................................446
Self administration.........................................................................................................................................449
Accessing the self administration configuration pages.........................................................................450
Configuring the automatic creation of on-demand conference.............................................................450
Specifying the fields on the self administration page for moderators...................................................451
Specifying self administration default values........................................................................................452
Hiding self administration..................................................................................................................... 457
Chapter 29: Customizing the Audio Console application................................................. 459

Customization............................................................................................................................................... 459
Logging on to Audio Console........................................................................................................................462
Customizing Audio Console..........................................................................................................................462
Activating and deactivating toolbar functions................................................................................................464
Enabling the sub conference feature............................................................................................................ 465
Properties file................................................................................................................................................ 466
Chapter 30: Integrating with Microsoft applications..........................................................469

Overview of Microsoft integrations................................................................................................................469
Avaya Conference Scheduler for Microsoft Outlook..................................................................................... 469
Prerequisites.........................................................................................................................................470
Conferencing for Microsoft Live Meeting and Microsoft Office Communicator............................................. 471
Microsoft adapter..................................................................................................................................471
OCS adapter.........................................................................................................................................472
Chapter 31: Installing/configuring Conference Scheduler for Microsoft Outlook.......... 475

Timezones.....................................................................................................................................................475
Stored procedures.........................................................................................................................................475
Configuring for a manual installation.............................................................................................................475
Configuring for a silent installation................................................................................................................ 476
Configurable settings.................................................................................................................................... 478
Configuring Conference Scheduler for Microsoft Outlook.............................................................................479
Ensuring that Conferencing notification e-mails are not classified as junk...........................................480
Reinstalling....................................................................................................................................................480
Chapter 32: Installing/configuring Conferencing for Microsoft Live Meeting.................481

Microsoft adapter installation........................................................................................................................ 481
Installing JRE........................................................................................................................................482
Installing Microsoft adapter...................................................................................................................483
Configuring BSmon.............................................................................................................................. 484

Uninstalling Microsoft adapter..............................................................................................................485
Microsoft adapter configuration.....................................................................................................................486
Configuring TLS....................................................................................................................................486
Microsoft adapter administrative interface............................................................................................488
Configuring the gateway settings.........................................................................................................490
Configuring the logs settings................................................................................................................491
Configuration of Microsoft Office Communications Server 2007 R2 for MSAdapter............................493
Microsoft adapter and the Conferencing application server..........................................................................495
Adding the application server...............................................................................................................496
Editing the application server...............................................................................................................497
Removing the application server..........................................................................................................498
Starting and stopping the application server........................................................................................498
Configuring the individual client machines....................................................................................................499
Chapter 33: Installing/configuring Conferencing for Microsoft Office Communicator

.................................................................................................................................................501
OCS adapter installation...............................................................................................................................501
Configuring JRE...................................................................................................................................502
Configuring .Net....................................................................................................................................503
Installing IIS..........................................................................................................................................503
Installing OCS adapter on the server...................................................................................................504
Installing OCS adapter on the client.....................................................................................................504
OCS adapter configuration............................................................................................................................505
Configuring OCS adapter.....................................................................................................................506
Configuring IIS......................................................................................................................................507
Configuration of the plug-in for your users....................................................................................................509
Accessing Conferencing Manager........................................................................................................510
Chapter 34: Integrating with IBM applications...................................................................513

Overview of IBM integrations........................................................................................................................513
Security considerations.................................................................................................................................514
Encrypting operator passwords............................................................................................................515
On demand conference considerations........................................................................................................516
Scheduled conference considerations..........................................................................................................518
Chapter 35: Configuring Conferencing for IBM Lotus Notes............................................521

The Conferencing Plug in for IBM Lotus Notes.............................................................................................521
Implementation considerations for IBM Lotus Notes.....................................................................................523
Configuring script libraries.............................................................................................................................524
Configuring sub forms...................................................................................................................................526
Configuring the calendar entry form..............................................................................................................527
Configuring database scripts.........................................................................................................................529
Configuring the Click to Call feature..............................................................................................................530
Enabling encryption between the SOAP server and the IBM Notes client....................................................531
Configuring logging.......................................................................................................................................532
Template updates for IBM Lotus Notes.........................................................................................................533
Jar file configuration......................................................................................................................................533
Using the Avaya e-mail template directly......................................................................................................534
Merging the Avaya e-mail template with your e-mail template......................................................................535
Chapter 36: Configuring Conferencing for IBM Lotus Sametime.....................................539

The Conferencing Plug in for IBM Lotus Sametime......................................................................................539

PIN enablement............................................................................................................................................540
Creating log ins for IBM Lotus Sametime......................................................................................................541
Enabling strong encryption............................................................................................................................542
Preparing the IBM Lotus Sametime server...................................................................................................543
Understanding some of the configuration files..............................................................................................544
Configuring conference-adapter-configuration.xml.......................................................................................544
Working with the CRS to create clients.........................................................................................................548
The IBM Lotus Sametime dialing plan..........................................................................................................549
Dialing plan mapping rules...................................................................................................................551
Configuring the dialing plan for campus sites.......................................................................................552
Configuring the dialing plan for local cities...........................................................................................553
Configuring the dialing plan for local countries.....................................................................................554
Configuring the dialing plan for international sites................................................................................556
Configuring the dialing plan for residential sites...................................................................................556
Mapping incoming dialed numbers to defined bridge numbers............................................................557
IBM Lotus Sametime logs.............................................................................................................................557
Telephony diagnostic log......................................................................................................................558
BCAPI log.............................................................................................................................................559
IBM Lotus Sametime Connect client.............................................................................................................560
Chapter 37: Viewing reports.................................................................................................561

Viewing Conferencing Reports......................................................................................................................561
Web Portal reports........................................................................................................................................561
Generating reports................................................................................................................................562
Chapter 38: Loading call detail records..............................................................................563

The Call Detail Record (CDR) Loader application........................................................................................563
The CDR Loader interface............................................................................................................................564
Some CDR Loader fields..............................................................................................................................565
Initialization file..............................................................................................................................................567
File management..................................................................................................................................567
Limitations on communciations ports...................................................................................................569
Secure file transfer protocol..................................................................................................................569
Troubleshooting the CDR Loader..................................................................................................................570
Chapter 39: Upgrading to/from Conferencing....................................................................571

Introduction to upgrading..............................................................................................................................571
Upgrading from Meeting Exchange Express.................................................................................................571
Chapter 40: Import Utility fields...........................................................................................575

Company fields.............................................................................................................................................575
Client fields....................................................................................................................................................576
Reservation and conference fields................................................................................................................577
Chapter 41: Avaya Aura™ Conferencing Implementation Workbook...............................585

Avaya Aura™ Conferencing implementation workbook................................................................................585
Avaya Aura™Conferencing overview............................................................................................................585
Architecture overview....................................................................................................................................586
Points of contact and site information...........................................................................................................587
Network and LAN information.......................................................................................................................589
SIP or TDM: ISDN configuration...................................................................................................................591
Remote access.............................................................................................................................................594

Implementation validation checklist...............................................................................................................595
Port usage.....................................................................................................................................................598
Miscellaneous notes......................................................................................................................................599
Index.......................................................................................................................................601

Chapter 1: Choosing Conferencing™ 6.0
Avaya Aura™ Conferencing 6.0

Avaya Aura™ Conferencing 6.0 is a fully integrated audio and data conferencing solution for
your organization. Conferencing consists of a number of components which provide booking
engines, account management utilities, data sharing functionality, billing outputs, directory
server integration capabilities, and audio management for all calls.
There are two flavors of Conferencing, as follows:
• The Standard Edition of Conferencing
• The Enterprise Edition of Conferencing
You must choose the solution which best matches your requirements. Typically, the Standard
Edition of Conferencing suits smaller deployments. In the Standard Edition of Conferencing,
the media server and the application server reside on a single server. Typically, the Enterprise
Edition of Conferencing suits larger, more complex deployments. The Enterprise Edition of
Conferencing supports complicated installations, such as those with multiple application
servers, a global distribution of servers, and redundancy requirements. The Enterprise Edition
of Conferencing also supports additional functionality, such as self registration for conferences,
reseller and wholesaler users, and video conference calls.
Conferencing comparison tables

Application server features
Feature Standard Edition of Enterprise Edition of

Conferencing Conferencing
Audio bridge
IP H.323
IP SIP
Maximum capacity 500 4000

Choosing Conferencing™ 6.0

Single server
Languages
SNMP alarming
Adhoc conferencing
Disaster recovery
Video
Database interface (API or stored

procedures)
Flex call flow
Bridge Talk application
Real-time conference control API
Media server features

Secure Real Time Transport
Protocol (SRTP)
Video conferencing
Multiple codecs
Separate media server
Applications

Multiple sites
Conference Viewer

Conferencing comparison tables

LDAP integration
Audio Console
Client Registration Server (CRS)
Self Registration
Web scheduling and Web

administration
Short message service (SMS)
notifications
Wholesalers and resellers
Billing
Reporting
E-mail notification subsystem
Multiple cabinets
Logical cabinet redundancy
Integrations with other products

Microsoft Outlook
Microsoft Office Communications

Server R2
IBM Lotus Sametime
IBM Lotus Notes
Adobe Connect
Avaya Web Conferencing

Choosing Conferencing™ 6.0

Avaya Web Conferencing recording
server
Avaya Web Conferencing playback
server
What you get

When you buy Avaya Aura™ Conferencing Standard Edition, you receive an IBM 3550 server
with all the required Conferencing software installed by default.
When you receive the Conferencing server, you only have to perform two tasks to complete
the installation:
• Change the IP and network information from the default values to the values in the
customer site.
• Apply a license to the software.
Note:
You may also have to apply some patches.
The full installation steps are included here for your information only. In the majority of cases,
you should never have to use these steps and you can proceed to the configuration steps after
you change the IP information and apply a license.
Related topics:
A series of short tasks on page 20
Applying a Conferencing license on page 57

Chapter 2: Updating network information
Introduction to network information

When you buy Avaya Aura™ Conferencing Standard Edition, you receive an IBM 3550 server
with all the required Conferencing software installed by default.
Avaya ships each server with a series of default or dummy IP addresses for each of the
Conferencing components. These default IP addresses and hostnames are listed here. You
must replace these IP addresses with the IP addresses from the customer site.
Component Explanation of Component Default Information

System Platform This is a generic virtual Cdom IP address
server software platform. 192.168.11.10
Cdom Host Name acevms1
Cdom IP Address
192.168.11.11
Cdom Host Name
acevms1cdom
Avaya Web Conferencing This is a data conferencing IP Address 192.168.11.15
(AWC) server. Host Name
xxxawc.avaya.com
Client Registration Server This is a customer booking IP Address 192.168.11.16
(CRS) server. Host Name
xxxcrs.avaya.com
Application server (bridge) Within the Conferencing IP Address 192.168.11.17
environment, this is called a Host Name
bridge. It hosts the mfg700a.avaya.com
conference calls.
Web Portal This is a customer booking IP Address 192.168.11.18
Web server. Host Name
xxxweb.avaya.com
Conferencing Manager This is a central management IP Address 192.168.11.19
and configuration console. It Host Name
enables you to manage and xxxsmgr.avaya.com
configure the other four
virtual machines. Some of
the fields on the interface

Updating network information
Component Explanation of Component Default Information

refer to Conferencing
Manager as SMGR. It is a
good idea to keep this point
in mind while you are
navigating through the
Conferencing installation
pages.
A series of short tasks

It is a good idea to think of the task of updating network information as a series of smaller tasks.
There are six small tasks in total.
For previous versions of Conferencing, Avaya provided the mx-ipChange.sh script to manage
the process of customizing Conferencing server network information. This script modified the
IP address, host name, domain name, netmask, gateway NTP, and the DNS of the server.
For this release of Conferencing, you can make changes to the IP addresses and hostnames of
the virtual machines in your network using System Platform. Each of the virtual machines
running on an instance of System Platform, must belong to the same subnet.
System Platform has two IP addresses or points of access. The browser access to System
Platform is sometimes called Customer/Console Domain (Cdom). The access to the base
operating system of System Platform is sometimes called Domain 0 (Dom0).
The other virtual machines that make up the Conferencing solution include:
• An application server
Within the Conferencing environment, this is called a bridge.
• A central management console
Within the Conferencing environment, this is called Conferencing Manager. It enables you
to manage the other four virtual machines. Some of the fields on the interface refer to
Conferencing Manager as SMGR. It is a good idea to keep this point in mind while you
are navigating through the Conferencing installation pages.
• A data conferencing server
Within the Conferencing environment, this is called Avaya Web Conferencing, or AWC.
• A customer booking server
Within the Conferencing environment, this is called a Client Registration Server or CRS.
• A customer booking Web server

Within the Conferencing environment, this is called Web Portal.

If you do not have network connectivity to the System Platform virtual machine, you must use a
crossover cable and a terminal emulator application called PuTTY to access System Platform.
PuTTY is a Linux SSH client that allows you to connect to other machines, giving you a terminal
window. You can download PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/putty/
download.html.
The six steps
The six tasks that are required to change the IP and hostname of Conferencing are as follows:
• Updating network information on System Platform
• Verifying network information on System Platform
• Verifying connectivity
• Manually restarting the Avaya Management Service on AWC
• Updating network information on Conferencing Manager
• Updating information on the CRS virtual machine
Related topics:
Updating network information on System Platform on page 21
Verifying network information on System Platform on page 24
Verifying connectivity on page 25
Manually restarting the Avaya Management Service on AWC on page 26
Updating network information on Conferencing Manager on page 27
Updating information on the CRS virtual machine on page 29
Updating network information on System Platform

This is the first task.
Prerequisites
Create new IP addresses and/or hostnames and make a note of them. You require seven IP
addresses for each deployment of Conferencing.
The purpose of this task is to update the IP and hostname details of the Conferencing instance
on System Platform.
1. If you do not have network connectivity to System Platform, which is the case when
you first change from the default IP addresses, you must use a crossover cable from
your services laptop to access the management port, which is Eth1/Gig2:
a. Configure your laptop with the following details:
IP address: 192.11.13.5

Subnet Mask: 255.255.255.252

Gateway IP: 192.11.13.6 (this is the IP address of the management port)
b. On your laptop, navigate to Start > Run and enter cmd in the Open field.
c. At the command line, enter ping 192.11.13.6.
d. Open the PuTTY application and enter the IP address 192.11.13.6.
e. Log in with the username admin and the password admin01.
f. Run the command:
ip_forwarding enable
This command may already be enabled in a default version of Conferencing
Standard Edition.
Now, you should be able to access System Platform directly, using your Web
browser.
2. On the services laptop, open an Internet browser and ensure that there is no proxy
enabled for connections that use a crossover cable.
For example, in Microsoft Internet Explorer, navigate to Tools > Options >
Connections and select LAN Settings. On the Local Area Network (LAN)
Settings dialog, ensure that Use a proxy server for your LAN is not selected.
3. In the Internet browser, enter the IP address of System Platform (Cdom).
This is http://192.168.11.10/
This link redirects to http://<System Platform IP>/webconsole
4. On the Login screen, in the User Id field, enter admin and click Continue.
5. In the Password field, enter admin01 and click Log On.
6. Navigate to Virtual Machine Management and confirm that each of the
Conferencing components are running.
Here is an example of the Virtual Machine Management screen on System
Platform.

7. Navigate to Server Management > Network Configuration and update three

sections, called the General Network Settings, Domain Network Interface, and
Global Template Network Configuration sections, as follows:
a. Scroll to General Network Settings and enter the following information:
Field Information
Default Gateway <The IP address of the Conferencing Manager virtual
machine>
Primary DNS Domain name server
Secondary DNS Optional field. You can leave this field blank
Domain Search List Optional field. You can leave this field blank
Cdom Hostname Hostname
Dom0 Hostname Hostname
b. On the same screen, scroll to the Domain Network Interface section edit the
avpublic IP address field in the Domain-0 sub-section and the avpublic IP
address field in the Console Domain sub-section.
Do not edit the avprivate IP address fields or any other field in the Domain-0
or Console Domain sub-sections.
Here is an example of the Domain Network Interface section on the Network
Configuration screen.

c. On the same screen, scroll to the Global Template Network Configuration

section and update each of the virtual machine IPs and hostnames.
For the Conferencing Manager virtual machine, you must enter the gateway,
netmask, and DNS too. These values must exactly match the values that you
entered in the General Network Settings section, above.
8. Double check all of your these changes in the General Network Settings, Domain
Network Interface and Template Network Configurations sections.
9. Click Save followed by OK.
System Platform updates the IP information and displays an information message
which states that there are Network Configuration changes in progress.... When
the changes are complete, System Platform displays the Login screen.
Next steps
Now you can verify that the changes have saved successfully.
Verifying network information on System Platform

This is the second task.

Prerequisites
Before you verify the IP and hostname details on System Platform, you must update them on
System Platform.
The purpose of this task is to check that the details that you updated in the first task are
successfully saved on the System Platform.
1. Log in to System Platform again.

2. On the Login screen, in the User Id field, enter admin and click Continue.
3. In the Password field, enter admin01 and click Log On.
4. Navigate to Server Management > Network Configuration
5. Check the gateway address listed under the Domain-0 (avpublic) section.
If this is the old gateway address, click Save on the Network Configuration screen.
6. Verify that the gateway address is now updated with the new IP address.
You may need to log out and log back in to System Platform.
Example
Sometimes, the old gateway address still displays on the Network Configuration screen.
You must ensure that when you finish this task, the new gateway address is correctly
displaying.
Next steps
Now you can verify network connectivity.
Verifying connectivity
This is the third task.
At this point, the Conferencing server should be on the network. You can unplug the crossover
cable.
When the System Platform virtual machine is not on the network and you only have access
to it using a crossover cable and a terminal emulator, you can only browse directly to System
Platform and not to any of the other Conferencing components. For example, you cannot
browse to the Conferencing Manager virtual machine.
So now, you need access to a PC or a laptop on the customer network.

Prerequisites
Before you 'ping' the various virtual machines that comprise the Conferencing solution, you
must update the network information on System Platform and verify that the newly updated
information is correctly displaying on System Platform.
The purpose of this task is to ensure that you have network connectivity with each of the
Conferencing virtual machines. Traditionally, this task is also known as pinging the virtual
machines. Pinging ensures that the virtual machines are reachable across the customer's
Internet Protocol (IP) network.
1. Access a PC or a laptop on the customer network.

2. Navigate to Start > Run and enter cmd in the Open field.
3. Enter the following command suing the IP address of one of the Conferencing virtual
machines.
ping <IP address>
The application should display a list of network information relating to the virtual
machine.
4. Repeat these steps for each of the virtual machines that comprise the Conferencing
solution.
Next steps
Now you must manually restart the Avaya Management Service on AWC.
Manually restarting the Avaya Management Service on AWC

This is the fourth task.
Prerequisites
Before you manually restart the Avaya Management Service, you must update the network
information on System Platform and verify that the newly updated information is correctly
displaying on System Platform.
The purpose of this task is to restart the management server on the AWC so that Conferencing
Manager can successfully connect to the AWC and query its status. You can use the remote
desktop feature to access the AWC virtual machine.
1. Click Start > Run.

2. Enter mstsc /console in the Run dialog.

3. In the Computer field, enter the AWC virtual machine IP address.

4. Select the Administrator tab and enter the password gatekeeper.
5. Navigate to Start > Run.
6. Enter services.msc in the Run dialog.
7. On the Services tab, select the services Restart button to restart the Avaya
Management Services service.
Here is an example of the Services tab.
Next steps
Now you can update the IP and hostname information on Conferencing Manager.
Updating network information on Conferencing Manager

This is the fifth task.

Prerequisites
Before you update the network information on Conferencing Manager, you must update it on
System Platform, verify your updates, and manually restart the AWC service.
The purpose of this task is to update the Conferencing Manager with the same changes that
you made on System Platform.
1. Log in to Conferencing Manager.

Conferencing Manager is a Web application. You can access it by entering the
Conferencing Manager IP address in a Web browser as follows:
<Conferencing Manager IP address>/SMGR
Some of the fields on the interface refer to Conferencing Manager as SMGR or
Udom.
By default, the username is admin and the password is admin123. You can change
these username and password settings at any time.
2. Navigate to Elements > Inventory > Manage Elements and change the IP
address information of the virtual machines:
a. Select a virtual machine.
b. Click Edit.
c. Edit the Node and Name fields.
d. Click Commit.
It is important to edit the node. If you delete it and create a new one, Conferencing
Manager deletes all conferences.
3. Log out of Conferencing Manager and then log back in to Conferencing Manager.
4. Navigate to Elements > Conferencing and apply any changes.
It is important to click Apply Changes within a short period of time. When the screen
refreshes, the Apply Changes button is no longer available. The screen refreshes
every 15 seconds. If the Apply Changes button is no longer available, you must
log out of Conferencing Manager and log back in again. Conferencing Manager will
not permit you to make any further updates to Conferencing information until you
commit the changes.
5. Wait for five minutes.
6. Log back in to Conferencing Manager and ensure that all services are powered on
and active. You can check the status of the services by navigating to the Elements >
Conferencing > Services menu.

Next steps
Now you must update the Client Registration Server (CRS) virtual machine with the new
application server (bridge) details.
Updating information on the CRS virtual machine

This is the six task. You are nearly finished now.
Prerequisites
Before you enter the application server (bridge) details on the Client Registration Server (CRS)
Front End, you must update the details on System Platform and Conferencing Manager, verify
your updates, and manually restart the AWC service.
The purpose of this task is the enter the details of the application server in the Client
Registration Server (CRS) Front End. This task ensures that the network information is
consistent across all applications. On the CRS Front End, you must update the Bridge name
field. You can use the remote desktop feature to access the CRS virtual machine.
1. Click Start > Run.

2. Enter mstsc /console in the Run dialog.
3. In the Computer field, enter the CRS virtual machine IP address.
4. Enter a password.
The password is Avaya123.
5. Open the CRS Front End application. The CRS Front End is installed on the CRS
virtual machine, by default.
The CRS Front End Username is Administrator and the Password is
Avaya123.
6. Click System Administration and click the Bridge tab.
7. Update the Name and Bridge DSN fields.
8. Click the Cabinets tab and update the Name field.
9. Navigate to Control Panel > Administrative Tools > Date Sources (ODBC) and
select System DSN followed by iCacheDB<IP address>.
10. Configure iCacheDB<IP address>.
11. Update the Datasource and Server fields.

Next steps
Now you are finished. You have successfully updated the IP and hostname information for your
instance of Conferencing.
Making changes to date and time

The purpose of this task is to update your Conferencing network with a new time and/or date.
1. On System Platform, navigate to Server Management > Date/Time Configuration

and stop the Network Time Protocol (NTPD).
2. Set the timezone and the time, as required and click Set Timezone and Save Date
and Time.
3. Remove the old NTP server.
4. Add a new NTP server.
The server will reboot when applying.
5. Using the remote desktop, connect to the CRS and AWC virtual machines:
a. Click Start > Run.
b. Enter mstsc /console in the Run dialog.
c. In the Computer field, enter the CRS virtual machine IP address for the
connection to the CRS virtual machine.
d. Enter a password.
The password is for the CRS virtual machine is Avaya123.
e. Verify that the date and time is correct.
If it is incorrect, manually change the date and time on the CRS virtual machine.
f. Repeat these steps for the AWC virtual machine.
The password for the AWC virtual machine is gatekeeper.

Chapter 3: Preinstalling Conferencing
Preinstallation steps
You can obtain the Conferencing files in a number of ways. One of these ways is called PLDS.
The other ways are via a DVD or a HTTP shared network location.
Avaya makes the Conferencing files available online, within the Product License and Delivery
System (PLDS) framework. PLDS is comprised of three components: license management,
software entitlement management, and software delivery. PLDS connects to a third party
delivery engine to facilitate the delivery of software.
Note:
Downloading the Conferencing files from the PLDS website can take a number of days.
Avaya recommends the DVD or HTTP methods, rather than the PLDS method.
If you choose to use the PLDS method of obtaining the Conferencing files, there are a number
of preinstallation steps which you must complete before proceeding to the installation steps.
If you choose to obtain the Conferencing files using a DVD or the HTTP method, you do not
need to complete these steps. Instead, you can proceed directly to the installation steps.
Within the PLDS framework, you can locate the files required for your Conferencing installation
by searching under:
• Application Name: Conferencing
• Version: 6.0
The files consist of three .iso images. An ISO image is an archive file of an optical disc in a
format defined by the International Organization for Standardization (ISO). This format is
supported by many software vendors. ISO image files typically have a file extension of .iso.
After you download these three .iso images, you must extract them to a single directory. When
you extract the .iso images, you can access the content within each .iso image.
The content in the .iso images consist of a number of . gz files and some other files such as .ovf
and .sh files. Here are some of the files, as an example:
• smgr-6.0.0.0.XX.gz
• bridge-6.0.0.0.XX.gz

Preinstalling Conferencing
• Conf_Standard_6.0.0.0.XX.ovf
• Conf_Standard_6.0.0.0.XX.mf
There may also be patches on the .iso images.
It is a good idea to read and review the Avaya Aura™ Conferencing Implementation Workbook
prior to commencing your installation.
Related topics:
Conferencing installation on page 39
Avaya Aura Conferencing implementation workbook on page 585
Registering for PLDS
1. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site (https://
plds.avaya.com).
You will be redirected to the Single sign-on (SSO) Web site.
2. Log in to SSO using SSO ID and Password.
You will be redirected to the PLDS registration page.
3. If you are registering:
• as an Avaya Partner, enter the Partner Link ID. If you do not know your Link
ID, send an e-mail to prmadmin@avaya.com.
• as a customer, enter one of the following:
- Company Sold-To
- Ship-To number
- License Authorization Code (LAC)
4. Click Submit.
Avaya will send you the PLDS access confirmation within one business day.

Downloading software in PLDS
Downloading software in PLDS
1. Type http://plds.avaya.com in your Web browser to access the Avaya PLDS

Web site.
2. Enter your Login ID and password to log on to the PLDS Web site.
3. Select Assets from the Home page and select View Downloads.
4. Search for the downloads available using one of the following methods:
• By Actual Download name
• By selecting an Application type from the drop-down list
• By Download type
• By clicking Search Downloads
5. Click the download icon from the appropriate download.
6. When the confirmation box displays, select Click to download your file now.
7. If you receive an error message, click on the message, install Active X, and continue
with the download.
8. When the security warning displays, click Install.
When the install is complete, PLDS displays the downloads again with a checkmark
next to the downloads which have been completed successfully.
Verifying the downloaded ISO image
Verifying the ISO image on a Linux-based computer

Prerequisites
Download any required software from PLDS.
Use this procedure to verify that the md5 checksum of the downloaded ISO image matches
the md5 checksum that is displayed for the ISO image on the PLDS Web site.

Use this procedure if you downloaded ISO images to a Linux-based computer.
1. Enter md5sum filename, where filename is the name of the ISO image. Include
the .iso file extension in the filename.
2. Compare the md5 checksum of the ISO image to be used for installation with the
md5 checksum that is displayed for the ISO image on the PLDS Web site.
3. Ensure that both numbers are the same.
4. If the numbers are different, download the ISO image again and reverify the md5
checksum.
Verifying the ISO image on a Windows-based computer

Prerequisites
Download any required software from PLDS.
Use this procedure to verify that the md5 checksum of the downloaded ISO image matches
the md5 checksum that is displayed for the ISO image on the PLDS Web site.
Use this procedure if you downloaded ISO images to a Windows-computer.
1. Download a tool to compute md5 checksums from one of the following Web sites:
• http://www.md5summer.org/
• http://zero-sys.net/portal/index.php?kat=70
• http://code.kliu.org/hashcheck/
Note:
Avaya has no control over the content published on these external sites. Please
use the content only as reference.
2. Run the tool on the downloaded ISO image and note the md5 checksum.
3. Compare the md5 checksum of the ISO image to be used for installation with the
md5 checksum that is displayed for the ISO image on the PLDS Web site.
4. Ensure that both numbers are the same.
5. If the numbers are different, download the ISO image again and reverify the md5
checksum.

Writing the downloaded software to DVD
Writing the downloaded software to DVD
DVD recommendations
Avaya recommends use of high quality, write-once, blank DVDs, such as Verbatim DVD-R or
DVD+R. Multiple rewrite DVDs are prone to error and should not be used.
When writing the data to the DVD, Avaya recommends a slower write speed of 4X or at a
maximum 8X. Attempting to write to the DVD at higher or the maximum speed rated on the
disc is likely to result in write errors.
Note:
If the software files you want to write on media are less than 680 Mb in size, you can use
a CD instead of a DVD.
Writing the ISO image to DVD

Prerequisites
1. Download any required software from PLDS.

2. Verify that the md5 checksum of the downloaded ISO image matches the md5
checksum that is displayed for the ISO image on the PLDS Web site.
This procedure requires a computer or server that has a DVD writer and software that is
capable of writing ISO images to DVD.
Important:
When the ISO image is being written to the DVD, do not run other resource-intensive
applications on the computer. Any application that uses the hard disk intensively can cause a
buffer underrun or other errors, which can render the DVD useless.
Write the ISO image of the installer to a DVD.

Extracting the content of the ISO images

Prerequisites
Before you extract the contents of the ISO images, you must download the ISO images using
the PLDS framework.
The purpose of this task is to convert the three ISO images into the constituent Conferencing
files. You can perform this task on a machine with the Windows operating system or the Linux
operating system.
Related topics:
Extracting the files to a Linux machine on page 36
Extracting the files to a Windows machine on page 38
Extracting the files to a Linux machine

To extract the files to a Linux machine, you must download an application called PuTTY. PuTTY
is a Linux SSH client that allows you to connect to other machines, giving you a terminal
window.
Prerequisites
the PLDS framework. You must also download PuTTY.
files.
1. Download PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/putty/

download.html.
2. Start PuTTY.
3. On the PuTTY dialog, enter the hostname or IP address of the machine where you
downloaded the .ISO images and click Open.
4. Change the current directory to the directory that contains the three .ISO image files.
5. Specify a target directory, as follows:
export TEMPLATE_DEST_DIR=/Conf_Standard_6.0.0.0.X
This is the directory to which theConferencing files will extract.

Extracting the content of the ISO images
There must be 10.5 GB of free disk space available. You can check if there is
sufficient space in the target directory using the following command:
df -hP ${TEMPLATE_DEST_DIR} | awk '{print $4}'
6. Specify a directory to contain DVD mount points, as follows:
export MNTDIR=/
7. Create the mount points, as follows:
mkdir -p ${MNTDIR}/DVD1
8. Mount the ISOs to those mount points, as follows:
mount Conf_Standard_6.0.0.0.X_DVD1.iso ${MNTDIR}/DVD1 -t
iso9660 -o loop
iso9660 -o loop
iso9660 -o loop
9. Create the destination directory, as follows:
mkdir -p ${TEMPLATE_DEST_DIR}
10. Copy the contents of the DVDs to destination directory, as follows:
/bin/cp ${MNTDIR}/DVD*/data/* ${TEMPLATE_DEST_DIR}
11. Un-mount mount points, as follows:and remove the directories:
umount ${MNTDIR}/DVD1
12. Remove the directories, as follows:
rmdir ${MNTDIR}/DVD1
13. Run a checksum on contents of ${TEMPLATE_DEST_DIR}, as follows:
cksum ${TEMPLATE_DEST_DIR}/*
The list of Conferencing files should be displayed. For a full, up-to-date list of these
files, see the Avaya Aura™ Conferencing Release Notes, which are available from
support.avaya.com.
Next steps
Now, you can begin the steps to install Conferencing using the HTTP method.

Related topics:
Installing Conferencing using HTTP on page 44
Extracting the files to a Windows machine

To extract the files to a Windows machine, you must download an application called IsoBuster.
IsoBuster is an application which allows you to explore the files within an ISO image.
Prerequisites
the PLDS framework. You must also download IsoBuster.
files.
1. Download IsoBuster from http://www.isobuster.com/isobusterdownload.php.

2. Start IsoBuster.
IsoBuster behaves in a similar way to the Windows Explorer.
3. In IsoBuster, navigate to the directory which contains the three .ISO images.
4. Select the first .ISO image.
Within the .ISO format, the Conferencing files are located in the Data directory.
5. Extract the Conferencing files to an accessible folder.
6. Select the second .ISO, repeat the steps, select the third .ISO and repeat the steps.
Ensure that you extract all three .ISO files to a single destination directory.
Next steps
Now, you can begin the steps to install Conferencing using the HTTP method.
Related topics:

Chapter 4: Installing Conferencing
Avaya Aura™ Conferencing is an integrated multimedia conferencing solution, consisting of
five virtual machines, which you must install in your customer network. The five virtual
machines are:
• A central management and configuration console
to manage and configure the other four virtual machines. Some of the fields on the
interface refer to Conferencing Manager as SMGR. It is a good idea to keep this point in
mind while you are navigating through the Conferencing installation pages.
This server also has conference management and reporting functions.
Within the Conferencing environment, this is called Web Portal. This server also has
conference management and reporting functions.
Before you install Conferencing, you must install and configure Avaya Aura™ System Platform.
System Platform is a virtual server that allows solution templates, or applications, to co-
reside on a single server. You use System Platform to obtain and install the Conferencing
template.
It is a good idea to read and review the Avaya Aura™ Conferencing Implementation Workbook
prior to commencing your installation. The Avaya Aura™ Conferencing Implementation
Workbook is available here as an appendix. Avaya also recommends completing the Avaya
Aura™ Conferencing Implementation 6.0 Standard Edition training course, which is training
course number ATI00102VEN on https://www.avaya-learning.com/.
Conferencing consists of all the virtual machine elements that are necessary for successful
conferencing. The virtual machine files are defined in a file called an open virtualization format

Installing Conferencing
file. This file has the file extension .ovf. You can install the Conferencing installation files using
one of the following methods:
• DVDs
• HTTP
Important:
Before you install the Conferencing files, you must ensure that the timezone setting on
System Platform is the one that you require in your Conferencing deployment. If it is not,
Avaya recommends changing the timezone setting so that it reflects the time setting that
you require for Conferencing. There are two formats in the System Platform timezone list.
There are short forms of timezones, such as ETC/GMT and there are long forms of
timezones, such as Europe/Dublin. Always use the long form of the timezone.
DVD installation
Avaya ships Conferencing on a series of DVDs. Typically, three DVDs are required for each
deployment. The DVDs contain the Conferencing files, the operating systems, and the folders
and files that are necessary for successful operation of the Conferencing solution. To install
Conferencing, you must follow a procedure to copy the contents of each of the DVDs to the
System Platform server machine and install the files from the System Platform server machine.
An automatic script installs the files into the correct folder on the System Platform server
machine.
Note:
The DVD method is a method of obtaining and installing the Conferencing files.
HTTP installation
If you copy the Conferencing installation files to a local Web server, you can install them using
the HTTP method. As with the DVD option, you must install the files using the System Platform
server machine.
Note:
The HTTP method is a method of installing the Conferencing files. Before you use the HTTP
method, you must first obtain the files, using another method, such as PLDS or on DVDs.
Avaya makes the Conferencing files available online, within the PLDS framework. PLDS is
comprised of three components: license management, software entitlement management, and
software delivery. PLDS connects to a third party delivery engine to facilitate the delivery of
software. Downloading the files from the PLDS website can take a number of days. This time
delay is due to the large size of the Conferencing template. The time delay varies depending
on your connection to the Internet. Avaya recommends the DVD method, rather than the PLDS
method. If you are using the PLDS method, download the files in advance of your customer
site visit. Once you have the files from PLDS, you can save them to a shared location on the
customer network and use the HTTP installation steps from that point. If you choose to obtain
the files using PLDS, you must complete some preinstallation steps relating to PLDS
registration. Using PLDS, you download the files in an .ISO format and then extract the .ISO
files to a single directory.

Note:
The PLDS method is a method of obtaining the Conferencing files. After you obtain the files
from PLDS, you must install them using another method, such as HTTP or DVD.
Summary table
Tasks Options available to you

How do I obtain the • You can obtain the files online using the PLDS method at
Conferencing template https://plds.avaya.com/.
files?
• Alternatively, you can receive delivery of the Conferencing
template on DVDs.
How do I install the • You can copy the files to a shared location on the customer
Conferencing template? network and use the HTTP method of installation.
• Alternatively, you can bring DVDs to the customer site and use
the DVD method.
All installation methods use the System Platform server machine. You require System Platform
in order to install the Conferencing template.
Related topics:
Preinstallation steps on page 31
Extracting the content of the ISO images on page 36
Installing Conferencing using DVDs on page 41
Architecture overview on page 586
Installing Conferencing using DVDs

Prerequisites
Before you install Conferencing using DVDs, you must:
• Install and configure System Platform.
The System Platform documentation is available from support.avaya.com.
• Ensure that System Platform is patched as required in the Avaya Aura™ Conferencing
Release Notes, which are available from support.avaya.com.
• Ensure that the timezone setting on System Platform is the one that you require in your
Conferencing deployment.
• In the customer network, ensure that the ports on the LAN switch are configured to match
the settings on the Conferencing server. The LAN switch must be 100Mb/s or higher and
both connected ports should be set to full duplex, with autonegotiation (autoneg) enabled.

These settings ensure that the customer network can establish a link to the Conferencing
application server.
• Download an application called PuTTY from http://www.chiark.greenend.org.uk/
~sgtatham/putty/download.html. PuTTY is a Windows SSH client that allows you to
access the Windows virtual machines (the CRS and AWC virtual machines) by way of
System Platform (Dom0), giving you a terminal window.
The purpose of these steps is to install the Conferencing files. These files contain all the virtual
machine elements that are necessary for Conferencing. There are five virtual machine
elements in the package.
1. Log in to the System Platform server machine using a Command Prompt window.
The System Platform server machine is sometimes called Domain 0 or Dom0. The
System Platform server machine also has a virtual machine called Cdom (previously
called Udom). The IP address of Cdom refers to a Web console, which enables you
to manage System Platform. For the purposes of this step, you must log in to the
Command Prompt window and the PuTTY application.
a. On the PuTTY dialog, enter the hostname or IP address of the System Platform
machine.
b. Enter the username admin and the password admin01.
c. Run the command su root to increase the access permissions.
The password is root01.
Note:
These usernames and passwords are the System Platform default
usernames and passwords. Avaya configures these values when they ship
a new System Platform. It is likely that an administrator has updated this
information following the installation of System Platform in your site.
2. Put the first DVD into the CD Rom drive of the System Platform server machine.
3. Mount the DVD by running the command mount -r /dev/cdrom /media.
4. Run the following script, setup_install_data, to ensure that the template folders
install in the correct location on the System Platform server machine.
This script is located in script/media. When you run setup_install_data, the
script displays a series of prompts. Follow the prompts as they instruct you to insert
the second and third DVDs. Conferencing has three DVDs in total.
5. Log in to System Platform by entering the System Platform virtual machine IP
address in a Web browser. The System Platform documentation is available from
support.avaya.com.
By default, the User ID is admin and the password is admin01.
6. On System Platform, navigate to Virtual Machine Management > Solution
Template.

7. On the Search Local and Remote Template screen, select SP Server from the
Install Template From list.
8. Click Search and locate the Conf_Standard_6.x.x.x.x.ovf file. This is the Open
Virtualization Format file that contains the templates. There should only be a
single .ovf file in the directory.
This file is located in /vsp-template/Conf_Standard_6.x.x.x.x/.
9. Highlight the file and click Select.
10. On the Template Details screen, review the installation requirements and click
Install.
You can see more details about each virtual machine by clicking the CRS, Web
Portal, AWC, and Bridge buttons. System Platform displays the detailed
information at the bottom of the screen.
11. On the Template Network Configuration screen, select an ethernet port from the
Dedicated NIC drop-down list and click Save.
Conferencing uses two NICs. It uses ethernet port 0 (which is port 1) for the CRS,
Web Portal, and AWC virtual machines and one of the remaining ethernet ports for
the application server. The application server is also called the bridge. Ensure that
the ethernet port that you select is physically connected to a switch with 100Mb/s
or higher. The bridge link defaults to 100 Mb/s. The corresponding switch port must
be configured for auto negotiation and must be connected and have carrier (NIC
LED illuminated) prior to the installation of the template.
If you are deleting a template and re-installing it, System Platform may display an
error message referring to dedicated NIC connectivity. If you see this error message,
reboot System Platform and start the Conferencing installation again.
12. On the following screen, enter an IP address and a fully qualified domain name
(FQDN) for the bridge, CRS, AWC and Web Portal virtual machines. You must
overwrite the existing text, such as localhost.localdomain. The purpose of
this text is to provide a hint about the required syntax.
A fully qualified domain name (FQDN) is sometimes referred to as an absolute
domain name, It is a domain name that specifies its exact location in the tree
hierarchy of the Domain Name System (DNS). For example, given a device with a
local hostname myhost and a parent domain name example.com, the fully
qualified domain name is written as myhost.example.com. This fully qualified
domain name therefore uniquely identifies the host — while there may be many
resources in the world called myhost, there is only one myhost.example.com.
13. For the SMGR (Conferencing Manager) virtual machine, separate the hostname
and the domain name into the SMGR Host Name and SMGR Domain fields,
respectively. In other words, do not enter the FQDN in the SMGR Host Name field.
14. For the SMGR virtual machine, you must also add the gateway, netmask, DNS, and
search string. The network administrator in the customer site should provide this
information. You do not require this information for the CRS, bridge, AWC, and Web

Portal virtual machines because these machines obtain these settings from System
Platform.
15. Click Install.
The Template Installation screen displays the progress of the installation. The
installation can take up to 90 minutes. When it is complete, System Platform
displays the phrase Template Installation Completed Successfully on the
Template Installation screen.
Next steps
You can now enter the product keys for the Windows license on the CRS and the AWC virtual
machines. These two virtual machines use the Windows operating system. The bridge, the
Conferencing Manager, and Web Portal virtual machines use the Linux operating system and
do not require licensing or have an open source licensing agreement.
Once the installation is complete, you can manage the virtual machines using the System
Platform interface, by navigating to Virtual Machine Management > Manage. In addition, you
can change the networking information of the virtual machines by navigating to Server
Management > Network Configuration.
Related topics:
Windows licensing on page 45
Installing Conferencing using HTTP

Prerequisites
Before you install Conferencing using HTTP, you must:
• Obtain the Conferencing files using one of the other installation methods, such as DVD
or PLDS.
• Copy the Conferencing files to a local Web server.
• Complete the prerequisites listed as part of the DVD installation.
The purpose of these steps is to install the Conferencing files. These files contain all the virtual
machine elements that are necessary for Conferencing. There are five virtual machine
elements in the package.
Note:
In some instances, if you are connecting to the installation files via a proxy server, you are
more likely to experience download difficulties. Potential download difficulties include the
cancellation of the installation, timeouts, and the reaching of the maximum data transfer
limit. If any issues occur, it is a good idea to switch off the proxy. As a matter of good practise,
you should only switch off the proxy if the HTTP server is within the local network.

Windows licensing

support.avaya.com.
2. On System Platform, navigate to Virtual Machine Management > Solution
Template.
3. On the Search Local and Remote Template screen, select HTTP from the Install
Template From list.
4. Enter the Web server address where you copied the Conferencing files.
5. Click Search.
Next steps
You can now select the .ovf template file, as described as part of the DVD installation. You can
follow the DVD installation steps from step 8 onwards.
Related topics:
Installing Conferencing using DVDs on page 41
Windows licensing
System Platform is a virtual server that allows solution templates, or applications, to co-
reside on a single server. After you install the Conferencing files, System Platform hosts the
five virtual machines that comprise the Conferencing solution. These five virtual machines are:
• Client Registration Server (CRS)
• Avaya Web Conferencing (AWC)
• Web Portal
• Bridge (The bridge is the application server)
• Conferencing Manager (Conferencing Manager is a console or central management
system for configuring Conferencing)
The CRS and the AWC use the Windows operating system. The bridge, Web Portal, and
Conferencing Manager use the Linux operation system. You must comply with the licensing
requirements of the Windows operating system before you continue with the remainder of the
installation tasks. The Linux operating system does not require licensing.
At this stage of the installation, there is no IP connectivity between the host (System Platform)
and the CRS and AWC virtual machines. This lack of IP connectivity is because the Windows
operating systems have not completed their installations. As a result, you must use a special

method, called in-band communication, to access these virtual machines in order to enter the
Windows product keys. Avaya recommends using an X Windows server, such as Xming and
a terminal emulator application, such as PuTTY to access the virtual machines through System
Platform. After you enter the license keys, the Windows operating system reboots. At this point,
you must also adjust the time and date on the CRS and AWC virtual machines.
Xming and PuTTY
Xming and PuTTY are freely available as standalone open source applications.
PuTTY is a Windows SSH client that allows you to access the Windows virtual machines (the
CRS and AWC virtual machines) by way of System Platform (Dom0), giving you a terminal
window.
Xming is an X Server for Windows. An X server enables you to access the graphical user
interface of the Windows virtual machines.
Location of the license keys
The license keys are usually displayed on a sticker attached to the Windows installation CD
or attached to the Conferencing server hardware.
Anti-virus policy
After you enter the license keys for the Windows operating system, Avaya recommends
installing anti-virus software in accordance with the current policy in the deployment site.
Windows updates
After you enter the license keys for the Windows operating system, Avaya recommends
complying with the Windows updates policy in the deployment site.
Related topics:
Entering Windows keys using Xming and PuTTY on page 46
Setting the time after entering Windows keys on page 48
Entering Windows keys using Xming and PuTTY

Prerequisites
If you are using a Windows operating system on the computer that you are using to connect
to the CRS and AWC virtual machines, you must install Xming and PuTTY . If you are running a
Linux or a Macintosh operating system, you do not need to install Xming and PuTTY. By default,
the Linux and Macintosh operating systems have utilities that perform like Xming and PuTTY.
The purpose of this task is to enter the license keys for the Windows operating system on the
CRS and AWC virtual machines. These steps describe how to connect to CRS and AWC when
you are running a Windows operating system. If you are running a Linux or a Macintosh
operating system, you must use their generic utilities to perform the PuTTY and Xming
functions.

Windows licensing
1. If you are using a Windows operating system on your computer, download Xming
from http://sourceforge.net/projects/xming/ and download PuTTY from http://
www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
When downloading Xming, It is a good idea to select the option to create a shortcut
to Xming on your desktop.
There are many different PuTTY downloads listed. Typically, your deployment
requires the putty.exe file.
2. Right-click on the Xming shortcut on your desktop and select Properties.
3. Replace all the text in the Target field with this text: xming.exe :0 -clipboard
-multiwindow –ac
4. Start Xming and PuTTY.
The taskbar displays an icon to show that Xming is running.
5. On the PuTTY dialog, enter the hostname or IP address of the System Platform
machine.
The System Platform is displayed as Dom0 in the System Platform graphic user
interface.
6. On the PuTTY left pane, ensure that Connection > SSH > X11 > Enable X11
Forwarding is selected.
7. Click Open.
8. Log in to System Platform using the username admin and the password admin01.
9. Run the command su root to increase the PuTTY access permissions.
Note:
These usernames and passwords are the System Platform default usernames
and passwords. Avaya configures these values when they ship a new System
Platform. It is likely that an administrator has updated this information following
the installation of System Platform in your site.
10. Run the command xm vncviewer awc to access the AWC virtual machine.
This command displays a Windows dialog in which you can enter the Windows
license keys.
If the VNC Viewer utility does not launch:
a. Enter the command export DISPLAY=<IP address of the current
desktop machine>:0.0 and press the Enter key.
b. Run the command xm vncviewer awc again.
11. Enter the Windows license keys using the regular Windows steps.
12. Run the command xm vncviewer crs to access the CRS virtual machine.

This command displays a Windows dialog in which you can enter the Windows
license keys.
13. Enter the Windows license keys using the regular Windows steps.
After you enter the keys and restart Conferencing, the Windows virtual machines
are available from that point onwards.
You can display the Log-in dialog by pressing the F8 key. The F8 key, when pressed
within the PuTTY dialog, behaves like the Windows command CTRL+ALT
+DELETE. The password for the log in on the CRS virtual machine is Avaya123.
The password for the log in on the AWC virtual machine is gatekeeper. The
passwords are case-sensitive.
If you want to return to the System Platform Dom0 virtual machine, close the
Windows dialog or enter the following command in the PuTTY dialog:
<CTRL> ]
In other words, press the CTRL key and enter the square right close bracket symbol.
Next steps
Now you must adjust the time and date settings on the CRS and AWC virtual machines.
Related topics:
Entering Windows keys using VNC Viewer
System Manager/Conferencing Manager and virtual machines on page 54
Setting the time after entering Windows keys

After you enter the Windows keys on the CRS and AWC virtual machines, you must adjust the
time and date settings.
Prerequisites
Before you configure the time and date on the CRS and AWC virtual machines, you must enter
the Windows license keys
The purpose of this task is to manually adjust the time and date settings on the CRS and AWC
virtual machines to align them with the other Conferencing components.
1. Access the CRS virtual machine. You can use the remote desktop feature to access
the virtual machine.

Patch management
c. In the Computer field, enter the CRS virtual machine IP address.

d. Enter the username administrator and the password Avaya123.
2. Navigate to Start > Settings > Control Panel > Date and Time.
3. Click Change date and time... and set the time and date to align with the time and
date that you configured on System Platform
4. Repeat these steps for the AWC virtual machine.
The username for the AWC virtual machine is administrator and the password
is gatekeeper.
Next steps
Now it is a good idea to install any patches that are required. Avaya recommends that you
ensure that you have IP connectivity to each of the virtual machines at this point. IP connectivity
is essential for the deployment of patches.
You can install anti-virus and Windows update software in accordance with the current policy
in the deployment site. You must install any anti-virus or update software on the C drive. Avaya
uses the D drive for the Conferencing software. If you perform the backup and restore function
for the Conferencing software, the process may remove any non-Conferencing software from
the D drive.
Patch management
Patch management is the process of obtaining a fix and applying it to your software. From time
to time, after Avaya releases software, Avaya releases a fix for a known issue in the software.
You can use the patch management process to obtain the fix and update your software. Avaya
deploys patches using Avaya Aura™ System Platform. System Platform is a virtual server that
allows solution templates, or applications, to co-reside on a single server. You use System
Platform to obtain and install the Conferencing files.
Just like the other virtual machines that make up the Conferencing solution, System Platform
is a virtual machine. The System Platform server machine is sometimes called Domain 0 or
Dom0. The System Platform server machine also has a virtual machine called Cdom. The IP
address of Cdom refers to a Web console, which enables you to manage System Platform.
Just like Conferencing, you can obtain fixes using a number of methods:
• DVDs
• PLDS
Avaya recommends obtaining the patches from PLDS because PLDS always lists the latest
versions of each patch. A DVD could contain an older version of a patch.

In this documentation, these patches are referred to as regular patches.

Exception
There is one exception to the System Platform process of deploying patches. This single
exception involves the patches for Conferencing Manager. You must obtain the Conferencing
Manager patches from your Avaya Support Representative or from the PLDS site at https://
plds.avaya.com/. You must then use PuTTY and WinSCP to install the patches. WinSCP is an
application which enables you to securely copy files over a network.
In this documentation, these patches are referred to as Conferencing Manager patches.
The process of rollback is similar to the undo feature. Rollback means returning to the state
prior to the installation of the patch. Conferencing Manager patches do not support rollback.
Some regular patches support rollback.
Note:
Avaya recommends that you ensure that you have IP connectivity between System Platform
and each of the virtual machines at this point, before you install any patches. You can verify
connectivity using a ping command. Ping is a computer network administration utility used
to test whether a particular host is reachable across an Internet Protocol (IP) network and
to measure the round-trip time for packets sent from the local host to a destination computer.
On the System Platform interface, each of the virtual machines is listed along with the status
of each virtual machine. The status 'running' means that the operating system on that virtual
machine is running. It does not mean that the Conferencing applications on each virtual
machine are running. Furthermore, it does not mean that there is IP connectivity to each of
those virtual machines.
Related topics:
Installing and activating Conferencing Manager patches on page 50
Installing and activating regular patches on page 52
Installing and activating Conferencing Manager patches

Prerequisites
Before you install any Conferencing patches, you must install Conferencing.
You must also install an application which enables you to transfer files securely, such as the
WinSCP application, which you can download from http://winscp.net/eng/download.php.
WinSCP is an application which enables you to securely copy files over a network. If you are
running a Linux or a Macintosh operating system, you do not need to install WinSCP. By default,
the Linux and Macintosh operating systems have utilities that perform like WinSCP and PuTTY.
It is a good idea to read the corresponding release notes for the patch. The Avaya Aura™
Conferencing Release Notes are available on support.avaya.com.
The purpose of this task is to obtain and apply any fixes which are currently available for your
Conferencing software. These steps are for Conferencing Manager patches. Recall that within
the Conferencing environment, Conferencing Manager is sometimes known as SMGR. These
steps describe how to install the patches when you are running a Windows operating system. If

Patch management
you are running a Linux or a Macintosh operating system, you must use their generic utilities
to perform the WinSCP and PuTTY functions.
1. Open a PuTTY session.

2. On the PuTTY dialog, enter the hostname or IP address of the Conferencing
Manager virtual machine.
3. Log into Conferencing Manager using the username root and the password
root01.
4. Obtain the Conferencing Manager patch file and copy it to the desktop of the
machine you are currently using.
Typically, this patch file is bundled with the Conferencing installation files.
Alternatively, you can obtain the file using the PLDS framework. You can also obtain
this file from your Avaya Support Representative. Your representative may also be
able to provide you with an online link to the file. This is more likely if you are a
business partner.
The file extension is .sh and it is bundled within a zipped file (.zip).
5. Open WinSCP and log into the Conferencing Manager virtual machine using the
username root and the password root01.
WinSCP provides access to your current machine in the left pane and provides
access to the Conferencing Manager virtual machine in the right pane.
6. Copy the patch file from your desktop and paste it into the left pane.
WinSCP pastes the file into the / directory on the Conferencing Manager virtual
machine.
7. Unzip the patch file.
8. Maximize your PuTTY window.
9. Enter the following command:
sh runInstaller.sh
This command installs the patch. There is no need to stop and restart the jboss
service.
Example
The patch file has the file extension .sh. For example, runInstaller.sh.
Next steps
Now you can install the regular patches, which are distributed using System Platform.

Installing and activating regular patches

Prerequisites
Before you install any Conferencing patches, you must install Conferencing and license the
Windows operating system on the AWC and CRS virtual machines.
You must also verify that you have connectivity between System Platform and the other virtual
machines that comprise the Conferencing solution.
Avaya recommends that you install the AWC patch before you install the other patches. You
must install the AWC patch before you use AWC. The AWC patch does not install correctly
once the AWC CPU usage reaches 100%.
The purpose of this step is to obtain and apply any patches which are currently available for
your Conferencing software. There may be multiple, separate patches.

address in a Web browser.
2. Navigate to Virtual Machine ManagementManage, select the AWC virtual
machine, and click Reboot.
3. Wait for approximately two minutes.
4. Verify that the AWC service has started:
a. Log in to Conferencing Manager.
Conferencing Manager is a Web application. You can access it using a Web
browser
By default, the username is admin and the password is admin123.
b. Navigate to Elements > Conferencing > Services.
c. Verify that the AWC service is active.
If the AWC service is not active, follow the steps to manually start the AWC
service.
5. Press the ALT+CTRL+DELETE keys and click the Task Manager button to display
the Task Manager.
6. Ensure that CPU usage is below 100%. If it is at 100%, reboot the AWC virtual
machine again.
7. Navigate to Server Management > Patch Management > Download/Upload.
8. Select the method you are using to obtain the fixes from the Choose Media list. For
example, if you have a DVD which contains the fix, select SP CD/DVD.

Patch management
9. Click Search or Browser.

The button name changes depending on the media selection. If you select HTTP,
you can also configure a proxy.
System Platform searches for any files with the supported file extensions. If System
Platform locates a supported file, it displays the filename.
10. Select the file and then click Upload.
System Platform copies the patch file and makes it available for installation in your
deployment. System Platform displays the patch detail.
At the time of release, the AWC patch is called AWC patch 256.
11. Click Install to install the patch.
System Platform copies the file to the appropriate virtual machine. For example, if
it is a CRS patch, System Platform copies the patch to the CRS virtual machine.
12. Click Activate to apply the patch.
Note:
You may have to click Refesh to display the correct state.
After you install the AWC patch, you must repeat these steps for each patch file.
As an aside, if the patch supports rollback, you can click Deactivate to roll it back.
At any time, you can use System Platform to navigate to Server Management >
Patch Management > Manage. The Patch List page lists all the patches that are
installed or activated in your deployment. It may take approximately one minute
before the patch is displayed in the Patch List.
Next steps
You can now add the Conferencing virtual machine elements to Conferencing Manager.
Conferencing Manager is a central management console, which enables you to configure the
other virtual machines, and in doing so, configure many aspects of your Conferencing
deployment. This is a required step to register the Conferencing virtual machines with
Conferencing Manager.
The process of rollback is similar to the undo feature. Rollback means returning to the state
prior to the installation of the patch. Some patches support rollback and some others do not
support rollback. The release notes associated with each patch indicate which patches support
rollback and which do not. If a patch supports rollback, you can rollback by selecting the
Deactivate button on the patch management screen. For more details on rollback support, it
is a good idea to read the release notes. The Avaya Aura™ Conferencing Release Notes are
available on support.avaya.com.
Conferencing Manager patches do not support rollback.
Related topics:
Manually starting AWC on page 244

System Manager/Conferencing Manager and virtual

machines
After you install the Conferencing virtual machines on the System Platform and enter the
Windows license keys, you must register the virtual machines with the Conferencing Manager.
This step involves making the Conferencing Manager virtual machine aware of the four virtual
machines that consist the Conferencing solution. The Conferencing Manager virtual machine
enables the management and configuration of the Conferencing solution.
These four virtual machines are:
• Avaya Web Conferencing (AWC)
• Web Portal
• Bridge (The bridge is the application server)
A point of clarification: The term 'bridge' in this document refers to the Conferencing bridge.
Avaya also implements a System Platform bridge. The System Platform bridge is entirely
separate and there is no reference to it in this document. For more information on the System
Platform bridge, see the System Platform documentation, which is available from
support.avaya.com. The Conferencing application terminates telephone calls and mixes audio
on the Conferencing bridge
The Conferencing Manager virtual machine is not in this list because it is the console or central
management system for configuring the four virtual machines that consist the Conferencing
solution.
If you have Avaya Aura™ System Manager 6.0
If the customer has Avaya Aura™ System Manager installed already, they can use System
Manager instead of Conferencing Manager. If they have System Manager, they can ignore
Conferencing Manager. Conferencing Manager behaves in a similar way to System Manager
but only contains a subset of the features contained in System Manager. Some of the fields
on the Conferencing Manager interface refer to Conferencing Manager as SMGR. This is
because Conferencing Manager is a stripped down version of System Manager that Avaya
has designed to allow single box deployment for a customer who does not have Avaya Aura™
System Manager.
Related topics:
Adding virtual machines to Conferencing Manager on page 55

CRS virtual machine connectivity
Adding virtual machines to Conferencing Manager

The purpose of this step is to make the Conferencing Manager aware of the four virtual
machines in the Conferencing network.
1. Log in to Conferencing Manager by entering the Conferencing Manager virtual

machine IP address in a Web browser, as follows:
http://<Conferencing Manager IP address>/SMGR
Some of the fields on the interface refer to Conferencing Manager as SMGR.
2. Navigate to Elements > Inventory > Manage Elements .
3. Click New to add the first of the four virtual machines:
a. On the New Entities Instance screen, select Conferencing 6.0 from the Type
drop-down list.
b. In the Application area, in the Name field, enter a name for the virtual machine,
such as CRS. You can also add a description, if you like.
c. In the Node field, enter the IP address of the virtual machine.
d. Click Commit.
4. Repeat these steps for each of the four virtual machines.
When you add each new virtual machine, the Conferencing Manager performs a
query on the virtual machine entity to identify the virtual machine type. Using this
response, Conferencing Manager can distinguish between the various virtual
machines. For example, it can differentiate the application server virtual machine
from the CRS virtual machine.
Next steps
You can now connect the CRS, Web Portal, and AWC virtual machines to the bridge virtual
machine. This step is necessary to ensure connectivity between all the Conferencing virtual
machines on the network. It is one of the final tasks in the installation process.
CRS virtual machine connectivity

After you install the Conferencing template on the System Platform, activate the Windows
license keys, and add the virtual machines to the Conferencing Manager, you must create

connections between the virtual machines. Specifically, you must assign a bridge, Avaya Web
Conferencing (AWC), and Web Portal virtual machine to the CRS virtual machine.
This step involves configuring the CRS virtual machine to communicate with the other
Conferencing virtual machines. This association means that when operators and moderators
book conferences, the bridge allocates resources and delivers the conferencing experience.
This is one of the final stages in the installation of the Conferencing solution.
Related topics:
Assigning virtual machines to the CRS on page 56
Importing the customer model at the customer site on page 403
Assigning virtual machines to the CRS

The purpose of this step is to establish connectivity between the virtual machines that you have
added. This step ensures connectivity between all the virtual machine elements that comprise
the Conferencing solution.

Conferencing Manager is a Web application. You can access it using a Web browser
2. Navigate to Elements > Conferencing > Client Registration.
Conferencing Manager displays the IP address of the available CRS virtual
machine.
3. Select the CRS virtual machine.
4. Click Configure.
5. On the Client Registration Server configuration sub-pages screen, click General.
6. In the Components area, select the application server virtual machine in the
Available Conferencing Servers panel and move it to the Assigned
Conferencing Servers panel.
7. Select the Avaya Web Conferencing (AWC) virtual machine IP address in the Web
Conferencing Server list.
8. Select the Web Portal virtual machine in the Available Web Application servers
panel and move it to the Assigned Web Application servers panel.
9. Click Save.
10. Click Apply Changes.
11. Click Apply Changes again to restart Conferencing.

A license for Conferencing
Next steps
At this point, you have installed Conferencing Manager, licensed the Windows operating
system, added the virtual machines to the Conferencing Manager and assigned the virtual
machines to the CRS virtual machine. You are now ready to connect Conferencing to your
network.
You may want to initiate a backup of your configurations at this point. You can initiate a backup
using System Platform.
Note:
If Avaya has made a fix available for your Conferencing software, you may have to install it
before you connect Conferencing to your network. You can install fixes using the patch
management process.
Related topics:
CRS virtual machine connectivity on page 55
A license for Conferencing

Every instance of Conferencing ships from the factory with a license that covers a grace period
of 30 days. After this period, you must formally license the solution. You can obtain a valid
license from the Avaya Product License and Delivery System (PLDS) Web site at https://
plds.avaya.com/submitRegistration.htm. The license is in the format of an .XML file. You must
save it to your desktop computer.
As an aside, licenses are also required for:
• The Windows operating system on the Avaya Web Conferencing (AWC) virtual machine.
• The Windows operating system on the Client Registration Server (CRS) virtual machine.
• The Avaya Web Conferencing (AWC) application, running on the Avaya Web
Conferencing (AWC) virtual machine.
The instructions for applying these licenses are also included here.
Related topics:
Applying a Conferencing license on page 57
Applying a Conferencing license

Every instance of Conferencing ships from the factory with a license that covers a grace period
of 30 days. After this period, you must formally license the solution.

Prerequisites
Before you apply a license to your Conferencing server, you must obtain the license from the
PLDS Web site.
The purpose of this task is to apply a license to the Conferencing solution.

2. Navigate to Licenses > Install License.
3. At the Enter License Path field, click Browse and locate the license file which you
obtained from the PLDS Web site and saved to your desktop.
4. Click Open followed by Install to install the license.
Conferencing Manager installs the license.
Example
The solution is licensed against the MAC address of the Conferencing Manager. The unique
index for the license is the LAN MAC address of the Conferencing Manager. You can view
the MAC address using System Platform.
Next steps
Now you can configure the Conferencing solution to suit the customer requirements.
Troubleshooting installation
The purpose of this task is to provide some suggestions for overcoming any installation issues.
• Ensure that there are no download size constraints implemented in the network. The
Conferencing installation files are very large. Issues in relation to download size are
more likely to occur if you are downloading the Conferencing installation files via a proxy
server.
• If you experience difficulties downloading the Conferencing installation files via a local
Web server (referred to in this document as the HTTP method), use an alternative
method, such as the DVD method.

Troubleshooting installation
• Consider the impact of the firewall rules in your deployment. You may have to customize
the Conferencing firewall rules to accommodate the requirements of your deployment.
a. Log in to the application server (bridge) virtual machine using PuTTY.
b. Enter the name craft and the password craft01.
c. Use the sroot command to change from craft to sroot access.
The sroot command is:
su sroot
d. Navigate to /root2/etc/firewall/conf/mx_firewall.rules.
e. Enter the following command to stop a service:
service iptables stop
f. Make a back-up copy of the mx_firewall.rules file.
g. Edit the mx_firewall.rules file to suit your deployment.
h. Enter the following command to restart the service:
service iptables restart
• To find out about license information, you can follow these steps:
Enter the following line in the Address field of a Web browser:
http://<Application server virtual machine>:18080/info
The application server returns the license status, for example:
edition=Standard Edition
audio-ports=300
license-status=LICENSE_GRACE
version=6.0.0.0.1
productId=bridge
• To query the status of the operating system on the management servlet running on
each of the virtual machines that comprise the Conferencing solution:
On a Web browser, enter the following: http://<IP address of virtual
machine>:18080/status.
• If you are deleting a template and re-installing it, System Platform may display an error
message referring to dedicated NIC connectivity. If you see this error message, reboot
System Platform and start the Conferencing installation again.
• To enter the Windows license keys on the CRS and AWC virtual machines, you require
a utility called VNC Viewer. If the VNC Viewer utility does not launch:

a. Enter the command export DISPLAY=<IP address of the current

desktop machine>:0.0 and press the Enter key.
b. Run the command xm vncviewer awc again.
Related topics:
Location of additional logs of interest on page 109

Chapter 5: Connecting Conferencing to
your network
Overview of supported deployments

You can connect Conferencing to your existing network in a number of ways.
• You can directly connect the Conferencing infrastructure to a single Avaya Aura™
Communication Manager.
• You can also connect the Conferencing infrastructure to Communication Manager or the
Communications Server 1000 (CS1K) by way of Avaya Aura™ Session Manager.
• Alternatively, you can directly connect the Conferencing infrastructure to a single CS1K.
• Additionally, if your network is a circuit-switched telephone network, you can connect
Conferencing to an Audiocodes Mediant media gateway. The Audiocodes gateway is a
Voice over Internet Protocol (VoIP) media gateway, which acts as a translation unit
between a Public Switched Telephone Network (PSTN) telecommunications network and
the Conferencing VoIP telecommunications network. The media gateway performs the
conversion from Time Division Multiplexing (TDM) to VoIP. This conversion enables your
deployment to use the Session Initiation Protocol (SIP). SIP is a signaling protocol, widely
used for controlling multimedia communication sessions such as voice and video calls
over Internet Protocol (IP).
Note:
The requirements of your network infrastructure may differ from those described here.
Use these instructions as a general guide.
The Conferencing solution also supports a number of other integrations and several hardware
options from other vendors. For more information on these deployments, contact your Avaya
Support Representative.
The main configuration settings that are relevant to connect Conferencing to the network are
the SIP settings.
The Avaya DevConnect Web site contains a large number of Solutions and Interoperability
Lab (SIL) application notes at: https://devconnect.avaya.com/public/dyn/d_dyn.jsp?fn=314,
such as The Application Notes for configuring Avaya Aura™ Communication Manager 6.0 and
Avaya Aura™ Session Manager 6.0 to allow interoperability between Avaya Aura™

Connecting Conferencing to your network
Conferencing Standard Edition 6.0 using SIP Trunks. This Web site is an excellent resource
for deployment information.
Related topics:
Conferencing and Communication Manager on page 62
Conferencing and Session Manager on page 63
Conferencing and Audiocodes on page 63
Conferencing and Communications Server 1000E (CS1K) on page 64
Conferencing and Communication Manager

You can connect Conferencing to a single Communication Manager. A Conferencing and
Communication Manager integration routes incoming calls using a series of hierarchical tables.
When a caller makes a telephone call to Communication Manager, the Communication
Manager server analyses a dial plan table to see if the telephone number pattern matches an
entry. If it finds a match, it reads the corresponding routing instructions. As an example, these
instructions could direct the server to analyze a second table, called the Uniform Dial Plan
(UDP) table. Again, it analyses the UDP table to see if the pattern matches an entry. If it finds a
match, it reads the corresponding routing instructions. As an example, these instructions could
direct the server to analyze a third table, called the Automatic Alternate Routing (AAR) table.
If it finds a match, it reads the corresponding trunk information and will route the call through
that trunk. As a last step, the server analyses a route pattern table to see if there are any further
instructions before it places the call into the Conferencing server. Instructions could include
adding or removing some digits from the telephone number string. These steps through each of
the hierarchical tables illustrates the possibilities and flexibility of Communication Manager.
You can configure the fields to process the telephone number according to the specific
requirements of your deployment.
Signalling group
Typically, the signalling board on Communication Manager is a Control Local Area Network
(CLAN) board. If your deployment uses a single CLAN board to connect your SIP trunk from
Communication Manager to Conferencing, there is a single point of failure if this is the primary
connection. A more resilient option would be to configure multiple CLAN boards to connect to
Conferencing. For example, in a configuration with two CLAN boards, Conferencing sends a
SIP option message to both CLAN boards. If both CLAN boards are operational, Conferencing
connects the call to the first CLAN board. If the first CLAN board fails, it responds with a service
unavailable message when Conferencing sends a SIP option message. If Conferencing
receives a service unavailable message, it sends a SIP invite message to the second CLAN
board and connects the call. Similarly, there are mechanisms in place in Communication
Manager which enable it to detect if the Conferencing server has failed. For example, using
Look Ahead Routing (LAR), you can configure a routing preference for additional connection
attempts if Communication Manager cannot connect to the Conferencing server on the first
attempt.

Overview of supported deployments
Conferencing and Session Manager

You can connect the Conferencing infrastructure to Communication Manager or the
Communications Server 1000 (CS1K) by way of Avaya Aura™Session Manager. There are
detailed application notes on these deployments on the Avaya DevConnect Website.
Related topics:
What is Session Manager? on page 63
What is Session Manager?

Companies typically have a diverse set of communications products within their corporate
intranet that cannot communicate with each other. A standard signaling protocol is required to
make these products work together. Avaya has adopted the Session Initiation Protocol (SIP)
as the signaling protocol for communication.
Avaya Aura™Session Manager is a SIP routing and integration tool and the core component
within the Avaya Aura™ Enterprise Edition solution. It integrates all the SIP entities across the
entire enterprise network within a company. Session Manager offers a new perspective on
enterprise communication where individual locations are no longer managed as separate units
within the enterprise. Each location, branch, or application is part of the overall enterprise,
managed as an enterprise, and seen as an enterprise. Session Manager offers:
• a simplified network-wide feature deployment
• centralized routing, SIP trunking, and user profiles
• cost-effective scalability (from small to very large deployments)
• high availability with geographic redundancy
• a secure environment that conforms to specific SIP standards and practices
Conferencing and Audiocodes

The AudioCodes gateway is a Voice over Internet Protocol (VoIP) media gateway, which acts
as a translation unit between a Public Switched Telephone Network (PSTN)
telecommunications network and the Conferencing VoIP telecommunications network. The
media gateway performs the conversion from Time Division Multiplexing (TDM) to VoIP.
There are detailed application notes on this deployment on the Avaya DevConnect Website.

Conferencing and Communications Server 1000E (CS1K)

The Avaya CS1K is formally known as the Nortel CS1K. There are detailed application notes
on this deployment on the Avaya DevConnect Website.
SIP settings
The main configuration settings that are relevant to connecting Conferencing to the network
are the SIP settings. The Session Initiation Protocol (SIP) is a signaling protocol, widely used
for controlling multimedia communication sessions such as voice and video calls over Internet
Protocol (IP). Within a SIP communications framework, the method of transmission is
configurable.
The SIP communications across your network must use one of the following methods of
transmission:
• Transport Layer Security (TLS)
• Transmission Control Protocol (TCP)
• User Datagram Protocol (UDP)
Related topics:
SIP listener URI on page 64
Response contact on page 65
Session refresh timer on page 65
Min session refresh timer allowed on page 66
Configuring SIP on page 66
SIP listener URI

SIP Listener URI is a string that specifies the address of the Conferencing application server
and the transport method for connecting with the application server. You can configure the
TCP, UDP, or TLS method of transmission, using the following syntax:
SIP Listener URI=sip:Digit String@Conferencing application server IP:5060;transport=tcp
SIP Listener URI=sip:Digit String@Conferencing application server IP:5060;transport=udp
SIP Listener URI=sips:Digit String@Conferencing application server IP:5061;transport=tls
The digit string is simply an identifying number for the Conferencing application server. You
can enter any value but it defaults to 6000.

SIP settings
In the case of a TLS configuration, you should enter the port number 5061 instead of 5060.
Also, you should add an s to sip at the beginning of the string.
Note:
The transport protocol that you select for the SIP Listener URI field must match the transport
protocol that you select for the Response Contact field.
Response contact
Response Contact is also a string that specifies the address of the Conferencing application
server and the transport method for connecting with the application server. You can configure
the TCP, UDP, or TLS method of transmission, using the following syntax:
Response Contact=sip:Digit String@Conferencing application server IP:5060;transport=tcp
Response Contact=sip:Digit String@Conferencing application server IP:5060;transport=udp
Response Contact=sips:Digit String@Conferencing application server IP:5061;transport=tls
As with the SIP Listener URI field, the digit string is simply an identifying number for the
Conferencing application server. You can enter any value but it defaults to 6000.
In the case of a TLS configuration, you should enter the port number 5061 instead of 5060.
Also, you should add an s to sip at the beginning of the string.
Note:
The transport protocol that you select for the Response Contact field must match the
transport protocol that you select for the SIP Listener URI field.
Session refresh timer

Session Refresh Timer corresponds to a field in the Communication Manager Signaling Group
screen called Session Establishment Timer (min).
• If you are connecting Conferencing to Communication Manager, Avaya recommends a
value of 1800. Avaya recommends this value because it optimizes communications
between Conferencing and Communication Manager.
• If you are connecting Conferencing to an Audiocodes Mediant media gateway, you can
configure a value of 900.
Your deployment may have specific requirements and you may want to set different values.

Min session refresh timer allowed

Min Session Refresh Timer Allowed corresponds to a field in the Communication Manager
Trunk Group screen called Preferred Minimum Session Refresh Interval (sec).
• If you are connecting Conferencing to Communication Manager, Avaya recommends a
value of 100. Avaya recommends this value because it optimizes communications
between Conferencing and Communication Manager.
• If you are connecting Conferencing to an Audiocodes Mediant media gateway, you can
configure a value of 900.
Your deployment may have specific requirements and you may want to set different values.
Configuring SIP
Prerequisites
Before you configure the SIP settings, you must install Conferencing and configure a media
gateway.
The purpose of this task is to configure the transport protocols for communications from the
Conferencing server.
1. Navigate to Elements > Conferencing > Media.

2. Select the IP address of the application server and click Configure.
If you have multiple application servers that you want to configure to the same value,
you can select all of them, and click Configure.
3. Click Configuration.
4. In the SIP panel, configure the settings as required in your deployment.
5. Click Save.
Next steps
Now you can configure the telephone numbers.

Chapter 6: Configuring telephone numbers
Call routing
Call routing describes a number of mechanisms which Conferencing uses to provide
conference participants with a customized conferencing experience, depending on the
telephone number they used to access the conference. Conferencing experience consists of
audio messages, languages, and conference call flow.
Call routing also refers to the way Conferencing interprets the telephone numbers that
participants use to dial a conference and the telephone numbers that participants use to dial
out from a conference to another potential participant.
To configure call routing, you must customize a number of settings in your deployment of
Conferencing.
Related topics:
Call routing on page 136
Obtaining conference telephone numbers
Your customer should provide the telephone numbers which they wish to use for
conferencing. These telephone numbers should be dialed number identification
service (DNIS) numbers. In some regions, DNIS numbers are called direct dial inward
(DDI) numbers.
Example
For example, if you have 100 licensed ports, you could allocate the range 2710600 to
2710699 to Conferencing.
Next steps
Now you can configure the number of digits to match.

Configuring telephone numbers
Number of digits to match

The Number Of Digits To Match field enables you to configure the number of digits that the
Conferencing server selects from the full telephone number or DNIS/DDI. This number must
not exceed the actual number of DNIS/DDI digits received from the network. The Conferencing
server assumes receipt of a complete DNIS/DDI number when this limit is reached, ignoring
any extra digits sent. The default value for this parameter is 4. The maximum value is 16.
It is worth noting that you can configure CDR reports to display the complete DNIS/DDI.
Related topics:
Configuring the number of digits to match on page 68
Configuring the number of digits to match

Prerequisites
Before you configure the number of digits to match, you must install Conferencing.
The purpose of this task is to specify the number of digits which Conferencing selects from a
full telephone number.
1. Navigate to Elements > Conferencing > Audio Conferencing.

3. Click Call Routing.
4. In the Number of digits to match field, enter the number of digits that you want to
select from a full telephone number.
5. Click Save.
Next steps
Now you can configure the Conferencing call branding table.
Related topics:
Call branding on page 69

Call branding
Call branding
Call branding overview
Call branding is a feature that enables you to configure the participants’ conference experience,
based on the telephone number that they use to dial Conferencing.
When conference participants dial the Conferencing server to enter their conference, the
Conferencing server plays them a series of audio prompts. Avaya provides customers with the
flexibility to configure different telephone numbers that will all dial into the same server.
Customers can link customized audio prompts with each of these different telephone numbers.
By default, Avaya configures Conferencing with eight languages.
Customers can also link different call flows with each of these different telephone numbers.
These telephone numbers are called Direct Dial Inward (DDIs) or Dialed Number Identification
Service (DNISs). A call flow refers to the sequential experience of the conference participant
as they dial into a conference or listen back to a conference recording.
Avaya also allows customers to limit the length of the DDI which Conferencing processes. For
example, if customers use the telephone numbers 1234001, 1234002, 1234003, 1234004, and
so on, you can configure Conferencing to read only the digits that vary. Conferencing does not
need to process all digits. The number of digits that you configure to be processed by
Conferencing is called the Number of digits to match.
The configuration of processing preferences such as limiting the number of digits to match and
linking various call flows is called call branding. Call branding occurs when Conferencing
collects the digits that the participant dials, matches them to an entry in a call branding table,
then processes the call in accordance with the instructions that you have configured in that
call branding table.
The call branding table enables you to assign a specific annunciator message, line name,
company name, system function, and audio prompt sets. You must ensure that the final entry in
the call branding table is the wild card entry, which is ????. If Conferencing collects a DNIS
that is not listed in the table, it processes the call based on the instructions that you have
configured in this entry. By default, Avaya ships Conferencing with this entry already configured
in the call branding table.
When a caller first uses a DNIS, Conferencing checks the call branding table. Conferencing
then routes the call in accordance with the configuration settings for that DNIS. After this initial
check, Conferencing caches the call branding routing instructions in the shared memory
database. Caching the instructions means that Conferencing avoids having to check the call
branding table each time.
Variable Description
DDI Specifies the digit pattern of the DNIS. In certain regions, this is
known as Direct Dial Inward (DDIs). You can specify the number
of digits that Conferencing collects using the Number of digits
to match field.

Name An optional line name that you can associate with the DNIS. The
name can contain up to 20 characters. Conferencing displays
this name to the operator and also displays it in call and
conference detail records (CDRs and CODRS). This optional
line name is especially useful for calls destined for the Enter
Queue because it helps operators to provide custom greetings.
The default is blank. If you leave this field as blank and you have
configured SCAN or FLEX in the func field, Conferencing uses
this field to display the last passcode that the participant enters.
The Standard Edition of Conferencing does not support Bridge
Talk. Bridge Talk is the Avaya application that enables operators
to monitor live conferences and perform actions on live
conferences, such as attended conferences. If your customer
has their own application which provides a similar function, you
can configure Conferencing to use this external application. You
can do this using the Avaya Conferencing Provider Application
Programming Interface (ACP API). For more information about
configuring Conferencing to operate with external applications,
contact your Avaya Support Representative. The Standard
Edition of Conferencing supports Bridge Talk.
Organization Name An optional company name to associate with the DNIS. The
name can contain up to 20 characters. Conferencing displays
this name to the operator and also displays it in call and
conference detail records (CDRs and CODRS). The default is
blank.
Reservation Group The Standard Edition of Conferencing does not support this
feature.
Message Number The annunciator message, listed by number, that Conferencing
plays to the participant before it processes the call in
accordance with the instructions that you have configured for
this entry.
Message Set Number The number of the audio prompt set, from 0 to 20, that
Conferencing uses to play the annunciator messages.
Conferencing supports up to 21 languages.
Use Conf Message Set Specifies if Conferencing plays the audio prompt set from the
language that the moderator or operator has assigned to the
conference or if it plays the audio prompt set from the language
that you have configured, using the call branding table, for this
entry. The valid values are Y and N.
On entry Specifies how Conferencing processes a call that matches the
incoming digits. The valid values are:
Direct to enter queue
Conferencing places the call in the Enter Queue. The Enter
Queue is where participants await the attention of an operator.

Call branding
This is the most common choice for a conference in Attended
Mode.
Direct to conference
Conferencing places the call directly in a conference without a
request for a passcode. This a common choice for unattended
calls. This function does not support flex flow conferences. If
you require the DNIS to dial a flex flow conference, configure
the On entry value to Flex call flow.
Scan call flow
Conferencing plays an annunciator message to prompt the
participant to enter the passcode for the conference. This a
common choice for unattended calls.
Disconnect
Conferencing ends the call.
Auto virtual link line
This field is reserved for a multisite conference. Multisite refers
to a network of Conference Reservation Servers (CRSs)
located in different geographical locations.
Flex call flow
Conferencing identifies the call as a flexflow call. A flexflow
conference is a specific type of on-demand conference. In
flexflow conferences, all call routing is based on the conferee
passcode. In addition to the conferee passcode, moderators
enter a moderator passcode, which grants access to a
moderator-specific menu.
Playback
Conferencing routes the call to the repository of conference
recordings. Conferencing prompts the user for a conference
reference number and a passcode and plays the appropriate
conference recording, if it is available.
On failure Specifies how Conferencing deals with failed actions that the
participant makes, such as entering an incorrect passcode.
Conferencing places the participant in the enter queue (Direct
to enter queue) or ends the call (Disconnect). This field is not
valid if you set the On entry drop-down list to Direct to enter
queue, Disconnect, or Direct to conference. If you select
Default, Conferencing uses the failure instructions that you
have configured using the Invalid Code parameter. The Invalid
Code parameter is a global parameter. Conferencing applies
the Invalid Code value to all conferences unless you configure
a value using the call branding table. A call branding value of
Direct to enter queue or Disconnect overrides the Invalid
Code value. On the other hand, a call branding value of Default
will apply the Invalid Code values.
Note:
Another value, outside of call branding, also exerts an influence
over the functionality of this variable. That value is called

Security Code Error3. For the call branding value to operate
successfully, you must set Security Code Error3 to Tone. If you
set it to any value other than Tone, Conferencing uses the
Invalid Code value.
Conference Room Start An optional starting Bridge Talk conference room assigned to
this DNIS. This setting along with conference room end sets a
range of rooms. When callers call the DNIS, Conferencing
places them into the conference room. Operators, using Bridge
Talk, can see the callers in the Conference Room dialog.
Customers can use this feature to assign responsibility for
specific conference rooms to specific operators. Customers can
also use this feature, along with Name and Organization Name
to ensure that operators customize the conferencing experience
for callers.
can configure Conferencing to use this external application.
Conference Room End An optional ending Bridge Talk conference room assigned to
this DNIS. This setting along with conference room start sets a
range of rooms.
can configure Conferencing to use this external application.
Conference Security An optional setting that is only used with the Direct to
Code conference value from the On entry drop-down list. When you
configure the Direct to conference call flow from the On entry
drop-down list., Conferencing places the call directly in a
conference. Using this Conference Security Code field, you
can enter a conference code for use with a Direct to conference
call flow.
For example, consider a deployment with the following values:
• DNIS: 1234
• On entry: Direct to conference
• Conference Code: 5678
When a caller dials in with DNIS 1234, Conferencing places
them in a conference with the passcode 5678. Using this
feature, it is possible to have any number of Direct to conference
call branding entries putting callers into the same conference.
If you do not configure the Conference Security Code field,
Conferencing places a caller who dials in with DNIS 1234 into

Call branding
a conference that has the passcode 1234. This passcode can
be a moderator passcode, a conferee passcode, or a co-chair
passcode, so at most, Conferencing can route three Direct to
conference call branding entries to a given conference. The
Conference Security Code field eliminates this restriction.
This feature is sometimes called Unlimited DDIs
DDI phones
The DDI phones functionality is optional. DDI Phones configuration is not required for the
successful operation of call branding. The DDI Phones table enables you to associate DDI
telephone numbers with the call branding entry. For example, these telephone numbers are
displayed to conference participants on e-mail invitations.
Reservation groups
The reservation groups functionality is optional. Reservation groups configuration is not
required for the successful operation of call branding. The reservation groups feature enables
participants to use a single conference passcode to enter a number of different conferences.
Reservation groups are not supported in the Standard Edition of Conferencing. They are
supported in the Enterprise Edition of Conferencing.
Related topics:
Configuring the number of digits to match on page 68
Adding a call branding entry on page 73
Editing a call branding entry on page 75
Deleting a call branding entry on page 75
System language on page 283
Participant experience on page 284
Configuring audio messages for your system on page 296
Configuring the playback call flow on page 309
Adding a call branding entry

Prerequisites
Before you add a call branding entry, you must install Conferencing and connect Conferencing
to your network.
The purpose of this task is to create an association between a particular DDI and a
Conferencing call flow. A call flow refers to the sequential experience of the conference
participant as they dial into a conference or listen back to a conference recording.


2. If necessary, select the IP address of the application server and click Configure.
4. Click Call Branding to display the Call Branding Entry table and click Add.
5. Enter a call branding entry using a DDI from your deployment.
6. Click Save.
You can move the entry up and down the call branding table. Conferencing reads
the table from top to bottom.
Example
For example, you can configure specific conference call flow for each department in
customer site, such as Sales, Finance, and Marketing. You can also configure Conferencing
to route any callers who incorrectly enter the conference telephone number to a help queue,
so that they can speak to an operator. Operators can see a display of the help queue using
the Bridge Talk application or a similar external application. The help queue is also known
as the enter queue.
This example uses the telephone number range from 2710600 to 2710699. In this example
range, only the final two digits vary. All the other digits are the same. This example also
assumes that the Number of digits to match has the value of 4. So, Conferencing reads
the final four digits of an incoming telephone number.
• For the wildcard entry, ensure that ???? is in the DDI field and DDI Unknown is in the
Name field. Select Direct to enter queue from the On entry drop-down list.
• For the Sales department, enter a DDI such as 0601 in the DDI field and Sales
Department in the Name field. Select Scan call flow from the On entry drop-down list.
• For the Finance department, enter a DDI such as 0602 in the DDI field and Finance
• For the Marketing department, enter a DDI such as 0603 in the DDI field and
Marketing Department in the Name field. Select Scan call flow from the On entry
drop-down list.
In this example, Conferencing routes callers who dial any number in the range 2710604 to
2710699 into the help queue. Conferencing routes callers who dial 2710601, 2710602, or
2710603 to a customized conference call flow for a particular department. The reason for
allocating separate call flows in this example is to enable operators to record a customized
welcome message for each department. This flexibility is useful in enterprise or service
provider deployments. To use this feature, you must configure also the Message Number
field in the call branding table. Conferencing ships with 2000 slots for audio messages but
reserves the first 460 (approximately) for the required messages. Operators using Bridge
Talk could record a message into one of the remaining slots. You must enter this slot number
in the Message Number field.
By default, the On failure drop-down list is set to Direct to enter queue. This means that
if a caller dials the correct telephone number but subsequently enters an incorrect

Call branding
conference passcode a configurable number of times, Conferencing routes them to the help
queue to be intercepted by an operator.
Editing a call branding entry

Prerequisites
Before you edit a call branding entry, you must add the call branding entry.
The purpose of this task is to change or update call branding information.

4. Click Call Branding to display the Call Branding Entry table.
5. Select a call branding entry and click Edit.
6. Update the details as required.
7. Click Save.
Deleting a call branding entry

Prerequisites
Before you delete a call branding entry, you must add the call branding entry. You cannot delete
the wildcard entry.
The purpose of this task is to remove a call branding entry from the Conferencing server.


5. Select a call branding entry and click Delete.

6. Click Save.
DDI phones
The DDI Phones functionality is optional. DDI Phones configuration is not required for the
successful operation of call branding.
The DDI Phones table enables you to associate DDIs and telephone numbers in the following
ways:
• You can associate a single DDI with multiple telephone numbers. For example, you can
link a single DDI with an internal telephone number and an external number.
• You can associate a single telephone number with multiple DDIs. For example, you can
specify a single phone number that has multiple DDIs used to access several
conferences.
When you add a DDI phone, you must enter the location of the telephone number and a
description. The location is significant because telephone numbers can be location-specific to
ensure more economical rates.
Related topics:
Adding DDI phones on page 76
Deleting DDI phones on page 77
Adding DDI phones

Prerequisites
Before you add a DDI phone, you must install Conferencing.
The purpose of this task is add a telephone number with the aim of creating an association
between DDIs and telephone numbers. Once you add a DDI phone, you cannot edit the details.
To update the details, you must delete the DDI phone and add a new one.

4. Follow the steps to add or edit a call branding entry.

Configuration of Conferencing to handle a number it does not recognize
5. In the DDI Phones section, click Add.

6. Enter the details of a telephone number from your deployment.
7. Click Save.
Next steps
Now you can configure Conferencing to handle a number it does not recognize.
Deleting DDI phones

Prerequisites
Before you delete a DDI phone, you must add the DDI phone.
The purpose of this task is to remove the DDI phone from the Conferencing server.

5. Select the call branding entry with the DDI phone that you want to delete and click
Edit.
6. Select the DDI phone and click Delete.
7. Click Save.
Configuration of Conferencing to handle a number it does

not recognize
By default, Conferencing attempts to make a partial match when it receives fewer digits that it
expects.
In addition, you can configure Conferencing to handle DNIS numbers that it does not recognize.
You can do this by adding a wildcard entry to the Call Branding table. You may already have

added a wildcard entry when you added the regular call branding entries for your telephone
number range. If not, it is a good idea to do it now.
Note:
By default, Avaya ships Conferencing with this wildcard entry already added.
These features enable Conferencing to respond to incorrect or unexpected telephone
numbers.
When Conferencing receives collects too few DNIS/DDI digits. It attempts a partial match in
right to left order. For example, if Conferencing only collects the digits 127 when four digits are
required, it matches these digits to the first entry in the Call Branding table having 127 as its
right most three digits. Conferencing searches the Call Branding table in ascending order until it
finds the first match. This feature, which is enabled by default, works in tandem with the
wildcard entry in the Call Branding table. Using the wildcard feature and the partial match
feature, you can configure how Conferencing handles a telephone number that it does not
recognize. Using these features, Conferencing can handle a partial match or no match at all.
Related topics:
Adding a wildcard on page 78
Adding a wildcard
Avaya recommends adding an entry to the call branding table to deal with situations when
participants dial a telephone number that the Conferencing server does not recognize. You
may already have added a wildcard entry when you added the regular call branding entries for
your telephone number range. If not, it is a good idea to do it now.
Note:
By default, Avaya ships Conferencing with this wildcard entry already added. You cannot
delete the wildcard. These steps are for your information only.
Prerequisites
Before you add a wildcard, you must install Conferencing.
The purpose of this task is to specify how Conferencing deals with a DNIS that is not listed
in the call branding table.

3. Click Call Routing and follow the steps for adding a call branding entry.
4. In the DDI field, enter ???? and select a response from the On entry drop-down list.

Pattern matching
For example, select Direct to enter queue to ensure that Conferencing routes the
caller to the help queue.
Next steps
Now you can configure pattern matching.
Pattern matching
Within the Conferencing environment, pattern matching is necessary because callers use
telephone numbers but Conferencing uses URIs. To enable successful conferencing, you must
match telephone number patterns to URIs. The pattern matching files are called URIToTelnum
and TelnumtoURI.
Simply speaking, the URIToTelnum file states that the Conferencing application server should
recognize a given URI and identify this URI’s corresponding DNIS. The call branding file states
that the Conferencing application server should recognize this DNIS and handle the call in a
certain way, for example, by routing the call into a conference call flow or a conference playback
call flow. Similarly, the TelnumtoURI file states that the Conferencing application server should
recognize a DNIS entered by a moderator during a conference and dial out using a
corresponding URI.
Conference participants dial telephone numbers to access Conferencing. Similarly,
participants dial telephone numbers once they are in a conference to dial out to other potential
participants. These two types of calls are called incoming calls and outgoing calls.
Conferencing changes each telephone number to a URI. A URI consists of a string of
characters used to identify or name a resource on the Internet.Conferencing contains two files,
which translate telephone numbers to URIs. One file converts incoming URIs to telephone
numbers and the other file converts outgoing telephone numbers to URIs. Essentially, these
files act as a conversion between a traditional form of telephony in the form of DNIS/DDI
numbers and the more modern, SIP form of transmission. Before you deploy Conferencing,
you must configure these files.
The files, TelnumToURI and URIToTelnum, use the same format. They contain three columns of
information. The last column contains a comment or textual information about the first and
middle columns. The first column provides a pattern match for the input value. Conferencing
searches this column in order. This column supports wild cards.
Name Symbol Description

Asterisk * Match zero or more characters. This symbol matches
any character, not just digits.
Question Mark ? Match a single character in an exact postion.
In the files, TelnumToURI and URIToTelnum, the middle column provides the translation for the
entry in the first column. This column supports string substitutions using the syntax, $n, where n

is an integer. Essentially, this file functions by looking for a pattern in the left column and
produces an output based on the middle column.
The middle column uses this syntax:
• $0 substitutes the full input string.
• $1 substitutes the first wild card.
• $n substitutes the nth wild card.
The system considers ??? a single wild card, but treats *?* as three distinct wild cards. It is
also worth noting that while * matches any character, not just digits, it does not match empty
strings at the beginning. For example:
*sip:* matches <sip:xxxx@ but does not match sip:xxxx@
So to alleviate this issue, Avaya normally add one extra entry for the empty character:
*sip:*
sip:*
Here are some example wildcard substitutions:
Input Pattern Match Translation Output

51234 5* sip: sip:
$1@10.221.10.100 1234@110.221.10.1
00
9123456 ?*?6 sip: sip:
$2@10.221.10.100 1234@110.221.10.1
00
1234 * sip: sip:
$0@10.221.10.100 1234@110.221.10.1
00
Related topics:
Tel num to URI on page 80
URI to tel num on page 81
Configuring patterns for dialing in on page 83
Configuring patterns for dialing out on page 83
Tel num to URI

When they are in a conference, participants can dial out to other potential participants. To
initiate a dial out, participants typically enter a DTMF pattern, such as *1. As an aside,
customers can choose to disable the dialout feature in their deployment.
The TelnumToUri.tab file is stored in the /usr/ipcb/config directory. Generally this file starts with
one or more comments. Like most text files, comments begin with the hash (#) character.

Pattern matching
Following the comments, the file has one or more lines containing data. Each data line contains
three pieces of information: TelnumPattern, TelnumConversion, and Comment.
It is unlikely that you should ever have to access this file in its raw state on the application
server. You can now configure these settings using the Conferencing Manager interface.
Entry Description
Telnum This entry is the telephone number that participants dial. This
entry may contain wildcards for pattern matching. For example,
93???? matches any telephone number that begins with the
digits 9 and 3, such as 931234, 939999, or 938765.
URI Conferencing replaces the Telnum with this entry when it dials
out to the new caller. This entry always begins with the
characters sip: followed by the dial out number, the @ character,
and ends with the IP address of the media gateway or proxy.
For example: sip:6352@10.221.10.111. The characters
$1 in this column replace the first wildcard matched from the
Telnum column.
Comment Any text that provides some information about the pattern.
Some examples are: bridge, media gateway, or proxy server.
This field must not have any spaces so many people use
underbars to separate the words.
Avaya recommends adding an entry to handle situations where a participant does not enter a
dial out telephone number. To configure this row, enter an asterisk * in the Telnum column.
This configuration operates for all Conferencing deployments, with the exception of
deployments that include Avaya Web Portal and Avaya Audio Console. If your deployment
includes the Avaya Web Portal and Avaya Audio Console applications, you must include an
entry for these applications in the TelnumToUri.tab file. During the operation of Avaya Web
Portal and Avaya Audio Console, the Conferencing application server makes an outgoing
telephone call to the Conferencing Web server. From the participants’ perspective, this call
occurs behind the scenes. To ensure that Conferencing can make this outgoing call, you must
include a row that uses the asterisk * symbol, using the following syntax:
* sip:1234@<Web Server IP address>modAPIoperator
URI to tel num

Uri To Telnum maps work in tandem with call branding to brand the customer experience for
callers who dial into a conference or who dial a conference recording.
Simply speaking, the UriToTelNum.tab file states that the Conferencing application server
should recognize a given URI and identify this URI’s corresponding DNIS. The call branding
file states that Conferencing application server should recognize this DNIS and handle the call
in a certain way, for example, by routing the call into a conference callflow or a conference
playback callflow. Similarly, the TelnumToUri.tab states that the Conferencing application

server should recognize a DNIS entered by a moderator during a conference and dial out using
a corresponding URI.
The UriToTelNum.tab file is stored in the /usr/ipcb/config directory. The UriToTelNum.tab file is
similar in structure to the TelnumToUri.tab file. Each data line contains three pieces of
information: URI, Telnum Conversion, and Comment.
It is unlikely that you should ever have to access this file in its raw state on the application
server. You can now configure these settings using the Conferencing Manager interface.
Entry Description
URI The IP address of the telephone line that the participant dialed.
This entry always begins with the characters sip: followed by
the dial-in number, the @ character, and ends with the IP
address of the media gateway or proxy. Since Conferencing
may not recognize every dial-in telephone number, this entry
usually contains wildcards for pattern matching. For example,
*@10.221.10.11, matches any call delivered via that IP
address.
Telnum Conversion Conferencing replaces the TelnumPattern with this entry and
then routes it to the corresponding call flow.
Comment Any text that provides some information about the pattern.
Some examples are: bridge, media gateway, or proxy server.
This field must not have any spaces so many people use
underbars to separate the words.
As with the TelnumToUri.tab file, Avaya recommends adding an entry to handle situations
where Conferencing receives a call from a URI that it is not defined in the file. To configure this
row, enter an asterisk *, followed by @, and then another asterisk * in the URI column. In
addition, you can add rows for each operator. These rows are optional and are for situations
where you want to be able to dial into a specific operator. If you add these rows, you can ensure
that operators can dial into the Conferencing application server. Use the following syntax for
these lines:
op<DNIS>x<operator index>@<ip address>
The operator index is the identity number associated with an operator, such as operator 1,
operator 2, and so on, rather than the Logical Channel Number (LCN) of the operator. The call
handler does not perform any processing on the DNIS number at this stage, but it is important to
enter a numeric value at this point in the syntax. You can configure a dial in for other channels in
the same way. The other channels are the link, record/playback, and music channels. For
example, for a music channel:
mu<DNIS>x<operator index>@<ip address>
For the link channel, use LK, for the record/playback channel, use RP.

Pattern matching
Configuring patterns for dialing in

Prerequisites
Before you configure patterns for dialing in, you must configure the Conferencing call branding
table.
The purpose of this task is to create a pattern to enable Conferencing to recognize a URI.

4. Click Edit at the URI to Telnum field.
5. Click Add to display a new empty row.
6. Enter the pattern details that you require.
Conferencing adds the pattern to the URI to Telnum file.
Configuring patterns for dialing out

Prerequisites
Before you configure patterns for dialing out, you must configure the Conferencing call
branding table.
The purpose of this task is to create a pattern to enable conference moderators to dial out to
other potential participants. As an aside, you can choose to disable this feature in your
deployment.

4. Click Edit at the Telnum to URI field.
5. Click Add to display a new empty row.
6. Enter the pattern details that you require.

Conferencing adds the pattern to the Telnum to URI file.
Example
In this example, Conferencing is connected to a Communication Manager with the IP address
123.45.678.9:
Telnum: *
URI : sips:$0@123.45.678.9:5061;transport=tls
Comment: CallsThroughCM
This instruction uses the wildcard to represent any telephone number. The instruction states
that Conferencing should direct any attempt to dial out to other telephone numbers from
inside a conference to Communication Manager. Communication Manager will then handle
the call from that point onwards. It also refers to the fact that communications between
Communication Manager and Conferencing should use the TLS method of transmission.
The method of transmission must be consistent with the method entered in the SIP Listener
URI and Response Contact fields.
Just as in the case of Communication Manager, if Conferencing is connected to another
device, such as an Audiocodes or a CS1K gateway, you must enter the IP address of the
Audiocodes or CS1K in the URI field, in place of the Communication Manager IP address.
Next steps
Now you can verify your installation.

Chapter 7: Verifying your installation
Verification
It is a good idea, at this stage, to verify the installation and configuration steps that you have
taken so far.
Verification involves testing connectivity to each of the virtual machines that comprise the
Conferencing solution. Verification also involves making a test call and creating a test
conference.
Application server
The application server is also known as the bridge.
You can verify connectivity to the bridge by placing a test call to the Conferencing bridge. In
order to place a test call, Avaya recommends using Avaya Aura™Avaya one-X Communicator.
You can download Avaya one-X Communicator here: https://support.avaya.com/css /
appmanager/css/support/Downloads/P0516#wlp_Downloads_Page
Related topics:
Key features on page 85
Placing a call on page 87
Key features
Basic feature
The Avaya one-X Communicator offer includes the following Basic features:
• Desktop access to all your communication tools from a single, intuitive user interface
• Telephony features similar to Avaya one-X Desktop Edition and Avaya IP Softphone
• Click-to-Dial from Microsoft Office Communicator via Avaya Aura™ Application
Enablement Services

Verifying your installation
• Click-to-Dial from Microsoft Office Communicator or IBM Sametime Connect via native
Avaya one-X Communicator integration
• Telephony integration with Microsoft Office Communicator or IBM Sametime Connect
• Desktop video for H.323 softphones for face-to-face communications to streamline
decision making and reduce travel expenses
• Click-to-Dial capability from Microsoft Internet Explorer and Mozilla Firefox
• Click-to-Dial capability from Microsoft Outlook Contacts
• Wipe-to-dial (clipboard dialing) capability from any application
• Contact lookup of Microsoft Outlook or IBM Lotus Notes contact from the Avaya one-X
Communicator user interface
• Contact management tools that help you find contact information quickly
• Telephone share control that provides telephony functionality from a server to your
desktop
• Enhanced login preferences: Automatic login and Autostart
• Emergency call handling (not supported with SIP)
• Docking and undocking of Dialpad and Bridge Conferencing windows
• Expanded video options: Full screen option, Always on top feature, and Screen Saver
and Monitor Power Saving feature
• Customization of the emergency call-handling disclaimer, the Avaya one-X logo, and the
title on the Login and Welcome windows
Unified Communications features
Unified Communications features require integration with one-X Portal. These features
include:
• All of the Basic feature set, as described above
• Intelligent presence to determine the best way to reach a colleague quickly
• Visual Voice Mail that allows you to filter and sort voice messages so you can respond to
the most important messages quickly
• Visual Audio Bridge Conferencing that is easy to start, join, and manage for improved
collaboration and conference call effectiveness
• Communication History logs that help you trace the history of your enterprise calls and
voice messages
• Contact management tools that help you find contact information quickly and view the
presence information of corporate contacts
• Presence access requests control
Some functionality also requires integration with additional products.

Application server
Placing a call
It is a good idea to place a call from Avaya one-X Communicator to the Conferencing
application server, or bridge, to test connectivity to the bridge.
Prerequisites
Before you place a test call, you must connect Conferencing to your network and configure
the call branding table with appropriate DDI information.
The purpose of this task is to ensure that you have correctly completed the initial installation
and configuration of Conferencing.
1. Download Avaya one-X Communicator from https://support.avaya.com/css/

appmanager/css/support/Downloads/P0516#wlp_Downloads_Page and install it.
It is also a good idea to connect some headphones or earphones to the computer
you are using.
2. In the Telephone Number field, enter a valid DDI followed by the IP address of the
application server, using this syntax:
<DDI>@<Conferencing application server IP address>
3. Click the Place Call button.
Avaya one-X Communicator should dial the Conferencing application server. You
should hear the response of the Conferencing server through your headphones.
Example
Consider a telephone number range from 2710600 to 2710699, with the following call
branding entries:
• For the wildcard entry, enter ???? in the DDI field and DDI Unknown in the Name field.
Select Direct to enter queue from the On entry drop-down list.
• For the Sales department, enter a DDI such as 0601 in the DDI field and Sales
• For the Finance department, enter a DDI such as 0602 in the DDI field and Finance
• For the Marketing department, enter a DDI such as 0603 in the DDI field and
Marketing Department in the Name field. Select Scan call flow from the On entry
drop-down list.
To place a call using these example telephone numbers, enter 2710601 in the Telephone
Number field. Through the headphones, Conferencing should respond with a welcome
message and a request for a passcode. You could also test the wildcard entry by entering a

telephone number such as 2710604. In this case, Conferencing should respond by playing
a message to say that you are in a line to speak with an operator.
Next steps
Now, you can test connectivity to the CRS virtual machine by installing CRS Front End and
creating a test conference.
Client Registration Server

The CRS Front End consists of two parts. It is a scheduling interface for operators. It is also
an interface through which administrators can manage Conferencing resources. Operators
can access the Customer Bookings section and administrators can access the System
Administration section.
Avaya installs an instance of CRS Front End on the CRS virtual machine, by default. You can
use this instance of CRS Front End to verify the installation and configuration steps that you
have completed so far. Once you install the CRS Front End, you can use it to verify that the
Conferencing application server, or bridge, is corrected installed. You can also use the CRS
Front End to create a test conference and perform a test call.
As an aside, the Web Portal is similar to the CRS Front End. Essentially, it is a Web deployment
of the CRS Front End windows environment. Administrators and operators can use the Web
Portal to perform many of the tasks that they can perform using the CRS Front End. There are
limitations to the Web Portal, however, and it on ly covers a subset of CRS Front End
functionality.
Related topics:
Installing CRS Front End on the CRS server on page 88
Creating a test conference on page 90
Distributing CRS Front End to the operators on page 91
Installing CRS Front End on the CRS server
Note:
Avaya installs an instance of CRS Front End on the CRS virtual machine, by default. The
installation steps are included here for information purposes only.
It is a good idea to install an instance of CRS Front End on the CRS virtual machine. Using
this instance of CRS Front End, you can create a test conference and verify the installation
and configuration steps that you have completed so far. It is a good idea to test the deployment

at this stage, before you distribute the Conferencing applications to the operators and
moderators in your deployment.
Prerequisites
Before you install CRS Front End on the CRS server, you must install Conferencing.
The purpose of this task is to install an instance of CRS Front End so that you can create a
test conference and perform a test call.
2. In a Windows Explorer dialog, navigate to Avaya > ClientInstall and double-click
crs_client_suite to launch the installation wizard for the CRS Front End.
3. Navigate through the installation wizard. You require the CRS virtual machine IP
address to complete the installation.
On the final dialog of the installation wizard, you can click the Generate an
automatic installation script button to create an installation script which contains
each of the choices you made as you navigated through the wizard. This is useful
for installing the CRS Front End on the client machines for operators.
4. When the installation completes, you can start the CRS Front End on the CRS virtual
machine.
5. Enter admin in the Password field.
6. Click System Administration and click the Bridges tab to verify that the CRS has
visibility of the Conferencing application server.
Next steps
You can now create a conference to verify the installation and configuration steps that you
have completed so far.

Creating a test conference

It is a good idea to use the instance of CRS Front End that you have installed on the CRS
virtual machine to create a conference so that you can test the steps that you have completed
so far.
Prerequisites
Before you verify the installation, you must install and configure Conferencing and install an
instance of CRS Front End.
The purpose of this task is to create a company, a client, and a conference in order to test the
Conferencing connectivity.
1. On CRS Front End, click Customer Bookings and click Create Company.
2. Create a company for testing purposes. The only mandatory fields on the New
Company dialog are Name and Phone.
3. Select the newly created company and create a client for testing purposes. The only
mandatory fields on the New Client dialog are Name and Phone. However, to
enable access to Web Portal, you must enter a Password and an E-mail address.
4. Make a note of the password and e-mail address.
5. Select the newly created client and click Create Reservation.
6. Verify that the Check Reservation dialog displays the IP address of the
Conferencing application server in the Cabinet drop-down list.
7. Select On Demand to create an on-demand conference that is available at any time
and requires no scheduling.
8. Enter the number of participants in the Participants field. For example, 10.
9. Select Moderator and select Data.
The reason for selecting Moderator is to enable you to test the conference using a
participant entry and using a moderator entry. The reason for selecting Data is to
enable you to test the AWC component.
At any time, you can click DNIS/DDI to view the call branding entries.
10. Click OK and then click Confirm.
11. Enter a name for the conference. For example, Test Conference.
12. Click OK.

Web Portal
13. Make a note of the DDI, the conference reference number, the participant code, and
the moderator code. Click OK.
14. Place a call using Avaya one-X Communicator and enter the moderator code at the
audio prompt.
Next steps
Now you can test connectivity to the Web Portal and AWC virtual machines. Alternatively, you
can distribute the CRS Front End to your team of operators.
Distributing CRS Front End to the operators

Operators use the CRS Front End to manage customer accounts and schedule conferences.
You must install an instance of CRS Front End for each of the operators.
Prerequisites
Before you distribute the CRS Front End to the operators, you must install Conferencing and
perform some configuration steps. It is also a good idea to verify the installation before you
make the CRS Front End widely available.
The purpose of this task is to provide operators with a graphic user interface for managing
customer accounts, scheduling conferences, and viewing reports.
1. On the CRS virtual machine, navigate to /Avaya/ClientInstall and copy the

crs_client_suite file.
2. Save this file to location on the network that operators can access.
3. Instruct operators to access this file and install the application on their machines.
At this point, it is a good idea to provide operators with the Operating Avaya Aura™
Conferencing Guide, which is available from support.avaya.com.
4. You can also create a script using the Generate an automatic installation script
on the CRS Front End installation wizard and distribute that script to the operators'
machines.
Web Portal
The Web Portal is like a Web deployment of the CRS Front End. It provides moderators with
a Web interface for scheduling their conferences. It provides administrators with a Web

interface for managing moderators. However, there are some limitations and it does not provide
access to the full range of CRS Front End functions.
The Web Portal interface is divided into parts defined by unique URLs.
• Moderator’s section
The Web Portal moderator’s section enables moderators to book and manage
conferences, contacts, and account information and view reports. It is a good idea to
provide moderators with the Using Avaya Aura™ Conferencing Guide, which is available
from support.avaya.com. The Web Portal moderator URL is: http://Web Portal virtual
machine IP/webportal/login.
• Administrator’s section
The Web Portal’s Administrator’s section enables administrators to configure available
functionality, define the appearance of the Web Portal, and generate administrator
reports. The Web Portal administrator URL is: http://Web Portal virtual machine IP/
webportal/admin/login.
It is important to note that the Web Portal virtual machine uses the Linux operating system.
As a result, you cannot use the Windows remote desktop feature to access the Web Portal
virtual machine.
Related topics:
Accessing Web Portal on page 92
Accessing Web Portal using PuTTY on page 93
Client registration server on page 249
Login type on page 249
Mail server on page 250
Mail from on page 250
SSL enabled on page 251
SSL certificate on page 251
SSL private key on page 251
HTTPS on page 252
Brand prefix on page 252
Accessing Web Portal

It is a good idea to test connectivity to the Web Portal so that you can verify the steps that you
have completed so far.
Prerequisites
Before you verify the installation, you must install and configure Conferencing.

Web Portal
The purpose of this task is to log in to Web Portal to view the on-demand test conference that
you created using CRS Front End.
1. On any machine in your network, such as the Conferencing Manager server, open a
Web browser.
2. Enter the following URL: http://Web Portal virtual machine IP/
webportal/login and press Enter.
3. Enter the e-mail address and password for the client that you created using CRS
Front End.
Each client that you create using CRS Front End equates to a moderator in the Web
Portal environment.
4. Click Login.
Web Portal displays the My Schedule screen. You should be able to see the on-
demand test conference that you created using CRS Front End in the list of currently
scheduled conferences.
Next steps
As an additional verification step, you could use CRS Front End to create a test administrator
account. Make a note of the name and password that you configure for this test administrator
account. In the browser, enter http://Web Portal virtual machine IP/webportal/
admin/login and enter the name and password of the newly created administrator. Click
Login. Web Portal should display the Admin Reports screen.
Accessing Web Portal using PuTTY

The Web Portal virtual machine uses the Linux operating system. As a result, you cannot use
the Windows remote desktop feature to access the Web Portal virtual machine. You must use
the PuTTY application to access the Web Portal virtual machine.
Prerequisites
The purpose of this task is to log in to the Web Portal virtual machine using PuTTY to ensure
connectivity to the virtual machine..

download.html.
2. Start PuTTY.

3. On the PuTTY dialog, enter the IP address of the Web Portal virtual machine and
click Open.
4. Log in using the name craft and the password craft01.
The Web Portal virtual machine should respond with a prompt.
Next steps
You can now verify the Avaya Web Conferencing (AWC) virtual machine.

Avaya Web Conferencing (AWC) is an application that enables audio conference participants
to share data and video during their conferences. It is a component of the Conferencing suite of
products. In older releases of Conferencing, AWC was sometimes called Data Xchange.
Using AWC, participants enter a data conference either by following an e-mail link or using
their Web browser to browse to a URL and then entering security details. The conference client
loads in the Web browser and enables participants to communicate with each other using the
following methods.
• Chat (sending text messages)
• Whiteboard (free-form text and drawings)
• Shared applications (one user can share a program running on their computer and other
users can see it in operation; another user can even take control and work with the
program as if it were running on their own computer)
• Slide shows (snapshots of the Whiteboard or shared applications, Microsoft™ Powerpoint
slides, or JPEG images or voting slides; all slides can be annotated as they are
discussed )
The tools above can be used to present different types of conferences. For example, the
conference can be run like a seminar in which a moderator or presenter gives a pre-
prepared pitch. In this scenario, the other conference participants make up the audience.
Alternatively, the moderator can choose to allow all participants to have full use of all the
communication methods. In that case, a group of computer users in different locations can
work together as though they were sitting at the same computer. They can chat to each other
and view and control the same programs.
Related topics:
Accessing AWC on page 95

Accessing AWC
Prerequisites
The purpose of this task is to log in to AWC to view the on-demand test conference that you
created using CRS Front End.
1. On any machine in your network, such as the Conferencing Manager server, open a
Web browser.
2. Enter the following URL: http://AWC virtual machine IP/
conferencing and press Enter.
AWC should display the Avaya Web Conferencing Login Page.
3. Enter a name and telephone number.
4. Enter the conference reference number and the moderator passcode that you made
a note of when you created a test conference.
5. Click Login.
The AWC interface is displayed.
Next steps
Now you have installed Conferencing and verified the installation. You can now configure
Conferencing to match the customer requirements and the customer environment.


Chapter 8: Configuring logs and alarms
Logs and alarms

For this release of Conferencing, Avaya has developed a new process for viewing and
managing Conferencing logs and alarms. This new process replaces the older system of
Simple Network Management Protocol (SNMP) traps and core services monitoring. The new
process is also compatible with an SNMP framework and, as before, you can configure the
logs and alarms to report to a Network Management System (NMS).
Secure Access Link (SAL) is an Avaya serviceability solution that supports log and alarm
reception and relay. Avaya installs SAL Agent 1.0 software on the Conferencing application
server (bridge) and provides log and alarm relay to Conferencing Manager and System
Manager for all Conferencing components. SAL Agent 1.0 does not support remote access.
For the successful relay of Conferencing logs and alarms to Conferencing Manager and
System Manager, you must configure the Conferencing SAL agent on the application server
(bridge).
Note:
If you change the IP address, host name, or domain name of any of the Conferencing virtual
machines, you must re-configure logs and alarms.
The following tables describe the Conferencing logs and alarms. In the following tables, the
<> symbols represent a variable.
Web Portal logs and alarms
The Web Portal generates a number of logs and alarms. For example, the Web Portal
generates a log when administrators or moderators log in to Web Portal.
Category Type Severity Content of message Comment

Audit Event Informational Admin user <> logged in
Audit Event Informational Wholesaler user <> logged in
Audit Event Informational Moderator user <> logged in
Audit Event Informational Configuration changed Does not log which
parameters have been
changed.
Operation Event Informational Application started

Configuring logs and alarms

Operation Event Informational Application stopped
Application Programming Interface (API) logs and alarms

The Avaya Conferencing Provider Interface (ACP or ACPI) is an object-oriented, programming
interface, written in Java. The API can be used by any application that can make a Java call.
Through ACPI operations, developers can create applications that create ad-hoc conferences,
open a scheduled or demand conference using it's participant codes, manage conference
recording and playback, manage conference security, manage Q&A and polling, dial out
participants and so on. The API generates a number of logs.
Category Type Severity Content of message

Operation Event Warning Avaya Conferencing Provider Application Programming
Interface (ACP API) communication problem <>
Secret PIN logs and alarms

A secret PIN is a unique number that Conferencing assigns to each Conferencing participant. A
secret PIN provides access to a conference that is booked using the Identify and Validate
setting of Participant ID mode. When operators or moderators book a Participant ID mode
conference with Identify and Validate, all conference participants must enter an identifying
number and a secret PIN on their telephone keypad prior to entering the conference. A Web-
based, secret PIN management application enables the management of these secret PINs.
This PIN management application generates a number of logs. For example, the PIN
management application generates a log when administrators or moderators log in to the
application.

Audit Event Informational Admin user <> logged in
Audit Event Informational Moderator user <> logged in
Audit Event Informational PIN changes
CRS logs and alarms

The CRS generates a number of logs if it encounters an issue.

Operation Event Warning CRS communication problem. It does not provide specific
Refer to logs for further details. detail about the issue.
Operation Event Error CRS exception <> For example, a database
error

Logs and alarms
AWC logs and alarms

These AWC alarms relate to the transfer of information between AWC and CRS.

Operation Event Warning CRS — DB AWC local DBServices is
communication problem offline.
<>
Operation Event Error CRS exception <> For example, a database error
Operation Event Warning AWC rebooting When AWC is rebooting, the link
between the authenticator and
CRS is offline.
Media and application server logs and alarms

The media server component of Conferencing provides a number of functions, such as, audio
mixing, Dual Tone Multi Frequency (DTMF) detection, message playing, and conference
recording. The media server logs and alarms primarily monitor two aspects of media server
functionality. They monitor the operation of Secure Real-time Transport Protocol (SRTP) and
they monitor the usage of telephone lines or ports.
SRTP defines a profile of RTP intended to provide encryption, message authentication, and
integrity, and replay protection to data. Conferencing supports this protocol for all audio and
data transfers.
The application server is also called the bridge. It is the "heart" of the Conferencing solution.
It handles all telephone calls to Conferencing and selects a media server on which to terminate
each call. It interprets all DTMF inputs, SIP information, database requests, and it processes
billing data. The application server communicates with the media server to provide a complete
Conferencing solution. It is often called a call handler application server.
The phrase 'Reserved Port Pool' refers to the number of ports set aside for scheduled
conferences. Typically, when you install and configure Conferencing, you assign a number of
ports for scheduled conferences and a number of ports for on-demand conferences.
An on-demand conference is a conference that is available whenever the conferees require it.
On-demand conferences are also known as demand conferences. Each instance of a demand
conference requires no additional scheduling. Participants can access the demand conference
provided they have the appropriate telephone number and passcodes.
A scheduled conference is a conference that has a defined start time and end time. When
moderators book a scheduled conference, Conferencing reserves system resources to cater
for the duration and size of the conference.
It is important to take account of the usage pattern of the Conferencing system when assigning
the allocation of ports for scheduled and on-demand conferences.
Category Type Severity Content of Comment

message
Operation Event Error Reserved Port Pool Conferencing generates this alarm
Usage has when the number of used ports in
increased above the reserved port pool equals or


message
configured upper exceeds the upper watermark
watermark. configured for that pool providing
the corresponding lower
watermark has been crossed
since the last time Conferencing
generated this alarm. The default
value for a high threshold is 85%.
Operation Event Informational Reserved Port Pool Conferencing generates this alarm
Usage has when the number of used ports in
decreased below the reserved port pool falls below
configured lower the lower watermark configured for
watermark. that pool providing the
corresponding upper watermark
has been crossed since the last
time Conferencing generated this
alarm. The default value for a Low
Threshold is 75%.
Operation Event Error Unreserved Port Conferencing generates this alarm
Pool Usage has when the number of used ports in
increased above the unreserved port pool equals or
configured upper exceeds the upper watermark
the corresponding lower
value for a High Threshold is 85%.
Operation Event Informational Unreserved Port Conferencing generates this alarm
Pool Usage has when the number of used ports in
decreased below the unreserved port pool falls
configured lower below the lower watermark
the corresponding upper
value for a Low Threshold is 75%.
Operation Event Emergency Application server Triggered when endpoints cannot
failed set up a Secure Real-time
Transfer Protocol (SRTP) session
or have an unreliable session.
Operation Event Emergency Media server failed Triggered when endpoints cannot
set up an SRTP session or have
an unreliable session.

Logs and alarms

message
Operation Event Warning Host server Triggered when endpoints cannot
rebooted set up an SRTP session or have
an unreliable session.
Operation Event Error Rx SRTP errors Triggered when endpoints cannot
since beginning of set up an SRTP session or have
session an unreliable session.
Operation Event Warning Too much time
process at once
dump packets acc
usecs.
Operation Event Critical Disk is full {0} Sent when a disk reaches 100%
utilization.
Operation Event Warning High disk utilization Sent when a disk reaches
{0} utilization of 80% or more.
Operation Event Warning High CPU Sent when a CPU utilization is
utilization. System 90% or more.
idle {0} percent
Operation Event Informational Conferencing Sent when a bridge start has
engine is completed.
operational.
Note:
You can view some of this information in a file on the Conferencing Manager virtual machine.
This file is located on the Conferencing Manager virtual machine in the following location:
/var/log/Avaya/mgmt/resource/com/avaya/conferencing/bridge/
EventCodes.properties
Here is an example of the output:
OP-BRIDGE00003 Reserved Port Pool Usage has increased above upper
watermark - up per watermark/max. ports: {0}/{1}
OP-BRIDGE00004 Reserved Port Pool Usage has decreased below lower
watermark - lo wer watermark/max. ports: {0}/{1}
OP-BRIDGE00005 Unreserved Port Pool Usage has increased above upper
watermark - upper watermark/max. ports: {0}/{1}
OP-BRIDGE00006 Unreserved Port Pool Usage has decreased below lower
watermark - lower watermark/max. ports: {0}/{1}
OP-BRIDGE00009 Host server has rebooted OP-BRIDGE00010 Disk is
full. {0}.
OP-BRIDGE00011 High disk utilization. {0} {1} percent used.
OP-BRIDGE00012 High CPU utilization. System idle {0} percent.

OP-BRIDGE00013 Conferencing engine is operational.

Session Initiation Protocol (SIP) logs and alarms
These alarms and logs relate to the Avaya Conferencing Provider (ACP) SIP notification
interface (SNI). Conferencing uses the SIP method of signalling.

Operation Event Error Could not load supplied The program still runs
properties file <filename> but the properties are
most likely incorrect and
lead to errors.
Operation Event Emergency ACP-SNI-SIP agent Program exits after
communications problem <> creating this log
Operation Event Emergency Could not send to SIP agent Program exits after
using PIPC ID <id> from local creating this log
channel <local channel> to
remote channel <remote
channel>
Operation Event Emergency ACP-SNI-ACPI Program exits after
communications problem <> creating this log
Operation Event Error Could not send request for RAI Program continues but is
information, RAI information is in a state of error. It is
out of date possible to get out of this
state, which is why the
program does not exit.
Operation Event Emergency Communication with SIP agent Program exits after
using RIPC service has been creating this log
shut down
Conferencing Manager logs and alarms

As part of the Conferencing architecture, there is a servlet on each of the virtual machines in
the Conferencing solution. Each servlet sends information about the virtual machine on which it
resides.

Operation/Audit Event Informational <Component> started
Operation Event Warning <Component> start failed <>
Operation/Audit Event Informational <Component> stopped
Operation Event Warning <Component> stop failed <>
Operation/Audit Event Informational <Component> back up succeeded
Operation Event Warning <Component> back up failed
Operation/Audit Event Informational <Component> restore succeeded

Logs and alarms

Operation Event Warning <Component> restore failed <>
Operation Event Warning <Component> get configuration failed <>
Operation/Audit Event Informational <Component> set configuration succeeded
Operation Event Informational <Component> set configuration failed <>
Operation Event Informational <Component> validation passed
Operation Event Warning <Component> validation failed <>
Operation Event Informational <Component> license state OK
Operation Event Error <Component> license state 30 day grace period
Operation Event Emergency <Component> license state invalid license
Operation Event Emergency <Component> license state Expired
Operation Event Emergency <Component> license state 30 days grace expired
Operation Event Informational <Component> scheduled task <> started
Operation Event Informational <Component> scheduled task <> finished
Operation Event Error <Component> scheduled task <> failed
Operation Event Informational <Component> restarting the operating system
Operation Event Informational <Component> halting the operating system
Operation Event Informational <Component> license state OK (Cached)
Operation Event Informational <Component> license feature <feature> request
succeeded <value>
Operation Event Error <Component> license feature <feature> request
failed <value>
Operation Event Informational <Component> license feature <feature> release
succeeded <value>
Operation Event Error <Component> license feature <feature> release
succeeded <value>
Operation Event Informational Connected to license server
Operation Event Error Cannot connect to license server
Operation Event Informational Connection to license server restored
Related topics:
SAL connectivity settings
Three pieces of information on page 104
Port pool usage thresholds on page 176

Three pieces of information

To configure logs and alarms, you require three pieces of information. You require an
enrollment password, an Avaya Aura™ Alarming ID, and an Avaya Aura™Conferencing 6.0
Managed Element ID (which is also called an Avaya Aura™ Conferencing ID).
You can obtain the enrollment password using Conferencing Manager. To obtain the Avaya
Aura™ Alarming ID and the Avaya Aura™Conferencing 6.0 Managed Element ID (Avaya
Aura™Conferencing ID), you must send an e-mail to Avaya.
Related topics:
Logs and alarms on page 97
Enrollment password on page 104
Avaya AuraConferencing 6.0 Managed Element ID on page 104
Avaya Aura Alarming ID on page 104
Enrollment password
An enrollment password is a unique code that Conferencing Manager generates. You require
this code in order to configure logs and alarms. As an alternative to accepting the code that
Conferencing Manager provides, you can enter your own phrase as an enrollment password.
Avaya Aura™Conferencing 6.0 Managed Element ID

The Avaya Aura™ Conferencing 6.0 Managed Element ID is a 10 digit numeric sequence which
you can obtain from Avaya.
The Avaya Aura™ Conferencing 6.0 Managed Element ID is called Avaya Aura™Conferencing
ID in the Conferencing Manager and System Manager administrative interfaces.
Avaya Aura™ Alarming ID

The Avaya Aura™ Alarming ID is a 10 digit numeric sequence which you can obtain from Avaya.
This ID is unique to the SAL Agent software installed on the bridge (application server).

Obtaining the three pieces of information
Obtaining the three pieces of information

Prerequisites
Before you obtain the three pieces of information that are necessary for configuring logs and
alarms, you must know your Avaya Sold-to Number (customer number).
The purpose of this task is to obtain the three pieces of information that are necessary for the
successful operation of logs and alarms.
1. Write an e-mail to salreg@avaya.com. In the e-mail include the following details:

• Your Avaya Sold-to Number (customer number)
• Your customer name
• Your contact information to help Avaya contact you if there are questions
Avaya uses this information to register your request. When the registration is
complete, Avaya send you:
• An e-mail with the Avaya Aura™ alarming ID and the Avaya Aura™Conferencing
6.0 Managed Element ID (Avaya Aura™ Conferencing ID)
• A list of the devices currently registered at this location
• A listing of your other company locations
2. Make a note of these IDs.
3. Log in to Conferencing Manager. By default, the username is admin and the
password is admin123.
4. Navigate to Security > Certificates > Enrollment Password.
5. From the Password expires in drop-down list, select a time interval.
6. Click Generate.
Conferencing Manager displays a password in the Password field.
7. Make a note of this password.
Next steps
Now you can configure logs and alarms.
Related topics:
SAL connectivity settings on page 147


Prerequisites
Before you configure logs and alarms, you must obtain the three pieces of information
necessary for the successful operation of logs and alarms.
The purpose of this task is to configure logs and alarms.

machine.
4. Click Configure.
6. In the SAL Connectivity Settings section, enter your enrollment password and the
Avaya Aura™Conferencing 6.0 Managed Element ID (Avaya Aura™Conferencing
ID).
7. Click Save at this point but do not apply the changes because you must perform a
further configuration step.
Conferencing Manager displays the IP address of the available application server
or bridge virtual machine.
9. Select the bridge virtual machine.
10. Click Configure.
11. On the bridge configuration sub-pages screen, click System Config.
12. In the SAL Connectivity Settings section, enter the Avaya Aura™ Alarming ID.
13. Click Save.
You can now apply the changes by clicking the Apply Changes button.
Next steps
Now you can view the logs and alarms. Optionally, you can configure the logs and alarms to
transmit to a Network Management System (NMS).

Sending the logs and alarms to a network management system
Related topics:
Sending the logs and alarms to a network management

system
Prerequisites
Before you configure the transfer of the logs and alarms to an external device, such as a
Network Management System (NMS), you must configure the logs and alarms using
The purpose of this task is to enable the transfer of logs and alarms to an NMS so that you
can leverage the features of an NMS.

2. Navigate to Conferencing Manager Data > Settings > Alarm Management
Service > Agent management.
3. Set NMS forward to true.
4. In the NMS urls field, enter the IP address(es) of the NMS and port 162.
5. Start PuTTY.
6. On the PuTTY dialog, enter the hostname or IP address of the Conferencing
Manager virtual machine.
8. Use the sroot command to change from craft to sroot access.
su sroot
9. Enter the command service jboss restart.
Conferencing Manager restarts jboss. This step is necessary in order to configure
the NMS location.
Next steps
Now you can configure more Conferencing settings. It is also a good idea to verify that
Conferencing Manager is successfully generating logs and alarms by viewing them on

Viewing logs and alarms

Some people like to view logs and alarms using a utility called Vi Editor. Avaya does not
recommend using Vi Editor to open any files that are greater than 10 MBs in size. If you use
Vi Editor to open large files, the central Processing Unit (CPU) usage may rise to 100% for a
period of time.
Vi is a family of screen-oriented text editors which share certain characteristics, such as
methods of invocation from the operating system command interpreter, and characteristic user
interface features.
Prerequisites
You must configure logs and alarms before you can view them.
It is a good idea to view the logs and alarms at this stage in order to verify that your configuration
steps have been successful.

2. Navigate to Events > Alarms to view the alarms.
3. Navigate to Events > Logs > Log Viewer to view the logs.
Troubleshooting logs and alarms

• If you experience issues with logs and alarms, you must re-configure the Conferencing
SAL agent, using the same steps that you originally used to configure logs and alarms. If
you change the IP address, host name, or domain name of any of the Conferencing
virtual machines, you must also re-configure logs and alarms.
• If you need to perform debugging on of the files, the following table lists the relevant
folders.
Folder Description
/var/log/avaya/ The SAL agent initialization log
spirit.config.log Check for [Error] entries
/opt/spirit/logging/ SAL agent runtime log
spirit.log

Location of additional logs of interest
Folder Description
Check for communication issues with
Conferencing Manager
/var/log/avaya/spirit.log Conferencing components log to this file using
rsyslog
Lines in this file should be in the correct Avaya
Common Logging Format (CLF)
All CLF lines should be forwarded to Conferencing
Manager as a log and as an alarm
Location of additional logs of interest

Aside from the SAL functionality, there are a number of other logs that you might wish to view.
Each virtual machine runs a management servlet. These servlets produce log files. These logs
are listed here.
Component Log Location

Web Portal <Web Portal virtual machine>/var/log/avaya/conferencing/avaya-
web-configurator:
avaya-web-configurator.log
debug.log
warn.log
System Platform <System Platform virtual machine>/vspdata/backup:
backup.log
Application server <Application server virtual machine>/var/log/avaya/acbms
(bridge) General logs
Application server In a browser, enter: http://<Application server virtual machine>:
(bridge) license 18080/info
information The application server returns the license status, for example:
edition=Standard Edition
audio-ports=300
license-status=LICENSE_GRACE
version=6.0.0.0.1
productId=bridge


Chapter 9: Configuring the application
server
An application server is the location of many of the core Conferencing processes. It is the
"heart" of the Conferencing solution. It handles all telephone calls to Conferencing and selects
a media server on which to terminate each call. It interprets all DTMF inputs, SIP information,
database requests, and it processes billing data. The application server communicates with
the media server to provide a complete Conferencing solution. It is often called a call handler
application server or bridge or audio conferencing server.
In the Standard Edition of Conferencing, the application server and the media server reside
on the same virtual machine. In the Enterprise Edition of Conferencing, the application server
and the media server can reside on separate virtual machines.
The Conferencing media server provides a number of functions, such as, audio mixing, Dual
Tone Multi Frequency (DTMF) detection, message playing, and conference recording. In the
Standard Edition of Conferencing, the media server and the application server reside on the
same box: An IBM 3550 server.
The configuration of the application server involves the configuration of five aspects of
application server properties. The five aspects are:
• Bridge features
• Conference features
• Call routing
• System configuration
• General configuration
Related topics:
Bridge features on page 112
Conference features on page 121
System configuration on page 141
General configuration on page 150

Configuring the application server
Bridge features
The bridge features consists of five different sections:
• Media servers
• Prompt set management
• Bridge features
• Scheduling
• Sign-in users
In the case of each of these areas, the documentation describes each setting. Following the
field descriptions, there is a description of how to configure a sample setting.
Related topics:
Media servers on page 112
Prompt set management on page 112
Bridge features on page 113
Scheduling on page 116
Sign in users on page 118
Configuring bridge features on page 120
Media servers
In the Standard Edition of Conferencing, the application server and the media server reside
on the same virtual machine. In the Enterprise Edition of Conferencing, the application server
and the media server are separate. In the Enterprise Edition of Conferencing, the media
server(s) are on dedicated servers, rather than virtual machines.
Prompt set management

During a conference, Conferencing plays audio messages to participants to inform them of
conference information and to prompt them for a response. These audio messages are
sometimes called audio prompts or annunicator messages. A group of audio messages is often
called a prompt set.
Using Conferencing Manager, you can view the prompt sets and audio message text.
Conferencing Manager obtains this information from the application server, or bridge.

Bridge features
Related topics:
Audio messages and prompt sets on page 291
Viewing prompt sets on page 298
Bridge features
The bridge features settings relate to the behavior of the Conferencing application server, or
bridge, during a live conference. This section contains settings relating to audio messages and
DTMF commands, among other aspects of Conferencing. This section also includes settings
relating to features such as operator assistance and blast dial out.
Related topics:
Name record playback seconds on page 113
Recite wrong passcode on page 114
Mute participants during playback on page 114
Automatic conference clear on page 114
Attended originator dial out on page 115
Operator assistance on page 115
On hold message frequency on page 116
Startup notify time on page 116
Name record playback seconds

Name record playback (NRP) refers to a feature whereby participants can state their name as
they enter a conference. Conferencing records their name and makes it available for other
features, such as the roll call of participants or the entry and exit name announcements. Name
record playback seconds relates to how Conferencing behaves if you enable NRP in your
deployment. In particular, this parameter controls how Conferencing deals with the #
terminator. The valid values range from 0 to 16 seconds. The default value is 0. Avaya
recommends a value of 3.
•0
Participants must press # after they state their name.
• 1–16
The number of seconds that Conferencing waits before automatically placing the
participant in their conference.

Recite wrong passcode

If a caller enters an incorrect passcode, this setting determines if Conferencing plays an error
message that mentions the actual individual DTMF digits entered by the caller. The default
value is OFF.
• OFF
Conferencing plays an error message that states that the caller entered a wrong code.
This message does not mention the actual digits.
• ON
Conferencing plays an error message that mentions the individual DTMF entries entered
by the caller so that the caller can recognize if they entered an incorrect code.
Mute participants during playback

Mute Participants During Playback specifies whether Conferencing mutes participant lines
during the playback of a recorded conference. The default value is OFF. If you update this
setting on a live system, with a playback in progress, the update does not impact active
conferences.
• ON
Conferencing mutes participant lines during playback.
• OFF
Conferencing does not mute participant lines during playback.
Automatic conference clear

Automatic Conference Clear specifies whether Conferencing automatically clears attended
conference settings when a conference ends. Conferencing generates a conference detail
record (CODR) and a conference report for a conference only after that conference has been
cleared. The default value for this setting is OFF. This setting only applies to attended
conferences. Conferencing always automatically clears unattended conferences.
• ON
Conferencing automatically clears conference settings when the last participant exits an
attended conference. Settings cleared include: entry tone, exit tone, ID, lecture, links,
lock, music, name, note, playback, record, security, and time information.
• OFF

Bridge features
An operator must run the Conference Clear_all command in Bridge Talk to remove
features from completed attended conferences.
Attended originator dial out

Attended Originator Dial Out (ODO) defines whether moderators can use their telephones to
dial out to other telephone during an active conference. This feature is useful for contacting
participants who cannot dial in. The default value is OFF. Conferencing restricts ODO to one
moderator at a time per conference.
• ON
In an attended conference, a moderator can use ODO, if there is a free channel configured
for ODO Allow.
• OFF
In an attended conference, a moderator cannot use ODO.
Operator assistance
Operator Assistance specifies whether operators provide help to entire conferences or only to
the participant who requests help. When an operator provides help only to the participant who
requested the help, Conferencing temporarily removes the participant from the conference to
speak privately with the operator. The default option is INDVL. Conferencing operators
individually help participants requesting help from muted lines, regardless of the setting.
• INDVL
The operator helps only individual conferees who request help.
• CONF
The operator provides help to the entire conference. Conferencing does not remove
anyone from the conference. All conferees hear whatever assistance is provided by the
operator.
Typically, a feature involving operators requires Bridge Talk. Bridge Talk is an application which
enables operators to monitor conferences. The Standard Edition of Conferencing does not
support the Bridge Talk application but it can support an external application with similar
features. You can configure this application to operate with Conferencing using the ACP API.

On hold message frequency

On Hold Message Frequency specifies whether Conferencing plays the On Hold message (#
208) in the Enter queue and the frequency with which it plays the message. The default value is
OFF.
• OFF
Conferencing does not play the on hold message.
• 5, 10, 15...50, 55, 60
This value represents the interval, in seconds, after which Conferencing plays the on hold
message. For example, if you specify 5, Conferencing plays the message every 5
seconds.
Startup notify time

Startup Notify Time specifies whether Conferencing automatically sets up scheduled attended
conferences and notifies operators for those conferences. The default value is OFF.
Conferencing checks for conferences that need setup at 1 minute intervals. If there are
concurrent attended conferences with the same name, Bridge Talk only displays one of them.
To ensure that Conferencing displays the fields Contact Name, Contact Telephone,
Scheduled Participants, and Scheduled Minutes in Conference Reports, you must enable
this value.
• OFF
does not start up scheduled attended conferences.
•0
Conferencing starts the setup and sends notification messages at the conference’s
specified start time.
• 1, 2, 3, 4, 5, 10, 15, 20, 25, or 30
This value represents the number of minutes before the conference’s scheduled start time
that Conferencing sets up the conferences and sends the notifications.
Scheduling
The Scheduling section contains a list of features. These features are not installed on the
Conferencing server, by default. If you require access to these features, you must enable them.
These features are free. Avaya does not charge for them.
Conferencing Manager only displays the Line overbooking and Overbook percent fields
when it is not associated with a Client Registration Server (CRS). When there is a CRS

Bridge features
association, you can control the overbooking settings on the Elements > Conferencing >
Client Registration > General > General Settings using the Allow Infinite Ports and
Overbook Percent fields.
Related topics:
Pin code on page 117
Line overbooking on page 117
Overbook percent on page 117
Flex call flow on page 118
Pin code
Pin Code specifies whether PIN codes are enabled in your Conferencing deployment. A PIN
code is an identification number that is unique to each participant. In a deployment with PIN
codes enabled, operators and moderators can book unattended conferences which require
participants to enter their conference passcode and their PIN code before accessing the
conference.
Line overbooking
Line Overbooking is the process of reserving more than the maximum number of available
telephone lines for a given time period. This functionality ensures that you can maximize the
use of Conferencing by allowing for the fact that in many cases, full conference attendance
does not occur. Operators and moderators can overbook for scheduled conferences. The
overbooking feature does not impact on-demand conferences.
In a sense, the overbooking feature increases the reserved port pool by providing an additional,
virtual reserved port pool. If the overbooking percentage is too high, Conferencing may reject
participants if too many participants attempt to attend a conference and there are not enough
available ports. It is important to set the overbooking percentage at an appropriate level for the
usage pattern associated with your deployment of Conferencing.
To enable the overbooking feature in your deployment, you must enable this parameter. You
must also configure the overbooking percentages on the CRS server. The CRS parameter is
called Overbook Percent.
Overbook percent
The overbooking feature increases the available ports by providing a pool of additional virtual
ports. These virtual ports are available for reserved conference bookings. This functionality
ensures that customers can maximize the use of Conferencing by allowing for the fact that in
many cases, full conference attendance does not occur.

The Overbook Percent parameter specifies the percentage of Conferencing lines that
operators and moderators can overbook for scheduled conferences. This parameter does not
impact on-demand conferences. By default, the value of the Overbook Percent parameter is 0.
• If the value of the Overbook Percent parameter is between 1and 100:
Operators and moderators can reserve a percentage from 1% to 100% more than the
maximum number of lines available for a given time period. Lines configured for operators,
music, record/playback, or link lines are not included in the line count. For example, if
your deployment of Conferencing has 1000 lines available for scheduled conferences and
you set this parameter for 10%, you can schedule 1100 lines.
• If the value of the Overbook Percent parameter is 0:
Conferencing allows infinite conference overbooking.
Related settings
To make overbooking available in your deployment, you must also enable the Line
Overbooking feature on the Conferencing application server, or bridge.
A related parameter is the On Demand Pct % parameter.
Example scenario
In practice, it is a good idea to set the Overbook Percent parameter to 0 which is infinite and
On-Demand Pct (%) to 50%. Avaya sets the On-Demand Pct (%) to 50%. These values allow
for 50% of the ports to be allocated to on-demand conferences and 50% to be allocated to
scheduled conferences. The available ports is the total number of telephone lines with the total
number of FDAPI resources subtracted from this total. FDAPI resources include operator
telephone lines and playback telephone lines.
Flex call flow

Flex Call Flow is the term used to identify the user experience for a participant as they enter
a special kind of conference, called a flex flow conference. Flex flow conferences are
conferences in which all participants enter a conferee passcode on their telephone keypad.
After entering a conferee passcode, moderators can enter a moderator passcode to promote
their status.
If you want to support the flex flow user experience in your deployment, you must enable this
parameter.
Sign in users
A sign-in consists of a login name and a password created to enable an application or a user to
connect to the Conferencing application server. Each application that uses the ModAPI
conventions to connect to the application server requires a sign-in. Similarly, each user, such
as an administrator or an operator, requires a sign-in.

Bridge features
There are three types of sign-ins:
Sign-in type Description

User Administrators can create this type of sign-in. Administrators can also edit
the passwords of user sign-ins.
System The Conferencing system creates these sign-ins to enable applications to
connect to the application server. Administrators cannot view the passwords
associated with this type of sign-in. However, administrators can reset the
passwords. Conferencing makes all the connecting applications and the
application server aware of the newly reset passwords.
The reset password function is beneficial if your deployment has a policy
requirement in relation to periodically updating passwords.
Template The Conferencing system creates template sign-ins. Administrators cannot
modify or delete them.
Each sign-in type also has a privilege level. The privilege level for a sign-in specifies which
resources that sign-in can use and what management interface menus the sign-in can access.
Users with the higher-level sign-ins can access more resources than users with lower-level
sign-ins.
Sign ins were particularly important in older versions of Conferencing because system
administrators had to perform many of the configuration tasks using the command line menu.
Although the Standard Edition of Conferencing does not support Bridge Talk, sign ins are still
important. For example, you require a sign in for some integrations, such as the Conferencing
Plug in for IBM Lotus Sametime.
There are four sign-in levels.
Sign in level Privileges

Maintenance Access to all scheduling resources and management interface options,
including maintenance, administrator, operator, scheduler tasks, and
network configuration.
Administrator Access to all scheduling resources and administrator-level management
interface options.
Operator Access to operator tasks only. No access to the System Administrator menu.
Scheduler Access to the Bridge Talk Scheduler application.
Note:
The Standard Edition of Conferencing does not support Bridge Talk.
Related topics:
Configuring sign ins on page 120

Configuring sign ins

The purpose of this task is to add, edit, or delete a sign-in account.

Conferencing Manager may display the IP address of the available application
server virtual machine.
3. Select the application server, or bridge virtual machine if necessary.
4. Click Configure.
5. On the Audio Conferencing Configuration screen, click Bridge Features.
6. Click Sign In Users and click Edit.
7. Click Add to add a new sign in.
You can edit or delete any existing resellers using the Change or Delete buttons.
8. Enter the sign in information.
The user name can be up to eight characters in length and can include only letters
and numbers. The telephone number is an optional field. Do not use underscores
(_), hyphens (-), spaces, or other special characters in the User Name or User
password field. These two fields are case-sensitive. For example, lee, Lee, and
LEE represent three different sign-in names. You cannot use identical sign-in
names, but different sign-in names can have identical passwords.
9. When you have finished entering the information, click Back.
Conferencing saves the new sign in.
Configuring bridge features

Prerequisites
Before you configure bridge features, ensure that you install Conferencing and assign each of
the virtual machines to the CRS virtual machine in the Components section.
The purpose of this task is to make changes to the Conferencing default properties to match
the requirements of your deployment.

Conference features

4. Click Configure.
5. On the Audio Conferencing Configuration screen, click Bridge Features.
6. Click Expand All to display all the configurable settings.
7. Update the settings as necessary.
8. Click Save.
9. If you wish to apply those updates to the Conferencing network, click Apply
Changes and then Apply Changes again.
When you apply changes, Conferencing restarts. It is a good idea to apply changes
only when you are finished all your configuration tasks.
Example
For example, if you wish to enable dial out for moderators during live conferences, select
Attended ODO.
Conference features
The conference features consists of several different sections:
• Conference defaults
• Conference settings
• Conference error behavior
• Conference features
• Ad-hoc conferencing

Related topics:
Conference defaults on page 122
Conference settings on page 125
Conference error behavior on page 131
Conference features on page 133
Adhoc conferencing on page 134
Configuring conference features on page 135
Conference defaults
The Conference Defaults settings are the automatic values that are assigned to conferences,
outside of moderator intervention. A moderator or an operator can overwrite some of these
values at conference booking time. These conference default values are similar to preset
properties.
Related topics:
Tone type on participant entry on page 122
Tone type on participant exit on page 122
Play first person message on page 123
Single person (SP) 1st period on page 123
Number of SP subsequent prompts on page 123
SP prompt waiting period on page 123
Auto extend conference duration on page 123
Auto extend conference ports on page 124
Early start minutes on page 124
Conference passcode on page 125
Tone type on participant entry

Tone Type On Participant Entry specifies the number of beeps in an entry tone when a
participant enters a conference. Operators and moderators can also enable or disable entry
tones on a per-conference basis, using any of the booking interfaces, such as Web Portal,
CRS Front End, the Avaya Conference Scheduler Plug-in for Microsoft Outlook, and so on.
Tone type on participant exit

Tone Type On Participant Exit specifies the number of beeps in an exit tone when a participant
leaves a conference. Operators and moderators can also enable or disable exit tones on a
per-conference basis, using any of the booking interfaces, such as Web Portal, CRS Front
End, the Avaya Conference Scheduler Plug-in for Microsoft Outlook, and so on.

Conference features
Play first person message

Play First Person Message specifies whether Conferencing plays message 221; “You are the
first participant in this conference”, when the first participant enters a conference.
Enable Play First Person Message to ensure that Conferencing plays the message.
Single person (SP) 1st period

When Conferencing detects that there is only one person in a conference, Single Person (SP)
1st Period represents the number of minutes that Conferencing waits before playing a prompt
requesting a DTMF digit to indicate that the conference should continue.
Number of SP subsequent prompts

Number Of SP Subsequent Prompts represents the number of times that Conferencing plays
the prompt requesting a DTMF digit to indicate that the conference should continue.
SP prompt waiting period

SP Prompt Waiting Period represents the number of minutes that Conferencing waits after
requesting a DTMF digit before playing subsequent prompts. Once it receives a DTMF digit,
Conferencing resets the timer to the Single Person (SP) 1st period.
Auto extend conference duration

Auto Extend Conference Duration specifies whether Conferencing attempts to automatically
extend the duration of in-progress unattended conferences for 25 additional minutes.
Conferencing attempts to extend a conference three additional times after successfully
extending it the first time. This means that a conference can extend up to 100 minutes beyond
its original end time. If you enable warning tones, each time Conferencing plays a warning
tone, it also attempts to extend the conference, including one last time just before the
conference ends. If you do not enable warning tones for unattended conferences,
Conferencing attempts to extend a conference one time just before a conference’s end time.
Conferencing plays annunciator message 241 to inform participants that it has extended their
conference; otherwise, the conference ends at the scheduled end time. If your deployment

uses an External Passcode Validation (EPV) process, Auto Extend Conference Duration is
always disabled.
• Default on
Conferencing attempts to extend unattended conferences. Successful extension
depends on the availability of telephone lines and passcodes. Operators and moderators
can change this setting on a per-conference basis, using many of the Conferencing
booking applications.
• Default off
Conferencing does not attempt to extend unattended conferences. Operators and
moderators can change this setting on a per-conference basis, using many of the
Conferencing booking applications.
• Always off
Conferencing does not attempt to automatically extend unattended conferences.
Operators and moderators cannot change this setting on a per-conference basis.
Auto extend conference ports

Auto Extend Conference Ports specifies whether Conferencing can allocate additional
participant ports (telephone lines) to unattended conferences while they are in progress.
Flexflow conferences do not support Auto Extend Conference Ports.
• Default on
Conferencing attempts to allocate additional ports to accommodate additional participants
as required. Successful allocation of ports depends on the availability of (non-reserved)
ports. Operators and moderators can change this setting on a per-conference basis, using
many of the Conferencing booking applications.
• Default off
Conferencing does not attempt to allocate additional ports to accommodate additional
participants. Operators and moderators can change this setting on a per-conference
basis, using many of the Conferencing booking applications.
• Always off
Conferencing does not attempt to allocate additional ports. Operators and moderators
cannot change this setting on a per-conference basis.
Early start minutes

Early Start Minutes specifies whether participants can enter unattended conferences earlier
(1 - 30 minutes) than the scheduled start time if ports (telephone lines) are available. The

Conference features
default value is Off. Two or more conferences may have conflicting passcodes if you enable
Early Start Minutes and an operator or moderator extends an earlier conference. Conferencing
detects when a conflict will occur. As a result, if Conferencing detects a conflict, operators and
moderators cannot edit and save their reservation until they change the conference start or
end time.
• Off
Participants cannot enter conferences earlier than the scheduled start time.
• 1 - 10, 15, 20, 25, 30
Participants can enter conferences earlier than the scheduled start time. The setting
specifies how early, in minutes, that participants can enter conferences.
Conference passcode
In a flexflow conference, Conference Passcode allows for an additional passcode that
participants must enter on their telephone keypad to join the flexflow conference. A moderator
creates the passcode using DTMF commands when starting the conference. Conferencing
does not save the passcode after the conference ends. This parameter does not apply to
regular conferences, which are sometimes called scan conferences.
Conference settings
Using the Conference Settings section, you can configure a large number of settings for
conferences, such as how long to retain conference records and the number of available lines
for on-demand conferences. These values are global values.
Using the Conference Settings section, you can configure Conferencing to play a tone, a voice
message, or both to notify participants of conference events, provide instructions for
conference functions, and announce how much time is left in a conference.
• If you select Tone, Conferencing sounds the currently defined tone to indicate a condition.
• If you select Message, Conferencing plays a preassigned voice message (msg nnn) to
indicate a condition.
• If you select Both, Conferencing sounds the tone and plays a preassigned voice message
to indicate a condition.
Tip:
Avaya recommends using Tone or Both when an immediate warning is required. The
Message setting could delay the warning message if all annunciators are busy when the
condition requiring the warning occurs. The settings apply to every conference supported
by Conferencing. You do not have to reboot the system after changing settings. You can

also configure entry and exit tones on a per-conference basis using any of the Conferencing
booking applications.
Related topics:
Scan time on page 126
Scan attempts on page 126
Auto hang-up on page 127
Warning tones on page 127
Originator dial out on page 127
Automatic security codes on page 128
Conference retention on page 128
On demand percentage on page 128
Conf name required on page 129
ODO messages on page 129
Security on message on page 130
Security off message on page 130
Conference entry message on page 130
Conference exit message on page 130
Security error 1 and 2 message on page 130
Security error 3 message on page 130
PIN code error 1 and 2 messages on page 130
PIN code error 3 message on page 131
Termination warning (15-1 min) messages on page 131
Termination now message on page 131
Scan time
Scan Time represents the number of seconds (5 to 20) that Conferencing scans for additional
passcode digits after a participant enters the first digit. The default is 20 seconds. Avaya
recommends adjusting this parameter to accommodate the longest passcode on your system.
This parameter applies to blast dials only. In a blast dial, the called party must acknowledge
the call using a DTMF command within a configurable time. This step ensures that
Conferencing quickly disconnects calls that are answered by voicemail.
Scan attempts
Scan Attempts specifies the number of times that Conferencing prompts for a passcode. The
possible values are 1, 2, or 3 times. The default value is 3.

Conference features
Auto hang-up
Auto Hang-Up specifies whether Conferencing disconnects all lines when the conference
duration expires. This feature is especially important in a deployment in which there are no
operators. Another parameter, the Auto Extend Duration parameter enables moderators to
extend their conferences up to 100 minutes beyond the specified end time. By default, Auto
Hang-Up is not enabled.
• If you enable Auto Hang-Up:
Conferencing disconnects all lines when a conference duration expires. All lines become
immediately available.
• If you do not enable Auto Hang-Up:
Conferencing does not automatically disconnect all lines.
Warning tones
Warning Tones specifies whether Conferencing plays warning tones to remind participants that
conference time is about to expire. By default, Warning Tones are not enabled.
• If you enable Warning Tones:
Conferencing plays warning tones before disconnecting conference lines.
• If you do not able Warning Tones:
Conferencing does not play warning tones before disconnecting conference lines.
Originator dial out

Originator Dial Out defines whether moderators can use their telephones to access an open
line for dial out and add participants to an active unattended conference. This feature is useful
for contacting participants who cannot dial into the conference. This setting only applies to
flexflow conferences. A flexflow conference is a specific type of conference. In flexflow
conferences, all call routing is based on the conferee passcode. In addition to the conferee
passcode, moderators enter a moderator passcode, which grants access to a moderator-
specific menu.
• Disabled
Moderators cannot dial out of secured or unsecured conferences.
• Unsecured

Unattended moderators of unsecured conferences can access free lines for dial out, if
sufficient channels are available based on the conference reservation.
• All
Moderators can dial out for both secured and unsecured conferences.
Automatic security codes

Automatic Security Codes specifies whether Conferencing automatically assigns security
codes to conferences. By default Automatic Security Codes are disabled. The values for this
parameter are:
• The number of digits for the code, between 7 and 16
Conferencing automatically assigns both conferee and moderator passcodes to a
conference when it is created. For example, if you enter 7, Meeting Exchange assigns
unique 7-digit passcodes to conferences. Operators and moderators can modify the
passcodes that Conferencing assigns.
• Disabled
Conferee and moderator passcode fields remain blank. Operators and moderators must
specify codes for conferences.
Conference retention
Conference Retention sets the number of weeks that Conferencing retains conference records.
The default value is 52 weeks.
• 1 to 52
The number of the most recent weeks for which you want to retain conference records.
For example, if you want to retain conference records from the last ten weeks, enter 10
for this parameter.
•0
Do not retain any records expired as of midnight of the previous day.
On demand percentage
On Demand Pct % specifies the percentage of Conferencing telephone lines or ports available
for on-demand conferences. On-demand conferences are unattended conferences that can
be convened on an ad hoc, first-come, first-served basis. The remaining percentage of
Conferencing capacity is designated for regularly scheduled conferences.

Conference features
On-demand conferences are also known as demand conferences. Each instance of an on-
demand conference requires no additional scheduling. Participants can access the on-
demand conference provided they have the appropriate telephone number and passcodes.
operators or moderators book a scheduled conference, Conferencing reserves system
resources to cater for the duration and size of the conference.
It is important to take account of the Conferencing usage pattern when assigning the allocation
of ports for scheduled and on-demand conferences. For example, consider the following
scenario: If the customer buys a 500 port license, they have 500 ports available for allocation to
either scheduled or on-demand conferences. If you set On-Demand Pct (%)=0, all available
ports are available for scheduled conferences only. In this configuration, there is no on-
demand capability and Conferencing cannot cater for on-demand conferences. However, if
you set On-Demand Pct (%)=100, all available ports are available for on-demand conferences
only. In this configuration, there is no scheduled conference capability and Conferencing
cannot cater for scheduled conferences.
A related parameter is the Overbook Percent parameter.
Related topics:
User access on page 310
Conf name required

Conf. Name Required specifies whether Conferencing requires a conference name for each
conference. Operators and moderators provide conference names when they schedule
conferences.
• If you select Conf. Name Required:
Conferencing requires a conference name for each conference.
• If you do not select Conf. Name Required:
Conferencing does not require a conference name.
ODO messages
Conferencing plays this tone/message when a moderator attempts to dial out to another
telephone line during a conference but Conferencing is unable to accommodate the request.

Security on message
Conferencing plays this tone/message when an operator or moderator locks a conference.
Security off message

Conferencing plays this tone/message when an operator or moderator unlocks a conference.
Conference entry message

Conferencing plays this tone/message when a participant enters the conference.
Conference exit message

Conferencing plays this tone/message when a participant leaves the conference.
Security error 1 and 2 message

Conferencing plays this tone/message when a participant enters an invalid conference
passcode.
Security error 3 message

Conferencing plays this tone/message when a participant enters an invalid conference
passcode and Conferencing places them in the queue for operator assistance.
PIN code error 1 and 2 messages

Conferencing plays this tone/message when a participant enters an invalid PIN code.

Conference features
PIN code error 3 message

Conferencing plays this tone/message when a participant enters an invalid PIN code and
Conferencing places them in the queue for operator assistance.
Termination warning (15-1 min) messages

Conferencing plays this tone/message at configurable intervals to indicate that the conference
is due to end soon.
Termination now message

Conferencing plays this tone/message when the conference ends.
Conference error behavior

The Conference Error Behavior settings enable you to configure the response of the
Conferencing server to a number of situations, such as when there are no more telephone
lines available when a participant attempts to enter a conference.
Related topics:
Invalid code on page 131
Timeout on page 132
Conference secured on page 132
Max lines reached on page 132
Invalid time of day on page 133
Invalid code
Invalid Code specifies the Conferencing response to participants who enter an invalid
passcode. The Scan Time parameter specifies the allowed time. The default value of Invalid
Code is ENTER.
• ENTER
Conferencing places the participant in the Enter conference to wait for operator
assistance.
• HANG-UP

Conferencing disconnects the caller.
Timeout
Timeout specifies the Conferencing response to participants who do not enter the digits within
the time allowed. The Scan Time parameter specifies the allowed time. The default value of
Timeout is ENTER.
• ENTER
Conferencing places the participant in the Enter conference to wait for operator
assistance.
• HANG-UP
Conference secured
Conference Secured specifies the Conferencing response to participants who enter invalid
passcodes for conferences that have been secured by a moderator. The default value is
ENTER. Moderators press *7 on their telephone keypad to secure a conference.
• ENTER
Conferencing places the participant in the Enter Conference to wait for operator
assistance.
• HANG-UP
Max lines reached

Max. Lines Reached specifies the Conferencing response to participants who enter valid
passcodes for conferences that already contain the specified maximum number of telephone
lines. The default value is ENTER. Operators specify the maximum number of lines when they
schedule a conference.
• ENTER
assistance.
• HANG-UP

Conference features
Invalid time of day

Invalid Time Of Day specifies the Conferencing response to participants who enter a valid code
at the wrong time, for example by attempting to enter a conference too early or too late. The
default value is ENTER.
• ENTER
assistance.
• HANG-UP
Conference features
The Conference Features section contains a short list of features. If you require access to
these features, you must enable them.
Related topics:
Digital conference record playback on page 133
Unattended blast on page 133
Digital conference record playback

Digital Conference Record Playback relates to the ability of Conferencing to record
conferences and make them available for playback.
• If you select Digital Conference Record Playback:
Conferencing enables the recording and playback feature.
• If you do not select Digital Conference Record Playback:
Conferencing does not enable the recording and playback feature.
Unattended blast
Unattended Blast relates to the ability of moderators to dial out to a group of potential
participants during an unattended conference call. In a typical blast dial, Conferencing dials
an entire list of phone numbers simultaneously. When potential participants answer the call,

an audio message prompts them to press specific digits on their telephones to join the
conference. The blast dial feature uses dial lists to store the information that it requires.
• If you select Unattended blast:
Moderators can dial out to a list of telephone numbers simultaneously.
• If you do not select Unattended blast:
Moderators cannot dial out to a list of telephone numbers simultaneously.
Adhoc conferencing
Conferencing provides adhoc conferencing functionality for video conferences.
Adhoc video conferencing is the instant creation of a video conference. An adhoc video
conference does not require an on-demand conference reservation. Typically, an adhoc video
conferences is created when two people, talking on the telephone, decide that they require the
participation of a further person (or people). One of the original people can press the
Conference button on their telephone keypad to instantly create an adhoc video conference
hosted by the Conferencing server. The adhoc video conferencing feature requires a video-
enabled deployment.
In a non video-enabled deployment, two people can instantly create an audio conference. As
with the adhoc video conferencing feature, they do not require an on-demand conference
reservation. One of them can press the Conference button on their telephone keypad to add
participants to their call. This type of call is hosted on Communication Manager. Currently,
Communication Manager uses the application server (bridge) for ad-hoc video conferences.
It does not use the bridge for ad-hoc audio conferences.
By allocating telephone lines, or ports, to the adhoc video conferencing feature, you may risk
resource shortages for regular conferencing. To determine how many adhoc video
conferencing ports that you require in your organization, you must consider a number of points:
• You should consider the number of users to whom you intend to allocate the adhoc video
conferencing capability. Using the Communication Manager Class of Service (COS)
setting, you can control the allocation of this feature to certain individuals.
• You should also consider the bandwidth usage patterns of each individual. For example,
using Communication Manager Priority Video Calling, you can choose to allocate a higher
bandwidth to selected VIP users. These users will each now occupy multiple ports.
• You should consider whether you intend to isolate a certain number of ports for selected
VIP users. In this scenario, you can segregate a number of ports to ensure guaranteed
port availability even during high usage peak times. This configuration limits port
availability for regular users.
• Lastly, before making a decision on the number of ad hoc video conferencing ports that
you require, it is a good idea to monitor general usage patterns over time. For example,
it may be the case that consumption patterns peak at certain times or it may be the case

Conference features
that consumption is spread over a number of timezones, creating a flatter pattern. You
can perform an audit on the CDR files to obtain this information.
Related topics:
URI pattern on page 135
Min ports available on page 135
Default conference size on page 135
URI pattern
URI Pattern is the pattern used in the construction of the unique conference Uniform Resource
Identifier used to join the conference. It is of the form sip:AdhocDirect$1@$2 where $1 is
replaced by the conference passcode and $2 is replaced by the Conferencing IP address.
Min ports available

Min Ports Available represents the minimum number of telephone lines that must be available
in order for Conferencing to create a new ad hoc conference. If you set this parameter to a
high value, you risk limiting Conferencing. The minimum ports available must be less than, or
equal to, the unreserved ports available. Unreserved ports available is the total number of ports
minus the reserved ports.
Default conference size

Default Conference Size is the default size, or number of conferees, of the new ad hoc
conferences that Conferencing creates. The default size must be less than or equal to the
minimum ports available.
Configuring conference features

Prerequisites
Before you configure conference features, ensure that you install Conferencing and assign
each of the virtual machines to the CRS virtual machine in the Components section.


4. Click Configure.
5. On the Audio Conferencing Configuration screen, click Conference Features.
8. Click Save.
Example
For example, if you wish to configure Conferencing to disconnect any caller who enters an
invalid passcode, select HANG-UP from the Invalid Code drop-down list.
Call routing
For the most part, call routing is described as part of configuring the Conferencing telephone
numbers. The remaining aspects of call routing involve dialing out from a conference to a
potential participant or a group of potential participants.
Related topics:
Dial out on page 137
Blast dial settings on page 138

Call routing
Dial out
Conferencing can dial out to a group of participants and invite them to join the conference. For
the successful operation of this feature, Conferencing must have access to a dial list or an
LDAP dial list. The parameters in this section refer to the LDAP dial list feature.
Dial list
Conferencing automatically saves the current conference participant list as a dial list using the
conference reference number as the filename. Conferencing makes this file available for
transfer to a dial list directory on the Conferencing application server. An operator or a
moderator can also associate a dial list that is currently saved in the dial list directory on the
Conferencing application server with the current conference.
LDAP dial list
Operators can also link an LDAP dial list with the conference using the CRS Front End. In
simple terms, an LDAP (Lightweight Directory Access Protocol) is a list of details about
members of an organization in a series of groups. Operators can choose one of these groups
and link it to the conference. Moderators and operators can then perform a blast dial, which
is a simultaneous dial out to the dial list. When a moderator initiates the blast dial feature in a
conference with an LDAP dial list, Conferencing calls these group members. Moderators can
initiate a blast dial by entering *92 on their telephone keypad or using the Audio Console or
Roster View interface. Operators can initiate a blast dial using Bridge Talk. During an LDAP
blast dial, Conferencing adds an international, country, and local prefix to the telephone
numbers listed in the LDAP dial list. Conferencing supports the + character in these fields.
Note:
The Standard Edition of Conferencing does not support the Bridge Talk application.
Related topics:
Country code on page 137
International prefix on page 138
Local prefix on page 138
Configuring blast dial settings on page 372
Country code
Country Code is a numeric sequence that Conferencing adds to a telephone number when a
moderator or operator uses an LDAP dial list for a blast dialout. This field accepts a maximum of
three digits. The country code identifies the country. Examples include 44, 1, 61, and so on.

International prefix
International Prefix is a numeric sequence that Conferencing adds to a telephone number when
a moderator or operator uses an LDAP dial list for a blast dialout. This field accepts a maximum
of three digits. The international prefix identifies the call as an international call. For example,
011.
Local prefix
Local Prefix is a numeric sequence that Conferencing adds to a telephone number when a
moderator or operator uses an LDAP dial list for a blast dialout. This field accepts a maximum of
three digits. The local prefix identifies an area or region within a country.
Blast dial settings

Conferencing enables operators and moderators to dial a large group of potential participants
using a single command. This feature is called a blast dial. For the successful operation of the
blast dial feature, you must create and save blast dial lists.
In a typical blast dial,Conferencing dials an entire list of phone numbers simultaneously. When
potential participants answer the call, an audio message prompts them to press specific digits
on their telephones to join the conference. The blast dial feature uses dial lists to store the
information that it requires. Each entry in the dial list includes a participant name and telephone
number. Entries can also include a company name, a question and answer (Q&A) priority and a
moderator status flag. Each list has a unique 8-character name and an optional access code.
The number of dial lists is limited only by the amount of hard drive space available on the
application server. Operators can create, modify, print, and delete dial lists using BridgeTalk.
operators can also import dial lists using CRS Front End.
When they are booking conferences, operators, using Bridge Talk or CRS Front End, can set
the blast dial feature to:
• Dial the dial list automatically as soon as a moderator enters the conference.
• Dial the dial list when the moderator presses a DTMF keypad sequence on their
telephone. This sequence is typically *92.
Using Bridge Talk, operators can also dial a single entry in a dial list. This feature is called fast
dial.
When a Blast Dial List contains a sixteen digit code containing all zeros (0000000000000000),
participants are immediately placed into a conference when the line is answered without
hearing an annunciator. If the blast dial list does not contain the sixteen zero code then the
bridge plays an annunciator message to participants when the line is answered.

Call routing
Aside from the blast dial list feature, Conferencing enables moderators to dial out to multiple
participants using another method. Using Web Portal, moderators can add participants to their
personal address book. Using Avaya Audio Console, moderators can dial out to single or
multiple participants from their address book. They can also edit and save their address book
as a .csv file. There is no direct relationship between blast dial lists stored on the application
server and the address book feature. For more information on the address book feature, see
Using Avaya Aura™ Conferencing Guide, which is available from support.avaya.com.
Note:
Related topics:
Maximum concurrent channel blast on page 139
Delay between blasts on page 139
Invalid code entered on page 139
Scan time on page 140
Call progress timeout on page 140
Configuring blast dial settings on page 372
Maximum concurrent channel blast

Maximum concurrent channel blast is the number of channels (1 to 16) that Conferencing
simultaneously dials during a blast dial. The default is eight channels. Dialing channels in
groups with a short pause between each group prevents flooding the network with calls. The
Delay Between Blasts parameter specifies the pause between blast dials.
Delay between blasts

Delay between blasts is the number of seconds (0 to 60) that Conferencing waits before dialing
the next group of channels in a blast dial. The default is two seconds.
Invalid code entered

Invalid code entered is the Conferencing response to participants who enter an invalid
passcode or participants who do not enter the digits within the time allowed. The Scan Time
parameter specifies the allowed time. There are two values. The default value is ENTER.
• ENTER

The participant is placed in the Enter Conference queue to wait for operator assistance.
• HANG-UP
The Invalid Code setting also specifies the Conferencing response to participants entering
codes for secured blast conferences. This parameter applies to coded blast dials only. In coded
blasts, the called party must acknowledge the call using a DTMF command within a
configurable time. This step ensures that Conferencing quickly disconnects calls that are
answered by voicemail.
Scan time
Scan time is the number of seconds (5 to 20) that Conferencing scans for additional passcode
digits after a participant enters the first digit. The default is 20 seconds. Avaya recommends
adjusting this parameter to accommodate the longest passcode on your system. This
parameter applies to coded blasts only. In coded blasts, the called party must acknowledge
the call using a DTMF command within a configurable time. This step ensures that
Conferencing quickly disconnects calls that are answered by voicemail.
Call progress timeout

Call progress timeout specifies what happens to lines that remain in the Call Progress (CLPG)
state after a blast dial. (Some lines may remain in the CLPG state because no one answers
the blast dial, or the participant fails to enter digits.) The default value is 0.
• 30 to 600 (seconds)
Conferencing automatically hangs up lines remaining in the CLPG state beyond the
specified time. This includes participants using rotary phones, who cannot enter DTMF
commands.
•0
There is no timeout. Lines remain in the CLPG state until an operator accesses the line
or clears or exits Blast Dial, which hangs up all lines in the CLPG state.
Avaya recommends specifying a timeout value when operators are not available to clear the
lines.

System configuration
The system configuration consists of four different sections:
• Networking
• NFS mounts
• SAL connectivity settings
• Miscellaneous
Related topics:
Networking on page 141
NFS mounts on page 145
Miscellaneous on page 148
Configuring system configuration on page 149
Networking
The Networking section lists a number of settings relating to the Conferencing media server.
recording.
Related topics:
Network type on page 141
Diff serv signalling TOS value on page 142
Diff serv media TOS value on page 142
Ethernet signalling VLAN value on page 142
Ethernet media VLAN value on page 143
Enable firewall service on page 143
Enable SIP proxies on page 143
SIP proxy configuration on page 143
Network type
Network Type represents the speed of the customer network.

When Avaya ships Conferencing to a customer site, Avaya configures it to fit to a 100 megabit,
full duplex network. This is 100BASE-TX and it is the default setting. If the customer’s network
is a gigabit network, you must change this configuration setting to 1000BASE-T. Also, if a
customer has more than 700 telephone lines with a single connection to the switch, you must
change this configuration setting. It is likely that the Conferencing server will drop calls if you
do not change the default megabit setting in a customer site with over 700 ports connected
with a single connection to the switch.
Diff serv signalling TOS value

TOS is type of service. The TOS value is a differentiated service setting for SIP IP packets.
Differentiated services attempt to guarantee quality of service on large networks, such as the
Internet. Using TOS, you can assign priority to certain traffic, such as network-critical traffic.
Diff Serv Signalling TOS Value is one of two TOS parameters. This value appears in the TOS
field of the IP packet. Avaya recommends a value of 46. This value relates to signalling traffic,
such as telephone calls to the Conferencing server.
Diff serv media TOS value

TOS is type of service. The TOS value is a differentiated service setting for SIP IP packets.
Differentiated services attempt to guarantee quality of service on large networks, such as the
Internet. Using TOS, you can assign priority to certain traffic, such as network-critical traffic.
Diff Serv Media TOS Value is one of two TOS parameters. This value appears in the TOS
field of the IP packet. Avaya recommends a value of 24. This value relates to media traffic,
such as video.
Ethernet signalling VLAN value

The Ethernet VLAN Value places restrictions on traffic flow, permitting traffic to pass among a
select group of network nodes, to the exclusion of other network nodes, based on the assigned
group membership of individual nodes or switch ports. The VLAN Value range is between 0
and 32. The default value is 0. However, the choice of an appropriate VLAN value depends on
the network being used and the type of traffic; signalling or media.
Ethernet Signalling VLAN Value is one of two VLAN parameters. This value appears in the
TOS field of the IP packet. This value relates to signalling traffic, such as telephone calls to
the Conferencing server.
Before you configure this value, you must create the actual VLANs on the Conferencing
application server. This task is technical and requires expertise.

Ethernet media VLAN value

The Ethernet VLAN Value places restrictions on traffic flow, permitting traffic to pass among a
select group of network nodes, to the exclusion of other network nodes, based on the assigned
group membership of individual nodes or switch ports. The VLAN Value range is between 0
and 32. The default value is 0. However, the choice of an appropriate VLAN value depends on
the network being used and the type of traffic; signalling or media.
Ethernet Media VLAN Value is one of two VLAN parameters. This value appears in the TOS
field of the IP packet. This value relates to media traffic, such as video.
Enable firewall service

If the customer deployment includes a firewall, you must select Enable Firewall Service. It is
selected by default.
Enable SIP proxies

You can connect the Conferencing infrastructure to Communication Manager by way of a SIP
Enablement Server (SES) proxy. If you wish to enable this configuration, select the Enable
SIP proxies field.
SIP proxy configuration

In a deployment of Conferencing with an SES proxy, the SES proxy acts as a gateway between
Communication Manager and Conferencing. In this scenario, any calls to Conferencing route
through the Communication Manager server, then the SES proxy server, before terminating
on the Conferencing application server. Communication Manager handles all H.323 and PSTN
calls. Typically, Communication Manager does not handle SIP calls. The SES proxy handles
SIP calls. If your deployment uses some SIP endpoints, you must perform some additional
configuration steps.
The configuration settings are listed here.
Field Description Syntax

SIP Proxy The IP address of the SES proxy server sip:<SES proxy IP address>
URI that you intend to use.

Field Description Syntax

Contact URI The address of the Conferencing DDI/ sip:<DNIS>@<Conferencing IP
DNIS that you wish to allocate to the address>
SES proxy server.
To URI The address of the SES proxy DNIS that sip:<DNIS>@<SES proxy IP
corresponds with the Conferencing address>
DNIS that you entered in the Contact
URI field.
From URI The address of the SES proxy DNIS that sip:<DNIS>@<SES proxy IP
corresponds with the Conferencing address>
DNIS that you entered in the Contact
URI field.
Username The account username which XXXX
Conferencing will use to register with the
SES proxy server.
Password The account password which XXXX
Conferencing will use to register with the
SES proxy server.
Refresh Time The refresh time should be 1800, as you 1800
configured in the Session refresh timer
field. To locate the Session refresh
timer field, navigate to Elements >
Conferencing > Media >
Configuration > SIP.
Related topics:
Configuring SIP proxies on page 144
Configuring SIP proxies

Prerequisites
Before you configure SIP proxies using the Conferencing Manager interface, you must deploy
and configure an SES proxy server in your network.
The purpose of this task is to enable Conferencing to route SIP calls via an SES proxy.

4. Click Configure.

5. On the Audio Conferencing Configuration screen, click System Config.

6. In the Networking section, click Edit and then New to display the SIP settings.
7. Enter the SIP details as they apply to your deployment.
8. Click Save.
Next steps
Now you can configure further settings, such as NFS mounts.
NFS mounts
Typically, customers use an external Network File System (NFS) server to store conference
recordings. An external NFS server offers more space for recordings than an NFS server that
resides on the application server. An NFS server is a key component of the Conferencing
solution. You should always consider the robustness of connections and hardware. You should
also consider the NFS server when planning outages that impact the Conferencing experience.
Each Conferencing server has two LAN NIC connections that you can use to bind to virtual
Linux interface bond0:
• Eth0
• Eth2 or Eth 3
Eth1 is always the services port.
Avaya recommends that you connect all systems to the customer LAN infrastructure with
resilience in case of unforeseen outages between the NFS client and the NFS server which
disrupt conferencing. Also, ensure that you connect the NFS server into the same LAN
switching infrastructure as the Conferencing solution
The NFS server, which the customer provides, should have similar capabilities to the
application server. It should be dual-homed and be able to detect and switch over without
interruption. Ideally, you should hard wire the NFS server into the same LAN switching
infrastructure as the Conferencing server.

Some guidelines for NFS server implementation

• Add multiple NICs to the NFS server to allow resilient network connectivity to the LAN
infrastructure. Configure these NICs to use active and standby type connections.
• Install dual power supplies into the NFS server. Deliver the feeds from different circuits
or, if a UPS is present, deliver the feed by both the UPS and the building mains.
• Implement RAID on the NFS server.
• Configure alarming on the NFS server and ensure that the traps are sent to your central
management system, if deployed.
• Align maintenance windows on the NFS server with Conferencing maintenance windows.
• Do not modify firewall rules on any of the servers while production traffic is running.
Related topics:
NFS server IP address
Configuring the external recording server (NFS) on page 146
Configuring the external recording server (NFS)

Prerequisites
Before you configure an external conference recording server using the Conferencing Manager
interface, you must deploy and configure an NFS server in your network.
The purpose of this task is to make Conferencing aware of an external server for storing
recordings. These steps also describe the configuration tasks on the external NFS server-side.

4. Click Configure.
6. In the NFS Mounts section, enter the IP address of the external conference
recording server in the Conference Recording Mount Server IP Address field.
7. Click Save.

9. Access the NFS server box.
You can use PuTTY to access the NFS server box:
a. Download PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/putty/
download.html.
b. Start PuTTY.
c. On the PuTTY dialog, enter the IP address of the NFS server and click Open.
10. Create a directory called /var/usr3/confrp.
11. Edit the /etc/hosts file to add the Conferencing application server.
12. Add the following line to the /etc/exports file:
/var/ <name of application server>(rw, async, no_root_squash)
The NFS server is now configured.
Next steps
Now you can configure further settings, such as the notification service. It is also a good idea to
verify the operation of the NFS server.

Secure Access Link (SAL) is an Avaya serviceability solution for support and remote
management of a variety of devices and products. SAL provides remote access and alarm
reception capabilities. SAL uses the existing Internet connectivity of a customer to facilitate
remote support from Avaya. All communication is outbound from the environment of the
customer over port 443, and uses encapsulated Hypertext Transfer Protocol Secure (HTTPS).
The Conferencing logs and alarms are now generated using the Avaya Secure Access Link
(SAL) infrastructure.
Related topics:
Obtaining the three pieces of information on page 105
Configuring logs and alarms on page 106

Miscellaneous
The Miscellaneous section lists the Flexible Digital Auxiliary Port Interface (FDAPI) resources.
If you are familiar with previous version of Conferencing, the FDAPI settings were located in
the System Maintenance Main Menu > FDAPI Configuration section.
Related topics:
Flex DAPI configuration on page 148
Flex DAPI configuration

On the Conferencing server, you must configure Flexible Digital Auxiliary Port Interface
(FDAPI) resources. An FDAPI resource is a permanant link between the Conferencing server
and an operator or an API connection. You must configure an FDAPI resource for each operator
in your deployment. You need an FDAPI resource for each concurrent operator.
You must also configure an FDAPI resource for each API connection in your deployment. Many
components of Conferencing, such as the Client Registration Server, the Web Portal, or Bridge
Talk, connect to the Conferencing server using an API connection. You need an FDAPI
resource for every application which uses an API connection to communicate with the
FDAPI resources are similar, in concept, to telephone lines. FDAPI resources enable operators
to manage the Conferencing server, record conferences, play music files, and so on. Each
FDAPI resource reduces the number of available conference telephone lines (ports). For
example, if a customer purchases 500 ports and requires 10 FDAPI resources, the number of
ports available for conferencing is 490.
In a Time Division Multiplexing (TDM) deployment, FDAPI resources are physical lines. In a
Voice over IP (VoIP) deployment, FDAPI resources are virtual lines. In the Flex DAPI
Configuration section, you can enter the number of lines that you require for operators. You
can also enter the number of lines that you require for playing music, facilitating the recording
and playback feature, and providing link lines for multisite conferences.
Related topics:
Operators on page 148
Music on page 149
Number of annunciator channels on page 149
Operators
Operators schedule and attend conferences. Operators also manage company and client
accounts. Operators use Bridge Talk and the Client Registation Server (CRS) Front End to
perform their duties.
You must configure a Flexible Digital Auxiliary Port Interface (FDAPI) resource for each
operator in your deployment. You need an FDAPI resource for each concurrent operator. For

example, if there are five operators on duty simultaneously, you must configure five FDAPI
operator resources.
Music
The Conferencing product has music included with it. For example, participants who are on
hold hear the Conferencing music tracks. These are default music tracks. In some
deployments, you might want to play a certain piece of music, such as a company
advertisement jingle. Any customized music of this kind is stored on an external server. You
must configure a Flexible Digital Auxiliary Port Interface (FDAPI) resource for each music track
on an external server. In your deployment. You need an FDAPI resource for each concurrent
external music track that you want to play.
Number of annunciator channels

Conferencing uses annunciator channels for playing greetings and in-conference
announcements as well as for recording and playing back conferences. Essentially,
Conferencing uses annunciator channels for any sound data going to or from the internal hard-
disk. This setting sets the maximum number of those resources that Conferencing uses at any
one time. In an in-service deployment, the record and playback features hold the annunciator
channel resource for long periods of time. For this reason, the record and playback usage is
capped at a sub-set (70%) of the value entered here.
Conferencing reserves 30% for the playing of regular audio messages during conferences.
This metric aims to balance the requirements of the regular conference audio messages and
the recording and playback feature. This parameter represents the number of overall
annunciator channels. The platform limit is 1500. This is also the default value.
Configuring system configuration

Prerequisites
Before you configure system configuration settings, ensure that you install Conferencing and
assign each of the virtual machines to the CRS virtual machine in the Components section.


4. Click Configure.
8. Click Save.
Example
For example, if your network is a gigabit network, you must change the Network Type from
the default value of 100BASE-TX to 1000BASE-TX.
General configuration
The general configuration consists of eight different sections:
• General
• DTMF controls
• Recording and playback
• Logging
• Flex settings
• Billing
• RAI configuration
• Port pool usage thresholds
Related topics:
General on page 151
DTMF controls on page 157
Recording and playback on page 168
Logging on page 170

Flex settings on page 172

Billing on page 174
RAI configuration on page 175
Port pool usage thresholds on page 176
Configuring general configuration settings on page 178
General
The General section includes many configuration parameters relating to the conference
recording feature. It also includes a number of settings in relation to DTMF suppression.
Related topics:
Bridge ID number on page 151
Licensed audio ports on page 152
Playback roll call on page 152
Automatic record all on page 153
Secure blocks record on page 153
PIN mode on page 153
Flex leader code on page 154
DTMF regeneration on page 154
DTMF passthrough on page 155
Billing code length on page 155
System alert enabled on page 155
System alert message on page 156
Playback small jump on page 156
Playback medium jump on page 156
Playback long jump on page 156
Bridge ID number
This number uniquely identifies the Conferencing application server, or bridge. The
Conferencing recording feature uses this number for all recording filenames. If Conferencing
automatically names a recording, it uses the following conventions:
<Conference confirmation number><Bridge ID number>XXXX
The value of XXXX grows sequentially, as follows:
• If the operator or moderator stops and then restarts recording during the conference,
Conferencing increments the value of XXXX.
• Similarly, if all participants leave the conference and later re-join, Conferencing
increments the value of XXXX. As an example, this scenario occurs when moderators

use their on-demand conference for a weekly meeting. Conferencing views this weekly
recurring meeting as multiple instances of a single conference.
If your deployment consists of a number of application servers, called a multicabinet
environment, there are implications for the automatic naming convention. Conferencing
encodes all recording filenames on a given bridge with the bridge number. This fact can be
used to keep recordings from difference bridges from having name conflicts if customers copy
them to a common playback device. Conversely, if customers can guarantee that name
conflicts will not occur due to other factors, such as configuring confirmation numbers to be
unique across all recording source bridges, then customers can set the Bridge ID Number
values to be the same on all bridges. In this scenario, users can play multi-sourced files from
a single-source playback. This scenario only operates successfully in a deployment that
includes a CRS server. If there is no CRS server, you must set the Bridge ID Number to a
unique value on all servers. Avaya recommends consulting with your Avaya Support
Representative for advice if your deployment includes a complex server environment. As an
aside, operators and moderators can manually specify the filename of a conference recording.
They can enter almost any digit string for this purpose but it must not start with zero. Automatic
filenames always start with zero. This filename forms the XXXX portion of the complete
recording filename:
Note:
In the Standard Edition of Conferencing, there is no support for a multicabinet environment.
The Enterprise Edition of Conferencing supports multicabinet.
Licensed audio ports

The Licensed audio ports represents the number of separate, licensed Conferencing telephone
lines in the deployment.
Playback roll call

Playback roll call identifies whether Conferencing records users' names when they are in the
playback call flow. The playback call flow is the term used to describe the user experience of
listening back to a conference recording. By default, playback roll call is not selected.
• If you do not select Playback roll call:
Conferencing does not prompt the user for their name during the playback call flow.
• If you select Playback roll call:
Conferencing prompts the user for their name during the playback call flow. Conferencing
adds the recording filename to the roll call file and stores it in /usr2/pkbrosters.

Automatic record all

Automatic record all identifies whether Conferencing records all conferences, regardless of
the per-reservation setting. The default value is OFF.
• If you select OFF:
Conferencing does not automatically record all conferences.
• If you select ON:
Conferencing automatically records all conferences.
As an aside, at reservation time, operators and moderators can enable two settings relating
to recording: Operators, using the CRS Front End or Bridge Talk, and moderators, using the
Web Portal, can enable the automatic recording of a conference. If they enable this feature,
Conferencing automatically starts recording the conference as soon as participants begin to
talk.
Operators, using the CRS Front End or Bridge Talk, and moderators, using the Web Portal,
can also enable moderator control of the recording feature. If they enable this feature,
moderators can start and stop the conference recording. The default value is ON. For more
information on creating reservations using CRS Front End, Bridge Talk, or the Web Portal, see
Using Avaya Aura™ Conferencing Guide, which is available from support.avaya.com The value
of Automatic Record All supersedes any reservation-specific settings.
Secure blocks record

Secure blocks record identifies whether Conferencing allows conference recording when a
moderator secures, or locks, the conference. By default, Secure blocks record is ON.
If a moderator locks a conference, by pressing *7 on their telephone keypad,
Conferencing terminates any in-progress recording and does not allow the moderator to
begin recording.
If a moderator locks a conference, Conferencing continues any in-progress recording and
allows the moderator to begin recording.
PIN mode
PIN mode specifies the PIN code requirements for unattended conferences scheduled on the
Conferencing system. The default value is Optional.

• If you select Optional:

Callers do not have to enter a PIN code, however they may enter one. They must press
the pound key (#) in response to a PIN code prompt.
• If you select Required:
Callers are required to enter a PIN code in response to a PIN code prompt. The PIN code
does not have to be unique per participant, for example one PIN code per conference.
• If you select Required and must be unique:
Callers are required to enter unique PIN codes (a unique PIN code for each caller).
The PIN mode option is not available if PIN codes are not installed.
Flex leader code

The Flex Leader Code provides the option for a moderator to join a flex flow conference when
they enter a single passcode instead of the default Flex flow requirement of two passcodes.
• If Flex Leader Code is ON
A moderator joins conference upon entry of one code.
• If Flex Leader Code is OFF
A moderator must enter two codes to join a flex flow conference.
DTMF regeneration
Each time a conference participant enters a dual tone multifrequency (DTMF) keypad
sequence, their telephone emits a tone. Under normal circumstances, Conferencing
participants do not hear DTMF tones. This is called clamping. In certain circumstances,
operators may wish to allow the DTMF tones to play to the conference. Operators may also
request that Conferencing ’cleans’ the tones before playing them into the conference to remove
any distortion.
This parameter enables the display of a drop-down menu on Bridge Talk called DTMF
Regeneration, which has three options:
• System
This value enables all conferences to hear the regenerated DTMF tones, by default.
• ON
This value enables the regenerated DTMF tones for the particular conference.
• OFF

This value ensures that participant do not hear the DTMF tones.
The DTMF Passthrough parameter enables a related drop-down menu. Both options only
operate for in-band DTMF. You cannot enable both simultaneously.
DTMF passthrough
Each time a conference participant enters a dual tone multifrequency (DTMF) keypad
sequence, their telephone emits a tone. Under normal circumstances, Conferencing
participants do not hear DTMF tones. This is called clamping. In certain circumstances,
operators may wish to allow the DTMF tones to play to the conference.
This parameter enables the display of a drop-down menu on Bridge Talk called DTMF Pass
Through, which has three options:
• System
This value enables all conferences to hear the DTMF tones, by default.
• ON
This value enables the DTMF tones for the particular conference.
• OFF
This value ensures that participants do not hear the DTMF tones.
The drop-down menu is on the Bridge Talk Schedule Conference dialog. The DTMF
Regeneration parameter enables a related drop-down menu. Both options only operate for
in-band DTMF. You cannot enable both simultaneously.
Billing code length

The Billing Code Length parameter specifies the length of the billing code, which moderators
must enter using their DTMF keypad.
System alert enabled

System alert enabled determines if Conferencing should play a message to all conferences.
If enabled, Conferencing plays the message before any per-conference messages. The default
value is OFF.

Conferencing plays a message to all conferences.

Conferencing does not play a message to all conferences.
Related topics:
System alert message

If you set System alert enabled to ON, you must specify which message that Conferencing
should play to all conferences. There are 2000 message slots in each prompt set, so valid
values for this field are 1-2000.
Related topics:
Playback small jump

During playback, users can move through the conference recording using rewind and forward
options. By default, to rewind a playback by a short amount, users press 1 on their telephone
keypad. By default, to forward a playback by a short amount, users press 3 on their telephone
keypad. This parameter sets the number of seconds for that short amount.
Playback medium jump

options. By default, to rewind a playback by a medium amount, users press 4 on their telephone
keypad. By default, to forward a playback by a medium amount, users press 6 on their
telephone keypad. This parameter sets the number of seconds for that medium amount.
Playback long jump

options. By default, to rewind a playback by a long amount, users press 7 on their telephone
keypad. By default, to forward a playback by a long amount, users press 9 on their telephone
keypad. This parameter sets the number of seconds for that long amount.

DTMF controls
Dual Tone Multi Frequency (DTMF) Controls refer to the extent to which moderators can
change conference properties using their telephone keypad. Moderators can use their
telephone to enter keypad sequences which influence conference behavior.
Conferencing Manager lists the default keypad codes which participants enter on their
telephone keypad to attend and participate in regular conferences. It also lists the default
keypad codes which participants enter to listen to conference recordings.
When attending and participating in conferences, moderators can access a larger number of
options than conferees. When listening to conference recordings, moderators and conferees
have access to the same options.
For the purposes of DTMF mappings, Conferencing effectively supports two different
conference types. These conference types are commonly called scan conferences and flex
flow conferences. The conference recording playback options are the same for both
conference types. For flex flow conferences, moderators are often called leaders.
Related topics:
Scan flow DTMF mapping on page 157
Flex flow in conference DTMF mapping on page 161
Flex flow account management DTMF mapping on page 164
Configuring mapping on page 165
Ignore DTMF commands on page 166
Moderator conference hangup on page 166
Moderator lecture mode on page 166
Sub-conferencing on page 166
Self-mute on page 167
DTMF acknowledge on page 167
Scan flow DTMF mapping

The scan conference DTMF sequence uses the sFlowDigits.reg configuration file. It is
important to note that some mappings are not configurable. For more information, contact your
Avaya Support Representative. If you make any changes to the default DTMF mappings, you
must ensure that you also configure the audio prompt messages to play the correct message.
Typically, scan conferences are regular conferences in which the participants enter a
moderator passcode or a conferee passcode on their telephone keypad to access the
conference.

Moderator commands
Function name Press... To...

reqHelp *0 Request help by entering the Help Requests queue.
As a system administrator, you can configure this feature to
play a message, to connect to an operator with audiopath
capabilities, or to connect to an assistant without audiopath
capabilities.
countWithRoster *8 Play the number of conference participants, followed by a
roll call of conference participants when used in conjunction
with the name record/playback feature. If there is no roll call,
this command simply plays the number of conference
participants.
• If there is no roll call, Conferencing always plays this
message as a private message.
• When you enable roll call:
If a conferee presses *8, Conferencing plays this
If a moderator presses *8, Conferencing can play this
message as a private message or as a conference
message.
odoInit *1 Initiate a dial out.

Once a moderator enters *1 on their telephone keypad, the
moderator will be placed into a self-explanatory Interactive
Voice Response (IVR) sequence for requesting, collecting,
and dialing a telephone number. Once the telephone call
has been made, Conferencing makes the following options
available:
• *2 Returns both moderator and caller to the conference.
• *3 Returns moderator to the conference and hangs up the
called party.
recordingToggle *2 Enter the conference recording menu.

If Conferencing is not currently recording the conference, it
plays the options for starting a recording session.
If Conferencing is currently recording the conference, it
plays the following options:
• 1 Ends the recording.
• 2 Toggles the pause/resume feature.
• 3 Replays a conference recording file number.
• * Exits the menu.
playbackToggle *3 Enter a playback menu, which enables the moderator to

play a conference recording to the entire conference.


Conferencing contains a newer method for playing a
conference recording. This older DTMF command is a
legacy feature, which plays the conference recording to the
entire conference. Additionally, this older playback feature
does not support pause and resume.
lectureToggle *5 Turn Lecture on or off.
Conferencing places all participant lines in mute.
Participants cannot unmute their individual lines while in
lecture mode.
selfMuteToggle *6 Mute or unmute the telephone line.
muteAllToggle *96 Turn Mute All on or off.
Conferencing mutes all participant lines in the conference.
Participants can unmute their individual lines while in mute
all mode.
secureToggle *7 Turn conference security on or off.
endConfNow ## End the conference.
reqBillingCode *91 Enter a billing code.
Conferencing plays a message which prompts the
moderator for a billing code for the conference.
uBlast *92 Trigger an unattended, automatic Blast Dial or reblast.
For the successful operation of this command, the operator,
using Bridge Talk or CRS Front End, or the moderator, using
Web Portal, must enable Blast Dial for the conference.
subConfCntrl *93 Start a subconference or join a subconference.
Once a moderator enters *93 on their telephone keypad,
Conferencing makes the following options available:
• 1-9 Places the moderator into a subconference room. For
example, if a moderator presses 7, Conferencing places
them into subconference number 7.
• 0 Returns the moderator to the main conference.
• # Plays a warning message into all subconferences to
indicate that participants will be rejoining the main
conference shortly. After a few moments, Conferencing
transfers all lines back to the main conference.
• If the moderator presses the current subconference
number, Conferencing ignores the command.
• * Does nothing. It exits this menu.
reqRecordingName *94 Replay the last or current conference recording file number.
enterWebID *95 Associate a Web conference with the audio conference.
moHangToggle *98 Toggle moderator hang-up.


This sequence turns on or turns off the moderator hang-
up option. If a conference has moderator hang-up enabled,
Conferencing closes the conference when the last
moderator leaves the conference. If a conference does not
have moderator hang-up enabled, Conferencing does not
close the conference when the last moderator leaves the
conference.
qaRem 1 Leave a Q&A queue.
Conferencing places moderators in the Q&A queue, by
default.
welcome #2 Record a personal greeting for the conference.
Once a moderator enters #2 on their telephone keypad,
• 1 Records a greeting.
• 2 Plays the current greeting.
• 3 Deletes the current greeting.
Conferee commands

reqHelp *0 Request help by entering the Help Requests queue.
As a system administrator, you can configure this feature to
play a message, to connect to an operator with audiopath
capabilities, or to connect to an assistant without audiopath
capabilities.
selfMuteToggle *6 Mute or unmute the telephone line.
countWithRoster *8 Play the number of conference participants, followed by a roll
call of conference participants when used in conjunction with
the name record/playback feature. If there is no roll call, this
command simply plays the number of conference participants.
• If there is no roll call, Conferencing always plays this
• When you enable roll call:
If a conferee presses *8, Conferencing plays this message
as a private message.
If a moderator presses *8, Conferencing can play this
message as a private message or as a conference message.
subConfCntrl *93 Start a subconference or join a subconference.

Once a conferee enters *93 on their telephone keypad,

• 1-9 Places the conferee into a subconference room. For

example, if a conferee presses 7, Conferencing places them
into subconference number 7.
• 0 Returns the conferee to the main conference
• If the conferee presses the current subconference number,
Conferencing ignores the command.
qaAdd *1 Enter a Q&A queue.

Once a conferee enters *1 on their telephone keypad,
Conferencing makes the following option available:
1 removes the conferee from the Q&A queue.
Flex flow in conference DTMF mapping

The flexflow conference DTMF sequence uses the flexflow_cfg.reg configuration file. It is
important to note that some mappings are not configurable. For more information, contact your
Avaya Support Representative.
Typically, flex flow conferences are conferences in which all participants enter a conferee
passcode on their telephone keypad. After entering a conferee passcode, moderators can
enter a moderator passcode to promote their status.
If you make any changes to the default mappings, a program called /usr/dcb/bin/flexdigits is a
useful utility to test your customized flexflow_cfg.reg before you place the new settings into a
live environment. To test your configuration changes, enter the file name after the utility.
For example: usr/dcb/bin/flexdigits testFlexFlow_cfg.reg
This program parses the input file and reports any errors.
If you make any changes to the default DTMF mappings, you must ensure that you also
configure the audio prompt messages to play the correct message.

OperatorConference *0 Display the conference in the help request queue.
Once the conference enters this queue, an operator,
using Bridge Talk can see that the conference
requires assistance.
This feature requires operator support.
OperatorIndividual 00 Display an individual telephone line in the help
request queue.
Once moderators enter this queue, an operator, using
Bridge Talk can see that they require assistance.
This feature requires operator support.


DialOut *1 Initiate a dial out.
Once a moderator enters *1 on their telephone
keypad, the moderator is placed into a self-
explanatory Interactive Voice Response (IVR)
sequence for requesting, collecting, and dialing a
telephone number. Once the telephone call has been
made, Meeting Exchange makes the following
options available:
• *1 Return to the conference with the called party.
• *2 Return to the conference without the called party.
• *3 Deposit the called party into the conference and
stay in the IVR sequence to make another call.
• *4 Hang-up that call and and stay in the IVR
sequence to make another call.
ConferenceRecord *2 Enter the conference recording menu. If

Conferencing is not currently recording the
conference, it plays the options for starting a
recording session. If Conferencing is currently
recording the conference, it plays the following
options:
• 1 Ends the recording.
• 2 Toggles the pause/resume feature.
• 3 Replays a conference recording file number.
• * Exits the menu.
ChangeEntryExit *3 Enter an IVR sequence to change entry and exit

tones and announcements.
LockConference *4 Turn conference security on. This sequence locks the
conference.
UnlockConference *5 Turn conference security off. This sequence unlocks
the conference.
MuteIndividual *6 Mute the telephone line.
UnmuteIndividual *7 Unmute the telephone line.
ConferenceContinuation *8 Toggle between two options, as follows:
• The conference will continue after the moderator
leaves.
• The conference will end when the moderator
leaves.
This option is similar to the moderator hang-up option
in the scan conference call flow.


PrivateRollCall *9 Play an available list of participant names into the
telephone line.
MuteGroup ## Turn Mute All on.
Conferencing mutes all conferee lines in the
conference. Conferees can unmute their individual
lines while in mute all mode.
UnmuteGroup 99 Turn Mute All off.
Conferencing unmutes all conferee lines in the
conference.
ParticipantCount *# Play the number of participants.
ListKeypadCommands ** Play a menu which lists the available DTMF
telephone keypad sequences and their associated
functions.
DTMFConferenceHangup 77 End the conference.
This DTMF sequence ends the conference if a
parameter called DTMF Conference Hang Up is
configured on the Conferencing application server.
GoToSubParent 93 Start a subconference or join a subconference.
Once a moderator enters *93 on their telephone
keypad, Conferencing makes the following options
available:
• 1-9 Places the moderator into a subconference
room. For example, if a moderator presses 7,
Conferencing places them into subconference
number 7.
• 0 Returns the moderator to the main conference.
• # Plays a warning message into all subconferences
to indicate that participants will be rejoining the
main conference shortly. After a few moments,
Conferencing transfers all lines back to the main
conference.
• * Does nothing. It exits this menu.
• If the moderator presses the current subconference
number, Conferencing ignores the command.
PlayRecordFileNumber 94 Replay the last or current conference recording file

number.
EnterWebId 95 Associate a Web conference with the audio
conference.
ConferenceWelcome #2 Record a personal greeting for the conference. Once
a moderator enters #2 on their telephone keypad,

• 1 Records a greeting.
• 2 Plays the current greeting.
• 3 Deletes the current greeting.
2 At the start of a conference, after the moderator

enters their conferee passcode and then upgrades
their status with a moderator passcode, they can
press 2 to enter an IVR sequence that enables them
to make changes to their conference properties. All
changes made to the default conference properties
will apply to active and future conferences with the
exception of quick start.
Once in this menu: Press:
• 1 to enter an IVR sequence to change the
moderator, or leader, passcode.
• 2 to change the conference entry and exit tones.
• 3 to change the settings in relation to quick start,
which relates to whether the conference begins
when the first conferee arrives or when the first
moderator arrives.
• 4 to change the settings in relation to conference
closure.
• 9 to hear an explanation of each of these
conference properties.
Flex flow account management DTMF mapping

At the start of a conference, after the moderator enters their conferee passcode and then
upgrades their status with a moderator passcode, they can press 2 to enter an IVR sequence
that enables them to make changes to their conference properties. All changes made to the
default conference properties will apply to active and future conferences with the exception of
quick start. Once in this menu, the following values apply.

ChangeLeaderPIN 1 Enter an IVR sequence to change the moderator, or leader,
passcode.
NameRecTones 2 Change the conference entry and exit tones.
QuickStart 3 Change the settings in relation to quick start, which relates
to whether the conference begins when the first conferee
arrives or when the first moderator arrives.


AutoContinuation 4 Change the settings in relation to conference closure.
Describe 9 Hear an explanation of each of these conference properties.
Configuring mapping
Prerequisites
Before you configure DTMF mapping, you must install Conferencing and configure connectivity
between the virtual machines.
The purpose of this task is to change the default DTMF commands for moderators and
conferees.

4. Click Configure.
5. On the Audio Conferencing Configuration screen, click General Config.
6. In the DTMF Controls section, click the Edit button corresponding to the conference
call flow for which you wish to change the DTMF mappings.
8. Click Save and thenSave again.
Next steps
Now you can configure further settings.

Ignore DTMF commands

Ignore DTMF Commands determines whether Conferencing ignores DTMF commands
entered by participants. By default, this setting is not selected. Flexflow conferences do not
support Ignore DTMF Commands.
• If you select Ignore DTMF Commands:
Conferencing ignores DTMF commands entered by participants. Conferencing also
blocks help requests when this feature is active.
• If you do not select Ignore DTMF Commands:
Conferencing interprets all DTMF commands entered by participants.
Moderator conference hangup

Moderator Conference Hangup determines if moderators can end their conference using the
DTMF command.
• If you select Moderator Conference Hangup:
Moderators can press ## to end their conference.
• If you do not select Moderator Conference Hangup:
If moderators press ##, they cannot end the conference.
Moderator lecture mode

Moderator Lecture Mode specifies whether moderators can mute all non-moderator lines. This
feature is not available during Q&A and polling sessions. By default, this setting is not selected.
• If you select Moderator Lecture Mode:
Moderators can mute all non-moderator lines and place the conference in Lecture mode.
Operator screens update to show that the conference is in Lecture mode, indicating that
non-moderator lines within the conference are muted.
• If you do not select Moderator Lecture Mode:
Moderators cannot mute lines for Lecture mode.
Sub-conferencing
Sub-conferencing specifies whether a participant can create a sub-conference from a main
conference by pressing *93 on their telephone keypad. If Conferencing cannot fulfill a sub-

conference request, it plays message 24, “This operation is currently unavailable.” By default,
Sub-conferencing is Off.
• Anyone
Any participant can create a sub-conference.
• Moderator
Only a moderator can create a sub-conference.
• Off
Sub-conferencing is disabled.
Self-mute
Self-mute specifies whether participants can mute their own lines. If an operator mutes or
unmutes a participant, this operator action always overrides the participant mute status. If an
operator mutes a line, a participant cannot unmute it. By default, this setting is off.
• Off
No one can mute their own line.
• Participant
Conferees can mute their own lines.
• Anyone
All participants, including moderators, can mute their own lines. Muted moderators retain
all moderator privileges such as lecture and moderator hang-up, but their audio input is
not fed into a conference.
DTMF acknowledge
DTMF Acknowledge specifies whether Conferencing sounds a tone when it receives DTMF
dialing input. These acknowledgment tones assure participants that Conferencing received
their DTMF input. By default, this setting is not selected.
• If you select DTMF acknowledge:
Conferencing emits an acknowledgment tone when participants press valid DTMF digits
on their telephones to enter a response to a poll question or to place themselves in either
the Help or Q&A queues.
• If you do not select DTMF acknowledge:

Conferencing does not emit an acknowledgment tone. However, participants typically

hear normal DTMF tones as they press digits on their telephone keypad.
Recording and playback

Recording and Playback refers to the properties relating to the conference recording feature.
This feature is useful for customers who wish to store any or all conferences for security
reasons. It is also useful for customers who wish to make conferences available for playback,
for example, to people who were unable to attend a conference. Conferencing can store and
manage recordings within the Conferencing server environment. If customers use this option, it
is often called on-bridge recording. Alternatively, customers can send the conferences to an
external device for recording, management, and playback. If customers use this option, it is
often called off-bridge recording. If customers use the off-bridge recording option, they cannot
make use of the playback facilities within Conferencing.
For legal reasons, in many countries, participants must be informed that the conference is
being recorded. As a result, Conferencing plays an audio message to inform them that the
conference is being recorded. If an operator or a moderator pauses the recording and then
subsequently resumes it, Conferencing replays the audio message. This is not configurable.
Related topics:
Bridge record on page 168
Phone number on page 169
Dial string on page 169
Pre dial delay period on page 169
DRP auto gen fname on page 170
Introduction to recording on page 301
Bridge record
Bridge Record specifies whether Conferencing records conference information on the
application server or to an external device. The application server is also called the bridge.
Typically, conference recordings are stored on the usr3/confrp drive of the IBM 3650 M2. By
default this setting is set to On-bridge. If you configure Bridge Record to Off-bridge and
operators are using Bridge Talk Conference Scheduler, you must also configure Bridge Talk
Conference Scheduler to Off-bridge. If you do not configure Off-bridge recording in both
locations, Conferencing defaults to On-bridge.
• On-bridge
Conferencing records conference information to the bridge.
• Off-bridge
Conferencing records conference information to an external device. In an Off-bridge
deployment, you must enter a value in the Phone Number and Dial String parameters.

When you configure Conferencing for Off-Bridge recording and an operator or moderator
schedules a conference for a maximum of 10 participants, the conference can have either:
9 participants and an external recording, or 10 participants and no external recording.
Phone number
Phone Number specifies the number to dial when Bridge Record is set to Off-bridge. This is
the telephone number of the external recording device.
Dial string
Dial String specifies the DTMF digits that Conferencing sends to the external recording device
after the recorder answers the call. Some of the information contained in the Dial String may
be vendor-specific. Some information may be derived at run time. Use these values in the
string to specify run-time values:
• %P
This value is expanded at run time to contain the conference passcode.
• %T
This value is expanded at run time to contain conference start time in Linux time format
(seconds since 1/1/1970).
• %C
This value is expanded at run time to contain conference confirmation number.
For example, if you set the Dial String to *000#*%P#*%T#%C## and the following conference
properties apply in your conference:
• The Passcode is 1234
• The conference starts on August 3, 2010 at 9:58 AM
• The confirmation number is 123456789012
Under these conditions, Conferencing sends the string
*000#*1234#*1280829516#*123456789012## to the external recording device.
Pre dial delay period

Pre dial delay period designates number of seconds that Conferencing waits before sending
a Dial String to the external recording device. The maximum setting is 50.

DRP auto gen fname

DRP Auto Gen Fname identifies whether Conferencing automatically allocates a filename to
a conference recording when an operator or moderator manually initiates a recording. By
default, this setting is selected.
• If you select DRP Auto Gen Fname:
Conferencing automatically allocates a filename to a conference recording.
• If you do not select DRP Auto Gen Fname:
Conferencing does not automatically allocate a filename to a conference recording.
Instead, operators manually enter a filename and moderators enter a DTMF string on
their telephone keypad to represent the filename.
Logging
Logging refers to the properties and extent of the audit trail that Conferencing produces during
the course of regular conference activity. For example, Conferencing produces operator logs
that report a number of operator actions and user logs that report a number of moderator and
participant actions. These logging settings specify a number of properties relating to the logging
feature.
Related topics:
Operator transaction logs on page 170
User transaction logs on page 171
Automatic CDR print on page 171
Date format on page 171
Time format on page 171
Operator transaction logs

Operator Transaction Logs specifies whether Conferencing generates operator transaction
logs. Operator transaction logs are detailed reports of individual Bridge Talk operator behavior.
These reports provide an audit trail of Bridge Talk operator actions. By default, this setting is
not selected. However, Avaya recommends selecting it.
• If you select Operator Transaction Logs:
Conferencing generates transaction logs.
• If you do not select Operator Transaction Logs:
Conferencing does not generate transaction logs.

User transaction logs

User Transaction Logs Identifies whether Conferencing logs all of a caller’s DTMF actions and
the Conferencing responses to the caller's actions. By default, this setting is not selected.
• If you select User Transaction Logs:
Conferencing writes caller DTMF and the Conferencing responses to a user transaction
log, which is a text file.
• If you do not select User Transaction Logs:
Conferencing does not create a user transaction log.
Automatic CDR print

Automatic CDR Print specifies whether Conferencing automatically exports the automatic call
detail record (CDR) and conference detail record (CODR)s. You can configure this feature to
process records in real time by configuring a remote host. By default, this setting is Off.
• LAN
Conferencing exports CDRs across the network to a client in real-time. If you set this
value, you must restart Conferencing.
• Off
Conferencing does not automatically generate real-time CDRs and CODRs.
Date format
Date Format specifies one of the following system date formats for the logging files. Date
Format has no effect on date formats in CDRs and CODRs. The default value is the US
standard date format: mm/dd/yyyy.
• mm/dd/yyyy
• yyyy/mm/dd
• dd/mm/yyyy
Time format
Time Format specifies whether Conferencing uses a 12–hour or 24–hour clock format for all
time references on the application server, including system time, schedule times, and operator

screens. Time Format has no effect on time formats in CDRs and CODRs. The default value
is 12–hour clock.
• 24–hour clock
• 12–hour clock
Flex settings
A flex flow conference is a specific type of on-demand conference. In flex flow conferences,
all call routing is based on the conferee passcode. In addition to the conferee passcode,
moderators enter a moderator passcode, which grants access to a moderator-specific menu.
Using this menu, moderators can edit conference attributes via DTMF from their telephone
keypad. You can configure a number of properties relating to flex flow calls.
Related topics:
Flex short time on page 172
Flex short attempts on page 172
Flex long time on page 173
Flex long attempts on page 173
Flex minimum dialout digits on page 173
Flex maximum dialout digits on page 173
Flex leader PIN modify on page 173
NRP operator timeout on page 174
Flex short time

Flex Short Time defines the number of seconds, from three to 20, that Conferencing gives
participants for entering a single DTMF digit. The default value is five.
This setting only applies to flex flow conferences.
Flex short attempts

Flex Short Attempts specifies the number of attempts, from one to five, that Conferencing gives
participants for entering a single DTMF digit. The default value is three.

Flex long time

Flex Long Time specifies the number of seconds, from five to 60, that Conferencing gives
participants for entering a sequence of DTMF digits. The default value is 40.
Flex long attempts

Flex Long Attempts specifies the number of attempts, from one to three, that Conferencing
gives participants for entering a sequence of DTMF digits. The default value is one.
Flex minimum dialout digits

Flex Minimum Dialout Digits specifies the minimum number of digits that Conferencing allows
for a dial out. The default value is four and the maximum is 99.
Flex maximum dialout digits

Flex Maximum Dialout Digits specifies the maximum number of digits that Conferencing allows
for a dial out. The default value is four, the maximum is 99.
Flex leader PIN modify

Flex Leader PIN Modify defines whether Conferencing allows moderators to modify their
moderator passcode using the DTMF commands on their telephone keypad. The minimum
moderator passcode length is set to 4. The maximum length is set to 16. The audio prompt
message that Conferencing plays to moderators when they are modifying their moderator
passcode refers to the minimum and maximum length values. By default, this setting is
selected.
• If you select Flex Leader PIN Modify:

The moderator can modify the moderator passcode by pressing 2 on a telephone keypad
to access the Default Conference Options menu before the conference starts.
• If you do not select Flex Leader PIN Modify:
The moderator cannot modify the moderator passcode in the Default Conference
Options menu before the conference starts.
NRP operator timeout

NRP Operator Timeout is related to a Bridge Talk setting that an operator sets when they make
a conference booking using the Bridge Talk Conference Scheduler. When an operator sets the
Name Record/Playback option to OPER when they book a conference using the Bridge Talk
Conference Scheduler, the NRP Operator Timeout parameter specifies where Conferencing
places a participant who fails to press “#” after recording their name. By default, this parameter
is set to Conf.
• Conf
Conferencing places participants who record a name, but who do not press #, into the
conference.
• Enter
Conferencing places participants who record a name, but who do not press #, into the
Enter queue.
Billing
The Billing section contains a single feature, which is not installed on the Conferencing server
by default. If you require access to this feature, you must enable it. This feature is free. Avaya
does not charge for it.
Related topics:
CDR end date filename on page 174
CDR end date filename

CDR End Date Filename relates to a Conferencing feature called CDR End Date. The CDR
End Date feature enables a conferencing system to generate CDRs or a CODR for a
conference on the end date rather than the start date when a conference extends past
midnight.
Conferencing produces a CDR file each day. As conferences open and close during the day,
all their CDR information is added to the CDR file. The file gets larger as the day progresses. As

soon as midnight passes, Conferencing creates a new CDR file. The CDR End Date feature
refers to conferences that start before midnight and span into the following day. The CDR End
Date Filename parameter indicates that the CDRs of these conferences should go into the
new CDR file.
• If you select CDR End Date Filename:
The CDRs are based on the end date of the conference, rather than the start date.
Effectively, the CDRs go into the new CDR file, rather than the one from the previous day.
• If you do not select CDR End Date Filename:
The CDRs are based on the start date of the conference, rather than the end date.
Effectively, the CDRs go into the old CDR file, rather than the new one for the following
day.
Related topics:
Introducing billing on page 313
RAI configuration
Resource Availablility Indicator (RAI) is a message that Conferencing sends out to external
devices. The message shows the current status of the Conferencing server. The message
contains the current availability of telephone lines, or ports. It is a usage status information
message.
Note:
Communication Manager uses the RAI when it is configured to an application server, or
bridge, which supports video. Communication Manager sends a SIP subscribe message to
the bridge and the bridge then periodically sends RAI notifications. Communication Manager
only sends the subscribe message if it is configured to connect to a video bridge. Currently,
Communication Manager uses the bridge for ad-hoc video conferences. It does not use the
bridge for ad-hoc audio conferences.
Related topics:
Notification interval on page 175
High threshold on page 176
Low threshold on page 176
Max subscribers on page 176
Notification interval
Notification Interval is the Resource Availablility Indicator (RAI) notification interval.
Conferencing sends out a message to an external device to indicate the current availability of
telephone ports. This parameter specifies the interval, in seconds, between status messages.
For example, if it is set to 60, Conferencing sends out an RAI status message every minute.
An example of an external device is Communication Manager. In a deployment that uses video

conferencing, Communication Manager needs to know how many ports are available on the
High threshold
High Threshold relates to the RAI feature. When the telephone port usage on the Conferencing
server exceeds a certain percentage, Conferencing enters a high usage state. The message
that Conferencing sends to external devices to indicate its current availability, states that
Conferencing has entered a high usage state. This parameter specifies the percentage that
represents high usage. For example, if this parameter is set to 90, Conferencing will enter a
high usage state when 90% of the telephone ports are being used. Conferencing will only exit
the high usage state when the usage drops below the percentage indicated in the Low
Threshold parameter.
Low threshold
Low Threshold relates to the RAI feature. This parameter specifies the percentage of use that is
required to exit a high usage state. Conferencing enters a high usage state when a large
percentage of the telephone ports are currently in use. Conferencing can exit the high usage
state when the current load reduces and more telephone ports are made available. For
example, if this parameter is set to 75, Conferencing will exit a high usage state when 75% of
the telephone ports are available.
Max subscribers
Max Subscribers relates to the RAI feature. Max Subscribers indicates the number of external
devices to which Conferencing can send an RAI status message. If this parameter is set to 10,
Conferencing can send a status message to 10 external devices. An example of an external
device is Communication Manager.
Port pool usage thresholds

Port Pools refer to the percentage of telephone lines, or ports, allocated to scheduled
conferences and on-demand conferences. Typically, in a new deployment, you must assign a
percentage of ports for scheduled conferences and a percentage of ports for on-demand
conferences.
Each instance of an on-demand conference requires no additional scheduling. Conferees can

access an on-demand conference provided they have the appropriate telephone number and
passcodes.
moderators book a scheduled conference, Conferencing reserves system resources to cater
for the duration and size of the conference.
Port Pool Usage Thresholds refer to the usage levels that trigger an alarm. When Conferencing
reaches these levels, it sends an alarm, or a trap, using the SNMP system. The usage levels
are calculated in terms of a percentage of telephone lines, or ports.
Related topics:
Logs and alarms on page 97
Reserved low on page 177
Reserved high on page 177
Unreserved low on page 178
Unreserved high on page 178
Reserved low
Reserved Low is a percentage threshold to indicate the point at which Conferencing resets the
high usage SNMP alarm for scheduled conference port usage. Once Conferencing resets the
high usage alarm, the alarm is available for activation if the it exceeds the high usage parameter
for scheduled conferences. This reset mechanism means that Conferencing does not send
large numbers of alarms if the port usage varies around the high usage threshold point. For
example, consider a configuration where the high usage threshold is 80% and the reset point is
70%. Conferencing sends an alarm once the usage reaches 80%. Following this point, the
usage could fall to 78% but then rise again to 80%, only to fall again to 76% and rise again to
80%. In the absence of the reset mechanism, Conferencing would send alarms to the network
management system each time the usage reached 80%. With the reset mechanism,
Conferencing does not send an alarm until usage falls to 70% and rises again to 80%. Once
usage falls to 70%, it resets the high usage parameter and it is available for activation once
again.
Reserved high
Reserved High is a percentage threshold to indicate the point at which Conferencing sends an
alarm to warn the network management system that it is experiencing high usage. The
Reserved High parameter relates to the percentage of telephone lines, or ports, available for
scheduled conferences only. For example, if you enter 80%, Conferencing sends an alarm to
the network management system if it is currently using more than 80% of the ports that are
available for scheduled conferences.

Unreserved low
Unreserved Low is a percentage threshold to indicate the point at which Conferencing resets
the high usage SNMP alarm for on-demand conference port usage. Once Conferencing resets
the high usage alarm, it is available for activation if it exceeds the high usage parameter for
on-demand conferences. This reset mechanism means that Conferencing does not send large
numbers of alarms if the port usage varies around the high usage threshold point. For example,
consider a configuration where the high usage threshold is 80% and the reset point is 70%.
Conferencing sends an alarm once the usage reaches 80%. Following this point, the usage
could fall to 78% but then rise again to 80%, only to fall again to 76% and rise again to 80%.
In the absence of the reset mechanism, Conferencing would send alarms to the network
management system each time the usage reached 80%. With the reset mechanism, the
conferencing system does not send an alarm until usage falls to 70% and rises again to 80%.
Once usage falls to 70%, it resets the high usage parameter and it is available for activation
once again
Unreserved high
Unreserved High is a percentage threshold to indicate the point at which Conferencing sends
an alarm to warn the network management system that it is experiencing high usage. The
Unreserved High parameter relates to the percentage of telephone lines, or ports, available
for on-demand conferences only. For example, if you enter 80%, Conferencing sends an alarm
to the network management system if it is currently using more than 80% of the ports that are
available for on-demand conferences.
Configuring general configuration settings

Prerequisites
Before you configure the general configuration settings, ensure that you install Conferencing
and assign each of the virtual machines to the CRS virtual machine in the Components
section.



4. Click Configure.
8. Click Save.
Example
For example, if you do not want Conferencing to automatically allocate a filename to a
conference recording when an operator or moderator manually initiates a recording, ensure
that DRP: Auto-gen fname is not selected.


Chapter 10: Configuring media settings
Media server settings

recording. The media server component resides with the application server on a single 'box'
in the Standard Edition of Conferencing. This box hardware is an IBM 3550 server.
Conferencing hosts live conferences on the media server component.
For the successful operation of the Conferencing solution in your network, you must configure a
number of media server settings. You can configure most of these settings using the
Conferencing Manager interface. In particular, most of the settings are in the Conferencing >
Media > Configuration and the Conferencing > Media > Features menus.
Media server features settings

The media server features settings relate to the quality of the Conferencing experience.
Although, many of the media server settings have default values, the bandwidth availability in
each deployment varies. You can configure different values in order to optimize the quality of
the Conferencing experience in your deployment.
Avaya recommends that only those with media server technical knowledge should make
changes to the media settings.
Related topics:
Audio quality on page 181
Video quality on page 183
TTY on page 183
SRTP on page 184
Network performance on page 185
Audio quality
Avaya has implemented a number of features to ensure that audio quality during conferences is
optimized. These features include the generation of a subtle background sound (called comfort

Configuring media settings
noise) and a deliberate lack of acknowledgment of sounds below a certain threshold (called
silence suppression). These features and others relating to audio quality are configurable.
Related topics:
Automatic gain enabled on page 182
AGC target power level on page 182
AGC noise floor on page 182
Comfort noise enabled on page 182
Comfort noise level on page 183
Silence suppression enabled on page 183
Silence suppression energy threshold on page 183
Packet loss concealment enabled on page 183
Automatic gain enabled

Automatic Gain Control (AGC) regulates the volume of participants in a conference. AGC
operates by reducing the volume of conference lines with a high volume and increasing the
volume of conference lines with a low volume. If you disable AGC, Conferencing does not
regulate volume.
AGC target power level

This value specifies the target power level during sound and volume mixing. The valid values
are –6dBFS to –20dBFS in 2dBFS steps.
AGC noise floor

This value specifies the lowest level at which Conferencing acts to eliminate background noise.
This feature is called the application of Gain. The minimum level for agcNoiseFloor is -26dbs.
Conferencing does not apply Gain to levels below this value to eliminate background noise.
Comfort noise enabled

Comfort noise generation adds background white noise to a conference to avoid total silence
when none of the participants are talking. If you disable comfort noise generation, Conferencing
does not play white noise when none of the participants are talking.

Comfort noise level

Comfort noise generation adds background white noise to a conference. This value specifies
the level at which Conferencing plays the comfort noise.
Silence suppression enabled

Enable this option to enable silence suppression. Silence suppression is the process of not
transmitting information over the Conferencing network when the parties involved in a
conference call are not speaking, thereby reducing bandwidth usage.
Silence suppression energy threshold

When silence suppression is enabled, this value represents the energy threshold at which the
media server stops sending audio.
Packet loss concealment enabled

Packet loss concealment (PLC) is a technique to mask the effects of packet loss in VoIP
communications. Because the voice signal is sent as packets on a VoIP network, they may
travel different routes to get to destination. At the receiver a packet might arrive very late,
corrupted or simply might not arrive. You can enable Conferencing to cope with a certain
amount of packet loss. This is a very effective error-control technique.
Video quality
The Standard Edition of Conferencing does not support video.
TTY
A telecommunications device for the deaf (TDD) is an electronic device for text communication
via a telephone line, used when one or more of the parties has hearing or speech difficulties.
Other names for TDD include TTY (telephone typewriter or teletypewriter, although TTY is also
a term used for teletypes in general). You can configure support for TTY in the Conferencing
environment.

Related topics:
TTY support enabled on page 184
TTY redundancy support enabled on page 184
TTY support enabled

This value determines whether Conferencing supports the text telephone feature for the
hearing impaired. When this option is enabled, the media server supports the pass through of
out-of-band (OOB) TTY tones in a conference. Only deployments with Avaya
Aura™Communication Manager support OOB TTY tones. For more information on enabling
OOB TTY for endpoints, see the Communication Manager documentation, which is available
on support.avaya.com. You do not require this option when using in-band TTY tones. In-
band TTY tones always pass through a conference. Avaya does not recommend using in-
band TTY for any codec other than G.711.
TTY redundancy support enabled

This value determines whether Conferencing supports redundancy for the text telephone
feature. This option allows for support of redundant out-of-band TTY packets. This option only
comes into play when TTY support is enabled. Select this option if you are having problems
with packet loss on the network.
SRTP
SRTP defines a profile of RTP (Real-time Transport Protocol), intended to provide encryption,
message authentication, and integrity, and replay protection to data. Conferencing now
supports this protocol for all audio transfers.
Related topics:
Encryption enabled on page 184
SRTP crypto suite on page 185
Encryption enabled
Select this parameter to enable SRTP for audio streams.

SRTP crypto suite

This field determines which encryption and authentication algorithms that Conferencing uses
for SRTP with RTP. For example, srtpCryptoSuite=AES_CM_128_HMAC_SHA1_80.
Network performance
You can configure three settings in relation to Conferencing and the customer network.
Alternatively, you can accept the default values.
Related topics:
Base RTP port on page 185
Min RTCP transmission interval on page 186
VLAN service on page 186
Base RTP port

This value specifies the base port number to be used by the Conferencing media server
component for all RTP and RTCP streams. The base port number can be any port number that
is not in use by any other service on your computer. The base port number should always
be an even number.
The range of UDP ports used for the RTP media is defined by the number of channels per
software media server and the number of software media servers configured:
((maxChannels * 2) * numberOfSoftms processes) + baseRTPPort)
For example, (((702 x 2)x 6) + 42000) = 50424
This example shows the default value of 702 maxChannels per Softms x 2 which is the number
of UDP ports used in an audio call. This value (1404) is then multiplied by the number of Softms
processes configured on the system, in this example 6 giving a value of 8424. When added to
the base range of 42000 this gives a final UDP port number of 50424. The UDP range in this
case is 42000 - 50424.
As an aside, the calculation if the conferencing bridge has video enabled is as follows:
((maxChannels * 4) * numberOfSoftms processes) + baseRTPPort) Note there are 4 UDP RTP
streams for audio and video instead of 2.

Min RTCP transmission interval

This value specifies the minimum time between transmissions of RTCP packets, measured in
milliseconds. The reason for allocating a minimum interval is to avoid sending RTCP packets
too often on a network where you wish to conserve bandwidth for the audio streams.
VLAN service
This value determines the VLAN service on RTP packets. The default is 0.
Media server configuration settings

The media server configuration settings relate to Conferencing performance and resource
availability among other aspects. Many of the media server settings have default values which
you do not need to change. However, in order to successfully implement the Conferencing
solution, you have to configure the SIP settings.
Avaya recommends that only those with media server technical knowledge should make
changes to the media settings.
Related topics:
SIP settings on page 64
General on page 186
Media codecs on page 187
General
The General section includes parameters relating to speaker thresholds and active speaker
notification.
Related topics:
ASN interval on page 187
Audio talker interval on page 187
Wav file clip on page 187

ASN interval
By default, Conferencing checks each channel every 2000 milliseconds to see if someone is
speaking. The active speaker notification (ASN) interval parameter controls this timer. For
example, if ASN interval is 500, Conferencing checks each channel every 500 milliseconds.
The ASN interval value overrides the default value on the application server.
Audio talker interval

This value represents the energy threshold for Audio Talkers. The recommended value is -18
dB, but the value can vary between -50 dB and -5 dB as required. It is an integer.
Wav file clip

This setting relates to audio recordings. This feature clips a defined number of milliseconds
from the end of a .wav recording. The default is 30 milliseconds.
Media codecs
A codec is a device or computer program capable of encoding and/or decoding a digital data
stream or signal.
In relation to audio codecs, the Standard Edition of Conferencing supports the G.711 codec.
The Standard Edition of Conferencing does not support any other codecs. G.711 represents
logarithmic pulse-code modulation (PCM) samples for signals of voice frequencies, sampled
at the rate of 8000 samples/second.
The Standard Edition of Conferencing does not support video conferencing and so does not
support video codecs.
Related topics:
Audio codecs on page 187
Video codecs on page 188
Configuring codecs on page 188
Audio codecs
The Standard Edition of Conferencing does not support any other codecs. G.711 represents

logarithmic pulse-code modulation (PCM) samples for signals of voice frequencies, sampled
at the rate of 8000 samples/second.
Video codecs
The Standard Edition of Conferencing does not support video conferencing and so does not
support video codecs.
Please contact your Avaya Support Representative to discuss alternative methods of obtaining
video support. The Avaya product suite contains a number of alternative options that may suit
your requirements.
Configuring codecs
There are two flavors of G.711: The µ-law algorithm (used in North America & Japan) and A-
law algorithm (used in Europe and the rest of the world).
Both are logarithmic, but A-law was specifically designed to be simpler for a computer to
process. The standard also defines a sequence of repeating code values which defines the
power level of 0 dB. The µ-law and A-law algorithms encode 14-bit and 13-bit signed linear
PCM samples (respectively) to logarithmic 8-bit samples. Thus, the G.711 encoder will create a
64 kbit/s bitstream for a signal sampled at 8 kHz.[5] G.711 μ-law tends to give more resolution to
higher range signals while G.711 A-law provides more quantization levels at lower signal levels.
By default, Conferencing supports both compression algorithms. The µ-law algorithm is called
PCMU. The A-law algorithm is called PCMA. You can disable one of them, if required.
When the Conferencing server makes a telephone call, it includes a SIP_INVITE message.
The SIP_INVITE request that the Conferencing server sends out when it places an external
telephone call includes a list of the codecs which Conferencing supports. The list order
specifies a selection preference. By default, Conferencing supports PCMU first and then
PCMA. You can change this order, if required.
As an aside, the telephone-event codec refers to a method of support for out-of-band DTMF
processing. Typically, Conferencing sends DTMF signals along the same stream as audio
information. However, you can configure Conferencing to send DTMF signals along a different
stream. This is called out-of-band DTMF processing.
Prerequisites
Before you configure codecs, you must install and configure Conferencing.
The purpose of this task is to make changes to the default configuration of codecs.


4. In the Media Codecs panel, click Edit at the Audio Codecs field.
5. Configure the codecs, as required.
• To change the order preference, select an algorithm and click Move Up or
Move Down.
• To disable an algorithm, de-select the corresponding Enabled field.
6. Click Save.
7. Click Save again.
When you apply changes, Conferencingrestarts. It is a good idea to apply changes
SIP settings
The main configuration settings that are relevant to connecting Conferencing to the network
are the SIP settings. The Session Initiation Protocol (SIP) is a signaling protocol, widely used
for controlling multimedia communication sessions such as voice and video calls over Internet
Protocol (IP). Within a SIP communications framework, the method of transmission is
configurable.
The SIP communications across your network must use one of the following methods of
transmission:
• Transport Layer Security (TLS)
• Transmission Control Protocol (TCP)
• User Datagram Protocol (UDP)
Related topics:
SIP listener URI on page 64
Response contact on page 65
Session refresh timer on page 65
Min session refresh timer allowed on page 66
Configuring SIP on page 66

Configuring SIP
Prerequisites
Before you configure the SIP settings, you must install Conferencing and configure a media
gateway.
The purpose of this task is to configure the transport protocols for communications from the

4. In the SIP panel, configure the settings as required in your deployment.
5. Click Save.
Next steps
Now you can configure the telephone numbers.

Chapter 11: Configuring the CRS

The CRS Front End consists of two parts. It is a scheduling interface for operators. It is also
an interface through which administrators can manage Conferencing resources. Operators
can access the Customer Bookings section and administrators can access the System
Administration section.
Avaya installs an instance of CRS Front End on the CRS virtual machine, by default. You can
use this instance of CRS Front End to verify the installation and configuration steps that you
have completed so far. Once you install the CRS Front End, you can use it to verify that the
Conferencing application server, or bridge, is corrected installed. You can also use the CRS
Front End to create a test conference and perform a test call.
As an aside, the Web Portal is similar to the CRS Front End. Essentially, it is a Web deployment
of the CRS Front End windows environment. Administrators and operators can use the Web
Portal to perform many of the tasks that they can perform using the CRS Front End. There are
limitations to the Web Portal, however, and it on ly covers a subset of CRS Front End
functionality.
Related topics:
Installing CRS Front End on the CRS server on page 88
Creating a test conference on page 90
Distributing CRS Front End to the operators on page 91
CRS configuration
The configuration of CRS involves the configuration of a number of aspects of CRS properties.
The aspects are:
• General settings
• Timezones
• Users

Configuring the CRS
In the case of each of these areas, the documentation contains a description of the concept,
followed by the steps required to configure a sample setting for that concept.
Tip:
Rather than reading the full list of CRS configuration settings, you can use the search tool
to locate a description of any setting.
In the System Administration section of the CRS Front End, you can configure a number of
these concepts. However, Avaya recommends that you configure the CRS settings using
Conferencing Manager, despite this support on the CRS Front End.
Related topics:
General settings on page 192
Reseller settings on page 223
Timezone settings on page 223
User settings on page 224
Wholesaler settings on page 229
General settings
Within CRS configuration, the general settings is the largest area. It consists of several different
sections:
• Components
• General Settings
• Features
• Reservation and Conference Settings
• User Settings
• Notification Settings
• Billing Settings
• Perpetual Conference Settings
• Groupware clients
• SAL connectivity settings
Related topics:
Components on page 193
General settings on page 193

CRS configuration
Features on page 196

Reservation and conference settings on page 197
User settings on page 200
Notification settings on page 208
Billing settings on page 212
Perpetual conference settings on page 214
Groupware clients on page 216
Outlook settings on page 218
Configuring general settings on page 222
Components
The Components section contains a list of the IP addresses of the virtual machines that
operate alongside the CRS virtual machine to deliver the Conferencing experience. The other
virtual machines in the Conferencing network are:
• Application server or bridge
In the Conferencing Manager interface, this is called Conferencing Server(s)
In the Conferencing Manager interface, this is called Web Conferencing Server
In the Conferencing Manager interface, this is called Web Application Server
When you add the virtual machines to the Conferencing network, you must establish
connectivity between the virtual machines that you have added. You can do this, using this
Components section.
General settings
The General settings section contains a list of settings which you can configure to match your
customer requirements. The Conferencing solution is highly configurable. You can customize
many aspects of the Conferencing experience using the CRS parameters.
Tip:
If you cannot find the a particular setting in the Client Registration > General section, it is
likely that you will find it in the Audio Conferencing > Bridge Features or Audio
Conferencing > Conference Features sections. Together, these three sections contain the
most customizable aspects of Conferencing.
Related topics:
Overbook percent on page 117

Configuring the CRS
Phone number format type on page 194

Allow infinite ports on page 194
Site timezone on page 195
Authentication required at login on page 195
Dialout prefix on page 196
Phone number format type

The Phone Number Format Type parameter specifies whether a telephone number can include
round brackets, which are also known as open brackets or parentheses (). If Phone Number
Format Type is set to 1, Conferencing permits round bracket characters (). The default value
of the Phone Number Format Type parameter is 0. When Phone Number Format Type=0,
Conferencing rejects round brackets.
Allow infinite ports

The Allow Infinite Ports parameter specifies whether Conferencing allows an operator or a
moderator to book an infinite number of ports, or telephone lines for their conference. By
default, the Allow Infinite Ports parameter is not selected. If you select the Allow Infinite Ports
parameter, Conferencing ignores the value of the Overbook Percent parameter.
• If you select Allow Infinite Ports:
Conferencing enables operators and moderators to book any number of ports.
• If you do not select Allow Infinite Ports:
Conferencing enables operators and moderators to book ports in accordance with the
number of ports in their deployment.
Overbook percent
The overbooking feature increases the available ports by providing a pool of additional virtual
ports. These virtual ports are available for reserved conference bookings. This functionality
ensures that customers can maximize the use of Conferencing by allowing for the fact that in
many cases, full conference attendance does not occur.
The Overbook Percent parameter specifies the percentage of Conferencing lines that
operators and moderators can overbook for scheduled conferences. This parameter does not
impact on-demand conferences. By default, the value of the Overbook Percent parameter is 0.
• If the value of the Overbook Percent parameter is between 1and 100:
Operators and moderators can reserve a percentage from 1% to 100% more than the
maximum number of lines available for a given time period. Lines configured for operators,
music, record/playback, or link lines are not included in the line count. For example, if
your deployment of Conferencing has 1000 lines available for scheduled conferences and
you set this parameter for 10%, you can schedule 1100 lines.
• If the value of the Overbook Percent parameter is 0:
Conferencing allows infinite conference overbooking.

CRS configuration
Related settings
To make overbooking available in your deployment, you must also enable the Line
Overbooking feature on the Conferencing application server, or bridge.
A related parameter is the On Demand Pct % parameter.
Example scenario
In practice, it is a good idea to set the Overbook Percent parameter to 0 which is infinite and
On-Demand Pct (%) to 50%. Avaya sets the On-Demand Pct (%) to 50%. These values allow
for 50% of the ports to be allocated to on-demand conferences and 50% to be allocated to
scheduled conferences. The available ports is the total number of telephone lines with the total
number of FDAPI resources subtracted from this total. FDAPI resources include operator
telephone lines and playback telephone lines.
Site timezone
There are two aspects to timezones:
• Site timezone
• Operating system timezone
The Site Timezone parameter specifies the timezone of the CRS database, which is called
BSRes2. The CRS uses this timezone for booking and scheduling.
The Site Timezone drop-down list is populated using the list of timezones in the Elements >
Conferencing > Client Registration > Timezones menu in Conferencing Manager. The
Timezone list contains a default list of the most common timezones. If your timezone is not in
the list of timezones, you can add it using Conferencing Manager.
After you install Conferencing, you must always manually configure the Site Timezone drop-
down list to set the site timezone.
It is important, at this stage to distinguish between the site timezone and the operating system
timezone. You must manually configure the site timezone after you install Conferencing.
The operating system timezone is different. Conferencing inherits the operating system
timezone from System Platform. When you install Conferencing, System Platform pushes the
timezone setting to all Conferencing operating systems and virtual machines. Before you install
Conferencing, check that the timezone setting on System Platform is the setting that you
require in your Conferencing deployment. If it is not, it is a good idea to change the timezone
setting on System Platform before installing Conferencing.
Authentication required at login

The Authentication Required At Login parameter specifies whether a password is required for
CRS access. It is a parameter in the BSRes2 database table. This acts as a second level of
security for those who are logging in to CRS Front End.
If Authentication Required At Login=1, the CRS Front End prompts users to enter a password
when they access the CRS. If Authentication Required At Login=0, the CRS Front End does
not prompt users to enter a password when they access the CRS.

Configuring the CRS
CRS Front End users are defined as operators, supervisors, administrators, user-
administrators, and user-auditors.
Authentication Required At Login is a CRS server-side setting. There is a related setting called
ValidationRequired in the bands.ini file. The bands.ini file resides on each client machine and
contains the CRS client-side settings. If the two values (Authentication Required At Login and
ValidationRequired) are inconsistent, the CRS server imposes synchronization by propagating
the server-side value to the client side. In this event, the first log-in attempt by the CRS client
fails and the CRS server resets the value. Any subsequent log-in attempt should be successful.
The maximum password length is 20 characters. You can set the minimum password length
using the Minimum Password Length parameter. The default value for Minimum Password
Length is four. You can also set the password complexity using the Minimum Password
Complexity parameter. There are four levels of complexity. You can also set password expiry
using the Period to Password Expiry parameter.
If you enable Authentication Required At Login, the Web Portal application verifies the
password that Web Portal administrators and wholesalers enter when they access Web Portal.
Dialout prefix
The Dialout Prefix parameter specifies the number that Conferencing places before the
telephone number when operators and Web Portal moderators dial out to other telephone
numbers while in a conference.
Moderators can dial out by pressing *1 or *92 on their telephone keypad. If they press *1, they
can dial a single telephone number. If they press *92, they can trigger a blast dial.
Blast dial refers to a feature whereby operators and moderators can dial a large group of
potential participants using a single command. For the successful operation of this command,
the operator, using CRS Front End, or the moderator, using Web Portal, must enable Blast Dial
for the conference. In addition, you must create and save blast dial lists.
Features
The Features section contains a single field, relating to data conferencing.
Data conferencing is the simultaneous sharing of voice and visual information using a Web
Front End called Avaya Web Conferencing (AWC). Using AWC, moderators can share their
desktop, a whiteboard, or a Microsoft™ Powerpoint presentation. Moderators and participants
can also share messages and video using AWC. If your deployment requires either of these
features, you must enable them here.
In previous releases of Conferencing, you could enable this feature using a file on the
application server called featcfg.
Related topics:
Disable data on page 197

CRS configuration
Disable data
The Disable Data checkbox specifies whether the Data checkbox on the CRS Front End
Check Reservation dialog is accessible to operators. Operators select the Data checkbox to
schedule a telephone conference with a Web component. Using the Web component,
moderators can share slides, share their desktop, and stream video. The Web component is
provided by an application called Avaya Web Conferencing (AWC).
• If you select Disable Data:
The Data checkbox is not selected and is inaccessible to operators.
• If you do not select Disable Data:
The Data checkbox is accessible to operators.
Reservation and conference settings

The Reservation and Conference Settings section contains a number of parameters relating
to the limitations of Conferencing in your deployment. In the Reservation and Conference
Settings section, you can set limitations on the size and length of conferences. You can also
set a number of other properties, relating to passcodes and conference expiry.
Related topics:
Maximum conference duration on page 197
Minimum conference duration on page 198
Maximum conference size on page 198
Minimum conference size on page 198
Minutes between DDI reuse on page 198
Maximum number of conferences per booking on page 198
Auto generated passcode length on page 199
Minimum passcode length on page 199
Maximum passcode length on page 199
Period until conference disabled on page 199
Maximum conference duration

The Maximum Conference Duration parameter specifies the length of the longest conference
that Conferencing permits.
When operators schedule a conference, they enter the duration on the Check Reservation
dialog. However, if the proposed duration exceeds the Maximum Conference Duration
parameter, Conferencing prompts the operator to reduce the duration below the maximum
allowed. For example, if Maximum Conference Duration=1440, the duration set must not
exceed 1440 minutes (24 hours). On-demand conferences are configured to last for 1440
minutes, regardless of the value of the Maximum Conference Duration parameter .

Configuring the CRS
Minimum conference duration

The Minimum Conference Duration parameter specifies the length of the shortest conference
that Conferencing permits. When operators schedule a conference, they enter the duration on
the Check Reservation dialog. However, if the proposed duration is less than the Minimum
Conference Duration parameter, Conferencing prompts the operator to increase the duration
above the minimum allowed. For example, if Minimum Conference Duration=10, then the
duration set must be greater or equal to 10 minutes.
Maximum conference size

The Maximum Conference Size parameter specifies the largest conference that Conferencing
permits.
You can restrict conference size in your deployment to ensure system resources are not
overstretched.
For example, if a deployment has 240 telephone lines or ports, it is advisable that the Maximum
Conference Size parameter is a percentage of the overall ports available. For example, if
Maximum Conference Size=80, it is possible to schedule three conferences using 80 ports
each, to occur at the same time. The Maximum Conference Size parameter is specific to
conferences booked through CRS.
Minimum conference size

The Minimum Conference Size parameter specifies the smallest conference that Conferencing
permits. Conferencing rejects a conference if the number of participants is less than the
minimum required as configured in the system parameters. For example, if Minimum
Conference Size=3, then at least three participants are required to schedule a conference.
Minutes between DDI reuse

The Minutes Between DDI Reuse parameter specifies the minimum duration that must lapse
between the end of one conference and the beginning of a second conference with the same
DNIS/DDI.
DNIS/DDIs can generally be used repeatedly; however, the same DNIS/DDI cannot be used
by two or more conferences that occur at the same time. In addition, a DDI may be set up
permanently to point at a single conference, in which case, it is unavailable for any other use.
For example, if you set this field to 40, then 40 minutes must lapse between scheduled
conferences before the DNIS/DDI can be reused.
Maximum number of conferences per booking

The Maximum Number Of Conferences Per Booking parameter restricts the number of
conferences associated with a single reservation.
When an operator schedules a conference, Conferencing associates it with a reservation.
However, a reservation can contain multiple conferences in a variety of states. A reservation
contains multiple conferences if a conference has been scheduled to repeat.
Using the Maximum Number Of Conferences Per Booking parameter, you can restrict the
number of conferences associated with a reservation. For example, if Maximum Number Of

CRS configuration
Conferences Per Booking=100, then only one hundred conferences can be associated with a
reservation.
Auto generated passcode length

The Auto Generated Passcode Length parameter specifies the length of automatically
generated passcodes.
When operators or moderators book a conference, they can enter their own choice for conferee
and moderator passcodes. The passcode lengths are subject to the Maximum passcode
length and Minimum passcode length parameters, which you can configure using
Alternatively, if the Autocode checkbox on the CRS Front End or the Auto-Generate
Passcodes checkbox in the Web Portal are selected, the CRS automatically generates
passcodes and sets their length according to the value of the Auto Generated Passcode Length
parameter. For example, if the Auto Generated Passcode Length=6, Conferencing generates a
number that is 6 digits long.
Minimum passcode length

The Minimum Passcode Length parameter specifies the minimum length of the conference
passcode. The Minimum Passcode Length parameter applies to moderator, conferee, and co-
chairperson passcodes. The default value of Minimum Passcode Length is 4.
Maximum passcode length

The Maximum Passcode Length parameter specifies the minimum length of the conference
passcode. The Maximum Passcode Length parameter applies to moderator, conferee, and
co-chairperson passcodes. The default value of Maximum Passcode Length is 16.
Period until conference disabled

The Period Until Conference Disabled parameter specifies the length of time for which an on-
demand conference can remain unused before the CRS suspends it. For example, if Period
Until Conference Disabled=90, the CRS suspends on-demand conferences which are inactive
for over 90 days. If Period Until Conference Disabled=0, the CRS does not implement the
feature.
A database stored procedure called p_DisableInactiveConferences checks for conferences
that have exceeded the threshold and suspends them. Avaya recommends that you schedule
this procedure to run every day or every week using the Windows Scheduler or the SQL Server
Scheduled Task Manager.
CRS operators, supervisors, and administrators can re-enable any suspended conferences,
using the conference editing functionality. For more information on re-enabling suspended
conferences, see Using Avaya Aura™ Conferencing Guide, which is available from
support.avaya.com.

Configuring the CRS
User settings
The User Settings section contains a number of parameters relating to account numbers,
passwords, passcodes, and unique identifying numbers (secret PIN). In the CRS Front End
environment, conference users who have Conferencing accounts are called clients. In the Web
Portal environment, conference users who have Conferencing accounts are called
moderators.
Related topics:
Account number length on page 200
Period to conference passcode renewal on page 200
Period of passcode overlap on page 202
Maximum number of login attempts on page 202
Minimum password length on page 203
Minimum password complexity on page 203
Period to password expiry on page 203
Default client phone number on page 204
Period until user disabled on page 205
Period until client disabled on page 205
URL to reset participant secret PIN on page 206
External user participant identifier on page 206
External user participant PIN on page 207
Account number length

The Account Number Length parameter specifies the length of automatically generated client
account numbers.
Conferencing configures an account number for each client established on the conferencing
database. Conferencing automatically generates an account number when operators launch
the New Client dialog from the Customer Bookings screen. The number generated by
Conferencing corresponds to the string length that you set for the Account Number Length
parameter. For example, if the Account Number Length=10, then the number generated is 10
digits long. When you modify the Account Number Length parameter, the next time you open
existing client account details, Conferencing displays a system message. The message states
that the old account number length is not consistent with the current system parameter. You
need to modify the account number manually and then update the record.
Period to conference passcode renewal

The Period to Conference Passcode Renewal parameter specifies the default value for the
time period between automatic pass code refresh cycles.
The Period to Conference Passcode Renewal parameter has a range of 0 to 365. Operators
can modify this time period by entering a new value in the Renew Days field in the New
Company and Edit Company dialogs.

CRS configuration
The CRS automatically generates new pass codes for on-demand conferences if the owner
of the demand conference does not change their pass code within a configurable period of
time. The CRS directs the Notifications Subsystem to generate an e-mail notification to inform
the conference owner of their new pass codes. For a configurable period of time, the old pass
codes are still valid. This period gives the conference owner the time to adjust their conference
details. When the overlap period ends, the CRS directs the Notifications Subsystem to
generate an e-mail notification to inform the conference owner that their old pass codes are
no longer valid.
At Company level, operators can configure:
• The time period between automatic pass code refresh cycles.
Operators can modify this time period by entering a new value in the Renew Days field
in the New Company and Edit Company dialogs. The CRS Front End obtains the default
value for the Renew Days field from the Period to Conference Passcode Renewal
parameter in the Company table in the BSRes2 database. The Period to Conference
Passcode Renewal parameter has a range of 0 to 365.
• The time period for which the old pass codes are still valid.
Operators can modify this time period by entering a new value in the Overlap Days field in
the New Company and Edit Company dialogs. The CRS Front End obtains the default
value for this field from the Period of Passcode Overlap parameter in the Company table in
the BSRes2 database. The Period of Passcode Overlap parameter has a range of 0 to 30.
Note:
The CRS performs a check to ensure that the Period to Conference Passcode Renewal
parameter is less than the Period of Passcode Overlap parameter.
You can set the default value to display in the CRS Front End New Company and Edit
Company dialogs by setting the value of the Period of Passcode Overlap and Period to
Conference Passcode Renewal parameters in the Company table in the BSRes2 database.
The Conference table also contains two parameters that enable this functionality.
• PassCodeChangedDT stores the date and time that the pass codes were last changed.
• OverlapStartDT stores the date and time that the overlap period started.
Name Location Description

Period to Conference Company The time period between automatic pass
Passcode Renewal code refresh cycles
Period of Passcode Company The time period for which the old pass codes
Overlap are still valid
PassCodeChangedDT Conference The date and time that the pass codes were
last changed
OverlapStartDT Conference The date and time that the overlap period
started

Configuring the CRS
In order for the overlap aspect of this feature to operate successfully, two demand conferences
co-exist:
• The old on-demand conference with the old pass codes.
• The new on-demand conference with the new pass codes.
These two conference co-exist for the duration of the Period of Passcode Overlap parameter.
Each night, the CRS runs a scheduled task called DoRenewPassCodes. DoRenewPassCodes
performs the following actions:
• Creates a new demand conference where:
PassCodeChangedDT + (Period to Conference Passcode Renewal - Period of Passcode
Overlap) < NOW()
• Generates an e-mail notification for each new demand conference.
• Removes or cancels all demand conferences where:
OverlapStartDT + Period of Passcode Overlap < NOW()
• Generates an e-mail notification for each removed demand conference.
When DoRenewPassCodes creates a new conference, it moves all participants to the new
conference. DoRenewPassCodes also moves the Import Utility identification (ImportID) to the
new conference. The new conference becomes the primary conference. If an operator changes
the old conference during the overlap period, the changes will not be reflected in the new
conference. DoRenewPassCodes only selects on-demand conferences that match the
following criteria:
• Type: Meet-me, unattended, or flex flow
• State: Confirmed, in-progress, completed, billed
The state of a conference influences how DoRenewPassCodes handles it once the overlap
period ends. DoRenewPassCodes removes billed conferences but cancels confirmed, in-
progress, and completed conferences.
You can investigate any problems that occur during the renewal process by examining the
RenewConferencesHistory table in BSRes2. The Conferencing Import Utility application does
not import the Period to Conference Passcode Renewal and Period of Passcode Overlap fields
when you instruct it to import a Company record. This means that imported companies do not
use the passcode expiry feature.
Period of passcode overlap

The Period of Passcode Overlap parameter specifies the default value for the time period for
which the old pass codes are still valid. The Period of Passcode Overlap parameter has a
range of 0 to 30. Operators can modify this time period by entering a new value in the Overlap
Days field in the New Company and Edit Company dialogs.
Maximum number of login attempts

The Maximum Number Of Login Attempts parameter specifies the number of times a Web
Portal moderator can enter an incorrect password when they are attempting to log in to the

CRS configuration
Web Portal application. If their number of attempts exceeds the value in Maximum Number Of
Login Attempts, the CRS server disables their account.
Minimum password length

The Minimum Password Length parameter specifies the minimum password length for CRS
clients and consequently, Web Portal moderators. In the Conferencing environment, there is
a CRS client for each Web Portal moderator. The Minimum Password Length parameter also
specifies the minimum password length for CRS users. CRS users are:
• Administrators
• Supervisors
• Operators
• User-Administrators
• User-Auditors
The default value for the Minimum Password Length parameter is 4. The default value for the
Maximum Password Length parameter is 20 characters.
Minimum password complexity

The Minimum Password Complexity parameter specifies the level of password complexity for
CRS users, CRS clients and consequently, Web Portal moderators. There are four levels of
password complexity, as follows:
• 7-bit-ascii-lower
This is the most basic level of complexity. To enable this level of complexity, set the value
of Minimum Password Complexity to 1.
• 7-bit-ascii-upper
There must be some upper case characters in the password. To enable this level of
complexity, set the value of Minimum Password Complexity to 2.
• Digits
There must be some digits and some upper case characters in the password. To enable
this level of complexity, set the value of Minimum Password Complexity to 3.
• Other
There must be digits, upper case characters, and additional characters, such as # or =.,
in the password. To enable this level of complexity, set the value of Minimum Password
Complexity to 4.
The default value for Minimum Password Complexity is 0.
Period to password expiry

The Period To Password Expiry parameter, BSRes2 system parameter, specifies the lifespan
of a password in days. If you enable Period To Password Expiry, the Web Portal application

Configuring the CRS
prompts Web Portal administrators, wholesalers, and moderators to enter a new password if
they attempt to log in to the Web Portal using an expired password. The Period To Password
Expiry parameter forces CRS Front End operators, supervisors, and system administrators to
update their password following a configurable period of time.
For Period To Password Expiry to operate correctly for Web Portal Administrators and Web
Portal Wholesalers, you must ensure that Authentication Required at Login=1. Authentication
Required at Login is a parameter in the BSRes2 database.
For example;
• To ensure that all users update their password every 28 days, set Period To Password
Expiry=28. In this scenario, their password expires after 28 days and when they next log
in, the Web Portal prompts them to enter a new one. It is worth noting that if they are an
infrequent user, their next log in could occur on, for example, the 40th day.
• To ensure that all users never have to update their password, set Period To Password
Expiry=0. If Period To Password Expiry=0, no password expiry takes place.
When the period specified by Period To Password Expiry elapses, the CRS Front End prompts
the user to enter a new password. In this situation, the CRS Front End prompts the user for
the following information:
• Their old password
• A new password
• Confirmation of the new password
The Database users table stores a parameter, called PasswordChangedDateTime to record
the date that a user updates their password. Passwords are case-sensitive.
The Period To Password Expiry parameter also impacts client passwords. Operators create
new clients, edit clients, and delete clients.
As in previous releases of Meeting Exchange, CRS passwords are subject to the system
parameters Minimum Password Complexity and Minimum Password Length.
Default client phone number

The Default Client Phone Number parameter specifies the telephone number to add to a client
profile if there is no telephone number associated with a client. This parameter relates to two
Conferencing features called:
• Directory Services Client Application (DSCA)
• Import Utility
These two features enable you to bulk load large amounts of Conferencing data into the
Conferencing system. The DSCA feature enables you to leverage the account data on your
Lightweight Directory Access Protocol (LDAP) server. Using the DSCA, you can convert LDAP
accounts to Conferencing accounts. Typically, you can convert LDAP users to CRS clients. In
the Web Portal environment, CRS clients are Web Portal moderators. The Import Utility feature
enables you to import companies, clients, and conferences from an external application, such

CRS configuration
as another conferencing database, The data must conform to a format that Conferencing
recognizes.
In the case of the DSCA and Import Utility, if there is no telephone number associated with a
client record, Conferencing will associate the value in the Default Client Phone Number with
the record.
Period until user disabled

The Period Until User Disabled parameter specifies the length of time in days for which a user
must be inactive before the CRS disables their account. If Period Until User Disabled=0, the
CRS does not implement account expiry for users.
CRS users are defined as CRS operators, CRS supervisors, CRS administrators, CRS user-
auditors, or CRS user-administrators.
If a CRS user does not log in to the CRS Front End for the period of time defined by Period
Until User Disabled, the CRS disables the CRS user. Once the CRS disables the CRS user,
another CRS user, such as a CRS administrator, must enable the disabled CRS user.
Account expiry does not apply to system accounts. System accounts are defined as
applications which connect to the CRS. Each application which connects to the CRS requires a
system log-in. These applications include the Notifications Subsystem, and the Web Portal.
A parameter in the BSRes2 database, called LastLoginDateTime, records the date and time
when a user logs in to the CRS. This parameter is in the database users table.
A database stored procedure called, p_DisableInactiveLogons, disables any CRS user that
has exceeded the value in the Period Until User Disabled parameter. You can schedule this
job to run at a configurable frequency. Avaya recommends that you configure this stored
procedure to run on a daily basis.
When a CRS user re-enables a disabled account, the CRS resets the date and time in
LastLoginDateTime to the current date and time. If this functionality disables your own CRS
administrator account and there are no other CRS administrator accounts in your Conferencing
deployment, contact Avaya for reactivation.
Period until client disabled

The Period Until Client Disabled parameter specifies the length of time in days for which a
client must be inactive before the CRS disables their account. If Period Until Client Disabled=0,
the CRS does not implement account expiry for Clients, and hence, Web Portal Moderators.
In the Web Portal environment, CRS clients are called Web Portal moderators. Each Web
Portal moderator must have a CRS client account. CRS operators can create, edit, and delete
client accounts using the CRS Front End.
If a Web Portal moderator does not log in to the Web Portal for the period of time defined by
Period Until Client Disabled, the CRS disables the Web Portal moderator. Once the CRS
disables the Web Portal moderator, a CRS user, such as a CRS operator, must enable the
Web Portal moderator.

Configuring the CRS
A parameter in the BSRes2 database, called LastLoginDateTime, records the date and time
when a user logs in to the CRS. This parameter is in the database client table.
A database stored procedure called, p_DisableInactiveLogons, disables any CRS client that
has exceeded the value in the Period Until Client Disabled parameter. You can schedule this
job to run at a configurable frequency. Avaya recommends that you configure this stored
procedure to run on a daily basis.
When a CRS user re-enables a disabled client account, the CRS resets the date and time in
LastLoginDateTime to the current date and time.
URL to reset participant secret PIN

The URL To Reset Participant Secret PIN parameter specifies the Website where conference
participants can reset their secret PIN.
A secret PIN is a participants' unique, self-managed, hidden number. You cannot see this
number but you can reset it for participants, using the CRS Front End. When you reset it, the
CRS sends the participant an e-mail notification, which contains a link to a Website where they
can change their own number.
Using this parameter, you must configure the address of the PIN Management Website where
participants can change their own secret PIN. In order for this feature to operate successfully,
you must install a Web Portal which is directed at the CRS.
When they book conferences, if CRS operators or Web Portal moderators select Identify and
Validate, all conference participants must enter an identifying number and a secret PIN on
their telephone keypad prior to entering the conference. In some cases, this number identifies
and validates an individual participant. In other cases, this number identifies and validates a
participant as an external guest participant.
The CRS allocates a "guest" secret PIN and a "guest" employee identification number to:
• All participants who join conferences from outside of your organization. These are people
who are not listed as participants of your CRS.
• All participants created by CRS operators or Web Portal moderators.
The CRS allocates a true identifying number and secret PIN number to:
• All participants imported from the Import Utility.
• All participants imported from the Directory Services Client Application (DSCA).
To configure the values of the "guest" secret PIN and a "guest" employee identification number,
you must configure the External User Participant Identifier and External User Participant PIN
parameters.
External user participant identifier

A participant identifier is a unique number which is allocated to each participant or it is a number
which identifies a participant as someone who has joined the conference from outside of the

CRS configuration
organization. Typically, a participant identifier is a widely available number, as opposed to a

secret number. For example, it can be a Human Resources employee number.
When they book conferences, if CRS operators or Web Portal moderators select Identify, all
conference participants must enter this identifying number on their telephone keypad prior to
entering the conference. In some cases, this number identifies an individual participant. In
other cases, this number identifies a participant as an external guest participant.
This parameter, the External User Participant Identifier parameter, specifies the value of the
“guest” employee identification number.
External user participant PIN

A secret PIN is a participants' unique, self-managed, hidden number.
When they book conferences, if CRS operators or Web Portal moderators select Identify and
Validate, all conference participants must enter an identifying number and a secret PIN on
their telephone keypad prior to entering the conference. In some cases, this number identifies
and validates an individual participant. In other cases, this number identifies and validates a
participant as an external guest participant.
This parameter, the External User Participant PIN parameter, specifies the value of the “guest”
secret PIN.

Configuring the CRS
Notification settings
The Notification Settings section contains a large number of parameters relating to e-mail
notifications. If you enable e-mail notifications, Conferencing sends conference participants an
invitation e-mail to invite them to upcoming conferences.
Related topics:
Conference reminder X minutes before on page 208
Activate e-mail notifications on page 208
Activate attachments on page 209
Attachments directory on page 209
Activate attendance notifications on page 210
Web conferencing URL on page 210
Activate vcalendar on page 210
Activate SMTP on page 210
SMTP server address on page 210
SMTP server port on page 211
SMTP username on page 211
SMTP password on page 211
E-mail sender on page 211
Authenticate on page 211
HTML format on page 211
Attendance record processing delay on page 212
Introduction to notifications on page 323
Conference reminder X minutes before

The Conference Reminder X Minutes Before parameter relates to the notification options
feature on the CRS Front End Options dialog. When operators schedule conferences, they
can specify notification options, such as a reminder option. When operators select the reminder
notification option, conference participants receive a reminder before the conference starts.
The Notifications Subsystem is the mechanism that sends the notification. This parameter
specifies the timing of the reminder. For example, if Conference Reminder X Minutes
Before=180, then each participant receives a reminder 180 minutes (3 hours) before the
scheduled start time.
Activate e-mail notifications

The Activate E-mail Notifications parameter specifies whether Conferencing sends e-mails to
remind and inform participants of conferences. Some examples of e-mail notifications include:
• Invitations to a booked conference
• Confirmations of a conference booking (sent to the moderator only)

CRS configuration
• Reminders to participants of conference details (sent at a configurable time before the

conference start, for example, 15 minutes before the conference)
• Notifications to make conference moderators and conferees aware of any changes or
cancellations to bookings
• Lists of conference attendees after the conference has taken place (sent to the moderator
only)
At booking time, operators using CRS Front End and moderators using Web Portal can specify
which types of e-mail notifications they would like to send. You must enable this parameter in
order to make the e-mail notifications option available at booking time.
Activate attachments
The Activate Attachments parameter specifies whether moderators can send attachments with
conference invitations using the Web Portal application. To enable moderators to send
attachments in Web Portal, you must enable this parameter.
Using Web Portal, moderators can invite conferees to their conference using a number of
methods. The Activate Attachments parameter applies to situations whereby a moderator
invites conferees using the on-board Web Portal address book.
Attachments directory
The Attachments Directory parameter specifies a folder that the Notifications Subsystem
checks for files to send as attachments to conference invitations sent from Web Portal.
methods. If they invite conferees using the on-board Web Portal address book, they can add
attachments to the conference invitation.
The Notifications Subsystem is the application which provides e-mail and SMS broadcast
services for Conferencing.
When moderators, using Web Portal, attach a file to a conference invitation, the Web Portal
copies the file to a folder on the Conferencing application server. The Notifications Subsystem
checks this folder on the application server and attaches the file to the conference invitation.
This parameter specifies the folder on the application server that the Notifications Subsystem
checks for files. You must ensure that you configure a value on the Web Portal to ensure that the
Web Portal copies the file to the same folder. The two values must be consistent in order for
the feature to operate successfully. The Web Portal parameter is in webportal.properties and
is called AttachmentsFolder.
An issue arises because the Web Portal virtual machine uses the Linux operating system and
the CRS virtual machine uses the Windows operating system. The Notifications Subsystem
resides on the CRS virtual machine. The CRS virtual machine has difficulties reading the Linux
syntax for the folder location. As a result, you have to perform some manual configuration. On
the CRS virtual machine, you must map a new network drive for \\<Web Portal virtual machine

Configuring the CRS
IP address>\attachments. Ensure that you select Reconnect at Login and set avaya as both
the username and password.
Related topics:
Configuring the attachment folder and security
Activate attendance notifications

The Activate Attendance Notifications parameter specifies whether Conferencing sends a list
of the participants to a moderator when a conference finishes. An application called Post
Conference Reports generates the attendance information when a conference completes.
which types of notifications they would like to send. You must enable this parameter to ensure
that Conferencing can successfully send the attendance report.
Web conferencing URL

The Web Conferencing URL parameter specifies the uniform resource locator (URL) address,
or link, for the Avaya Web Conferencing (AWC) application. When moderators using Web
Portal or operators using the CRS book a conference that includes a Web conference aspect,
Conferencing includes the Web conference link in the e-mail invitation notification for all
participants. Web conferences are also known as data conferences. The AWC application is
the application which enables Web conferences. AWC operates alongside the Conferencing
server to provide a combined audio and data conference experience. Using AWC, moderators
can present slides, annotate whiteboards, and exchange messages.
Activate vcalendar
The Activate vCalendar parameter specifies whether Conferencing generates a vcalendar file
for each scheduled conference. If you enable the Activate vCalendar parameter, Conferencing
generates a vcalendar file and attaches it to conference invitation notification e-mails.
vCalendar is an industry standard format for exchanging scheduling and activity-recording
information electronically. If Conferencing sends a vCalendar attachment in an invitation e-
mail, participants can drag-and drop it (or otherwise move it) to a personal information manager
(PIM) type of application program and integrate with or relate it to their own schedule.
vCalendar was developed along with the vCard electronic business card specification.
Activate SMTP
The Activate SMTP parameter specifies whether Conferencing uses the Simple Mail Transfer
Protocol (SMTP) protocol for e-mail notifications.
Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (e-mail)
transmission across Internet Protocol (IP) networks.
By default, the Activate SMTP parameter is not selected.
SMTP server address

The SMTP Server Address parameter specifies the SMTP server address used by the stored
procedure p_CheckMailAndSend. The co-chairperson feature also uses the SMTP Server

CRS configuration
Address parameter. The p_CheckMailAndSend stored procedure checks for e-mails in the
EMailMessage table and sends them.
SMTP server port

The SMTP Server Port parameter specifies the SMTP server port used by
p_CheckMailAndSend. The co-chairperson feature also uses the SMTP Server Port
parameter. The p_CheckMailAndSend stored procedure checks for e-mails in the
SMTP username
The SMTP Username parameter specifies a username that Conferencing uses to log in to the
e-mail server for all e-mail notifications. The e-mail server requires a username and a password
if Authenticate is selected. The Authenticate parameter adds a layer of security to the e-
mail communications.
SMTP password
The SMTP Password parameter specifies a password that Conferencing uses to log in to the
E-mail sender
The E-mail Sender parameter specifies the name or phrase that Conferencing enters in the
From field of the e-mail notifications that it sends. For example, if the E-mail Sender parameter
is conferencing@customername.com, participants receive e-mail notifications from this
e-mail address.
Related topics:
Ensuring that Conferencing notification e-mails are not classified as junk on page 480
Authenticate
The Authenticate parameter specifies whether Conferencing requires a username and a
password to log in to the e-mail server. The Authenticate parameter adds a layer of security
to the e-mail communications.
HTML format
The HTML Format parameter specifies whether Conferencing uses Hyper Text Markup
Language in the e-mails that it sends. If you do not select the HTML Format parameter,
Conferencing uses plain text in the e-mails that it sends.

Configuring the CRS
Attendance record processing delay

The Attendance Record Processing Delay parameter specifies the number of minutes after
the current time that must elapse before the Post Conference Report application queries the
data for this time period.
The Post Conference Report application examines the booking and billing databases and
makes conference details available to other applications, such as the Notifications Subsystem.
The Notifications Subsystem is the e-mail and SMS broadcast provider for Conferencing. The
Post Conference Report application polls the booking database at a configurable time period
and obtains a list of closed conferences. For example, if Attendance Record Processing
Delay=15, the Post Conference Report application polls the database every 15 minutes for
conferences that closed in the last 15 minutes.
Billing settings
The Billing Settings section contains a large number of parameters in relation to the production
of Conferencing bill files.
Related topics:
Primary bill file location on page 212
Secondary bill file location on page 212
Bill file extension on page 213
Bill file prefix on page 213
Bill frequency on page 213
Bill start offset (mins) on page 213
Bill at time on page 214
Bill file header on page 214
Bill file trailer on page 214
Period to retain CDR files on page 214
Free if cancelled X minutes before on page 214
Introducing billing on page 313
Primary bill file location

The Primary Bill File Location parameter specifies the folder location where Conferencing
outputs and stores conference billing files. By default, the Primary Bill File Location parameter
is C:\BILL\files. The Conferencing billing application also generates back-up billing files
and stores them in an alternative location, specified by the Secondary Bill File Location
parameter.
Secondary bill file location

The Secondary Bill File Location parameter specifies the folder location where Conferencing
outputs and stores conference billing files. By default, the Secondary Bill File Location

CRS configuration
parameter is C:\BILL\files2. The secondary bill file location is for redundancy.

Conferencing also outputs billing files to a primary bill file location.
Bill file extension

The Bill File Extension parameter specifies the extension on the billing files that Conferencing
produces. By default, the Bill File Extension parameter is bil.
Bill file prefix

The Bill File Prefix parameter specifies the prefix of the bill file name. So, the full file name
consists of:
<Bill File Prefix><Bill Stamp>.<Bill File Extension>
Bill Stamp is the current file number.

For example, if the Bill File Prefix is Avaya_, the Bill Stamp is 123, and the Bill File Extension
is .bil, the next bill that Conferencing produces is Avaya_123.bil.
There is a special situation if you configure the Bill File Prefix parameter to the value <date>. In
this situation, Conferencing uses a special, date-based file name format. If the Bill File Prefix
parameter has the value <date>, Conferencing ignores the Bill Stamp number. Instead,
Conferencing names the files according to the current date, using the following format and
syntax:
YYMMDDNN.bil
• YY=year, where 2000=00
• MM=month, where October=10
• DD=day, such as 31
• NN=the file number on that particular day
For the first bill of the day, NN=00. The number increases incrementally from then
onwards. If the NN number reaches 99, Conferencing does not run until the date changes.
Bill frequency
The Bill Frequency parameter specifies how often Conferencing runs the billing cycle. If the
Bill Frequency parameter is 0, Conferencing generates a bill every day at the time specified
by the Bill At Time parameter.
Bill start offset (mins)

Bill Start Offset (mins) enables you to further configure the Bill Frequency setting. It enables
you to specify the minute part of the billing process schedule. If you set Bill Start Offset (mins) to
35, for example, and Bill Frequency is set to 1, then the billing schedule will look like this: 00:35,
01:35, 02:35, 03:35....and so on.

Configuring the CRS
When Bill Start Offset (mins) is 0, this feature is turned off. When this setting is 0, then the
billing schedule depends on the time at which you start the application.
Bill at time
The Bill At Time parameter specifies the time that Conferencing produces billing data.
Conferencing uses this parameter solely for daily bills. By default, the Bill At Time parameter
is 0100.
Bill file header

The Bill File Header parameter specifies whether Conferencing adds a header to the bill output
file. If you select the Bill File Header parameter, Conferencing adds a header.
Bill file trailer

The Bill File Trailer parameter specifies whether Conferencing adds a footer to the bill output
file. If you select the Bill File Trailer parameter, Conferencing adds a footer.
Period to retain CDR files

The Period to Retain CDR Files parameter specifies an age threshold in days. If a file is older
than the value of this parameter, an automatic deletion task deletes it. For example, if Period
to Retain CDR Files=30, the CDR Loader automatically deletes the file if it is older than 30
days. The Call Detail Records (CDR) Loader is an application that transfers CDRs data from
the Conferencing application server, or bridge, to the CDRs database. The CDR Loader
application also supports the creation of billing information for a number of different bridges
using a single interface.
Free if cancelled X minutes before

The Free If Cancelled X Minutes Before parameter relates to the billing of cancelled
conferences. Cancelled conferences are billed if they are cancelled too late. If the cancellation
occurs no later than the time frame allotted in the Free If Cancelled X Minutes Before
parameter, the customer will not be billed. For example, if Free If Cancelled X Minutes
Before=180, a client that cancels a conference 180 minutes (3 hours) before its scheduled
start time is not billed. If a conference is cancelled within that time frame, Conferencing bills
the client.
Perpetual conference settings

A perpetual conference is a repeat conference that is automatically extended. This occurs
without any operator or system administrator intervention. Conferencing sends an optional e-
mail to confirm the conferences that have been successfully extended. Any conferences that
fail to be rebooked automatically are indicated in the e-mail, along with the cause. Conferencing
sends this e-mail using SMTP protocols. A possible cause could be if the passcode had been
allocated to another conference. The failure reason is also displayed on the CRS Front End.

CRS configuration
To book a perpetual conference, an operator must schedule a repeat booking in which the
number of conferences exactly equals the maximum possible conferences in a single
reservation. A parameter called, Maximum Number of Conferences Per Booking, determines
the maximum number of conferences that can be booked in a single reservation. For example,
if Maximum Number of Conferences Per Booking=100, operators can book conferences that
repeat up to 100 times. If an operator attempts to book a conference that repeats 101 times,
an error message is displayed. If they book fewer conferences, the repeating conference is
not interpreted as a perpetual conference.
A parameter called Perpetual Conference PreBook Period specifies the number of days by
which a conference booking should be extended. If Perpetual Conference PreBook Period=30,
the system extends all perpetual conferences to 30 days from the current date. Perpetual
Conference PreBook Period is located in the BSRes2 database.
Conferencing checks for conferences that may need to be extended via a scheduled job, called,
ExtendPerpetualConferencesJob. By default, ExtendPerpetualConferencesJob is scheduled
to run on a weekly basis. The ExtendPerpetualConferencesJob:
• Checks for reservations that may need to be extended.
• Extends reservations that meet the criteria for extension.
• Checks for e-mails in the EMailMessage table and sends them.
The following parameters are involved in perpetual conferencing:
• Perpetual Conference PreBook Period
• Perpetual Conference Recipient Email Address
• Perpetual Conference CC Email Address
• Perpetual Conference Sender Email Address
• SMTP Server Address
• SMTP Server Port
The following scheduled jobs are involved in perpetual conferencing:
• p_CheckMailAndSend
• p_ExtendPerpetualConf
• p_ExtendPerpetualConfs
If the Maximum Number of Conferences Per Booking parameter is increased, conferences that
previously qualified as perpetual conferences may no longer qualify. This is because the
number of repeat conferences may no longer equal Maximum Number of Conferences Per
Booking. For conferences to qualify as perpetual conferences, they must be repeat
conferences and the number of repeat conferences must equal Maximum Number of
Conferences Per Booking. As a result, you must adjust perpetual conferences if you the
increase Maximum Number of Conferences Per Booking parameter.

Configuring the CRS
Related topics:
Perpetual conference prebook period on page 216
Perpetual conference recipient e-mail address on page 216
Perpetual conference CC e-mail address on page 216
Perpetual conference sender e-mail address on page 216
Perpetual conference prebook period

The Perpetual Conference Prebook Period parameter specifies the number of days by which a
perpetual conference should be extended.
Perpetual conference recipient e-mail address

The Perpetual Conference Recipient Email Address parameter specifies the e-mail address
to which p_CheckMailAndSend sends e-mails. A valid e-mail address must be specified here.
Perpetual conference CC e-mail address

The Perpetual Conference CC E-mail Address parameter specifies another e-mail address to
which p_CheckMailAndSend sends e-mails. This parameter must be set to a valid e-mail
address or a blank string.
Perpetual conference sender e-mail address

The Perpetual Conference Sender Email Address parameter specifies the e-mail address from
which p_CheckMailAndSend sends e-mails. A valid e-mail address must be specified here.
Groupware clients
Groupware is a term that Avaya uses to refer to a number of 'plug-in' applications which it has
developed in order to integrate Conferencing functionality with external applications, such as
Microsoft™ Outlook, Live Meeting, and Office Communicator and IBM Lotus™ Notes and
Sametime.
The Conferencing plug-ins manifest themselves as extra buttons or menus on the existing
interfaces of the external applications.
The value of a Conferencing plug-in is that moderators can book and manage their conferences
without having to install and operate a dedicated Conferencing interface, such as Web Portal or
CRS Front End. Avaya has ensured that the plug-ins are easy to deploy and require no
additional technical instruction for regular computer users.
If your deployment includes any of the groupware plug-ins or clients, you must configure these
settings. If your deployment includes the Conference Scheduler Plug-in for Microsoft Outlook,
you must also configure the settings in the Outlook Settings section.
Related topics:
BCAPI username on page 217

CRS configuration
Override mask on page 217

Attribute mask on page 218
BCAPI username
The Bridge Control API (BCAPI) is an object-oriented, programming interface, written in Java.
The API can be used by any application that can make a Java call, such as IBM Lotus Notes.
The BCAPI Username parameter specifies the sign-in name of the Conferencing application
server. By default, it is set to jc3. You must configure this parameter to jc3 if the Conferencing
deployment includes the Avaya Plug-in for IBM Lotus Notes. The BCAPI Username parameter
is essential for the successful operation of the Click-to-Call feature in the Avaya Plug-in for
IBM Lotus Notes.
Override mask
The Override Mask parameter specifies which conferencing options are displayed on the
Conference Scheduler for Microsoft Outlook, by default. For example, you might want to hide
certain options from users, by default.
Some conferencing options have dependencies. For example, for the successful operation of
Roll Call, Name Announcement on Entry, and Name Announcement on exit, you must display
Prompt Conferees For Name On Entry.
You can enable or disable the following settings:
• Play Tone on Entry
• Play Tone on Exit
• Play Name on Entry
• Name Announcement on Exit
• Auto-Generate Codes
• Play Wait for Moderator
• No Operator Allowed
• Request Bill Code
• Prompt Moderator for Security Code on Entry
• Moderator Hand-Up
• Allow Manual Port Extension
• Allow Manual Duration Extension
• Allow Conference Recording
You should not make changes to any settings that are not in this bullet list.
A file called profile.xls contains a list of these settings. The profile.xls file is located in
<Conferencing application server IP address>/outlook/files/profile.xls. Using profile.xls, you
can display or hide the settings in accordance with your requirements. The relevant settings
are in column C, from row 60 to row 112. A function in cell C116 computes a binary value based

Configuring the CRS
on your settings. Using a scientific calculator, you must convert this value to a decimal amount.
You can then enter this decimal value in the Override Mask field.
Attribute mask
The Attribute Mask parameter specifies which conferencing options are enabled on the
Conference Scheduler for Microsoft Outlook, by default. For example, you might want to enable
roll call, by default.
Some conferencing options have dependencies. For example, for the successful operation of
Roll Call, Name Announcement on Entry, and Name Announcement on exit, you must enable
Prompt Conferees For Name On Entry.
You can enable or disable the following settings:
• Play Tone on Entry
• Play Tone on Exit
• Play Name on Entry
• Name Announcement on Exit
• Auto-Generate Codes
• Play Wait for Moderator
• No Operator Allowed
• Request Bill Code
• Prompt Moderator for Security Code on Entry
• Moderator Hand-Up
• Allow Manual Port Extension
• Allow Manual Duration Extension
• Allow Conference Recording
You should not make changes to any settings that are not in this bullet list.
A file called profile.xls contains a list of these settings. The profile.xls file is located in
<Conferencing application server IP address>/outlook/files/profile.xls. Using profile.xls, you
can enable and disable the settings in accordance with your requirements. The relevant
settings are in column C, from row 5 to row 57. A function in cell C115 computes a binary value
based on your settings. Using a scientific calculator, you must convert this value to a decimal
amount. You can then enter this decimal value in the Attribute Mask field.
Outlook settings
If your deployment includes the Conference Scheduler Plug-in for Microsoft Outlook, you must
configure the Outlook Settings. If you wish, you can retain the default values.

CRS configuration
Related topics:
Invitation header on page 219
Invitation body on page 219
Audio numbers on page 219
On demand on page 219
Schedule on page 219
Web conference on page 220
Join conference on page 220
Show roster list on page 220
Most recent list size on page 221
Invitation header
The Invitation Header parameter specifies the text in the Subject field of e-mails that
Conferencing sends using the Conference Scheduler Plug-in for Microsoft Outlook.
Invitation body
Invitation Body specifies the text that Conferencing displays in the body of e-mails that it sends
using the Conference Scheduler Plug-in for Microsoft Outlook.
Audio numbers
The Audio Numbers parameter specifies the Conferencing telephone number for recipients of
e-mail invitations that Conferencing sends using the Conference Scheduler Plug-in for
Microsoft Outlook. This is a free text field. You can enter explanatory words and several
numbers.
On demand
You can configure which features are displayed on the Conference Call tab of the New
Appointment dialog. For example, you can configure the Avaya Plug-in for Microsoft Outlook
to display or hide the Use on-demand audio conference checkbox. If you choose to display
the checkbox, you can display it in an available state or in a disabled and inaccessible state.
• Select On from the On Demand drop-down list to display and enable the Use on-
demand audio conference.
• Select Off/Hide from the On Demand drop-down list to ensure that the Use on-
demand audio conference checkbox is not displayed. If you select this option, the
feature is also disabled.
• Select Off/Show from the On Demand drop-down list to display but disable the Use on-
demand audio conference checkbox.
Schedule

Configuring the CRS
to display or hide the Schedule an audio conference checkbox. If you choose to display the
checkbox, you can display it in an available state or in a disabled and inaccessible state.
• Select On from the Schedule drop-down list to display and enable the Schedule an
audio conference.
• Select Off/Hide from the Schedule drop-down list to ensure that the Schedule an audio
conference checkbox is not displayed. If you select this option, the feature is also
disabled.
• Select Off/Show from the Schedule drop-down list to display but disable the Schedule
an audio conference checkbox.
This setting also impacts the Conferencing Plug in for IBM Lotus Notes.
Web conference
to display or hide the Web Conference checkbox. If you choose to display the checkbox, you
can display it in an available state or in a disabled and inaccessible state.
• Select On from the Web Conference drop-down list to display and enable the Web
Conference.
• Select Off/Hide from the Web Conference drop-down list to ensure that the Web
Conference checkbox is not displayed. If you select this option, the feature is also
disabled.
• Select Off/Show from the Web Conference drop-down list to display but disable the Web
Conference checkbox.
Join conference
to display or hide the Join a Conference button. If you choose to display the checkbox, you
can display it in an available state or in a disabled and inaccessible state.
The Join a Conference button enables participants to enter the conference telephone number
in a Join Conference dialog and to click Dial to enter the conference.
• Select On from the Join Conference drop-down list to display and enable the Join a
Conference.
• Select Off/Hide from the Join Conference drop-down list to ensure that the Join a
Conference checkbox is not displayed. If you select this option, the feature is also
disabled.
• Select Off/Show from the Join Conference drop-down list to display but disable the Join
a Conference checkbox.
Show roster list

The Show Roster List parameter specifies whether the conference invitation e-mail displays a
link to the Audio Console application. The Audio Console application shows a live graphic

CRS configuration
depiction of the conference, with icons to represent the participants and their states. There are
three possible values:
• Off/Show
Select Off/Show to hide the link to the Audio Console application.
• Off/Hide
Select Off/Hide to hide the link to the Audio Console application.
• On
Select On to display a link to the Audio Console application. Participants can click on this
link at the conference time to see a graphic representation of the conference.
Most recent list size

The Most Recent List Size parameter specifies the maximum number of previously entered
dial numbers that the Conference Scheduler Plug-in displays in the Enter Phone Number
drop-down list on the Join Conference dialog. The default value is 10.

Secure Access Link (SAL) is an Avaya serviceability solution for support and remote
management of a variety of devices and products. SAL provides remote access and alarm
reception capabilities. SAL uses the existing Internet connectivity of a customer to facilitate
remote support from Avaya. All communication is outbound from the environment of the
customer over port 443, and uses encapsulated Hypertext Transfer Protocol Secure (HTTPS).
The Conferencing logs and alarms are now generated using the Avaya Secure Access Link
(SAL) infrastructure.
Related topics:
Obtaining the three pieces of information on page 105
Configuring logs and alarms on page 106
Avaya Aura™Conferencing 6.0 Managed Element ID

The Avaya Aura™ Conferencing 6.0 Managed Element ID is a 10 digit numeric sequence which
you can obtain from Avaya.
The Avaya Aura™ Conferencing 6.0 Managed Element ID is called Avaya Aura™Conferencing
ID in the Conferencing Manager and System Manager administrative interfaces.

Configuring the CRS
Enrollment password
An enrollment password is a unique code that Conferencing Manager generates. You require
this code in order to configure logs and alarms. As an alternative to accepting the code that
Conferencing Manager provides, you can enter your own phrase as an enrollment password.
Configuring general settings

Prerequisites
Before you configure general settings, ensure that you install Conferencing and assign each
of the application servers to the CRS virtual machine in the Components section.

Conferencing Manager may display the IP address of the available CRS virtual
machine.
3. Select the CRS virtual machine if necessary.
4. Click Configure.
8. Click Save.
It is a good idea to apply changes only when you are finished all your configuration
tasks.
Example
For example, if you wish to limit the size of conferences to 50 people, change the value of
Maximum Conference Size to 50. The default value of Maximum Conference Size is 180
people.

CRS configuration
Next steps
Now, you can make further CRS configuration changes, such as configuring timezones or
adding resellers.
Reseller settings
The Standard Edition of Conferencing does not support resellers.
Timezone settings
You control the number of time zones used with in Conferencing. You can configure numerous
time zones. However, most customers only use a few, major time zones.
In the CRS database called BSRes2, the timezone table also has a Coordinated Universal
Time (UTC) field. It is a read-only field and you cannot edit it. The UTC field ensures that the
SOAP Adaptor treats conference times correctly, even if you delete or move the GMT timezone.
The Conference Scheduler Plug-in for Microsoft Outlook uses the SOAP Adaptor.
Fields Description
Name The time zone name as well as any associated cities.
Offset The standard time difference between each time zone. The offset is calculated
against GMT (0). For example, the offset for New York is -300, which is 300
minutes or 5 hours behind GMT.
Start DST The date and time when Daylight Savings Time starts using the dd/mm/
yyyyhh:mm format. Daylight savings time (DST) occurs on a different date
each year. DST must be configured annually.
DST Offset The time (in minutes) when accounting for annual daylight savings, usually 60
minutes.
Finish DST The date and time when Daylight Savings Time ends using the dd/mm/
yyyyhh:mm format.
Related topics:
Configuring timezones on page 223
Timezones on page 475
Configuring timezones
The purpose of this task is to add, edit, or delete timezones.

Configuring the CRS

machine.
4. Click Configure.
5. On the Client Registration Server configuration sub-pages screen, click
Timezones.
6. Click New to add a new timezone.
You can delete any existing timezones using the Delete button.
7. Enter timezone information in the new row.
8. Click Save.
tasks.
Next steps
Now, you can make further CRS configuration changes.
User settings
It is a good idea, at this point, to clarify the term, users. CRS users are:
• Administrators
• Supervisors
• Operators
• User-Administrators
• User-Auditors
The CRS Front End represents each of these users on the Login screen of the Systems
Administration section. People who make use of the audio conferencing facilities that
Conferencing provides, are called clients or, on the Web Portal application, moderators.

CRS configuration
User Type Description

Administrator Administrators can perform all operator and supervisor tasks. In addition,
they can manage Conferencing resources and configure Conferencing
parameters, using the System Administration section of on the CRS
Front End.
If administrators contact Avaya Support, the Avaya Support Engineers
can activate the user-administrator and user-auditor roles. Once the
Avaya Support engineers activate these roles, administrators can create
user-administrators and user-auditors.
Supervisor Supervisors can perform all Operator tasks. In addition, they can also
manage Resellers.
Operator Operators can create company and client accounts. They can also
create and manage conferences. In addition, operators can view existing
schedules and print conference reports and reservations.
For more information on operator tasks, see the Operating Avaya Aura™
Conferencing Guide, which is available from support.avaya.com
User- User-administrators can create, edit, and delete operators and
administrator supervisors. They can also view the Login Change History screen, which
documents significant changes to users.
User-auditor User-administrators can view the list of users. They can also view the
Login Change History screen, which documents significant changes to
users.
For each user, Conferencing saves a number of details.
Field Description
Name, Description, and E-mail address Enter a name, brief description, and a
contact e-mail address for the user.
Level A user’s system privilege level.
Password The password acts as a second level of
security as the user accesses the CRS Front
End. The maximum password length is 20
characters. You can set the minimum
password length using Minimum Password
Length. You can also set varying levels of
password complexity using Minimum
Password Complexity. There are four
levels of password complexity, as follows:
(1) 7-bit-ascii-lower: This is the most basic
level of complexity.
(2) 7-bit-ascii-upper: You must include some
upper case characters.
(3) Digits: You must include some digits and
some upper case characters

Configuring the CRS
Field Description
(4) Other: You must include digits, upper
case characters, and additional characters,
such as # or =.
If you have advanced knowledge on the
Conferencing solution, you can choose to
enable or disable the password feature. If it
is enabled, users are required to enter a
password when they log on. To enable this
feature, ensure that ValidationRequired=1 in
the bands.ini file and ensure that the system
parameter, ValidationLevel=1, in the
BSRes2 database. If the feature is disabled,
a password is not required for log on. To
disable this feature, ensure that
ValidationRequired=0 in the bands.ini file
and ensure that the system parameter,
ValidationLevel=0, in the BSRes2 database.
ValidationLevel is the CRS server-side
setting. ValidationRequired is the CRS client-
side setting. If the two values are
inconsistent, the CRS server imposes
synchronization by propagating the server-
side value to the client side. In this event, the
first log-in attempt by the CRS client fails and
the CRS server resets the value. Any
subsequent log-in attempt should be
successful.
You can also configure password expiry.
Using this functionality, you can force
operators to update their password following
a configurable amount of time.
Confirm password You must re-enter the password that you
have entered in the Password field.
Disabled You can disable users so that they cannot
access CRS Front End. If a user does not log
in to the CRS Front End for a configurable
period of time, the CRS can also disable the
user.
Owner A user or login can be a system login or a
wholesaler login. System users are not
associated with a Wholesaler. Wholesaler
users are associated with a wholesaler. If you
would like to associate the user with a
wholesaler, you can select the wholesaler
here.

CRS configuration
Password expiry
You can force users to update their password following a configurable period of time using
Period to Password Expiry.
For example:
• To ensure that all users update their password every 28 days, set Period to Password
Expiry to 28.
• To ensure that CRS Front End users never have to update their password, set Period to
Password Expiry to 0. If Period to Password Expiry is 0, no password expiry takes
place.
When the period specified by Period to Password Expiry elapses, the CRS Front End
prompts the user to enter a new password. In this situation, the CRS Front End prompts the
user for the following information:
• Their old password
• A new password
• Confirmation of the new password
The Database users table stores a parameter, called PasswordChangedDateTime to record
the date that a user updates their password. Passwords are case-sensitive. Using Avaya Aura™
Conferencing, which is available from support.avaya.com describes this aspect of the
password feature to users. The Period to Password Expiry parameter also impacts client
passwords. Operators create new clients, edit clients, and delete clients. For more information
on operator tasks, see the Operating Avaya Aura™ Conferencing Guide, which is available
from support.avaya.com.
User account expiry
If a CRS user, such as a CRS operator, CRS supervisor, or CRS administrator does not log
in to the CRS Front End for a configurable period of time, the CRS can disable the CRS user.
Once the CRS disables the CRS user, another CRS user, such as a CRS administrator, must
enable the disabled CRS user.
Similarly, if a Web Portal moderator does not log in to the Web Portal for a configurable period of
time, the CRS can disable the Web Portal moderator. Once the CRS disables the Web Portal
moderator, a CRS user, such as a CRS operator, must enable the Web Portal moderator.
As a reminder of the mapping between roles in the booking applications, it is worth stating that
each Web Portal moderator must have a CRS client account. CRS operators can create, edit,
and delete client accounts using the CRS Front End. CRS operators can also create, edit, and
delete conference reservations on behalf of clients on the CRS Front End.
A number of parameters from the CRS BSRes2 database control this feature:
Parameter Description
LastLoginDateTime (Users This parameter records the date and time when a user
table) logs in to the CRS. This parameter is in the database
Users table.
LastLoginDateTime (Client This parameter records the date and time when a Client
table) logs in to the CRS. When a Web Portal Moderator logs in

Configuring the CRS
to the Web Portal application, they create a Client
connection to the CRS. This parameter is in the database
Client table.
UserInactiveLogonThreshold This parameter is the length of time for which a user must
(Users table) be inactive before the CRS disables their account. If
UserInactiveLogonThreshold=0, the CRS does not
implement account expiry for users.
UserInactiveLogonThreshold This parameter is the length of time for which a client must
(Client table) be inactive before the CRS disables their account. If
UserInactiveLogonThreshold=0, the CRS does not
implement account expiry for clients, and hence, Web
Portal moderators.
When a CRS user, such as a CRS administrator, CRS supervisor, or CRS operator, re-
enables a disabled account, the CRS resets the date and time in LastLoginDateTime to the
current date and time.
A database stored procedure called, p_DisableInactiveLogons, disables any CRS user and
client accounts that have exceeded the value in UserInactiveLogonThreshold. As a CRS
administrator, you can schedule this job to run at a configurable frequency. Avaya recommends
that you configure this stored procedure to run on a daily basis.
Resetting passwords
There are two main reasons for resetting passwords:
• If a user has forgotten their password
• If a user account is disabled due to password expiry
If a user has forgotten their password, simply edit the user account. You can enter a new
password in the Password and Confirm password fields.
If the CRS disables a user account, you must uncheck the Disabled checkbox. You must also
enter a new password in the Password and Confirm password fields.
Related topics:
Configuring users on page 228
Configuring users
Prerequisites
Before you add users, ensure that you add any necessary wholesalers.
The purpose of this task is to add, edit, or delete users.

CRS configuration

machine.
4. Click Configure.
5. On the Client Registration Server configuration sub-pages screen, click Users.
6. Click New to add a new user.
You can edit or delete any existing users using the Edit or Delete buttons.
8. Enter user information.
9. Click Save.
tasks.
Wholesaler settings
The Standard Edition of Conferencing does not support wholesalers.

Configuring the CRS

Chapter 12: Configuring the AWC

Avaya Web Conferencing (AWC) is an application that enables audio conference participants
to share data and video during their conferences. It is a component of the Conferencing suite of
products. In older releases of Conferencing, AWC was sometimes called Data Xchange.
Using AWC, participants enter a data conference either by following an e-mail link or using
their Web browser to browse to a URL and then entering security details. The conference client
loads in the Web browser and enables participants to communicate with each other using the
following methods.
• Chat (sending text messages)
• Whiteboard (free-form text and drawings)
• Shared applications (one user can share a program running on their computer and other
users can see it in operation; another user can even take control and work with the
program as if it were running on their own computer)
• Slide shows (snapshots of the Whiteboard or shared applications, Microsoft™ Powerpoint
slides, or JPEG images or voting slides; all slides can be annotated as they are
discussed )
The tools above can be used to present different types of conferences. For example, the
conference can be run like a seminar in which a moderator or presenter gives a pre-
prepared pitch. In this scenario, the other conference participants make up the audience.
Alternatively, the moderator can choose to allow all participants to have full use of all the
communication methods. In that case, a group of computer users in different locations can
work together as though they were sitting at the same computer. They can chat to each other
and view and control the same programs.
Related topics:
Accessing AWC on page 95
Configuration of AWC using Conferencing Manager

Using the Conferencing Manager management console, you can configure a single aspect of
the AWC implementation. This single aspect is the type of authentication that the AWC

Configuring the AWC
authenticator uses to connect to the CRS server. The method that the AWC authenticator uses
to connect to the CRS server is unrelated to the participant log-in to the AWC application. When
a participant clicks on an AWC link to access an AWC conference, they must always enter the
conference reference number and the conference passcode. Participants must always enter
a conference reference number and the conference passcode, regardless of the type of
authentication that the AWC authenticator uses to connect to the CRS server.
In addition to configuring the type of authentication that the AWC authenticator uses to connect
to the CRS server, you must also configure AWC licenses, before you deploy the AWC in your
organization. By default, Conferencing ships with seven licenses for AWC. There are five
platinum licenses and two for over-alloaction. This means that you cannot connect more than
seven AWC clients to the CRS server without configuring additional licenses. In other words,
in order to support more clients, you must purchase more licenses.
• To configure the type of authentication that the AWC authenticator uses to connect to the
CRS server, you use the Conferencing Manager management console.
• To configure AWC licenses, you use the AWC virtual machine. You can access the AWC
virtual machine using the remote desktop function.
Related topics:
Login type
The Login Type drop-down menu displays the set of security validation methods that you wish
AWC authenticator to use when connecting to the CRS server. You can use this menu to select
an option for your deployment. You can force the authenticator to use both conference
reference and conference passcode. This is called strong authentication. Alternatively, you can
force the authenticator to just use the conference passcode but not the conference reference.
This is called weak authentication. Avaya recommends strong authentication.
As described, the method that the AWC authenticator uses to connect to the CRS server is
unrelated to the participant log-in to the AWC application.
Related topics:
Configuring login type on page 232
Configuring login type

Prerequisites
Before you configure the AWC virtual machine, you must install Conferencing and configure
connectivity between the various virtual machines in the Conferencing network.

Configuration of your network in preparation for AWC
The purpose of this task is to make the AWC feature available for your Conferencing
moderators and participants.

2. Navigate to Elements > Conferencing > Data Conferencing.
Conferencing Manager may display the IP address of the available AWC virtual
machine.
3. Select the AWC virtual machine if necessary.
4. Click Configure.
5. On the Data Conferencing configuration sub-pages screen, select the login type
from the Login Type drop-down list.
6. Click Save.
Next steps
In previous releases of Conferencing, you had to perform a large number of configuration tasks
on the CRS and AWC virtual machines. In the current release, there is a single configuration
task. The only configuration task is the configuration of a license for telephone ports. You can
proceed to this step now.
Configuration of your network in preparation for AWC

Tip:
For more information on the preparation of your network in advance of an AWC deployment,
contact your Avaya Support Representative and request a copy of the Conferencing Pre-
Installation Site Survey Implementation Workbook.
In a typical deployment, the application server, or bridge, virtual machine and the AWC virtual
machine are separated by a firewall. In a typical deployment, there is also a firewall between
the AWC virtual machine and the external Internet. These firewalls are in place even though
the Standard Edition of Conferencing is a virtualized solution. In order to enable the
communications between the application server and AWC, you must open several ports.

Configuring the AWC
Similarly, in order to enable communications between AWC and the external Internet, you must
open several ports.
Communications between application server and AWC
Open the following ports:
• 5020
• 5021
• 5022
• 5023
• 5040
• 20001
• 20002
Communications between AWC and the external Internet
Open the following ports:
• 80
• 443
Internal and external deployments
Some customer sites offer an internal AWC solution, while some customer sites offer an
external AWC solution.
An internal solution means that participants can only access the AWC Web site if they are on
the internal network. An external solution means that anyone can access the AWC Web site.
If you wish to offer an external solution, you must have a Fully Qualified Domain Name (FQDN)
that is resolvable both internally and externally.
Environmental requirements for AWC
Tip:
For more information on the environmental requirements for Conferencing, see the Avaya
Aura™ Conferencing Release Notes, which are available from support.avaya.com.
Make/Model IBM X3550 M2

Processor Two x Quad Core Intel® Xeon Processor X5520 4C (2.26GHz 8MB L3
Cache 1066MHz 80w)
Memory 8 GB (4 x 2GB DDR3-1333 2Rx8 LP RDIMM)Com
Bezel Avaya BEZEL
Raid RAID 5 - MR10i Integrated RAID Controller
Disk Drives 3 x 146GB SAS 2.5" 10K RPM 6G DP Hard Drive
Addl NIC's Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
Removable Media DVD-R/W SATA slimline

Configuration of the AWC virtual machine
Power Supply 2 x 675W 12V Hotplug AC power supply

Fans Redundant multi-speed fans
Firmware IMM v1.05, RAID v11.0.1-0019, uEFI v1.03 and HDD v1.05
Compatible cameras
AWC supports video. You can display a video window at the top right of the AWC screen which
sends a live video to the conference participants. This feature supports a large number of video
industry-standard cameras, including the following:
• Microsoft LifeCam VX-3000
• Labtec Pro
• D-Link DSB-C120
• Creative PD1170L4
• Philips SPC315NC
• Logitech - Quick Cam Chat
• Logitech - Quick Cam Zoom
• Logitech - Quick Cam Sphere
• Ezonics EZCam III
• Micro Innovations - Basic Webcam
• Sweex mini USB webcam
• Vimicro webcam
• A4Tech PK-7MA
Note:
Just to clarify, the Standard Edition of Conferencing does not support video in the sense of
the Conferencing application server providing a high quality video feed. However, the
Standard Edition of Conferencing does support the AWC deployment of video, which
consists of a small video window in the top right of the AWC screen.
Related topics:

In previous releases of Conferencing, there were a large number of manual tasks in the
configuration of AWC. These tasks included creating two databases, running scripts, installing
Java, licensing AWC, and integrating audio. In the current release of Conferencing, most of
these previously manually tasks are now automated. When you install Conferencing using the
Conferencing Manager interface, the Conferencing installer automatically creates and

Configuring the AWC
configures the databases, runs the required scripts, and completes most of the other
configuration tasks.
In fact, now there are only two configuration tasks for AWC:
• The application of an AWC license
• The configuration of the Microsoft Windows operating system password
By default, AWC ships to customers with support for five ports, or telephone lines. This
configuration enables you to check connectivity and verify functionality, but for field
deployment, you must upgrade the license to support a greater number of ports.
The AWC virtual machine uses the Microsoft Windows operating system. The AWC has a
Windows password. If this password expires, the AWC functionality does not operate
successfully. You must configure this password to ensure that it does not expire. You must
perform this task as soon as you install the AWC virtual machine.
In terms of ongoing administration tasks, you can log in to the AWC administrator interface to
monitor Conferencing activity.
Related topics:
Licensing AWC on page 236
Configuring the AWC Windows password on page 237
Licensing AWC
Prerequisites
Before you license AWC, you must contact your Avaya Support Representative to obtain a
license. Your Avaya Support Representative has access to a license generator tool and they
can create a license file and send it to you. It is a registry file with a file extension of .reg. There
are five types of license: Bronze, Silver, Gold, Platinum, and Video. These steps assume that
you have obtained a license and copied it to your current computer.
Note:
Just to clarify, the Standard Edition of Conferencing does not support video in the sense of
the Conferencing application server providing a high quality video feed. However, the
Standard Edition of Conferencing does support the AWC deployment of video, which
consists of a small video window in the top right of the AWC screen.
The purpose of this task is to upgrade from the default of five telephone ports to a larger number
of telephone ports.
1. On your computer, share out the folder in which you have saved the license file:
a. Right-click on the license folder and select Properties.

b. Click the Share tab and select Everyone from the sharing list.
2. Access the AWC virtual machine using the remote desktop feature.
c. In the Computer field, enter the AWC virtual machine IP address.
password is case-sensitive.
3. Access the shared folder which you shared out.
This folder contains the license file.
a. On the AWC virtual machine, click Start > Run.
b. Enter //<IP address of the computer on which you have saved
the license folder> in the Run dialog.
4. Select the license folder and copy it to the AWC virtual machine.
5. Doubleclick the license file.
6. Click through the security dialogs to accept the file.
7. Restart the AWC virtual machine.
You must restart the AWC virtual machine because the license file has made some
changes to the registry settings.
8. Log on to the AWC administrator interface to verify that the number of licenses has
changed from five to the amount on the license.
You can log on to the AWC administrator interface by opening a Web browser and
entering the following address: http://<AWC virtual machine IP
address>/Conferencing/admin, using the username administrator and
the password Avaya123. The License limit column on the AWC administrator
interface main page displays the number of licenses.
Next steps
Now you verify the license by checking the AWC administrator interface.
Configuring the AWC Windows password

By default, the Microsoft Windows password for Avaya Web Conferencing virtual machine
eventually expires. You can configure it to ensure that it does not expire. You can also configure
it to ensure that other users cannot change it. By default, this password is gatekeeper.

Configuring the AWC
Prerequisites
Before you configure the AWC Windows password, you must install and configure
Conferencing and license the AWC.
The purpose of this task is to ensure that you do not unexpectedly loose the functionality of
Avaya Web Conferencing when the Windows password expires.
1. Access the AWC virtual machine using the remote desktop feature.
c. In the Computer field, enter the AWC virtual machine IP address.
password is case-sensitive.
2. Navigate to Start > Computer > Manage to open the Server Manager screen.
3. In the left panel, select Configuration > Local Users & Groups > Users.
4. Right click on Administrator and display the Properties panel.
5. Select User can not change password and Password never expires.
6. Click Apply then Save.
Next steps
Now you can perform the administrative tasks on the AWC administrator interface, which you
can access using a Web browser.
Administration of AWC
You can perform a number of administration tasks on the AWC administrator interface.
You can open the AWC administrator interface using a Web browser and the following address:
http://<AWC virtual machine IP address>/Conferencing/admin. You can log
on to the AWC administrator interface using the username administrator and the password
gatekeeper.
Using the AWC administrator interface, you can:

• View current conferences
• View past conferences

• View licenses
• Create new administrator logins
• Configure password settings
• View servers
Under normal conditions of operation, there should be no need to access the AWC
administrator interface. Typically, administrators only access the AWC administrator interface
for troubleshooting purposes. In the current release, Conferencing Manager performs most of
the AWC administration.
Related topics:
Verifying the license on page 239
Creating new administrator logins on page 240
Configuring AWC password settings on page 240
Deleting duplicate servers on page 241
Verifying the license

Prerequisites
Before you verify the AWC license, you must install it on the AWC virtual machine.
The purpose of this task is to check that the number of supported telephone ports is greater
than the default of five.
1. In a Web browser, enter http://<AWC virtual machine IP address>/

Conferencing/admin.
2. Log in using the username administrator and the password Avaya123.
3. View the License limit column.
Next steps
Now you can navigate through any of the other options on the right pane, such as Set up
administrator.

Configuring the AWC
Creating new administrator logins

Prerequisites
Before you create new administrator logins for AWC, you must install and configure
The purpose of this task is to create new administrator logins. AWC ships with a single
administrator login.

Conferencing/admin.
3. Navigate to Set up administrator.
4. Click Add a new administrator to create a new administrator login.
Next steps
Now you can navigate through any of the other options on the right pane, such as Admin
settings.
Configuring AWC password settings

You can use the AWC administrator interface to configure a number of settings in relation to
administrator passwords. Administrator passwords do not relate to participant passwords.
Similarly, administrator passwords do not relate to the Microsoft Windows operating system
password, which you configure using Microsoft Server Manager to ensure that it does not
expire. You configure the administrator passwords using the AWC browser.
Prerequisites
Before you configure password settings for administrators , you must install and configure
The purpose of this task is to change some of the default settings in relation to a number of
password settings, such as password expiry intervals.


Conferencing/admin.
3. Navigate to Admin settings.
4. Enter a password expiry interval in the Password expiry period (days) field.
5. Enter a minimum password length in the Minimum password length field.
6. Enter a number of parameters relating to password complexity in the Password
syntax checking field.
7. Click OK to save the values.
Example
For example, if you would like passwords to expire every three months, enter 90 in the
Password expiry period (days) field.
Next steps
Now you can navigate through any of the other options on the right pane, such as Manage
Conference Servers or Manage Audio Bridges.
Deleting duplicate servers

When you install Avaya Web Conferencing, an issue exists whereby the Conferencing
installation script installs multiple instances of the Conferencing server on the AWC virtual
machine. After you complete the installation of AWC, but before you starting using AWC in a
production environment, you must delete the duplicate Conferencing server entries.
Prerequisites
Before you view the details of the conferencing server, you must install and configure
Conferencing and license the AWC
The purpose of this task is to remove any additional instances of the Conferencing application
server or bridge. The Standard Edition of Conferencing support a single bridge.

Conferencing/admin.

Configuring the AWC
3. Navigate to Manage Conference Servers to view the AWC virtual machine

settings.
4. Navigate to Manage Audio Bridges to view the application server virtual machine
settings.
5. Click on the second bridge instance to view the bridge details.
6. Click Quiesce Bridge Now, followed by OK.
7. Repeat these steps for any additional duplicate bridges.
When you are finished, you should be left with a single bridge entry in the list.
Example
If you do not perform this task, it is likely that the AWC will display each participant a number
of times in the roster.
Next steps
Now you can start to use AWC in a production environment.
Installing AWC in a DMZ

A DMZ or demilitarized zone is a physical or logical subnetwork that contains and exposes an
organization's external services to the Internet. A DMZ is an intermediate network between an
internal network in the customer site and the outside world in the form of the Internet.
To accommodate AWC access for participants from outside the customer organization, Avaya
has devised a deployment method that exposures the AWC to the Internet, by way of a DMZ,
while simultaneously protecting the other components in the Conferencing solution from
Internet exposure. This deployment method requires the installation and configuration of two
instances of the Conferencing solution. The first instance resides on a server within the
customer network. The second instance resides on a server in the DMZ. On the first instance,
all Conferencing components are enabled, with the exception of AWC. On the second instance,
all Conferencing components are disabled, with the exception of AWC. Using this
configuration, administrators can use a single interface to configure both servers.
Administrators can use the Conferencing Manager administrative interface on the first instance
to perform configuration activities on both the first instance and the second instance.
Component/Virtual machine Conferencing instance on Conferencing instance on

the internal server the DMZ server
Application server (bridge) Enabled Disabled
Client Registration Server (CRS) Enabled Disabled

Installing AWC in a DMZ
Web Portal Enabled Disabled

Conferencing Manager Enabled Disabled
Avaya Web Conferencing Disabled Enabled
Prerequisites
Before you install AWC in a DMZ, you must configure your network with a DMZ.
The purpose of this task is to install AWC in a specific configuration that enables participants
from outside the network to access the AWC functionality across the Internet while protecting
the other components in the Conferencing solution from Internet exposure.
1. Install the Conferencing solution on two separate servers.

2. Follow the instructions to enter the Windows license keys for the CRS and AWC
virtual machines.
These steps refer to the two instances as the internal instance and the DMZ
instance.
3. On the DMZ instance, follow the instructions to create the inventory nodes for each
of the virtual machines. Associate the virtual machines with the CRS virtual machine
and create a DDI.
4. On the DMZ instance, on the Conferencing Manager administrative interface,
navigate to Elements > Conferencing > Services and ensure that all services are
active.
This active state means that the DMZ instance is up and running successfully.
5. On the DMZ instance, disassociate the AWC and the CRS:
a. On the Conferencing Manager administrative interface, navigate to Elements
> Conferencing > Client Registration > General.
b. In the Components area, select None at the Web Conferencing Server list.
c. Click Save then apply your changes.
6. On the internal instance, follow the instructions to create the inventory nodes for
each of the virtual machines. Associate the virtual machines with the CRS virtual
machine and create a DDI.
When you are creating the AWC node, ensure that you enter the IP address of the
DMZ instance of the AWC.
7. On the internal instance, on the Conferencing Manager administrative interface,
navigate to Elements > Conferencing > Services and ensure that all services are
active.

Configuring the AWC
This active state means that the internal instance is up and running successfully
and that the DMZ instance of the AWC is associated with the internal instance of
Next steps
Now you can verify your AWC installation by booking a data conference or changing AWC
settings using the Conferencing Manager interface.
Manually starting AWC

Sometimes, when you reboot Avaya Web Conferencing (AWC) from the System Platform
graphic user interface, the Avaya Web Conferencing service does not automatically restart.
You must restart it manually.
Prerequisites
Before you manually restart AWC from System Platform, you must install Conferencing.
The purpose of this task is to manually start the AWC service in the event that it does not start
automatically.

support.avaya.com.
2. On System Platform, navigate to Virtual Machine Management > Manage, select
the AWC virtual machine, and click Reboot.
The AWC starts the reboot.
4. Navigate to Elements > Conferencing > Services.
5. If the AWC is displayed as inactive, click the Start Service button and click Confirm.
6. Wait for one to two minutes.

Disabling the AWC permanently
The AWC service should become active.
Example
You may have to perform this step when you install patches.
Related topics:
Installing and activating regular patches on page 52
Disabling the AWC permanently

If you would like to use an alternative application to provide data sharing and Web conferencing
features, you can permanently disable the Avaya Web Conferencing (AWC) application.
Prerequisites
Before you can deactivate the AWC virtual machine, you must install Conferencing and add
the AWC virtual machines to your inventory.
The purpose of this task is to render the AWC virtual machine inactive.

3. Select the AWC virtual machine that you want to deactivate.
4. Click Stop Service(s).
5. Click Confirm.
Conferencing Manager updates the Service State column after a couple of minutes.
You can still access the AWC Login screen but you cannot log in to the application.
Example
Microsoft Live Meeting is an example of an alternative provider of Web conferencing
features.
Next steps
Now you can configure the alternative Web conferencing application.

Configuring the AWC

Chapter 13: Configuring the Web Portal
Web Portal virtual machine

The Web Portal virtual machine hosts two Conferencing applications:
• Audio Console
• Web Portal
You can configure the Web Portal virtual machine using the Conferencing > Web
Applications menu.
Audio Console
Audio Console is a Web-based application that enables moderators to control conferences in
real time by displaying a visual representation of the conference. In the Conferencing
environment, Audio Console enables moderators to view participants, mute participants,
initiate sub-conferences, and dial out to individuals or a group of people. Audio Console also
enables moderators to control conference recording. From the Audio Console, moderators can
start, stop, and pause recording.
In addition, moderators can access many of these features using Dial Tone Multi Frequency
(DTMF) keypad sequences, such as *5 to activate lecture mode. However, Audio Console
provides a visual representation and enables moderators to access some features, such as
conference recording.
Related topics:
Client registration server

The Client Registration Server field specifies the IP address of the CRS virtual machine that
the selected Web Portal virtual machine is using for Conferencing information.

Configuring the Web Portal
Login type
The Login Type drop-down menu displays the set of personal validation details that
moderators must supply when they log in to Audio Console. You can use this menu to select
an option for your deployment. The available values are:
• Conference ID and passcode
• Confirmation number and passcode
• Conference ID, confirmation number, and passcode
Web Portal
The Web Portal is like a Web deployment of the CRS Front End. It provides moderators with
a Web interface for scheduling their conferences. It provides administrators with a Web
interface for managing moderators. However, there are some limitations and it does not provide
access to the full range of CRS Front End functions.
The Web Portal interface is divided into parts defined by unique URLs.
• Moderator’s section
The Web Portal moderator’s section enables moderators to book and manage
conferences, contacts, and account information and view reports. It is a good idea to
provide moderators with the Using Avaya Aura™ Conferencing Guide, which is available
from support.avaya.com. The Web Portal moderator URL is: http://Web Portal virtual
machine IP/webportal/login.
• Administrator’s section
The Web Portal’s Administrator’s section enables administrators to configure available
functionality, define the appearance of the Web Portal, and generate administrator
reports. The Web Portal administrator URL is: http://Web Portal virtual machine IP/
webportal/admin/login.
It is important to note that the Web Portal virtual machine uses the Linux operating system.
As a result, you cannot use the Windows remote desktop feature to access the Web Portal
virtual machine.
Related topics:
Accessing Web Portal on page 92
Accessing Web Portal using PuTTY on page 93

Web Portal

Mail server on page 250
Mail from on page 250
SSL enabled on page 251
SSL certificate on page 251
SSL private key on page 251
HTTPS on page 252
Brand prefix on page 252
Client registration server

The Client Registration Server field specifies the IP address of the CRS virtual machine that
the selected Web Portal virtual machine is using for Conferencing information.
Login type
The Login Type drop-down menu displays the set of personal validation details that
moderators must supply when they log in to Web Portal. You can use this menu to select an
option for your deployment. In Conferencing terminology, moderators are sometimes known
as clients. The available values are:
• E-mail address and password
• Company name, client name, and account reference
• Account reference and password
• Client name and password
• Directory server: User, password, content
The Directory server: User, password, content option relates to the Lightweight Directory
Access Protocol (LDAP) functionality of the Web Portal. LDAP is an open, standardized
method of interface with a directory server. It enables the Web Portal to authenticate users,
query user data, and invite users to a conference. The directory server contains user
information in a standard format. The formats are edited depending on the requirement of the
directory server administrators. The Web Portal can be integrated with any directory server
format, as long as the users Name and e-mail address are contained. LDAP integration in the
Web Portal also provides a log in type to allow authentication against a directory server, a
tool to search the directory server to locate invitees, and a means of adding contacts to your
conference address book.
For an LDAP integration to operate successfully in your deployment, you must follow the steps
to configure the Directory Services Client Application (DSCA) parameters and then select the
Directory server: User, password, content option in the Login Type drop-down menu.

Previous releases of Conferencing referred to the Directory server: User, password, content
option as Login Type 9.
Another log-in method for moderators, called Single Sign On (SSO) is not compatible with
LDAP integration. You can implement SSO or LDAP, but not both.
Related topics:
DSCA parameters on page 356
DSCA and Web Portal on page 365
Single sign on on page 445
Mail server
The Mail Server value is the IP address of the e-mail server that this instance of Web Portal
uses for sending notification e-mails. Conferencing sends a number of notification e-mails,
such as confirmation e-mails and reminder e-mails. This field is necessary for the following
functions:
• The Forgot password? link on the Login screen
• The Create Appointment for Moderator button on the Reservation Created successfully
screen.
Note:
If you click Create Appointment for Moderator, Conferencing sends a Microsoft
Outlook appointment directly to the moderator. This is not a downloadable calendar
file. However, if you click Create Appointment & Invite Conferees, Conferencing
sends a downloadable calendar file.
Mail from
The Mail From value is the word or phrase that displays in the From field of notification e-
mails. For example, you could enter a phrase such as Conferencing System. This field is
necessary for the following functions:
• The Forgot password? link on the Login screen
• The Create Appointment for Moderator button on the Reservation Created successfully
screen.
Note:
If you click Create Appointment for Moderator, Conferencing sends a Microsoft
Outlook appointment directly to the moderator. This is not a downloadable calendar

Web Portal
file. However, if you click Create Appointment & Invite Conferees, Conferencing
sends a downloadable calendar file.
SSL enabled
This field relates to secure communications between the Web Portal server and the Web Portal
browser clients using the Apache HTTPD method.
Secure Socket Layer (SSL) is a cryptographic protocol which provides secure communications
on the Internet for activities such as data transfer. SSL allows the Web Portal clients and the
Web server to communicate across a network in a way designed to prevent eavesdropping,
tampering, and message forgery.
When you install Web Portal, it installs in non-SSL mode. To enable SSL communications in
your Conferencing deployment, select SSL Enabled.
SSL operates using digital public key certificates. Public key certificates are like digital
signatures and can be used to verify identity. Certificates pass between the Web Portal clients
and the Web server. Certificates are issued by a Certificate Authority. Certificate Authorities
are trusted third parties. With the Web Portal, Avaya has provided instructions to obtain a self
signed certificate. As a system administrator, you can use this certificate to verify that SSL is
in operation. Once you verify that SSL is in operation, you must purchase a valid certificate
from a Certifcate Authority. Avaya does not provide this certificate.
SSL certificate
browser clients using the Apache HTTPD method. For SSL to operate successfully, you must
install a certificate. You can obtain this certificate from a Certificate Authority, such as
Verisign™.
Note:
Do not confuse this SSL certificate for secure communications between the Web Portal
server and the Web Portal browser with the LDAP certificate for secure communications
between an LDAP server and the Web Portal server.
SSL private key

browser clients using the Apache HTTPD method. For SSL to operate successfully, you must

install a private key. You can obtain this private key from a Certificate Authority, such as
Verisign™.
HTTPS
Data conferencing refers to the Avaya Web Conferencing (AWC) functionality. If your
deployment includes an AWC virtual machine, you can offer a data conferencing option to your
conference participants.
In a deployment with AWC, the Web Portal can send an e-mail notification that includes a link to
the AWC Web site. If the Web Portal sends the e-mail notification to a conferee, the AWC link
connects to the AWC Log in screen with the conferee passcode already entered in the AWC
Security Code field. If the Web Portal sends the e-mail notification to a moderator, the AWC
link connects to the AWC Log in screen with the moderator passcode already entered in the
AWC Security Code field. You can also configure the Web Portal properties file to bypass the
AWC Log in screen for moderators. This is called automatic moderator log in.
By default, the AWC link in the Web Portal e-mail invitation uses the regular, non-secure HTTP
syntax. If you configure the AWC virtual machine to use the Secure Sockets Layer (SSL)
security setting, you must select HTTPS here to ensure that the AWC link uses the secure
HTTPS syntax.
Brand prefix
You can customize the look and feel of the Avaya Web Conferencing (AWC) screens. For
example, you can replace the Avaya logo with a customer's logo. Similarly, you can customize
the look and feel of the Web Portal and Audio Console applications. The process of customizing
an interface is called branding.
By default, the AWC screens have the Avaya branding. If you create a branding for your
deployment, you must enter the branding name in this field. To learn more about the process
of customizing the AWC, contact your Avaya Support Representative.

Chapter 14: Configuring the Conferencing
watchdog
Booking and scheduling monitor

The Booking and Scheduling Monitor (BSMon) application monitors the various Conferencing
components and restarts them in the unlikely event that one of them goes offline. BSMon
ensures that all applications that support CRS are running. As a result, the BSMon plays an
important role in the detection of a system failure.
When Avaya ships Conferencing, by default, BSMon monitors the following CRS applications:
• The Reservation Server application (Reserver)
• The Scheduling API (SchAPI Manager)
• The CDR Loader application
• The Billing application
Optionally, you may choose to enable BSMon to monitor some of the remaining CRS
applications, such as:
• The Notifications Subsystem, which sends notification e-mails
• The PC Reports application, which sends attendance e-mails.
• The Directory Services Client Application or the Import Utility application, which import
accounts.
Configuring BSMon to monitor an application

By default, Conferencing monitors a number of applications on the CRS virtual machine. You
can configure BSMon to monitor a number of additional applications.
Prerequisites
Before you configure BSMon to monitor an application, you must install Conferencing and
configure connectivity between the virtual machines.

Configuring the Conferencing watchdog
The purpose of this task is to extend the scope of BSMon so that it 'watches' a greater number of
applications.
2. In a Windows Explorer dialog, navigate to Avaya > BSMonitor and open the
BSMonitorconf.reg file in a text editor, such as the Notepad application.
This file lists the applications that the BSMon monitors by default. There are four
applications in the list and they number from 0 to 3.
3. Copy an existing entry and paste it at the end of the list.
Ensure that you copy a complete single entry from [HKEY_LOCAL_MACHINE
\SYSTEM\ as far as 00000000.
4. Update the number of the entry. If this is the first new entry in a default file, the
number of this entry should be 4.
5. Update the Name parameter by adding the name of the executable that you want
BSMon to monitor.
6. Update the Path parameter by adding the path to the executable that you want
BSMon to monitor.
7. Save the file.
8. In a Windows Explorer dialog, doubleclick the file.
9. Click Yes, followed by OK at the two information dialogs.
10. Restart the application that you have added to the BSMonitorconf.reg file.
11. Verify that BSMon is successfully monitoring the application by closing the
application and viewing the Process tab in Task Manager to see if BSMon restarts
it.
Next steps
If you want to learn more about the BSMon application, you can read the install.txt in the
BSMonitor folder.

Chapter 15: Activating and deactivating
virtual machines
Virtual machines and services

Avaya Aura™ Conferencing is an integrated multimedia conferencing solution, consisting of
five virtual machines, which you must install in your customer network. The five virtual
machines are:
You can activate and deactivate these virtual machines using the Conferencing Manager
administration interface.
• An active virtual machine is available and in service.
• An inactive virtual machine is online but unavailable. It can be restarted/rebooted using
the Conferencing Manager administration interface.
• A stopped virtual machine is offline, unavailable, and cannot be restarted/rebooted using
the Conferencing Manager administration interface.
The status of the virtual machines is reflected on the System Platform interface.
Using the Services menu, you can also import and export configuration settings. Using this
import and export functionality, you can model a customer configuration in your own site and

Activating and deactivating virtual machines
then import it to the customer site. This functionality means that the installation and
configuration of Conferencing is fast and highly efficient.
Related topics:
Introduction to the import and export process on page 401
Activating virtual machines and services

You can activate and deactivate the virtual machines that comprise the Conferencing solution
using the Conferencing Manager administration interface.
Prerequisites
Before you can activate a virtual machine, it must have the Service State of
Inactive.Conferencing and add the virtual machines to your inventory.
The purpose of this task is to make a virtual machine available.

3. Select an inactive virtual machine.
4. Click Start Service(s).
5. Click Confirm.
Deactivating virtual machines and services

You can activate and deactivate the virtual machines that comprise the Conferencing solution
using the Conferencing Manager administration interface.
Prerequisites
Before you can deactivate a virtual machine, you must install Conferencing and add the virtual
machines to your inventory.

Deactivating virtual machines and services
The purpose of this task is to render a virtual machine inactive.

3. Select the virtual machine that you want to deactivate.
4. Click Stop Service(s).
5. Click Confirm.
Example
For example, you may wish to deactivate a virtual machine to perform a maintenance task
on that virtual machine.
Next steps
Now, you can activate the virtual machine.

Activating and deactivating virtual machines

Chapter 16: Backing up and restoring
settings
Backing up and restoring

To backup all your Conferencing database files, configurations, and customizations, Avaya
recommends using the Backup/Restore feature within System Platform. System Platform is
a virtual server that allows solution templates, or applications, to co-reside on a single server.
You use System Platform to obtain and install the Conferencing files. For more information,
see the System Platform documentation, which is available from support.avaya.com.
Conferencing is an integrated multimedia conferencing solution, consisting of five virtual
machines, which you must install in your customer network. The five virtual machines are:
The central management console (also called Conferencing Manager or SMGR) is the
interface through which you configure the other virtual machines that make up the
Conferencing solution. In terms of backing up and restoring, the Conferencing database files,
configurations, and customizations reside on the other virtual machines and not on the
Conferencing Manager virtual machine. So, the scope of an effective backup and restore must
include the files on these virtual machines:

Backing up and restoring settings
• Bridge
• AWC
• CRS
• Web Portal
To back up these files, you must perform some additional steps after you use the Backup/
Restore feature within System Platform. So, effectively, there are two phases in the back up
process. You must back up files using System Platform and then you must back up the
additional Conferencing files. You must complete these two tasks for a successful back up.
The first stage is called System Platform backup and the second stage is called Additional
backup.
For the backup, you require a server with a minimum of 1GB of space.
Similarly, for the restore process, there are a number of phases. First, you must disable the
Avaya Web Conferencing restore feature. The Avaya Web Conferencing (AWC) restore feature
can cause some issues with the restoration of the other Conferencing virtual machine files, so
Avaya recommends disabling the AWC restoration and manually restoring the AWC files. After
you disable the AWC restore process, you must use the Backup/Restore feature within
System Platform to restore the files and then you must restore the additional Conferencing files.
Related topics:
Two stages in the backup process, three stages in the restore process on page 260
What is included? on page 261
What is not included? on page 263
Two stages in the backup process, three stages in the restore

process
There are two stages in the backup process.
• You must back up the files using System Platform.
• Then, you must back up some additional Conferencing files.
There are three stages in the restore process.
• You must disable the Avaya Web Conferencing (AWC) restoration process.
• You must restore the files using System Platform.
• Then, you must restore some additional Conferencing files.
To back up your Conferencing deployment: To restore your Conferencing deployment:

First, back up the system by using the First, disable the AWC restore process
System Platform Web Console

Lastly, back up additional Conferencing Second, restore the system by using the
files using PuTTY. System Platform Web Console
Lastly, restore additional Conferencing files
using PuTTY.
You can follow the steps here to perform all of these tasks.
What is included?
The following files are included in the System Platform backup and restore feature. System
Platform copies each of these files to a folder on the machine that you are currently using,
called C:\temp\Avaya.
AWC
File Additional information

DCMS database This includes all AWC specific registry settings
The Tomcat and Apache configuration Tomcat/conf/Catalina/localhost/
files that are specific to the Authenticator Authenticator.xml
service Apache2/conf/active/wp_mappings.conf
Authenticator configuration
CRS

All databases BSRes2
CDRs
SBill
Reports
Import
Data event
BSMon entries
BSScheduler templates
Web Portal

Configuration files /etc/httpd/conf/
/etc/httpd/conf.d
/etc/sysconfig/httpd
/etc/sysconfig/tomcat


/etc/sysconfig/iptables
/etc/sysconfig/samba
/etc/sysconfig/avaya-web-configurator
/etc/sysconfig/logrotate.d
/opt/apache-tomcat
/opt/tomcat1
/opt/Avaya/conf
Note:
Excluding subfolders log / logs / *.log / lib / *.jar / modules / run /
temp / tmp / work
More configuration /etc/sysconfig/network-scripts/ifcfg-eth0
files /etc/sysconfig/network
/etc/resolv.conf
/etc/hosts
Bridge

Configuration /usr/ipcb/config/
files /usr/dcb/config/
/usr/dcb/cdr/
/usr/dcb/codr/
/usr/dcb/modilog
/usr/dcb/netmgr
/usr/dcb/traffic
/usr/dcb/dbase/diallists
/usr/dcb/dbase/ologs
/usr/dcb/lanstats
/usr/dcb/dbase/oprints
/usr/dcb/dbase/polprnts
/usr/dcb/dbase/sysmsg
/usr/dcb/dbase/unattend
/usr/dcb/dbase/admin
/usr/dcb/utlogs
/usr/dcb/dbase/tagfiles
/usr/dcd/dbase/signin
/usr/dcb/bin/feature.dat
/usr/dcb/bin/procargs.txt
/usr/dcb/bin/dsparams.txt
/etc/resolv.conf
/usr2/Prompts
/etc/exports
/etc/hosts
/etc/sysconfig/network-scripts/ifcg-eth0


/etc/sysconfig/network-scripts/ifcg-bond0
/etc/rc.d/init.d/bondingConfig
/usr/share/tomcat-5.5.9/conf/server.xml
usr/share/tomcat-5.5.9/webapps/axis/WEB-INF/classes/Crystal.cfg
/usr/share/tomcat-5.5.9/webapps/axis/WEB-INF/classes/CrystalLog.cfg
usr/share/tomcat-5.5.9/webapps/axis/WEB-INF/classes/mx.tables.xml
/usr/local/etc/snmp/snmpd.conf
What is not included?

System Platform backs up but does not restore a number of files.
Virtual machine Files

AWC SSL certificates
CRS Scheduled maintenance tasks
Initialization files (.ini)
Web Portal /opt/webapps/webportal
/opt/webapps/console
/opt/webapps/part-pin-webapp
Note:
Excluding subfolders logs / *.log / lib / *.jar
Bridge (application server) Cronjobs
Secure Access Link (SAL) configuration
Bridge database (called Bridgedb)
In addition, it is important to note that you must make separate provisions for conference
recordings. Conference recordings are not included in the System Platform backup and restore
feature.
Special provisions for the bridge database
The bridge database is not part of the backup and restore process. In the unlikely event that
a bridge virtual machine has a fatal error, you can re-populate the bridge database using the
information from the Client Registration Server (CRS). This process of re-population can take a
number of hours. As a workaround, to avoid this delay, Avaya has created a scheduled job that
automatically copies the daily bridge local backup to a remote server. Essentially, this
scheduled job sends a daily copy of the bridge database to a remote FTP server so that you
can use that copy to restore the bridge database in the event of an error on the production
machine.
Related topics:
Copying the bridge database to an FTP server on page 264

Copying the bridge database to an FTP server

Prerequisites
Before you configure Conferencing to copy the daily bridge local backup to a remote server,
you must install and configure Conferencing.
The purpose of this task is to configure a scheduled job to send the daily backup copy of the
bridge database to an FTP server.
1. Log in to the application server (bridge) virtual machine using PuTTY.

2. Enter the name craft and the password craft01.
su sroot
4. Setup authentication.
The automated copy is non-interactive. As a result, you must setup authentication
to avoid password prompting when the files are copying.
a. Generate an RSA key by entering this command:
ssh-keygen -t rsa
This command generates a private and public key. By default, it stores the
private key in /root/.ssh/id_rsa and it stores the public key in /
root/.ssh/id_rsa.pub.
b. Copy the public key to the server where you want to store the backups.
For example, use the user account <myuser> on the remote server
<remoteserver>.
ssh <myuser>@<remoteserver> mkdir .ssh
cat /root/.ssh/id_rsa.pub | ssh <myuser>@<remoteserver>
"cat >> .ssh/authorized_keys"
5. Create a scheduled task to copy the bridge database backup on a daily basis.
a. Get a list of the current cron jobs by entering this command:
crontab -u sroot -l > my_cron_jobs
b. Edit the my_cron_jobs file to add the new task at the end by pasting this line
into the file:
00 05 * * * /usr/bin/scp `ls -t /usr3/BACKUPS/*full* |
head -n 1` <myuser>@<remoteserver>:<remotedirectory>

System Platform backup
This command copies the latest bridge database backup at 05:00 each
morning.
c. On the remote server, create the folder <remotedirectory> and ensure that
<myuser> on <remoteserver> can write to it.
d. Inform the crontab of the updated tasks by entering this command:
crontab -u sroot my_cron_jobs
Next steps
It is a good idea to verify the scheduled job before you place the server into production.

You can back up configuration information for System Platform and the solution template (all
virtual machines). Sets of data are backed up and combined into a larger backup archive.
Backup sets are related data items that need to be backed up. When you perform a back
up, the system executes all the backup sets. All the backup sets must succeed to produce a
backup archive. If any of the backup sets fail, then the system removes the backup archive.
The amount of data backed up is dependent on the specific solution template.
The system stores the backup data in the /vspdata/backup directory in Console Domain.
This is a default location. During an upgrade, the system does not upgrade the /vspdata
folder, so that you can restore the data, if required. You can change this location and back up
the System Platform backup archives to a different directory in System Platform or in an
external server. You can also send the backup data to an external e-mail address if the file size
is not larger than 10 MB.
If a backup fails, the system automatically redirects you to the Backup page after login and
displays the following message: Last Backup Failed. The system continues to display the
message until a backup is successful.
Note:
It is not the aim of the backup feature to provide a mechanism to re-enable a failed High
Availability Failover node back to High Availability Failover configuration. Follow the
instructions in this document on how to re-enable failed High Availability Failover node back
to High Availability Failover configuration.
Related topics:
Backing up the system by using the System Platform Web Console on page 266
Scheduling a backup on page 266
Transferring the Backup Archives to a remote destination on page 267
Viewing backup history on page 267

Backup field descriptions on page 268
Backing up the system by using the System Platform Web Console

Use this procedure to back up configuration information for System Platform and the solution
template (all virtual machines).
1. Click Server Management > Backup/Restore.

2. Click Backup.
3. On the Backup page, select the Backup Now option to start the backup operation
immediately.
Important:
The backup file size can reach 3 GB. Ensure that you have that much free space
at the location where you are storing the backup archive.
4. Select where to store or send the backup files:
• Local: Stores the backup archive file on System Platform in the /vspdata/
backup/archive directory.
• SFTP: Stores the backup archive file on the designated SFTP host server as
well as on the System Platform server.
• Email: Sends the backup archive file to the e-mail address that you specify as
well as stores the file on the System Platform server.
Note:
Avaya does not recommend that you use the Email option due to the large
size of backup files. The backup file size can reach 3 GB.
5. Enter other information as appropriate.
6. Click Backup Now.
Scheduling a backup
Use this procedure to back up System Platform and the solution template on a regular basis.
Backups are not scheduled by default on System Platform.


2. Click Backup.
3. On the Backup page, select Schedule Backup.
4. Specify the following:
• Frequency
• Start Time
• Archives kept on server.
• Backup Method
Use this field to copy the backup archive file to a remote server or to send the
file to an e-mail address. The file is also stored on the on theSystem Platform
server.
5. Click Schedule Backup.
Transferring the Backup Archives to a remote destination

You can send the backup archive to a mail address or to a remote server by SFTP with using the
Backup Method option.
1. To send the archive by email:

a. Select the Email option as the Backup Method.
b. Specify the Email Address and the Mail Server.
2. To send the archive to a remote server by SFTP:
a. Select SFTP option as the Backup Method.
b. Specify the SFTP Hostname (or IP Address), Directory to which the archive
will be sent and the username and password to log in the server.
Viewing backup history

Use this procedure to view the last 10 backups executed and their status. If the last backup
failed, the system automatically redirects you to the Backup page after login and displays the

following message: Last Backup Failed. The system continues to display the message
until a backup is successful.

2. Click Backup.
3. On the Backup page, select Backup History.
The system displays the last 10 backups executed with their dates and the status.
Backup field descriptions

Use the Backup page to back up configuration information for System Platform and the solution
template (all virtual machines).
Backup Now fields
The following table describes the fields that are displayed if you select Backup Now at the top
of the Backup page.
Field Descriptions
Names
Backup Select a location to send the backup file:
Method
• Local: Stores the backup archive file on System Platform in the /vspdata/
backup/archive directory.
• SFTP: Stores the backup archive file on the designated SFTP host server
as well as on the System Platform server.
Enter the hostname, directory, user name, and password for the SFTP
server.
• Email: Sends the backup archive file to the e-mail address that you specify
as well as stores the file on the System Platform server.
Enter the e-mail address and the server address of the recipient.
Backup Starts the backup operation.

Now
Schedule Backup fields

The following table describes the fields that are displayed if you select Schedule Backup at
the top of the Backup page.

Additional backup
Field Names Descriptions

Frequency Select one of the following options:
• Daily
• Weekly
• Monthly
Start Time The start time for the backup.

Archives kept on The number of backup archives to store on the System Platform
the server server. The default is 10.
Backup Method Select a location to send the backup file:
• Local: Stores the backup archive file on System Platform in the /
vspdata/backup/archive directory.
• SFTP: Stores the backup archive file on the designated SFTP host
server as well as on the System Platform server.
Enter the hostname, directory, user name, and password for the
SFTP server.
• Email: Sends the backup archive file to the e-mail address that you
specify as well as stores the file on the System Platform server.
Enter the e-mail address and the server address of the recipient.
Schedule Backup Schedules the backup process.

Cancel Schedule Cancels an existing backup schedule.
Additional backup
To complete the full back up of all Conferencing data, you must perform some additional steps.
To perform these steps, you require the PuTTY application. PuTTY is a Windows SSH client
that allows you to access the application server, giving you a terminal window. You can
download PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
There are many different PuTTY downloads listed. Typically, your deployment requires the
putty.exe file.
Related topics:
Backing up using PuTTY on page 269
Backing up using PuTTY

These steps describe how to back up several files on the application server virtual machine,
the Client Registration Server (CRS) virtual machine, and the Web Portal virtual machine. You

do not need to perform any additional back up steps on the Avaya Web Conferencing (AWC)
virtual machine.
Prerequisites
Before you back up the additional Conferencing files, you must back up the Conferencing files
using System Platform.
The purpose of this task is to back up additional Conferencing files that are not included in the
System Platform back up.

su sroot
/usr/dcb/dbase/bridgedb_postgres/exe.other/
bridgedb_maintain_pg.sh no_prompt backup bridgedb
This command backs up the Conferencing database to a directory called /usr3/
BACKUPS and give the file an extension of XXX.pgc.gz.
5. Copy the Conferencing database and save it to a secure server on the customer
network.
a. Identify a secure server on the customer network and make a note of the log-
in details and the domain name.
b. Enter the command:
scp bridgedb_full_XXXX_XXXX.pgc.gz <user>@<IP of another
server>:/home/admin/
This command copies the Conferencing database to the current directory.
6. Back up the Conference Scheduler Plug-in for Microsoft Outlook files.
a. Identify a secure server on the customer network and make a note of the log-
in details and the domain name.
b. Enter the following commands:
cd /usr3/BACKUPS
tar -cvf outlook_conf_files.tar /usr/ipcb/outlook/files/*
c. Use a copying application such as WinSCP or SCP to copy the files to the other
server:
/usr3/BACKUPS/outlook_conf_files.tar

Stop AWC restore
For example:
scp /usr3/BACKUPS/outlook_conf_files.tar
admin@XXX.XX.XX.X:/home/admin/
8. Copy the following files to the secure server on the customer network.
• C:\Windows\*.ini
• D:\Profiles\dsca.pfl
9. Access the Web Portal virtual machine using the same method you used to connect
to the application server virtual machine.
10. Copy the following files to the secure server on the customer network, using the
same method that you used to copy files from the application server virtual machine:
• /home/sroot/keystore.jks (If present)
• /etc/pki/tls/certs/localhost.crt (If present)
• /etc/pki/tls/private/localhost.key (If present)
• /opt/webapps/webportal/WEB-INF
• /opt/webapps/webportal/WEB-INF/default
• /opt/webapps/webportal/customisations/default/default/properties
Next steps
Now it is a good idea to test the restoration process. Recall that you must disable the Avaya
Web Conferencing (AWC) restore process before you restore the files using the System
Platform restore process.
Stop AWC restore

The automatic restore feature of Avaya Web Conferencing (AWC) can cause issues with the
restoration of the other aspects of the Conferencing solution. For this reason, Avaya
recommends that you stop the AWC restore process. To do this, you must edit a file on the

System Platform virtual machine (Cdom). To edit this file, you must use PuTTY to access the
System Platform virtual machine.
After you disable the automatic restore feature of AWC, you must manually restore AWC.
Related topics:
Disabling AWC restore on page 272
Disabling AWC restore

Prerequisites
Before you disable the AWC automatic restore process, back up the Conferencing files using
the steps described here.
The purpose of this task is to disable the AWC restoration process on the System Platform
virtual machine so that it does not cause problems with the restoration of the other
Conferencing components. This task involves changing a phrase of text and adding a single
function.
1. Log in to the System Platform virtual machine (Cdom) using PuTTY.

su sroot
vi /vspdata/template/MX-STD/systems/awc/plugins/restore/
plugins_mx-6251.sh
This command displays a file.
5. In this file, search for the text doRestore.
6. Change doRestore to doNothing.
7. Add the following function:
function doRestore() {
echo NotRunningAWCRestore
}
8. Save the file.

System Platform restore
The automatic restore is now disabled.
Example
Here is an example of a section of the file:
#### function doRestore() {
echo NotRunningAWCRestore
}
function donothing() {
RESTORE_DIR="${WORK_DIR}"
#wget --post-data
"action=restore&username=admin&password=admin01&uri=sftp://$
{CDOM_IP}${RESTORE_DIR}" http://${VM_IP}:18080/data -O /tmp/$
{VM_ID}.restore.status
#sleep 60
if [ -f "/home/vspvm/.ssh/id_dsa" ];then
result=`curl -F "file=@/home/vspvm/.ssh/id_dsa"
"http://${VM_IP}:18080/data?
action=restore&username=vspvm&password=&uri=sftp://${CDOM_IP}$
{RESTORE_DIR}"`
if [ "$result" != "true" ];then
echo "$result "
Next steps
Now you can restore the remainder of the Conferencing files using System Platform.

After you disable the AWC restore process on System Platform, you can use System Platform
to restore the other Conferencing files. This automatic process restores most of the
Conferencing files. However, when you complete these steps, you must perform an additional
task, using PuTTY, to restore some files that were not captured by System Platform.
Related topics:
Restoring backed up configuration information on page 274

Restoring backed up configuration information

Use this procedure to restore backed up configuration information for System Platform and the
Solution Template (all virtual machines).
Note:
The restore operation does not restore the High Availability Failover configuration from the
backup file. It is not the aim of the restore feature to re-enable the failed High Availability
Failover node back to High Availability Failover configuration. Follow the instructions given in
this document on how to re-enable the failed High Availability Failover node back to High
Availability Failover configuration. Avaya recommends that you restore the backup
configuration before configuring and starting High Availability Failover.

2. Click Restore.
The Restore page displays a list of previously backed up archives on the System
Platform system.
3. Select an archive file from the list, and then click Restore to restore from the
selected archive.
Restoring an archive requires the System Platform Web Console to restart, so you
must log in again when the restore operation is completed.
Related topics:
Restore field descriptions on page 274
Viewing restore history on page 275
Restore field descriptions

Restore from Select the location of the backup archive file from which you want to restore
configuration information.
• Local: Restores from a file on System Platform. If you select this option,
the Restore page displays a list of previously backed up archives on the
System Platform system.
• SFTP: Restores from a file on a remote server. If you select this option,
enter the hostname or IP address of the remote server, directory where

the archive file is located, and user name and password for the SFTP
server.
• Upload: Restores from a file on your computer.
Archive Filenames of the backup archive files at the location you specify.
Filename
Archive Date Date that the file was created.
Selection Select this check box to restore from the archive file.
Restore Displays the restore history for the last ten restores. If an error occurred
History during the last restore, the system directs you to this page after login and
continues to display an error message until a restore is successful.
Button descriptions
Button Description
Search Displayed if you select SFTP. Searches for archive files in the specified
directory of the remote server.
Clear Search Clears the list of archive files found on a remote server after an SFTP
Result search.
Viewing restore history

Use this procedure to view the last 10 restores executed and their status. If the last restore
failed, the system automatically redirects you to the Restore page after login and displays the
following message: Last Restore Failed. The system continues to display the message
until a restore is successful

2. Click Restore.
3. On the Restore page, select the Restore History option.

Additional restore
After the System Platform restore, you have to perform some manual steps using PuTTY. You
must restore the AWC files as well as several application server, Client Registration Server
(CRS), and Web Portal files.
Related topics:
Restoring using PuTTY on page 276
Restoring using PuTTY

Prerequisites
Before you restore the additional Conferencing files, you must restore the main files using the
System Platform back up and restore process.
The purpose of this task is to restore some additional files that were not captured by the System
Platform back up and restore process.
1. Log in to the System Platform virtual machine (Cdom) using PuTTY.

su sroot
cd /vspdata/backup/archive/
5. Identify the backup file that you wish to restore by checking the date and time which
is part of the filename.
6. Enter the following commands:
tar zxvf backup_[hostName-[IP]_[DateTimeStamp].tgz
cd backup_[hostName-[IP]_[DateTimeStamp]/vm-data/awc/data/0
tar zxvf auth-archive.tgz
tar zxvf awc-archive.tgz
mkdir branding
cp awc-branding-[DateStamp]-[TimeStamp].tgz branding/

Additional restore
cd branding
tar zxvf awc-branding-[DateStamp]-[TimeStamp].tgz
7. Enter the following command to view the contents of the directory:
ls -al
This directory contains a number of files, including:
• Authenticator.xml
• wp_mappings.conf
• Authenticator.properties
• log4j.properties
8. Use WinSCP to restore the following files and directories:
Restore this file... To this location...

Authenticator.xml D:\Avaya\MX60\Tomcat\conf\Catalina\localhost
\Authenticator.xml
wp_mappings.conf D:\Avaya\MX60\Apache2\conf\active
\wp_mappings.conf
Authenticator.properties D:\Avaya\MX60\webapps\Authenticator
\Authenticator.properties
log4j.properties D:\Avaya\MX60\webapps\Authenticator
\log4j.properties
9. Restart the following services:

• Avaya Apache Tomcat
• Avaya Apache HTTPD
10. Stop the following services:
• World Wide Web Publishing service
• Conferencing Gateway
11. Restore the AWC database called the DCMS database using the following
command:
sqlcmd -d master -U avaya -P gatekeeper -Q "restore database
DCMS from disk = 'D:\Avaya\ams\backup\AWC\DCMS.bak'"
12. Use WinSCP to restore the branding directory from the secure server to the
following location on the application server virtual machine::
D:\Conferencing\Jenga\branding
13. Restart the following services:
• World Wide Web Publishing service
• Conferencing Gateway

14. Restore the bridge database file from the secure server to the following location on
the application server virtual machine:
• /var/avaya/backup [the file has a pgc.gz file extension]
• /home/sroot/outlook_conf_files.tar
15. Restore the Conference Scheduler for Microsoft Outlook files from the secure server
to the following location on the application server virtual machine:
/home/sroot
tar xvf outlook_conf_files.tar
mv /home/sroot/usr/ipcb/outlook/files/* /usr/ipcb/outlook/
files/
16. Ensure that the application server (bridge) is not running and that the Client
Registration Server (CRS) is not connected to the bridge database:
SSH to the bridge
service postgresql stop
/usr/dcb/bin/bridge-restore.sh
18. Restart the application server service.
You can restart the application server on the Conferencing Manager administrative
screens (Elements > Conferencing > Services > Bridge Service Start).
20. Copy the following files from the secure server on the customer network to the CRS
virtual machine.
• C:\Windows\*.ini
• D:\Profiles\dsca.pfl
21. Access the Web Portal virtual machine.
22. Copy the following files from the secure server on the customer network to the Web
Portal virtual machine
• /home/sroot/keystore.jks
• /etc/pki/tls/certs/localhost.crt
• /etc/pki/tls/private/localhost.key

Additional restore
• /opt/webapps/webportal/WEB-INF
• /opt/webapps/webportal/WEB-INF/default
• /opt/webapps/webportal/customisations/default/default/properties


Chapter 17: Configuring languages
Introduction to languages
At the present time, the Conferencing audio messages are available in a limited number of
languages. However, the applications are only available in English.
Most people interact with Conferencing as conference conferees or conference moderators.
With this idea in mind, Avaya plans to localize the participant experience by translating the
graphic user interfaces (GUIs) of a number of Conferencing applications and by making
Conferencing audio messages available in a number of languages.
Conferencing applications include booking applications and meeting management
applications such as:
• Web Portal
• Avaya Conference Scheduler for Microsoft Outlook
• Avaya Web Conferencing
• Audio Console
• Avaya Plug-in for Microsoft Live Meeting
• Avaya Plug-in for Microsoft Office Communicator
• Avaya Plug-in for IBM Lotus Sametime
Avaya plans to make each of these applications available in a number of languages. Similarly,
Avaya plans to make all audio messages available in each of the supported languages. Once
this is accomplished, the end-to-end experience of participants engaging in conferencing will
be localizable.
Note:
On the release date, Conferencing supports some of these languages. Conferencing will
support the full list of all languages 90 days after the release date. Please contact your Avaya
Support Representative for more information about release dates for a fully localizable
implementation. During the period of 90 days before Conferencing supports the full list of
languages, if an operator or a moderator chooses an unsupported language when booking a
conference, Conferencing plays the English audio messages in place of the unsupported
language.
The audio messages are available in the following languages:

Configuring languages
Language Directory on the application server Name/label in CRS, Web

Portal, and Conferencing
Manager interfaces
English /usr2/Prompts/MX60Prompts/English Prompt Set 1
Simplified Chinese/ /usr2/Prompts/MX60Prompts/ Prompt Set 2
Mandarin Chinese
Japanese /usr2/Prompts/MX60Prompts/ Prompt Set 3
Japanese
Malaysian /usr2/Prompts/MX60Prompts/ Prompt Set 4
Malaysian
Korean /usr2/Prompts/MX60Prompts/Korean Prompt Set 5
French /usr2/Prompts/MX60Prompts/French Prompt Set 6
German /usr2/Prompts/MX60Prompts/ Prompt Set 7
German
Italian /usr2/Prompts/MX60Prompts/Italian Prompt Set 8
Russian /usr2/Prompts/MX60Prompts/ Prompt Set 9
Russian
Latin Spanish /usr2/Prompts/MX60Prompts/ Prompt 10
Spanish-LA
Brazilian /usr2/Prompts/MX60Prompts/ Prompt Set 11
Portuguese Portuguese-Br
English for teletype /usr2/Prompts/MX60Prompts/TTY- Prompt Set 12
devices English
English /usr2/Prompts/MX60Prompts/ Prompt Set 13
English-US
Canadian French /usr2/Prompts/MX60Prompts/ Prompt Set 14
French-CA
Castilian Spanish /usr2/Prompts/MX60Prompts/ Prompt Set 15
Spanish-CS
It is important to note that even after Avaya makes the Conferencing end-user applications
available in a number of languages, system administrators must still understand English in
order to successfully install, configure, and monitor the operation of Conferencing. Similarly,
operators interacting with CRS Front End and Bridge Talk must also understand English.
Note:
The Standard Edition of Conferencing does not support the Bridge Talk application but can
support an external application with similar features. You can configure this application to
operate with Conferencing using the ACP API.

A point of clarification regarding languages
Audio messages inform participants of information and prompt participants for responses.
These audio messages are sometimes called audio prompts or annunciator messages. A
group of audio messages is often called a prompt set.
Related topics:
Linked files and linking on page 295
A point of clarification regarding languages

At this point, it is worth clarifying an important distinction between system language and
conference language. System language is often called DNIS-driven language.
Related topics:
Conference language on page 283
Participant experience on page 284
System language
When you configure call branding, you create an association between a dialed number
identification service (DNIS/DDI) and an audio prompt set. This association determines the
system language. In each row of a call branding table, the DDI field represents the DNIS and
the Message Set Number field represents the audio prompt set. So, for example, you could
create an association between the DDI 12345 and the English audio prompt set. This is the
system language.
Related topics:
Configuring audio messages for your system on page 296
Conference language
When operators or moderators book a conference, using CRS Front End, Bridge Talk, or Web
Portal, they can create an association between the conference and an audio prompt set. This
association creates the conference language. Bridge Talk operators can access the Prompt
Set drop-down list in the Conference Scheduler utility, CRS Front End operators can access
the Prompt Set drop-down list on the Options dialog, and Web Portal moderators can access
the Prompt Set drop-down list on the Advanced Booking Options screen.

Moderators cannot specify an audio prompt set if they book their conference using the
Conference Scheduler Plug-in for Microsoft Outlook or IBM Lotus Notes.
For more information on selecting a prompt set for a conference using Web Portal > Booking
Meeting > Reservation Details > Advanced Options, see Using Avaya Aura™ Conferencing
Guide, which is available from support.avaya.com.
For more information on selecting a prompt set for a conference using CRS Front End >
Customer Bookings > Check Reservation > Confirm Reservation > Options, see
Operating Avaya Aura™ Conferencing Guide, which is available from support.avaya.com.
Note:
Related topics:
Configuring audio messages at conference-level on page 297
Participant experience
When participants dial the DNIS/DDI, Conferencing always plays audio messages in the
system language. For example, if you associate the DNIS with the English audio prompt set,
participants always hear English messages. Once participants enter their conference
passcode, Conferencing has visibility of the conference settings. At this point, there are two
possible outcomes, as follows: Each entry in the call branding table also has a parameter called
Use Conf Prompt Set. By default, Use Conf Prompt Set is disabled.
• If Use Conf Prompt Set is enabled, Conferencing plays the conference audio prompt set
once the participants enter the conference passcode.
• If Use Conf Prompt Set is not enabled, Conferencing plays the system audio prompt set
at all times, even after the participants enter the conference passcode.
Related topics:
Scope of localization
In this release of Conferencing, Avaya has maximized the scope of localization by ensuring
that Conferencing end users are the main priority for all localization efforts. Within the
Conferencing environment, end users are called moderators or participants. These are the
people who book and attend conferences on a regular basis. Where possible, Avaya has
focused localization efforts on the end user experience. For this reason, Avaya has not
localized the administrative elements of the various Conferencing components. As a result,
system administrators must have knowledge of the English language.

At this stage it is a good idea to clarify the terms: Localization and Internationalization
Related topics:
Internationalization on page 285
Localization on page 285
Plug-in components on page 285
Web components on page 287
CRS components on page 287
APIs on page 288
Application server components on page 288
Operator components on page 289
Internationalization
For the purposes of the Conferencing product, the term internationalization refers to the
process of making a component capable of being localized in the future. This means that the
component can support a number of languages, but currently, the component is not shipped
with language files. In addition, internationalization means that the component can store and
transport data that has been input or imported from a number of different source locales. For
example, the internationalized components can process a number of Asian language scripts.
Localization
For the purposes of the Conferencing product, the term localization refers to the process of
providing a component in multiple languages. This means that the component supports a
number of languages. For the most part, Avaya has confined localization to end user
components, such as end user graphic user interfaces (GUIs) and end user audio messages.
Plug-in components
Recall that within the Conferencing solution, Avaya has developed the following plug-in
applications to provide Conferencing capabilities for users who are running a number of IBM
and Microsoft solutions:
• Conference Scheduler for Microsoft Outlook
• Conferencing for Microsoft Live Meeting
• Conferencing for Microsoft Office Communicator

• Conferencing for IBM Lotus Notes

• Conferencing for IBM Lotus Sametime
This table shows the aspects of the plug-in components that Avaya has localized and
internationalized.
Component Is it internationalized? Is it localized?

Conferencing for IBM Lotus Sametime Yes Yes
graphic user interface
Conferencing for IBM Lotus Sametime No online help No online help
online help
Conferencing for IBM Lotus Sametime No No
installer
Conferencing for IBM Lotus Notes graphic No No
user interface
Conferencing for IBM Lotus Notes online No No
help
Conferencing for IBM Lotus Notes installer No No
Conference Scheduler for Microsoft Outlook Yes Yes
graphic user interface
online help
installer
Conferencing for Microsoft Live Meeting Microsoft user interface Microsoft user
graphic user interface interface
Conferencing for Microsoft Live Meeting No online help No online help
online help
Conferencing for Microsoft Live Meeting No No
installer
Conferencing for Microsoft Office Yes Yes
Communicator graphic user interface
Conferencing for Microsoft Office No online help No online help
Communicator online help
Conferencing for Microsoft Office No No
Communicator installer

Web components
Recall that within the Conferencing solution, Avaya has developed the following Web-based
applications:
• Web Portal
• Audio Console
• Avaya Web Conferencing
• Conference Viewer
• Conferencing Manager administrative interface
This table shows the aspects of the Web components that Avaya has localized and
internationalized.

Web Portal administrative screens Yes No
Web Portal end user screens Yes Yes
Conference Viewer No No
Audio Console Yes Yes
Avaya Web Conferencing Yes Yes
Avaya Web Conferencing log messages No No
Avaya Web Conferencing recording server Yes Yes
Avaya Web Conferencing playback server Yes Yes
Conferencing Manager administrative interface Yes Yes
CRS components
This table shows the aspects of the Client Registration Server (CRS) components that Avaya
has localized and internationalized.

CRS Reservation Server Yes No
CRS Billing application Yes No
CRS Import Utility application Yes No

Directory Services Client Application (DSCA) Yes No

CRS Reports application Yes No
Notifications Subsystem Yes Yes
CRS SQL server e-mail notifications Yes Yes
APIs
Avaya has developed a number of Application Programming Interfaces (APIs) to enable
customers to customize their Conferencing solution and to enable them to develop their own
applications which process Conferencing data.
Some of the APIs are limited by a fixed field size. These APIs are SCHAPI, MODAPI, BCAPI,
and ACAPI. This means that Conferencing may truncate some text strings.
This table shows the aspects of the APIs that Avaya has localized and internationalized.

Session Initiation Protocol (SIP) notification Yes Not applicable
interface
XCON interface Yes Not applicable
CRS booking and scheduling API Yes Not applicable
CRS stored procedures Yes Not applicable
Avaya Conferencing API (ACAPI) Yes Not applicable
Bridge control API (BCAPI) Yes Not applicable
SOAP adapter error strings Yes Yes
Scheduling API (SCHAPI) Yes Not applicable
Moderator API (MODAPI) Yes Not applicable
Application server components

This table shows the aspects of the application server components that Avaya has localized
and internationalized. As with the APIs, some of the components are limited by a fixed field
size. This means that Conferencing may truncate some text strings.
Also note that the operator sign-in names and passwords are not internationalized or localized.


Audio message prompts Not applicable Yes
Media server Not applicable Not applicable
PostgreSQL database Yes Yes
Operator components
This table shows the aspects of the operator components that Avaya has localized and
internationalized.
Recall that within the Conferencing solution, Avaya has developed two applications specifically
for operators.
Operators differ from moderators and participants. Operators manage large numbers of
conference calls, for example, within a Conferencing provider environment. Operators attend
conferences and control features such as polling, question and answer sessions, and the help
queue. Operators use the Client Registration Server (CRS) Front End and the Bridge Talk
application to perform their tasks. Moderators book their own conferences and attend them.
Moderators use the Web Portal application or one of the plug-ins to perform their tasks.
Participants attend the conferences that moderators and operators book.
Note:

Bridge Talk Yes No
Client Registration Server (CRS) Front End Yes Yes


Chapter 18: Configuring audio messages
Audio messages and prompt sets

During a conference, Conferencing plays audio messages to participants to inform them of
conference information and to prompt them for a response. These audio messages are
sometimes called audio prompts or annunicator messages. A group of audio messages is often
called a prompt set.
Avaya ships Conferencing with the capability of supporting 20 prompt sets. You can configure
your deployment to use one or several of these prompt sets. Each prompt set contains 2000
message slots. By default, Conferencing uses 299 of these message slots for the basic audio
messages that guide participants through the process of using the Conferencing server.
In the remaining message slots, you can record new messages and configure Conferencing
to use these new messages.
Avaya does not recommend recording new messages over the default messages. Set0
contains the default English audio messages. Avaya stores the Conferencing prompt sets on
the application server in the /MX60Prompts/ directory. Each of the directories contains a folder
for messages and a folder for numbers. For example:
• /usr2/Prompts/MX60Prompts/French-CA/messages/
• /usr2/Prompts/MX60Prompts/French-CA/numbers/
• /usr2/Prompts/MX60Prompts/Russian/messages/
• /usr2/Prompts/MX60Prompts/Russian/numbers/
By default, Avaya ship Conferencing with the 299 default messages in a number of languages,
in addition to English.
The audio messages are Raw PCM audio, 8 KHz sample rate, 16-bit resolution, mono, mu-
Law files. These messages have a filename but no file extension. The filename of the saved
messages is one less than the message number on Conferencing. For example, message 1
has a filename of 0.
You can configure the instances in which Conferencing plays messages in the Audio
Conferencing > Conference Features > Conference Settings section.
As there are 2000 message slots in each prompt set and only 299 default messages, you can
use the spare message slots to record customized messages, such as per-conference
messages or system wide messages.

Configuring audio messages
Related topics:
Introduction to languages on page 281
Per conference messages on page 292
System wide messages on page 293
Message rules on page 293
Audio transcript on page 295
Linked files and linking on page 295
Per conference messages

Operators can use Bridge Talk to record messages to any message slot. For example, they
can record a new message for a specific conference. Using the CRS Front End, they can
associate the message with the conference. If operators use Bridge Talk to schedule their
conference, they cannot associate the message with the conference. The message slot that
they use must be in the prompt set that is associated with the conference. So, if Prompt Set
1 is associated with the conference, operators must record the conference message in a
message slot within Prompt Set 1.
Here is an example of a real world scenario:
• A Bridge Talk operator records a message using their telephone audio path and the Tools
> Annunciator dialog. They record the message in Prompt Set 2, message slot 1500.
They edit the corresponding text field with the message text.
• Conferencing stores the message in /usr2/Prompts/Set2/messages/1499.
• A CRS operator schedules a conference and selects Prompt Set 2 and message 1500
as the conference message.
This feature is only available for deployments of Conferencing on the S6200 server platform.
It is not available if your deployment consists of an S6800 conferencing server.
The CRS Front End does not have visibility of the message text so Avaya recommends
maintaining a separate transcript of messages for operators who have CRS Front End access
but not Bridge Talk access. Moderators can also use a DTMF keypad sequence (#2, by default)
to record their own message for their conference. These messages, created by moderators,
are entirely independent of the messages that the operator creates. To avoid confusion, it is a
good idea to refer to the messages that the operator creates as conference welcome messages
and to refer to the messages that the moderator creates as personal welcome messages.
Operating Avaya Aura™ Conferencing, which is available from support.avaya.com describes
this aspect of Bridge Talk and the CRS Front End.
Note:
The Standard Edition of Conferencing does not support the Bridge Talk application. In this
case, you could create recordings using an alternative method. You can then copy these

recordings to the relevant prompt set using an application such as WinSCP, which provides
secure copying.
System wide messages

Operators can also use Bridge Talk to record messages that Conferencing plays to all
conferences. Conferencing plays this message before any conference-specific messages.
System administrators enable this system wide message in the Audio Conferencing >
General Config > General section.
In-service examples of the use of this feature include messages such as:
• This is a loss of service announcement. Conferencing services will not be available 2am to
7am January 20th due to essential maintenance. Apologies for any inconvenience.
• Half price conferencing this weekend!
Note:
A limitation exists in relation to these per-conference and system messages. Specifically,
the Avaya Conferencing Provider Application Programming Interface (ACP API) does not
support these messages. So, if the ACP API is used to route participants to a conference,
the participants do not hear these messages. It is important to note that the Conference
Scheduler Plug-ins for Microsoft Outlook and IBM Lotus Notes use the ACP API to support
the Click to Join button. So, if participants enter a conference by clicking Click to Join,
they do not hear the per-conference or system messages.
A important point to note in relation to system wide messages is that if a caller dials in using
SCAN call flow, Conferencing plays the message in the language configured to the DNIS. If a
caller dials in using the DIRECT call flow, Conferencing plays the message in the language
associated with the conference. This behavior is due to the fact that the DIRECT call flow routes
the call directly to the conference.
Note:
The Standard Edition of Conferencing does not support the Bridge Talk application. In this
case, you could create recordings using an alternative method. You can then copy these
recordings to the relevant prompt set using an application such as WinSCP, which provides
secure copying.
Message rules
By default, Conferencing follows certain rules in relation to playing audio messages. It is
important to consider these rules when recording and configuring new audio messages.

• By default, Conferencing plays message 1 to each telephone line entering the

Conferencing system.
• Conferencing plays message 242 to callers who respond to a blast dial, unless the
operator specifies another message when they initiate the blast dial.
• Conferencing plays message 247 as the PIN code prompt for unattended conferences
with PIN codes security in effect.
• If you configure call branding for your customer, Conferencing plays the message that
you configure in for that call branding entry. If you assign 0 to a DNIS, Conferencing does
not play a welcome message.
• Conferencing plays some messages to individual lines and plays other messages to the
entire conference.
• When Conferencing plays a message to the entire conference, it mutes all conference
lines.
• Conferencing may delay some actions until the message finishes playing.
• If participants are listening to a line-specific message, Conferencing does not play any
conference tones to that participant.
• When Conferencing plays a message to the conference, operators can perform actions,
such as removing a line from a conference. If an operator accesses a line waiting for a
line message, Conferencing does not play any message to that line that it was intending to
play.
• Conferencing records all audio messages along with the conference.
• Under conditions of extremely heavy load, Conferencing may delay playing a message.
This behavior can result in a pause between a conference event and the corresponding
message. This behavior can occur if messages are long or if many participants enter a
conference within a short period of time. If this situation occurs, Avaya recommends
adjusting the lengths of messages or substituting a tone for a message.
• You can configure Conferencing to play a continuously looping “on hold” message in the
Enter Queue. If you enable the On-Hold Message Frequency parameter, this change
does not take effect until the Enter Queue clears. You can configure the On-Hold
Message Frequency parameter in the Audio Conferencing > Bridge Features >
Bridge Features section.
• Some messages are initial segments, such as The file number you entered is. Some
messages are middle segments, such as the digits 0-9. Some messages are tail
segments, such as Participants currently in your conference. Some messages are
standalone segments, such as Conference security has been activated.

Audio transcript
On the application server virtual machine, there is a file containing a transcript of message
text. System administrators should maintain an up-to-date transcript of message text.
It is a good idea to maintain an up-to-date list of message text. Avaya ships Conferencing with a
list of the default message text. If you intend to customize some of the messages in your
deployment, it is a good idea to keep this list aligned with the audio messages.
This file is located on the application server virtual machine in the usr/dcb/dbase/admin
directory and is called annmsgs.txt. You can access the file if you use PuTTY to log in to
the application server and navigate to the appropriate directory. You can view, copy, and edit it.
You can also view and edit the file using Conferencing Manager by navigating to the Elements
> Conferencing > Audio Conferencing > Bridge features > Prompt set management
screen.
Linked files and linking

Conferencing supports 20 prompt sets. To save space and optimize performance, Avaya does
not ship 20 separate prompt sets.
Avaya does not ship 20 separate prompt sets because separate sets take up a large amount
of disk space and it unlikely that every customer requires this large number of separate sets.
Instead, Avaya ships a smaller number of sets and links them to each other.
For example, set0 is the default set of English messages. Set1 is linked to set0. In a typical
deployment without any customization, system administrators configure the system prompt set
to use set1. Similarly, moderators and operators book conferences using set1 as the
conference prompt set. Due to the link between set1 and set0, the Conferencing server uses
set0 when set1 is selected as the system prompt set and the conference prompt set.
If you wish to customize some of the messages, Avaya recommends that you make a complete
copy of set0 and paste it into another set folder. This way, you retain a copy of the default
messages and you have a new copy that you can customize.
Related topics:
Introduction to languages on page 281

Configuring audio messages for your system

Within the Conferencing environment, a collection of audio messages is often called a prompt
set.
Prerequisites
Before you can configure audio messages for your system, you must install and configure
Conferencing. You must also obtain a list of available DDIs/DNIS telephone numbers which
you can use for conferencing provision.
The purpose of this task is to associate a language and a Conferencing telephone number.
When callers dial this telephone number, Conferencing plays audio messages in the
associated language.

5. Click Call Branding to display the Call Branding Entry table and click Add.
6. Enter a call branding entry using a DDI from your deployment.
7. Ensure that you enter a number in the Message Set Number field.
For example, enter 9 to ensure that Conferencing plays Russian audio messages
when participants dial this DDI.
8. Click Save.
You can change the move the entry up and down the call branding table.
Conferencing reads the table from top to bottom.
Example
To play Spanish audio messages, enter 15 in the Message Set Number field. It is also a
good idea to enable or disable Use Conf Message Set as required.

Configuring audio messages at conference-level
Next steps
Now it is a good idea to verify the language by dialling the DDI and listening to the audio
message response from the Conferencing server.
Related topics:
Configuring audio messages at conference-level

At conference booking time, operators and moderators can specify a particular audio message
language. This flexibility is useful if the operator or moderator knows that the participants in
their conference speak a different language from the system language.
Prerequisites
Before you can configure a specific language for your conference, you must install and
configure Conferencing. You must also configure a system language.
The purpose of this task is to set a conference-specific language that differs from the configured
system language.
• Book a conference using the CRS Front End.
a. Access the CRS virtual machine. You can use the remote desktop feature to access
b. Open CRS Front End > Customer Bookings and book a conference in the normal
way.
c. On the Options dialog, select a prompt set from the Prompt Set drop-down menu.
The prompt set you select here becomes the prompt set that is associated with the
conference. For example, if you select 4, Conferencing sets the conference
language to Spanish.
d. Finish the booking in the normal way.
• Alternatively, book a conference using Web Portal.
a. Log into the Web Portal moderator interface.
The Web Portal moderator URL is: http://Web Portal virtual machine
IP/webportal/login
b. Book a conference in the normal way.
c. On the Advanced Options screen after the Reservation Details screen, select a
prompt set from the Prompt Set drop-down menu.
d. Finish the booking in the normal way.

Next steps
It is a good idea to dial into the conference to verify the language. Also, it is a good idea to
consult Using Avaya Aura™ Conferencing Guide for more information about Web Portal
conference booking and Operating Avaya Aura™ Conferencing Guide for more information
about CRS Front End conference booking. Both of these guides are available from
support.avaya.com.
Related topics:
Conference language on page 283
Viewing prompt sets

Using Conferencing Manager, you can view the prompt sets and audio message text. The
Conferencing Manager management console provides remote access to the virtual machines
in the Conferencing network. Conferencing Manager obtains this information from the
application server, or bridge.
Prerequisites
Before you view prompt sets and message text, you must install and configure Conferencing.
The purpose of this task is to view the details of the audio messages in your deployment.

4. Navigate to Bridge features > Prompt set management.
5. View the list of prompt sets. You can also click View to view a list of the message text.
Next steps
It is a good idea to verify that the message transcript file on the application server is correctly
populating the fields in Conferencing Manager. You can do this by making a temporary change
to a specific message in the transcript file on the application server and looking again at the
message text on Conferencing Manager.

Viewing prompt sets
Related topics:


Chapter 19: Configuring recording
Introduction to recording
Conferencing includes a feature which enables customers to record their conferences. This
feature is useful for customers who wish to store any or all conferences for security reasons.
It is also useful for customers who wish to make conferences available for playback, for
example, to people who were unable to attend a conference.
Conferencing can store and manage recordings within the Conferencing server environment. If
customers use this option, it is often called on-bridge recording. Alternatively, customers can
send the conferences to an external device for recording, management, and playback. If
customers use this option, it is often called off-bridge recording. If customers use the off-
bridge recording option, they cannot make use of the playback facilities within Conferencing.
The following descriptions and tasks are mainly concerned with on-bridge recording.
As an aside, some people also refer to the recording feature as Digital Record and Playback
(DRP). You can configure settings related to the recording feature using the Elements >
Conferencing > Audio Conferencing > General Config > Recording and playback menu.
Related topics:
Recording and playback on page 168
Some important parameters relating to recording

There are a number of important parameters relating to the recording feature. You can
configure these parameters using the Conferencing Manager interface. You can find these
parameters in a number of locations on the Conferencing Manager interface:
• Elements > Conferencing > Audio Conferencing > Conference Features >
Conference Features.
• Elements > Conferencing > Audio Conferencing > General Config > Recording and
Playback.
• Elements > Conferencing > Audio Conferencing > General Config > General.
• Elements > Conferencing > Audio Conferencing > System Config > Miscellaneous >
Flex DAPI Settings.

Configuring recording
Related topics:
Digital conference record playback on page 133
Number of annunciator channels on page 149
Bridge ID number on page 151
Automatic record all on page 153
Secure blocks record on page 153
Playback small jump on page 156
Playback medium jump on page 156
Playback long jump on page 156
Bridge record on page 168
Phone number on page 169
Dial string on page 169
Pre dial delay period on page 169
DRP auto gen fname on page 170
Digital conference record playback

Digital Conference Record Playback relates to the ability of Conferencing to record
conferences and make them available for playback.
• If you select Digital Conference Record Playback:
Conferencing enables the recording and playback feature.
• If you do not select Digital Conference Record Playback:
Conferencing does not enable the recording and playback feature.
Bridge record
Bridge Record specifies whether Conferencing records conference information on the
application server or to an external device. The application server is also called the bridge.
Typically, conference recordings are stored on the usr3/confrp drive of the IBM 3650 M2. By
default this setting is set to On-bridge. If you configure Bridge Record to Off-bridge and
operators are using Bridge Talk Conference Scheduler, you must also configure Bridge Talk
Conference Scheduler to Off-bridge. If you do not configure Off-bridge recording in both
locations, Conferencing defaults to On-bridge.
• On-bridge
Conferencing records conference information to the bridge.
• Off-bridge
Conferencing records conference information to an external device. In an Off-bridge
deployment, you must enter a value in the Phone Number and Dial String parameters.

When you configure Conferencing for Off-Bridge recording and an operator or moderator
schedules a conference for a maximum of 10 participants, the conference can have either:
9 participants and an external recording, or 10 participants and no external recording.
Phone number
Phone Number specifies the number to dial when Bridge Record is set to Off-bridge. This is
the telephone number of the external recording device.
Dial string
Dial String specifies the DTMF digits that Conferencing sends to the external recording device
after the recorder answers the call. Some of the information contained in the Dial String may
be vendor-specific. Some information may be derived at run time. Use these values in the
string to specify run-time values:
• %P
This value is expanded at run time to contain the conference passcode.
• %T
This value is expanded at run time to contain conference start time in Linux time format
(seconds since 1/1/1970).
• %C
This value is expanded at run time to contain conference confirmation number.
For example, if you set the Dial String to *000#*%P#*%T#%C## and the following conference
properties apply in your conference:
• The Passcode is 1234
• The conference starts on August 3, 2010 at 9:58 AM
• The confirmation number is 123456789012
Under these conditions, Conferencing sends the string
*000#*1234#*1280829516#*123456789012## to the external recording device.
Pre dial delay period

Pre dial delay period designates number of seconds that Conferencing waits before sending
a Dial String to the external recording device. The maximum setting is 50.

DRP auto gen fname

DRP Auto Gen Fname identifies whether Conferencing automatically allocates a filename to
a conference recording when an operator or moderator manually initiates a recording. By
default, this setting is selected.
• If you select DRP Auto Gen Fname:
Conferencing automatically allocates a filename to a conference recording.
• If you do not select DRP Auto Gen Fname:
Conferencing does not automatically allocate a filename to a conference recording.
Instead, operators manually enter a filename and moderators enter a DTMF string on
their telephone keypad to represent the filename.
Playback small jump

options. By default, to rewind a playback by a short amount, users press 1 on their telephone
keypad. By default, to forward a playback by a short amount, users press 3 on their telephone
keypad. This parameter sets the number of seconds for that short amount.

options. By default, to rewind a playback by a medium amount, users press 4 on their telephone
keypad. By default, to forward a playback by a medium amount, users press 6 on their
telephone keypad. This parameter sets the number of seconds for that medium amount.
Playback long jump

options. By default, to rewind a playback by a long amount, users press 7 on their telephone
keypad. By default, to forward a playback by a long amount, users press 9 on their telephone
keypad. This parameter sets the number of seconds for that long amount.

Automatic record all

Automatic record all identifies whether Conferencing records all conferences, regardless of
the per-reservation setting. The default value is OFF.
Conferencing does not automatically record all conferences.
Conferencing automatically records all conferences.
As an aside, at reservation time, operators and moderators can enable two settings relating
to recording: Operators, using the CRS Front End or Bridge Talk, and moderators, using the
Web Portal, can enable the automatic recording of a conference. If they enable this feature,
Conferencing automatically starts recording the conference as soon as participants begin to
talk.
Operators, using the CRS Front End or Bridge Talk, and moderators, using the Web Portal,
can also enable moderator control of the recording feature. If they enable this feature,
moderators can start and stop the conference recording. The default value is ON. For more
information on creating reservations using CRS Front End, Bridge Talk, or the Web Portal, see
Using Avaya Aura™ Conferencing Guide, which is available from support.avaya.com The value
of Automatic Record All supersedes any reservation-specific settings.
Secure blocks record

Secure blocks record identifies whether Conferencing allows conference recording when a
moderator secures, or locks, the conference. By default, Secure blocks record is ON.
If a moderator locks a conference, by pressing *7 on their telephone keypad,
Conferencing terminates any in-progress recording and does not allow the moderator to
begin recording.
If a moderator locks a conference, Conferencing continues any in-progress recording and
allows the moderator to begin recording.

Bridge ID number
This number uniquely identifies the Conferencing application server, or bridge. The
Conferencing recording feature uses this number for all recording filenames. If Conferencing
automatically names a recording, it uses the following conventions:
The value of XXXX grows sequentially, as follows:
increments the value of XXXX. As an example, this scenario occurs when moderators
use their on-demand conference for a weekly meeting. Conferencing views this weekly
recurring meeting as multiple instances of a single conference.
If your deployment consists of a number of application servers, called a multicabinet
environment, there are implications for the automatic naming convention. Conferencing
encodes all recording filenames on a given bridge with the bridge number. This fact can be
used to keep recordings from difference bridges from having name conflicts if customers copy
them to a common playback device. Conversely, if customers can guarantee that name
conflicts will not occur due to other factors, such as configuring confirmation numbers to be
unique across all recording source bridges, then customers can set the Bridge ID Number
values to be the same on all bridges. In this scenario, users can play multi-sourced files from
a single-source playback. This scenario only operates successfully in a deployment that
includes a CRS server. If there is no CRS server, you must set the Bridge ID Number to a
unique value on all servers. Avaya recommends consulting with your Avaya Support
Representative for advice if your deployment includes a complex server environment. As an
aside, operators and moderators can manually specify the filename of a conference recording.
They can enter almost any digit string for this purpose but it must not start with zero. Automatic
filenames always start with zero. This filename forms the XXXX portion of the complete
recording filename:
Note:
In the Standard Edition of Conferencing, there is no support for a multicabinet environment.
The Enterprise Edition of Conferencing supports multicabinet.
Number of annunciator channels

Conferencing uses annunciator channels for playing greetings and in-conference
announcements as well as for recording and playing back conferences. Essentially,
Conferencing uses annunciator channels for any sound data going to or from the internal hard-

Enabling the recording feature
disk. This setting sets the maximum number of those resources that Conferencing uses at any
one time. In an in-service deployment, the record and playback features hold the annunciator
channel resource for long periods of time. For this reason, the record and playback usage is
capped at a sub-set (70%) of the value entered here.
Conferencing reserves 30% for the playing of regular audio messages during conferences.
This metric aims to balance the requirements of the regular conference audio messages and
the recording and playback feature. This parameter represents the number of overall
annunciator channels. The platform limit is 1500. This is also the default value.
Enabling the recording feature

Using Conferencing Manager you must enable the recording feature.
Prerequisites
Before you enable the recording feature, you must install and configure Conferencing.
The purpose of this task is to make the recording feature available for your participants.

4. Navigate to Conference Features > Conference Features.
5. Select the Digital Conference Record Playback checkbox.
6. Click Save.
Next steps
Now you can configure the recording feature.

Configuring the recording feature

You can customize the functionality of the recording feature to suit the requirements of your
customers and their network.
Prerequisites
Before you configure the recording feature, you must enable the recording feature.
The purpose of this task is to customize recording in your deployment.

4. Navigate to General Config > Recording and Playback.
5. Configure the following fields:
Bridge Record
Phone Number
Pre Dial Delay Period
DRP Auto-Gen Fname
6. Navigate to General Config > General.
7. Configure the following fields:
Playback small jump
Playback long jump
Automatic Record All
Secure Blocks Record
Bridge ID Num
8. Navigate to System Config > Miscellaneous > Flex DAPI Settings.
9. Configure the Number of annunciator channels field.

Configuring the playback call flow
10. Click Save.

Next steps
Now you can configure the playback parameters.
Configuring the playback call flow

To enable conference playback, you must add a call branding entry for a playback call flow.
You can do this by allocating a specific DDI/DNIS for playing back conferences and selecting
Playback at the On Entry drop-down list. Conferencing ignores many of these columns for
the playback call flow. For example, in a playback call flow, Conferencing ignores Reservation
Group, Conference Room Start, and Conference Room End.
When participants dial the DNIS that you configure for playback, Conferencing plays the audio
message that you enter in the Message Number field. In a typical in-service scenario, you
could enter a greeting message number here. If you enter a zero value in the field,
Conferencing does not play a greeting message.
Next, Conferencing plays an audio message to prompt the user for a conference reference
number. Once they enter the correct conference reference number, Conferencing prompts
them for their passcode. If they enter a valid passcode, Conferencing may additionally prompt
them for their name before granting them access to the conference recording. If there are one
or more recordings associated with the conference reference, Conferencing lists the total
number of recordings and plays a series of messages that offer access to each recording.
Related topics:
Managing files
As a system administrator, you must manage the recording files and ensure that users can
access them when required. There are two aspects to this configuration. You must consider
your allocation of on-demand port resource. You must also consider the recording file sizes
and names.

Prerequisites
Before you configure the options for managing files, you must enable the recording and
playback features.
The purpose of this task is to balance file sizes and available resources to ensure that
participants can access recordings when required.
• Ensure access for users.
• Manage recording size and names.
Related topics:
User access on page 310
File sizes and file names on page 310
Legacy Web Portal feature on page 312
User access
Calls to the playback call flow occupy on-demand port resources. Your allocation of on-
demand resources must take account of these lines. You can allocate a percentage of your
telephone ports for on-demand conferences using the On-Demand Pct % field. You can
configure On-Demand Pct % using the Conferencing Manager interface, by navigating to
Elements > Conferencing > Audio Conferencing > Conference Features.
Related topics:
File sizes and file names

Conferencing stores conference recordings in /usr3/confrp as Raw PCM audio, 8 KHz sample
rate, 16-bit resolution, mono, mu-Law files, wrapped up in a .WAV header.
Conferencing can store approximately 325 hours of recordings.
Individual recording files can contain up to four hours of digitally recorded conference dialog.
When the recordings directory /usr3/confrp reaches a certain size, Conferencing deletes
the files. Avaya has created a cronjob to monitor the /var partition. If the partition usage
exceeds 18 gigabytes, the cronjob deletes the oldest files in each of the following directories
until disk usage is brought below a threshold of 16 gigabytes:
• /usr3/confrp
• /usr3/savedroster

Managing files
• /usr3/pbkroster
• /usr2/roster
This cronjob runs on a daily basis. Avaya enables this cronjob by default on each new instance
of Conferencing. You can disable this cronjob. The cron does not delete from /usr3/
confrp if there is an external NFS server in the deployment.
The recording filenames use the following syntax:

<Reservation Confirmation Number>+<Bridge Number>+XXX
For the Standard Edition of Conferencing, the bridge number is 0, by default. The Standard
Edition of Conferencing does not support multiple bridges. A deployment with several bridges is
usually referred to as a multicabinet environment.
If you enable automatic naming of the recordings, using the DRP:Auto-gen fname parameter,
the value of XXXX begins with 0001 and grows to 09999999. If you enable automatic naming,
the value of XXXX grows sequentially, as follows:
increments the value of XXXX.
If you disable automatic naming and opt for manual naming of the recordings, the value of
XXXX begins with 1 and grows to 99999999. Manual names can be any name that does not
already exist.
Related topics:
Disabling the cronjob on page 311
Disabling the cronjob

Cron is a time-based job scheduler in Unix-like computer operating systems. The name cron
comes from the word "chronos", Greek for "time". Cron enables users to schedule jobs
(commands or shell scripts) to run periodically at certain times or dates.
The purpose of this task is to suspend a daily cronjob that deletes old files in a number of
folders. These folders are:
• /usr3/confrp
• /usr3/savedroster
• /usr3/pbkroster
• /usr2/roster


su sroot
4. Navigate to /usr/dcb/bin/aura-conferencing-bridge-engine-cron.
5. Add # to the start of the last line (purgeRecordings).
The cronjob updates automatically.
Legacy Web Portal feature

For Web Portal moderators, Conferencing still supports an older method of conference
playback. With the older functionality, moderators dial the conference telephone number and
enter the recording filename. Moderators can obtain the recording filename from the My
Recorded Conferences screen. The limitation with this method is that if the recording was
made using a previous version of Conferencing, such as Conferencing 5.1, they cannot access
the recording using this method. They must use the new method instead. If the recording was
made using Conferencing 5.2, they can access the recording using this older method. If you
delete a recording from the recordings folder /usr3/confrp, these recordings may still appear
on the Web Portal My Recorded Conferences screen. However, moderators will not be able to
access them.

Chapter 20: Producing bills for conferences
Introducing billing
The Conferencing Billing application provides data that is used as an input to an external billing
application in order to invoice users of the Conferencing system. Any audio and data events
occurring on Conferencing are output in the billing. This application differs from the
Conferencing Reports application in that the Conferencing Billing application runs on a
scheduled basis and produces machine readable output files. The Conferencing Reports
application, on the other hand, is used by administrators or operators to produce intuitive
representation of the same data.
The Conferencing Billing application supports many different billing formats. Here, we describe
billing format 0, which is a customizable billing format and is the recommended format in that
it is the most flexible. Billing format 0 is determined by the settings in the sbill.ini file, which is
located in the Windows directory.
The format of the billing output is defined by the administrator. You can choose which fields
you would like to output. The billing application produces a number of text files per day which
are stored in a designated network location where they can be accessed by the external
invoicing application. The fields included in the file, the sequence of fields, and the separator
must be designated. Also, the file name and the frequency of the billing must be defined.
Records without all fields populated can occur in the case of conference deletion.
Related topics:
CDR end date filename on page 174
Billing settings on page 212
Layout of bills
All fields that are required for billing must be designated in the sbill.ini file. For example, if you
require billing for Avaya Web Conferencing usage, it is necessary to include the Avaya Web
Conferencing fields in the definition of the billing output. All records produced in the bill file
have the same fields, however, some are blank depending on the type of event occurring on
the system. For example, an audio event results in the audio related fields being populated
and the data related fields are blank.

Producing bills for conferences
Field Type Description

Client fields Displays information relating to a particular client. For example, their e-
mail address, name and account reference number.
Reservation fields Displays information relating to conference reservations. For example,
the date and time the reservation was made, the reservation reference
number and status of the reservation.
ConfName fields Displays information relating to the conference name. For example, the
conference name, conference charge number and the conference
moderator’s name.
Conference fields Displays information similar to the ConfFields. The exception is that
Conference Fields also display information relating to when the
conference opened and closed.
Conferee fields Displays information regarding activities during a conference and also
PIN details. For example the amount of time spent on hold, the data
and time the conferee joined the conference and the conferee’s
personal PIN number.
Call fields Displays information regarding the calls connection to the conference.
For example the caller’s Direct Dial Inward (DDI) number, Caller Line
Identification (CLI) number and the line which the call was received.
For more information about each of the fields, contact your Avaya Support Representative.
Billing configuration
An initialization file called sbill.ini controls all the billing configuration settings. The sbill.ini file
resides in the billing directory on the CRS virtual machine. In most cases, you do not have to
configure this file because you can configure the most important properties using the
Conferencing Manager administration interface. These properties are listed here.
Related topics:
Primary bill file location on page 212
Secondary bill file location on page 212
Bill file extension on page 213
Bill file prefix on page 213
Bill frequency on page 213
Bill start offset (mins) on page 213
Bill at time on page 214
Bill file header on page 214
Bill file trailer on page 214
Period to retain CDR files on page 214

Free if cancelled X minutes before on page 214

Configuring billing on page 317
Primary bill file location

The Primary Bill File Location parameter specifies the folder location where Conferencing
outputs and stores conference billing files. By default, the Primary Bill File Location parameter
is C:\BILL\files. The Conferencing billing application also generates back-up billing files
and stores them in an alternative location, specified by the Secondary Bill File Location
parameter.
Secondary bill file location

The Secondary Bill File Location parameter specifies the folder location where Conferencing
outputs and stores conference billing files. By default, the Secondary Bill File Location
parameter is C:\BILL\files2. The secondary bill file location is for redundancy.
Conferencing also outputs billing files to a primary bill file location.
Bill file extension

The Bill File Extension parameter specifies the extension on the billing files that Conferencing
produces. By default, the Bill File Extension parameter is bil.
Bill file prefix

The Bill File Prefix parameter specifies the prefix of the bill file name. So, the full file name
consists of:
<Bill File Prefix><Bill Stamp>.<Bill File Extension>
Bill Stamp is the current file number.

For example, if the Bill File Prefix is Avaya_, the Bill Stamp is 123, and the Bill File Extension
is .bil, the next bill that Conferencing produces is Avaya_123.bil.
There is a special situation if you configure the Bill File Prefix parameter to the value <date>. In
this situation, Conferencing uses a special, date-based file name format. If the Bill File Prefix
parameter has the value <date>, Conferencing ignores the Bill Stamp number. Instead,

Conferencing names the files according to the current date, using the following format and
syntax:
YYMMDDNN.bil
• YY=year, where 2000=00
• MM=month, where October=10
• DD=day, such as 31
• NN=the file number on that particular day
For the first bill of the day, NN=00. The number increases incrementally from then
onwards. If the NN number reaches 99, Conferencing does not run until the date changes.
Bill frequency
The Bill Frequency parameter specifies how often Conferencing runs the billing cycle. If the
Bill Frequency parameter is 0, Conferencing generates a bill every day at the time specified
by the Bill At Time parameter.
Bill start offset (mins)

Bill Start Offset (mins) enables you to further configure the Bill Frequency setting. It enables
you to specify the minute part of the billing process schedule. If you set Bill Start Offset (mins) to
35, for example, and Bill Frequency is set to 1, then the billing schedule will look like this: 00:35,
01:35, 02:35, 03:35....and so on.
When Bill Start Offset (mins) is 0, this feature is turned off. When this setting is 0, then the
billing schedule depends on the time at which you start the application.
Bill at time
The Bill At Time parameter specifies the time that Conferencing produces billing data.
Conferencing uses this parameter solely for daily bills. By default, the Bill At Time parameter
is 0100.

Bill file header

The Bill File Header parameter specifies whether Conferencing adds a header to the bill output
file. If you select the Bill File Header parameter, Conferencing adds a header.
Bill file trailer

The Bill File Trailer parameter specifies whether Conferencing adds a footer to the bill output
file. If you select the Bill File Trailer parameter, Conferencing adds a footer.
Period to retain CDR files

The Period to Retain CDR Files parameter specifies an age threshold in days. If a file is older
than the value of this parameter, an automatic deletion task deletes it. For example, if Period
to Retain CDR Files=30, the CDR Loader automatically deletes the file if it is older than 30
days. The Call Detail Records (CDR) Loader is an application that transfers CDRs data from
the Conferencing application server, or bridge, to the CDRs database. The CDR Loader
application also supports the creation of billing information for a number of different bridges
using a single interface.
Free if cancelled X minutes before

The Free If Cancelled X Minutes Before parameter relates to the billing of cancelled
conferences. Cancelled conferences are billed if they are cancelled too late. If the cancellation
occurs no later than the time frame allotted in the Free If Cancelled X Minutes Before
parameter, the customer will not be billed. For example, if Free If Cancelled X Minutes
Before=180, a client that cancels a conference 180 minutes (3 hours) before its scheduled
start time is not billed. If a conference is cancelled within that time frame, Conferencing bills
the client.
Configuring billing
Prerequisites
Before you configure billing, you must install and configure Conferencing.

The purpose of this task is to change the default settings for the Billing application.

machine.
4. Click Configure.
5. On the Client Registration Server configuration sub-pages screen, click Billing
Settings.
7. Click Save.
Example
For example, you can change the default location for billing files or change the billing time.
Billing application graphic user interface (GUI)

In previous editions of Conferencing, Billing consisted of an application with a graphic user
interface (GUI). In the past, administrators used this GUI to configure many aspects of the
operation of billing. They could also configure advanced settings in the Billing initialization file,
called sbill.ini.
In the current edition of Conferencing, Billing is treated like a process or a service. It runs in
the background. Due to security settings in the Windows 2008 operating system, which runs
on the CRS virtual machine, administrators cannot access the Billing GUI while the BSMon is
running.
The Booking and Scheduling Monitor (BSMon) is a watchdog. A watchdog is a software timer
that triggers a system reset or other corrective action if the main program enters a faulty state.
BSMon monitors each of the Conferencing applications, such as the Billing application, the

Billing application graphic user interface (GUI)
CDR Loader application, and so on. If any of the Conferencing applications fails and closes,
BSMon restarts them.
For the majority of customers and deployments, the configuration of the settings in
Conferencing Manager is sufficient to ensure that Billing operates as required.
If you require access to the Billing application to create a bill for a specific date or date range
or for the rebilling function, you must:
• Stop the BSMon monitoring of Billing.
• Stop the Billing task using the Task Manager.
• Access the Billing application and perform the tasks that you require.
• Restart BSMon when you are finished.
The Billing GUI consists of a panel called Databases and a panel called Bill Files.
Databases panel
Item Description
Booking Data Displays the name of the Central Registration Server database.
Call Data Displays the name of the call database.
Login Timeout Displays the time in seconds after which logging into a database fails.
Query Timeout Displays the time in seconds after which a query to a database fails.
Bill Files panel
Item Description
Bill Delays Displays the time lag between the completion of a conference and the
dispatching of the conference bill. If it is set to “0” then all completed
conferences whose call data has been processed will be billed whenever
the billing generation is run. If it is “1” then any conferences completed in
the previous hour are not billed in the current billing.
Path The file path where billing output files are generated and stored.
Format The billing output format. This is customer specific.
Max Records The maximum number of billing records per bill file. One record is output
for each caller in a conference or for each unused or cancelled conference.
Bill Every The customer can specify (in the INI file) how often automatic billing
generation occurs.
Note:
This is between 1 and 24 hours.
Here are some of the tasks that the GUI enables you to perform.

To... Do This...
Initiate instant billing Click Bill Now.
The billing generation takes place instantly without waiting for the
automatic billing generation to occur.
View logs Click View Log.
The SBill log screen is displayed.
Rebill Click Rebill.
The Rebill dialog is displayed.
View version details Click About.
The billing version details are displayed.
Creating a bill for a specific date

The Billing application is called SBIll. It is a good idea to paste a shortcut to the SBill executable
file on the desktop. The Billing application resides on the CRS virtual machine.
Prerequisites
Before you create a bill for a specific date, it is a good idea to ensure that there was conference
activity on the day that you select. You can generate conference activity by booking some test
conferences and dialing into them.
The purpose of this task is to create a bill file for a specific date to view the billing details for a
single, selected, day.
1. Double click the Billing icon on the Windows desktop.

2. Ensure that all conferences are closed.
3. On the Billing Generation dialog, click Unbill.
4. Enter the specific date for which you want to create billing output.
5. Click OK.
6. Click Bill Now.
Billing output is created for this date.

Creating a bill for a specific date range
Creating a bill for a specific date range

Prerequisites
Before you create a bill for a specific date range, it is a good idea to ensure that there was
conference activity on the day range that you select. You can generate conference activity by
booking some test conferences and dialing into them.
The purpose of this task is to create a bill file for a specific date range to view the billing details
for that selected period.

2. Ensure that all conferences are closed.
3. On the Billing Generation dialog, click Unbill.
4. Enter the start date and the end date for the billing output.
5. Click OK.
6. Click Bill Now.
Billing output is created for this period.
Clarification on billing scenarios

There are three scenarios where more than one file is may be produced if the user has the
billing application configured to bill once a day.
• Threshold: If the threshold is passed a new file is created.

• Shut Downs: A bill file is produced when the SBill is shut down.
• Bill Now: When Bill Now is selected a new billing file is created.

Rebilling
The rebill feature enables you to regenerate a bill file for a specific day. It produces a file name
that is the day the data was rebilled (not the current date). You can configure the rebill file name
and where it is saved.
Ensure that the file generated during rebill is not processed by the standard external billing
system. This may create the risk of double billing.
• Rebill only works with “Billed” files. This does not apply to bill files created on the present
day. For example, the billed files must be created on, or before, the previous day.
• Rebill supports SBill formats 0, 6 and 7.
• All data is output to 1 file (format 0) or 2 files (format 6, 7).
Prerequisites
Before you use the rebill functionality, you must create a bill. Rebill only processes billed files.
The purpose of this task is to create a second billing output for a specific day. This feature is
useful if there were issues with the original bill on that day.

2. On the Billing Generation dialog, click Rebill.
3. Select the date to rebill from the Rebill for day drop-down list.
4. Enter the name of the file to rebill in the File name area. This only applies if you
want to change the default value.
5. Click to select a location to save the rebill path. This only applies if you want to
change the default value.
6. Click ReBill.
A dialog is displayed if you are creating a rebill with the same details as a previously
saved file.
7. Click OK.

Chapter 21: Configuring e-mail notifications
Introduction to notifications
The Avaya Notifications Subsystem program is an e-mail and short message service (SMS)
broadcast provider for the Conferencing system. The following types of e-mail, or SMS
broadcasts are currently available:
only)
The Notifications Subsystem runs on the CRS virtual machine and communicates with the
CRS by retrieving details of all notifications to be sent at given times. The requests are queued
until a resource line becomes available. The Notifications Subsystem is a back-end application
that should need little or no interaction with an operator.
Note:
The Standard Edition of Conferencing does not support SMS notifications. The Enterprise
Edition of Conferencing supports SMS notifications.
In previous editions of Conferencing, the Notifications Subsystem consisted of an application
with a graphic user interface (GUI). In the past, administrators used this GUI to configure many
aspects of the operation of notifications. In addition, in previous editions of Conferencing,
administrators also used a Template Editor application to customize e-mail templates. They
could also configure advanced settings in the Notifications Subsystem initialization file, called
broadcast.ini.
In the current edition of Conferencing, the Notification Subsystem is treated like a process or
a service. It runs in the background. Due to security settings in the Windows 2008 operating
system, which runs on the CRS virtual machine, administrators cannot access the Notification
Subsystem GUI while the BSMon is running.

Configuring e-mail notifications
In the current edition of Conferencing, administrators can configure many aspects of the
operation of notifications using Conferencing Manager. The Notifications Subsystem settings
are located in Elements > Conferencing > Client Registration > General. Administrators
can also customize e-mail templates using a HTML editor.
Conferencing Manager and the configuration of the HTML template will be sufficient to ensure
that Notifications Subsystem operates as required.
Task Location
Configuring notifications In Conferencing Manager, using the Elements > Conferencing
settings > Client Registration > General menu.
Customizing e-mail On the CRS virtual machine, in the installation directory (typically
templates the C drive) /Avaya/BroadcastScheduler/Booking/email/
email1.html.
However, in exceptional cases, administrators may require access to the advanced settings in
broadcast.ini. If administrators need to make changes to the settings in broadcast.ini, they
must stop the BSMon monitoring of the Notification Subsystem before they save the change.
This is called the back door method.
Related topics:
Notification settings on page 208
The Notification Settings section contains all the configurable options for e-mail notifications.
Related topics:
Conference reminder X minutes before on page 208
Activate e-mail notifications on page 208
Activate attachments on page 209
Attachments directory on page 209
Activate attendance notifications on page 210
Web conferencing URL on page 210
Activate vcalendar on page 210
Activate SMTP on page 210
SMTP server address on page 210
SMTP server port on page 211

SMTP username on page 211

SMTP password on page 211
Authenticate on page 211
HTML format on page 211
Attendance record processing delay on page 212
Activate SMS notifications on page 327
Self registration URL on page 327
Conference reminder X minutes before

The Conference Reminder X Minutes Before parameter relates to the notification options
feature on the CRS Front End Options dialog. When operators schedule conferences, they
can specify notification options, such as a reminder option. When operators select the reminder
notification option, conference participants receive a reminder before the conference starts.
The Notifications Subsystem is the mechanism that sends the notification. This parameter
specifies the timing of the reminder. For example, if Conference Reminder X Minutes
Before=180, then each participant receives a reminder 180 minutes (3 hours) before the
scheduled start time.
Activate e-mail notifications

The Activate E-mail Notifications parameter specifies whether Conferencing sends e-mails to
remind and inform participants of conferences. Some examples of e-mail notifications include:
only)
which types of e-mail notifications they would like to send. You must enable this parameter in
order to make the e-mail notifications option available at booking time.

Activate attachments
The Activate Attachments parameter specifies whether moderators can send attachments with
conference invitations using the Web Portal application. To enable moderators to send
attachments in Web Portal, you must enable this parameter.
methods. The Activate Attachments parameter applies to situations whereby a moderator
invites conferees using the on-board Web Portal address book.
Attachments directory
The Attachments Directory parameter specifies a folder that the Notifications Subsystem
checks for files to send as attachments to conference invitations sent from Web Portal.
methods. If they invite conferees using the on-board Web Portal address book, they can add
attachments to the conference invitation.
The Notifications Subsystem is the application which provides e-mail and SMS broadcast
services for Conferencing.
When moderators, using Web Portal, attach a file to a conference invitation, the Web Portal
copies the file to a folder on the Conferencing application server. The Notifications Subsystem
checks this folder on the application server and attaches the file to the conference invitation.
This parameter specifies the folder on the application server that the Notifications Subsystem
checks for files. You must ensure that you configure a value on the Web Portal to ensure that the
Web Portal copies the file to the same folder. The two values must be consistent in order for
the feature to operate successfully. The Web Portal parameter is in webportal.properties and
is called AttachmentsFolder.
An issue arises because the Web Portal virtual machine uses the Linux operating system and
the CRS virtual machine uses the Windows operating system. The Notifications Subsystem
resides on the CRS virtual machine. The CRS virtual machine has difficulties reading the Linux
syntax for the folder location. As a result, you have to perform some manual configuration. On
the CRS virtual machine, you must map a new network drive for \\<Web Portal virtual machine
IP address>\attachments. Ensure that you select Reconnect at Login and set avaya as both
the username and password.
Related topics:
Configuring the attachment folder and security

Activate SMS notifications

The Activate SMS Notifications parameter specifies whether Conferencing sends Short
Message Service (SMS) mobile telephone messages to remind and inform participants of
conferences.
which types of SMS notifications they would like to send. You must enable this parameter in
order to make the SMS notifications option available at booking time.
Activate attendance notifications

The Activate Attendance Notifications parameter specifies whether Conferencing sends a list
of the participants to a moderator when a conference finishes. An application called Post
Conference Reports generates the attendance information when a conference completes.
which types of notifications they would like to send. You must enable this parameter to ensure
that Conferencing can successfully send the attendance report.
Web conferencing URL

The Web Conferencing URL parameter specifies the uniform resource locator (URL) address,
or link, for the Avaya Web Conferencing (AWC) application. When moderators using Web
Portal or operators using the CRS book a conference that includes a Web conference aspect,
Conferencing includes the Web conference link in the e-mail invitation notification for all
participants. Web conferences are also known as data conferences. The AWC application is
the application which enables Web conferences. AWC operates alongside the Conferencing
server to provide a combined audio and data conference experience. Using AWC, moderators
can present slides, annotate whiteboards, and exchange messages.
Self registration URL

The Self Registration URL parameter specifies the uniform resource locator (URL) address,
or link, for the Avaya self registration online form. When moderators using Web Portal or
operators using the CRS book a conference with Self Registration enabled, Conferencing
includes a link to the self registration online form.
Self registration is the process of conferee enrollment. Individual conference conferees access
a virtual sign-in sheet and submit their personal details. Using these details, Meeting Exchange

compiles a list of registered conferees. The conference organizer can use the conferee list to
co-ordinate the conference with maximum efficiency and minimal delay at the start of the
conference. Typically, self registration is used for a type of secure broadcast known as an event
call. Event calls involve the transmission of often highly sensitive information to a group of
interested parties, such as investors.
Activate vcalendar
The Activate vCalendar parameter specifies whether Conferencing generates a vcalendar file
for each scheduled conference. If you enable the Activate vCalendar parameter, Conferencing
generates a vcalendar file and attaches it to conference invitation notification e-mails.
vCalendar is an industry standard format for exchanging scheduling and activity-recording
information electronically. If Conferencing sends a vCalendar attachment in an invitation e-
mail, participants can drag-and drop it (or otherwise move it) to a personal information manager
(PIM) type of application program and integrate with or relate it to their own schedule.
vCalendar was developed along with the vCard electronic business card specification.
Activate SMTP
The Activate SMTP parameter specifies whether Conferencing uses the Simple Mail Transfer
Protocol (SMTP) protocol for e-mail notifications.
Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (e-mail)
transmission across Internet Protocol (IP) networks.
By default, the Activate SMTP parameter is not selected.
SMTP server address

The SMTP Server Address parameter specifies the SMTP server address used by the stored
procedure p_CheckMailAndSend. The co-chairperson feature also uses the SMTP Server
Address parameter. The p_CheckMailAndSend stored procedure checks for e-mails in the
SMTP server port

The SMTP Server Port parameter specifies the SMTP server port used by
p_CheckMailAndSend. The co-chairperson feature also uses the SMTP Server Port

parameter. The p_CheckMailAndSend stored procedure checks for e-mails in the

SMTP username
The SMTP Username parameter specifies a username that Conferencing uses to log in to the
SMTP password
The SMTP Password parameter specifies a password that Conferencing uses to log in to the
E-mail sender
The E-mail Sender parameter specifies the name or phrase that Conferencing enters in the
From field of the e-mail notifications that it sends. For example, if the E-mail Sender parameter
is conferencing@customername.com, participants receive e-mail notifications from this
e-mail address.
Related topics:
Authenticate
The Authenticate parameter specifies whether Conferencing requires a username and a
password to log in to the e-mail server. The Authenticate parameter adds a layer of security
to the e-mail communications.

HTML format
The HTML Format parameter specifies whether Conferencing uses Hyper Text Markup
Language in the e-mails that it sends. If you do not select the HTML Format parameter,
Conferencing uses plain text in the e-mails that it sends.
Attendance record processing delay

The Attendance Record Processing Delay parameter specifies the number of minutes after
the current time that must elapse before the Post Conference Report application queries the
data for this time period.
The Post Conference Report application examines the booking and billing databases and
makes conference details available to other applications, such as the Notifications Subsystem.
The Notifications Subsystem is the e-mail and SMS broadcast provider for Conferencing. The
Post Conference Report application polls the booking database at a configurable time period
and obtains a list of closed conferences. For example, if Attendance Record Processing
Delay=15, the Post Conference Report application polls the database every 15 minutes for
conferences that closed in the last 15 minutes.
Configuring notification settings

In the current edition of Conferencing, you can configure many aspects of the operation of
notifications using Conferencing Manager.
Prerequisites
Before you configure the notifications subsystem, you must install Conferencing and open
The purpose of this task is to configure and customize the operation of e-mail notifications to
match the requirements of your deployment,.

machine.

Advanced settings

4. Click Configure.
5. On the Client Registration Server configuration sub-pages screen, navigate to
General > Notification Settings.
7. Click Save.
Example
For example, enter the name of the customer in the EMail Sender field, such as
conferencing@companyname.com. Also, if your deployment includes an AWC virtual
machine, ensure that you enter the IP address of the AWC virtual machine in the Web
Conferencing URL field using this syntax: http://AWC virtual machine IP/
conferencing.
Next steps
Now you can configure the e-mail templates for your notifications.
Advanced settings
The majority of customers will never have to make any changes to the Notifications Subsystem
initialization file, broadcast.ini. A limited number of customers may wish to know the location
of the file and an explanation of the significant fields. The information for those customers is
provided here. If you need to make changes to the settings in broadcast.ini, you must stop the
BSMon monitoring of the Notification Subsystem before you save the change. This is called
the back door method.
The broadcast.ini file is located on the CRS virtual machine installation directory (typically the C
drive) /Windows/.
You can access the CRS virtual machine using the remote desktop feature. You can open
broadcast.ini using the Notepad application.
All the parameters in broadcast.ini have default values. If you need to make changes to these
values, you must break the connection between BSMon and the Notifications Subsystem. This
is called the back door method. After you complete the changes, you can restore the BSMon
monitoring of the Notifications Subsystem.

FileName The name of the logging text file. The default is broadcast.log.
MaxFileSize The maximum size in kilobytes of the logging file. The default is 200KB.
WorkingDir Internal working directory and position of e-mail templates. The default is /
Avaya/BroadcastScheduler/Booking/Email.
DateFormat Sets the mask for all dates in e-mail output. The default is DD/MM/YYYY.
TimeFormat Sets the mask for all times in e-mail output. The default is TTT, which
corresponds to the AM/PM clock.
PollingDir Directory of raw report files by PC Reports. The default is /Avaya/PCReports/
Output.
The variables in the template

The e-mail templates for notifications consist of text and variables. Conferencing substitutes
the variables for the correct value as it applies for each notification. For example, Conferencing
replaces the variable called [CNUM] with the conference reference number and [CSTIME] with
the conference start time.
The e-mail templates are completely configurable. Avaya has populated the templates with
default text, which you can edit as necessary. A single HTML file contains all the settings for
all the different types of notification, such as the reminder notification and the cancellation
notification. The file is located in the installation directory (typically the C drive) /Avaya/
BroadcastScheduler/Booking/email/email1.html
RNUM Booking reservation number
CNUM Conference reference number
CNAME Conference name
CSTIME Conference start time
CETIME Conference end time
CSDATE Conference start date
CEDATE Conference end date
CMTIME Conference booking modified time
CMDATE Conference booking modified time
FTEXT Comment box/Free text
NAME Participant name

The variables in the template
EMAILER Receiver’s e-mail address

DDI Conference direct dial in
PIN Conference PIN entry number
CPIN Conference conferee passcode
MPIN Conference moderator passcode
UNAME Operator name
CMNAME Company name
CLNAME Client name
CFREES Conference participant size
DATE Current date (see DateFormat.)
TIME Current time (see TimeFormat.)
CHAIRNAME Name of moderator
CHAIREMAIL E-mail of moderator
TZONE Conference time zone
LOCALTIME Conference local time
LOCALDATE Conference local date
PPIN Participant PIN
CLNUM Client reference
CMNUM Company reference
CLACC Client a/c
DDIS Number of DDIs associated with conference
DPIN PIN associated with multiple DDIs
DDILOCAL Location associated with DDI
DDIPHONE Phone no. associated with DDI
SysOwner1 The owner of the system. Free text field.
SysOwner2 Second line of the system owner name. Free text field.
SysAdr1 First line of the address of the system owner. Free text field.
SysAdr2 Second line of the address of the system owner.
SysAdr3 Third line of the address of the system owner. Free text field.
SysURL1 Typically used for Self Registration or Avaya Web Conferencing (AWC)
links.
SysURL2 Typically used for Self Registration or AWC links.

SysURL3 Typically used for Self Registration or AWC links.

GLOBALIND GLBIND Indicates if conference is booked as global. 1 = yes 0 = No
Customizing e-mail templates

The Notification Subsystem supports a form of e-mail transport called Simple Mail Transfer
Protocol (SMTP). It does not support a form of e-mail transport called Messaging Application
Programming Interface (MAPI).
Prerequisites
Before you customize the e-mail templates, ensure that you configure the notification settings
in the Conferencing Manager.
The purpose of this task is to replace the text in the e-mail templates with new text. You can
also cut and paste the variables as necessary.
d. Enter the username administrator and the password Avaya123.
2. Navigate to the HTML file in the installation directory (typically the C drive) /Avaya/
BroadcastScheduler/Booking/email/email1.html.
You can open this file using any application that supports HTML editing. This single
template file contains all the text from each of the different types of e-mail
notification.
3. Customize the text as appropriate.
4. Save the file.
Next steps
Now it is a good idea to verify the notifications functionality by booking a test conference and
checking to see if Conferencing sends a notification.

Viewing logs
Viewing logs
In previous versions of Conferencing, you could view the logs of the Notification Subsystem
using the Notification Subsystem GUI. In the current release, you must navigate to the log
directory in order to view the logs. If BSMon is running, the Notification Subsystem GUI is not
accessible.
Prerequisites
Before you view logs, ensure that Conferencing generates some notifications so that the log
files have meaningful content.
The purpose of this task is to view the recent activity on Notification Subsystem. This task is
useful for troubleshooting any issues.
2. Navigate to the HTML file in the installation directory (typically the D drive) /Avaya/
BroadcastScheduler/Broadcast.log.
You can open this file using the Notepad application.
3. View the recent activity on Notification Subsystem.


Chapter 22: Understanding PINs, passcodes,
and security
Understanding some terms

At this stage, it is a good idea to clarify some terms in relation to accessing conferences. In
particular, these terms relate to the codes that participants enter in order to access their
conference. Conferencing supports a number of levels of security.
Term Explanation
Passcode A passcode enables entry to a conference. There are two types of passcode:
conferee passcode and moderator passcode. A conferee passcode grants
access to conferee-level conference features. A moderator passcode grants
access to moderator-level conference features. In the Conferencing
applications, Passcode is often shorted to Code. In the wider Conferencing
environment, many people refer to passcodes as security codes, host codes,
conference codes, access codes, entry codes, and even PIN codes.
Passcodes are specific to conferences.
PIN code PIN code is an identification number that is unique to each participant (both
moderators and conferees). The name of the participant and their unique
identification number are stored in a PIN list. When operators using the CRS
Front End and moderators using the Web Portal, create a new participant, the
CRS generates a PIN code for each new participant. The CRS Front End
interface refers to this field as User PIN. The PINs and the name of the
participant are stored in a database table. If an operator, using the CRS Front
End or a moderator using the Web Portal books an unattended conference,
they can choose a PIN Mode in the Options dialog. If customers require
additional security for their conferences, they can book conferences that
require a conference passcode and the participant’s PIN code to access the
conference.
PIN codes are specific to individuals.
Second If an operator books a flex flow conference using the CRS Front End, they
level can enable Security Passcode at booking time. If the operator enables this
passcode feature, Conferencing plays a message such as "Would you like to associate a
second level passcode with this conference?" to moderators after they enter
their moderator passcode. moderators can then enter a code using DMTF.
Moderators are responsible for distributing this code to conferees. To
successfully access the conference once the moderator has registered the

Understanding PINs, passcodes, and security
Term Explanation
code, conferees require their conferee passcode and the Second Level
Passcode.
This feature is not available to moderators who book conferences using Web
Portal.
Secret PIN Secret PIN is a participant’s unique, self-managed, hidden number. Operators
and system administrators cannot see this number. System administrators
can reset this number, using the System Administration section of the CRS
Front End.
Each user knows their own number and can change their number if:
• They have access to the Web Portal.
• A system administrator resets the number using the CRS Front End.
If a system administrator resets the number, the CRS sends a notification to
the participant, which includes a link to a Web location where they can change
the number.
Employee Employee identifying number is also a participant’s unique, personal number.
identifying However, this number is generally widely known or accessible. An example
number is an employee’s human resources number.
Security For operators using CRS Front End and moderators using Web Portal, there is
checkbox a configuration option, which is available during conference booking. This
checkbox is called Security and is unrelated to passcodes, PIN codes, secret
PINs, and employee identifying numbers.
It is mentioned here to prevent any confusion.
The Security checkbox is only available if a moderator is selected for the
conference. When the Security checkbox is selected, the conference is
called a secured conference. In a secured conference, a moderator can
prevent anyone from listening to or joining the conference. Specifically,
operators cannot enter, record, scan, or listen to the conference. Moderators
must press *7 on their telephone keypads during the conference to activate
this feature. Moderators hear a tone or voice message to indicate that the
conference is secured or unsecured.
PIN functionality
At conference booking time, an operator using the CRS Front End or a moderator using the
Web Portal can specify a PIN Mode. The PIN Mode button is displayed in the Options dialog on
CRS Front End and within the Advanced tab on the Web Portal. The PIN mode options are:
• Off
• System
• Conference

PIN functionality
Off
If an operator or moderator selects Off, Conferencing does not use PIN codes for the
conference reservation.
System
If an operator or moderator selects System, Conferencing grants conference access to a
participant if they enter the correct passcode and a PIN code which matches any entry in the
system’s PIN list, which is stored in a database table.
The CRS creates this PIN list automatically. When an operator adds new participants to a
Client’s address book or a moderator adds new participants to their own address book, the
CRS allocates a PIN to each new participant. Conferencing stores the PIN in a system-
generated PIN list.
Operators and moderators use System PIN mode when they need to identify attendees. Each
attendee has a unique PIN.
Conference
If an operator, using CRS Front End, selects Conference, Conferencing grants conference
access to a participant only if they have been invited to that particular conference. In other
words, it grants access if a participant enters the correct passcode and a PIN code which
matches any entry in that particular conference’s PIN list. The CRS automatically creates a
conference PIN list for each conference. The conference PIN list contains the PINs of
participants who have been specifically invited to that particular conference.
Operators do not have to enter the name of a PIN list in the PIN List field. Behind the scenes,
Conferencing uses this naming convention: cl_conference reference.txt. If the
conference reference is 123456, Conferencing automatically enters cl_123456.txt in the
PIN List field.
Similarly, if a moderator, using Web Portal, selects Conference, they do not need to enter the
name of a PIN list in the PIN List field. On the Web Portal, moderators cannot edit the PIN
List field. Conferencing automatically allocates the cl_conference reference.txt PIN
list to the conference.
Operators and moderators use Conference PIN mode when they need to add security to the
conference. This mode guarantees that the participants have been specifically invited.
Related topics:
PINs in use on page 339
PINs in use
PINs and conference types
PIN functionality varies depending on the type of conference that the operator or moderator is
booking.

Conference Functionality
Unattended For Unattended conferences, operators and moderators can choose
conferences Off, System, or Conference PIN mode.
Attended For Attended conferences, Conferencing disables PIN mode
conferences functionality.
Flex flow For flex flow conferences, operators and moderators can choose Off,
conferences System, or Conference PIN mode.
Self Registration If an operator using CRS Front End books a self registration
conferences conference, Conferencing disables the PIN mode options on the
interface. The PIN mode options are inaccessible to operators
because, for self registration conferences, Conferencing automatically
uses the Conference PIN mode. The CRS generates a subset of the
PIN List database table for each self registration conference. This
subset contains only the invited, or registered, participants.
Note:
In the Standard Edition of Conferencing, there is no support for self
registration.
PINs and the user experience

Conferencing users are participants, either moderators or conferees, who attend conference
calls. The user experience varies depending on the PIN mode.
PIN mode Experience when entering the conference

Off Participants enter their passcode on the telephone keypad.
System Participants enter their passcode and their PIN code on the telephone keypad.
Conference Participants enter their passcode and their PIN code on the telephone keypad.
Secret PIN functionality

Operators, using CRS Front End, or moderators, using Web Portal can add varying levels of
security to the conference, using the Participant ID Mode option.
At conference booking time, an operator using the CRS Front End or a moderator using the
Web Portal can specify a Participant ID Mode. The Participant ID Mode button is displayed
in the Options dialog on CRS Front End and within the Advanced tab on the Web Portal. The
Participant ID Mode options are:
• Off
• Identify
• Identify & Validate

It is important to note that if operators enable the Participant ID Mode option, Conferencing
ensures that the PIN Mode is set to Off. You cannot use both features in a single conference.
Off
If an operator or moderator selects Off, Conferencing disables the Participant ID Mode feature.
Identify
If an operator or moderator selects Identify, Conferencing ensures that all conference
participants must enter an identifying number on their telephone keypad prior to entering the
conference. In some cases, this number identifies an individual participant. In other cases, this
number identifies a participant as an external guest participant.
Identify & Validate
If an operator or moderator selects Identify & Validate, Conferencing ensures that all
conference participants must enter an identifying number and a PIN on their telephone keypad
prior to entering the conference. In some cases, this number identifies and validates an
individual participant. In other cases, this number identifies and validates a participant as an
external guest participant. CRS system administrators can reset PIN numbers on behalf of a
participant but operators cannot reset or change PIN numbers.
Related topics:
Secret PINs in use on page 341
Secret PIN administration on page 342
Secret PINs in use

To understand secret PIN functionality, consider a scenario in which an organization holds a
conference call which contains participants from the organization and also participants from
an external organization.
Participant ID mode: Identify
The Conferencing solution is installed in organization A. The participants in organization A all
have an employee number as their identifying number. When these participants enter a
conference, Conferencing can uniquely identify each individual. When a member of
organization A invites a participant from organization B to a conference, Conferencing sends
the participant from organization B a guest number, which identifies them as a guest. All guests
use the same number.
Participant ID mode: Identify & Validate
As before, the Conferencing solution is installed in organization A. The participants in
organization A all have an employee number as their identifying number. They also all have a
secret PIN number. Conferencing notified participants of their secret PINs using e-mail
notification. When these participants enter a conference, Conferencing can uniquely identify
each individual and will not grant conference access unless participants know their employee
number and their secret PIN. When a member of organization A invites a participant from
organization B to a conference, Conferencing sends the participant from organization B a guest

identifying number and a guest PIN number, which validates them as a guest. All guests use
the same numbers.
Secret PIN administration

It is important to note that Conferencing only allocates unique identifying numbers and secret
PINs to participants created using the Import Utility or Directory Services Client Application
(DSCA). This is a significant aspect of the functionality.
When Operators using CRS Front End and Moderators using Web Portal create participants,
Conferencing always allocates a guest identifying number and a guest PIN number to them.
As a system administrator, you can use the Directory Services Client Application (DSCA) or
the Import Utility to give clients their true identifying number and secret PIN number. When you
import clients using the Import Utility, you can enter their true identifying number, which
identifies them as members of an organization and not guests.
Similarly, when you use the DSCA to import client accounts from a Lightweight Directory
Access Protocol (LDAP) server, you can associate clients with their personalized identifying
number.
As a system administrator, you cannot access each user’s secret PIN. You can reset the secret
PIN using the CRS Front End. If you reset the secret PIN, the CRS sends a notification to the
user, which includes a link to a Web location where they can change the number. This Web
location is known as the PIN Management Web site.
Similarly, operators cannot access secret PINs. In addition, they cannot reset secret PINs.
However, operators using CRS Front End can see the employee identifying number of
conference participants on the Edit Participant dialog. Moderators, with access to Web Portal,
can change their own secret PIN on the PIN Management Web site. For more information on
how operators and moderators use these fields, see Using Avaya Aura™ Conferencing, and
Operating Avaya Aura™ Conferencing which are available from support.avaya.com.
• Using Avaya Aura™ Conferencing describes the Web Portal.
• Operating Avaya Aura™ Conferencing describes the CRS Front End.
As a system administrator, there are a number of tasks involved in the administration of secret
PINs.
• You must configure the address of the PIN Management Web site where participants can
change their own secret PIN. In order for this feature to operate successfully, you must
have a Web Portal virtual machine and a CRS virtual machine. This is a task that you
should only have to do when you install or upgrade Conferencing.
• If participants forget their secret PINs, you must reset their secret PIN. When you reset
a secret PIN, Conferencing sends the participant an e-mail which contains their new
secret PIN. If the participant has access to the Web Portal as a moderator, they can then

change their secret PIN to a value which they can easily remember. This is potentially a
regular task.
• You must customize the e-mail that participants receive when you reset their PIN. There is
a single e-mail for all companies in your CRS. You cannot customize the text on a per-
company basis. This is a task that you should only have to do when you install or upgrade
Conferencing.
• You must allocate values for the guest identifying number and guest secret PIN. This is
a task that you should only have to do when you install or upgrade Conferencing.
• You must configure the Web Portal settings, such as Mail server and Mail from using
Conferencing Manager by navigating to Elements > Conferencing > Web Applications
> Web Portal. This is a task that you should only have to do when you install or upgrade
Conferencing.
Related topics:
Configuring guest numbers on page 343
Configuring PIN Management Web site on page 344
Customizing e-mail on page 345
Resetting a secret PIN on page 347
Configuring guest numbers

Prerequisites
Before you configure values for the guest secret PIN and the guest employee ID number, you
must install Conferencing and configure the CRS virtual machine.
The purpose of this task is to enable participants from outside of the company to enter a
conference that has been booked with the Identify or Identify and Validate Participant ID
Mode.

machine.
4. Click Configure.
General > General Settings.
6. Enter values for External user participant identifier and External user
participant PIN.

The External user participant identifier is the guest equivalent of the participant
identifying number. It is necessary when Participant ID Mode is Identify.
The External user participant PIN is the guest equivalent of the participant secret
PIN. It is necessary when Participant ID Mode is Identify and Validate.
7. Click Save.
Next steps
Now it is a good idea to verify the secret PIN functionality by booking a conference with the
Identify and Validate Participant ID Mode.
Configuring PIN Management Web site

The PIN Management Web site is a Web application where participants can enter a new secret
PIN. When a system administrator clicks Reset Secret PIN on the CRS Front End Edit
Participant dialog, Conferencing sends the participant a link to the PIN Management Web site.
Prerequisites
Before you configure the PIN Management Web site, ensure that you install Conferencing and
configure the Web Portal and CRS virtual machines.
The purpose of this task is to configure the address of the PIN Management Web site. By
default, there may already be a value configured, but it is a good idea to verify the value before
deploying Conferencing in your network

machine.
4. Click Configure.
General > General Settings.
6. Enter a value for URL to reset participant secret PIN using the following syntax:

http://<IP address of the Web Portal virtual machine>/part-pin-webapp/faces/

pages/login-frontend.xhtml?participantRef=<ref>
7. Click Save.
Next steps
Now, you can customize the e-mail that participants receive when you reset their PIN.
Customizing e-mail
When you reset a secret PIN, Conferencing sends the participant an e-mail containing the PIN
Management Web site link.
In most cases, when Conferencing sends e-mails, it uses a mechanism called the Notifications
Subsystem. For example, Conferencing uses the Notifications Subsystem when it sends
conference reminder e-mails or conference cancellation e-mails. You can customize the
Notifications Subsystem e-mail templates using a HTML file on the CRS virtual machine.
For the reset secret PIN notification e-mail, Conferencing does not use the Notifications
Subsystem. You cannot customize the reset secret PIN notification e-mail using the CRS virtual
machine. You must customize the reset secret PIN notification e-mail using the Web Portal
virtual machine. The Web Portal virtual machine uses the Linux operating system. You cannot
use the remote desktop feature to access the Web Portal virtual machine. Instead, you must
use a terminal emulator, such as PuTTY.
Prerequisites
Before you customize the e-mail template that Conferencing sends when you reset a secret
PIN, ensure that you have a knowledge of the commands that the Linux operating system uses
and a knowledge of the VI text editor.
The purpose of this task is to customize the e-mail containing the PIN Management Web site
link that Conferencing sends when you reset a secret PIN. For example, you can add the
customer name to the default text.
1. If you don't have it installed already, download PuTTY from http://

www.chiark.greenend.org.uk/~sgtatham/putty/download.html.

There are many different PuTTY downloads listed. Typically, your deployment
requires the putty.exe file.
2. Start PuTTY.
3. On the PuTTY dialog, enter the hostname or IP address of the Web Portal virtual
machine.
su sroot
6. Navigate to the folder which contains the e-mail template by entering this command:
cd /opt/webapps/part-pin-webapp/customisations/default/
default/email/reset_pin_mail.tpl
7. Open the template in a text editor, such as vi.
vi is a modal text editor. The name vi is derived from the shortest unambiguous
abbreviation for the command visual in ex; the command in question switches the
line editor ex to visual mode.
The default text is as follows:
MX Conferencing Self Admin Pin Change Notification
Hello %Name%,
your new pin has been reset to %Pin% by a system
administrator.
regards,
The MX Conferencing Team
Please do not reply as this is not a monitored address.
The text between %% is replaced by live values. If a participant e-mail is empty,
Conferencing sends the e-mail to the client e-mail address. If the client e-mail
address is empty, Conferencing sends the e-mail to the client contact e-mail
address. If there is no client contact e-mail address, Conferencing does not reset
the secret PIN.
8. Save your changes.
You do not have to restart the Apache or Tomcat processes.
Example
For example, you could enter the customer's company name in the e-mail text.

Passcode functionality
Next steps
Now it is a good idea to verify the updates to the e-mail template by resetting a secret PIN and
viewing the text in the e-mail that Conferencing sends.
Resetting a secret PIN

The Reset Secret PIN button is not displayed on the Edit Participant dialog when operators
access the dialog. Only system administrators can reset secret PINs.
Prerequisites
Typically, you reset a secret PIN when a participant contacts you to tell you that they have
forgotten or lost their secret PIN.
The purpose of this task is to prompt the Conferencing server to send an e-mail notification
to a participant containing a Web site link to the PIN Management Web Site to enable the
participant to create new secret PIN.
2. Open the CRS Front End and click the Customer Bookings button.
3. Navigate through the companies and clients to select the client you wish to modify.
4. Click Edit Client and select Participants.
5. On the Participants dialog, click Edit.
6. On the Edit Participants dialog, click Reset Secret PIN.
As a system administrator, you must configure a number of CRS parameters in order to
customize passcode functionality to suit your requirements. In previous releases of
Conferencing, system administrators configured these parameters using an initialization file

called bands.ini and a database table called the System Parameters table in the BSRes2
database. The bands.ini file and the BSRes2 database were on the CRS server. The bands.ini
is in the <installation directory>Avaya/CRS Front End and the BSRes2 database is accessible
using Microsoft SQL Server Management Studio™.
For the current release of Conferencing, the parameters are still accessible in these two
locations on the CRS virtual machine. However, you can now configure these parameters using
The fields relating to passcode functionality are located on the Conferencing Manager interface
Elements > Conferencing > Client Registration > General section.
Related topics:
Auto generated passcode length on page 199
Minimum passcode length on page 199
Maximum passcode length on page 199
Period to conference passcode renewal on page 200
Period of passcode overlap on page 202
Passcodes in use in the Web applications on page 351
Auto generated passcode length

The Auto Generated Passcode Length parameter specifies the length of automatically
generated passcodes.
When operators or moderators book a conference, they can enter their own choice for conferee
and moderator passcodes. The passcode lengths are subject to the Maximum passcode
length and Minimum passcode length parameters, which you can configure using
Alternatively, if the Autocode checkbox on the CRS Front End or the Auto-Generate
Passcodes checkbox in the Web Portal are selected, the CRS automatically generates
passcodes and sets their length according to the value of the Auto Generated Passcode Length
parameter. For example, if the Auto Generated Passcode Length=6, Conferencing generates a
number that is 6 digits long.
Period to conference passcode renewal

The Period to Conference Passcode Renewal parameter specifies the default value for the
time period between automatic pass code refresh cycles.
The Period to Conference Passcode Renewal parameter has a range of 0 to 365. Operators
can modify this time period by entering a new value in the Renew Days field in the New
Company and Edit Company dialogs.

The CRS automatically generates new pass codes for on-demand conferences if the owner
of the demand conference does not change their pass code within a configurable period of
time. The CRS directs the Notifications Subsystem to generate an e-mail notification to inform
the conference owner of their new pass codes. For a configurable period of time, the old pass
codes are still valid. This period gives the conference owner the time to adjust their conference
details. When the overlap period ends, the CRS directs the Notifications Subsystem to
generate an e-mail notification to inform the conference owner that their old pass codes are
no longer valid.
At Company level, operators can configure:
• The time period between automatic pass code refresh cycles.
Operators can modify this time period by entering a new value in the Renew Days field
in the New Company and Edit Company dialogs. The CRS Front End obtains the default
value for the Renew Days field from the Period to Conference Passcode Renewal
parameter in the Company table in the BSRes2 database. The Period to Conference
Passcode Renewal parameter has a range of 0 to 365.
• The time period for which the old pass codes are still valid.
Operators can modify this time period by entering a new value in the Overlap Days field in
the New Company and Edit Company dialogs. The CRS Front End obtains the default
value for this field from the Period of Passcode Overlap parameter in the Company table in
the BSRes2 database. The Period of Passcode Overlap parameter has a range of 0 to 30.
Note:
The CRS performs a check to ensure that the Period to Conference Passcode Renewal
parameter is less than the Period of Passcode Overlap parameter.
You can set the default value to display in the CRS Front End New Company and Edit
Company dialogs by setting the value of the Period of Passcode Overlap and Period to
Conference Passcode Renewal parameters in the Company table in the BSRes2 database.
The Conference table also contains two parameters that enable this functionality.
• PassCodeChangedDT stores the date and time that the pass codes were last changed.
• OverlapStartDT stores the date and time that the overlap period started.
Name Location Description

Period to Conference Company The time period between automatic pass
Passcode Renewal code refresh cycles
Period of Passcode Company The time period for which the old pass codes
Overlap are still valid
PassCodeChangedDT Conference The date and time that the pass codes were
last changed
OverlapStartDT Conference The date and time that the overlap period
started

In order for the overlap aspect of this feature to operate successfully, two demand conferences
co-exist:
• The old on-demand conference with the old pass codes.
• The new on-demand conference with the new pass codes.
These two conference co-exist for the duration of the Period of Passcode Overlap parameter.
Each night, the CRS runs a scheduled task called DoRenewPassCodes. DoRenewPassCodes
performs the following actions:
• Creates a new demand conference where:
PassCodeChangedDT + (Period to Conference Passcode Renewal - Period of Passcode
Overlap) < NOW()
• Generates an e-mail notification for each new demand conference.
• Removes or cancels all demand conferences where:
OverlapStartDT + Period of Passcode Overlap < NOW()
• Generates an e-mail notification for each removed demand conference.
When DoRenewPassCodes creates a new conference, it moves all participants to the new
conference. DoRenewPassCodes also moves the Import Utility identification (ImportID) to the
new conference. The new conference becomes the primary conference. If an operator changes
the old conference during the overlap period, the changes will not be reflected in the new
conference. DoRenewPassCodes only selects on-demand conferences that match the
following criteria:
• Type: Meet-me, unattended, or flex flow
• State: Confirmed, in-progress, completed, billed
The state of a conference influences how DoRenewPassCodes handles it once the overlap
period ends. DoRenewPassCodes removes billed conferences but cancels confirmed, in-
progress, and completed conferences.
You can investigate any problems that occur during the renewal process by examining the
RenewConferencesHistory table in BSRes2. The Conferencing Import Utility application does
not import the Period to Conference Passcode Renewal and Period of Passcode Overlap fields
when you instruct it to import a Company record. This means that imported companies do not
use the passcode expiry feature.
Period of passcode overlap

The Period of Passcode Overlap parameter specifies the default value for the time period for
which the old pass codes are still valid. The Period of Passcode Overlap parameter has a
range of 0 to 30. Operators can modify this time period by entering a new value in the Overlap
Days field in the New Company and Edit Company dialogs.

Maximum passcode length

The Maximum Passcode Length parameter specifies the minimum length of the conference
passcode. The Maximum Passcode Length parameter applies to moderator, conferee, and
co-chairperson passcodes. The default value of Maximum Passcode Length is 16.
Minimum passcode length

The Minimum Passcode Length parameter specifies the minimum length of the conference
passcode. The Minimum Passcode Length parameter applies to moderator, conferee, and co-
chairperson passcodes. The default value of Minimum Passcode Length is 4.
Passcodes in use in the Web applications

Web Portal and passcodes
As a Web Portal system administrator, you can configure the editing rules for the Moderator
and Conferee Passcode fields.
Using the Form Fields screen, you can specify whether Web Portal moderators can enter their
own sequence of numbers for their passcodes when they book conferences. The Form Fields
screen contains the following options:
• Moderator Passcode for Demand Conferences
• Participant Passcode for Demand Conferences
• Moderator Passcode for Scheduled Conferences
• Participant Passcode for Scheduled Conferences
Using these options, you can customize the editing rules to exactly meet your requirements.
The Auto-Generate Passcodes option indicates whether Conferencing generates the
passcodes for conference. If Auto-Generate Passcodes is enabled, Conferencing generates
the conference passcodes. If Auto-Generate Passcodes is not enabled, moderators can
enter their own sequence of numbers for your conference passcodes.
When moderators access the Booking screen, the Auto-Generate Passcodes field is always
enabled. If you choose not to allow moderators to edit the passcode fields, Conferencing
always generates conference passcodes and moderators cannot disable Auto-Generate
Passcodes. Similarly, if you choose not to allow moderators to edit one of the passcode fields,
such as the Participant Passcode field, Conferencing always generates conference
passcodes and moderators cannot disable Auto-Generate Passcodes. If you choose to allow
moderators to edit the passcode fields, moderators can disable Auto-Generate Passcodes.

Passcodes are numeric. You can configure the length of passcodes using the CheckPINSize
parameter in webportal.properties.
If CheckPINSize=1, Conferencing validates the length of the passcodes using the value of
the CRS field, Auto Generated Passcode Length.
If CheckPINSize=0, Conferencing sends any length of passcode to the CRS. However, the
CRS database, BSRes2, may reject the value if it is too long for the database.
Avaya Web Conferencing and passcodes
To enter a data conference hosted by the Avaya Web Conferencing application, participants
must know their moderator or conferee passcode and the conference reference number. For
more information, see the Avaya Web Conferencing Quick Reference Guide, which is available
from support.avaya.com.
Summary
It is easy to get confused between all the terms relating to Conferencing security. There are
many terms and many configurable security features. It is important to be clear about the
various definitions.
A secure conference is a conference in which a moderator can prevent anyone from listening
to or joining the conference. This is also sometimes called a locked or secured conference.
Operators and moderators book a secure conference by selecting the Security checkbox at
booking time. The Security checkbox is only available if a moderator is selected for the
conference. In a secured conference, operators cannot enter, record, scan, or listen to the
conference. Moderators must press *7 on their telephone keypads during the conference to
activate this feature. Moderators hear a tone or voice message to indicate that the conference
is secured or unsecured.
A PIN mode conference is a conference in which participants must enter a PIN code and a
passcode in order to gain access. Operators and moderators book a PIN mode conference by
selecting the Conference or System PIN mode at booking time.
A participant ID identify conference is a conference in which participants must enter an
identifying number and a passcode in order to gain access. Operators and moderators book
a participant ID identify conference by selecting the Identify Participant ID mode at booking
time.
A participant ID identify and validate conference is a conference in which participants must
enter an identifying number, a secret PIN, and a passcode in order to gain access. Operators
and moderators book a participant ID identify and validate conference by selecting the Identify
& Validate Participant ID mode at booking time.
A second level passcode conference is a conference in which participants must enter two
passcodes in order to gain access. Moderators must distribute the second passcode to the
participants by e-mail prior to the conference start time. Operators and moderators book a

Summary
second level passcode conference by selecting the Security Passcode checkbox at booking
time. This only applies to flex flow conferences.


Chapter 23: Configuring LDAP for
Conferencing
The Directory Services Client Application (DSCA)

The Directory Services Client Application (DSCA) ensures that registration details stored on
the Client Registration Server (CRS) are synchronized with registration details stored on the
directory server. Registration data on the CRS is updated using the directory server registration
data.
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 organizations, 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. The following types of directory server can be
integrated with the CRS:
• Microsoft Windows 2003 Service Pack 1 active directory
• Sun Java directory server
The Web Portal can only integrate with the Microsoft Windows 2003 Service Pack 1 active
directory. It cannot integrate with the Sun Java directory server. Only the CRS supports the
Sun Java directory server.
Before you configure LDAP Conferencing integration in your organization, you must have an
active directory installed and configured in your network.
The process of configuring LDAP for Web Portal and CRS clients involves:
• Obtaining a Web Portal certificate from your active directory server.
• Installing the Web Portal certificate in the Web Portal.
• Obtaining a CRS certificate from your active directory server.
• Installing the CRS certificate in the CRS client.
Once you complete these steps, you can verify the LDAP integration in two ways:

Configuring LDAP for Conferencing
• You can check the list of clients in CRS Front End. Every user in your active directory
should have a client account. In addition, if you have configured the creation of an on-
demand conference for each new client, each of your clients should have their own on-
demand conference.
• You can also book a conference with a dial list that obtains the participants from your
active directory server.
Related topics:
User data retrieved on page 363
DSCA demand profile creation on page 364
DSCA and secure sockets layer on page 364
DSCA parameters
This table lists the DSCA parameters. You must configure these parameters to match your
deployment. For example, you must enter the full path name and file name for the CRS SSL
certificate file in the SSLCertificate parameter.
DirectoryServerHost The IP address of the directory server.
DirectoryServerLdapPort The port number (the default value is 389).
UseSSL Specifies whether SSL is in use.
SSL not in use: UseSSL=0
SSL in use: UseSSL=1
The default value is 0.
DirectoryServerLdapSSLPort The SSL port number (the default value is 636).
SSLCertificate Enter the full path name and file name for the SSL
certificate file.
SSLEncodingFileType Enter the SSL encoding file type
For B64: SSLEncodingFileType=1
For DER: SSLEncodingFileType=2
SSLKeystore You only have to configure this parameter if you are using
the Web Portal application in your deployment.
Enter the full path name and file name for the SSL
keystore file.
LoginDN Enter the account name that you created on the directory
server for the DSCA.

For example, cn=CRSAdmin, cn=Users, dc=DSServer,
dc=com.
The DSCA application does not validate this LoginDN. It
just passes it to the directory server.
Password Enter the password for the LoginDN account.
DirectorySearchBase Enter the search location on the customer directory
server.
For example, - ou=department, dc=DSServer1, dc=com,
cn=users, dc=DSServer1, dc=com.
DirectoryUserSchema Enter the user schema. For example, user.
<USERSCHEMA> in the profile will be replaced with the
value of DirectoryUserSchema. The default is user.
DirectorySearchPath Enter the search path from which the users in directory
server will be retrieved by the DSCA application.
DirectoryContext The DSCA uses this parameter to create a default
company name. If there is no value in this parameter, the
DSCA uses the phrase LDAP as the company name.
If your Conferencing deployment includes the Web Portal
application, the Web Portal uses this parameter to
establish a connection to the directory server.
DirectoryBindFormat This parameter relates to the Web Portal application. An
example is <user>@<context>
SecurityPrincipal This parameter relates to the Web Portal application.
SecurityCredentials This parameter relates to the Web Portal application.
DirectoryBindMethod This parameter relates to the Web Portal application.
An example is simple or DIGEST-MD5
CurrentUserFilterFormat This parameter relates to the Web Portal application. An
example is UserPrincipalName=<user>@<context>
CreateDefaultDemandProfile f you set this parameter to true, the DSCA will create an
on-demand profile when it creates a new client account.
The default is CreateDefaultDemandProfile=1.
D.S. N/W timeout (secs) This parameter relates to the DSCA timeout in seconds.
The default is D.S. N/W timeout (secs)=15.
SPCondition1 This is an optional condition that you can use to restrict
the entries that the search returns.
Comment This is a free text field for profile information.
DirectoryServerType This indicates the type of directory server.
For a generic directory server: DirectoryServerType=0
For an active directory server: DirectoryServerType=1

Alternative_DN Normally, the client account in the CRS database
(BSRes2) stores the DN from the directory server. You
can use this parameter to store other information that is
more static to that client.
Client Parameters Map the user entries on the directory server with these
fields on the DSCA. For example:
CLIENT_NAME: cn
CLIENT_MAIN_PHONE: telephoneNumber
CLIENT_MAIN_FAX: facsimileTelephoneNumber
CLIENT_EMAIL: mail
CONTACT_NAME: cn
CONATCT_PHONE: telephoneNumber
CONTACT_FAX: facsimileTelephoneNumber
CONTACT_EMAIL: mail
SECONDARY_CONTACT_PHONE: otherTelephone
MOBILE_CONTACT_PHONE: mobile
IMPORTID: initials
Participant Parameters You must configure these values if your Meeting
Exchange deployment includes the Web Portal
application. For example:
PARTICIPANT_NAME cn
PARTICIPANT_DEF_CONTACT_PHONE:
telephoneNumber
PARTICIPANT_DEF_CONTACT_EMAIL: mail
Search Attributes You must configure these values if your Meeting
Exchange deployment includes the Web Portal
application. For example:
SEARCH_NAME: cn
SEARCH_EMAIL: mail
SEARCH_PHONE: telephoneNumber, homePhone,
mobile
Company This is an optional parameter that the DSCA uses to
create a company. If you would like to place the clients
into different companies, for example, based on their
department, you should map this parameter to the
parameter in the directory server that identifies the
client’s department.
ExternalString This is an optional parameter. The DSCA uses it to import
external data into the client’s ClientExternalString field.
EmployeeUID This is an optional parameter and is used for Participant
ID Mode. The DSCA uses it to import external data into
the client’s participant’s EmployeeID field.
UserAccountControl This parameter identifies the user account control details
for the directory server. For example:
UserAccountControl: UserAccountControl

DisableMask This value, when used with UserAccountControl, will
result in the disabled status of the account. In a non-
Windows directory server environment, you should set
this value to 0.
Setting for Demand Profile Conference Size: Specifies the conference size
Recording On: Indicates whether recording is on or off.
Note:
Recording has to be set to 0 in order to create demand
conferences. Otherwise conferences are not created
and following message is displayed in DSCA logs:
"There are no recording DDIs for this language type
and cabinet combination in the system".
Data On: Indicates the date. The possible values are 1/0.
Entry Tone On: Indicates the type of entry tone. The
possible values are:
System=1
Tone=2
Message=3
Both=4
Leaving Tone On: Indicates the type of leaving tone. The
possible values are:
System=1
Tone=2
Message=3
Both=4
Notification Type: The possible values are:
0 (None)
2 (Email)
4 (SMS)
6 (Email 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
Notification is on or off. The possible values are 1/0.
Disable Non DS Clients When set to 1, the DSCA will disable all CRS clients for
a specific company <DirectoryContext> that were not
returned by the directory server search.
DirectoryPhoneNumbersFiltered When this parameter is enabled, the DSCA removes any
non-numeric characters from the telephone number
fields. Valid characters are '0123456789 +-'.
Disable_On_No_Mand_On When set to 1, the DSCA will disable a user if it their
profile is missing the mandatory fields: ClientName and
ClientPhone.
BinaryAttributes This parameter relates to the Web Portal application.

By default, the DSCA assumes that attributes are in
ASCII format. On the directory server, some attributes
are in binary format.
ProcessIntervaltype This setting along with ProcessIntervalValue will
determine how often synchronization the process is run.
These values represent each type of time slot:
0: Seconds
1: Minutes
2: Hours
3: Days (Default)
ProcessIntervalValue This setting along with ProcessIntervaltype will
determine how often synchronization the process is run.
For example, to run the process every 30 minutes:
ProcessIntervaltype:1
ProcessIntervalValue:30
For example, to run the process once a day:
ProcessIntervaltype:3
ProcessIntervalValue:1
Last Process Date Time This parameter stores last process date/time .
Use_Config_Date_Time When set to 1, the next process will read the Last
Process Date Time from the configuration file instead of
using the Last process date time from the database.
CRSClientPwd This setting is not in the Configuration dialog. It is in the
Options section of the profile.
Use it to enter a default password when a single sign on
password is required. The client should then change their
password when they first log in. For example:
CRSClientPwd=avaya123
Ensure that the UniquePasswordInd field in the system
parameters table is set to 0.
Secure_Conf_Mode This setting is not in the Configuration dialog. It is in the
If secure conferencing is set to off:
Secure_Conf_Mode=0
If secure conferencing is set to identify:
Secure_Conf_Mode=1
If secure conferencing is set to identify and validate:
Secure_Conf_Mode=2
RunOnStartup This setting is not in the Configuration dialog. It is in the
When RunOnStartup=1, the DSCA sets the process
state to running, by default, and the process will
automatically start.

When RunOnStartup=1, the DSCA sets the process
state to stopped, by default, and you will have to
manually start the process.
If your Conferencing deployment includes the BSMon
monitoring application, you should set RunOnStartup=1.
DSStatus This is a feature for non-Windows active directory
servers. It disables the client sychronization associated
with an LDAP attribute. For example:
DSStatus=dsStatus
DSDisabledList This is used with DSStatus. It lists the strings associated
with an inactive user. For example:
DSDisabledList=0, false, inaactive, disabled
It is important to note that in oder to switch from the
original active directory method (UserAccountControl
and DisabledMask=2), you must set the
DisabledMask=0 to enable the DSStatus feature.
Related topics:
Editing parameters on page 361
Single sign on on page 445
Editing parameters
In previous editions of Conferencing, the DSCA consisted of an application with a graphic user
interface (GUI). In the past, administrators used this GUI to configure many aspects of the
operation of the DSCA.
In the current edition of Conferencing, the DSCA is treated like a process or a service. It runs in
the background. Due to security settings in the Windows 2008 operating system, which runs
on the CRS virtual machine, administrators cannot access the DSCA GUI while the BSMon is
running.
If you require access to the DSCA application, you must:
• Stop the BSMon monitoring of the DSCA.
• Stop the DSCA task using the Task Manager.

• Access the DSCA application and perform the tasks that you require.
To configure the DSCA parameters for your deployment, you can either access the DSCA GUI
as described here or you can edit the DSCA.pfl file using an editor such as the Notepad
application.
Prerequisites
Before you configure the DSCA parameters, you must have an active directory installed and
configured in your network.
The purpose of this task is to configure the LDAP settings to match the settings in your
deployment.
1. Access the DSCA interface.

Remember that you must stop the watchdog first, as follows:
a. Stop the BSMon monitoring of the DSCA.
b. Stop the DSCA task using the Task Manager.
c. Access the DSCA application.
2. Configure the DSCA parameters as required.
3. Save your changes and close the application.
4. Restart BSmon.
5. If your deployment includes the Web Portal application and you would like the Web
Portal application to pick up the LDAP integration, you must ensure that the DSCA
pushes the LDAP settings to the Web Portal virtual machine.
b. Navigate to Elements > Conferencing > Web Applications.
Conferencing Manager may display the IP address of the available Web Portal
virtual machine.
c. Select the Web Portal virtual machine if necessary.
d. Click Configure.
e. Select the Directory server: User, password, content option from the Login
Type menu.
The first time you select the Directory server: User, password, content option
in your deployment, the DSCA pushes the DSCA profile to the Web Portal.
Each time you subsequently edit the DSCA parameters, you must initiate this
DSCA push in order to enable the Web Portal to pick up the new updates. You
can do this by selecting another value (such as E-mail address and password)
from the Login Type menu and applying this setting. Once Conferencing

Manager applies this setting, return to the Login Type menu select the
Directory server: User, password, content option and apply this setting. By
freshly selecting the Directory server: User, password, content option, you
prompt the DSCA to resend the DSCA parameters to the Web Portal virtual
machine.
Related topics:
Synchronizing DSCA parameters with Web Portal on page 365
User data retrieved

This table shows the data that is retrieved from the directory server.
User Data LDAP Attribute Names CRS Field Names

Distinguished Name Dn CLIENT_DISTINGUISHEDNAME
Name Cn CLIENT_NAME
Phone Number HomeNumber CLIENT_MAIN_PHONE
TelephoneNumber CLIENT_MAIN_FAX
FacsimileTelephoneNumber CLIENT_CONTACT_MOBILE
Moblie
E-mail Mail CLIENT_EMAIL
User Account Control User AccountControl N/A
Disabled Mask N/A CLIENT_DISABLEDIND
EmployeeUID employeeUID EMPLOYEE_UID
DSStatus dsstatus N/A
To permit brackets as acceptable characters in the Phone Number field, update the Phone
Number Format Type field to 1. You can access the Phone Number Format Type field using
Conferencing Manager by navigating to Elements > Conferencing > Client Registration >
General menu. The default value of the Phone Number Format Type field is 0. When Phone
Number Format Type is 0, brackets are rejected.
• An example of a phone number with brackets: (353) 895623
• An example of a phone number without brackets: 353 8598623
The DSCA has configurable mappings for CRS fields to LDAP attributes, as attributes are not
standard across LDAP schemas. LDAP attributes to query for name, phone number, and e-
mail searches are set in the DSCA properties file. This file is in the same format as the Web
Portal LDAP. It may 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.
DSCA demand profile creation

You can configure Conferencing to create a new on-demand conference for each new client
added to the CRS database. The CRS database is called BSRes2.
Some of the details used to create this demand profile are taken from the DSCA configuration
and other details are taken from the BSDefaults table found in the BSRes2 database.
If you set DefaultEnabledInd to 0 on the BSDefaults table, Conferencing disables the creation
of demand profiles.
DSCA and secure sockets layer

The DSCA communicates with the directory server using SSL. Here are the configuration
settings that apply to SSL.
Configuration Item Description

UseSSL UseSSL=0 indicates that the communication between the
DSCA and the directory server does not use SSL. In this
situation, the DSCA uses the port number in
DirectoryServerLdapPort when communicating with the
directory server.
UseSSL=1 indicates that the communication between the
DSCA and the directory server uses SSL. In this situation,
the DSCA uses the port number in
DirectoryServerLdapSSLPort when communicating with the
directory server.
You can change the value in this parameter to switch
between SSL and non-SSL.
DirectoryServerLdapSSLPort This setting holds the port number to use when connecting
to the directory server when using SSL. The default SSL port
is 636.
SSLCertificate This is the location of the certificate file to use when
connecting using SSL. For example:
C:\avaya\dsca\certificates\DSCA01.cer

Configuration Item Description

This value only applies when using DirectoryServerType=1,
which is openLDAP.
SSLEncodingFileType SSLEncodingFileType=1 indicates that the SSL certificate
is of Base 64 encoded X.509 type.
SSLEncodingFileType=2 indicates that the SSL certificate
is of DER encoded binary X.509 type. This is the default.
Keystore This is the location of the Web Portal keystore.
DSCA and Web Portal

In previous releases of Conferencing, administrators configured the webportal.properties file
in order to set up an LDAP configuration. In the current release, a management servlet on the
CRS virtual machine pushes the DSCA profile from the CRS virtual machine to the Web Portal
virtual machine. Using this mechanism, the LDAP information on the Web Portal virtual
machine is automatically synchronized with the LDAP information on the CRS virtual machine.
You no longer have to configure the webportal.properties file in order to set up an LDAP
configuration.
To ensure that the Web Portal synchronizes with the DSCA:
• Create a DSCA profile in the normal way, by configuring the DSCA parameters to match
your deployment.
• Select the Directory server: User, password, content option from the Login Type field
in the Conferencing Manager menu: Elements > Conferencing > Web Applications.
The Directory server: User, password, content option was called Login Type 9 in
previous releases of Conferencing.
• Save the change.
Now, a management servlet on the CRS virtual machine pushes the DSCA profile from the
CRS virtual machine to the Web Portal virtual machine. The LDAP integration is configured.
Related topics:
Synchronizing DSCA parameters with Web Portal on page 365
Synchronizing DSCA parameters with Web Portal

When you make changes to the DSCA parameters using the DSCA application, you must
ensure that the CRS virtual machine pushes these updates to the Web Portal virtual machine.

Prerequisites
Before you synchronize the DSCA parameters with the Web Portal, you must configure the
DSCA parameters.
The purpose of this task is to ensure the DSCA parameters on the CRS virtual machine are
consistent with the LDAP parameters on the Web Portal virtual machine.
• The first time you select the Directory server: User, password, content option on the
Conferencing Manager menu: Elements > Conferencing > Web Applications, the
DSCA pushes the LDAP parameters to the Web Portal.
• If you make any changes to the DSCA profiles at any point, you must re-initiate this
DSCA push. You can do this as follows:
b. Navigate to Elements > Conferencing > Web Applications.
Conferencing Manager may display the IP address of the available Web Portal
virtual machine.
c. Select the Web Portal virtual machine if necessary.
d. Click Configure.
On the interface, the Directory server: User, password, content option should
already be selected from the Login Type menu.
e. Select the E-mail address and password option from the Login Type menu.
f. Click Save.
g. Click Apply Changes and then Apply Changes again.
h. Navigate back to the Login Type menu and select the Directory server: User,
password, content option
i. Click Save.
j. Click Apply Changes and then Apply Changes again.
The DCSA pushes the newly updated LDAP parameters to the Web Portal.
Related topics:
Editing parameters on page 361
Exporting the certificate for CRS

Exporting a certificate is the term used for the process of obtaining a certificate from an active
directory server.

Exporting the certificate for CRS
Prerequisites
The purpose of this step is to obtain a certificate from an active directory server.
1. Login to the active directory server.

2. Navigate to Start > Programs > Administrative tools > Certificate Authority
tool.
3. In the Certification Authority main screen, navigate to cadsca > Issued
Certificates.
4. Select the certificate in the right hand panel and display the certificate properties.
5. Display the Details tab.
6. Click Copy to File...
The Certificate Authority tool displays the Certificate Export Wizard.
7. On the Welcome screen, click Next.
The Certificate Export Wizard displays the Export File Format dialog.
8. Select the format that you want use for the certificate export and click Next.
Conferencing supports the DER format or the Base-64 format.
The Certificate Export Wizard displays the File to Format dialog.
9. Enter the path and file name of the certificate you want to export and click Next.
The Certificate Export Wizard displays the Completing the Certificate Export
Wizard dialog.
10. Click Finish.
You can now use this exported certificate on the CRS client. You must paste this
certificate in a place where the DSCA application can access it. You must enter the
location at the parameter SSLCertificate. The process of pasting the certificate is
called installing the certificate.
Example
This example shows the steps for the Microsoft active directory. Conferencing also supports
the Sun Java directory server.
Next steps
Now, you can install the certificate and enter the full name and address in the DSCA
configuration setting, SSLCertificate.

Installing the certificate and keystore for CRS

There is no need to perform any complex steps to install the certificate on the CRS virtual
machine. You can simply obtain an SSL certificate and paste it into a location on the CRS
virtual machine. After you copy it to the CRS virtual machine, you can configure the certificate
location in the DSCA parameters file.
Prerequisites
Before you install the certificate for CRS, you must have an active directory installed and
configured in your network. Also, before you install the certificate on the CRS virtual machine,
you must first obtain a certificate from the active directory server. The process of obtaining a
certificate is called exporting the certificate.
The purpose of this task is to make the DSCA aware of the SSL certificate on the CRS virtual
machine.
1. Copy the SSL certificate on to the CRS virtual machine.

You can use the WinSCP application to access the CRS virtual machine and copy
the file. You can download WinSCP from http://winscp.net/eng/download.php.
WinSCP is an application which enables you to securely copy files over a network.
2. Open the DSCA application and navigate to Edit > Configuration.
3. Update the configuration parameters to point to the certificate file.
SSLCertificate is the name of the parameter which stores the certificate filename
and location.
Next steps
Now you can obtain or export a certificate for Web Portal clients. Alternatively, you can book
a conference using the CRS Front End. You can select the LDAP dial list option for the
conference to see if your active directory list is displayed in the participant selection dialog.
Exporting the certificate for Web Portal

Exporting a certificate is the term used for the process of obtaining a certificate from an active
directory server.

Installing the certificate for Web Portal
Prerequisites
The purpose of this step is to obtain a certificate from an active directory server.
You can obtain a certificate from the certification authority. However, the easiest way is to
copy the file that the certification authority creates. The file is in the root directory of the
drive in which you installed the certification authority. For example, C:
\dueng04test.punch.home_shark.crt on the active directory server.
Installing the certificate for Web Portal

Prerequisites
active directory installed and configured in your network. Also, before you install the certificate
on the Web Portal virtual machine, you must first obtain a certificate.
The purpose of this task is to make the DSCA aware of the SSL certificate on the Web Portal
virtual machine.
1. Copy the SSL certificate to the /home/craft directory on the Web Portal virtual
machine.
You can use the WinSCP application to access the Web Portal virtual machine (and
copy the file. You can download WinSCP from http://winscp.net/eng/
download.php. WinSCP is an application which enables you to securely copy files
over a network.
download.html.
3. Start PuTTY.
4. On the PuTTY dialog, enter the IP address of the Web Portal virtual machine and
click Open.
The Web Portal virtual machine should respond with a prompt.
su sroot

7. Run the command:

/opt/Avaya/bin/javaCerts.sh
This command generates a keystore. For example:
/opt/Avaya/bin/javaCerts.sh import test /home/craft/avaya-
lpecku10p.punch.home_shark.crt
In this example, import is the operation and test is the name or alias.
8. Follow the commands to enter a password.
The default password is changeit.
The keystore.jks is generated in /home/sroot.
Example
You can run a number of other commands on the certificate, such as:
/opt/Avaya/bin/javaCerts.sh list test
/opt/Avaya/bin/javaCerts.sh export test export.crt
/opt/Avaya/bin/javaCerts.sh delete test
To delete the certificate from the java key store, you must run this last command on the Web
Portal virtual machine and enter the same password as before (changeit).
Next steps
Now, you can verify your LDAP and Web Portal integration by selecting the Directory server:
User, password, content option from the Login Type field in the Conferencing Manager
menu: Elements > Conferencing > Web Applications. The Directory server: User,
password, content option was called Login Type 9 in previous releases of Conferencing.
If the LDAP and Web Portal integration is successful, communications between the LDAP
server and the Web Portal server are encrypted.
To encrypt communications between the Web Portal server and Web Portal client browsers,
you must enable SSL in the Conferencing Manager menu: Elements > Conferencing > Web
Applications. You must also configure two other fields on the Conferencing Manager called
SSL Certificate and SSL Private Key. This form of encryption uses the Apache HTTPD
method.

Chapter 24: Understanding blast dial
Introduction to blast dial

In a typical blast dial, Conferencing dials an entire list of phone numbers simultaneously. When
potential participants answer the call, an audio message prompts them to press specific digits
on their telephones to join the conference. The blast dial feature uses dial lists to store the
information that it requires. Each entry in the dial list includes a participant name and telephone
number.
There are two flavors, or types of blast dial.
• Conferencing saves the current conference participant list and makes it available for
transfer to the application server. System administrators can transfer this list to a dial list
directory on the application server. Alternatively, system administrators can create their
own dial list and save it to the dial list directory on the application server. Operators using
CRS Front End can link these lists to the conference. This type of dial list is a dial list
on the application server.
• Conferencing also supports the integration of an LDAP list. This type of dial list is called
an LDAP dial list.
With regard to the user experience of blast dial, there are two modes of blast dial. Operators
using CRS Front End can set the blast dial feature to:
• Dial the dial list automatically as soon as a moderator enters the conference.
• Dial the dial list when the moderator presses a DTMF keypad sequence on their
telephone. This sequence is typically *92.
Aside from the blast dial list feature, Conferencing enables moderators to dial out to multiple
participants using another method. Using Web Portal, moderators can add participants to their
personal address book. Using Avaya Audio Console, moderators can dial out to single or
multiple participants from their address book. They can also edit and save their address book
as a .csv file. There is no direct relationship between blast dial lists stored on the application
server and the address book feature. For more information on this feature, see Using Avaya
Aura™ Conferencing Guide, which is available from support.avaya.com.

Understanding blast dial
Configuring blast dial settings

Prerequisites
Before you configure Conferencing for blast dial, you must install Conferencing and configure
the virtual machines in the Conferencing network.
The purpose of this task is to configure a number of settings in relation to blast dial functionality.
These settings apply to both LDAP dial lists and dial lists saved on the application server.

4. Click Configure.
5. On the Audio Conferencing Configuration screen, click Call Routing.
6. Click Dial out to display all the configurable settings.
8. Click Blast dial settings to display all the configurable settings.
10. Click Save.
Next steps
Now you can configure the CRS virtual machine to enable the blast dial feature for LDAP dial
lists or configure the application server for dial lists.
Related topics:

LDAP dial lists
LDAP dial lists

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 organizations, including Microsoft, Novel, Netscape, IBM, Lotus have
pledged support for LDAP.
In simple terms, an LDAP or active directory server is a list of details about members of an
organization in a series of groups. You can choose one of these groups and link it to the
conference. When a moderator initiates the blast dial feature, the Conferencing server calls
these group members.
An application called the Directory Services Client Application (DSCA) ensures that registration
details stored on the Client Registration Server (CRS) are synchronized with registration details
stored on the directory server. Registration data on the CRS is updated using the directory
server registration data.
Related topics:
Configuration of CRS for LDAP on page 373
Configuration of CRS for LDAP

To enable the blast dial feature, you must perform some configuration tasks on the CRS virtual
machine. After you configure CRS settings, operators can see the LDAP lists in the LDAP
Group Search dialog on the CRS Front End. They can select a list and associate it with the
conference.
Related topics:
Configuring the CRS virtual machine for LDAP on page 373
Configuring the CRS virtual machine for LDAP

Operators can link LDAP groups to conferences for the purpose of a blast dial. When operators
book a conference, they can enable the blast dial feature for the conference. If they enable the
blast dial feature, moderators can initiate a blast dial using a DTMF keypad. In this way,
moderators can dial out to large groups of potential participants simultaneously. The blast dial
feature requires a dial list. A dial list is a list of people and their contact details. An LDAP dial
list is a list that uses the directory server to generate the content of the list. For more information
about linking LDAP dial lists to the conference, see Operating Avaya Aura™ Conferencing
Guide, which is available from support.avaya.com.

To configure the CRS virtual machine for LDAP, you must enter values in a CRS database
table called LDAPConfig. The values in this table then populate two stored procedures called
LDAPSearch and LDAPWrite700DialList.
Prerequisites
Before you configure the CRS virtual machine for blast dial and LDAP support, it is a good idea
to configure the blast dial settings.
The purpose of this task is to configure the CRS for LDAP dial list support.
2. Open Microsoft SQL Server Management Studio.
3. Using Microsoft SQL Server Management Studio, navigate to LDAPConfig table in
the BSRes2 database.
4. Enter values in the LDAPConfig parameters.
Column Type Description

ConfigRef A system-generated identification number.
Enabled Boolean By default, this is set to false (0). To enable LDAP,
set it to true (1).
Host Char The IP address of the directory server.
Port Int For normal communications, the port is 389.
For secure sockets layer (SSL) communications,
the port is 636.
LoginDN Char The user distinguished name that we should use to
login to the LDAP server. Use the empty string for
the anonymous bind option.
LoginPassword Char The user password. Use the empty string for the
anonymous bind option.
Base Char The location in the LDAP tree at which our search
will start.
TimeoutSeconds Int The number of seconds to wait for a LDAP
response.

LDAP dial lists
Column Type Description

ObjectGroup Char The objectclass name of a group object. The
objectclass name is what we search for when
looking for CRS groups.
Enter group here.
ObjectPerson Char The objectclass name of a person object. The

objectclass name is what we search for when
looking for CRS people.
Enter user here.
5. Save the values.

6. Restart the Reservation Server (Reserver) application on the CRS virtual machine.
Example
Here is an example configuration:
Enabled= 1
Host= 'localhost'
Port= '389'
LoginDN= 'cn=Directory Manager'
LoginPassword= 'administrator'
TimeoutSeconds= '30'
Base= 'o=ExampleCompany'
ObjectGroup= 'ecmailgroup'
ObjectPerson= 'ecperson'
In the example, the CRS connects to the LDAP server on IP address localhost (127.0.0.1),
port 389, using the login cn=Directory Manager and the password administrator. It
allows 30 seconds for LDAP queries to succeed against that server.
Port 389 is the default LDAP port.
When operators select the LDAP Dial List feature, the CRS connects to the LDAP server
and starts a search at the LDAP location o=ExampleCompany. It searches below that object
for any objects of the type ecmailgroup. It presents the groups found to the CRS Front
End user in the LDAP Group Search dialog.
When the CRS user selects an LDAP group as their dial list, the group members (ecperson
in this example) are located and are written to a dial list file for this conference. This file
resides in the file directory \temp\diallist. This file directory should be accessible to the
bridge. During the conference, when the moderator invokes the blast dial command using

their DTMF keys, the application server, or bridge dials out to all members listed in the dial
list file for this conference.
o represents an organization. ecmailgroup represents Example Company Mail Group.
Next steps
Now it is a good idea to test the blast dial feature by booking a conference and selecting an
LDAP list on the Options dialog in CRS Front End.
Dial lists saved on the application server

Conferencing automatically saves the current conference participant list as the dial list using
the conference reference number as the filename. Conferencing makes this file available for
transfer to a dial list directory on the Conferencing server. To enable this feature, you must
configure a directory on the CRS server and also configure a scheduled job to transfer the
file to the Conferencing server.
Related topics:
Configuring the CRS for application server dial lists on page 376
Configuring the CRS for application server dial lists

System administrators can manually create blast dial lists and place them in a directory on the
application server.
In addition to manually-created blast dial lists, Conferencing generates blast dial lists
automatically. When operators, using CRS Front End, or moderators, using Web Portal, book a
new conference, Conferencing automatically saves the current conference participant list as
the dial list using the conference reference number as the filename. Conferencing makes this
file available for transfer to a dial list directory on the Conferencing server.
Prerequisites
Before you configure the CRS for blast dial, you must install Conferencing and configure the
virtual machines in the Conferencing network.
The purpose of this task is to configure the CRS to handle blast dial lists that are saved in a
directory on the application server. These saved dial lists can be manually created by a system
administrator or automatically created by Conferencing.
1. Create a directory on the CRS server.

Linking a blast dial list to a conference
For example, C:avaya\diallist

2. Update the system parameters table with the path of the directory on the CRS
server.
The system parameters table is in the BSRes2 database and the relevant field is
called diallistdir.
Conferencing save the automatically-generated participant lists to this directory.
3. Configure a scheduled job to transfer the files to the Conferencing application
server, or bridge.
You can use any method for transferring the files, such as FTP or secure file transfer
(WinSCP).
Next steps
Once the scheduled job is up and running, it is a good idea to test the blast dial feature by
booking a conference with a moderator and some participants and selecting a Blast Mode on
the CRS Front End Options dialog. Dial into the conference and press *92 on your telephone
keypad to dial the telephone numbers on the participant list.
When you leave the Dial List field blank at booking time, the CRS automatically populates the
field when you confirm the conference. The CRS automatically creates a dial list that contains
the invited participants and saves it to the C:avaya\diallist directory. The scheduled job
transfers the file to the /usr/dcb/dbase/diallists directory, where the Conferencing
server can access it.
Linking a blast dial list to a conference

Note:
For more information about linking to blast dial lists and booking conferences, see the
Operating Avaya Aura™ Conferencing Guide, which is available from support.avaya.com.
Prerequisites
Before linking a blast dial list to a conference, configure the blast dial settings on the application
server and CRS virtual machines.
The purpose of this task is to verify that the LDAP blast dial function operates successfully.


2. Open CRS Front End > Customer Bookings and book a conference in the normal
way.
3. Verify LDAP dial lists.
a. On the Options dialog, ensure that you select Auto or Manual from the Blast
Mode drop-down list in the Blast Options panel.
When you select Auto or Manual from the Blast Mode drop-down list, the CRS
Front End enables the LDAP Dial List checkbox.
b. Select the LDAP Dial List checkbox.
c. Click the ... button next to the Dial List field.
The CRS Front End displays the LDAP Group Search dialog. If you
d. Select an LDAP group from the list of LDAP groups.
e. Click Select.
The CRS Front End returns to the Options dialog and the Conferencing server
links the LDAP dial list to the conference
4. Verify application server dial lists.
a. When you book the conference, ensure that you select a moderator and some
participants.
When you complete the booking, Conferencing automatically saves the list of
participants as the dial list. Provided you have configured the CRS dial list folder
and the scheduled job, Conferencing should make the dial list available for
transfer to the application server and then transfer it as you have scheduled.
b. Dial into the conference and press *92 to initiate the blast dial.

Chapter 25: Importing companies, clients,
and conferences
Introduction to the Import Utility

The Import Utility application takes content from an existing database and places it into the
Conferencing database. It takes the following content:
• Company details
• Client details
• Demand conference profiles
Avaya has developed the Import Utility to meet the needs of:
• Enterprise Customers - Who want to transfer existing personnel/employee information
into an Avaya database. Appropriate discussions should take place between system
administration staff and Avaya to ensure successful migration of database content.
• Service Providers - Who have recently negotiated a large corporate customer to join its
network. Large corporations typically have employee information available in a variety of
formats suitable for transferal to the new Conferencing system database.
This utility is intended to replace existing customer-specific import utilities, providing a
consistent framework for future development according to customer requirements. Operators
use the CRS Front End to enter company and client data as well as scheduling reservation
based and demand conferences. Inconsistencies may arise if existing CRS data is imported.
When you install Conferencing in your deployment, the Conferencing Manager automatically
installs the Import Utility. Conferencing Manager installs the Import Utility on the CRS virtual
machine. It does not automatically paste a desktop shortcut on the desktop of the CRS virtual
machine. Also, Conferencing Manager does not configure the Import Utility to operate with
BSMon. You must manually configure the Import Utility to operate with BSMon.

Importing companies, clients, and conferences
Import Utility main features

The Import Utility is a wizard within an application. It enables system administrators to populate
the Conferencing database quickly and efficiently with existing data.
Using the import utility you can:
• Import existing company content
• Import existing client content
• Import existing demand profile content
• Customize the structures for company/client/demand content according to customer
needs
• Generate log files with information about the import
• Schedule an import for later or to start immediately
• Generate a report displaying all defined demand profiles
Other features supported include:
• Flexible handling of name fields
• Default values associated with demand profiles
• Auto-generate demand passcode’s provided by the Avaya database, or an external
system
Using the configuration screen, you can define fields to customize the company/client/
demand profile. These settings are then automatically saved within the profile (or .pfl) file within
the Avaya/BSIMPORT/Profiles directory. These settings are then automatically saved to an INI
file. The import proceeds as configured by these ini settings. The ini file (BSimport.ini) is stored
to the default windows directory.
When database content is imported into the target Conferencing BSRes2 database, it is stored
in appropriate tables. Any issues that arise during import will be captured in a log file, accessible
from the import utility application.
When using a multisite conference, you must only select options that are compatible with the
Global calls. This applies to multisite only. In the Standard Edition of Conferencing, multisite
is not supported.

Preparation of data
Preparation of data
Before you import companies, clients, and conferences, you must ensure that your data files
conform to a number of requirements. These design considerations and field conventions are
described here. For more information, contact your Avaya Support Representative.
Related topics:
Database compatibility on page 381
Input files on page 381
Orphan clients on page 382
The logging file on page 382
Attribute fields on page 383
Field types on page 384
Existing records on page 385
Significant fields on page 385
The CRS Front End and duplication of content on page 386
Demand conference profiles on page 388
Database compatibility
Ensure that the target BSRes2 database installed. This is the database on the CRS virtual
machine which holds all the company, client, and conference information.
Input files
Database content comes in the form of input files. These are typically .csv file which can be
opened using Notepad. These must conform to a file format that can be processed by the
Import Utility.
An ini file controls the execution of the import process. While the import wizard defines most
of the importable items, other more general items are only editable within the ini file itself.
The main considerations for constructing the input files include:
• Input files must match the field sequence as specified in the wizard
• Files must be in the location specified in the wizard
• Company & client files must be placed in the same directory
• Company & client files must have different names

Once the input files have been processed (either successful or error notified) by the utility, they
are moved to a back-up directory called Processed. This directory contains each *.bak files
processed. Subsequent iterations of the utility should use new input files.
Orphan clients
The design of the utility supports the import of companies independent from clients at the same
time. However, company content has to be imported before client/demand profiles.
All clients/demand profiles must be assigned to a company.
Any information about client/demand profiles missing a link to a company will not be processed.
Details about such clients can be located in the import log file which records all import errors.
The logging file

Logging file output can be customized to provide information relevant to your specific
requirements. Details about processing errors are captured in the logging file.
In cases of non critical data, the utility can proceed even when presented with inappropriate
information. In this instance, the utility will modify the original input data to conform to particular
rules and continue. A ‘Warning’ with general details of the modified entry, will be captured in
the logging file.
Warnings are only written to the log if the ini file has been configured to capture this content.
For example, if the log setting...
LogLevel=2
...then log errors and warnings will be captured in the log file.
For normal successful processing, the utility can be configured to write such details to the
logging file. Within the ini file, the various configuration items regarding logging are defined.
Directly below are the default log settings, along with explanations for each:
[LogSettings]
MaxLogLines=2000
MaxLogFiles=62
LogSize=100
LogLevel=3
LogDir=c:\Avaya\import

Preparation of data
MaxLogLines This value defines the number of lines in each log file. When this limit is
reached, a new log file is created.
MaxLogFiles This value defines the number of log files that are stored at any time. When
this limit is reached, the oldest log file is deleted.
LogSize Maximum log file size (Kbytes) On reaching this size, the log will start to
rewrite, and the oldest information will be overwritten. [Default = 100KB]
LogLevel Define the level of detail to retain. [Default = 3]
0=No logging active
1=Log errors only
2=Log errors & warnings
3=Log all records – successful or otherwise
LogDir Define the directory location where the log file will be captured.
Attribute fields
The utility is based upon the handling of attribute fields to define the particular item (company,
client or demand profile). These fields are incorporated together by the utility to control how
relevant parameter values are submitted to the Conferencing database.
These fields match the relevant attributes currently supported by the Avaya database system
(irrespective of any import capability). Any fields not defined cannot be stored on the database,
and require database alterations.
• Key fields
• Name fields
• "Skip" fields
Key fields
A basic principle of relational databases is that every row of every table must be uniquely
identified. The attribute field (or combination of attribute fields) that ensures this uniqueness
is called the Key field.
The Import Utility supports the use of two keys giving rise to a composite key field.
Every record type within each input file must have a key field defined for that particular file.
The values of the key field will be placed in the ‘Import_ID’ field within either the company and
client tables, depending on the transaction.
The utility supports two methods of populating the key field:
• Within the wizard, include the ‘Import_ID’ field as one of the required field sequences for
the file input.
• Alternatively, a field can be designated as ‘Key’ within the wizard. In this case, the actual
field (for example the ‘Company_Name’ field will actually be inserted into the database

twice. Once to its original intended attribute (“Company_Name”) and secondly to the
‘Import_ID’ field.
Name fields
The wizard supports two methods of populating name fields within the input data files:
• The name field is populated by a single entry in the input file e.g. “Frank Jones”.
• The name field is populated by two separate entries in the file e.g. “Frank”, “Jones”.
The generic term Name fields covers company contact name; client name; client contact name.
Skip fields
When importing data from an external database, irrelevant fields can often be included. To filter
these out during import, you must identify the “Skip” field as an importable field. Each unwanted
field must be reflected in the Import Utility by a corresponding “Skip” field. To do this continue to
add successive "Skip" fields into the Import Fields section until an account has been made
of all fields.
Field types
The following field type values are supported:
Field Description
String Variable length single byte character string
Numeric 0|1|2|3|4|5|6|7|8|9
Boolean 0|1
The Import Utility only recognizes the following phone/fax numbers 0|1|2|3|4|5|6|7|8|9|,|-|+
Comma (,) denotes extension numbers. These will be placed to the right of the comma. Any
field that includes a comma must be closed using quotation marks.
For example: “1234567,987”. This will be interpreted as extension 987 of main number
1234567.
Within the wizard (general configuration screen), you can select predefined characters to be
stripped and removed from each input. Selecting this option results in the following characters
being removed at import:
Symbol Character Name

“ Double quote
' Single quote
< Less than
> Greater than

Preparation of data
Symbol Character Name

& Ampersand
` Apostrophe
Existing records
In addition to supporting the migration of database content into the Conferencing database,
the Import Utility can also be used to make changes to existing company/client/demand
profiles.
When importing modified data, it is important that all existing data is included. If a field is
missing from the imported content, the corresponding field in the existing table will be deleted.
This is illustrated here:
Company Name Company Address Company e-mail Import ID

Avaya Dublin post@avaya.com S012
The company file ready for import includes the following entry:
[Avaya,London,””, S012]
Existing database content is overwritten by the new entry. The company table within the
database now includes this entry:
Company Name Company Address Company e-mail Import ID

Avaya London S012
Significant fields
When you select fields for importing, a key field must be defined for both company and client
& demand profiles. If the Import ID field is included, it defaults as the Key field.
• Company
• Client
Company
For company-related input files, the following fields also have particular significance:
• Company Name (this must be unique to the system database)
• Company Phone

If the Company does not include a company name, but has a valid company ID, the utility will
generate a unique company name and also return a warning to the user. If the input file does not
contain a company phone, the utility will insert dummy values of 123 for all such cases.
Client
For Client-related input files, the following fields also have particular significance:
• Client Name (this must be unique within the parent company)
• Client Phone
If the client does not include a client name, but has a valid client ID, the utility will generate a
unique client name and also return a warning to the user. If the input file does not contain a
client phone, the utility will insert dummy values of 123 for all such cases.
The CRS Front End and duplication of content

When importing company/client/demand profiles into the Conferencing database:
• Check to ensure it has not already been entered using the CRS Front End. This will
prevent content duplication as well as conflict between duplicate entries.
• Enter Unique Company and Client Names.
It is important to note that if you are using the Import Utility, there are two options. You can
choose to update existing records or you can choose not to update existing records. The
software bases the identification of records on the primary key of the record. If you choose not
to update existing records, and the utility recognizes that the key is in the database already, it
skips the record. If you choose to update existing records, and the utility recognizes that the
key is in the database already, it replaces the content of the import file with the content of the
CRS record.
Related topics:
Conflicting duplicate entries on page 386
Unique company and client names on page 387
Truncation of company and client names on page 387
Conflicting duplicate entries

If you try to import an update to company/client data previously entered manually into the
system, it will fail when:
• An Import ID field has not already been identified
When importing data through the utility, great significance is placed upon the Import_ID
field. If new company/client details are entered manually to the conferencing system the
Import_ID will not be defined.

Preparation of data
If a subsequent import of the same entry with a minor update/change is attempted an

Import_ID is automatically assigned. The import will then fail as a conflict exists between
the imported data and the existing system data.
In this scenario any updates must be applied manually.
• Passcodes are not unique
If the updated data includes passcodes that are not unique the import will fail.
Passcodes must be unique for each subsequent import of data. The import will also
succeed if the Passcode fields are left blank.
Unique company and client names

Also ensure that each company/client name is unique. If this is not the case, each additional
company/client with the same name, when added to the database will include a sequential
appendage. This only occurs if other fields in the company/client entry are unique, such as the
company address. The utility ignores other fields, such as address and telephone number. The
utility recognizes records based on the primary key. CompanyName are ImportID are the only
two factors.
The following example shows what happens if a file contains multiple companies with the same
name. This also applies to duplicate clients within a company.
Company Name Address 1

Duplicate Company New York
Duplicate Company London
Duplicate Company Dublin
After import, this table shows how this data is displayed in the Conferencing database.
Company Name Address 1

Duplicate Company New York
Duplicate Company 1 London
Duplicate Company 2 Dublin
Duplicate details are included in the generated import log file as a ‘warning’.
Truncation of company and client names

If company/client names fail to meet the less than 50 character criteria, they risk losing their
uniqueness. In this case a sequence number (up to 9) is appended as the 50th character.

Only 9 duplicate entries are supported. A tenth entry will be rejected with error details written
to the log file.
Other scenarios could result in unintentional duplicated companies, and so on.
Demand conference profiles

Existing demand conference profiles for clients can be imported into the database. However
this will only work for client information entered using the Import Utility. There are a number of
aspects to be considered before carrying out an import procedure. These include:
• Passcode generation
• Multiple profile indicator
• Provision of default values
• Demand profile output reports
Related topics:
Passcode generation on page 388
Multiple profile indicator on page 388
Provision of default values on page 389
Demand profile output reports on page 389
Passcode generation
With respect to pass code generation, there are a number of methods supported:
• AutoGen passcodes - An operator provides personal details for the profiles. However,
Conferencing is responsible for generating unique passcodes used to access the
conference at any time. Conferencing provides two passcodes, the ModeratorPIN and
the ParticipantPIN.
• Supplied passcodes - Where passcodes are predefined, appropriate fields must be
created to ensure successful import.
If an imported supplied passcode number already exists in the system, the new profile is not
created and details are captured in the log file.
Multiple profile indicator

The Conferencing database supports the ability of an individual user to have multiple demand
profiles. Within the Import Utility ini file, a configurable parameter [MultipleProfiles=0|
1] dictates how the import process handles multiple profiles.

Preparation of data
MP=0 One profile only, new details overwrite
existing profile [default]
MP=1 Allows multiple profiles
MP>1 Invalid value. The default value is returned.
It is not possible to edit individual profiles if multiple profiles are defined. To do so you must
use the CRS Front End to manually alter certain attributes.
If only one demand profile is supported, then use the Import Utility to edit attributes (including
passcodes) assuming the attribute is not the key field.
Provision of default values

If demand profiles to be created are to have defaults values, such as all profiles will have Entry
Tone=On, the Import Utility provides a means whereby the administrator can specify default
values for certain fields. These defaults will apply to any profile within the input file that does
not include values for these fields.
The input file can include a mixture of both full-profile definitions and part-definitions, whereby
the utility will use the default values defined for the non-specified field values.
Demand profile output reports

The Import Utility provides a demand profile report displaying data generated for recent imports
to the Conferencing system database.
This table shows the structure of the demand report.
Company Client Name Conference Conferee Moderator

Reference Passcode Passcode
Number
Acme Inc. John Doe 124881 12345678 87654321
In the ini file, these fields are controlled by the following configuration entry:
ReportSequence=76,102,301,338,339
This can be configured to import a different combination of fields. Field types are denoted by
number which the Avaya database already recognizes. For example, 76 = Company Name.
The BSImport.ini file includes a section called Demand Report. As well as the above entry
the following details are included:

[DemandReport]
ReportSequence=76,102,301,338,339
ReportName=DemandReport.txt
ReportDays=7
ReportSequence This enables you to define the fields that will be imported and the
sequence they will appear in the demand report.
ReportName This enables you to enter the name of the input file that includes the data
to be imported. This file must be present in the same location as other
input files. For example: c:\Avaya\import
ReportDays This enables you to enter the number of days prior to import that the
utility should consider when including demand profiles.
The Import Utility interface

In previous editions of Conferencing, the Import Utility consisted of an application with a graphic
user interface (GUI). In the past, administrators used this GUI to configure many aspects of
the operation of the Import Utility.
In the current edition of Conferencing, the Import Utility is treated like a process or a service.
It runs in the background. Due to security settings in the Windows 2008 operating system,
which runs on the CRS virtual machine, administrators cannot access the Import Utility GUI
while the BSMon is running.
Conferencing Manager is sufficient to ensure that the Import Utility operates as required.
If you require access to the Import Utility application, you must:
• Stop the BSMon monitoring of the Import Utility.
• Stop the Import Utility task (BSImport.exe) using the Task Manager.
• Access the Import Utility application and perform the tasks that you require.

The Import Utility is presented as a wizard. The wizard enables you to exploit the full capability
and options supported, without causing the database any problems. Using the Import Utility
wizard, you can:
• Configure the import to suit your company needs
• Schedule an import
• Start an import immediately
• View the import log file
• View the demand profile report
The Import Utility wizard is accessible on your CRS virtual machine. It is a good idea to place a
shortcut icon on your desktop so that you can conveniently start the wizard.
Within the Avaya Import Utility screen, two view panels and a number of graphic icons are
displayed.
• Import Data - This provides details about company/client data that will be imported. This
view-only information is based on the previous import configuration and can be changed
using the configuration wizard.
• Import Schedule - This provides details about the daily import schedule provided it has
been set in the import configuration screen. Also included is an Import Now button.
Here is a list of the icons on the interface.
Icon Name Description

Shortcut If you paste a desktop shortcut to the Import Utility
application, this is the icon that you will see.
Configuration Wizard Set configurable options specific to your importing

needs.
View Demand Profile View a demand profiles report.

Report
View Log View all details about the previous import procedure.
Exit Import Utility Exit the Import Utility. This will be disabled during
import.
Import Now Start the import process immediately, based on the

current configuration options.
Test Click this button to perform a test on the data to see

if it complies with the rules for importing data.

Note:
Avaya recommends that you do not execute the Import Utility at peak traffic times.
Related topics:
Import Utility fields on page 392
Import Utility fields

When you click the Configuration Wizard button on the Import Utility screen, the Import Utility
Configuration screen is the first screen in the wizard series. Depending on the options you set,
up to three additional screens are displayed:
• The Companies Fields screen
• The Clients Fields screen or the Client and Demand Profiles screen
• The Summary screen
These screens are only displayed if configured to appear.
Here is a description of fields.
Field Description
Import Companies Select this option to inform the Import Utility that company fields
have to be imported into the Conferencing system database. When
it is selected, the Company File name field is enabled.
Import Clients Select this option to inform the Import Utility that client fields have
to be imported into the Conferencing system database. When it is
selected the Client File name and Client Options panel are enabled.
To import demand profile information for each client, the Import
Demand Profiles option must also be selected.
Import Demand The client file can be configured to contain details for conference
Profiles on demand clients or reservation based clients, but not both at the
same time.
Import Path Enter the current directory location for the data file(s) needed for
import. If you are importing more than one input file, they must be
located in the same directory (e.g. c:\Avaya\import).
Company Filename Enter the company file name as it already exists.
Client File name Enter the client file name as it already exists.
Field Separator Within the files, a particular character will separate the individual
fields; the character used should be defined here (separator must
apply to all input files per import sequence).

Field Description
Default null boolean to When this function is enabled any missing boolean data is
false defaulted to false (boolean value=0). This function prevents import
failure due to missing boolean data.
Remove invalid Certain characters displayed in the input file not compatible with
characters (‘‘ <> ` & ’) the Conferencing database can be controlled from here.
Fail on bad data If you select this option, the import process ignores and skips any
bad entry. It moves on to the next entry and continues the import.
Names as a single The Conferencing database recognizes names as a single field.
field First Name and This option is selected by default in the Name Fields panel.
Last Name fields However if the original name fields have two parts (first and last
name) you need to select the First Name and Last Name fields
option. This will result in the two constituent fields being merged
into one field during import.
Disable all client’s not This option when selected will restrict use of the Conferencing
in import file system to only those specified in the data input file.
Note:
The client fields are
only enabled when
you select the
Import Clients
option.
Deny Updating of This option, when selected, will not allow the updating of existing
Existing clients clients.
Scheduling Enables you to define when the Import Utility should execute
(single or daily). You can also initiate the import immediately.
Profile Enables you to create a new client profile. This assists you to save
particular requirements by their name.
Having entered the appropriate information, click Next to proceed and define the field
sequences. These will correspond to input files named in this screen.
• If you select Import Companies, the Import Utility displays the Company Fields.
• If you only select Import Clients, the Import Utility displays the Clients Fields/Client and
Demand Profiles screen
The process for selecting each of the company, client/client and demand profile fields for import
is almost the same.

Using Import Utility

Using Import Utility consists of:
• Selecting fields
• Configuring on-demand conferences
• Finishing the process of import
Related topics:
Selecting fields on page 394
Configuring on demand profiles on page 395
Finishing the import on page 398
Selecting fields
Prerequisites
Before you select fields on the Import Utility, you must install and configure the CRS virtual
machine.
The purpose of this task is to select the pieces of data that you would like to import to the
Conferencing BSRes2 database. The BSRes2 database resides on the CRS virtual machine
and holds all the company, client, and conference data.
1. From the Available Fields panel, select the appropriate field(s).

The Select Import Fields screen displays two panels. Using the arrows you can
select fields to be identified for importing. The Available Fields panel displays every
existing field available in the input file for import. The Import Fields panel displays
each of the available fields that have been selected for import.
2. Click the arrow pointing right.
The field is transferred into the Import Fields panel.
3. From the Import Fields panel, select the appropriate field.
Once all relevant fields have been selected for import, a Key field must also be
selected. If the Import ID field is selected, it automatically defaults as the key field.
4. Click the Key button.

Next steps
Now you can configure on-demand profiles. This feature of the Import Utility enables you to
create an on-demand conference for each new moderator that you create as you import them to
the BSRes2 database.
Configuring on demand profiles

Although, the process for selecting each of the company, client/client and demand profile fields
for import is almost the same, the Client and Demand Profile screen includes default
conference attributes that can be modified. This enables you to set additional attributes that
may not already be available to the demand profiles. If any of these attributes are already
available, they will be selected in the Demand Profile Defaults dialog.
Prerequisites
Before you configure fields on the Import Utility, you must install and configure the CRS virtual
machine.
The purpose of this task is to customize the exact properties of the on-demand conferences
that Import Utility will create for each new moderator.
1. From the Client and Demand Profiles screen, click Defaults.

2. From the Type drop-down list, select an appropriate conference type.
3. Select any additional attributes required for the conference, from the remaining
options.
Field Description
Type You can select from a number of conference types. A
typical on-demand conference is not attended by an
Operator.
Duration The duration should be 1440 minutes so that the
conference is available all day.
Start Time As long as the duration is 1440, the start time does not
matter.
No. Of You can select the conference size.
Participants
Entry Tone You can switch tones on or off. The following options are
Type available:
• Off: The feature is not active.
• System: The Conferencing server uses a pre-
configured default setting.

Field Description
• Tone: The Conferencing server sounds a tone.

• Message: The Conferencing server plays a voice
message.
• Both: The Conferencing server sounds a tone and play a
voice message.
Exit Tone Type You can switch tones on or off. The following options are
available:
• System: The Conferencing server uses a pre-
configured default setting.
message.
voice message.
Music Source You can set the location of the source file for the music that
is played when a Conferee is on hold.
Prompt Set You can set a default language for audio messages.
NRP Mode If you enable Name Record Playback (NRP), the
Conferencing server prompts all participants to call out their
name before they enter the conference. Moderators can
then play a audio roll call of attendees. There are number
of possible values:
• Off: The Name Record Playback option is not enabled.
• Individual: The system plays a recording only to the
individual.
• Conference: The system plays a recording to the
conference.
Moderator You can enable moderator access for the on-demand

conference. A moderator accesses the conference using
the moderator passcode. Moderators can access a number
of conference features that are not available to regular
conferees.
Data You can choose to enable or disable data conferencing in
the on-demand conference that is created
Security If Security is enabled, moderators can lock the on-
demand conference that is created
Auto Extend You can choose to enable Auto Extend Duration by default.
Duration Auto Extend Duration means that the Conferencing server

Field Description
automatically increases the length of a conference. For on-
demand conferences, this option is on.
Auto Extend You can choose to enable Auto Extend Ports by default.
Ports Auto Extend Ports means that the Conferencing server
automatically increases the number of ports allocated to
the on-demand conference if the number of participants
exceeds the number of booked participants.
Disable Operator Recall enables participants to signal to operators
Operator that they require assistance during a conference.
Recall Participants signal to operators by entering a pre-
configured DTMF key sequence, such as *0, on their
telephone keypad. When participants require assistance,
their name is displayed in the Help Requests dialog in the
BridgeTalk application.
You can set a default value for Disable Operator Recall for
all on-demand conferences that the Import Utility creates.
Block Dial Out The Dial Out feature enables moderators to make external
calls during a conference. Moderators can bring new
participants into the conference using this feature. You can
set a default value for Block Dialout for all on-demand
conferences that the Import Utility creates.
If you enable it, the Conferencing server prevents
moderators from dialling out during a conference. If you
disable it, the Conferencing server permits dial out.
Moderator You can choose a default status for Moderator Hang up for
Hangup the on-demand conference. If you enable Moderator Hang
up, the on-demand conference ends when the last
moderator exits.
Toll Free You can choose to enable toll free calling for the on-
demand conference that is created. The Conferencing
server flags toll free conferences in the billing output to
ensure that the service provider is billed and not the
participants.
Global A feature called multisite dynamically links conferences
distributed over bridges located anywhere in the world. A
caller dials into a local bridge, joins the local conference,
and is connected by audio to other local conferences that
make up the global conference.
Note:
In the Standard Edition of Conferencing, multisite is not
supported.

Next steps
Now you can finish the import.
Finishing the import

Once you define all the relevant fields for import, the Import Utility displays a summary screen of
the field sequences defined to use with input fields.
Prerequisites
Before you view the summary screen at the end of an import, you must select the fields and
configure the on-demand profiles.
The purpose of this task is to complete the import of data and view any errors.
1. View the summary screen.

Within the report, internal field numbers are displayed (as the first column for each
field) which is intended for use by Avaya support staff in the event of issues arising
form the import. The bottom pane of the screen displays general information about
the import. When the import process is complete, the Import Utility application
creates logs that list the number of successful and failed bookings. It is important
to note that a single entry in an import file can equate to several conferences if the
conference is a repeating conference.
2. View a log by clicking the View Logs button on the Import Utility dialog.
Example
Here is an example log file:
2009-12-20 17:17:41 [E]: => Failed to add S700 6 to the Database. p_S700_MkConf:
p_schapi_MkConf failed RetCode=61211, There are no conferences in this request.
2009-12-20 17:17:41 [I]: => booking details - Requests=0, Confirmed=0, Failed=0
2009-12-20 17:17:41 [W]: -> Record written to fail-schedule file Line: 6
2009-12-20 17:17:41 [W]: Line 8: RetCode = 10214, ConfirmNum=7, Tel=978-552-6268,
UserName=Anderson, ConfType=2
2009-12-20 17:17:41 [E]: => Failed to add S700 7 to the Database. p_S700_MkConf:
10214, in p_S700_ValidateDateTimeRange: End-Date-Time has already elapsed.

2009-12-20 17:17:41 [W]: -> Record written to fail-schedule file Line: 7 2009-12-20 17:17:13
[I]: => S700 Record 8 has been Processed.
2009-12-20 17:17:13 [I]: S700 import file successfully backed up 2009-12-20 17:17:13 [I]:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2009-12-20 17:17:34 [I]: => Conference import summary 2009-12-20 17:17:34 [I]: => - Import
file : c:\avaya\import\import\xsched.csv
2009-12-20 17:17:34 [I]: => - Processed file : c:\avaya\import\import\Processed\xsched.bak
2009-12-20 17:17:34 [I]: => - Failures file : c:\avaya\import\import\Fail
\schfail-20091220171734
2009-12-20 17:17:34 [I]: => - Record(s) Failed : 2
2009-12-20 17:17:34 [I]: => Total booking details - Requests=139, Confirmed=0, Failed=0
2009-12-20 17:17:34 [I]:
Next steps
Now you can view all the imported data using the CRS Front End. It is a good idea to view it
using CRS Front End so that you can verify the import.


Chapter 26: Importing and exporting
configurations
Introduction to the import and export process

On the Conferencing Manager administrative interface, the Elements > Conferencing >
Services screen enables you to import and export the configuration of all the Conferencing
services. You can use this functionality for a number of purposes:
• Validating a configuration in a test laboratory before applying it to production systems.
• Migrating from Avaya Aura™ Conferencing Manager to Avaya Aura™ System Manager
when additional Avaya Aura™ products have been installed on site.
• Pre-configuring a deployment using Solution Modeller.
The Conferencing Solution Modeller is a tool that enables you to configure all the Conferencing
settings before you install Conferencing in the customer site. The Conferencing Solution
Modeller runs on your own laptop or PC, without the need for the backend Conferencing
hardware. The Conferencing Solution Modeller looks and behaves exactly like the
Conferencing Manager application to enable you to mimic the customer site remotely.
Using Solution Modeller, you can configure all the customer preferences and customizations
in advance of the physical installation of the Conferencing environment in the customer site.
You can save the configuration settings in a file, send this file to the customer site, and upload
the file into the customer network once you arrive at the customer site.
Typically, you use the Import functionality in the Conferencing Manager administration
interface to import the configuration settings from an instance of Solution Modeller to an
instance of Conferencing Manager. If you are upgrading from an instance of Conferencing
Manager to an instance of System Manager, you must also use the Export and Import
functionality. You can also use the Export and Import functionality if you wish to move the
configuration from one instance of Conferencing Manager to another instance of Conferencing
Manager.
Point of clarification: System Manager and Conferencing Manager
System Manager and Conferencing Manager are very similar. Conferencing Manager is a
paired-down version of System Manager. Using Conferencing Manager, you can manage the
components in the Conferencing solution. Using Conferencing Manager, you cannot manage
any other Avaya Aura™ products. Using System Manager, you can manage other Avaya Aura™

Importing and exporting configurations
products, aside from Conferencing. The Conferencing functionality in System Manager and
Conferencing Manager is identical.
System Manager is the integrated management console that you can use to manage all the
Avaya Aura™ products. System Manager runs on a separate physical server from
Conferencing.
Conferencing Manager is a cut-down version of System Manager and is included in the
Standard Edition of Conferencing. Avaya developed Conferencing Manager for customers who
do not have any additional Avaya Aura™ products and require a single server deployment.
Conferencing Manager only supports a single box deployment. If a customer has multiple
Avaya Aura™ products or even multiple instances of Conferencing, they must use System
Manager to manage their Conferencing servers.
The Solution Modeller is a standalone version of Conferencing Manager which you can use to
model a deployment before any Conferencing servers are available.
Related topics:
Exporting the customer model on page 402
Importing the customer model at the customer site on page 403
Exporting the customer model

Prerequisites
Before you export your configuration settings from Conferencing Manager or Solution Modeller,
you must configure the Conferencing settings to suit your current requirements.
The purpose of this task is to export a configuration from Conferencing Manager or Solution
Modeller. You need to export the model to create a file that you can import into the actual
customer deployment at the customer site, using Conferencing Manager. The process of
exporting the model creates a .cfg file from the acsm file.
1. On the Conferencing Manager or Solution Modeller interface, navigate to Elements

> Conferencing > Services and click Export.
2. On the Export screen, click Download.
Conferencing Manager or Solution Modeller creates a file that contains the current
configuration settings, as a configuration file (X.X.X.X._conferencing.cfg).
X.X.X.X is the IP address of the Conferencing Manager or System Manager from
which the configuration was exported. When exporting a configuration from Solution
Modeller, the name typically defaults to either 127.0.0.1_conferencing.cfg or the IP
address of your own laptop or PC.
3. Select Save File.

Introduction to the import and export process
Conferencing Manager or Solution Modeller downloads the file to your laptop or PC.
Example
In advance of an upgrade, you can follow these steps for exporting current settings using
the Conferencing Manager Elements > Conferencing > Services menu. It is a good idea
to export the configuration settings in advance of an upgrade, to ensure that you retain a
copy of all current selections and IP information.
Next steps
You can now send the configuration file to the customer site using any method such as e-
mail, memory key, or DVD.
Importing the customer model at the customer site

Prerequisites
Before you import configuration settings into a customer instance of Conferencing Manager,
you must create the model and export it to a configuration file.
Once you arrive at the customer site, you must install Conferencing in the normal way.
The purpose of this task is to upload a set of saved configuration settings and install them into
the customer site.
1. At the customer site, log in to Conferencing Manager.

machine.
4. Click Configure.
6. Disassociate the CRS from all the other virtual machines:
a. In the Components area, ensure that the Assigned Conferencing Servers
panel is empty.
b. Select None in the Web Conferencing Server list.
c. Ensure that the Assigned Web Application servers panel is empty.

7. Click Save.
10. Click Import.
11. At the Import configuration file field, select a configuration file and click Next.
Conferencing Manager imports the configuration file.
Example
You can use this feature to mimic the customer site while you are in another location, such
as your office. You can configure the customer's settings and then upload the settings file
once you arrive at the customer site.
Additionally, after an upgrade, you can follow these steps for importing any saved settings.
Next steps
Now you can associate the virtual machines that currently contain the dummy IP information
with the actual IP addresses at the customer site.
Related topics:
CRS virtual machine connectivity on page 55
Using Solution Modeller

The Solution Modeller application looks and feels like the Conferencing Manager
administration interface. The menu options and their location on the interface are identical.
Using Solution Modeller, you can create a file with an .acsm extension which is similar to a .cfg
extension. Essentially, an .acsm file is a configuration file that includes some information about
purchasing codes and physical deployment . A .cfg file is a configuration file that does not
include any purchasing codes or physical deployment information. It is the .cfg file that you
export from Conferencing Manager or System Manager.
The customer model that you create and configure using Solution Modeller is an .acsm file,
such as solution.acsm. Using Solution Modeller, you can export the customer model. The
process of exporting the file from Solution Modeller changes the solution.acsm to solution.cfg.
At the customer site, you can use Conferencing Manager to import solution.cfg into the
customer deployment. By exporting the model, you are removing the purchasing codes and
physical deployment information that is not understood by Conferencing Manager or System
Manager.
The typical sequence of tasks is as follows:

Creating your model in Solution Modeller
Step 1 Step 2 Step 3 Step 4

Open the Solution Navigate to Elements When you complete At the customer site,
Modeller > Conferencing and the configuration of install Conferencing.
application. customize the model. you model, navigate Log in to
Navigate to At any time, you can to Elements > Conferencing
Solutions > save your model, load Conferencing > Manager and
Servers > an existing model, or Services to export navigate to Elements
Provision to discard your model. the model. > Conferencing >
create a model. Services to import
the model.
File format: .acsm File format: .acsm File format: .acsm File format: .cfg
to .cfg
By default, Solution Modeller starts with a model which does not contain any servers. Before
you can start to configure this model, you must provision at least one server into the model.
Avaya recommends opening the Solution Modeller using Microsoft Internet Explorer 8 or
Mozilla Firefox 3.6. The Solution Modeller uses Java 1.6.0 update 13 or newer. Also, it is
important to ensure that the CLASSPATH variable is not set on the desktop computer. You can
check the CLASSPATH variable as follows:
1. On your desktop computer, navigate to Start > Settings > Control Panel > System.
2. On the System Properties dialog, click the Advanced tab and click Environment
Variables.
3. Ensure that the variable CLASSPATH does not appear in the user variables or
system variables lists.
4. Click OK twice to close the dialogs.
Note:
Avaya has created the Solution Modeller as a test utility and for importing configurations to
the customer site at installation time. Avaya has not designed the Solution Modeller for
exporting and importing the configurations of Conferencing instances that are live and in a
production environment. The import/export process does not guarantee persistence of the
BSRes2 database. For example, during the process, you may loose any scheduled
conferences. On the Solution Modeller interface, the links for buttons such as the About
dialog, Change Password, and Log-off do not operate in the normal way. Solution Modeller
inherits these values from Conferencing Manager.
Creating your model in Solution Modeller

Typically, you create a model of your customer deployment using Solution Modeller running
on your own laptop or PC. Solution Modeller does not require any hardware. It is a standalone
Java application. Your Avaya Support Representative can send you the Solution Modeller zip

file which contains the Avaya Conferencing Solution Modeller (ACSM) launcher file called
acsm.exe in a folder called bin.
Prerequisites
Before you create your model, you must obtain the Solution Modeller application from your
The purpose of this task is to minimize the time required for configuration activities at the
customer site. By modelling the customer solution in advance, you can provide a far more
efficient services solution.
1. Obtain the Solution Modeller zip file from your Avaya Support Representative.
2. Navigate to \acsm\bin and launch acsm.exe.
3. On the Solution Modeller interface, navigate to Solutions > Servers and click
Provision.
4. Select the type of server.
The Standard Edition of Conferencing supports a single type of server.
Solution Modeller allocates a purchasing code to the server. Solution Modeller also
assigns 'dummy' IP information to the virtual machines that comprise the
Conferencing solution. During the import of the configuration at the customer site,
the import wizard steps through the mapping of the 'dummy' IP addresses to the
real IP addresses of the servers deployed on the customer site.
5. Click Provision.
Solution Modeller provisions the selected server into the model and returns to the
list of servers screen. At this stage, the model contains all the default values that
are present in each new instance of Conferencing.
Next steps
Now you can configure the model to suit the requirements of the customer deployment. At any
point, you can save the model or load an existing model into the Solution Modeller by navigating
to Solutions > Save Model or Solutions > Load Model.
Customizing/Configuring your model

The process of configuring your model refers to the task of changing the default properties of
the Conferencing solution. It is a good idea to conduct a number of customer interviews to illicit
the exact customer requirements in advance. It is also a good idea to deploy the Avaya Aura™
Conferencing Implementation Workbook.

Saving the model
Prerequisites
Before you configure your model, you must either provision at least one server into the model or
load a previous model file as a starting point. The model has the file extension .acsm.
The purpose of configuring your model is to create a file which contains all the Conferencing
properties and configuration settings that the customer requires. You can create this file on
your own laptop or PC, in your own time.
1. On the Solution Modeller interface, navigate to Elements > Conferencing and

configure the various virtual machines that comprise the Conferencing solution.
Many of the configuration tasks are described in these pages.
2. At any point, you can save your model by navigating to Solutions > Save Model.
You can load a saved model into the Solution Modeller by navigating to Solutions >
Load Model.
3. When you are finished with your customization, save the configuration and click
Apply Changes and Apply Changes again to save all the settings.
The Solution Modeller may display a message next to some of the updates to say
that a system restart is required. A system restart is not required. This message
refers to making changes in Conferencing Manager where there are actual
hardware implications.
Your model now exists and has a filename with the extension .acsm.
Next steps
Now you can export your model from Solution Modeller.
Related topics:
Exporting the customer model on page 402
Saving the model

Prerequisites
Before you save your model, you must create it using the Provision button. The model has
the file extension .acsm.
The purpose of saving your model is to store a file which contains all the Conferencing
properties and configuration settings that the customer requires. You can access it again at a
later time.

1. On the Solution Modeller interface, navigate to Solutions > Save Model.

2. Click Save and then Save again.
Solution Modeller displays the Save As dialog.
3. Enter a filename and save the file to a suitable location.
By default, the filename is called solution.acsm.
Example
For example, you can change the filename to a meaningful customer name.
Next steps
Now, you can access this file at any time to make further configuration updates. To access the
file again, you must load it into Solution Modeller.
Loading the model

Prerequisites
Before you load your model, you must create it using the Provision button and save it using
the Save button. The model has the file extension .acsm.
The purpose of loading your model is to open a file that you have previously saved and which
contains all the Conferencing properties and configuration settings that the customer requires.
1. On the Solution Modeller interface, navigate to Solutions > Load Model.

2. At the Solution template to load field, click Browse to select a model that you
have previously saved.
Solution Modeller displays the Choose File dialog.
3. Select a filename with the file extension .acsm.
4. Click Open and then Load.
Solution Modeller loads the model.
Next steps
Now you can update the model using Solution Modeller.

Discarding the model
Discarding the model

Prerequisites
Before you discard your model, you must create it using the Provision button. The model has
the file extension .acsm.
The purpose of discarding your model is to delete a model and all the configuration settings in
that model.
1. On the Solution Modeller interface, navigate to Solutions > Discard.

2. Click Discard to remove the model from Solution Modeller.
Solution Modeller removes the model.
Example
For example, you can discard a model that you have exported from Solution Modeller after
you import the model on the customer site.


Chapter 27: Customizing the Web Portal
application
Web Portal administrator interface

The administrator’s interface enables the administrator to define the available functionality on
the Web Portal. The Web Portal provides the capability to set certain specifications as default,
yet hide them from the interface. For example, the administrator may wish to select Best Fit
for all conferences without displaying it as an option on the conference reservation interface.
The default Web Portal admin URL is:
http://<Web Portal virtual machine IP address>/webportal/admin/login
The Web Portal Administrator Interface provides the administrator with two options.
• Configuring a particular company’s interface.
The administrator can configure a particular company’s display details by entering the
company name or clicking the Find button to browse a list of companies. Web Portal
displays an Edit dialog.
• Applying universal changes to all companies on the database.
The administrator can apply changes in functionality to all companies in the database.
This is done by ticking the global configuration button on the Configuration screen.
The administrator’s interface is divided into four main sections:
• Display
This section controls the links to the administrator’s e-mail address, banner url and online
help. The administrator can also define what format to use for date and time in conference
invitation e-mails as well as the first day of the week in the Web Portal’s pop-up calendar.
• Tabs & Buttons
The Tabs & Buttons section enables the administrator to set what functionality displays
on the Web Portal interface. For example, the administrator can include the recurring
booking options. The administrator can also define what displays in the navigation menu
(the menu displayed on the left hand side of the Web Portal) using this section.
• Form Fields

Customizing the Web Portal application
The Form Fields section enables the administrator to configure whether various booking
fields are displayed or hidden. For example, the administrator can make the Best Fit option
available on the User’s Advanced tab of the Booking Menu section of the Web Portal.
• Default Field Values
The Default Field Values section enables the administrator to set what options are set as
default on the Web Portal interface. The default field values configure the default values
for various fields whether they are displayed or hidden. The administrator can hide
functionality for the User interface, by de-selecting it from the Tabs& Buttons or Form
Fields tab and selecting it on the Default Field Values section.
Note:
Avaya recommends that only one person configures the Web Portal at a time. If there
are multiple simultaneous attempts to configure Web Portal settings, the Web Portal
may become unstable.
Configuring the Web Portal display

Prerequisites
Before you configure the Web Portal display, you must install and configure the Web Portal
virtual machine.
The purpose of this task is to customize the administrator e-mail address. This is the e-mail
address that moderators can send messages to, if they require administrator assistance.
These steps also describe how to customize the location of the moderator online help file and
how to set the Web site which is opened when a moderator clicks the Web Portal banner.
1. Log into the Web Portal administrator interface at: http://<Web Portal virtual
machine IP address>/webportal/admin/login.
The default username is avaya. The default password is avaya.
3. Select Global Configuration.
4. Enter the administrator e-mail address in the Administrator email address field.
5. Enter a Web site address in the Banner url field.

Legal disclaimer
6. Enter the location of the online help in the Help file(s) url field.
7. Click Commit.
Example
For example, you can configure the banner URL to display the customer's Web site.
Next steps
Now you can set up a legal disclaimer page, if required.
Legal disclaimer
As a Web Portal system administrator, you can configure the display of a legal disclaimer
screen. This legal disclaimer screen is displayed when Users log on to the Web Portal. To
progress to the My Schedule screen, Users must click OK on the legal disclaimer screen.
Related topics:
Configuring a legal disclaimer on page 413
Configuring a legal disclaimer

Prerequisites
Before you configure a legal disclaimer, you must install and configure the Web Portal virtual
machine.
The purpose of this task is to activate and customize a legal disclaimer screen.
1. Locate the following file:

opt\webapps\webportal\customisations\default\default\properties
2. To display the legal disclaimer, ensure that the parameter
EntryBannerTextDisplay=true.
3. To hide the legal disclaimer, ensure that the parameter
EntryBannerTextDisplay=false.
4. Log into the Web Portal administrator interface.

7. Click Commence Wizard and edit the text in the Entry Banner Text field.
8. Click Commit.
If you click the Restore button to restore the default values, the Web Portal does
not restore the default legal disclaimer text. The Restore button only restores
properties, not messages.
You can also customize the text by editing the text file directly. The text file is stored
here:
opt\\webapps\webportal\customisations\default\default\i18n\brand
Ensure that you save the file as a UTF8 file. For this reason, it is a good idea to
edit it using Notepad.
Next steps
Now you can configure passcode functionality.
Passcodes
As a Web Portal System Administrator, you can configure the editing rules for the Moderator
and Conferee Passcode fields. Using the Form Fields screen, you can specify whether Users
can enter their own sequence of numbers for their conference passcode.
Auto-generate passcodes field
On the Web Portal Booking Meeting screen, the Auto-Generate Passcodes option indicates
whether Conferencing generates the passcodes for conference. If Auto-Generate Passcodes
is enabled, Conferencing generates the conference passcodes. When Users access the Book
tab on the Book Meeting screen, the Auto-Generate Passcodes option is always enabled. If
you choose not to allow Users to edit the passcode fields, Conferencing will always generate
conference passcodes and Users cannot disable the Auto-Generate Passcodes option.
Similarly, if you choose not to allow Users to edit one of the passcode fields, such as the
Conferee Passcode field for scheduled conferences, Conferencing will always generate
conference passcodes and Users cannot disable the Auto-Generate Passcodes option. If you
choose to allow Users to edit the passcode fields, Users can disable the Auto-Generate
Passcodes option.
Passcode length
Passcodes are numeric. You can configure the length of passcodes using the CheckPINSize
parameter in webportal.properties.
If CheckPINSize=1, Conferencing validates the length of the passcodes using the value of the
Auto Generated Passcode Length parameter. You can configure the Auto Generated
Passcode Length parameter using the Elements > Conferencing > Client Registration >
General menu.

Passcodes
If CheckPINSize=0, Conferencing sends any length of passcode to the CRS. However, the
CRS database, BSRes2, may reject the value if it is too long for the database.
Four options
There are four options available on the Form Fields screen:
• Moderator passcode for Demand Conferences
Select to provide the User with the option of entering their own Moderator passcode for
demand conference access. Users can edit the passcodes associated with their Demand
conference by clicking the Edit button associated with their Demand conference and
displaying the Edit Conference screen.
• Moderator passcode for Scheduled Conferences
Select to provide the User with the option of entering their own Moderator passcode for
scheduled conference access. The Web Portal displays a text box on the User’s Book
Meeting screen. This enables the User to enter their specific Moderator passcode for
scheduled conferences.
• Conferee passcode for Demand Conferences
Select to provide the User with the option of entering their own Conferee passcode for
demand conference access. Users can edit the passcodes associated with their Demand
conference by clicking the Edit button associated with their Demand conference and
displaying the Edit Conference screen.
• Conferee passcode for Scheduled Conferences
Select to provide the User with the option of entering their own Conferee passcode for
scheduled conferences. The Web Portal displays a text box on the User’s Book Meeting
screen. This enables the User to enter their specific Conferee passcode for scheduled
conferences.
Related topics:
Configuring Web Portal passcodes on page 415
Configuring Web Portal passcodes

Prerequisites
Before you configure the Web Portal display, you must install and configure the Web Portal
virtual machine.
The purpose of this task is to enable editable passcode functionality.

2. Navigate to Configuration > Form Fields.

3. Select from the four options as required.

4. Click Commit.
The Web Portal displays the selected passcode options on the moderator’s Book
Meeting screen for Scheduled conferences and on the Edit Conference screen for
Demand conferences. It is important to note that moderator cannot book Demand
conferences but can edit the passcodes associated with their Demand conference
via the Edit Conference screen.
Next steps
Now you can configure secure conferencing.
Configuring participant ID identify and validate

conferencing
Prerequisites
Before you configure participant ID identify and validate conferencing for Web Portal, you must
you must install and configure the Web Portal virtual machine.
The purpose of this task is to enable the secret PIN functionality for participants. Once you
enable the secret PIN functionality, operators and moderators can book conferences that
require a secret PIN for access and moderators can access the PIN Management Web site.

machine.
4. Click Configure.
General > User Settings.
6. In the URL To Reset Participant Secret PIN field, enter the following address:
http://<Web Portal virtual machine IP address>/part-pin-webapp/faces/pages/login-
frontend.xhtml?participantRef=<ref>

Time and date formats
7. Click Save.
8. If your deployment includes either of these plug-ins:
• Conference Scheduler Plug-in for Microsoft Outlook
• Conference Scheduler Plug-in for IBM Lotus Notes
You must enter the Microsoft Exchange server address or the IBM Domino server
address here:
WebPortal HOME\webapps\part-pin-webapp\WEB-INF\web.xml, parameter
<param-name>MailServer</param-name>
Next steps
Now you can set the time and date formats.
Time and date formats

Time and date formats enables the administrator to set the way that time and date displays on
the Web Portal interface, and in Conference Invitations. Months are displayed as a string of
letters. For example, July is “Jul” in the MMM setting.
There are a number of options:
Option Description
MMMMM dd yyyy Month (5 characters), Date (2 characters), Year (4 characters)
dd MMMMM yyyy Date (2 characters), Month (5 characters), Year (4 characters)
hh:mm aa Hour: Minute (am/pm)
HH:mm Hour: Minute (24 hour)
dd:MMM:hh:mm:a Date (two characters): Month (three characters): Hour: Minute
(am/pm)
MMM:dd:hh:mm:a Month (three characters): Date (two characters):Hour:Minute
(am/pm)
dd:MMM:yy Date (two characters): Month (three characters): Year (two
characters)
MMM:dd:yy Month (three characters): Date (two characters): Year (two
characters)
Time Format 12= 12 hour clock (am/pm) 24= 24 hour clock
EEEEE:MMMMM:dd:yyyy Day of week (five characters): Month (five characters): date
(two characters): year (four characters)
This applies to Self Registration display only.

Option Description
EEEEE:dd:MMMMM:yyyy Day of week (five characters):date (two characters): Month (five
characters): year (four characters)
This applies to Self Registration display only.
EEEE:dd:MMMM Day of week (four characters):date (two characters): Month
(four characters)
EEEE:MMMM:dd Day of week (four characters):Month (four characters): date
(two characters)
EEE:dd:MMM Day of week (three characters): Date (two characters): Month
(three characters)
EEE:MMM:dd Day of week (three characters): Month (three characters): Date
(two characters)
Related topics:
Setting time and date on page 418
Setting time and date

Prerequisites
Before you set the time and date for Web Portal, you must install and configure the Web Portal
virtual machine.
The purpose of this task is to set the invitation date and time. You can also set the self
registration date format using these steps.

4. Click Commence Wizard.
5. Edit the fields as required:
• Select your preferred date format from the Invitation Date Format drop down
list.
• Select your preferred time format from the Invitation Time Format drop down
list.
• Select your preferred date format from the Self Registration date format drop
down list.
6. Click Commit.

Configuring booking options
The formats are saved.
Next steps
Now you can customize some of the other features on the Web Portal application, such as the
booking options.
Configuring booking options

Prerequisites
Before you set the booking options for Web Portal, you must install and configure the Web
Portal virtual machine.
The purpose of this task is to configure which booking options are available to moderators on
the Booking section of the Web Portal. As an administrator, you can precisely specify which
options are visible and available for moderators.

5. Click Tabs & Buttons and select your preferred options from the Scheduling Items
section.
Option Description
Notification Options Select to enable the conference notification options.
Recording List Select to enable the recording options.
Recurring Options Select to enable the recurring booking options.
Advanced Options Select to enable the advanced booking options.
Schedule search Select to enable the schedule search. Users can
option now search for conference details using criteria
such as date/ time, conference reference number
etc.
6. Click Commit.

Next steps
Now you can customize some of the other features on the Web Portal application, such as
setting the navigation menu.
Setting the navigation pane

Prerequisites
Before you set the navigation pane for Web Portal, you must install and configure the Web
The purpose of this task is to configure which options are available to moderators on the left
hand side of the Web Portal interface. As an administrator, you can precisely specify which
options are visible and available for moderators.

5. Click Tabs & Buttons and select your preferred options from the Navigation section.
Option Description
Schedule Menu Select to enable the schedule menu. Moderators can
Option view their conference schedule or search for other
scheduled conferences. Moderators can access the
Avaya Audio Console from the console button in the
conference My Schedule list.
Booking Menu Select to enable the booking menu. Moderators can
Option reserve conferences, set recurring bookings and
specify conference recording details using this tab.
Onboard Select to enable the Participant’s option. Moderators
Participant’s can add, delete or edit participants from their Web
Option Portal address book.
Onboard Account Select to enable the edit one’s own account option.
Option Moderators can change their passwords, view
recorded conferences and create Web Portal usage
reports.
Onboard Help Select to provide moderators with the opportunity to
Option access the online help.
6. Click Commit.

Configuration of access to functionality
Next steps
advanced booking options.

As an administrator, you can disable or enable Web Portal functionality. The available
functionality with the Web Portal is listed here. This flexibility means that you can selectively
restrict how many features that moderators can access.
• Disabling/enabling conference booking options
• Disabling/enabling notification options
• Configuring attachment functionality
• Disabling/enabling recurring conference options
Related topics:
Disabling/enabling conference booking options on page 421
Disabling/enabling notification options on page 427
Disabling/enabling recurring conference options on page 429
Disabling/enabling conference booking options

Prerequisites
Before you disable or enable conference booking options for Web Portal, you must install and
configure the Web Portal virtual machine.
The purpose of this task is to hide features from moderators. Conversely, you can also enable
other features to exactly match your requirements. As an administrator, you can set what
booking options are available on the Web Portal interface using the Form Fields tab. The
selected options are then displayed on the Advanced tab of the Book Meeting section of the
Web Portal. You can also set the default values used for each field on the Default Field Values
tab. The default value is used even if the field is hidden.



5. Select Form Fields and select the options that you would like moderators to be able
to access.
Option Description
Moderater Moderators can select whether they want a moderator to
attend the conference or not.
Cost Center For accounting purposes, cost codes (cost centers) can
be associated with a conference reservation. The
available cost centers are:
• User Code (UC): The end User’s identifing number.
• International calling card (ICC): A code for an
external telecoms provider. When you create a client,
you can specify an ICC.
• Account Reference (AR): The client’s account
number.
• Dial number (DN): The telephone number of the caller.
• Calling line identifier (CLI): The redirecting number
information for the caller.
• External string (ES): A free text field which can
resolve to an external database. When you create a
client, you can specify an ES.
The Cost Center field cannot be empty. It can contain
up to 20 characters.
The Web Portal obtains the default value for the Cost
Center field from the PaymentType field in
UserBooking.properties. Typically, this value is
AR.
If you change the PaymentType field from AR to either
ICC or ES and there is no ICC or ES associated with that
client, moderators see an error message when they
attempt to book a conference. You can add an ICC and
ES when you create a client. You can also edit an existing
client to add an ICC or ES.
If the PaymentType field is either ICC or ES, it cannot
be edited by moderators or wholesaler User roles. CRS
operator assistance is required.
If you change the PaymentType field to CLI, moderators
cannot edit Cost Center field. If the Cost Center field has
any other value, other than CLI, moderators can edit it.
If moderators edit the Cost Center field, the payment type
field in the conference billing report changes to UC.
Wholesalers can select a payment type when they book
a conference on behalf of their client. In the case of
wholesaler bookings, the Cost Center field defaults to the

Option Description
value of Payment Type field in
UserBooking.properties.
Best Fit If enabled, the best fit feature ensures that if the
necessary conference resources are not available at the
specified conference time, and alternative time and
resource combination is offered.
Attended If enabled here and chosen by a moderator, the
conference is flagged as an operator conference. An
operator monitors the call and can greet participants.
Typically, the Bridge Talk application supports attended
operators. The Standard Edition of Conferencing does
not support the Bridge Talk application. However, in the
Standard Edition of Conferencing, you can enable
attended operators if you configure an alternative
application using the ACP API.
Moderator Hang If enabled, the conference closes once the moderator
Up hangs up or leaves.
Allow Enabling conference lock permits the moderator to lock
Conference Lock the conference. No further participants are allowed into
the conference once it is locked.
Conference This option defines the length of time that the conference
passcode passcode is available.
Duration
Pin Mode A PIN code is an identification number that is unique to
each participant. The name of the participant and their
unique identification number are stored in a PIN list.
When moderators using the Web Portal, create a new
participant, the CRS generates a PIN code for each new
participant. The PINs and the name of the Participant are
stored in a database table.
As a Web Portal system administrator, you can choose
to display a set of PIN Mode options to moderators. Using
these PIN Mode options, moderators can force
participants to enter a passcode and their PIN code in
order to access their conference.
There are three PIN Mode options:
• If a moderator selects Off, Conferencing does not use
PIN codes for the conference reservation.
• If a moderator selects System, Conferencing grants
conference access to a participant if they enter the
correct passcode and a PIN code which matches any
entry in the system’s PIN list, which is stored in a
database table on the bridge. The CRS creates this
PIN list automatically. When a moderator adds new
participants to their own address book, the CRS

Option Description
allocates a PIN to each new participant. Conferencing

stores the PIN in a system-generated PIN list.
• If a moderator selects Conference, the CRS assigns a
dynamically-created PIN list to the conference. The
CRS dynamically creates a PIN list for each
conference. This PIN list contains only the invitees for
that particular conference. Conferencing grants
conference access to participants if they enter the
correct passcode and a PIN code which matches any
entry in this PIN list.
Billing Code This option prompts the moderator to enter a billing code
Prompt when they access the conference.
PIN List If moderators select the Conference PIN Mode option,
the CRS assigns a dynamically-created PIN list to the
conference. The CRS dynamically creates a PIN list for
each conference. This PIN list contains only the invitees
for that particular conference. Conferencing grants
conference access to participants if they enter the correct
passcode and a PIN code which matches any entry in
this dynamically-created PIN list.
In the Conferencing environment, there are main two
sources of PIN lists.
• As a system administrator, you can create and load PIN
lists into Meeting Exchange.
• Alternatively, the CRS dynamically creates a PIN list
for each conference. This PIN list contains only the
invitees for that particular conference. If moderators
specify Conference PIN as their PIN Mode, they can
restrict conference entry to the invitees only. The CRS
names this PIN list using this naming convention:
cl_conference reference.txt. So, if the
conference reference is 123456, the PIN list is
cl_123456.txt.
On the Web Portal, moderators cannot edit the PIN List
field. The CRS automatically assigns the
cl_conference reference.txt value to the
conference. It is a good idea to provide moderators with
the Using Avaya Aura™ Conferencing Guide, which is
available from support.avaya.com. This guide describes
the PIN mode and PIN lists to moderators.
Name Record This option prompts the participants to enter their name
Playback when they dial into the conference.
Enter Tone Entry tones can be enabled and disabled on a per
conference basis.

Option Description
Leaving Tone Leaving tones can be enabled and disabled on a per
conference basis.
Music Source Moderators can set the location of the source file for the
music that is played when a Conferee is on hold.
Auto Increase Moderators can automatically increase the number of
Participants reserved participants during a live conference.
Auto Extend Moderators can automatically extend the reserved
Duration duration of a live conference.
Biometric Biometric authentication is a feature which uses voice
Authentication recognition software to verify the identity of Participants.
For Conferencing, the biometric authentication feature is
still in development. Avaya recommends that you do not
display this field to moderators.
Dial List If enabled here, a moderator can enter the filename of a
dial list in the Dial List field. A dial list is a list of contact
names and telephone numbers that moderators can
associate with the conference. They can prompt the
Conferencing server to dial all the numbers in this list. It
is important to note that you must create the dial list file
beforehand, if you intend to enable the Dial List field for
moderators. You can create dial lists using any text
editor. No file extension is required. However, the format
for the files must follow a specific pattern. It is particularly
important that the file name does not contain any spaces.
Dial lists are stored on the bridge in /usr/dcb/
dbase/diallists. Typically, operators generate
them or upload them using Bridge Talk. It is a good idea
to provide moderators with the Operating Avaya Aura™
Conferencing Guide, which is available from
support.avaya.com. This guide describes Bridge Talk
and CRS Front End to operators.
Note:
The Standard Edition of Conferencing does not
support the Bridge Talk application.
Mute All If enabled here, moderators can select the Mute All
checkbox to place all conferees in the mute status when
they join the conference. Moderators retain full listen and
talk privileges.
Auto Record If you enable moderators to see this checkbox, they can
select this option to ensure that Conferencing
automatically records the conference as soon as it
begins.
It is important to note that CRS operators and Web Portal
wholesalers can also configure Recording Mode at

Option Description
company-level. The settings that operators and
wholesalers configure override the settings that you
configure on this screen for moderators.
As an aside: To successfully enable the recording
feature, you must also configure the recording settings
using Conferencing Manager. Specifically, you must
enable Digital conference record playback in
Elements > Conferencing > Audio Conferencing >
Conference Features.
Control If you enable moderators to see this checkbox, they can
Recording select this option to enable them, or any participant with
moderator status, to record the conference if they wish.
To start recording, they can press the DTMF keypad
sequence, *2 at any time during the live conference. It
is important to note that CRS operators and Web Portal
wholesalers can also configure Recording Mode at
company-level. The settings that operators and
wholesalers configure override the settings that you
configure on this screen for moderators.
Participant ID You can select this checkbox to enable moderators to
Mode view the Participant ID checkbox on their Advanced
Booking Options screen.
Mandatory Bill If you enable this feature, moderators can view the
Code Mandatory Bill Code checkbox on their Advanced
Booking Options screen. If they select this checkbox,
moderators must enter a valid billing code on their
telephone keypad before they join their conference.
Using this feature, you can ensure that moderators
cannot access the conference usless they have a valid
billing code.
Client password This option controls the password field on the my account
tab.
Editable My- This option enables moderators to edit client account
Account details such as timezone.
Information
Participant If enabled here, the Preferred Notification Language
Language field is displayed on the Participant Self Registration
screen. Participants who are self registering, can select
which language they would prefer for their notification e-
mails.
Simultaneous Enables the moderator to reserve a data conference. For
Data Conference more information on data conferences, see the Avaya
Web Conferencing Quick Reference Guide, which is
available from support.avaya.com. This displays as a
standard booking option. If you are using Adobe

Option Description
Connect, this option also enables the user to reserve a
data conference. For more information on data
conferences, see the Adobe Connect User Guide. This
displays as a standard booking option.
Advertise Advertised conferences are conferences whose access
Conference details are displayed on the Web Portal. Web Portal
moderators with a valid account and company name can
view the list of advertised conferences associated with
their company. Advertising means that anyone, using an
appropriate account and company name, can view the
starting time and entry codes associated with
conferences. This option is hidden by default and is a
standard booking option.
6. Click Commit.
Next steps
notification options.
Disabling/enabling notification options

Prerequisites
Before you disable or enable notification options for Web Portal, you must install and configure
the Web Portal virtual machine.
The purpose of this task is to configure the notification options which are available to
moderators. As a system administrator, you can define the notification settings for two separate
areas. You can configure the display of the E-mail invitations and Outlook Calendar area of
the ‘Reservation Created Successfully’ screen You can also configure which notification
options are selected as default from the Notification tab. The Notification tab displays when
the User is editing an existing reservation.
To configure the notification options, you must navigate to the Tabs & Buttons section and the
Default Field Values tab on the Web Portal administrator interface.



5. Select Tabs and Buttons and select the options that you would like moderators to
be able to access. For example,
• Select Invite conferees with email client to enable moderators to invite
conferees using an e-mail client. For example, Microsoft Outlook.
• Select Invite conferees with browser email to enable moderators to invite
conferees by copying the text into a browser e-mail service. For example,
Hotmail.
• Select Invite moderator using calendar to enable moderators to invite
another moderator using their e-mail client calendar.
6. Select Default Field Values and scroll down until the Notification Defaults are
displayed.
7. Select the required notification method and notification types.
Option Description
Notification Select to enable the notification functionality.
Comments Select to allow the moderators to enter a short
comment with the e-mail conference notifications.
Contact Choice Select to enable the moderators to choose to send
notifications by e-mail or fax.
Notify Attendance Sends a participant report to the moderator after the
conference has taken place.
Notify Sends a reservation confirmation to the moderator to
Confirmations confirm that the conference has been booked. Also
sends invitations to the conference participants.
Notify Cancellations Sends a notification to participants if the conference
is cancelled.
Notify Changes Sends a mail to participants if any changes are made
to the conference reservation.
Notify Reminder Sends a reminder to participants before the
conference is due to take place.
8. Click Commit.
Next steps
attachment functionality.

Disabling/enabling recurring conference options

Prerequisites
Before you configure recurring conference options for Web Portal, you must install and
The purpose of this task is to configure recurring conference options.

5. Select Tabs and Buttons.
6. Select Recurring Options from the scheduling items sections.
Option Description
Recurring Select to enable recurring conference functionality.
Conference
Total Conference Enables moderators to set how many occurrences of
Count the booking they require.
Frequency Enables moderators to set the frequency of the
booking. E.g. Weekly, Daily, Monthly.
Day of week Enables moderators to set the day of the week that
the booking occurs. Applies to daily setting only.
Week in Month Enables moderators to set which week in the month
the booking occurs. Applies to monthly frequency
setting only.
Exclude Monday Enables moderators to set a daily booking, excluding
Mondays.
Exclude Tuesday Enables moderators to set a daily booking, excluding
Tuesdays.
Exclude Wednesday Enables moderators to set a daily booking excluding
Wednesdays.
Exclude Thursday Enables moderators to set a daily booking excluding
Thursdays.
Exclude Friday Enables moderators to set a daily booking excluding
Fridays.

Option Description
Exclude Saturday Enables moderators to set a daily booking excluding
Saturdays.
Excluding Sunday Enables moderators to set a daily booking excluding
Sundays.
7. Select Default Field Values and scroll down until the recurring functions are
displayed.
8. Select Recurring Conference.
9. Select the options that you want to set as default on the Web Portal interface.
This means that these options are automatically selected on the Web Portal
moderators interface.
10. Click Commit.
Next steps
recording options.
Recording
To successfully enable the recording feature, you must also configure the recording setting in
the Conferencing Manager menu: Elements > Conferencing > Audio Conferencing >
General Config.
In addition, there are a number of other considerations with regard to conference recording:
• As a system administrator, you can configure recording at moderator, or client, level.
• Moderators can configure recording at conference level.
From the company level downwards, the settings at each level determine the options available
at the following level. You can configure these settings using the CRS Front End. For more
information about the CRS Front End, see the Operating Avaya Aura™ Conferencing Guide,
which is available from support.avaya.com.
• If wholesalers select Mandatory from the Recording Mode drop-down list at company
level, Conferencing automatically records all conferences for that company. Also,
Conferencing selects the Auto Record check box and makes it inaccessible at
conference level to ensure that it is always on for that company. As with many booking
options, Web Portal system administrators can set a default value for Auto Record. They
can also choose to display the Auto Record checkbox or hide it. If wholesalers select

Recording
Mandatory from the Recording Mode drop-down list at company level, system
administrator settings have no impact.
• If wholesalers select DTMF-Menu, Conferencing enables moderators to choose to record
their conferences if they wish. To start recording, they press the DTMF keypad sequence,
*2. Also, Conferencing selects the Control Recording check box and makes it
inaccessible at conference level to ensure that it is always on for that company. As with
many booking options, Web Portal system administrators can set a default value for
Control Recording. They can also choose to display the Control Recording checkbox
or hide it. If wholesalers select DTMF-Menu from the Recording Mode drop-down list at
company level, system administrator settings have no impact.
• If wholesalers select Conference, Conferencing enables moderators to choose between
automatic recording (Auto Record) and manual recording (Control Record) on a per-
conference basis. If wholesalers select Conference from the Recording Mode drop-
down list at company level, system administrator settings do have an impact. If system
administrators enable Auto Record and hide the checkbox, Conferencing automatically
records all conferences for that company. If system administrators enable Control
Recording and hide the checkbox, Conferencing enables moderators to choose to record
their conferences if they wish.

Hiding functionality
Administrators can hide functionality from moderator’s Web Portal interface. For example, the
administrator can have the Best Fit value set to on and the form field set to off. Best fit is then
always configured on and moderators cannot change it since it is not presented to them on
the advanced tab.
Prerequisites
Before you hide functionality for Web Portal, you must you must install and configure the Web
The purpose of this task is to hide or disable functionality from moderators.

Web Portal look and feel

5. Click Tabs & Buttons/Form Fields and select or deselect your preferred options.
6. Select Default Field Values and select the relevant function.
7. Click Commit.
The function/menu is hidden from the User interface but is still set as default during
conference reservation.
8. Relaunch the browser and log into the Web Portal as a moderator to view the
updates. Wait 30/60 seconds as the Web Portal takes this length of time to
recognize the updates configurations. No restart of the Tomcat service is required.
Example
For example, if you do not have Avaya Web Conferencing installed in your deployment, you
may wish to disable and hide the Simultaneous Data Conference option from moderators.
Next steps
cascading style sheet (CSS).

As an administrator, you can customize the appearance of the Web Portal. This allows you to
configure the Web Portal interface to a particular companies specifications. Customization is
performed by editing the Cascading Style Sheet (CSS). The CSS is divided into a series of
classes which impact different parts of the interface.
Before you start:
• Copy the default CSS to a location on your hard drive.
• Rename the CSS before you commence editing it.
• Ensure that you have registered the company that you are branding on the CRS.
• Ensure that you have the list of the different classes and their explanation.

Ensure that you have enter the Web Portal admin URL. This is your Web Portal URL with /
admin/login added.
Related topics:
Uploading files on page 434
Uploading graphics on page 435
Deleting customizations on page 437
Searching for customizations on page 437
Uploading files
Prerequisites
Before you customize the Web Portal look and feel, you must install and configure the Web
Portal virtual machine. Before you upload a customized CSS, you must download the CSS
and edit a copy of it.
The purpose of this task is to upload previously saved cascading style sheets. This enables
you to configure the Web Portal’s interface appearance.
1. Click Upload. It is necessary to upload all nine files before completing uploading.
The Avaya Audio Console customization screens display.
There are two Avaya Audio Console customization screens. The first screen
enables you to customize the Avaya Audio Console toolbar. The second screen
enables you to customize the Avaya Audio Console participant states. If you do not
want to customize the Avaya Audio Console, you can click Skip to proceed to the
final step in the customization of the Web Portal. The Skip button is at the bottom
of the screen
The final screen in the branding process displays.
2. Select Create Branding Now.
The Branding created screen is displayed. The File is uploaded and the Web Portal
interface changes to reflect the new specifications. If the company name contains
a special character, such as Company$a, the Web Portal creates a branding alias
called Companya.
3. Save a copy of the default CSS to a location on your hard drive, rename it, then edit
it.
4. Navigate to Branding > Web Portal Branding.
5. Select the applicable company name by click the Company Search icon.
6. Select the Company and click Start Branding Wizard.
7. Click Browse in the Full Path to branded CSS section.

8. Select the file and click Open.

of the screen
called Companya.
Next steps
Now you can customize other aspects of the Web Portal interface, such as the graphics.
Uploading graphics
Prerequisites
Before you customize the Web Portal look and feel, you must install and configure the Web
The purpose of this task is to exchange the default Web Portal logos with different logos.

2. Select the applicable company name by click the Company Search icon.
3. Select the Company and click Start Branding Wizard.
4. Click Browse in the Full Path to branded image logo file section.
5. Select the file and click Open.
6. Repeat these steps for the following files.

File Description
Company logo: You can place a company’s logo in the
<companyname>.gif Web Portal interface. This displays on all
pages.
Phone: Phone.gif You can place a phone icon in the Web
Portal interface. This displays beside
applicable phone numbers.
Menu arrows: Menu_arrow.gif / You can configure the appearance of the
Menu_arrow_selected.gif/ arrow along the left hand side of the menu
screens. They can configure the
appearance of both the selected and
unselected arrow.
Separator: Menu_separator.gif You can configure the appearance of the
separator. The default is a dotted line.
Help graphic: Help.gif You can insert a help graphic.
Information image: You can insert an information image in the
Information.gif Web Portal interface. This is used to
access pertinent conference details from
a conference entry on the schedule.
Recurrent image: You can insert an image that signifies a
Recurrence.gif recurring conference reservation on the
Web Portal interface.
of the screen
called Companya.
Next steps
Now you can customize other aspects of the Web Portal interface, such the graphics in the
online help file. The easiest way to customize the graphics in the online help file is to view the

folder using the Thumbnail view in the Windows Explorer. Using Thumbnail view, you can see
the logo graphics, such as mh_logo.png, which is the Avaya logo.
Deleting customizations
Prerequisites
Before you delete customizations or brandings, you must you must install and configure the
Web Portal virtual machine.
The purpose of this task is to remove a company's branding.
1. Select Web Branding.

The Web Branding screen displays.
2. Select the applicable company’s name and select Delete Branding and
Configuration.
The selected company’s branding is removed and all their uploaded files or graphics
deleted. Deleting a branding removes any files that were uploaded by the selected
company.
Searching for customizations

You can search for a particular wholesaler, company or client branding
Prerequisites
Before you search for customizations or brandings, you must you must install and configure
the Web Portal virtual machine.
The purpose of this task is to search for a particular wholesaler, company or client branding
1. Select Web Branding.

The Web Branding screen displays.
2. Select Search.

The Brand Alias Screen is displayed.

3. Enter either the wholesaler, company or client name and click Brand Search.
Example
If the company name contains any special characters, such as Company$a, the Web Portal
creates a branding alias called Companya. The branding alias is simply the company name
with any special characters removed.
Localizing Web Portal

Note:
The Standard Edition of Conferencing supports localization from 90 days after the release
date onwards.
Web Portal conforms to the i18n internationalization standard.
Web Portal fields can be translated by customers. However, Avaya does not supply the
customized language files. Customers must provide these translations themselves.
Using eXtensible Markup Language (XML), language files are created to translate displayed
text into almost any language. Displayed text includes all field and button names, such as,
“Status”, “Name”, “View Polling Report”, and so on. These language files must follow the
internationalization conventions (I18N) agreed by the World Wide Web Consortium (W3C). For
more information, see www.w3.org/International/. Any number of language files can be
associated with an application. The process of language file selection is entirely automated
and depends on the locale setting on the client machine. For example, if there are several
language files associated with the application, such as English, French, and German and if
the locale setting on the client machine is French, the French language file is automatically
selected. All screen text displays in French.
The naming convention for the language files is; messages_xx.xml. For example:
• messages_en.xml= English
• messages_fr.xml= French
The locale setting can be viewed using the Regional Options dialog in the Control Panel.
These language files or “resource bundles” consist of a series of mappings between labels in
the XML and labels in the output text. Essentially, they are XML files with a prescribed naming
convention and content tag list, such as:

Localizing Web Portal
• <message key='common.button.submit'>Login</message>
• <message key='common.button.back>Back</message>
• <message key='login.title'>Login Page</message>
• <message key='console.edit.participant.name'>Name</message>
• <message key='console.part.menu.mute'>Mute</message>
• <message key='console.part.menu.unmute'>Unmute</message>
• <message key='chat.text.allmod'>ALL MODERATORS</message>
• <message key='chat.text.allop>ALL OPERATORS</message>
• <message key='console.polling.question.prompt'>Put your question here</message>
• <message key='console.polling.answer.prompt'>Put your answer here</message>
To create a new resource bundle, copy the default resource bundle and modify the text
corresponding to the tag keys. For example, if you are creating an Italian resource bundle, you
may have the following entries:
• <message key='common.button.submit'>Inizio attività</message>
• <message key='common.button.back>Vada indietro</message>
• <message key='login.title'>Pagina Di Inizio attività</message>
• <message key='console.edit.participant.name'>Nome</message>
• <message key='console.part.menu.mute'>Muto</message>
• <message key='console.part.menu.unmute'>Onu-muto</message>
• <message key='chat.text.allmod'>Tutti i Moderatori</message>
• <message key='chat.text.allop>Tutti gli Operatori</message>
• <message key='console.polling.question.prompt'>Scriva la vostra domanda a macchina
qui</message>
• <message key='console.polling.answer.prompt'>Scriva la vostra risposta a macchina
qui</message>
Resource bundles can be updated at any time. Apache and Tomcat must be restarted to view
the updates. A Tomcat restart on the Web Portal is required if languages are configured on the
CRS. You can restart these services using the Conferencing Manager menu: Elements >
Conferencing > Services.
You can view the languages via Internet Explorer. To view languages, go to Tools > Internet
Options > Languages.


Chapter 28: Administering the Web Portal
application
Web Portal user authentication

As a Web Portal and Client Registration Server (CRS) system administrator, you can configure
a number of different settings relating to user authentication in the Web Portal application. By
configuring these settings, you can ensure that Web Portal users log in to the Web Portal
application according to your requirements.
It is a good idea, at this point, to clarify the meaning of the terms Web Portal users and CRS
users. Currently, three roles or types of user access the Web Portal application. These roles
are:
• Web Portal moderators
• Web Portal administrators
The situation with regards to the CRS is slightly more complex. Three roles or types of user
access the CRS Front End:
• CRS administrators
• CRS supervisors
• CRS operators
There are also two additional CRS roles; user-Administrator and user-Auditor.
CRS administrators, supervisors, and operators can be system-owned or wholesaler-owned.
System-owned roles can access the full list of BSRes2 objects, using the CRS Front End
application. Wholesaler-owned roles can access the list of BSRes2 objects that are associated
with their wholesaler. BSRes2 is the name of the database that stores all information about
companies, clients, and bookings.
CRS operators and CRS supervisors can only perform a limited number of tasks. CRS
operators can create companies, clients, and conferences using the Customer Bookings
section of the CRS Front End. CRS supervisors can view a limited number of tabs on the
System Administration section of the CRS Front End.
This table shows the relationship between Web Portal roles and CRS roles.

Administering the Web Portal application
Web Portal Role Equivalent CRS Role

Web Portal moderators CRS clients
For more information on creating clients, see the Operating
Avaya Aura™Conferencing Guide, which is available from
support.avaya.com.
Web Portal administrators System-owned CRS administrators
As a result of this mapping, if you configure CRS Client authentication settings, Web Portal
moderators must adhere to these settings.
Similarly, if you configure CRS administrator authentication settings, Web Portal administrators
must adhere to these settings.
Creation of Web Portal users
You must create an entry for each Web Portal user in the CRS database, BSRes2. When a
Web Portal user exists in the database, they can access the Web Portal. The database stores
all Web Portal moderators and administrators:
• Each Web Portal moderator must exist as a CRS client.
• Each Web Portal administrator must exist as a CRS administrator.
You can create users in the database using the following applications and methods:
The CRS Front End is the PC-based application, typically used by operators to create
companies, clients, and conferences and by administrators to configure resources,
bridges, cabinets, DDIs, telephones, timezones, and system parameters.
• Stored Procedure Interface to the CRS
Avaya provides the Stored Procedure Interface to the CRS as a software developer’s tool
kit. It allows application developers to create companies and clients in the CRS database
from within application programs.
• CRS Import Utility
The CRS Import Utility enables you to upload companies and clients in batch to the CRS
database. This utility is useful when the CRS is first brought into service and in cases
where periodic synchronization with external databases is required.
It is important to note that you can set an account inactivity threshold for CRS users, namely,
CRS administrators, CRS supervisors, and CRS operators. You can also set an account
inactivity threshold for CRS clients. As mentioned in the table above, an account inactivity
threshold for CRS clients impacts Web Portal moderators. Similarly, an account inactivity
threshold for CRS users impacts Web Portal administrators and Web Portal wholesalers.
With this functionality, if a Web Portal moderator or Web Portal administrator does not log in
to the Web Portal for a configurable period of time, the CRS disables their account. A CRS
operator can re-enable a Web Portal moderator by editing the corresponding CRS client
account. A CRS administrator can re-enable a Web Portal administrator by editing the
corresponding user account.

Web Portal password expiry
If the CRS disables all CRS and Web Portal administrator accounts due to account inactivity,
you must contact Avaya Support.
The configuration parameters for the account inactivity threshold are stored in the users, client,
and system parameters tables in the BSRes2 database.
Web Portal connection to the Web server
In a typical configuration, the Web server also requires a CRS log-in to connect to the CRS.
The important feature of this log-in is that it is at System level. System level log-ins are not
subject to the password expiry rules that you configure for Web Portal moderators,
administrators, and wholesalers.
You must configure the CRS connection information on the Web server. You must also
configure the Web server information on the CRS.
• Configuring the Web server connection on the CRS
In CRS, Avaya creates a Web server log-in on your behalf, by default. To activate the log-
in, you must access the System Administration section of the CRS Front End. In the
System Administration section of the CRS Front End, select the System option in the
View panel on the right side of the Logins tab and click the Create Default button. When
you click the Create Default button, the CRS Front End displays the default log-ins that
Avaya created. These log-ins are used for all systems that connect to the CRS, such as
the Notification Subsystem, the eXtended Message Server (XMS), the Web Portal, and
so on.
• Configuring the CRS connection on the Web server
You can configure the CRS connection in the Conferencing Manager interface: Navigate
to Elements > Conferencing > Web Applications. You can also set the log-in type using
the Conferencing Manager.
Web Portal password expiry

Password expiry is managed by a number of settings in the system parameters table in the
BS Res2 database and in the webportal.properties files. The BSRes2 database is the database
which holds all the account and reservation data for Conferencing. The important password
expiry settings are listed here.
Setting Location Description

Period to System parameter For Period to password expiry field to
password in the BS Res2 operate correctly for Web Portal administrators and
expiry field database and Web Portal wholesalers, you must ensure that
accessible from Authentication required at login=1
Conferencing PasswordExpiryThreshold sets the lifespan
Manager of a password in days. For example:
Elements >
Conferencing >

Setting Location Description

Client • To ensure that all moderators update their
Registration > password every 28 days, set Period to
General password expiry field=28. In this
scenario, their password expires after 28 days and
when they next log in, the Web Portal prompts
them to enter a new one. It is worth noting that if
they are an infrequent user, their next log in could
occur on, for example, the 40th day.
• To ensure that all moderators never have to update
their password, set Period to password
expiry field=0. If PPeriod to
password expiry field=0, no password
expiry takes place.
If you enable Period to password expiry
field, the Web Portal application prompts Web
Portal administrators, wholesalers, and moderators
to enter a new password if they attempt to log in to
the Web Portal using an expired password.
Authentication System parameter If Authentication required at
required at in the BS Res2 login=1, the CRS Front End prompts users to
login database and enter a password when they access the CRS. If
accessible from Authentication required at login=0,
Conferencing the CRS Front End does not prompt users to enter a
Manager password when they access the CRS. If you enable
Elements > Authentication required at login, the
Conferencing > Web Portal application verifies the password that
Client Web Portal administrators and wholesalers enter
Registration > when they access Web Portal.
General
Maximum System parameter Maximum number of login attempts
number of login in the BS Res2 represents the number of times a Web Portal user
attempts database and can enter an incorrect password when they are
accessible from attempting to log in to the Web Portal application. If
Conferencing their number of attempts exceeds the value in
Manager Maximum number of login attempts, the
Elements > CRS server disables their account. Maximum
Conferencing > number of login attempts only impacts
Client Web Portal moderators. It has no impact on Web
Registration > Portal administrators or Web Portal wholesalers.
General
Enabling password expiry

• To enable password expiry for Web Portal moderators:

Single sign on
Configure the Period to password expiry field with the lifespan of the password
in days.
• To enable password expiry for Web Portal administrators and wholesalers:
Configure the Period to password expiry field with the lifespan of the password
in days and ensure that Authentication required at login=1.
Disabling password expiry
• To disable password expiry for Web Portal moderators:
Ensure that Period to password expiry field=0.
• To disable password expiry for Web Portal administrators and wholesalers:
Ensure that Period to password expiry field=0.
Note:
Avaya recommends that you disable password expiry for Web Portal moderators who use
log-in type 1 or 4.
Single sign on
The SSO feature only applies to Web Portal moderators. The SSO feature does not apply to
Web Portal administrators or Web Portal wholesalers.
In a similar way, the Login type field in the Conferencing Manager menu (Elements >
Conferencing > Web Applications) only applies to Web Portal moderators.
Single Sign On provides streamlined access to the Web Portal. SSO is beneficial to moderators
who are already logged on to/authenticated by the network as they do not have to log on a
second time. Also, if Conferencing is offered with other services, the moderator does not have
to log on to the conference separately.
SSO applies to installations where the Web Portal is deployed within a Service Provider or
Enterprise system. Normally, the moderator is authenticated by the Service Provider or
Enterprise portal. Therefore, it is not necessary for the moderator to enter further information
to access the Avaya Web Portal.
SSO does not support password expiry functionality because in an SSO implementation,
moderators are typically not familiar with their Web Portal password. If SSO is implemented in
your organization, Avaya recommends disabling the password expiry feature.
SSO may not function correctly when used with a reverse proxy server, or if authentication and
session management are not handled by Web Portal.
It is important to note that the SSO solution has a number of limitations. The SSO solution
cannot pick up the operating system username and password. It cannot use Simple and
Protected GSSAPI Negotiation Mechanism (SPNEGO). It cannot authenticate against a

corporate database or Lightweight Directory Access Protocol (LDAP). It simply provides a

solution which hides the Web Portal Log On screen because users are previously
authenticated and suitable credentials are passed to the CRS for reverification.
Related topics:
Implementing single sign on on page 446
Implementing single sign on

Moderators are normally required to enter details to access the Avaya Web Portal product.
Moderators enter these details on the Log-in page.
Log in form
A HTML form-based log-in mechanism is provided to facilitate integrated Web Portal,
Enterprise and Service Provider authentication. The HTML form is designed to facilitate the
embedding of the log-in mechanism with other pages. It may be in addition to providing, or
instead of, a log-in page. The HTML file must have selected log-in type and the appropriate
variables must be populated.
The Template here contains 3 log-in types: Type 4, type 7, type 8.
The HTML form can be customized and embedded into the web page that provides the access
point to the Web Portal product.
Web Portal servers supports many log-in types but only one log-in type can be implemented
at any single time. The different types are displayed here as an example only.
HTML form template
Note:
This example is in English.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<meta http-equiv="Content-Script-Type" content="text/javascript"/>
< meta http-equiv="Content-Style-Type" content="text/css"/>
<meta http-equiv="Expires" content="0"/>
<meta http-equiv="Pragma" content="no-cache"/>
<meta http-equiv="Cache-Control" content="-1"/>
/head> body>

Single sign on


<form target="" onSubmit="" action="http://localhost/webportal/do-login" method="GET"
d="login" name="login"/accept-charset=”UTF-8”>
<table width="100%" cellspacing="0" valign="top" cellpadding="0" border="0">
<tr valign="bottom">
<td>
<input onClick="" class="formButton" value="Login Type 8" type="submit" id="" name=""/>
<input value="-120" id="tzoff" name="tzoff" type="hidden"/>
<input value="default" id="companyname" name="companyname" type="hidden"/>
<input value="test@Avaya.com" id="emailaddress" name="emailaddress" type="hidden"/>
<input value="test" id="password" name="password" type="hidden"/>
<input value="1" id="loginmode" name="loginmode" type="hidden"/>

< /td>
</tr>
< /table>
< /form>
<form target="" onSubmit="" action="http://localhost/webportal/do-login" method="POST"
id="login" name="login"/accept-charset=”UTF-8”> >
<td>
<input value="test" id="accountname" name="accountname" type="hidden"/>
<input value="test" id="password" name="password" type="hidden"/>
<input value="default"id="companyname" name="companyname" type="hidden"/>
<input value="1"id="loginmode" name="loginmode" type="hidden"/>
<input value="en_IE"id="locale" name="locale" type="hidden"/>
</td>
</tr>

</table>
</form>
<form target="" onSubmit="" action="http://localhost/webportal/do-login" method="GET"
id="login" name="login"/accept-charset=”UTF-8”>
<td>
<input value="default" id="companyname" name="companyname" type="hidden"/>
<input value="test" id="accountname" name="accountname" type="hidden"/>
<input value="4167340069" id="accountreference" name="accountreference" type="hidden"/
>
<input value="1" id="loginmode" name="loginmode" type="hidden"/>
<input value="fr" id="locale" name="locale" type="hidden"/>
</td>
< /tr>
</table>
</form>
</body>
</html>
</tr>
</table>
</form>
The user must exist in the directory server with user logon name=”test” and password =”Test1”.
On the active directory server Windows 2008 password must meet complexity requirements.
Directory context name is case sensitive.
The locale parameter is optional. The browsers default language is used if it is not present.
The “companyname” parameter is used to validate all log-in types and is not optional.

Self administration
Self administration
The Self Administration feature enables non-Web Portal moderators to use the Web Portal
system. Non-Web Portal moderators can create their own Web Portal log-in and then create
their own conferences. In this way, non-Web Portal moderators can become Web Portal
moderators. Self Administration empowers Web Portal users and reduces your administration
workload.
As a Web Portal system administrator, you can configure the Self Administration feature. For
example, you may want to hide the feature completely or you may want to limit the number of
fields that are displayed to moderators.
If your deployment makes use of the Import Utility or the Directory Services Client Application
(DSCA) to import and create moderators, you should hide the Self Administration feature. The
self-administration feature is more suited to smaller, enterprise deployments where moderators
are not imported from an external source.
The Self Administration feature enables non-Web Portal moderators to create Web Portal
moderators. It is a powerful feature, which allows non-Web Portal moderators to be
independent and reduces their reliance on Wholesaler users or CRS operators.
When a non-Web Portal moderator creates a login and becomes a Web Portal moderator,
these new moderator’s details are synchronized with the CRS server. The CRS server adds a
new client to the CRS BSRes2 database to reflect the addition of the new Web Portal
moderator. You can locate a corresponding CRS client record on the CRS Front End for each
new Web Portal moderator.
The validation rules that apply when a CRS operator adds a new client on the CRS also apply to
the Self Administration functionality. For example, with regard to the Password field, you can
set both password length and password complexity on the CRS Front End System
Administration section. It is worth considering that Web Portal moderators will be subject to
these rules when you set up the validation limitations on the CRS. You can configure the CRS
password settings on Elements > Conferencing > Client Registration > General. Web Portal
adminstrators must rely on CRS administrators for this setting. When you enable Self
Administration for Web Portal moderators, you can configure the Web Portal to create an on-
demand conference for each new moderator. Similarly, you can configure the system not to
create an on-demand conference for each new moderator.
If you intend to deploy the Self Administration feature in your customer site, Avaya
recommends that you configure the User Login page to ensure that moderators can log in to
Web Portal by entering their username and password or their e-mail address and password.
The reason for this recommendation is that moderators who are created using the Self
Administration feature do not know their Account Reference. They will not be able to log in
to the Web Portal by entering an Account Reference as verification.

When CRS operators create new clients in the CRS Front End, they can enter an Account
Reference number for each new client. If operators do not enter a value in the Account
Reference field, the CRS server allocates an automatic Account Reference number to the
client.
You can specify the log in credentials for moderators in Conferencing Manager in Elements
> Conferencing > Web Applications.
Related topics:
Accessing the self administration configuration pages on page 450
Configuring the automatic creation of on-demand conference on page 450
Specifying the fields on the self administration page for moderators on page 451
Specifying self administration default values on page 452
Hiding self administration on page 457
Accessing the self administration configuration pages

Prerequisites
Before you access the self administration configuration pages, you must you must install and
The purpose of this task is to navigate to the self administration configuration pages.

2. Click Configuration > Self Administration.
Next steps
Now you can configure the automatic creation of an on-demand conference.
Configuring the automatic creation of on-demand conference

You can configure the Self Administration feature to ensure that the Conferencing server
creates an on-demand conference for each new moderator who is created using the Web
Portal Self Administration feature. Similarly, you can configure the feature to ensure that the
Conferencing server does not create a new on-demand conference for each new moderator.

Self administration
Prerequisites
Before you configure the automatic creation of on-demand conferences, you must access the
self administration configuration pages.
The purpose of this task is to set up the Self Administration feature so that it creates a new
on-demand conferences for each new moderator.
1. Navigate to the Default Values tab on the Self Administration configuration pages.
2. Select the Auto create demand conference for new clients checkbox.
3. Click Commit Changes.
The Web Portal Application will create a new on-demand conference for each new
moderator who is created using the Web Portal Self Administration feature. To
ensure that the conferencing server does not create a new on-demand conference,
ensure that the Auto create demand conference for new clients checkbox is not
selected.
Next steps
Now you can configure further options with regard to the Self Administration feature.
Specifying the fields on the self administration page for moderators

You can specify which fields to display to Web Portal moderators. Using this capability, you
can hide a number of fields from Web Portal moderators.
Prerequisites
Before you specify the displayed fields for the Self Administration feature, you must install and
The purpose of this task is to display or hide certain fields to moderators.
1. Navigate to the Form Fields tab on the Self Administration configuration pages.
2. Select a field to display it.
Field Description
Title The title of the new moderator. For example, enter a title
such as, Mrs., Mr., Dr., and so on.
Address The address of the new moderator. Many users enter the
company address.

Field Description
Second Phone A second telephone number of the new moderator. For
example, users can enter an assistant’s telephone
number.
Mobile Phone A mobile telephone number for the new moderator.
Fax Number A fax number for the new moderator.
Job Title The new moderator’s job title.
Comment This is a free text field. Moderators can enter some
additional information or a special note in relation to the
new moderator.
Timezone The default timezone for the new moderator.
Preferred The preferred language for e-mail notifications and audio
Language prompt sets.
External ID A numeric value to associate the new moderator with an
external database. For example, moderators can enter a
phrase which links the moderator with an external list of
sales targets.
External String A phrase which associates the new moderator with an
external database. For example, moderators can enter a
phrase which links the moderator with a list of resources
that exists outside of the CRS framework.
3. Alternatively, you can choose to hide a field by ensuring that it is not selected.
4. Click Commit Changes to apply your settings.
Next steps
Specifying self administration default values

You can specify default field values for a number of fields on the Self Administration User page.
For example, you can specify the default timezone to be displayed in the Timezone field on
the Self Administration User page.
You can also specify the default field values for the on-demand conference that can be created
for each newly created moderator. You can choose not to create a new on-demand conference
for each newly created moderator. It is worth noting that you can also configure the CRS to
suspend any on-demand conferences that remain unused for a period of time. For example,
if you set Period until conference disabled to 90 days, the CRS suspends any on-demand
conferences that are not used for 90 days. Suspended conferences do not occupy conference
resources. These settings only apply when an on-demand conference is created with each

Self administration
new moderator through the Self Administration tool. When the newly created moderator logs
into the Web Portal and books a new conference, the regular system-wide settings apply to
that user and that conference. You can set Period until conference disabled in Conferencing
Manager in the Elements > Conferencing > Client Registration > General menu.
Prerequisites
Before you specify the default values for the Self Administration feature, you must install and
The purpose of this task is specify default values for the Self Administration User page and for
the on-demand conference that is automatically created for new moderators.
2. You can set the default value for a number of client settings.
Field Description
Company You can specify which company name is displayed as the
Name default company name. You can use the Search button to
locate the default company name.
Prompt Set You can specify the language of the audio prompt set that is
displayed by default on the Self Administration User page.
Timezone You can specify the timezone that is displayed by default on
the Self Administration User page.
Block The Dial Out feature enables moderators to make external
Dialout calls during a conference. Moderators can bring new
participants into the conference using this feature.
As the Web Portal system administrator, you can set a default
value for Block Dialout for all moderators created using the
Self Administration feature on the Web Portal.
If you enable it, the Conferencing server prevents moderators
created using the Self Administration feature from dialling out
during a conference.
If you disable it, the Conferencing server permits users created
using the Self Administration feature to dial out during a
conference.
On the CRS Front End, operators can set the Block Dialout
feature at company, client, and conference level. The user/
client level setting overrides the company level setting.
Similarly, the conference level setting overrides the user/
client level setting.
On the Web Portal application, moderators cannot edit this
setting at their account level, which equates to user/client level
in the CRS Front End, or at conference level. So, it is important
to note that your choice for Block Dialout becomes a
moderator attribute which the moderator cannot change within
the Web Portal application. The Block Dialout attribute is

Field Description
hidden from moderators on their account details page and on
their conference booking page.
Disabled You can choose to allocate Disabled status to all moderators
created using the Self Administration feature. In this state, the
new moderators cannot create conferences. CRS system
administrators must enable them in the CRS Front End.
Disable Operator Recall enables participants to signal to operators that
Operator they require assistance during a conference. Participants
Recall signal to operators by entering a pre-configured DTMF key
sequence, such as *0, on their telephone keypad. When
participants require assistance, their name is displayed in the
Help Requests dialog in the BridgeTalk application.
As the Web Portal system administrator, you can set a default
value for Disable Operator Recall for all moderators created
using the Self Administration feature on the Web Portal.
If you enable it, the conferencing server sets Disable
Operator Recall as an attribute for all conferences booked by
moderators who were created using the Self Administration
feature.
If you disable it, the conferencing server sets Enable Operator
Recall as an attribute for all conferences booked by
moderators who were created using the Self Administration
feature.
On the CRS Front End, operators can set the Disable
Operator Recall as a feature at company, client, and
conference level. The user/client level setting overrides the
company level setting. Similarly, the conference level setting
overrides the user/client level setting.
On the Web Portal application, moderators cannot edit this
setting at their account level, which equates to user/client level
in the CRS Front End, or at conference level. So, it is important
to note that your choice for Disable Operator Recall becomes
a moderator attribute which the moderator cannot change
within the Web Portal application. The Disable Operator
Recall attribute is hidden from moderators on their account
details page and on their conference booking page.
3. You can set the default value for a number of on-demand conference settings.
Field Description
Number of You can specify the Number of Participants that will apply
Participants to the on-demand conference that is created for the new
moderator, using the Self Administration feature.
Data You can choose to enable or disable data conferencing in
Conference the on-demand conference that is created for the new
moderator, using the Self Administration feature. Data

Self administration
Field Description
conferencing enables participants to share applications,
slide shows, and whiteboards.
Auto Extend You can choose to enable Auto Extend Ports by default.
Ports Auto Extend Ports means that the Conferencing server
automatically increases the number of ports allocated to a
particular conference if the number of participants exceeds
the number of booked participants.
Prompt Set You can also specify the language of the audio prompts in
the on-demand conference that is created for the new
moderator, using the Self Administration feature. For
example, if you select English, the English audio prompts
are used for the moderator’s on-demand conference.
Payment Type The available values for Self Administration are:
• Account Reference (AR): The moderator’s account
number.
• Dial number (DN): The telephone number of the caller.
• Calling line identifier (CLI): The redirecting number
information for the caller.
Enter Tone You can select a default value for the configuration of tones
Leaving Tone and messages as participants enter and exit the on-
demand conference that is created for the new moderator,
using the Self Administration feature.
The following options are available:
• System: The Conferencing server uses a pre-configured
default setting.
message.
voice message.
Moderated A moderator accesses the conference using the moderator

Conference passcode. Moderators can access a number of conference
features that are not available to regular conferees. You can
choose a default status for the on-demand conference that
is created for the new moderator, using the Self
Administration feature.
Music Source You can choose a default value for the Music Source drop-
down list for the on-demand conference that is created for
the new moderator, using the Self Administration feature.

Field Description
From the Music Source drop-down list, you can select Off
to switch the music off. Alternatively, you can select a
source for the music. The numbers one to four represent
four file locations on the bridge. Music is stored in the .wav
format, but additional functionality is available to dial out to
an external music source.
Note:
It is important to note that if you select Off, moderators
cannot place their participants in an on hold state.
Moderator You can choose a default status for Moderator Hang up for
Hang up the on-demand conference that is created for the new
moderator, using the Self Administration feature. If you
enable Moderator Hang up, the on-demand conference
ends when the last moderator exits.
Secure Mode If Secure Mode is enabled, moderators can lock the on-
demand conference that is created for the new moderator,
using the Self Administration feature.
Name Record You can choose a default value for the Name Record
Playback Playback drop-down list for the on-demand conference
that is created for the new moderator, using the Self
Administration feature.
If you enable Name Record Playback (NRP), the
Conferencing server prompts all participants to call out their
name before they enter the conference. Moderators can
then play a audio roll call of attendees. There are number
of possible values:
• Off: The Name Record Playback option is not enabled.
• Individual: The system plays a recording only to the
individual.
• Conference: The system plays a recording to the
conference.
Biometrics In a future version of Conferencing, voice verification

Controlled software will be used as an optional secure entry method
into conferences. This feature is not available at present.
Avaya recommends switching off this feature.
4. Click Commit Changes to apply your settings.
Next steps

Self administration
Hiding self administration

You can switch off the Self Administration feature. If you switch off the Self Administration
feature, users cannot create other users via the Web Portal Application. If you switch off the
Self Administration feature, users do not see the Create an Account link on the Login screen.
If your deployment makes use of the Import Utility or the Directory Services Client Application
(DSCA) to import and create users, you should hide the Self Administration feature. The self-
administration feature is more suited to smaller, enterprise deployments where users are not
imported from an external source.
Prerequisites
Before you hide the Self Administration feature, you must install and configure the Web Portal
virtual machine.
The purpose of this task is to hide the Self Administration feature from moderators.
2. Ensure that the Self Administration Feature Enabled checkbox is not selected.
3. Click Commit Changes.


Chapter 29: Customizing the Audio Console
application
Customization
Customization, or branding is a value-added service that Communication Service Providers
(CSPs) can offer customers. Enterprise customers can also brand the Audio Console for their
own internal use to ensure that the interface is consistent with their overall Web style.
Using branding functionality, you can integrate customer styles and logos into existing Audio
Console screens. You can customize Audio Console screens on a per client basis. Branding
presents a consistent look and feel across all conferences for a particular client.
Audio Console system administrators can customize the Audio Console screen for individual
clients, using a series of branding options in the Web Portal suite.
Cascading Style Sheet (CSS) is a simple mechanism for adding style (such as fonts, colors,
spacing, and so on) to Web documents. All Web pages reference the style sheet and you can
use the style sheet to change the look and feel of an entire site. CSS files simplify the
customization process because you can make changes in a single location.
A branding wizard guides you through the process:

Customizing the Audio Console application
You can customize the Audio Console toolbar and also the Audio Console participant states.
Toolbar
Participant states
The Audio Console displays each conference participant using an icon. These icons represent
the various participant states. For example, if a participant enters the Mute state, their
participant icon changes to an icon which represents the Mute state. Similarly, moderators are
distinguished from participants using specific iconography.
Audio Console system administrators can replace these default icons with new images. The
default icons are 24 pixels X 24 pixels in size. It is advisable to replace the default icons with
new images of an identical or very similar size.
It is important to note that if moderators access the Audio Console using a branded URL, the
Web Portal does not embed URLs in the Web page that refer to different CSS and image
locations. The Web Portal does substitute different strings so that the Web page appears
different to the browser cache. The consequence of this feature is that:

Customization
• If a user visits their branded URL for the first time, the Web page displays the branded
images successfully.
• If a user visits a different company or the default branding before they visit their branded
URL, they must clear the browser cache to display the correctly branded images
successfully. If the user simply refreshes the Web page, the correct images do not display.
They must clear the cache.
Icon Description
Conferee
Conferee talking
Conferee mute
Conferee hold
Moderator
Moderator talking
Moderator mute
Moderator hold
Subconference flag
Conferee interceptee
Moderator interceptee
Moderator interceptor
Dialing conferee
Dialing moderator
Note:
Avaya recommends that only one person customizes the Audio Console at a time. If there
are multiple simultaneous attempts to configure Audio Console settings, the Audio Console
may become unstable.
Supported browsers
Avaya recommends Microsoft Internet Explorer 8.0 and Mozilla Firefox 3.6 for use with the
Audio Console.

Logging on to Audio Console

Prerequisites
Before you log on to Audio Console, you must install and configure the Web Portal virtual
machine. You must also have an administrator account on the CRS Front End.
The purpose of this task is to access the administration pages of the Audio Console.
1. In a Web browser, enter the Web Portal administrator URL: http://Web Portal
virtual machine IP/ webportal/admin/login.
2. Enter an account name and a password and click Login.
Next steps
Now you can customize the Audio Console toolbar and the Audio Console participant states.
Customizing Audio Console

Prerequisites
Before you customize Audio Console, you must install and configure the Web Portal virtual
machine. You must also have an administrator account on the CRS Front End.
The purpose of this task is to give the Audio Console a customized look and feel.
1. Navigate to Branding > Web Poral Branding.

2. Enter a company name in the Company Name field. You can also use the Search
icon to search for a company name. If you want to update the default branding,
select the Default Branding check box.
3. Click Start Branding Wizard.
The Web Portal starts the Branding Wizard. The Branding Wizard divides the
process of branding into three discrete steps. The three steps are:
• Branding the Web Portal interface

Customizing Audio Console
• Branding the Audio Console toolbar

• Branding the Audio Console participant states
The Web Portal displays the Web Portal Interface Branding screen.
4. Enter a the location of a valid cascading style sheet (CSS) and a series of images
in the branding fields. You can use the Browse button to locate the files.
5. Click Upload.
The Web Portal uploads the file and images that you entered.
The Web Portal progresses to the second step in the branding wizard.
The Web Portal displays the Audio Console Toolbar Branding screen.
6. Enter the locations of the image files that you want to use to brand the toolbar.
The Web Portal supports image files in the following formats:
• gif
• jpeg
You can use the Browse button to locate the files.
7. Click Upload.
The Web Portal progresses to the third step in the branding wizard.
The Web Portal displays the Audio Console Participant States Branding screen.
8. Click Skip to proceed to the end of the branding wizard.
If you click Skip, the Web Portal displays the Branding Creation screen.
Alternatively, you can brand the Audio Console participant states.
9. Enter the locations of the image files that you want to use to brand the participant
states.
As before, the Web Portal supports image files in the following formats:
• gif
• jpeg
You can use the Browse button to locate the files.
10. Click Upload.
The Web Portal progresses to the end of the branding wizard.
The Web Portal displays the Branding Creation screen.
11. Click Create Branding Now to create a branding from the files you have entered.
Alternatively, you can click Previous to return to previous screens.
The Web Portal displays the Branding Success screen.
The small logo, Small logo image on the Audio Console, is always displayed in
a space of width 100 and height 55 pixels. The Web Portal resizes the .gif file

provided for any company branding to fit that space regardless of the size of the
image.
Next steps
Now you can customize further options with regard to the Audio Console application.
Activating and deactivating toolbar functions

Prerequisites
Before you activate or deactivate toolbar functionality, you must install and configure the Web
Portal virtual machine. You must also have an administrator account on the CRS Front End.
The purpose of this task is to activate or deactivate toolbar functions. This task is useful if you
want to customize moderator access to specific features.
Note:
You can configure most of these settings using the Conferencing Manager administrator
interface. It is unlikely that you should have to edit the manage-menu.xml file. These steps
are included for information only.
When you deploy the Audio Console, it locates a file called manager-menu.xml in the
docs/client directory. To activate and deactivate toolbar icons, you must edit this file.
To de-activate any feature, comment out the associated entity. Typically, Avaya
Support Engineers perform this level of customization.
Example
In this example, the Avaya Support Engineers have disabled dial list functionality:
<?xml version="1.0"?>

<menu xmlns:i18n="http://apache.org/cocoon/i18n/2.0">
<entity id="dial">
<description><i18n:text>console.conf.status.dialout.help</i18n:text></description>

Enabling the sub conference feature
<image>/console/images/btn_dial_enabled.gif</image>
<onclick>dialListDialog</onclick>
</entity>

Enabling the sub conference feature

As the Audio Console system administrator, you must enable the sub conference feature on
the audio Conferencing bridge.
Prerequisites
Before you enable the sub conference functionality for the Audio Console, you must install and
configure the Web Portal virtual machine. You must also have an administrator account on the
CRS Front End.
The purpose of this task is to enable the sub conference feature for Audio Console.
On Conferencing Manager, navigate to Elements > Conferencing > Audio

Conferencing > General Config.
There are three ways to configure the sub conference feature on the audio
Conferencing bridge:
• You can set it to Off. The sub conference feature is not available.
• You can set it to Moderator. In this situation, at least one moderator must be
moved into the sub conference in order to open the sub conference. Once the
sub conference is open, anyone can be transferred to the sub conference. The
moderator does not have to remain in the sub-conference. The moderator is only
required to initially open the sub conference. The sub conference closes when
it is empty.

• You can set it to Anyone. In this situation, any conferee can be transferred to a
sub conference in order to open the sub conference. The sub conference closes
when it is empty.
Next steps
Now you can customize further options with regard to the Audio Console application.
Properties file
The Conferencemanager.properties file contains the Audio Console configurable parameters.
The Conferencemanager.properties file is located in: <installation directory>/
webapps/console/WEB-INF
The Conferencemanager.properties file consists of a series of parameters and accompanying

values. The other important location for Audio Console configuration settings is on
Conferencing Manager. To configure any of these settings, navigate to Elements >
Conferencing > Web Applications.
As an Audio Console system administrator, you can configure a number of parameters. This
table lists the parameters. In addition to these parameters, there are a number of parameters
that you should not change. If you change these parameters, the system can become
unreliable.
Conferencemanager.properties file
LogConf The name of the file that contains the log4j
properties. Log4j is a 3rd party logging tool that is
configured for Audio Console debug output. The
log4j properties are things like the log file name
and location, the format of logged output etc.
Note:
All the Web products use log4j for logging.
BRIDGE_NAME The IP address or the hostname of the bridge.
If the Audio Console is setup to talk to a CRS, then
BRIDGE_NAME can be blank. Audio Console
takes the bridge name from CRS in this case.
UserName This parameter specifies the username, which is
the operator log in name that is used to log on to
Audio Console.

Properties file
PASSWORD This parameter specifies the password, which is
the operator log in password that is used to log on
to Audio Console.
CodrDBServer The IP address or hostname of the CODR
database server.
CodrDBUser The CODR database system administrator
username.
CodrDBPwd The CODR database system administrator
password.
ReportsChartBgColor These parameters are not used in the current
ReportsChartPlotBackgroundColor release of Conferencing. Web Portal compiles the
ReportsChartSeriesForegroundColor reports and uses the settings in
ReportsChartFont webportal.properties.
ReportsChartFontSize
ReportsChartFontStyle
LogonType LogonType detemines the fields that are
presented to the user on the Log On screen. This
Note: parameter is specified as a numeric value, as
On the Conferencing, LogonType is follows. Logon includes a name entry. When a
defined by ModApiLogonType. CRS is present a password is also required.
• 1 = Conference ID, Confirmation Number and
Moderator PIN - all three required
• 2 = Confirmation Number and Moderator PIN -
both required
• 3 = Conference ID and Moderator PIN - both
required
• 4 = Moderator PIN - only this is required (this
logon type does not work if Audio Console is
configured with a CRS)
SaveInputCheckbox The SaveInputCheckbox parameter determines

whether the Save Login Details field is displayed
on the Log On screen.
If SaveInputCheckbox=off, the Save Login Details
option is not available to Audio Console users.
If SaveInputCheckbox=on, the Save Login Details
option is available to Audio Console users.
The Save Login Details option enables users to
store their log on details for future re-use. The
default value of SaveInputCheckbox=off.
PING You can configure the interval between automatic
requests to the bridge. Automatic requests are
required to keep the connection alive when there
is a firewall in the network configuration. A firewall

would close the connection if there was no activity
for a particular length of time. The PING
parameter configures the length of time in
seconds between pings to keep the firewall alive.
For example, PING=30.
Do not change these parameters

• CrsHost
• CrsPort
• CrsImpl
• CodrDBDriver
• OPER_NUM
• IMPL_TYPE
• ConsoleLoadSmall
• ConsoleLoadMedium
• ConsoleLoadHigh
• JChatAdminLogin
• JChatAdminPassword
• ReportsChartImageRelativeDir
• ReportsChartImageWebDir
• ReportsChartWidth
• ReportsChartHeight
Note:
In the case of a Web Portal and Self Registration installation:
- Set CRS_Name to the IP address or hostname of the CRS.
- Comment out Bridge_Name.
Avaya advises not to change the default configuration.

Chapter 30: Integrating with Microsoft
applications
Overview of Microsoft integrations

Conferencing integrates with a number of Microsoft applications. Avaya has created a number
of plug-in applications which enable Microsoft users to leverage Conferencing functionality.
These plug-ins add additional functionality to the Microsoft applications and enable users to
use Conferencing resources with little or no training. The Standard Edition of Conferencing
integrates with:
• Microsoft Live Meeting
• Microsoft Office Communicator
• Microsoft Outlook
Using these integrations, Microsoft users can book conferences and attend conferences, on-
demand.
For more information about how to implement the Microsoft integrations in your deployment,
see the Implementing Avaya Aura™ Conferencing Guide which is available from
support.avaya.com..
Avaya Conference Scheduler for Microsoft Outlook

You can make Conferencing capabilities available throughout your organization using a plug-
in application which Avaya has developed to integrate seamlessly with Microsoft Outlook. The
Conference Scheduler plug-in for Microsoft Outlook enables end-users to book conference
calls in the same way that they book an appointment or a meeting. The plug-in consists of an
additional tab, called, Conference Call, which is displayed on the Calendar screen in Microsoft
Outlook.
The plug-in supports deployment on clients with Microsoft Office Outlook 2003 and 2007 on
Microsoft Windows XP (Service Pack 2 or later), and Microsoft Windows 7. Computers with
Microsoft Outlook 2003 must have Microsoft Office 2003 Service Pack 1 or later installed, or
the plug-in installation process will fail.

Integrating with Microsoft applications
The Conference Scheduler plug-in for Microsoft Outlook has two installation options:
• You can run the client set-up for the Conference Scheduler plug-in for Microsoft Outlook
on each User’s computer. After set-up, the assemblies needed for the plug-in reside on
the User’s computer.
• You run a silent installation without the installer by extracting the client set-up and running
the .msi file only. This is a fast and efficient method.
If Microsoft Outlook is in offline mode, but is still connected to the network, then the plug-in
operates as normally. It retrieves the details of users’ on-demand conferences and it creates
new scheduled conferences for users. However, if Microsoft Outlook is in offline mode and is
not connected to the network, then the plug-in displays a network error if users try to retrieve
on-demand conference details or schedule new conferences.
Related topics:
Prerequisites on page 470
Prerequisites
The plug-in is based on Microsoft Visual Studio Tools for Office (VSTO) technology. As a result,
you must install the following pre-requisites on the client PC’s.
Note:
Avaya ships all prerequisites with the Conferencing software.
If you are using Microsoft Outlook 2003
• Microsoft .Net Framework 2.0
• Microsoft Visual Studio Tools for Office 2005 Runtime
• Microsoft Visual Studio Tools for Office 2005 Language Pack (optional)
• Microsoft Office 2003 Primary Interop Assemblies
If you are using Microsoft Outlook 2007
• Microsoft .Net Framework 2.0 and 3.5
• Microsoft Visual Studio Tools for Office 2005 Second Edition Runtime
• Microsoft Office 2007 Primary Interop Assemblies
If the clients, or target PCs, are using non-English locale settings, they must have an
appropriately localized version of the Microsoft .Net Framework 2.0 installed on their PC. This is
a requirement for both Microsoft Windows XP (Service Pack 2 or later), and Microsoft Windows
Vista platforms. It is your responsibility as the system administrator to ensure that the correctly
localized version of the Microsoft .Net Framework 2.0 is installed on the target PCs.

Conferencing for Microsoft Live Meeting and Microsoft Office Communicator
Conferencing for Microsoft Live Meeting and Microsoft

Office Communicator
Conferencing integrates with a number of Microsoft products. Conferencing also integrates
with:
• Microsoft Office Communicator 2007 R2
• Microsoft Office Live Meeting 8
To provide these integrations, Avaya has created two adapters, which act as an interface
between and Microsoft Office Communicator. These two adapters are called the Microsoft
Adapter and the Office Communications Server (OCS) Adapter. To successfully enable the
Conferencing integrations, you must install and configure these adapters.
• If your clients are running Live Meeting, you must configure the Microsoft Adapter.
• If your clients are running Office Communicator 2007 R2, you must configure the OCS
Adapter.
Related topics:
Microsoft adapter on page 471
OCS adapter on page 472
Microsoft adapter
Microsoft Adapter integrates Microsoft Office Communications Server R2 (OCS) and the Avaya
Conferencing application server (bridge) to provide protocol conversion between the Microsoft
Live Meeting client application and an Avaya Conferencing bridge.
Microsoft Adapter is deployed in a Conference Service Provider (CSP) or an Enterprise
environment to provide the following protocol conversions:
• Conversion of SIP events that are received from OCS, to commands that are specific to
the Avaya Conferencing bridge. The Conferencing bridge then initiates an audio
conference. The Conferencing bridge is also deployed in the environment of the CSP.
• Conversion of events that are specific to the Conferencing bridge, to SIP events. Microsoft
Adapter then sends these SIP events to OCS.
Related topics:
Microsoft adapter components on page 472

Microsoft adapter components

Microsoft Adapter includes the following components:
• Microsoft Adapter Installer: Installs Microsoft Adapter
• Administration interface: A graphical user interface that you use to configure and
administer Microsoft Adapter
• Audio Conferencing Provider (ACP) Server. An interface to Microsoft Office
Communications Server (OCS). ACP Server handles the movement of conference data
to and from meeting clients and bridges. ACP Server performs the following functions:
- Event listening
- Connecting to an audio conferencing bridge
- Support for Office Communicator 1.0 audio functionality
- Communication with a Conferencing bridge
- Logging of events and messages
• BCAPI Client:
- Creates the connection to the bridge and maintains the bridge object
- Keeps information of the state of this connection
- Listens to the BCAPI events
- Sends BCAPI events to ACP Interface so that these can be sent to LM/OC
- Maps the ACP Module events to corresponding BCAPI method calls
- All the Bridge connection references are maintained. These connections are
persistent
• ACP BCAPI Client Interface
OCS adapter
Avaya has developed the Microsoft Office Communications Server Adapter, often called the
OCS Adapter, to act as an interface between Microsoft Office Communicator 2007 R2 and the
Related topics:
OCS adapter feature set on page 473
OCS adapter audit trail on page 473
OCS adapter operating environment on page 474

Conferencing for Microsoft Live Meeting and Microsoft Office Communicator
OCS adapter feature set

The features set include the following:
• A user can start an audio conference by selecting participants from the Microsoft Office
Communicator contact list. Once the audio conference begins, this user becomes the
conference moderator.
• Moderators can view the status and details of all participants, during a live conference.
• Moderators can update the line status to mute and unmute participants.
• Participants can mute their line. Similarly, participants can unmute their line.
• Moderators can mute the lines of all participants. Similarly, moderators can unmute the
lines of all participants. Moderators can also mute the lines of selected participants.
Similarly, moderators can unmute the lines of selected participants.
• Participants can leave a conference by hanging up their telephone line or by clicking an
interface icon.
• Moderators can hang up a participant from the conference by clicking an interface icon.
• Moderators can end the conference by clicking an interface icon. Moderators can lock
and unlock a conference to prevent any further Participants from joining the conference.
Note:
In the OCS Adapter environment, Name Record Playback (NRP) is not supported. Similarly,
entry and exit tones and announcements are not supported.
OCS adapter audit trail

The OCS Adapter maintains a log of any errors and faults. There are a number of levels of
logging events:
• Error
• Debug
• Warning
• Information
You can configure the logging level to capture the events that you require. The log files are
stored in a configurable location. When the size of the file reaches a configurable size, the
OCS Adapter creates a new file. The default maximum size is currently 2 MB.

OCS adapter operating environment

The OCS Adapter operates with the following systems:
• Conferencing Standard Edition
• Microsoft Office Communicator 2007 R2 on Windows XP or Windows Vista 7 Professional
Edition with Internet Explorer 6 or 7
• Microsoft Office Communications Server 2007 Standard Edition on Windows Server 2008
Standard Edition
The OCS Adapter requires the following systems:
• Windows .NET 3.5 Service Pack 1
• Sun JRE 1.5.0_07 or higher
• Microsoft IIS 7
• ASP.NET 2.0
• AJAX 1.0

Chapter 31: Installing/configuring
Conference Scheduler for
Microsoft Outlook
Timezones
The Avaya Conference Scheduler Plug-in for Microsoft Outlook uses timezone 1 UTC (System)
as the default timezone for booking conferences. This configuration is hardcoded. Do not edit
the timezone list in the Client Registration Server Front End. If you want to update the timezone,
make the change using the Conferencing Manager application (Elements > Conferencing >
Client Registration > Timezones menu).
Related topics:
Timezone settings on page 223
Stored procedures
The CRS Stored Procedure Interface (CSPI) is a series of SQL stored procedures that provide
developers with conference managing tools. CSPI is part of the BSRes2 Database. CSPI
enables third party developers call the procedures from their preferred programming language
or directly via SQL.
For more information on CSPI, see the Avaya CRS Stored Procedures Guide, which is
available from your Avaya Support Representative. For the successful operation of the
Conference Scheduler Plug-in for Microsoft Outlook application, you must install the
Conferencing CSPI component. For more information, contact your Avaya Support
Representative.
Configuring for a manual installation

Manual installation is also known as client installation. The client set-up installs all the files and
registry entries that the Conference Scheduler plug-in for Microsoft Outlook requires. It also

Installing/configuring Conference Scheduler for Microsoft Outlook
sets the .NET security policy to enable Microsoft Outlook to run the plug-in. It is a standalone
set-up, which is suited to a local installation scenario. The client set-up is located in the
Conferencing installation folder at:
• /Outlook2007/Setup.exe if you are running Microsoft Office Outlook 2007
• /Outlook2003/Setup.exe if you are running Microsoft Office Outlook 2003
The client set-up performs the following actions:
• Checks that the pre-requisites are installed.
• Prompts the user to accept license agreements for any of the pre-requisites which are
not installed.
• Installs any missing pre-requisites.
• Prompts the user to accept the Avaya license agreements.
• Prompts the user to enter the IP address of the Conferencing bridge.
• Prompts the user to e-mail address and password that matches their client account on
the CRS Front End. Each user of the Conference Scheduler plug-in for Microsoft
Outlook requires a client account on the CRS Front End.
• Provides a default installation folder; C\Program Files\Avaya\Outlook Conference
Scheduler\ and prompts the user to select an installation folder.
• Installs the Conference Scheduler plug-in for Microsoft Outlook.
The add-in loads when the user restarts Microsoft Outlook or when it is enabled in the
COM add-in menu.
• During an un-install, the client set-up:
a. Removes the contents of the installation folder.
b. Removes the security policy settings for OutlookConferenceScheduler.
c. Removes the registry entries for OutlookConferenceScheduler.
Note:
Users runs the un-install using the Add/Remove Programs feature in the
Windows Control Panel. The un-install does not remove the pre-requisites for
the Conference Scheduler plug-in for Microsoft Outlook.
Configuring for a silent installation

The installation packages for the Conference Scheduler for Microsoft Outlook are available on
the Conferencing server once you install Conferencing. These steps describe how to enable
the silent installation on your network.

Configuring for a silent installation
Prerequisites
Before you can configure a silent installation of the Conference Scheduler for Microsoft Outlook
in your deployment, you must obtain the installation files from your Avaya Support
Representative. Avaya ship these files as an .ISO image.
The purpose of this task is to role out the Avaya plug in for Microsoft Outlook in your
organization.
1. The installation package as an .ISO image containing the following files and
directories:
• Administrator: The directory used by setup.exe to check for administrator
privileges. This file is not relevant for a silent installation.
• dotnetfx: Microsoft .Net Framework 2.0
• localisation: Localized Resource DLL’s
• Office200xPIA: Microsoft Office Outlook Primary Interop Assemblies
• VSTOR: Visual Studio Tools for Office (VSTO) or VSTO Second Edition for
Outlook 2007 version
• OutlookConferenceSchedulerClientSetup.msi or
Outlook2007ConferenceSchedulerClientSetup.msi: MSI install package
• setup.exe: Setup program
2. Install the relevant pre-requisites on the target computers.
3. Install the MSI Installation package on the target computers.
4. Run the command for installing the Avaya Conference Scheduler for Microsoft
Outlook. Here is an example of this command:
msiexec /quiet /package
OutlookConferenceSchedulerClientSetup2007.msi
5. Use the remote registry editor or another tool to roll out the following 3 registry
entries (strings) to each target computer:
[HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{9B6591DB-66E8-4975-
BDB4-6E05BD1239BF}]
• hostname
• EmailAddress
• AccountPassword
The three entries are the IP address of the Conferencing server, the User’s e-mail
address, and the User’s password as set on their account on the Conferencing
server.
6. If your users are running Microsoft Outlook 2003:

a. Request your users to restart Microsoft Outlook in order to access Avaya

Conference Scheduler for Microsoft Outlook.
b. After the restart, request your Users to run the following file:
EnableOffice2003User.reg
By default, this file should be located in
c:\Program Files\Avaya\Outlook Conference Scheduler
7. If your users are running Microsoft Outlook 2007:
Request your users to restart Microsoft Outlook in order to access Avaya
Conference Scheduler for Microsoft Outlook.
Unlike Microsoft Outlook 2003 Users, Microsoft Outlook 2007 Users do not need
to run the registry file in order to access the Conference Scheduler plug-in. There
is one exception to this rule: If you restart Microsoft Outlook immediately after the
installation, while still logged in as an administrator, the Microsoft Outlook 2007
user must run EnableOffice2007User.reg when they log in.
Next steps
Now you can configure the Microsoft Outlook settings using the Conferencing Manager
administration interface.
Configurable settings
You can configure many of the properties of the Conference Scheduler for Microsoft Outlook
using the Conferencing Manager administrator interface.
For example, you can hide certain Conferencing options or you can configure certain options to
display on the GUI in an enabled state. You can also configure which features are displayed
for users on the Conference Call tab of the New Appointment dialog. Using this functionality,
you can customize the end user experience to exactly match your requirements.
Related topics:
Audio
Invitation header on page 219
Invitation body on page 219
Audio numbers on page 219
On demand on page 219
Schedule on page 219
Web conference on page 220
Join conference on page 220

Configuring Conference Scheduler for Microsoft Outlook
Show roster list on page 220

Most recent list size on page 221
Configuring Conference Scheduler for Microsoft Outlook

You can configure many of the properties of the Conference Scheduler for Microsoft Outlook
using the Conferencing Manager administrator interface.
Prerequisites
Before you configure the Conference Scheduler for Microsoft Outlook settings, ensure that you
install and configure Conferencing and install the Conference Scheduler for Microsoft Outlook.
The purpose of this task is to customize the plug-in in your deployment.

machine.
4. Click Configure.
6. Click Groupware Clients to display the Conference Scheduler for Microsoft
Outlook settings.
8. Click Save.
Next steps
Restart Microsoft Outlook to verify that your configuration options are reflected in the
Conference Scheduler for Microsoft Outlook interface.
Related topics:

Ensuring that Conferencing notification e-mails are not classified

as junk
Microsoft have developed a junk e-mail filter for Microsoft Outlook. This filter is present in
Microsoft Outlook 2007 and in updated versions of Microsoft Outlook 2003. To ensure that the
Conferencing notification e-mails that the Notifications Subsystem sends to participants to
inform them of conference invitations, conference cancellations, and so on are not classified
as junk e-mails, you must perform some configuration steps.
Prerequisites
Before you ensure that notification e-mails are not classified as junk, you must install the Avaya
Aura™ Conferencing Plug-in for Microsoft Outlook.
The purpose of this task is to add the Conferencing details to the safe sender list in Microsoft
Outlook.
1. Make a note of the e-mail address that you entered in the Email Sender field in the
Conferencing Manager menu: Elements > Conferencing > Client Registration
Server > General settings > Notification settings.
2. Add this e-mail address to the Microsoft Outlook address book or add it to the Safe
Senders list.
Example
The E-mail Sender field can be a value such as conferencing@customername.com or
conferencing@noreply.com.
Next steps
Now it is a good idea to verify this configuration by sending a test e-mail to see if it is classified
as a junk e-mail. You can send a test e-mail by booking a test conference.
Related topics:
Reinstalling
In the unlikely event that a user has to re-install the Conference Scheduler plug-in for Microsoft
Outlook, ensure that they uninstall the previous version of Conference Scheduler plug-in for
Microsoft Outlook prior to beginning the re-installation.

Conferencing for Microsoft Live
Meeting
Microsoft adapter installation

A key component of the Avaya Conferencing Plug-in for Microsoft Live Meeting is the Microsoft
adapter. Avaya has developed the Microsoft adapter to bridge the gap between the Avaya
components and the Microsoft components.
For the successful operation of the Conferencing Plug-in for Microsoft Live Meeting, you must
install and configure the Microsoft adapter.
There are a number of stages in the installation of the Microsoft adapter. You must perform
these steps in the order listed here:
• Installation of the Java Runtime Environment (JRE)
• Installation of Microsoft adapter
• Configuration of BSMon
• Configuration of Transport Layer Security (TLS)
• Configuration of the gateway settings and log settings on the Microsoft adapter
administrative interface
• Addition of Conferencing application server (bridge) on the Microsoft adapter
administrative interface
• Configuration of Microsoft Live Meeting on client machines
Related topics:
Installing JRE on page 482
Installing Microsoft adapter on page 483
Configuring BSmon on page 484

Installing/configuring Conferencing for Microsoft Live Meeting
Uninstalling Microsoft adapter on page 485
Installing JRE
The Microsoft adapter requires Java files in order to operate successfully. The Java files are
called the Java Runtime Environment (JRE).
Prerequisites
Before you configure the JRE environment, you must install and configure Conferencing. You
must also install and configure Microsoft Live Meeting.
The purpose of this task is to install and configure the Java prerequisites that are necessary
for the Microsoft adapter. The Microsoft adapter is a key component in the Conferencing plug-
in for Microsoft Live Meeting.
1. Install the Java Runtime Environment (JRE).

To download JRE, navigate to http://www.java.com/en/download/manual.jsp.
2. Right-click My Computer on your desktop and then click Properties.
3. Click the Advanced tab and then click Environment Variables.
The system displays the Environment Variables screen.
4. In the System Variables area, select the Path variable and then click Edit.
The system displays the Edit System Variable screen.
5. To set the JRE environment path, copy the JRE path from the location of installation
and paste the JRE path into the System Variable field. Type a semicolon (;) at the
end of the existing path.
6. On the Edit System Variable screen, click OK.
7. On the Environment Variables screen, click OK.
Example
An example of a JRE path is C:\Program Files\Java\jre1.5.0_07\bin\client.
Next steps
Now, you can install the Microsoft adapter.

Installing Microsoft adapter

Avaya has developed the Microsoft adapter to bridge the gap between the Avaya components
and the Microsoft components.
Prerequisites
Before you install the Microsoft adapter, install and configure the JRE environment.
The purpose of this task is to install and configure a key component for the Conferencing Plug-
in for Microsoft Live Meeting.
1. Click setup.exe.
The system starts the InstallShield wizard for Microsoft Adapter and displays the
Welcome to the InstallShield Wizard screen.
2. Click Next.
The system displays the license agreement screen.
3. On the Customer Information screen, type your user name and your company
name. Click Next.
4. On the Choose Folder screen, select the folder in which to install the application.
Click Next to accept the default installation path C:\Program Files
\Microsoft Adapter or click Browse to choose another location. Select the
folder and then click OK to accept the changes.
The system displays the Select a Program Folder screen.
By default, the Avaya BSMon service is installed in C: \Program Files\
Microsoft Adapter. If you change the default installation path of Microsoft
Adapter, you must also change the BSMon registry manually and start the service
manually.
5. To create a shortcut for Microsoft Adapter, ensure that Microsoft Adapter is selected
in the Existing Folders area and click Next.
The system displays the Ready to Install the Program screen.
6. Click Next and then click Install to start the installation.
When the installation is finished, the system displays the Installation Complete
screen.
7. Click Finish.
If you set the default path to C:\Program Files\Microsoft Adapter, the
system installs and starts the BSMon service.
If you set the path to a location other than the default, you must configure the
BSMon.

The configuration file is automatically installed. Avaya recommends making a copy

of this file or backing it up to another location. This file is useful in the event of an
upgrade or in the unlikely event of a system failure.
Next steps
Now, you can configure BSMon if you did not install the Microsoft adapter at the default location.
Configuring BSmon
that triggers a system reset or other corrective action if the main program enters a faulty state. If
you install the Microsoft adapter in any location other than the default location (C:
\ProgramFiles\Microsoft Adapter), you must configure BSMon.
Prerequisites
Before you configure BSMon, you must install the Microsoft adapter.
The purpose of this task is to change the registry entry and start-up type for BSMon.
1. Click Start > Run. In the Open field, type regedit and click OK.
The system displays the Registry Editor screen.
2. Navigate to MY COMPUTER > HKEY_LOCAL_MACHINE > SYSTEM >
ControlSet001 > Services > Avaya BSmonitor.
3. In the left pane, click AvayaBsMonitor > Parameters > 0.
In the right pane, the system displays the default path C:\ProgramFiles
\Microsoft Adapter\bin.
4. Right-click Path and then click Modify.
The system displays the Edit String screen.
5. In the Value data field, enter the path where the Microsoft Adapter application is
installed and click OK to save.
6. Start the BSMon service.
7. Open the Microsoft Windows Services screen.
By default, the startup type for the Avaya BsMonitor service is Manual.
8. Right-click Avaya BsMonitor and click Properties.
The system displays the Avaya BsMonitor Properties screen.

9. In the Startup type field on the General tab, select Automatic.

10. Click Apply and then click OK.
Next steps
Now, you can configure Microsoft adapter.
Uninstalling Microsoft adapter

When you uninstall Microsoft Adapter, you remove the application from the target computer.
You also remove all the related entries that you made during the installation.
Prerequisites
Before you uninstall Microsoft adapter, you must install it.
The purpose of this task is to remove the Microsoft adapter from your computer.
1. Close the Microsoft adapter.

2. Click Start > Settings > Control Panel > Add or Remove Programs
3. In the list of programs, click Microsoft Adapter and then click Change/Remove.
The system displays the Maintenance Welcome screen.
The process might experience an error at this point and displays the following
message:
1155: File C:\Program Files\InstallShield Installation
Information\ {37A789A9-EDDC-4500-9B7D-1B04F1 Gateway
Application.msi not found.
If you see this message, do not continue with this procedure. Instead, double-
click setup.exe to uninstall Microsoft Adapter.
4. Select Remove and click Next.
The system displays a confirmation box.
5. Click Yes.
The system stops the Avaya BSMonitor service and then displays the Uninstall
Progress screen. When the uninstallation is complete, the system displays the
Uninstall Complete screen.
6. Click Finish.

The application is removed from the target computer. The related entries that are
made during installation are also removed.
Microsoft adapter configuration

Before you can deploy the Avaya Conferencing Plug-in for Microsoft Live Meeting, you must
perform a number of configuration tasks.
These steps involve configuring security and configuring the connection to the Conferencing
application server.
Before you perform these tasks, you must purchase a security certificate from a trusted security
vendor, such as Verisign™.
Related topics:
Configuring TLS on page 486
Microsoft adapter administrative interface on page 488
Configuring the gateway settings on page 490
Configuring the logs settings on page 491
Configuration of Microsoft Office Communications Server 2007 R2 for MSAdapter on
page 493
Configuring TLS
Microsoft Adapter starts only if a valid Transport Layer Security (TLS) certificate exists.
Prerequisites
Before you perform this task, you may purchase a security certificate from a trusted security
vendor, such as Verisign, or you can install a security certificate from your Active Directory
Certificate Services.
The purpose of this task is to configure security for the Conferencing Plug-in for Microsoft Live
Meeting. Microsoft Adapter starts only if a valid Transport Layer Security (TLS) certificate
exists. The first thing that Microsoft Adapter does is try to read the default certificate file
acp.cer from the default path \\MSAdapter\config\acp.cer. If Microsoft Adapter does
not find the certificate or finds an invalid certificate, you see an error message. Microsoft
Adapter then opens in the default mode, from which you can provide the valid certificate path.

1. To provide the valid certificate path, click Gateway Configuration > Gateway
Settings.
2. On the Gateway Settings screen, click Browse and select the valid certificate path.
3. Click Save.
Microsoft Adapter stops and then restarts automatically with the new path.
4. Add the certificate to Microsoft Management Console:
To add the certificate to Microsoft Management Console:
a. Click Start > Run. In the Run screen, type mmc and click OK.
b. On the Console screen File menu, click Add/Remove Snap-in.
c. On the Add/Remove Snap-in screen, click Add.
d. On the Add Standalone Snap-in screen, click Certificates and then click Add.
e. On the Certificates snap-in screen, select Computer account and click Next.
f. In the Select Computer screen, select Local computer and click Finish.
g. On the Add Standalone Snap-in screen, click Close.
h. On the Add/Remove Snap-in screen, click OK.
5. Export the TLS certificate.
To export the TLS certificate:
a. Click Start > Run. In the Run screen, type mmc and click OK.
b. In the left pane of the Console screen, expand Certificates (Local Computer)
> Personal.
c. In the right plane, double-click Certificates.
d. Right-click the issued certificate and then click All Tasks > Export.
e. Click Next.
f. On the Welcome screen, click Next.
The system displays the Export Private Key screen. By default, the option No,
do not export the private key is selected.
g. Click Next.
The system displays the Export File Format screen. By default, the option DER
encoded binary X.509 (.CER) is selected.
h. Click Next.
i. On the File to Export screen, in the File Name field, enter the name of the
certificate file or click Browse to select the Config folder where Microsoft
Adapter is installed. Export the certificate file to that folder.
j. Click Finish.
If you rename the TLS certificate or change the location of the certificate and
then try to start Microsoft Adapter or if Microsoft Adapter is already running, the

application displays an error message that asks for the correct TLS certificate
file. You must then provide the correct certificate file details and restart the
application.
Next steps
Now, you can explore the Microsoft adapter interface.
Microsoft adapter administrative interface

The Conferencing application server is also known as a Conferencing bridge.
Use the administrative interface of Microsoft Adapter to perform the following functions:
• Add a bridge configuration to the Config file
• Add the Conferencing bridge
• Modify an existing bridge configuration
• Delete an existing bridge configuration
• Start a connection to an existing bridge
• End the connection to an existing bridge
• Set the log path and other parameters for log messages
• Set the gateway application configuration to configure port and other parameters such as
TLS connectivity and certificate details
• Display information that pertains to a particular Conferencing bridge
Microsoft adapter main screen
You cannot resize the screens of the administrative interface.
Interface component Description

Menu bar The menu bar includes the following menus:
• File
View Trace
Exit
• Gateway Configuration
Gateway Settings
Log Settings
• Conference Bridge
Add New
Edit
Remove

Start
Stop
• Help
About
Information panel This panel provides information about the

bridge configuration and any active
conferences on a bridge. You can select a
bridge node or a conference node on the
treeview pane.
When you select an audio conference
bridge, the application displays the
properties of that bridge.
When you select an audio conference from
the treeview pane, the application displays
the start time and the number of participants
for that conference.
Trace pane The trace pane displays all errors, alarms,
warning messages, and vital information
such as “Conference Server started.” To
display the trace pane, click View Trace on
the File menu. Avaya recommends that you
do not enable the trace pane if you enable
debug logging on a live production system.
Treeview pane The treeview pane consists of a tree with a
root node that is named “Conferencing
Bridges.” This pane shows the Conferencing
bridge that is on the gateway.
Use this pane to:
• Collapse and expand the root tree node to
view all the bridge nodes or bridge
configurations
• Add a bridge node to the root node
• Remove a bridge node from the root node
• Start a bridge connection
• Stop a bridge connection
• View a bridge configuration
• Modify a bridge configuration
• View conference information
Note:
See the notes in the next section.


Shortcut keys The administrative interface includes
keyboard shortcuts for some of the major
administrative tasks.
• Alt+F: Shows the File menu.
• Alt+G: Shows the Gateway Configuration
menu.
• Alt+C: Shows the Conference Bridge
menu.
• Alt+H: Shows the Help menu.
Notes in relation to the Treeview pane

• When you remove a bridge node, the application removes the bridge configuration
information from the configuration file and removes the bridge node from the root of the
tree pane. The bridge node cannot be removed when it is in a CONNECTED state.
• If a conference ends and there are no dial-in users in the conference, the application
deletes the conference child node from the bridge node.
• You cannot modify conference information.
Configuring the gateway settings

Gateway settings include port information and security information. You must configure the
gateway settings on the Microsoft adapter administrative interface to enable the successful
operation of the Conferencing Plug-in for Microsoft Live Meeting.
Prerequisites
Before you configure logs, you must install and configure the Microsoft adapter and the
The purpose of this task is to configure the adapter connection settings to suit your deployment
requirements.
1. On the Microsoft Adapter main screen, click Gateway Configuration > Gateway
Settings.
2. On the Gateway Settings dialog, complete the following information:
Field Description
Local Port The port on which Microsoft Adapter listens to the OCS
events. The default is 5060 for TCP and 5061 for TLS
connections.

Field Description
Polling Interval After a successful connection, Microsoft Adapter
continues to poll the audio conferencing bridge every n
seconds, where n is a number that you can configure. The
default is 30 seconds.
Re-Connection If a connection failure occurs, Microsoft Adapter tries to
Attempts re-establish the connection n number of times, where n is
a number that you can configure. The default is five
attempts.
Re-Connection If a connection failure occurs, Microsoft Adapter tries to
Attempt Interval re-establish the connection every n seconds, where n is
a number that you can configure. The default is five
seconds.
TLS Live Communications Server sends the SIP traffic to the
audio bridges on the secured TLS layer over the Internet.
TLS Path The path where the TLS Certificate exists.
3. Click Save to save the gateway settings.

If you complete all the fields correctly, the application adds the configuration on the
gateway. If you do not complete all the fields correctly, the system displays a warning
message that states the problem. If you correct the entries, the application then
saves the configuration on the gateway.
Next steps
Now, you can add the Conferencing application server (bridge) information to the Microsoft
adapter.
Configuring the logs settings

You can configure a number of parameters in relation to logs. Alternatively, you can accept the
default values. These logs are useful if issues arise with the operation of the Microsoft adapter.
Prerequisites
Before you configure logs, you must install and configure the Microsoft adapter and the
The purpose of this task is to change the default log settings to suit your deployment
requirements.

1. On the Microsoft Adapter main screen, click Gateway Configuration > Log
Settings.
2. On the Gateway Settings screen, complete the following information:
Field Description
Log Level Microsoft adapter logs messages and events based on the log
level that you select.
Log Path The path where the log files are sent. By default, the logs are
sent to the Logs folder. This Logs folder resides in the folder
where the application is installed. For example, if the
application is installed in D:\ACPGateway, the logs are stored
is D:\APCApplication\Logs.
Log File Microsoft adapter logs messages into multiple log files. When
Size the size of the file reaches the value that you set here, a new
file is created. The maximum size that you can set is 10 MB.
The default value is 2 MB.
Log Storage Microsoft adapter stores log files for n days, where n is a
Duration number that you can configure. The default is 30 days. The
system deletes files that are older than n days.
Free This is the free memory threshold of the Microsoft adapter. If
Memory the application memory utilization crosses the threshold value,
Microsoft adapter displays a warning message on the GUI for
administrators. The threshold value ranges between 100 MB
and 500 MB. The default value is 1 GB.
Free Disk This is the free disk space threshold of the Microsoft adapter. If
Space the log size crosses the threshold value, Microsoft adapter
displays a warning message on the GUI for Administrators.
The threshold value ranges between 1 GB and 10 GB. The
default value is 1 GB.
3. Click Save to save the log settings.

If you complete all the fields correctly, the application adds the configuration. If you
do not complete all the fields correctly, the system displays a warning message that
states the problem. If you correct the entries, the application then saves the
configuration.
Example
Example log levels:
The trace pane displays the messages and the events that Microsoft Adapter logs.
Microsoft Adapter supports the following four different modes to log messages and events:

Logs Description
(0) ERROR Logs the failed operations including failure to connect to a bridge.
(1) WARNING Logs all warnings that pertain to operations or events that can cause
errors, such as connection attempts and resource thresholds. By
default, the log level WARNING is selected when the application starts.
(2) INFO Logs all events and commands, such as SIP events, Bridge Control
API (BCAPI) commands and responses, BCAPI events, and
connection messages.
(3) DEBUG Logs all information-level items.
On the Log Settings screen, you can choose the option that you want.
ACP Server logs all messages and events into log files for debugging. The system stores
these log files in the path that you specify in the Log Settings screen. Microsoft Adapter
generates the following three types of log files:
File Description
CPPlogger.txt This log file contains the logs that are related to the
ACPBCAPIClient Interface module. This file describes the flow of
the commands and events between the ACPServer module and the
BCAPIClient module
BCAPImodule.txt This log file contains the commands as received from the ACP
Server module, and the events and responses received from the
Conferencingbridge.
MSAdapter.txt This log file contains all the messages that you see in the trace pane.
These logs are located in the Logs folder, which is automatically created when the Microsoft
Adapter application is started.
During the installation of the application, information about the installation process, such as,
errors and warnings are logged in the Installer log file Microsoft_Adapter_Logs.txt.
This log file is located in the Microsoft_Adapter_Logs folder. You should delete log files
in accordance with the parameters, Log File Size and Log Storage Duration.
Next steps
Now, you can configure Microsoft adapter with the Conferencing bridge.
Configuration of Microsoft Office Communications Server 2007 R2

for MSAdapter
To integrate the Microsoft adapter that Avaya has developed with Microsoft Office
Communications Server (OCS) 2007 R2, you must perform the configuration steps.

Firstly, you must administer certificates. Conferencing and Microsoft Office Communication
Server communicate using Transport Layer Security (TLS). For communication to take place,
Conferencing and Microsoft Office Communications Server 2007 R2 must exchange signed
server certificates each time a TLS session is opened. For more information on this task, see:
• Microsoft Office Communications Server 2007 R2 Document: Standard Edition
Deployment Guide
• Microsoft Office Communications Server 2007 R2 Document: Integrating Telephony with
Office Communications Server 2007 R2
• Microsoft Office Communications Server 2007 R2 Document: Enterprise Edition
Deployment Guide
• Microsoft Office Communications Server 2007 R2 Document: Active Directory Guide
All documents are available from www.microsoft.com.
Secondly, you must perform some configuration steps on the Microsoft Office Communications
Server (OCS) 2007 R2 for Microsoft adapter. The last configuration stage involves using the
Conferencing Manager administrative interface to configure the settings for your user client
machines.
Related topics:
Configuring the Microsoft Office Communications Server (OCS) 2007 R2 for MSAdapter on
page 494
Configuring the Microsoft Office Communications Server (OCS) 2007 R2 for

MSAdapter
Prerequisites
Before you configure the Microsoft Office Communications Server, you must install it in your
customer site. You must also install Conferencing and perform the install steps for the OCS.
The purpose of this task is to configure the Microsoft Office Communications Server (OCS)
2007 R2 for OCS adapter.
1. Navigate to Start > Administrative Tools > Office Communications Server 2007
R2.
2. Stop all services.
3. Open Pool Front End Properties.
The system displays the Properties screen.
4. On the Host Authorization tab, click Add.
The system displays the Add Authorized Host screen.

Microsoft adapter and the Conferencing application server
5. In the Server area, select Network address and enter the fully qualified domain
name (FQDN). The FQDN is the name of the server on which OCS adapter is
installed.
6. In the Settings area, select Throttle as Server and Treat as Authenticated.
7. Click OK.
8. On the Routing tab, click Add.
The system displays the Add Static Route screen.
9. Complete the following fields:
• Domain. Enter the FQDN of the server.
• Network address. Select and enter the FQDN of the server on which the OCS
adapter is installed.
• Transport. Select TLS.
• Port. Enter 5061.
10. Select Replace host in request URI.
11. Click Select Certificate and select the appropriate certificate.
12. Click OK.
13. Click Apply.
14. To start Microsoft Office Communications Server, right-click the Microsoft Office
Communications Server name and click Start All Services.
Next steps
Now you can use the Conferencing Manager administrative interface to configure the settings
for your user client machines.

You must add the details of the Conferencing application server (bridge) to the Microsoft
adapter, using the Microsoft adapter administrative interface.
When you add the details of the Conferencing application server (bridge) to the Microsoft
adapter, you must enter the following details:
Field Description
Conferencing A logical name for the Conferencing bridge. This name can contain a
Bridge Name maximum of 64 alphanumeric characters.

Bridge Type The type of bridge. The default is S6200. The S6200 is the bridge type
that applies to the Standard Edition of Conferencing.
DNIS Number The DNIS number to map to the Conferencing bridge. The DNIS
number must be unique. You cannot use the same DNIS for different
bridges. You must use one DNIS per bridge. This number can contain
from 1 to 16 digits and can include the question mark (?) as a wildcard
character. However, if you use wildcard characters if a multiple bridge
environment, ensure that you do not submit an ambiguous entry that
could match several bridges.
Bridge IP The IP address of the Conferencing bridge. This address must be
unique for the configuration.
User Name The user name that is associated with the Conferencing bridge. This
name can contain a maximum of eight alphanumeric characters.
Password The password that is associated with the user name for the
Conferencing bridge. This password can contain a maximum of eight
alphanumeric characters.
Related topics:
Adding the application server on page 496
Editing the application server on page 497
Removing the application server on page 498
Starting and stopping the application server on page 498
Adding the application server

You must provide the Microsoft adapter with the details of the Conferencing application server.
The Standard Edition of Conferencing supports a single server.
Prerequisites
Before you add the application server to the Microsoft adapter, you must install and configure
the Microsoft adapter and the Conferencing server.
The purpose of this task is to make the Microsoft adapter aware of the Conferencing application
server.
1. Open the Microsoft adapter administrative interface.

2. In the treeview pane click Conferencing Bridges.
3. Perform one of the following actions:
• On the main menu, click Conference Bridge > Add New.
• Right-click Conferencing Bridges. On the Context menu, click Add.

4. On the New Conferencing Bridge dialog, enter the bridge details.

5. Click Save to save the bridge configuration.
If you complete all fields correctly, the application adds the bridge configuration to
the gateway. If you do not complete all fields correctly, the system displays a warning
message that states the problem. Correct the entries. The application then saves
the configuration on the gateway.
Next steps
Now you can configure the Conferencing Plug-in for Microsoft Live Meeting for your users.
Editing the application server

Once you add the Conferencing application server, you can edit the details if you wish.
Prerequisites
Before you edit the application server on the Microsoft adapter interface, you must add it first.
The purpose of this task is to update the bridge details on the Microsoft adapter. You can edit a
bridge configuration only when the bridge connection is in the NOT CONNECTED state.
1. Open the Microsoft adapter administrative interface.

2. Click the bridge node.
• On the main menu, click Conference Bridge > Edit.
• Right-click the bridge node. On the Context menu, click Edit.
4. On the Edit Conferencing Bridge dialog, edit the bridge details.
5. Click Save to save the bridge configuration.
If you complete all fields correctly, the application adds the bridge configuration to
the gateway. If you do not complete all fields correctly, the system displays a warning
message that states the problem. Correct the entries. The application then saves
the configuration on the gateway.
Next steps
Now you can configure the Conferencing Plug-in for Microsoft Live Meeting for your users.

Removing the application server

You cannot delete an active bridge. You must stop the bridge if you want to delete it.
Prerequisites
Before you remove the application server on the Microsoft adapter interface, you must add it
first.
The purpose of this task is to delete the bridge details on the Microsoft adapter.
1. Take a note of the bridge details and stop the bridge if it is running.
2. In the treeview pane, click the bridge node that you want to remove.
• On the main menu, click Conference Bridge > Remove.
• Right-click on the bridge node. On the Context menu, click Remove.
4. On the Remove click OK to remove the bridge configuration.
Next steps
Now you can add a new Conferencing application server (bridge).
Starting and stopping the application server

At any time, you can start or stop the application server connection on the Microsoft adapter
administrative interface.
Prerequisites
Before start or stop the application server to the Microsoft adapter, you must add it.
The purpose of this task is to start or stop the application server on the Microsoft adapter.
• To start a bridge connection:
a. In the treeview pane, click the bridge node for which you want to start the
connection.
b. Perform one of the following actions:
- On the main menu, click Conference Bridge > Start.
- Right-click the bridge node. On the Context menu, click Start.

Configuring the individual client machines
If the connection is successful, the bridge node turns green and the Start button is
disabled. If the connection is unsuccessful, the system displays an error message.
• To stop a bridge connection:
a. In the treeview pane, click the bridge node for which you want to start the
connection.
b. Perform one of the following actions:
- On the main menu, click Conference Bridge > Stop.
- Right-click the bridge node. On the Context menu, click Stop.
If you stop the bridge connection, the bridge node is no longer green and the Stop
button is disabled. If active conferences exist on the bridge, the Stop button is
disabled.
Configuring the individual client machines

As a final stage in the installation and configuration of the Conferencing Plug-in for Microsoft
Live Meeting, you must enable the plug-in for each of the users in your deployment. You must
configure each client machine individually. You can use the remote desktop utility to access
each of the client machines. Alternatively, you can notify the users and provide them with the
instructions to install the plug-in themselves. The installation steps are not in the Using Avaya
Aura™ Conferencing guide.
Tip:
If you would like your users to perform this task, you can extract these steps using the
Document > Extract Pages feature in Adobe Acrobat Professional.
Prerequisites
Before you configure the settings on each machine, you must install and configure the Microsoft
adapter. You must also set up an on-demand conference on the CRS Front End for each of
your users. For more information on booking these on-demand conferences for your users,
see Operating Avaya Aura™ Conferencing which is available from support.avaya.com. It is a
good idea to distribute the Using Avaya Aura™ Conferencing guide to your users. This guide
describes how to use the Conferencing Plug-in for Microsoft Live Meeting.
You must also have the Microsoft Office Communications Server 2007 R2 installed in the
customer site.
The purpose of this task is to enable the Conferencing Plug-in for Microsoft Live Meeting for
each user.

1. Open the Microsoft Office Live Meeting console.

2. On the Microsoft Live Meeting Welcome dialog, click on the menu button icon in
the left corner of the title bar and select Open User Accounts.
3. Enter a sign-in name and click Advanced.
4. On the Advanced Connection Settings dialog, select Use these servers and enter
the Microsoft Office Communications Server (OCS) name or IP address.
5. On the same dialog, select Connect using TCP or TLS and click OK.
6. On the User Accounts dialog, click Test Connection.
Microsoft Office Live Meeting should verify your log-in information.
7. Click OK to complete the configuration steps.
8. On the Microsoft Live Meeting Welcome dialog, the Meet Now button now
displays.
9. Click Meet Now.
10. On the Live Meeting Audio Options dialog, select Dial in to the meeting using
a telephone conference service and enter the following details:
Field Description
Provider Enter the fully qualified domain name (FQDN) of the
Microsoft Office Communications Server 2007 R2 that is
installed in the customer site.
Toll-free The DNIS number to map to the Conferencing bridge. You
Number entered this information when you added the
Conferencing application server.
Toll Number Enter any toll number.
Participant Enter the user’s on-demand conferee code. This code
Code must match the code associated with the on-demand
conference which you created for this user on the CRS
Front End.
Leader Code Enter the user’s on-demand moderator code. This code
must match the code associated with the on-demand
conference which you created for this user on the CRS
Front End.
Next steps
Now it is a good idea to verify the Conferencing functionality in Microsoft Live Meeting.

Conferencing for Microsoft
Office Communicator
OCS adapter installation

A key component of the Conferencing Plug-in for Microsoft Office Communicator is the Office
Communications Server (OCS) adapter. Avaya has developed the OCS adapter to bridge the
gap between the Avaya components and the Microsoft components.
For the successful operation of the Conferencing Plug-in for Microsoft Office Communicator,
you must install and configure the OCS adapter.
There are a number of stages in the installation of the OCS adapter. You must perform these
steps in the order listed here:
• Configuration of the Java Runtime Environment (JRE) path
• Configuration of the .NET framework path
• Installation of Internet information services (IIS)
• Installation of OCS adapter on the server and on the client
• Configuration of OCS adapter
• Configuration of IIS
• Configuration of Microsoft Office Communications Server 2007 R2
• Configuration of Conferencing Manager
Software requirements for the OCS adapter
Software type Description

Operating system Windows 2008 Server, 32 bit, Standard Edition, with
Service Pack 2
IIS Internet Information Services 7
.Net framework .NET Framework version 3.5 Service Pack 1
Java Runtime Environment JRE 1.5 or higher
(JRE)

Installing/configuring Conferencing for Microsoft Office Communicator
Software type Description

Library Microsoft Ajax Library 1.0
Related topics:
Configuring JRE on page 502
Configuring .Net on page 503
Installing IIS on page 503
Installing OCS adapter on the server on page 504
Installing OCS adapter on the client on page 504
Configuring JRE
As with the Microsoft adapter, you must configure some Java settings for the successful
operation of the OCS adapter. The Java settings are called the Java Runtime Environment
(JRE).
Prerequisites
Before you configure JRE for the Conferencing Plug-in for Microsoft Office Communicator, you
must install and configure Conferencing and Microsoft Office Communicator.
The purpose of this task is to configure the JRE path for the Conferencing Plug-in for Microsoft
Office Communicator application.

2. Click the Advanced tab and click Environmental Properties.
3. In the System Variables panel of the Environmental Variables dialog, select the
Path variable and click Edit.
4. Copy the JRE path and paste it into Variable Value field.
5. Type a semicolon (;) at the end of the existing path.
6. Click OK on the Edit System Variable and Environment Variables dialogs.
Example
Example JRE path: C\Program Files\Java\Jre1.5.0\bin\client
Next steps
Now you can configure the .NET framework path.

OCS adapter installation
Configuring .Net
You must configure a .NET framework path.
Prerequisites
Before you configure .NET for the Conferencing Plug-in for Microsoft Office Communicator,
you must install and configure Conferencing and Microsoft Office Communicator.
The purpose of this task is to configure the .NET path for the Conferencing Plug-in for Microsoft
Office Communicator application.

2. Click the Advanced tab and click Environmental Properties.
3. In the System Variables panel of the Environmental Variables dialog, select the
Path variable and click Edit.
4. Copy the .NET path and paste it into Variable Value field.
5. Type a semicolon (;) at the end of the existing path.
6. Click OK on the Edit System Variable and Environment Variables dialogs.
Example
Example .NET path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Next steps
Now you can install Internet information services (IIS).
Installing IIS
Internet Information Services (IIS) - formerly called Internet Information Server - is a web server
application and set of feature extension modules created by Microsoft for use with Microsoft
Windows. Please refer to the Microsoft documentation for information on how to install IIS. The
documentation is available here: http://technet.microsoft.com/en-us/library/ee692294%28WS.
10%29.aspx.
Prerequisites
Before you install IIS for the Conferencing Plug-in for Microsoft Office Communicator, you must
install and configure Conferencing and Microsoft Office Communicator.

The purpose of this task is to install IIS for the Conferencing Plug-in for Microsoft Office
Communicator application.
1. Install IIS as described in the Microsoft documentation.

2. Ensure that the following three services are installed:
• ASP.NET
• .NET Extensibility
• ASP
Next steps
Now you can install the OCS adapter.
Installing OCS adapter on the server

Prerequisites
Before you install the OCS adapter, you must install and configure Conferencing and Microsoft
Office Communicator.
The purpose of this task is to install OCS adapter on the server.
1. Double-click the setup.exe file to start the installation.

2. Click Next on each dialog to accept all default options.
The installation completes within a few moments.
Note:
To uninstall the OCS Adapter, use the Add/Remove Programs feature on the
Windows Control Panel.
Next steps
Now you can configure the OCS adapter or install the OCS adapter on each client machine.
Installing OCS adapter on the client

As a final stage in the installation and configuration of the OCS adapter, you must install the
adapter on each of the client machines in your deployment. You can use a 'push' application

OCS adapter configuration
to push the files to each of the users in your network. Alternatively, you can notify the users
and provide them with the instructions to install the adapter themselves. The installation steps
are not in the Using Avaya Aura™ Conferencing guide.
Tip:
If you would like your users to perform this task, you can extract these steps using the
Document > Extract Pages feature in Adobe Acrobat Professional.
You must install the OCS adapter on each client machine.
Prerequisites
Before you install the OCS adapter, you must install and configure Conferencing and Microsoft
Office Communicator R2.
The purpose of this task is to install OCS adapter on each end user client machine.
1. Double-click the setup.exe file in client directory to start the installation.

2. Enter the OCS adapter server IP address or hostname if required.
3. Click Next on each dialog to accept all default options.
The installation completes within a few moments.
Next steps
You can now configure the OCS adapter.

There are two main tasks in the configuration of OCS adapter. The steps are:
• Configuring OCS adapter
• Configuring Internet Information Server (IIS)
You must install the OCS adapter before you begin these steps.
Related topics:
Configuring OCS adapter on page 506
Configuring IIS on page 507

Configuring OCS adapter

Prerequisites
Before you configure the OCS adapter, you must install it.
The purpose of this step is to configure the OCS adapter.
1. Ensure that the following directory is set to Allow Full Control:

C:\program files\Common Files\Avaya\logs
To check the setting on this directory:
a. Right-click the directory name and click Properties.
b. On the Logs Properties dialog, click the Security tab.
c. On the upper panel in the Security tab, select Users.
d. On the lower panel, click Allow Full Control.
2. Click OCSadapterAdm.exe.
OCSadapterAdm.exe is located here: C:\program files\avaya\avaya ocs
adapter\bin.
3. Configure these settings:
Setting Description
BridgeIP The Conferencing bridge IP address to which you
want to connect.
BridgeUserName The sign-in name for the bridge. You must
associate this value with the Conferencing bridge
sign-in.
BridgePassword The Conferencing bridge log-in password. You
must associate this value with the Conferencing
bridge sign-in.
reconnectionAttempts Number of reconnection attempts.
reconnectionInterval Length of reconnection interval.
pollBridgeInterval The interval between bridge polls.
RefreshInterval The refresh interval for the Microsoft Office
Communicator client.
LogPath The path of the log file.
MaxLogFileSize The maximum size of the log files.
DebugLevel The debugging level:

Setting Description
• (0) ERROR. This level logs failed operations,

such as the failure to connect to a Conferencing
bridge.
• (1) WARNING. This level logs warnings that
pertain to operations or events that can cause
errors, such as connection attempts and
resource thresholds.
• (2) INFO. This level logs events and commands,
such as SIP events, Bridge Control API (BCAPI)
commands and responses, BCAPI events, and
connection messages.
• (3) DEBUG. This level logs all information-level
items.
Manager e-mail Each user of Microsoft Office Communicator must

have a client account on the CRS Front End. This
client account is used to retrieve each users’ on-
demand conference details from CRS via SOAP
adapter.
Password This is the password of the client account.
For more information about creating client
accounts, see the Operating Avaya Aura™
Conferencing Guide, which is available from
support.avaya.com.
Next steps
When you complete these steps, you must configure Internet information server (IIS). You must
also configure the Conferencing Plug-in for Microsoft Office Communicator for your users.
Configuring IIS
Prerequisites
Before you configure Internet information services (IIS), you must install it.
The purpose of this task is to configure IIS.

1. On the server machine, navigate to Programs > Administrative Tools > Internet
Information Services (IIS) Manager.
2. On the main Internet Information Services (IIS) Manager screen, navigate to
<hostname> > Application Pools.
3. Right-click Application Pools and click Add Application Pool.
4. On the Add Application Pools dialog, enter OCSAdapterAppPool in the Name
field.
5. Select .Net Framework v2.050727 in the .Net Framework Version drop-down list.
6. Select Classic in the Managed Pipeline Mode drop-down list.
7. Click the Start Application Pool Immediately checkbox and click OK.
<hostname> > Application Pools.
9. Select OCSAdapterAppPool.
10. From the right panel window, select Advanced Settings.
11. Modify the settings as follows:
Options Description
Setting Recommended Value
Limit Interval (minutes) 1440
Identity NetworkService
Idle Time-out (minutes) 14400
Load User Profile False
Disable Recycling for Configuration Changes True
Regular Time Interval (minutes) 14400
12. Right-click Default Web Site and from the right-click menu, click New > Virtual
Directory.
13. On the Add Virtual Directory dialog, enter ocdadapterws in the Alias field, and
click browse to select the Avaya OCS Adapter folder where the OCS Adapter is
installed and click OK.
Internet Information Services > <hostname> > Sites > Default Web Site to
display the ocsadapterws properties.
15. Right-click on ocsadapterws and from the right-click menu, click Convert to
application to display the ocsadapterws properties.
16. Select OCSAdapterAppPool.

Configuration of the plug-in for your users
17. Ensure that ASP.NET is installed as follows:

a. On the main server manager screen, navigate to Roles, Web server (IIS).
b. Ensure that ASP.NET is installed.
18. Ensure that the TCP Port that you enter in IIS is an open port on the firewall, as
follows:
a. On the main Internet Information Services (IIS) Manager screen, navigate to
Default Websites.
b. On the right-click menu, select Properties.
c. On the Properties dialog, select the Website tab.
d. Make a note of the TCP Port.
e. Navigate to Control Panel > Windows Firewall.
f. On the Exceptions tab, click Add Port and enter a Port Name and the Port
Number from the TCP Port field.
Next steps
When you complete these steps, you must configure the Conferencing Plug-in for Microsoft
Office Communicator for your users.

You must use the Conferencing Manager administrative interface to configure the settings for
your user client machines.
Configure the following values:
Field Set to:

Attended ODO On
Originators Dial Out All
Self Mute Anyone
Moderator lecture On
When operators are creating on-demand conferences for the users, using the CRS Front End,
ensure that they select Security in the General Conference Options dialog. For more
information on booking on-demand conferences for the users, see Operating Avaya Aura™

Conferencing which is available from support.avaya.com. It is a good idea to distribute this

guide to operators.
Related topics:
Accessing Conferencing Manager on page 510
Accessing Conferencing Manager

This is the final task in the configuration of the Conferencing for Microsoft Office Communicator
plug-in.
Prerequisites
Before you configure the values in Conferencing Manager, you must install and configure the
other aspects of the OCS integration.
The purpose of this task is to update the default values that are displayed on the Conferencing
Manager administrative interface.

4. Click Configure.
8. Click Save.

Next steps
Now it is a good idea to verify the operation of the plug-in.


Chapter 34: Integrating with IBM applications
Overview of IBM integrations

Conferencing integrates with two IBM applications:
• IBM Lotus Notes
• IBM Lotus Sametime
The Conferencing Plug-in for IBM Lotus Sametime is a plug-in that provides audio for Web
conferences generated by IBM Lotus Sametime. The plug-in integrates IBM Lotus Sametime
data conferences with audio conferences generated by the Conferencing server.
The Conferencing Plug-in for IBM Lotus Notes is a plug-in that provides conference scheduling
and Web conferencing functionality using the existing appointments capability of IBM Lotus
Notes.
A plug-in is an application that links to a second application to extend the functionality of the
second application. The Conferencing plug-ins extend the functionality of IBM Lotus Notes and
IBM Lotus Sametime by offering features such as Click to Conference and Click to Call. For
more information on these features, see the Using Avaya Aura™ Conferencing Guide, which
is available from support.avaya.com.
Before you deploy either of the IBM plug-ins in your network, Avaya recommends creating an
on-demand conference for every IBM Lotus Notes or IBM Lotus Sametime user. You can
configure Conferencing to create a new on-demand conference for each new moderator that
it creates from an LDAP integration or a bulk upload from a existing database. In the
Conferencing environment, an application called Directory Services Client Application (DSCA)
manages LDAP integrations and an application called Import Utility manages bulk uploads
from existing databases. Alternatively, you can manually create new on-demand conferences
for clients using the CRS Front End. Once each IBM Lotus Notes user has an on-demand
conference, they can use IBM Lotus Notes to schedule conference meetings and invite
participants. Once each IBM Lotus Sametime user has an on-demand conference, they can
use IBM Lotus Sametime to start instant conferences and view talker indicator icons. In this
way, Conferencing extends the functionality in the IBM Lotus applications.
On-demand conference is a type of unattended conference that can start and end at any time.
An on-demand conference is a non reserved conference that is always available, on a first-
come, first-served basis.

Integrating with IBM applications
A conference profile is a collection of conference properties. An on-demand conference profile

is a collection of the properties associated with on-demand conferences. A scheduled
conference profile is a collection of the properties associated with a scheduled conference.
In the Conferencing environment, the IBM integrations are often referred to as groupware
integrations.
Security considerations
As a system administrator, you should be aware of potential security issues surrounding the
use of passwords between Sametime servers and the Conferencing servers. Avaya
recommends taking a number of precautions to minimize any potential security risks.
• A file called conference-adapter-configuration.xml identifies the Conferencing

application server or bridge that the plug-in for IBM Lotus Sametime uses. It is a good
idea to use an Avaya utility called bridgepassword to encrypt operator passwords for
the bridge defined in conference-adapter-configuration.xml. The Avaya utility,
bridgepassword, is located in the <Plug-in installation path>\Lotus
\Domino directory.
• Consider the following encryption issues:
- There is no encryption between Sametime servers and the Conferencing application
servers or media servers.
- The BCAPI connection is in clear text and not encrypted. Non encrypted data
includes:
BCAPI operator logins and passwords
Conference passcodes
Bridge commands and events
Participant names and telephone numbers
Important:
BCAPI is the bridge control application programming interface. It is an object-
oriented, programming interface that is written in Java. Programmers use BCAPI to
write applications that communicate with Conferencing application servers and media
servers.
• If your deployment is entirely within a LAN and does not cross the Internet, there are a
number of safeguards that you can implement.
- Isolate non encrypted information about the LAN by creating a secured network
segment.
- Set up coresident Sametime servers and Conferencing application or media servers.

Security considerations
- Prevent malicious interception.

- Ensure that the on-demand conferences that you create for each Sametime user
include the Lock Conference feature.
• If your deployment is outside of a LAN or WAN, there are a number of safeguards that
you can implement to provide access to Conferencing participants outside the LAN or
WAN without granting them LAN/WAN access:
- Secure Sametime access using HTTPS.
- Sametime administrators can:
Enable SSL / HTTPS in the Sametime Web interface.
Configure Sametime to encrypt all meeting data.
Related topics:
Encrypting operator passwords on page 515
Encrypting operator passwords

The bridgepassword utility encrypts passwords only in the conference XML document on
the Sametime server. However, passwords are sent in clear text over the network to the
application server or bridge.
Prerequisites
Before you encrypt operator passwords on the Sametime server, you must install and configure
the Conferencing Plug-in for IBM Lotus Sametime. Also, before you encrypt operator
passwords, you must configure and test the connectivity between the Sametime server and
the Conferencing application server with a plain text password.
The purpose of this task is to increase the level of security on the Sametime server.
1. On the Sametime server, navigate to <Plug-in installation path>\Lotus

\Domino.
2. Open the bridgepassword utility.
3. Enter the password using the following syntax:
bridgepassword bridge_id plaintext_password

The bridgepassword utility outputs a encrypted form of a password is in text-

encoded hexadecimal bytes.
Example
Here is an example of an encrypted password:
63:eb:3b:11:fd:48:8b:30:af:3e:cd:fe:96:98:72:3d:c:d9:fa:90:b3:be:17:38:f7:31:88:74.
It is important to note that repeated invocations of the bridgepassword command with the
same clear text password produces different encrypted forms.
Next steps
Now you can configure the remaining settings for the Conferencing Plug-in for IBM Lotus
Sametime.
On demand conference considerations

Before you deploy either of the IBM plug-ins in your network, Avaya recommends creating an
on-demand conference for every IBM Lotus Notes or IBM Lotus Sametime user. You can
configure Conferencing to create a new on-demand conference for each new moderator that
it creates from an LDAP integration or a bulk upload from a existing database. These two
methods are the most widely used methods when a customer has a large number of existing
users or clients. These two methods are efficient and quick. You can also create on-demand
conferences for each new user that you manually add to CRS Front End.
On-demand conferences are always available and require no additional scheduling. On-
demand conferences have a number of properties, such as whether the roll call option is
enabled, whether there are entry and leaving tones enabled, and so on.
The on-demand conferences that you create for your IBM Lotus Sametime and IBM Lotus
Notes users must have a number of particular properties in order to effectively operate with
the IBM applications. This table lists the important properties and the values that you should
set. Ensure that you set these values for the on-demand conferences that you create for your
IBM Lotus Sametime or IBM Lotus Notes users.
Option Description
Status Select 'enabled'.
Mode Select 'on demand'.
Frequency Daily (or 24X7)
Weekend Set to yes.

On demand conference considerations
Option Description
Conference name Provide a conference name.
Moderator code Include a moderator passcode for the conference.
Conferee code Include a conferee passcode for the conference. This code is the
only alphanumeric sequence that uniquely identifies a conference
scheduled on a bridge.
Block dialout The system blocks or allows moderator dial out.
Set to off, which allows the moderator to dial out.
PIN mode Select Conf PIN (conference PIN).
PIN list Use all capital letters to type in the name "ANYPIN."
Music When enabled, the system places the callers on hold and plays
music until an audio conference moderator enters the conference.
However, data-only participants can enter the Web conference
immediately. Set to off.
Start time and end time Set to 12:00 AM.
Security Set to on. This option must be enabled for the Lock Conference
feature to work.
Roll call Yes
Enter Tone & Leaving In the IBM Lotus Sametime environment, the enter and leaving
tones tones are not supported.
(Moderator) Hang up Optional. The settings are:
Off: Conferencing will extend the conference after the last audio
conference moderator hangs up. (Recommended)
On: Conferencing will end the meeting when the last audio
conference moderator hangs up.
Operator help Set to on.
Name record playback In the IBM Lotus Sametime environment, NRP is not supported.
(NRP)
Of all the on-demand conference properties, one property, in particular, is very important. This
is the PIN list property.
On-demand conference profiles must have a PIN list identified as ANYPIN for the Conferencing
system to use PIN codes to match application users with users that enter the conference
automatically.
The ANYPIN list provides the following functionality:
• A caller dials into the Conferencing application server or bridge. The bridge prompts the
caller to enter a passcode and to enter a PIN code.
• If callers enter any passcode along with the pound (#) sign or just the pound sign, the
system places the caller into the conference.

• IBM Lotus Sametime matches the PIN code the caller enters with the PIN codes displayed
in the Sametime interface. Also, IBM Lotus Sametime associates each caller line with a
data conference session. For example, a caller can enter passcode: 9876 and PIN: 5172.
• A moderator can create an association manually between the audio line and data session
of each caller. Specifically, a moderator can select one or more data users and one audio
participant, then right-click and select Associate Users from the submenu. Also, a
moderator can associate users by choosing the Tools > Audio > Associate Users
command from the menu bar.
So, in summary, you must set up your on-demand conferences to use an ANYPIN list. Using
ANYPIN, Conferencing can use PIN codes to match existing Web participants with audio
participants that dial directly into the audio conference server. Conferencing prompts users for
a PIN using the ANYPIN stored procedure and accepts whatever the user enters into the IBM
Lotus Sametime application. Specifically, Conferencing prompts a participant to enter a PIN
into IBM Lotus Sametime. The Conferencing plug-in forwards the PIN to Sametime, which
validates the entry against a list of predefined PINs. If there is a match, Sametime identifies
the phone line as a Sametime login. Conferencing accepts any PIN that callers enter along
with the pound (#) sign or no PIN at all and just the pound sign. Note that no validation occurs on
the audio conference server. Conferencing always places the callers into the conference.
Related topics:
Understanding some terms on page 337
PIN functionality on page 338
Scheduled conference considerations

A scheduled conference does not exist until a user schedules it. Unlike an on-demand
conference, a scheduled conference is not always available. For example, if all available
Conferencing resources are completely allocated to other conferences at a certain time, the
system does not allow a user to schedule their conference at that time. Users must set up a
scheduled conference by entering details such as start time, duration, and optionally,
conference properties.
You can configure a number of default properties for the scheduled conferences that IBM Lotus
Notes users create. A collection of properties is called a profile. You can configure a default
scheduled conference profile. The default scheduled conference profile contains all the
settings which will be enabled or available when a user books a scheduled conference using
IBM Lotus Notes.
This table shows the default properties for scheduled conferences. Avaya configure these
settings before they ship the software. To modify the settings in the default conference profile,
you must make configuration changes in the SOAP server. For more information, contact your

Scheduled conference considerations
Option Description
Status Select 'enabled'.
Mode In the default profile for scheduled conferences, the mode is Unattended.
In an unattended conference, callers dial into the bridge and enter a
passcode to join the conference that is managed by a Moderator. This
mode differs from the Attended mode. In an attended conference, an
operator places callers into the conference and remains available to
conferees and moderators for the duration of the conference.
Conference This is the title of the conference and is an alphanumeric string of less
name than 12 characters.
Moderator code Include a Moderator code for the conference. The user can specify this
code or, if they leave the Moderator Code field blank, Conferencing auto-
generates the code.
Conferee code Include a conferee code for the conference. The user can specify this
code or, if they leave the Conferee Code field blank, Conferencing auto-
generates the code.
Block dialout Conferencing blocks or allows moderator dial out. In the default
conference profile for scheduled conferences, it is set to off, which allows
the moderator to dial out.
PIN mode In the default conference profile for scheduled conferences, it is set to off.
If it is set to System PIN or Conference PIN, participants must enter a
PIN as well as a passcode before joining the conference. System PINs
are stored in a system-wide PIN code database. Conference PINs are
PIN codes from a specified PIN list.
PIN list This field is not enabled in the default conference profile for scheduled
conferences. PIN list stores the name of the Conference PIN file if
Conference PIN is selected from the PIN Mode field. If PIN Mode is set to
on and PIN list is idenfied as ANYPIN, Conferencing can use Sametime
PIN codes to match existing Web participants with audio participants who
dial directly into the audio Conferencing server.
Music The music is set to on. The music source is set to M1. When enabled,
Conferencing places the callers on hold and plays music until a moderator
enters the conference.
Security Set to Off in the default conference profile for scheduled conferences. The
feature, when enabled (On), allows a leader to add a second passcode
using DTMF commands prior to conference start. This feature must also
be enabled for the LOCK CONFERENCE feature to work.
Roll call Set to Off in the default conference profile for scheduled conferences. The
rollcall feature plays annunciator messages that prompt callers to record
their names and other relevant information when dialing into an
unattended or on-demand conference. There are a number of rollcall
settings such as INDVL, CONF, OPER, which correspond to playing the
rollcall to an individual, a conference, or the operator.

Option Description
Enter Tone & Set to Tone for scheduled conferences. Other values include:
Leaving tones Off: Omit tones or voice messages.
System: Use the pre-configured default setting.
Message: Play a voice message.
Tone & Message: Sound a tone and play a voice message.
(Moderator) Set to On for scheduled conferences. This means that Conferencing will
Hang up end the meeting when the last moderator hangs up.
If it is set to Off, Conferencing will extend the conference after the last
moderator hangs up.
Operator help Set to On for scheduled conferences. The Operator Help feature allows
or blocks help requests on a per conference basis.
If it is set to Off, Conferencing plays a user-defined annunciator message,
such as “Operator Assistance is not available” when Moderators or
Participants press *0 or 0.
Auto extend Auto Extend Duration is always set to On for IBM Lotus Sametime users.
duration
For more information on booking scheduled conferences, see Using Avaya Aura™
Conferencing, and Operating Avaya Aura™ Conferencing which are available from
support.avaya.com. It is a good idea to distribute these guides to your users.

Chapter 35: Configuring Conferencing for
IBM Lotus Notes
The Conferencing Plug in for IBM Lotus Notes

Note:
Avaya recommends that only certified IBM Lotus Domino experts configure the
Conferencing Plug-in for IBM Lotus Notes.
The Conferencing Plug-in for IBM Lotus Notes consists of a directory with the following
subdirectories:
Mail Template
- X.X.X
English
- X.X
English
- Jars
Notes_ST
On the IBM Lotus Domino server, these files are located here:
• Domino/Home/data/mail8.ntf. The location applies to deployments with IBM Lotus
Domino 8.0.2.
• Domino/Home/data/mail85.ntf. The location applies to deployments with IBM
Lotus Domino 8.5.
The Mail Template directory contains the Avaya mail template.
The Jars directory contains jar files that you must install on each client machine. The
notes_st_classpath.txt file in the Jars directory contains a line of text that should be added to
the notes.ini file of each user. The notes_st_classpath.txt also contains a line of text which
refers to the installation directory. By default, it refers to the C drive. If you install the
Conferencing Plug-in for IBM Lotus Notes on any other drive, such as the D drive, you must
change that line of text in notes_st_classpath.txt. Copy the Notes_ST subdirectory to the PC
of each user, or make it available to users on a shared network drive.

Configuring Conferencing for IBM Lotus Notes
Preparation for deployment
Note:
The Avaya e-mail template, which contains all the features for the Conferencing Plug in for
IBM Lotus Notes, is referred to as the Avaya template. The IBM Lotus Notes e-mail template
that your organization currently uses is referred to as your template. Engineers often refer to
the process of adding the Avaya customizations to your template as the merge process.
• The Avaya features are contained in the Avaya template. You must copy the Avaya
template to the IBM Lotus Domino server. You can then use the IBM Lotus Domino
Designer to open the Avaya template. Using IBM Lotus Domino Designer, you can also
open your template. Always open your template from the Domino\Data directory. Avaya
recommends that you save a back-up copy of your template before you begin.
• Every installation of IBM Lotus Notes is different. Depending on how you have configured
the security settings on your network, IBM Lotus Notes may display some security
information dialogs during the merge process. If this is the case, click Yes on these
information dialogs to progress to the next step.
• Many of the steps in the merge process involve copying sections of code from the Avaya
template and pasting them into your template. The relevant Avaya code is always
indicated as follows:
---START AVAYA CODE
<code appears here>
---END AVAYA CODE
In cases where you must copy multiple sections of code, the number of sections is
indicated as follows:
---START AVAYA CODE (Section 1 of 2)
<code appears here>
---END AVAYA CODE (Section 1 of 2)
...
...
...
---START AVAYA CODE (Section 2 of 2)
<code appears here>
---END AVAYA CODE (Section 2 of 2)
• If your template has no customizations, you can simply copy the Avaya template. If you
copy the Avaya template, you can skip many of configuration tasks but you must perform
the following:
- Configure the Click to Call feature
- Enable encryption between the SOAP server and the Notes client

Implementation considerations for IBM Lotus Notes
- Configure the jar files for IBM Lotus Notes
Implementation considerations for IBM Lotus Notes

At this point, it is a good idea to clarify a number of important implementation considerations
for IBM Lotus Notes. The Conferencing Plug-in for IBM Lotus Notes offers a number of options.
You can deploy the Conferencing Plug-in for IBM Lotus Notes in a deployment with IBM Lotus
Domino 8.0.2. or IBM Lotus Domino 8.5.
If your deployment has IBM Lotus Domino 8.0.2, you must configure a number of files, such
as script libraries, forms, and database scripts. You configure these files on the IBM Lotus
Domino server. After you configure these files, you must instruct your client users to perform
a number of configuration tasks on their individual computers or laptops. These client
configurations involve updating an initialization file. Users have to enter the location of a
number of Java files in a notes.ini file. So, essentially, there are server-side and client-side
configurations. This is referred to as deployment option A.
If your deployment has IBM Lotus Domino 8.5, you have a number of options:
• You can configure the files exactly as you would in a deployment with IBM Lotus Domino
8.0.2. In other words, you can configure script libraries, forms, database scripts, and so
on, on the IBM Lotus Domino server. You can then instruct your client users to configure
the notes.ini file on each individual machine. This is referred to as deployment option B.
• If the e-mail template that you use in your organization has no customizations, you can:
Configure the script libraries, forms, database scripts, in the regular way. You must
perform all the service side configuration activities. However, you do not have to instruct
your client users to perform any configuration tasks. There are no client-side
configurations. Instead, your deployment can simply use the Avaya e-mail template in the
place of your e-mail template. The Avaya e-mail template contains all the additional
features required by your client users to access the Conferencing Plug-in for IBM Lotus
Notes. This is referred to as deployment option C.
• If the e-mail template that you use in your organization contains customizations, you can:
Configure the script libraries, forms, database scripts, in the regular way. You must
perform all the service side configuration activities. In addition, you must perform some
additional steps on the IBM Lotus Domino server. These steps involve merging the Avaya
e-mail template features with your e-mail template. If you perform these steps on the IBM
Lotus Domino server, you do not have to instruct your client users to perform any
configuration tasks. There are no client-side configurations. This is referred to as
deployment option D.

Tip:
Select the option which best fits your deployment and keep the letter (A, B, C, or D) in mind as
you read the configuration steps that follow.
Configuring script libraries

Note:
Perform this task on the IBM Lotus Domino server. It is required for options A, B, C, and D.
Script libraries are generic pieces of code that can be used by one or more controls. Script
libraries are stored as modules in the Shared Code section in the IBM Lotus Notes database. In
relation to script libraries, you must complete two tasks: You must add a number of new Avaya
script libraries and you must make changes to a number of existing script libraries.
Prerequisites
Before you configure script libraries, you must obtain a copy of the Conferencing Plug in for
IBM Lotus Notes software.
The purpose of this task is twofold. This task involves copying the Avaya script libraries and
making some changes to a number of existing libraries.
1. Open the Avaya template and your template.

In IBM Lotus Notes 8.0.x, the script libraries are in Shared Code\Script
Libraries. In IBM Lotus Notes 8.5, the script libraries are in Code\Script
Libraries.
2. In the Avaya template, navigate to the Shared Code or Code folder and expand
the Script Libraries folder.
3. Select the following Avaya script libraries:
• BridgeInterface
• ScheduleFunctions
• OndemandFunctions
• WebFunctions
• UserBridgeDetails
• Utility
• MJS
4. Copy and paste the script libraries into the same location in your template.

Configuring script libraries
As you paste the script libraries, IBM Lotus Notes may display some information
dialogs.
5. Click Yes on any information dialogs.
7. In the Avaya template, navigate to the Shared Code or Code folder and expand
the Script Libraries folder.
8. Using the table as a guide, open each of the script libraries and copy the Avaya
code sections to the currently active mail template. In all cases, the Avaya code is
indicated
Script Library Section
Common [options]
CSExtAppDocSave functions
CSCalendarEntry [declarations] > CalendarEntry class
There is a single block of Avaya code in the onChange
method within the class.
CSUIViewClass viewDragPasteHandler
There are two sub-sections of Avaya code.
CSEventNotes [Options]
There is one section of Avaya code.
[DraftSpecificWork]
[Declarations] > CSEventNotes class
There are blocks of code in each of the following two
methods: The Function
OpenChangeRepeatDialog(nNoCancelOp As
Integar) As Integar method and also the Sub
QueryClose(bContinue As Variant) method.
CSEventsClass [Options]
[Declarations] > CsEvent class
There is a single block of Avaya code in the Sub
CSDocSave (vContinue As Variant) method within the
class.
9. Save all your changes.

10. Archive/compile your IBM Lotus Notes Database Template (NFT) file. You should
be able to access your original functionality.
Next steps
Now, configure the sub forms.

Configuring sub forms

Note:
There are two sub forms that you must copy. In IBM Lotus Notes 8.0.x, the sub forms are in
Shared Code\subforms. In IBM Lotus Notes 8.5, the sub forms are in Shared Elements
\Subforms.
Prerequisites
Before you configure the sub forms, it is a good idea to configure the script libraries.
The purpose of this task is to copy some sub forms from the Avaya template and paste them
into your template.

In IBM Lotus Notes 8.0.x, the sub forms are in Shared Code\subforms. In IBM
Lotus Notes 8.5, the sub forms are in Shared Elements\Subforms Libraries.
2. In the Avaya template, navigate to the Subforms folder.
3. Select the following Avaya sub forms:
• AboutBox
• ConferenceCallDetails
4. Copy and paste the script libraries into the same location in your template.
Next steps
Now, configure the calendar entry form.

Configuring the calendar entry form
Configuring the calendar entry form

Note:
As in the case of script libraries and sub forms, you must copy a number of sections from the
Avaya template to your template to enable your users to view the Avaya features.
Prerequisites
Before you configure the sub forms, it is a good idea to configure the sub forms.
The purpose of this task is to copy some items, such as tabs and buttons from the Avaya
template and paste them into your template.

2. Copy the Conference Call tab from the Avaya template to your template.
a. Navigate to the Description tab and right-click just after the Attach button
b. In the right-click menu, select Table Select > Entire Table.
c. With the entire table selected, right-click to display the right-click menu.
d. In the right-click menu, select Append > Row.
IBM Lotus Notes displays a blank tab.
e. Click the blank tab and right-click to display the right-click menu.
f. In the right-click menu, select Table Properties.
g. On the Table dialog, click the table row tab.
h. In the Tab Label and caption field, enter Conference Call.
i. Copy the contents of the Conference Call tab from the Avaya template to the
newly-created Conference Call tab in your template.
3. Copy the Click-to-Call button
a. Navigate to the top of the Avaya template form.
b. Navigate to the Click to Call variable and copy the it to your template
This is displayed on the Description tab below the body field. Click to Call
variable relates to an optional feature for your users. If you do not require this
feature, you do not need to copy the variable. If you require this feature, you
must copy the variable and you must also perform some additional configuration
tasks.

c. Save your template.

4. Copy Avaya objects code.
From the Avaya template, you must copy a number of tags from two objects. The
objects are (Globals) Appointment and Appointments (Form).
a. Open the Programmer’s Pane by selecting View > Programmer's Pane.
b. On the Avaya template, navigate to the Objects menu in the left panel.
c. Navigate to Global (Appointments) and copy the Avaya tags to your template.
In each case, the Avaya code is indicated.
• Options
• Declarations
• Initialize
d. Navigate to Appointments (Form) and copy the Avaya tags to your template. In
each case, the Avaya code is indicated.
• Querysave (there are several sections of Avaya code)
• PostOpen event
• QueryOpen event
• Remove Invitees (There is one section of Avaya code in the click event of
the Remove Invitees hotspot. In the Programmer’s Pane, it is called
hotspot.)
Tip:
Navigate to this code on the _Calendar Entry form, rather than in the
Programmer’s Pane. It is easier to find in the _Calendar Entry form.
e. Save your template.
5. Copy the action bar and menu.
Once you install the plug-in, the users in your organization will be able to access an
About dialog, a help URL, and their conference log-in details from the Action
toolbar and the Action menu. The following steps enable these menus.
a. Expand the Action bar entries on the right panel by selecting the View menu
and ensuring that the Action Pane item is selected.
b. Select the entry, Conference Call Options.
c. Copy and paste Conference Call Options entry into the Action bar entries
section your template.
d. Save all your changes.
e. Archive/compile your NFT file. At this point, users have access to a limited set of
Conferencing features.

Configuring database scripts
Next steps
Now, configure the database scripts.
Configuring database scripts

Note:
Database Scripts store generic pieces of code that can be used by one or more controls for
certain actions, such as Delete. Database scripts are stored as a module in the Other section of
the IBM Lotus Notes database. You must copy the database scripts from the Avaya template
and paste them into your template. In IBM Lotus Notes 8.0.x, the database scripts are in Other
\Database Resources\Database Script. In IBM Lotus Notes 8.5, the database scripts
are in Code\Database Script.
Prerequisites
Before you configure the database scripts, it is a good idea to configure the calendar entry form.
The purpose of this task is to copy some database scripts from the Avaya template and paste
them into your template.

2. On the Avaya template, navigate to the Other/Database Resources or the Code
menu.
3. Navigate to Database Script and copy the Avaya tags to your template. In each
case, the Avaya code is indicated.
• Options
• Querydocumentdelete
Next steps
Now, configure the Click to call feature.

Configuring the Click to Call feature

Note:
Prerequisites
Before you configure the Click to call feature, you must configure the calendar entry form.
When you configure the calendar entry form, one of the steps involves copying the Click to call
button. You must copy the Click to call button to make the Click to call feature available for
users.
The purpose of this task is to configure the Click to call feature. You must configure the Click
to call feature using the Conferencing Manager interface.

2. Navigate to Elements > Conferencing > Audio Conferencing > Bridge Features
> Bridge Features.
3. Set Attended ODO (Attended originator dial out) to on.
4. Navigate to Elements > Conferencing > Audio Conferencing > Conference
Features > Conference Settings.
5. Set Originator Dial Out to All.
6. Navigate to Elements > Conferencing > Client Registration > General >
Groupware Clients.
7. Set BCAPI Username to jc3.
This field is used to connect to the Conferencing application server using BCAPI.
Next steps
Now, enable encryption between the SOAP server and the IBM Lotus Notes client.
Related topics:

Enabling encryption between the SOAP server and the IBM Notes client

BCAPI username on page 217
Enabling encryption between the SOAP server and the IBM

Notes client
Note:
A Simple Object Access Protocol (SOAP) server allows Java objects and COM objects to talk to
each other in a distributed, decentralized, Web-based environment. There is a SOAP server
between the Conferencing solution and the IBM Lotus Domino server.
Prerequisites
Before you configure the sub forms, it is a good idea to configure the other aspects of the
solution, such as the Click to call feature.
The purpose of this task is to ensure that SOAP messages between the IBM Lotus Notes client
and the Conferencing application server or bridge are encrypted
1. In a Web browser, open https://<Conferencing application server IP address>:443/

axis
2. Click View Certificate on the Security Alert dialog.
3. On the Details tab of the Certificate dialog, click Copy to File….
4. Click Next on the Welcome to the Certificate Export Wizard dialog.
5. Select DER encoded binary.X509 (.CER) on the Export File Format dialog and
click Next.
6. Enter C:\temp\conference.cer in File name: field on the File to Export dialog
and click Next.
7. Click Finish on the Completing the Certificate Export Wizard dialog.
8. Open a Dos command line and enter the following command:
Cd c:\program files\IBM\Lotus\Notes\jvm\bin
keytool -import -trustcacerts -keystore ..\lib\security
\cacerts -alias sche -file c:\temp\conference.cer -storepass
changeit

SOAP message encryption is now enabled between the IBM Lotus Notes client and
the Conferencing application server.
Next steps
Now, configure logging.
Configuring logging
Note:
If you are running the IBM Lotus Domino 8.5 server with IBM Lotus Notes 8.5, you must perform
an extra step to ensure that the logging feature operates successfully in your deployment. This
step is not required for deployments that consist of IBM Lotus Domino 8.0.2 with IBM Lotus
Notes 8.0.2.
Prerequisites
Before you configure logging, it is a good idea to configure the other aspects of the solution,
such as enabling encryption between the SOAP server and the IBM Lotus Notes client.
The purpose of this task is to enable an audit trail or log for IBM Lotus 8.5 deployments.
1. Open the file in <Notes 8.5 installation directory>\jvm\lib

\security\java.policy.
2. In the main grant block, add the following line:
permission java.util.logging.LoggingPermission "control";
3. Save the file.
Next steps
Now, update your template for IBM Lotus Notes.

Template updates for IBM Lotus Notes
Template updates for IBM Lotus Notes

The IBM Lotus Notes e-mail template that your organization currently uses is referred to as
your template. You must synchronize updates to your template.
It is important to synchronize database files on the various client machines. Template design
updates enable the exchange of modifications in database documents between specified
databases. Each database is assigned a unique number called a replica ID. During the design
update process, the IBM Lotus Domino server looks for the replica ID of the database that
needs to be synchronized on a client machine. Once the IBM Lotus Domino server locates the
database on the client machine, it updates the database with the new modifications, which are
on the IBM Lotus Domino server.
Jar file configuration

Note:
Perform this task on the IBM Lotus Domino client machines. It is required for options A and B
only.
You must install several jar files as part of the installation of the Conferencing Plug in for IBM
Lotus Notes software. A JAR file (or Java ARchive) aggregates many files into one file.
Software developers generally use .jar files to distribute Java applications or libraries
The Simple Object Access Protocol (SOAP) client code is bundled into a jar file called
ExternalConferenceInterface.jar. ExternalConferenceInterface.jar is contained in the Avaya
mail template. ExternalConferenceInterface.jar contains all the code required to connect to the
SOAP server. From within the Avaya mail template, IBM LotusScript uses controls to call the
code within ExternalConferenceInterface.jar.
IBM Lotus Notes uses the Lotus to Java process to enable LotusScript to call Java methods
from within the LotusScript code. ExternalConferenceInterface.jar is contained in the master
template and is replicated into the client machine.
As a system administrator, you must distribute a setup application to the users on your network.
The setup file copies the extra jar files that are required for SOAP server access. The setup
file installs these jar files here:
C:\Notes_ST
The setup application obtains the Lotus Notes installation path from the System Registry. The
setup application also adds the JavaUserClasses property along with the classpaths of the
jar files to the notes.ini file.

The setup application adds the JavaUserClasses property along with the classpaths because
IBM Lotus Notes does not use the system classpath. Instead it uses the JavaUserClasses
property as a classpath.
You must install these jar files because the SOAP client uses these files and they are not
accessible from within the IBM Lotus Notes database.
Jar file list
The jar files which you need to install are as follows:
• axis.jar
• commons-discovery-0.2.jar
• commons-logging-1.0.4.jar
• jaxrpc.jar
• saaj.jar
• wsdl4j-1.5.1.jar
Initialization file modification
You must also add the following line to the end of the ini file:
JavaUserClasses=<NotesSchedulerPath>/
axis.jar;<NotesSchedulerPath>/
commons-discovery-0.2.jar;<NotesSchedulerPath>/
commons-logging-1.0.4.jar;<NotesSchedulerPath>/
jaxrpc.jar;<NotesSchedulerPath>/
saaj.jar;<NotesSchedulerPath>/
wsdl4j-1.5.1.jar
Note:
<NotesSchedulerPath> represents the path location where the jar files are copied. This task
must be performed manually. The system does not automatically apply these changes.
Using the Avaya e-mail template directly

Note:
Perform this task on the IBM Lotus Domino server. It is required for options C and D.

Merging the Avaya e-mail template with your e-mail template
Prerequisites
Before you use the Avaya e-mail template, you must perform all of the other configuration tasks
that are required for options C and D.
The purpose of this task is to make the Avaya e-mail template available for your client users.
The Avaya e-mail template will replace your existing template. For this reason, ensure that
your existing template has no customizations.
1. Open the Avaya template.

In IBM Lotus Notes 8.5, the script libraries are in Code\Script Libraries.
2. In the Avaya template, navigate to the Code folder and expand the Script Libraries
folder.
3. Select the MJS script library and double-click it to edit it.
4. In the declarations section, locate the following code:
' Flag to enable / disable the automatic Jar deployer
Public Const ENABLE_JAR_DEPLOYER = False
5. Change this code to True:
' Flag to enable / disable the automatic Jar deployer
Public Const ENABLE_JAR_DEPLOYER = True
Next steps
Now it is a good idea to verify that the Avaya template features are available for your clients.

Note:
Perform this task on the IBM Lotus Domino server. It is required for option D only.
Prerequisites
Before you merge the Avaya e-mail template with your template, you must perform all of the
other configuration tasks that are required for option D.

The purpose of this task is to make the specific Conferencing features from the Avaya e-mail
template available in your e-mail template. The automatic deployment of the Conferencing
Plug-in for IBM Lotus Notes is only successful if you install it in the default location on the C
drive (C:\Notes_ST). If you install it on the client machines in any other folder location, you
must update the script and set libpath to reference the folder location.

2. In your template, create a dummy form and add an action containing a script
(embedJarsInTemplate.lss) that will embed the libraries in a profile in your
template..
a. In IBM Lotus Domino Designer, on your template, navigate to Forms > New
Form.
b. From the menu bar, click Create > Action > Action.
c. Name the action and change the type to Lotusscript.
d. Paste the code from embedJarsInTemplate.lss.
embedJarsInTemplate.lss is in the installation directory, in the
resources folder.
3. On the menu bar, click Design > Preview in Notes.
4. When this form opens in IBM Lotus Notes, click on the action that you created.
IBM Lotus Notes embeds the libraries in the template.
5. Ensure that the profile document will be replicated correctly when you use an
application such as load convert to deploy the template to your client users:
a. Right-click on the database in IBM Lotus Domino Designer and select
Application > Properties.
IBM Lotus Domino Designer opens the Database properties window.
b. In the Database properties window, click on the Design tab and ensure that
Copy profile documents with design and Database file is a master
template are selected.
c. Ensure that Std8Mail is in the Template name field.
Next steps
For successful roll out, this automatic deployment feature requires permissions, including:
• Profile document access
• Access to the file system

• Access to embedded objects

• Access to the network
Avaya recommends that the template and its contents are signed by a trusted certifier on the
customer’s IBM Lotus Domino environment so that the end-user is not prompted to give these
permissions when they first use the template.


Chapter 36: Configuring Conferencing for
IBM Lotus Sametime
The Conferencing Plug in for IBM Lotus Sametime

The Conferencing Plug-in for IBM Lotus Sametime is a plug-in that provides audio for Web
conferences generated by IBM Lotus Sametime.
The Conferencing Plug-in for IBM Lotus Sametime leverages the functionality of the
Conferencing server and extends Conferencing features to IBM Lotus Sametime users.
For the successful operation of the Conferencing Plug-in for IBM Lotus Sametime, you must
enable some configuration settings on the Conferencing server. You can enable these settings
using the Conferencing Manager interface.
Conferencing Manager is a central management console. It enables you to manage the other
four virtual machines that comprise the Conferencing solution. Some of the fields on the
interface refer to Conferencing Manager as SMGR. You can access the Conferencing Manager
central management console by entering the Conferencing Manager virtual machine IP
address in a Web browser, as follows: http://<Conferencing Manager IP address>/SMGR. By
default, the username is admin and the password is admin123. You can change these
username and password settings at any time.
This table shows the settings which you must enable for the successful operation of the
Conferencing Plug-in for IBM Lotus Sametime.
Setting Description
PINs You must enable the PIN code functionality for on-demand
conferences.
Then when you are creating a default on-demand conference for all
of your IBM Lotus Sametime users, ensure that you select
Conference PIN as your PIN Mode and enter the phrase
ANYPIN in the PIN list field.
FLEX DAPI You must ensure that you have a Flexible Digital Auxiliary Port
resources Interface (FDAPI) for each IBM Lotus Sametime server connection.
Operator log ins You must ensure that you have a log in, at operator level, for each
IBM Lotus Sametime server connection.
Lecture You must enable Moderator Lecture Mode.

Configuring Conferencing for IBM Lotus Sametime
Setting Description
Self Mute You must enable Self Mute.
Early start minutes You must enable Early Start Minutes.
On demand You must allocate a certain percentage of ports to provide support
conferences for on-demand conferences by setting the On demand percentage
parameter.
Tip:
To identify the current build of the Conferencing Plug-in for IBM Lotus Sametime, open a
browser and enter the following: http://<Host name of IBM Lotus Sametime
server>/sametime/avaya-plugin-version.txt.
To identify the current build of IBM Lotus Sametime, open a browser and enter the following:
http://<Host name of IBM Lotus Sametime server>/sametime/
buildinfo.txt.
To uninstall the Conferencing Plug-in for IBM Lotus Sametime, use the Add/Remove
Programs feature on the Windows operating system.
Related topics:
Early start minutes on page 124
On demand conference considerations on page 516
PIN enablement on page 540
PIN enablement
If you wish to install the Conferencing Plug-in for IBM Lotus Sametime, you must enable PINs.
PINs are identification numbers that are unique to each participant.
You can enable PINs in your deployment, using the Conferencing Manager administration
interface. On the Conferencing Manager interface, navigate to Elements > Conferencing >
Audio Conferencing > Bridge Features > Scheduling and select Pin Code.
Related topics:
Understanding some terms on page 337

Creating log ins for IBM Lotus Sametime
Creating log ins for IBM Lotus Sametime

You must create an operator log in and password for the IBM Lotus Sametime server
connection to the Conferencing application server. BCAPI uses these operator log ins and
passwords to link to the Conferencing application server.
The Bridge Control API (BCAPI) is an object-oriented, programming interface, written in Java.
The API can be used by any application that can make a Java call.
You must also add the log ins to the conference-adapter-configuration.xml file.
Prerequisites
Before you create log ins for IBM Lotus Sametime, you must ensure that you have reserved a
Flex DAPI port for the IBM Lotus Sametime connection.
The purpose of this task is to enable the IBM Lotus Sametime server to connect to the
1. Reserve a Flex DAPI port using the Conferencing Manager interface by navigating
to the Elements > Conferencing > Audio Conferencing > System Config >
Miscellaneous > Flex DAPI configuration menu.
2. Create an operator sign in to represent the IBM Lotus Sametime connection to the
Conferencing server using the Conferencing Manager interface by navigating to the
Elements > Conferencing > Audio Conferencing > Bridge Features > Sign In
Users menu.
3. Add the operator log in's to the conference-adapter-configuration.xml file.
Next steps
Now you can enable strong encryption.
Related topics:
Operators on page 148
Configuring conference-adapter-configuration.xml on page 544

Enabling strong encryption

This task only applies to IBM Lotus Domino 8.0.x. By default, IBM ships Java with a security
policy that disables strong encryption. For the successful operation of Conferencing with the
new Avaya Conferencing Provider Application Programming Interface (ACP API), you must
enable strong encryption.
Prerequisites
Before you enable strong encryption, you must have an operational IBM Lotus Domino server.
The purpose of this task is to enable ACP API to communicate with IBM Lotus Sametime.
1. Stop the IBM Lotus Domino server.

2. Open a browser and navigate to http://www.ibm.com/developerworks/java/jdk/
security/.
3. Select the link that matches your version of Java, for example: http://www.ibm.com/
developerworks/java/jdk/security/50/ or http://www.ibm.com/developerworks/java/
jdk/security/60/.
4. Scroll down and click the IBM SDK Policy Files link.
5. On the Unrestricted JCE Policy Policy Files for SDK 1.4 page, register to create
an IBM identification and password and sign in using these details. If you already
have an IBM identification and password, sign in using these details.
6. Select Unrestricted JCE Policy Files for SDK 1.4.2 and click Continue.
7. Read the license that IBM provides and click I Agree if the terms are acceptable.
8. Click Download Now to download the unrestrict142.zip file.
9. Extract the local_policy.jar and US_export_policy.jar files.
10. Place these files in these directories and overwrite the existing files that have the
same filename:
<install directory>\jvm\lib\security
<install directory>\ibm-jre\lib\security
Next steps
Now you can make a configuration change on the IBM Lotus Sametime server to increase the
memory to the amount required by the ACP API.

Preparing the IBM Lotus Sametime server
Preparing the IBM Lotus Sametime server

This installation step is only required if you are running IBM Lotus Sametime 8.5.1. By default,
the IBM Lotus Sametime installer allocates 128MB of memory to the Java Virtual Machine
(JVM). To run the Avaya Sametime Conferencing Adapter, you must manually increase the
JVM memory allocation to 256MB. This step is required because the IBM Lotus Sametime
8.5.1 deployment uses Avaya Conferencing Provider Application Programming Interface
(ACP-API).
Prerequisites
Before you prepare the IBM Lotus Sametime server, you must have an operational IBM Lotus
Domino server and Sametime server.
The purpose of this task is to increase the memory allocation to enable ACP API to
communicate with IBM Lotus Sametime.
1. On the IBM Lotus Sametime server, click Start > Runand type regedit in the
Open field on the Run dialog.
2. Navigate to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lotus
\Sametime\MeetingServer\Services\.
3. In the right hand panel, right-click on the variable VMArguments.
4. From the right-click menu, select Modify.
5. On the Edit String dialog, edit the Value data field as follows:
Change -Xmx128m to -Xmx256m.
-Xmx128m appears at the start of the Value data string.
6. Click OK.
7. Restart the server.
Next steps
Now it is a good idea to take a look at some of the configuration options. Many of the
configuration options are stored in the conference-adapter-configuration.xml file, which is on
the IBM Lotus Domino server in the IBM/Domino/Home/Telephony_ext/MX/Lib folder.

Understanding some of the configuration files

There are four configuration files for the Conferencing Plug-in for IBM Lotus Sametime.
The four configuration files are called:
• conference-adapter-config.xml
• dial-plan.xml
• SametimeDiagnostics_Telephony. properties
• log4j.properties
conference-adapter-config.xml and dial-plan.xml are located in IBM/Domino/
Home/Telephony_ext/MX/Lib.
SametimeDiagnostics_Telephony. properties and log4j.properties are

located in IBM/Domino/Home.
Configuration File To Configure

conference-adapter-config.xml The Conferencing Adapter on a per-bridge basis
to enable IBM Lotus Sametime to communicate
with each audio conference server (bridge). This
component primarily involves configuring bridge
settings, user names and passwords, dial-in
numbers, and announcement messages.
Note:
support multiple bridges.
dial-plan.xml The dialing plan rules on mapping telephone
numbers dialed by participants to numbers that the
audio server can readily dial.
SametimeDiagnostics_Telephony. The IBM Lotus Sametime telephony logs
properties generated by the Conferencing plug-in.
log4j.properties The BCAPI log verbosity generated by the BCAPI.
Configuring conference-adapter-configuration.xml
Typically, the IBM Lotus Domino server and the IBM Lotus Sametime server are co-resident
on the same machine. The conference-adapter-configuration.xml is located on this machine.

Prerequisites
Before you configure conference-adapter-configuration.xml, you must install the Conferencing
Plug-in for IBM Lotus Sametime.
The purpose of this task is to customize the features and functionality of the Conferencing
Plug-in for IBM Lotus Sametime to match the requirements of your deployment site.
1. On the IBM Lotus Domino/Sametime server machine, navigate to IBM/Domino/

Home/Telephony_ext/MX/Lib and open the conference-adapter-
configuration.xml file.
2. Update the values in the conference-adapter-configuration.xml file to match your
requirements, as described in the following table.
Most fields in the configuration file have values set to CHANGEME in the template.
You must update the CHANGEME values before using the plug-in.
Entry Value
ID <id>
A unique identifier for the bridge. Example:
FrontRunner_CS700#1
Display name <display-name>
An easily identifiable display name for the bridge. IBM
Lotus Sametime displays this entry in the interface. The
bridgetest utility reveals the name.
Host name <host-name>
The IP hostname of the bridge. Example:
CS7001.dr.frontrun.com or 10.100.10.100.
Implementation <impl-type>
type The type of API used. Do not change this value. Use:
MODAPI
Server port <server-port>
The IP port on which the BCAPI server is running.
Example: 20002
Note:
The default value is 20002 and must rarely be
changed, if ever.
jndi-service- <jndi-service-location>
location The JNDI is used by BCAPI to get a session object to
connect to a conference server. Specifically, this string
contains an IP address and the port number of a server
as shown. Example: jnp://123.45.67.123:1099. This
entry is ignored by other servers.
Client events port <client-events-port>

Entry Value
The IP port on which the IBM Lotus Sametime plug-in
receives bridge events. Example: 5020. The default is
5020 for the first configured bridge. For subsequent
bridges, add one to this number, such as 5021, 5022,
5023.
Note:
Client state port <client-state-port>
The IP port on which the IBM Lotus Sametime plug-in
receives bridge state updates. Example: 5040. The
default is 5040 for the first configured bridge. For
subsequent bridges, add one to this number, such as
5041, 5042, 5043.
Note:
SIP support <sip-supported>
A flag for SIP support. Do not change this value. Use:
false
Verify that this value is set to false for this release.
Maximum number <max-conferences>
of supported The maximum number of conferences that the IBM
conferences Lotus Sametime plug-in is allowed to start on the bridge.
This value can be set to any number less than or equal
to the maximum number of conferences that the bridge
can support. Example: 500.
Auxiliary dial-in <auxilliary-dial-in-number>
number An auxiliary dial-in number for the bridge that is used
only for display purposes only. IBM Lotus Sametime
plug-in software never dials the number. There might be
more than one of these numbers for each bridge. This
number must be in an easily readable form. Example:
(123) 555-1212.
Toll dial-in <toll-dial-in-number>
number A toll dial-in number for the bridge that is used only for
display purposes only. IBM Lotus Sametime plug-in
software never dials the number. There might be more
than one of these numbers for each bridge. This number
must be in an easily readable form. Example: (123)
555-1212 or NONE.
Toll-free dial-in <toll-free-dial-in-number>
number A toll-free dial-in number for the bridge that is used only
for display purposes only. IBM Lotus Sametime plug-in

Entry Value
software never dials the number. There might be more
than one of these numbers for each bridge. This number
must be in an easily readable form. Example: (800)
555-1212 or NONE.
Announcement <announcement-mapping>
mapping A mapping of the location of an IBM Lotus Sametime
data user to a recorded bridge announcement. There
might be more than one announcement for each bridge.
Each announcement mapping has the following sub
fields:
<language>: a two-letter ISO code for the language of
the location Example: en for English
<country>: a two-letter ISO code for the country of the
location, for example: Example: US for the United
States
<announcement-number>: the index of the recorded
announcement for the location on the bridge Example:
242
The defaults are listed but the values can be changed
if desired.
The announcement indices must be valid and match the
audio server configuration.
3. Create operator log ins (sign ins) as described in the following table.
The log ins that you create here must be identical to the operator log ins that you
created on the Conferencing application server using the Conferencing Manager
administrator interface.
Entry Description
Operator <operator-login>
login name The operator login name for the plug-in, which must not be
used for any other purpose. Operator names and passwords
must be identical to those defined on the bridge. Example:
gpwr1 or gpwr2.
Operator <operator-password>
password This value can be set to the clear text operator password. The
password can later be encrypted with a command-line utility.
Example: 63:eb:3b:11:fd:48:8b:30:af:3e:cd:fe:
96:98:72:3d:c:d9:fa:90:b3:be:17:38:f7:31:88:74.
The encrypted values display as hexadecimal-encoded
numbers.
Operator <operator-number>
number A number that specifies the channel the plug-in uses to log in
to the bridge. Set this value to:
• A maintenance channel to dedicate the channel for use only
with the plug-in. For example, enter a number between one

Entry Description
and the number of operators that the bridge can

accommodate. Example: 3
• Zero (0) to automatically assign the channel to the next
available operator number. Example: 0
4. Save and close the file.

5. Restart the IBM Lotus Domino/Sametime server.
Restart the IBM Lotus Sametime server to reload the plug-in if an audio conference
server is added or deleted. Also, restart IBM Lotus Sametime if the configuration or
parameters are modified. The changes take effect after the IBM Lotus Sametime
server restarts. Restart to reconnect to newly configured bridges for the changes
take effect immediately.
Next steps
Now it is a good idea to open the Client Registration Server (CRS) Front End application to
create a CRS client for the IBM Lotus Sametime server and clients for each IBM Lotus
Sametime user.
Related topics:
Creating log ins for IBM Lotus Sametime on page 541
Working with the CRS to create clients

In order for the Conferencing Plug-in for IBM Lotus Sametime to operate successfully, you
must create a Client Registration Server (CRS) client for the IBM Lotus Sametime server. You
must also create CRS clients for each IBM Lotus Sametime user in your deployment.
You must create a CRS client for the IBM Lotus Sametime server in the CRS because the IBM
Lotus Sametime server makes scheduled conference bookings on behalf of the IBM Lotus
Sametime users. The IBM Lotus Sametime server must be represented in the CRS. Similarly,
each IBM Lotus Sametime user in your deployment must have their own account on the CRS.
The Operating Avaya Aura™ Conferencing Guide, which is available from support.avaya.com
describes how to create clients using the CRS Front End.
The requirements of the CRS clients vary depending on whether you are creating the CRS
client for the IBM Lotus Sametime server or the CRS clients for the IBM Lotus Sametime users
in your deployment.
You can also use the following table as a guide when you are creating the CRS client for the
IBM Lotus Sametime server:

The IBM Lotus Sametime dialing plan
Entry Description
adaptor-user- When you create a CRS Client for the IBM Lotus Sametime server, you
name must ensure that the E-mail field associated with the CRS Client is identical
to the adaptor-user-name field in the conference-adapter-
configuration.xml file for the IBM Lotus Sametime server.
adaptor- When you create a CRS Client for the IBM Lotus Sametime server, you
password must ensure that the Password field associated with the CRS Client is
identical to the adaptor-password field in the conference-adapter-
configuration.xml file for the IBM Lotus Sametime server.
When you are creating the CRS client for each IBM Lotus Sametime user in your deployment,
the values in the conference-adapter-configuration.xml file are not significant. However, the
name of the CRS client must match the name on the IBM Lotus Sametime account for each
user. For example, if the name on the IBM Lotus Sametime account is John Smith, you must
create a CRS client with the name, John Smith.
When you finish creating the clients on the CRS Front End, restart the IBM Lotus Domino/
Sametime server.
For more information on creating, editing, and deleting clients, see the Operating Avaya Aura™
Conferencing Guide, which is available from support.avaya.com.
Now, it is a good idea to configure the dialing plan.

For convenience, users might want to enter telephone numbers similar to the way they normally
dial. However, the Conferencing server, which dials the number for the caller, might be located
elsewhere within the telephone network. If the number dialed by the caller does not work from a
particular location, the Conferencing Plug-in for IBM Lotus Sametime provides a configurable
dialing plan. The dialing plan converts user-dialed numbers into a form that the Conferencing
server can readily dial, such as the international E.164 format. The Conferencing Plug-in for
IBM Lotus Sametime passes the E.164, a fully qualified form of a user-dialed number, to the
Conferencing server. The Conferencing server then translates the number into a form that the
public telephone network can dial.
Common acronyms used in the dialing plan
Acronym Definition
AC Area Code
CC Country Code
IDP International Dialing Prefix
LP Local Prefix

Acronym Definition
LTP Leading Trunk Prefix
NDC National Destination Code
NSN National Significant Number
PBX Private Branch Exchange
PSTN Public Switched Telephone Network
SN Subscriber Number
TAP Trunk Access Prefix
TP Trunk Prefix
How the dialing plan works

The Conferencing Plug-in for IBM Lotus Sametime and one or more connecting bridges share
the administration of a conversion mechanism for the dialing plan. The Conferencing Plug-in
for IBM Lotus Sametime converts incoming dialed numbers to a fully qualified E.164 format
and passes the form to the audio Conferencing application server (or bridge). The
Conferencing bridge converts the E.164 format to a dialed form that the PBX or voice network
can recognize. Note that the administrator must configure the dialing plan for the following
components.
Component How to configure

Conferencing Plug-in for IBM Lotus Sametime User-dialed to E.164
Conferencing application server E.164 to network-dialed
The following sections describe specific E.164 conversion cases and provide accompanying
examples. If converting to the E.164 format, administrators must configure IBM Lotus
Sametime and all connecting bridges to interpret and dial incoming E.164 numbers correctly.
The conversion of a dialed number to E.164 format is a two-step process. The IBM Lotus
Sametime dialing plan mechanism must:
• Match an incoming number against a sequence of patterns to determine the originating
location and intended destination of the caller.
• Modify the outgoing-string digits so that the number is fully qualified but does not contain
any dialing prefixes like TP, IDP, or TAP.
The IBM Lotus Sametime installation utility installs a default dial-plan.xml file. The dial-
plan.xml file defines a set of rules for mapping input digit strings to output digit strings. dial-
plan.xml also contains commented-out examples of how to use each mapping rule to achieve
the desired results. In addition, this XML file implements a pass-through policy, for example,
an input number can be returned unchanged.
Note:
The Standard Edition of Conferencing does not support multiple bridges.

Related topics:
Dialing plan mapping rules on page 551
Configuring the dialing plan for campus sites on page 552
Configuring the dialing plan for local cities on page 553
Configuring the dialing plan for local countries on page 554
Configuring the dialing plan for international sites on page 556
Configuring the dialing plan for residential sites on page 556
Mapping incoming dialed numbers to defined bridge numbers on page 557
Dialing plan mapping rules

There are two forms of mapping rules, one for fixed-length strings and one for variable-
length strings.
Mapping Description
Rule
Fixed length Basic format example:
<mapping match="91303XXXXXXX" replace="1303XXXXXXX"/>
This format takes an input string that starts with 91303 and is exactly 12 digits
long. The format produces an output string that starts with 1303 and reduces
the string to 11 digits. In the basic format example, the mapping process
removes the leading number, 9.
Variable Basic format example:
length <mapping match="9011*" replace="*"/>
This format takes an input string that starts with any length <n> that starts
with 9011. The format produces an output string that starts with a string length
of N-4 and removes the leading 9011 digits. In the basic format example, the
mapping process removes the leading number, 9
The dialing plan mechanism processes a sequence of rules for each input number in the dial-
plan.xml. The processing of the rule sequence is in order, from top to bottom, until a match is
found. Once a match is found, the rule output is returned immediately with no further processing
of any subsequent rules.
The rules file in the default dialing plan defines a single rule that matches any input number
and returns the number unchanged. However, the single rule immediately stops further
processing of the dialing plan. To use the single rule, place the rule at the end of the rules file to
terminate processing of dialing plan. Administrators can remove the single rule, if desired. If
the rule is removed, the system sends a failure notification to the caller if no other rules match
the input number.
Technical support representatives can modify the dial-plan.xml file to suit the following
scenarios: Configuring the dialing plan for local campus sites, local cities, local countries,
international sites, and residential sites.

Configuring the dialing plan for campus sites

Most organizations support abbreviated dialing within a single campus location or across
several campus locations. The IBM Lotus Sametime dialing plan can support a local campus
deployment under the following conditions:
• The abbreviated dialing plan is identical across all locations served by an IBM Lotus
Sametime instance.
OR
• IBM Lotus Sametime can uniquely identify the dialing plans of all independent campuses
served by IBM Lotus Sametime by dialed number length or common prefix.
Prerequisites
Before you configure dial-plan.xml, it is a good idea to configure conference-adapter-
configuration.xml.
The purpose of this task is to configure a dialing plan.
1. Locate and open the dial-plan.xml file.

2. Use the rules in the example below to set up a campus-local destination. These
rules are mutually exclusive. Use either example A or one of the examples in
example B.
• Example A
<mapping match="XXXXXXX" replace="XXXXXXX"/>
• Example B
<mapping match="XXXX" replace="1720444XXXX"/>
<mapping match="852XXXX" replace="1732852XXXX"/>
<mapping match="207XXXX" replace="3531207XXXX"/>
3. Use these rules to set up an abbreviated dialing plan that can pass through all
seven-digit dialed numbers. Note that abbreviated telephone numbers can pass
through the IBM Lotus Sametime dialing plan unchanged.
Rule examples specify where a particular campus site is located in the telephone
network.
• CC="1", NDC="720", LP="444"
This example identifies a campus in Denver, CO, USA, with 4-digit abbreviated
dialing.
• CC="1", NDC="732", SN="852XXXX"

This example identifies a campus in Lincroft, NJ, USA, with 7-digit abbreviated
dialing.
• CC="353", NDC="1", "SN=207XXXX"
This example identifies a campus in Dublin, Ireland, with 7-digit abbreviated
dialing.
These examples specify the dialing campus locations for Example B, above.
Abbreviated dialing schemes similar to the previous example are often not
coordinated across sites. Therefore, non coordinated sites are likely to trigger
ambiguities if the same IBM Lotus Sametime instance serves multiple sites. The
only solution is to force callers to use longer numbers like 9720444XXXX instead
of XXXX as shown in the previous example.
The local campus switching system must recognize a longer form for local numbers.
If the switching system does not, there is no solution that allows IBM Lotus
Sametime to dial the numbers. As a work around, use another external mechanism,
such as the bridge TUI, which requires the caller to know the dialing plan of the
bridge.
The changes take effect after the IBM Lotus Sametime server is restarted. The next
number dialed uses the updated mappings.
Configuring the dialing plan for local cities

A local city dialing destination is defined as either inside or outside a targeted local campus,
and does not require a TP dialing prefix.
Prerequisites
configuration.xml.

2. Use the following rule examples to determine the location of the dialed number. The
rules try to match the dialed number against valid destinations at each campus
location.
Example Rules
• TAP="9", CC="1", NDC="303,720", SN="538XXXX"

This example identifies a campus in Denver, CO, USA.

• TAP="9", CC="61", NDC="2", SN="8XXXXXXX,9XXXXXXX"
This example identifies a campus in campus in Sydney, Australia.
• TAP="9", CC="353", NDC="1", SN="XXXXXXX"
This example identifies a campus in Dublin, Ireland.
3. Use the following rule examples to allow all campuses to dial any local city number.
Example Rules
• <mapping match="9303XXXXXXX" replace="1303XXXXXXX"/>
• <mapping match="99XXXXXXX" replace="6129XXXXXXX"/>
• <mapping match="91XXXXXXX" replace="3531XXXXXXX"/>
When the file gets saved, the changes take effect immediately. The next number
dialed uses the updated mappings.
Example
Note that these rules are modifiable and, therefore, easily broken. For example, adding
another city with an eight-digit local number starting with 1, 8, or 9 can cause ambiguity in
the rule set. A possible solution is to add more digits but do not overlap the numbering
schemes. For example, the IBM Lotus Sametime dialing plan cannot resolve numbers when
a local number in two different cities are exactly the same.
Configuring the dialing plan for local countries

A local country dialing destination is defined as outside the targeted local campus but inside
the targeted country, and requires a TP dialing prefix.
Local country dialing is usually synonymous with long distance dialing within a country. Similar
to local city dialing, the IBM Lotus Sametime dialing rules must determine the dialed number
location. To do this, the dialing rules must match the dialed number against valid destinations at
each campus location. However, large countries usually have an exhaustive number of
potential destinations. As a work around, set up rules so that callers can dial numbers from a
small number of frequently used area codes. The area codes must be near to campus locations
located within the enterprise and country.

Prerequisites
configuration.xml.

This list shows how to determine the location of the dialed number by matching the
dialed number against valid destinations at each campus location.
• TAP="9", TP="1" CC="1", NDC="303,720"
This example identifies a campus in Denver, CO, USA.
• TAP="9", TP="0", CC="61", NDC="2", SN="8XXXXXXX,9XXXXXXX"
This example identifies a campus in campus in Sydney, Australia.
• TAP="9", TP="0", CC="353", NDC="1", SN="XXXXXXX"
This example identifies a campus in Dublin, Ireland.
2. Use the country-local rules to allow specified cities to dial any location within a state
or country. Combine the country-local rules with the city-local rules from the previous
section.
This list shows how to set up the rules so that Denver callers can dial any location
within the state of Colorado. Also, Dublin callers can dial any location within the city
of Cork.
• <mapping match="91719XXXXXXX" replace="1719XXXXXXX"/>
• <mapping match="91970XXXXXXX" replace="1970XXXXXXX"/>
• <mapping match="9021XXXXXXX" replace="35321XXXXXXX"/>
The changes take effect after the IBM Lotus Sametime server is restarted. The next
number dialed uses the updated mappings.

Configuring the dialing plan for international sites

Prerequisites
configuration.xml.

• International numbers are usually the easiest to define in a dialing plan because they
include fully qualified country codes. In most cases, only the TAP and IDP need to be
removed.
For example, the following rules can resolve international numbers that are dialed from
most worldwide locations.
- <mapping match="9011*" replace="*"/>
- <mapping match="900*" replace="*"/>
• Some countries use an international dialing prefix that is indistinguishable from that of
other countries. For example, Australia uses 0011. A possible solution is to map dialed
numbers from the unique countries to other frequently dialed countries first, and then
use a catch-all rule to map numbers for other countries, as shown.
- <mapping match="9011*" replace="*"/>
- <mapping match="900111*" replace="*"/>
- <mapping match="90011353*" replace="*"/>
- <mapping match="900*" replace="*"/><!-Most world places to somewhere else->
To summarize the rules defined in the previous example, Australians can dial North
America and Ireland. However, all other international calls dialed from Australia fail.
Note that callers located in other countries can dial any worldwide location.
Configuring the dialing plan for residential sites

At times, users might want to dial into a IBM Lotus Sametime conference from outside the
office. In this scenario, users do not need to dial a TAP. In most cases, users can dial numbers in
the same way they do at work. However, if users try to dial numbers in the same way they do at
home, the dialing process fails because of the dialing rules. This task describes how to
configure for dialing from outside the office.

IBM Lotus Sametime logs
Prerequisites
configuration.xml.

2. Copy all the rules except the campus-local rules.
3. Remove all the TAPs.
4. Check for conflicts that might arise between these new rules and campus-local
rules.
When the file gets saved, the changes take effect immediately. The next number
dialed uses the updated mappings.
Mapping incoming dialed numbers to defined bridge numbers

To avoid the E.164 format conversion process, technicians can map incoming numbers to
numbers that are easily dialed by the conference servers. This process is only feasible when
conference servers are coresident and follow the same internal dialing plan.
Avaya does not recommend this practice because of the added complexity to the rule set and
limited scalability if new bridges are added to the configuration.

There are two main logs for the Conferencing Plug-in for IBM Lotus Sametime:
• The telephony diagnostics logs: SametimeDiagnostics_Telephony.properties
• The Bridge Control API (BCAPI) logs: log4j.properties
For more information, see https://www.ibm.com/developerworks/lotus/documentation/
sametime/
Related topics:
Telephony diagnostic log on page 558

BCAPI log on page 559
Telephony diagnostic log

IBM Lotus Sametime checks for changes to the SametimeDiagnostics_Telephony.properties
file every five minutes and rereads the file if any modifications are made.
The standard log levels are described in the following table.
Setting Description
SEVERE (highest value)
WARNING
INFO Default
CONFIG
FINE
FINER Granular
FINEST (lowest value) Very granular, includes log pings. The log verbosity increases.
Background information about the diagnostics configuration file

The default configuration provides a single FileHandler that writes log messages to the file
<DOMINO_DIR>/Trace/telephony_<X>.log, where <X> is a decimal number between zero (0)
and 9. The telephony_0.log file is always the current log file to which the IBM Lotus Sametime
plug-in writes log messages.
Other files like telephony_1.log, telephony_2.log, and so on, are older log files that are rolled
or queued for deletion. The oldest log file, telephony_9.log, disappears when the system rolls
the file. The example, telephony_9.log, depends on the contents of the log configuration file.
One of the following events can trigger rolling:
• File size reaches a maximum of 10,000,000 bytes. The maximum is a configurable
parameter: java.util.logging.FileHandler.limit=10000000.)
• IBM Lotus Domino server is restarted
• Configuration file is reread after modifications are made
Related topics:
Setting up the telephony diagnostics logs on page 559

Setting up the telephony diagnostics logs

Prerequisites
Before you configure the IBM Lotus Sametime logs, you must install and configure
Conferencing and configure your IBM Lotus Sametime deployment.
The purpose of this task is to change the log level to match your requirements.
1. Open SametimeDiagnostics_Telephony.properties file and locate the following

lines.
.level=INFO
. java.util.logging.FileHandler.level=INFO
Note:
The default log level for the IBM Lotus Sametime plug-in is INFO.
2. Change the value, INFO, on these two lines to one of the lower log levels, such as
FINEST, and save the file. Within five minutes, the verbosity of the logs increases.
To return the reduce the log levels, return values to INFO and wait another five
minutes. For more information, see http://java.sun.com/j2se/1.4.2/docs/guide/util/
logging/overview.html.
When the file is saved, the changes take effect within a few minutes.
Next steps
Now, it is a good idea to configure the BCAPI logs.
BCAPI log
The log4j.properties file stores the BCAPI logs for IBM Lotus Sametime. You can configure the
following BCAPI logging settings:
• Standard output
• File output
• JDK 1.4 logging adapter
This table compares the logging levels in the log4j.properties file with the Java logging levels.

log4j logging Java logging

DEBUG FINE
INFO INFO
WARN WARNING
ERROR WARNING
FATAL SEVERE
OFF OFF
ALL ALL
The BCAPI log messages are forwarded to the IBM Lotus Sametime plug-in logging utility.
Since the SametimeDiagnostics_Telephony.properties file controls the IBM Lotus Sametime
plug-in logging utility, set the same verbosity levels in both files for the messages to appear in
the logs. For example, the DEBUG-level messages from BCAPI do not appear in the logs if
you set the logging level to DEBUG in log4j.properties and INFO in
SametimeDiagnostics_Telephony.properties.
For more information, see http://logging.apache.org/.
IBM Lotus Sametime Connect client

IBM Lotus Sametime Connect is the IBM instant messaging tool. It provides presence
awareness and Web conferencing features, which enable people to collaborate in real time.
The Avaya plug-in for IBM Lotus Sametime extends the features of IBM Lotus Sametime
Connect to provide fully integrated conference telephony capabilities. Using this functionality,
you can promote a regular call to an instant meeting with full Meeting Room Center (MRC)
access.
IBM Lotus Sametime Connect users can configure the Conferencing settings on the IBM Lotus
Sametime Connect client interface using the File > Preferences > Telephony Connections
menu. Once the IBM Lotus Sametime Connect users configure these settings, they can avail of
Conferencing functionality using IBM Lotus Sametime Connect. In other words, users can
access their on-demand conference using IBM Lotus Sametime Connect. The settings that
they have to configure include the moderator and participant passcodes. Users must define
their contact telephone numbers in the IBM Lotus Domino server.
Users can initiate Conferencing by selecting participants from the buddy list and selecting Click
to Call from the right-click menu. Users can also initiate instant data-sharing meetings using
the AWC.

Chapter 37: Viewing reports
Viewing Conferencing Reports

You can produce a large variety of reports on the performance and usage patterns of
Conferencing.
Web Portal reports

There are a number of types of Web Portal reports for administrators.
• Booking Reports: Displays booked resources versus used ports in a selected graphical
format.
• Moderator Console Report: Displays the number of moderators that started the Audio
Console in graphical format.
• Session Load: The administrator can view how many moderators are currently logged on
to the Web Portal using Session Load. Select the Session Load option and click Generate
Report to view.
• User (moderator) Sessions: The moderator sessions give a report of how many
moderators accessed the Web server over a period of time. Totals are for each day in the
date range specified. This information displays in a variety of different formats.
Administrators can also view the number of separate sessions that have taken place on
the Web Portal.
You can also view the data in a Microsoft Excel™ spread sheet. The output is listed in a series of
fields.
Note:
For more information on the reports that are available for moderators, see the Using Avaya
Aura™ Conferencing Guide, which is available from support.avaya.com. The Web Portal
moderator URL is: http://Web Portal virtual machine IP/webportal/login.
Related topics:
Generating reports on page 562

Viewing reports
Generating reports
Prerequisites
In order to produce a meaningful report, you must ensure that some activity takes place on the
Web Portal application.
The purpose of this task is to generate graphical representations of conference activity.
1. Click Reports.
2. To generate a booking or moderator console report:
a. Click Admin Reports.
b. Select what type of report you want to generate.
c. Select the date that you want the report generation to start from the Start Day
drop down list.
d. Select the date that you want the report generation to end from the End Day
drop down list.
e. Select the chart type.
3. To generate a session load or user session report:
a. Click Session Reports.
b. Select User Sessions for a User Sessions report.
c. Enter the date range for the reports.
d. Select your preferred graph type.
4. Click Generate Report.
Next steps
If you like, you can view the report details in a Microsoft Excel™ spreadsheet. To view the report
in a Microsoft Excel™ spreadsheet, Click Report CSV File, followed by OK and Save.

Chapter 38: Loading call detail records
The Call Detail Record (CDR) Loader application

Note:
Typically, you use the Call Detail Record (CDR) Loader application in deployments that have
multiple application servers, or bridges. The Standard Edition of Conferencing does not
The CDR Loader application enables you to load call detail record (CDR) files from a number of
different application servers or bridges. The CDR Loader application also enables you to create
billing information for a number of different bridges using one interface. The loader transfers
CDR data from the bridge to the CDRs database.
The CDR Loader replaces the Read CDRs application, providing significant performance
improvement. It transfers CDRs data from the Conferencing application server, or bridge, (.cdr
and .codr) to the CDRs database in two stages:
• The CDR Loader application loads the files and inserts the data into special CS700 tables
in the CDRs database. These tables are Cdr700 and Codr700.
• A scheduled SQL server task, which runs at configurable intervals, reads the data from
these special CS700 tables, converts it into the correct format, and then inserts it into the
standard CDRs tables. These tables are Call, Conferee, Conference, and ConfName.
The CDR Loader application suits the creation of large files as it supports incremental
downloads, in other words, the least amount of network traffic is generated every time the
loader checks data from the bridge. Each bridge has a dedicated SFTP download thread,
enabling the loader to access all the bridges simultaneously.
Old files, consisting of CDR and CODR information transferred from a bridge, are deleted
automatically so that the folder size does not exceed the available storage space. Automatic
deletion of old files also ensures that system performance never deteriorates due to the
exhaustion of storage space.
The CDR Loader downloads the CDR and CODR files from a bridge using a secure form of
the standard file transfer protocol (FTP). The secure form of FTP is known as SFTP. For SFTP
to operate successfully, you must configure the CDR Loader initialization file.
The SFTP form of communication requires the CDR Loader to open a listening port for each
incoming file transfer. In addition, the CDR Loader opens outgoing ports for sending commands
to the server. You can specify which ports to use for the bidirectional communication.

Loading call detail records
The CDR Loader interface

In previous editions of Conferencing, the CDR Loader consisted of an application with a graphic
user interface (GUI). In the past, administrators used this GUI to configure many aspects of
the operation of the CDR Loader. They could also configure advanced settings in the CDR
Loader initialization file.
In the current edition of Conferencing, the CDR Loader is treated like a process or a service.
It runs in the background. Due to security settings in the Windows 2008 operating system,
which runs on the CRS virtual machine, administrators cannot access the CDR Loader GUI
while the BSMon is running.
Conferencing Manager is sufficient to ensure that the CDR Loader operates as required.
If you require access to the CDR Loader application, you must:
• Stop the BSMon monitoring of the CDR Loader.
• Stop the CDR Loader task using the Task Manager.
• Access the CDR Loader application and perform the tasks that you require.
This table describes some the CDR Loader graphic user interface (GUI).
Section Description
CDR Loader Displays details regarding:
main fields Bridge Name: Displays the name of the bridge.
IPAddress: Displays the bridge’s IP address.
Model: Displays the bridge type. The S70, S700_20, S700_21, S700_31
are currently supported. S700_31 is used by default if no value is displayed.
Enabled: It is recommended that ‘1’ is used.
CDR LastImportDate: Displays the last CDR import date. The loader
recommences from this date.
Bridge IP Address: Displays the IP address of the bridge.
LastBytePos: Displays the last byte position in CDR file on the bridge. This
is used by incremental download and is always 0 on start.
CDR_LocalStore: Displays the name of the CDR Files local directory
storage location.
CDR_RemoteStore: Displays the full path on the bridge where FTP can
find the CDR Files.

Some CDR Loader fields
Section Description
CODR_LastImportDate: Displays the last CODR import date. The loader
recommences from this date.
CODR_LastBytePos: Displays the last byte position in CODR file on the
bridge. This is used by incremental download and is always 0 on start.
CODR_LocalStore: Displays the name of the CODR Files local directory
storage location.
CODR_RemoteStore: Displays the full path on the bridge where FTP can
find the CODR Files.
CabinetRef: Displays the cabinet reference number.
SynchInterval: Displays the time interval between each download. This
value is in seconds and is configurable.
Main Area Displays the progress details of CDR file creation. Alerts the user to any
fault in connection to the bridge.
Red Text: Displays an alert.
Green Text: Displays a success message.
Blue Text: Displays normal information
Bridge Area Enables the user to set the interval time to check for new information. New
CDR files are created if there is new information available.
Patcher Enables the user to create process files for manually downloaded
Started Area information.
Open Active Enables the user to open a note pad file which displays the log details of
Log the created CDR Files.
Exit Button Enables the user to exit the CDR Loader.
You can start the CDR loader using silent mode. Silent mode starts all the services, for
example, update db process and automatic download process for all specified bridge(s).
Some CDR Loader fields

Avaya has added some new fields to the CDR Loader application in the recent releases. This
section lists some of those recent additions.
CDR field
Field Name Data Type Comment

PromptSet smallint Indicates the Prompt Set used for the conference. In other words,
this is the language type for messages to be played. It must be
a value between 1 and 20.

CoDR fields

PromptSet smallint Indicates the Prompt Set used for the conference. In other
words, this is the language type for messages to be played.
It must be a value between 1 and 20.
ConfSecCode varchar (16) Conference Security Code (This is the conferee
passcode.)
ModSecCode varchar (16) Moderator Security Code (This is the moderator
passcode.)
SelfReg tinyint Indicates whether Self Registration was enabled for the
conference.
AccountNumber varchar (50) Corresponds to the account number in the conference
reservation.
Conferee table

PromptSet smallint Indicates the Prompt Set used for the conference. In other words,
this is the language type for messages to be played. It must be
a value between 1 and 20.
Conference table

MaxUserCount integer Maximum number of simultaneous conference
participants, excluding operators (1— 1200).
QA tinyint 1/0 – Indicates whether Q&A was enabled for the
conference. (0= Q&A was not enabled, 1= Q&A was
enabled).
Polling tinyint 1/0 – Indicates whether Polling was enabled for the
conference. (0= Polling was not enabled, 1= Polling was
enabled).
DataConferencing tinyint 1/0 – Indicates whether Data Conferencing was enabled
for the conference. (0= Data Conferencing was not
enabled, 1= Data Conferencing was enabled).
Note:
Data conferencing is provided by an application
called Avaya Web Conferencing (AWC).
Conference Viewer tinyint 1/0 – Indicates whether Conference Viewer was
enabled for the conference. (0= Conference Viewer was
not enabled, 1= Conference Viewer was enabled).

Initialization file

PromptSet smallint Indicates the Prompt Set used for the conference. In
other words, this is the language type for messages to
be played. It must be a value between 1 and 20.
ConfSecCode varchar (16) Conference Security Code (This is the conferee
passcode.)
ModSecCode varchar (16) Moderator Security Code (This is the moderator
passcode.)
SelfReg tinyint Indicates whether Self Registration was enabled for the
conference.
AccountNumber varchar (50) Corresponds to the account number in the conference
reservation.
Initialization file
The CDR Loader initialization file is called CDRLoader.ini. It contains a number of system
parameters that control CDR Loader functionality. Using CDRLoader.ini, you can configure the
settings that manage:
• The deletion of old data files
• The limitations on the range of communication ports
• The secure file transfer protocol
Related topics:
File management on page 567
Limitations on communciations ports on page 569
Secure file transfer protocol on page 569
File management
Old files, consisting of CDR and CODR information transferred from an application server
(bridge), are deleted automatically so that the folder size does not exceed the available storage
space. Automatic deletion of old files also ensures that system performance never deteriorates
due to the exhaustion of storage space.
You can choose to enable automatic deletion or you can choose not to enable it.
If you do not enable it, you must manually delete old files.
If you enable automatic deletion, the automatic deletion task is triggered every 60 minutes.
The automatic deletion task inspects the contents of each bridge’s local CDR and CODR
directories and deletes all files that are older than a predefined threshold. The automatic

deletion task makes an exception for files with an .imp file extension. These files are considered
to be not yet processed. Usually, the CDR and CODR files loose the .imp extension as they
are imported into the CDRs database but a file may still retain the .imp extension in exceptional
circumstances.
The CDR Loader calculates the age of the file according to the most recent time it was either
created, modified, or “accessed”. "Accessing" means opening a file for reading. So if a file was
opened within the age threshold, the CDR Loader will not delete it, even if it was created or
modified beyond the age threshold.
The CDR Loader Logging screen shows detailed information about the automatic deletion
process.
Related topics:
Managing automatic deletion on page 568
Managing automatic deletion

Prerequisites
Before you manage CDR automatic deletion, you must install and configure Conferencing.
The purpose of this task is to ensure that the CDR and CoDR file sizes do not grow too large.
• To enable automatic deletion:
a. Ensure that PurgeOldFile=1 parameter in the [LocalStore] section of
CDRLoader.ini.
b. Enter a value for DaysToKeepFilesBeforePurge.
DaysToKeepFilesBeforePurge refers to an age threshold in days. If a file is
older than this value, the automatic deletion task deletes it.
• To disable automatic deletion:
Ensure that PurgeOldFile=0 parameter in the [LocalStore] section of
CDRLoader.ini.
Example
For example, if DaysToKeepFilesBeforePurge=30, the CDR Loader automatically
deletes the file if it is older than 30 days.
Next steps
Now you can limit the range of communication ports.

Initialization file
Limitations on communciations ports

The CDR Loader downloads the CDR and CODR files from a bridge using a secure form of
FTP, called SFTP. The SFTP form of communication requires the CDR Loader to open a
listening port for each incoming file transfer.
In addition, the CDR Loader opens outgoing ports for sending commands to the server. You
can specify which ports to use for the bidirectional communication. The ability to specify the
port range means that:
• You can eliminate the chance of clashing with other services running on the same
computer.
• You can ensure that the CDR Loader can communicate with the SFTP server if there is
a firewall between them.
Secure file transfer protocol

Secure file transfer protocol (SFTP) means that communication between the applications
servers (bridges) and the CDR Loader is not as vulnerable to attack as it was in previous
releases of Conferencing. The CDR Loader uses an external SFTP client to provide secure
communication.
The external client is called PSFTP.exe and it is available from the open source package,
PuTTY. The current version is .58. It is available here:
http://www.chiark.greenend.org.uk/~sgtatham/putty/
You must enter the fully qualified path for PSFTP.exe in the CDR Loader initialization file. If
you do not enter the path, Conferencing assumes that PSTFP.exe is in the same directory as
CDR Loader.
To enter the fully qualified path:
Enter the fully qualified path to PSFTP.exe in the PuttySftpPath parameter in the
[LocalStore] section of CDRLoader.ini.
At CDR Loader startup, the CDR Loader performs a SFTP test connection. It attempts to
connect to each bridge using the bridge username and password. If the test is successful, the
CDR Loader uses SFTP for all communication with that bridge. If the test is not successful,
the CDR Loader assumes that the bridge does not support SFTP. In this case, the CDR Loader
uses FTP, without performing an FTP test connection.
If SFTP support is enabled on a bridge while the CDR Loader is running, you must restart the
CDR Loader to enable SFTP because the CDR Loader only performs the SFTP test connection
at CDR Loader startup.

Related topics:
Enabling SFTP on page 570
Enabling SFTP
Prerequisites
Before you enable secure file transfer protocol, it is a good idea to configure CDR and CoDR file
management.
The purpose of this task is to ensure that CoDR and CDR file transfers are secure. By default
SFTP is enabled.
To enter the fully qualified path: Enter the fully qualified path to PSFTP.exe in the
PuttySftpPath parameter in the [LocalStore] section of CDRLoader.ini.
Troubleshooting the CDR Loader

To help you to diagnose any issues that might occur in the application, CDR Loader generates a
logging file. This logging file acts as an audit trail and enables you to identify the cause of any
problems. The logging file records the time and nature of various events in the CDR Loader.
For example, if a User exits the application using the Exit option on the File menu or the Close
button in the top right of the screen, an entry is recorded as follows:
User initiated shutdown
The logging file is stored in the Install directory (C:\AVAYA\CDRLOADER, by default).

Chapter 39: Upgrading to/from Conferencing
Introduction to upgrading
You can upgrade to the General Availability (GA) version of Avaya Aura™ Conferencing 6.0
Standard Edition from:
• Avaya Meeting Exchange Express version 2.0, Service Pack 1
• The beta version of Avaya Aura™ Conferencing 6.0 Standard Edition
These upgrade paths preserve customer data such as:
• Companies
• Clients (accounts)
• Reservations
• Conferences
If you are a beta customer and require an upgrade from the beta version of Avaya Aura™
Conferencing 6.0 Standard Edition, contact an Avaya Support Representative.
Upgrading from Meeting Exchange Express

The latest edition of Avaya Meeting Exchange Express is version 2.0, Service Pack 1. You can
upgrade to the Standard Edition of Conferencing from Meeting Exchange Express version 2.0,
Service Pack 1.
The instance of Conferencing should not contain any existing data. The Conferencing
database should be clear. It is important to note that an approximate mapping occurs because
there is not an identical set of features in Conferencing and Meeting Exchange Express. Note
that Meeting Exchange Express is often called Crystal.
Prerequisites
Before you upgrade to Avaya Aura™ Conferencing, you must have a clean instance of Avaya
Aura™ Conferencing and an instance of Meeting Exchange Express. You also require an
understanding of the functionality and features of Microsoft SQL Server Management Studio™.

Upgrading to/from Conferencing
The purpose of this task is to move to Avaya Aura™ Conferencing from an instance of Meeting
Exchange Express is version 2.0, Service Pack 1.
2. Create an Open Database Connectivity Data Source Name (ODBC DSN) to access
the Meeting Exchange Express database from the CRS virtual machine.
a. Navigate to Start > Programs > Administrative Tools > Data Sources
(ODBC).
b. On the ODBC Data Source Administrator dialog, click Add.
c. From the list of database types, select PostgreSQL Unicode.
You must select Unicode, rather than ANSI because Conferencing supports
multiple languages.
d. On the PostgreSQL Unicode ODBC Driver (psqlODBC) dialog, enter the
information as follows:
Field Value
Data Source crystaldb
Database crystal
Server <IP address of Meeting Exchange Express server>
User Name postgres
Description <any descriptive information>
SSL Mode disable
Port 5432
Password postgres
3. Open Microsoft SQL Server Management Studio.

4. Load the import script into the BSRes2 database.
a. Navigate to the BSRes2 database.
b. Right-click on the BSRes2 database and select New Query.
c. Navigate to File > Open File and select the import script.

Upgrading from Meeting Exchange Express
The script is located in BSRes2\DBUpgrade\ImportCrystalData.sql

This script may report errors. If it reports errors, you must change the security
properties:
a. Navigate to Server Objects > Linked Servers > crystaldb.
b. Click Security.
c. Select Be made using this security context.
d. On the Remote login field, enter crystal and on the With password field,
enter crystal.
5. Run the import script on the BSRes2 database.
You can run a single script or you can run three separate scripts:
Option One: Run a single script Option Two: Run three separate scripts
exec ImportCrystalData 'import' exec ImportCrystalData 'copy'
exec ImportCrystalData 'insert'
exec ImportCrystalData 'reload'
6. When the script finishes, open the SCManager application.

You can access the SCManager application from the Start menu on the CRS virtual
machine.
7. On the SCManager application, click Reload to push the new reservations to the
Conferencing application server (bridge).
The SCManager signs in to the bridge using the name crs and password crs. This
sign-in exists by default in each new instance of Conferencing.
Next steps
Now you can check that the Meeting Exchange Express companies, clients, reservations, and
conferences exist on the Conferencing instance. The easiest way to do this is to open the CRS
Front End and navigate to the Customer Bookings section.

Upgrading to/from Conferencing

Chapter 40: Import Utility fields
Company fields
ID Field Type Definition
75 Company Ref 9(8) The company reference of this company.
76 Company Name* X(50) The name of this company.
77 Address Line 1 X(50) Company address
81 Phone X(40) Company phone number
Although a phone is required, it is possible to
assign the telephone number in the Import
Profile. If it is not present in the import record or
supplied in the import profile, it defaults to 123.
82 Fax X(40) Company fax number
83 E-mail X(50) Company email address
84 Contact Name X(50) The contact name for this company
85 External ID 9(10) An external id for the company.
87 Import ID* X(50) Uniquely identify the imported record.
88 Disabled 9(1) Disabled field
89/90 ContactFirstName X(50) The ContactFirstName and ContactLastName
ContactLastName fields are combined, with a space in between, to
form a single field, called,
Company.ContactName. Their combined length
is a maximum of 50. There is only one
ContactName field in the Company record, so
the Import Utility allows a choice of entering:
Contact Name (field 84)
ContactFirstName<space>ContactLastName
(fields 89 and 90)


91 WholesalerExternalString X(50) An associative link to an external database
Client fields
100 Client Ref 9(8) The client reference of this client.
Although a phone is required, it is possible to
assign the telephone number in the Import
Profile. If it is not present in the import record
or supplied in the import profile, it defaults to
123.
101 Company Import ID* 9(8) The company reference of this client. This is a
cross reference to the Company’s Import ID.
For more information, see the previous table.
102 Name* X(50) The name of this client
103 Address 1 X(50) Address line 1
107 Main Phone X(24) Client’s main phone number
108 Main Fax X(24) Client’s main fax number
109 Main Icc X(24) Client’s main credit card number
110 External Id 9(10) Client’s external ID. (foreign database link)
111 Client Main Email X(50) Client’s main contact email
112 Contact Name X(50) Contacts name for the client
113 Contact Address Line 1 X(50) Contacts address
117 Contact Phone X(40) Contacts phone number
118 Contact Fax X(40) Contacts fax number
119 Contact E-Mail X(50) Contacts email address

Reservation and conference fields

123 Account Number 9(16) Contacts account number
148 Import ID* X(50) The ID associated with this import
149 Time Zone Type 9(1) Relevant time zone
150 Password X(8) Passwords used
151 Disabled 9(1) Disabled
176 Company Key Field 2* X(50) This is the key to the company file that is being
imported. It is associated with the Import ID at
company level.
177 PreferredDDI X(32) DDI preferred by client
178 ExternalString X(50) An associative link to an external database.
Helps to link the client with an entry in an
outside system.
179 SecondaryPhone Phone (40) An alternative client telephone number.
180 MobilePhone Phone (40) The client’s mobile telephone number.
181 DisableOpRecall Boolean If DisableOpRecall is enabled, participants
cannot use a telephone keypad sequence to
dial an operator for assistance.
182 BlockDialOut Boolean If BlockDialOut is enabled, moderators
cannot dial out to potential participants during
a conference call.
183 EmployeeUID 9 The client’s unique identifying number. For
example, this can be an employee number.

Reservation fields

200 Reservation Ref 9(8) The reservation reference
201 Book Date Time X(14) The date and time the reservation was made
202 Type 9(2) The type of reservation.
0 = Single booking
1 = Repeat booking
2 = Adhoc booking
204 Client Ref 9(8) The client reference of the owner of this reservation


205 User Ref 9(8) The user reference of the operator who made this
reservation
206 SalesPersonRef 9 This field can be set to zero. Alternatively, it can refer
to a Sales Person reference number.
207 TotalConferenceCount 9 This field can be set to 1 for a single instance
conference or a number greater than 1 for repeating
conferences. This repeating conference number
corresponds to the number of recurrences.
208 ConferenceRepeatType 9(1) This field can be set to zero for a single instance
conference or 1 for a repeating conference.
209 BridgeId 9 This field can be set to zero. Alternatively, it can refer
to a bridge (application server) reference.
Conference fields

300 Reservation Ref 9(8) The reservation that
owns this
conference
301 Conference Ref 9(10) The conference
reference of this
conference
303 Status 9(1) The status of this
conference.
0 = Aborted
1= Provisional (not
booked yet)
2= Confirmed
(booked)
3 = Suspended
4 = In progress
5 = Completed
6 = Cancelled
7 = Billed
8 = Not available
(failed to book)
304 Start Date Time X(14) The start date time
of this conference
305 End Date Time X(14) The end date time of
this conference
306 Original Duration 9(10) The booked
duration of this
conference. Note,


due to conference
extension/reduction
the end date time
minus the start date
time may not be
equal to the original
duration
307 Type 9(2) The conference
type.
1 = Meet me direct
16 = Flexflow
308 Language 9(1) The conference
language type.
1 = English
309 Priority 9(1) The conference
priority type.
1 = Normal
310 Name X(50) The conference
name.
313 Moderator 9(1) Is this a moderator
controlled
conference
314 Demand 9(1) Is this a demand
conference
318 PaymentType 9(2) Payment type.
319 PaymentNumber X(20) Payment number.
325 Notification Type 9(1) The type of
notification
requested for this
conference.
0 = No notification
1 = Fax notification
2 = Email
notification
3 = Fax and Email
notification
326 Notification X(255) Have comments
Comments been provided.
327 Notify Confirmation 9(1) Has a confirmation
notification been
requested.


328 Notify Cancellation 9(1) Has a cancellation
notification been
requested.
329 Notify Change 9(1) Has a change
notification been
requested.
330 Notify Reminder 9(1) Has a reminder
notification been
requested.
331 Notify Attendance 9(1) Has a attendance
notification been
requested.
337 Conferee PIN X(8) The passcode
number to be used
by the conferees.
338 Moderator passcode X(8) The passcode
number to be used
by the moderator.
339 Operator Type 9(1) The type of operator
assistance required.
1 = Assisted
345 Toll Free 9(1) Is this a toll free
conference.
346 Conference X(255) Comments entered
Comments by the booking
operator for this
conference.
351 DDI X(24) DDI assigned to this
client
359 Enter Tone 9(1) Ambient noise
heard on entering a
conference.
360 Leaving Tone 9(1) Ambient noise
heard on leaving a
conference.
361 StreamLive Boolean If live streaming is
enabled for this
conference,
StreamLive=1.
If live streaming is
not enabled,
StreamLive=0.


362 StreamPlayback Boolean If streaming
playback is enabled
for this conference,
StreamPlaybac
k=1. If streaming
playback is not
enabled,
StreamPlaybac
k=0.
363 Locked Boolean Conference lock
ensures that
potential
participants cannot
enter the
conference after the
Moderator enables
the lock function. If
the lock function is
available for use by
the Moderator,
Locked=1
. If the lock function
is not available,
Locked=0.
364 WelcomeMsg 9 The Welcome
message is the
message that is
played into the
conference. The
value in this field
indicates the
message number.
365 BellMsg 9 The Bell message
is played to
participants while
they are waiting for
the Operator. The
value in this field
indicates the
message number.
366 HoldMsg 9 The Hold message
is played to
participants while
they are on hold.
The value in this


field indicates the
message number.
367 TenMinuteMsg 9 The
TenMinuteMsg is
played to
participants to
indicate the first
warning that the
conference will soon
end. The value in
this field indicates
the message
number.
368 OneMinuteMsg 9 The
OneMinuteMsg is
played to
participants to
indicate the second
warning that the
conference will soon
end. The value in
this field indicates
the message
number.
369 ConferenceFullMsg 9 The
ConferenceFul
lMsg is played to
potential
participants if the
number of
participants already
in the conference
exceeds the alloted
number of
participants/ports.
The value in this
field indicates the
message number.
370 StartingLaterMsg 9 The
StartingLater
Msg is played to
participants if the
conference start is
delayed by the
Moderator. The
value in this field


indicates the
message number.
371 InConferenceMsg 9 The
InConferenceM
sg is played to
participants while
they are in the
conference. The
value in this field
indicates the
message number.
372 EnterPINMsg 9 The
EnterPINMsg is
played to
participants to
prompt them to
enter their PIN. The
value in this field
indicates the
message number.
373 WelcomeFirstMsg 9 The
WelcomeFirstM
sg is played to the
first participant to
arrive in the
conference. The
value in this field
indicates the
message number.
374 HoldFirstMsg 9 The
HoldFirstMsg is
played to the first
participant to arrive
in the conference.
The message
indicates that the
Moderator has not
yet arrived and that
the conference has
not yet started. The
value in this field
indicates the
message number.
376 AutoPIN 9 If AutoPIN=1,
automatic allocation


of conference
passcodes is
enabled for this
conference. If
AutoPIN=0,
automatic allocation
of conference
passcodes is not
enabled.
377 Global 9 If Global=1, the
conference is a
global conference. If
Global=0, the
conference is not a
global conference.
378 WaitForModerator 9 If
WaitForModera
tor=1, the
conference does not
start until the
Moderator arrives. If
WaitForModera
tor=0, this feature
is not available.
379 SecondPassCode 9 If
SecondPassCod
e=1, an additional
level of security is
available for
participants.
Moderators can
choose to add an
extra security code
to the conference. If
SecondPassCod
e=0, this feature is
not available.
380 BreezeTemplateID 9 BreezeTemplat
eID is the reference
number of the
Adobe Connect
template.

Chapter 41: Avaya Aura™ Conferencing
Implementation Workbook
Avaya Aura™ Conferencing implementation workbook

The Avaya Aura™ Conferencing implementation workbook provides the implementation
checklists and worksheets for implementing Conferencing.
You must complete all sections prior to commencing installation.
Related topics:
Configuration of your network in preparation for AWC on page 233
Customizing/Configuring your model on page 406
Avaya Aura™Conferencing overview

The Avaya Aura™ Conferencing Standard Edition contains the following components.
Audio bridge
Avaya Aura™ Conferencing Standard Edition allows you to easily deploy on-premises audio-
only or audio and Web conferencing across your entire enterprise, providing all of the
capabilities you need, in one cost-effective solution. The S6200 server is the audio
Conferencing server, software-based IP conferencing platform that supports Avaya
Conferencing features on standard Intel-based servers. The S6200 is interoperable with Avaya
and third party IP-PBXs and IP phones.
This is a database and server. It utilizes an MS-SQL database to support a wide range of
functions including: system administration, booking, scheduling, reporting and billing
applications. The end user application CRS Front End is used to interface to the CRS system.
Web Portal
This is a Web based user interface to the CRS and audio bridge. It enables secure and
streamlined conference scheduling, management, and administration through an intuitive
browser-based interface. Additionally, Web Portal carries the Audio Console application, which
can be integrated with Web Portal or be used standalone with the Conferencing bridge. The

Avaya Aura™ Conferencing Implementation Workbook
Audio Console provides moderators with real-time control during conferences, using icons
representing each participant and intuitive buttons for tasks such as mute, inbound call
intercept, dial out, sub conferencing, and recording/playback controls. In the Standard Edition
of Conferencing, the Web Portal cannot reside in a DMZ (as all components of the system
reside on a single server) so it’s recommended for internal use only.
Avaya Web Conferencing enables Web conferencing features that include white boarding,
PowerPoint presentations, video steaming of moderators, and application sharing functionality
using a Web browser. In the Standard Edition of Conferencing, the AWC cannot reside in a
DMZ (as all components of the system reside on a single server) so it’s recommended for
internal use only.
Audio Codes Mediant 2000
This is a TDM to SIP gateway. It is used to integrate Conferencing into a legacy TDM telephony
environment. It supports T1, T1 ISDN, E1 ISDN.
Virtualization
In the Standard Edition of Conferencing, the applications above run as Virtual Machines (VM)
on a single server. Collectively the VMs are known as the Conferencing template.
• You must install System Platform on the server before the template can be applied.
System Platform consists of two components, system domain & console domain.
• As well as CRS, Bridge, Webportal and AWC, there is a virtual machine called
Conferencing Manager which provides a single interface to configure the Conferencing
applications. Consequently, seven sets of networking data (IP address, hostname,
gateway, DNS, NTP) are required for the Conferencing installation. All IPs must be on the
same subnet. Avaya has created the Conferencing Manager virtual machine for use in
deployments where there is no System Manager installed. Avaya has created
Conferencing Manager to manage one and only one Avaya Aura™ Conferencing 6.0
Standard Edition server. Customers who have multiple servers require Avaya Aura™
System Manager 6.0 server to manage multiple Avaya Aura™ products.
Architecture overview
This diagram shows the relationships between the components of Avaya Aura™.

Points of contact and site information
Points of contact and site information

Avaya requires all of this information prior to commencing installation.
Requirement Values Completed?

Customer information Customer Site
Address:
City:
State/Province:
Postal Code:
Country:
Primary Technical
Contact:
E-Mail:
Tel:
Mobile:
Secondary Technical
Contact:
E-Mail:
Tel:
Mobile:
Channel contacts (Resellers/BP) Channel/Company:
Address: City:
State/Province:
Postal Code:
Country:
Technical Contact:
E-Mail:
Tel:
Mobile:

Requirement Values Completed?

Installation location If address is different
please advise
physical location of
equipment
installation site:
Security If there are any
special security or
access requirements
to the customer
location please
details the process or
requirement:
Hotel and airport Please inform us as
to the closest hotel to
the installation
location. Avaya uses
this information for
reference purposes
only. You only need
to list one hotel.
Please inform us as
to the closest airport
to the installation
location. Avaya uses
this information for
reference purposes
only. You only need
to list one airport.
Training location If training is ordered
and the training
location will be
different to that of the
equipment location
please detail the
address to be used:
Working hours Please inform us as
to the available daily
working hours for the
installation
consultant or if any
restrictions apply.

Network and LAN information
Network and LAN information

A minimum of two physical LAN connections are required for production traffic.
• Eth0/Gig1: System Platform/Avaya Web Conferencing/CRS/Webportal/Conferencing
Manager
• Eth3/Gig4: Conferencing bridge, for a GB switch ensure the connection is set to auto-
negotiate.
Virtual machine Values Notes

System Platform Hostname: Also known as
System Domain IP: Domain 0
Required Subnet Mask:
Gateway IP Address:
DNS Server IP
Address:
Network Domain:
NTP server:
System Platform Hostname: Also known as the
Console Domain IP: CDOM
Required Subnet Mask:
Gateway IP Address:
DNS Server IP
Address:
Network Domain:
NTP server:
Conferencing bridge Hostname: The hostname is the
LAN Configuration IP: unique name
Required Subnet Mask: assigned to the
Gateway IP Address: Conferencing
DNS Server IP application server by
Address: the administrator.
Network Domain: The hostname is
NTP server: alphanumeric, it
cannot contain
special characters or
dashes. The
hostname can be a
max of 8 characters
in length.
The IP of the system
cannot contain any
0s.


The default network
speed on the bridge
is 100 Full Duplex,
this can be updated
after install to 1GB.
For initial
connections to GB
LAN switches
however, the LAN
switch should be set
to auto-negotiate.
CRS Server Hostname: An SMTP email
LAN Configuration IP: account is required if
Required Subnet Mask: your deployment
Gateway IP Address: includes the
DNS Server IP Notification
Address: Subsystem.
DNS Server IP Cannot have any – or
Address: _ in the server host
Network Domain: name.
SMTP email server A Windows 2008
IP/hostname : product key is
SMTP email account required, this should
details: ship with the
hardware, please
keep somewhere
safe until the time of
install.
WebPortal Hostname: Cannot have any – or
LAN configuration IP: _ in the server host
Required Subnet Mask: name.
Gateway IP Address:
DNS Server IP
Address:
Network Domain:
AWC Server Hostname: A Windows 2008
LAN Configuration IP: product key is
Optional Subnet Mask: required, this should
Gateway IP Address: ship with the kit,
DNS Server IP please keep
Address: somewhere safe until
DNS Server IP the time of install.
Address:
Network Domain:
FQDN:
Conferencing Manager Hostname:
Required IP:

SIP or TDM: ISDN configuration

Subnet Mask:
Gateway IP Address:
DNS Server IP
Address:
Network Domain:

This worksheet lists the information that you need to configure Conferencing for
Communication Manager or TDM gateway usage.
Network Type Values Notes

SIP – CM, SES, SM, Avaya Aura™ The Conferencing The software version
integration server to of the
Communication Communication
Manager/SES or SM Manager must be a
integration guides minimum of R012x.
are contained within 02.0.111.4
Systems Integrations If there is a firewall
Lab/DevConnect between the bridge
(SIL) documents and the clients
which the network (e.g. SIP
Conferencing Phone) the following
installation ports are required to
consultant will be open:
supply. A SIP Ports 5060 or
Communication 5061 (TCP or TLS)
Manager/SS RTP port range is
engineer resource configurable in
will be required to softMediaServer.cfg
complete the baseRtpPort=42000
telephony side The 6200 Standard
programming for Edition only supports
Conferencing the G711 Codec.
integration. IP trunk licenses
CLAN Information must be ordered for
(Recommended if the Communication
bridge is behind an Manager for
S8700). Customer is Conferencing
responsible for telephony
providing a CLAN integration.
Interface.
IP Address of the
CLAN/SES/SM:


It is advisable to have
a network/SS
engineer review the
associated telephony
infrastructure
required to support
the traffic to the
For example
additional medpro
resources may be
required.
Confirm the
telephony side
design for the
Conferencing SIP
integration has been
reviewed & any
additional hardware,
software licensing is
in place:
The bridge will need
to be configured with
DDI numbers –
please advise what
the number or
number ranged to be
pointed to the
Conferencing will be.
DDI range to used on
the bridge:
SIP – Integration Conferencing You must confirm SIP
Other non Avaya IPT environment. integration guides interoptibility with
Nortel, Cisco, Alcatel, SIP proxy, Cantana are contained within Conferencing for non
IMG and so on. SIL documents which Avaya IP PBXs,
the Conferencing proxies or gateways.I
installation f there is a firewall
consultant will between the bridge
supply. and the clients
Customer/BP are network (such as a
responsible for all SIP Phone), the
telephony side following ports are
programming for required to be open:
Conferencing SIP Ports 5060 or
integration. 5061 (TCP or TLS)
IP Address of the SIP RTP port range is
server/gateway/ configurable in
PBX:


It is advisable to have softMediaServer.cfg
a network/SS baseRtpPort=42000
engineer review the The Standard Edition
associated telephony of Conferencing only
infrastructure supports the G711
required to support Codec.
the traffic to the
Conferencing. For
example additional
media resources
may be required.
Confirm the
telephony side
design for the
Conferencing SIP
integration has been
reviewed & any
additional hardware,
software licensing is
in place:
The bridge will need
to be configured with
DDI numbers –
please advise what
the number or
number ranged to be
pointed to the
Conferencing will be.
DDI range to used on
the bridge:
TDM – Gateway Integration. Each Audiocodes The Audio Codes
Avaya provided. M2K or G860 (AC2000) is only
gateway requires an required for TDM
IP address, 2x based Conferencing
physical LAN audio bridge
connections & dual integration. This is
power supplies. optional to support
LAN IP address of T1/E1 as opposed to
the audio codes SIP.
board: Each AC must have a
LAN IP address of static IP address &
the 2nd audio codes should be on the
board (if app): same subnet mask &
Switch type (make/ gateway as the
model/release): Conferencing server.
T1 RB –
configuration:
T1 ISDN Varient;


E1 ISDN Variant:
CRC4 ON/OFF:
DDI ranges to be
used on the bridge:
Remote access
This worksheet lists the information that you need to configure remote access for Conferencing.
Remote access is required for all remote Conferencing implementations. This access must be
tested & confirmed as operational by Avaya prior to the start of the system implementation.
Access Type Values Notes

Direct IP Access Will a direct IP For remote
RECOMMENDED for all installations. access be available installation,
REQUIRED for remote installations. at the time of connection is
Modems are not supported. installation: required on port 22
External IP address (PuTTY access).
of the System Once Conferencing
Platform Console is installed, Avaya
Domain (CDom): use the NSM client/
Will a SSG/SIG or server application for
SAL access be remote access to the
available at the time Windows CRS
of installation: server. Via NSM, it is
possible to access a
remote machine via
IP connectivity, take
control of the server
and file transfer. All
other Conferencing
servers are
accessible via the
CRS using NSM for
Windows based
servers & via putty/
SSH for S6200.
NSM uses port
number 5405.
Alternatively, on a
customer request
Avaya can use the
MS RDP application.

Implementation validation checklist
Access Type Values Notes

All Conferencing
systems, which are
accessed via direct
IP connection from
Avaya for remote
external access, will
need port 5404 open
on the firewall from
the CRS server on
site to the following
range of Avaya IP
addresses;
135.124.124.8
through to
135.124.124.19 (i.e.
135.124.124.8,
135.124.124.9,
135.124.124.10
etc...) up to .18
IP VPN Access Type of VPN (make/ Avaya will allow the
OPTIONAL application name): use of customer
Connection details: preferred VPN
applications for
remote access. To
enable the access
please provide
details on the VPN
application to be
used.

Each section of the below checklist needs to be confirmed.
All tick boxes must be checked prior to the Avaya Conferencing Consultant arriving on site for
the implementation.
# Task Description
1 Site Location Site address

Information Points of contact
Recommended Hotel/
Airport

# Task Description
2 Access Information Any special security or

access information
required to allow access
to the site for our
consultant.
3 Environmental Rack Confirm rack space
Space ready
If the Conferencing
servers are to be installed
in a cabinet where other
servers already
mounted, it is important
to confirm that the server
rails will mount
successfully in the
cabinet, for example,
cabinet beams may have
already been adjusted to
mount a different server
model.
4 Environmental Power Confirm all power cabling
is presented at the rack.
(Nominally, 2x power
points are required per
server & one for the
monitor, one for the video
switch box and one for
the modem).
Customer may need to
provide a monitor and
keyboard if not
specifically ordered.
5 Environmental Confirm all cable runs
Network Connections (ceiling, walls, and floor)
prior to installation date.
Cabling must be
terminated and ready to
interface as required.
Confirm network LAN
cabling presented to the
rack. (2x LAN
connections required).
6 Networking Confirm availability of all
Information system server IP’s,
hostnames & network
details for each of the

# Task Description
servers and TDM

gateways if applicable.
7 Telephony Integration. SIP: Confirm availability
TDM / IPT Information of all CM details if
applicable. A resource
must be arranged to
integrate & complete the
Communication Manager
side of the Conferencing
configuration. Confirm
SIP trunk licenses for CM
are ordered & available.
ISDN: Confirm E1s are
provisioned & configured
(EURO ISDN or QSIG,
CRC 4 ON/OFF? E1s
presented as RJ 45
connectivity for TDM
Audio Codes Gateway).
For testing purposes,
access to a phone and
desk is required for the
installation consultant.
8 Remote Access Confirm direct IP or VPN
access for remote device
access during and after
as required.
9 Resources Confirm access to
company personnel with
detailed knowledge of the
telecommunications and
data networking
environments.
10 License Obtain and make note of
the license information
from Product License
and Delivery System
(PLDS). Avaya
shipsConferencing with a
default license that
covers a 'grace period'. It
is important to apply a
real license at the earliest
opportunity in order to
continue using
Conferencing.

Port usage
The following ports are used with the different Avaya products. Depending on your selection,
these ports need to be open as required.
All ports are bi-directional.
Source Destination Protocol Port Description

S6200 NTP Server UDP 123 Time Synchronization
CRS/Web NTP Server UDP 123 Time Synchronization
S6200 Operator TCP 20001 Bridge Talk application
Workstation
Workstation
Workstation
S6200 Operator TCP and 5021 ModAPI Control
Workstation UDP
S6200 Operator TCP and 5022 Bridge Talk application
Workstation UDP
S6200 Operator TCP 22 SFTP and Telnet
Workstation
S6200 Operator TCP and 5023 Bridge Talk application
Workstation UDP
CRS/Web Operator TCP 1433 Reports application
Workstation
CRS/Web Operator TCP 5050 CRS Front End
Workstation application
Internet AWC TCP 80
Internet AWC TCP 443 Session initiated by
external user to AWC
Avaya CM/Med S6200 RTP 32770-44289 Communication
Pro Boards Manager
communications with
S6200
Avaya CM/Med S6200 TCP 5060 Communication
Pro Boards Manager

Miscellaneous notes

communications with
S6200
Avaya CM/Med S6200 TLS 5061 Communication
Pro Boards Manager
communications with
S6200
Conferencing All virtual TCP 18080 Conferencing Manager
Manager or machines or System Manager
System Manager communications with
all Conferencing virtual
machines.
Note:
The Standard Edition of Conferencing does not support Bridge Talk.
For remote support use

Support CRS server TCP 5405 NSM_file transfers and keyboard/mouse
control
Support Web Portal TCP 5405 NSM_file transfers and keyboard/mouse
control
Support AWC TCP 5405 NSM_file transfers and keyboard/mouse
control
Support application server TCP 22 Telnet command control session
Miscellaneous notes
For a complete list of the server environmental specifications for your Conferencing
deployment, see the Avaya Aura™ Conferencing Release Notes, which are available from
support.avaya.com.
CRS: Client imports
The application server (bridge), CRS, and Web Portal have the capability to accept scheduling
and user account data through input utilities and tools. This allows customers to export from
an existing system, such as an Avaya 70 or 700 schedules, or from a Human Resources
database. The input requirements vary according to the system to be installed, but a comma
separated value (CSV) file is preferred. Please review the requirements with your Avaya
Support Representative.

Additional Conferencing customization options available

Ask your Avaya Project Manager for pricing.
• Active directory LDAP integration for automatic CRS client registration: DSCA to CRS
• Active directory LDAP integration for automatic WP Authentication: Allows users to
authenticate to Web Portal using existing AD.
• Active directory LDAP auto account conference creation: On demand conferences are
automatically created if the user has an existing LDAP account .
• Web Portal customizations for look & feel: Customize your web pages on Web Portal and
or Web Conferencing servers with your company logo, colors & text
• Web Portal feature customizations: Change certain features displayed to users on the
Web Portal pages.
• Messages/Audio Files: Ability to play your custom audio file in place of standard prompts.
• Music on Hold: Ability to customize the Music on Hold.
• Import Users: Create users by importing data from a comma delimited file.
Notes on server hardware and software
• Monitor and Keyboard: Avaya does not furnish keyboards and monitors with the bridge
or servers unless specifically stated on the sales order. If included a physical location is
required for such equipment such as a rack shelf or adjacent workstation desk, and must
be provided by the customer.
• Anti-Virus Software: Avaya does not supply anti-virus software on any Avaya servers
provided. It is the customer’s responsibility to provide any required anti-virus software and
to insure this is kept up to date against current anti-virus updates.
• Microsoft OS patches: Avaya does not supply Microsoft OS patches on any Avaya servers
provided. It is the customer’s responsibility to update the Microsoft Operating System
patches when and as required.
• Customer installed software: Any 3rd party non-Avaya supplied installed applications
must receive prior approval from Avaya. It is the customer’s responsibility to insure all
such pieces of software are compatibility tested against Avaya applications.
• Customer Supplied Servers/Hardware: Avaya will allow on request customers to supply
the hardware for the CRS, WP & AWC if agreed. It is the customer’s responsibility to
insure all required software licenses are supplied such as OS, SQL, NSM or others.
Please refer to your Conferencing Consultant for or Support Representative for further
information.

Index
A automatic conference clear .......................................114

automatic gain enabled ............................................182
account number length .............................................200 automatic record all ...........................................153, 305
activate attachments .........................................209, 326 automatic security codes ..........................................128
activate attendance notifications .......................210, 327 Avaya Web Conferencing ...................................94, 231
activate e-mail notifications ...............................208, 325 AWC ....................26, 94, 95, 231–233, 235, 236, 238–241
activate SMS notifications ........................................327 administration .....................................................238
activate SMTP ...................................................210, 328 administrator passwords ....................................240
activate vcalendar .............................................210, 328 administrators .....................................................240
adapter ..............................................................471, 472 configuration .......................................................235
adding a bridge .........................................................496 configuration of ...................................................231
adding instances ...................................................54, 55 license .........................................................236, 239
adding wildcard ..........................................................78 network ...............................................................233
adhoc conferencing ..................................................134 servers ...............................................................241
AGC noise floor ........................................................182 AWC restore .............................................................271
AGC target power level ............................................182
alarming ID ...............................................................104 B
alarms .........................................................................97
allow infinite ports .....................................................194
annunciator channels ........................................149, 306 back-up ......................................................259, 261, 263
APIs ..........................................................................288 exclusions ..........................................................263
application server .........................................85, 111, 289 inclusions ...........................................................261
application server features .......................................120 backing up
architecture overview ................................................586 System Platform and solution template ..............266
ASN interval ..............................................................187 backup
attachments directory ........................................209, 326 about ..................................................................265
attendance record processing delay .................212, 330 extra steps ..........................................................269
attended originator dial out .......................................115 scheduling ..........................................................266
attribute fields ...........................................................383 two stages ..........................................................260
attribute mask ...........................................................218 viewing history ....................................................267
audio codecs ............................................................187 backup method .........................................................267
Audio Console ...................................................247, 466 Backup page
properties ...........................................................466 field descriptions ................................................268
audio messages .................................112, 291, 296–298 base RTP port ..........................................................185
audio numbers ..........................................................219 BCAPI username ......................................................217
audio quality .............................................................181 beeps
audio talker interval ..................................................187 participant entry ..................................................122
audio transcript .........................................................295 participant exit ....................................................122
audiocodes .................................................................63 bill at time ..........................................................214, 316
authenticate .......................................................211, 329 bill file extension ................................................213, 315
authentication required at login ................................195 bill file header ....................................................214, 317
auto extend conference duration ..............................123 bill file prefix ......................................................213, 315
auto extend conference ports ...................................124 bill file trailer ......................................................214, 317
auto generated passcode length .......................199, 348 bill frequency .....................................................213, 316
auto hang-up ............................................................127 Bill start offset ....................................................213, 316
automatic CDR print .................................................171 billing ...................................174, 313, 314, 317, 319–322
configuring ..................................................314, 317

date ....................................................................320 checklist ..............................................587, 589, 595, 599
date range ..........................................................321 click to call ................................................................530
interface .............................................................319 Click-to-Dial ................................................................85
introduction .........................................................313 client fields ................................................................576
layout ..................................................................313 client registration server ...........................88, 89, 91, 191
multiple bills ........................................................321 codecs ......................................................................188
rebilling ...............................................................322 comfort noise enabled ..............................................182
billing code length .....................................................155 comfort noise level ....................................................183
billing settings ...........................................................212 Communication Manager ......................................61, 62
blast dial ............................................................371, 377 communication ports ................................................569
linking to a ..........................................................377 company fields ..........................................................575
blast dial settings ......................................................138 comparisons ...............................................................15
brand prefix ...............................................................252 components ..............................................................193
branding ....................................................................459 conf name required ...................................................129
bridge ..................................................................85, 289 conference booking options ......................................421
bridge dial lists ..........................................................376 conference defaults ..................................................122
bridge features ...................................................112, 113 conference entry .......................................................122
bridge ID number ..............................................151, 306 conference entry message .......................................130
bridge record .....................................................168, 302 conference error behavior ........................................131
bridgedb ....................................................................264 conference exit .........................................................122
broadcast scheduler ..................................330–332, 334 conference exit message ..........................................130
broadcast.ini .............................................................331 conference features ...................................121, 133, 135
BSMon ..............................................................253, 484 conference language ................................................283
conference passcode ...............................................125
C conference reminder X minutes before .............208, 325
conference retention .................................................128
calendar entry form ...................................................527 conference scheduelr ...............................................469
call branding ....................................................69, 73, 75 conference secured ..................................................132
adding ..................................................................73 conference settings ..................................................125
deleting ................................................................75 conference-adapter-configuration.xml ......................545
editing ..................................................................75 conferencing
call progress timeout ................................................140 comparisons .........................................................15
call routing ...........................................................67, 136 overview ...............................................................15
campus sites .............................................................552 conferencing ID .................................................104, 221
cdom ...........................................................................41 Conferencing installation ............................................39
CDR Conferencing Manager .......................................28, 510
automatic deletion ..............................................568 configuration
fields ...................................................................565 restoring for System Platform .............................274
file management .................................................567 configuring
initialization file ...................................................567 dial out ................................................................120
interface .............................................................564 NRP ....................................................................120
ports ...................................................................569 configuring booking options ......................................419
SFTP ...........................................................569, 570 configuring on demand profiles ................................395
troubleshooting ...................................................570 configuring your model .............................................407
CDR end date filename ............................................174 connectivity .................................................................26
CDR Loader ..............................................................563 contact points ...........................................................587
CDRs ........................................................................563 country code .............................................................137
certificate cron job .....................................................................311
exporting for CRS ...............................................367 CRS ............................88, 89, 91, 191, 247, 249, 287, 548
exporting for Web Portal ....................................369 CRS and bridge association .................................55, 56
installing on CRS ................................................368 CRS virtual machine IP ..............................................29
installing on Web Portal .....................................369

crystal .......................................................................571 DTMF mapping ...................................157, 161, 164, 165
CS1K ..........................................................................64 DTMF passthrough ...................................................155
customization ............................................................459 DTMF regeneration ..................................................154
customizing Audio Console ......................................462 DVD
recommendations ................................................35
D writing ISO image .................................................35
dvds ............................................................................41
database compatibility ..............................................381
database scripts .......................................................529
date and time ..............................................................30 E
date format ...............................................................171
e-mail sender .....................................................211, 329
DDI phones ...........................................................76, 77
E.164 ........................................................................551
adding ..................................................................76
early start minutes ....................................................124
deleting ................................................................77
editing a bridge .........................................................497
default client phone number .....................................204
email .........................................................................267
default conference size .............................................135
encryption .................................................................531
definition .....................................................................15
encryption enabled ...................................................184
delay between blasts ................................................139
enrollment password ..................................104, 105, 222
deleting customizations ............................................437
ethernet media VLAN value ......................................143
demand conference profiles .....................................388
ethernet signalling VLAN value ................................142
demand profile output reports ...................................389
existing records ........................................................385
deployments ...............................................................61
export ........................................................................404
Desktop integration ....................................................85
exporting settings .....................................................402
dial lists .....................................................................376
external user participant identifier .............................206
dial out ......................................................................137
external user participant PIN ....................................207
dial string ...........................................................169, 303
dial-plan.xml .............................................................551
dialing plan ...............................................................549 F
dialout prefix .............................................................196
diff serv media TOS value ........................................142 features .....................................................................196
diff serv signalling TOS value ...................................142 Features
digital conference record playback ............133, 302, 307 Basic ....................................................................85
digits to match ............................................................68 Unified Communication ........................................86
disable data ..............................................................197 field types .................................................................384
disabling AWC permanently .....................................245 file management .......................................................567
distributing CRS .........................................................91 firewall rules ...............................................................58
DMZ ..........................................................................243 firewall service ..........................................................143
dom0 ..........................................................................41 flex call flow ..............................................................118
downloading software .................................................33 flex DAPI configuration .............................................148
drp .....................................................................133, 302 flex leader code ........................................................154
DRP auto gen fname .........................................170, 304 flex leader PIN modify ..............................................173
DSCA .........................................................355, 362–366 flex long attempts .....................................................173
editing .................................................................362 flex long time ............................................................173
on-demand conferences ....................................364 flex maximum dialout digits ......................................173
SSL ....................................................................364 flex minimum dialout digits .......................................173
synchronization ..................................................366 flex settings ...............................................................172
user data ............................................................363 flex short attempts ....................................................172
Web Portal .........................................................365 flex short time ...........................................................172
DSCA parameters ....................................................356 flexflow
DTMF ........................................................................166 passcode ............................................................125
DTMF acknowledge ..................................................167 free if cancelled X minutes before .....................214, 317
DTMF controls ..........................................................157 FTP ...........................................................................264

G unique names .....................................................387
using ...................................................................394
general configuration .........................................150, 178 importing settings .....................................................403
general settings ..................................151, 192, 193, 222 incorrect passcode ...................................................120
generating reports ....................................................562 ini file ........................................................................567
groupware clients .....................................................216 input files ..................................................................381
installing
dvds .....................................................................41
H HTTP ....................................................................44
installing patches ..................................................50, 52
hiding functionality ....................................................432
integration .........................................................469, 513
high threshold ...........................................................176
international prefix ....................................................138
hostname ....................................................................21
international sites ......................................................556
HTML format .....................................................211, 330
internationalization ....................................................285
HTTP ..........................................................................44
invalid code ...............................................................131
HTTPS ......................................................................252
invalid code entered .................................................139
invalid time of day .....................................................133
I invitation body ...........................................................219
invitation header .......................................................219
IBM ...............................513–516, 518, 521, 523, 535, 539 IP ..........................................................................21, 28
e-mail template ...................................................535 IP change ...................................................................20
encryption ...........................................................515 IP tasks .......................................................................20
implementation ...................................................523 ISO ........................................................................36, 38
Notes ..................................................................521 Linux ....................................................................36
on demand conference ......................................516 Windows ..............................................................38
Sametime ...........................................................539 ISO image
scheduled conference ........................................518 verifying on Linux-based computer ......................33
security ...............................................................514 verifying on Windows-based computer ................34
ignore DTMF commands ..........................................166 writing to DVD ......................................................35
IIS .............................................................................507
import ........................................................................404
import utility ...253, 379–390, 392, 394, 395, 398, 575–577 J
attributes ............................................................383
jar files ......................................................................533
BSMon ...............................................................253
join conference .........................................................220
database ............................................................381
junk ...........................................................................480
default values .....................................................389
duplication ..........................................................386
fields ....................................................384, 392, 394 L
finishing ..............................................................398
GUI .....................................................................390 LAN information ........................................................589
input files ............................................................381 languages ..........................................................281, 283
logging ................................................................382 LDAP .................................................................372–374
main features .....................................................380 application server configuration .........................372
on-demand .........................................................388 configuration .......................................................373
orphans ..............................................................382 CRS configuration ..............................................374
passcodes ..........................................................388 legal disclaimer .........................................................413
preparing data ....................................................381 license ...................................................................57, 58
profiles ........................................................388, 395 licensed audio ports ..................................................152
records ...............................................................385 licensing windows
reports ................................................................389 PuTTY and Xming ................................................46
significant fields ..................................................385 line overbooking ........................................................117
truncation ...........................................................387 linked messages .......................................................295

Live Meeting BSMon ...............................................................484
clients .................................................................499 configuration .......................................................486
local cities .................................................................553 gateway ..............................................................490
local countries ...........................................................555 installing .............................................................483
local prefix ................................................................138 JRE ....................................................................482
localization ..........................................281, 284–287, 289 logs .....................................................................491
internationalization .............................................286 TLS .....................................................................486
localizing Web Portal ................................................438 uninstalling .........................................................485
logging ...............................................................170, 532 Microsoft Office Communicator ................................471
logging file ................................................................382 Microsoft Outlook ...............................469, 470, 478, 479
logging on to Audio Console .....................................462 configuring ..........................................................479
login type ...................................................232, 248, 249 settings ...............................................................478
logs ..............................................................97, 109, 335 min ports available ....................................................135
logs and alarms .........................................104, 106–108 min RTCP transmission interval ...............................186
Lotus Notes ..............................................................521 min session refresh timer allowed ..............................66
Lotus Sametime ........................................................539 minimum conference duration ..................................198
low threshold ............................................................176 minimum conference size .........................................198
minimum passcode length ................................199, 351
M minimum password complexity .................................203
minimum password length ........................................203
mail from ...................................................................250 minutes between DDI reuse .....................................198
mail server ................................................................250 miscellaneous ...........................................................148
managed element ID .........................................104, 221 moderator conference hangup .................................166
manual installation ....................................................476 moderator lecture mode ...........................................166
manually restarting AWC ..........................................244 most recent list size ..................................................221
mapping rules ...........................................................551 multiple profile indicator ............................................388
max lines reached ....................................................132 music ........................................................................149
max subscribers .......................................................176 mute participants during playback ............................114
maximum concurrent channel blast ..........................139 my listener ..................................................................64
maximum conference duration .................................197
maximum conference size ........................................198 N
maximum number of conferences per booking ........198
maximum number of login attempts .........................202 name record playback .......................................113, 174
maximum passcode length ...............................199, 351 network connections ...................................................61
media codecs ...........................................................187 network performance ................................................185
media servers ............................................112, 181, 186 network type .............................................................141
configuration .......................................................186 networking ................................................................141
features ..............................................................181 NFS mounts ......................................................145, 146
Meeting Exchange Express ......................................571 notification interval ....................................................175
messages notification options ....................................................427
linking .................................................................295 notification settings ............................................208, 330
per-conference ...................................................292 notifications ...............................................................323
rules ...................................................................293 notifications subsystem .......323, 324, 330–332, 334, 480
system wide .......................................................293 initialization file ...................................................331
transcript ............................................................295 junk .....................................................................480
Microsoft ...................................................................469 settings .......................................................324, 330
Microsoft adapter .......................................471, 472, 495 templates ............................................................334
bridge .................................................................495 variables .............................................................332
components ........................................................472 NRP ...................................................................120, 174
Microsoft Live Meeting .........471, 481–486, 488, 490, 491 NRP operator timeout ...............................................174
adapter ...............................................................481 NRP seconds ............................................................113
adapter interface ................................................488 number of digits to match ...........................................68

number of SP subsequent prompts ..........................123 installing .........................................................50, 52
managing .............................................................49
pattern matching .........................................................79
O PCMA .......................................................................188
PCMU .......................................................................188
OCS adapter ................472–474, 493, 494, 501–506, 509
period of passcode overlap ...............................202, 350
.NET ...................................................................503
period to conference passcode renewal ...........200, 348
adapter ...............................................................501
period to password expiry .........................................203
audit trail .............................................................473
period to retain CDRs files ................................214, 317
client ...................................................................505
period until client disabled ........................................205
clients .................................................................509
period until conference disabled ...............................199
configuration .......................................................505
period until user disabled ..........................................205
configuring ..................................................494, 506
perpetual conference CC e-mail address .................216
feature set ..........................................................473
perpetual conference prebook period .......................216
IIS .......................................................................503
perpetual conference recipient e-mail address ......... 216
JRE ....................................................................502
perpetual conference sender e-mail address ...........216
operating environment .......................................474
perpetual conferences ..............................................214
R2 .......................................................................493
phone number ...................................................169, 303
server .................................................................504
phone number format type .......................................194
users ..................................................................509
pin code .............................................................117, 337
ODO messages ........................................................129
PIN code error 1 and 2 message ..............................130
on demand ................................................................219
PIN code error 3 message ........................................131
on demand percentage .............................................128
PIN mode ..........................................................153, 338
on hold ......................................................................116
PINs .....................................117, 337–339, 343–345, 540
on hold message frequency ......................................116
customizing e-mail .............................................345
operator assistance ..................................................115
guest ..................................................................343
operator components ................................................289
management web site ........................................344
operator help .............................................................115
placing a call ...............................................................87
operator transaction logs ..........................................170
play first person message .........................................123
operators ..................................................................148
playback ...................................................................309
originator dial out ......................................................127
playback long jump ...........................................156, 304
orphan clients ...........................................................382
playback medium jump .....................................156, 304
Outlook .....................................................................469
playback roll call .......................................................152
Outlook settings ........................................................218
playback small jump ..........................................156, 304
overbook percent ...............................................117, 194
PLDS ....................................................................31–33
overbooking ..............................................................117
downloading software ..........................................33
override mask ...........................................................217
plug-ins .....................................................................286
overview .....................................................................15
port pool usage thresholds .......................................176
port usage .................................................................598
P pre dial delay period ..........................................169, 303
preinstallation .............................................................31
packet loss concealment enabled ............................183 prerequisites .............................................................470
participant experience ..............................................284 primary bill file location ......................................212, 315
participant ID conferencing .......................................416 prompt sets .........................................112, 291, 296–298
passcode generation ................................................388 managing ...........................................................291
passcodes ...................................337, 348, 351, 414, 415 purge .........................................................................311
fields ...................................................................348 PuTTY ...........................................................46, 93, 270
use of .................................................................351
password ..................................................................238 R
passwords ................................................................240
patch management .....................................................49 RAI configuration ......................................................175
patches rebilling .....................................................................322

recite wrong passcode ..............................................114 memory issue .....................................................543
recording ............................................301, 307–310, 430 residential sites ..................................................557
configuring ..........................................................308 strong encryption ................................................542
enabling ..............................................................307 telephony diagnostics .........................................559
file management .................................................310 scan attempts ...........................................................126
managing files ....................................................310 scan time ...........................................................126, 140
parameters .........................................................301 schedule ...................................................................219
playback .............................................................309 scheduling .................................................................116
recording and playback ............................................168 scope of localization .................................................284
recurring conference options ....................................429 script libraries ...........................................................524
registering ...................................................................32 searching for customizations ....................................437
reinstalling ................................................................480 secondary bill file location .................................212, 315
remote access ..........................................................594 secret PINs ................................................340–342, 347
removing a bridge .....................................................498 secure blocks record .........................................153, 305
reports ......................................................................561 security checkbox .....................................................352
resellers ....................................................................223 security error 1 and 2 message ................................130
reservation and conference settings .........................197 security error 3 message ..........................................130
reservation fields ......................................................577 security off message .................................................130
reserved high ............................................................177 security on message .................................................130
reserved low .............................................................177 self administration ..............................449–451, 453, 457
residential sites .........................................................557 accessing ...........................................................450
response contact ........................................................65 demand conferences ..........................................451
restore ..........................259–261, 263, 271–273, 275, 276 hiding ..................................................................457
additional steps ..................................................276 specifying defaults ..............................................453
AWC ...................................................................271 specifying fields ..................................................451
disable ................................................................272 self mute ...................................................................167
exclusions ..........................................................263 self registration URL .................................................327
inclusions ...........................................................261 services ....................................................................255
PuTTY ................................................................276 Session Manager ..................................................61, 63
System Platform .................................................273 session refresh timer ..................................................65
two stages ..........................................................260 setting the navigation pane .......................................420
viewing history ....................................................275 settings .....................................................................331
Restore page SFTP ........................................................................267
field descriptions ................................................274 show roster list ..........................................................220
restoring System Platform configuration information .... sign in users ..............................................................118
274 sign ins .....................................................................120
rollcall ........................................................................113 significant fields ........................................................385
silence suppression enabled ....................................183
S silence suppression energy threshold ......................183
silent installation .......................................................477
SAL connectivity settings ..................................147, 221 Single person 1st period ...........................................123
Sametime single sign on ....................................................445, 446
campus sites ......................................................552 SIP ..................................................64, 66, 189, 190, 591
configuration ...............................................544, 545 SIP listener URI ..........................................................64
Connect ..............................................................560 SIP proxies ........................................................143, 144
dialing plan .........................................................549 site survey .........................................................585, 595
international sites ...............................................556 site timezone ............................................................195
local cities ...........................................................553 SMTP password ................................................211, 329
local countries ....................................................555 SMTP server address .......................................210, 328
log ins .................................................................541 SMTP server port ..............................................211, 328
logs .............................................................557–559 SMTP username ...............................................211, 329
mapping numbers ..............................................557

SNMP .......................................................................107 two stages ................................................................260
SOAP ........................................................................531
solution modeller ................................401, 402, 406–409
configuring your model .......................................407
U
creating a model .................................................406 udom ..........................................................................41
discarding ...........................................................409 unattended blast .......................................................133
exporting ............................................................402 unique client names ..................................................387
loading ................................................................408 unique company names ...........................................387
modelling ............................................................406 unknown number ........................................................77
saving .................................................................407 unrecognizable numbers ............................................77
solution overview ......................................................585 unreserved high ........................................................178
SP prompt waiting period .........................................123 unreserved low .........................................................178
SRTP ........................................................................184 updating hostname .....................................................21
SRTP crypto suite .....................................................185 updating IP .................................................................21
SSL ...........................................................................251 upgrading ............................................................19, 571
starting services ........................................................256 uploading files ...........................................................434
starting the bridge .....................................................498 uploading graphics ...................................................435
startup notify time .....................................................116 URI pattern ...............................................................135
stopping services ......................................................256 URI to telnum ........................................................81, 83
stopping the bridge ...................................................498 URL to reset participant secret PIN ...................206, 416
stored procedures .....................................................475 user access ..............................................................310
strong encryption ......................................................542 user settings .............................................................200
sub conferencing ...............................................166, 465 user transaction logs ................................................171
sub forms ..................................................................526 users .................................................................224, 228
system alert enabled ................................................155
system alert message ...............................................156
system configuration .........................................141, 149 V
system language ......................................................283
System Platform .........................................................25 variables ...................................................................332
verifying configuration ................................................90
verifying installation ..............................................85, 90
T vi ...............................................................................108
TDM ..........................................................................591 video .........................................................................134
tel num to URI .......................................................80, 83 video codecs .............................................................188
telephone numbers .....................................................67 video quality ..............................................................183
telephone_event .......................................................188 virtual machines ..................................................54, 255
template customizations ...........................................535 VLAN service ............................................................186
template updates ......................................................533
templates ..................................................................334 W
termination now message .........................................131
termination warning ..................................................131 warning tones ...........................................................127
testing installation .......................................................90 wav file clip ...............................................................187
time and date formats .......................................417, 418 Web components ......................................................287
time format ................................................................171 web conference ........................................................220
timeout ......................................................................132 web conferencing URL ......................................210, 327
timezones ..........................................................223, 475 Web Portal ................91–93, 248, 312, 411, 412, 414, 415
traps ..........................................................................107 administering ......................................................411
troubleshooting installation .........................................58 display ................................................................412
truncation ..................................................................387 legacy feature .....................................................312
TTY ...........................................................................183 passcodes ...................................................414, 415
TTY redundancy support enabled ............................184 recording ............................................................312
TTY support enabled ................................................184 Web Portal functionality ............................................421

Web Portal localization ......................................287, 438 workbook ..................................................................585
Web Portal look and feel ..........................................433
Web Portal password expiry .....................................443
Web Portal reports ....................................................561 X
Web Portal toolbar ....................................................464
Web Portal user authentication ................................441 Xming .........................................................................46
Web Portal virtual machine .......................................247
what you get ...............................................................18 Y
wholesalers ...............................................................229
Windows ........................................................46, 48, 238
your template ............................................................533
windows licensing .......................................................45

Avaya Aura

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avaya Aura

Uploaded by

Copyright:

Available Formats

Implementing Avaya Aura™ Conferencing

Chapter 1: Choosing Conferencing™ 6.0..............................................................................15

Chapter 2: Updating network information.............................................................................19

Chapter 3: Preinstalling Conferencing..................................................................................31

Chapter 4: Installing Conferencing........................................................................................39

Chapter 5: Connecting Conferencing to your network........................................................61

Implementing Avaya Aura™ Conferencing June 2010 3

Chapter 6: Configuring telephone numbers.........................................................................67

Chapter 7: Verifying your installation....................................................................................85

Chapter 8: Configuring logs and alarms...............................................................................97

4 Implementing Avaya Aura™ Conferencing June 2010

Chapter 9: Configuring the application server....................................................................111

Chapter 10: Configuring media settings.............................................................................181

Implementing Avaya Aura™ Conferencing June 2010 5

Chapter 11: Configuring the CRS.........................................................................................191

Chapter 12: Configuring the AWC........................................................................................231

Chapter 13: Configuring the Web Portal.............................................................................247

Chapter 14: Configuring the Conferencing watchdog.......................................................253

Chapter 15: Activating and deactivating virtual machines................................................255

6 Implementing Avaya Aura™ Conferencing June 2010

Chapter 16: Backing up and restoring settings..................................................................259

Chapter 17: Configuring languages.....................................................................................281

Chapter 18: Configuring audio messages..........................................................................291

Chapter 19: Configuring recording......................................................................................301

Implementing Avaya Aura™ Conferencing June 2010 7

Chapter 20: Producing bills for conferences......................................................................313

Chapter 21: Configuring e-mail notifications......................................................................323

8 Implementing Avaya Aura™ Conferencing June 2010

Chapter 22: Understanding PINs, passcodes, and security..............................................337

Chapter 23: Configuring LDAP for Conferencing...............................................................355

Chapter 24: Understanding blast dial..................................................................................371

Implementing Avaya Aura™ Conferencing June 2010 9

Chapter 25: Importing companies, clients, and conferences...........................................379

Chapter 26: Importing and exporting configurations........................................................401

Chapter 27: Customizing the Web Portal application........................................................411

10 Implementing Avaya Aura™ Conferencing June 2010

Chapter 28: Administering the Web Portal application......................................................441

Chapter 29: Customizing the Audio Console application................................................. 459

Chapter 30: Integrating with Microsoft applications..........................................................469

Chapter 31: Installing/configuring Conference Scheduler for Microsoft Outlook.......... 475

Chapter 32: Installing/configuring Conferencing for Microsoft Live Meeting.................481

Implementing Avaya Aura™ Conferencing June 2010 11

Chapter 33: Installing/configuring Conferencing for Microsoft Office Communicator

Chapter 34: Integrating with IBM applications...................................................................513

Chapter 35: Configuring Conferencing for IBM Lotus Notes............................................521

Chapter 36: Configuring Conferencing for IBM Lotus Sametime.....................................539

12 Implementing Avaya Aura™ Conferencing June 2010

Chapter 37: Viewing reports.................................................................................................561

Chapter 38: Loading call detail records..............................................................................563

Chapter 39: Upgrading to/from Conferencing....................................................................571

Chapter 40: Import Utility fields...........................................................................................575

Chapter 41: Avaya Aura™ Conferencing Implementation Workbook...............................585

Implementing Avaya Aura™ Conferencing June 2010 13

14 Implementing Avaya Aura™ Conferencing June 2010

Avaya Aura™ Conferencing 6.0

Conferencing comparison tables

Feature Standard Edition of Enterprise Edition of

Maximum capacity 500 4000

Implementing Avaya Aura™ Conferencing June 2010 15

Feature Standard Edition of Enterprise Edition of

Database interface (API or stored

Bridge Talk application

Real-time conference control API