Meeting Exchange 5.1

Meeting Exchange 5.1
Meeting Exchange 5.1
Release Notes for Customers
04-602764
Issue 1
October 2008
Compas ID 133428
© 2008 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, or deletions to
the original published version of this Documentation unless such modifications,
additions, or deletions were performed by Avaya.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked third
party Web sites referenced elsewhere within this Documentation and Avaya
does not necessarily endorse the products, services, or information described
or offered within them. We cannot guarantee that these links will work all of the
time and we have no control over the availability of the linked pages.
License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S
ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL
LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT
http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF
YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST
RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN
(10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.
Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the Documentation or other
materials available to End User. "Designated Processor" means a single
stand-alone computing device. "Server" means a Designated Processor that
hosts a software application to be accessed by multiple users. "Software"
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone Products or
pre-installed on Hardware. "Hardware" means the standard hardware
Products, originally sold by Avaya and ultimately utilized by End User.
License Type(s):
Concurrent User License (CU). End User may install and use the Software on
multiple Designated Processors or one or more Servers, so long as only the
licensed number of Units are accessing and using the Software at any given
time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the
pricing of its licenses and can be, without limitation, an agent, port or user, an
e-mail or voice mail account in the name of a person or corporate function
(e.g., webmaster or helpdesk), or a directory entry in the administrative
database utilized by the Product that permits one user to interface with the
Software. Units may be linked to a specific, identified Server.
Database License (DL). Customer may install and use each copy of the
Software on one Server or on multiple Servers provided that each of the
Servers on which the Software is installed communicate with no more than a
single instance of the same database.
Copyright
Except where expressly stated otherwise, the Product is protected by copyright
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense under the
applicable law.
Third-party Components
Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements ("Third Party
Components"), which may contain terms that expand or limit rights to use
certain portions of the Product ("Third Party Terms"). Information identifying the
copyright holders of the Third Party Components and the Third Party Terms
that apply is available on Avaya's web site at:
http://support.avaya.com/ThirdPartyLicense/
For full information, please see the complete document, Avaya Third Party
Terms, Document number 04-601558. To locate this document on the website,
simply go to http://www.avaya.com/support and search for the document
number in the search box.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the following Web site:
http://www.avaya.com/support.
Avaya fraud intervention
If you suspect that you are being victimized by toll fraud and you need technical
assistance or support, call Technical Service Center Toll Fraud Intervention
Hotline at +1-800-643-2353 for the United States and Canada. Suspected
security vulnerabilities with Avaya Products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
For additional support telephone numbers, see the Avaya Web site:
http://www.avaya.com/support
Trademarks
Avaya and the Avaya logo are registered trademarks of Avaya Inc. in the
United States of America and other jurisdictions. Unless otherwise provided in
this Documentation, marks identified by "®," "™" and "SM" are registered
marks, trademarks and service marks, respectively, of Avaya Inc. All other
trademarks are the property of their respective owners.
For the most current versions of documentation, go to the Avaya support Web
site: http://www.avaya.com/support
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Environment . . . . . . .
Common Server Specifications.
Hardware . . . . . . . . . . . . .
CS700/780 . . . . . . . . . .
S6800 . . . . . . . . . . . . .
Recording . . . . . . . . . . . .
S6800 . . . . . . . . . . . . .
S6200 . . . . . . . . . . . . .
Interoperability . . . . . . . . . .
CS700/780 . . . . . . . . . .
S6200 . . . . . . . . . . . . .
S6800 . . . . . . . . . . . . .
Third Party Support . . . . . . .
CS700/780 . . . . . . . . . .
S6200/S6800 . . . . . . . . .
Microsoft Server . . . . . . . . .
Microsoft Desktop Client . . . .
SQL Server . . . . . . . . . . . .
Browsers . . . . . . . . . . . . .
Avaya Web Conferencing . . . .
Software Application Summary.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
6
10
10
10
10
10
11
11
11
11
11
11
11
12
12
12
12
12
13
13
Chapter 2: Introducing Meeting Exchange 5.1 Release New Features .
14
S700/S780 . . . . . . . . . . . .
Supported upgrade paths . .
PIN codes. . . . . . . . . . .
Multiple billing code option .
Flexible ANI . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14
14
15
15
15
S6200/S6800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported upgrade paths . . . . . . . . . . . . . . . . . . . . . . .
Operating system . . . . . . . . . . . . . . . . . . . . . . . . . . .
New database called PostgreSQL . . . . . . . . . . . . . . . . . .
PIN codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dial out to a SIP URI . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple queue actions based on DNIS/DDI . . . . . . . . . . . . .
Route callers to a range of conference rooms based on DNIS/DDI
Multiple billing code option . . . . . . . . . . . . . . . . . . . . . .
Port expansion to 4000 . . . . . . . . . . . . . . . . . . . . . . . .
Support for 140 Operators . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
15
16
16
16
16
17
17
17
17
17
18
Issue 1 October 2008
2
Contents
Call supervision . . . . . . . . . . . . . . . . . . . .
Secure Bridge API . . . . . . . . . . . . . . . . . . .
SNMP changes . . . . . . . . . . . . . . . . . . . . .
SNMP version support. . . . . . . . . . . . . . .
CPU usage threshold . . . . . . . . . . . . . . .
Disk space usage threshold. . . . . . . . . . . .
Reserved and unreserved port pool thresholds .
Critical service down . . . . . . . . . . . . . . .
Critical service up . . . . . . . . . . . . . . . . .
New message for Operator assistance. . . . . . . .
.
.
.
.
.
.
.
.
.
.
18
18
18
18
19
19
19
19
20
20
Avaya Conferencing Provider API . . . . . . . . . . . . . . . . . . . . . . . . . .
21
MultiSite Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Stored Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Bridge Talk . . . . . . . . . . . . . . . . . .
Real time talker updates. . . . . . . . .
VLL selection box reduced in size . . .
Increased DNIS filter capacity . . . . .
Bridge status warning . . . . . . . . . .
Administrator changes for Bridge Talk
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
21
22
22
22
22
22
Client Registration Server. . . . . . . . . .
Conference Expiry . . . . . . . . . . . .
User Password Expiry . . . . . . . . . .
Account Expiry. . . . . . . . . . . . . .
User-Administrators and User-Auditors
User Change Log and User Status . . .
Reservation Groups . . . . . . . . . . .
Daylight Savings Time Adjustments . .
Universal Coordinated Time Field . . .
Global Conference Support . . . . . . .
New Participant Fields. . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
23
23
24
24
24
24
25
25
25
25
25
Web Portal . . . . . . . . . . . . . .
Password Expiry . . . . . . . . .
Account Expiry. . . . . . . . . .
Legal Disclaimer Free Text Field
New Adapter . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
26
26
26
27
27
Avaya Conference Scheduler Plug-in for Microsoft Outlook . . . . . . . . . . . .
Join a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SOAP Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
28
3 Meeting Exchange 5.1 Release Notes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
Chapter 3: Issues Resolved in this Release . . . . . . . . . . . . . . . .
30
S6200/S6800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
S700/S780 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
ACP API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
Avaya Bridge Talk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
MultiSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
Avaya Client Registration Server . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
Avaya Web Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
Avaya Conference Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
Avaya Plug-in for IBM Lotus Sametime . . . . . . . . . . . . . . . . . . . . . . .
42
Avaya Conference Scheduler Plug-in for Microsoft Outlook . . . . . . . . . . . .
43
Chapter 4: Known Operational Issues . . . . . . . . . . . . . . . . . . .
44
S6200/S6800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
S700/S780 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
Pyramid Configuration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
ACP API Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
Avaya Client Registration Server . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
Avaya Bridge Talk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
Avaya Web Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
Avaya Audio Console . . . . . . . . . . . . . . . . . . . . . . . .
Avaya Audio Console Advanced Configuration . . . . . . . .
Web Portal and Avaya Audio Console on a Single Server
CRS Connection Delays . . . . . . . . . . . . . . . . . . .
Web Server Connections . . . . . . . . . . . . . . . . . .
Avaya Audio Console Issues . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
55
55
55
56
56
58
Avaya Conference Scheduler Plug-in for Microsoft Outlook . . . . . . . . . . . .
59
Avaya Plug-in for IBM Lotus Sametime . . . . . . . . . . . . . . . . . . . . . . .
63
Avaya Conference Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
Adobe Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Issue 1 October 2008
4
Contents
5 Meeting Exchange 5.1 Release Notes
Chapter 1: Introduction
This document lists the new functionality and known operational issues in Meeting Exchange
5.1.
The versions of the applications shown in this document reflect those fully approved by Avaya.
The nature of the Avaya architecture allows for ongoing updates of the different software
applications on an independent basis. Please consult with the Avaya Account Manager or
Avaya support desk for ongoing updates.
Supported Environment
This section contains the following sections:
l
Common Server Specifications
l
Hardware
l
Recording
l
Interoperability
l
Third Party Support
l
Microsoft Server
l
Microsoft Desktop Client
l
SQL Server
l
Browsers
l
Avaya Web Conferencing
l
Software Application Summary
Common Server Specifications
This section contains a number of tables and describes the Avaya common server
specifications:
l
S6200, Pyramid, and S6800 Application Server
l
CRS, AWC Playback, Web Portal, OCS and CV
l
Avaya Web Conferencing
Issue 1 October 2008
6
Introduction
l
AWC Recordings Server and DRPS
l
Meeting Exchange 5.0 Server Specifications
Table 1: S6200, Pyramid, and S6800 Application Server
Note:
Application
S6200, Pyramid and S6800 Application Server
Model
Dell 1950 v3
Processor
Two Quad Core Intel® Xeon® E5440, 2x6MB Cache, 2.83GHz, 1333MHz
FSB
Memory
4 GBytes – 4 x 1 GB dual ranked FB DIMMs (667 Mhz).
Bezel
Avaya Bezel
HW Raid 1
PERC 6/i Integrated RAID controller. Supports SAS & SATA
Slot
Two full height half length PCI-E slots (2x8 lane). PCI-E Riser.
Disk Drive
Two 250GB SATA Enterprise Level 3.5” Hot Plug Hard Drives
Addl Nic
Intel® PRO 1000PT Dual Port Server Adapter, Gigabit NIC, Cu, PCIe x4
Rmv Media
8x DVD-ROM
Power Supply
Two Hot-plug Power Supplies for Redundancy
Fans
Redundant Multi-Speed Fans
Note:
The server specification in Table 1 supports capacities up to a maximum of 4000
ports (3200 ports on S6200) on G.711.
Table 2: CRS, AWC Playback, Web Portal, OCS and CV
Application
CRS, AWC Playback, Web Portal, OCS and CV
Model
Dell 1950 v3
Processor
One Quad Core Intel® Xeon® E5440, 2x6MB Cache, 2.83GHz,
1333MHz FSB
Memory
2 GBytes – 2 x 1 GB dual ranked FB DIMMs (667 Mhz).
Bezel
Avaya Bezel
HW Raid 1
PERC 6/i Integrated RAID controller. Supports SAS & SATA
Slot
Two full height half length PCI-E slots (2x8 lane). PCI-E Riser.
7 Meeting Exchange 5.1 Release Notes
Supported Environment
Table 2: CRS, AWC Playback, Web Portal, OCS and CV
Application
CRS, AWC Playback, Web Portal, OCS and CV
Disk Drive
Two 250GB SATA Enterprise Level 3.5” Hot Plug Hard Drives
Addl Nic
(none)
Rmv Media
8x DVD-ROM
Power Supply
Two Hot-plug Power Supplies for Redundancy
Fans
Redundant Multi-Speed Fans
Table 3: Avaya Web Conferencing
Application
Avaya Web Conferencing
Model
Dell 1950 v3
Processor
One Quad Core Intel® Xeon® E5440, 2x6MB Cache, 2.83GHz,
1333MHz FSB
Memory
4 GBytes – 4 x 1 GB dual ranked FB DIMMs (667 Mhz).
Bezel
Avaya Bezel
HW Raid 1
PERC 6/i Integrated RAID controller. Supports SAS & SATA
Slot
Two full height half length PCI-E slots (2x8 lane). PCI-E Riser.
Disk Drive
Two 250GB SATA Enterprise Level 3.5” Hot Plug Hard Drives
Addl Nic
(none)
Rmv Media
8x DVD-ROM
Power Supply
Two Hot-plug Power Supplies for Redundancy
Fans
Redundant Multi-Speed Fans
Table 4: AWC Recordings Server and DRPS
Application
AWC Recordings Server and DRPS
Model
HP DL385 G5, 2U Chassis. Dual socket capable
Processor
l
One -AMD Opteron 2352 Quad Core / 2.1 GHZ socket F
(1207)
l
4MB L2 + L3 Cache
(Barcelona code name)
Issue 1 October 2008
8
Introduction
Table 4: AWC Recordings Server and DRPS
Application
AWC Recordings Server and DRPS
Memory
4 GB (2x2 GB of 2:1 interleaved PC2-5300 DIMMs (DDR2-667)
with Advanced ECC capabilities. Use 2GB DIMMS only.
Bezel
Avaya Bezel
HW RAID 5
Smart Array P400 Raid controller with battery backup and 512Mb
cache.
Hot Plug Backplane
Eight Small Form Factor hot plug hard drives bays included in
base unit.
Slot
2xPCI-x / 1xPCI-e full-size Riser Cage option kit
Disk Drive
3 x 146GB SAS 2.5" 10K RPM.
Addl Nic
Two embedded NC373i Multifunction Gigabit Network Adapters
(with TCP/IP Offload Engine).
Rmv Media
DVD-ROM 8X 5.25 " internal
Video
Integrated ATI ES1000, 32MB video standard
Power Supply
Redundant hot plug AC power supply (1+1 redundancy).
Fans
N+1 Hot Plug Fully Redundant Fans Standard (included in base
unit).
Table 5: Meeting Exchange 5.0 Server Specifications
Application
S6200, Pyramid, S6800, CRS, AWC Playback, Web Portal, OCS
and CV
Model
Dell 1950
Processor
One Quad Core Intel® Xeon® X5355, 2x4MB Cache, 2.66GHz,
1333MHZ FSB
Memory
2GB 667MHZ FBD 4X512MB -1R
Bezel
Dell Bezel
HW Raid 1
PERC 5/i Integrated RAID Controller Card
Slot
Riser with PCIe Support (2x PCI Express slots)
Disk Drive
Two 146GB, SAS, 3.5-inch, 15.000 rpm Hard Drive(hot plug)
Addl Nic
Intel® PRO 1000PT Dual Port Server Adapter, Gigabit NIC, Cu, PCIe
x4
Rmv Media
24X CDRW/DVD Combo Drive, IDE, Half Heigh
9 Meeting Exchange 5.1 Release Notes
Supported Environment
Table 5: Meeting Exchange 5.0 Server Specifications
Note:
Application
S6200, Pyramid, S6800, CRS, AWC Playback, Web Portal, OCS
and CV
Power Supply
Two Hot-plug Power Supplies for Redundancy
Fans
Redundant Multi-Speed Fans
Note:
The server specifications in Table 5 support capacities up to a maximum of 2000
ports for S6200/S6800/Pyramid. All other applications are supported on Meeting
Exchange 5.1 regardless of port capacity.
Hardware
CS700/780
CPU: 5550 (700Mhz) and 5551
DSP: NS300 and NS301
S6800
SCC-II1 and SCC-III
MPC-II2 and MPC-IV
Recording
S6800
When recording completes, the 6800 server creates a link file, which is the same size as the
recording file. This link file is needed for playback purposes. This process of creating a link file
means that storage capacity is halved to approximately 2000 hours. Meeting Exchange 5.1
stores recordings as .WAV encapsulated files, which contain the audio in linear PCM format
which is both narrow band or wide band and results in a size of 16 kilobytes per second for
narrow band and 32 kilobytes per second for wide band.
1 The SCC-II will not work in CMS-9000.
2 The MPC-II will not work in CMS-9000.
Issue 1 October 2008
10
Introduction
S6200
In the Meeting Exchange 5.1 release, the 6200 server supports approximately 2100 hours of
recordings.
Interoperability
CS700/780
Audiocodes Mediant 2000
S6200
Audiocodes Mediant 2000
Cantata IMG1010 G/W (Ver: 10.5.0.249)
Element Management System Version: 10.5.0.180
Avaya Communication Manager 5.1, 5.0
Avaya SIP Enabled Server 5.1, 5.0
S6800
Audiocodes Mediant 2000
Cantata IMG1010 G/W (Ver: 10.5.0.249)
Element Management System Version: 10.5.0.180
CMS-6000 and CMS-9000
Avaya Communication Manager 5.1, 5.0
Avaya SIP Enabled Server 5.1, 5.0
Radisys Firmware Version 4.13.0.4
Third Party Support
CS700/780
Microsoft Outlook 2003 & 2007
11 Meeting Exchange 5.1 Release Notes
Supported Environment
S6200/S6800
Adobe Connect 6
IBM Lotus Notes 7.0.2
IBM Lotus Sametime 7.5.1 CF1 & 8
IBM Lotus Domino 7 & 8.0.1
Microsoft Live Communications Server 2005
Microsoft Office Communications Server 2007
Microsoft Outlook 2003 & 2007
Microsoft Live Meeting 7 & 8
Microsoft Office Communicator 1 & 2
Microsoft Server
Windows Server 2003 Standard Edition R2 (SP2)
Microsoft Desktop Client
Windows XP (SP2)
Windows Vista Business
SQL Server
SQL 2005 (SP2)
Browsers
Microsoft Internet Explorer 6 & 7
Mozilla Firefox 2.0
Issue 1 October 2008
12
Introduction
Avaya Web Conferencing
Meeting Exchange 5.1 ships with Avaya Web Conferencing 4.1.20. AWC 4.1.20 supports a
single window for conferencing. AWC 4.1.20 also supports video conferencing. For more
information, see the Avaya Web Conferencing 4.1.20 Administration Guide, which is available
on support.avaya.com.
Software Application Summary
Table 6 contains a list of Meeting Exchange 5.1 software included in this release.
Table 6: Software Application Summary
Product Area
Version Number
Avaya Web Conferencing
4.1.20.2
BCAPI/ACPI
5.1.0.0.61
Bridgetalk
5.1.0.0.12
Conference Viewer
5.1.0.0.11
Client Registration Server
5.1.0.0.20
Avaya Plug-in for IBM Lotus Sametime
5.1.0.0.6
Microsoft Adapter (MSAdapter)
5.0.0.5
Microsoft Office Communications Server Adapter (OCSAdapter)
5.1.0.0.16
Avaya Conference Scheduler Plug-in for Microsoft Outlook
5.1.0.63
S6200/S6800
5.1.0.0.161
S700
5.1.0.0.37
SOAP Adapter
5.1.0.0.35
Web Portal
5.1.0.0.24
13 Meeting Exchange 5.1 Release Notes
Chapter 2: Introducing Meeting Exchange 5.1
Release New Features
This chapter describes the new features in the Meeting Exchange 5.1 release. It contains the
following sections:
l
S700/S780
l
S6200/S6800
l
Avaya Conferencing Provider API
l
MultiSite Application
l
Stored Procedures
l
Bridge Talk
l
Client Registration Server
l
Web Portal
l
Avaya Conference Scheduler Plug-in for Microsoft Outlook
S700/S780
This section describes the S700/S780 enhancements in Meeting Exchange 5.1. It contains the
following sections:
l
Supported upgrade paths
l
PIN codes
l
Multiple billing code option
l
Flexible ANI
Supported upgrade paths
The following upgrade paths are supported:
l
5.0 GA > 5.1
l
Latest 5.0 Service Pack > 5.1
Issue 1 October 2008
14
Introducing Meeting Exchange 5.1 Release New Features
PIN codes
PIN Codes contain three new optional fields, Line Aux 1, Line Aux 2, and Line Aux 3 to allow
additional participant information to be captured for billing records. This information is added as
part of the Call Detail Record.
The PIN Code Admin utility is no longer supported on the Meeting Exchange platform. The CRS
is used to administer the PIN codes database on the bridge. Refer to the Meeting Exchange 5.1
Relational Database Guide for S700/S780 Conferencing Servers, which is available on
support.avaya.com.
Multiple billing code option
It is now possible for a moderator to be prompted for both a Billing Code and a Client Matter
code when they start a conference. This will allow billing to be generated for each end user
within a single conference. An example of this would be found in a court setting where the
billing code would reference an overall case while the separate client matter codes would define
each of the attorneys involved.
Flexible ANI
It is now possible for the bridge to count both the delimiters and the digits to determine when
digit collection is complete. This will speed the processing time for an incoming call.
S6200/S6800
This section describes the S6200/S6800 enhancements in Meeting Exchange 5.1. It contains
the following sections:
l
Supported upgrade paths
l
Operating system
l
New database called PostgreSQL
l
PIN codes
l
Dial out to a SIP URI
l
Multiple queue actions based on DNIS/DDI
l
Route callers to a range of conference rooms based on DNIS/DDI
15 Meeting Exchange 5.1 Release Notes
S6200/S6800
l
Multiple billing code option
l
Port expansion to 4000
l
Support for 140 Operators
l
Call supervision
l
Secure Bridge API
l
SNMP changes
l
New message for Operator assistance
Supported upgrade paths
The following upgrade paths are supported for any system components:
l
5.0 GA > 5.1
l
Latest 5.0 Service Pack > 5.1
Operating system
The installation program installs the following operating system:
Red Hat Enterprise Linux 4 Update 6
New database called PostgreSQL
The relational Database for the Linux-based S6200/6800 platform will be PostgreSQL version
8.1.4. When upgrading from release 5.0 to release 5.1, the upgrade shall preserve the data
contained in the Informix database.
PIN codes
PIN Codes contain three new optional fields, Line Aux 1, Line Aux 2, and Line Aux 3 to allow
additional participant information to be captured for billing records. This information shall be
added as part of the Call Detail Record.
The PIN Code Admin utility is no longer supported on the Meeting Exchange platform. The CRS
is used to administer the PIN codes database on the bridge. Refer to the Meeting Exchange 5.1
Relational Database Guide for S6200/6800 Conferencing Servers, which is available on
support.avaya.com.
Issue 1 October 2008
16
Introducing Meeting Exchange 5.1 Release New Features
Dial out to a SIP URI
It is now possible to dial out to a SIP URI in addition to a telephone number. This allows an
endpoint to be dialed without having to use the TelNumtoURI field. This feature is only
supported via an API.
Multiple queue actions based on DNIS/DDI
It is now possible to differentiate incoming calls, based on their DNIS/DDI , and provide different
queue actions when the caller enters an invalid code or the caller fails to enter any code. This
new On Failure setting in the call branding table will supersede the Timeout and Invalid Code
settings found in the Administration Menu under Configure Scheduler.
Route callers to a range of conference rooms based on DNIS/DDI
It is now possible to route callers to a range of conference rooms based on the DNIS/DDI they
use. The new Room Start and Room End fields will determine the room range to which a caller
can be sent based on their DNIS/DDI digits. It does not affect Operator function. The default
setting of 0 will allow calls to start a conference in any available room.
Multiple billing code option
It is now possible for a moderator to be prompted for both a Billing Code and a Client Matter
code when they start a conference. This will allow billing to be generated for each end user
within a single conference. An example of this would be found in a court setting where the billing
code would reference an overall case while the separate client matter codes would define each
of the attorneys involved.
Port expansion to 4000
A pyramid configuration of Meeting Exchange now supports up to 4000 ports. The S6800 also
supports 4000 ports. The S6200 supports 3200 ports.
Note:
Note:
Port capacities are G.711 only.
17 Meeting Exchange 5.1 Release Notes
S6200/S6800
Support for 140 Operators
Meeting Exchange 5.1 now supports up to 140 simultaneous Operators without Secure Socket
Layer (SSL). Meeting Exchange supports up to 70 Operators with an SSL implementation.
Call supervision
Meeting Exchange 5.1 allows for call supervision through the addition of a progress tone
simulation system for SIP calls. SIP equipment does not normally produce the traditional
audible indications of a call’s progress so Meeting Exchange produces applicable tones based
on SIP values.
Secure Bridge API
In Meeting Exchange 5.1, System Administrators can configure the BridgeTalk and the bridge
APIs to communicate with the conferencing server over the encrypted transport protocol, SSL.
The bridge APIs are ACPI and BCAPI.
SNMP changes
This section describes the SNMP enhancements in Meeting Exchange 5.1. It contains the
following sections:
l
SNMP version support
l
CPU usage threshold
l
Disk space usage threshold
l
Reserved and unreserved port pool thresholds
l
Critical service down
l
Critical service up
SNMP version support
The system now supports SNMP v3 in addition to SNMP v2.
Issue 1 October 2008
18
Introducing Meeting Exchange 5.1 Release New Features
CPU usage threshold
When CPU usage reaches or exceeds a certain threshold on systems using SNMP, an SNMP
alarm shall be sent identifying the affected system.
Disk space usage threshold
When disk usage reaches or exceeds a certain threshold on systems using SNMP, an SNMP
alarm shall be sent identifying the affected system.
Reserved and unreserved port pool thresholds
The system will allow the configuration of a system-wide setting for both reserved and
unreserved ports. When a specified percentage of either of these pools of ports is exceeded on
systems using SNMP, the system will send an SNMP trap.
Note:
For more information on each of these features, see the Meeting Exchange 5.1
S6200/S6800 Configuration Guide which is available on support.avaya.com.
Note:
Critical service down
Meeting Exchange issues a trap When one of the following system processes stops:
l
serverComs
l
softMS
l
initiPCB
l
msdispatcher
l
callhand
l
schapid
l
modapid
l
sipagent
l
cdr
l
startd
l
chdbased
l
traffic
l
timer
l
netservices
l
bridgetranslator
19 Meeting Exchange 5.1 Release Notes
S6200/S6800
l
convMS
Note:
Avaya added these new traps in response to customer enhancement requests.
Note:
Critical service up
Meeting Exchange issues a trap When one of the following system processes starts:
l
serverComs
l
softMS
l
initiPCB
l
msdispatcher
l
callhand
l
schapid
l
modapid
l
sipagent
l
cdr
l
startd
l
chdbased
l
traffic
l
timer
l
netservices
l
bridgetranslator
l
convMS
New message for Operator assistance
In Meeting Exchange 5.1, Avaya has added a new message which is played when Participants
request assistance from an Operator. In previous releases, Meeting Exchange placed
Participants in an Operator queue when they pressed *0 on their telephone keypad. In the new
release, Meeting Exchange plays a message, such as "Please wait for Operator Assistance"
and then places the Participant in an Operator queue.
Issue 1 October 2008
20
Introducing Meeting Exchange 5.1 Release New Features
Avaya Conferencing Provider API
Avaya are releasing a new Application Programming Interface (API) with the Meeting Exchange
5.1 release. The new API is called the Avaya Conferencing Provider (ACP) API. It exposes the
real time conference control functionality of BCAPI as well as Operator level conference control
functionality previously only available with Bridge Talk.
MultiSite Application
For Meeting Exchange 5.1, Avaya has made a number of enhancements to the MultiSite
functionality. The 5.1 version now contains the following new features:
l
A new Windows interface to aid Support Engineers
l
New log file maintenance to remove old log files. This feature is configurable.
l
Now supports SSL-based communication with the conferencing bridge
l
Enhanced logging details and improved diagnostics
Stored Procedures
Avaya has made a number of improvements to the stored procedures for database connectivity.
Among them were a number of customer-requested enhancements. For example, in the new
release, the p_cspi_ChangeConferencePin returns a negative value when it is run but then
subsequently fails. This ensures consistent logic with other failure codes.
Bridge Talk
This section describes the Bridge Talk enhancements in Meeting Exchange 5.1. It contains the
following sections:
l
Real time talker updates
l
VLL selection box reduced in size
l
Bridge status warning
l
Administrator changes for Bridge Talk
21 Meeting Exchange 5.1 Release Notes
Bridge Talk
Real time talker updates
The talk indications on Bridge Talk shall appear in real time, and the user shall not be able to
discern a delay. In past releases, the line talk indications would appear slightly after the person
had actually begun to speak. This feature is configurable on the bridge. Also, in this release,
there are an increased number of customizable options available to Bridge Talk System
Administrators who wish to configure how Bridge Talk Operators monitor active talkers.
VLL selection box reduced in size
The VLL selection box in the Line Detail window has been reduced in size to prevent operators
from accidentally setting lines as VLL.
Increased DNIS filter capacity
It is now possible for an operator to filter up to 50 DNIS/DDI numbers when using the DNIS
Filter feature.
Bridge status warning
A warning message will appear when a user logs into a Bridge Talk station that is connected to
a system in standby mode. This will alert an operator that the system is not currently active.
The operator can click OK to continue or Cancel to return to the login box.
Administrator changes for Bridge Talk
The following settings can only be changed by a Bridge Talk administrator:
l
Nighttime Mode
The Nighttime mode field shall be hidden by default in the Bridge Talk display. This is to
prevent operators from accidentally setting the bridge in NightTime mode which prevents
new callers from accessing the system. An administrator can set Nighttime mode to be
visible in Bridge Talk.
l
Set Answer
The Set Answer setting shall be hidden by default in the Bridge Talk display. By default all
lines are set to Answer. An administrator can set Answer to be visible in Bridge Talk.
Issue 1 October 2008
22
Introducing Meeting Exchange 5.1 Release New Features
Note:
For more information on each of these features, see the Meeting Exchange 5.1
Bridge Talk User Guide which is available on support.avaya.com.
Note:
Client Registration Server
This section describes the Client Registration Server enhancements in Meeting Exchange 5.1.
It contains the following sections:
Note:
l
Conference Expiry
l
User Password Expiry
l
Account Expiry
l
User-Administrators and User-Auditors
l
User Change Log and User Status
l
Reservation Groups
l
Daylight Savings Time Adjustments
l
Universal Coordinated Time Field
l
Global Conference Support
l
New Participant Fields
Note:
For more information on each of these features, see the Meeting Exchange 5.1
Client Registration Server System Administration Guide which is available on
support.avaya.com.
Conference Expiry
Meeting Exchange 5.1 contains new functionality to enable CRS System Administrators to
configure the suspension of any unused on-demand conferences. So, if an on-demand
conference remains unused for a configurable period such as 90 days, CRS System
Administrators can configure the CRS to suspend it. This action removes the conference from
the audio conferencing server and releases the port allocation. It is an effective resource
management tool.
23 Meeting Exchange 5.1 Release Notes
Client Registration Server
User Password Expiry
Meeting Exchange 5.1 contains new functionality to force all levels of Users to update their CRS
Front End passwords at regular intervals. CRS System Administrators can configure the
lifespan of passwords using a new system parameter from the BSRes2 database, called
PasswordExpiryThreshold. This system parameter also impacts Client password expiry.
Account Expiry
Meeting Exchange 5.1 contains new functionality to ensure that if CRS Users or Web Portal
Moderators do not log in to the conferencing system for a configurable period of time, the CRS
disables their account. This functionality impacts all CRS User levels, such as CRS
Administrators, CRS Supervisors, and CRS Operators. Similarly, it impacts CRS clients. CRS
clients equate to Web Portal Moderators. Each Web Portal Moderator has a CRS client account.
User-Administrators and User-Auditors
Meeting Exchange 5.1 contains a two new User roles. These User roles are called
User-Administrators and User-Auditors.
User-Administrators can create, edit, and delete Operators and Supervisors. They can also
view a report that show significant changes to User accounts, such as User creation, User
deletion, password changes, and so on. Avaya created the User-Administrator role for people
who are responsible for staff management.
User-Auditors can view the list of Users. They can also view a report that show significant
changes to User accounts. Their role is similar to the User-Administrator role. The main
difference between User-Administrators and User-Auditors is that User-Auditors cannot create,
edit, and delete any other Users. Avaya created the User-Auditor role for people who are
responsible for overseeing and analyzing staff resources.
User Change Log and User Status
User-Administrators and User-Auditors can view a report that show significant changes to User
accounts, such as User creation, User deletion, password changes, and so on.
Issue 1 October 2008
24
Introducing Meeting Exchange 5.1 Release New Features
Reservation Groups
The Reservation Groups feature allows Operators to schedule multiple conferences with the
same conference code at the same time. Each DDI is associated with a specific Reservation
Group. Avaya included the Reservation Groups feature in the Meeting Exchange 5.0, Service
Pack 1 release. It is now part of Meeting Exchange 5.1.
Daylight Savings Time Adjustments
This new feature relates to the CRS Stored Procedures Interface (CSPI).
For Meeting Exchange 5.1, Avaya added some new parameters to the stored procedures that
the SOAP Adaptor uses. These parameters include @DSTData and enable Meeting Exchange
5.1 to identify a Daylight Savings Time (DST) changeover that occurs during a recurring
conference booking. In the event of a DST changeover, Meeting Exchange recognizes the
impact on the individual conferences and makes adjustments accordingly. For more
information, see the Meeting Exchange 5.1 Stored Procedures Interface Guide.
Note:
Note:
All conference bookings made using the SOAP Adaptor are converted to UTC.
Universal Coordinated Time Field
In the BSRes2 database, the timezone table has a new Coordinated Universal Time (UTC) field.
This field is displayed in the Timezone tab on the CRS Front End but cannot be edited or
deleted. 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.
Global Conference Support
For Meeting Exchange 5.1, Avaya Engineers have developed a configuration solution for
ensuring the display of site-specific telephone numbers in notification e-mails. Contact Avaya
Support Engineers for more information on this configuration solution.
New Participant Fields
On the CRS Front End, Users can now add additional information about conference
Particiapnts in a number of free text fields, called Line Aux 1, 2, and 3. If the conference is an
25 Meeting Exchange 5.1 Release Notes
Web Portal
Attended Conference, this information is visible to the Operator on the BridgeTalk application.
The information also appears in billing and reporting records. Each of the three new fields
accepts up to 80 characters.
Web Portal
This section describes the Web Portal enhancements in Meeting Exchange 5.1. It contains the
following sections:
Note:
l
Password Expiry
l
Account Expiry
l
Legal Disclaimer Free Text Field
l
New Adapter
Note:
For more information on each of these features, see the Meeting Exchange 5.1
Web Portal Administrator Guide, which are available on support.avaya.com.
Password Expiry
In Meeting Exchange 5.1, Avaya has updated the Web Portal authentication mechanisms.
Password validation is now case-sensitive. In addition, passwords now have a limited lifespan.
System Administrators can configure the password expiry threshold in the System Parameters
table in the Client Registration Server (CRS) database; BSRes2.
Account Expiry
In Meeting Exchange 5.1, Avaya has added configuration parameters to create an account
inactivity threshold. With this functionality, the CRS disables the accounts of Web Portal
Moderators, Administrators, and Wholesalers who do not log in to the Web Portal for a
configurable period of time.
Issue 1 October 2008
26
Introducing Meeting Exchange 5.1 Release New Features
Legal Disclaimer Free Text Field
In Meeting Exchange 5.1, you can now configure the display of a legal disclaimer. Users will
view this legal disclaimer after they log in to the Web Portal. They can click OK to progress to
the My Schedule screen. The content is free text and is limited to 800 characters. While many
customer may use this feature to add a legal disclaimer, it can also be used to add a welcome
message or any other message of less than 800 characters.
New Adapter
In Meeting Exchange 5.1, the Avaya Audio Console is bundled with a new Bridge Control
Application Programming Interface (BCAPI) Adapter which uses the Avaya Conferencing
Provider’s Interface (ACPI). This new adaptor gives an improvement in performance for Avaya
Audio Console and also, because Avaya wrote it specifically with thread safety and concurrency
in mind, it enhances reliability.
Avaya Conference Scheduler Plug-in for Microsoft Outlook
This section describes the Avaya Conference Scheduler Plug-in for Microsoft Outlook
enhancements in Meeting Exchange 5.1. It contains the following sections:
l
Join a Conference
l
SOAP Adapter
Join a Conference
In this release, Users can now access a Join Conference button on the toolbar at the top of the
Appointment screen in Microsoft Outlook 2003 and in the Add-Ins menu of the appointment in
Microsoft Outlook 2007. Using this feature, they can select the bridge telephone number to join
the conference. System Administrators configure this feature in outlook/files/
configuration.xml, which is located on the conferencing server. It is important to note that
the Join a Conference feature is only supported for a group of users within an enterprise using
a single conferencing server. Each user must have the Avaya Conference Scheduler Plug-in for
Microsoft Outlook on their computers in order to use the feature.
27 Meeting Exchange 5.1 Release Notes
Avaya Conference Scheduler Plug-in for Microsoft Outlook
SOAP Adapter
For this release, Avaya has made a number of improvements to the SOAP Adapter. The
template for configuring scheduled conference options is more intuitive. The text of error
messages is now more informative. The SOAP Adapter can now recover from a restart of the
CRS. Avaya has also improved timezone management and added a new RPM to the
installation of the conferencing server called soap-on-mx-5-x.x.x.i386.rpm.
Issue 1 October 2008
28
Introducing Meeting Exchange 5.1 Release New Features
29 Meeting Exchange 5.1 Release Notes
Chapter 3: Issues Resolved in this Release
This chapter describes the issues that are resolved in Meeting Exchange 5.1. It contains the
following sections:
l
S6200/S6800
l
S700/S780
l
ACP API
l
Avaya Bridge Talk
l
MultiSite
l
Avaya Client Registration Server
l
Avaya Web Portal
l
Avaya Conference Viewer
l
Avaya Plug-in for IBM Lotus Sametime
l
Avaya Conference Scheduler Plug-in for Microsoft Outlook
S6200/S6800
Table 7: S6200/S6800 Resolved Issues
MR Number
Description
RNDCS00052675
After an upgrade, processing of new calls can be slow when the
server is busy.
Workaround: Reboot the server after the upgrade.
RNDCS00053615
After an MPC is reset, the SJ Phone audio is distorted on systems
with more than 1000 active calls.
113449
RNDCS00016551
If a user disconnects from a call during the NRP request, some
CDR fields may be blank or contain incorrect information.
If the first person to join the conference drops the line, these fields
are blank:
CrossRef, ConfirmNum, ConferenceName.
If the second or later person to join the conference drops the line,
the conferenceEntryTime field displays 00:00 GMT.
1 of 3
Issue 1 October 2008
30
Issues Resolved in this Release
Table 7: S6200/S6800 Resolved Issues
MR Number
Description
RNDCS00048704
Mxmonitor did not produce a core file when the process was killed
with signal 11.
RNDCS00049493
A moderator connected via Adobe Acrobat Connect Professional
can dial out from conference that has Block Dial Out enabled in
the reservation.
Note:
Note:
This has been determined to be an Adobe
Connect issue.
RNDCS00052675
After an upgrade, processing of new calls can be slow when the
server is busy.
Workaround: Reboot the server after the upgrade.
RNDCS00056940
Loss of audio due to sipagent issue
In previous releases, if the conferencing server received a 491
request when it tried to complete a re-invite to move a call from
MPC 1 to MPC 2, it did not complete its transaction. This behavior
caused Msdispatcher to loose track of the channel. As a result,
the call lost audio. For Meeting Exchange 5.1, Avaya enhanced
the sipagent to handle this instance.
RNDCS00059164
Issue regarding loss of SNMP following an IP change
In previous releases, the server lost SNMP functionality after an
IP address update. For Meeting Exchange 5.1, Avaya produced a
new script to resolve this issue. System Administrators should run
ip_Change_Mx_Cs.sh instead of the old script: ipChange.sh.
RNDCS00059231
Type of Service (TOS) value ineffective for signaling
In previous releases, the value of TOS only applied to media
messages and not signaling messages. For Meeting Exchange
5.1, Avaya updated the system.cfg file to ensure that the TOS
value applies to both media and signaling for inbound and
outbound calls.
RNDCS00059195
Calls dropped when LAN is disconnected
In previous releases with an active/standby server configuration,
calls were dropped in a LAN failover situation. This was due to the
fact that the failed master server attempted to connect the calls. In
Meeting Exchange 5.1, Avaya updated mxMonitor to resolve the
issue. The relevant parameters in mxMonitor are configurable.
2 of 3
31 Meeting Exchange 5.1 Release Notes
S6200/S6800
Table 7: S6200/S6800 Resolved Issues
MR Number
Description
RNDCS00059670
Music on audiopath between Operator and Participant
In previous releases, the conferencing server played music when
a Participant requested Operator assistance during conferences
that had music enabled. In Meeting Exchange 5.1, music is
disabled in the call flow engine instead of being inherited from the
main conference. The issue no longer occurs.
RNDCS00056351
Bridge Talk talkers
In previous releases, the display of the talkers on the Bridge Talk
interface did not update in real time. For Meeting Exchange 5.1,
Avaya updated the refresh interval to ensure a more immediate
response.
RNDCS00056352
Progress tones on dialout
In previous releases, when Operators or Moderators dialed out
from a conference, they did not hear any progress tones and so
did not know if the call was successful. In Meeting Exchange 5.1,
they can now hear the tones and so can detect if the line is busy.
RNDCS00057875
Missing domain information
In previous releases, the domain information was removed from
the /etc/hosts file when customers ran the mx-ipChange
script following a change of IP address. When domain information
is missing, coreservies cannot be upgraded. In the current
release, this script has been replaced and the issue no longer
occurs.
RNDCS00058170
Active/Standby server
In previous releases with an active/standby server configuration,
the S6200/S6800 bridge servers could not communicate their
status to the CRS server. In this release, Avaya has improved
communications between the bridge and the CRS. Now, the CRS
Front End updates to accurately show the active bridge.
RNDCS00058204
Modapi core dumps
In previous releases, the Modapi core-dumped when it received
an invalid channel. It should display an error message instead. In
Meeting Exchange, Avaya addressed this issue and it no longer
occurs.
RNDCS00052985
Informix ODBC error
In order for the Self Registration component to operate
successfully, your Web Portal configuration requires an Informix
ODBC driver. In previous releases of Meeting Exchange, the
Informix ODBC driver failed if you enabled the Meeting Exchange
Bridge Firewall. In this release, Avaya addressed this issue by
opening port 1525 on the audio conferencing server.
3 of 3
Issue 1 October 2008
32
Issues Resolved in this Release
S700/S780
Table 8: S700/S780 Resolved Issues
MR Number
Description
RNDCS00051539
Running isdnmgr -stop command may result in the wrong T1
board stopping when initiating a hot swap. Verify the correct
board has stopped prior to removing board from the chassis.
RNDCS00046863
T1 clock glitch causes PRI boards to drop their clock resulting in
loss of audio.
RNDCS00051534
Hot swapping a T1 board can result in static being heard on
trunks on other T1 boards in the system.
RNDCS00057481
EPV memory too small
In previous releases, EPV did not correctly respond after a certain
point. The EPV memory was large enough to include the
increasingly expanding features of Meeting Exchange. In Meeting
Exchange 5.1, Avaya addressed this issue and made the memory
buffer an unlimited size. This issue was also fixed for the S6200/
S6800 servers.
RNDCS00057223
Incorrect time on conference recordings
In previous releases, the system displayed the incorrect times
next to conference recordings on the bridge. For Meeting
Exchange 5.1 release, Avaya changed the implementation of the
time display feature to resolve this issue.
RNDCS00054194
Incorrect message played during a dial out
In previous releases, in certain circumstances, the server played
an incorrect message to Participants that were dialed by the
Moderator during a dial out from a conference. This issue was
specifically related to message 243 when the Direct to Conf
setting was selected. In Meeting Exchange, Avaya improved blast
dial functionality to elimate this problem.
RNDCS00057266
Virtual link line appears to be in use
In previous releases, when a caller disconnected from a virtual
link line (VLL) during a flex flow conference, the server kept the
VLL setting as Y. On the Bridge Talk interface, the VLL appeared
to be in use. Avaya addressed this issue in Meeting Exchange 5.1
and it no longer occurs.
33 Meeting Exchange 5.1 Release Notes
ACP API
ACP API
Table 9: BCAPI Resolved Issue
MR Number
Description
RNDCS00057987
Pausing and resuming conference playback
In previous releases of Meeting Exchange, when BCAPI issued a
command to pause and then resume the playback of a
conferencing recording, the command did not execute
successfully. Avaya addressed this issue in Meeting Exchange
5.1 and corrected the BCAPI behavior.
Avaya Bridge Talk
Table 10: Avaya Bridge Talk Issue
MR Number
Description
RNDCS00059686
Roll call feature deactivated
In previous releases of Meeting Exchange, the Bridge
Talk application occasionally switched off the roll call
conference property. This issue occurred when an
Operator viewed the conference details in Bridge Talk and
clicked OK on the conference details dialog. Avaya fixed
this issue in Meeting Exchange 5.1.
Issue 1 October 2008
34
Issues Resolved in this Release
MultiSite
This section describes the MultiSite issues that are resolved in Meeting Exchange 5.1.
Table 11: MultiSite Resolved Issues
MR Number
Issue
RNDCS00050578
Multisite conferences dropped if MultiSite Engine
Restarts
In previous releases of Meeting Exchange, if the Multisite
Engine (MSE) was restarted, the active Multi Site
conferences were dropped. This issue was due to a
synchronization issue between the CRS and the bridge. In
Meeting Exchange 5.1, Avaya addressed this issue and it
no longer occurs.
RNDCS00058456
Multisite log purge
In previous releases, the Multisite logs did not purge when
they reached a certain size. In Meeting Exchange 5.1,
MultiSite.exe has been replaced by MSE.exe.
MSE.exe has the desired functionality. and can specify:
l
how many logs to keep
l
the size of the log files
MSE.exe will automatically delete logs based on these
settings.
RNDCS00046471
Virtual link line (VLL) issue
In previous releases of Meeting Exchange, if a VLL
between two Multi Site locations failed, the MSE did not
attempt to reconnect the dropped VLL. In Meeting
Exchange 5.1, Avaya addressed this issue and it no longer
occurs.
RNDCS00034993
Inactive hubs are activated
In previous releases, the MSE occasionally created VLLs to
Multi Site hub locations even if there were no callers in that
particular location. This issue was due to a synchronization
issue between the CRS and the bridge. In Meeting
Exchange 5.1, Avaya addressed this issue and it no longer
occurs.
35 Meeting Exchange 5.1 Release Notes
Avaya Client Registration Server
Avaya Client Registration Server
Table 12: CRS Resolved Issues
MR Number
Description
RNDCS0005547
Error in MSI Installer
In previous releases, System Administrators
had to ensure that they ran the Service Pack MSI Installer
only once. If System Administrators ran the Service Pack
MSI Installer and then ran it again, the MSI Installer did not
install the service pack components successfully. This issue
occurred if System Administrators altered an installation
configuration setting while running the MSI Installer for the
second time. In this release, Avaya addressed the issue
and it no longer occurs.
RNDCS00052980
Inconsistent use of the terms Pincode and Passcode
In previous releases, the CRS Front End used the term
Pincode to refer to conference codes. Throughout the rest
of the Meeting Exchange suite, the components used the
term Passcode. In Meeting Exchange 5.1, Avaya
addressed this issue and ensured consistency of
terminology across all applications.
RNDCS00052982
Error in Participant PIN display
In previous releases of the CRS Front End, if Operators
created a Participant and allocated a User PIN to the new
Participant, the PIN field appeared as blank. In Meeting
Exchange 5.1, this field is now populated by the User PIN
information.
RNDCS00053062
PCReports error
In previous releases of Meeting Exchange, the PCReports
application had a time and date error. The Next Process
Time field was set to 1999 and System Administrators had
to manually edit it. Avaya partially addressed this issue in
Meeting Exchange 5.1 by adding some logic. Now, the
Next Process Time field is set to 01-01-<current
year>-1.
RNDCS00053114
In-progress display error
In previous releases, if Users opened an on-demand
conference, the CRS Front End displayed the conference
as Confirmed rather than the correct state of
In-progress. In Meeting Exchange 5.1, Avaya addressed
this issue and now the conference state on CRS is updated
as conferences open and close on the audio conferencing
bridge.
Issue 1 October 2008
36
Issues Resolved in this Release
Table 12: CRS Resolved Issues
MR Number
Description
RNDCS00054293
NULL fields in reports
In previous releases of Meeting Exchange, the CRS did not
populate some of the fields in the Global Post Conference
Report. This issue related in particular to the
pg_cspi_GetPostCDRConfList call. The server
returned NULL values in the Global ID and Client Name
fields. Avaya fixed this issue for Meeting Exchange 5.1.
RNDCS00055571
MSI Error if multiple cabinets
In previous releases, if a System Administrator ran the MSI
Installer on a system which had multiple cabinets, the MSI
Installer updated the main SCManager.exe application but
did not update the SCManager.exe in each of the bridge
directories. Avaya addressed this issue for Meeting
Exchange 5.1 and the issue no longer occurs.
RNDCS00058152
Second conference deleted
In previous releases, if a Moderator had to make two
attempts to book a conference, the conferencing server
deleted the conference from the audio conference bridge.
For example, if a Moderator tried to book a conference for a
certain time but the booking failed due to insufficient port
availability at that time, the Moderator’s second attempt
would be deleted by the bridge. This issue was a CRS issue
but only occurred when the booking was made using the
Web Portal. In Meeting Exchange 5.1, the issue no longer
occurs.
RNDCS00058782
Incompatibility between Notifications Subsystem and
DoRenewPasscodes parameter
In previous releases, the conferencing server could not
easily delete the conferences of Users who did not renew
their passcodes within the configurable period. This issue
occurred when the automatic e-mail setting in the passcode
renew feature was disabled. In the current release,
conferences can be deleted regardless of the automatic
e-mail setting.
RNDCS00059641
p_ExtendPerpetualConf error
In previous releases, this stored procedure caused the
extendperpetualConf job to fail due to an arithmetic
overflow error. Avaya updated this stored procedure and
resolved the problem in Meeting Exchange 5.1.
37 Meeting Exchange 5.1 Release Notes
Avaya Client Registration Server
Table 12: CRS Resolved Issues
MR Number
Description
RNDCS00059642
Perpetual conference logs
In sites that use perpetual conferencing, the log setting is
typically set to debug so that System Administrators can
monitor any issues with the perpetual conferencing feature.
In previous releases, these logs grew very large because
the server did not maintain them by deleting old entries.
Avaya addressed this issue in Meeting Exchange 5.1 and
now the p_ExtendPerpetualConf(s) stored procedure
clears debug entries that are older than two months.
RNDCS00059709
Field 319 missing from report
In previous releases, this field was missing from the post
conference report. The field outputted the string:
BAD-FIELD-SEQUENCE instead of the correct value. This
field is configured using the bsimport.ini file. In Meeting
Exchange 5.1, this issue has been fixed.
RNDCS00058507
PIN List automatically specified
In previous releases of the CRS Front End, when Operators
made a booking that specified Participant entry using the
Conference PIN feature, they had to enter a PIN List name.
IN Meeting Exchange 5.1, they can leave the PIN List field
as blank. They do not have to enter a PIN list name. The
server automatically associates the conference PIN list to
the conference.
Issue 1 October 2008
38
Issues Resolved in this Release
Avaya Web Portal
Table 13: Web Portal Resolved Issues
MR Number
Description
RNDCS00053244
E-mail address validation error in Web Portal
In previous releases, the Web Portal did not accept certain
User e-mail addresses for User account information. The
Web Portal accepted simple e-mail addresses, such as
name@company.com but often rejected more complex
e-mail addresses, such as name@company.abc.cde.te.
In Meeting Exchange 5.1, Avaya addressed this issue and
now the Web Portal accepts a wide range of e-mail
address information.
RNDCS00053113
Search option NULL error
In previous releases, if a User searched for a client and
attempted to view their schedule of conferences, the Web
Portal occasionally returned an unintuitive error message.
The error message text was NULL. In Meeting Exchange
5.1, Avaya addressed this issue and it no longer occurs.
RNDCS00052047
Requirement to manually create a folder
On the Web Portal, an SSL configuration requires the
following folder: C:\Avaya\Mx50\Apache2\conf\ssl.
In previous releases, System Administrators had to
manually create this folder because it did not exist. In
Meeting Exchange 5.1, Avaya addressed this issue and
now selfsign.bat installs this folder.
RNDCS00059058
Cost Center field modification issue
If a System Administrator used the Form Fields tab to
hide the display of the Cost Center field, Moderators could
not modify certain conference bookings. This issue was
specifically related to a User making multiple modifications
following a failed booking on the first attempt. In Meeting
Exchange 5.1, Avaya addressed the issue and also
improved some error message text.
RNDCS00059530
Partially displayed e-mail address
If System Administrators configured Moderator account
details to be uneditable and they also configured the
Moderator e-mail address field to accept the maximum
number of characters, the Web Portal did not display some
of the e-mail address on the Moderator’s interface. In
Meeting Exchange 5.1, Avaya changed common.xsl to
address this issue and it no longer occurs.
39 Meeting Exchange 5.1 Release Notes
Avaya Web Portal
Table 13: Web Portal Resolved Issues
MR Number
Description
RNDCS00057407
Music source confusion
In previous releases, if System Administrators enabled
conference music but hid the Music Source field for
Moderators, the server did not schedule music for the
conference. Avaya updated the implementation of music
functionality in Meeting Exchange 5.1 to eliminate this
issue.
RNDCS00059573
Audio Console and special characters in client name
In previous releases, if a client name contained the &
character, Audio Console did not successfully launch. In
Meeting Exchange 5.1, Avaya updated
ConferenceManagerURLGenerator.java to resolve
this issue.
RNDCS00058199
Web Portal link
Previous releases of Web Portal used a specific Web
Portal link related to the Web Portal version number.
Certain upgrade paths caused this link to fail. In Meeting
Exchange 5.1, Avaya addressed this issue to make the
Web Portal link more generic.
RNDCS00057996
Avaya Web Conferencing window too small
In previous releases, if Moderators launched the Avaya
Web Conferencing application using the Console button
on the Web Portal, the resulting AWC window was too
small. In Meeting Exchange 5.1, Avaya addressed this
issue. However, due to Microsoft Internet Explorer
limitations, Avaya had to hardcode the AWC window size
to 800x600 for this browser.
Issue 1 October 2008
40
Issues Resolved in this Release
Table 13: Web Portal Resolved Issues
MR Number
Description
RNDCS00058343
RNDCS00056674
PIN list issue
In previous releases, Moderators could use Web Portal to
book a conference that used Conference PIN as an entry
criterion, without entering a PIN list name in the PIN List
field. In these previous releases, the PIN List field was still
active and enabled. Now, in Meeting Exchange 5.1, Avaya
has modified the display of this field. The PIN List field is
now inaccessible. Web Portal automatically associates the
conference PIN list with the conference. For more
information, see the Meeting Exchange 5.1 Web Portal
User Guide, which is available on support.avaya.com.
RNDCS00059059
If a System Administrator used the Form Fields tab to
hide the display of the Multisite field, Moderators could not
modify certain conference bookings. This issue was
specifically related to a User making multiple modifications
following a failed booking on the first attempt. In Meeting
Exchange 5.1, Avaya addressed the issue and also
improved some error message text.
Avaya Conference Viewer
Table 14: Avaya Conference Viewer Issues
MR Number
Description
RNDCS00057994
Installation issue with Java Virtual Machine
For Meeting Exchange 5.1, Avaya has produced a new
version of the Conference Viewer installer. This new
installer fixes an issue that was present in previous
releases. If a customer attempted to install the application
on a system which incorporated JVM, the installation
failed. This issue no longer occurs in the new installer.
41 Meeting Exchange 5.1 Release Notes
Avaya Plug-in for IBM Lotus Sametime
Table 14: Avaya Conference Viewer Issues
MR Number
Description
RNDCS00053124
Issue with Internet Explorer 7
In previous releases of Meeting Exchange, Conference
Viewer was not fully compatible with Internet Explorer 7.
In Meeting Exchange 5.1, Conference Viewer fully
supports Internet Explorer 7.
RNDCS00056671
JVM memory leak
In previous releases of Meeting Exchange 5.1,
Conference Viewer stopped responding after a number of
weeks and a reboot was required. The issue was due to a
JVM memory leak. Avaya addressed this problem in the
current release and it no longer occurs.
Avaya Plug-in for IBM Lotus Sametime
Table 15: Avaya Plug-in for IBM Lotus Sametime Resolved Issues
MR Number
Description
RNDCS00038616
RNDCS00049959
Connect Client error
In prevous releases of the Avaya Plug-in for IBM Lotus
Sametime, if a User selected a number of other Users and
used the Call > Start a Call feature from their right-click
menu, this feature occasionally became unavailable for
future audio conference calls. This issue now no longer
occurs.
RNDCS00054192
Permitted characters in the dial-plan.xml file
In previous releases, the dial-plan.xml file did not
permit the + character. This character is important in
relation to international dial codes. Avaya addressed this
issue in the dial-plan.xml for Meeting Exchange 5.1.
Issue 1 October 2008
42
Issues Resolved in this Release
Avaya Conference Scheduler Plug-in for Microsoft Outlook
Table 16: Avaya Conference Scheduler Plug-in for Microsoft Outlook
MR Number
Description
RNDCS00055780
Editing recurring conferences
In previous versions, an issue occurred when Users tried to
edit recurring conferences. Specifically, if Users tried to
update the date or time and apply it to the entire recurrence
series, the Client Registration Server did not record this
change. The issue was due to a fault in the stored
procedures. In Meeting Exchange 5.1, this issue no longer
occurs.
RNDCS00054138
Error with recurring conferences spanning DST change
In previous release, the Avaya Plug-in for Microsoft Outlook
occasionally did accurately calculate the correct time for
recurring conferences that occurred across a daylight
savings time conversion. Avaya fixed this issue in the
SOAP Adapter for Meeting Exchange 5.1.
RNDCS00052185
Blank SIP URI field in meeting invitation
In previous versions of the meeting details screen, the
Avaya Plug-in for Microsoft Outlook did not display the SIP
URI details. The SIP URI field was blank. For Meeting
Exchange 5.1, Avaya made a large number of changes to
the meeting details screen. The fields are now more
intuitive.
RNDCS00055774
RNDCS00055735
Dragging and dropping
In the last release, Users could not drag and drop a single
instance of a recurring conference to edit the date of the
conference. Users had to delete the conference series and
create a new one. Avaya addressed this issue for Meeting
Exchange 5.1 and it no longer occurs.
RNDCS00055781
Changing to single conference to a recurring
conference
In previous releases, Users could not edit a single instance
conference to make it a recurring conference. If Users tried
to make this change, the CRS did not update the
conference on the audio conferencing server. For Meeting
Exchange 5.1, Avaya made some changes to the SOAP
Adapter and now, this issue no longer occurs.
43 Meeting Exchange 5.1 Release Notes
Chapter 4: Known Operational Issues
Note:
Avaya no longer consider RNDCS00018002, RNDCS00019614,
RNDCS00019913, RNDCS00020072, RNDCS00020221, RNDCS00020224,
and RNDCS00018648, RNDCS00021678, RNDCS00024966,
RNDCS00026622, RNDCS00017213, RNDCS00017830, RNDCS00057134 to
be known operational issues.
Note:
This chapter is divided into the following sections:
l
S6200/S6800
l
S700/S780
l
Pyramid Configuration Issues
l
ACP API Issues
l
Avaya Client Registration Server
l
Avaya Bridge Talk
l
Avaya Audio Console
l
Avaya Conference Scheduler Plug-in for Microsoft Outlook
l
Avaya Plug-in for IBM Lotus Sametime
l
Avaya Conference Viewer
l
Adobe Connect
S6200/S6800
This section describes the known issues in the S6200/S6800.
Table 17: Operational Issues for the S6X00 Media Servers
MR Number
Description
RNDCS00050780
It is necessary to log into the server as a superuser to copy the EPW
file from dcbguest to the working directory.
SPR 203200
RNDCS00019750
The first entry on a dial list may fail to connect when using Bridge Talk
to Re-blast the dial list.
1 of 6
Issue 1 October 2008
44
Known Operational Issues
Table 17: Operational Issues for the S6X00 Media Servers
MR Number
Description
RNDCS00039034
When music channels are activated by dialing into the server, if music
channel 2, 3, or 4 is assigned to a conference, only music channel 1
will play. The music channels play correctly if the server dials out to
activate music.
RNDCS00048809
Setting Auto Extend Ports to ON in a flex call causes conference to
not fill to capacity.
Workaround: Do not use Auto Extend Ports for flex calls.
RNDCS00050222
No DTMF received on some channels when 1800 callers try to access
a conference simultaneously.
RNDCS00057014
Automate the merging of new default /usr/ipcb/config parameters
during upgrade, while preserving existing settings
New default parameters introduced in a target build will not be
implemented after an upgrade (/usr/ipcb/config).
RNDCS00055320
Audio path open as a new Participant joins a conference
When a new Participant joins a conference on the S6800
conferencing bridge, any Participants who are already in the
conference can hear the new Participant while the conferencing
bridge places the new Participant in the conference. The existing
Participants typically only hear the new Participant for less than a
second.
RNDCS00051138
Recording starts early
The S6800 conferencing bridge starts to record a conference a
fraction of a second too early. The S6800 conferencing bridge starts
recording as it plays the annunciator message to indicate that
recording is about to start.
RNDCS00050393
Unmute functionality in Line Listen dialog
If you use the Line Listen dialog to select a line and mute it, the
unmute function may not operate successfully if you navigate away
from the line.
Workaround: Mute the line and then unmute the line from the
conference room instead.
RNDCS00057886
Tones played into conference
If the System Administrator configures the conferencing server with a
Communication Manager or Audio Codes gateway and disables the
conference tones, the conferencing server may still play tones into the
conference under certain conditions. This situation occurs when the
gateway is configured for in-band DTMF.
2 of 6
45 Meeting Exchange 5.1 Release Notes
S6200/S6800
Table 17: Operational Issues for the S6X00 Media Servers
MR Number
Description
RNDCS00059431
Viewing large reports causes a delay
If there are a large number of Bridge Talk sessions simulataneously
occuring and an Operator requests a large amount of report data, the
conferencing server may experience delays. This issue is only likely to
occur when more than 50 instances of Bridge Talk are open and the
system has a large number of ports.
RNDCS00059483
Fast forwarding through recordings
If an Operator or a Conferee plays conference recordings from the
conferencing bridge, the fast forward feature does not operate
properly. As a result, Operators and Conferees must listen to the
playback from the start and cannot skip forward.
RNDCS00059458
French audio prompts
The folder that contains the French audio prompts does not contain
the numbers configuration file. The file is missing. This file is required
for a number of features such as the roll call feature and the dialout
feature.
RNDCS00055218
Music set to ON in conference room 1
By default, the music setting should be set to Music=OFF in
conference room 1. This issue is significant because if Operators
establish a dialog, they will hear music because the conferencing
server automatically places them in conference room 1.
RNDCS00051226
Issue when video is enabled on Communication Manager
In a very limited number of circumstances, the S6200 conferencing
bridge may reject a call if the Communication Manager has video
enabled. This issue only occurs when calls are routed through an
Avaya SIP phone to an SES using Communication Manager.
Workaround: Disable IP Video on the Communication Manager
signal group.
RNDCS00059529
Moderator line muted during playback
While the conferencing server is playing back a conference recording,
Moderator telephone lines are in a muted state. This issue only occurs
during playback and not during the actual conference.
RNDCS00059422
Issue when Participant fails to press #
If a Participant fails to press # when they enter their passcode on their
keypad after 3 attempts, the conferencing bridge either places them in
the Operator queue or directly into the conference. In a Pyramid
configuration with a flexflow conference, the first option is not
supported.
3 of 6
Issue 1 October 2008
46
Known Operational Issues
Table 17: Operational Issues for the S6X00 Media Servers
MR Number
Description
RNDCS00059396
Blast dial entry following an invalid passcode
When the conferencing server dials a group of callers, a System
Administrator can configure the server to request a passcode prior to
granting conference access to the callers. Depending on the settings,
the conferencing server may place the callers in the pending queue in
a mute status if they enter an invalid passcode. The relevant settings
are Scan Time and Invalid Code.
RNDCS00059366
Incorrect conference PINs
In a conference with Conference PINs enabled, if a Participant enters
an incorrect PIN, followed by their correct PIN, the conferencing
server may not accept the corrected PIN.
Workaround: Participants should hang up, dial into the conference
again, and re-enter their passcode and PIN.
RNDCS00059255
Warning message not played in sub-conference
In a configuration with Moderator Hang-up enabled, Participants in
sub-conferences may not hear a warning message prior to
disconnection if the Moderator leaves the conference. This issue only
occurs if the Moderator is in the main conference of a Flexflow or a
SCAN-type conference
RNDCS00058904
Incompatibility of message prompts if rollback occurs
After they perform an upgrade from Meeting Exchange 5.0 to 5.1,
System Administrators can roll back to 5.0. If they roll back, they must
manually replace the audio prompts in the appropriate folders. This
issue is due to the fact that 5.0 uses a different message format than
5.1. This issue is documented in the Meeting Exchange 5.1 S6200/
6800 Configuration Guide.
RNDCS00058010
No longer possible to allocate different responses to two
Participant actions
In previous releases, System Administrators could assign a certain
server response when a Participant entered an invalid passcode and
another server response when a Participant did not enter any
passcode. In Meeting Exchange 5.1, the server response to both
situations must be the same. So, for example, if the System
Administrator configures a disconnection response to an invalid
passcode, the server will also disconnect the Participant if they do not
enter any passcode.
RNDCS00059377
If the partition fills to 100%, the server does not accept calls
If the shared partition reaches 100% usage, the S6200 conferencing
server no longer accepts calls. This issue can occur during heavy
load, especially if the recording facility is active and /usr3/confrp
reaches the maximum size.
4 of 6
47 Meeting Exchange 5.1 Release Notes
S6200/S6800
Table 17: Operational Issues for the S6X00 Media Servers
MR Number
Description
RNDCS00058521
cbutil error
cbutil lookup enables System Administrators to search the Call
Branding table for a specific entry. In the current release, the cbutil
lookup facility returns incorrect information.
RNDCS00058833
cpartition information error
cpartition is the common installer partition manager.
According to the man page, the following command: cpartition
-o
should make the current standby partition active upon the next reboot
only, reverting to current active partition on subsequent reboots.
However, on the Dell 1950 server, this is not the case. The command:
cpartition -o
makes the current standby partition active, on all reboots.
RNDCS00058967
Incomplete copying of files during an upgrade
During a Meeting Exchange upgrade, a number of files from /root2/
usr/dcb are copied across to the new directory. Not all files are
copied. For example, you may want to copy utlogs and traffic
stats.
RNDCS00059503
Incorrect default value for encryption
In the file, chdbased.reg, there is a new parameter for Meeting
Exchange 5.1. This parameter enables encryption and is called
enable_encryption. By default, it should be set to false (0). In
the current release, it is set to true.
RNDCS00059681
ModAPI logging error
If ModAPI logging is active and an Operator transfers a line from one
conference to another, using Bridge Talk, the ModAPI logging
encounters errors. It "cores".
RNDCS00059692
Modapi status information inaccurate
In the current release of the Moderator API, the
opapi_msg_channels information may be inaccurate if a channel is
disconnected. For example, Multiste is a ModAPI client user and
opapi_msg_channels may show the wrong status for virtual link
lines or Moderators.
RNDCS00059732
No option for changing the host name after IP change
When System Administators run the mx-ipChange.sh script, they can
no longer change the server hostname. Avaya removed the option to
update the hostname from the 5.1 release of Meeting Exchange.
Avaya took this action because the hostname change option caused
some issues with SNMP traps.
5 of 6
Issue 1 October 2008
48
Known Operational Issues
Table 17: Operational Issues for the S6X00 Media Servers
MR Number
Description
RNDCS00059733
Name Record Playback (NRP) issues with large files
Occasionally, the NRP feature duplicates or omits recorded
Participant names during playback. This problem occurs when the
NRP file exceeds 120K, which, with a sampling of 16K/sec, occurs
after 7.5 seconds. The 120 K file size is the default value of
globalReadCacheBufferSize=120000 in the
softMediaServer.cfg file.
RNDCS00059705
Listener error following a large number of crisis alerts
In the current release, the Listener may encounter an error when a
performance crisis alert request runs for 200 times. The error
message is logged in the notificationCtrlServer.log file. In
addition, the Bridge is disconnected warning is logged.
RNDCS00059717
SchAPI does not include a flag for AutoStartRecord
In the current release, Meeting Exchange does not include a flag to
indicate AutoStartRecord. This flag is available via other
components, such as chdbased/SpectelACS, callHandler, and from
the database.
RNDCS00059743
Callers being disconnected when using a Back-to-Back User
Agent
In this release, callers that use a B2BUA are disconnected when the
session timer from the primary server activates. At this point, the
primary server sends a RE-INVITE.
6 of 6
S700/S780
This section describes the known issues in the S700/S780.
Table 18: S700/S780 Issues
MR Number
Description
RNDCS00047171
Not all conferences start up under conditions of heavy load
In a heavy traffic scenario with large numbers of attended
conferences starting at the same or similar times, the
conferencing server may not successfully start up all
conferences. Core files are generated.
49 Meeting Exchange 5.1 Release Notes
Pyramid Configuration Issues
Pyramid Configuration Issues
Table 19: Pyramid Configuration Issues
MR Number
Description
RNDCS00039033
Hanging up lines outside of a conference
In a Pyramid configuration, Bridge Talk does not allow an
Operator to hang up a link line between 2 bridges unless the
lines are in an active conference. In this scenario, the Audio
Path dialog shows the Dial and Hang-up buttons as
inaccessible.
RNDCS00043317
Retrieve function not operating successfully
The Retrieve function in Bridge Talk should return to the last
line that was accessed by the Operator. In a Pyramid
configuration, the Retrieve function does not operate
successfully. This issue occurs if the Retrieve function is
accessed using the main menu or accessed using the Q&A
menu.
Issue 1 October 2008
50
Known Operational Issues
ACP API Issues
This section describes the issues in the Avaya Conferencing Provider Application Programming
Interface (ACP API).
Table 20: ACP API Operational Issues
MR Number
Description
RNDCS00059645
Operator Recall function
An incompatibilty issue exists between the functionality of
the ACP API and the functionality of the bridge. On the
bridge, a caller can request Operator assistance and for
the audio path between both parties, the caller remains in
a mute state. The ACP API expects the line to be
unmuted.
N/A
Off-bridge recording and analogrecording/playback is
currently untested.
Avaya Client Registration Server
This section describes the known issues in Avaya Client Registration Server 5.1.
51 Meeting Exchange 5.1 Release Notes
Avaya Bridge Talk
Table 21: Operational Issues for the CRS
MR Number
Description
RNDCS00051316
Repeat reservation details
If an Operator books a repeating reservation, the CRS may not show
all the details of the repeating conferences. This issue occurs if an
Operator chooses a specific number of conferences or a specific end
date as the conference limiting factor on the Book Reservation
dialog.
RNDCS00059519
Stored procedure issue related to user permissions
If an Engineer runs the cspi.sql script and attempts to log in as
cspi_user, the Engineer will not be able to access any stored
procedures.
Workaround: Manually add permissions to the stored procedure by
adding cspi_user to the public group or by granting permissions for
each procedure to the public group.
Avaya Bridge Talk
This section describes the known issues in Avaya Bridge Talk 5.1.
Table 22: Operational Issues
MR Number
Description
RNDCS00046791
No Operator Transaction Log is produced when conference
scan time is changed from Bridge Talk.
RNDCS00046871
Operator talk path appears to remain ON after returning
lines to the Enter queue.
RNDCS00048692
Opening a "putty ssh" session from BridgeTalk logs in
as craft
Subsequent attempts to open a PuTTY.ssh session fail after
first session is created
RNDCS00049694
In Audio Path window, dialed in music channel information
can be incorrectly displayed.
RNDCS00051021
Using Alt + Spacebar to toggle operator talk also selects
Menu Bar.
Issue 1 October 2008
52
Known Operational Issues
Table 22: Operational Issues
MR Number
Description
RNDCS00052272
Bridge Talk slows down and eventually locks after
prolonged activity
If Operators keep the Bridge Talk application open for a long
period, it eventually slows down severely.
Workaround: Operators should close down Bridge Talk at
the end of their working day. This tip is included in the
Meeting Exchange 5.1 Bridge Talk User Guide and Meeting
Exchange 5.1 Bridge Talk Online Help File.
RNDCS00052989
Shortcut keyboard keys not working
In some situations, particularly if an Operator opens an
audio path, certain keyboard shortcut keys do not operate
successfully. The CTRL + E and CTRL + H sequences are
examples.
RNDCS00054525
Q&A retrieve function not handled correctly for TOP priority
line. The line is retrieved, but it is not placed in the correct
position.
RNDCS00057834
Deleting recordings using Bridge Talk
If an Operator records and then plays back a conference
recording, Bridge Talk displays an error message if the
Operator attempts to delete the conference recording when
the playback is complete. The error message suggests that
the file is in use.
Workaround: If the Operator clicks Update to refresh their
session, they can successfully delete the conference
recording file.
RNDCS00058831
Restarting the conferencing server causes Bridge Talk
to stall
Under certain conditions, Bridge Talk may not operate if the
conferencing server is restarted. This issue occurs if there is
an open audio path dialog in the Bridge Talk application.
RNDCS00059593
Conference Viewer chat issue
If you attempt to use the Conference Viewer chat feature
directly from the Bridge Talk application, Bridge Talk displays
an error message.
Workaround: Users should open the Conference Viewer
application on the computer on which they are running the
Bridge Talk application. They should log into the conference
as a Moderator using Conference Viewer. Bridge Talk
should now connect successfully to the Conference Viewer
chat feature.
53 Meeting Exchange 5.1 Release Notes
Avaya Bridge Talk
Table 22: Operational Issues
MR Number
Description
RNDCS00059625
Stopping recordings in Bridge Talk
Operators cannot stop the recording feature unless they
refresh the Recording dialog.
Workaround: If the Operator closes then reopens the dialog
to refresh their session, they can successfully stop the
conference recording.
This issue is similar to RNDCS00057834.
RNDCS00059708
Operator help lines dropped from Polling dialog
In the current release, the Polling dialog does not display the
lines of Participants who are requesting Operator help. If a
Participant presses *0 to request Operator help, Bridge Talk
removes them from the Polling dialog. The conferencing
server plays the Participant the correct audio message and
places them in a queue for Operator assistance.
Workaround: If the Operator refreshes the Polling dialog,
Bridge Talk displays the lines of the Participants who are
requesting Operator help.
RNDCS00052510
Bridge Talk toolbar not displaying
In the current release, the Bridge Talk toolbar may not
display correctly after an Operator places a caller into a
conference using the Line Detail dialog. This is an
intermittent issue which occurs only occasionally.
RNDCS00059754
Pending, Enter, and Help Queue disappear when you
re-order the windows
In this release, when Bridge Talk Operators choose the
Docked on Top option to view the Bridge Talk display, the
user interface behaves erratically.
Workaround: Bridge Talk is more reliable when the
Conference Navigator is displayed on top. To enable this
configuration, Operators should navigate to View >
Conference Navigator > Docked on Top. Select Windows
> Tile Horizontal. Future Bridge Talk sessions will display
correctly.
Issue 1 October 2008
54
Known Operational Issues
Avaya Web Portal
Table 23: Avaya Web Portal Issues
MR Number
Description
RNDCS00058694
Error in display of Reservation Confirmation page
In a limited number of circumstances, the Web Portal
application does not display the Reservation Confirmation
page. The issue is due to a known issue in third party software,
such as Cocoon. The third party software does not compile the
.xsp page correctly. There are two workaround options.
Workaroun:
Delete the tomcat/work folder to force the third party software
to recompile the page. Also 'touch' the xsp page mentioned in
the error. Restart tomcat and httpd.
Avaya Audio Console
This section is divided as follows:
l
Avaya Audio Console Advanced Configuration
l
Avaya Audio Console Issues
Avaya Audio Console Advanced Configuration
This section is divided as follows:
l
Web Portal and Avaya Audio Console on a Single Server
l
CRS Connection Delays
l
Web Server Connections
Web Portal and Avaya Audio Console on a Single Server
In Meeting Exchange 5.1, Web Portal contains configuration for Apache and Tomcat which
throttles requests. This configuration aims to ensure that the Web Portal is never under too
much pressure. The Avaya Audio Console can process requests at a much faster rate than the
55 Meeting Exchange 5.1 Release Notes
Avaya Audio Console
Web Portal. As a result of this differing processing speed, you should configure the Avaya Audio
Console to allow more requests to it. If the Avaya Audio Console CPU usage is under load of up
to 50% and if the Web Portal is also under load, the server speed slows and performance is
impaired.
As a result of these observations, Avaya recommends that Avaya Audio Console is deployed on
a dedicated server or, at minimum, the Avaya Audio Console should have a dedicated Tomcat
and Apache. In the Avaya Audio Console Tomcat and Apache, use the following configuration
settings:
l
Update the Apache conf/httpd.conf as follows:
<IfModule mpm_winnt.c>
ThreadsPerChild 500
MaxRequestsPerChild 10000
</IfModule>
ListenBacklog 511
l
Update the Tomcat conf/server.xml as follows:
<Connector port="8009" protocol="AJP/1.3" maxThreads="550"/>
CRS Connection Delays
When each Avaya Audio Console client validates against the CRS, there is an impact on
performance. Each operation results in a WebValidate message to CRS. In addition, as each
Avaya Audio Console client starts up, it pulls a Participant List from the CRS. If a large number
of Moderators log in at the same time, they will experience a delay. This delay is also
experienced by Moderators who are already logged in at that time.
As a result of these observations, Avaya recommends deploying the Avaya Audio Console
without CRS connection details.
Web Server Connections
Each Avaya Audio Console client polls the Web server at regular intervals. You should fine tune
the response rate to compliment the typical system load.
Avaya recommends configuring two values in conferencemanager.properties to
determine the refresh rate:
Issue 1 October 2008
56
Known Operational Issues
LoadConfig - The possible values are as follows:
1 = The number connected to conference. Decide the refresh rate depending on the
number of Avaya Audio Console clients connected to a conference. This is the old existing
method for refresh calculations and Avaya do not recommend it now.
2 = The number connected to Web server. Decide the refresh rate depending on the
number of Avaya Audio Console clients connected to the Web server.
3 = Do not use any algorithm for calculating refresh rate
Avaya recommend LoadConfig=3. With this setting, the Avaya Audio Console is updated
periodically. For LoadConfig values of 1 or 2, the following settings apply:
ConsoleLoadSmall=100
ConsoleLoadMedium=200
ConsoleLoadHigh=400
When the load on Avaya Audio Console is small, a refresh rate of 1000ms is applied.
When the load on Avaya Audio Console is medium, a refresh rate of 2500ms is applied.
When the load on Avaya Audio Console is high, a refresh rate of 5000 is applied.
After the high load is exceeded, then a refresh rate of 10000ms is applied.
ServerDefaultResponse - This setting takes effect only when LoadConfig=3. It determines
how often the browser updates its clients view of the conference.
ServerDefaultResponse=2000 should work for the average deployment. It sets the
response time to the client to two seconds; Every two seconds the browser’s view of the
conference is updated if necessary. If there is no value given for
ServerDefaultResponse, 1000 milliseconds is the default.
There are deployment scenarios in which ServerDefaultResponse should be reduced
and equally, there are deployment scenarios in which ServerDefaultResponse should
be increased. ServerDefaultResponse depends on the usage patterns of the Avaya
Audio Console. ServerDefaultResponse relates to the traffic between Avaya Audio
Console client and Web server. Essentially, the less traffic, the quicker the response can be.
For example, if there is no talker data, you can reduce ServerDefaultResponse.
57 Meeting Exchange 5.1 Release Notes
Avaya Audio Console
Avaya Audio Console Issues
Table 24: Avaya Audio Console Issues
Reference Number
Description
RNDCS00044676
Avaya Audio Console and Mozilla Firefox issue
If customers deploy the Avaya Audio Console using Mozilla
Firefox as their client browser, an issue arises during log-in. When
Users log into Avaya Audio Console, the Mozilla Firefox browser
prompts them to change their saved password. This prompt is
due to an issue in the Mozilla Firefox browser. For more
information, see https://bugzilla.mozilla.org/
show_bug.cgi?id=370394. This issue only applies to Firefox 2.
The Mozilla Foundation have resolved this issue in Firefox 3.
RNDCS00057221
Performance issues with large numbers of Participants
When the number of Participants in Avaya Audio Console
exceeds 10, the performance of the application deteriorates. In
particular, the navigation from page to page is slow. This issue
occurs with Microsoft Internet Explorer 6 and 7.
Issue 1 October 2008
58
Known Operational Issues
Avaya Conference Scheduler Plug-in for Microsoft Outlook
This section describes the known issues relating to Avaya Conference Scheduler Plug-in for
Microsoft Outlook in Meeting Exchange 5.1.
59 Meeting Exchange 5.1 Release Notes
Avaya Conference Scheduler Plug-in for Microsoft Outlook
Table 25: Avaya Conference Scheduler Plug-in for Microsoft Outlook
Reference Number
Description
RNDCS00058424
Issue relating to the deletion of the first conference in a series
If a User attempts to delete the first individual conference within a
series of repeating conferences, the Avaya Conference Scheduler
Plug-in for Microsoft Outlook displays an error message.
Workaround:
Avaya recommends that you disable the Users’ ability to delete an
individual conference within a series of repeating conferences. To
disable this feature:
1. Open configuration.xml on the Meeting Exchange
bridge.
2. Set allowrecurringconferencedeletion=2.
Now, the Avaya Conference Scheduler Plug-in does not
permit Users to delete an individual conference within a
repeating conference series.
Note:
RNDCS00058426
Note:
The same workaround applies to RNDCS00058426.
Issue relating to the deletion of an individual conference in a
series
If a User attempts to delete an individual conference within a series
and then modifies the remaining conferences, the Avaya
Conference Scheduler Plug-in for Microsoft Outlook restores the
individual conference that the User attempted to delete.
Workaround:
Avaya recommends that you disable the Users’ ability to delete an
individual conference within a series of repeating conferences. To
disable this feature:
1. Open configuration.xml on the Meeting Exchange
bridge.
2. Set allowrecurringconferencedeletion=2.
Now, the Avaya Conference Scheduler Plug-in does not permit
Users to delete an individual conference within a repeating
conference series.
Note:
Note:
The same workaround applies to RNDCS00058424.
1 of 3
Issue 1 October 2008
60
Known Operational Issues
Table 25: Avaya Conference Scheduler Plug-in for Microsoft Outlook
Reference Number
Description
RNDCS00053809
Issue relating to deleting a single conference instance
In Microsoft Outlook 2003 and 2007, Users can delete a single
instance of a conference from their Microsoft Outlook calendar. If
Users perform this action, Meeting Exchange does not delete the
conference instance from the Meeting Exchange bridge.
To clarify; If Users highlight the conference in the calendar and click
Delete or right-click the conference and click Delete, Meeting
Exchange does not delete it from the bridge. However, if Users open
the conference and delete it, Meeting Exchange does delete it
successfully from the bridge.
RNDCS00059110
Release number incorrect in Add/Remove Programs
If you install the Avaya Conference Scheduler Plug-in for Microsoft
Outlook 2007, the Add/Remove Programs function of Microsoft
Windows displays an incorrect version number for the plug-in. It
correctly displays the vesion number 2.5.17.
RNDCS00044540
Increase in start up time for Microsoft Outlook
After Users install the Avaya Conference Scheduler Plug-in for
Microsoft Outlook, the start-up time for Microsoft Outlook can
increase by up to 11 seconds.
RNDCS00056663
Error if User creates a folder in the Calendar
Using Microsoft Outlook, if a User creates a folder within the
Calendar and then attempts to create a new appointment within that
folder, the Avaya Conference Scheduler Plug-in for Microsoft
Outlook displays an error message. The text in this error message is
Add-in exception. Error in open event. If the User clicks
OK on this message, Microsoft Outlook opens a New Appointment
dialog but this dialog has no Conference tab.
RNDCS00059526
Configuration is not user-friendly
Configuring the Avaya Conference Scheduler Plug-in for Microsoft
Outlook is difficult. The file permissions mean that customers with
craft access cannot configure the files. Therefore, Avaya Support
Engineer intervention is required. In addition, many values are
hard-coded which means that customization is awkward. Lastly, a
certain line of code should be commented out by default. In the
current release, this code must be manually commented out. The
code is:
<audionumbers>Internal:5473985,Local:1-201-547-398
5</audionumbers>
2 of 3
61 Meeting Exchange 5.1 Release Notes
Avaya Conference Scheduler Plug-in for Microsoft Outlook
Table 25: Avaya Conference Scheduler Plug-in for Microsoft Outlook
Reference Number
Description
RNDCS00059594
Support for default conference options
In this release of the Avaya Conference Scheduler Plug-in for
Microsoft Outlook , Avaya are only supporting the default conference
options. There are files that enable the customization of conference
options, such as mx.tables.xml. Avaya do not support any
changes made by customers to these files.
RNDCS00059109
Error if User creates a shared folder in the Calendar
Using Microsoft Outlook, if a User creates a shared folder within the
Calendar and then attempts to create a new appointment within that
folder, the Avaya Conference Scheduler Plug-in for Microsoft
Outlook displays an error message. This error prevents the use of
the Avaya plug-in functionality.
This issue is similar to RNDCS00056663.
RNDCS00058423
Deletion of meeting occurs too quickly
This issue only occurs in the case of a repeating conference. If a
User clicks on an occurence and clicks Delete, Microsoft Outlook
provides the following options: Send cancellation and delete
meeting or Delete without sending a cancellation. Beofre the
User makes a selection, the Client Registration Server deletes the
conference from the bridge. This is too soon because the User could
change their mind about deleting the conference and click Cancel
when provided with the two options.
RNDCS00059580
Display error when a User clears a selection
When a User selects the On-Demand checkbox and Web
Conference checkboxes, the Avaya Conference Scheduler Plug-in
for Microsoft Outlook displays the On-Demand and Web Conference
details for the User. If the User clears the On-Demand checkbox,
the plug-in should clear both the On-Demand and Web Conference
details. In the current release, the plug-in still shows the Web
Conference details in this situation.
3 of 3
Issue 1 October 2008
62
Known Operational Issues
Avaya Plug-in for IBM Lotus Sametime
Note:
Note:
During the installation of the Avaya Plug-in for IBM Lotus Sametime, the installer
saves the Meeting Exchange documentation in the installation directory. These
documents are now out of date. To ensure that you access the latest
documentation, you should replace these documents with the PDF files that are
located in the Avaya MX For IBM Lotus Sametime\5.1.0.0.6 directory.
Table 26: Avaya Plug-in for IBM Lotus Sametime
Reference Number
Description
RNDCS00046089
Issue when Users end, then immediately restart a Connect
Client session
If Users close then immediately re-open a Connect Client
session, they may experience some loss of functionality. This
issue only occurs in limited circumstances, when they restart
within a 3 minute period and follow this restart with a period of
idleness in the Connect Client session.
Workaround: Users should wait for approximately 4 minutes
before restarting a Connect Client session.
RNDCS00044688
Multiple conferencing servers operating with a single
Sametime server
During heavy load, there are performance issues in
configurations with more than one conferencing server and a
single instance of the Sametime server. This issue typically
results in the Sametime roster not displaying certain callers. The
line numbers linked to these callers are duplicated due to the fact
that there is more than one conferencing server in the
configuration. The Sametime roster only displays one of the
callers with a duplicated line number.
RNDCS00040631
Under conditions of heavy load, disconnected callers may
still display in a Sametime Web conference
Under conditions of heavy load over consecutive hours on the
server, disconnected callers may still appear as present in a
Sametime Web conference. These callers are no longer in the
conference but are listed as current Attendees. They are
disconnected from the conferencing bridge and no longer appear
in Bridge Talk.
1 of 3
63 Meeting Exchange 5.1 Release Notes
Avaya Plug-in for IBM Lotus Sametime
Table 26: Avaya Plug-in for IBM Lotus Sametime
Reference Number
Description
RNDCS00059678
A "Just this instance" modification may apply to all
instances of a recurring conference
If a User attempts to modify a single instance of a recurring
conference, their modification may be applied to all instances of
that recurring conference even if they select the Just this
instance option. For example, this issue may occur if they
attempt to modify the passcodes of a single instance of a
recurring conference. It is important to note that, in this situation,
the correct and updated passcodes are displayed in each
conference link.
RNDCS00059631
A "Just this instance" modification, followed by a "This
meeting and all subsequent instances" modification causes
a conflict
If a User edits an instance of a recurring conference and then
proceeds to make another edit but applies it to all conferences in
the series, the CRS and Sametime schedule may conflict. There
may be a difference between the details on the conferencing
bridge and the details on the Sametime schedule.
RNDCS00059607
Passcode and Service Location fields
In the Meeting Details, the field names for the following fields:
l Passcode
l Service Location
...may not be displayed.
RNDCS00059658
Sametime may switch Callers between mute and unmute
In a very limited number of circumstances, Sametime may switch
Users who join the conference, between a mute state and an
unmute state. This issue rarely occurs. When it does occur, it
applies to the state of the telephone line and the appearance of
the User on the roster.
RNDCS00059628
Conferee Code as mandatory field
The Conferee Code field is marked on the New Meeting page as
the only mandatory field. If Users attempt to book a conference by
entering a code in this field and leaving all the other fields as
blank, Sametime may encounter an error.
RNDCS00059667
bridgetest & bridgepassword utilities output exception errors
When a System Administrator uses cmd prompt to view the usage
of the bridgetest & bridgepassword utilities, the utilities also
print out an exception error.
2 of 3
Issue 1 October 2008
64
Known Operational Issues
Table 26: Avaya Plug-in for IBM Lotus Sametime
Reference Number
Description
RNDCS00059620
Sametime ignores the max-conferences parameter
The Sametime Adapter does not enforce the value of the
max-conferences parameter. It ignores the value of the
parameter. The max-conferences parameter controls the
number of conferences that a User can open simultaneously.
RNDCS00059644
Individual mute, followed by Mute All and Unmute All
If a Moderator User mutes a single Participant and then selects
Mute All, followed by Unmute All, the originally muted
Participant appears as muted in the roster. Furthermore, the
Moderator cannot select the Participant and click Unmute. The
only option available to the Moderator is to Mute.
RNDCS00059617
Audio prompts played during a dial out
If a User performs a dial out during the conference, the
conferencing server does not play the dial out announcement in
the localized language in accordance with the User’s locale
setting. Instead, the conferencing server plays the dial out
announcement using the dial out message contained in:
/usr2/Prompts/Set0/messages
3 of 3
Avaya Conference Viewer
This section describes the known issues relating to Avaya Conference Viewer 5.1.
Table 27: Avaya Conference Viewer Issues
Reference Number
Description
RNDCS00059426
Relative positions in Q&A queue
If a Moderator changes the positions of the Participants in the
Questioner’s Queue, the Conference Viewer application may not
accurately update the new positions.
65 Meeting Exchange 5.1 Release Notes
Adobe Connect
Adobe Connect
This section describes the known issues relating to the Adobe Connect integration with Meeting
Exchange 5.1.
Table 28: Adobe Connect Issues
Reference Number
Description
RNDCS00058836
Unclear audio with Adobe Connect
If Users record an audio conference while using the Adobe
Connect application and then play back the recording using the
Adobe Connect application, the audio may be unclear. This issue
is most likely caused by the conversion from .wav to .mp3.
Workaround: If you download the raw files from the audio
conferencing bridge, the audio is clear.
Issue 1 October 2008
66
Known Operational Issues
67 Meeting Exchange 5.1 Release Notes
Was this manual useful for you? yes no
Thank you for your participation!

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

Download PDF

advertising