Meeting Exchange 5.1. Release Notes for Customers Issue 1 October 2008 Compas ID

Transcription

1 Meeting Exchange 5.1 Reease Notes for Customers Issue 1 October 2008 Compas ID

2 2008 Avaya Inc. A Rights Reserved. Notice Whie reasonabe efforts were made to ensure that the information in this document was compete and accurate at the time of printing, Avaya Inc. can assume no iabiity for any errors. Changes and corrections to the information in this document may be incorporated in future reeases. Documentation discaimer Avaya Inc. is not responsibe for any modifications, additions, or deetions to the origina pubished version of this Documentation uness such modifications, additions, or deetions were performed by Avaya. Link discaimer Avaya Inc. is not responsibe for the contents or reiabiity of any inked third party Web sites referenced esewhere within this Documentation and Avaya does not necessariy endorse the products, services, or information described or offered within them. We cannot guarantee that these inks wi work a of the time and we have no contro over the avaiabiity of the inked 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 ("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 icense within the scope of the icense types described beow. The appicabe number of icenses and units of capacity for which the icense is granted wi be one (1), uness a different number of icenses or units of capacity is specified in the Documentation or other materias avaiabe to End User. "Designated Processor" means a singe stand-aone computing device. "Server" means a Designated Processor that hosts a software appication to be accessed by mutipe users. "Software" means the computer programs in object code, originay icensed by Avaya and utimatey utiized by End User, whether as stand-aone Products or pre-instaed on Hardware. "Hardware" means the standard hardware Products, originay sod by Avaya and utimatey utiized by End User. License Type(s): Concurrent User License (CU). End User may insta and use the Software on mutipe Designated Processors or one or more Servers, so ong as ony the icensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its soe discretion, bases the pricing of its icenses and can be, without imitation, an agent, port or user, an e-mai or voice mai account in the name of a person or corporate function (e.g., webmaster or hepdesk), or a directory entry in the administrative database utiized by the Product that permits one user to interface with the Software. Units may be inked to a specific, identified Server. Database License (DL). Customer may insta and use each copy of the Software on one Server or on mutipe Servers provided that each of the Servers on which the Software is instaed communicate with no more than a singe instance of the same database. Copyright Except where expressy stated otherwise, the Product is protected by copyright and other aws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a crimina, as we as a civi, offense under the appicabe aw. Third-party Components Certain software programs or portions thereof incuded in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or imit rights to use certain portions of the Product ("Third Party Terms"). Information identifying the copyright hoders of the Third Party Components and the Third Party Terms that appy is avaiabe on Avaya's web site at: For fu information, pease see the compete document, Avaya Third Party Terms, Document number To ocate this document on the website, simpy go to and search for the document number in the search box. Warranty Avaya Inc. provides a imited warranty on this product. Refer to your saes agreement to estabish the terms of the imited warranty. In addition, Avaya s standard warranty anguage, as we as information regarding support for this product, whie under warranty, is avaiabe through the foowing Web site: Avaya fraud intervention If you suspect that you are being victimized by to fraud and you need technica assistance or support, ca Technica Service Center To Fraud Intervention Hotine at for the United States and Canada. Suspected security vunerabiities with Avaya Products shoud be reported to Avaya by sending mai to: securityaerts@avaya.com. For additiona support teephone numbers, see the Avaya Web site: Trademarks Avaya and the Avaya ogo are registered trademarks of Avaya Inc. in the United States of America and other jurisdictions. Uness otherwise provided in this Documentation, marks identified by "," " " and "SM" are registered marks, trademarks and service marks, respectivey, of Avaya Inc. A other trademarks are the property of their respective owners. For the most current versions of documentation, go to the Avaya support Web site:

3 Contents Chapter 1: Introduction Supported Environment Common Server Specifications Hardware CS700/ S Recording S S Interoperabiity CS700/ S S Third Party Support CS700/ S6200/S Microsoft Server Microsoft Desktop Cient SQL Server Browsers Avaya Web Conferencing Software Appication Summary Chapter 2: Introducing Meeting Exchange 5.1 Reease New Features. 14 S700/S Supported upgrade paths PIN codes Mutipe biing code option Fexibe ANI S6200/S Supported upgrade paths Operating system New database caed PostgreSQL PIN codes Dia out to a SIP URI Mutipe queue actions based on DNIS/DDI Route caers to a range of conference rooms based on DNIS/DDI Mutipe biing code option Port expansion to Support for 140 Operators Issue 1 October

4 Contents Ca supervision Secure Bridge API SNMP changes SNMP version support CPU usage threshod Disk space usage threshod Reserved and unreserved port poo threshods Critica service down Critica service up New message for Operator assistance Avaya Conferencing Provider API MutiSite Appication Stored Procedures Bridge Tak Rea time taker updates VLL seection box reduced in size Increased DNIS fiter capacity Bridge status warning Administrator changes for Bridge Tak Cient Registration Server Conference Expiry User Password Expiry Account Expiry User-Administrators and User-Auditors User Change Log and User Status Reservation Groups Dayight Savings Time Adjustments Universa Coordinated Time Fied Goba Conference Support New Participant Fieds Web Porta Password Expiry Account Expiry Lega Discaimer Free Text Fied New Adapter Avaya Conference Scheduer Pug-in for Microsoft Outook Join a Conference SOAP Adapter Meeting Exchange 5.1 Reease Notes

5 Contents Chapter 3: Issues Resoved in this Reease S6200/S S700/S ACP API Avaya Bridge Tak MutiSite Avaya Cient Registration Server Avaya Web Porta Avaya Conference Viewer Avaya Pug-in for IBM Lotus Sametime Avaya Conference Scheduer Pug-in for Microsoft Outook Chapter 4: Known Operationa Issues S6200/S S700/S Pyramid Configuration Issues ACP API Issues Avaya Cient Registration Server Avaya Bridge Tak Avaya Web Porta Avaya Audio Consoe Avaya Audio Consoe Advanced Configuration Web Porta and Avaya Audio Consoe on a Singe Server CRS Connection Deays Web Server Connections Avaya Audio Consoe Issues Avaya Conference Scheduer Pug-in for Microsoft Outook Avaya Pug-in for IBM Lotus Sametime Avaya Conference Viewer Adobe Connect Issue 1 October

6 Contents 5 Meeting Exchange 5.1 Reease Notes

7 Chapter 1: Introduction This document ists the new functionaity and known operationa issues in Meeting Exchange 5.1. The versions of the appications shown in this document refect those fuy approved by Avaya. The nature of the Avaya architecture aows for ongoing updates of the different software appications on an independent basis. Pease consut with the Avaya Account Manager or Avaya support desk for ongoing updates. Supported Environment This section contains the foowing sections: Common Server Specifications Hardware Recording Interoperabiity Third Party Support Microsoft Server Microsoft Desktop Cient SQL Server Browsers Avaya Web Conferencing Software Appication Summary Common Server Specifications This section contains a number of tabes and describes the Avaya common server specifications: S6200, Pyramid, and S6800 Appication Server CRS, AWC Payback, Web Porta, OCS and CV Avaya Web Conferencing Issue 1 October

8 Introduction AWC Recordings Server and DRPS Meeting Exchange 5.0 Server Specifications Tabe 1: S6200, Pyramid, and S6800 Appication Server Appication Mode Processor Memory Beze HW Raid 1 Sot Disk Drive Add Nic Rmv Media Power Suppy Fans S6200, Pyramid and S6800 Appication Server De 1950 v3 Two Quad Core Inte Xeon E5440, 2x6MB Cache, 2.83GHz, 1333MHz FSB 4 GBytes 4 x 1 GB dua ranked FB DIMMs (667 Mhz). Avaya Beze PERC 6/i Integrated RAID controer. Supports SAS & SATA Two fu height haf ength PCI-E sots (2x8 ane). PCI-E Riser. Two 250GB SATA Enterprise Leve 3.5 Hot Pug Hard Drives Inte PRO 1000PT Dua Port Server Adapter, Gigabit NIC, Cu, PCIe x4 8x DVD-ROM Two Hot-pug Power Suppies for Redundancy Redundant Muti-Speed Fans Note: The Note: server specification in Tabe 1 supports capacities up to a maximum of 4000 ports (3200 ports on S6200) on G.711. Tabe 2: CRS, AWC Payback, Web Porta, OCS and CV Appication Mode Processor Memory Beze HW Raid 1 Sot CRS, AWC Payback, Web Porta, OCS and CV De 1950 v3 One Quad Core Inte Xeon E5440, 2x6MB Cache, 2.83GHz, 1333MHz FSB 2 GBytes 2 x 1 GB dua ranked FB DIMMs (667 Mhz). Avaya Beze PERC 6/i Integrated RAID controer. Supports SAS & SATA Two fu height haf ength PCI-E sots (2x8 ane). PCI-E Riser. 7 Meeting Exchange 5.1 Reease Notes

9 Supported Environment Tabe 2: CRS, AWC Payback, Web Porta, OCS and CV Appication Disk Drive Add Nic Rmv Media Power Suppy Fans CRS, AWC Payback, Web Porta, OCS and CV Two 250GB SATA Enterprise Leve 3.5 Hot Pug Hard Drives (none) 8x DVD-ROM Two Hot-pug Power Suppies for Redundancy Redundant Muti-Speed Fans Tabe 3: Avaya Web Conferencing Appication Mode Processor Memory Beze HW Raid 1 Sot Disk Drive Add Nic Rmv Media Power Suppy Fans Avaya Web Conferencing De 1950 v3 One Quad Core Inte Xeon E5440, 2x6MB Cache, 2.83GHz, 1333MHz FSB 4 GBytes 4 x 1 GB dua ranked FB DIMMs (667 Mhz). Avaya Beze PERC 6/i Integrated RAID controer. Supports SAS & SATA Two fu height haf ength PCI-E sots (2x8 ane). PCI-E Riser. Two 250GB SATA Enterprise Leve 3.5 Hot Pug Hard Drives (none) 8x DVD-ROM Two Hot-pug Power Suppies for Redundancy Redundant Muti-Speed Fans Tabe 4: AWC Recordings Server and DRPS Appication AWC Recordings Server and DRPS Mode HP DL385 G5, 2U Chassis. Dua socket capabe Processor One -AMD Opteron 2352 Quad Core / 2.1 GHZ socket F (1207) 4MB L2 + L3 Cache (Barceona code name) Issue 1 October

10 Introduction Tabe 4: AWC Recordings Server and DRPS Appication Memory Beze HW RAID 5 Hot Pug Backpane Sot Disk Drive Add Nic Rmv Media Video Power Suppy Fans AWC Recordings Server and DRPS 4 GB (2x2 GB of 2:1 intereaved PC DIMMs (DDR2-667) with Advanced ECC capabiities. Use 2GB DIMMS ony. Avaya Beze Smart Array P400 Raid controer with battery backup and 512Mb cache. Eight Sma Form Factor hot pug hard drives bays incuded in base unit. 2xPCI-x / 1xPCI-e fu-size Riser Cage option kit 3 x 146GB SAS 2.5" 10K RPM. Two embedded NC373i Mutifunction Gigabit Network Adapters (with TCP/IP Offoad Engine). DVD-ROM 8X 5.25 " interna Integrated ATI ES1000, 32MB video standard Redundant hot pug AC power suppy (1+1 redundancy). N+1 Hot Pug Fuy Redundant Fans Standard (incuded in base unit). Tabe 5: Meeting Exchange 5.0 Server Specifications Appication S6200, Pyramid, S6800, CRS, AWC Payback, Web Porta, OCS and CV Mode De 1950 Processor One Quad Core Inte Xeon X5355, 2x4MB Cache, 2.66GHz, 1333MHZ FSB Memory 2GB 667MHZ FBD 4X512MB -1R Beze HW Raid 1 Sot Disk Drive Add Nic Rmv Media De Beze PERC 5/i Integrated RAID Controer Card Riser with PCIe Support (2x PCI Express sots) Two 146GB, SAS, 3.5-inch, rpm Hard Drive(hot pug) Inte PRO 1000PT Dua Port Server Adapter, Gigabit NIC, Cu, PCIe x4 24X CDRW/DVD Combo Drive, IDE, Haf Heigh 9 Meeting Exchange 5.1 Reease Notes

11 Supported Environment Tabe 5: Meeting Exchange 5.0 Server Specifications Appication Power Suppy Fans S6200, Pyramid, S6800, CRS, AWC Payback, Web Porta, OCS and CV Two Hot-pug Power Suppies for Redundancy Redundant Muti-Speed Fans Note: The Note: server specifications in Tabe 5 support capacities up to a maximum of 2000 ports for S6200/S6800/Pyramid. A other appications are supported on Meeting Exchange 5.1 regardess of port capacity. Hardware CS700/780 S6800 CPU: 5550 (700Mhz) and 5551 DSP: NS300 and NS301 SCC-II 1 and SCC-III MPC-II 2 and MPC-IV Recording S6800 When recording competes, the 6800 server creates a ink fie, which is the same size as the recording fie. This ink fie is needed for payback purposes. This process of creating a ink fie means that storage capacity is haved to approximatey 2000 hours. Meeting Exchange 5.1 stores recordings as.wav encapsuated fies, which contain the audio in inear PCM format which is both narrow band or wide band and resuts in a size of 16 kiobytes per second for narrow band and 32 kiobytes per second for wide band. 1 The SCC-II wi not work in CMS The MPC-II wi not work in CMS Issue 1 October

12 Introduction S6200 In the Meeting Exchange 5.1 reease, the 6200 server supports approximatey 2100 hours of recordings. Interoperabiity CS700/780 S6200 S6800 Audiocodes Mediant 2000 Audiocodes Mediant 2000 Cantata IMG1010 G/W (Ver: ) Eement Management System Version: Avaya Communication Manager 5.1, 5.0 Avaya SIP Enabed Server 5.1, 5.0 Audiocodes Mediant 2000 Cantata IMG1010 G/W (Ver: ) Eement Management System Version: CMS-6000 and CMS-9000 Avaya Communication Manager 5.1, 5.0 Avaya SIP Enabed Server 5.1, 5.0 Radisys Firmware Version Third Party Support CS700/780 Microsoft Outook 2003 & Meeting Exchange 5.1 Reease Notes

13 Supported Environment S6200/S6800 Adobe Connect 6 IBM Lotus Notes IBM Lotus Sametime CF1 & 8 IBM Lotus Domino 7 & Microsoft Live Communications Server 2005 Microsoft Office Communications Server 2007 Microsoft Outook 2003 & 2007 Microsoft Live Meeting 7 & 8 Microsoft Office Communicator 1 & 2 Microsoft Server Windows Server 2003 Standard Edition R2 (SP2) Microsoft Desktop Cient Windows XP (SP2) Windows Vista Business SQL Server SQL 2005 (SP2) Browsers Microsoft Internet Exporer 6 & 7 Mozia Firefox 2.0 Issue 1 October

14 Introduction Avaya Web Conferencing Meeting Exchange 5.1 ships with Avaya Web Conferencing AWC supports a singe window for conferencing. AWC aso supports video conferencing. For more information, see the Avaya Web Conferencing Administration Guide, which is avaiabe on support.avaya.com. Software Appication Summary Tabe 6 contains a ist of Meeting Exchange 5.1 software incuded in this reease. Tabe 6: Software Appication Summary Product Area Version Number Avaya Web Conferencing BCAPI/ACPI Bridgetak Conference Viewer Cient Registration Server Avaya Pug-in for IBM Lotus Sametime Microsoft Adapter (MSAdapter) Microsoft Office Communications Server Adapter (OCSAdapter) Avaya Conference Scheduer Pug-in for Microsoft Outook S6200/S S SOAP Adapter Web Porta Meeting Exchange 5.1 Reease Notes

15 Chapter 2: Introducing Meeting Exchange 5.1 Reease New Features This chapter describes the new features in the Meeting Exchange 5.1 reease. It contains the foowing sections: S700/S780 S6200/S6800 Avaya Conferencing Provider API MutiSite Appication Stored Procedures Bridge Tak Cient Registration Server Web Porta Avaya Conference Scheduer Pug-in for Microsoft Outook S700/S780 This section describes the S700/S780 enhancements in Meeting Exchange 5.1. It contains the foowing sections: Supported upgrade paths PIN codes Mutipe biing code option Fexibe ANI Supported upgrade paths The foowing upgrade paths are supported: 5.0 GA > 5.1 Latest 5.0 Service Pack > 5.1 Issue 1 October

16 Introducing Meeting Exchange 5.1 Reease New Features PIN codes PIN Codes contain three new optiona fieds, Line Aux 1, Line Aux 2, and Line Aux 3 to aow additiona participant information to be captured for biing records. This information is added as part of the Ca Detai Record. The PIN Code Admin utiity is no onger supported on the Meeting Exchange patform. The CRS is used to administer the PIN codes database on the bridge. Refer to the Meeting Exchange 5.1 Reationa Database Guide for S700/S780 Conferencing Servers, which is avaiabe on support.avaya.com. Mutipe biing code option It is now possibe for a moderator to be prompted for both a Biing Code and a Cient Matter code when they start a conference. This wi aow biing to be generated for each end user within a singe conference. An exampe of this woud be found in a court setting where the biing code woud reference an overa case whie the separate cient matter codes woud define each of the attorneys invoved. Fexibe ANI It is now possibe for the bridge to count both the deimiters and the digits to determine when digit coection is compete. This wi speed the processing time for an incoming ca. S6200/S6800 This section describes the S6200/S6800 enhancements in Meeting Exchange 5.1. It contains the foowing sections: Supported upgrade paths Operating system New database caed PostgreSQL PIN codes Dia out to a SIP URI Mutipe queue actions based on DNIS/DDI Route caers to a range of conference rooms based on DNIS/DDI 15 Meeting Exchange 5.1 Reease Notes

17 S6200/S6800 Mutipe biing code option Port expansion to 4000 Support for 140 Operators Ca supervision Secure Bridge API SNMP changes New message for Operator assistance Supported upgrade paths The foowing upgrade paths are supported for any system components: 5.0 GA > 5.1 Latest 5.0 Service Pack > 5.1 Operating system The instaation program instas the foowing operating system: Red Hat Enterprise Linux 4 Update 6 New database caed PostgreSQL The reationa Database for the Linux-based S6200/6800 patform wi be PostgreSQL version When upgrading from reease 5.0 to reease 5.1, the upgrade sha preserve the data contained in the Informix database. PIN codes PIN Codes contain three new optiona fieds, Line Aux 1, Line Aux 2, and Line Aux 3 to aow additiona participant information to be captured for biing records. This information sha be added as part of the Ca Detai Record. The PIN Code Admin utiity is no onger supported on the Meeting Exchange patform. The CRS is used to administer the PIN codes database on the bridge. Refer to the Meeting Exchange 5.1 Reationa Database Guide for S6200/6800 Conferencing Servers, which is avaiabe on support.avaya.com. Issue 1 October

18 Introducing Meeting Exchange 5.1 Reease New Features Dia out to a SIP URI It is now possibe to dia out to a SIP URI in addition to a teephone number. This aows an endpoint to be diaed without having to use the TeNumtoURI fied. This feature is ony supported via an API. Mutipe queue actions based on DNIS/DDI It is now possibe to differentiate incoming cas, based on their DNIS/DDI, and provide different queue actions when the caer enters an invaid code or the caer fais to enter any code. This new On Faiure setting in the ca branding tabe wi supersede the Timeout and Invaid Code settings found in the Administration Menu under Configure Scheduer. Route caers to a range of conference rooms based on DNIS/DDI It is now possibe to route caers to a range of conference rooms based on the DNIS/DDI they use. The new Room Start and Room End fieds wi determine the room range to which a caer can be sent based on their DNIS/DDI digits. It does not affect Operator function. The defaut setting of 0 wi aow cas to start a conference in any avaiabe room. Mutipe biing code option It is now possibe for a moderator to be prompted for both a Biing Code and a Cient Matter code when they start a conference. This wi aow biing to be generated for each end user within a singe conference. An exampe of this woud be found in a court setting where the biing code woud reference an overa case whie the separate cient matter codes woud define each of the attorneys invoved. Port expansion to 4000 A pyramid configuration of Meeting Exchange now supports up to 4000 ports. The S6800 aso supports 4000 ports. The S6200 supports 3200 ports. Note: Note: Port capacities are G.711 ony. 17 Meeting Exchange 5.1 Reease Notes

19 S6200/S6800 Support for 140 Operators Meeting Exchange 5.1 now supports up to 140 simutaneous Operators without Secure Socket Layer (SSL). Meeting Exchange supports up to 70 Operators with an SSL impementation. Ca supervision Meeting Exchange 5.1 aows for ca supervision through the addition of a progress tone simuation system for SIP cas. SIP equipment does not normay produce the traditiona audibe indications of a ca s progress so Meeting Exchange produces appicabe tones based on SIP vaues. Secure Bridge API In Meeting Exchange 5.1, System Administrators can configure the BridgeTak and the bridge APIs to communicate with the conferencing server over the encrypted transport protoco, SSL. The bridge APIs are ACPI and BCAPI. SNMP changes This section describes the SNMP enhancements in Meeting Exchange 5.1. It contains the foowing sections: SNMP version support CPU usage threshod Disk space usage threshod Reserved and unreserved port poo threshods Critica service down Critica service up SNMP version support The system now supports SNMP v3 in addition to SNMP v2. Issue 1 October

20 Introducing Meeting Exchange 5.1 Reease New Features CPU usage threshod When CPU usage reaches or exceeds a certain threshod on systems using SNMP, an SNMP aarm sha be sent identifying the affected system. Disk space usage threshod When disk usage reaches or exceeds a certain threshod on systems using SNMP, an SNMP aarm sha be sent identifying the affected system. Reserved and unreserved port poo threshods The system wi aow the configuration of a system-wide setting for both reserved and unreserved ports. When a specified percentage of either of these poos of ports is exceeded on systems using SNMP, the system wi send an SNMP trap. Note: For Note: more information on each of these features, see the Meeting Exchange 5.1 S6200/S6800 Configuration Guide which is avaiabe on support.avaya.com. Critica service down Meeting Exchange issues a trap When one of the foowing system processes stops: servercoms softms initipcb msdispatcher cahand schapid modapid sipagent cdr startd chdbased traffic timer netservices bridgetransator 19 Meeting Exchange 5.1 Reease Notes

21 S6200/S6800 convms Note: Note: Avaya added these new traps in response to customer enhancement requests. Critica service up Meeting Exchange issues a trap When one of the foowing system processes starts: servercoms softms initipcb msdispatcher cahand schapid modapid sipagent cdr startd chdbased traffic timer netservices bridgetransator convms New message for Operator assistance In Meeting Exchange 5.1, Avaya has added a new message which is payed when Participants request assistance from an Operator. In previous reeases, Meeting Exchange paced Participants in an Operator queue when they pressed *0 on their teephone keypad. In the new reease, Meeting Exchange pays a message, such as "Pease wait for Operator Assistance" and then paces the Participant in an Operator queue. Issue 1 October

22 Introducing Meeting Exchange 5.1 Reease New Features Avaya Conferencing Provider API Avaya are reeasing a new Appication Programming Interface (API) with the Meeting Exchange 5.1 reease. The new API is caed the Avaya Conferencing Provider (ACP) API. It exposes the rea time conference contro functionaity of BCAPI as we as Operator eve conference contro functionaity previousy ony avaiabe with Bridge Tak. MutiSite Appication For Meeting Exchange 5.1, Avaya has made a number of enhancements to the MutiSite functionaity. The 5.1 version now contains the foowing new features: A new Windows interface to aid Support Engineers New og fie maintenance to remove od og fies. This feature is configurabe. Now supports SSL-based communication with the conferencing bridge Enhanced ogging detais 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 exampe, in the new reease, the p_cspi_changeconferencepin returns a negative vaue when it is run but then subsequenty fais. This ensures consistent ogic with other faiure codes. Bridge Tak This section describes the Bridge Tak enhancements in Meeting Exchange 5.1. It contains the foowing sections: Rea time taker updates VLL seection box reduced in size Bridge status warning Administrator changes for Bridge Tak 21 Meeting Exchange 5.1 Reease Notes

23 Bridge Tak Rea time taker updates The tak indications on Bridge Tak sha appear in rea time, and the user sha not be abe to discern a deay. In past reeases, the ine tak indications woud appear sighty after the person had actuay begun to speak. This feature is configurabe on the bridge. Aso, in this reease, there are an increased number of customizabe options avaiabe to Bridge Tak System Administrators who wish to configure how Bridge Tak Operators monitor active takers. VLL seection box reduced in size The VLL seection box in the Line Detai window has been reduced in size to prevent operators from accidentay setting ines as VLL. Increased DNIS fiter capacity It is now possibe for an operator to fiter up to 50 DNIS/DDI numbers when using the DNIS Fiter feature. Bridge status warning A warning message wi appear when a user ogs into a Bridge Tak station that is connected to a system in standby mode. This wi aert an operator that the system is not currenty active. The operator can cick OK to continue or Cance to return to the ogin box. Administrator changes for Bridge Tak The foowing settings can ony be changed by a Bridge Tak administrator: Nighttime Mode The Nighttime mode fied sha be hidden by defaut in the Bridge Tak dispay. This is to prevent operators from accidentay setting the bridge in NightTime mode which prevents new caers from accessing the system. An administrator can set Nighttime mode to be visibe in Bridge Tak. Set Answer The Set Answer setting sha be hidden by defaut in the Bridge Tak dispay. By defaut a ines are set to Answer. An administrator can set Answer to be visibe in Bridge Tak. Issue 1 October

24 Introducing Meeting Exchange 5.1 Reease New Features Note: For Note: more information on each of these features, see the Meeting Exchange 5.1 Bridge Tak User Guide which is avaiabe on support.avaya.com. Cient Registration Server This section describes the Cient Registration Server enhancements in Meeting Exchange 5.1. It contains the foowing sections: Conference Expiry User Password Expiry Account Expiry User-Administrators and User-Auditors User Change Log and User Status Reservation Groups Dayight Savings Time Adjustments Universa Coordinated Time Fied Goba Conference Support New Participant Fieds Note: For Note: more information on each of these features, see the Meeting Exchange 5.1 Cient Registration Server System Administration Guide which is avaiabe on support.avaya.com. Conference Expiry Meeting Exchange 5.1 contains new functionaity to enabe CRS System Administrators to configure the suspension of any unused on-demand conferences. So, if an on-demand conference remains unused for a configurabe 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 reeases the port aocation. It is an effective resource management too. 23 Meeting Exchange 5.1 Reease Notes

25 Cient Registration Server User Password Expiry Meeting Exchange 5.1 contains new functionaity to force a eves of Users to update their CRS Front End passwords at reguar intervas. CRS System Administrators can configure the ifespan of passwords using a new system parameter from the BSRes2 database, caed PasswordExpiryThreshod. This system parameter aso impacts Cient password expiry. Account Expiry Meeting Exchange 5.1 contains new functionaity to ensure that if CRS Users or Web Porta Moderators do not og in to the conferencing system for a configurabe period of time, the CRS disabes their account. This functionaity impacts a CRS User eves, such as CRS Administrators, CRS Supervisors, and CRS Operators. Simiary, it impacts CRS cients. CRS cients equate to Web Porta Moderators. Each Web Porta Moderator has a CRS cient account. User-Administrators and User-Auditors Meeting Exchange 5.1 contains a two new User roes. These User roes are caed User-Administrators and User-Auditors. User-Administrators can create, edit, and deete Operators and Supervisors. They can aso view a report that show significant changes to User accounts, such as User creation, User deetion, password changes, and so on. Avaya created the User-Administrator roe for peope who are responsibe for staff management. User-Auditors can view the ist of Users. They can aso view a report that show significant changes to User accounts. Their roe is simiar to the User-Administrator roe. The main difference between User-Administrators and User-Auditors is that User-Auditors cannot create, edit, and deete any other Users. Avaya created the User-Auditor roe for peope who are responsibe for overseeing and anayzing 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 deetion, password changes, and so on. Issue 1 October

26 Introducing Meeting Exchange 5.1 Reease New Features Reservation Groups The Reservation Groups feature aows Operators to schedue mutipe conferences with the same conference code at the same time. Each DDI is associated with a specific Reservation Group. Avaya incuded the Reservation Groups feature in the Meeting Exchange 5.0, Service Pack 1 reease. It is now part of Meeting Exchange 5.1. Dayight Savings Time Adjustments This new feature reates 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 and enabe Meeting Exchange 5.1 to identify a Dayight 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 individua conferences and makes adjustments accordingy. For more information, see the Meeting Exchange 5.1 Stored Procedures Interface Guide. Note: Note: A conference bookings made using the SOAP Adaptor are converted to UTC. Universa Coordinated Time Fied In the BSRes2 database, the timezone tabe has a new Coordinated Universa Time (UTC) fied. This fied is dispayed in the Timezone tab on the CRS Front End but cannot be edited or deeted. It is a read-ony fied and you cannot edit it. The UTC fied ensures that the SOAP Adaptor treats conference times correcty, even if you deete or move the GMT timezone. Goba Conference Support For Meeting Exchange 5.1, Avaya Engineers have deveoped a configuration soution for ensuring the dispay of site-specific teephone numbers in notification e-mais. Contact Avaya Support Engineers for more information on this configuration soution. New Participant Fieds On the CRS Front End, Users can now add additiona information about conference Particiapnts in a number of free text fieds, caed Line Aux 1, 2, and 3. If the conference is an 25 Meeting Exchange 5.1 Reease Notes

27 Web Porta Attended Conference, this information is visibe to the Operator on the BridgeTak appication. The information aso appears in biing and reporting records. Each of the three new fieds accepts up to 80 characters. Web Porta This section describes the Web Porta enhancements in Meeting Exchange 5.1. It contains the foowing sections: Password Expiry Account Expiry Lega Discaimer Free Text Fied New Adapter Note: For Note: more information on each of these features, see the Meeting Exchange 5.1 Web Porta Administrator Guide, which are avaiabe on support.avaya.com. Password Expiry In Meeting Exchange 5.1, Avaya has updated the Web Porta authentication mechanisms. Password vaidation is now case-sensitive. In addition, passwords now have a imited ifespan. System Administrators can configure the password expiry threshod in the System Parameters tabe in the Cient Registration Server (CRS) database; BSRes2. Account Expiry In Meeting Exchange 5.1, Avaya has added configuration parameters to create an account inactivity threshod. With this functionaity, the CRS disabes the accounts of Web Porta Moderators, Administrators, and Whoesaers who do not og in to the Web Porta for a configurabe period of time. Issue 1 October

28 Introducing Meeting Exchange 5.1 Reease New Features Lega Discaimer Free Text Fied In Meeting Exchange 5.1, you can now configure the dispay of a ega discaimer. Users wi view this ega discaimer after they og in to the Web Porta. They can cick OK to progress to the My Schedue screen. The content is free text and is imited to 800 characters. Whie many customer may use this feature to add a ega discaimer, it can aso be used to add a wecome message or any other message of ess than 800 characters. New Adapter In Meeting Exchange 5.1, the Avaya Audio Consoe is bunded with a new Bridge Contro Appication Programming Interface (BCAPI) Adapter which uses the Avaya Conferencing Provider s Interface (ACPI). This new adaptor gives an improvement in performance for Avaya Audio Consoe and aso, because Avaya wrote it specificay with thread safety and concurrency in mind, it enhances reiabiity. Avaya Conference Scheduer Pug-in for Microsoft Outook This section describes the Avaya Conference Scheduer Pug-in for Microsoft Outook enhancements in Meeting Exchange 5.1. It contains the foowing sections: Join a Conference SOAP Adapter Join a Conference In this reease, Users can now access a Join Conference button on the toobar at the top of the Appointment screen in Microsoft Outook 2003 and in the Add-Ins menu of the appointment in Microsoft Outook Using this feature, they can seect the bridge teephone number to join the conference. System Administrators configure this feature in outook/fies/ configuration.xm, which is ocated on the conferencing server. It is important to note that the Join a Conference feature is ony supported for a group of users within an enterprise using a singe conferencing server. Each user must have the Avaya Conference Scheduer Pug-in for Microsoft Outook on their computers in order to use the feature. 27 Meeting Exchange 5.1 Reease Notes

29 Avaya Conference Scheduer Pug-in for Microsoft Outook SOAP Adapter For this reease, Avaya has made a number of improvements to the SOAP Adapter. The tempate for configuring schedued 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 aso improved timezone management and added a new RPM to the instaation of the conferencing server caed soap-on-mx-5-x.x.x.i386.rpm. Issue 1 October

30 Introducing Meeting Exchange 5.1 Reease New Features 29 Meeting Exchange 5.1 Reease Notes

31 Chapter 3: Issues Resoved in this Reease This chapter describes the issues that are resoved in Meeting Exchange 5.1. It contains the foowing sections: S6200/S6800 S700/S780 ACP API Avaya Bridge Tak MutiSite Avaya Cient Registration Server Avaya Web Porta Avaya Conference Viewer Avaya Pug-in for IBM Lotus Sametime Avaya Conference Scheduer Pug-in for Microsoft Outook S6200/S6800 Tabe 7: S6200/S6800 Resoved Issues MR Number RNDCS RNDCS RNDCS After an upgrade, processing of new cas can be sow when the server is busy. Workaround: Reboot the server after the upgrade. After an MPC is reset, the SJ Phone audio is distorted on systems with more than 1000 active cas. If a user disconnects from a ca during the NRP request, some CDR fieds may be bank or contain incorrect information. If the first person to join the conference drops the ine, these fieds are bank: CrossRef, ConfirmNum, ConferenceName. If the second or ater person to join the conference drops the ine, the conferenceentrytime fied dispays 00:00 GMT. 1 of 3 Issue 1 October

32 Issues Resoved in this Reease Tabe 7: S6200/S6800 Resoved Issues MR Number RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Mxmonitor did not produce a core fie when the process was kied with signa 11. A moderator connected via Adobe Acrobat Connect Professiona can dia out from conference that has Bock Dia Out enabed in the reservation. Note: Note: This has been determined to be an Adobe Connect issue. After an upgrade, processing of new cas can be sow when the server is busy. Workaround: Reboot the server after the upgrade. Loss of audio due to sipagent issue In previous reeases, if the conferencing server received a 491 request when it tried to compete a re-invite to move a ca from MPC 1 to MPC 2, it did not compete its transaction. This behavior caused Msdispatcher to oose track of the channe. As a resut, the ca ost audio. For Meeting Exchange 5.1, Avaya enhanced the sipagent to hande this instance. Issue regarding oss of SNMP foowing an IP change In previous reeases, the server ost SNMP functionaity after an IP address update. For Meeting Exchange 5.1, Avaya produced a new script to resove this issue. System Administrators shoud run ip_change_mx_cs.sh instead of the od script: ipchange.sh. Type of Service (TOS) vaue ineffective for signaing In previous reeases, the vaue of TOS ony appied to media messages and not signaing messages. For Meeting Exchange 5.1, Avaya updated the system.cfg fie to ensure that the TOS vaue appies to both media and signaing for inbound and outbound cas. Cas dropped when LAN is disconnected In previous reeases with an active/standby server configuration, cas were dropped in a LAN faiover situation. This was due to the fact that the faied master server attempted to connect the cas. In Meeting Exchange 5.1, Avaya updated mxmonitor to resove the issue. The reevant parameters in mxmonitor are configurabe. 2 of 3 31 Meeting Exchange 5.1 Reease Notes

33 S6200/S6800 Tabe 7: S6200/S6800 Resoved Issues MR Number RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Music on audiopath between Operator and Participant In previous reeases, the conferencing server payed music when a Participant requested Operator assistance during conferences that had music enabed. In Meeting Exchange 5.1, music is disabed in the ca fow engine instead of being inherited from the main conference. The issue no onger occurs. Bridge Tak takers In previous reeases, the dispay of the takers on the Bridge Tak interface did not update in rea time. For Meeting Exchange 5.1, Avaya updated the refresh interva to ensure a more immediate response. Progress tones on diaout In previous reeases, when Operators or Moderators diaed out from a conference, they did not hear any progress tones and so did not know if the ca was successfu. In Meeting Exchange 5.1, they can now hear the tones and so can detect if the ine is busy. Missing domain information In previous reeases, the domain information was removed from the /etc/hosts fie when customers ran the mx-ipchange script foowing a change of IP address. When domain information is missing, coreservies cannot be upgraded. In the current reease, this script has been repaced and the issue no onger occurs. Active/Standby server In previous reeases with an active/standby server configuration, the S6200/S6800 bridge servers coud not communicate their status to the CRS server. In this reease, Avaya has improved communications between the bridge and the CRS. Now, the CRS Front End updates to accuratey show the active bridge. Modapi core dumps In previous reeases, the Modapi core-dumped when it received an invaid channe. It shoud dispay an error message instead. In Meeting Exchange, Avaya addressed this issue and it no onger occurs. Informix ODBC error In order for the Sef Registration component to operate successfuy, your Web Porta configuration requires an Informix ODBC driver. In previous reeases of Meeting Exchange, the Informix ODBC driver faied if you enabed the Meeting Exchange Bridge Firewa. In this reease, Avaya addressed this issue by opening port 1525 on the audio conferencing server. 3 of 3 Issue 1 October

34 Issues Resoved in this Reease S700/S780 Tabe 8: S700/S780 Resoved Issues MR Number RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Running isdnmgr -stop command may resut in the wrong T1 board stopping when initiating a hot swap. Verify the correct board has stopped prior to removing board from the chassis. T1 cock gitch causes PRI boards to drop their cock resuting in oss of audio. Hot swapping a T1 board can resut in static being heard on trunks on other T1 boards in the system. EPV memory too sma In previous reeases, EPV did not correcty respond after a certain point. The EPV memory was arge enough to incude the increasingy expanding features of Meeting Exchange. In Meeting Exchange 5.1, Avaya addressed this issue and made the memory buffer an unimited size. This issue was aso fixed for the S6200/ S6800 servers. Incorrect time on conference recordings In previous reeases, the system dispayed the incorrect times next to conference recordings on the bridge. For Meeting Exchange 5.1 reease, Avaya changed the impementation of the time dispay feature to resove this issue. Incorrect message payed during a dia out In previous reeases, in certain circumstances, the server payed an incorrect message to Participants that were diaed by the Moderator during a dia out from a conference. This issue was specificay reated to message 243 when the Direct to Conf setting was seected. In Meeting Exchange, Avaya improved bast dia functionaity to eimate this probem. Virtua ink ine appears to be in use In previous reeases, when a caer disconnected from a virtua ink ine (VLL) during a fex fow conference, the server kept the VLL setting as Y. On the Bridge Tak interface, the VLL appeared to be in use. Avaya addressed this issue in Meeting Exchange 5.1 and it no onger occurs. 33 Meeting Exchange 5.1 Reease Notes

35 ACP API ACP API Tabe 9: BCAPI Resoved Issue MR Number RNDCS Pausing and resuming conference payback In previous reeases of Meeting Exchange, when BCAPI issued a command to pause and then resume the payback of a conferencing recording, the command did not execute successfuy. Avaya addressed this issue in Meeting Exchange 5.1 and corrected the BCAPI behavior. Avaya Bridge Tak Tabe 10: Avaya Bridge Tak Issue MR Number RNDCS Ro ca feature deactivated In previous reeases of Meeting Exchange, the Bridge Tak appication occasionay switched off the ro ca conference property. This issue occurred when an Operator viewed the conference detais in Bridge Tak and cicked OK on the conference detais diaog. Avaya fixed this issue in Meeting Exchange 5.1. Issue 1 October

36 Issues Resoved in this Reease MutiSite This section describes the MutiSite issues that are resoved in Meeting Exchange 5.1. Tabe 11: MutiSite Resoved Issues MR Number RNDCS RNDCS RNDCS RNDCS Issue Mutisite conferences dropped if MutiSite Engine Restarts In previous reeases of Meeting Exchange, if the Mutisite Engine (MSE) was restarted, the active Muti 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 onger occurs. Mutisite og purge In previous reeases, the Mutisite ogs did not purge when they reached a certain size. In Meeting Exchange 5.1, MutiSite.exe has been repaced by MSE.exe. MSE.exe has the desired functionaity. and can specify: how many ogs to keep the size of the og fies MSE.exe wi automaticay deete ogs based on these settings. Virtua ink ine (VLL) issue In previous reeases of Meeting Exchange, if a VLL between two Muti Site ocations faied, the MSE did not attempt to reconnect the dropped VLL. In Meeting Exchange 5.1, Avaya addressed this issue and it no onger occurs. Inactive hubs are activated In previous reeases, the MSE occasionay created VLLs to Muti Site hub ocations even if there were no caers in that particuar ocation. 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 onger occurs. 35 Meeting Exchange 5.1 Reease Notes

37 Avaya Cient Registration Server Avaya Cient Registration Server Tabe 12: CRS Resoved Issues MR Number RNDCS RNDCS RNDCS RNDCS RNDCS Error in MSI Instaer In previous reeases, System Administrators had to ensure that they ran the Service Pack MSI Instaer ony once. If System Administrators ran the Service Pack MSI Instaer and then ran it again, the MSI Instaer did not insta the service pack components successfuy. This issue occurred if System Administrators atered an instaation configuration setting whie running the MSI Instaer for the second time. In this reease, Avaya addressed the issue and it no onger occurs. Inconsistent use of the terms Pincode and Passcode In previous reeases, 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 terminoogy across a appications. Error in Participant PIN dispay In previous reeases of the CRS Front End, if Operators created a Participant and aocated a User PIN to the new Participant, the PIN fied appeared as bank. In Meeting Exchange 5.1, this fied is now popuated by the User PIN information. PCReports error In previous reeases of Meeting Exchange, the PCReports appication had a time and date error. The Next Process Time fied was set to 1999 and System Administrators had to manuay edit it. Avaya partiay addressed this issue in Meeting Exchange 5.1 by adding some ogic. Now, the Next Process Time fied is set to <current year>-1. In-progress dispay error In previous reeases, if Users opened an on-demand conference, the CRS Front End dispayed 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 cose on the audio conferencing bridge. Issue 1 October