Quantcast
Channel: Mitel MiContact Center Knowledge Base » Knowledgebase » Popular Articles
Viewing all 453 articles
Browse latest View live

Release Notes for MiContact Center Business version 9.3.2.0

$
0
0
Article ID: 52681 - Last Review: April 26, 2021

INFORMATION

Please see the attached DRN document for details on the MiContact Center Business version 9.3.2.0.

Note that there is both a SIP and MiVoice Business (MiVB) version of the Release Notes. Consult the one relating to your deployment.



APPLIES TO

MiCC 9.3.2.0 

Keywords: detailed release notes


HotFix KB517014 - SMS and Multimedia Reporting fixes

$
0
0
Article ID: 52682 - Last Review: May 13, 2021

PROBLEM

This Hotfix addresses multiple issues:

  • SMS Reply Templates were not being show in Web Ignite
  • Chat Reports were pegging more chats Handled than Answered by Agent Group
  • Historical and Real-Time were giving conflicting Service Levels


RESOLUTION

This Hotfix is to be installed onto MiContact Center Business version 9.3.1.0.

  1. Go to https://www.mitel.com/
  2. Click the Login button.
  3. Click the Sign in button under MiAccess.
  4. On the left, select the Software Download Center.
  5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.1.0 and HotFixes.
  6. Download the KB517014 HotFix to the MiContact Center server.
  7. Double-click the KB517014 and follow the on-screen prompts.
  8. Wait for the repackager and auto-updates to complete. 

NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption please install this patch after hours or during a scheduled maintenance window.



APPLIES TO

MiCCB 9.3.1.0 

Keywords: Hotfix KB517014 517014 SMS reply template chat report service level

HotFix KB513824 - Multiple reporting fixes

$
0
0
Article ID: 52683 - Last Review: May 21, 2021

PROBLEM

This Hotfix addresses multiple issues:

  • SQL Writer not writing due to Duplicate PKeys in Outbound call scenarios in Consolidated Reporting
  • Queue Performance reports showing inaccurate talk times during some conference scenarios
  • Queue Facts for Time To Answer sometimes showing negative value in Consolidated Reporting
  • Maintenance reporting data purge error resulted in missing LifeCycle data


RESOLUTION

This Hotfix is to be installed onto MiContact Center Business version 9.3.0.0.

  1. Go to https://www.mitel.com/
  2. Click the Login button.
  3. Click the Sign in button under MiAccess.
  4. On the left, select the Software Download Center.
  5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.0.0 and HotFixes.
  6. Download the KB513824 HotFix to the MiContact Center server.
  7. Double-click the KB513824 and follow the on-screen prompts.
  8. Wait for the repackager and auto-updates to complete.
NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please apply this patch after hours or during a scheduled maintenance window.


APPLIES TO

MiCC 9.3.0.0 

Keywords: Hotfix 513824 KB513824 reporting consolidated reporting sql writer pkey duplicate talk time to answer

HotFix KB516576 - Multiple SIP fixes

$
0
0
Article ID: 52684 - Last Review: May 25, 2021

PROBLEM

This Hotfix addresses multiple issues:

  1. Web Ignite and Contact Center Client showed multiple calls stuck in queue
  2. Web Ignite was intermittently showing a Work-timer rolling over to 24h remaining after the call hand ended
  3. When the MiVoice Connect Client was shut down from the system tray, Web Ignite was not showing the agent Offline (this fix also requires MiVoice Connect 19.2 SP1, and BluStar 7.3.0.244 or newer)
  4. When one call was requeued the agent would sometime display as being on that call and their next call at the same time
  5. After an attempted consult transfer failed, an agent would remain showing as Non-ACD Hold after the second attempt succeeded
  6. Data summarization failed if the Employee ID was more than 10 characters
  7. Intermittently agents would become stuck in an ACD state and not receive further calls
  8. Calls forwarded to Voicemail were not being credited
  9. Intermittently the system would reuse a CallID resulting in inaccurate real-time
  10. Intermittently agents were presented with ACD calls while in a Busy state
  11. Agent Inbox was showing a call that had already ended.  New calls were routing correctly
  12. After a consult call was cancelled the caller was placed on hold and transferred regardless
  13. If an agent transferred a call to a second queue they would not get Work-timer when they disconnected
  14. Intermittently an Email queue Work-timer would roll over to 24h instead of ending
  15. Data summarization failed if the LastRedirectedDevice was delivered as an ETX
  16. Native events were not linked if the Employee was recreated in YourSite Explorer
  17. Intermittently Queue Performance reports were not pegging Abandons
  18. The MiCCSipSettings.SpecialDeviceDN global application setting did not take effect until the service was restarted



RESOLUTION

This Hotfix is to be installed onto MiContact Center Business version 9.3.2.0 for SIP

  1. Go to https://www.mitel.com/
  2. Click the Login button.
  3. Click the Sign in button under MiAccess.
  4. On the left, select the Software Download Center.
  5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.2.0 and HotFixes.
  6. Download the KB516576 HotFix to the MiContact Center server.
  7. Double-click the KB516476 and follow the on-screen prompts.
  8. Wait for the repackager and auto-updates to complete.
NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption please install this patch after hours or during a scheduled maintenance window.

IMPORTANT:  In order to resolve the issue #3 you will need to install the additional patches mentioned above, and do the following:
  1. Stop bluStar services
  2. Edit ctisrv.ini file in the C:\Windows directory by adding the following line under [PABXSpecific 1] section where x.x.x.x is the MiVC HQ server IP address:
  • [PABXSpecific 1]
  • OutOfServiceLine=x.x.x.x.x
  • Start blustar services


  • APPLIES TO

    MiCC 9.3.2.0 for SIP

    Keywords: Hotfix 516576 KB516576 SIP

    HotFix KB518072 - Multiple Consolidated Reporting fixes

    $
    0
    0
    Article ID: 52685 - Last Review: June 10, 2021

    PROBLEM

    This Hotfix resolves the following issues:

    • ClassificationFacts is missing the QueueID when an agent entered of classification code 
    • When an Agent in Queue 1 diverted a call to Queue 2, the agent in the second queue was pegged incorrectly
    • In QueueFacts some calls showed a negative time to answer
    This Hotfix is only applicable to customers who are using the Consolidated Reporting feature.


    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.2.0

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.2.0 and HotFixes.
    6. Download the KB518072 HotFix to the MiContact Center server.
    7. Double-click the KB518072 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.
    NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please install this patch after hours or during a scheduled maintenance window.


    APPLIES TO

     MiCC 9.3.2.0

    Keywords: Hotfix 518072 KB518072 CR consolidated reporting QueueFacts ClassificationFacts

    Release Notes for MiContact Center Business version 9.3.3.0

    $
    0
    0
    Article ID: 52686 - Last Review: July 30, 2021

    INFORMATION

    Please see the attached DRN document for details on the MiContact Center Business version 9.3.2.0.

    Note that there is both a SIP and MiVoice Business (MiVB) version of the Release Notes. Consult the one relating to your deployment.



    APPLIES TO

    MiCCB 9.3.3.0 

    Keywords: DRN detailed release note notes 9.3.3.0

    HotFix KB521569 - SIP PBX not routing calls if an agent's name contains a special character

    $
    0
    0
    Article ID: 52687 - Last Review: September 10, 2021

    PROBLEM

    MiVoice 5000 not routing calls if an agent's name contains a special character.  Restarting freeswitch temporarily resolves.



    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.3.0.

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.3.0 and HotFixes.
    6. Download the KB521569 HotFix to the MiContact Center server.
    7. Double-click the KB521569 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.

    NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption please install this patch after hours or during a scheduled maintenance window. 



    APPLIES TO

    MiCC 9.3.3.0 

    Keywords:

    Workforce Management data incomplete - How to recover missing data

    $
    0
    0
    Article ID: 52413 - Last Review: September 14, 2021

    PROBLEM

    You find that some data is not being collected correctly by the WFM Connector. 



    SYMPTOMS

    Occasional agent interval data is missing from FTP data sent to WFM server. 



    CAUSE

    Calls which span more than two 15 minute intervals will not be included in the FTP packet since the WFM service is sending data offset only by 15 minutes. For example, a call that arrives at 12:14:59 and lasts until 12:30:01 spans three 15 minute intervals, the 12:00-12:15 interval when it arrived, the 12:15-12:30 interval that it was still occurring in, and the 12:30-12:45 interval when it ended. The 12:00-12:15 interval data was sent to the server at 12:30, so the call that began in interval one and didn't end until interval three is missed in the data upload because that upload occurred at 12:30. 



    RESOLUTION

    Run the historical data recollector with the -auto switch and it will recollect all interval data from the previous day and fill in the missing data.  To increase the accuracy of WFM reports during the day, create a separate scheduled task to run the Historical Data Recollector tool several times throughout business hours using a numeric switch (1-8) to regenerate up to 8 intervals of report data at a time.

    By default, the Historical Data Recollector is found in:  [InstallDir]\Services\WFM\prairieFyre.WFM.Utilities.HistoricalDataRecollector.exe

    Create a new scheduled task using the attached batch file to run one hour after nightly maintenance. By default, maintenance runs at 02:00, so schedule the task for 03:00.

    NOTE: The attached batch file assumes a default [InstallDir] of C:\Program Files (x86)\prairieFyre Software Inc\CCM\ or C:\Program Files (x86)\MiContact Center\.  If you have installed to another location, you will need to edit the batch file accordingly.

    NOTE: Prior to version 8.0.1.0, to rebuild AgentScoreCard (adherence) data, the Historical data recollector must be run manually and the timeframe selected must cross midnight for the day you wish to recreate the scorecard for. For example, you want to recreate the scorecard for Jan 19, 2016 - In the recollection tool, set the START DATE to 01-19-2016 and the START TIME to 23:45 then set the END DATE to 01-20-2016 at 00:15.

    KNOWN LIMITATIONS: Same day WFM reports may be incomplete for the above mentioned reasons. Historical reports will be complete if data recollection is performed. 



    VALIDATING DATA RECOLLECTION

    1. Go to the log: [InstallDir]\Logs\DataProcessor.log.

    2. There will be a log line to indicate that the service has started a summarize job:

    ***********************************STARTING LOGGING 2016-Apr-06 02:02:27.357***********************************

    3. Then not far below, look for a line like the following to indicate what date or date range of call records it is summarizing:

    Info 2016-Apr-06 02:02:32.757 Summarize process information - Summarize for 4/5/2016 starting. Start time: 4/6/2016 2:02:32 AM

    4. After summarize has written to SQL you will see some log lines like:

    Info 2016-Apr-06 02:03:19.721 Summarize process information - Summarize for 4/5/2016 ended. End time: 4/6/2016 2:03:19 AM; Duration: 00:00:46.9646057

    Info 2016-Apr-06 02:03:19.722 Summarize process information - End time: 4/6/2016 2:03:19 AM; Duration: 00:00:47.1370509

    5. If there are no errors or warnings in the logs, writing to SQL has completed at the time indicated.

    6. Next look at the Historical Recollector log to ensure it did not start before the data was sent to SQL by the Data Processor Summarize. The log for the recollector is at [InstallDir]\Logs\prairieFyre.WFM.Utilities.HistoricalDataRecollector.log.

    7. You will see a log line to indicate the recollector has started like this:

    ***********************************STARTING LOGGING 2016-Jun-02 03:12:48.940***********************************

    8. You will see a log line a little lower showing the date range of data to re-send over FTP. It should be for the previous day on an automatically configured re-collection and then a log line farther down showing it has completed:

    Info: 2016-Jun-02 03:12:49.298 Data collected and sent. ()

    9. If there are no warnings or errors, then FTP files should havve been re-sent reflecting summarization of the previous days call records.

     



    APPLIES TO

    MiCC 6.x, 7.x, 8.x 

    Keywords: WFM workforce management connector collector recollector missing incomplete FTP

      


    HowTo - Setup a Reverse Proxy in IIS for webchat

    $
    0
    0

    Article ID: 52451 - Last Review: September 21, 2021

    INFORMATION

    Setting up a reverse proxy for Multimedia Contact Center chat on an IIS web server requires specific configuration options to be enabled. IIS must have the Application Request Routing and URL Rewrite add-ons installed before IIS can be installed. These add-ons are available from http://www.iis.net/downloads/microsoft/application-request-routing.

    To set up a reverse proxy, the web administrator must configure Application Request Routing to enable server proxying and then configure Inbound and Outbound rules. Depending on the web administrator’s preference, that can be done in IIS or in the website’s web.config file. If compression is enabled for your website, you must enable writing to HTTP_ACCEPT_ENCODING.

    To set up a reverse proxy with IIS, you must:

    • Configure Application Request Routing
    • Enable writing to HTTP_ACCEPT_ENCODING (optional)
    • Configure Inbound and Outbound rules using IIS
    • Set up proxy rewrite to support SSL

    Inbound and Outbound rules can be configured using either IIS or web.config.

    Optionally, as an additional step, you can configure your reverse proxy to dynamically use multiple host addresses without having to change your existing settings whenever you want to test or make changes to access. This requires an additional custom server variable in order to support multiple host addresses to be reverse proxied.

    To configure Application Request Routing
    1. Start Internet Information Services (IIS) Manager.
    2. In the Connections pane, select your website.
    3. In the Applications pane, double-click Application Request Routing Cache.
    4. In the Actions pane, select Server Proxy Setting.
    5. Select Enable proxy.
    6. In the Actions pane, click Apply.
    7. Click Back to ARR Cache.

    To enable writing to HTTP_ACCEPT_ENCODING
    1. Start Internet Information Services (IIS) Manager.
    2. In the Connections pane, select your website.
    3. In the Applications pane, double-click URL Rewrite.
    4. In the Actions pane, select View Server Variables....
    5. In the Actions pane, click Add… and enter HTTP_ACCEPT_ENCODING.
    6. Click OK.
    7. In the Actions pane, select Back to Rules.

    To configure your Inbound and Outbound rules using IIS
    1. Start Internet Information Services (IIS) Manager.
    2. In the Connections pane, select your website.
    3. In the Applications pane, double-click URL Rewrite.
    4. In the Actions pane, click Add Rule(s)..
    5. Select Reverse Proxy and click OK.
    6. Under Inbound Rules, enter the Enterprise Server IP address.
    7. Optionally, if you are using HTTPS communications and have SSL enabled and your certificate(s) set up, clear Enable SSL Offloading.
    8. Select Rewrite the domain names of the links in HTTP responses.
    9. After To:, enter the DNS for your corporate website.
    10. Click OK.
    11. Select the Inbound rule and in the Actions pane, click Edit.
    12. Under Pattern, enter ccmwa/(.*).
    13. If you are using HTTP_ACCEPT_ENCODING, under Conditions, click Add and add it with a non-blank value.  This is required as IIS does not let you save a blank value. It must be removed from the web.config file after setting up your Inbound and Outbound rules using IIS.
        NOTE: You must have enabled writing to HTTP_ACCEPT_ENCODING previously.
    14. Under Rewrite URL, update the IP address to include /ccmwa/ in the path.
    15. In the Actions pane, click Apply.
    16. Click Back to Rules.
    17. Select the Outbound rule and in the Actions pane, click Edit.
    18. Under Match the content within field, select everything except Use Custom Tags.
    19. After Pattern:, update the URL address to include /ccmwa/.
    20. Under Action Properties, update the Value field to include ccmwa in the path.
    21. In the Actions pane, click Apply.
    22. Click Back to Rules.
    23. If you are using HTTP_ACCEPT_ENCODING, open your web.config file and remove the HTTP_ACCEPT_ENCODING value.

    To configure your Inbound and Outbound rules using web.config
    1. Navigate to your website’s web.config file and open it in an editor.
    2. Add the following rules to the system.webServer section:
        <rewrite>
            <rules>
            <clear />
                 <rule name="ReverseProxyInboundRule1" stopProcessing="true">
                 <match url="ccmwa/(.*)" />
                 <action type="Rewrite" url="http://192.168.0.1/ccmwa/{R:1}" />
                 </rule>
            </rules>
        <outboundRules>
        <remove name="ReverseProxyOutboundRule1" />
            <rule name="ReverseProxyOutboundRule1" preCondition="ResponseIsHtml1">
            <match filterByTags="A, Area, Base, Form, Frame, Head, IFrame, Img, Input, Link, Script" pattern="^http(s)?://192.168.0.1/ccmwa/(.*)" />
            <action type="Rewrite" value="http{R:1}://localhost/{R:2}" />
         </rule>
            <preConditions>
                <preCondition name="ResponseIsHtml1">
                <add input="{RESPONSE_CONTENT_TYPE}" pattern="^text/html" />
            </preConditions>
            </outboundRules>
        </rewrite>
    1. Update the Inbound rule action type URL address reference to the address of your Enterprise Server.
    3. Update the reference to localhost in the outbound rule action type to the domain of the corporate website.
    4. Save and close the editor.

    To handle multiple host addresses with IIS reverse proxy
    1. Start Internet Information Services (IIS) Manager.
    2. In the Connections pane, select your website.
    3. In the Applications pane, double-click URL Rewrite.
    4. In the Actions pane, select View Server Variables....
    5. In the Actions pane, click Add… and enter HTTP_INCOMMING_HOST.
    6. Click OK.
    7. In the Actions pane, select Back to Rules.
    8. Edit the inbound rule you created earlier.
    9. Under Server Variables, click Add and enter HTTP_INCOMMING_HOST.
    10. Set the value to {HTTP_HOST} and ensure Replace the existing value is selected.
    11. Click OK.
    12. In the Action section, ensure Stop processing of subsequent rules is selected.
    13. Click Apply in the Actions pane and then click Back to Rules
    14. Edit the existing Outbound rule you created earlier.
    15. Under Conditions, click Add.
    16. Set the Condition input to {HTTP_INCOMMING_HOST}. Set “Check if input string:” to
    17. “Matches the Pattern” and in “Pattern:”, enter the host value used in the Action Properties of the Action section. Ensure “Ignore case” is selected.
    18. Click OK.
    19. Click Apply and then Back to Rules in the Actions pane.
    Add additional outbound rules for any additional host values you want to support following the same series of steps.

    To set up proxy rewrite to support SSL
    1. Start Internet Information Services (IIS) Manager.
    2. In the Connections pane, select your website.
    3. In the Applications pane, select URL Rewrite.
    4. Double-click the Inbound Rules.
    5. Under Conditions, click Add.
    6. Under Condition input, enter {CACHE_URL}.
    7. Under Check if input string, select Matches the Pattern.
    8. Under Pattern, enter ^(https?)://
    9. Select Ignore case.
    10. Click OK.
    11. Select Track capture groups across conditions.
    12. Under Rewrite URL, replace http with {C:1}.
    13. Click Apply.


     

    APPLIES TO

    MiCC Webchat Version 8.0 and newer 

    Keywords: reverse proxy webchat

    Release Notes for MiContact Center Business version 9.3.4.0

    $
    0
    0
    Article ID: 52688 - Last Review: October 26, 2021

    INFORMATION

    Please see the attached DRN document for details on the MiContact Center Business version 9.3.2.0.

    Note that there is both a SIP and MiVoice Business (MiVB) version of the Release Notes. Consult the one relating to your deployment.




    APPLIES TO

    MiCC 9.3.4.0 

    Keywords: detailed release notes

    HotFix KB522095 - Multiple fixes for SIP

    $
    0
    0
    Article ID: 52689 - Last Review: November 2, 2021

    PROBLEM

    This Hotfix addresses multiple issues:

    • REST API updated to fully support Agent Group Membership and basic Employee management.

    • Open SIP Agent Transfer not completed after BLIND Transfer
    • Agent answers a Consultation call which then gets cancelled. Agent incorrectly show as on an ACD call
    • Web Ignite 'Call Control' greyed-out for ~ 10 seconds after a Blind Transfer
    • No possibility to make more than one help request
    • Calls not correctly managed in IGNITE if the "remove hold" button was clicked on transitory state during monitored transfer
    • Calls were lost when attempting to transfer to helper


     

    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.3.0 for SIP.

    1. Go to https://www.mitel.com/

    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.3.0 and HotFixes.
    6. Download the KB522095 HotFix to the MiContact Center server.
    7. Double-click the KB522095 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.

    NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please install this patch after hours or during a scheduled maintenance window.

    APPLIES TO

    MiCC 9.3.3.0 

    Keywords: SIP Hotfix 522095 KB522095 transfer helper rest api consult

    HotFix KB522237 - Cloudlink Chat sending out transcipt multiple times

    $
    0
    0
    Article ID: 52690 - Last Review: November 4, 2021

    PROBLEM

    In some cases sites configured to use Cloudlink Chat were sending out multiple copies of the chat transcripts.


    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.1.0.

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.1.0 and HotFixes.
    6. Download the KB522237 HotFix to the MiContact Center server.
    7. Double-click the KB522237 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.
    NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption please install this patch after hours or during a scheduled maintenance window.

    APPLIES TO

    MiCC 9.3.1.0 

    Keywords: Hotfix cloudlink chat transcript duplicate 522237 KB522237

    HotFix KB522969 - Calls still routing to Primary Queue in Virtual Queue Group when PBX is unavailable

    $
    0
    0
    Article ID: 52691 - Last Review: November 15, 2021

    PROBLEM

     Calls still routing to Primary Queue in Virtual Queue Group when PBX is unavailable



    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.4.0.

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.4.0 and HotFixes.
    6. Download the KB522969 HotFix to the MiContact Center server.
    7. Double-click the KB522969 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.


    NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please install this patch after hours or during a scheduled maintenance window.



    APPLIES TO

    MiCC 9.3.4.0 

    Keywords: hotfix 522969 KB522969 virtual queue group

    HotFix KB523043 - Multiple SIP fixes

    $
    0
    0
    Article ID: 52692 - Last Review: November 17, 2021

    PROBLEM

    This Hotfix resolves the following issues:

    • SIP Agent transfer intermittently not completing after blind transfers.
    • SIP Agent shows ACD after creating and cancelling a consultation.
    • Web Ignite 'Call Control' greyed-out for ~ 10 seconds after a Blind Transfer.
    • Calls could be lost on transfer to a helper.
    • Call not correctly managed in IGNITE if button "remove on hold" clicked on transitory state during monitored transfer.
    • It is not possible to make more than one help request.
    • Call hold by the MiCC agent fails if the silent monitor is activated on the agent. The voice is lost.
    • REST API updated to fully support Agent Group Membership and basic Employee management.


    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.4.0.

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.4.0 and HotFixes.
    6. Download the KB523043 HotFix to the MiContact Center server.
    7. Double-click the KB523043 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.
    NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please install this patch after hours or during a scheduled maintenance window.

    APPLIES TO

     MiCC 9.3.4.0

    Keywords: SIP transfer blind consult helper REST api

    HotFix KB523231 - Chat Multimedia reports over-pegging handled chats

    $
    0
    0
    Article ID: 52693 - Last Review: December 1, 2021

    PROBLEM

    Chat multimedia performance reports were over-pegging the number of handled chats. 



    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.4.0.

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.4.0 and HotFixes.
    6. Download the KB523231 HotFix to the MiContact Center server.
    7. Double-click the KB523231 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.
    NOTE:  Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please install this patch after hours or during a scheduled maintenance window.

    APPLIES TO

     MiCC 9.3.4.0

    Keywords: Hotfix 523231 KB523231 chat multimedia performance handled


    Release Notes for MiContact Center Business version 9.3.5.0

    $
    0
    0
    Article ID: 52694 - Last Review: February 22, 2022

    INFORMATION

    Please see the attached DRN document for details on the MiContact Center Business version 9.3.5.0.

    Note that there is both a SIP and MiVoice Business (MiVB) version of the Release Notes. Consult the one relating to your deployment.


    APPLIES TO

    MiCC 9.3.5.0 

    Keywords: detailed release notes

    HotFix KB530024 - Two fixes to PCI compliance workflow behavior

    $
    0
    0
    Article ID: 52695 - Last Review: April 13, 2022

    PROBLEM

    This Hotfix addresses two problems:

    • If the caller hangs up while the agent is on hold, the agent and IVR port call are not cleared.
    • When the caller is done entering the information required and the agent re-joins the conference, the PCI compliance workflow doesn't move on to the next activity until after 10 seconds. 


    RESOLUTION

    This Hotfix is to be installed onto MiContact Center Business version 9.3.5.0.

    1. Go to https://www.mitel.com/
    2. Click the Login button.
    3. Click the Sign in button under MiAccess.
    4. On the left, select the Software Download Center.
    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.3.5.0 and HotFixes.
    6. Download the KB530024 HotFix to the MiContact Center server.
    7. Double-click the KB530024 and follow the on-screen prompts.
    8. Wait for the repackager and auto-updates to complete.

     NOTE: Installing this Hotfix will restart the MiContact Center services.  To avoid service interruption, please apply this patch after hours or during a scheduled maintenance window.



    APPLIES TO

    MiCC 9.3.5.0 

    Keywords: hotfix 530024 KB530024 PCI compliance hold

    Release Notes for MiContact Center Business version 9.4.0.0

    $
    0
    0
    Article ID: 52694 - Last Review: July 11, 2022

    INFORMATION

    Please see the attached DRN document for details on the MiContact Center Business version 9.4.0.0.

    Note that there is both a SIP and MiVoice Business (MiVB) version of the Release Notes. Consult the one relating to your deployment.


    APPLIES TO

    MiCC 9.4.0.0

    Keywords: detailed release notes

    Hotfix KB536902 - Fixes: Unable to save employee added via Pick user from Active directory and Email processing fixes and improvements

    $
    0
    0
    Article ID:  - Last Review: September 20, 2022

    What’s Fixed?

    This Hotfix addresses the following 3 issues:

    Issue Description

    Symptoms

    Resolution

    Unable to save employee that was added in YourSite Explorer using Pick User from active directory when system is configured to use windows authentication

    After pressing “pick user” in YSE to pick an active directory user to import into YSE, you were unable to save that employee due to an incorrect validation error

    No longer will get validation error on password when windows authentication is configured.

    Emails could stop being pulled into the system when multiple IMAP expunge failures cause emails to not be moved to processed folder

    Emails no longer come into the system once we get more than 10 flagged as deleted and unable to be moved to processed folder

    Improved logic to handle this error situation and properly unflag the item in inbox as deleted in order for it to be retried again.

    Global Reply Template name that has a slash in it can cause issues with email handling

    Agents handling emails and using global reply templates would see errors if the global reply template had a slash in the name

    Properly escaping names with slashes

    Cumulative Fixes Included

    The following previous hotfixes are also included in this hotfix:

    Hotfix

    Description

    Link

    KB536401

    Fixes for Microsoft Exchange OAuth mail server connections and Web Ignite Callback Widget issue

    https://mitel.custhelp.com/app/answers/answer_view/a_id/1018450/242437553

    Environment

    MiContact Center Business

    Installation

    This Hotfix is to be installed onto MiContact Center Business version 9.4.0.0

    1. Go to https://www.mitel.com

    2. Click the Login button.

    3. Click the Sign in button under MiAccess.

    4. On the left, select the Software Download Center.

    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.4.0.0 and 9.4.0.0 HotFixes.

    6. Download the "MiCC Hotfix KB536902.exe" Hotfix to the MiContact Center server.

    7. Double-click the MiCC HotFix KB536902.exe and follow the on-screen prompts.

    8. Wait for the repackager and auto-updates to complete. 

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

    Hotfix KB536401 - Fixes for Microsoft Exchange OAuth mail server connections and Web Ignite Callback Widget issue

    $
    0
    0
    Article ID:  - Last Review: September 20, 2022

    What’s Fixed?

    This Hotfix addresses the following 4 issues:

    Issue Description

    Symptoms

    Resolution

    When using OAuth connection with Exchange Online multiple emails could be sent out when agent replies instead of just one

    When an agent replies to and email, in some cases multiple replies are sent to the recipient instead of just one

    Only one reply is now sent out.

    When using OAuth connection with Exchange Online sometimes email replies are not received by recipient when you have two mail servers defined with the same from address even though it appears they were sent in web ignite.

    If you have two mail servers defined in YSE and both have the exact same from address it could cause us to try to send out on the wrong mail server and fail but still show as if it sent successfully.

    Fixed logic when we have multiple mail servers with same from address that we first pick the one assigned to the Email media server from within the storage service. If we can’t find one them we have logging to say why we aren’t able to send the email.

    Unable to support multiple Exchange Online OAuth mails servers that reside on different clouds in Office 365

    If you try to configure a mail sever that lives in an alternate cloud other than the default global outlook.office365.com cloud (ex: US Gov cloud at outlook.office365.us) it will fail to connect

    Added support to not only automatically infer the cloud we are connecting to but in case of any custom future settings provided the ability to override with custom settings if needed.

    Supervisors can see all callbacks in web ignite callback widget even when “may see all queues” checkbox is not checked

    When an employee is logged into web ignite with a supervisor license they were able to see all callback for all queues regardless of setting of “may see all queues”

    The “may see all queues” checkbox setting is now respected in the web ignite callback widget

    Environment

    MiContact Center Business

    Installation

    This Hotfix is to be installed onto MiContact Center Business version 9.4.0.0

    1. Go to https://www.mitel.com

    2. Click the Login button.

    3. Click the Sign in button under MiAccess.

    4. On the left, select the Software Download Center.

    5. Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.4.0.0 and 9.4.0.0 HotFixes.

    6. Download the "MiCC Hotfix KB536401.exe" Hotfix to the MiContact Center server.

    7. Double-click the MiCC HotFix KB536401.exe and follow the on-screen prompts.

    8. Wait for the repackager and auto-updates to complete. 

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

    Viewing all 453 articles
    Browse latest View live