PROBLEM

When searching the list of account codes in Web-Ignite, only the first 15 results will populate and no Search More button is available to see the rest. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.3.0. 

APPLIES TO

8.1.3.0 

PROBLEM

Some calls were being counted twice towards the totals in Queue Spectrum reports. 

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 8.1.3.0.

APPLIES TO

MiCC 8.1.3.0 

CREATING A NEW EMAIL ADDRESS

CREATING A DISTRIBUTION GROUP

• Display Name: This name appears in your organization's address book.  This field is required, and must be unique in the forest.
• Alias: This is the alias for the group.  It cannot exceed 64 characters and must be unique in the forest.
• Description:  This is the description of the group as it will appear in the address book.
• Organizational unit: By default, the New Distribution Group wizard displays the Users container in the Active Directory directory service. To change the default organizational unit (OU), click Browse, and then select the OU you want.
• Owners:  The person creating the group will be added by default.  All other owners can be added by clicking the Add button.
• Members:  Add members to this distribution group.

5. Click Finish.

NOTE:  By default, Distribution Groups are configured to require authentication.  If you configure your SMTP server to not require authentication, you must also ensure that your Distribution Groups are not configured to require authentication.

SETTING SEND AS PERMISSIONS

1. In the EAC, go to Recipients =>Groups.
2. Select the group you wish to edit, then click Edit.
3. Go to the Group Properties page, and click Group Delegation.
4. Click Add next to Send As, and add the necessary users.
5. Click OK.
6. Click Save.

Repeat this process for each queue.

IMAP AND SMTP SETTINGS

APPLIES TO

7.0 and newer, please consult the System Engineering Guide for version compatibility on a specific release.

PROBLEM

When using an Interflow activity to transfer enqueued emails to another destination the FailedRoute alarm (ALM0125) would be thrown frequently, and not all transfers would complete. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.3.0. 

APPLIES TO

MiCC 8.1.3.0 

PROBLEM

Ignite conversation window cuts off most of the buttons used to transfer, hang-up, hold and mute. Mostly found with Lync 2013 client. 

SYMPTOMS

 

Even when trying to expand the conversation window, you are still missing most of the buttons you need for a call.

RESOLUTION

1. Close completely out of Ignite
2. Navigate to the following directory on the agent's computer: [InstallDir]\CCM\Applications\Ignite\
3. Open up Ignite.exe.config with Notepad
4. Search for the line which says WrapperWindowDockingDelayMilliSec
5. By default it will be set to 500 milliseconds.  Change the value to 1000
        <setting name="WrapperWindowDockingDelayMilliSec" serializeAs="String">
        <value>1000</value>
6. Click Save in Notepad and exit
7. Reopen Ignite and test. The time may need to vary (repeat steps above to adjust time further). 

 

APPLIES TO

Contact Center for Lync 5.10.X.X

PROBLEM

This HotFix addresses two issues:

• The Enterprise server service being restarted intermittently due to performance issues.
• The Calls Waiting statistic in the QueueNow monitor not updating reliably for an EMail queue.

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.1.0.

1. Download the attached KB416156.EXE to the MiContact Center server.
2. Double-click the KB416156.EXE and follow the on-screen prompts.
3. Wait for the repackager, and all remote node/client systems to update.

NOTE:  Installing this patch will restart the MiContact Center services.  To avoid service interruption we recommend applying this update after hours or during a scheduled maintenance window.

APPLIES TO

MiCC 8.1.1.0 

SUMMARY

INFORMATION

As of version 8.0, two settings have been added to Multimedia Contact Center to limit the size (in bytes) of all emails being sent from Ignite.  This size limit applies to the email and its attachment(s).  By default, the limit is 10MB, but this limit can be changed in the Global Application Settings Editor (see details below).  

FEATURE BEHAVIOR

Ignite will warn agents when the sum of attachments and email body exceeds the max message size supported by the mail server, and fail the attachment.  

When the agent attempts to send an email, an additional validation is done, and the system will again warn the agent if the email exceeds the max message size. 

In both cases the agent will be able to edit the email reduce the mail message size.

Purpose of the "Failed to Send" Subfolder in Ignite

If the max message size in Global Applications Settings is greater than the max message size that the email server will accept, the system attempts to send the email, the send will fail and the email will be placed in the subfolder “Failed to Send” which resides under the agent’s “Failed” folder. 

For example, if your mail server will only send outgoing messages that are 5MB and under, but you have left the EmailSizeLimitBytes setting at its default value of 10 MB, any email large than 5MB that agents attempt to send from Ignite will end up in the "Failed to Send" folder.  

This failed email will also appear in the supervisor’s “Failed to Send” subfolder which resides under “Failed” folder located in the all level folders. 

To call attention to the presence of emails that have failed to send, the name of the “Failed” folder will change color and appear red when there are emails present in the "Failed to Send" folder.  This color change will be visible in Ignite for both the agent who attempted the send, and for the supervisor.

In both cases the agent and the supervisor will be provided an “Edit” button to correct the size issue and allow the message to be sent again. Protection exists to prevent both the supervisor and agent from simultaneously editing the same email draft. 

CONFIGURING THE EmailSizeLimitBytes

NOTE: The max message size is configurable and is applied to all supported mail servers. Therefore it must be set to the lowest message size supported across all mail servers.

1. Open the GlobalAppSettingsEditor located in [InstallDir]\CCM\Services\ConfigService\

2. Fill in the following details:

• Application:  Leave this blank.
• Section Group:  Select appSetting from the drop-down
• Name:  Enter EmailSizeLimitBytes
• Value:  The default value of 10485760 will appear - equivalent to 10 MB.    http://bit-calculator.com/ can be used to calculate the correct value to enter for a different number of MB.
• Description:  Add a note on why this is being changed.  NOTE: You must enter something in this field in order to save.

CONFIGURING THE UseSmtpSizeLimit

This option is set to False by default.  If set to True, it will attempt to poll each SMTP server for it's own unique size limit.  If it gets a value back from an SMTP server, we will use that value instead of the one specified with EmailSizeLimitBytes specified above.

NOTE:  Polling your mail server automatically will not always yield accurate results.  In our testing some servers return a value larger than they will actually accept.  If you use the UseSmtpSizeLimit setting, please test the auto-detected limit.

1. Open the GlobalAppSettingsEditor located in [InstallDir]\CCM\Services\ConfigService\

2. Fill in the following details:

• Application:  Leave this blank.
• Section Group:  Select appSetting from the drop-down
• Name:  Enter UseSmtpSizeLimit
• Value:  Set this to True
• Description:  Add a note on why this is being changed.  NOTE: You must enter something in this field in order to save.

CONFIGURING the maxAllowedContentLength

In some cases, even with the above two settings users may still receive a warning about the file size.  In this case, you can add this last configuration.

1. Go to [InstallDir]\WebSites\MCCWa\ folder.
2. Make a copy of web.config as a backup.
3. Edit web.config with an application like Notepad.
4. Search for maxAllowedContentLength.  You should find the following section:
        <security>
          <requestFiltering>
            <requestLimits maxAllowedContentLength="26214400" />
          </requestFiltering>
        </security>
5. Edit the length value (in bits) for the maximum size for an email message to be sent (this includes body and all attachments).
6. Save.
7. Restart the Mccwa application pool, or perform an IISRESET.

NOTE: The default value is 25MB.

 

APPLIES TO

8.0 

PROBLEM

IVR Ports were becoming stuck in Dialing or Ringing states intermittently. 

SYMPTOMS

The port logs will show warnings/errors like the following:

Warning: 2017-Apr-27 17:01:06.137   Mitel.Routing.Mitel.Implementation.PlayPromptImplementation - Phone is NOT ready to play prompt - TX is closed, we will wait a max of 2500 ms for TX to open. (8601 - 192.168.1.23)
Error: 2017-Apr-27 17:01:09.230   Mitel.Routing.Mitel.Implementation.PlayPromptImplementation - TX is still NOT open after 2500ms. Playing Prompt anyway. (8601 - 192.168.1.23) 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.2.0. 

1. Download the attached KB404909.EXE file to the MiContact Center server.
2. Double click KB404909.EXE and follow the on-screen prompts.
3. Wait for the repackager and client updates to complete.
4. Install the KB418119 Hotfix.
    NOTE: Any site that installs 404909 must also install 418119 after.

APPLIES TO

MICC 8.1.2.0 

PROBLEM

When a Softphone user was off-hook and went back on-hook at the same moment an ACD call was offered to them, the Answer button would sometimes remain greyed out, resulting in a Requeue. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.2.0. 

APPLIES TO

MiCC 8.1.2.0. 

INFORMATION

The attached documents contains the detailed release notes for MiContact Center Version 8.1.4.0.

MiContact Center Business software can be used with MiVoice Business or SIP (MiVoice Office 400 and 5000) voice platforms.  Although the software is the same, the documentation has been separated for ease of consumption.  Please select the DRN for the appopriate voice platform.

APPLIES TO

MiCC 8.1.4.0 

PROBLEM

When communicating with SQL the WFM Connector's scripts would intermittently time out, or suffer poor performance.

RESOLUTION

This HotFix is to be installed onto MiContact Center Business Version 7.1.3.2. 

1. Download the attached KB421532.EXE to the MiContact Center server.
2. Double-click the KB421532.EXE and follow the on-screen prompts.

NOTE: Installing this HotFix will restart the Mitel services.  To avoid service interruption we recommend applying the patch after hours or during a scheduled maintenance window.

APPLIES TO

MiCC 7.1.3.2

PROBLEM

When configuring your MCD to use a Softphone Extension and a HotDesking ACD agent, you should only need to use one license on your MCD, by setting the Softphone extension to IP Device Only.

INSTRUCTIONS

1. On your 3300, create the softphone device with service level IP Device Only. 




2. Open YourSite Explorer and perform a Telephone System Synchronization.

• Go to Media Servers on the left.
• Click the Synchronization tab at the top.
• Select Telephone System.
• Click the Run button.

APPLIES TO

CCM, all versions. 

PROBLEM

In your realtime monitors, agent Idle times reset to zero after they handle a non-ACD or outbound call. 

SYMPTOMS

The PBX determines who will receive the next call in a path based on the time since their last ACD call, so the Idle time effectively continues to count during non-ACD and outbound calls. 

RESOLUTION

This behavior can be adjusted using a configuration in our Global Application Settings Editor.

NOTE:  The MiVoice Business also resets your idle time based on Agent Skill group Presence, which means that your Idle time in different queues may actually be different.  The MiContact Center real-time does not reflect this particular detail.

1. Open the GlobalAppSettingsEditor.EXE found in [InstallDir]\CCM\Services\ConfigService\.
2. Insert a new entry with the following details:

• ApplicationName: leave this field blank.
• SectionGroup: This should be prairieFyre.BAL.DataAnalysis.Properties.Settings , note that it is case sensitive.
• Name: This will be CalculateLastACDIdleFromLastACD , note that this is case sensitive.
• Value: This should be 1 to enable the feature (0 if you wanted to disable it again).
• Description: Add a note as to why you are adding the feature.  Note that you must have something in this field.

APPLIES TO

CCM 6.0.2.X and newer

SUMMARY

All information contained within this article including a communication channel diagram are attached at the bottom of this page.

The port requirement list covers the following products (and any applications or services installed with them):

• Contact Center Management
• Multimedia Contact Center
• Intelligent Queue
• IVR Routing
• Remote Server Software
• Client Applications (Contact Center Client, Workforce Scheduling Client, Flexible Reporting, SalesForce Integration, YourSite explorer, Outlook MCC Plugin, Mitel Border Gateway Connector (MBG)

Table 1 contains the unique port list required by the suite of services and applications including the port, protocol, and a brief description of its usage.

Table 2 contains deployment scenarios to aid in determining which CCS services and applications are installed depending on your deployment. The server scenarios are:

• Contact Center Management Only
• Contact Center Management with IVR
• Contact Center Management with IVR & MCC
• Remote Server Software

Description of Attachments

The attachment "CCS_PortMapping.xlsx" contains the Contact Center Solutions port mapping list. This table contains the name of the application or service, its executable, type, the port required, its destination server or service, the protocol, and any additional details which may be useful when determining firewall exceptions or network routing. Please refer to this spreadsheet for detailed information.

The attachment "CCS_PortDiagram.pdf" contains the Contact Center Solutions communication channels diagram. This diagram depicts on a visual level which servers are communicating with each other and over what ports

NOTE: The attached files were created based on our 6.X and 7.X software suites. 

Table 1 - Unique Port List

Port	Protocol	Description
21	TCP	FTP connectivity for third party Workforce Management services
25	TCP	SMTP connection for alarms and report distribution
80	TCP	HTTP traffic for CCMWeb
389	TCP	LDAP
587	TCP	Used to send automatic e-mail alarms (When using SSL)
1433	TCP	SQL Traffic
1443	TCP	SQL Traffic
1719-1720	TCP	Freeswitch (MiCC 8.1 and up)
1752	TCP	SMDR data collection from PBX
1754	TCP	Traffic data collection from PBX
3478-3479	TCP	Freeswitch (MiCC 8.1 and up)
4000-4999	TCP	Nuance (MiCC 9.0 and up)
5000-5010	TCP	Contact Center Client
5022	TCP	Web Chat requests
5024	TCP	Real time data stream
5025	TCP	Auditor data stream
5026	TCP	Call control
5030	TCP	Call recording control
5050	TCP	Multimedia Contact Center communication
5060	TCP	Freeswitch (MiCC 8.1 and up)
5066	TCP	Freeswitch (MiCC 8.1 and up)
5070	TCP	Freeswitch (MiCC 8.1 and up)
5080	TCP	Freeswitch (MiCC 8.1 and up)
5090	TCP	Nuance (MiCC 9.0 and up)
5091	TCP	Nuance (MiCC 9.0 and up)
5092	TCP	Nuance (MiCC 9.0 and up)
5152	TCP	Multimedia Contact Center communication
5320	TCP	MiTAI communications (MiCC 8.0 and newer)
5400	TCP	Data stream from remote collector services
6999	TCP	Used to stream real time data to third party Workforce Management applications
7000	TCP	Configuration service and authentication
7001	TCP	Configuration service and authentication
7002	TCP	Configuration service and authentication
7003	TCP	Configuration service and authentication
7004	TCP	IVR Updater service
7011	TCP	Data syncronization with PBX
7443	TCP	Freeswitch (MiCC 8.1 and up)
8000-8001	TCP	MiTAI connection to PBX (MiCC 7.1 and older)
8002	TCP	Server Monitoring Agent
8021	TCP	Freeswitch (MiCC 8.1 and up)
8080	TCP	Freeswitch (MiCC 8.1 and up)
8083	TCP	Callback management and messaging
8084-8085	TCP	Callback management and messaging
8188	TCP	Professional Services dialer port
10001	TCP	Connecting to Wallboard
10118	TCP	Client communication to Exchange for MCC ACD
15373	TCP	ACD data collection from PBX
16384-32768	TCP	Freeswitch (MiCC 8.1 and up)
35001	TCP	External connections to the Mitel Border Gateway on this port translate to port 5030 to the CCM Server inside the corporate network
35002	TCP	External connections to the Mitel Border Gateway on this port translate to port 7001 to the CCM Server inside the corporate network
35003	TCP	External connections to the Mitel Border Gateway on this port translate to port 7003 to the CCM Server inside the corporate network
35004	TCP	External connections to the Mitel Border Gateway on this port translate to port 8083 to the CCM Server inside the corporate network
35005	TCP	External connections to the Mitel Border Gateway on this port translate to port 8084 to the CCM Server inside the corporate network
35006	TCP	External connections to the Mitel Border Gateway on this port translate to port 42440 to the CCM Server inside the corporate network
35008	TCP	External connections to the Mitel Border Gateway on this port translate to port 8188 to the CCM Server inside the corporate network
36000	TCP	External connections to the Mitel Border Gateway on this port translate to port 80 to the CCM Server inside the corporate network
36001	TCP	External connections to the Mitel Border Gateway on this port translate to port 443 to the CCM Server inside the corporate network
36002	TCP	External connections to the Mitel Border Gateway on this port translate to port 5024 to the CCM Server inside the corporate network
36003	TCP	External connections to the Mitel Border Gateway on this port translate to port 5025 to the CCM Server inside the corporate network
36004	TCP	External connections to the Mitel Border Gateway on this port translate to port 5026 to the CCM Server inside the corporate network
42440	TCP	WFS Client connectivity
46600-49500	TCP	MiTAI communications with the MiVoice Business (MiCC 8.X and newer)
50122	TCP	WFS Client connectivity
1433-1434	UDP	SQL Server Traffic
3268-3269	TCP	LDAP Connection
50000-50511	UDP	Console Voice Channel for voice communication to PBX
6800-6803	TCP	MiNET connection to Mitel PBX
9000-9001	UDP	Phone media RTP for voice communication to PBX
9200	TCP	Elasticsearch (MiCC 8.X and up)
9300	TCP	Elasticsearch (MiCC 8.X and up)

Table 2 - Deployment Scenarios

CCM Enterprise Server

• Microsoft World Wide Web Publishing Service (IIS)
• prairieFyre Auditor Server
• prairieFyre CCS Server
• prairieFyre Collector Service (v5)
• prairieFyre Config Service
• prairieFyre Data Processor Service
• prairieFyre Data Synchronization Service
• prairieFyre Maintenance Alarm Dispatcher
• prairieFyre MiTAI Proxy Server
• prairieFyre Reporting Service
• prairieFyre Server Monitoring Agent
• prairieFyre SQLWriter (v5)
• prairieFyre Wallboarder
• prairieFyre Workforce Management Service
• Mitel Networks XML Service (MiXML)
• prairieFyre .NET Enterprise Server
• Elasticsearch (MiCC Version 8.0 and up)
• Freeswitch (MiCC Version 8.1 and up)

 

CCM Enterprise Serverwith IVR

• Microsoft World Wide Web Publishing Service (IIS)
• prairieFyre Auditor Server
• prairieFyre CCS Server
• prairieFyre Collector Service (v5)
• prairieFyre Config Service
• prairieFyre Data Processor Service
• prairieFyre Data Synchronization Service
• prairieFyre Maintenance Alarm Dispatcher
• prairieFyre MiTAI Proxy Server
• prairieFyre Reporting Service
• prairieFyre Server Monitoring Agent
• prairieFyre SQLWriter (v5)
• prairieFyre Wallboarder
• prairieFyre Workforce Management Service
• Mitel Networks XML Service (MiXML)
• prairieFyre .NET Enterprise Server
• prairieFyre Ivr Inbound Service
• prairieFyre Ivr Music Service
• prairieFyre Ivr Outbound Service
• prairieFyre Ivr UPIQ Service
• Elasticsearch (MiCC Version 8.0 and up)
• Freeswitch (MiCC Version 8.1 and up)

CCM Enterprise withIVR & MCC

• Microsoft World Wide Web Publishing Service (IIS)
• prairieFyre Auditor Server
• prairieFyre CCS Server
• prairieFyre Collector Service (v5)
• prairieFyre Config Service
• prairieFyre Data Processor Service
• prairieFyre Data Synchronization Service
• prairieFyre Maintenance Alarm Dispatcher
• prairieFyre MiTAI Proxy Server
• prairieFyre Reporting Service
• prairieFyre Server Monitoring Agent
• prairieFyre SQLWriter (v5)
• prairieFyre Wallboarder
• prairieFyre Workforce Management Service
• Mitel Networks XML Service (MiXML)
• prairieFyre .NET Enterprise Server
• prairieFyre Ivr Inbound Service
• prairieFyre Ivr Music Service
• prairieFyre Ivr Outbound Service
• prairieFyre Ivr UPIQ Service
• Elasticsearch (MiCC Version 8.0 and up)
• Freeswitch (MiCC Version 8.1 and up)

Remote ServerSoftware

• prairieFyre Collector Service (v5)
• prairieFyre Ivr Inbound Service
• prairieFyre Ivr Music Service
• prairieFyre Ivr Outbound Service
• prairieFyre Ivr UPIQ Service
• prairieFyre MCC Exchange Objects
• prairieFyre MCC Exchange Setup
• prairieFyre Server Monitoring Agent
• prairieFyre Wallboarder
• prairieFyre Updater Service
• prairieFyre MiAudio Emulation Server
• prairieFyre MiTAI Proxy Server

Client Installations

• Contact Center Client
• WorkForce Scheduling Client
• Flexible Reporting
• SalesForce Integration
• YourSite Explorer
• Outlook MCC Plugin
• Mitel Border Gateway Connector (MBG)
• Spring Board (Professional Services ONLY)

Revision Notes:

March 22, 2013 - Initial documentation released
April 12, 2013 - Corrected MiAUDIO console voice channel port range from 50000-50255 UDP to 50000-50511 UDP.
August 12, 2013 - Updated MiTAI ports to include 8000
April 22, 2016 - Updated to include changes in MiCC Version 8.0 and 8.1
 

Keywords:port list, ports, client ports, tcp, udp, firewall, NAT

INFORMATION 

• The CCM Installer believes UAC is enabled, even after it is correctly disabled.
• Visual C 2010 Runtime Libraries fail to install.

Disabling User Access Control:

When you disable UAC in Windows 2012, the system no longer writes the expected registry key to identify that it has been done, as such our installer believes that it is still enabled.

1. On your keyboard hit the Windows button.  Right-click on the screen and left-click All Apps.  Click on Run, and type regedit.exe
2. browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
3. Find the key named EnableLUA.
4. Right-click this key and Modify.  Change the value to 0.
5. Reboot the computer (it will likely prompt you to do this).


Visual C 2010 Runtime Libraries install error:

Windows 2012 comes with a slightly newer version of the Visual C Runtime Libraries already installed.  This can cause our bundled installer to halt with the error message "Asia". If this occurs, please do the following:

1. Verify the log file indicated in the error message to ensure this is why it is failing.
2. Remove the Microsoft Visual C 2010 Redistributable from Programs and Features.
3. Restart the installation.



APPLIES TO

MiCC 6.0.0.0 and above

Article ID: 52566 - Last Review: December 1, 2017

PROBLEM

When upgrading a site, you change the Software Version from 7.X (or older) directly to 8.1.4.0.  After updating the record, it still shows 7.X licensing objects (listed as EE, BE , Basic, Standard, Advanced, Premium Agents or Employees).

WORKAROUND

1. Set the Software Version back to where it was originally (or 7.1.3.3).  Click Update.
2. Set the Software Version to 8.0.0.0.  Click Update.
NOTE:  The licensing should convert to the 8.X Licensing model now.
3. Set the Software Version to the correct version (8.1.X.X).  Click Update.

If this does not work, please log a ticket with the AMC support team at AMC_Accounts@Mitel.com .

RESOLUTION

A code fix is being applied to the AMC in January 2018 to ensure that the conversion occurs whether you change to 8.0.0.0, or any newer 8.X release. 

APPLIES TO

AMC, MiCC 8.1.4.0

Keywords: AMC conversion license update

PROBLEM

When upgrading a site, you change the Software Version from 7.X (or older) directly to 8.1 (or newer).  After updating the record, it still shows 7.X licensing objects (listed as EE, BE , Basic, Standard, Advanced, Premium Agents or Employees).

WORKAROUND

1. Set the Software Version back to where it was originally (or 7.1.3.3).  Click Update.
2. Set the Software Version to 8.0.0.0.  Click Update.
NOTE:  The licensing should convert to the 8.X Licensing model now.
3. Set the Software Version to the correct version (8.1.X.X).  Click Update.

If this does not work, please log a ticket with the AMC support team at AMC_Accounts@Mitel.com .

RESOLUTION

A code fix is being applied to the AMC on April 4th to ensure that the conversion occurs whether you change to 8.0.0.0, or any newer 8.X release. 

APPLIES TO

AMC, MiCC 8.1 

PROBLEM

In a high call volume environment, it may appear that calls are waiting in queue while agents are idle.

CAUSE

In the 3300's System Options Assignment form, there is an option called "ACD Event Statistics Refresh Rate" which dictates the amount of records pushed per refresh cycle. The default setting is 4, which is more than enough for good call volume. However, this value can be changed to increase the amount of ACD records pushed per cycle.

RESOLUTION

This value can be set to anything from 1 to 100.

APPLIES TO

CCM 5.X and newer

PROBLEM

Intermittently the MiVoice Business sends an unexpected phone logout event.  When this occurs Ignite sees this as an agent logout, and proceeds to logout all other agents associated to the employee.

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.3.0.

1. Ensure that KB410407 is installed.
2. Ensure that KB410718 is installed.
3. Download the attached KB425351.EXE file to the MiContact Center server.
4. Double-click the KB425351.EXE file and follow the on-screen prompts.
5. Wait for the Repackager to complete and any clients to update.

NOTE: Installing this HotFix will restart the MiCC services.  To avoid service interruption we recommend applying the patch after hours or during a scheduled maintenance window.

APPLIES TO

MiCC 8.1.3.0