Basic Call Management Reporting Desktop R2.4.2 Release Notes
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 might 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. Customer and/or End User agree to indemnify and hold
harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in
connection with, subsequent modifications, additions or deletions to
this documentation to the extent made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any
linked 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 the time and we have no control over the
availability of the linked pages.
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 Avaya Support Web site:
http://www.avaya.com/support
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 WEB SITE
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.
CPU License (CP). End User may install and use each copy of the
Software on a number of Servers up to the number indicated by
Avaya provided that the performance capacity of the Server(s) does
not exceed the performance capacity specified for the Software. End
User may not re-install or operate the Software on Server(s) with a
larger performance capacity without Avaya's prior consent and
payment of an upgrade fee.
Copyright
Except where expressly stated otherwise, the Produ ct is prote cte d 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 Third Party Components and the Third Party
Terms that apply to them is available on the Avaya Support Web site:
http://support.avaya.com/ThirdPartyLicense/
Preventing toll fraud
"Toll fraud" is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of toll fraud
associated with your system and that, if toll fraud occurs, it can result
in substantial additional charges for your telecommunications
services.
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. For additional support telephone numbers, see
the Avaya Support Web site:
http://www.avaya.com/support
Trademarks
Avaya and the Avaya logo are either registered trademarks or
trademarks of Avaya Inc. in the United States of America and/or other
jurisdictions. All other trademarks are the property of their respective
owners.
Downloading documents
For the most curre nt versions of documentation, see the Avaya
Support Web site:
Avaya support
Avaya provides a telephone number for you to use to report problems
or to ask questions about your product. The support telephone
number is 1-800-242-2121 in the United States. For additional
support telephone numbers, see the Avaya Support Web site:
http://www.avaya.com/support
http://www.avaya.com/support
Contents
Release notes overview........................................................................................3
What's New...........................................................................................................3
Problems fixed......................................................................................................6
Database Merge Utility..........................................................................................8
When can you use the Database Merge Utility?................................................8
How to use the Database Merge Utility.............................................................9
How to perform a Database merge? .................................................................9
BCMRD R2.4.2 (Build 317) Installation Instructions............................................11
*Assumptions .................................................................................................. 12
Reference Images...............................................................................................13
Hints and tips......................................................................................................14
To upgrade to BCMRD R2.4.2 ........................................................................14
Technical Support...............................................................................................15
Basic Call Management Reporting Desktop R2.4.2 Release Notes
Release notes overview
BCMRD R2.4.2 aims to provide an essential upgrade to the current release of BCMRD R2.4.1.
The upgrade will enable BCMRD to operate with Communication Manager 5.2.
The document provides important information about the Avaya Basic Call Management Reporting
Desktop (BCMRD) including issue description, enhancements and suggested solutions for
R2.4.2. It provides a description of Database Merge Utility for upgrading the database to the
latest format. It also includes scenarios with the corresponding installation instructions and
assumptions that you must consider while installing BCMRD. This document also includes the
supported Communication Manager (CM) versions.
BCMRD R2.4.2 release includes fixes (like dual/multi-core processor support etc) made in
previous service pack i.e. R2.4.1.
For more information about R2.4.1 features and fixes please refer to the R2.4.1 release notes on
the Avaya support Web site.
Note:
BCMRD R2.4 and later releases are not certified to work on a 64-bit operating system.
Please refer to the Installation guide and User guide on the Avaya support Web site,
http://www.avaya.com/support for more information on previously supported platforms,
functionality and installation instructions.
What's New
1. BCMRD R2.4.2 compatibility with Communication Manager 5.2
The BCMRD R2.4.2 release supports Communication Manager 5.2 and also supports backward
compatibility with Communication Manager releases 5.1, 5.0, and 4.0.
2. Enhanced database support
If Agent Login ID and VDN ID fields exceed 7 characters or if alphanumeric values or any special
characters
error dialog box is displayed while downloading historical database:
” Download completed with error. Check the error log for more details”
For example: For VDN ID, you see the following error message in the error log:
”1101 Database error:[hvdn] The field is too small to accept……….. ”
BCMRD R2.4.2 database supports both 7-digit dial plan and 13-digit dial plan to prevent any
errors while downloading and allow smooth display of historical report irrespective of the dial plan
you are using. The database is modified to support upgraded switches offering a 13-digit dial
plan. It also supports special characters "-" (hyphen) and "." (dot) for all the supported dial plans.
3. Database Merge Utility
In BCMRD R2.4.2, changes in database schema enable supporting a 13-digit dial plan. The
Database Merge Utility enables migrating data from a previous database with an older schema to
the latest database.
The Database Merge Utility is a generic merging tool to merge databases very effectively. In case
there is a need to generate historical reports from more than one old databases, this merge utility
should be used to first merge the old databases repeatedly until we have one composite old
database and then this merge utility should be used to merge the old and new database. You can
"-" (hyphen) and "." (dot) for Agent Login ID and VDN ID are used then the following
Use Pursuant to Company Instructions Page 3 of 15
Avaya Inc. – Proprietary
Basic Call Management Reporting Desktop R2.4.2 Release Notes
merge the databases even if multiple historical databases (histdb.mdb) exist as a result of
multiple server profiles.
Copy the file Merge.exe from the folder Merge_Utility and use it to merge the databases.
For more information on usage of this tool, see
Database Merge Utility.
Use Pursuant to Company Instructions Page 4 of 15
Avaya Inc. – Proprietary