Quantcast
Channel: Mitel MiContact Center Knowledge Base
Viewing all 959 articles
Browse latest View live

CPU Utilization Expectations during upgrade to 8.X for Existing Multimedia Customers

$
0
0
Article ID: 52429 - Last Review: March 30, 2016

INFORMATION

During upgrades, for Multimedia Contact Center customers, the installer migrates in-queue and in-progress multimedia messages to Elasticsearch. This migration uses a large share of the processor resources and, as such, may adversely affect system stability for Remote Desktop Sessions. After the migration process is complete, the installation continues and processor resources return to normal consumption levels.

NOTE: If system monitoring or management systems are configured to alarm on high resource utilization, a false flag may present during upgrades.
After installation is complete, multimedia interactions continue to be processed in the background and placed into the Elasticsearch archive. Multimedia messages are not searchable via the Ignite client until the message has been archived. Messages are archived, beginning with the most recent interactions, at a rate of approximately 8000 items per hour. The processing rate depends on your processor, available system resources, and number of historical multimedia interactions to be migrated.

Migration speed can be decreased if the server is under high load and you want to prioritize production operations. Migration speed should only be decreased if the system is in a high performance production environment and there is no immediate need to search older archived items. Default settings should provide appropriate performance for the majority of multimedia implementations.

To modify the migration speed, prior to upgrading:
1. Open the Global App Settings Editor in [Install Dir]CCM\Services\ConfigService\ .
2. Fill in the following details:
    • Application: Leave this empty.
    • SectionGroup: StorageService.ElasticsearchMigration.Properties.Settings
    • Name: MigrationDelay
    • Value: The default value is 1. Increasing this value slows down the migration speed. (A value of 100 makes the migration 10 times slower.)
    • Description: Provide a description and click Save.
3. You can now proceed with the upgrade.


APPLIES TO

MiCC Version 8.X and newer 

Keywords: migration multimedia upgrade elasticsearch


Required .NET Framework by Release

$
0
0
Article ID: 52113 - Last Review: February 14th, 2014

INFORMATION

The 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 ReleaseRequired Framework Version
5.7.NET 3.5
5.8.NET 3.5
6.0.NET 4.0
7.0.NET 4.5

ACD record Real-time Format Specification, with Function Codes

$
0
0
Article ID: 51046 - Last Review: April 6, 2016

Real Time Event Format Specification
The basic format for call events is shown in the following illustration. Note that all ASCII
characters are enclosed in single quotes.

Call Event Format

Idle Event Format

Group and Path Statistics Event Format

Refresh Reports Event Format

STX
ASCII start of text. Hex value 2.  NOTE: This is a special character sent by the PBX to denote the start of the record.  It is not saved in the raw data files.

REC NUM
This is a two character field that contains the record number. This field goes from ’00’ to ’99’.
After the ’99’ th record, the numbers cycle back to ’00’.

FUNCTION / EVENT
The following function codes are used for event records:

Aagent login
Bagent logout
Cset DND
Dremove DND
Eset make busy
Fremove make busy
Ganswer ACD call
Hanswer personal call
Ioriginate CALL
Jagent idle
Kgroup report
Lwork timer start
Mwork timer expire
Ncall hold
Ohold retrieve
Phold abandon
Qpath report
Rrefresh reports
Sanswered remote ACD call
TAgent ringing
UAgent end ringing

For a complete list of ACD and MiTAI function codes please see the attached Function_Code_Definitions.pdf file.

TIME
This six character field displays the time in 24-hour format.

DIRECTORY NUMBER
The directory number is a seven character field.

AGENT ID
This seven character field displays the agent ID. Blanks in this field means an agent is not logged
in.

BUTTON NUMBER
This field is the button number of the line appearance that initiated the event. Events that are line
appearance independent, have a button number of zero. The following events always have a
button number of zero:

Note: If ACD Make Busy Reason Codes are used, the reason code is placed in the Button Number field.

  •  agent log on
  •  agent log off
  •  work timer start
  •  work timer end
  •  set make busy
  •  remove make busy
  •  set DND
  •  remove DND event.
The call events that have button numbers are:
  • answer ACD call
  • answer personal call
  • originate call
  • agent idle
  • call hold
  • call hold retrieve
  • call hold abandon

ETX
End of text. Hex value 3.  NOTE: This is a special character sent by the PBX to denote the end of a record.  It is not saved in the raw data files.

Keywords: acd records event real time mitel 3300 pbx technical reference



8.0.0.0 - Detailed Release Notes

$
0
0
 Article ID: 52411 - Last Review: April 12, 2016

INFORMATION

The attached document contains the Detailed ReleaseNotes for MiContact Center Version 8.0.0.0. 


 

APPLIES TO

8.0.0.0

Keywords: DRN Detailed ReleaseNotes 8.0.0.0

7.1.3.1 Release Notes

$
0
0

Article ID: 52356 - Last Review: April 12, 2016

INFORMATION

The attached document contains the Detailed Release Notes for MiContact Center Version 7.1.3.1. 

EDIT NOTE:  Compatible MiVB versions updated as of Oct 19th.  Revised DRN document attached.
 

APPLIES TO

7.1.3.1

Keywords: DRN Detailed Release Notes 7.1.3.1

HotFix KB340635 - IVR workflow continues to process after a hangup activity within a subroutine

$
0
0
Article ID: 52431 - Last Review: April 20, 2016

PROBLEM

After a Hangup activity inside a subroutine, the workflow will continue to process until it reaches an end condition or an error.  If an error is encountered first, an alarm indicating a workflow error is triggered. 



RESOLUTION

This HotFix must be installed onto MiContact Center Version 8.0.0.1.

NOTE: As this HotFix contains client application fixes, you must ensure that all client applications are fully closed.  If a client application is open (including sitting at the login screen) then it will not receive the update until it is next exited.

1. Download the attached MiCC HotFix KB340635.exe file to the MiCC server.
2. Double click the MiCC HotFix KB340635.exe file and follow the on-screen prompts.
3. Wait for the MiCC Redistributable Packager to complete (this may take up to 20 minutes).

NOTE: Installing this hotfix will restart all the MiContact Center services.  In order to avoid service interruption we recommend scheduling the update after hours or during a scheduled maintenance window.


APPLIES TO

MiCC 8.0.0.1 

Keywords: IVR workflow subroutine hangup

HowTo - Configure IVR callbacks when more than one area code is considered a local call

$
0
0
Article ID: 52432 - Last Review: April 22, 2016

PROBLEM

When IVR initiates a callback it will determine whether the call requires a 1 for long-distance, or 011 for international based on the saved callback number.  If the server resides in a region where multiple area codes are dialed as local, this can result in misdialed numbers as the 1 for long distance is added to the phone number. 



SYMPTOMS

In the device log for the outbound port you will see an error like the following:

Error: 2016-Apr-22 11:46:34.489   Mitel.Routing.Mitel.Implementation.ConferenceImplementation - Received CallFailedEvent due to Invalid Destination [16151231234]. (4006 - 10.47.34.85)

In the above example, 615 is considered local by the telephone service provider, however since 613 was configured as the local area code in YourSite Explorer the destination has included a leading 1 for a long distance call. 


 

WORKAROUND

There are two ways of working around this limitation.  The first would be to program the ARS Routing rules in your MiVoice Business to correct the outbound dialing digits after IVR has added the leading 1.  This is not the ideal solution in most cases since it requires a large amount of programming on the MiVoice Business.

The recommended workaround is to add a Variable Compare to the outbound subroutines.

1. Open YourSite Explorer and log in as a System Administrator account. 
2. On the left, open the IVR Routing section.  Select Subroutines.
3. Open the Outbound subroutine needing modification.  NOTE: If you use multiple forms of outbound callbacks you may need to add these changes to a voice, web, and abandon callback subroutine.
4. In the outbound subroutine, under the designer pane find the Conference with Customer activity (by default it is inside Menu option 2, just under a Save Callback activity).
5. Just above the Conference with Customer activity add a Variable Compare activity.
6. Right-click the Variable Compare and click Add Variable Compare Condition.
7. Click the Add button at the top to add a new line.  Configure it as follows:

     <<CallbackClientNumber>>     Starts with     ###  

... where ### is the first area code that is local.

8. Click the Add button at the top to add a new line, and configure the next line the same as above, but with the next local area code.  Repeat until you have one line for each local area code.
9. Click the teal bar to the left of the first variable.  Hold SHIFT and click the teal bar to the left of the last variable.  This should highlight all of the lines.
10.  Click the Group OR button at the top.  All the lines should now be linked by an OR.
11. Click OK.
12. You will be back to the subroutine now.  Right-click the Conference with Customer activity and Cut.
13. In the Variable Compare activity, under No Match, right-click and Paste.
14. Click the Conference with Customer under No Match.  In the properties pane on the right ensure that the External checkbox is checked.
15. In the branch for your area codes in the Variable Compare window, right-click and Paste.
16. Click the Conference with Customer activity under the branch for your area codes.  In the properties pane on the right ensure that the External checkbox is unchecked.

What this means is:

  • IF the callback number provided starts with any of the area codes you specified, the system will not attempt to evaluate whether it is long distance and will dial it as provided.
  • ELSE if the callback number provided does not start with any of the area codes you specified, the system will evaluate it as normal and append the 1 for long distance if needed.



APPLIES TO

MiCC IVR all versions

Keywords: Callback callbacks area code local long distance long-distance 

Detailed Release Notes - 8.0.1.0

$
0
0
Article ID:  - Last Review: April 25, 2016

INFORMATION

The attached document contains the detailed release notes for MiContact Center Version 8.0.1.0 


APPLIES TO

MiCC 8.0.1.0 

Keywords: DRN release notes 8.0.1.0


Workforce Scheduling (WFS) clients cannot connect

$
0
0
Article ID: 50623 - Last Review: April 28, 2016

Problem

Workforce Scheduling clients cannot connect to the server



Symptoms

When opening the WFS client you will see the error:
“A network-related or instance-specific error occurred while establishing a connection to the SQL server. The server was not found or not accessible.”



Cause

The Server and clients may not be on the same domain or for whatever reason the clients cannot resolve the computer name of the server, possibly because of a DNS issue.



Resolution

The WFS clients pull down SQL information from the connection string on the server inside the registry.  If the clients cannot resolve this computer name, we need to do one of the following workarounds:

NOTE:  Do not perform step 2 on the MiContact Center server.  This is for client machines only, and can cause serious issues with real-time and softphone control if performed on the server itself.

  1. Edit the connection string on the server to use the IP instead of the computer name.
  • On the server, type regedit in the Run box then press Enter
  • Expand the key HKEY_LOCAL_MACHINE\SOFTWARE\prairieFyre Software Inc\CCM\Enterprise
  • Double click the ConnectionString key on the right and modify the DataSource
    • You should see something in the string like 'Data Source=CCM\SQLEXPRESS'
    • Replace the computer name with the IP address of the server
    • In this example, after the change it would look like 'Data Source=192.168.1.100\SQLEXPRESS'
  • Create a connection string on the client in the registry. There is logic in the system that if a connection string exists on the client, it will use that instead of looking to the server. (This will need to be done on each client)
    • Type regedit in the RUN box to open the registry editor.
    • expand the key HKEY_LOCAL_MACHINE\SOFTWARE\prairieFyre Software Inc\CCM\Common
    • Create a new String Value called CCSConnectionString and set the value to the same as in step #1
  • Edit the hosts file on the local system to resolve the IP address to a computer name. (This will need to be done on each client)
    • With notepad, edit the hosts file located in "c:\WINDOWS\system32\drivers\etc\hosts"
    • Add the server IP address and server computer name on a new line below the loopback (127.0.0.1   localhost)
      • Example: 192.168.1.100     CCM
  • Edit the DNS servers to point the server computer name to the correct IP address.


  • Applies To

    CCM version 5.6 and newer



    INFO - Understanding Overriding State

    $
    0
    0
    Article ID: 52434 - Last Review: May 4, 2016

    INFORMATION

    The MiContact Center software looks at employees as a single phone line in Agent State real-time monitors and some reports, such as Agent Event.  In environments where two lines may be in use at the same time we must chose an overriding state to display. 

    This overriding state is a very simple hierarchy.  The overriding state will be set to the highest ranking state on the following list (where 1 is highest priority and 18 is lowest).

    1. LoggedOut
    2. Idle
    3. ACD
    4. ACDHold
    5. NonACD
    6. NonACDHold
    7. Outbound
    8. OutboundHold
    9. Do Not Disturb (DND)
    10. Worktimer
    11. Make Busy (MKB)
    12. Ringing
    13. System Make Busy
    14. OffHook
    15. CampOn
    16. ForwardedTo
    17. LogIn
    18. RingingNonACD



    APPLIES TO

    MiCC all version 

    Keywords: overriding state info information

    Workflow not being copied to remote IVR server, and has a # character in the name

    $
    0
    0
    Article ID: 52435 - Last Review: May 5, 2016

    PROBLEM

    A workflow is not being copied to the remote IVR server.  When checking the workflow in YourSite Explorer, you find that the workflow name contained the # character. 



    WORKAROUND

    Rename the workflow such that it does not contain the # character.  You must not use thus symbol in workflow names.

    The following symbols can be safely used:   ! @ $ % ^ & * ( ) _ = - ~ ? >< , . : ; " | \ / { } [] `



    APPLIES TO

    IVR, all versions 

    Keywords: workflow copy copied remote ivr # symbol

    Support Boundaries: MiContact Center Web Chat

    $
    0
    0
    Article ID: 52436 - Last Review: May 5, 2016

    INFORMATION

    The implementation of a web chat queue involves both configuration if the MiContact Center server, and a public web server.  Mitel supports our web chat within the MiContact Center software itself.  If you are experiencing difficulties, test the internal URL provided for your web chat.  If it is functioning correctly to that point, then our own support will consider this functioning.

    From the internal URL to the external connection is the responsibility of the customer (Dealer, or end customer) and their web administration team.  Our recommended implementations are either a relative URL, or a reverse proxy.

    NOTE:  We are planning to update this article in the future to expand on the above details.

     

    APPLIES TO

    MCC, all versions 

    Keywords: web chat webchat multimedia mccmicc support

    Supported 3300 ICP releases by CCM versions

    $
    0
    0
    Article ID: 51183 - Last Review: May 6, 2016

    INFORMATION

    Below is a table displays the supported MiVoice Business (3300) software versions for MiContact Center by version.  Using an unsupported MiVoice Business version can result in performance, reporting, or synchronization errors.  We do not test against unsupported MiVB releases, and do not support them.

    Software VersionSupported MiVB (3300 ICP) Release for Synchronization
    CCM and IQ 5.3 GARev 7 - Rev 9
    CCM and IQ 5.4 GARev 7 - Rev 9
    CCM and IQ 5.5 GARev 8 - Rev 9
    CCM and IQ 5.5 SP3Rev 8 - MCD 4.0 (With the installation of KB27061)
    CCM and IQ 5.6 GARev 8 - MCD 4.0
    CCM and IQ 5.7 GARev 8 - MCD 4.0
    CCM and IQ 5.7 SP1 Rev 8 - MCD 4.2 (with Hotfix Rollup KB41351)
    CCM and IQ 5.8 GARev 8 - MCD 4.2
    CCM and IQ 5.8.0.7Rev 8 - MCD 4.0 SP3, MCD 4.2, MCD 5.0 (base version only)
    CCM 6.0.0.0 and IQ 5.8.0.9MCD 4.0 SP4, and MCD 5.0 through MCD 5.0 SP1
    CCM 6.0.1.0 and IQ 5.8.0.9MCD 4.0 SP4, and MCD 5.0 through MCD 5.0 SP2 PR1
    CCM 6.0.1.1 and IQ 5.8.0.9MCD 4.0 SP4, and MCD 5.0 through MCD 5.0 SP2 PR2
    CCM 6.0.2.0 and IQ 5.8.0.9MCD 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.9MCD 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.9MCD 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.9MCD 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.9MCD 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.9MCD 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.9MCD 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.1MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1
    MiCC 7.1.1.0MCD 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.0MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, and MCD 7.1*
    MiCC 7.1.2.1MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, and MCD 7.1*
    MiCC 7.1.3.0MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, and MCD 7.1*
    MiCC 7.1.3.1MCD 6.0 SP3, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2
    MiCC 8.0.0.0MCD 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.0MCD 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

    *MCD 7.1 PR1 is not compatible with MiCC CCM.  We have corrected this in MCD 7.1 PR2 and newer.

    You can lookup the MCD version by build number here:  KB51645

    NOTE: As of Version 7.1.0.0 we no longer support interfacing with an Intelligent Queue (IQ) server.

    Keywords:  3300 ICP synchronization supported releases PBX Firmware MCD

    HotFix KB325438 - Corrected behavior for the ProcessConferenceRecordsInLifeCycle configuration option

    $
    0
    0
    Article ID: 52437 - Last Review: May 6, 2016

    PROBLEM

    In some instances, durations of conference calls are not attributed correctly to some participants.  A configuration option wa simplemented to resolve this, but some specific scenarios were still pegging incorrectly. 


    RESOLUTION

    This HotFix must be applied to MiCC 8.0.0.1


    1. Download the attached KB325438.EXE file to the MiCC server.
    2. Double click the KB325438.EXE file and follow the on-screen prompts.
    3. Go to [InstallDir]\Services\ConfigService\
    4. Launch the GlobalAppSettingsEditor.EXE
    5. Fill in the following details:
    • Application: (leave this blank)
    • SectionGroup: prairieFyre.BAL.DataAnalysis.Properties.Settings
    • Name: ProcessConferenceRecordsInLifeCycle
    • Value: True
    • Description: (enter anything in here)
    6. Click Save.  Note that it can take up to a minute for the changes to save.  Wait for the confirmation prompt.

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

    APPLIES TO

    MiCC 8.0.0.1 

    Keywords: conference duration peg hotfix 325438 KB325438

    HotFix KB341094 - Agents available not being evaluated correctly when agent belongs to multiple queues

    $
    0
    0
    Article ID: 52438 - Last Review: May 6, 2016

    PROBLEM

    QueueNow real-time monitors and ICC Queue Control conditions based on Agents Available for an individual queue were not evaluating the count correctly.

    An agent that belonged to one queue but was not present, which answered a call in a second queue would show as available in both.


    RESOLUTION

    This HotFix must be installed onto MiContact Center Version 8.0.0.1.

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

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

    APPLIES TO

    MiCC 8.0.0.1 

    Keywords: 341094 KB341094 queuenow icc queue control available present


    YSEAppProfile corruption causing issues when opening YourSite Explorer.

    $
    0
    0
    Article ID: 52273 - Last Review: April 30, 2015

    PROBLEM / SYMPTOMS

    The YSEAppProfile.xml file stores temporary, cached information for the YourSite Explorer application that is specific to the Windows user and PC on which YSE is being opened. This file can become corrupted, which causes issues when opening YSE (the program will not open, or will open and immediately throw an error).

    Problems caused by the YSEAppProfile.xml file being corrupted will only be apparent on one PC. They can happen on the server, as well (in this case, they would only happen on the server, and not on other client PCs running YSE).

    Deleting the YSEAppProfile.xml file is very safe, and will not disrupt your CCM server’s operations if done on a production system.


    RESOLUTION

    To delete the YSEAppProfile.xml file:

    1. Close all instances of YourSite Explorer running on your computer.

    2. Open Windows Explorer, and, in the address bar, type the following: %appdata%.
    You will either end up in C:\Users\YourUsername\AppData, or in C:\Users\YourUsername\AppData\Roaming.
    If you are not in the Roaming folder, and you don’t see YSEAppProfile.xml, please go into the Roaming folder and look for the file there.
    3. Delete YSEAppProfile.xml

    4. Open YourSite Explorer.


    APPLIES TO

    CCM version 6.0.0.0 and newer

    Keywords:
    YSEappprofile %appdata  profile YourSite Explorer  YSE  not loading  can’t open

    HowTo: Set up a custom chat request page

    $
    0
    0
    Article ID: 52373 - Last Review: May 11, 2016

    INFORMATION

    MiCC Web Chat comes preconfigured to use a pre-chat page to capture a user name, email address, and an optional topic to request a chat. The user name and email address are required, and as stated, the topic is optional.

    You may have a system in place that has already captured this information in order to have a user logged in to your website/application and as such would like to forgo having your users have to re-enter this information if/when they want to engage in a chat.

    To this end, the preconfigured pre-chat can be bypassed via some configuration and then submitting the correct query string parameters to the chat system.



    CONFIGURATION

    Open up your chat client configuration file and edit the following 2 parameters for either the default configuration and/or whichever queue configurations you have setup that you want to by-pass the pre-chat page for.

    1. Locate the "UsePrechatArea" parameter and set it to "false". This parameter tells the system not to render the pre-chat page.

    2. Locate the "PrechatDataFromUrl" parameter and set it to "true". This parameter tells the system to look at the chat request url and validate that a name, email and optional topic are present in the url to be used to request and render a chat.

    NOTE: in 8.0 the chat client configuration file in CCMWa is called Chat.public.config.DEFAULT.js and in 8.1 it is called chat.public.config.js.



    URL SUBMISSION

    Configure your website/application to render the chat request url with the required parameters. A request to the ccmwa chat url will require the queue id, along with the name, email, and optional topic. For example, if your website was www.wickedtix.com and was fully configured for MiCC web chat, then the url submission for user jon at myaddress@wickedtix.com would look like this:

    http://www.wickedtix.com/ccmwa/chat/26F1A5C3-DD2C-45FF-BE75-2BC7B85012D0?name=jon&email=myaddress@wickedtix.com&topic=Something%20to%20talk%20about

    NOTE: If you omit to include a topic in the url, ensure the "RequireTopic" parameter in your client chat configuration is set to false. If it is set to true, then you will need to pass this in as well.



    APPLIES TO

    MCC Version 8.0 and newer

    Keywords: prechat pre-chat webchat web chat

    Unable to install client or server, with a No Deployment Found error

    $
    0
    0
    Article ID: 52439 - Last Review: May 13, 2016

    PROBLEM

    When trying to install, the installer stops at a screen that reports "No Deployment Found". 



    CAUSE

    The Windows Firewall has been disabled at the service level (not just turned off in the control panel).  Even when turned off, our installer attempts to communicate with the service and if it does not respond this will cause an error. 



    RESOLUTION

    Go into your Services Control Panel and start the Windows Firewall service.  Then go to the Windows Firewall Control Panel and turn it off through this section.



    APPLIES TO

    MiCC 8.X and newer 

    Keywords: no deployment found ccp client component pack install installation installer

    Loading historical data in the Workforce Scheduling tool results in an error message

    $
    0
    0
    Article ID: 52360 - Last Review: October 22, 2015

    PROBLEM

    Loading historical data in the Workforce Scheduling tool results in an error message 



    SYMPTOMS

    When Launching WFS and running the forecasting tool when clicking 'Load Historical Data ' The following error appears in the WFS log file and the page does not load.

    Error: 2015-Oct-07 12:15:35.136 A fatal error occurred, with the message: Could not load file or assembly 'Syncfusion.Grouping.Base, Version=11.3045.0.30, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89' or one of its dependencies. The system cannot find the file specified. ()
    Fatal: 2015-Oct-07 12:15:37.635 Unhandled Exception
    --- Start Exception Stack ---
    System.IO.FileNotFoundException: Could not load file or assembly 'Syncfusion.Grouping.Base, Version=11.3045.0.30, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89' or one of its dependencies. The system cannot find the file specified.
    File name: 'Syncfusion.Grouping.Base, Version=11.3045.0.30, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89'
    at prairieFyre.Forecasting.LoadHistoricalCallData..ctor(IForecastingServer forecastingServer)
    at prairieFyre.Forecasting.CreateForecastingUI.LoadHistoricalData_Click(Object sender, EventArgs e)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Button.OnClick(EventArgs e)
    at System.Windows.Forms.Button.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    --- End Exception Stack ---

    If you launch the forecasting tool directly from Contact Center Client, this function will work properly. 



    CAUSE

    A pair of .DLL files needed are missing from the WFS folder, but present in the Contact Center Client. 



    RESOLUTION

    You will need to copy two files.

    1. Go to [InstallDir]\Applications\ContactCenterClient\.
    2. Copy the syncfusion.grid.grouping.windows.dll and syncfusion.grouping.base.dll files. 
    3. Paste these files into [InstallDir]\Applications\CcsClient\.
    4. Re-launch the WFS application.

    NOTE: These files were correctly added to the installation for WFS in Version 7.1.3.1 and newer.

    APPLIES TO

    MiCC Version 7.1.3.0 

    Keywords: WFS historical data forecasting error

    HowTo - Setup a Reverse Proxy in IIS for webchat

    $
    0
    0

    Article ID: 52451 - Last Review: June 28, 2016

    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 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 ^(. )://.
    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

    Viewing all 959 articles
    Browse latest View live