You are unable to find the Front End Component Pack in the Programs control panel.
Only the windows login which originally installed the component can see it in the Programs control panel.
MiCC 5.10.X.X
Keywords: front end component pack uninstall programs control panelDuring a new install the Mitel System Check returns an error while checking for deprecated workflow activities.
1. Go to your intended [InstallDir] and add the folders for \Ivr\Workflow\Compiled\.
eg: C:\Program Files (x86)\prairieFyre Software Inc\CCM\Ivr\Workflow\Compiled\
2. Re-run the installer and it will pass this check successfully.
This issue is resolved in MiCC Version 8.X.
MiCC 7.1.X.X
Keywords: deprecated workflow activity install error system checkConfiguring any Classification Codes enables Lifecycle code within the Enterprise service.
Large sites are recommended to keep Lifecycle reporting disabled unless necessary, as it can cause large resource usage. If your configuration has any classification codes programmed in YourSite Explorer, this code is in use regardless of whether Lifecycles are disabled in the configuration, which could result in excess memory usage from the Enterprise Server service.
MiCC 7.1.X.X
Keywords: classification code codes lifeycle enterprise memory use usage large footprint leakCCM displays error and event messages to inform you of successful and unsuccessful operations. A subset of the error and event messages have been assigned unique ID numbers in the form ABC####
| ALM -- Alarms | |
| ALM0001 | IVR File synchronization error |
| ALM0002 | IVR Missing audio file |
| ALM0003 | IVR Port out of service |
| ALM0004 | IVR Ports out of service count |
| ALM0005 | IVR Calls processed per hour |
| ALM0006 | IVR Invalid destination for callback |
| ALM0007 | IVR Workflow failed to execute |
| ALM0008 | IVR Average time to answer |
| ALM0009 | Mitai congestion errors |
| ALM0010 | Connection to alarm agent lost |
| ALM0011 | Service restart detected |
| ALM0012 | High CPU usage |
| ALM0013 | Low disk space |
| ALM0014 | Low available memory |
| ALM0015 | IVR Bad audio file |
| ALM0016 | IVR Insufficient out bound ports |
| ALM0017 | IVR Port in DND |
| ALM0018 | IVR Port not answering |
| ALM0019 | IVR UPIQ port deprived |
| ALM0020 | IVR phone audio error |
| ALM0021 | Data filing IO problem |
| ALM0022 | IIS problem |
| ALM0023 | MSMQ problem |
| ALM0024 | SQL problem |
| ALM0025 | License violation |
| ALM0026 | Invalid configuration |
| ALM0027 | Media server offline |
| ALM0028 | Media server data timeout configuration |
| ALM0029 | PBX to PC time drift |
| ALM0030 | Data collection |
| ALM0031 | Data link |
| ALM0032 | Messaging service down |
| ALM0033 | IQ audio problem? |
| ALM0034 | Invalid agent destination callback |
| ALM0035 | UPIQ port deprived |
| ALM0036 | Maintenance |
| ALM0037 | Queue Control |
| ALM0038 | Service High memory (bytes) |
| ALM0039 | IVR Calls Forwarded |
| ALM0040 | Service High CPU usage (%) |
| ALM0041 | Client Server Version Mismatch |
| ALM0042 | IVR Ports over licensed |
| ALM0043 | IVR Not licensed for Web Callbacks |
| ALM0044 | No Default Audio Driver Found on Local Box |
| ALM0045 | IVR Missing Callflow Device |
| ALM0046 | |
| ALM0047 | |
| ALM0048 | Router Certificate Expiry |
| ALM0049 | Listener Offline |
| ALM0050 | SIP Drive Low Disk Space |
| ALM0051 | SQL Drive Low Disk Space |
| ALM0052 | CCM Drive Low Disk Space |
| ALM0053 | OS Drive Low Disk Space |
| ALM0054 | Resiliency in Effect |
| ALM0055 | HCI/CTI/TAPI Call Control Allowed |
| ALM0056 | HCI/CTI/TAPI Monitor Allowed |
| ALM0057 | Message Waiting |
| ALM0058 | Do Not Disturb |
| ALM0059 | Public Network Access via DPNSS |
| ALM0060 | Recorded Announcement Device |
| ALM0061 | SMDR External |
| ALM0062 | SMDR Internal |
| ALM0063 | Suppress Simulated CCM after ISDN Progress |
| ALM0064 | ACD 2000 - Auto Logout Last Agent On No Answer |
| ALM0065 | ACD Make Busy Walk Away Codes |
| ALM0066 | ACD Real Time Events Feature Level |
| ALM0067 | Extended Digit Length |
| ALM0068 | MCD - Report Transfers |
| ALM0069 | Network Format |
| ALM0070 | Report Account Codes |
| ALM0071 | Report Incoming Calls |
| ALM0072 | Report Internal Calls |
| ALM0073 | Report Meter Pulses |
| ALM0074 | Report Outgoing Calls |
| ALM0075 | SMDR Meter Unit Per Station |
| ALM0076 | SMDR Record Transfer |
| ALM0077 | System Identification |
| ALM0078 | Time Change Reporting |
| ALM0079 | Twenty-four Hour Time Reporting |
| ALM0080 | ANI/DNIS/ISDN/CLASS Number Delivery Reporting |
| ALM0081 | Extended Time To Answer |
| ALM0082 | Standardized Network OLI |
| ALM0083 | Standardized Call ID Format |
| ALM0084 | Report Internal Unanswered Calls |
| ALM0085 | SMDR Extended Reporting Level 1 |
| ALM0086 | SMDR Extended Reporting Level 2 |
| ALM0087 | Report Attendant Name |
| ALM0088 | Account Code Reporting for Internal Calls |
| ALM0089 | Path Reporting for Internal ACD2 Calls |
| ALM0090 | Enable Agent Group Events |
| ALM0091 | Path Real Time Events Enabled |
| ALM0092 | SMDR Time Rollback |
| ALM0093 | ACD Time Drift |
| ALM0094 | System ID Data vs Config Check |
| ALM0095 | Missing Devices Alarm |
| ALM0096 | Historical Agent Activity Alarm |
| ALM0097 | Duplicate System ID withing Cluster |
| ALM0098 | You must perform an initial media server synchronization |
| ALM0099 | Work timer mismatch between this COS and its associated Queues and Agents |
| ALM0100 | MiTAI Link is down |
| ALM0101 | IVR Insufficient outbound ports |
| ALM0102 | Routing Service General Failure |
| ALM0103 | Monitoring agent ringing state not enabled |
| ALM0104 | Carrier plan not associated to a media server or trunk group |
| ALM0105 | Secondary line use detected for agent(s) and "Ignore agent secondary line activity" is not enabled |
| ALM0106 | Calls handled between 11:30pm and 12:30am and "This enterprise operates 24 hours a day" is not enabled |
| ALM0107 | OAI Data link is down |
| ALM0108 | Uncosted extensions making outbound calls |
| ALM0110 | No UPiQ ports programmed on PBX |
| ALM0111 | MiTAI failed to initialize |
| ALM0113 | MiTAI performed a hotrestart |
| ALM0114 | Callback request failed to save |
| ALM0016 | Outbound Dialer failed to execute Outbound Call Flow |
| ALM0117 | Duplicate reporting numbers present |
| ALM0118 | Hotdesking and traditional agent mismatch |
| ALM0119 | Windows Search Service is not started |
| ALM0121 | Router invalid transfer destination |
| ALM0122 | Storage service not polling |
| ALM0123 | CCMRouting database is full |
| ALM0124 | Items in the mail server Failed folder |
| ALM0125 | Emails in FailedRoute state |
| ALM0126 | Media server synchronization failed |
| ALM0128 | Concurrent calls have exceeded licensed amount |
| ALM0129 | Emails in outbox with exceeded max retries |
| ALM0133 | Conversations in Outbox cannot be indexed |
| ALM0134 | Conversations cannot be indexed |
| ALM0135 | Conversations are missing Tag information |
| ALM0136 | Routing Media Service cannot connect to the CCMRouting database |
| ALM0137 | Error playing back Text-to-speech from the Nuance Speech Server |
| ALM0138 | MRCP initialization error |
| ALM0139 | Speech recognition request failed |
| ALM0141 | Failed to save SMS configuration locally |
| ALM0142 | SMS connection creation error |
| ALM0143 | Invalid SMS connection configuration |
| ALM0144 | Invalid SMS service configuration |
| ALM0145 | SMS connection not polling |
| ALM0146 | Update validation mismatch detected |
| ALM0152 | Storage path is not accessible from the Storage Service |
| ALM0153 | Storage path is not accessible from MCCWa |
| ALM0155 | Elasticsearch is down |
| ALM0156 | Unable to move emails to Processed folder |
| CFG - Configuration | |
| CFG0001 | Configuration Service General Failure |
| CFG0002 | Call Accounting Upgrade Failure |
| CFG0003 | Multimedia (MCC) Client History Backup Failure |
| CFG0004 | CCM Configuration Backup Failure |
| CFG0005 | License Server Failure |
| CFG0006 | Couldn't disable Dr.Watson |
| CFG0007 | Unable to acquire invoker DN for third party join/leave control |
| CFG0008 | Unable to unblock CCC ports in the Windows Firewall |
| CFG0009 | Configuration Wizard Unable to Configure CCMWeb for Windows Authentication |
| CFG0010 | Unable to configure CCMWeb for Anonymous Authentication |
| CFG0011 | SIP Address or Line URI Already in Use |
| CFG0012 | An agent shift lasted past midnight |
| CFG0013 | A Front End time is not synchronized to the Router time |
| CFG0014 | Unable to Monitor Performance Counter |
| CFG0015 | YSE: Import CSV general error |
| CFG0016 | YSE: Email server connection test general error |
| CFG0017 | Support package creation general error |
| CFG0019 | Couldn't load license agreement file |
| CFG0021 | Microsoft IIS is not installed |
| CFG0022 | Not enough hard drive space |
| CFG0023 | Not enough RAM |
| CFG0024 | Missing deployment package |
| CFG0025 | Login attempt without adequate licensing to manage the web site |
| CFG0026 | YSE Profile Mismatch |
| CFG0036 | Cannot connect to RealTime server |
| CFG0042 | Powershell 2.0 not installed |
| CFG0043 | The Powershell Lync module is not installed |
| CFG0044 | There was a problem communicating with PBX |
| CFG0045 | There was a problem with your credentials |
| CFG0046 | There was a problem with the supplied MiXML login |
| CFG0048 | An unknown error occurred on the media server |
| CFG0049 | Workstation has lost trust with the domain |
| CFG0050 | An object has already been modified |
| CFG0051 | Enterprise IP address not found in registry |
| VWM - Visual Workflow Manager | |
| VWM0001 | IVR Callback Make Call failed |
| VWM0002 | IVR Callback Calling Customer Invalid Phone Number |
| VWM0003 | No Callflow Associated with Port |
| VWM0004 | Port Is Associated With Another Server |
| VWM0005 | Port's Virtual Identifier is Invalid |
| VWM0006 | Config Service not Running and No DSTourSite in Cache Folder |
| VWM0007 | Tap Call Delayed More Than 100 Times |
| VWM0008 | Tap Call Failed |
| VWM0009 | Duplicate Dialable for Queue Detected |
| VWM0010 | Realtime Events Disabled for Queue |
| VWM0011 | Could Not Connect to Excel File |
| VWM0012 | Port Out Of Service |
| VWM0013 | Port Not Monitored |
| VWM0014 | Failed to Connect to MiTAI Proxy Server |
| VWM0015 | Enterprise Server Real-time Trace Buffer Overflow |
| VWM0016 | Invalid Hunt Group Members Detected |
| VWM0017 | No Sound Card Detected |
| VWM0018 | Invalid Audio File Detected |
| VWM0019 | Outbound Dialer Failed to Execute the Outbound Callflow |
| VWM0020 | IVR Node is missing |
| VWM0021 | No UPiQ ports assigned |
| VWM0022 | CallReceivedEvent Queue is filling up |
| VWM0023 | Transfer activity invalid destination |
| VWM0024 | Call flow creation exceeded 4 seconds |
| VWM0025 | IVR port failed to transfer call due to MiTAI error |
| VWM0026 | PowerShell disabled on IVRInbound/IVROutbound system |
| VWM0027 | WebService configuration out of date |
| MPS - MiTAI Proxy Server | |
| MPS0001 | Failed to Open MiTAI Connection to PBX |
| REP - Reporting | |
| REP0001 | Distribution - Can Not Print Excel Report When Protected View is Enabled |
| REP0002 | Excel Not Installed |
| REP0003 | Exception Thrown on Attempt to Kill Process |
| REP0004 | Generate Report - Data Limit Exceeded |
| REP0005 | Generate Report - Column Limit Exceeded |
| REP0006 | Generate Report - Out Of Memory Exception |
| REP0007 | Invalid Default Printer |
| REP0008 | No Default Printer |
| REP0009 | Report Distribution - Preferred Printer Unavailable |
| REP0010 | Report Distribution - Print Locally |
| REP0011 | No Printers Available |
| REP0012 | Unknown Error |
| REP0013 | Report Distribution - Available Printers |
| REP0014 | Unknown Error Checking for Installed Printers |
| REP0015 | Forecast Report - Unable to Export Forecast to Excel from CCC or WFS |
| REP0016 | Reporting parameter missing. Using default. |
| REP0017 | No report parameter, No default available, setting state failed |
| REP0018 | Report failed to generate. Invalid report parameters |
| REP0019 | Unable to determine the type of report to generate |
| REP0020 | Failed to set the current thread to the specified user |
| REP0021 | No file to distribute |
| REP0022 | Failed to print to PDF |
| REP0023 | Report failed to print locally |
| REP0024 | PDF report failed to generate |
| CaR - Call Recording | |
| CAR0001 | Oaisys Call Not In Progress During Call Tagging |
| CAR0002 | License not available |
| CAR0003 | Could not reach OAISYS server |
| SMA - Service Monitoring Agent | |
| SMA0001 | Unable to Connect to the Service Monitoring Agent |
| SMA0002 | Monitored Services Disabled |
| SMA0003 | Alarm Has Expired and Will Be Cleared |
| MAD - Maintenance Alarm Dispatcher | |
| MAD0001 | Unable to Connect to the Maintenance Alarm Dispatcher |
| MAD0002 | Unable to Connect to the Alarm Feed |
| MAD0003 | Unable to Find the SNMP Memory Mapped File |
| DSS - Data Synchrtonization Service | |
| DSS0001 | Unable to Access an Active Directory (AD) Object |
| DSS0002 | Multiple media servers with same IP address |
| DSS0003 | Synchronization failed due to MiXML error |
| DSS0004 | Synchronization failed due to Intertel error |
| DSS0005 | Synchronization failed due to Active directory error |
| DSS0006 | Synchronization failed due to Commit error |
| DSS0007 | Synchronization failed due to Unknown error |
| DSS0008 | Queue conversion failure |
| IGN - Ignite | |
| IGN0001 | Cannot sign in to Ignite |
| IGN0002 | IVQ panel is missing when Ignite is launched |
| IGN0003 | Ignite no longer offers Agent Control features |
| IGN0004 | Ignite no longer responding after long period of time |
| IGN0005 | Ignite stops functioning correctly |
| IGN0006 | Requested media item not found |
| ELS - Elasticsearch | |
| ELS0001 | Elasticsearch sniffing error caught. Unable to connect to Elasticsearch server. |
Out Of Memory exceptions being thrown by MiContact Center services as a result of a memory leak int he MiTAI Client being used.
This HotFix is to be applied onto MiContact Center 7.1.3.2 .
1. Download the attached KB355769.EXE to the MiCC server.
2. Double-click the KB355769.EXE file and follow the on-screen prompts.
NOTE: Installing this hotfix will restart the MiContact Center services. In order to avoid service interruption we recommend applying the update after hours, or during a scheduled maintenance window.
MiCC 7.1.3.2
Keywords: KB355769 355769 out of memory exception leak mitaiAn agent is being placed unexpectedly in MakeBusy state.
The agent is picking emails or chats from the queue, rather than waiting for them to be delivered. These items are not being handled immediately.
Items that are picked, rather than delivered are subject to a sperate requeue timer.
You can control the requeue timer for multimedia items picked using the Global Application Settings Editor.
1. Go to [InstallDir]\Services\ConfigService\.
2. Launch the GlobalAppSettingsEditor.exe.
3. Fill in the following:
Application: RoutineMediaService.exe
SectionGroup: Mitel.Routing.Acd.AcdRouterSettings
Name: (enter DefaultPickEmailRequeueTime for email, or DefaultPickChatRequeueTime for chat)
Value: (enter the desired time in HH:MM:SS format)
Description: (enter who or why the setting is being changed here)
4. Click Save.
NOTE: It can take up to two minutes for the save to take effect. Wait for the confirmation prompt before closing the Global Application Settings Editor.
MiCC 8.0 and newer
Keywords: agent MKB make busy makebusy pickPrior to MiContact Center Version 8.0.0.0 we did not have a selection for Teleopti in YourSite Explorer. You can still configure a Teleopti connection, however.
In YourSite Explorer select the WFM type of TotalView, as most of the options behave the same. See the Installation Guide for more details.
In particular, ensure that you double check:
These settings must match those on the Teleopti server under the Mitel section of it's configuration.
MiCC 7.X
Keywords: teleopti wfm workforce management connectorUsers encounter an error message when trying to export a Forecast to Excel from inside the Contact Center Client or WorkForce Scheduling clients.
Error
Forecast was not exported to Excel.
There are two reasons why exporting forecasted reports to excel may sometimes not work which are independent of our software
1. Security issue with template file location
The excel report builder works by droping a dataset onto an report excel template file. The issue is that the template file location has not been identified by the Excel app as a trusted location. This causes a dialog message to appear stating "Office has detected a problem with this file. Editing it may harm your computer". This dialog prevents the report builder from exporting the report to excel and throws an exception. Error screeshots and logs are attached.
The steps to fix this issue are:
1. Click Start, Run and type Excel
2. Click the Dash Arrow icon in the Title bar (see "dash arrow excel" attachment)
3. Select more commands
4. Select Trust Center
5. Click Trust Center Settings
6. Select trusted locations
7. Click add new location
8. Add the location of the xlt file so Excel will know to trust the file
2. Microsoft Excel license renewal dialog
If an excel license needs to be renewed a dialog message is launched each time excel is opened prompting the user to renew their license. Again, this dialog prevents the report builder from exporting the report to excel and lauches a dialog.
6.0 SP1 through 7.1.X.X
Keywords: REP0015 forecast report unable to export forecast excel CCC WFSThe 8.0 Installer fails to install pre-requisite components.
The installer logfile displays an error like the following:
Error: 2015-Dec-23 15:00:26.529 The operation has exceeded the timeout without completion. ()
Error: 2015-Dec-23 15:00:26.531 Exception caught while attempting to deploy package:
--- Start Exception Stack ---
System.Exception: The operation has exceeded the timeout without completion. Please check that your firewall is disabled and check log for more details.
at prairieFyre.Installer.Core.Actions.ChocolateyInstaller.Process() in e:\TeamBuild\CCS\8.0.0.0_Deployment\src\Source\Applications\pfInstaller\prairieFyre.Installer.Core\Actions\ChocolateyInstaller.cs:line 87
--- End Exception Stack ---
()
Info: 2015-Dec-23 15:00:26.531 Finished ChocolateyInstaller ()
Either a firewall or network condition is preventing the installer from downloading the needed files for pre-requisite installation.
Use the Offline Install procedures as described below for local or remote installations.
To perform an offline installation of the MiCC Server
To perform an offline installation of the Remote Server Components
MiCC Version 8.0 and newer
Keywords: install installation fail fails error firewall pre-requisite componentsIt is possible to install IVR on a remote server in order to have it running independently rather than be co-located with the enterprise software.
Below are the steps we recommend following to ensure the remote IVR is setup correctly.
1. Install the core Contact Center Solutions software on the Enterprise Server.
2. If the Remote IVR is the only instance, and this is not setup to run on the Enterprise Server as well, we recommend disabling all but one of the IVR Services on the Enterprise Server. This step is not required however it will free up resources and reduce excess logging on the Enterprise Server. The services to be disabled are:
3. Download and install the Remote Server software on the remote server, from the Optional Components section on the Mitel Online Downloads page.
4. Ensure the IVR Services are registered and running on the remote server by going to Start =>Run and typing services.msc.
5. Ensure that the MSMQ private queues have the Anonymous permission added to the needed queues To do so:
6. Log into the YSE from either system and proceed with the setup of the IVR as you would normally.
7. When creating the Ports, choose the option for “This is a remote port” and choose the remote server name from the selection.
NOTE: If you are only licensed for one IVR Server, you need to ensure all your ports are listed as being on the same server, or you will encounter errors about licensing. All of the Ports need the same server name; none can have the other server selected or be blank.
8. Work Flows, and Media (audio files, etc.) are replicated automatically from the Enterprise Server to the Remote Server. To ensure proper replication between servers, ensure they are on the same Domain or WorkGroup and that they are on the same Subnet.
NOTE: To test that the permissions are correct, you should be able to access the shared directory on either system from the other without a logon prompt. For example, on the remote server, type into an explorer or run window the UNC path for the Enterprise Server's IVR directory and ensure you can access it without a windows authentication message coming up. IE: \\maincomputer\ivrdirectory should take you right to the IVRDirectory on the main computer from the remote computer, without asking you to login. This folder requires that both the Administrators group, and Everyone group be given Read/Write permissions. The Routing Inbound service on a remote IVR should run using the same service account as the Configuration service on the Enterprise server.
Client Applications: The Contact Center Client, YourSite Explorer and other applications are installed on the remote node during the installation process. However, the shortcuts are not created due to feedback from the field. The programs do exist however and can be run from the <install dir>\ccm\applications folder. Also, if you run the Client Role Selector, you can choose to create the shortcuts for them.
Firewall Rules: The following ports need to be open for traffic in both directions between the two servers:
Services on the Remote Server: The Remote Server software at this time installs all the remote components, not just the ones for the IVR. In a future release, you will be able to choose to just install the ones you need.
In regards to the remote IVR, the only services required are:
The rest can be disabled and shut-down.
IVR 6.0 and higher
Keywords: Remote Server setup installation howto IVRThe attached document contains the detailed release notes for MiContact Center Version 8.1.0.0
MiCC 8.1.0.0
Keywords: DRN 8.1.0.0 release notesThe following table shows the required version of .NET required for proper operation of the MiContact Center software including the Client Component Pack. For additional details, please refer to the Contact Center Solutions Systems Engineering Guide, and the Contact Center Solutions Installation Guide.
| MiContact Center Release | Required Framework Version |
|---|---|
| 5.7 | .NET 3.5 |
| 5.8 | .NET 3.5 |
| 6.0 | .NET 3.5 and .NET 4.0 |
| 7.0 | .NET 3.5 and .NET 4.5 |
| 8.0 | .NET 3.5 and .NET 4.5 |
| 8.1 | .NET 3.5 and either .NET 4.5 or 4.6 |
| Software Version | Supported MiVB (3300 ICP) Release for Synchronization |
| CCM and IQ 5.3 GA | Rev 7 - Rev 9 |
| CCM and IQ 5.4 GA | Rev 7 - Rev 9 |
| CCM and IQ 5.5 GA | Rev 8 - Rev 9 |
| CCM and IQ 5.5 SP3 | Rev 8 - MCD 4.0 (With the installation of KB27061) |
| CCM and IQ 5.6 GA | Rev 8 - MCD 4.0 |
| CCM and IQ 5.7 GA | Rev 8 - MCD 4.0 |
| CCM and IQ 5.7 SP1 | Rev 8 - MCD 4.2 (with Hotfix Rollup KB41351) |
| CCM and IQ 5.8 GA | Rev 8 - MCD 4.2 |
| CCM and IQ 5.8.0.7 | Rev 8 - MCD 4.0 SP3, MCD 4.2, MCD 5.0 (base version only) |
| CCM 6.0.0.0 and IQ 5.8.0.9 | MCD 4.0 SP4, and MCD 5.0 through MCD 5.0 SP1 |
| CCM 6.0.1.0 and IQ 5.8.0.9 | MCD 4.0 SP4, and MCD 5.0 through MCD 5.0 SP2 PR1 |
| CCM 6.0.1.1 and IQ 5.8.0.9 | MCD 4.0 SP4, and MCD 5.0 through MCD 5.0 SP2 PR2 |
| CCM 6.0.2.0 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, and MCD 6.0 |
| CCM 6.0.2.1 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, and MCD 6.0 |
| CCM 6.0.2.2 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, MCD 6.0, and MCD 6.0 SP1 |
| CCM 6.0.2.3 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, MCD 6.0 through MCD 6.0 SP2 |
| CCM 6.0.3.0 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, MCD 6.0 through MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| CCM 7.0.0.0 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, MCD 6.0 through MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| CCM 7.0.1.0 and IQ 5.8.0.9 | MCD 4.0 SP4, MCD 5.0 through MCD 5.0 SP2 PR2, MCD 6.0 through MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| MiCC 7.1.0.0 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| MiCC 7.1.0.1 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| MiCC 7.1.1.0 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| MiCC 7.1.1.1 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1 |
| MiCC 7.1.2.0 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, and MCD 7.1* |
| MiCC 7.1.2.1 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, and MCD 7.1* |
| MiCC 7.1.3.0 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, and MCD 7.1* |
| MiCC 7.1.3.1 | MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2 |
| MiCC 8.0.0.0 | MCD 6.0 SP3 (12.0.3.24 or higher), MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, and MCD 7.2 |
| MiCC 8.0.1.0 | MCD 6.0 SP3 (12.0.3.24 or higher)**, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2, and MCD 7.2 SP1 |
| MiCC 8.1.0.0 | MCD 6.0 SP3 (12.0.3.24 or higher)**, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2, and MCD 7.2 SP1 |
The following tables show what versions of .NET, IE, SQL, Windows (Server), and Windows (Client) are supported by version of prairieFyre software. Please note that a * indicates that it is only partially supported and you should check the System Engineering Guide for more details. In cases where the table shows Yes SP# this means that it is supported, and has been tested additionally up to the SP# as well. When in doubt, always check your System Engineering Guide for more detail.
.NET Framework
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.X.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| 3.5 SP1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 4.0 | No | No | No | Yes | Yes | Yes | Yes | Yes |
| 4.5 | No | No | No | Yes* | Yes | Yes | Yes | Yes |
| 4.6 | No | No | No | No | No | No | No | Yes |
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.X.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| IE 6 | Yes | Yes | Yes | Yes | No | No | No | No |
| IE 7 | Yes | Yes | Yes | Yes | No | No | No | No |
| IE 8 | Yes | Yes | Yes | Yes | Yes | Yes (up to 7.1.0.1 only) | No | No |
| IE 9 | No | No | No | Yes | Yes | Yes | No | No |
| IE 10 | No | No | No | Yes* | Yes | Yes | Yes | Yes |
| IE 11 | No | No | No | No | Yes | Yes | Yes | Yes |
| Edge | No | No | No | No | No | No | No | Yes |
NOTE: With MiCC Version 7.1 and newer we recommend using IE10 or newer. Older versions will work for the most part, but some controls are affected. An example of this is the manual EMail Address field under report distribution being a non-editable field. For sites using Multimedia or the Ignite client we recommend IE11 for best performance and compatibility.
SQL Server
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.0.X | 6.0.1.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| 2005 Express | Yes | Yes | Yes | Yes | Yes | No | No | No | No |
| 2008 Express | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| 2008 Express R2 | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| 2005 SP3 | Yes | Yes | Yes | Yes SP4 | Yes | No | No | No | No |
| 2008 SP1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
| 2008 R2 | Yes | Yes | Yes | Yes SP1 | Yes | Yes | Yes | No | No |
| 2012 Express | No | No | No | No | Yes | Yes | Yes | Yes | Yes |
| 2012 | No | No | No | No | Yes | Yes | Yes | Yes | Yes |
| 2014 Express | No | No | No | No | No | No | Yes | Yes | Yes |
| 2014 | No | No | No | No | No | No | Yes | Yes | Yes |
| 2016 | No | No | No | No | No | No | No | No | No |
| 2016 Express | No | No | No | No | No | No | No | No | No |
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.X.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| 2003 SP2 | Yes | Yes | Yes | Yes | No | No | No | No |
| 2007 SP2 | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
| 2010 | No | No | No | Yes | Yes | Yes | Yes | Yes |
| 2013 | No | No | No | No | Yes | Yes | Yes | Yes |
| 2016 | No | No | No | No | No | No | No | Yes |
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.0.X | 6.0.2.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| XP Pro SP3 | Yes* | Yes* | Yes* | No | No | No | No | No | No |
| 2003 R2 (32-bit) | Yes SP1 | Yes SP1 | Yes Sp2 | Yes Sp2 | Yes Sp2 | No | No | No | No |
| 2008 SP2 (32-bit) | Yes | Yes | Yes | Yes | Yes | No | No | No | No |
| 2008 R2 (64-bit) | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes* |
| Windows 7 32-bit | Yes* | Yes* | Yes* | Yes* | Yes* | No | No | No | No |
| Windows 7 64-bit | No | No | No | Yes* | Yes* | Yes* | Yes* | No | No |
| Small Business 2011 | No | No | No | Yes | Yes* | No | No | No | No |
| Windows 2012 | No | No | No | No | Yes | Yes | Yes | Yes | Yes |
| Windows 2012 R2 | No | No | No | No | Yes | Yes | Yes | Yes | Yes |
| Windows 8 32-bit | No | No | No | No | Yes* | No | No | No | No |
| Windows 8 64-bit | No | No | No | No | Yes* | Yes* | Yes* | No | No |
| Windows 8.1 64-bit | No | No | No | No | No | Yes* | Yes* | No | No |
| Windows 8.1 32-bit | No | No | No | No | No | No | No | No | No |
Windows on the Client
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.0.X | 6.0.2.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| XP Pro | Yes | Yes | Yes | Yes | Yes | No | No | No | No |
| Vista 32-bit | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
| Vista 64-bit | No | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
| Windows 7 32-bit | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes* |
| Windows 7 64-bit | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Windows 8 32-bit | No | No | No | No | Yes | Yes | Yes | Yes | Yes* |
| Windows 8 64-bit | No | No | No | No | Yes | Yes | Yes | Yes | Yes |
| Windows 8.1 32-bit | No | No | No | No | No | Yes | Yes | Yes | Yes* |
| Windows 8.1 64-bit | No | No | No | No | No | Yes | Yes | Yes | Yes |
| Windows 10 | No | No | No | No | No | No | No | Yes | Yes |
| 5.7 GA | 5.7 SP1 | 5.8.0.X | 6.0.X.X | 7.0.X.X | 7.1.X.X | 8.0.0.0 | 8.1.0.0 | |
| 3300 ICP | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| SX-200 | Yes | Yes | Yes | Yes* | No | No | No | No |
| SX-2000 | Yes* | Yes* | Yes* | No | No | No | No | No |
| 5000/Axxess | Yes* | Yes* | Yes | Yes | No | No | No | No |
CCM 5.7 GA, 5.7 SP1, 5.8, 6.0, 7.0, 7.1, 8.0, 8.1
Keywords: compatibility .NET Windows SQL IE internet explorer excelAfter creating an Excel Data Provider in YourSite Explorer you click the Test Connection button and it gets stuck on "Connecting".
After some time a fatal error is reported.
"...did not receive a reply within the configured timeout..."
We will need to reinstall the Microsoft Access Database Engine 2010 components.
1. Go to Control Panel > Programs and Features
2. Uninstall all versions of Microsoft Access Database Engine 2010 present.
3. Click the start menu/button and type in cmd.exe. Right-click the Command Prompt and Run As Administrator.
4. In the command prompt run the following two commands:
MiCC 8.X and newer
Keywords: connecting timeout ODBC query Excel data providerStarting in MiContact Center Version 8.0.0.0, we had added a configuration setting to help control the Storage Service memory usage by capping the number of active emails in the MiCC server at any given time.
The MaxNumberOfActiveEmails will limit the maximum number of active emails in the system. Once this threshold is reached the Storage Service will stop polling for new emails. Once the number of active emails is reduced below the configured threshold the Storage Service will resume polling for new email messages.
In order to be counted as an active email, the MSG file must be in one of the following states:
By default the Storage Service is configured to stop polling for new emails if there are 10,000 active emails. With an average estimated email size of 100 KB, 10,000 mails active means that the Storage Service is holding 1 GB of memory just for emails. You can raise or lower this threshold if you wish.
1. Go to [InstallDir]\Services\ConfigService\.
2. Open the GlobalAppSettingsEditor.exe.
3. Fill in the following:
Application: (leave this blank)
SectionGroup: Storage.Properties.Settings
Name: MaxNumberOfActiveEmails
Value: (enter the maximum number of active emails before the storage service stops polling for new email)
Description: (enter a description of why the change was made and/or by whom here)
4. Click Save.
NOTE: It can take up to 2 minutes to complete the save. Wait for the confirmation message before closing the Global Apps Settings Editor.
MiCC 8.0 and newer
Keywords: storage service polling downloading email emails audit config configuration configurable optionYou can configure a server-wide default for both font and size in webchat. By default we use the Andale Mono font and 11 px size.
1. On the MiCC server go to [InstallDir]\websites\Ccmwa\.
2. Open the Web.config file in an editor such as Notepad.
3. Save a backup of the Web.config as Web.config.old.
4. Find the following values and replace them with your desired ones:
<add key="DefaultAgentChatFontSize" value="11px" />
<add key="DefaultAgentChatFontFamily" value="Helvetica" />
NOTE: The fonts you can choose are limited to:
5. Once the changes are saved in the Web.config file agents will see the new defaults once they refresh their Ignite clients by right-clicking and selecting Refresh, or log out and back in.
MiCC 8.0 and newer
Keywords: default font size chatWhen the FastRecovery option is enabled for the Enterprise Server service, the IVQ monitor will not recover existing calls. it will continue to display new calls coming in as normal.
MiCC 8.0 and newer
Keywords: interactive visual queue ivq fastrecovery restartThe attached article contains the required gateway settings when using a SIP media server with MiContact Center 8.1.0.1 or newer.
In order to use this document, unzip the attached file and run the Settings.htm file to get started.
MiCC 8.1.0.1 and newer
Keywords: golden rules required gateway settings sipThe attached document contains information about applying AMC licensing included with your MiContact Center bundle.
MiCC 8.X
Keywords: AMC licensing MiCC MiContact Center bundle