Professional Documents
Culture Documents
1
Release Notes
April 19, 2016
v9.1.0160.0
Contents
Introduction
Environment
Pre-requisites
MiContact Center Enterprise Installation
SMS Gateway Installation
Important Information
Workarounds, Limitations and Known Issues
Hot Fix Numbering Guidelines
Documentation
Tools Directory
Introduction
The purpose of the Release Notes document is to communicate what is provided in this software package.
It also documents workarounds, limitations and known issues.
=========================================================================
Environment
Please refer to the MiContact Center Enterprise Compatibility Matrix (ASE/SEC/PLM/0004) for supported Operating Systems
and Communication Platforms.
Microsoft updates:
For Windows Server 2008/R2 apply the "Important" and "Recommended" updates, provided by Microsoft as of March 1,
2016.
For Windows Server 2012/R2 apply the "Important" and "Recommended" updates, provided by Microsoft as of March 1,
2016.
=========================================================================
Pre-requisites
Before installing MiContact Center Enterprise, the following pre-requisites must be met:
License installation
The Enterprise License Manager (ELM) server must be installed on a server PC.
Please refer to Enterprise License Manager, 23/1553-LXA 119 154 for details.
SNMP integration
To install the MIB files in this folder:
1. Copy the files in this folder to the Solidus server.
2. Run the bat file <ConfigureSNMPTraps.bat> to set it up.
=========================================================================
1. When upgrading MiContact Center Enterprise from a previous product release, ensure that the compatibility mode of the
existing nextccdb is set to a minimum of SQL 2005.
Compatibility may be set lower if the original installation was done using SQL 2000.
The compatibility mode can be changed through the Properties of the database in SQL Management Studio.
2. Make sure to set the authentication mode to Mixed Mode (SQL and Windows Authentication) during SQL setup.
3. Make sure that the TCP/IP network option is checked when setting the SQL Server network support.
4. It is very important to increase the size of TempDB to 25% of the intended size of the MiContact Center Enterprise
database.
5. Model database size should not be more than 5 MB.
For MiContact Center Enterprise systems using an external SQL 2008 server, the following features from SQL 2008 need to be
installed on the MiContact Center Enterprise server:
Siebel installation
If you are using the Siebel integration with MiContact Center Enterprise, you must reinstall the Siebel package.
The installation package is available in the ThirdParty\Siebel75 folder.
OAS security
If OAS security is used, it is very important that a password be assigned to the Windows user account that belongs to the
"AASTRA OAS ADMIN" and "AASTRA OAS CLIENT", Windows Global Groups.
=========================================================================
Please refer to MiContact Center Enterprise Installation Instruction, 3/1531-LXA 119 154 for details on installation.
Note: After SMS gateway is upgraded, open the SMS Gateway configuration utility and click OK. This will allow the Gateway to
connect to SQL (LDCBR00086268).
=========================================================================
Team
ClearQuest Headline
Track
Core Services
Documentation
With ACS solution and hardphone support - CPI must describe list of features supported
201600 LDCBR00091452
by Agent application
203064 LDCBR00091852 SPELL CHECK CAPABILITY - how to install other languages
Agent
Configuration Manager
200261 LDCBR00091074 Default language for phone agent isn't saved
205136 LDCBR00092429 Group closed in web manager does not change in CM
205182 LDCBR00352536 CM shows agent group as read only when created from web manager
206400 LDCBR00092505 Not possible to add same mailaddress as sender for several SG
207815 LDCBR00092790 CM would not add the tenants to the object tree if connection to OAS down
Information Manager
Mobile Agent
Report Manager
Unit format of Sub column "Clerical" is wrong under column "Session State Duration" on
197292 LDCBR00090558
Agent Group Activity report
199297 LDCBR00091007 RM Voice Non Service Call duration not in sync with Incoming and outgoing duration.
203268 LDCBR00091929 Solidus agent group activity report duplicating when no agent column included
204108 LDCBR00092169 CDR call record save as & report outline showing incorrect data
204686 LDCBR00092263 No report data for SG report and Agent activity for Emails SG
205621 LDCBR00092482 CDR call record using save as & report outilne showing incorrect data
205960 LDCBR00092462 Report is incorrect after upgrading to SeC 8.3 SP3
209234 LDCBR00097209 CDR details showing duplicate records when selecting few CDR records
211565 LDCBR00352622 Problem creating User Template in Report Manager after selecting a user templates
Missing scroll bar in agent activity report in report manager after selecting agents in
211570 LDCBR00352624
G`erman locale
211987 LDCBR00352708 No clerical time after no-answer on outbound call
Scheduler
Script Manager
SeCCfg Tool
201408 LDCBR00091392 Maintain user preferences for agents is missing in Seccfg.exe
204728 LDCBR00092295 Unable to launch help from seccfg agent tab
SMS Gateway
Web Manager
199779 LDCBR00090983 User still can change settings even without permission in CM using Web Manager
202304 LDCBR00091657 An unhandled exception in /LM/W3SVC/1/ROOT/WebApp
205138 LDCBR00352541 Possible to select group closed with always open option in web manager
205148 LDCBR00352540 Web manager showing "resend rejected calls to same agent" settings in seconds only
205149 LDCBR00352539 Web Manager showing preferred agent time limit in seconds only
205153 LDCBR00352538 Overflow settings for SG changed in web manager not reflected correctly in CM
205180 LDCBR00352537 Workday Performance Interval values in SG is incorrect in web manager
205543 LDCBR00092409 Can not change HTTP port for Web Server on Solidus Setup
205574 LDCBR00352542 Possible to view and change the settings for account from web manager
205984 LDCBR00092486 WebManager possible to delete vital system objects
Installation
184445 LDCBR00086365 Automatic updates installation does not provide logs for DM and BSA
DBMT
=========================================================================
=========================================================================
Important Information
Integration with CMG Directory
Note that only CMG 8.2 is supported for MiContact Center Enterprise 9.1.
It is strongly recommended that both the MiContact Center Enterprise server and the Script Manager configurations are backed
up before a migration is started and are restored after the migration.
Listed below are the recommended steps for migrating the MiContact Center Enterprise server:
1. Install Enterprise License Manager and add all the necessary licenses (or add the new licenses to your existing
Enterprise License Manager Server).
2. Install IIS, SQL Server 2008/2012 and MiContact Center Enterprise on the new server. Select the option to "Create a
new database" from the MiContact Center Enterprise installation.
3. On the existing Solidus server, use DBMT to backup the Solidus database including CDR data, Campaign data,
Configuration data, Monthly Report data, Script Manager and optionally the Registry information.
4. It is strongly recommended to turn off your existing MiContact Center Enterprise server at this point. If this is not
practical for your situation, extra care must be taken after restoring the data on the new server. If services from the new
server connect to the existing server or multiple servers monitor the same BVD's, it may cause operational problems for
both systems.
5. On the new server, run Script Manager Configuration. Stop all the Script Manager services. Right-click on the server
name in the tree view and select "All Tasks" and then "Backup/Restore". Check the "Restore SM Configuration" box and
then press the Restore button to restore your Script Manager configuration. Do not start the services when prompted
after the restore.
6. Launch DBMT. Stop all Solidus services except for the Broker service and restore the database and optionally the
Registry information.
7. Stop the Broker Service.
8. Run the MiContact Center Enterprise Setup utility. Make any necessary changes to server names (Broker location, Script
Manager services location, OAS Server Names, etc).
9. Start all MiContact Center Enterprise and Script Manager services.
Additional information on upgrade scenarios from previous releases to MiContact Center Enterprise 9.1 can be found in Chapter
2 of Solidus Installation Instruction, 3/1531-LXA 119 154.
1. Create a user account in the same domain as the MiContact Center Enterprise server. The account must have Local
Administrator privileges
2. Logon to the desktop under this account and install any printers that may be used for scheduled reports
3. Open the Service Control Manager and change the logon settings for the CCReport service to use this account
4. Restart the CCReport service
=========================================================================
If the "Phone Agent XML App for 6739i Phones" feature is used, there is a need to edit the <solidus_acd.conf> file with
appropriate credentials after installing 9.1 or upgrading to subsequent Release.
Upgrade via Remote Desktop with another user logged on using the services
Make sure that all other users are logged off on the Remote Desktop.
Some applications services need to be closed during upgrade.
Conference
With X-Link, more than 3 parties can be added to a conference from MiContact Center Agent.
=========================================================================
=========================================================================
Documentation
All CPI is available as pdf documents in the Documentation folder.
=========================================================================
Tools Directory
The Tools directory contains helpful utilities that work with MiContact Center Enterprise, including:
EventSentry A 3rd party tool that monitors the Windows Event Log. Event Sentry can be configured to send
notifications when events take place.
LogReader A tool for viewing log files.
OpenMediaConnect Open Media and Session Information test clients.
Code samples for integrating with MiContact Center Enterprise Real Time Interface service COM
SampleCode interface, integrating an E-mail Knowledge Base with MiContact Center Enterprise, and using the
web-based Information Manager display tools.
SocialMediaPlugin Contains the Solidus Social Media Plugin.
The MiContact Center Enterprise Registry configuration program. This can be used to configure
custom settings in the Windows Registry to change the behavior of MiContact Center Enterprise
SecCfg.exe
services and applications.
Please refer to the SecCfg Help file for more details.